Including password change and reset tracking across multiple data sou…

…rces
Fixes #
Proposed Changes

Similar hunting query exists with overlapping logic, although has some differences on trigger criteria and datasources list. Do we want to keep both or merge with differences ?  https://github.com/Azure/Azure-Sentinel/blob/master/Hunting Queries/MultipleDataSources/MultiplePasswordresetsbyUser.yaml .


Make nextClickDelay works with ClickAnywhere

Description
Similar to ClickOnDialog for dialog progression. It has capability to delay the next input, while ClickAnywhere does not
What is the current behavior?
nextClickDelay does not work with ClickAnywhere
What is the new behavior?
nextClickDelay now works with ClickAnywhere
Important Notes

My change does not require modifcations or additions to documentation

Thanks for the PR.


Optionally add event contents to topic

Adds a new feature: When events-topic is provided for a binding, then the actual contents of those events are published to that topic as a big blob of JSON.
Also, this updates the Dockerfile to install the specifically expected versions of gevent and greenlet.

Thank you @DavidMikeSimon, sorry for the delay, please add to the docs and a bit of a test to demonstrate.


Big number chart appears a fronted error when is rendering

Describe the bug
TypeError: Cannot read property 'families' of undefined
To Reproduce
Steps to reproduce the behavior:

Go to our charts page
Click on a button to render a Big number
Scroll down to see my code and my dependencies
(1) my code

<SuperChart
      key={`${chartId}`}
      id={`chart-id-${chartId}`}
      chartType={type}
      width={400}
      height={400}
      formData={{
               colorPicker: {
                 a: 1,
                 b: 135,
                 g: 122,
                 r: 0
               },
               compareLag: 1,
               compareSuffix: 'over 10Y',
               metric: 'sum__SP_POP_TOTL',
               showTrendLine: true,
               startYAxisAtZero: true,
               vizType: 'big_number',
               yAxisFormat: '.3s'
             }}
      queryData={{
               data: [
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>000,
                   sum__SP_POP_TOTL:<PHONE_NUMBER>
                 },
                 {
                   __timestamp:<PHONE_NUMBER>00,
                   sum__SP_POP_TOTL: 617333941
                 }
               ]
             }}
    />

(2) my dependencies
"@superset-ui/chart": "^0.14.0",
"@superset-ui/chart-controls": "^0.14.0",
"@superset-ui/color": "^0.14.0",
"@superset-ui/core": "^0.14.0",
"@superset-ui/dimension": "^0.14.0",
"@superset-ui/number-format": "^0.14.0",
"@superset-ui/style": "^0.14.0",
"@superset-ui/time-format": "^0.14.0",
"@superset-ui/translation": "^0.14.0",
"@superset-ui/connection": "^0.14.0",
"@superset-ui/query": "^0.14.0",
"@superset-ui/validator": "^0.14.0",
"@superset-ui/legacy-preset-chart-big-number": "^0.14.9"
4. See error
Oops! An error occured!
TypeError: Cannot read property 'families' of undefined
Expected behavior
The Big number chart can be rendered correctly
Screenshots

.
Environment (please complete the following information):

superset-ui version: [0.14.0]
Node version: node - v10.16.0
npm version: npm -v6.9.0

Additional context
I plan to use plugins of SuperSet-ui for my projects

@pjw126 are you using SuperChart and superset-ui outside of Superset, in some other codebase? If so, I think I may have the info you need...
This bug about families is the plugin trying to find theme.typography.families which is an Emotion theme passed into plugins by Superset. theme defaults to an empty object when not passed in, thus the error you see. In your react app(s), you can:
import { supersetTheme, ThemeProvider } from '@superset-ui/style';
then wrap your App (or whatever) in them like so:
<ThemeProvider theme={supersetTheme}>
  <YourApp>
    <SuperChart ...>
    ...
  </YourApp>
</ThemeProvider>

