Add option to load visuals a few slides before -> viewDistance

A feature request. Right now the visuals are loaded when the slide comes into the screen, meaning that (when something heavy) needs load, you start out with an empty screen before the visual flashes on. I was therefore wondering if it was possible to add something akin to viewDistance from revealJS, where you could set how many slides in advance you want to have reveal.js-d3 to start loading the html file.
Not sure if this is possible because it has to be done by revealJS, but perhaps the data-preload could somehow be used from the lazy loading of iframes?

Alright, I started to play with this idea, and it seems that this is doable! Thanks for making me aware of all those new features by the way, I haven't had the opportunity to create a brand new presentation in a while, so I haven't followed much what had changed in the latest Reveal.js updates.
To be honest, that might even simplify how the plugin works ... right now, the iFrames are created only when we navigate to the slide, but because Reveal.js lazy loads all the iFrames by default, it means that I can create all the iFrame when the presentation loads, and only the ones with the data-preload attribute will be loaded in advance if the viewDistance has been set in the options.
I still have to integrate the automatic creation of the fragments in the slide and the option to trigger the latest transistion, but I have a pseudo-working demo right now. Exciting!

Awesome! :D Having the data-preload working for this plugin to give the behavior of viewDistance would be great!
Just to note, I'd love to keep the current behaviour though that it destroys the visual/iframe after you move far enough away (as in, either immediately on slide change, or on viewDistance, so that not too much heavy visuals/iframes remain in the DOM. But that it does reload again if you move backwards and come within viewDistance again)
An no problem! I've been wanting to try out your plugin ever since you notified me about it (what, like a year ago?), but it's literally been that long since I started a brand new (revealJS) presentation, hehe (*^▽^*)ゞ
Good luck with the updates!

@nbremer, a compatible version of the plugin with the viewDistance/data-preload combo can be found in the lazy-loading branch.
Just set the viewDistance option to something greater than 1 and add the data-preload attribute to the container of the visualization you want to preload, and that should work as expected.
I still have to make sure nothing else is broken, but any chance you could test if it works for you?
Note that the keepIframe option doesn't exist anymore, since it is completely useless now with the new implementation of the plugin.
And to answer your question, the iframes are not destroyed anymore, but the content is killed once you get outside of the viewDistance window, so that should work as you expect.

Everything seemed in order, I have merged the changes!

Great! Sorry it was already midnight when I got your message, I had intended to try when I would wake again, hehe (going to try it now ^^)

For me the visuals/iframes that used to be added to the .background section are added to the .slides section instead. For me this now results in those "full-screen" visuals to no longer appear as full screen, but smaller (even in 1920x1080). Would it be possible to add them back to the background again, if they are set on the section itself?
(I also notice that all iframes get loaded at the start, and not only within viewDistance away from the slide though. Not sure if that would make the presentation too heavy, if everything is loaded. I'm sorry, I don't know how to check if the content of an iframe is killed, in case that is what is happening when you are father than viewDistance away. Does that mean that there should be no document present within the iframe?)
BTW, with all visuals being loaded at the start, this has helped to make sure my data is loaded when I get to the slide, either moving forward or backward, so it sort of solves #17 as well (although I'd still be curious for that demo though).

And I noticed that it goes even more "wrong" when your window isn't upholding the 1920x1080 (or whatever size you've set in the options), see for example:

So I'd really need that full background option from before, hehe :)

I spotted the problem, the iframe has to be on the new slide-background-content to be in full screen. Fixing it right now.

@nbremer, commit 496bb070b253001d69e58bf0ba4fb3b76325424d should have fixed the issue. It's in the latest  master.
Does that work on your end?

Also, note that to add your visualization in the background (background slides section of Reveal), don't use the data-background-iframe attribute of Reveal, just create your slide with:

Your title

The above should give you what your are looking for.
Note that by default, if the .fig-container class is added to the
 tag, then the iframe will be added in the corresponding background slide (in the "background" slide section of Reveal). If you want it to be added to the
 and not to the corresponding background slide, then you can add the data-no-background option:

Your title

And to answer your question about the loading of the iframes, they are now created when the presentation initializes, but their loading (documentContent) is dependent of the viewDistance option if it has been setup. So yes, it is normal that from the start all the  tags will be added to the slides, but they won't be loaded until you get to the slide (or are within the viewDistance).

Thank you for looking into this (and all the others) so fast! (thank you explaining the killing of the iframes!).
I'm afraid though that it now only works when I reload the slide where the full background should be, and then only for that slide, while you're on it. For me all the iframes do get loaded at the start (empty  indeed, however it's still empty for slides within viewDistance), but then when I move just one slide, all the iframes are destroyed, and I only see the original empty

 in the .slide-background's that contained the iframes.
I'm now calling it like this:

(It makes no difference if I put the data-preload on it or not, the same behavior stays)

Ah!
Will look into it. I don’t see this behavior on my end, so maybe I need to make a more complex presentation than the current demo.

Just send you a simplified version of my current presentation that still has the issue. Hope you can spot what might be going on :)

Thanks for sending your presentation to me, it helped a lot in understanding the problem!
I believe #19 should have fixed the issue! Merged on master.


Artist Name displays too many characters

Description
So I used this skin for quite a long time, but i recently saw that if my artist name is too long, it will go on my others skins. Is there anyway to clip the artist name with fewer characters? I don't want to change the size since it's perfect in height.
Versions

Rainmeter Version: [4.1.0 r2989]
OS Version: [Windows 10 Home 64bit]
Skin Version: [1.7]

Additional notes/images

Likely related to https://github.com/MarcoPixel/Monstercat-Visualizer/issues/138

Should be fixed with https://github.com/MarcoPixel/Monstercat-Visualizer/commit/afc919fa2020ce680a161924afb32994f71bab3b, check out the README for the manual installation for now.


minor fixes and logo in title bar.

Click here if you want to create code_sniffer's auto-correct Pull Request

See the documentation if you want to get more information about auto-correct.
Document


Incorrect Helm Chart Generated

Output of helm version:
Client: 2.11.0
Server: 2.13.0
Output of kubectl version:
N/A
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
N/A
I've run across an issue in helm chart packaging where an incorrect chart is generated. Here are the steps to reproduce it:
Create a chart A where chart B is a dependency.
Package chart A
Copy chart A to a new directory and unpackage it.
Create an updated version of chart B and publish it to a remote chart-museum.
Change to the unpacked directory for chart A. Update the Chart.yaml version number.
Update the requirements.yaml file to explicitly identify the new version of chart B.
Execute the command "helm dep update".
When you look into the charts directory, you will see B/ and B-X.X.X.tgz.
Repackage chart A. Execute the command: "helm package A".
A new chart with updated version number will be created.
Now, examine the new helm chart:
tar -tzvf A-x.x.x.tgz | sort
what you will see is that the directory charts/B/ is present TWICE, along with all the files.
The behavior when installing this chart can be unpredictable.
I "think" the correct solution should be that if a chart entry is present in requirements.yaml, and it's present in exploded form in the charts directory, then that directory should be removed as part of helm dependency build.

I've verified this but hesitant to label it a bug.
Fetching a tarball from remote, unpacking it, and making modifications to it is not the same as making changes in your git source tree. IMO this is a non-standard workflow. Once a chart version is in a chart repo, it should be treated as if it were immutable.
@gsexton make sense?

@jdolitsky I would mostly agree with you. Our workflow is a little odd. Essentially what I'm doing is a CI/CD Pipeline, and when a child chart is built, building the parent chart and deploying it.
I'm a little bugged about the tar file having the directory contents twice. That's really unexpected, and I think there should be some sort of behavior other than silently ignoring the issue. I've coded my work-around, but it seems like a bug...

@gsexton I understand. I would recommend then to release the child charts as tarballs to your chartmuseum, and keep no record of them in the charts/ dir of the parent chart. Simply reference them in requirements.yaml/requirements.lock and run a "dep update" on a clean source tree prior to installation via CI/CD system

Unless of course they are stored in same git repo, in which case you may not need to use chart repo at all

I'm going to close this ticket due to inactivity, but please re-open if this still needs to be addressed. Thanks!


Module xDSCResourceDesigner was not found in central repository

While working on PR #4 I found that I was not able to install xDSCResourceDesigner from the central repository. Was asked to file an issue on this as I should have been able to pull this down.

Resolved with #16


Fixed all build processes.

Fixed all build processes.

@fordnox @evrifaessa  This pull request integrates all other pull requests and fixes the build issues. I have tagged the security issue with this pull request.

Trying with PHP 8, the installer doesn't pass the database process with this error:
[Mon Apr 19 09:02:28.059870 2021] [php:error] [pid 71876:tid 1832] [client ::1:18736] PHP Fatal error:  Uncaught Error: Undefined constant "BB_PATH_LANGS" in C:\\xampp\\htdocs\\bb-library\\Box\\Translate.php:78\nStack trace:\n#0 C:\\xampp\\htdocs\\bb-di.php(358): Box_Translate->setup()\n#1 C:\\xampp\\htdocs\\install\\install.php(410): Box_Installer->{closure}()\n#2 C:\\xampp\\htdocs\\install\\install.php(109): Box_Installer->generateEmailTemplates()\n#3 C:\\xampp\\htdocs\\install\\install.php(418): Box_Installer->run('install')\n#4 {main}\n  thrown in C:\\xampp\\htdocs\\bb-library\\Box\\Translate.php on line 78, referer: http://localhost/install/install.php
As I can't get through the installation process, I can't test further. Let me try again with PHP 7.

PHP 8 is still not supported. But at least it doesn't seem to be erroring out in tests. Merging.

@timothygwebb something similar happened here:
https://travis-ci.org/github/boxbilling/boxbilling/builds/767548724
mind fixing?


Accessibility features

Allow the user to identify important controls (or come up with a list of static ones) that can be presented with larger buttons in a separate movable panel.

What else would help with accessibility?


Update to work with supported Django versions (2.2-4.1), use GitHub actions for testing

This fixes tests in Django versions up to 2.0. It also contains few code fixes and cleanings.
It contains one change, that could potentially break something - the removal of bare try-except around admin.autodiscover(). I don't know, what was purpose of that, but it could overshadow some admin problems. If there is reason for that, we should catch only certain error classes.

@SeanHayes I have added also Django 2.1 testing, and it passes.

@SeanHayes I have updated the whole project pass tests in currently supported Django versions and migrated to GitHub actions.
I would like to update this project and add some more features. Can you please give me access to this repository? I already have access to PyPI and I can change the home repository there, but I would like to keep the issues and also credit you as creator of this project.


