Modify naming flags

Delegate, secret are a bit confusing in the current description:

We should modify delegate to bakerAddress so it's very clear that it's the baker's address and not the payout's wallet. Also, the fact that there is no need to specify the Payout Wallet Public Key because of passing the PK should be made clear to the user by using secretPayoutWallet.
Naming proposal:
i). bakerAddress:  Baker's address, the node that is running the Tezos Bakery.
ii). delegators: the different addresses that are delegating to the Baker's address.
iii). payoutWallet & secretPayoutWallet: the wallet that is sending payouts to delegator addresses. We can use secretPayoutWallet for "encrypted secret key of the wallet paying (e.g. --secret=)"
To look have something like that:
./payman payout \
    --bakerAddress=tz3gN8NTLNLJg5KRsUU47NHNVHbdhcFXjjaB \
    --secretPayoutWallet=edesk1Qx5JbctVnFVHL4A7BXgyExihHfcAHRYXoxkbSBmKqP2Sp92Gg1xcU8mqqu4Qi9TXkXwomMxAfy19sWAgCm \
    --password=abcd1234 \
    --cycle=160 \
    --node=<IP_ADDRESS> \
    --port=8732 \
    --fee=0.05

@bneiluj I'm going to have to disagree with you on these changes. I want to keep the flags uniform with the official Tezos Documentation. Tezos refers to bakers as Delegates. Additionally, the tezos-client calls the secret a secret, and it's pretty self explanatory that the secret is to a wallet.
I also believe the descriptions are pretty obvious, but if there's something you believe is missing in them, I could update those.
-d, --delegate string        public key hash of the delegate that's paying out (e.g. --delegate=<phk>)
-s, --secret string          encrypted secret key of the wallet paying (e.g. --secret=<sk>)

Thanks for your feedback!

Also @bneiluj by the looks of it you are using an old version on payman. I would recommend you update to v1.0.3!

@DefinitelyNotAGoat Ok perfect. Let's just update the description. It makes sense to me.


Three-step cryptic clue not getting clue hint

Haven't there been rev updates since 3-cryptic clues released though? I don't think any of these three were changed since that point.

I'm unable to repro when hacking in the exact clue text in the plugin, so I'm closing this.
To test like I did, just apply this diff:
diff --git a/runelite-client/src/main/java/net/runelite/client/plugins/cluescrolls/ClueScrollPlugin.java b/runelite-client/src/main/java/net/runelite/client/plugins/cluescrolls/ClueScrollPlugin.java
index 24d9aad89..a18fdb89f 100644
--- a/runelite-client/src/main/java/net/runelite/client/plugins/cluescrolls/ClueScrollPlugin.java
+++ b/runelite-client/src/main/java/net/runelite/client/plugins/cluescrolls/ClueScrollPlugin.java
@@ -467,11 +467,13 @@ public class ClueScrollPlugin extends Plugin

 		if (clueScrollText == null)
 		{
-			return null;
+			// return null;
 		}

+		String clueText = "Shhhh!

Where safe to speak, the man who offers the pouch of smallest size wishes to see your alignment.

Great demons, dragons and spiders protect this blue rock, beneath which, you may find what you seek.";
+
 		// Remove line breaks and also the rare occasion where there are double line breaks
-		final String text = Text.sanitizeMultilineText(clueScrollText.getText()).toLowerCase();
+		final String text = Text.sanitizeMultilineText(clueText).toLowerCase();

 		// Early return if this is same clue as already existing one
 		if (clue instanceof TextClueScroll)
@@ -539,7 +541,7 @@ public class ClueScrollPlugin extends Plugin
 		}

 		// three step cryptic clues need unedited text to check which steps are already done
-		final ThreeStepCrypticClue threeStepCrypticClue = ThreeStepCrypticClue.forText(text, clueScrollText.getText());
+		final ThreeStepCrypticClue threeStepCrypticClue = ThreeStepCrypticClue.forText(text, clueText);

 		if (threeStepCrypticClue != null)
 		{


Unable to install python 3.10.2 on Linux Mint 20.2.

When I try to install python with the command: "asdf install python 3.10.2" I receive the following message:
python-build 3.10.2 /home/alexandre/.asdf/installs/python/3.10.2
Downloading Python-3.10.2.tar.xz...
-> https://www.python.org/ftp/python/3.10.2/Python-3.10.2.tar.xz
Installing Python-3.10.2...
WARNING: The Python bz2 extension was not compiled. Missing the bzip2 lib?
WARNING: The Python readline extension was not compiled. Missing the GNU readline lib?
ERROR: The Python ssl extension was not compiled. Missing the OpenSSL lib?
Please consult to the Wiki page to fix the problem.
https://github.com/pyenv/pyenv/wiki/Common-build-problems
BUILD FAILED (Linuxmint 20.2 using python-build 2.2.4-1)
Inspect or clean up the working tree at /tmp/python-build.20220128113543.302640
Results logged to /tmp/python-build.20220128113543.302640.log

I solved this problem by installing the dependencies below:
udo apt-get install make build-essential libssl-dev zlib1g-dev
libbz2-dev libreadline-dev libsqlite3-dev wget curl llvm
libncursesw5-dev xz-utils tk-dev libxml2-dev libxmlsec1-dev libffi-dev liblzma-dev


FieldLabel should contain the fields it labels?

It seems that FieldLabel often wraps the components it labels, so perhaps the markup needs to change for this to have an outer <div> as well as an inner <label> and a <span> for the validation message...

This is still a thing.

I think this would be covered by using Form to layout the field label and the input.


x/website: codewalk locks up scroll on initial page load for chrome

https://go.dev/doc/codewalk/functions/
On both linux and mac chrome, loading any of the codewalk pages seems to lock up scrolling of the main page.
Scrolling sidebar works.
Scrolling the main content area works and also seems to unlock whatever was preventing scrolling on the main page.
Doesn't seem to reproduce on mac safari
Chrome UA: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36

I think this is working as intended or a bug in Chrome. Scroll is prevented in the main page when continuously scrolling through the textarea. Main page scroll resumes when there is a short break between scrolling to an edge of the textarea and then scrolling again.


Multi font + Swifty

addressing #23, #24, #2 and maybe #13 (haven’t thoroughly tested yet).
You can see the newly generated font file format in Samples/Pods/Iconic/Source/FontAwesomeIcon.swift
Also moved catalog hierarchy.
Changed Sample swift controllers to use the new style API.
Decided not to introduce new env variable for multi-font, instead the  Iconizer.sh is smart enough to check if the path is a ttf file or directory, and act accordingly for multi-fonts.

shoot... didn't update the tests yet... cancel this for now until I fix the tests...


SWTG024AS-v2-RTL8372N

It's the same PCB number as the other one, but the main chip is an RTL8372N and seems to have an empty pad for an RTL8221B. Merchants claim that the new power consumption is lower heat is smaller, but after testing, the power consumption is the same, and heat is smaller just remove the thermal pads between the pcb and the case.

Awesome! Thank you for the added details as well, very much appreciated 👍🏻


Generator loss starts around 2000 and never decreases

i am working on Anomaly generation from Normal data.The dataset consists of 41 features ,all integers so i have padded the number 255  23 times to make it  8x8image.. discriminator loss keeps fluctuating ... even after 1000 iterations the Gloss is around 3000 range.

@supre3th I am sorry that I have no experience on your special task.

thanks for the reply


Blur mod not blurring the background help

hello! I installed the blur mod and it's not doing the blurring effect, it is showing the gradient effect though, not sure how to fix this. I have optifine with bsl shaders and use curseforge for my mods (not sure if that matters) and have fast render and antialiasing off.
ingame screenshot
https://imgur.com/a/VrapRmE
mod options
https://imgur.com/a/4lHfoTA
https://imgur.com/a/oaMRf6I

you have to open the imgur links in google to look at them


KeyError: 'im_info' and 'gt_boxes' when running 'example_train_slurm.sh'

Running the 'demo.py' works fine, but running 'example_train_slurm.sh' returns the following key error:

Traceback (most recent call last):
File "/local/s174/rgz_rcnn/tools/train_net.py", line 105, in
max_iters=args.max_iters, start_iter=args.start_iter)
File "/local/s174/rgz_rcnn/tools/../lib/fast_rcnn/train.py", line 333, in train_net
sw.train_model(sess, max_iters, start_iter=start_iter)
File "/local/s174/rgz_rcnn/tools/../lib/fast_rcnn/train.py", line 217, in train_model
self.net.im_info: blobs['im_info'],
KeyError: 'im_info'

The traceback refers to this code in "rgz_rcnn/lib/fast_rcnn/train.py":
210             # get one batch
211             blobs = data_layer.forward()
212
213             # DEBUG
214             print(blobs.keys())
215             # Make one SGD update
216             feed_dict = {self.net.data: blobs['data'],
217                           self.net.im_info: blobs['im_info'],
218                          self.net.keep_prob: 0.5,
219                          self.net.gt_boxes: blobs['gt_boxes']}

I added the debug statement on line 214, which returns:

['bbox_inside_weights', 'labels', 'rois', 'bbox_targets', 'bbox_outside_weights', 'data']

Suggesting that not only 'im_info' but also 'gt_boxes' is a non existent key in the data_layer.
Any suggestions on what the problem might be?

Looks like the data layer is not reading the data set properly.  Before delving into the code further, just wondering how did you run the 'example_train_slurm.sh'? The script was made to run on a cluster, where the Python (TF) environment is pre-installed. So it won't invoke your python virtual environment as per the READ.ME. Do you mind shared your version of 'example_train_slurm.sh' somewhere on git?
Thanks!

Sure.
I changed 'example_train_slurm.sh' to 'example_train.sh', which results in the keyerror (see crash_log_example_train.txt for the full output):
#!/bin/bash

export CUDA_VISIBLE_DEVICES=7
source activate py2-tensorflow

RGZ_RCNN=/local/s174/rgz_rcnn

python $RGZ_RCNN/tools/train_net.py \
                    --device 'gpu' \
                    --device_id 0 \
                    --imdb rgz_2017_trainD4 \
                    --iters 80000 \
                    --cfg $RGZ_RCNN/experiments/cfgs/faster_rcnn_end2end.yml \
                    --network rgz_train \
                    --weights $RGZ_RCNN/data/pretrained_model/imagenet/VGG_imagenet.npy

The example_test_cpu.sh works fine and is adapted to look like this:
# please change to your own python virtual environment path
export CUDA_VISIBLE_DEVICES=7
source activate py2-tensorflow
RGZ_RCNN=/local/s174/rgz_rcnn

python $RGZ_RCNN/tools/test_net.py \
                    --device 'cpu' \
                    --device_id 0 \
                    --imdb rgz_2017_testD4 \
                    --cfg $RGZ_RCNN/experiments/cfgs/faster_rcnn_end2end.yml \
                    --network rgz_test \
                    --weights $RGZ_RCNN/data/pretrained_model/rgz/D4/VGGnet_fast_rcnn-80000 \
                    --comp

Irrespective of the --device flag, 'example_test_cpu.sh' will actually always run on the gpu:

