Implement custom Authorizing page/layout/template in TodoTemplate

The default Authorizing template of TodoTemplate which is displayed during the user authorizing by system only displays a simple  message and it is little boring, not beautiful and not well recognizable

Let's call this authorizing phase
Additional info:
I'd prefer not to tell the user about something that she can't understand.
A loading view that indicates app is loading would be enough
Note that this view is especially helpful for blazor hybrid where this step took a little bit longer
There is also another step that needs a loading indicator (while non pre-rendered blazor web assembly or blazor hybrid are being loaded). Let's call this initializing phase
The main difference between initializing and authorizing phases is that in initializing phase, we don't have access to blazor components while in authorizing phase we can use all blazor features.
I'd prefer to create something blazor independent (like the progress bar that we've in PWA mode) so we can use that in both scenarios.
@msynk @maryamhdr

@ysmoradi
good points. let's discuss these further and submit separate issues if required.


add: added $client[prefix]

I know this is a ridiculous pull request, but I think it's a necessary function.

ok

this code won't work if I were to set my prefix as
prefix:"."


Progress Indicator in UploadStreamToBlockBlobOptions

Which version of the SDK was used?
Latest
Which platform are you using? (ex: Windows, Linux, Debian)
Linux Ubuntu 19.04
What problem was encountered?
Feature Request - I'm trying to upload large files to Blob Storage and the best way to do that is using streams. It would be very useful to show the user a progress indicator. Unfortunately the UploadStreamToBlockBlobOptions does not support a progress callback / function.
How can we reproduce the problem in the simplest way?
Feature Request
Have you found a mitigation/solution?
No

Actually, you can do this now by wrapping the steam with a RequestBodyProgress stream. See https://godoc.org/github.com/Azure/azure-storage-blob-go/azblob#example-package--ProgressUploadDownload for an example.