Thank you Mr rusackas, my Big Number Chart can be render correctly.
Then, I plan to use  the plugins of  Superset-ui,  could you provide the detailed user's manual how to use every plugin outside of Superset

Hi @pwj126 Sorry for the delayed reply. I don't know of any user docs on using superset-ui plugins outside of Superset. In fact, I've never personally tried it. I'd love to hear mroe about your use case so i can help to support it if it's a potentially common one. I believe @kristw has some insight into how to use these plugins in other projects, and may be able to provide some small amount of help. That said, I'm wondering if the  tip is enough to mark this particular bug as resolved.

The codebase on this repo has been moved to the main Apache Superset repo, and consequently the repo is in the process of being archived. See the Superset Improvement Proposal for details: https://github.com/apache/superset/issues/13013 . While all currently open issues and PRs will be closed, we encourage you to reopen this issue on the main repo if it is still relevant.


continue gracefully if cloc isn't installed

line-counting isn't essential functionality, the build should proceed even if cloc isn't installed
reported by @patriknw when trying to follow the https://github.com/scala/community-builds/wiki/Troubleshooting-a-failure instructions. this shouldn't be a hurdle for library authors trying to help
also fwiw

wget is also needed, but that is detected immediately

fixed by bfadba96d6d441a5586eb242ec724e6dd8bd33fb (2.12.x will get the fix when we unfreeze)


update megaman to version 0.2 release

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Strange... CI is failing saying it can't download the package, but I have no problem locally:
$ curl -O https://pypi.python.org/packages/source/m/megaman/megaman-0.2.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   306  100   306    0     0   1721      0 --:--:-- --:--:-- --:--:--  2217
$ ls
megaman-0.2.tar.gz

Any ideas why this might be happening?

Ah – turns out I was downloading the 404 page :grin:

Ah – PyPI has a new URL scheme: http://lists.science.uu.nl/pipermail/nix-dev/2016-April/020237.html
Found a conda-forge discussion here: https://github.com/conda-forge/staged-recipes/issues/481

Travis is failing with
dyld: Library not loaded: @rpath/libisl.10.dylib

Travis is failing with

dyld: Library not loaded: @rpath/libisl.10.dylib

Not sure what is going on, but did you try to unpin gcc and libgcc?

They're currently pinned to 4.8* on osx. Should that be changed?

They're currently pinned to 4.8* on osx. Should that be changed?

It is worth a try :smile:

Still failing with the same error 😡  I'm not sure what to do...
What in the OSX build has changed since when this previously worked?

Any ideas @msarahan?

@jakevdp can you try adding (pinning) isl like this. That will ensure you'll get the default channel isl instead of conda-forge's. I believe ours might be broken.
Note that only on OS X conda is pulling conda-forge's isl... That deserves some investigation.

Looks like it worked!
One question: I un-pinned gcc here; I recall that being recommended for some reason previously. Also #1 mentions gcc should be a dependency on Linux as well... any opinions on those?

