[Animated] crashes when animated value is computed with other variables.

I'm using a single Animated.Value to drive the opacity of 2 components, when I compute ( 1 - this.state.anim) it crashes the app with some ShadowQueue error on XCode.
How to repro would be like
var Sample = React.createClass({   getInitialState() {     return {       anim: new Animated.Value(0),     };   },   render() {     return (       <View>         <View           style={{           opacity: this.state.anim,           }}         />         <View           //errors on this           style={{           opacity: 1 - this.state.anim,           }}         />       </View>     );   }, });

I don't think things should crash however I will say this is not how animated works.
this.state.anim is not an actual value it is an instance in which Animated.View can grab the current value and apply it, watch here. Also you need to use Animated.View to use animated values. Watch how this all works here (https://www.youtube.com/watch?v=xtqUJVqpKNo)

I bet the native layer is crashing on a NaN opacity value. The app should throw up a redbox but probably should outright crash back to the home screen.

Thanks, @browniefed for pointing me in the right direction, I'm now using interpolate, but yes @ide, in the previous versions where I tried computing the other variables with Animated.Value it does not crash in XCode, funny that I only realized this mistake in 0.14.2.

This looks like it can be closed?


[Dashboard] Dataset name doesn't change when it's updated

This PR fixes a bug that maps or dataset names were not updated in the main view when the user changes it via quick actions.
This name should be updated now and whenever liking a dataset from recent content it should be updated in the sections below.
Acceptance

Dataset/Map name change in Search

Search any maps/datasets within your uploaded content using the Search bar
Change the name using map/dataset quick actions
Check that the name's been changed within the original card
Please check both cases (map and dataset)

Like consistency in Home

Go to dashboard's Home Page
Like any map/dataset from recent content and check that it's been updated in the proper section below.

Related to #14733.

Steps followed for acceptance (staging):
Create user -> Log in -> Create a map

[ ] Search keyword to make the new map appear in search page
[ ] In Search page: Change map name -> check that name is properly changed
[ ] In Search page: Change map privacy -> check that privacy is properly changed
[ ] Go to Home page -> check that map name and privacy have been updated

Acceptance OK!


schema parser dies on postgres table namespaces

x.sql
CREATE TABLE public.foobar (
  id text
)

gives
  caused by: error parsing x.sql
  caused by: error parsing Postgres `CREATE TABLE`
  caused by: error at 1:20: expected `(`

Temporary workaround: Just substitute a fake table name, because very few workflows actually use the table name in the schema for anything interesting.

for interested first-time contributors, this is still an issue in 0.4.2-beta.5
Error: error: error parsing Postgres CREATE TABLE
  ┌─ x.sql:1:20
  │
1 │ CREATE TABLE public.foobar (
  │                    ^ expected "("


Remove references to deprecated v1 Android embedding

Remove references to deprecated v1 Android embedding
To ensure this plugin will work with users running the next stable version of Flutter remove references to the v1 embedding.
The v1 embedding was deprecated around 6 and a half years ago. In Flutter 3.22, the Flutter tool dropped support for building v1 apps entirely. Flutter plans to delete version one of it's Android embedding in the next stable release, per https://medium.com/flutter/whats-new-in-flutter-3-22-fbde6c164fe3 (in the "Removal of v1 Android embedding" section).
When that deletion happens, any apps using plugins that still have references to the removed classes will fail to build when updating to the next stable version (probably Flutter 3.26).
As a part of this deprecation, the Flutter Android team is doing community outreach by filing bugs and submitting some pull requests to update plugins to minimize the impact this removal has on the community.
Some example PRs:

Flutter team maintained plugins: https://github.com/flutter/packages/pull/6494
android_alarm_manager_plus https://github.com/fluttercommunity/plus_plugins/pull/2864

Consequences:

This change should have no impact on users of this plugin that are building apps using the v2 embedding (we don't have a percentage to share, but this is the vast majority of users).
It will remove support for users that are still using the v1 embedding on versions of Flutter older than 3.22.

If this change doesn't land, this plugin will instead be broken for all apps building on the next stable version of Flutter and beyond.
Is there a way to support both v1 and v2 embedding apps in the next stable version of Flutter?
No.
This is the PR where we are removing the deprecated engine classes: https://github.com/flutter/engine/pull/52022

Thanks for the detailed issue.
I'll do some maintenance on this lib in the coming weeks

I believe this should not be an issue for the latest release of this library. Please feel free to re open the issue if I am wrong.

I still see references in your example app.
That wont impact your users but will cause the example to break.

Ah interesting this is a brand new example application

As in you made the example with a recent version of flutter? If so what version? I thought we had migrated all the templates but if not then I need to follow up with a flutter framework change.

From what I can tell our template code is migrated.
https://github.com/search?q=repo%3Aflutter%2Fflutter+path%3A%2F^packages\%2Fflutter_tools\%2Ftemplates\%2F%2F+("io.flutter.view.FlutterMain"+OR+"io.flutter.view.FlutterNativeView"+OR+"io.flutter.view.FlutterView"+OR+"io.flutter.embedding.engine.plugins.shim"+OR+"io.flutter.app"+OR+"PluginRegistry.Registrar")&type=code
The lone example shown there happens to use the same package but does not reference any of the removed classes.
That said if I missed something please let me know.


added ananya in contributors

Issue Number #
Changes proposed in this pull request :
[Live Link](provide link here)

@ananya-agrawal you did  not add the image in the given path.


Adding c29r3 staking pool

Hi c29r3! Thank you for your submission. We follow a sequential order for all the resources, so I kindly ask you to move your entry at the bottom of the queue, thank you 🤗
Uhh and don't forget to star the repo 🚀

Got any chance to look at this PR?

To be fair with PR #19 I would suggest pointing the pool to your actual block producer website, so the user can make a weighted decision on why to delegate to you rather than other people. Awesome Mina Tools doesn't aim to become another delegators list like "StakeTab's delegators list", but rather a curated list of resources. Linking the StakeTab's profile doesn't really add any specific value to the block producer (e.g. why delegating to you).
Thank you for your understanding 🙏 . Feel free to update the pr and ping me directly for a quick merge :)


only get 200.html , but no other pages. I have no idea what to do @@

Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.
File sizes after gzip:
147.55 KB  build/static/js/main.6cbd44b6.js
15.12 KB   build/static/css/main.d0134822.css
The project was built assuming it is hosted at the server root.
To override this, specify the homepage in your package.json.
For example, add this to build it for GitHub Pages:
"homepage" : "http://myname.github.io/myapp",
The build folder is ready to be deployed.
You may serve it with a static server:
npm install -g serve
serve -s build
🕷   Starting crawling http://localhost:64801/
Error: Uncaught [SyntaxError: Unexpected token <]
at reportException (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:58:24)
at processJavaScript (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:130:7)
at HTMLScriptElementImpl._eval (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:65:7)
at e (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/browser/resource-loader.js:31:22)
at Object.check (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/Document-impl.js:89:11)
at /Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/Document-impl.js:108:12
at wrappedEnqueued (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/browser/resource-loader.js:255:16)
at Request.request [as _callback] (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/browser/resource-loader.js:203:9)
at Request.self.callback (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/request/request.js:188:22)
at emitTwo (events.js:106:13) SyntaxError: Unexpected token <
at createScript (vm.js:56:10)
at Object.runInContext (vm.js:88:10)
at processJavaScript (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:128:10)
at HTMLScriptElementImpl._eval (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:65:7)
at e (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/browser/resource-loader.js:31:22)
at Object.check (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/Document-impl.js:89:11)
at /Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/Document-impl.js:108:12
at wrappedEnqueued (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/browser/resource-loader.js:255:16)
at Request.request [as _callback] (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/browser/resource-loader.js:203:9)
at Request.self.callback (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/request/request.js:188:22)
Error: Uncaught [TypeError: Cannot read property 'fn' of undefined]
at reportException (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:58:24)
at processJavaScript (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:130:7)
at HTMLScriptElementImpl._eval (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/HTMLScriptElement-impl.js:65:7)
at e (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/browser/resource-loader.js:31:22)
at Object.check (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/Document-impl.js:89:11)
at /Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/living/nodes/Document-impl.js:108:12
at wrappedEnqueued (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/browser/resource-loader.js:255:16)
at Request.request [as _callback] (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/jsdom/lib/jsdom/browser/resource-loader.js:203:9)
at Request.self.callback (/Users/binny/Desktop/Big-Project/projs/batchfield-react/node_modules/request/request.js:188:22)
at emitTwo (events.js:106:13) TypeError: Cannot read property 'fn' of undefined
at eval (webpack:///./src/owl.carousel.js?:1667:3)
at eval (webpack:///./src/owl.carousel.js?:1701:3)
at Object. (http://localhost:64801/static/js/main.6cbd44b6.js:1:432398)
at e (http://localhost:64801/static/js/main.6cbd44b6.js:1:420602)
at eval (webpack:///./components/OwlCarousel.jsx?:23:1)
at Object. (http://localhost:64801/static/js/main.6cbd44b6.js:1:420741)
at e (http://localhost:64801/static/js/main.6cbd44b6.js:1:420602)
at http://localhost:64801/static/js/main.6cbd44b6.js:1:420689
at http://localhost:64801/static/js/main.6cbd44b6.js:1:420694
at n.(anonymous function).exports (http://localhost:64801/static/js/main.6cbd44b6.js:1:420314)
🔥 'render' from react-snapshot was never called. Did you replace the call to ReactDOM.render()?
🕸   Finished crawling.

Please provide small application where it is possible to reproduce error


Tidying works

Use ffi types, size_t, c_char, etc
Replace deprecated failure with anyhow
rustfmt
Use less restrict x.y version number in Cargo.toml, which is suggested for lib crates
Replace deprecated uninitialized() with MaybeUninit
Tidy use ... statements.
Other code simplifications

Thanks a lot for this PR !
I also merged https://github.com/mthh/sfcgal-sys/pull/2.
I will update a few other dependencies (geo, geojson) to be aligned with the rust geo ecosystem and make a new release later this day.


stat/distmv: rename NewNormalChol and add Sigma as an input argument

I'm not sure this is the best name, but I can't think of anything better.

Fixes #47

Do you have any ideas for the name?

No unfortunately - I would have suggested one if I did.

What exactly is the reason for retaining this now since #47 says it's signficant raison d'être of saving allocation no longer exists?

It saves the cost of computing Sigma, which is an O(n^3). Thinking though, it may be better to export particular functions (like LogProb), where the Cholesky is already known. This saves all of the overhead (allocation, computation of sigma, etc.)

We've done more of the latter. If there's a compelling use case, we can reconsider.


Kenneth Reitz

https://www.kennethreitz.org/essays/the-reality-of-developer-burnout

Thanks, that was a good read.

Thanks! Added: https://github.com/nayafia/awesome-maintainers/pull/19


fix compatibility with python 3.2+

Now script can run also on systems where python 3.2+ is default python version
Also changed tabs into spaces and added  2 lines to template script to echo variables.

@alekibango - thanks for the pull request!


Unit Test: Create Event Page test

[ ]  This issue looks to resolve the lack of unit test for the create event page

Closing this issue due to lack of engagement. If you feel this needs to be revisited please reach out to leadership.


[UTIL] fix the bug in nntr parallel run

This PR fix the nntr prarallel run. Previously it is not set properly according to NNTR-NUM-THREADS options in meson_options.txt
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2802. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2802-202411221610270.057086944580078-f87ba9785fb8ef766b289df1490e6b17973ddfae/.


docs: fuzzing with go-fuzz tutorial

This commit adds a tutorial on fuzzing with the go-fuzz library into the docs folder. It includes an introduction to fuzzing, setup and installation steps to run go-fuzz with lnd, tips to generate a valid corpus for use with go-fuzz, and finally it includes a small explanation of the test harness that was used
to find bugs in lnd.

Addressed changes and noticed that I forgot to instruct the reader to change the package name of wirefuzz.go to the new folder they created.  Should be ready for merge now!


add Sparrow (Terminal)

s.a. https://github.com/sparrowwallet/sparrow/releases/tag/1.7.0
maybe brings whirlpool to raspiblitz?

YES!
# download
wget https://github.com/sparrowwallet/sparrow/releases/download/1.7.0/sparrow-server_1.7.0_arm64.deb
wget https://github.com/sparrowwallet/sparrow/releases/download/1.7.0/sparrow-1.7.0-manifest.txt
wget https://github.com/sparrowwallet/sparrow/releases/download/1.7.0/sparrow-1.7.0-manifest.txt.asc
# checksum check
sha256sum -c sparrow-1.7.0-manifest.txt --ignore-missing
# get PGP pubkey
curl https://keybase.io/craigraw/pgp_keys.asc | gpg --import
# signature check
gpg --verify sparrow-1.7.0-manifest.txt.asc

# options
/opt/sparrow/bin/Sparrow --help

# start
/opt/sparrow/bin/Sparrow

Change
"preventSleep": false,
to
"preventSleep": true,

A guide with screenshots and using tmux: https://sovrnbitcoiner.com/an-iphone-enters-the-poolside-chat/


fontcreator: Add version <IP_ADDRESS>62

FontCreator for Windows - the most popular font editor
code modified from BluYous/ScoopBucket

[x] I have read the Contributing Guide.

/verify

/verify

/verify

/verify


Compilation with relative path imports fails when specifying working directory

Compiler cannot find imported files which are in a folder nested inside the working directory specified. Error returned is : File import callback not supported

Hello @thegostep, we will look into that issue. Thank you.

Hi, @thegostep! Can you confirm the problem still exists? If so, can you provide your repo so we can examine what's the case?  Thanks!

@thegostep I think that this bug no longer exists.


In pickLongestCandidateSignature, instantiate using inferred type arguments

Fixes #26639 and #26132

See https://github.com/Microsoft/TypeScript/issues/26426#issuecomment-412689587 -- for some reason the code only runs in services.


CI tests via GitHub actions and conda

This is a fairly minimal version of continuous integration (CI) tests using GitHub actions consisting of two workflows:

python-package-conda: This workflow uses a conda-based install for everything and tests only against the latest scipy and Python 3.6 and 3.9.  So compared with our current Travis CI testing, we lose scipy-0.19.1 testing and Python 2.7.  Coverage is implemented, but not sure (yet) whether it properly connects to coveralls.
control-slycot-src: This workflow installs slycot from source, which allows testing against the latest version of slycot (in case we need it). No coverage testing.

This workflow users coveralls and pushes results up to coveralls.io.
Note: I think that as soon as this PR is merged then we should see the workflows show up in the Actions tab on GitHub.  This is working correctly in my personal fork.

Coverage increased (+10.9%) to 87.539% when pulling 627754fd9c4b7bd81cc16b9e8e22da1e85c8f308 on murrayrm:github-actions-conda into a82b520e5acb95ae37ebfc2610a3b5065cee7927 on python-control:master.

Coverage increased (+10.9%) to 87.539% when pulling 627754fd9c4b7bd81cc16b9e8e22da1e85c8f308 on murrayrm:github-actions-conda into a82b520e5acb95ae37ebfc2610a3b5065cee7927 on python-control:master.

I am not done with Slycot yet (coming closer), but see https://github.com/bnavigator/Slycot/blob/3c0cb727d5371996c038c94e9bd68621a5430b8a/.github/workflows/slycot-build-and-test.yml for an example how to deal with coveralls.

I am not done with Slycot yet (coming closer), but see https://github.com/bnavigator/Slycot/blob/3c0cb727d5371996c038c94e9bd68621a5430b8a/.github/workflows/slycot-build-and-test.yml for an example how to deal with coveralls.

I think this PR is good to go.  There are some small changes that @bnavigator suggests, but I don't these these substantially add/enhance functionality => we can probably stick with this for now (and see if it all works when merged).

I think this PR is good to go.  There are some small changes that @bnavigator suggests, but I don't these these substantially add/enhance functionality => we can probably stick with this for now (and see if it all works when merged).

Sorry, for being so pedantic here. I went through many of these hoops for Slycot and the openSUSE rpm packages so I want to share the "proper" solutions.

The coveralls jobs should get a proper name tag so that the listing looks nicer. (coveralls-python FAQ previously linked)
Compare https://coveralls.io/builds/36275777 to https://coveralls.io/builds/36276758
The coveralls link on the master commit :heavy_check_mark: is still from Travis. Do we remove Travis eventually or do we try to merge those two coveralls reports per PR/commit, Otherwise we will always have to subsequent datapoints in the history, possibly with different values.
The way miniconda is set up this limits everything to Unix. Maybe even Linux only.

Sorry, for being so pedantic here. I went through many of these hoops for Slycot and the openSUSE rpm packages so I want to share the "proper" solutions.

The coveralls jobs should get a proper name tag so that the listing looks nicer. (coveralls-python FAQ previously linked)
Compare https://coveralls.io/builds/36275777 to https://coveralls.io/builds/36276758
The coveralls link on the master commit :heavy_check_mark: is still from Travis. Do we remove Travis eventually or do we try to merge those two coveralls reports per PR/commit, Otherwise we will always have to subsequent datapoints in the history, possibly with different values.
The way miniconda is set up this limits everything to Unix. Maybe even Linux only.

I'll move these comments to issue #446 so that we can continue to track these improvements. I mainly wanted to get shifted over to some new test infrastructure since Travis CI is getting so frustrating. (GitHub actions clears commits in 2-3 minutes, versus what was often 30+ min for Travis).
I think we can leave Travis and GitHub Actions running for a few days, as we see whether new PRs and things are properly handled, but then I think we shift away from Travis completely.

I'll move these comments to issue #446 so that we can continue to track these improvements. I mainly wanted to get shifted over to some new test infrastructure since Travis CI is getting so frustrating. (GitHub actions clears commits in 2-3 minutes, versus what was often 30+ min for Travis).
I think we can leave Travis and GitHub Actions running for a few days, as we see whether new PRs and things are properly handled, but then I think we shift away from Travis completely.


Add Incubation Project to README.md

Current State:
Currently, we have one incubation project listed here. We need to add our second incubation project, the tbLEND protocol.

Task:
Please add our tbLEND project to the chart here in our org's README.

For the description, see this overview of the project.
Discord channel link: https://discord.com/channels/937858703112155166/1149083370408640626
As there is no repo yet, use the Discord link for the project's name, similar to how the "credential selector" links to its project.
Project Lead: @ianpatton

Picking Up This Issue:

If you'd like to work on this, please comment "picking this up" below, and I'll assign the issue to you

Questions:

If you need assistance or clarification, feel free to comment below.
Feeling overwhelmed? Join our #hack-together channel and collaborate with a buddy.
New to open-source? Check out our Hacktober #getting-started channel.
Leaderboard: Check your ranking after finishing this task.

Resources:

READMEs are written in Markdown. If you're unfamiliar, here's a Markdown cheatsheet to help.

Tip: Use the "Preview" tab at the top when editing the README to ensure the format aligns with your expectations.

Good Luck! 🍁

picking this up

Also I want to ask that should I add a 3rd table next to the previous 2 tables or make it in the new line

@Pratham271 Thank you so much for your enthusiasm and readiness to contribute!
I'd like to note that Hacktoberfest officially kicks off on October 1st. Contributions made before the event may not be eligible for the challenge. However, if you're keen on this specific issue, feel free to start working on it, but I'd recommend holding off on submitting your PR until the event begins.

make sure you're registered, registration opens September 26th.

Also stay tuned our Hacktoberfest channels  in discord will be live this Thursday. That's where you'll find all the updates leading up to and during Hacktoberfest. I'm super excited to see your contributions!
To claify, I would love it to be right next to "credential selector" the same way "Web5" and "tbDEX" are in the chart above it.  - thanks!

@Pratham271 are you still interested in taking this one?

Hello! I'd like to work on it if available! Thank You!

Hello, I would like to work on the issue. Thank you!

Yes I am working on it
On Sun, 1 Oct, 2023, 09:56 Angie Jones, @.***> wrote:

@Pratham271 https://github.com/Pratham271 are you still interested in
taking this one?
—
Reply to this email directly, view it on GitHub
https://github.com/TBD54566975/developer.tbd.website/issues/731#issuecomment-1741953299,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT6EA4SDMFRF6MUURITCTHTX5DWITANCNFSM6AAAAAA464HJIA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey I am also willing to work on this. Please assign me this @EbonyLouis

@Pratham271 hey!! How are things going with this PR? Do you need any assistance?

I generated a pr for this issue today but it the readme files are on another repo

@Pratham271 yes, send me a link to your PR please

https://github.com/TBD54566975/.github/pull/8
Here is the link to that pr, please check and let me know if I have to change something


Very low framerate

Game seems to run at a low framerate when not sped up, and it makes it difficult to reliably flip the bits.

The app now updates the background less often. Please try again with version 1.16.

Installed on android and the numbers looks choppy on default speed,
not sure what engine this was made in but you might want to use interpolation for the movement of the bits, perhaps that might fix the 'framerate' issue
here's a 5min example from Garbaj:
Fixing Jittery Movement In Godot

I am having the same experience on Android. Tapping on the invading bits to flip them works only half of the time for me and it all seems really low fps, except when the speedup is active.

Version 1.21: The game now runs at a fixed (and, in most cases, higher) frame rate. Tried it in the emulator with different screen resolutions, and it runs much smoother now, even on large-sized displays.


dxScrollView doesn't have the display: block style and scrolling doesn't work

<EMAIL_ADDRESS>dxScrollView should have this style out of the box for proper scrolling.
Example - http://plnkr.co/edit/cYQbKLRlZfghS6MTtzNx?p=preview

Duplicated in T472952


Is integrating elm-lint in scope?

https://github.com/jfmengels/elm-lint seems to hint to a lot of good practices.
Do you see including this in scope for this package or should someone turn it into a separate package?

Hi!  https://github.com/stil4m/elm-analyse, a similar tool, is going to have an Atom package (https://twitter.com/ElmNetherlands/status/875063341575798784).

Wow! This is cool!


Write a script to populate a Scala repo server from a local static repo

Fetch each schema from under /schemas (e.g. https://github.com/snowplow/iglu-central)
POST each schema to an Iglu Scala Repo

I've got this working for iglucentral.com, but there's one problem: I can't seem to download every JSON, just the 13 linked to in index.html. This happens when I use
httrack iglucentral.com --robots=0

or
wget -r -l inf -e robots=off --no-cookies iglucentral.com

Any idea what about the website might be causing this?
It's not a huge problem since we can just download the latest Iglu Central release from GitHub instead.

I think push from local copy is safest...


[Run] Provide access to network share

It would be nice and useful, since I guess I'm not the only one using network shares in everyday life.
So, \\network_share\ currently does not work

Would you please take this into consideration?
Thank you.

Good idea @mark00p, here's the PR for this #4224 and the original issue is here #4096
closing this as duplicate


Evaluate method added to DDPG, PPO1, VPG

Fix for #38 . Can be easily extended by copy-pasting the same code to other algos.

I guess we can make it a common method in utils.py under deeprl. Would that be fine? Because the code needn't be different for each of them

Yup, should work.

Just the common function comment, then I think we can have this PR merged as well. @Zeus3101 Please also make sure about to have a class variable signature of the function I.e., self.evaluate = evaluate

Please check the new commit. Made evaluate a common function in utils.py under jigglypuffRL.common

Looks like there are some conflicts, can you resolve these?

Resolved changes and removed evaluate from parameters descriptions


Lots of requests, but are there any examples using these other than those in the README?

Just looking to try and use more of the library. Are there anymore examples of the other Requests that are in the repo?
thanks, K

Addressed in rewrite or no longer relevant.


Nested placeholder don't works with argument

When using nested placeholders (e.g. %changeoutput_equals_input:{objective_score_language}_matcher:1_ifmatch:EN_else:Otherlanguage%) with replacements (e.g. /papi parse me %shortcut_trad:test), the expansion raises an error : java.lang.NumberFormatException: For input string: "objective_score_language".
I see two ways to fix this issue : replace the {n} for replacements with other chars e.g. <n>, or add a check to only check numbers when checking for replacements.

I can't really see where this is caused by the shortcut expansion?

I can see now what you mean. Haven't looked into this expansion for a while so I was a bit confused.
This sadly isn't as easy to fix as you may think. I use a method provided by Java that replaces {n} with whatever values I give, so if I want this to work, would I need to figure out another system to make this work. Perhaps with Regex, but that could have a negative impact on performance if the amount of matches is too high...
Need to look into this.

Thanks you for your work!

Mind testing out this jar (Zipped it as GitHub doesn't support jar uploads. So you have to unzip it)
Shortcut-1.2.0.zip

That's strange, from my testing did it work fine.
Used this file:
Value 1: {0}
Value 2: {1}
Missing Value: {2}

And tested with the following commands:
papi parse --null %shortcut_test:apple:pineapple:banana%
papi parse --null %shortcut_test:apple:pineapple%

Results:
[17:01:41] [Server thread/INFO]: Value 1: apple
Value 2: pineapple
Missing Value: banana
[17:01:48] [Server thread/INFO]: Value 1: apple
Value 2: pineapple
Missing Value: {2}

Just in case, remember that this expansion parses custom replacements before any PAPI placeholders, so if the {0} comes from such a placeholder, you have to accept that it won't work like this.

I have this in my shortcut file:
%changeoutput_equals_input:{objective_score_language}_matcher:1_ifmatch:{0}_else:Otherlanguage%

When I run /papi parse ascpial %shortcut_trad_en:test% the result is {0}.
If my score is different from 1, the output is correct (OtherLanguage)

I found the issue. Accidentally checked for if the number of arguments was 1 to return text without handling replacements...
Please try this version now:
Shortcut-1.2.1.zip

Works perfectly now! :ok_hand:

Okay. Will later merge the PR and publish it.

Should now be live on the eCloud. It may require verification from the staff there before you can download it through PlaceholderAPI


Cloud Source Repositories EOL

It seems that Cloud Source Repositories are being retired for new customers. Will the option to configure your function from a repo_source other than Cloud Source Repositories be planned for a future release? If not I see that there are still options to use Google Cloud Storage. I know something was mention at Google Next about using GitLab SaaS as a replacement for small org's and hobbiest, wasn't sure if there is a planned product replacement that will get added down the line. Thanks

bumping the comment. Still interested if a different repo source will be supported down the line. If the answer is "no" feel free to close


Cannot parse ATI -  "ParseString" error

I'm on 0.8.4 at the moment and trying to parse the manufacturer revision information. I've tried working through serde_at/src/de/mod.rs to try and understand the failure but can't quite grok it.
The request I'm sending:
#[derive(Clone, AtatCmd)]
#[at_cmd("I", responses::Ident)]
pub struct IdentificationInformation;

The response struct:
#[derive(Clone, Debug, AtatResp, Serialize)]
pub struct Ident {
    pub revision: String<consts::U128>,
}

The raw logs:
DEBUG [atat::client:112] Sending command: ""ATI""
DEBUG [atat::ingress_manager:118] Received response ""Quectel\r\nUC20\r\nRevision: UC20GQBR03A12E1G""

However, the ParseString error is always returned. Any ideas? I get the feeling the Quectel\r\nUC20\r\n section of the string is confusing the parser, as the modem doesn't echo back the ATI first.

Just to get a base understanding here.

as the modem doesn't echo back the ATI first

Is this due to you not having ATE enabled, or is the ATI command a special-case, that doesn't ever echo? In case of the former, i think your issue is that we currently rely on the echo to distinguish between URC's, and command responses. This is definitely something we want to improve, and i think the road towards it was paved by #70, so it should be possible. See #82 for more on this.
In case of the latter, this might be solvable by adding force_receive_state = true to the at_cmd, like so: #[at_cmd("I", responses::Ident, force_receive_state = true)]. That will blindly force the ingress end of atat into an Receiving state after sending the command, and thus not require the echo to be present. This is also the basic suggestion to solving #83, but i haven't had time to test if it works in all cases.
If this keeps being a problem, please report back here, and i will try to setup a small test to see if i can replicate :)

ATE is on in this case. I actually had confused my concepts a bit - commands such as AT+CGREG? which print +CGREG: 0,1 were what I was thinking of as "echo". However, commands like AT+CGSN print the bare serial number without any prefix, which is parsed correctly by atat.
Because of this confusion on my part, force_receive_state = true doesn't work since it is entering the receive state with no issues.
One thing I've noticed about all the other commands we're executing is their results always are single-line. ATI is unique in that it returns 3 lines before the empty line and OK. Could these be throwing off the parser?

Ahh, alright. In that case i think i get the issue.
Do you have the option of testing of the full rx,tx in a regular terminal, and posting the full correspondance here? That way i can add a regression test to test it out, and at the same time make sure it doesn't break in the future.
Something along the lines of:
> ATI
< ATI
< Quectel
< UC20
< Revision: UC20GQBR03A12E1G
<
< OK

One other thing to notice, is that String expects the response to be surrounded by ", but this also does seem to be the case here, based on your raw logs?

I think the logs just put extra quotes around things. Here's an example correspondence with some "normal" commands as well - I don't have local echo turned on, so the commands you're seeing are the ones sent back by ATE being on.
AT
OK
AT+CGREG?
+CGREG: 0,1

OK
AT+CGMI
Quectel

OK
ATI
Quectel
UC20
Revision: UC20GQBR03A12E1G

OK

Cool :+1:
Does CGMI work with atat currently?

Yes it does! The struct for that is
#[derive(Clone, Debug, AtatResp, Serialize)]
pub struct ManufacturerId {
    #[at_arg(position = 0)]
    pub id: String<consts::U64>,
}

Okay, cool! Then i guess the string thingy is indeed a logging thing.
I will try to setup a regression test on this, to see if i can figure out why ATI doesn't seem to parse..
What you could try in the meantime, is to attempt with the newly introduced CharVec type: https://github.com/BlackbirdHQ/atat/blob/c57de3d23e99301a10dfaa44c07427186c0df1d0/serde_at/src/de/mod.rs#L22-L119
use serde_at::CharVec;

#[derive(Clone, Debug, AtatResp)]
pub struct IdentificationInformationResponse {
    pub app_ver: CharVec<consts::U32>,
}

Not sure if that requires you to update atat version though?
I will be away most of the coming week for easter, so i might not be able to test it out until i get back.

I'm trying to avoid updating to 0.9.0 because of the removal of log-logging. I think defmt's inablity to produce logs using stdout/logging is a problem with defmt, not atat, so once I can work out how on earth parsing of the interned strings works I'll probably open a PR upstream to provide a std-based global_logger.
Luckily, 0.8.4 still works (almost!) with CharVec - I get back a vec of bytes, which converted to a string becomes QuectelUC20Revision:UC20GQBR03A12E1G - the correct response, minus newlines.
Our use of ATI is to try and determine common factors in flaky modems - the newlines aren't important because I can pull out the revision anyway. This is a great solution for now!

Ahh, yeah thats fair enough (Sorry for blundly removing the log_logging, wasn't aware of anyone using it :) I would happily take a PR that adds it again, if you were to make it?)
I think it should be possible to make a defmt -> log facade that kinda just acts as if it had been a regular log::logger. That would indeed be a great addition to the defmt infrastructure.

@mon Just to let you know, the log logging is now back, thx to @fkohlgrueber and #92

Excellent news! I'll update to 0.10.0 next time I add more features to my project. Great to be back in line with master :)

It will be part of 0.11.0, so you should probably update to that one instead 😉
I won't do the release until we have the heapless dependency bump merged though, unless you strictly require it with heapless 0.5.5?

Nope! No problems there

@mon Released :tada:  https://crates.io/crates/atat
Give it a spin when you get time, and let me know if anything is not working.

Been a few months but finally got time to get back into this - main issues are just updating the initialization boilerplate from 0.8.4 to 0.11.1, the examples appear to be out of date again.
Specifically, Queue(heapless::i::Queue::u8()); for all the initializers doesn't work because heapless::i doesn't contain Queue in heapless 0.7.0. I fixed it using Queue::new() instead.
My own extensions have broken too -
<A as AtatCmd<LEN>>::Error` doesn't implement `std::fmt::Debug`  is breaking my "coerce everything to anyhow::Error" strategy, is there better way to get the error as a string in newer atat?
I have a macro that creates wrapper functions around my requests, an example as the compiler sees it is:
    pub fn get_manufacturer<A: AtatCmd<LEN>, const LEN: usize>(&mut self) -> Result<<requests::GetManufacturerId as A>::Response> {
        self.send(&requests::GetManufacturerId)
    }

0.11.1 broke this too due to cannot find associated type `Response` in `A`  and I'm not sure whether there's some syntax magic to fix it, whether it's impossible or if there's a better way.
Thanks for continuing to help out with this - it seems I still have a lot of rust to learn!

Hi!
I am sorry about the state of the documentation & examples. They do seem to be a bit out of date. Guess i should really push to have them fixed and added to the CI.

Specifically, Queue(heapless::i::Queue::u8()); for all the initializers doesn't work because heapless::i doesn't contain Queue in heapless 0.7.0. I fixed it using Queue::new() instead.

This would be the correct way :+1:

My own extensions have broken too -
<A as AtatCmd>::Errordoesn't implementstd::fmt::Debug` is breaking my "coerce everything to anyhow::Error" strategy, is there better way to get the error as a string in newer atat?

This would be because A::Error is no longer forced to implement Debug. What would could do in your case would be:
    pub fn get_manufacturer<A: AtatCmd<LEN> + Debug, const LEN: usize>(&mut self) -> Result<<requests::GetManufacturerId as A>::Response> {
        self.send(&requests::GetManufacturerId)
    }

0.11.1 broke this too due to cannot find associated type Response in A and I'm not sure whether there's some syntax magic to fix it, whether it's impossible or if there's a better way.

I think this is a follow-up error on the Debug one? A::Response should at least still be a thing..

I might actually need another feature to complete this - want me to open a new issue or keep commenting on this one?
So this works:
    pub fn get_manufacturer(&mut self) -> Result<<requests::GetManufacturerId as AtatCmd<10>>::Response> {
        self.send(&requests::GetManufacturerId)
    }

But obviously 10 has to be entered manually.
I came very close by using the LEN from AtatLen:
    pub fn get_manufacturer(&mut self) -> Result<<requests::GetManufacturerId as AtatCmd<{<requests::GetManufacturerId as AtatLen>::LEN}>>::Response> {
        self.send(&requests::GetManufacturerId)
    }

...but this is just the struct len, not the ident len as well.
Would a viable solution be to provide a CMD_LEN or similar in the impl of AtatLen? I can make the PR for that if you reckon it's a good idea.

In addition, it took some work but I got the send function to work by constraining the type of Error, I wasn't aware you could restrict trait member types like this!
    fn send<A: AtatCmd<LEN, Error=atat::GenericError>, const LEN: usize>(&mut self, cmd: &A) -> Result<A::Response> {
        self.client.send(cmd).map_err(|e| anyhow!("AT error: {:?}", e))
    }

Apologies, but I've had to give up trying to port my serial ingest to the new atat - I'm leaving my current company and won't be doing any more rust for the foreseeable future... Thank you for your time so far, it's been a pleasure.

Sorry to hear you didn't manage to make it work, but hey!  Congratz on the new job & best of luck!


Add user-contributions-stats-in-hovercard feature

Implements #4657 (per https://github.com/sindresorhus/refined-github/issues/4657#issuecomment-922159327)
Test URLs
Any Issue and PR page, e.g. this one and that linked above.
Screenshot/screen capture

Notes to reviewers:

It's based (simplified) on the 'Contributors on Github' extension.

It makes 3 connections:
For commit count and contributions position: (only the first 30 usernames)
// Target: https://api.github.com/repos/{owner}/{repo}/contributors

For Issue and PR count, respectively:
// https://api.github.com/search/issues?q=+author:{author}+repo:{owner}/{repo}+type:issue&order=asc&per_page=1&sort=created
// https://api.github.com/search/issues?q=+author:{author}+repo:{owner}/{repo}+type:pr   &order=asc&per_page=1&sort=created

It simply makes these connections via fetch+parse json. It doesn't make use of the RG token. Could I make use of it via using request options in fetch(), I mean like this: ?

click to expand:
https://github.com/sindresorhus/refined-github/blob/b504a42cd783836b979688731a43a0a07be65bf8/source/options.tsx#L50-L57

  I am asking, because I didn't find any such request options in other features.
Or, could these 3 requests be combined into one via GraphQL API? I am not familiar with it, but I think it's not possible.

It doesn't store the fetched data, i.e. repeats the requests on every new mouseover.

If you find this PR is too lengthy/unnecessary complicated/not salvageable, feel free to close it.

Thanks for the PR! Unfortunately it's quite long, as expected, and makes multiple requests, so I'll close this


Default unavailable_server_retry_responses

What does this PR (Pull Request) do?
This avoid warnings in Traffic Server logs by setting the default value explicitly
[May  7 18:48:34.899] Server {0x2b8caf4ddd40} WARNING: [ParentSelection] initializing UnavailableServerResponseCodes on line 2 to 503 default.
[May  7 18:48:34.899] Server {0x2b8caf4ddd40} WARNING: UnavailableServerResponseCodes - unavailable_server_retry_responses is null loading default 503 code.
[May  7 18:48:34.901] Server {0x2b8caf4ddd40} WARNING: [ParentSelection] initializing UnavailableServerResponseCodes on line 4 to 503 default.
[May  7 18:48:34.901] Server {0x2b8caf4ddd40} WARNING: UnavailableServerResponseCodes - unavailable_server_retry_responses is null loading default 503 cod

[x] This PR is not related to any Issue

Which Traffic Control components are affected by this PR?

Traffic Ops
Traffic Ops ORT
Documentation: Not required, just avoid a warning.

What is the best way to verify this PR?
Run ORT against Traffic Server and verify not warning or errors displayed in diags.log
The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3640/
Test PASSed.

@smalenfant wouldn't it be better to keep these error messages as an indicator that the configuration is missing? One could set up monitoring to look for this, which would allow them to reconfigure MSO accordingly. This seems like it's a little magical and someone might not realize that they're only failing over on 503s. Swallowing the error via forcing the default in TO gives the user no indication that they have an incomplete configuration.
Thoughts?

Yeah, I tend to agree here. :/ ATS is warning you that it loaded a default value. Setting a default here also means that you're not inheriting a new default if ATS ever changes it, which also seems bad. I think ATS is probably doing the right thing and we shouldn't generally suppress it. People already have several solutions to this problem: set their log parsers to ignore the message, set the value to 503 explicitly, and so on, depending on their exact goals.

I will add/keep the defaults to 503, this will match other parameters that have defaults.
I will put validation back in and modify as current validation requires quotes, quotes will be stripped. ATS DOES NOT requires the quotes.
Question. Should I add validation and warning about non 5xx codes?
In the end, I don't want to see those WARNINGs all the time. There was no warning in 5.3.2 and defaults were taken.

I think you should validate, ATS will reject anything other than 5xx codes and not load that config line.


Changes the structure of resolution packages

Description
Follow up from this discussion: moving things around in internal/resolution.
Before:
internal/resolution
├── entitysources
│   └── catalogdsource.go
├── resolver_test.go
└── variable_sources
    ├── bundlesanddependencies
    │   ├── bundles_and_dependencies.go
    │   └── bundles_and_dependencies_test.go
    ├── crdconstraints
    │   ├── crd_constraints.go
    │   └── crd_constraints_test.go
    ├── entity
    │   ├── bundle_entity.go
    │   └── bundle_entity_test.go
    ├── olm
    │   ├── olm.go
    │   └── olm_test.go
    ├── requiredpackage
    │   ├── required_package.go
    │   └── required_package_test.go
    └── util
        ├── predicates
        │   ├── predicates.go
        │   └── predicates_test.go
        └── sort
            ├── sort.go
            └── sort_test.go

11 directories, 16 files

After:
internal/resolution
├── entities
│   ├── bundle_entity.go
│   └── bundle_entity_test.go
├── entitysources
│   └── catalogdsource.go
├── resolver_test.go
├── util
│   ├── predicates
│   │   ├── predicates.go
│   │   └── predicates_test.go
│   └── sort
│       ├── sort.go
│       └── sort_test.go
├── variables
│   ├── bundle.go
│   ├── bundle_test.go
│   ├── required_package.go
│   ├── required_package_test.go
│   └── variables_test.go
└── variablesources
    ├── bundles_and_dependencies.go
    ├── bundles_and_dependencies_test.go
    ├── crd_constraints.go
    ├── crd_constraints_test.go
    ├── operator.go
    ├── operator_test.go
    ├── required_package.go
    ├── required_package_test.go
    └── variablesources_test.go

8 directories, 22 files

Reviewer Checklist

[ ] API Go Documentation
[ ] Tests: Unit Tests (and E2E Tests, if appropriate)
[ ] Comprehensive Commit Messages
[ ] Links to related GitHub Issue(s)

@everettraven there are no contstraints in variablesources (nothing which implements deppy.Constraint interface), but I agree that there is an opportunity to split variables and variable sources. I gave it a go in a separate commit. Please take another look.

To make sure I know what you're doing. There is a difference of 6 files (16 in the old tree, 22 in the new)
Unmoved: (2)

entitysources/catalogdsource.go
resolver_test.go

Moved: (12)

variable_sources/bundlesanddependencies/bundles_and_dependencies.go -> variablesource/bundles_and_dependencies.go (and _test.go)
variable_sources/crdconstraints/crd_constraints.go -> variablesource/crd_constraints.go (and _test.go)
variable_sources/entity/bundle_entity.go -> entities/bundle_entity.go (and _test.go)
variable_sources/olm/olm.go -> variablesources/operator.go (and _test.go)
variable_sources/util/... -> util/...

New (+4):

variables/variables_test.go
variablesources/variablesources_test.go
variables/bundle.go (and _test.go)

Split/copied?? (2 vs 4)

variable_sources/requiredpackage/required_package.go (and _test.go)

-> variables/required_package.go
-> variablesources/required_package.go

@tmshort Yes, I think your summary is mostly accurate apart from the variablesoruce/variable split (see 2f7f1480c00b0e6b0bf6833ceff08359f6b149cd).

variable_sources/crdconstraints/crd_constraints.go:

Variable ended up in variables/bundle.go (and _test.go for it)
Variable source in variablesource/crd_constraints.go (and _test.go for it)

variable_sources/bundlesanddependencies/bundles_and_dependencies.go:

Variable ended up in variables/bundle.go (and _test.go for it)
Variable source in variablesource/bundles_and_dependencies.go (and _test.go for it)

variable_sources/requiredpackage/required_package.go:

Variable ended up in variables/required_package.go (and _test.go for it)
Variable source in variablesources/required_package.go (and _test.go for it)

variables/variables_test.go and variablesources/variablesources_test.go are just to enable ginkgo tests. I suspect they will go away once we complete #189

Rebased to fix conflicts in internal/resolution/variablesources/bundles_and_dependencies.go and internal/resolution/variablesources/crd_constraints_test.go after merging #272.
Please take another look.


Fixes and enhancements to rolling fama-french regression

rolling_fama_french is actually more general, as one can also pass in their own risk-factors. I thus renamed the function (by default it will still load FF). While doing that I also found a couple of other problems that I fixed here.

Looks good - I'm not super familiar with how the performance attribution works, but this also computes an alpha. Is there any overlapping functionality between perf_attrib and here that we could combine?

OK, names should match up now.

@twiecki Ok, good to merge from my point of view, if you think this isn't an issue: https://github.com/quantopian/pyfolio/pull/444#discussion_r141683801


Storage Volume Created by Rancher is not in a good state

Steps:

add Rancher NFS infra catalog v0.0.3
In Rancher UI, choose a host and click Add Container for that host
fill out the volume tab with rancher-nfs driver and "test:/test" volume mount details
click create

results:

volume with name "test" shows up in storagepool with State="Requested"
click on the link of the volume, the resource lacks of "Update" action
from the plugin logs, I see the volume can’t be updated at create call. Errors:

From above steps, I suspect, the Rancher side created a half usable resource at the first stage during Add Container step, but it does not finishing up with mature resource.

Can you check ?

ibuildthecloud [4:41 PM]
what state was it in?

[4:42]
was it requested?

jimeng [4:42 PM]
yes

ibuildthecloud [4:42 PM]
okay, that's a bug

jimeng [4:42 PM]
This link does not have Update action, but it still has Create action and click on it, the resource state changes to inactive, then Docker plugin could update it during create call.

Tested with v1.2.0-pre4-rc9 and rancher/storage-nfs:v0.3.0.
"requested" state is not supported for volumes anymore.
When a volume gets created , its state is in "inactive" state now.
Once the volume is attached to container , its state gets to "active" state.
Volume is actually created in the nfs server.
When the volume is not attached to any container anymore , it gets to "inactive" state.
We have the ability to delete volumes in "inactive" state at which point they get removed from the nfs server.


fix(profile): update profile requx actions, types, and reducers naming and unit tests

Related Ticket(s)
Change profile endpoint on Carbon Masthead for signed in state #4701
Description
Update naming and unit tests from feedback: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/4909
Changelog
Changed

update getUserStatus action to loadUserStatus in accordance to naming strategy
create Unauthenticated const in ProfileAPI type
use request instead of status for the setRequestUserStatusInProgress and setUserStatus actions

Looking good so far, and the CI is passing! Thank you for making this change quickly @annawen1!

Looking good so far, and the CI is passing! Thank you for making this change quickly @annawen1!


[Snyk] Security upgrade com.google.inject:guice from 4.2.3 to 5.0.0

Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

pom.xml

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

489/1000  Why? Has a fix available, CVSS 5.5
Information Disclosure SNYK-JAVA-COMGOOGLEGUAVA-1015415
com.google.inject:guice:  4.2.3 -> 5.0.0
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

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

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

No longer required


explore using SRC_GEOLOC_ARRAY for external GCPS

ref: https://github.com/rasterio/rasterio/pull/2884

GEOLOC_ARRAY/SRC_GEOLOC_ARRAY=filename. (GDAL >= 3.5.2) Name of a GDAL dataset containing a geolocation array and associated metadata. This is an alternative to having geolocation information described in the GEOLOCATION metadata domain of the source dataset. The dataset specified may have a GEOLOCATION metadata domain containing appropriate metadata, however default values are assigned for all omitted items. X_BAND defaults to 1 and Y_BAND to 2, however the dataset must contain exactly 2 bands. PIXEL_OFFSET and LINE_OFFSET default to 0. PIXEL_STEP and LINE_STEP default to the ratio of the width/height of the source dataset divided by the with/height of the geolocation array. SRS defaults to the geolocation array dataset's spatial reference system if set, otherwise WGS84 is used. GEOREFERENCING_CONVENTION is selected from the main metadata domain if it is omitted from the GEOLOCATION domain, and if not available TOP_LEFT_CORNER is assigned as a default. If GEOLOC_ARRAY is set SRC_METHOD defaults to GEOLOC_ARRAY.

ref: https://gdal.org/api/gdal_alg.html

didn't work!


[BACKLOG-39104] ExcelWriter: missing repository save for createParentFolders

 Note:

Frogbot also supports Contextual Analysis, Secret Detection, IaC and SAST Vulnerabilities Scanning. This features are included as part of the JFrog Advanced Security package, which isn't enabled on your system.

🐸 JFrog Frogbot

:white_check_mark: Build finished in 31m 59s
Build command:
mvn clean verify -B -e -Daudit -amd -pl plugins/excel/core

:ok_hand: All tests passed!
Tests run: 117, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message

 Note:

Frogbot also supports Contextual Analysis, Secret Detection, IaC and SAST Vulnerabilities Scanning. This features are included as part of the JFrog Advanced Security package, which isn't enabled on your system.

🐸 JFrog Frogbot

:white_check_mark: Build finished in 16m 15s
Build command:
mvn clean verify -B -e -Daudit -amd -pl plugins/excel/core

:ok_hand: All tests passed!
Tests run: 117, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


Bundled type definitions are faulty

Initial checklist

[x] I read the support docs
[x] I read the contributing guide
[x] I agree to follow the code of conduct
[x] I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions: 4.0.0
Steps to reproduce
mkdir bug
cd bug
yarn init -y
yarn add typescript unist-util-position @types/unist
yarn tsc --init
echo "import { pointStart } from 'unist-util-position';" > index.ts
yarn tsc index.ts

Expected behavior
Compiles with no errors.
Actual behavior
$ yarn tsc index.ts
yarn run v1.22.4
$ /home/daniel/Projekte/bug/node_modules/.bin/tsc index.ts
node_modules/unist-util-position/index.d.ts:16:11 - error TS2304: Cannot find name 'type'.

16   export {type as displayName}
             ~~~~

Found 1 error.

thanks @d-fischer, released!


update license deps

Please validate that I don't break anything ;-)

Pff, something's wrong

Ok, was about to start reviewing ;-)

Pff, something's wrong

I don't see any changes that look problematic at first. What did you notice that's wrong?


Support of high DPI

Nana 1.8 will include the support of DPI feature. It automatically scales the fonts and UI elements which are layed out by place for current display DPI.
When DPI is changed, Nana adjusts the fonts and UI elements for best display.

Please download the develop-1.8 branch for trying this new feature, I am looking forward to your feedback/bug report.

Related issues: #184 , #378

Hi, @cnjinhao .
As you commented at https://github.com/cnjinhao/nana/issues/184#issuecomment-279116011, it seems DPI scaling feature has been added using the place class. I take my hat off to your efforts. Though I requested High DPI support in the past, I haven't contributed to the feature. so feel free to call me guilty.
To be honest, I still haven't tried layout management with that class, so this is a good opportunity to grasp its functionalities.
Anyways, the unit of size and position of widget system is still pixels (so as form class as it inherits widget_object). This probably makes it difficult for users to automatically adjust creation size and position according to DPI which can be varied per desktop environment.

Hi, @beru
Thanks for your feedback.

the unit of size and position of widget system is still pixels

Yes, it is. Because it is very difficult to implement the coordinate system to scale according to DPI, including redesign of class graphics and support of device-independent pixel unit.
The class place is very useful for DPI scaling.

Is this on develop already? I've been wondering, when I do a div like this: <weight=28 menu> is it correct? is it always forcing 28 pixels or will that 28 scale depending on the DPI and system font size?

It’s develop-1.8 already. all the values that indicate the space/distance  in div-text are depending on DPI. E.g.weight=28,gap=28, their pixels are 28 * DPI /96.
I am planning to add a fixed pixel unit for div-text, like this <weight=28px>


AWS Tile Resolution

After sampling the AWS public dataset skadi files, it appears that the resolution is 30m.   Is there a source that is 10m or better?

The documentation shows where the resolution is better as image and as geojson coverage file.

On Jul 20, 2018, at 12:26, Seth Fitzsimmons<EMAIL_ADDRESS>wrote:
Skadi will always be 30m, since they're effectively SRTM HGT files (the format supports only 30m and 15m data).
All of the other formats will have better resolution (but not everywhere, depending on underlying source availability).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


G9MG

Key
Value

View
https://database.shabados.com/line/G9MG

Source
Sri Dasam Granth

Page
5

ID
G9MG

Line
ck® bk® iPrY cqur ck mwnhI pur qIn ]82]

c`k® b`k® c`k
Nitnem Gutka - May 2017 - SGPC, Sri Amritsar

#95
One of the adhaks creates an imbalance. Chand is of 24 beats, 3 added adhaks make the pankti 25 beats.


Update BoltCard Extension README

Why was the readme updated from wiping using a json (QRed or copy pasted) to copy paste manualy every single key?

Hey Gene, If cards are written wrong fromon the beginning (e.g. only key3+4) it didnt work for Darth. This works always. If you feel it should be in as well we can add the former text ?

Maybe I'm missing something, but in the present readme there are described the same steps that happens when the key json is scanned/pasted. Presuming there's a typo in the last number in repeat with Key1/Key2/Key3/Key0 where should be 4? So I just don't see how would there be a different outcome.

With the json all are updated at once, maybe thats why ? You´re right shoult be 4 in the end, lets then just add both ways and everyone is fine :)


production installer: Add server script to sign up for push notifications.

Currently, in order to sign up for push notifications, server admins have to email a support address and wait for someone to service the request. It would be better for everyone to make this more automatic.
The task is to add a script scripts/setup/register-server that sends the EXTERNAL_HOST, ZULIP_ADMINISTRATOR, zulip_org_id, and zulip_org_key to an endpoint on zulipchat.com (like /remotes/register).
I would structure the script so that the transcript of an interaction looks something like:
This script will register your server with the Zulip push notification bouncer service.
You can read more about the service at
    http://zulip.readthedocs.io/en/latest/prod-mobile-push-notifications.html.

Hostname (EXTERNAL_HOST): xxx
Contact email (ZULIP_ADMINISTRATOR): xxx
Is the information above correct? We recommend using an email address
like ops@ that will outlast changes in personnel. [Y/n]

Would you like to sign up for the zulip-announce mailing list?
Used for new releases, security advisories, updates to the
terms of service, etc. (~1 email/mo.) [Y/n]

Use of the bouncer is subject to the Zulip Terms of Service at https://zulipchat.com/terms/.
Do you agree to those terms? [Y/n]

Registering server ...
Server successfully registered.

See http://zulip.readthedocs.io/en/latest/prod-mobile-push-notifications.html
for instructions on how to enable and test mobile notifications on your server.

And various error situations:

At the beginning, check if they have the four things set to non-default values, and if they don't print an appropriate error message, like: "Please set EXTERNAL_HOST in /etc/zulip/settings.py.", or "Please run scripts/setup/generate_secrets.py first."
The backend route should return success, or failure if either the zulip_org_id or hostname already has an entry. In that case we can print "Server already registered. Please email<EMAIL_ADDRESS>to update registration information."

@zulipbot claim

@alirizwi what's your status on this?

Is this issue still being worked on?


MQTT message on camera error

The Problem:
Many professional camera systems have a feature that sends out some kind of alarm if the video feed of one or more cameras is lost.
Sadly i couldnt find a way to activate something like this feature in camera UI.
I have a camera that randomly drops out of the wifi, needing to be restartet. That would be easily doable with a relay that is triggered by an MQTT error message send by camera UI.
The Request:
Is it possible to add a feature that sends an MQTT error message as soon as camera UI starts to display the "CAMERA OFFLINE" screen?
This would enable the automatic detection of camera problems and may even be usefull to detect cut wires like in professional installations.
I imagine that this shouldnt be too hard to implement as the Offline screen is already triggered by a missing video feed and MQTT is also already involved for motion detection.
I hope this is as easily possible as I think and that it can be implementet in the next version.

🎉 A new version of camera.ui
A new version of camera.ui is currently under active development. An initial alpha/beta release and previews are coming soon. Stay tuned for exciting updates: https://github.com/seydx/camera.ui/issues/448 .
This version will no longer be developed / fixed. The new version contains many novelties and fixes (most important is for HKSV recording).


Fixes 7094 - Replace "kubernetes_auth" with kubectl config view

Removed the deprecated “kubenetes_auth” command and replaced it with
the “kubectl config view” command (and corresponding example).

@RichieEscarez If you set your git configuration to use your @google.com email address it should help appease the CLA bot.

As discussed:

Delete the listing of the services.
Add an example for bearer token auth (either in this PR or a follow up PR)
Use kubtctl cluster-info

I had the git config --global user.email configured but the GIT_COMMITTER_EMAIL & GIT_AUTHOR_EMAIL environment variables were blank. Ive now set those as well, hopefully the CLA bot will accept my changes.

If that does not work I think we should bug @lavalamp who knows much about such things.

@satnam6502 I will deliver the discussed changes in a follow up PR.

I think we need help with the CLA. @lavalamp ?

@google account must be public on your github profile.

ICLA signed (requirement for Google contractors)


chore(release): beta v2.9.0-beta.3

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[x] 📦 Chore (Release)
[ ] ⏩ Revert

Description

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

Merging this to unblocked all other work.


[GLUTEN-6920][CORE][VL] New APIs and refactors to allow different backends / components to be registered and used

This is the major API layer change for #6920.
The PR introduces a new concept Component int Gluten and adjusts the role of current concept Backend.
After the change, Backend API will become a special variant of Component API. Details are as below:

Dependency

Component should have at least one parent. Each parent can either be another Component or Backend.
Backend doesn't have any parents.

Component and Backend instances are used as exactly the same manner in Gluten. Gluten treats them all as regular entities that inject custom code into Gluten.
Having Component's parents defined, Gluten will figure out a fixed order / priority of using the components. For exmaple:

A component's parent's loading APIs, namely onDriverStart / onExecutorStart, will be guaranteed to call EARLIER than the same APIs of the child.
A component's parent's rule injection API, namely injectRules, will be guaranteed to call LATER than the same API of the child.

For legacy reason, only one SubstraitBackend will be allowed to register at the same time. Which means, CH backend and Velox backend are still not allowed to load at the same time. When they are both loaded, error will be thrown. See code.

In subsequent PRs of #6920, we will:

Make iceberg / hudi / delta implement component API, remove the previous rule injection points used by their code.
Make uniffle / celeborn implement component API, remove the previous rule injection points by used their code.
Add an example backend that can work together with Velox backend.

Non-goals:

This doesn't tend to make Velox backend and CH backend work together.

Non-goals:
This doesn't tend to make Velox backend and CH backend work together.

This is for clarifying the non-goal of this pr or mixed backend work. According to #6920,  it seems making different backends co-work at runtime is the long-term goal. Just a bit confused.

Non-goals:
This doesn't tend to make Velox backend and CH backend work together.

This is for clarifying the non-goal of this pr or mixed backend work. According to #6920, it seems making different backends co-work at runtime is the long-term goal. Just a bit confused.

Good question, thanks.
Velox / CH may be possible to work together but it may require for considerable effort on refactoring. I am not sure whether any user is interested with this kind of combination now so I didn't intentionally put it as a goal for this PR (will make a note in issue #6920 too). I think we can choose to have another individual thread for VL+CH working together when it's proved to be worth to have our investment.

I am merging this. Let me know if any other questions @jackylee-ch
Thanks for you guys' review!


[UI] Tab Order

We need to go through and clean up the tab order for each widget, its pretty random and annoying atm

[ ] System Widget
[ ] Image Settings Widget
[ ] Movement Widget
[ ] Milling Widget
[ ] Hardware Settings
[ ] Manipulator Widget


ENH: CSS only sidebar toggling

This is updates our left sidebar behavior so that instead of using javascript functions to control the display of the left sidebar with a class, instead we use a CSS input box + :checked to toggle its visibility. This will make these pages a bit lighter and less-complex, and make them more robust if wonky things happen with javascript on the page.
It also implements Furo-style left sidebar behavior on mobile devices, so that the whole left sidebar pops up in an overlay and you close it by clicking elsewhere on the screen.
Old behavior
(shown on widescreen first, then mobile) (sorry for the red tint)

New behavior
Note that the left TOC closes automatically, because it will be hidden by default on pageload on mobile

Refs
closes https://github.com/executablebooks/sphinx-book-theme/issues/366
closes https://github.com/executablebooks/sphinx-book-theme/issues/355
closes https://github.com/executablebooks/jupyter-book/issues/1379
closes https://github.com/executablebooks/jupyter-book/issues/1361
closes https://github.com/executablebooks/jupyter-book/issues/950

Curious is @pradyunsg has any other suggestions here, or if this looks mostly reasonable to you :-)
cc also @AakashGfude since this restructures a little bit of the HTML


keep-alive doesn't work with @nuxt/device

Everything has been going well using module, but i noticed that the browser no longer caches my pages again (using fetch & keep-alive) when i use this module for dynamic layouts (like shown in the docs :
layout: (ctx) => ctx.isMobile ? "mobile" : "desktop").

This is intended behaviour @DanLowo, since the component is kept-alive, it won't call the layout property anymore.

This is intended behaviour @DanLowo, since the component is kept-alive, it won't call the layout property anymore.


Components are getting unmounted when route change.

Issue Type
[x] Question
Description
When route change using <Link> or browserHistory.push() every component get unmounted. I'm not sure if it is default behaviour.
But the problem is when i want to route to the same page, but bind param (e.g.from /user/ =>  /user?showModal=true). All component should not get unmount/remount... It won't unmount if it's under the same route.
Steps to reproduce

clone repository
add below code in HomePage/index.js

  componentWillUnmount() {
    alert(1);
  }

run server, and click Feature button.
You can see the alert box, imply that it's being unmounted.

every component get unmounted

I guess this is due to the code splitting. See mxstbr's post linked at top of routes file.

should be. Thank you :) @sedubois

I have the same behavior
On open first route i have
constructor
componentWillMount
componentDidMount
componentWillUnmount

constructor
componentWillMount
componentDidMount

componentWillReceiveProps

It's weird

Most likely it's a standard behavior (see https://github.com/ReactTraining/react-router/blob/master/docs/guides/ComponentLifecycle.md) unless you see WillUnmount while navigating and staying on the same route.


[BUG] Make DetailsView taller

Describe the bug
Now that there are more node parameters, the DetailsView should be taller, so fewer of them are hidden.

Fixed with https://github.com/Chowdhury-DSP/ChowMatrix/commit/ab7e81c433e08a33212e61d933a95b615099a56f

Fixed with https://github.com/Chowdhury-DSP/ChowMatrix/commit/ab7e81c433e08a33212e61d933a95b615099a56f


update the README to change pip [packages] to pip install [packages]

There is a typo in readme file: 'install' is omitted after pip.

Thank you!


issue #105 fixed and add Exception Handling logic for TrinityConfig

[YataoBot] Can one of the admins verify this patch?

@jiabaohan,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@jiabaohan good work, note that you don't have to close a PR and reopen it. After pushing your changes to your branch, it will be automatically appended to the currently active PR.

ok to test!


MudDataGrid: Fix CurrentPage not working (#7267)

Add default parameter to SetRowsPerPageAsync to allow pager to set rows per page without resetting CurrentPage to 0. New parameter is only passed in OnInitializedAsync in MudPagerComponent.
Description

How Has This Been Tested?

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

Also considered adding a SetCurrentPageAsync as currently the only way to set the CurrentPage is directly on a ref to the table and that gives a "BL0005: Component parameter should not be set outside of its component" warning. Happy to update if this would be a preferred approach to the optional parameter.

Hi.
This is kinda a breaking change.
When an optional parameter is added, compile-time compatibility is preserved, but not the binary compatibility is not.
To avoid this, I would suggest making an overload instead:
 public Task SetRowsPerPageAsync(int size) => SetRowsPerPageAsync(size, true);
+public async Task SetRowsPerPageAsync(int size, bool resetPage) {...}


How to use Keyboard module

Keyboard module is undefined in Android

import Keyboard from 'Keyboard';

is right but
import {Keyboard} from 'react-native';

is error

Maybe because Keyboard is not a module from react-native ?
What are you trying to do ?

The Keyboard module will be exported as expected in the upcoming 0.27.1 bugfix release. It's also already fixed in 0.28-rc.


Add search to docs

A site specific search would be a very useful addition to the monome docs.

@simonvanderveldt did a nice search on his jekyll site:
http://rennsportengineering.com/wiki/
https://github.com/rennsportengineering/wiki

Yeah, it's slightly problematic in that GitHub Pages/Jekyll are static sites, meaning there's no backed you can send search queries for.
So pretty much the only thing you can do is create an index which contains all the data/things you want to search for, probably in a JSON file, and then use that as the "backend" for the search.
This does mean that all this data needs to be downloaded/read by the browser so while it works for small sites it definitely doesn't for larger ones.
I don't know where the docs fall in this, we could try it out.
The site linked uses https://github.com/olivernn/lunr.js

I went ahead and forked the docs repo to play around with an mkdocs build. You can have a poke around that output here: https://aidanreilly.github.io/docs-test/ the actual markdown content is unchanged, so some of the page links are broken, however, the left hand 'site nav', and right hand 'page nav' should be working OK, or enough to get a feel for how mkdocs works. The search also works. Site search is powered by lunr.js
The site theme is material for mkdocs. https://squidfunk.github.io/mkdocs-material/
I'm not a developer, so further tinkering would be beyond me, not that I have the time either tbh.

edit links on every page could bring you to the source in github. Nice for collaborative edits and related work.
disqus plugin could also be enabled - this could draw users in with easy comments features on every page. Maybe there is a discourse plugin that could be leveraged for comments? that could be cool.

Anyway. I'll leave this up for a day or two, let me know what your thoughts are. If you're planning a custom route for the look and feel, or just further development on the current jekyll build that's cool.
:)
Off to bed now...

this is very impressive! i wasn't aware of mkdocs, thank you
i could see this working well with some styling and removal of some features.
wondering if it's possible to represent more of the doc hierarchy on the left (basically sub-files) or perhaps it's better design to have the ToC be for digging in.
curious to hear more feedback from others.

I've worked with mkdocs about 1.5 years ago, it was OKish back then, we dropped it in the end. Don't really remember the details.
What would be the advantage vs the current setup?
Anyway, it would mean a CI setup would need to be added to build the site automatically since it's not Jekyll.
If you like the styling it's probably easier to just use readthedocs and if you want custom styling and to fit it into the monome site I'd expect the current solution to be be easier.

edit links on every page could bring you to the source in github. Nice for collaborative edits and related updates work.

Hmm. Hadn't considered that a CI would be required for mkdocs. From a technical standpoint, I'm not sure there is a benefit tbh.  The out of the box navigation and search is what appeals to me. Perhaps just developing the nav and search for the jekyll build is the best approach as you say.  There is a tech doc theme for jekyll here which seems well featured: https://idratherbewriting.com/documentation-theme-jekyll/index.html the search is kind of goofy though.
this also looks good: https://aksakalli.github.io/jekyll-doc-theme/

ah. yes we need a jekyll solution--- i really don't want to add another CI layer.
just-the-docs looks good and would be a simple starting point for styling

i'll spin that up and see what it looks like.

@tehn Do you have any ideas/direction regarding styling of the docs?
How much should it match with the monome site?

@aidanreilly looks like a good start! the search works well.
interesting that there are a bunch of links missing on the sidebar. and there's no ToC?
@simonvanderveldt re: styling. it should follow the monome site (colors, face, etc) i think something close to the TT docs layout makes sense: https://monome.org/docs/modular/teletype/manual/
makethedocs had really good table format styling

@simonvanderveldt re: styling. it should follow the monome site (colors, face, etc) i think something close to the TT docs layout makes sense: https://monome.org/docs/modular/teletype/manual/

That looks pretty nice and very legible!
It seems to be an HTML page generated using pandoc. i guess we could look into getting the basic styling and sidebar layout and transplanting that on top of just-the-docs?

Re: page titles - this particular theme requires a title in the header for navigation. There’s probably an easy enough search and replace to duplicate the first occurrence h1 titles into the header for *.md. Child topics navigation would also need to be done.
There may be a Jekyll plug-in to make this easier, I’m not sure.
Aidan

On 16 Oct 2019, at 19:17, brian crabtree<EMAIL_ADDRESS>wrote:

styling/formatting is easy to change as long as the core functionality we want is there (sidebar pages, ToC, search)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I was independently drafting some visual ideas for the fresh docs today, and was notified of this existing thread by @tehn -- hope I'm not stepping on any toes. I'm no web developer (I just have some basic css chops), but I do love design -- happy to help in any way I can.
Here's a basic side navigation layout I put together today (similar to work I did on the TT web manual), using crow as a lens to organize it:
https://monome-docs-nav.glitch.me/
And a couple of mobile-friendly versions too, where the nav shifts to the top of the content, and becomes sticky + collapsible:

Olivier, these look really nice! Have you looked at the sample site i linked above? I think we could incorporate these ideas easily enough. I'm not a web developer either though, but i do enjoy hacking at these things.
@tehn @simonvanderveldt - need to decide if we are going to proceed with this just-ther-docs theme. If we do, then we'll need to build a navigation for each and every markdown file. Not a difficult task, but probably time consuming. See here for detail: https://pmarsceill.github.io/just-the-docs/docs/navigation-structure/
Basically, the current docs implementation uses hardcoded links at the top of every topic to provide the navigation. lofi, but it works. If we want a right hand nav, then we'll need to do a bit more to  include the nav items. Different jekyll themes probably approach this in dfferent ways. This just-the-docs method is probably as advanced as any other jekyll theme that i've seen.
Open to suggestion/direction on how to proceed. I think we'll need to decide on a jekyll framework/theme, and then work to retrofit the content into that theme.

I'm not sure I understand the question entirely, but I'll respond with another question :stuck_out_tongue:
Do we want the in page navigation to be in the sidebar as well or should it be at the top of the page itself?

oh you mean we need some requirements? :)

regarding my previous post, this is an example of the kind of header info we need per markdown file to provide a nav with this theme:

this is what is present in the doc files right now:

Not a complicated thing to fix, but time consuming.

I admit to being relatively ignorant of technical constraints (though of course I want to learn!), but I think a nice model would be for the side nav to change depending on the context so that it's more useful.
In essence, the /docs index would remain the same (perhaps just a light re-design would do), and then the side navigation would become available once you've jumped to a specific category from there (crow/norns/etc.) -- basically, the nav then functions as a ToC, since in that proposed model, all crow docs (for example) would be aggregated in a single page.
Curious to hear thoughts, pros/cons. I'll start mapping some examples out for easier discussion, and if it's easier to move design talk to a different issue here, I'm happy to open it.

@oliviercreurer https://github.com/monome/docs/issues/164

it's confusing to have two issues about the same redesign so i'm going to say we merge this discussion with https://github.com/monome/docs/issues/164


Portal does not work in some browsers

In some browsers, the developers portal does not work. Navigating around gives blank page for any URL until hard refresh clearing local cache. Clicking on any link again goes to blank page.
Observed on Mac:

Brave - Version 0.70.122 Chromium: 78.0.3904.87 (Official Build) (64-bit) and newer.  (reported by @vojtechsimetka , works in chrome though) Error:

Chrome - Version 78.0.3904.108 (Official Build) (64-bit) and newer (reported by @auhau). Error:

This seems to be related to the previous devportal being cached in your browser. We've investigated and the previous portal used a webjob which is still running in your browser. Navigate to: chrome://serviceworker-internals/
And stop the worker associated to the old devportal.