I tensorflow/core/common_runtime/gpu/gpu_device.cc:885] Found device 0 with properties:
name: GeForce GTX 980 Ti
major: 5 minor: 2 memoryClockRate (GHz) 1.076
pciBusID 0000:8a:00.0
Total memory: 5.94GiB
Free memory: 5.83GiB
I tensorflow/core/common_runtime/gpu/gpu_device.cc:906] DMA: 0
I tensorflow/core/common_runtime/gpu/gpu_device.cc:916] 0:   Y
I tensorflow/core/common_runtime/gpu/gpu_device.cc:975] Creating TensorFlow device (/gpu:0) -> (device: 0, name: GeForce GTX 980 Ti, pci bus id: 0000:8a:00.0)
Loading model weights from /local/s174/rgz_rcnn/data/pretrained_model/rgz/D4/VGGnet_fast_rcnn-80000


Question about "filename"

What exactly is filename used for? Module caching (i.e. prevents string-loaded module with filename "X" from being reloaded)? If so, does it need to be a "real" filename or could it be any unique string?
And/or is it used to determine the relative file system root for 'require' statements within the string-loaded code?

I think this was answered in https://github.com/floatdrop/require-from-string/issues/11#issuecomment-330143887


refactor: improve performance of backtesting

Include histogram of returns
Limit dataframe in each iteration
Change avg price calculation

Codecov Report
Patch coverage: 78.64% and project coverage change: +0.92 :tada:

Comparison is base (0043d08) 40.40% compared to head (23e01f8) 41.32%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #276      +/-   ##
==========================================
+ Coverage   40.40%   41.32%   +0.92%
==========================================
  Files          19       19
  Lines        2896     2911      +15
==========================================
+ Hits         1170     1203      +33
+ Misses       1650     1636      -14
+ Partials       76       72       -4

Impacted Files
Coverage Δ

model/order.go
100.00% <ø> (ø)

plot/chart.go
39.69% <42.85%> (-0.37%)
:arrow_down:

order/controller.go
54.10% <77.50%> (+3.24%)
:arrow_up:

model/model.go
73.58% <100.00%> (+13.98%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


allowMultiple=false doesn't prevent array of activeItems

Probably similar to #51
Example:
<Accordion allowMultiple={false} activeItems={[0,1,2]}>
</Accordion>

When the page first loads then 0, 1, 2 are expanded
Click item 1 it will close and others (multiple) will remain open
Click item 1 again it will re-open, and then the others will close

Possible solutions:

warn/error if passing an array when allowMultiple is false
grab the first entry, ignore rest of array
don't worry about it this isn't a very serious issue

fixed with #74


pre-commit: add flake8 for python

This will fail for now, until a couple of the ongoing PRs are merged first, e.g. https://github.com/GoogleChromeLabs/chromium-bidi/pull/492


feat: handle license files from clab topo (clabernetes/clabverter)

title. need to handle clabverter creating configmap w/ license files (ex for sros) and also make sure clabernetes handles the mounting of those configmaps as well as making sure that field is copied into the sub topology

closing, follow up in #23


[Recognizer] Setup CD

After this PR, a new docker Recognizer docker image will be created, published and deployed every time we create a tag recognizer-vX where X can be anything e.g. v0.1.0 v0.1.0-32dfeg v0.1.0-dev.
Docker image can be pulled with docker pull ghcr.io/elixir-webrtc/apps/recognizer:0.1.0 (so with v stripped) or using latest.
Deployed version is available under https://recognizer.elixir-webrtc.org

Btw, there's something wrong with the tab title on the deployed version

Wasn't it Home <dot> Recognizer before?

@LVala Github workflows cannot be nested so I prefixed them with __CI__ and __CD__ for some kind of sorting and easier navigation

@LVala

Wasn't it Home  Recognizer before?

Fixed


use Process instead of Thread to speed up the build-all option

Use Process to replace Thread to speed up the scl scenario build-all --clean <scenario_dir> runtime.
Before:
(.venv) sqy201x@Patrick-Desktop:~/SMARTS$ time scl scenario build-all --clean ./scenarios/intersections/
build-scenario ./scenarios/intersections//2lane
build-scenario ./scenarios/intersections//2lane_circle
build-scenario ./scenarios/intersections//4lane
build-scenario ./scenarios/intersections//6lane
build-scenario ./scenarios/intersections//4lane_t
Waiting on scenarios/intersections/2lane ...
Warning: Speed of turning connection 'edge-north-NS_0->edge-west-EW_0' reduced by 44.96 due to turning radius of 4.62 (length=5.00, angle=90.00).
Warning: Speed of turning connection 'edge-north-NS_2->edge-east-WE_2' reduced by 40.49 due to turning radius of 16.45 (length=20.48, angle=90.00).
Warning: Speed of turning connection 'edge-east-EW_0->edge-north-SN_0' reduced by 44.96 due to turning radius of 4.62 (length=5.00, angle=90.00).
Warning: Speed of turning connection 'edge-east-EW_2->edge-south-NS_2' reduced by 40.49 due to turning radius of 16.45 (length=20.48, angle=90.00).
Warning: Speed of turning connection 'edge-south-SN_0->edge-east-WE_0' reduced by 44.96 due to turning radius of 4.62 (length=5.00, angle=90.00).
Warning: 8 total messages of type: Speed of % connection '%' reduced by % due to turning radius of % (length=%, angle=%).
Warning: Speed of turning connection 'edge-north-NS_0->edge-west-EW_0' reduced by 41.67 due to turning radius of 12.63 (length=15.48, angle=90.00).
Warning: Speed of turning connection 'edge-north-NS_0->edge-east-WE_0' reduced by 40.45 due to turning radius of 16.57 (length=20.64, angle=90.00).
Warning: Speed of turning connection 'edge-east-EW_0->edge-north-SN_0' reduced by 41.67 due to turning radius of 12.63 (length=15.48, angle=90.00).
Warning: Speed of turning connection 'edge-east-EW_0->edge-south-NS_0' reduced by 40.45 due to turning radius of 16.57 (length=20.64, angle=90.00).
Warning: Speed of turning connection 'edge-south-SN_0->edge-east-WE_0' reduced by 41.67 due to turning radius of 12.63 (length=15.48, angle=90.00).
Warning: 8 total messages of type: Speed of % connection '%' reduced by % due to turning radius of % (length=%, angle=%).
Waiting on scenarios/intersections/2lane_circle ...
Waiting on scenarios/intersections/4lane ...
Waiting on scenarios/intersections/6lane ...
Waiting on scenarios/intersections/4lane_t ...

real    0m10.042s
user    0m13.173s
sys     0m12.675s

After:
(.venv) sqy201x@Patrick-Desktop:~/SMARTS$ time scl scenario build-all --clean ./scenarios/intersections/
build-scenario ./scenarios/intersections//2lane
build-scenario ./scenarios/intersections//2lane_circle
build-scenario ./scenarios/intersections//4lane
build-scenario ./scenarios/intersections//6lane
build-scenario ./scenarios/intersections//4lane_t
Waiting on ./scenarios/intersections//2lane ...
Warning: Speed of turning connection 'edge-north-NS_0->edge-west-EW_0' reduced by 44.96 due to turning radius of 4.62 (length=5.00, angle=90.00).
Warning: Speed of turning connection 'edge-north-NS_2->edge-east-WE_2' reduced by 40.49 due to turning radius of 16.45 (length=20.48, angle=90.00).
Warning: Speed of turning connection 'edge-east-EW_0->edge-north-SN_0' reduced by 44.96 due to turning radius of 4.62 (length=5.00, angle=90.00).
Warning: Speed of turning connection 'edge-east-EW_2->edge-south-NS_2' reduced by 40.49 due to turning radius of 16.45 (length=20.48, angle=90.00).
Warning: Speed of turning connection 'edge-south-SN_0->edge-east-WE_0' reduced by 44.96 due to turning radius of 4.62 (length=5.00, angle=90.00).
Warning: 8 total messages of type: Speed of % connection '%' reduced by % due to turning radius of % (length=%, angle=%).
Warning: Speed of turning connection 'edge-north-NS_0->edge-west-EW_0' reduced by 41.67 due to turning radius of 12.63 (length=15.48, angle=90.00).
Warning: Speed of turning connection 'edge-north-NS_0->edge-east-WE_0' reduced by 40.45 due to turning radius of 16.57 (length=20.64, angle=90.00).
Warning: Speed of turning connection 'edge-east-EW_0->edge-north-SN_0' reduced by 41.67 due to turning radius of 12.63 (length=15.48, angle=90.00).
Warning: Speed of turning connection 'edge-east-EW_0->edge-south-NS_0' reduced by 40.45 due to turning radius of 16.57 (length=20.64, angle=90.00).
Warning: Speed of turning connection 'edge-south-SN_0->edge-east-WE_0' reduced by 41.67 due to turning radius of 12.63 (length=15.48, angle=90.00).
Warning: 8 total messages of type: Speed of % connection '%' reduced by % due to turning radius of % (length=%, angle=%).
Waiting on ./scenarios/intersections//2lane_circle ...
Waiting on ./scenarios/intersections//4lane ...
Waiting on ./scenarios/intersections//6lane ...
Waiting on ./scenarios/intersections//4lane_t ...

real    0m5.897s
user    0m13.309s
sys     0m5.346s

I think we will want to update the CHANGELOG.


Theme support

Is it possible to use this package for themes in stead of plugins? I would love to have this functionality with my custom theme, that depends on some plugins that need to be installed and active.

The theme should rely so specifically on the plugins. You can use this package, but because there's no real "booting" procedure of the theme it will be difficult to hold it off like in the plugin. You can display the notice in admin though

My theme has it's own boot mechanism, and plugins are only called if they are actually present, by checking the plugin base class.
I'll give it a try, and will document and share my findings here.

I think you should be good to go then! Please share your findings, I'm very curious.


Add FastifyRouteHandlerTypebox type and example

Description
Piggybacking on the existing FastifyRequestTypebox and FastifyReplyTypebox in the docs, this PR adds a FastifyRouteHandlerTypebox that will automatically infer the request and reply types for any non-inline route handler.
Instead of just documenting the type, this PR exports the new type directly to make this process as easy and painless for users - as the typescript needed to override the TypeProvider on Fastify types can be pretty confusing for new users.
I've removed the documentation for FastifyRequestTypebox and FastifyReplyTypebox since they are no longer needed if the handler function type is set, but we can keep them (or add them as exports as well) if that's something we want/need.
Proof this works:

Thanks!
Checklist

[x] run npm run test and npm run benchmark
[x] tests and/or benchmarks are included
[x] documentation is changed or added
[x] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

Thanks for opening a PR! Can you please add a unit test? We use tsd for testing the types: https://github.com/fastify/fastify-type-provider-typebox/tree/main/types.

for no activity


B20449-MAIN-nts ntsr missing shipment num

Agility ticket
B20449
INT PR
13391
Summary
After a customer has created a move, they may review the move by clicking the "review" button at the bottom of the page.  Regardless whether the move was submitted or not, the shipment number of the shipments under the "move setup" section were empty.  The goal of the story was to fix that.
How to test

Customer:

Create a move with an NTS and NTS-R shipment.
Submit the move
Click the "Review Request" button at the bottom
Scroll down to the "Move Setup" section.
Confirm both moves have a shipment number.

ANDI Screenshots

Shipment Number added to the UI has no action item.
App Screenshots

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 7f46ab40bbcd8102a1bd44aa6f02613299843c26


Video in Meetings is broken

This issue is plaguing many people in my organization:
https://techcommunity.microsoft.com/t5/microsoft-teams/new-teams-video-freezing/m-p/3925515

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


proposal: doc: addressing inaccessible links on CN site

Many of the external links on golang.google.cn are inaccessible from Mainland China (e.g. *.golang.org, *.blogspot.com, *.googlesource.com), which might cause some troubles for Chinese developers.
Directly removing all inaccessible links would lead to situations like: "For more details, please check out this post" (while there isn't a link, nor is it clear which post it is). Instead, we can keep those links and automatically render a tooltip for blacklisted URLs that is shown if you put your mouse over it (a hover overlay, like tensorflow.google.cn, put mouse over the Google logo in the company list to test)
The other route we could take is to separate files, like go_faq.zh.html, and let them slowly be translated by the community. It would be nice to have Chinese translations in the future. We'd have to remember to add content to both in the future, though.
See the discussion on https://go-review.googlesource.com/c/go/+/89215 for more context.
/cc @chenglu for checking CN site policies   @andybons @bradfitz

This is not really a "proposal"

The proposal process should be used for any notable change or addition to the language, libraries and tools.

I've changed this to a plain issue and added a NeedsDecision label.

-1
No, I don't think it's a problem for Chinese developers.

I agree that it isn't a problem for developers.
But I don't know whether the PRC government will be angry about those links.
Maybe Google want to remove those links only to reduce trouble.

We're in the process of revamping our web site. Let's revisit this when that effort starts in earnest.


Re #164 - Crontab time syntax

what todo about crons that never got a chance to fire ? like if the server was turned off etc


I can't use IMU in cartographer

only Lidar can be used to built map,but when i  joined the IMU, there is an error:
[ INFO] [1489563685.321344447]: I0315 15:41:25.000000 16889 map_builder_bridge.cc:37] Added trajectory with ID '0'.
[ WARN] [1489563685.525837849]: W0315 15:41:25.000000 16889 tf_bridge.cc:51] Lookup would require extrapolation at time<PHONE_NUMBER>.525495000, but only time<PHONE_NUMBER>.530481674 is in the buffer, when looking up transform from frame [imu] to frame [base_link]
[ WARN] [1489563685.528745250]: W0315 15:41:25.000000 16889 tf_bridge.cc:51] Lookup would require extrapolation at time<PHONE_NUMBER>.477205200, but only time<PHONE_NUMBER>.529379831 is in the buffer, when looking up transform from frame [laser] to frame [base_link]
F0315 15:41:25.544420 16889 sensor_bridge.cc:67] Check failed: sensor_to_tracking->translation().norm() < 1e-5 The IMU frame must be colocated with the tracking frame. Transforming linear acceleration into the tracking frame will otherwise be imprecise.
[FATAL] [1489563685.544553362]: F0315 15:41:25.000000 16889 sensor_bridge.cc:67] Check failed: sensor_to_tracking->translation().norm() < 1e-5 The IMU frame must be colocated with the tracking frame. Transforming linear acceleration into the tracking frame will otherwise be imprecise.
 Transforming linear acceleration into the tracking frame will otherwise be imprecise.