@jakevdp that seems to work. Can you please open an issuereporting our faultyisl`?
https://github.com/conda-forge/isl-feedstock/issues

There is nothing wrong with ISL package on conda-forge. GCC 4.8, which is in the default anaconda channel, supports only ISL 0.12.2. GCC 5, for example, supports 0.13 .. 0.14, and GCC - 0.14 .. 0.16. It is just a poor GCC package on anaconda, which doesn't pin supported versions of ISL at all, as well as cloog, mpc, and mpfr.

Ah, thanks @frol. So is the best course for the time-being to pin gcc 4.8* and isl 0.12* in these recipes?

@jakevdp As far as I can tell, yes - https://github.com/conda-forge/staged-recipes/issues/436. However, using gcc dependency is controversial - https://github.com/conda-forge/conda-forge.github.io/issues/29.

In this case, we're depending on gcc in order to use OpenMP.

@jakevdp no need to pin gcc as that won't ensure you'll get the right isl. That problem only exist b/c conda-forge added a newer isl, so only isl needs to be pinned. (Pinning gcc here won't hurt though.)

However, using gcc dependency is controversial

Indeed. But note that since numpy with openblas was added libgcc will be present in a number of projects causing all sort of havoc.

It is better to pin GCC when ISL is pinned. Otherwise, once GCC will be upgraded, you will get some weird compilation errors instead of dependency error.

It is better to pin GCC when ISL is pinned.

Unless you pin it down to a release there is nothing ensuring that this would work. The current package on defaults for gcc should pin isl to avoid this. Otherwise the mismatch can always happen in updates/changes.

Looks like tests are on their way to passing.
I'm going to be away from my computer this evening, but getting this merged is a bit time-sensitive since we're re-submitting a paper for review with install instructions based on conda-forge. Can someone merge for me ASAP if things look to be in order? Thanks!

@jakevdp I saw that the tests passed before so let's be naughty and merge this before Travis-CI finishes :wink:


data-min-length setting bug

・If I do not set the data-min-length value or set with 6 value in markup code, dropdownlist shows only 5 result items as default
・If I set the data-min-length value the greater-than 6 value in markup code, dropdownlist does not show anything.
Please let me know more details about this problem. Thank you.

https://github.com/sergeyt/meteor-typeahead/issues/109
It seems to be related to this resolved issue!
It works like charm with data-limit="40".


Support for PiggyCustomEnchants?

When using a smelting pickaxe it doesn't give a smelted item.
I know this isn't really an "issue" but I would love to see it implemented.

I don't know how 'PiggyCustomEnchants' works but if it sets the drops for the block break event correctly then AutoInv will behave as expected.
https://github.com/JackNoordhuis/AutoInv-PocketMine/blob/c8192ec1f7f5dbdfdb40c30626ca65c3d2698483/src/jacknoordhuis/autoinv/event/handle/BlockBreakPickup.php#L44

Changing the event priority here
https://github.com/DaPigGuy/PiggyCustomEnchants/blob/abcc34e83d9c73da6eeb00102bb0aacc00890323/src/PiggyCustomEnchants/EventListener.php#L103 in PiggyCustomEnchants to 'HIGH' should fix your problem.

Thank you :)


prefix methods that fetch a single item with Get

Current cloudflare-go version
0.28.0
Description
Similar to #612, perhaps all methods should use a standardized naming that has a verb prefix.  Since List already has its own issue, I think the remaining methods that do not already use a verb prefix are querying a single resource and should use the Get prefix, which is already used for some resources.
Use cases
Similar to the argument for List, this could help with autocomplete
Potential cloudflare-go usage
just like now, but prefixed with Get.

References

#612

Related to this, is there a deprecation framework for api-incompatible change like this?  These new function names could easily be added and then deprecation warnings on the old names could be introduced to warn folks they'll be removed at a future date.  Just not sure if there's already a process for this kind of thing in place.

an approach like #758 is preferable and like you suggest; add new methods wrapping the old ones and eventually deprecate the old ones after a few releases.

this is no longer required as we will be taking a different approach with the experimental client (for v2) with different, yet consistent interfaces.
see for initial musings https://github.com/cloudflare/cloudflare-go/blob/master/docs/experimental.md


Optimize load dictionary and stop by embed files, support user dictio…

Please provide Issues links to:

Issues: #

Provide test code:

Description
...

Codecov Report

Merging #113 (11bdec4) into master (ff04d83) will increase coverage by 0.32%.
The diff coverage is 92.30%.

@@            Coverage Diff             @@
##           master     #113      +/-   ##
==========================================
+ Coverage   91.96%   92.28%   +0.32%
==========================================
  Files          12       12
  Lines         983      998      +15
==========================================
+ Hits          904      921      +17
+ Misses         52       51       -1
+ Partials       27       26       -1

Impacted Files
Coverage Δ

dict_1.16.go
91.30% <92.30%> (+6.11%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ff04d83...11bdec4. Read the comment docs.


optimize handler chain

Optimize handler chain

RouterHandler returns Status instead of bool, can stop directly (route not found)
HandlerChain keeps the clustersnapshot, returns to proxy,  so the Handler's snapshot is same as proxy used

LGTM


re-gen docs

Coverage remained the same at 94.597% when pulling 4c44f5e6f234ff8c4c897680415fa2522f3c1ab2 on gen-docs into 1c44991e62b772e046b07cd6ff32eb9fd94b01b7 on master.

Coverage remained the same at 94.597% when pulling 4c44f5e6f234ff8c4c897680415fa2522f3c1ab2 on gen-docs into 1c44991e62b772e046b07cd6ff32eb9fd94b01b7 on master.


Add Distribution Calculations subsection to Integrate/Incentives

Review / feedback would be much appreciated

Feedback:
Good job! I'm glad to have this supplement the page.
Mentioning the OSMO-bias might be nice, especially since it could be the topic of on-chain governance soon. It also puts less accountability to keep the 1.5x and 0.5x figures updated, as a user could question and easily find out if the OSMO-bias has changed since the time of writing.
Minor, but 'ie' should always be i.e. Also, a couple typos: 'equivlant' and 'durration '.
Wash trading could benefit with a link. Perhaps Investopedia? https://www.investopedia.com/terms/w/washtrading.asp
Remove the word 'towards' ? (line 44)

@UnityChaos  Thank you for the detailed information.
@JeremyParish69  I fixed the small typos, merging for now!
Thank you again!

@daniel-farina Thank you for fixing those and merging. Will try to post PRs to here alongside any future changes to the algo.


Improve CLI --help messages

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2202
Originally created by @DouweM on 2020-07-29 16:43:39

View 4 previous comments from the original issue on GitLab


Solving coding problems

Put a solution for your favourite coding problem with  your favourite programming language  as a part of fun for Hacktoberfest.

hey! i have added program for computing large factorial which are out of limit to be stored in single data type.
pls accept it.


streetViewControl and Zoom control  not working?

I tried
<GoogleMap
ref={props.onMapLoad}
zoom={props.zoom}
center={props.center}
onClick={props.onMapClick}
onBoundsChanged = {props.onBoundsChanged}
streetViewControl= {props.streetViewControl}
zoomControl={false}

they aren't working. any solutions for this?

Fixed: Sorry, I just need to indicate zoomControl and streetView control inside the options property

Sounds good, glad you were able to figure it out @PinkPanda17 👍

For those wondering how to set options:
  <GoogleMap
    defaultZoom={...}
    defaultCenter={...}
    options={{streetViewControl: false, mapTypeControl: false}}
  >


Automatically pull android tombstone files

In https://github.com/flutter/flutter/issues/6503#issuecomment-256150692 @eseidelGoogle says that on Android there are tombstone files saved after crashes and that the logs mention them. We should have the tool automatically notice these messages and save the tombstone files locally for ease of uploading to bugs.

I'm not sure this is really necessary after https://github.com/flutter/flutter/pull/12923 - that change gives you everything you need to symbolicate a crash, which is, AFAICT, all you'd want the tombstone for anyway.
Do we still need this bug?


Clarify relationship with jsonfield2 and django-jsonfield

This project is published on Pypi as jsonfield. There are other packages with similar names, all for Django, which is confusing:

jsonfield2 on Pypi
django-jsonfield on Pypi

The similar names are causing confusion. For example, have a look at this comment https://github.com/django-notifications/django-notifications/issues/269#issuecomment-585088457 in the project django-notifications.
Please add to README.rst a warning pointing out the naming confusion. It also looks like Pypi packages jsonfield and jsonfield2 are supposed to be merged now?

Hi @Flimm. Here are the details:

This package has always been jsonfield on PyPI, but previously, the GH repository was django-jsonfield.
This caused confusion, as there is also the django-jsonfield project on PyPI.
jsonfield wasn't actively maintained, so I created a fork called jsonfield2.
However, I was recently granted ownership of jsonfield, merged my fork in, and then archived my fork as it was no longer necessary.
Lastly, I changed the repo name from django-jsonfield to jsonfield to be consistent with the project name.

Also, I removed the paragraph about the jsonfield/django-jsonfield confusion, because the naming conflict is no longer there.

Thank you for renaming the Github repo to jsonfield to match the Pypi name, that does help remove opportunities for confusion.
Since you're the maintainer of Pypi package jsonfield2, could you release an update on Pypi, updating the README of jsonfield2, to make it clear that it is deprecated in favour of jsonfield? Right now, if you visit https://pypi.org/project/jsonfield2/ , that isn't clear at all. It says it is a fork of django-jsonfield,  meaning the Pypi package jsonfield, and there is no mention that  jsonfield2 is no longer needed since it has been merged back into jsonfield.
That would really help.

Good point. I updated the README on GitHub, but hadn't push that to PyPI. That should be fixed now. Thanks!

Thank you!


Implement vote endpoints

A voting needs to have an endpoint to count votes.
A proper endpoint could be something like /voting/1/vote. Youtube uses /videos/rate but they have a different kind of voting though.
vote is an action and ReST should not expose actions.

Done.


Remove output columns in physical scan of Hudi table

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：
#3541
Problem Summary(Required) ：
Fix compile error due to incomplete modification of #3541

@HangyuanLiu @kangkaisen PTAL


// Minor Issues

<------ Some suggestion for Zee5_clone -------->

font-family (import fonts from google)
use % or vh instead of px
rounded-corners (border-radius)
align items in the header and body (equal spacing) ---> looks cleaner & balanced
fill empty spaces
Optional: Make it responsive by using anchor, href tags to make the cover picture switching...

<---------- Notes by seniors ------->
// don't use px (you should know the reason of not using)
// when to use and when not to use positions(absolute,fixed,sticky and relative)
// efficiently use flexbox  (all properties under display:flex)
// must know :- difference between margin and padding (when to use margin and when to use padding)
// take a basic understanding of css selectors
// box-sizing:border-box
// take a basic understanding of class and id (difference)
// vmax
// vmin
// vh , vw

issue_fixed


Chip: Tap/Click Targets

Is your feature request related to a problem? Please describe
As a convenience, especially on mobile, we’d like to use a tap/click on a filter chip to trigger the display of the configuration panel for that particular type of filter, saving a couple of taps/clicks for the user and a clear, direct relationship between the chip and the filters configuration panel.
This would require the ability to have 2 separate tap/click targets on a chip: 1) a target for action/event triggering, and 2) a target for deleting the chip.
Roadblock: Currently on mobile, the “delete chip” action is triggered by tapping anywhere on a chip.
Describe the solution you'd like
The ability to have 2 separate tap/click targets on a chip: 1) a target for action/event triggering, and 2) a target for deleting the chip.
See the Figma mockup.
https://www.figma.com/file/ITHqvarhTtYal257Z4JzCB/Share-with-DS-Team?type=design&node-id=1074-14863&mode=design&t=f1GBRRudhd4O9aj8-4
Provide evidence this is a needed component
No response
Describe alternatives you've considered
No response
Do you have anything already created for this that we can use?
None
Are you currently using this proposal inside your own service
None
Are you able to assist to bring the feature to reality?
yes
Additional context
No response

Closing this story as it's already covered by #1333


Leverage if blocks in Markdown

We are utilizing if blocks, based on parameters/etc, in our templates and shortcodes.
{{ if isset .Site.Params "includeinfoaboutx" }}

However, there are some cases where we need to modify the content itself -- in the Markdown file, for example if we have the parameter includeinfoaboutx set, then we want to show a specific block of text, if not, we may want to display a second block of text instead.
This would work fine if it was in a template and we wrote in HTML, but this doesn't work in a Markdown file used as content.
We would like to be able to do something like the following, in a Markdown file:
{{ if isset .Site.Params "includeinfoaboutx" }}

Here we will discuss the feature X and give some examples.

> NOTE: We will want to use markdown inside this block.

{{ else }}

Here we say that feature X is not documented in this version.

{{ end }}

https://hugodocs.info/content-management/shortcodes/

Please use http://discuss.gohugo.io/ for questions/troubleshooting. Also see  Hugo Documentation.


Update k8s.io/ja/docs/setup/multiple-zones/

This is a...

[x] Feature Request
[ ] Bug Report

Problem:
Outdated content content/ja/docs/setup/multiple-zones.md.
content/en/docs/setup/multiple-zones.md 95 insertion(+), 28 delettion(-)

Proposed Solution:
Update content content/ja/docs/setup/multiple-zones.md.
For details, please execute the following command.
git diff 551489f 7b07d19 -- content/en/docs/setup/multiple-zones.md

Page to Update:
https://kubernetes.io/ja/docs/setup/multiple-zones/

やります
/assign

/close


Lazily reduce problem data tensor

Reduce problem data tensor on first call to apply parameters.
An intermediate ParamConeProg is constructed when canonicalizing cone
programs; this ParamConeProg is never actually evaluated, so reducing
its tensor is unnecessary.
@sbarratt

@SteveDiamond @sbarratt The derivative tests are failing with
File "C:\conda\envs\testenv\lib\site-packages\ecos.py", line 62, in solve
1898    return _ecos.csolve((m,n1,p), c, data, indices, colptr, h, dims, A.data, A.indices, A.indptr, b, **kwargs)
1899TypeError: 'eps' is an invalid keyword argument for this function
This appears to be related to the recent release of diffcp, which included ECOS. Could one of you look into it?

Ah, whoops, looks like eps is no longer a valid argument if the solver is
"ECOS".
Shane
On Tue, Oct 20, 2020 at 11:09 AM Akshay Agrawal<EMAIL_ADDRESS>wrote:

@SteveDiamond https://github.com/SteveDiamond @sbarratt
https://github.com/sbarratt The derivative tests are failing with
File "C:\conda\envs\testenv\lib\site-packages\ecos.py", line 62, in solve
1898 return _ecos.csolve((m,n1,p), c, data, indices, colptr, h, dims,
A.data, A.indices, A.indptr, b, **kwargs)
1899TypeError: 'eps' is an invalid keyword argument for this function
This appears to be related to the recent release of diffcp, which included
ECOS. Could one of you look into it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cvxgrp/cvxpy/pull/1151#issuecomment-713042886, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7LUGPVHPJM7O4NETDIDTLSLXG6DANCNFSM4SYVQZMA
.

Not sure what to do here. We have a naming clash with the solver keyword. It's used in cvxpy and in diffcp.

Not sure what to do here. We have a naming clash with the solver keyword. It's used in cvxpy and in diffcp.

That's unfortunate.
I guess we can't really change CVXPY's interface. Can we change the keyword argument name in diffcp to method, instead of solver?

Not sure what to do here. We have a naming clash with the solver keyword. It's used in cvxpy and in diffcp.

That's unfortunate.
I guess we can't really change CVXPY's interface. Can we change the keyword argument name in diffcp to method, instead of solver?

er or I guess solve_method, since CVXPY also uses method

Rebased on top of b8a54937311063db42ac9a49e8ddce5520920b42 to retrigger the build ...


Battery test

Hello,
I made 2 tests with a full charged batteries:

LiPo 3.7v 240mAh - After 24h with 3 m sync period consumed only 35%.
LiPo 3.7v 120mAh - After 18h with 5 m sync period consumed 90% and the system sttoped to communicate.

Do you think this is a normal behaviour ?
Regards,
Hugo.-

Hi Hugo,
I have been using a 150 mAh lipo for a long time. I put the libreMonitor on ever morning and take it off when I go to bed (because I don't want to lie on it and possibly brake it, since I still don't use a case) and then I charge it over night. With a reading every two minutes even on long days with up to 18 or 20 hours it still worked when I took it of. And this even though the Simblee keeps a permanent bluetooth connection to the iPhone between the readings (with "Simblee_ULPDelay" command).
I put your and my values in the following table. Unfortunately I don't have a means to measure the remaining capacity for my lipo so I just assumed 100 percent.

Hugo 1 (RFduino)
Hugo 2 (RFduino)
Uwe (Simblee)

lipo energy [mAh]
240
120
150

used energy [%]
35
90
100

used energy [mAh]
84
108
150

usage time [h]
24
18
18

delay between readings (min)
3
5
2

reading frequency [1/h]
20
12
30

number of readings in usage time
480
216
540

energy consumption per reading [mAh]
0,175
0,5
0,28

So your large lipo performs very well in comparison to mine but your smaller lipo could do better. Overall it looks reasonable to me. Since I don't know what changes you possibly made: Please note that this comparison is only valid on the assumption that you read and transfer the same amount of data.
Regards,
Uwe

Hi Uwe,
Thank you very much for your comparison table.
I will also test for 2 minutes.
Do you find that there is any side effect with 1 minute besides the battery faster consume.
Yes I used always the same sample data to avoid mistaken results.
I agree that my large lipo performs very well (more that what was expected), however my smaller lipo is not enough (I wanted 24h / one day charge) for the same 3 minutes (at most).
Shouldn't the smaller lipo performance as 50% comparing to the bigger one ?
I mean, for he same 24h (3 minutes delay), consume 70% energy ?
Regards,
Hugo.

Hi Hugo,
I never tried a one minute interval. I just don't think it is necessary. I like the two minutes pretty much. Three minutes seems reasonable, too, but five minutes is just to long for me.
I am not sure if the one minute interval will have side effects.
Regarding side effects: Rarely, but it sometimes happens that I don't get a response from LibreMonitor any more and the Freestyle Libre Reader also refuses to provide values. Usually, after a while everything works fine again. And usually I take the LibreMonitor of when this happens. I do not know why this happens and I don't know if this is caused by LibreMonitor at all. But for sure I know that I had observed this with sensors before having started to use LibreMonitor, too. Same with sensors that completely failed. Just got two such cases recently with sensors that were very close to their expiry date. But also did have this in the early days without LibreMonitor.
To sum up: If you are keen on a one minute interval you have to try yourself. I personally would not expect problems, but who knows. And yes, I'd be interested in the results.
Lipo: Yes, I would have expected the small lipo to perform more equally, too. Maybe it has a different discharge capability (if this is of influence) and it could also be just a bad lipo. I guess that to be really sure about lipo performance and requirements more systematic tests will be necessary.
Regard
Uwe

Hi Uwe,
"I never tried a one minute interval. I just don't think it is necessary. I like the two minutes pretty much. Three minutes seems reasonable, too, but five minutes is just to long for me."
I agree with you.
"I am not sure if the one minute interval will have side effects."
Stop working for example but I will use 2 or 3 minutes.
"Regarding side effects: Rarely, but it sometimes happens ... "
I'm doing tests and experience exactly the same behaviour (I see that I'm not alone here :))
"Lipo: Yes, I would have expected the small lipo to perform more equally, too. Maybe it has a different discharge capability (if this is of influence) and it could also be just a bad lipo. I guess that to be really sure about lipo performance and requirements more systematic tests will be necessary."
I have been reading about discharge capability and in theory yes, it can influence a little but I don't believe that much. I bet in got bad 120mAh Lipo and a very good 240mAh one.
I'm expecting to receive tomorrow a new 150mAh (with the same discharge capability as the 240mAh and let's see how performe this one).
Regards,
Hugo.

A new test with a new LiPo 150mAh.
After 24h with 3m interval it keep working with full charge (of course it's not possible and a read battery level issue) but working.
A will run a new 24h test with the same 150mAh LiPo but now with 2m interval.

What about safety of LiPo using?
The device is fixed on the arm all the time. Is this not dangerous?
I mean a sudden ignition.

I do use a regulated Lipo and I haven't had any bad experience so far. Neither have I heard of any bad experience from similar projects like LimiTTer.


Adding pre-existing go instrumentation plugins

Adding

Macaron
Labstack
Mongodb

Could you add a language field, as in the README? Thanks!

Language field added to the plugins I added, but also to the preexisting plugins owned by the Otel-go repo (which were also missing).


AWS Sagemaker CloudFormation: Error Template validation error: Internal Failure

As the title says, the template does not launch. Tried in any of the provided regions.
The template, however, works when manually loaded through s3 link

Could you ask on the forum, and if everyone else is seeing the same problem, reopen this? If it's specific to your account, best off asking aws.


WIP implementation of caching

Doesn't compile yet, just showing the work in progress for #149
This is a "minimal diff" version that doesn't cache everything but at least introduces some caching. I think some refactoring is required to fully cache all the expensive-but-cachable stuff.
I basically moved three DB queries, the GetBucket call, and the parsing of _redirects and _headers into populateCache mostly unmodified. The last DB query may require refactoring all callers of AnalyticsVisitFromRequest.
This PR is also based on the changes in #150 so there's duplicate diffing happening.

Overall looks good to me!  Nothing to comment here, I like the general approach.

@neurosnap Hmm I think it's dawning on me now that using an in-process cache may not work because pgs/web and pgs/ssh are two separate processes. So I can't easily tell pgs/web to clear the cache when something happens in pgs/ssh, like a new _headers file being uploaded or a project being deleted.
Any preferences for what to do about that? Deploying an out-of-process cache like redis feels a little silly for avoiding DB queries since postgres's in-memory caching for reads are comparable to redis's read performance: https://www.cybertec-postgresql.com/en/postgresql-vs-redis-vs-memcached-performance/
Perhaps I should wait to see how enabling DNS caching affects things before proceeding. Some timing info from production would be helpful for knowing where to focus after that.

Another option could be something like https://github.com/caddyserver/cache-handler to just cache response bodies. It apparently has an API that can be used to clear the cache, which in theory could be called from pgs/ssh.

Oh, interesting!  I think it might be worth giving that caddy module a shot as it would move the responsibility of caching outside of our application code.  So long as we have the ability to purge the cache and it has the granularity we need.
Requirements:

Ability to purge project cache
Ability to purge user cache (optional but nice)
Ability to purge entire cache

If you would find it useful, feel free to email us at<EMAIL_ADDRESS>or join our irc channel (#pico.sh) on libera.chat if you want more active pairing.

Moved the commit that limits file sizes to #153 and will close this since in-process caching is likely a dead end.


Question about type method

Hello
Out of curiosity I saw in the source code of type:
var type = _curry1(function type(val) {
  return val === null
    ? 'Null'
    : val === undefined
      ? 'Undefined'
      : Object.prototype.toString.call(val).slice(8, -1);
});

you do an additional check to get the type of null and undefined, but I saw that you can get as well 'Null' or 'Undefined' with simply:
var type = _curry1(function type(val) {
  return Object.prototype.toString.call(val).slice(8, -1);
})

Is there any reason for this?
Thanks

I'm not certain that this was the case at the time the function was written, and I suspect that there may be environments where it would still fail.  but I don't recall any specifics.
However, unless we can find such, a PR to change this would be welcome.

@CrossEye Hey, thanks for the answer.
I understand, I could take a look at it when I have some time.
Thanks