[video_player] Remove embedding dependencies fallback

Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (flutter analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[ ] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[ ] I updated CHANGELOG.md to add a description of the change.
[ ] I signed the CLA.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[ ] No, this is not a breaking change.

There is no change in this PR. Can we close? @blasten


Use correct syntax for 'import qualified' (Haskell)

I'm not sure why you can build it
https://wiki.haskell.org/Import

Did you modify package.yaml locally?
GHC2021 implies ImportQualifiedPost.
Please see: https://ghc.gitlab.haskell.org/ghc/doc/users_guide/exts/import_qualified_post.html#extension-ImportQualifiedPost

I use cabal build


fix: Handle ENOENT error by reducing stageBlocks and stageBlockBytes

It is also reduced when clearing the read cache, so there is no need to change it if the change is too large


Make mapping of bust_stop ID to bus stop name e.g. 1752 -> "Gdansk SKM Zaspa 01" etc..

Implemented partially in #14


feat: Introduce support for init and sidecar containers.

Tests and examples will be added in a follow up pull request, related to jaeger.


Revert "Handling Command failures"

Reverts Microsoft/vsts-agent#1252

@nigurr I revert the commit, please address the comment i had on the original PR


TypeError: can't pickle _thread.lock objects When trying to pickle.dump model

I'm trying to save the model to use it without having to download and read the data itself every time but I get an error:

from stanfordcorenlp import StanfordCoreNLP
nlp = StanfordCoreNLP("/NLP_models/stanford-corenlp-full-2018-01-31")
pickle.dump(nlp, open("/NLP_models/pickled_wrapped_nlp", "w"))

And the error:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: can't pickle _thread.lock objects

What can I do?
Thanks

We can't pickle the StanfordCoreNLP object. Use an Existing Server may help you.


Rules for more fossil name clean up

[ ] Move terms starting with “see” or “See” into Fossil Notes

[ ] Move terms starting with “referred” or “refers” into Fossil Notes

[ ] Move word strings into Fossil Notes “possibly in concretion”, “inoceramid clam and a partial ammonite”, “right rear leg bones”, “cockroach hind wing”, “?patelliform gastropod (limpet) borings”, “cycad pinnule. Quaternary”, “mammal bone fragment”, "small theropod prints", "vole skeletal elements" into Fossil Note

[ ] Move terms with three or more words into Additional Taxonomic Information

[ ] Move terms containing or ending with “var.” or “va.” into Additional Taxonomic Information

[ ] Move terms containing “n. comb.” Or “comb. nov.” into Additional Taxonomic Information

[ ] Move terms containing “n. gen.” into Additional Taxonomic Information

[ ] Move terms containing “mut.” into Additional Taxonomic Information

[ ] Move terms containing “group” or “Group” into Additional Taxonomic Information

[ ] Move terms containing “sensu lato” or “s.l.” Into Additional Taxonomic Information

[ ] Move terms containing “type” into Additional Taxonomic Information

[ ] Move terms containing “indet.” Or “indeterminate” or “incertae” into Additional Taxonomic Information

[ ] Move terms containing brackets “()” into Additional Taxonomic Information

[ ] Move terms containing equal sign “=” into Additional Taxonomic Information

[ ] Move terms containing the word “small” into Additional Taxonomic Information

[ ] Move terms containing the word “transient” into Additional Taxonomic Information

[ ] Move terms containing the word “fragment” “fragments”, “Fragment” or “Fragments” into Additional Taxonomic Information

[ ] Move terms containing the word “ghost” into Additional Taxonomic Information

[ ] Move terms containing the word “of” into Additional Taxonomic Information

[ ] Move term starting with “cf.” or “aff.” into Additional Taxonomic Information

[ ] Move terms starting with “new” or “New” or “nom novo” into Additional Taxonomic Information

[ ] Move terms containing the word “form” or “forma” or “-forma” into Additional Taxonomic Information, e.g. “Buchia okensis forma typica” or “Inoceramus subundatus form B”

[ ] Move terms containing “isp.” Into Additional Taxonomic Information

[ ] Move terms with the word “species” into Additional Taxonomic Information

[ ] Move terms with the word “genus” or “gen.” or “Genre” into Additional Taxonomic Information

[ ] Move terms with the word “juv.” into Additional Taxonomic Information

[ ] Move terms with the word “morphotype” or “morphotypes” or “morph.” into Additional Taxonomic Information

[ ] Move terms with the word “of” into Additional Taxonomic Information

[ ] Change “ex. Gr.” to ex. gr.

[ ] Move “Pseudocycas sp. A. Bell cf. P. unjiga” into Additional Taxonomic Information

[ ] Move “Triassocampe sp. B? ?Tripocyclia cf. acanthus” into Additional Taxonomic Information

[ ] Change “Inoceramuscf. I. naumanni” to “Inoceramus cf. Inoceramus naumanni”

[ ] Move “Melanhippites (Paltechioceras) ?n. sp.” Into Additional Taxonomic Information

[ ] Move “?Juniperus sp. Tsugaepollenites cf. T. mesozoicus” Into Additional Taxonomic Information

[ ] Move non-Genus taxonomic names into Additional Taxonomic Information - ending in “idae”, “inae”, “ptera”, “aceae”, “urae”, “eoidea”

[ ] Move non-Genus terms into Additional Taxonomic Information - Magnoliopsida sp., Hexactinellid sp., Actinopterygii sp., Chondrichthyes sp., Trochodendron sp., Stephanoceratid sp., Gastroplitid sp., Scarabaeoidea sp., Asaphid sp., Corbiculid sp., Proboscidea sp., Arcestid sp., Belemnitida sp., Pisces sp., Thalattosauria sp., Aves sp., Diplograptid sp., Hexaphyllian sp., Lepidodendron sp., Osteichthyes sp., Psiloceratid sp., Ptychoparid trilobite, Solenoporid algae, Sphaeroceratid sp.

[ ]

[ ] Change “Metasequoia occidentalis (Newberry) Chaney” to Metasequoia occidentalis

[ ] Change “Zelkova oregoniana (Knowlton) Brown” to Zelkova oregoniana

[ ] Change “sp.p.” to “sp.” And move names into Additional Taxonomic Information

[ ] Change “Spinoendothyra paracostif era” to Spinoendothyra paracostifera

[ ] Change “Spinoendothyra cost if era” to Spinoendothyra costifera

[ ] Change “Paradainella dainellif ormis” to Paradainella dainelliformis

[ ] Change “Araliaephyllum er. geisleri” to Araliaephyllum cf. geisleri

[ ] Change “Bimuria et . B. superba” to “Bimuria cf. superba”

[ ] Change “Aquilapollenites sp. A. rectus” to Aquilapollenites cf. rectus

[ ] Change “Eoparastaffella ella oval is” to Eoparastaffella ovalis”

[ ] Change “I. victoriae divergens” to Isograptus victoria divergens

[ ] Change “P. parallelus” to Paroistodus parallelus

[ ] Change “C. keelensis” to Cordilleracyathus keelensis

[ ] Change “D. gracilis” to Didymograptus gracilis

[ ] Change “A. undulatus” to Ajacicyathus undulatus

[ ] Change “Myophorella sp. Sff. M. orientalis” to Myophorella aff. Myophorella orientalis

[ ] Change “Strophomena et . S. planumbona” to Strophomena cf. Strophomena planumbona

[ ] Change “Disphyllum sp. A cf. D. goldfussia” to Disphyllum cf. Disphyllum goldfussi

[ ] Change “DicellograpfLts complanatus ornatus” to Dicellograptus complanatus ornatus

@LeannePyle - I think any of the above that are just 1 or 2 occurrences will be more efficiently handled as manual corrections after MVP. There are already so many rules for taxon that it's getting hard to keep track. Can you please spilt out the above that have more that 20 occurrences and we'll deal with those in the scripts and the rest can be handled as a post-MVP task?


Support for google/gemma

Recently google have released gemma model,
Maybe there can be a gemma example?

This has already been added, you can find it here, the associated PR was #1741 .


conda-env-activate can not select an empty env

If I create a new conda env using conda create --name emptyenv then the created env does not have a bin directory and so conda-env-candidates-from-dir does not pick up the emptyenv and thus it is not selectable in conda-env-activate.

Good catch, thank you for raising this!


Add Outlet Icons

Would it be possible to add the following outlet icons to the set :
C14, C19, C39 and their cross-off counter parts ?
Thx !

These following icons have already been published to all our icon-related packages, under the following names:
Outlet C19, Outlet C14, Outlet C39, Outlet Alt, Outlet C19 Off, Outlet C14 Off, Outlet C39 Off and Outlet Alt Off
Our website is old (still on React 17 and MUI 4; we have a story to work on it this quarter), so it is not showing all the Brightlayer UI and Material Design icons. Sorry for the confusion.

Thanks, I found what I was looking for


Ensure pty host logging is recorded from the beginning

Currently the pty host misses a bunch of its initial logs, it ends up connecting shortly after it has started up.

https://github.com/microsoft/vscode/blob/66ea90c593fa93392dfb33edeade8e380c18c50f/src/vs/platform/terminal/node/ptyHostService.ts#L178-L182


[SPARK-45755][SQL] Improve Dataset.isEmpty() by applying global limit 1

What changes were proposed in this pull request?
This PR makes Dataset.isEmpty() to execute global limit 1 first. LimitPushDown may push down global limit 1 to lower nodes to improve query performance.
Note that we use global limit 1 here, because the local limit cannot be pushed down the group only case: https://github.com/apache/spark/blob/89ca8b6065e9f690a492c778262080741d50d94d/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala#L766-L770
Why are the changes needed?
Improve query performance.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual testing:
spark.range(300000000).selectExpr("id", "array(id, id % 10, id % 100) as eo").write.saveAsTable("t1")
spark.range(100000000).selectExpr("id", "array(id, id % 10, id % 1000) as eo").write.saveAsTable("t2")
println(spark.sql("SELECT * FROM t1 LATERAL VIEW explode_outer(eo) AS e UNION SELECT * FROM t2 LATERAL VIEW explode_outer(eo) AS e").isEmpty)

Before this PR
After this PR

Was this patch authored or co-authored using generative AI tooling?
No.

I revised the PR title a little, @wangyum . You can change it back if you want.

Thank you @dongjoon-hyun The new PR title looks better than the previous one.

Merged to master. Thank you @wangyum
Thank you @dongjoon-hyun @HyukjinKwon @yaooqinn too.


Added operator-light

Signed-off-by: Harshit Dandriyal<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

The source blob I am seeing, is totally unoptimized. These svgs are not something to be coded on, so don't prettify it. Adding tabs and spaces and indenetations make it bigger.
Your svg file: https://github.com/meshery/meshery/blob/6a86f4fc1e19dfb835808e6ae22a32e7d842789c/ui/public/static/img/component-svg/operator-light.svg?short_path=2c5daa4
Please download as is from figma.
Additionally, all svgs should have: <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE svg> as their header. See what cytoscape suggests: https://js.cytoscape.org/#style/background-image

@Abhishek-kumar09 Sorry, it was meshery-operator.js being used not operator.js, We can merge this now.

The source blob I am seeing, is totally unoptimized. These svgs are not something to be coded on, so don't prettify it. Adding tabs and spaces and indenetations make it bigger. Your svg file: https://github.com/meshery/meshery/blob/6a86f4fc1e19dfb835808e6ae22a32e7d842789c/ui/public/static/img/component-svg/operator-light.svg?short_path=2c5daa4
Please download as is from figma.
Additionally, all svgs should have: <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE svg> as their header. See what cytoscape suggests: https://js.cytoscape.org/#style/background-image

on it..

@Abhishek-kumar09 done.

Thank You @Harshit-Dandriyal


Parameter: health-check-timeout seems not to be set on deployment

Description
mtad like this:
- name: backend
  type: javascript.nodejs
  path: backend
  parameters:
    buildpack: https://github.com/cloudfoundry/nodejs-buildpack.git#v${nodejs-buildpack-version}
    disk-quota: 1G
    health-check-http-endpoint: /cfhealth
    health-check-timeout: 180 # seconds
    health-check-type: http
    instances: 1
    memory: 2G

Expected behaviour is the same as setting via CF CLI:
cf set-health-check backend http --invocation-timeout 180

Your environment

MultiApps CF CLI Plugin version - 2.6.2
which CF vendor is used - SAP BTP

Steps to reproduce
Try health-check parameters in mtad like from above

Hello,
In order to use the invocation timeout the parameter in the mtad.yaml it should be set as:
health-check-invocation-timeout: 180
Full information regarding the health check parameters can be found in the second table:
https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/177d34d45e3d4fd99f4eeeffc5814cf1.html?locale=en-US
Thanks and best regards,
Ivan

Hello,
Closing the issue as there are no recent updates. Please check the link for the invocation timeout.


Improved PII stripping.

I have now created a function, that does nicer PII stripping, where most of the keys are still there, but the values are gone.

TBH I'm not sure if it's safe to do it like that - those keys depend on the protocol version used by mongo client and can change in the future so PII may be leaked.
Need to check how does it look with older queries but probably won't be able to do it this week.

Good point! I added this, because when we redact all the values then the resulting query does not show anything, and the developer can not figure out what query is the slow one. See this screenshot:

Having more information is very helpful:

But you are right about old versions. It could leak PII and that is not good.
So we could:
a) go back to redacting everything.
b) only keep the first element (to have at least the collection on that the query is performed)
c) go through some older version of MongoDB (so maybe the last 2 major version or such) and make proper stripping for them and limit the SDK to those versions.
(side note: this code will come in handy if we do a Elasticsearch integration in the future, because those queries are also json)