Change your tracking frame to be the IMU and that should fix it.

NB: If you are using Gazebo, there are a crucial issue:
Locate where your slam package is (for me it is done via 'rospack turtlebot3_slam)
edit 'config/turtlebot3_lds_2d.lua' in that location:
on line #23 you will find an "Easter egg" from developers:
tracking_frame = "imu_link", -- imu_link, If you are using gazebo, use 'base_footprint' (libgazebo_ros_imu's bug)
using that tip: replace "imu_link" with "base_footprint". Without this fix, there will be constant failure mentioning that the IMU frame has to be collocated with your 'tracking frame'.

but when I replace "imu_link" with "base_footprint" and roslaunch , there show error  W0527 10:09:53.000000 26453 tf_bridge.cc:52] "base_footprint" passed to lookupTransform argument target_frame does not exist.
so  how can I do in the next ?

In addition: if you use turtlebot3_slam in Gazebo, you must use param
<arg name="configuration_basename" default="turtlebot3_lds_2d_gazebo.lua"/>
instead of <arg name="configuration_basename" default="turtlebot3_lds_2d.lua"/>  in turtlebot3_slam.launch. It fix this error.

Hi, I am facing the same issue. I am using Cartographer on a rosbag offline, recorded from Gazebo on a Husky robot.  Cartographer only works when I set 'tracking frame' into base_link, does this mean that I am not using IMU?
I have tried to modify the original husky urdf so that its colocated with the tracking frame. I set the imu_link to share the same origin as the base_link, but am still facing the same error. Would really appreciate if anyone can help me point out if im doing anything wrong, thank you in advance!
Below are some files to better understand my setup:
Husky.lua
Modified Husky URDF


⚠ Bofrost.at has degraded performance

In 7426cb3, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2122 ms

Resolved: Bofrost.at performance has improved in 2e181e9.


Failed to parse SourceMap

I'm running into an issue when trying to create a service worker for my CDN assets. Here's what my Gulp task looks like:
'use strict'

const gulp = require('gulp')
const swPrecache = require('sw-precache')

const runtimeCaching = [
  {
    urlPattern: /^https:\/\/cdnjs\.cloudflare\.com/,
    handler: 'networkFirst'
  }
]

gulp.task('serviceWorker', (callback) => {
  swPrecache.write("build/service_worker.js", { runtimeCaching }, callback)
})

When I load the service worker into my browser, I get this error:
Failed to parse SourceMap: http://localhost:3000/build/sw-toolbox.map.json

Issue #93 seems related, but it's closed and I'm still seeing this issue with 4.0.0. Is there some way to turn off the source map or to generate the source map to get this error to go away?

I'm closing this in favor of https://github.com/GoogleChrome/sw-toolbox/issues/169


renderThumb: not working using styled component

const thumb = (props, state) =>


Unhandled Exception crash when TCP/RESET is receieved.

Describe the bug
On Starlink and many other NAT'ed networks the TCP handling can be a little harsh and the firewal/nat can send TCP RESET packets to break TCP connections.
I think that is the cause here as if I use Starlink i see crashes of the at_client  :
Unhandled exception:
SocketException: Connection reset by peer (OS Error: Connection reset by peer, errno = 54), address = 92a7c219-e2eb-5f50-ac23-d7acba106cf5.swarm0002.atsign.zone, port = 64831

If I use SierraTel my local Telco I see none or very few...
But the at_client should be able to recover not crash in this situation..
Steps to reproduce

I am not able to reprooduce the issue outside of my personal set up as yet

This effects longstanding at_clients like sshnpd more than anything else..
Expected behavior
TCP session can crash but the at_client should not!
Currently the "solution" is to put the client software in a shell loop or have daemon to restart after a crash whcih is a little ugly !
Screenshots
No response
Smartphones
all
Were you using an atApplication when the bug was found?
sshnpd
Additional context
No response

Both @cconstab and I feel that this may be coming from the socket that the sync service is using, as we haven't encountered the issue when we run programs with a NoOpSyncService. But to be clear, this is just guesswork right now

@cconstab Some progress ... I have been running a whole bunch of tests and have reproduced many times now - mostly with clients which are using sync - however I also reproduced this problem today with an at_talk version which was not using sync. So - the sync connection springing into life and doing stuff might be a common trigger, but the actual problem is elsewhere.

Have diagnosed the issue and am testing the fix.

Estimate 2SP to close this out during PR63


How to set up haproxy and varnish in laravel project

I am trying to figure out how to make haproxy and varnish work in laradock. There is no documentation about it. I am composing up haproxy it automatically composing proxy1 proxy2 and then cant figure out how does this work. Can anyone give any tip or any tutorial? Please?

Added PR with new varnish configuration. Probably it will help you.
https://github.com/laradock/laradock/pull/2348

That sounds Great.. But what are the next steps? just composing up haproxy and everything works fine?

Added PR with new varnish configuration. Probably it will help you.
#2348

That sounds Great.. But what are the next steps? just composing up haproxy and everything works fine?

Unfortunately i did not test it with haproxy. But proxy1 and proxy2 use varnish


cannot set using a list-like indexer with a different length than the value

Hi, I am using Jupyter notebook locally and got an error : ValueError: cannot set using a list-like indexer with a different length than the value. Detailed logs here. Thanks!

ValueError                                Traceback (most recent call last)
 in
1 # main calculations section
----> 2 ptf = PortfolioModels('data')
3 summary = ptf.portfolio_summary()
4 stocks = ptf.stocks_risk()
5 df_corr, df_cov = ptf.stocks_correlation()
~/Documents/robinhood-portfolio/backend/portfolio_models.py in init(self, datafolder)
15         self.datafolder = datafolder
16         self._daily = None
---> 17         self._calculate_daily()
18         return None
19
~/Documents/robinhood-portfolio/backend/portfolio_models.py in _calculate_daily(self)
153
154         # merge orders with market
--> 155         pf = self._merge_market_with_dividends(df, pf)
156
157         # replace null stock prices using backfill to avoid issues with
~/Documents/robinhood-portfolio/backend/portfolio_models.py in _merge_market_with_dividends(self, df_div, mkt)
81             df['cum_dividends'].fillna(0, inplace=True)
82
---> 83             mkt.loc[_symbol] = df.values
84
85         return mkt
~/Documents/robinhood-portfolio/robinhood/lib/python3.7/site-packages/pandas/core/indexing.py in setitem(self, key, value)
668
669         iloc = self if self.name == "iloc" else self.obj.iloc
--> 670         iloc._setitem_with_indexer(indexer, value)
671
672     def _validate_key(self, key, axis: int):
~/Documents/robinhood-portfolio/robinhood/lib/python3.7/site-packages/pandas/core/indexing.py in _setitem_with_indexer(self, indexer, value)
1800             # actually do the set
1801             self.obj._consolidate_inplace()
-> 1802             self.obj._mgr = self.obj._mgr.setitem(indexer=indexer, value=value)
1803             self.obj._maybe_update_cacher(clear=True)
1804
~/Documents/robinhood-portfolio/robinhood/lib/python3.7/site-packages/pandas/core/internals/managers.py in setitem(self, indexer, value)
532
533     def setitem(self, indexer, value) -> "BlockManager":
--> 534         return self.apply("setitem", indexer=indexer, value=value)
535
536     def putmask(
~/Documents/robinhood-portfolio/robinhood/lib/python3.7/site-packages/pandas/core/internals/managers.py in apply(self, f, align_keys, **kwargs)
404                 applied = b.apply(f, **kwargs)
405             else:
--> 406                 applied = getattr(b, f)(**kwargs)
407             result_blocks = _extend_blocks(applied, result_blocks)
408
~/Documents/robinhood-portfolio/robinhood/lib/python3.7/site-packages/pandas/core/internals/blocks.py in setitem(self, indexer, value)
852
853         # length checking
--> 854         check_setitem_lengths(indexer, value, values)
855         exact_match = (
856             len(arr_value.shape)
~/Documents/robinhood-portfolio/robinhood/lib/python3.7/site-packages/pandas/core/indexers.py in check_setitem_lengths(indexer, value, values)
150             ):
151                 raise ValueError(
--> 152                     "cannot set using a list-like indexer "
153                     "with a different length than the value"
154                 )
ValueError: cannot set using a list-like indexer with a different length than the value

@XiyanHu, alright, thanks for reporting. I just found out that Robinhood changed their API, but looks like you had issue was before that. Will need few days - very busy at work/home this days.

Thanks for the reply, absolutely no hurry :)

As you can imagine I didn't have a chance to look at it. Apologies. Will have to deprecate it. Feel free to salvage what you can.


Don't require labels for LineChart

If you're trying to plot any substantial amount of data, you can't show labels because it will overload the graph.

number of labels does not have to match the number of data points. But it's a good point otherwise, I made them optional. 👍


Show which files in the datasets are scanned as unsafe

Hello, HF datasets show that at least one files in our datasets are scanned as unsafe. There are more than 16,000 files in the repo, so it's quite difficult to find which file is scanned as unsafe. It would be great if the warning message tells which file is scanned as unsafe.

cc @McPatate @krampstudio

@xiaohk We've made somechanges to the hub. From now on, we've added links to the suspicious files. It should help you next time.


Correcting documentation for ExecuteFlumeSink

Removing reference to removed lineage identifier header for ExecuteFlumeSink additional details.

Merging. . .


Migrate to libtraceevent

This attempts to move gpuvis to upstream libtraceevent. For the most part the API is the same, just with minor differences:

There's now a tep namespace, with some structs being renamed accordingly (i.e. pevent is now tep_handle
tep_handle is now opaque, with getters/setters replacing the public struct

trace_read.cpp mostly translated really well, but trace_clock was completely removed which of course means there are some FIXMEs in this patch.
From their Git log...
    6921e57eabff567168600a1131eb64867f5da251
    libtraceevent: Remove tep_register_trace_clock()

    The tep_register_trace_clock() API is used to instruct the traceevent
    library how to print the event time stamps. As event print interface if
    redesigned, this API is not needed any more.  The new event print API is
    flexible and the user can specify how the time stamps are printed.

~Also on the TODO is reintroducing the tgid support from https://github.com/mikesart/gpuvis/commit/e4ee7daa5050d764a59eaba8fbb570e709149687 (and probably other commits I haven't found yet).~ Got it... just skipped the SHOW_TGIDS bit since that wasn't being used.

tgid support is back in... at least, the first version I found in the git log is now in. For trace_clock, from what I could tell trace_read only used the variable to get/set locally and does its own printing, so I just moved the variable to tracecmd_input. With that, everything builds and from what I can tell the program is working again.
So, just left with a couple items...

Check for local trace-cmd changes (if any), reintroduce to libtraceevent
Windows/macOS buildfixes

macOS and the first shot at Windows buildfixes are in. The Mac build was really easy, Windows was... well, the commit log should tell the story. This doesn't really go into the full log of fixes for Windows, but I was at least able to open up a trace without anything going wrong.
This is at least enough to start verifying for stability. Things I need to pull from the old trace-cmd source:

Optimizations
Windows fixes (thought I saw some for sizeof(long)?)

All the local changes to trace-cmd have been added back to the local copy of libtraceevent. A couple changes were found in upstream and so were skipped.
With the exception of the bizarre thing I found in 3201e23 and maybe some tab/space errors, this should now function as it did before including performance (unless upstream regressed in some way).

Force-pushed a cleaned up commit history so that this can be merged automatically.

Is this something I could try to get into master @flibitijibibo? Thanks much!

Yup, everything looked good when I last checked it out! It might be worth rebasing libtraceevent one more time, but I marked down the current revision so it's not urgent for the merge IMO.

Awesome. I'll get on this now. Thanks again, really appreciate the help!


qhub upgrade should reject custom authenticators [bug]

Describe the bug
If the qhub-config.yaml contains:
security:
  authentication:
    type: custom

when running qhub upgrade from 0.3.13, the resulting qhub-config.yaml will be invalid (since it will not change the 'custom' entry which is no longer supported).
Expected behaviour
It should warn the user about the problem - maybe error out and say they first need to change to type: password or something else (probably easiest and failsafe).
Or we could just warn since qhub deploy will break anyway, and they'll have to do something to move forward.
Actual behaviour
I believe qhub upgrade will allow through the invalid config which will then break qhub deploy.

Agree, we could put a note on the docs commenting that this is no longer supported, and at the same time add a schema validator to check which type of authentication was passed in the config.
Just out of curiosity, was the Traitlets configuration removed for these custom cases?

@viniciusdc if you mean the relevant code in the templates/jupyterhub_config.py.j2 file then yes - everything is now using the Keycloak OAuth2 provider, which in turn may be configured for password, Auth0, GitHub, or anything else.

@viniciusdc if you mean the relevant code in the templates/jupyterhub_config.py.j2 file then yes - everything is now using the Keycloak OAuth2 provider, which in turn may be configured for password, Auth0, GitHub, or anything else.

Cool, thanks! :+1:


status of this repo

what's the relationship between this repo (https://github.com/bytecodealliance/wamr-python)
and https://github.com/bytecodealliance/wasm-micro-runtime/tree/main/language-bindings/python ?

what's the relationship between this repo (https://github.com/bytecodealliance/wamr-python) and https://github.com/bytecodealliance/wasm-micro-runtime/tree/main/language-bindings/python ?

This repo had been merged to WAMR repo, I will update the README soon.

what's the relationship between this repo (https://github.com/bytecodealliance/wamr-python) and https://github.com/bytecodealliance/wasm-micro-runtime/tree/main/language-bindings/python ?

This repo had been merged to WAMR repo, I will update the README soon.

do you mean this repo is no longer used? if so, how about archiving it?

Yes, no longer used. OK, let's archive it.


Feature/nl restructure

Restructured folders and files in Starter SPA.  Removed unnecessary files and folders for Redux since we are using Context.  Re-added .env.sample back in.

changes reviewed with web team as a group in zoom. Site renders out without errors

changes reviewed with web team as a group in zoom. Site renders out without errors


SteamProvider breaks because of a Cloudflare browser check.

:bug: Describe the Bug
The SteamDB site may redirect to a Cloudflare browser check, depending on the bot's IP (at least it seems that way).
Either another method to query the SteamDB should be found or a Steam offers should be queried somewhere else.

Fixed in #12.


Missing translations

Hi !
I noticed that there are missing translations for "No messages." at least in French and Spanish. I can make the update for French!
Cheers,
Quentin

So the French update has been pushed ;)
There still is work to do for other languages such as Spanish.