Jeffrey Richter (watch Architecting Distributed Cloud Appshttps://azure.microsoft.com/training/distributed-cloud-apps/)

From: Shekhar Patnaik<EMAIL_ADDRESS>Sent: Tuesday, August 6, 2019 11:26 PM
To: Azure/azure-storage-blob-go
Cc: Subscribed
Subject: [Azure/azure-storage-blob-go] Progress Indicator in UploadStreamToBlockBlobOptions (#143)
Which version of the SDK was used?
Latest
Which platform are you using? (ex: Windows, Linux, Debian)
Linux Ubuntu 19.04
What problem was encountered?
Feature Request - I'm trying to upload large files to Blob Storage and the best way to do that is using streams. It would be very useful to show the user a progress indicator. Unfortunately the UploadStreamToBlockBlobOptions does not support a progress callback / function.
How can we reproduce the problem in the simplest way?
Feature Request
Have you found a mitigation/solution?
No
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-storage-blob-go/issues/143?email_source=notifications&email_token=AARLJP5ETJOQZ6MOPSG7Q3DQDJTILA5CNFSM4IJ4ZUAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HDZS4IQ, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AARLJP3N5VPVRJ7HREPIRJLQDJTILANCNFSM4IJ4ZUAA.

Thanks @JeffreyRichter - is Upload() the preferred way to upload streams instead of using UploadStreamToBlockBlob. Some of the other SDKS such as Nodejs (https://docs.microsoft.com/en-us/javascript/api/@azure/storage-blob/iuploadtoblockbloboptions?view=azure-node-preview) allow you to pass a progress callback to uploadStreamToBlockBlob()

For Go, progress is accomplished by wrapping any steam with the progress steam. The Upload
Function uploads a steam to a blob the max side is 250MB (if I remember correctly- PUT BLOB rest API). UploadStreamToBlockBlob will upload a steam that is much larger by breaking it into blocks and uploading each block. Also, Upload Steam to block blob does not require the steam to be seekable and so it can used by network-backed steams. Upload requires that the steam be seekable (like for memory buffers or files).
Upload is more efficient
Node doesn't have streams, so it is done differently.

Jeffrey Richter (watch Architecting Distributed Cloud Appshttps://azure.microsoft.com/training/distributed-cloud-apps/)

From: Shekhar Patnaik<EMAIL_ADDRESS>Sent: Wednesday, August 7, 2019 11:01 AM
To: Azure/azure-storage-blob-go
Cc: Jeffrey Richter; Mention
Subject: Re: [Azure/azure-storage-blob-go] Progress Indicator in UploadStreamToBlockBlobOptions (#143)
Thanks @JeffreyRichterhttps://github.com/JeffreyRichter - is Upload() the preferred way to upload streams instead of using UploadStreamToBlockBlob. Some of the other SDKS such as Nodejs (https://docs.microsoft.com/en-us/javascript/api/@azure/storage-blob/iuploadtoblockbloboptions?view=azure-node-preview) allow you to pass a progress callback to uploadStreamToBlockBlob()
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-storage-blob-go/issues/143?email_source=notifications&email_token=AARLJPZBNX2ECZ3ZACJ2C73QDMEW3A5CNFSM4IJ4ZUAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3ZHMBA#issuecomment-519206404, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AARLJP4GB2HOBESYAENANE3QDMEW3ANCNFSM4IJ4ZUAA.

Thanks @JeffreyRichter that works for me!


Bug when using NPM install

@dvlden , get this error message when running npm install.
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No repository field.
npm ERR! Linux 4.8.0-53-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR<EMAIL_ADDRESS>install: `node ./bin/install.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node ./bin/install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the husky package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./bin/install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs husky
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls husky
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/colin/Desktop/programs/simple.css/npm-debug.log

The contributors most likely able to help are:
@cpdevelops

So weird... Works fine when I run npm install. I removed package-lock.json, installed dependencies and pushed new package-lock.json. Maybe that solves your issue?

Used new package-lock.json and I get the same error @dvlden

This part of their documentation says that it logs all the node_modules it installs to make it so that modules aren't installed twice, metadata isn't duplicated, etc.

Could you send your npm logs file on gitter maybe? Remove the log file first, then init npm install then send me log.
Might be your env setup too.

Just sent it @dvlden


State of the cell is unclear

I noticed when I remove lines and ctrl+enter (iterate), it still appears to have the previous commands in effect.
This is very confusing and results in situations where I've after I've refactored, I don't have a working gnuplot.
https://s.natalian.org/2020-07-10/removing-lines.mp4
Any tips please?

See %reset, %%reset (magics) and the reset (gnuplot command) in the example
notebook
https://github.com/has2k1/gnuplot_kernel/blob/master/examples/gnuplot-kernel.ipynb
In this case just end the cell with the 'reset' command. This is just like
using gnuplot on the command line were you either unset specific settings
of reset all plot specific settings at once,
http://www.bersch.net/gnuplot-doc/reset.html.
On Fri., Jul. 10, 2020, 10:06 a.m. Kai Hendry<EMAIL_ADDRESS>wrote:

I noticed when I remove lines and ctrl+enter (iterate), it still appears
to have the previous commands in effect.
This is very confusing and results in situations where I've after I've
refactored, I don't have a working gnuplot.
https://s.natalian.org/2020-07-10/removing-lines.mp4
Any tips please?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/has2k1/gnuplot_kernel/issues/25, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAF6QNNGTIBECBXGPMQHIM3R224XTANCNFSM4OWJZEKA
.

Thank you https://s.natalian.org/2020-07-11/concern.mp4
Still find it a little confusing, but I think this is just the way Jupyter Notebook works

I'm still very confused by the https://s.natalian.org/2020-07-11/reset.mp4 logic...

Forget about %reset and %%reset.
Use 'reset' (no percent signs), the gnuplot command.
On Sat., Jul. 11, 2020, 6:39 a.m. Kai Hendry<EMAIL_ADDRESS>wrote:

Reopened #25 https://github.com/has2k1/gnuplot_kernel/issues/25.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/has2k1/gnuplot_kernel/issues/25#event-3535938596, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAF6QNNUJU3XFSXRYEN47B3R27NHJANCNFSM4OWJZEKA
.

Ok, that appears to work. Though darn, quite easy to get into a bad state.

Found it doesn't work for set colors..
https://s.natalian.org/2020-07-11/reset-color.mp4


[UAVCAN/CAN] for Arduino

Following up on my comment here I'm wondering about what's the best way to achieve this? There is currently no top-level <CAN.h> in the Arduino environment as there is for UART (<Serial.h>), I2C (<Wire.h>) and SPI (<SPI.h>). However, I could rather quickly donate a working Arduino Library intended for interacting with the (old but popular) MCP2515 CAN communication chip. But how should the folder structure be set up?
arduino
|-- libcanard
   |-- arduino (for eventual top-level CAN support?)
   |-- mcp2515

What do you think @pavel-kirienko ?

I am beginning to think that the libcanard subdirectory might a bit of a misnomer in some cases because, for example, the bxCAN driver contributed by TomDeRybel is completely decoupled from Libcanard -- it is very generic and can be used in a completely standalone application (or even with libuavcan, perhaps, although it would require some serious bolting-on). Maybe in such cases, we should say generic instead of libcanard or something else? Or would that introduce confusion?
But anyway, following the currently practiced approach, I think just arduino/libcanard/mcp2515 should be fine.

Are submodules in order too? Then I could just relicense 107-Arduino-MCP2515 to MIT and link it in. The library was written with being used with libcanard in mind, I could add an example demonstrating how to use the library in the presence of the libcanard defined types. What do you think? (A submodule has the added benefit that I need to fix issues only in one place).

That question made me realize something.
The code we keep here is not an actual product by itself, it is rather a pile of useful things that one can ruffle through in search of anything reusable. Meaning that this repository is never supposed to become part of anything wholesale. Embedding a library as a submodule amounts to just using this repository as a collection of references to external components intended to serve the same purpose. Continuing this line of thought I notice that it is just like adding a section "See Also" in the README pointing to various parts and components of the same nature.
I mean, adding a submodule makes sense if it is actually used for one of the drivers or test suites that are stored here, such as the case with libcanard that is submoduled to be used for building the unit tests for the SocketCAN driver. But if the submodule is a driver itself, then why have it, should we not just list the original repo in the docs?

I agree with you that this repository really starts to resemble a collection of useful code pieces and it might therefore be useful to just link towards the original repositories. As I see it, there's one small advantage of including submodules as opposed to linking to the original driver repository: If the original repository is deleted or turned private your link will point nowhere. Having the foreing repository included as submodule guarantees that you'll always have at least one copy at hand.

Having the foreing repository included as submodule guarantees that you'll always have at least one copy at hand.

That's not how submodules work. A submodule is just a link maintained and used by git, so when the origin is gone, it's dead. :skull_and_crossbones: You probably are talking about git-subtree.
So which one do you prefer: git-subtree or a new section in the README? Or something else maybe.

Tbh I didn't know that about submodules. git-subtree looks like the way to go to me, although I've not used them myself yet.

Subtree it is then.

Hi @pavel-kirienko :wave: I've completed everything - You can git-tree-away using https://github.com/107-systems/107-Arduino-MCP2515 master:head.

I thought your preference would be to use subtree. If you are inclined to leave it to me, I think it's more sensible to add a See Also section in the README. Even if the link rots away one day, it will still be possible to find the project by its name online.

I think that git-tree is the sensible solution from a future-proof POV, however I would have left the git-tree implementation to you. Really, we can do what-ever floats your boat. I'm between submodules because it's kind of elegant and git-trees because it keeps one copy safe. The one thing I don't really like is the link approach. If you look into a repository you want to see code imho.

Just seeing that I mistyped above, I meant git subtree of course. :facepalm:


Tests for History Manager

Adds tests for history_manager and extra logging in the history_manager. Tox config modified to allow application logging to show while running pytests.

@DavidXArnold if you have time this week to look through this PR, it's some additional tests and logging for the history_manager.

:+1:


Update ActiveMQ documentation

Purpose of this pull request
Update ActiveMQ documentation, Changes related to Helm Chart v3
Issue number: https://jira.kumoroku.com/jira/browse/SUMO-206934

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[x] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

Can we also save the draw.io sources for these diagrams in this repo somewhere? WDYT @kimsauce ?

It looks like @kkujawa-sumo did save this image to the repo: https://github.com/SumoLogic/sumologic-documentation/pull/1731/files

Can we also save the draw.io sources for these diagrams in this repo somewhere? WDYT @kimsauce ?

Yes, it is good idea,  I had a doubt where to add sources from draw.io.
I'll start adding them in same place where original pictures, with the same name but different extension.


Troubleshooting command badly formated

There is a problem on the README, Troubleshooting command is not rendered.

Hi @mxjeff, can you post a screenshot of what you're seeing?  It looks fine to me rendered on Github.  I'm not concerned with the rendering on PyPI, which is a very poor UX for maintainers.

Here what I see on firefox 60.6.3esr on Debian buster:

It looks like language type is not defined in rst source, but adding :: shell does not even seems to fix it, don't know what's happening here.

Ahh, I see what you mean now, thank you.

Tada:


Fixup JSON schemas

[x] Put required at the same level as properties, not under it.
[x] Put properties definitions under properties.
[x] Put regexps for validating IPv4 and IPv6 addresses.

I'm half-tempted to say we shouldn't validate IP addresses in the JSON schema, because the regexps are simply too awful.

Ping?

@DeviaVir @RyanSquared @singlerider Any of you would have time to review this?

@KellerFuchs sure thing, not sure how useful my opinion on this is though. What would validating the IPv4/IPv6 at this location give us vs. not doing it?
Code LGTM though.

@DeviaVir Basically, enforcing the IP format there means that we enforce that we have valid IP addresses at all points (API client, API server, database).
It doesn't enforce that the IP addresses are the right ones, of course.


Minification fixes/improvements

Some closure-related fixes/improvements:

pass --strict_mode_input false, closes openfl/openfl#1827

pass --source_map_location_mapping "/|file:///", which causes paths to be prefixed by file:// (similarly to the haxe-generated .js.map) so that the debugger can find them.

Even when closure creates a .js.map, it does not add a //# sourceMappingURL to the .js file! We do it ourselves so that the debugger can find it.

Haxe can generate source maps for -final builds using -Djs-souce.map, but minification discards them cause it is triggered by debug || source-map. I changed the condition to <souce.js.map exists> || source-map which is simpler.

With the above changes debugging a minified app in chrome dev tools works pretty well.

Perfect 👍


Change default realname to not advertise ZNC

Right now ZNC will use the string "ZNC - http://znc.in" as realname if the user hasn't set one. Unfortunately this makes it difficult for other clients to figure out whether the realname is meaningful or not. Clients who want to display the realname need to resort to deny-lists to avoid showing the default realname.
A widely implemented practice is to set the realname to the nickname if the user hasn't set a custom one. This allows other clients to easily figure out the "no custom realname" case without resorting to hacks.
Would you accept a patch to implement this behavior in ZNC?
Apologies if this has already been discussed. I haven't found any past issue about it.
Ref https://github.com/znc/znc/issues/818 which AFAIK was the last time the realname was changed.

If you're compiling ZNC from source, you can always change this line from m_sRealName(""), to m_sRealName(m_sCleanUsername + " using ZNC"), and this will use the set the default realname as something like PeGaSUS using ZNC.
This is a little hacky but can be used until someone submits a patch to ZNC or the team changes it.
Cheers


Do you have faces for 2048.xyz? Or it just have no faces information

Hi,
We don't have the face information since we only focus on the point cloud processing. If you need a corresponding mesh, I‘d suggest to first correct a ball mesh and sample 2048 points on it uniformly using open3d.

Thanks for your reply,
Actually i already done this， i obtain a mesh with o3d.geometry.TriangleMesh.create_from_point_cloud_XXXX(all 3 meshtods), and get a water tight mesh from 2048.xyz, it seems okay when the point cloud is a ball, but when i apply this faces information to the output of the 3DAttriflow, such as airplane or bench, the mesh is fully of  sharp corners, i have shown this in my repo, and the raw file also here.  I wonder if this might be caused by the incorrect information of faces generated by o3d randomly? Or others?

Hi,
It's a big challenge to extract faces directly from point clouds, so it's normal that o3d failed to reconstruct complex shapes. There are a lot of works trying to reconstruct surfaces from point clouds, but we don't focus on that since 3DAttri is designed for the task of point cloud generation.

Hi,
It's a big challenge to extract faces directly from point clouds, so it's normal that o3d failed to reconstruct complex shapes. There are a lot of works trying to reconstruct surfaces from point clouds, but we don't focus on that since 3DAttri is designed for the task of point cloud generation.

okay, thanks a lot


Split the pong guide into more code pieces

@jonatanklosko, I still need to revisit the text, so ignore any text changes for now, but you can review the code for feedback! :)

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Transaction tree

This PR marks the beginning of storing transactions as a directed graph instead of an array. Additionally, it exposes an API for controlling history.

@efatsi If you care to take a gander again. I realized that there is no reason to keep track of a nodes list in Graph. Instead, I just keep track of edges. Also, I added a tree method to make it easier to generate output.

Oh yeah, and it's muuuuch faster:
~/Development/microcosm transaction-tree
●° node bench/pathway.js
Creating a single path at 1000000 length
Appending: 346.94ms
Pathway: 107.792ms

This is really neat. two questions:

What are the memory implications of this change?
Do you have a sense of real use case where one would want to switch between change branches on the history tree?

@ltk
What are the memory implications of this change
Before this change, we stored transactions in an array. Now they are kept in an array of two element arrays. The default cleanup strategy is to merge all completed transactions. That is to say, all actions that return primitive values, resolved promises, and fully iterated generators.
This graph will not create an edge unless there are two transactions to join together. Using the default cleanup strategy, edges are never created and the penalty is never encountered
For cleanup strategies that support history, it'll assign an array for each edge. However it only stores the transaction, not the final state. This means that space is limited to the payload of the action. Framework memory usage should be rather low, the bottleneck would really be a matter of the size of the action payloads.
I could see a future where we have finer grained undo, where we can merge together complete transactions in the middle of history. That would allow for even more powerful undo; we just aren't there yet.
So, TL;DR; I don't think it's an issue. Certainly for existing apps, there should be no effect at all. For other use cases, I am curious if there is a more optimal way to do it. However I think it's pretty good now, and the only other alternative I can think of would be to redefine the Transaction class as a node in a trie. This implementation keeps them separate, which I like.
Do you have a sense of real use case where one would want to switch between change branches on the history tree?
The specific use case I am thinking of is the ability to compare two on going changes side by side in Colonel Kurtz. Let's say you have a page, but you want to change the hero graphic. You aren't sure which one you like better, so you toggle between the two trees to preview what they look like (this is assuming we add live preview eventually)

Nice :+1: all the way.

Well I just bumped into an issue. I should have thought of this earlier, but restructuring the graph as a tree for visualization bumps into maximum call stack territory on deep chains. Unfortunately we can't lean on tail call optimization either.
This should probably be envisioned as a tree.

Someone else should look at this, but :+1:

Thanks, everyone. I'm going to close this out. Tree recursion issues is a complete show stopper. I've got an outstanding branch that eliminates this by maintaining a tree structure on insertion (instead of now where it's determined via recursion as a public API).
More to come! Benchmarks are already super promising:
●° node --expose-gc benchmarks/pathway.js
Working.............
┌──────────┬─────────┬──────────┬───────┬───────┬────────┬────────┬───────────────┐
│ Branches │ Nodes   │ Append   │ Path  │ Root  │ Values │ Prune* │ Memory Growth │
├──────────┼─────────┼──────────┼───────┼───────┼────────┼────────┼───────────────┤
│ 1        │ 100,000 │ 0.0004ms │ 6.6ms │ 3.2ms │ 6.8ms  │ 22.6ms │ 0.29%         │
├──────────┼─────────┼──────────┼───────┼───────┼────────┼────────┼───────────────┤
│ 2        │ 50,000  │ 0.0007ms │ 4.0ms │ 1.2ms │ 4.2ms  │ 19.1ms │ -9.07%        │
├──────────┼─────────┼──────────┼───────┼───────┼────────┼────────┼───────────────┤
│ 3        │ 33,333  │ 0.0011ms │ 5.3ms │ 1.2ms │ 5.2ms  │ 20.0ms │ 0.18%         │
├──────────┼─────────┼──────────┼───────┼───────┼────────┼────────┼───────────────┤
│ 4        │ 25,000  │ 0.0014ms │ 4.4ms │ 1.1ms │ 4.6ms  │ 20.3ms │ 0.19%         │
├──────────┼─────────┼──────────┼───────┼───────┼────────┼────────┼───────────────┤
│ 5        │ 20,000  │ 0.0017ms │ 5.3ms │ 1.1ms │ 4.5ms  │ 23.4ms │ 0.17%         │
├──────────┼─────────┼──────────┼───────┼───────┼────────┼────────┼───────────────┤
│ 6        │ 16,666  │ 0.0022ms │ 5.5ms │ 1.5ms │ 4.5ms  │ 22.4ms │ 0.17%         │
├──────────┼─────────┼──────────┼───────┼───────┼────────┼────────┼───────────────┤
│ 7        │ 14,285  │ 0.0026ms │ 4.4ms │ 1.1ms │ 5.4ms  │ 23.0ms │ 0.17%         │
├──────────┼─────────┼──────────┼───────┼───────┼────────┼────────┼───────────────┤
│ 8        │ 12,500  │ 0.0029ms │ 5.3ms │ 1.1ms │ 6.5ms  │ 21.7ms │ 0.17%         │
├──────────┼─────────┼──────────┼───────┼───────┼────────┼────────┼───────────────┤
│ 9        │ 11,111  │ 0.0034ms │ 4.4ms │ 1.3ms │ 4.5ms  │ 20.3ms │ 0.17%         │
├──────────┼─────────┼──────────┼───────┼───────┼────────┼────────┼───────────────┤
│ 10       │ 10,000  │ 0.0038ms │ 5.7ms │ 1.2ms │ 4.5ms  │ 20.2ms │ 0.17%         │
└──────────┴─────────┴──────────┴───────┴───────┴────────┴────────┴───────────────┘
 * for entire branch


[csrng] Implement V2S tests

[x] Map as many CMs to common tests or FPV as possible.
[ ] For the remaining CMs, extend existing tests or write new tests.

estimate 32
remaining 2022-11-10 30
remaining 2022-11-11 28
remaining 2022-11-11 24
remaining 2022-11-14 23
remaining 2022-11-14 21
remaining 2022-11-14 17

I've started reviewing the test plans, tests and countermeasures to see what CMs are tested how and what needs to be done. It looks like quite some work is waiting here. We might however borrow ideas and code from entropy_src and AES DV.

Based on #16251, there is quite some work to be done. In particular we need (for details check out the testplan):

[ ] CONFIG.REGWEN: Add a directed test to verify CTRL and ERR_CODE_TEST cannot be modified unless REGWEN is high. This is a task for @vrozic who did the same for entropy_src
[ ] CONFIG.MUBI: Check that the recoverable alert actually fires.
[ ] INTERSIG.MUBI: Drive also False values and extend the testbench to support non-valid encodings. This is a task for @andreaskurth who did the same for entropy_src
[ ] DRBG_UPD.CTR.REDUN + DRBG_GEN.CTR.REDUN: We need to extend the csrng_intr and csrng_err to also fault these counters. Currently they only test GEN_CMD.CTR.REDUN. -> @marnovandermaas ?
[ ] CTRL.MUBI: Need to extend csrng_alert to also cover this similarly to CONFIG.MUBI -> @ctopal ?
[ ] MAIN_SM.CTR.LOCAL_ESC: Need to check that the main FSM enters a terminal error state upon faulting any counter.
[ ] CONSTANTS.LC_GATED: Need to extend the environment to drive non-valid MUBI encodings -> @andreaskurth
[ ] SW_GENBITS.BUS.CONSISTENCY: Need to extend csrng_alert to actually verify that the alert fires, not just checking the RECOV_ALERT_STS register.
[ ] AES_CIPHER.... Various CMs inside the AES cipher core are not tested inside CSRNG. They are however tested as part of AES. Let's not worry about these right now.

INTERSIG.MUBI and CONSTANTS.LC_GATED are covered by https://github.com/lowRISC/opentitan/pull/16310; I'll next address MAIN_SM.CTR.LOCAL_ESC.

I created a draft PR #16316 to address CONFIG.REGWEN

I've pushed a PR to verify CTRL.MUBI here: #16344
Also, I've updated the remaining efforts in the first comments. Thanks everybody for having provided updates and of course PRs ;-)

At the moment, all CM are verified as part of CSRNG except for the ones inside the AES core. These have already been verified at the AES block level. For now I am unassigning everyone. Tomorrow it will be deciced how we move forward with this.


chore(CRT-1372): update dependencies due vulnerabilities

Fixes CRT-1372

badger

badger secureDependencies

Badges for quill

Current level: 1/2
Description: assess the repository's dependencies from a security point of view

Level-up recommendations

You are in this level because the repo has one or more vulnerable dependencies that should be fixed.
Recommendations:

The vulnerable dependency has a fix available, a Snyk Priority Score of 700 or more, and it was identified by Snyk more than 20 days ago +More info

Do you have any feedback on the Badger app? Please fill out this typeform

badger secureDependencies

Badges for quill

Current level: 1/2
Description: assess the repository's dependencies from a security point of view

Level-up recommendations

You are in this level because the repo has one or more vulnerable dependencies that should be fixed.
Recommendations:

The vulnerable dependency has a fix available, a Snyk Priority Score of 700 or more, and it was identified by Snyk more than 20 days ago +More info

Do you have any feedback on the Badger app? Please fill out this typeform


added C++ hello world

In this pull request, I have added the hello world in c++ language.

@reveurguy Sir, Please review my PR and merge it. also please add the hactoberfest-accepted label.

Thanks! Make sure to give the repository a star and share about it as well! You can tweet about the repository as well using the tweet badge on the Readme file or website!


[Feature]: Image links to npm and taqueria plugins in /plugin-XX readme.md

Describe the feature you would like
Each of the plugin folders should include npm and taqueria links to the plugin in the readme.md

Is this feature solving a problem?
Details about the problem your feature solves
Please share any additional details you have?
See hardhat repo: https://github.com/NomicFoundation/hardhat/tree/master/packages/hardhat-vyper
Code of Conduct

[X] I agree to follow this project's Code of Conduct

https://shields.io/


Add OnDial handler for datachannels

Adds an OnDial handler to be fired once the dialing side has sent the DCEP OPEN message over the data channel.
DCEP specifies that ordered data can be sent by the dialing side as soon as it has sent the open message (link):

After the DATA_CHANNEL_OPEN message has been sent, the sender of that message MAY start sending messages containing user data without waiting for the reception of the corresponding DATA_CHANNEL_ACK message. However, before the DATA_CHANNEL_ACK message or any other message has been received on a data channel, all other messages containing user data and belonging to this data channel MUST be sent ordered, no matter whether the data channel is ordered or not

Leveraging this is useful in applications that only use reliable, ordered delivery, those that want to start sending ordered messages on unordered channels before receiving an ACK back from the other peer, etc. This was possible before https://github.com/pion/webrtc/pull/1994, but was no longer possible after OnOpen was (correctly) updated to wait for the ACK to be received.
Follows up on: https://github.com/pion/webrtc/issues/1063

Thanks for the review Benny! Will address these comments today

Addressed initial comments! For some reason re-requesting a review removed Sean, feel free to add him back if you think its necessary


Stop button overlaps with scrollbar

Testing #100850
It looks like there is a slight overlap between the stop button and the scrollbar.

Nice catch. Agree we could add a bit of margin-right.


Added if statement for window

Fix window is undefined when using Jetset with SSR.

Thank you kindly for this @g45t345rt !


Drupal 10 is broken; Drush 12 does not work with Drush Launcher

Drush Launcher is a tool that adds the path of drush to your path so commands can be written as drush (rather than vendor/bin/drush). It is known to be incompatible with Drush 12 (required by Drupal 10).
The Site Template invokes drush so it is failing.
Suggestion: Add /var/www/drupal/vendor/bin to $PATH. I'm not sure how to do this, I have tried both in the Dockerfile and in install.sh and neither of them work. The drupal logs report:
d10-rosie-drupal-dev-1  | [03-Aug-2023 14:57:26 UTC] PHP Fatal error:  Uncaught RuntimeException: Drush Launcher is not compatible with Drush 12+. See https://github.com/drush-ops/drush-launcher/issues/105. in /var/www/drupal/vendor/drush/drush/includes/preflight.inc:23
d10-rosie-drupal-dev-1  | Stack trace:
d10-rosie-drupal-dev-1  | #0 phar:///usr/bin/drush/bin/drush.php(141): drush_main()
d10-rosie-drupal-dev-1  | Islandora-Devops/isle-site-template#1 /usr/bin/drush(10): require('phar:///usr/bin...')
d10-rosie-drupal-dev-1  | Islandora-Devops/isle-site-template#2 {main}
d10-rosie-drupal-dev-1  |   thrown in /var/www/drupal/vendor/drush/drush/includes/preflight.inc on line 23
d10-rosie-drupal-dev-1  | s6-rc: warning: unable to start service install: command exited 128
d10-rosie-drupal-dev-1  | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
d10-rosie-drupal-dev-1  | prog: fatal: stopping the container.

and the container has stopped itself, so I can't get in to fix it.

Drush is installed in Buildkit and /usr/bin/drush is assumed here:

https://github.com/Islandora-Devops/isle-buildkit/blob/main/drupal/rootfs/usr/local/bin/drush

Drush is called without a path here:

https://github.com/Islandora-Devops/isle-buildkit/blob/main/drupal/rootfs/usr/local/bin/install-drupal-site.sh#L173
and here: https://github.com/Islandora-Devops/isle-buildkit/blob/main/drupal/rootfs/etc/islandora/utilities.sh
and here: test/rootfs/etc/s6-overlay/scripts/install.sh
and a few times in the code-server.

also /usr/share/drush is listed here:

https://github.com/Islandora-Devops/isle-buildkit/blob/main/drupal/rootfs/etc/drush/drush.yml

Solved with #286


Fix warning MissingReferenceMetadata when running unit test tests/unit_tests/simtel/test_simulator_light_emission.py::test_plot_simtel_ctapipe

pytest --no-cov tests/unit_tests/simtel/test_simulator_light_emission.py::test_plot_simtel_ctapipe gives the following warning:
/Users/maierg/micromamba/envs/simtools-dev/lib/python3.11/site-packages/ctapipe/core/provenance.py:332: MissingReferenceMetadata: Could not read reference metadata for input file: /Users/maierg/DESYCloud/CTA/Pipelines/MC-Pipeline/gammasim-tools/simtools/tests/resources/xyzls_layout.simtel.gz

This should be fixed.

I think this is as much an issue for ctapipe as here.
At the moment, we know that we cannot expect this metadata in simtel files, so ctapipe shouldn't warn about it.
In the long-term, simpipe should make sure that the required CTAO reference metadata is stored, by using the simtel metaparams system and ctapipe should read it.
I opened a PR in ctapipe to silence this warning for now here:
https://github.com/cta-observatory/ctapipe/pull/2644

Yes, we can close this.


Installing PNP from local files

My work environment is very locked down.  When running PowerShell as a local admin, I don't have internet access.  Therefore, I need to get PNP setup using the MSI downloaded files.
I followed the instructions on the PNP Page:
Setup files
You can download setup files from the releases section of the PnP PowerShell repository. These files will up be updated on a monthly basis. Run the install and restart any open instances of PowerShell to use the cmdlets.

Downloaded the file
I opened Powershell as admin.
Ran the SHarePointPnPPowerShellOnline.msi
Installed successfully.

When I list the available modules, SharePointPnPPowerShellOnline is not there.
Am I missing something?  Where can I find the detailed instructions for installing PNP from downloaded MSI Files?

@officedocsbot assign @yogkumgit

Hello @CTFlorian How are you?
Thanks for your feedback.
I need to kindly redirect you to open PnP cmdlets issues here a member of the PnP community will handle your request there.
Thank you!

	Thanks. I will do so!

	Thanks.-----------------------Christopher Florian

On Tue, Jun 9, 2020 at 2:33 PM -0500, "Andres Mariano Gorzelany"<EMAIL_ADDRESS>wrote:
Hello @CTFlorian How are you?
Thanks for your feedback.
I need to kindly redirect you to open PnP cmdlets issues here a member of the PnP community will handle your request there.
Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@get-itips  Thank you very much for the contribution and sharing this explanation. @CTFlorian
Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


version 4.6.0 - can't display a device with error "Unsupported JSONB encoding version"

After migrating to version 4.6.0 of chiprstack from version 4.4.3 I'm getting the following message when trying to display a device. (going to the application, and clicking on the deviceeui to display it)
An alert message is displayed with following message: Unsupported JSONB encoding version
the console shows:
code: 13
message: "Unsupported JSONB encoding version"
metadata:
content-length: "0"
content-type: "application/grpc-web-text+proto"
date: "Wed, 10 Jan 2024 20:41:19 GMT"
grpc-message: "Unsupported%20JSONB%20encoding%20version"
grpc-status: "13"
server:
"nginx/1.25.3"
stack
:
"Error: Unsupported JSONB encoding version\n    at new j (https://.../static/js/main.3719a277.js:2:1442435)\n    at Vt (https://.../static/js/main.3719a277.js:2:1466087)\n    at Et.<anonymous> (https://.../static/js/main.3719a277.js:2:1465905)\n    at qe (https://staging.helium-iot.xyz/static/js/main.3719a277.js:2:1452018)\n    at Ue (/static/js/main.3719a277.js:2:1451824)\n    at Ft (https://staging.helium-iot.xyz/static/js/main.3719a277.js:2:1459966)\n    at o.W (https://.../static/js/main.3719a277.js:2:1460986)\n    at o.R (/static/js/main.3719a277.js:2:1460965)"

The problem also seem to appear when a message arrives from network. this i breaking the communications:
2024-01-10T20:34:51.577917Z ERROR up{deduplication_id=f2253685-8e33-41e4-8acf-6bfc9e501514}: chirpstack::uplink::join: Handle join-request error error=Unsupported JSONB encoding version

I can not reproduce this issue. Could you provide more context, e.g.

OS version and PostgreSQL version?
Did you make any manual modifications to the database?
Could you print the schema of the device column?

Hi Orne, thank you for responding:

OS is Ubuntu 22.04.3 LTS
Postgres 14-alpine

I did not made any modification on the chirpstack tables structure (I add some tables into the db but don't touch the existing one)
column_name	     column_default	   data_type
join_eui		                                   bytea
application_id		                          uuid
device_profile_id		                  uuid
created_at		timestamp with time zone
updated_at		timestamp with time zone
last_seen_at		timestamp with time zone
scheduler_run_after		timestamp with time zone
skip_fcnt_check		boolean
is_disabled		boolean
tags		                                        jsonb
dev_eui		                             bytea
external_power_source		boolean
battery_level		numeric
margin		integer
dr		smallint
latitude		double precision
longitude		double precision
altitude		real
dev_addr		bytea
name		character varying
description		text
enabled_class		character
variables		character varying

OK, got it !
variables has been switch from jsonB to varchar because of springboot / hibernate new version bug preventing to correclty filter table for structure modifications. changed it back to jsonb and problem disapeared.
thank you for looking into it and confirm it was working


ShardInfo in NodeInfo MXBean is missing the schema name leading to duplicates

CrateDB version
any after #10835
CrateDB setup information
CrateDB + JMX Exporter (or another way to read the JMX metrics)
Problem description
ShardInfo in NodeInfo MXBean is missing the schema name leading to duplicates when exporting why jmx exporter.
This seems to be an oversight of https://github.com/crate/crate/pull/10835
Adding a schema will probably also need an update of the jmx exporter.
Steps to Reproduce
CREATE TABLE s01.tab (i INT) CLUSTERED INTO 1 SHARDS;
CREATE TABLE s02.tab (i INT) CLUSTERED INTO 1 SHARDS;
INSERT INTO s01.tab (i) VALUES (1);
INSERT INTO s02.tab (i) VALUES (1);

jmx exporter + Prometheus setup

Actual Result
name="shard_info",property="size",id="0",table="tab",partition_ident="",
name="shard_info",property="size",id="0",table="tab",partition_ident="",
Expected Result
name="shard_info",property="size",id="0",table="tab",schema="s01",partition_ident="",
name="shard_info",property="size",id="0",table="tab",schema="s02",partition_ident="",

Thx for finding out the root cause of those errors in prometheus!

@proddata Thx for finding out the root cause of those errors in prometheus!
Keep in mind that jmx_exported can probably handle the new attribute (schema) without any change, but please test it to verify that this is the case.

@proddata Could you test with dev builds containing both https://github.com/crate/jmx_exporter/pull/73 and https://github.com/crate/crate/pull/16456?

@proddata Could you test with dev builds containing both crate/jmx_exporter#73 and #16456?

Tested with CrateDB on master and 4.7.2 with jmx_exporter on master and 1.1.0.
Works as expected. ✅

I assume there is no meaningful mitigation for jmx_exporter to handle duplicates for older versions of CrateDB? i.e. adding a ordinal.

I assume there is no meaningful mitigation for jmx_exporter to handle duplicates for older versions of CrateDB? i.e. adding a ordinal.

Unfortunately no.

Released crate-jmx-exporter 1.2.0


Add highlight for WinSeparator

Nvim is deprecating VertSplit and moving to WinSeparator for window borders in 0.10. By default, WinSeparator links to normal which does not look great for most colorschemes.

Win Separator highlights have been added. You can customise the colour as well by setting the variable vim.g.apprentice_win_separator as the colour you want to set.


Your Solution Does Not Work!  Poor Documentation & Dependency Supporting Files

This version has files missing and the documentation simply Suck!  There not a good way to understand how to implement the entire solution.  It doesn't not work, period!  It's a waste of time!

LOL


Distance Aware Data Aug

"During training, similar to GT-AUG (Shi, Wang, and Li 2019), we add the sampled points and bounding box into the training sample for
data augmentation." How did you do this, can you please provide an example for one frame.

I have found it at "pcdet/datasets/augmentor/database_sampler.py" called DADataBaseSampler, I think this works for the augmentation method they proposed.


searchContacts never resolves in some cases

The pattern I'm seeing:
If the search returns no results, the promise resolves after wait amount of seconds.
If the search does send a result to the handler, the promise never resolves.

just moving this issue over here so we can investigate further. confirmed that I see the same behavior at the bridge level. specifically here,
https://github.com/textileio/react-native-sdk/blob/master/ios/TextileNode.m#L332
I see a DONE result come back if we hit the time limit without finding any result.
If we find a result before reaching the time limit, no DONE event will happen.
One quick fix. There is a bunch of cleanup to do around this handling anyway, so one simple solution would be to just handle the timeout event right in the SDK. we already know when it should happen, so as long as we don't get an early DONE we can fire it off.

Crap, not surprising I guess... no test for this guy. I'm sure it's simple ™, can look once tonight/morning...


Port to 3.0.0-preview5

@YohDeadfall merging this as it's pretty trivial/small changes (and we want to publish ASAP :)).


add kubectl and helm checks to setup-minikube

Issue
When users run setup-minikube it does not verify they have kubectl or helm, but in our workflow we need those tools.
Solution
Allow the setup-minikube command to check for helm and kubectl because minikube will want to use kubectl right away, and helm is needed for logging later on. Prompt the user to install them with helpful links.

Looks good to me -- detected missing all bins (as expected).
Perhaps one thing we could discuss this week:

Can we develop one (or two) main "supported workflow paths" which we will strive to support, document and have work well. For everything else user can be on their own...

User: (Only pip install, warcli commands, only via minikube)
Developer: (clone repo, any k8s backend)


Right arrow = Tab?

Details:
Using SSH
NeoVim 0.9.5
I use PlugInstall (vim-plug)
When pressing the right arrow, and when codeium is enabled in my init file.. It, instead of moving right, presses tab.
I have no idea.
Additional info:
Theres no bindings in my file
Only in Insert mode
Running Raspberry Pi OS (64 Bit) on an RPI 4B.
Codeium is up to date during all of this
I cannot find any issues on GitHub or information in :help codeium that would possibly explain any of this.
Codeium is set to default settings, I have changed nothing.
Disabling codeium with :Codeium Disable does not fix this issue. It is an issue with the plugin.
Codeium is also authenticated.
It doesn't seem discriminate. (It works on all file types I tried so far, including no file type.)
If it somehow matters, I use an init.lua, not an init.vim. I just use the vim.cmd() method for vim-plug and what not.

Somewhat related to #305
Yes.  I've been giving some thought to this, but I don't like that solutions I've come up with imply forcing users to pass the bindings as plugin options as opposed to setting them in standard Vim fashion.
Sin you're using Neovim, you can re-implement the bindings with proper fallback like this:
-- Disable Codeium default bindings
vim.g.codeium_disable_bindings = 1

local function set_keymap_codeium_opts(desc, opts)
	opts = opts or {}
	local codeium_default_options = {
		silent = true,
		expr = true,
		desc = desc,
	}
	return vim.tbl_extend("force", codeium_default_options, opts)
end

local function codeium_keymap_set(mode, keys, codeium_function, desc, opts, arg)
	opts = set_keymap_codeium_opts(desc, opts)
	vim.keymap.set(mode, keys, function()
		local status, completion_text = pcall(function()
			return vim.api.nvim_eval(
				"b:_codeium_completions.items[b:_codeium_completions.index].completionParts[0].text"
			)
		end)
		if not (status and completion_text and completion_text ~= "") then
			return vim.api.nvim_replace_termcodes(keys, true, true, true)
		end
		if arg ~= nil then
			return vim.fn[codeium_function](arg)
		end
		return vim.fn[codeium_function]()
	end, opts)
end

codeium_keymap_set("i", "<C-f>", "codeium#Accept", "Codeium Accept suggestion")
codeium_keymap_set("i", "<A-Bslash>", "codeium#Complete", "Codeium Trigger suggestion")
codeium_keymap_set("i", "<A-]>", "codeium#CycleCompletions", "Codeium Cycle completions forwards", {}, 1)
codeium_keymap_set("i", "<A-[>", "codeium#CycleCompletions", "Codeium Cycle completions backwards", {}, -1)
codeium_keymap_set("i", "<A-BS>", "codeium#Clear", "Codeium Clear completions")
codeium_keymap_set("n", "<leader>cd", "codeium#Chat", "Codeium Open Chat")
codeium_keymap_set(
	"i",
	"<Right>",
	"codeium#AcceptNextWord",
	"Codeium Accept next word",
	{ noremap = true, replace_keycodes = false }
)
codeium_keymap_set(
	"i",
	"<C-Right>",
	"codeium#AcceptNextLine",
	"Codeium Accept next line",
	{ noremap = true, replace_keycodes = false }
)

For now, I'll change the default bindings for partial completions to less common keys.

Thank's LeonardoMor, This work for me.

Oh! Thanks for noticing my issue. I'll try this.
I didn't take too much of a thorough search of the issues, which explains the relation.

@LeonardoMor are you planning to make a PR soon? I might need to revert your change if we don't have a fix by tomorrow.

It works! Thank you.

@LeonardoMor are you planning to make a PR soon? I might need to revert your change if we don't have a fix by tomorrow.

For now, submitted #397 to not use Right in the default bindings for the partial completions.
I can do something better for the fallback, namely, just return the keys  in the key map when there are no completions. But it'll take me a bit more time. The main issue here is that in order to get the keys that are set for Codeium functions, I have to parse the output of :imap, which might be a bit brittle. So I am investigating how to do this better. I'll submit a PR once I have a quality solution that doesn't introduce more bugs.
I'm sorry these partial completions have caused so many bugs. But things keep improving.

Actually no. It doesn't seem to work.
It fixed the issue but now codeium itself is not doing any completions?

Actually no. It doesn't seem to work. It fixed the issue but now codeium itself is not doing any completions?

That is a different issue that's been around. See #376
Although there was a PR that was supposed to fix it, I still find issues with Neovim (works fine with Vim).
What's been working for me is:

Go into insert mode, so that the plugin loads (I use Lazy)
Go to normal mode. Then :CodeiumToggle twice.

After that I get completions.

Still nothing.

Still nothing.

It doesn't work for me either. But the mappings  or the Lua code above is not what broke it.

@FateUnix29 See #399

Just updated because pressing the arrow-right in insert mode without any suggestions gave me errors in vim and a -1 in my insert. Now when I press the arrow-right I get tabs, if there are no suggestions.

Just updated because pressing the arrow-right in insert mode without any suggestions gave me errors in vim and a -1 in my insert. Now when I press the arrow-right I get tabs, if there are no suggestions.

Yeah, the arrow key thing will be fixed once #398  is merged.
Are you using Vim or Neovim?

Vim! Already applied #398 manually myself and works great now. Thanks for the work! Much appreciated.


Only the last signature of an overloaded function is allowed in Parameters

TypeScript Version:  3.2.1

Search Terms: overloaded function. overloaded signature, overloaded arguments
Code
function testFn(a: string): boolean;
function testFn(a: number): boolean;
function testFn(a: boolean): boolean;
function testFn(_a: string | number | boolean): boolean {
  return true;
}

interface Stub {
  callsFake(...args: Parameters<typeof testFn>): void
}

const stub1: Stub = {
  callsFake(_a: string): boolean {
    return true;
  }
}
const stub2: Stub = {
  callsFake(_a: number): boolean {
    return true;
  }
}
const stub3: Stub = {
  callsFake(_a: boolean): boolean {
    return true;
  }
}

Expected behavior:
Expected stub1 and stub2 to be compiled without any error.
Actual behavior:
Both stub1 and stub2 shows
Type '(_a: string) => boolean' is not assignable to type '(a: boolean) => any'.
  Types of parameters '_a' and 'a' are incompatible.
    Type 'boolean' is not assignable to type 'string'. [2322]

Playground Link:
http://www.typescriptlang.org/play/#src=function testFn(a%3A string)%3A boolean%3B
function testFn(a%3A number)%3A boolean%3B
function testFn(a%3A boolean)%3A boolean%3B
function testFn(_a%3A string | number | boolean)%3A boolean {
  return true%3B
}

interface Stub {
  callsFake(...args%3A Parameters<typeof testFn>)%3A void
}

const stub1%3A Stub %3D {
  callsFake(_a%3A string)%3A boolean {
    return true%3B
  }
}
const stub2%3A Stub %3D {
  callsFake(_a%3A number)%3A boolean {
    return true%3B
  }
}
const stub3%3A Stub %3D {
  callsFake(_a%3A boolean)%3A boolean {
    return true%3B
  }
}
Related Issues:
https://github.com/Microsoft/TypeScript/issues/13570
The closest I can find is this but it has generic types at the first function's signature, I am not sure fundamentally do they refer to the same issue.

From the documentation for "Conditional Types":

When inferring from a type with multiple call signatures (such as the type of an overloaded function), inferences are made from the last signature (which, presumably, is the most permissive catch-all case). It is not possible to perform overload resolution based on a list of argument types.

https://www.typescriptlang.org/docs/handbook/advanced-types.html
(section "Type inference in conditional types", direct linking unfortunately not possible)

Thanks, @MartinJohns
Closing this issue, and also providing the direct link for future reference:
https://www.typescriptlang.org/docs/handbook/advanced-types.html#type-inference-in-conditional-types

Oh, direct linking is possible! I did not bother check the markup, just assumed there would be a visible anchor.


TLS Support for consul on k8s

Additional environment details (Operating System, Cloud provider, etc):
Steps to reproduce the issue:

Consul setup with helm charts on k8s.  It is configured for TLS with a cert issued by the internal k8s CA.
Install DD Agent per https://app.datadoghq.com/account/settings#agent/kubernetes
Configure auto discovery on the Consul STS with the following annotations:

        ad.datadoghq.com/consul.init_configs: '[{}]'
        ad.datadoghq.com/consul.instances: '[{"url": "https://%%host%%:8501","catalog_checks": "true","new_leader_checks": "true", "tls_ca_cert": "/var/run/secrets/kubernetes/serviceaccount/ca.crt"}]'

Describe the results you received:
DD receives an error in log:
Caused by SSLError(CertificateError(\"hostname '<IP_ADDRESS>' doesn't match either of 'consul-server.consul.svc.cluster.local', 'server.vault-us-east-1.consul', '*.consul-server.consul.svc.cluster.local'\",),))\n"}]

Describe the results you expected:
Need to be able to perform consul checks against pods configured with TLS.
Additional information you deem important (e.g. issue happens only occasionally):
I believe this could be solved by adding a flag to use HostHeaderSSLAdapter as part of the requests in the code. https://toolbelt.readthedocs.io/en/latest/adapters.html#hostheaderssladapter

@ryan-dyer-sp Hello! What version of the Agent are you running?

The one as described in the install instructions here: https://app.datadoghq.com/account/settings#agent/kubernetes

@ofek ^^

Have you tried this? https://github.com/DataDog/integrations-core/blob/b0bc4fe953179692730d15660ee687de19e01fed/tls/datadog_checks/tls/data/conf.yaml.example#L38-L43

I've got a similar issue, but with Vault. I'm connecting to the vault API using the pod's IP, which isn't a subject alternate name on the certificate. I tried setting a Host header in the autodiscover config (per the Vault config) but that doesn't seem to have worked.
I think @ryan-dyer-sp's issue is the same as mine. TLS support does exist for Consul, and his problem is really that %%host%% is returning the pod IP which doesn't match any of the names on the certificate he's using (per the error).
What I don't understand is the config snippet @ofek links to. That's the config for a different type of check - how could I set that for a Vault check or how could @ryan-dyer-sp set that for his Consul check?
For the record, here's the autodiscover config I'm using for my Vault deployment:
      annotations:
        ad.datadoghq.com/vault.check_names: '["vault"]'
        ad.datadoghq.com/vault.init_configs: '[{}]'
        ad.datadoghq.com/vault.instances: |
          [
            {
              "api_url": "https://%%host%%:%%port%%/v1",
              "detect_leader": true,
              "headers": {
                "Host": "vault.infra"
              },
              "tls_ca_cert": "/etc/tls/vault/ca.pem",
              "tls_cert": "/etc/tls/vault/vault.pem",
              "tls_private_key": "/etc/tls/vault/vault-key.pem"
            }
          ]

And the error in the logs for my datadog agents:
SSLError: HTTPSConnectionPool(host='<POD IP>', port=8200): Max retries exceeded with url: /v1/sys/leader (Caused by SSLError(CertificateError("hostname '<POD IP>' doesn't match either of '<DNS NAME>', 'vault.infra', 'localhost', '<IP_ADDRESS>'",),))

I did try setting log_requests: true to see if the datadog agent is sending the Host header I'm setting per the Vault config but the datadog agent seems to ignore the Vault autodiscover configuration altogether when I add it:
$ kubectl exec datadog-agent-tlgg8 -n infra -- sh -c 'agent check vault'
Error: no valid check found
command terminated with exit code 255

I'm running v6.15.1 of the agent.

This can be addressed with tls_use_host_header available on 6/7.19.x onwards


Fix dataset insert API bug

#90

So it is our bug. I will catch up this later.
Thanks for patching it.
On Mar 18, 2016 3:29 PM, "Zhaonan Sun"<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/linkedin/WhereHows/pull/92
Commit Summary

Fix dataset insert API bug

File Changes

M backend-service/app/models/daos/DatasetDao.java
https://github.com/linkedin/WhereHows/pull/92/files#diff-0 (12)

Patch Links:

https://github.com/linkedin/WhereHows/pull/92.patch
https://github.com/linkedin/WhereHows/pull/92.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/linkedin/WhereHows/pull/92


Rangeslider captures mousedown

I'm using rangeslider.js in a scenario where I need to fire an event when sliding begins. I figured I'd do this with
$('input[type="range"]')
    .rangeslider({
      polyfill: false,
    })
    .on('mousedown touchstart', rangeSliderStart);

but rangeslider captures the mousedown and won't let it bubble up so rangeSliderStart is never called. If I change polyfill to true and use the native widget on Chrome it works as planned.

@luopio this should work in your case:
// Adding the EventListener to the `document`.
// Event delegation helps us to call `rangeSliderStart` only
// if `e.currentTarget` is `.rangeslider`
$(document).on('mousedown touchstart', '.rangeslider', rangeSliderStart);

If you would really touch, mousedown the $('input[type="range"]') element it'll work but it's actually visually hidden :)

Ah I see. Thanks for the quick answer.