I'm worried about future ones, not the past. Monitoring API was only introduced in 3.1 so there is not much to check in that part. And bounding upper version is a really bad idea.
There is also an option of adding an optional callback but with it being a kind of an integration that should enable itself by default (in the future) it's not a great solution either.
TBH maybe just adding a warning in docs "PII stripping tested up to Mongo x.y.z" is enough?

Could you please merge this into your branch @Agalin
We then can continue in your PR.


Fixes issue #93

Fixes issue #93

@Avinandan22 could you make the same changes in the remaining examples as well?

@Avinandan22  The changes look fine. Can you still rerun the notebooks locally to confirm everything is working?

Made changes for Adversarial Autoencoders and Custom Losses, the other 2 do not use MNIST so did not make any changes.

Ran them. Working correctly now.

Thanks @Avinandan22


Updater - Report on and add a way to update secondary (non-Direct) composer dependencies

Currently update-status and update-apply only looks at direct (-D) composer dependencies. There can be cases where there are pending non-direct dependencies that should be updated as well.
We should make two changes, minimally:

In update-status, it should build a second table for minor updates for non-direct dependencies
In update-apply, it should have a way of updating non-direct dependencies (we would need to build a way of determining which direct dependency is requiring the secondary dependency and then update --with-all-dependencies or something similar)

In addition, if possible, we should look into a way of doing something similar to drush pm-updatestatus before it was deprecated. Possibly as a drush command in a contrib module like https://www.drupal.org/project/vitals . The goal being to show a similar output that you can see on the update status page in the Drupal admin. Also something like drush eval "var_export(update_get_available(TRUE));"

Existing code for this was pushed with v0.0.5-alpha.


Make predictions is failing

After following all the steps with Shortcut: Download a Pre-Computed Training Set as mentioned here
It is failing at Make Predictions step in # Generate a prediction for a new TCE.
Following are the exceptions and Errors:
https://paste.ubuntu.com/p/TwSkY5YB54/

Issue is duplicate of #7. Apologies for missing already created issue.


Still has many issues. When are you fixing those?

This app is so good and has a great potential, when are you fixing it?

After Google I/O, I actually decided to rewrite a lot of the UI from scratch. This was partly because there were a lot of UI quirks that would be tedious to fix, but also because I wanted to use newer API's and change the view hierarchies so that I could use Google's new Design library.
Right now, I'm using the new view elements from the design libraries in place of the ones that are currently in Jockey (Namely the FAB and TabView), and I've replaced all of the ListViews and GridViews with RecyclerViews. I've also changed how the player service works so that it hopefully works properly.
I've also cleaned up a few dependencies and refactored some of the code to make it easier to work with. Right now I don't think it's ready to be released because it doesn't have all of the base functionality (mainly showing playlists or your now playing queue). Once that's been implemented again, I'll release the new version.
It might be ready as early as next week, but I don't want to promise anything yet since I'm doing a summer class, there's a Steam Summer Sale going on, and my new laptop stopped working yesterday and has to be repaired. In the meantime, though, here's a quick teaser.

Nice, that UI really looks better than what you had before! good luck with your summer classes and yeah don't waste much time playing games haha

Plus, make it big this time. When you release it, make sure you add your project Here too. This helps you get a lot of exposure and helps you learn new things daily! I've learned coding better due to those people. You can check out my Browser Project Here

Version 0.3_α-m0r0 has been uploaded


How to take screen shot of the application whenever expect fails

Is there any wait to capture screen shot of the application whenever expect fails. Idea it to capture all points of failure. Selenium driver supports some feature like this.Is there any kind of switch in protractor also .

I have written a Protractor plug in , that takes screenshot for every 'expect' failure and spec failure as well. Screenshot names are meaningful too.
Here is the npm module:
https://www.npmjs.com/package/jasmine2-protractor-utils
Note: It is compatible with Jasmine2 only.

@abhishekswain You want me to add your plugin to the community plugins list?

@sjelin Yes please , if it is possible. :)
Somehow I missed your mention here and it got skipped for a long time now.

Any way to take screenshot of the screen while (and including) Javascript alert open captured ?

Hi there!
I have forked and improved @abhishekswain tool.
Now the brand new fork called [protractor-screenshoter-plugin] (https://github.com/azachar/protractor-screenshoter-plugin)  captures for each browser instance a screenshot and console logs. The snapshot is made optionally for each expect or spec. It comes with a beautiful angular and bootstrap based analytics tool to visually check and fix tests results.
Check it out at https://github.com/azachar/protractor-screenshoter-plugin.
Also, I created a list of all available [alternatives] (https://github.com/azachar/protractor-screenshoter-plugin/wiki/Alernatives), so if you find something else, please do not hesitate to add it there.

Hi all! Could you help me to investigate jasmine-allure for fails screens?
I got next
 jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } }));
    var AllureReporter = require('jasmine-allure-reporter');
    jasmine.getEnv().addReporter(new AllureReporter({
        resultsDir: 'reports/allure-results'
    }));
	var pass = jasmine.getEnv().afterEach(function(done){
      if(!pass)
      browser.takeScreenshot().then(function (png) {
			allure.createAttachment('Screenshot', function () {
			  return new Buffer(png, 'base64')
			}, 'image/png')();
			done();
		  })
    })

Hi there,
Feel free to use https://github.com/azachar/protractor-screenshoter-plugin https://github.com/azachar/protractor-screenshoter-plugin  instead (disclaimer: I am the maintainer of it).
Cheers,
Andrej

On 19 Feb 2018, at 13:16, Sereda-Fazen<EMAIL_ADDRESS>wrote:
Hi all! Could you help me to investigate jasmine-allure for fails screens?
I got next
jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } }));
var AllureReporter = require('jasmine-allure-reporter');
jasmine.getEnv().addReporter(new AllureReporter({
resultsDir: 'reports/allure-results'
}));
var pass = jasmine.getEnv().afterEach(function(done){
if(!pass)
browser.takeScreenshot().then(function (png) {
allure.createAttachment('Screenshot', function () {
return new Buffer(png, 'base64')
}, 'image/png')();
done();
})
})
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/angular/protractor/issues/114#issuecomment-366675357, or mute the thread https://github.com/notifications/unsubscribe-auth/AEcXS0P9OD0okl6K9yL6xo46tQj40WI4ks5tWWYfgaJpZM4BCbS3.


email attachment

hello, I don't know if it is out of scope but it would be useful to be able to attach files as well as to be able to write a msg in html format.
thank you.

Hello @fdefilippo,
An html format might only be useful for "email" other services format the message in the apps.
While it is supported by some services to attach a file with the message, there is no reasonable way to have this feature for all the supported services.


\text in subscripts should have smaller font

Consider this sample:

The text ЭП should have smaller font size than КБ.

Have you tried using the FontSize Atom for the (Sub / Super)script pair? The Fontsize of the Font Size Atom should be calculated by multiplying the script factor by the Font Size of the current environment.


convert from pyproject.toml is broken for dependencies that are an array