Sorry, I don't speak spanish, so I can't provide the translation, maybe someone else can contribute it ...


bashate: 2.0.0 -> 2.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for bashate is: "Style enforcement for bash programs"
meta.homepage for bashate is: "https://opendev.org/openstack/bashate"
meta.changelog for bashate is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/3gxmkfl7s1kc4z25qdw9l1ydfqsxq21a-bashate-2.1.0/bin/bashate passed the binary check.

/nix/store/3gxmkfl7s1kc4z25qdw9l1ydfqsxq21a-bashate-2.1.0/bin/.bashate-wrapped passed the binary check.

2 of 2 passed binary check by having a zero exit code.

2 of 2 passed binary check by having the new version present in output.

found 2.1.0 with grep in /nix/store/3gxmkfl7s1kc4z25qdw9l1ydfqsxq21a-bashate-2.1.0

found 2.1.0 in filename of file in /nix/store/3gxmkfl7s1kc4z25qdw9l1ydfqsxq21a-bashate-2.1.0

directory tree listing: https://gist.github.com/fdb55d3d1ce20e6328369753b1b0c676

du listing: https://gist.github.com/302aa728cc8dba014c076a46fd029cba

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
bashate

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3gxmkfl7s1kc4z25qdw9l1ydfqsxq21a-bashate-2.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bashate https://github.com/r-ryantm/nixpkgs/archive/cbc705bb3d69bd696ef472bebd451f567ebe13a1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3gxmkfl7s1kc4z25qdw9l1ydfqsxq21a-bashate-2.1.0
ls -la /nix/store/3gxmkfl7s1kc4z25qdw9l1ydfqsxq21a-bashate-2.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

bashate

Maintainer pings
cc @fabaff for testing.

Result of nixpkgs-review pr 139083 run on x86_64-linux 1

1 package built:

bashate


Automatically detect when a YAML file is a template or plain YAML (obviating the --ignore-unknown-comments flag)