$ dephell deps convert --traceback --from pyproject.toml --to setup.py
WARNING cannot find tool.dephell section in the config (path=pyproject.toml)
ERROR AttributeError: 'Array' object has no attribute 'get'
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/dephell/cli.py", line 115, in main
    result = task()
  File "/usr/lib/python3.8/site-packages/dephell/commands/deps_convert.py", line 46, in __call__
    resolver = loader.load_resolver(path=self.config['from']['path'])
  File "/usr/lib/python3.8/site-packages/dephell/converters/base.py", line 94, in load_resolver
    root = self.load(path=path)
  File "/usr/lib/python3.8/site-packages/dephell/converters/base.py", line 54, in load
    root = self.loads(content=stream.read())
  File "/usr/lib/python3.8/site-packages/dephell/converters/poetry.py", line 110, in loads
    deps.extend(self._make_deps(
  File "/usr/lib/python3.8/site-packages/dephell/converters/poetry.py", line 334, in _make_deps
    url = content.get('file') or content.get('path')
AttributeError: 'Array' object has no attribute 'get'

The pyproject.toml is the current poetry 1.0.0 one, and contains
keyring = [
    { version = "^18.0", python = "~2.7 || ~3.4" },
    { version = "^19.0", python = "^3.5" }
]

After shoving some print statements into dephell (to print the type and repr of content), I notice the crash occurs here:
[{'version': '^18.0', 'python': '~2.7 || ~3.4'}, {'version': '^19.0', 'python': '^3.5'}]
<class 'tomlkit.items.Array'>
ERROR AttributeError: 'Array' object has no attribute 'get'

I think the dephell CI should fetch and process the poetry toml, as it is regularly causing problems.  c.f. https://github.com/dephell/dephell/issues/256
I've worked around it with a small patch https://build.opensuse.org/package/view_file/home:jayvdb:py-submit/python-poetry/simplify-toml.patch?expand=1

To be honest, we can't it full support. For now, DepHell has one node for every package on the graph. Nodes are merged if they have the same name. One exception is extras. They are represented as a modification of the name and the dependency itself depends on that extra when it's added to the graph. That's already quite complicated but it's the simplest solution that you can make to support extras without any hacks in the graph and resolving, this is just another type of dependencies.
However, array-based dependencies are really tricky and make things a lot more complicated. For example below, what if pkg1 depends on keyring 17 or 18, and pkg2 depends on keyring 18 or 19? Well, that's easy, the result is one keyring 18 node. But what about markers? What if they are different? We have to adjust nodes lookup, add a lot of tricks, think about merging. Another interesting thing is all changes on nodes should be revertable because after resolving I don't want to see markers and constraints of subdependencies in my requirements file. In that example, that means I still want to see keyring 17 or 18 in converted requirements file but keyring 18 in the lockfile.
Also, there is something unobvious. If you duplicate dependency in requirements.txt they are merged by AND rule, not OR. For example, django>=1.9 and django<1.12 in the same file are merged into django>=1.9,<1.12.
So, resolving in Python already incredibly complicated, and this doubles the complexity. And after all, let's be honest, any project needs only one version of one package. Maybe, both at the same time, but it's a different story. And it's never about ordependency for one project for different platforms. One package does one thing, the same on different platforms. For example, I'd like to install docker package only for unix because win doesn't support it, but it's hard to imagine that docker of some version works for win, and other versions aren't.
Hence such cases exist because developers try to do the job of the resolver, but they shouldn't. The resolver can check the supported platforms itself and install keyring 18.0 for old pythons (that will be out of life 2 weeks later btw) and 19.0 for new pythons.
I understand that we already created that hell and dephell have to help us to handle it. However, taking into account everything above, let's consider some simple solutions that can be applied in the poetry converter itself. The outcome if this decision is output will produce one dependency, not an array. For the example in the issue it will be keyring 18 || 19. What do you think?

Reading poetry's documentation on how to write a pyproject.toml it's not even clear this is supposed to be valid in the first place. :(
You're entirely correct, the resolver should be able to see that keyring 19 doesn't support python2, and try installing an older version. In fact, pip2 install keyring does exactly that, sooo...
<rant>
I don't even understand why it's somehow supposed to be necessary to enforce, in poetry, that you're running the latest version of keyring 19 while on python3. venv management tools will already try to install the latest version that matches requirements, keyring 18 is manifestly supported by poetry on python2 at a minimum and therefore I find it very very hard to believe it will crash on python3, and it isn't the job of a python package to enumerate which old versions work fine but the developer wants you to avoid anyway. Just specify that the project codebase depends on at least version 18, because some target platforms only have that available and therefore poetry is committed to making sure version 18 works.
Lastly, why on earth does poetry still support python 3.4 which was EOL'ed 9 months ago. o_O
</rant>

Lastly, why on earth does poetry still support python 3.4 which was EOL'ed 9 months ago.

Hah, the next dephell release will drop 3.5 support because, as I see in dephell package downloads dephell nobody (!) needs it. Meh, I did a lot of work to support it, even forked bowler and fissix. Anyway, it's time to move forward.
What about the issue, let's do it in the dirty hacks way: try to merge it and do not care about keeping both nodes separately. It helps in most of the use cases.

I think the dephell CI should fetch and process the poetry toml

Yeah, I thought about adding more smoke tests on actual data. Now we are parsing dephell's own metadata.

I've worked around it with a small patch

The page returns 404.

sorry openSUSE system is a bit odd.
Package was accepted, so now moved to https://build.opensuse.org/package/view_file/devel:languages:python/python-poetry/simplify-toml.patch?expand=1

ping @orsinium ; being able to parse the pyproject.toml of the poetry project is IMO really important as dephell can be a bootstrap for poetry.
openSUSE now has macros to use dephell as a bootstrap for pyproject.toml sdists, but it doesnt work for poetry https://build.opensuse.org/package/view_file/devel:languages:python/python-dephell/macros.py-dephell?expand=1

A simpler way to fix poetry' pyproject.toml:
sed -i '/^keyring = /,+3d' pyproject.toml
sed -i 's/\(\[tool.poetry.dependencies\]\)/\1\nkeyring = { version = "^18.0" }/' pyproject.toml

poetry now also has this in its pyproject.toml:
https://github.com/python-poetry/poetry/blob/1d64e1c75cfd03d8f98533645a7815f0dbcaf421/pyproject.toml#L61-L64
So it's now necessary to patch this too. Full patch:
--- poetry-1.0.9/pyproject.toml
+++ poetry-1.0.9/pyproject.toml
@@ -49,19 +49,13 @@
 virtualenv = { version = "^16.7.9", python = "~2.7" }
 # functools32 is needed for Python 2.7
 functools32 = { version = "^3.2.3", python = "~2.7" }
-keyring = [
-    { version = "^18.0.1", python = "~2.7 || ~3.4" },
-    { version = "^20.0.1", python = "^3.5" }
-]
+keyring = { version = "^18.0" }
 # Use subprocess32 for Python 2.7 and 3.4
 subprocess32 = { version = "^3.5", python = "~2.7 || ~3.4" }
 importlib-metadata = {version = "~1.1.3", python = "<3.8"}

 [tool.poetry.dev-dependencies]
-pytest = [
-    {version = "^4.1", python = "<3.5"},
-    {version = "^5.4.3", python = ">=3.5"}
-]
+pytest = {version = "^5.4.3" }
 pytest-cov = "^2.5"
 mkdocs = { version = "^1.0", python = "~2.7.9 || ^3.4" }
 pymdown-extensions = "^6.0"

I have poetry 1.1.0a3 building at https://build.opensuse.org/package/show/home:jayvdb:py-new/python-poetry . Needed a few more changes, as a new array was added for pytest .
sed -i '/packaging/d;/poetry-core/d;/clikit/d' pyproject.toml  # the dep version pins from dephell are unusable
sed -i '/^keyring = /,+4d' pyproject.toml
sed -i 's/\(\[tool.poetry.dependencies\]\)/\1\nkeyring = { version = "^18.0" }/' pyproject.toml
sed -i '/^pytest = /,+3d' pyproject.toml
dephell deps convert --from pyproject.toml --to-format setuppy --to-path setup.py

+keyring = { version = "^18.0" }

... which only allows keyring between 18.0 and <19 ... :(
While trying to fix the new isort plugins tests I found out, that poetry refuses to work, because it reads it's own egg.info/requires.txt and sees that the used keyring is way too new.

The correct dependency is of course keyring = "*" to permit all versions, unless it's actually known that some versions may be bad.


[Community Safety] Code of Conduct

People from all over the world will be joining the community.
Let's be inclusive!
A code_of_conduct.md is needed
Priority:
Medium

@cobycloud can i work on this?


[8.x] Updated fillables to allow wildcard fillables

Issue
In the recent update: https://blog.laravel.com/security-release-laravel-61835-7240 the ability to update JSON columns using arrow sign (->) without explicitly include the attribute name (e.g. set $fillables = ['meta->foo'] in order to update $object->update(['meta->foo' => 'bar'])) has been removed for security reason.
This has caused issues for the developers that have been developing their applications using the existing approach as specified in the documentations: https://laravel.com/docs/8.x/queries#updating-json-columns . It was well understood that the changes were made due to security reasons however including every single column inside the $fillables attribute is not feasible as the applications may require dynamic fields. Refer to discussions in: https://github.com/laravel/framework/issues/33975 and https://github.com/laravel/framework/issues/34630 . A several PR has also been sent such as: https://github.com/laravel/framework/pull/34299 and https://github.com/laravel/framework/pull/34631 but were rejected.
Some of the solutions that has been implemented by other include bypassing the isGuardableColumn as the following:
    protected function isGuardableColumn($key)
    {
        return true;
    }

Proposed solution
Instead requiring users to submit all the nested attributes (such as $fillables = ['foo->bar']), this PR allowed the user to specify the fillable columns using asterisk as while card. For example, if a user wanted to update using $object->update(['foo->bar' => 'baz']), he / she only need to specify $fillables = ['foo->*']; in order to allow it. The $fillables also allow nested wildcard assignment, e.g. $fillables = ['meta->age->*'] will allow the update using $object->update(['meta->age->foo->bar' => 'baz']) but not $object->update(['meta->phone'])

I feel like I keep saying this over and over. You do not need to specify every field.
$array = $model->array;
$array['anything-you-want'] = $value;
$model->array = $array;
$model->save();

@taylorotwell this wouldn't work if we need need to mass update attributes at the same time such as:
$object->update([
  'meta->age' => 16,
  'meta->phone' => '12345678',
  'meta->foo' => 'bar,
]);


Search - Read message shown in bold in search router result

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

Version Number: v9.0.66-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:
Prerequisite - User A send a message to user B
Steps

{User B} Navigate to https://staging.new.expensify.com/

{User B} Notice a new message is bold in LHN and Search router

{User B} Navigate to the message so that the message can be read

{User B} Notice LHN is not bold any more

{User B} Navigate to Search router

Expected Result:
As the Message is already read the Search router result should not be bold
Actual Result:
Read message shown in bold in search router result
Workaround:
Unknown
Platforms:

[x] Android: Standalone
[x] Android: HybridApp
[x] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/da533cae-f814-4ed5-aefa-9a3041cbc367

View all open jobs on GitHub

Besides the chat name (participant name) being bolded, the last message is missing:

and instead we show the email.
This has very likely the same root cause as https://github.com/Expensify/App/issues/53291

I think https://github.com/Expensify/App/pull/53293#discussion_r1862818438 fixes this

Made the PR ready for review: https://github.com/Expensify/App/pull/53293

@aldo-expensify this is apparently still not fixed based on qa testing here https://github.com/Expensify/App/pull/53293#issuecomment-2508062917

@aldo-expensify this is apparently still not fixed based on qa testing here https://github.com/Expensify/App/pull/53293#issuecomment-2508062917

😢 , will try to reproduce

btw, I'm still trying to fix my dev env because Auth started crashing.... I reproduced in staging, but I haven't been able to work with my vm yet :(

hmm, I think this is fixed in main, but not in staging. Staging ended up in a not so great state when we CP'd https://github.com/Expensify/App/pull/53293 because we are missing the changes from https://github.com/Expensify/App/pull/53056:

I'm not sure about what to do here... I doubt we want to CP: https://github.com/Expensify/App/pull/53056 since it is a big PR, or is that fine? @mountiny  do you have some thoughts about this? 😬 🙇

Maybe we can ignore this and deploy https://github.com/Expensify/App/pull/53056 normally on its time since the bold/no bod doesn't sound like a big issue to me

@aldo-expensify Yes I think we can treat this as non-blocker, its minor issue and we can let the refactor go through normal process to catch any regressions on that. Thanks for digging 🙌

No payment due.


Spring/damper has no effect in driving articulation joint

It seems that no matter what value I use for spring or damper, it has no effect on the simulation. I can set these values to whatever, zero or a billion, it has no effect. I'm trying to drive a joint towards an orientation. The ragdoll is very unstable since there is zero damping, the only parameter that seems to have an effect is max_force. I'm thinking there might be something wrong with the binding for this function "PxArticulationJointReducedCoordinate_setDriveParams_mut(joint, axis, &drive)" or something like that? unless I completely misunderstood something.
pub fn set_articulation_joint_reduced_target(
    joint: PtrArticulationJointReducedCoordinate,
    axis: PxArticulationAxis,
    max_force: f32,
    spring: f32,
    damper: f32,
    target: f32,
) {
    unsafe {
        println!("Spring/damper {} {}", spring, damper);
        let drive = PS::PxArticulationDrive_new_1(
            spring,
            damper,
            max_force,
            PS::PxArticulationDriveType::Target,
        );

        PS::PxArticulationJointReducedCoordinate_setDriveParams_mut(joint, axis, &drive);
        PS::PxArticulationJointReducedCoordinate_setDriveTarget_mut(joint, axis, target, true);
        PS::PxArticulationJointReducedCoordinate_setFrictionCoefficient_mut(joint, 2.0);
    }
}

How is the joint configured?

How is the joint configured?

All Spherical joints, with limits but rather large limits.

Are you setting motion type per axis?

Hmm. I'd narrow it down a bit by using a limited spherical joint, and probably using a Force drive type rather than Target. That'd be a more regular setup I think. This seems like a configuration issue, more so than a binding problem until we can prove the opposite. Articulation joints and drives are a lot less forgiving for configuration errors than their regular variants.
Just to double-check though; @blunzn or @bpaberg -- you've both looked at the articulations recently; did you notice any issues with drives?

I could try to use velocity drive to see if it makes a difference, it should be possible to drive towards an orientation using velocity as well, by setting velocity to zero when target is reached.

I'm not sure why force drive would work better?

Ok once I'm home I'll make a minimal example to try to reproduce it.

My bad, I should've use FORCE joint drive type instead of TARGET.

Thanks for the follow-up @mlp1802!


Artifact downloads

Hi
One question about mirroring. What is the final artifact from this step? Is it a h2.db file?
I would like to mirror the DB with this tool, and then, run Dependency check against it.
If the artifact that comes after this step is not a h2.db file, how do i run Dependency check against this artifact?
Thanks

This tool mirrors the NVD download site so that organizations can have their own internal mirror of the NVD. Refer to https://jeremylong.github.io/DependencyCheck/data/mirrornvd.html

Hi
Thanks for the update. I have already checked that page. My point is how
this can be converted into a format that can be understood by dependency
check (h2.db). Is there any tool that does it?
Thanks
On Tue, Sep 26, 2017 at 7:06 PM, Steve Springett<EMAIL_ADDRESS>wrote:

This tool mirrors the NVD download site so that organizations can have
their own internal mirror of the NVD. Refer to
https://jeremylong.github.io/DependencyCheck/data/mirrornvd.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stevespringett/nist-data-mirror/issues/7#issuecomment-332285278,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMK55sWlt6PgJmgrIHRlCXdhgBAzp9cuks5smT0kgaJpZM4PkbUi
.

Not sure I understand the question. Dependency-Check should be setup to download from the mirror (instead of the NVD). When this is done, the h2 database will be created like normal.

Sorry I should have been clearer
I want to have on one side just dep check only, without downloading the
database in every execution
On the other side, I want to have independently the db, and I have a job
that downloads it every night.
It might sound strange but there is a reason behind that ;)
So, I want to execute this dependency check instance against the database
that I am downloading every night with this mirroring and refer to it using
the -d option
Here is where the question comes. Is this database downloaded via mirroring
compatible with dependency check?
I was expecting to have an h2.db downloaded with this mirroring, since
this is the format for the database downloaded with dependency check
itself. but what I have seems to be json.gz for every year, and i dont
think dependency check will accept that input for database using -d.
My question is... how can i reference from dependency check using -d to the
database downloaded with the mirroring? Do i need to convert those files to
a format that is valid for dependency check (h2.db)?
Thanks
El El mié, 27 sept 2017 a las 3:41, Steve Springett <
<EMAIL_ADDRESS>escribió:

Not sure I understand the question. Dependency-Check should be setup to
download from the mirror (instead of the NVD). When this is done, the h2
database will be created like normal.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stevespringett/nist-data-mirror/issues/7#issuecomment-332392465,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMK55m1idrPado_JKP23SEopV2BZbb4Aks5smbXZgaJpZM4PkbUi
.

This is a very common use case.
dependency-check --updateonly --data /my/datadir --cveUrl12Modified http://myhost/nvd-mirror/nvdcve-Modified.xml.gz --cveUrl20Modified http://myhost/nvd-mirror/nvdcve-2.0-Modified.xml.gz --cveUrl12Base http://myhost/nvd-mirror/nvdcve-%d.xml.gz --cveUrl20Base http://myhost/nvd-mirror/nvdcve-2.0-%d.xml.gz
This will download the contents from a mirror hosted on your internal network and will create (or update) the data directory.
From the command line this looks a bit ugly, but Maven, Ant, Gradle, and Jenkins plugins all support this use case.
Just replace 'http://myhost/nvd-mirror/' with the hostname and directory to where your mirror is actually located.
Most orgs run nist-data-mirror followed by the above command (or similar) on a nightly basis.

Aha. Looks clearer now
Why there are three different ndvcve? Do they contain the same info but in
different formats?
Also, I was thinking on running just the dependency check cli with the
update argument as it will just download the h2.db. Do you recommend
mirroring instead of doing this?
And the last mandatory question... is there any difference between the
h2.db and those xml.gz, or is it the same in a different format?
Thanks!
El El jue, 28 sept 2017 a las 5:16, Steve Springett <
<EMAIL_ADDRESS>escribió:

This is a very common use case.
dependency-check --updateonly --data /my/datadir --cveUrl12Modified
http://myhost/nvd-mirror/nvdcve-Modified.xml.gz --cveUrl20Modified
http://myhost/nvd-mirror/nvdcve-2.0-Modified.xml.gz --cveUrl12Base
http://myhost/nvd-mirror/nvdcve-%d.xml.gz --cveUrl20Base
http://myhost/nvd-mirror/nvdcve-2.0-%d.xml.gz
This will download the contents from a mirror hosted on your internal
network and will create (or update) the data directory.
From the command line this looks a bit ugly, but Maven, Ant, Gradle, and
Jenkins plugins all support this use case.
Just replace 'http://myhost/nvd-mirror/' with the hostname and directory
to where your mirror is actually located.
Most orgs run nist-data-mirror followed by the above command (or similar)
on a nightly basis.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stevespringett/nist-data-mirror/issues/7#issuecomment-332723255,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMK55gIm_A9isiL5ZgLgEayU6NcQOrWsks5smx2kgaJpZM4PkbUi
.

Actually, there are four of them, not three. Yes, they are all different data feeds provided by the NVD. All four are necessary.
The xml.gz is the exact same thing that is available on the NVD. Once ODC downloads the data from the NVD (or a mirror of the NVD), it processes the feeds and creates a database (the h2 file).
Most orgs host an internal mirror of the NVD. They will then configure each instance of ODC to use the mirror.

Perfect. Thanks!
For me is easier to download it directly in h2.db in the central repo and
then configure Odc against the h2 itself
Thanks for everything! Really appreciated
El El vie, 29 sept 2017 a las 2:35, Steve Springett <
<EMAIL_ADDRESS>escribió:

Actually, there are four of them, not three. Yes, they are all different
data feeds provided by the NVD. All four are necessary.
The xml.gz is the exact same thing that is available on the NVD. Once ODC
downloads the data from the NVD (or a mirror of the NVD), it processes the
feeds and creates a database (the h2 file).
Most orgs host an internal mirror of the NVD. They will then configure
each instance of ODC to use the mirror.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stevespringett/nist-data-mirror/issues/7#issuecomment-333007516,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMK55to0L5SU_W_woL8DZmkdl0C5oPnEks5snElGgaJpZM4PkbUi
.


Use same heading IDs for all languages

Description

Use the same heading ID as English for all languages.
Add script to update all heading IDs and links as more pages translations get up-to-date.

This is an experiment brought up over the weekend, we still have to talk about it.

Hey, I'm sorry to burst your bubble Luiz, and it was a cool experiment. But especially with so many changes coming for Astro 5.0, we're not going to be able to play around with this idea any time soon.
So let's close this PR, and let's instead focus on one of the goals behind this idea: to identify translations that are too out of date to be helpful, and maybe should not be published in the version 5 docs if not properly updated.


Tablets. Enhancements according with suggestions

Services page. Reduce the size of images, centralized header and description

Team member. Check out resolution 1200. Has to fit 2 projects

"Star sky" return back

Tested
Comments

Team Member page: there presented more then two projects at the page

Known issues:
https://github.com/VS-work/vs-website/issues/146


Open News Summary in a Tab

News items come with a summary. There are already multiple options where to show the summary: in the article info "column" in the headlines list, in a "unified" way in the headlines list or in a separate part of the window according to some selected layout (either horizontal or vertical).
What is missing is the option to open the summary in a new tab.
At the moment, tabs can only be used to open the original article webpage ("Open Article Page").
Can you allow opening the news summary in a separate tab?
It can (and should) simply look like the horizontal or vertical layout's summary section of the window.

Would you explain the advantage this would bring to your workflow ?

Sure, here is a description of my specific workflow. There might be others, too.
Keeping TODO Lists in GitLab Issue Descriptions
The description is part of summary in the RSS feed.
And despite this bug in GitLab (https://gitlab.com/gitlab-org/gitlab/-/issues/345797), Vienna receives/shows proper checkbox lists. See here:

(source: https://gitlab.com/sbondorf/rsstestsvienna3/-/issues/1)
Un-/Checking a checkbox will refresh the article summary accordingly.


Provide helm packages

Is your feature request related to a problem? Please describe.
kustomize can be pretty difficult to support when you want a consistent versioned deployment. I ended up using ansible to build the deployments using kustomize but I don't particularly like the solution.
Describe the solution you'd like
helm in my opinion is a better way to manage deployments. Ideally I'd like to be able to do
helm install pingdirectory -f my-overrides.yaml pingidentify/pingdirectory

Hi -
Great timing as we just released our helm charts last week.
https://helm.pingidentity.com/
Please reach out if I can help in any way.
Best
Glen
https://www.pingidentity.com[image: Ping Identity]
https://www.pingidentity.com
Glen Morgan
DevOps Program Manager
<EMAIL_ADDRESS>c: +1<PHONE_NUMBER>
Connect with us: [image: Glassdoor logo]
https://www.glassdoor.com/Overview/Working-at-Ping-Identity-EI_IE380907.11,24.htm
[image:
LinkedIn logo] https://www.linkedin.com/company/21870 [image: twitter
logo] https://twitter.com/pingidentity [image: facebook logo]
https://www.facebook.com/pingidentitypage [image: youtube logo]
https://www.youtube.com/user/PingIdentityTV [image: Blog logo]
https://www.pingidentity.com/en/blog.html
https://www.google.com/url?q=https://www.pingidentity.com/content/dam/ping-6-2-assets/Assets/faqs/en/consumer-attitudes-post-breach-era-3375.pdf?id%3Db6322a80-f285-11e3-ac10-0800200c9a66&source=gmail&ust=1541693608526000&usg=AFQjCNGBl5cPHCUAVKGZ_NnpuFj5PHGSUQ
https://www.pingidentity.com/en/events/d/identify-2019.html
https://www.pingidentity.com/content/dam/ping-6-2-assets/Assets/Misc/en/3464-consumersurvey-execsummary.pdf
https://www.pingidentity.com/en/events/e/rsa.html
https://www.pingidentity.com/en/events/e/rsa.html
https://www.gartner.com/reviews/vendor/write/ping-identity/?utm_content=vlp-write&refVal=vlp-ping-identity-32202&utm_campaign=vendor&utm_source=ping-identity&utm_medium=web&arwol=false
https://www.gartner.com/reviews/vendor/write/ping-identity/?utm_content=vlp-write&refVal=vlp-ping-identity-32202&utm_campaign=vendor&utm_source=ping-identity&utm_medium=web&arwol=false
On Sun, Nov 8, 2020 at 5:45 AM sergioatom<EMAIL_ADDRESS>wrote:

Is your feature request related to a problem? Please describe.
kustomize can be pretty difficult to support when you want a consistent
versioned deployment. I ended up using ansible to build the deployments
using kustomize but I don't particularly like the solution.
Describe the solution you'd like
helm in my opinion is a better way to manage deployments. Ideally I'd
like to be able to do
helm install pingdirectory -f my-overrides.yaml pingidentify/pingdirectory
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pingidentity/pingidentity-devops-getting-started/issues/147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPFS25Y3XM4D7KONAE46WDSOZSCJANCNFSM4TOGZB5A
.

--
CONFIDENTIALITY NOTICE: This email may contain confidential and privileged
material for the sole use of the intended recipient(s). Any review, use,
distribution or disclosure by others is strictly prohibited.  If you have
received this communication in error, please notify the sender immediately
by e-mail and delete the message and any file attachments from your
computer. Thank you.

Do you have a git repo for them? I'd like to mirror them locally. Thanks.

@sergioatom Lol, sheesh I just finished all my ansible playbooks and stumbled across this.

Hi Sergio (and Cory),
We are in the final (hopefully) work on shoring up our helm charts for public consumption.  We've recently re-architected them to make it much easier.  But if you would like a sneak peek, you will find our chart 'devops2' that is a part of our helm.pingidentity.com/devops repo.  Understand that we will be changing this name from devops2 --> (probably devops) soon, and removing all the existing devops/product charts soon.
Once we get this to a stable state, we will most likely make the charts public.  Even though they are pretty much public via the repo artifacts.
Appreciate the interest and insight/questions you might have going forward.
tls

When you get a chance, you should now be able to see all the charts, docs, and a soft launch of the chart name we are ending up with 'ping-devops'.  You should be able to find all this by simply going to: https://helm.pingidentity.com
Feedback, questions, thoughts are welcome.
Thanks,
tls


experiment with Jekyll version

This is an experiment, do not merge. Wondering if a traditional Jekyll version will speed up the Netlify deploy.

This change is

The Netlify checks went from 5 minutes down to 2, which is good news, but doing this properly will require some CI updates. Will wait for @yingzhuchin ’s return before proceeding.


question: detecting which .wasm to load and run?

Hey 👋  I wasn't sure where to ask and this seemed like a better place that on the #krustlet channel in the K8s slack.
How do the shims decide what .wasm file(s?) to load when they get an image?
I see spin.toml in the example ghcr.io/deislabs/containerd-wasm-shims/examples/spin-rust-hello image specifies
[[component]]
id = "hello"
source = "spin_rust_hello.wasm"

...which leads me to wonder how the shims know to look for spin.toml in the image layer contents, and not credenza.toml or pteradactyl.toml. If I had all three, would only spin.toml be read by convention?
In wasimg I'm setting the .wasm module to run in the OCI Image Config's Entrypoint, but that doesn't seem to be read anywhere, and anyway you may end up moving to OCI Artifacts anyway, where there isn't necessarily a config (https://github.com/deislabs/containerd-wasm-shims/issues/43)
Can an Image/Artifact used by these shims contain multiple [[component]]s, and therefore multiple .wasm files? Can the shims read and consider multiple .toml files, potentially of different variants?
Trying to get an idea of how these images are expected to be laid out, so I can be sure I'm able to build images that are "conformant" with the "spec" (heavy quotes there 😆 ).

Glad you brought this up. @Mossaka and I were just talking about this. Right now, I believe the runtime expects an /app.wasm, as you say, it should be in the configuration or the entrypoint.
I'd like to see us move the slightfile out of the image and mount that as part of the pod spec. I think we are only adding it to the image at this point for simplicity.
We need to be much more precise in the "spec" for fs layout (definitely heavy quotes).

We'd like this to work with a single container for now, because it's easy and as there's a "shim per host model" each shim needs to know how to map the artifacts for that model. Well heck, that's not very "speccy". :-)
Note that David says

I'd like to see us move the slightfile out of the image and mount that as part of the pod spec. I think we are only adding it to the image at this point for simplicity.

I'm of two minds about this, so it's the kind of thing we'll iterate on with users and anyone else who wants to work with this approach.
On the one hand, using a container/graph to deploy the topology of the host model in one swoop means that you can deploy that host model singly -- as in fire-and-forget edge functions, for example -- and deploy precisely the same thing without any modification in a container/graph to k8s. This, mind you, so long as the shim is in sync with that version of the host model, right?
Upside: k8s is now very clean manifest/chart, workload is treated as an immutable unit, making deployments far, far easier for pretty much everyone, both dev and deployer alike.
Downside: It is now denying the pure k8s experience, in which the topology of a host model is ripped apart and config must migrate to volumes or configmaps and so on but brings with it the visibility of operations that a k8s operator would really like.

In behavior, a graph and a container have equivalent functionality here: they'd both enable the "stamp the immutable topology approach".
the oddness is that I could see enabling both approaches as well. It may be that small clusters in constrained, heterogeneous environments -- single node clusters on risc-v SoCs for example -- might well want a topology stamp. No operator is going to really want a bunch of separate things there; it's too much and those clusters will not have ongoing management. (If they're attached to an edge cluster management service, there's every chance that touching thousands or millions of those clusters is, while theoretically possible, realistically a mess to avoid.)
We'll have our thoughts here, but I'm happy to take ideas!

how the shims know to look for spin.toml in the image layer contents, and not credenza.toml or pteradactyl.toml. If I had all three, would only spin.toml be read by convention?

The spin shim has a convention to look for the spin.toml file in the root directory (rootfs). Yes you're right, if you have all three toml files, it would only read spin.toml by convention.
The slight shim, however, has a different convention for now. It reads slightfile.toml and app.wasm in the rootfs directory.
If you'd like to see how they are implemented, the relevent lines are here for spin shim and slight shim, resp:
https://github.com/deislabs/containerd-wasm-shims/blob/main/containerd-shim-spin-v1/src/main.rs#L49
https://github.com/deislabs/containerd-wasm-shims/blob/main/containerd-shim-slight-v1/src/main.rs#L64-L65

Can an Image/Artifact used by these shims contain multiple [[component]]s, and therefore multiple .wasm files?

The spin shim can, because all the paths to wasm modules are defined in a single spin.toml manifest file. The slight shim currently does only work for one wasm module named app.wasm.

Noted: this means that there must always be a mapping between shim and host model version as well. For now that's fine, as we move forward something a tad more "structured" should probably exist.


Windows Server 19

It doesn't work on windows server 19 :(

I don't see it because it's from the installation

I check on VPS

the commands work, I will try to run the project on this server in DEV


There's a way to reset the rf module?

When the rf module is high stressed and/or far from other nodes the checkmessagereceived return ever false and i can not send on my rf module.
But if turn off and on the device it start work again.
I've debugged carefully my sketch but it seems to be the library/hardware no responding.
There's so a way to reset the rf module without reboot the device?

I have also noticed this issue. Calling rf12_initialize resets the module. We do this every 60s:
    if ((now - last_rf_rest) > RF_RESET_PERIOD) {
      rf12_initialize(nodeID, RF_freq, networkGroup);                             // Periodically reset RFM69CW to keep it alive :-(
    }

https://github.com/openenergymonitor/emonpi/blob/rf_hang/Atmega328/emonPi_RFM69CW_RF12Demo_DiscreteSampling/emonPi_RFM69CW_RF12Demo_DiscreteSampling.ino#L250
I would love to get to the bottom of why such drastic action is required :-(
However resetting does not take a long time and seems to have not detrimental effects on receiving or transmitting periodic RF data

60s??? wow...
the issue happens to us after a long time, randomly, but, if happens, usually after 2-3 days of continuous use ... often after a few minutes / hours / day it back to work or  is definitelly frozen.
Reinitializing every 60 seconds has resolved the issue?
how frequently do you send RF data?
I tried to do the rf12_initialize if i don't receive messages from minutes... On your experience try to do rf12_initalize when the device is in this undefined status is useless?
I tried the following without success..
   if(lastMessageTime>0 && millis()-lastMessageTime>10000){
       uint16_t spi_control = rf12_control(0x0000);
       if(spi_control==65535 || spi_control==0){
         Serial.println("Reitializing RF Module...");
        rf12_initialize(NODEID, RF12_433MHZ, NETWORKID, 0x0640);
        rf12_control(0xC623);
        rf12_control(0x9820);
        rf12_control(getChannelByID(channelID));
     }
   }

   if((lastMessageTime>0 && millis()-lastMessageTime>30000) || (lastMessageSentTime>0 && millis()-lastMessageSentTime>30000)){
       lastMessageTime=millis()-10000;
       lastMessageSentTime=millis()-10000;
       lastReceivedMessageID=0;
       Serial.println("RESTORE RF");
       rf12_recvDone();
       rf12_sleep(RF12_SLEEP);
       delay(500);
       rf12_sleep(RF12_WAKEUP);
       delay(100);
       rf12_recvDone();
       rf12_initialize(NODEID, RF12_433MHZ, NETWORKID, 0x0640);
       rf12_control(0xC623);
       rf12_control(0x9820);
       rf12_control(getChannelByID(channelID));
       rf12_recvDone();
   }

I would love to get to the bottom of why such drastic action is required :-(

Same here - that's the RF12 driver in native ("classic") mode? I've never seen this before...

It's running in RFM69CW mode:
# define RF69_COMPAT 1
60's is probably an overkill, issue only occurs occasionally every few days.

So the only solution for you is a reinitialize every x seconds/minutes?

@lettierimarco would you be willing to give my test code a spin. It is derived from jeelib and a full git replacement: https://github.com/jcw/jeelib/tree/RFxConsole

@JohnOH  sure, but i repeat... the issue is quietly randomly, so difficult to reproduce ... i've take a fast look to your derived but i don't see big differences. I'll anyway try it now.

I may have incorrectly assumed you were having this problem with RFM69CW hardware. My tweaks for the RFM12B are indeed trivial. I have not seen anything to concern me while operating RFM12B devices.

Hi John,
What are the summary of changes you have made to jeelib in your branch?

sent from my mobile device
On 29 Mar 2016 17:15, "JohnOH"<EMAIL_ADDRESS>wrote:

I may have incorrectly assumed you were having this problem with RFM69CW
hardware. My tweaks for the RFM12B are indeed trivial. I have not seen
anything to concern me while operating RFM12B devices.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/jcw/jeelib/issues/92#issuecomment-202981103

I'm afraid I don't have a summary the changes evolved or quite a long period. A diff of the five RF69* files will show them.

I've compiled your rfm12.cpp without # define RF69_COMPAT 1, my RF works but i don't know if my issue will reproduce again...
Any idea why for my RFM12B ? Can i test something for a thoroughly investigate ?

I've forked jeelib and commit some little change i've done: https://github.com/lettierimarco/jeelib

I'd like to look into this - is there any more info which might help narrow this down?

@glynhudson @lettierimarco - are we mixing RF69 and RF12 issues in this discussion by any chance? if so, please consider splitting off a separate one - I really want to help get to the bottom of this, but I'm going to have a very hard time if two problems are being mixed up...

My issue happens using rf12.

I have just checked in two changes to the RF69 compat mode driver, i.e. inter-operating with an RF12 driver at the other end which should substantially improve bad packet rejection and reduce dead-time - i.e. better noise rejection and fewer missed packets - with a huge thank-you to Martyn and John.
This change does not affect the RF12 driver side of things.

@lettierimarco can you post your full sketch with an indication as to where the code is returning permanent false (checkmessagereceived).

@JohnOH I only supposed this... I can't reproduce the issue programmatically but it happens.
I don't know if it could be connected to RF69 issue or not.
Now I'm trying to detect in rf12_interrupt the FIFO Overflow bit and the power reset bit. I hope this can explain why my RF stop receive and sending until I restart my device.
Sadly no one of them verified since I started the test (a week ago).

I don't think you issue is connected with the RF69 issue.
Do you use rf12_canSend in your sketch?
Are you unable to post your sketch here?

@jcw I am using RFM69CW with # define RF69_COMPAT 1. Sounds good, I will setup a test including your latest commits 6f1af25695a51910d2bb8ca0e796a7edda028848

void setup() {
  cli();
  wdt_enable(WDTO_8S);
  sei();
  wdt_reset();
  Serial.begin(SERIAL_BAUD);
  Serial.println("---> SETUP BEGIN");
  rst.debounceTime = 10;
  rst.heldDownTime = DEFAULT_HOLD_BUTTON_TIME;
  rst.multiclickTime = 50;
  send_buffer.init(200);
  send_buffer.clear();
  banList.init(32);
  banList.clear();
  pinMode(LINK_LED, OUTPUT);
  pinMode(TX_RX_LED, OUTPUT);
  pinMode(IDENTIFY_LED, OUTPUT);
  pinMode(RELAY_ON_LED, OUTPUT);
  pinMode(RELAYPIN, OUTPUT);
  pinMode(A6, INPUT_PULLUP);
  pinMode(13, INPUT_PULLUP);
  pinMode(12, INPUT_PULLUP);

  digitalWrite(LINK_LED, LOW);
  digitalWrite(TX_RX_LED, LOW);
  digitalWrite(IDENTIFY_LED, LOW);
  digitalWrite(RELAY_ON_LED, LOW);

  Serial.println("Initializing threads...");

  PT_INIT(&powerMetering_pt);
  PT_INIT(&linkCheckVerifier_pt);
  PT_INIT(&configManager_pt);

  wdt_reset();

  Serial.println("Initializing RF Module...");
  rfReinitliazing =millis();
  //RFM12 initialization
  uint16_t channel = getChannelByID(channelID);
  rf12_initialize(NODEID, RF12_433MHZ, NETWORKID, channel);
  Serial.print("----> Setting RF Frequency ");Serial.print("(");Serial.print(channelID);Serial.print(") :");Serial.println(getChannelByID(channelID),HEX);
  wdt_reset();
  Serial.println("SETUP DONE! Firmware version: "__DATE__" "__TIME__);
  bootTime = millis();
}

void loop(){
  wdt_reset();

  //Verifica la pressione del pulsante di reset/accensione
  rst.Update();
  if(waitingConfiguration){
    setupConfiguration();
  }else {
		//Controlla il LINK LED in base al successo di validazione
		if(mainRoute.verified) {
		  digitalWrite(LINK_LED,HIGH);
		} else {
		  digitalWrite(LINK_LED,LOW);
		}
		wdt_reset();

		//check if a message arrived...
		checkMessageReceived();

		//Send RF Commands
		checkMessageToSend();

	   wdt_reset();
	   if(lastMessageTime>0 && millis()-lastMessageTime>10000){
		   //Serial.print("SERIAL :");
		   //Serial.println(rf12_control(0x0000),DEC);
		   uint16_t spi_control = rf12_control(0x0000);
		   if(spi_control==65535 || spi_control==0){
			//RFM12 initialization
			uint16_t channel = getChannelByID(channelID);
			rf12_initialize(NODEID, RF12_433MHZ, NETWORKID, 0x0640);
		 }
	   }
	}
}

static void checkMessageReceived(){
  if(rf12_recvDone()) {
    if(rf12_crc == 0) {
		//manage packet
	}
  }
}

static void checkMessageToSend() {
  boolean ableToSend = false;
  ableToSend = (mainRoute.verified && tokenAcquired) || (!mainRoute.verified);

  if(send_buffer.getSize() > 0 && ableToSend) {
    if(rf12_canSend()) {
	  //populate buffer to send
	  delay(10);
      rf12_sendStart(toSend.jeeDest, toSend.bytes, totLen);
      rf12_sendWait(0);
	}
  }
}

in rf12.cpp i'm trying this without success until now:
static void rf12_interrupt () {
       uint16_t r = rf12_xferSlow(cmd);
       if(r&0x2000)
           //manage Fifo Overflow occured
       else if(r&0x4000)
          //manage Power Reset occured

...

Might you try adding an } else { error-message } to the
if(rf12_canSend()) {
  //populate buffer to send
  delay(10);
  rf12_sendStart(toSend.jeeDest, toSend.bytes, totLen);
  rf12_sendWait(0);
} else {
    print an informative message
}

I've already done this debug in past.
I've a TDM of about 200 ms so is probably that canSend is false sometimes but is not a problem.
Like i told in first post the problem is that when the issue happens i can't receive and send but the firmware is running.
My first idea was that there is a interference on the RF but the issue happens, in a environment of 5 devices, only to one.
After the issue happens sometimes the device can restore the RF in some minutes, hours or never more.

I am sorry to have covered old ground for you. I thought you may be locking up where rf12_canSend never returns true. In my case this has been an issue whereby the RF noise floor was never quiet enough for rf12_canSend to return true. I don't have any further ideas for you at this point.

So far so good 3 days and counting....
I have setup a test using latest JeeLib. If anyone is interested I have experimented with git submodules this has allowed me to associate the github libs (at a specific point) used in my project within the project repo itself without loosing association with the original lib repo.
Using this method of lib management has been fantastic for this example: I created a new dev branch 'rf-test' and in that branch fast-forwarded jeelib to the latest version and made the changes to code required for the test.
https://github.com/openenergymonitor/emonpi/commit/e96cb04ba8d4999a8381dd8cf620ff18fbd66afe
I have documented using sub modules here:
https://github.com/openenergymonitor/emonpi/tree/master/firmware/libraries

Still looking good :+1:

Great - declare victory before it decides to change its mind! :)


Edge language

When run in a pt-PT windows 10, script changes region to en-Us.
It is possible to change code to not affect region?
Thanks.

The region setting in the script simply tells the script how to interpret the date format on the following line. It should have no effect on anything outside of the script. Are you saying your machine's region setting actually changed to en-US? Can you post a screenshot of what you're looking at?

Hi. Yes. Correct. I noticed that cause hour changed to PM at taskbar.
I will send you pics.
On Sat, Nov 18, 2023, 13:41 LesFerch @.***> wrote:

The region setting in the script simply tells the script how to interpret
the date format on the following line. It should have no effect on anything
outside of the script. Are you saying your machine's region setting
actually changed to en-US? Can you post a screenshot of what you're looking
at?
—
Reply to this email directly, view it on GitHub
https://github.com/LesFerch/IEModeExpiryFix/issues/4#issuecomment-1817512876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BECZR65Y5T7UG2FYB3A3J5DYFC3HFAVCNFSM6AAAAAA7Q2OIG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGUYTEOBXGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi,
Please notice that vbs execution is ok.
PS1 has the behavior.
Also note that my windows and edge is in pt-PT.
Here are the pics.
I have tried in my laptop with windows 11.
On Sat, Nov 18, 2023, 13:41 LesFerch @.***> wrote:

The region setting in the script simply tells the script how to interpret
the date format on the following line. It should have no effect on anything
outside of the script. Are you saying your machine's region setting
actually changed to en-US? Can you post a screenshot of what you're looking
at?
—
Reply to this email directly, view it on GitHub
https://github.com/LesFerch/IEModeExpiryFix/issues/4#issuecomment-1817512876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BECZR65Y5T7UG2FYB3A3J5DYFC3HFAVCNFSM6AAAAAA7Q2OIG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGUYTEOBXGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

The pics did not come through, but don't worry about that. Now I know to look at the PS1 version. I assumed the region setting in the PS1 script would be specific to the script, like it is in VBS. I'll look for a fix. Thank you!

Hi,
Oh.
Thank you very much. :)
Keep the good work.
LesFerch @.***> escreveu em sáb., 18/11/2023 às 16:08 :

The pics did not come through, but don't worry about that. Now I know to
look at the PS1 version. I assumed the region setting in the PS1 script
would be specific to the script, like it is in VBS. I'll look for a fix.
Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/LesFerch/IEModeExpiryFix/issues/4#issuecomment-1817547278,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BECZR64FACM5LPCTPH57XWDYFDMPHAVCNFSM6AAAAAA7Q2OIG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGU2DOMRXHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Fixed.


Summary of requests to configure the number of items in various lists

Is your feature request related to a problem? Please describe.
This is a summary of requests to configure the number of items in various lists. [I'm having trouble attaching this as an .ods. It worked fine yesterday.]

Issue
Page Name
URL on DSpace 7 Demo
DS7 current number in list
URL on DSpace 6 XMLUI Demo
DS6 current number in list
Request

No action needed
Search Results
https://demo7.dspace.org/search
initial: 10; user configurable: 5-100
https://demo.dspace.org/xmlui/discover
initial: 10; user configurable: 5-100
none

No action needed
Administrative Search results
https://demo7.dspace.org/admin/search
initial: 10; user configurable: 5-100
none
N/A
none

No action needed
Administer Workflow results
https://demo7.dspace.org/admin/workflow
initial: 10; user configurable: 5-100
none
N/A
none

No action needed
MyDSpace - Your submissions
https://demo7.dspace.org/mydspace?configuration=workspace
initial: 10; user configurable: 5-100
none
N/A
none

Search Facet: Increase the number of options displayed with each "Show more" click #8429
Search facets
https://demo7.dspace.org/search
initial: 5; "Show more" adds 5 more options
https://demo.dspace.org/xmlui/discover
initial: 5; "view more" leads to user configurable: 5-100
intial:5; next click to 25, 50, 75, 100

same
Administrative Search facets
https://demo7.dspace.org/admin/search
initial: 5; "Show more" adds 5 more options
none
N/A
intial:5; next click to 25, 50, 75, 100

same
Administer Workflow facets
https://demo7.dspace.org/admin/workflow
initial: 5; "Show more" adds 5 more options
none
N/A
intial:5; next click to 25, 50, 75, 100

same
MyDSpace - Your submission facets
https://demo7.dspace.org/mydspace?configuration=workspace
initial: 5; "Show more" adds 5 more options
none
N/A
intial:5; next click to 25, 50, 75, 100

Make number of communities on the home page configurable #1749
Home page Communities
https://demo7.dspace.org/home
initial: 5; each click goes to next page of 5
https://demo.dspace.org/xmlui/
unlimited
unlimited

Make the number of communities in the Browse by Community page configurable #1750
List of Communities
https://demo7.dspace.org/community-list
initial: 20; "Show More" adds 20
https://demo.dspace.org/xmlui/community-list
unlimited
unlimited

No action needed
Browse by issue date
https://demo7.dspace.org/browse/dateissued
initial: 20; user configurable: 5-100
https://demo.dspace.org/xmlui/browse?type=dateissued
initial: 20; user configurable: 5-100
none

No action needed
Browse by authors
https://demo7.dspace.org/browse/author
initial: 20; user configurable: 5-100
https://demo.dspace.org/xmlui/browse?type=author
initial: 20; user configurable: 5-100
none

No action needed
Browse by titles
https://demo7.dspace.org/browse/title
initial: 20; user configurable: 5-100
https://demo.dspace.org/xmlui/browse?type=title
initial: 20; user configurable: 5-100
none

No action needed
Browse by subjects
https://demo7.dspace.org/browse/subject
initial: 20; user configurable: 5-100
https://demo.dspace.org/xmlui/browse?type=subject
initial: 20; user configurable: 5-100
none

Display more than 5 e-people or groups per page #1764
EPeople
https://demo7.dspace.org/access-control/epeople
intial: 5; each click goes to next page of 5
https://demo.dspace.org/xmlui/admin/epeople
intial: 15; each click goes to next page of 15
intial: 15; each click goes to next page of 15

same
Groups
https://demo7.dspace.org/access-control/groups
intial: 5; each click goes to next page of 5
https://demo.dspace.org/xmlui/admin/groups
intial: 15; each click goes to next page of 15
intial: 15; each click goes to next page of 15

Display all the fields for a Metadata Schema in one page and include IDs #1766
Metadata Schema: "dc"
https://demo7.dspace.org/admin/registries/metadata/dc
Initial: 25; each click goes to next page of 25
https://vtechworks.lib.vt.edu/admin/metadata-registry and select "dc"
unlimited
unlimited

Display all bitstream formats on one page and include IDs. #1767
Bitstream Format Registry
https://demo7.dspace.org/admin/registries/bitstream-formats
Initial: 20; each click goes to next page of 20
https://vtechworks.lib.vt.edu/admin/format-registry
unlimited
unlimited

Make the number of bitstreams on the Item pages configurable #1774
Simple Item page
https://demo7.dspace.org/items/03731881-2185-4baf-a6a8-1438a4d29dc8
Initial: 5; "Show more" adds 5
https://demo.dspace.org/xmlui/handle/10673/43
unlimited
unlimited

same
Full Item page
https://demo7.dspace.org/items/03731881-2185-4baf-a6a8-1438a4d29dc8/full?obo.page=1#p-obo
Initial: 5; each click goes to next page of 5
https://demo.dspace.org/xmlui/handle/10673/43?show=full
unlimited
unlimited

Add Recently Added section to Home and Community pages and make number of items configurable #1775
Home page
https://demo7.dspace.org/home
none
https://demo.dspace.org/xmlui/
Initial: 5; "view more" goes to next page of 20
initial: create setting; "view more" leads to user configurable: 5-100

same
Community page
https://demo7.dspace.org/communities/ac2fc454-e6bb-46e1-88eb-30242785f5af
none
https://demo.dspace.org/xmlui/handle/10673/1
Initial: 20; "view more" goes to next page of 20
initial: create setting; "view more" leads to user configurable: 5-100

same
Collection page
https://demo7.dspace.org/collections/7d4f0e7b-e802-474c-a636-2a913c17dbb6
Initial: 5; each click goes to next page of 5
https://demo.dspace.org/xmlui/handle/10673/52
Initial: 20; "view more" goes to next page of 20
initial: create setting; "view more" leads to user configurable: 5-100

Those lists that have are adjustable by the user I have marked as “No action needed.” This includes the various Search results and Browse by date, subject, author, and title. The other lists can’t be configured by the user so I think they should either be 1. set much higher per page, 2. have no limit at all, or 3. controlled as a setting.

I think that (3) is the only choice that will satisfy every site.  Let any value less than 1 mean "no limit" and it can cover all three. it was really easy to make the initial sizes of the browse result lists configurable. - @mwoodiupui

So, as I understand it, there are two categories of lists under discussion:  lists whose window size can be adjusted by the user, and those with a fixed window size.  The latter are discussed above.  I feel that the former should also have a configurable initial size (because I've been asked to make them shorter here).  Example:  #1771 .
While I'm throwing out ideas:  should the adjustable-size windows have an initial size stored in the user's account?  That is:  user A hates scrolling and wants short windows, while user B hates paging through lists and wants long windows.  Why shouldn't each be able to save that as a preference?

DSpace7_lists_20220818.ods

As this is simply a summary ticket, I'm going to just pull it over to an "unscheduled backlog". It's not actionable, but I do understand it's a useful resource to find tickets related to this configuration issue.


Disable processing for offscreen overworld creatures

It would be nice to have big sprawling overworld areas with 15-25 creatures scattered about, but this would currently put a strain on some devices such as my mobile phone.
We should investigate disabling processing for offscreen creatures to see if this improves performance, and allows for these big sprawling overworld areas.

[ ] Add a variant of the stress test which specifically adds offscreen creatures, or offscreen decorations
[ ] Measure the performance impact of offscreen creatures and offscreen decorations
[ ] Disable processing on things like animation players, and measure the performance improvement

With the new focus on career mode, we will never need sprawling overworld areas like this.