Context: https://github.com/k14s/ytt/issues/14#issuecomment-726409172
I want to provide supply a combination of plain YAML and ytt YAML templates
and have ytt automatically figure out which are yaml-plain and which are yaml-template
so that I can — without doing any extra work — a) easily include YAML from 3rd party sources; and b) get the full benefits of ytt ensuring my templates execute well
__
Scenario: Mixed types of YAML files are correctly interpreted
Given at least one file that is plain YAML (e.g. includes standard YAML comments, # ) and at least one file that is a valid ytt template (i.e. contains at least one annotation #@)
When I invoke ytt specifying those files with no additional flags
Then the output contains both the properly evaluated template output and the plain YAML.
Scenario: Using (now) deprecated flag
When I invoke ytt with the --help flag
Then I see that the --ignore-unknown-comments flag is deprecated.
When I invoke ytt with the --ignore-unknown-comments
Then I see a warning (on standard error) that informs me that this flag is deprecated.
When I search the docs with keywords like "yaml-plain", "yaml-template", "detection", or "comments"
Or I navigate to sections that describe the "file mark" feature or that describe how templates are processed
Then I learn that ytt differentiates between "plain YAML" and "YAML templates", and how this behavior can be overiden.

Thanks @pivotaljohn.

So if the yaml file doesn't contain '#@' or marked as "yaml-plain", ytt will treat it as a plain yaml file and will not throw error if there is '# ' in the yaml file, even if --ignore-unknown-comments is not specified (by default) for ytt?
--ignore-unknown-comments is deprecated means there will be no --ignore-unknown-comments option in future. So in future will ytt throw error if there is '# ' in the non-plain-yaml file?

Thanks @pivotaljohn

🖖🏼

So if the yaml file doesn't contain '#@' or marked as "yaml-plain", ytt will treat it as a plain yaml file and will not throw error if there is '# ' in the yaml file, even if --ignore-unknown-comments is not specified (by default) for ytt?

Exactly. 👍🏼

--ignore-unknown-comments is deprecated means there will be no --ignore-unknown-comments option in future. So in future will ytt throw error if there is '# ' in the non-plain-yaml file?

ytt will continue to report an error if a YAML template contains a plain comment (the message specified in #226, or an improvement).
the --ignore-unknown-comments flag will eventually be removed. We can be quite patient about it given that we'll be giving a deprecation warning as part of this work. At the very least, it must be gone from any documentation of products that integrate/use ytt.

Works perfect! 👍


SetCursorPosition causes ArgumentOutOfRangeException when BufferHeight is reached

When the console window is filled with text from previous executions and i try to select a year, an ArgumentOutOfRangeException is thrown.
This happens because in BaseProgram.cs the argument top to the function SetCursorPosition(int left, int top) is greater than or equal to the Consoles BufferHeight.
The problem could be resolved by checking the BufferHeight and increasing it if necessary, however, this is only possible on Windows.
On Linux, the Exception does not occur but the available days are instead not displayed:

This sounds like it makes sense; you are kinda abusing the console by not clearing its buffer often enough, or increasing the max available buffer size.
That being said, what would you like the framework to do:

Clear the buffer entirely for you if it detects it's close to overflowing
Avoiding writing anything at all by simply checking if an overflow is bound to happening
Increase the buffer height automatically (Windows only is not ideal)
Prepare enough lines like it would happen normally
Ignore the problem and let it crash, showing you that you have not been clearing your console often enough

Should the above solutions be offered for the end user to pick? What would the default be? Configuring and customizing a framework sounds healthy to me, but I'd like some more opinions on that

I guess clearing the buffer would make sense and be easy to implement.
How would you image the configuration to be done?

The configuration would apply to a newly created class that would specifically handle buffer overflowing when trying to write, or preparing for writing.
Clearing the buffer at a certain threshold is the simplest solution of them, though I'd like to implement a more general solution that includes the configuration aspect of it. Will get down to it within the next couple of days.

Closed via 92e2bc2


build-storybook - CMD icon breaks in UI

Oops. What's this OS?

@thinkholic Could you add a SVG icon to this button?

OSX 10.4, Chrome stable. Latest.

@kevinSuttle We released a new version(v1.21.0) with a potential fix. Could you check that?

Nope. Unfortunately, no fix.

@mnmtanish @thinkholic Could you guys try @kevinSuttle's suggestions. I'm kind a noob in this area.

Hi @kevinSuttle
I think https://github.com/kadirahq/react-storybook/issues/215 is related. Can you try v1.28.1 I'm sure it will fix the issue.
CC: @arunoda @thinkholic

Woot! Seems fixed! Thanks gents!


bitcoin-abc: 0.15.0 -> 0.16.0

Please also backport to 17.09
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Wow, this thing has a brutal build time...

02b67d94b1


Log Timestamp

With the addition of logging sends in #72, I noticed that everything is being set to the current UTC day at midnight. From my limited testing, it looks like the times showing in the official app stored/display in EDT/EST? What time does it show for other users? I switch the TZ around on my phone but the time displayed remained the same in the app.
If so send current Eastern time in log ascent.

I just added date for the logging in the first release, and didn't care about the time.
But this can be added pretty easily …

Thanks for the report and PR, merged in the fix. Will deploy with the mirror changes once those are in

Deployed

@ItsDang did the Timestamp work for your timezone?
I logged a route with climbdex today at 08:00 local time in Vienna (should be 06:00 GMT).
When I checked the entry in the aurora app I saw 01:00. So I think the timestamps are (still) off.
When I check my Logbook export (or in the aurora app) the timestamps are shown in my local timezone, at least it looks like, because I did the boulders in the evening.

but didnt spent much time checking this, just realized it when I controlled the tick of the mirrored route today …

@gardaholm Hmm, yeah it "works" for me because it's set to EST, { timeZone: 'America/New_York'}, I think this needs to be removed and it should work for you too. Since the timezone isn't being stored, just storing local time seems best. I'll commit the change later today.

Fix should be deployed


A loading spinner component?

Very often in real-world examples made by @roym899, we end up with an empty view that stays empty for a while as we're waiting for some heavy computation to finish. E.g. there.
Now what if we could log an actual :slow-beach-ball: loading spinner kinda thing that would put the view in a 'please wait im computing' state? This would likely be a blueprint component I imagine.

This could be a SpaceView instead


Inconsistent behavior when formatting 'eHHmm'

Describe the bug
.format('eHHmm') returns an expected time string that moment validates as incorrect.
To Reproduce
Steps to reproduce the behavior:

Moment.tz('America/New_York').format('eHHmm') produces, say, 21530
But Moment('21530', 'eHHmm').isValid() returns false

Expected behavior
These two results should be (at least intuitively) consistent
Desktop (please complete the following information):

OS: Windows 11 WSL2
Browser: Chromium
Version: 112.0.5615.49 (Official Build) (64-bit)

Moment-specific environment

Vite 4.2.1 w/ Vue 3.2.47 running Node v18.12.1
Currently running on EDT

Please run the following code in your environment and include the output:
Tue Apr 11 2023 02:55:49 GMT-0400 (Eastern Daylight Time)
4/11/2023, 2:55:49 AM
240
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
2.29.4

Additional context
Moment('2-1530', 'e-HHmm') with any separator is, however, valid.

Yeah, e reads any number of digits instead of exactly one. You can submit a PR.


Indexer-service state channel error messages - 'Error during pushMessage'

This has been discussed within the indexers channel but not yet reported, adding an issue as suggested by @andrewgordstewart
[2020-12-21 00:37:54.123 +0000] ERROR     (997571 on node1): Error during pushMessage     dbName: "indexerprod"     walletVersion: "<EMAIL_ADDRESS>   reason: "Error during pushMessage"     data: {       "thisWalletVersion": "<EMAIL_ADDRESS>      "payloadWalletVersion": "<EMAIL_ADDRESS>      "cause": {         "reason": "Not in channel",         "type": "StoreError"       }     }     type: "PushMessageError"     stack: "Error: Error during pushMessage\n    at SingleThreadedWallet.pushMessage (/usr/local/lib/node_modules/@graphprotocol/indexer-service/node_modules/@statechannels/server-wallet/lib/src/wallet/wallet.js:283:19)\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)\n    at async timeAsync (/usr/local/lib/node_modules/@graphprotocol/indexer-service/node_modules/@statechannels/server-wallet/lib/src/metrics.js:58:16)\n    at async MessagePort.<anonymous> (/usr/local/lib/node_modules/@graphprotocol/indexer-service/node_modules/@statechannels/server-wallet/lib/src/wallet/multi-threaded-wallet/worker.js:36:169)"
service1.log

I am getting a lot of these errors
      "accept": "application/json, text/plain, */*",
      "content-type": "application/json",
      "user-agent": "axios/0.19.2",
      "content-length": "21277",
      "host": "<IP_ADDRESS>",
      "connection": "close"
    }
    err: {
      "type": "IndexerError",
      "message": "Failed to handle state channel message",
      "stack":
          IndexerError: Failed to handle state channel message
              at Object.indexerError (/home/lexprime/.nvm/versions/node/v14.9.0/lib/node_modules/@graphprotocol/indexer-service/node_modules/@graphprotocol/indexer-common/dist/errors.js:97:12)
              at /home/lexprime/.nvm/versions/node/v14.9.0/lib/node_modules/@graphprotocol/indexer-service/dist/server/index.js:262:42
              at Generator.throw (<anonymous>)
              at rejected (/home/lexprime/.nvm/versions/node/v14.9.0/lib/node_modules/@graphprotocol/indexer-service/dist/server/index.js:6:65)
      "code": "IE023",
      "explanation": "https://github.com/graphprotocol/indexer/blob/master/docs/errors.md#ie023",
      "cause": {
        "type": "Error",
        "message": "Error during pushMessage",
        "stack":
            Error: Error during pushMessage
                at SingleThreadedWallet.pushMessage (/home/lexprime/.nvm/versions/node/v14.9.0/lib/node_modules/@graphprotocol/indexer-service/node_modules/@statechannels/server-wallet/lib/src/wallet/wallet.js:283:19)
                at processTicksAndRejections (internal/process/task_queues.js:93:5)
                at async timeAsync (/home/lexprime/.nvm/versions/node/v14.9.0/lib/node_modules/@graphprotocol/indexer-service/node_modules/@statechannels/server-wallet/lib/src/metrics.js:58:16)
                at async MessagePort.<anonymous> (/home/lexprime/.nvm/versions/node/v14.9.0/lib/node_modules/@graphprotocol/indexer-service/node_modules/@statechannels/server-wallet/lib/src/wallet/multi-threaded-wallet/worker.js:36:169)
      }
    }
[2020-12-24 11:52:16.513 +0000] DEBUG (IndexerService/21686 on graph-indexer.darksiders-staking.com): POST /channel-messages-inbox 500 50 - 155.437 ms
    indexer: "0xBE9d7c691792937Ca7e2535652886ff390Cc5b86"
    operator: "0xE35C249f495C563E42D5822985158825Eb37e61e"
    component: "Server"
[2020-12-24 11:52:16.513 +0000] ERROR (21686 on graph-indexer.darksiders-staking.com): Error during pushMessage
    dbName: "mainnet_indexer1"
    walletVersion: "<EMAIL_ADDRESS>    reason: "Error during pushMessage"
    data: {
      "thisWalletVersion": "<EMAIL_ADDRESS>      "payloadWalletVersion": "<EMAIL_ADDRESS>      "cause": {
        "reason": "Not in channel",
        "type": "StoreError"
      }
    }
    type: "PushMessageError"
    stack: "Error: Error during pushMessage\n    at SingleThreadedWallet.pushMessage (/home/lexprime/.nvm/versions/node/v14.9.0/lib/node_modules/@graphprotocol/indexer-service/node_modules/@statechannels/server-wallet/lib/src/wallet/wallet.js:283:19)\n    at processTicksAndRejections (internal/process/task_queues.js:93:5)\n    at async timeAsync (/home/lexprime/.nvm/versions/node/v14.9.0/lib/node_modules/@graphprotocol/indexer-service/node_modules/@statechannels/server-wallet/lib/src/metrics.js:58:16)\n    at async MessagePort.<anonymous> (/home/lexprime/.nvm/versions/node/v14.9.0/lib/node_modules/@graphprotocol/indexer-service/node_modules/@statechannels/server-wallet/lib/src/wallet/multi-threaded-wallet/worker.js:36:169)"

https://raw.githubusercontent.com/LexPrime/logs/main/ind_serv.log


Adds support for HashiCorp Vault

Hello maintainers 👋🏼 - adding this as draft while we get the final bits and pieces in places.

What does this PR do?
This PR adds a reference to the HashiCorp Vault blueprint.
Motivation
We love EKS and believe we should make it easier to manage and protect secrets (and sensitive data, in general) in an EKS workflow.
More

[X] Yes, I have tested the PR using my local account setup  (Provide any test evidence report under Additional Notes)
[X] Yes, I have added a new example under examples to support my PR

As we are adding an external add-on, our example code lives in the external repository.

[ ] Yes, I have created another PR for add-ons under add-ons repo (if applicable)

Not applicable.

[X] Yes, I have updated the docs for this feature
[X] Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.
For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

Thanks @vara-bonthu - we're still working on getting some things on our side squared away before we publish the final (= 0.9.0) of this add-on to the Terraform Registry.
If y'all could wait with merging this until then, that would be very helpful!

(marked as draft; which I forgot to do when I opened this PR)

Hey folks! We've made an initial version of the module code available at the links present in this PR.
We anticipate down-the-road changes and may release newer module versions.
For now, please give Vault a try with the included example.

Hey folks! We've made an initial version of the module code available at the links present in this PR.
We anticipate down-the-road changes and may release newer module versions.
For now, please give Vault a try with the included example.

Thanks @ksatirli
I have tested the Vault Add-on and it worked without any issues 👍🏼
 vabonthu>…/terraform/eks
▶ kubectl get pods -n vault | grep vault
vault-0                                 1/1     Running   0          4m5s
vault-agent-injector-7f6bdfc48d-sct5p   1/1     Running   0          4m5s


Windows 7 supported partially 6.1.7601.25757 (x86)

Hello
Remote desktop only works two connections.
Need Help please! Thanks a lot !

termsrv.zip

Hello
Remote desktop only works two connections.
Need Help please! Thanks a lot !

Hi. Can you share the previous termsrv.dll (6.1.7601.24402)
There's no pdb file, so i need to search the offsets manually but it's very dificult without a previous one.
Thank you!

Thanks ! I had to uninstall some updates to make it fine. I can't get termsrv.dll (6.1.7601.24402) . Anyway , thanks a lot !

Yes, appreciated.
BTW, for manual patching (some may want to go that route), are the offsets and changed values posted around here somewhere for this release, which will probably be the last one?

offsets and changed values posted around here somewhere

No. We, who use rdpwrapper, don't patch termsrv.dll


twt support for zephyr L2 cmd

A. Add two parameters for TWT
B. Add default exponent value for TWT quick setup
C. Add BTWT feature support for sap.

Please update the title and add description to explain these set of changes.

Please update the title and add description to explain these set of changes.

Yes, of course, updated title and changes details , changes info also in separated PRs commit mesg

Hi @krish2718 @jukkar
Could you help to review?

Hi @krish2718  @jukkar
Could you help review.
Thanks!

Hi @jukkar @krish2718
All updated as comments, pls help review.

Hi @krish2718  @jukkar  @MaochenWang1
Separated PRs and updated as comments, pls help review.

Hi @krish2718  @jukkar
I want to insert other discussion about parameters usage of twt setup cmd.
The below two usage items, from the value range and spec description  , 'twt_wake_interval' should named as 'TWT Wake Duration', and 'twt_interval' should calculated from TWT Wake Interval(TWT Wake Interval Mantissa) and Exponent, so name as 'TWT Wake Interval' will be suitable.
A. <twt_wake_interval: 1-262144us>
B. <twt_interval: 1us-2^31us>
As I didn't find description about 'twt_interval' from spec, if my above suggestion and understanding is error, pls tell me.
If you agree, I will raise other PR to change the usage after this PR merged.
Thanks.

Hi @krish2718 @jukkar I want to insert other discussion about parameters usage of twt setup cmd. The below two usage items, from the value range and spec description , 'twt_wake_interval' should named as 'TWT Wake Duration', and 'twt_interval' should calculated from TWT Wake Interval(TWT Wake Interval Mantissa) and Exponent, so name as 'TWT Wake Interval' will be suitable. A. <twt_wake_interval: 1-262144us> B. <twt_interval: 1us-2^31us>
As I didn't find description about 'twt_interval' from spec, if my above suggestion and understanding is error, pls tell me. If you agree, I will raise other PR to change the usage after this PR merged. Thanks.

Please see https://github.com/zephyrproject-rtos/zephyr/pull/82312/files#r1875537287 , it's about keeping UI simple.

Hi @krish2718 @jukkar I want to insert other discussion about parameters usage of twt setup cmd. The below two usage items, from the value range and spec description , 'twt_wake_interval' should named as 'TWT Wake Duration', and 'twt_interval' should calculated from TWT Wake Interval(TWT Wake Interval Mantissa) and Exponent, so name as 'TWT Wake Interval' will be suitable. A. <twt_wake_interval: 1-262144us> B. <twt_interval: 1us-2^31us>
As I didn't find description about 'twt_interval' from spec, if my above suggestion and understanding is error, pls tell me. If you agree, I will raise other PR to change the usage after this PR merged. Thanks.

Please see https://github.com/zephyrproject-rtos/zephyr/pull/82312/files#r1875537287 , it's about keeping UI simple.

Sure, even if we don't use exponent, but the range of 'twt_wake_interval' is matched with 'TWT Wake Duration', so should we change the usage to 'TWT Wake Duration', twt_wake_interval make user confuse.

Hi @krish2718 @jukkar I want to insert other discussion about parameters usage of twt setup cmd. The below two usage items, from the value range and spec description , 'twt_wake_interval' should named as 'TWT Wake Duration', and 'twt_interval' should calculated from TWT Wake Interval(TWT Wake Interval Mantissa) and Exponent, so name as 'TWT Wake Interval' will be suitable. A. <twt_wake_interval: 1-262144us> B. <twt_interval: 1us-2^31us>
As I didn't find description about 'twt_interval' from spec, if my above suggestion and understanding is error, pls tell me. If you agree, I will raise other PR to change the usage after this PR merged. Thanks.

Please see https://github.com/zephyrproject-rtos/zephyr/pull/82312/files#r1875537287 , it's about keeping UI simple.

Sure, even if we don't use exponent, but the range of 'twt_wake_interval' is matched with 'TWT Wake Duration', so should we change the usage to 'TWT Wake Duration', twt_wake_interval make user confuse.

twt_wake_interval is mapped to Nominal Minimum TWT Wake Duration field and in 802.11ax-2021, the max value is https://github.com/zephyrproject-rtos/zephyr/blob/main/include/zephyr/net/wifi_mgmt.h#L765 i.e., Wake Duration Unit subfield == 1 and Nominal Minimum TWT Wake Duration field == 256 , can you please let me know how the range is incorrect?

Hi @krish2718 @jukkar I want to insert other discussion about parameters usage of twt setup cmd. The below two usage items, from the value range and spec description , 'twt_wake_interval' should named as 'TWT Wake Duration', and 'twt_interval' should calculated from TWT Wake Interval(TWT Wake Interval Mantissa) and Exponent, so name as 'TWT Wake Interval' will be suitable. A. <twt_wake_interval: 1-262144us> B. <twt_interval: 1us-2^31us>
As I didn't find description about 'twt_interval' from spec, if my above suggestion and understanding is error, pls tell me. If you agree, I will raise other PR to change the usage after this PR merged. Thanks.

Please see https://github.com/zephyrproject-rtos/zephyr/pull/82312/files#r1875537287 , it's about keeping UI simple.

Sure, even if we don't use exponent, but the range of 'twt_wake_interval' is matched with 'TWT Wake Duration', so should we change the usage to 'TWT Wake Duration', twt_wake_interval make user confuse.

twt_wake_interval is mapped to Nominal Minimum TWT Wake Duration field and in 802.11ax-2021, the max value is https://github.com/zephyrproject-rtos/zephyr/blob/main/include/zephyr/net/wifi_mgmt.h#L765 i.e., Wake Duration Unit subfield == 1 and Nominal Minimum TWT Wake Duration field == 256 , can you please let me know how the range is incorrect? Please note that depending on the user value, the Wake Duration Unit subfield == 1 is auto-encoded to 0/1 in the driver/firmware.

Yes, I mean should rename twt_wake_interval to

Hi @krish2718 @jukkar I want to insert other discussion about parameters usage of twt setup cmd. The below two usage items, from the value range and spec description , 'twt_wake_interval' should named as 'TWT Wake Duration', and 'twt_interval' should calculated from TWT Wake Interval(TWT Wake Interval Mantissa) and Exponent, so name as 'TWT Wake Interval' will be suitable. A. <twt_wake_interval: 1-262144us> B. <twt_interval: 1us-2^31us>
As I didn't find description about 'twt_interval' from spec, if my above suggestion and understanding is error, pls tell me. If you agree, I will raise other PR to change the usage after this PR merged. Thanks.

Please see https://github.com/zephyrproject-rtos/zephyr/pull/82312/files#r1875537287 , it's about keeping UI simple.

Sure, even if we don't use exponent, but the range of 'twt_wake_interval' is matched with 'TWT Wake Duration', so should we change the usage to 'TWT Wake Duration', twt_wake_interval make user confuse.

twt_wake_interval is mapped to Nominal Minimum TWT Wake Duration field and in 802.11ax-2021, the max value is https://github.com/zephyrproject-rtos/zephyr/blob/main/include/zephyr/net/wifi_mgmt.h#L765 i.e., Wake Duration Unit subfield == 1 and Nominal Minimum TWT Wake Duration field == 256 , can you please let me know how the range is incorrect? Please note that depending on the user value, the Wake Duration Unit subfield == 1 is auto-encoded to 0/1 in the driver/firmware.

Yes, I mean why don't named as 'TWT Wake Duration' directly?

Sure we can rename it to twt_wake_duration.

Hi @krish2718 @jukkar I want to insert other discussion about parameters usage of twt setup cmd. The below two usage items, from the value range and spec description , 'twt_wake_interval' should named as 'TWT Wake Duration', and 'twt_interval' should calculated from TWT Wake Interval(TWT Wake Interval Mantissa) and Exponent, so name as 'TWT Wake Interval' will be suitable. A. <twt_wake_interval: 1-262144us> B. <twt_interval: 1us-2^31us>
As I didn't find description about 'twt_interval' from spec, if my above suggestion and understanding is error, pls tell me. If you agree, I will raise other PR to change the usage after this PR merged. Thanks.

Please see https://github.com/zephyrproject-rtos/zephyr/pull/82312/files#r1875537287 , it's about keeping UI simple.

Sure, even if we don't use exponent, but the range of 'twt_wake_interval' is matched with 'TWT Wake Duration', so should we change the usage to 'TWT Wake Duration', twt_wake_interval make user confuse.

twt_wake_interval is mapped to Nominal Minimum TWT Wake Duration field and in 802.11ax-2021, the max value is https://github.com/zephyrproject-rtos/zephyr/blob/main/include/zephyr/net/wifi_mgmt.h#L765 i.e., Wake Duration Unit subfield == 1 and Nominal Minimum TWT Wake Duration field == 256 , can you please let me know how the range is incorrect? Please note that depending on the user value, the Wake Duration Unit subfield == 1 is auto-encoded to 0/1 in the driver/firmware.

Yes, I mean why don't named as 'TWT Wake Duration' directly?

Sure we can rename it to twt_wake_duration. But it would be a breaking API change.

Okay, will raise PR later after this PR merged.

Hi @krish2718 @jukkar I want to insert other discussion about parameters usage of twt setup cmd. The below two usage items, from the value range and spec description , 'twt_wake_interval' should named as 'TWT Wake Duration', and 'twt_interval' should calculated from TWT Wake Interval(TWT Wake Interval Mantissa) and Exponent, so name as 'TWT Wake Interval' will be suitable. A. <twt_wake_interval: 1-262144us> B. <twt_interval: 1us-2^31us>
As I didn't find description about 'twt_interval' from spec, if my above suggestion and understanding is error, pls tell me. If you agree, I will raise other PR to change the usage after this PR merged. Thanks.

Please see https://github.com/zephyrproject-rtos/zephyr/pull/82312/files#r1875537287 , it's about keeping UI simple.

Sure, even if we don't use exponent, but the range of 'twt_wake_interval' is matched with 'TWT Wake Duration', so should we change the usage to 'TWT Wake Duration', twt_wake_interval make user confuse.

twt_wake_interval is mapped to Nominal Minimum TWT Wake Duration field and in 802.11ax-2021, the max value is https://github.com/zephyrproject-rtos/zephyr/blob/main/include/zephyr/net/wifi_mgmt.h#L765 i.e., Wake Duration Unit subfield == 1 and Nominal Minimum TWT Wake Duration field == 256 , can you please let me know how the range is incorrect? Please note that depending on the user value, the Wake Duration Unit subfield == 1 is auto-encoded to 0/1 in the driver/firmware.

Yes, I mean why don't named as 'TWT Wake Duration' directly?

Sure we can rename it to twt_wake_duration. But it would be a breaking API change.

Okay, will raise PR later after this PR merged.

Please note we have to follow the rules here for any stable API https://docs.zephyrproject.org/latest/develop/api/api_lifecycle.html but I guess there aren't many users of TWT, so, not sure if we should call it stable or not. @jukkar WDYT?

Hi @krish2718 @jukkar @MaochenWang1
Follow @krish2718 comment to remove teardown changes, and there is no conclusion of 'exponent ', so keep exponent as shell input.

Hi @krish2718 @jukkar @MaochenWang1
Follow @krish2718 comment to remove teardown changes, and there is no conclusion of 'exponent ', so keep exponent as shell input.

Should we add both the options? If the user gives time we derive (exponent, mantissa) and if the user gives (exponent, mantissa) we use it directly, WDYT?

Hi @krish2718 @jukkar @MaochenWang1
Follow @krish2718 comment to remove teardown changes, and there is no conclusion of 'exponent ', so keep exponent as shell input.

Should we add both the options? If the user gives time we derive (exponent, mantissa) and if the user gives (exponent, mantissa) we use it directly, WDYT?

My concern is exist multiple sets of exponent and mantissa derived from a given time, and the time calculated from the derived exponent and mantissa may not equal to the given time. Customer may complain about why time set not as expectation.

Hi @krish2718 @jukkar @MaochenWang1
Follow @krish2718 comment to remove teardown changes, and there is no conclusion of 'exponent ', so keep exponent as shell input.

Should we add both the options? If the user gives time we derive (exponent, mantissa) and if the user gives (exponent, mantissa) we use it directly, WDYT?

My concern is exist multiple sets of exponent and mantissa derived from a given time, and the time calculated from the derived exponent and mantissa may not equal to the given time. Customer may complain about why time set not as expectation.

We share the (exponent, mantissa) in the frame to the AP, so, at least AP and STA will have the same time. Anyways giving both options is better we can leave it to the users to choose the appropriate one, no?

Hi @krish2718 @jukkar @MaochenWang1
Follow @krish2718 comment to remove teardown changes, and there is no conclusion of 'exponent ', so keep exponent as shell input.

Should we add both the options? If the user gives time we derive (exponent, mantissa) and if the user gives (exponent, mantissa) we use it directly, WDYT?

My concern is exist multiple sets of exponent and mantissa derived from a given time, and the time calculated from the derived exponent and mantissa may not equal to the given time. Customer may complain about why time set not as expectation.

We share the (exponent, mantissa) in the frame to the AP, so, at least AP and STA will have the same time. Anyways giving both options is better we can leave it to the users to choose the appropriate one, no?

Okay, how can we derive a set of exponent and mantissa from a given time, is there any algorithm for refer?

Hi @krish2718 @jukkar @MaochenWang1
Follow @krish2718 comment to remove teardown changes, and there is no conclusion of 'exponent ', so keep exponent as shell input.

Should we add both the options? If the user gives time we derive (exponent, mantissa) and if the user gives (exponent, mantissa) we use it directly, WDYT?

My concern is exist multiple sets of exponent and mantissa derived from a given time, and the time calculated from the derived exponent and mantissa may not equal to the given time. Customer may complain about why time set not as expectation.

We share the (exponent, mantissa) in the frame to the AP, so, at least AP and STA will have the same time. Anyways giving both options is better we can leave it to the users to choose the appropriate one, no?

Okay, how can we derive a set of exponent and mantissa from a given time with high accuracy, is there any algorithm for refer?

We took the simpler approach: https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/wifi/nrf_wifi/src/wifi_mgmt.c#L250

Hi @krish2718 @jukkar @MaochenWang1
Follow @krish2718 comment to remove teardown changes, and there is no conclusion of 'exponent ', so keep exponent as shell input.

Should we add both the options? If the user gives time we derive (exponent, mantissa) and if the user gives (exponent, mantissa) we use it directly, WDYT?

My concern is exist multiple sets of exponent and mantissa derived from a given time, and the time calculated from the derived exponent and mantissa may not equal to the given time. Customer may complain about why time set not as expectation.

We share the (exponent, mantissa) in the frame to the AP, so, at least AP and STA will have the same time. Anyways giving both options is better we can leave it to the users to choose the appropriate one, no?

Okay, how can we derive a set of exponent and mantissa from a given time with high accuracy, is there any algorithm for refer?

We took the simpler approach: https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/wifi/nrf_wifi/src/wifi_mgmt.c#L250

Sonnet 3.5 gave this for binary scaling input.
def convert_time_to_mantissa_exponent(time_ms):
    """
    Convert time in milliseconds to mantissa and exponent representation

    Args:
        time_ms (float): Time in milliseconds

    Returns:
        tuple: (mantissa, exponent)
    """
    # Start with base-2 exponent of 0
    exponent = 0
    mantissa = time_ms

    # Reduce mantissa by dividing by 2 and incrementing exponent
    while mantissa > 255:  # Typical max mantissa value
        mantissa /= 2
        exponent += 1

    return (int(mantissa), exponent)

# Example usage
time = 50  # milliseconds
mantissa, exponent = convert_time_to_mantissa_exponent(time)
print(f"Original time: {time}ms")
print(f"Mantissa: {mantissa}")
print(f"Exponent: {exponent}")
print(f"Reconstructed time: {mantissa * (2 ** exponent)}ms")

Hi @krish2718 @jukkar @MaochenWang1
Follow @krish2718 comment to remove teardown changes, and there is no conclusion of 'exponent ', so keep exponent as shell input.

Should we add both the options? If the user gives time we derive (exponent, mantissa) and if the user gives (exponent, mantissa) we use it directly, WDYT?

My concern is exist multiple sets of exponent and mantissa derived from a given time, and the time calculated from the derived exponent and mantissa may not equal to the given time. Customer may complain about why time set not as expectation.

We share the (exponent, mantissa) in the frame to the AP, so, at least AP and STA will have the same time. Anyways giving both options is better we can leave it to the users to choose the appropriate one, no?

Okay, how can we derive a set of exponent and mantissa from a given time with high accuracy, is there any algorithm for refer?

We took the simpler approach: https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/wifi/nrf_wifi/src/wifi_mgmt.c#L250

Sonnet 3.5 gave this for binary scaling input.
def convert_time_to_mantissa_exponent(time_ms):
    """
    Convert time in milliseconds to mantissa and exponent representation

    Args:
        time_ms (float): Time in milliseconds

    Returns:
        tuple: (mantissa, exponent)
    """
    # Start with base-2 exponent of 0
    exponent = 0
    mantissa = time_ms

    # Reduce mantissa by dividing by 2 and incrementing exponent
    while mantissa > 255:  # Typical max mantissa value
        mantissa /= 2
        exponent += 1

    return (int(mantissa), exponent)

# Example usage
time = 50  # milliseconds
mantissa, exponent = convert_time_to_mantissa_exponent(time)
print(f"Original time: {time}ms")
print(f"Mantissa: {mantissa}")
print(f"Exponent: {exponent}")
print(f"Reconstructed time: {mantissa * (2 ** exponent)}ms")

Thanks for sharing, as Nordic driver implemented the convert of  (exponent, mantissa, interval) , and need interval as argv, to compatible Nordic's exist implementation, the shell should prepare all of parameters(exponent, mantissa, interval) according to the input (exponent, mantissa) or interval, right? If you agree, I will make change.

Hi @krish2718 @jukkar  @MaochenWang1
Follow @krish2718 comments to support both interval  or (exponent, mantissa) as input parameters, format check pass in local, test pass base on RW612 board, could help review after CI check pass?

Hi @krish2718  @jukkar
As CI check failed early, I rebased for PR, could you help review?

Hi @jukkar @dleach02
Could you help review and merge PR?


fix: soft link packages to modules

This is a fix for linking packages inside package to node_modules.
I succeed to run the project and it is so attractive :100:

Coverage remained the same at 100.0% when pulling c85661767d9343420961530cfd80ca2caae570ef on saeidalidadi:fix-linking-packages into 3aee1aa58ba1b2cb3d92ecd812738e3ebeabc4c7 on google:master.

FIX: #17


Question about dashboard

Hello,
I plan to use k6-kafka. I know some k6 dashboard but not for the kafka extension. So before I start creating a new Grafana dashboard I was wondering if one already exists?
Thank you very much
kind regards

Hey @nj-apps,
There is no dashboard that I know of. Feel free to create it and contribute it to Grafana Dashboards or here in this repository.

Thank you very much. I will share the dashboard once operational

Feel free to re-open this when it's ready.

hi ,is there any dashboard available ?


EMFILE: too many open files

Steps to reproduce

ndb version: 1.06
Platform / OS version: macOS High Sierra 10.13.6
Node.js version: v10.7.0, npm v6.2.0

What steps will reproduce the problem?
npm i -g ndb
ndb test.js

Please include code that reproduces the issue.
function p1() {
	return new Promise((resolve, reject) => {
		setTimeout(() => {
			console.log('p1')
			resolve('p1');
		}, 3000);
	})
}

function p2() {
	return new Promise((resolve, reject) => {
		setTimeout(() => {
			console.log('p2')
			resolve('p2');
		}, 1000);
	})
}
function all() {
	return Promise.all([
		p1(),
		p2()
	]);
}

console.log(all().then((foo) => {
	console.log(foo);
}));

What happens instead?
ndb ~/test.js
Debugger listening on ws://<IP_ADDRESS>:50703/ac178172-a158-4ef8-bb19-f7127e29ca63
For help, see: https://nodejs.org/en/docs/inspector
Debugger listening on ws://<IP_ADDRESS>:50704/85b5cbff-d21b-4c98-bbbf-e42521324d6a
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Debugger attached.
Promise { <pending> }
p2
2018-07-23 10:54 node[13054] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2018-07-23 10:54 node[13054] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: EMFILE: too many open files, watch
    at FSEvent.FSWatcher._handle.onchange (internal/fs/watchers.js:120:28)
Emitted 'error' event at:
    at FSEvent.FSWatcher._handle.onchange (internal/fs/watchers.js:126:12)

The debugger opens but it closes itself after 2 seconds and the error above fires.
I haven't changed my Mac ulimit or max files. I tried setting
sudo launchctl limit maxfiles 2048 unlimited

from 256 as it is the default, even went up to 6000 but still the same error.
I know in the code files are watched from changes using the Node native API, but there might be better alternatives that will not break the OS limit. In the mean time not sure how to fix this.

I'm having the same issue with

ndb v1.0.9
macOS High Sierra 10.13.6
node v10.7.0 (also tested with v8.11.3 with same results)

It was working fine a couple of days ago with a previous version. I didn't change anything and just tried the same command again and it broke, so I tried upgrading ndb without success.

I just published 1.0.13 that uses chokidar instead of builtin watchers. This issue should be fixed.


Upgrade nvcomp to <IP_ADDRESS>

This updates kvikio to use nvcomp <IP_ADDRESS>. This includes some bug fixes needed for Spark-RAPIDS in 24.12.
The version is updated in rapids-cmake in https://github.com/rapidsai/rapids-cmake/pull/727.

Thanks Bradley! 🙏
Are we able to use a looser pinning for this dependency? Think that would make it easier to update (and for users to install)

Are we able to use a looser pinning for this dependency?

No, unfortunately. We require this to match rapids-cmake's pinnings exactly, and to ensure that we get bug fixes in the latest release. Eventually it would be nice to expand our range of nvcomp versions we allow, but we have been pinned at "latest" for a long time due to the requirement of matching rapids-cmake, in addition to many breaking changes and required bug fixes in each new release of nvcomp. Things are getting more stable over time, so this may be revisited in the medium/long term.

Ok happy to punt
Though let's see if we can find a simpler update path: https://github.com/rapidsai/build-planning/issues/125

Looks like the wheels are not on PyPI yet. Hence those CI jobs fail

Retargeting to 25.02.

After discussion with @sameerz, I think we can hold off on taking this update. We may take a different nvcomp release in 25.02.


Missing "./wire" specifier in "@bufbuild/protobuf" package

As of this morning (20/9), all of our builds, CI & local, are failing with the above message.
The full error is:
vite v4.5.3 building for development...
transforming...
✓ 50 modules transformed.
[commonjs--resolver] Missing "./wire" specifier in "@bufbuild/protobuf" package
✓ built in 1.88s
error during build:
Error: Missing "./wire" specifier in "@bufbuild/protobuf" package
    at e (file:///home/runner/01/_work/redacted/webpage/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:21445:25)
    at n (file:///home/runner/01/_work/redacted/webpage/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:21445:627)
    at o (file:///home/runner/01/_work/redacted/webpage/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:21445:1297)
    at resolveExportsOrImports (file:///home/runner/01/_work/redacted/webpage/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:28746:20)
    at resolveDeepImport (file:///home/runner/01/_work/redacted/webpage/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:28765:31)
    at tryNodeResolve (file:///home/runner/01/_work/redacted/webpage/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:28453:20)
    at Object.resolveId (file:///home/runner/01/_work/redacted/webpage/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:28212:28)
    at file:///home/runner/01/_work/redacted/webpage/node_modules/rollup/dist/es/shared/node-entry.js:25539:40
    at async PluginDriver.hookFirstAndGetPlugin (file:///home/runner/01/_work/redacted/webpage/node_modules/rollup/dist/es/shared/node-entry.js:25439:28)
    at async resolveId (file:///home/runner/01/_work/redacted/webpage/node_modules/rollup/dist/es/shared/node-entry.js:24112:26)

Googling doesn't seem to yield any results. And it doesn't appear to be a change on our part as rerunning a successful job from yesterday fails today.
Any help would be appreciated. Thanks.

We resolved this by pinning the version of buf.build/community/stephenh-ts-proto to v1.178.0.
It was updated yesterday and that appears to have broken our usage.

Hey Jon, it looks like Vite v4 does not support package.json exports yet. The limitation is most likely in Rollup, not Vite itself. It might very well be possible to fix the issue by updating to a more recent version of @rollup/plugin-node-resolve.


Incorrect Ancestry Attribute Boosts

Two Ancestries have incorrect Attribute Boosts/Flaws:

The Barathu have a boost in Dex instead of boosts in Con, Wis and a free boost, and a flaw in Dex
The Kasatha are missing a boost in Str and a flaw in Cha

Already fixed, duplicate of #9

Oh, going too fast on my phone. I'll fix kasatha later


Mark OpenSSLDie noreturn, supersedes #525

This is the revised version of PR #525.
It is good practice to mark functions that don't return as noreturn/_Noreturn. The former is a definition found in stdnoreturn.h, the latter is the actual keyword. Both are available from C11 onwards. If C11 is not used, optionally fall back to the GCC-specific __attribute__((noreturn)) or to nothing at all if the compiler is not GCC.
This change particularly helps in reducing static analysis false positives.

@levitte, should this be __onoreturn like __owur?  Your call, but I will +1 this if you want to take on the merge.

@richsalz, I'm obviously not a veteran OpenSSL contributor, but noreturn is not only a 'regular' attribute, but more of a core element of the C(11) language. The only reason of having the 'workaround' with stdnoreturn.h and _Noreturn is backwards compatibility, I guess.

@richsalz makes a good point.  Our redefining noreturn might disturb others having the same idea, so it would be preferable to do like...  I think I'd prefer that to be like ossl_inline, so @hesiod, if you could make it so e_os2.h defines ossl_noreturn and uses that, I'd be quite happy with this change.
BTW, you don't have to make a new pull request just to change a commit.  Just make a fixup commit, then git rebase -i with appropriate arguments, and git push -f when done.

And if that change is made, then my +1 still stands and @levitte can do the merge when he gets a chance.

@levitte, sometimes, when I'm in a lazy mood, I just rely on the point-and-click Github GUI.
Anyways, will do the changes.

I fixed the logic flaw and renamed noreturn to ossl_noreturn.
Note that by defining noreturn ourselves when using C11, we do not rely on stdnoreturn.h and any compatibility logic contained there, but afaik no platform does anything fancy in stdnoreturn.h at the moment.

ping @levitte  -- you okay with this?  I'll merge if you plus-one.

Ping @levitte

This looks much better.  +1

merged.
thanks for your patience!


AVS Camera  AddComServer

Modified AVSCamera.inx to show DeviceMFT registration using AddComServer/AddComClass

@jiteshkris is added to the review. #Closed

@SangChoe is added to the review. #Closed

@jikrishn is added to the review. #Closed


Filtering and smoothing movement

There is some jittering of PS move less or more noticeable depending on it's position.
It is possible to have some option to filter the rotation and position over time preventing too fast movements or reducing them in some time fraction value ?

This issue is covered by issue #13 (Kalman filter work), which will help smooth out the jitter. I'll be working on this in earnest this next week.


feat(output): pretty print marble differences for value objects

This is the other approach I mentioned in https://github.com/meltedspark/jest-marbles/pull/26, which still gives the same prettified output.

I still prefer the fast-deep-equal version :)


Missing description for parameter 'HiddenGroupMembershipEnabled'

Missing description for parameter 'HiddenGroupMembershipEnabled'

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bd7d69db-be49-179e-94ce-635337c98d07
Version Independent ID: 9e372e66-5c7e-4d9a-56de-a35ae353fa09
Content: Set-UnifiedGroup (exchange)
Content Source: exchange/exchange-ps/exchange/users-and-groups/Set-UnifiedGroup.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

Hi @Borkason, thank you for your feedback.
There is a line in the cmdlet description:
"The HiddenGroupMembershipEnabled parameter is only available on the New-UnifiedGroup cmdlet. You can't change this setting on an existing Office 365 Group group."
Also, this parameter is not available in this cmdlet.

@dariomws306  Thank you very much for the contribution and sharing this explanation. @Borkason
Hope this comment is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@officedocsbot close


Does this project still work?

I'm rather perplexed as I've tried all manner of things to attempt to get this project running and just haven't been able to. This is confusing to me as it seems like a decent number of blogs rely on this project to operate but the documentation for this entire project is outdated and wrong in many places.
My environment
I'm trying to connect my personal website:

Username: alexwaibel
Repo name: alexwaibel.github.io
Heroku mirror of Staticman: https://staticman-alex-waibel-mirror.herokuapp.com/

Instance variables which I've set:

GITHUB_TOKEN
RSA_PRIVATE_KEY

What I've tried so far

I've attempted to call a GET https://staticman-alex-waibel-mirror.herokuapp.com/v2/connect/alexwaibel/alexwaibel.github.io

This gets me a HTTP 500 which I think is indicative of a problem with the current master branch. I get the following error if I run the server in debug mode:

I've attempted to call a GET https://api.staticman.net//v2/connect/alexwaibel/alexwaibel.github.io

This is met with HTTP 503

Some digging
It seems maybe this problem comes from the connect controller not passing an API version to the Github helper. I'd try changing this myself to test it but I can't even get the server to start :(
It seems someone may have broken the latest build. This repo seems to be kind of a mess. Is there a maintainer still? If so, are you accepting contributors? This is a dependency for my website and I've got some free time lately.

Probably you can look at this PR https://github.com/eduardoboucas/staticman/pull/314(specially this file: https://github.com/eduardoboucas/staticman/blob/d615599118e281d2170a0aa1a1ea43cd8fee8f3b/lib/GitHub.js). I put an hack to fix it. FYI I haven't had the time to fix the tests yet that why travis CLI is failing.

I don't know if @eduardoboucas still maintains the project tbh. I was stuck for months until I switched to @staticmanlab. I'm in the process of searching for a new service to handle comments as it's unfortunately not reliable enough, despite the fast that it's really an elegant solution.

Well... Hopefully @eduardoboucas shows up some time soon. If not I may be able to muster up the time in the near-ish future to  take over and clean it up a bit.

What could be really nice is a proper tutorial on how to deploy your own Staticman instance.
Staticman still works perfectly, but it's plagued by the fact that people are using the free service provided by Eduardo, and it hits Github's limitations. The real way to use it should be for people to deploy their own private instance on Heroku or somewhere else, don't you think?

While I completely agree, have you actually been able to use static man recently? I had to tinker with it to even get it to npm start. If so, I'd love to hear more about your setup.

@VincentTam I see you've done a lot of work on this repo in the past. Do you know of a working commit of this project?

While I completely agree, have you actually been able to use static man recently? I had to tinker with it to even get it to npm start. If so, I'd love to hear more about your setup. @fbnlsr

I haven't deployed my own instance I must admit. I've switched to using @staticmanlab (Vincent's bot) as an emergency backup and plan on deploying my own instance of Staticman (or at least try to) as soon as I have some free time.

I do completely agree that providing users with the instructions to deploy their own instances is for the best. I plan to update add such instructions once I can get my own instance functional again

To answer my own question, this project in the current state of the master branch does not work. The express server does not start and many tests are failing. I've been granted contributor rights and will be working on restoring this repo to working order.

@alexwaibel Sorry for late reply.  The only thing that I remembered now is PR #219.