[Fix #50] Handle directory changes correctly

Actually handle the symlink -> merge directory case.
When this occurs we're processing a change dir op.  Previously we were correctly removing the symlink, but we would fail to then create the actual directory!
Note that this depends on https://github.com/stefanpenner/fs-tree-diff/pull/39

[ ] update to use new fs-tree-diff after https://github.com/stefanpenner/fs-tree-diff/pull/39 merged

Will wrap this up in the AM.

released as v1.1.5


Lookup tokens by username

Can I help in anyway to progress this PR?

@eyalbe4 I have addressed the comments. Can you have another look?

@sebinjohn,
getUserTokensTest fails, when the the user already has tokens. which have been created before.
I suggest modifying the test, so that it fails if the created token (the expected one) is not included in the list of tokens fetched.

@sebinjohn,
getUserTokensTest fails, when the the user already has tokens. which have been created before.
I suggest modifying the test, so that it fails if the created token (the expected one) is not included in the list of tokens fetched.

Done

@sebinjohn,
There still sees to be an issue with the test logic.
The expectedTokenID is not necessarily the token the test has just created. More than that, it can even be a token for a different user.
I recommend using the token returned by the createToken() API, to be the expectedTokenID. There's probably no need to call the testsSecurityService.GetTokens() API in this test.

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

@sebinjohn,
Are you planning to continue working on this?

I'm closing this one for now @@sebinjohn.


update APC link

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
https://github.com/yiisoft/yii2/issues/19209

👍🏻


Request...?

Can you an option to disable it in some worlds?
Example:
In World its disable,
In CPvPMap_1 is not disabled.

The world names you specify will have the feature enabled, whitelist-style. If you leave it blank all worlds will have the feature enabled.


ensure_path method always send NodeExists exception to log.

ensure_path method always send NodeExists exception to log when node already exists.
in session.py, send method, logging all the exceptions then raise it again.

Yeah, it seems like we're catching NodeExists errors in ensure_path but the underlying method is throwing and logging errors anyway. I'm not sure if we want to change this behavior right now.

Hope for changing this behavior, anyway I will close this issue ahead.


UI: Fix alignment of buttons and text

The delete button and theme toggle should be vertically aligned.

Earlier it was:

Let's delete the button with an icon if it doesn't fit.

Hi @muke1908 , I would like to work on this issue.

@aspanaich sure!

@muke1908 , Does this look alright?
Desktop view -

Mobile view -

Yes, looks great!


Clear snackbar timeout timer on unmount (fix for #226)

Thanks!
Could you sqash your commits? :)

Sure :) Done... Sorry about that...


Compiling Eigen 3.3.4 too slow

作者你好，请问你的Eigen3.3.4是怎么安装的呀？我这边自己从源代码编译，都已经编译了6个小时了，还没有结束。在线等，挺急的。

As i know, Eigen library  does not need  to be compiled. You can download the zip file from the website and  including it into your project. If you still have a problem, i can upload my files soon.

I hope that you can upload you files, thank you!

I hope that you can upload you files, thank you!

https://github.com/FeeZhu/Eigen3

got it!


scheme.activate() returns non zero exit status 1

I am trying to connect to a wireless network using wifi library in python script and am running python 3.6.8
Upon executing scheme.activate(), I get the following output
subprocess.CalledProcessError: Command '['/sbin/ifup', 'wlp6s0=wlp6s0-home', '-o', 'wpa-ssid=DataRoom', '-o', 'wpa-psk=902456bdc9a0ff7e7fecf72c303e75d87d4e6bf209e24c36453bc6cc8a9e1ee1', '-o', 'wireless-channel=auto']' returned non-zero exit status 1
I tried to search for the solution but found no related issue.
Thanks for the help

Same issue. Any update?

Also having the same issue with this, I have found a couple of threads that seem to be quite old and no longer relevant / closed and have not solved my issue.
The code i am using is:
`from future import print_function
from wifi import Cell, Scheme, SchemeWPA
get all cells from the air
ssids = [cell.ssid for cell in Cell.all('wlan0')]
schemes = list(Scheme.all())
cell = list(Cell.all('wlan0'))
for scheme in schemes:
ssid = scheme.options.get('wpa-ssid', scheme.options.get('wireless-essid'))
if ssid in ssids:
print('Connecting to %s' % ssid)
scheme.activate()
break`
"SchemeWPA" is a monkey patch job i found in another thread that helped get me here


Configuration data structure refactor

XRTK - Mixed Reality Toolkit Change Request
Overview
A pre-step to consolidating the editor inspector codes for drawing/displaying this list in the editor.
Target of the change:
Is this enhancement for:

Core (core framework, interfaces and definitions)

Changes:

Renamed the serialized backing fields so we can consolidate all the configuration structs into a single type

Breaking Changes:

Renamed BaseMixedRealityProfile.IsCustomProfile to IsEditable
Removed all the existing configuration data structures and consolidated them into one.
 I need to update the inspectors still.

Is this yet ready or is it pending the other PR?

Just need to finish up fixing the inspectors

Inspectors should be done. Only thing left is getting the dropdown filtering working properly again but we can do that later.

Not critical since this is due to be refactored, but Input Action Rules config has stopped working, the dropdowns don't work, not sure if it's related to this change


Change SPHINXOPTS in doc/makefile

Description

Although the recent change by PR #81 fixed the failure, a warning message was found in the step upload_artifact.
The author of sphinx-action recommended the change in this PR.

Anticipated changes to regression tests:

[x] Is baseline change expected ?

Subcomponents involved:

[ ] DA_update (ufs-community/land-DA)
[ ] ufsLand.fd (NOAA-EPIC/ufs-land-driver-emc-dev)
[ ] ufs_model.fd (ufs-community/ufs-weather-model)
[ ] vector2tile_converter.fd (NOAA-PSL/land-vector2tile)
[x] none

Linked PR's and Issues:

Fixes Issue #84
Testing (for CM's):

RDHPCS

[ ] Hera
[ ] Orion
[ ] Jet
[ ] Gaea
[ ] Cheyenne

CI

[ ] Completed

PW-Clouds

[ ] AWS
[ ] AZURE
[ ] GCP

@jkbk2004, please review this PR. As described above, I found a warning message in auto_build of the other PRs. The developer of sphinx-action recommended this change. I don't find the same warning in testing this PR, but I'd like to check it in other PRs once this pr is merged.

Thanks! :)


Occasional Blog

Phil, I know this is not a gpsctl issue per se.  I tried to contact you via the gmail on your occasional blog, no joy.  I think your cookbook on the occasional blog needs some updates.  I'd be glad to help and/or be the guinea pig to test when complete.    Just trying to make contact, feel free to delete this as its off topic.   The email from me is pacbell.net.
ie:
in /etc/udev/rules.d/  the file 80-gps-to-ntp.rules no longer exists.  It's now 99-rules.com
in lsmod | grep pps    I can never get the pps_core to show
hwclock does not survive reboots:
after reboot sudo hwclock -w -v
hwclock from util-linux 2.36.1
System Time:<PHONE_NUMBER>.691253
Trying to open: /dev/rtc0
Trying to open: /dev/rtc
Trying to open: /dev/misc/rtc
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.

My blog says to create that file. It's not wise to mess with system-provided config files.
$ cat /etc/udev/rules.d/80-gps-to-ntp.rules
Change MODE of ttyAMA0 so it is readable by NTP and provide
a symlink to /dev/gps0
KERNEL=="ttyAMA0", SYMLINK+="gps0", MODE="0666"
Symlink /dev/pps0 to /dev/gpspps0
KERNEL=="pps0", SYMLINK+="gpspps0", MODE="0666"
No idea why hwclock isn't working for you.

Started all over, clean slate.
Still do not get pps_core from lsmod | grep  pps
sudo ppstest /dev/pps0 fills with errors:
sudo ppstest /dev/pps0
trying PPS source "/dev/pps0"
found PPS source "/dev/pps0"
ok, found 1 source(s), now start fetching data...
source 0 - assert<PHONE_NUMBER>.010717963, sequence: 72 - clear  0.000000000, sequence: 0
time_pps_fetch() error -1 (Connection timed out)
time_pps_fetch() error -1 (Connection timed out)
time_pps_fetch() error -1 (Connection timed out)
time_pps_fetch() error -1 (Connection timed out)
Yes, I've read your postscript and tried to follow, however,
The line hw-clock-set with --systz -- badyear
The line  --systx only does exist
Then there is a line with --hctosys ???
When I go to run sudo configure-r3028.sh I am told "command not found", though it clearly exists in the prescribed directory.
I'm just following your cookbook.
Step for step.
All is well until lsmo | grep pps
As I mentioned in my email... if you got it, the 80-gps-to-ntp.rules does not exist and your instructions say to edit it...  not create it.   I realize you can do both, but it's not clear.
Phil, I really want to make this work, I'm retired and have done a fair amount of technical writing, I'd like to help clean this up and make the changes inline for your postscript notes...   I'll be the first to admit I don't know this stuff as well as you.  I think your build is superior as it eliminates the location and motion elements of GPS, but there have been a lot of updates the past few years.

pi@RPi4b-NTP-GPS:~/gpsctl $ sudo configure-rv3028.sh
sudo: configure-rv3028.sh: command not found
pi@RPi4b-NTP-GPS:~/gpsctl $ ls -la
total 680
drwxr-xr-x 3 pi pi   4096 Sep 20 16:01 .
drwxr-xr-x 4 pi pi   4096 Sep 20 16:21 ..
-rwxr-xr-x 1 pi pi    554 Sep  8 11:52 build.sh
-rw-r--r-- 1 pi pi   4950 Sep  8 11:52 Changelog
-rw-r--r-- 1 pi pi  77959 Sep  8 11:52 cJSON.c
-rw-r--r-- 1 pi pi  16193 Sep  8 11:52 cJSON.h
-rw-r--r-- 1 pi pi    414 Sep  8 11:52 CMakeLists.txt
-rwxr-xr-x 1 pi pi    956 Sep  8 11:52 configure-rv3028.sh
-rw-r--r-- 1 pi pi  11921 Sep  8 11:52 dictionary.c
-rw-r--r-- 1 pi pi   6647 Sep  8 11:52 dictionary.h
drwxr-xr-x 4 pi pi   4096 Sep  8 11:52 etc
-rw-r--r-- 1 pi pi     75 Sep  8 11:52 gdbserver.cmd
-rwxr-xr-x 1 pi pi    189 Sep  8 11:52 gdbserver.sh
-rwxr-xr-x 1 pi pi 174616 Sep 20 16:01 gpsctl
-rw-r--r-- 1 pi pi  66873 Sep  8 11:52 gpsctl.c
-rwxr-xr-x 1 pi pi     68 Sep  8 11:52 gpsctl_output.sh
-rw-r--r-- 1 pi pi  31420 Sep  8 11:52 iniparser.c
-rw-r--r-- 1 pi pi  16091 Sep  8 11:52 iniparser.h
-rw-r--r-- 1 pi pi     16 Sep  8 11:52 kill.cmd
-rwxr-xr-x 1 pi pi     52 Sep  8 11:52 kill.sh
-rw-r--r-- 1 pi pi   1073 Sep  8 11:52 LICENSE
-rwxr-xr-x 1 pi pi    217 Sep  8 11:52 prepare.sh
-rw-r--r-- 1 pi pi  10511 Sep  8 11:52 README.md
-rw-r--r-- 1 pi pi      6 Sep  8 11:52 remote_options.txt
-rwxr-xr-x 1 pi pi    114 Sep  8 11:52 run.sh
-rw-r--r-- 1 pi pi   2960 Sep  8 11:52 sl_bits.c
-rw-r--r-- 1 pi pi    367 Sep  8 11:52 sl_bits.h
-rw-r--r-- 1 pi pi   9350 Sep  8 11:52 sl_buffer.c
-rw-r--r-- 1 pi pi   1797 Sep  8 11:52 sl_buffer.h
-rw-r--r-- 1 pi pi   5509 Sep  8 11:52 sl_general.c
-rw-r--r-- 1 pi pi   2010 Sep  8 11:52 sl_general.h
-rw-r--r-- 1 pi pi  37283 Sep  8 11:52 sl_options.c
-rw-r--r-- 1 pi pi   4482 Sep  8 11:52 sl_options.h
-rw-r--r-- 1 pi pi   2164 Sep  8 11:52 sl_options.txt
-rw-r--r-- 1 pi pi  12589 Sep  8 11:52 sl_return.c
-rw-r--r-- 1 pi pi   2331 Sep  8 11:52 sl_return.h
-rw-r--r-- 1 pi pi  13487 Sep  8 11:52 sl_serial.c
-rw-r--r-- 1 pi pi   1112 Sep  8 11:52 sl_serial.h
-rw-r--r-- 1 pi pi  56520 Sep  8 11:52 ublox.c
-rw-r--r-- 1 pi pi  11579 Sep  8 11:52 ublox.h

OK the problem is Bullseye.  I backed off to the latest version of Buster at RPi and have gotten a bit further.  At least seeing the pps_core.
pi@RPi4b-NTP-GPS:~ $ lsmod | grep pps
pps_gpio               16384  0
pps_core               16384  1 pps_gpio
pi@RPi4b-NTP-GPS:~ $ dmesg | grep pps
[    3.028722] pps_core: LinuxPPS API ver. 1 registered
[    3.028766] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    3.042234] pps pps0: new PPS source<EMAIL_ADDRESS>[    3.042356] pps pps0: Registered IRQ 66 as PPS source
And PPS test isn't throwing errors
pi@RPi4b-NTP-GPS:~ $ sudo ppstest /dev/pps0
trying PPS source "/dev/pps0"
found PPS source "/dev/pps0"
ok, found 1 source(s), now start fetching data...
source 0 - assert<PHONE_NUMBER>.001079928, sequence: 5092 - clear  0.000000000, sequence: 0
source 0 - assert<PHONE_NUMBER>.001079604, sequence: 5093 - clear  0.000000000, sequence: 0
source 0 - assert<PHONE_NUMBER>.001081215, sequence: 5094 - clear  0.000000000, sequence: 0
source 0 - assert<PHONE_NUMBER>.001082352, sequence: 5095 - clear  0.000000000, sequence: 0
source 0 - assert<PHONE_NUMBER>.001084813, sequence: 5096 - clear  0.000000000, sequence: 0

Have you done

sudo apt update
sudo apt full-upgrade

and rebooted?

Yes, Sir.   If it's in your cookbook, I'm following it set by step.
One of the other builds I did (Kreeblah, here on Github) had an issue I found that was OS related, so I pulled the versions of Buster around the time you wrote your build but I decided to start with the latest version of Buster still accessible via the Pi imager - Legacy, Buster, Lite.    The build fails if I start with Bullseye image, As you see, it works if I start with Buster... and do the full-upgrade.  I stopped after the "ppstest /dev/pps0" last night.  I'll pick back up with "Enabling PPS/ATOM" after I have breakfast.
Is there any specific points in the process you feel are the best to process your postscripts?

Starting with Buster and following your cookbook, everything is as your cookbook shows (for the first time).  I have a complete build save the June 21, 2020 postscript.   Once I get to "sudo configure-rv3028.sh" the systems says it is not found even though I am IN the directory where it resides.   Oh, and I'm running a ver 6.3 Uputronics GPS hat
pi@RPi4b-NTP-GPS:~/gpsctl $ sudo configure-rv3028.sh
sudo: configure-rv3028.sh: command not found
So if you have a fix for the above error, I think I have a complete, working system.  If you are saying it is not a necessary step, then this should be good.  I'll wait for you before I run the hwclock write.
Incidentally, on my first run at your build I got greedy and used a 64bit version of Bullseye.  It failed early.   I've seen this before where you can start old and work your way to current... But you can't start current.   Ie: there is a HUGE difference in the presentation of /lib/udev/hwclock-set between a Buster and a Bullseye start point.  Buster gives me exactly what you indicated.  A Bullseye build does not.

Use the full path to the configure script, or ./ in front of it.
I honestly can't replicate your issues.
I built from scratch using bullseye 64-bit, and fixed any errors that I found in my blog post in the process.

Thanks, Phil.  That worked.   Seems to be fully working as per your cookbook.  I'll clone this SD card before walking the update path.
Did you use a full raspian 64 bit load or the lite?

I used the 64-bit Raspi OS lite build.
On Thu, 21 Sept 2023, 16:48 Falcon-118, @.***> wrote:

Thanks, Phil. That worked. Seems to be fully working as per your cookbook.
I'll clone this SD card before walking the update path.
Did you use a full raspian 64 bit load or the lite?
—
Reply to this email directly, view it on GitHub
https://github.com/philrandal/gpsctl/issues/21#issuecomment-1729851822,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADRPDNFSCLJNPOMMPQREQDX3ROWJANCNFSM6AAAAAA5AJ5ENU
.
You are receiving this because you commented.Message ID:
@.***>

I sent this over to one of the kids who used to work for me, he stays pretty active in this stuff.   He says judging by your build and note dates, he is guessing your build was in or before 2020?  In which case the 64bit build would have been Debian 10 Buster.  So maybe that is the catch.  Who knows?   After I clone and update...  work in your auto update...   do some testing and tuning... I may try an older 64 bit load out.
  Raspbian has only been available as ARMHF 32bit.
  Raspberry Pi ARMHF Operating System May 2020 onwards is based off Raspbian.
  Raspberry Pi ARM64 Beta and Early release Operating System was based off Debian 10 Buster.

Also, just a tidbit from my past.  I started my adult life as a US Navy fighter pilot and went on to work in the Dark World for a number of years.   You really don't want to use GLONASS for time...

My 64-bit build was bullseye

Ok, I have working copies of your build both on 32bit and 64bit platforms.  But even on the 64bit I had to revert to Buster to get things to work from your cookbook.  Fortunately as I've gone through this process, I have two of the Uputronics hats and a few RPi4b/2GB.   The key to the builds working completely is seeing the pps_core when you run lsmod.
The build works per your instructions with the latest 64bit Buster (2021-05-07) but not the earliest Bullseye (2021-10-30) from the Raspberry Pi archives.   I think I've built your system up about 12 times now.
Curious, did you have access to an early Beta of 64bit Bullseye?  Your latest postscript is dated October 17, 2020 but the earliest 64bit Bullseye image Raspberry Pi support could provide was October 30, 2021.
You are obviously more proficient with the Pi stuff than I am...  Would you suggest upgrading to Bullseye before working on the auto-update and tuning or after?   Either way, I'll get the 64bit image archived (so I don't have to build it again...) and start working on the rest of your document.
Thank you plowing this path.   I'm glad to have this up and running for my pfSense box.

I edited the blog post, and didn't update the postscript date or time.
Unfortunately I don't have the time to do a complete rebuild to triple-check.
I'll probably wait until the bookworm release of RaspiOS is released before trying a rebuild.
Sorry you're having so many issues.

Waiting for Bookworm is probably the best bet.   I understand about being busy, BTDT.   Seems everything today eats more time with less rewards.
But...   If/when you do decide to look into this, my offer to help with the testing and/or the documentation stands.  My way of helping and saying thanks.
You should have my email in your gmail account listed on your Occasional Blog... or you can reach me here.

Phil, everything seems to be running fine on this end, just doing some checking and cleanup.  I notice when I view the gpsctl config file the top of the display shows entries for the Antenna and power...   but those are not in the /etc/gpsctl.conf file.   I am running an active u-Blox ANN-MB-00 (3.0-5.0vdc) antenna.  Do those settings need to be set and if so, where?  Or are they auto set?
pi@RPi4b-NTP-GPS:~ $ /usr/local/bin/gpsctl -a -Q config
U-Blox GPS configuration
Antenna:
Power enabled:                no
Short detection:              no
Open detection:               no
Power down on short:          no
Auto recovery from short:     no

Short answer: The code is there to inspect.
I think those are just the defaults. I just parameterised the stuff in the original gpsctl when I forked it.
My main intent was to be able to enable Galileo support. Anything else was a bonus.

I've rebuilt my server using bookworm 64-bit and updated my blog post to match.
ntp.conf updated to use ntpsec "refclock" lines instead of the old ntp.conf style "server" lines for our GPS clock sources.

I didn't want to touch antenna power settings as I have no way of testing, sorry.

Phil, I've been up and running fine for a few weeks and seems very stable after a couple rounds of tuning.   But since you posted the new updates for running under Bookworm, I wanted to give it a try.  I have the extra, hat and antenna.
Need some clarification if you will.   Under the section where you edit ntp.conf  (now moved from /etc to /etc/ntpsec) you used to have the "server <IP_ADDRESS> mode....." and the "fudge <IP_ADDRESS> flag1..." lines in the ntp.conf file.   Those are no longer in that file or your example, but your very next line in the instructions still has your note:  (Note that I used “fudge <IP_ADDRESS> time2 0.050....)
So should the note about server and fudge be omitted or do those lines need to be added back to ntp.conf?

The refclock lines replace the server / fudge pairs.
The links to the ntpsec docs explain the syntax.
I'll fix my blog post.
Now to get it working on my Pi 5....  I'm getting "could not synchronise".  Arrgh!  Not sure when I'll have the timne to dig deeper.

Thanks, I'll play with this some more.  I followed your new cookbook step for step but I'm having an issue getting the asterisk to move to NMEA instance.  It wants to stay on the "preferred" server entry.
pi@RPi4b-NTP-GPS:~ $ ntpq -p
remote
oPPS(0)                                         .PPS.
NMEA(0)                                      .GPS.
*montpelier.ilan.caltech.edu           .GPS.
-tick.usnogps.navy.mil                   .IRIG.
+time-a-b.nist.gov                       .NIST.
+timekeeper.isi.edu                      .GNSS.

refclock nmea prefer minpoll 4 maxpoll 4 mode 8 stratum 2 baud 115200 time2 0.060 path /dev/ttyAMA0
Not sure if you need a prefer line on any of the other server lines

OK, the cookbook still has "Note You MUST add a preferred server or PPS doesn’t work"

That's in the refclock line
On Sun, 22 Oct 2023, 20:09 Falcon-118, @.***> wrote:

OK, the cookbook still has "Note You MUST add a preferred server or PPS
doesn’t work"
—
Reply to this email directly, view it on GitHub
https://github.com/philrandal/gpsctl/issues/21#issuecomment-1774174672,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADRPDKAKLTX7STEF4G6KZ3YAVVPXAVCNFSM6AAAAAA5AJ5ENWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZUGE3TINRXGI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

OK, thanks...  now NMEA is preferred.   (you also still show the preferred in the section above on the first server stated)
Now that you are using refclock, is it still necessary to process the instructions in your June 21, 2020 postscript? re: rv3028 and hwclock

If you're using a Uputronics HAT with built-in RTC, then my instructions should still apply.

Thanks, Phil.   I did do some research and reading on the RTC_UIE_ON error when you run the hwclock read.   Surprised it hasn't been fixed yet in the OS.
ioctl(4, RTC_UIE_ON, 0): Invalid argument
Anyway, with your changes and updates, the system builds fine under bookworm.   I'll play with the timing a bit then put it into production!

Phil,  I've let things run a day or more to stabilize with the antenna mounted outdoors.  Starting in on the tuning.
Is there a slash missing on the command line between the ntpsec service stop/start?
It reads:  sudo rm –f /var/log/ntpsec*
Should it be:  sudo rm –f /var/log/ntpsec/*

Well spotted.
Tuning isn't that complicated - it's only for the pedantic who want to get as close as possible to perfection. The NMEA offset seems to vary depending on how many GPS satellites are in view at the time, probably due to processing overheads in the ublox chipset.
Also, you can point your browser at http://<your pi's IP address>/ntpviz for graphical stats.

Well spotted.

I guess that's a nice way of saying "a bit anal"... and yeah, I've was accused of that most of my career, but it served me well.    Agreed on the pedantic part, too... but not so intense.  I'll run a couple of sessions and do some coarse tweeking.  Maybe run through it again in a few months.
But, that said.  Looks like you've now removed the lines referencing the 2 lines for stats 1 for filegen.  So is there no edit needed of /etc/ntpsec/ntp.conf anymore?
You previously stated you replaced the server and fudge statements with refclock.  But the cookbook still calls for "placing a noselect in the ntp.conf GPS line." (which is now the NMEA line)    So do we add a noselect to the refclock statement before running for offset files to process?
You also still state "When you’re done, remove the noselect from the server <IP_ADDRESS> line in ntp.conf."  But there is no longer a <IP_ADDRESS> line in the ntp.conf file.   Confusing.   Can you revisit the tuning section?  it seems to be a mix of old an new.
I hope you don't look at this as complaining, it's not intended that way.   I'd just like to get it right and I still think yours is the optimum approach for using the uputronics hat for a GPS/PPS/NTP server at this time and I'd like to steer others your way... to  working roadmap.
And thanks for the access link to the graphical stats.  That'll be very helpful the longer I run this.

Some people say using gpsd as the clock source (using SHM) is better as its NMEA handling is allegedly better than ntpd's.  I prefer to avoid middlemen where possible.
The NMEA clock offset calculation is a rough averaging exercise. I just guessed, ran for a while, adjusted, and so on iteratively without any noselect lines.
I've added linux-cpupower and a systemd unit for setting the "performance" cpu governor. This should give optimum stability.

I'm new to all this GPS/NPT stuff...  though I learned a fair bit about GPS and flew (Navy) with it's systems in the 80s before Reagan released it for public/commercial concerns.    I had built several systems using GPSD prior to finding yours.  While GPSD has some interesting aspects (like being able to monitor the live data via GPSMON).  It just seemed to have too much overhead for a system that will go largely unmonitored.    Not really analyzing if from an operational standpoint, but seeing the memory usage and the CPU usage by the heat load on the CPU...  The previous build used almost all the onboard memory and using the High Pi Pro case with a PWM fan, the fan ran constantly.   Your build is just the opposite, 2/3 of the memory is free and I've never seen a CPU temp over 45° C (and the minimum PWM control temp on the RPi is 60° C).   Not worrying about where it is, what direction or how fast it is moving just seems like the best way to run a system with an antenna that is bolted to the side of my back deck on a custom built arm.
  It has something to do with Nginx web code they use...
I'll look into your new stuff.  Is it in the Occasional Blog?

I've updated my blog.  It would be interesting to see what your PPS jitter settles down as.

sudo systemctl enable ntpsec.service
should do it.
You, like me, are using time.google.com.
If there are every any more leap seconds announced this won't be wise, as Google do gradual adjustment of their time to deal with leap seconds, instead of leaping.

Phil
Eventually, the "systemctl" itself was the culprit...  somehow it got compromised and was truncating input.  I didn't find it but I stopped by the local JC maker space and asked for some help and was steered to a young lady who was their go-to for Raspberry Pi.   She found the problem and once she got systemctl back to normal (removed/installed), we enabled ntpsec.service and it starts on boot now.   She thought it was a cool project and wants to build one.  So as thanks, I gave her my backup GPS hat and pointed her to your blog post.   Now I need to order another backup hat.
Google thing: Are you talking about "leap smear" or something like that?   If so, I read about that, but wasn't sure its impact...?  Are all their time servers running in that mode?  Or do you think it may become a standard across all REFIDs?
Do you have/know an IRIG server that has good returns?  Every one I tried had 3 digit returns.


Add gcollazo-mongodb, another MongoDB.app contender

The mongodb.rb cask tracks a project that seems to have stalled
out.  I have found another project that also provides a varient
of the MongoDB.app that is much more up-to-date

Thanks @aguynamedryan!


How to put requests from one consumer in queue (Lock feature)

I'm using kong as API gateway for frontend. How can I prevent multiple requests from frontend at the same time?
Expected options:

Kong put requests to the specific route from the same consumer to the queue.
Kong cancel requests to the specific route from the same consumer if there is active request already.

Example:
Consumer do 5 POST requests to the route '/api/order'.

Kong put all requests in queue and process each request in order after previous sent response.
Kong take first request and reject all rest requests to this specific route from that consumer while our first request is performing.

Interesting use case. How should this work on a Kong cluster? Ideas?

I imagine the second case would be very straightforward to do via cluster_mutex (or a local redis might be faster in a single DC deployment).
Queueing up requests would take a bit more logic, again, pretty easy to do with a local redis queue used and Kong consuming that queue.
Either option requires a custom plugin :)

@lavernyer to be clear, neither of these options is possible today. However, it's possible to extend Kong via plugins (see https://docs.konghq.com/1.1.x/plugin-development/), so you can develop the business logic you need here and implement it via a plugin for Kong.


CSP for "DisableOneDriveFileSync"

Hello,
We applied the following Intune rule to disable OneDrive for all the laptops. Windows version: Windows 10 Pro Ver. 10.0.19045.2846
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/System/DisableOneDriveFileSync
Value: 1
As mentioned in the documentation , OneDrive icon should disappear from the File Explorer, however we can still see it, create files and folders. It is worth noting that the corresponding registry has been created HKLM\Software\Policies\Microsoft\Windows\OneDrive\ DisableFileSyncNGSC and was set to 1 (in a nutshell, the Intune rule was correctly applied).
By any chance, this CSP policy is supported by Windows 10 Pro Ver. 10.0.19045.2846 ?
Best,
L.
(admin edit: add article metadata for proper linking)

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

ID: 2c833e5b-0fcf-2ace-a90a-3270286d23a9
Version Independent ID: 64afbc38-e7cc-fc14-9d57-1cd119b2395d
Content: System Policy CSP - Windows Client Management
Content Source: windows/client-management/mdm/policy-csp-system.md
Product: windows-client
Technology: itpro-manage
GitHub Login: @vinaypamnani-msft
Microsoft Alias: vinpa

I think this might be moot, as the page is auto-generated now from the DDF, but hoping @vinaypamnani-msft can review and confirm.

@laurentdelosieresfact I tested and just setting the GPO does disable OneDrive file sync, but the icon remains in the File Explorer navigation.
I want to make sure it gets directly into the hands of the engineering team. Fortunately, we've got dedicated channels for that very purpose. :)
For more info, see Send feedback to Microsoft with the Feedback Hub app.
I think it’s important that you submit it directly, because that allows you to receive notifications and more closely monitor the progress. I'm closing this issue as there's nothing actionable for docs at this time.


prevent searchbar from being hidden by header?

I keep running into this issue where the searchbar for docs using this theme becomes hidden if the user scrolls down the page far enough, is there a way to configure it to never move up past the bottom of the header? Attached is a screenshot from the demo docs page of this in action.

I don't know exactly when this issue was solved but I'm enable to reproduce your issue in v0.9. Note as well that this should definitevely be closed when #744 will be merged as the search bar won't be in the sidebar anymore.


HAWQ-1779. Add GitHub Action for building on macOS

Since building HAWQ on macOS(and also other platform) relies on several
dependency libraries, which are hard to track version via Homebrew, a
prebuilt dependency leave developers free from the tedious work.
Such process is easy to maintain and verify via GitHub Action. The
workable workflow file also indicates the new users on how to build
Apache HAWQ on macOS quickly.
This commit disables the previous problematic Travis CI as well.

Refer to here for the run result.

Refer to here for the run result.

LGTM +1

LGTM +1


Part table extra options

Add extra stock information as a drop-down in the part table

@SchrodingersGat that renderer should probably be it's own function/component so it can be reused in other places

@SchrodingersGat that renderer should probably be it's own function/component so it can be reused in other places

Would be good to factor this out into its own component


test(app): Upgrade flutter test with custom scope feature

Signed-off-by: Talwinder kaur<EMAIL_ADDRESS>

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (f5616d7) 89.02% compared to head (a192cb5) 89.02%.
 Consider uploading reports for the commit bcda680 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #688   +/-   ##
=======================================
  Coverage   89.02%   89.02%
=======================================
  Files         103      103
  Lines        4218     4218
=======================================
  Hits         3755     3755
  Misses        312      312
  Partials      151      151

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Not able to perform query/Mutation to database usnig prisma beta version

Description
I had updated the prisma to the beta version by uninstalling the earlier version from local project and globally installed. And tried deploying below datamodel with prisma beta version.
Datamodel
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
  output   = "./generated/client"
}

model User {
    UserId              String   @default(cuid()) @id
    FirstName           String
    LastName            String?
    Address             String?
    Email               String?
    posts               Post[]
}

model Post {
    PostId              String   @default(cuid()) @id
    title               String
    User                User
}

After Migrating the database first of all As specified by datamodel, model relationship does not get created in empty database.
And then genarated the prisma client by prisma2 generate command.
Expected Result:

Model relationship should get created in database after migration
I should be able to perform query and mutation using generated prisma client

Actual Result:

Model relationship does not get created in database after migration
By using generated prisma client, not able to perform the query and mutation It returns the below error

Error occurred during query execution:
InterpretationError("Error for binding \'1\': DomainError(ConversionFailure(\"record identifier\", \"assimilated record identifier\"))")
    at PrismaClientFetcher.request (D:\Sameer_Chorge\Projects\Demos\Multi_tenant_pkg\prisma\generated\client\runtime\index.js:1:51485)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

I performed the simple Mutation on post model :
const { PrismaClient } = require('./prisma/generated/client');
const prisma = new PrismaClient();
prisma.post.create({
    data: {
        title :"User1 First Post",
        User : {
            create: {
                FirstName : "user2"
            }
        }
    }
}).then((createdPost) => {
    console.log("createdPost");
    console.dir(createdPost);

}).catch((err) => {
    console.log("createPost Err");
    console.dir(err);
});

System:
@prisma/cli: ^2.0.0-beta.1
@prisma/client: ^2.0.0-beta.1

This datamodel is not valid (and our validation is unfortunately not telling you yet. This will be fixed soon.) Check the release notes for instructions and explanation: https://github.com/prisma/prisma/releases/tag/2.0.0-beta.1

Thank You @janpio
Closing this issue, After changing the datamodel as per suggested in release documents, I was able to perform the query and mutation without any problem.


Investigate differences in heap cost for Cats/Scalaz w/r/t hylo

The large TList/TListK tests cause StackOverflow exceptions in the Scalaz version of Iota. Investigate how to minimize the stack depth per recursion step of hylo.

Closing; this won't be needed when #116 is implemented.


external ip in demo.yaml

Add a script to update demo.yaml to update the external ip.

Updated do-all.sh to deploy application also. get-address.sh creates demo.yaml with the updated external ip address.


Tokio branch is strange

Hi,
I'm interested in implementing LDAP client library on top of tokio. Your project looks interesting, but some things look weird. It looks like you're going to implement tokio loop into LDAP structure. This isn't how protocols on top of tokio are usually written. I.e. they usually expose some things implementing Future/Steam/Sink/Service interface and are hosted in users' own main loop (coexisting with other things in the same loop).
So what's the plan? Do you want to expose tokio-friendly interface, or are you going to hide as much of the networking stuff as possible and expose only synchronous interface?

The current structure is very much a result of me trying out tokio and learning it. If you look at 824389ed8abb194f0acaefa217a167ae17ca2c51 you can see the startings of the API I am trying to implement; you have a Ldap structure that is a small abstraction of the underlying transport mechanism - be it LDAP, LDAPS or LDAPI (Unix sockets) - and an LdapSync structure that contains an Event Loop and will provide synchronous functions if you want a simpler API.
For what it's worth the current state of the library is unusable for anything except the most basic use-cases (simple_bind[_s] work).

Yeah. This one looks fine.
Any plans on "search"? Basically what I need is working bind and search.

Search is the next functionality I will add to this crate.
That however requires rather deep changes, since search in LDAP does not
return one single response but many responses over time containing parts
of the result. Tokio however is written with a protocol in mind that
returns only one response for each request.

Well, you probably mean tokio-proto. Tokio (core) is not limited to any pattern. But there are also two points:

tokio-proto has streaming interface right for this case
even if there are many responses over time it doesn't mean every client needs to read them over time, buffering all of them into a Vec<Response> is good enough for 99% use cases

tokio-proto has streaming interface right for this case

Correct, I am using that interface to implement said changes right now,
but I haven't pushed those yet.

even if there are many responses over time it doesn't mean every
client needs to read them over time, buffering all of them into a
Vec<Response> is good enough for 99% use cases

Yes, also changing the response type of one request type but not all
others (Future for most, Stream for search) is rather complex.
I might later implement a change like that but for now search simply
returns a Future over a Vec<SearchEntry>.

While very unstable and riddled with unwraps, basic search functionality works now.

Thanks! It worked for example request. On invalid request, the search_async example hangs, though (I'm not reporting it as I assume you're aware of many issues of this prototype). Anyway, I'm looking forward to integrate it into my toy projects :)


Use shared-config-file with the ex_aws

At first, thank you for providing useful OSS!
I want to switch account with profile parameter.
Can I use aws-shared-config-file(~/.aws/credentials) with the ex_aws?
For example, the content of file is like this.
[default]
aws_access_key_id=yourawsaccesskey1
aws_secret_access_key=yourawssecretaccesskey1

[profile2]
aws_access_key_id=yourawsaccesskey2
aws_secret_access_key=yourawssecretaccesskey2

For Ruby, like this
shared_credentials = Aws::SharedCredentials.new(profile_name: 'profile2')
s3_api_client = Aws::S3::Client.new(region: 'ap-northeast-1', credentials: shared_credentials)
...

can ex_aws like this?

https://github.com/CargoSense/ex_aws/pull/245 was just merged into master, which handles this situation.


etcd2 (bug?): env variables are not loaded on reboot

I have etcd2 set up from cloud-config on AWS.
#cloud-config
coreos:
  update:
    reboot-strategy: off

  etcd2:
    name: master
    listen-client-urls: http://<IP_ADDRESS>:2379
    listen-peer-urls: http://<IP_ADDRESS>:2380
    advertise-client-urls: http://$private_ipv4:2379
    initial-advertise-peer-urls: http://$private_ipv4:2380
    initial-cluster: master=http://$private_ipv4:2380
    initial-cluster-token: k8s_etcd
    initial-cluster-state: new

When the instance is rebooted, etcd2 does not respect any of the above values. Starts with localhost:2379 instead of <IP_ADDRESS>:2379 for example. This resulted in a k8s cluster outage for some time.
$ journalctl -u etcd2

-- Reboot --
Feb 09 21:09:30 ip-172-32-1-129.ec2.internal systemd[1]: Starting etcd2...
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: recognized and used environment variable ETCD_DATA_DIR=/var/lib/etcd2
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: recognized and used environment variable ETCD_NAME=db57595c09c94a13a0bd15c7f0423837
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: etcd Version: 2.3.7
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: Git SHA: fd17c91
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: Go Version: go1.7.3
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: Go OS/Arch: linux/amd64
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: setting maximum number of CPUs to 1, total number of available CPUs is 1
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: the server is already initialized as member before, starting as etcd member...
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: listening for peers on http://localhost:2380
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: listening for peers on http://localhost:7001
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: listening for client requests on http://localhost:2379
Feb 09 21:09:31 ip-172-32-1-129.ec2.internal etcd2[815]: listening for client requests on http://localhost:4001
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: recovered store from snapshot at index 2270227
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: name = db57595c09c94a13a0bd15c7f0423837
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: data dir = /var/lib/etcd2
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: member dir = /var/lib/etcd2/member
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: heartbeat = 100ms
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: election = 1000ms
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: snapshot count = 10000
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: advertise client URLs = http://localhost:2379,http://localhost:4001
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: restarting member a3c26d075afd717e in cluster a5ca89fce9cddded at commit index 2273197
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: a3c26d075afd717e became follower at term 2
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: newRaft a3c26d075afd717e [peers: [a3c26d075afd717e], term: 2, commit: 2273197, applied: 2270227, lastindex: 2273197, lastterm: 2]
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: added member a3c26d075afd717e [http://<IP_ADDRESS>:2380] to cluster a5ca89fce9cddded from store
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: set the cluster version to 2.3 from store
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: starting server... [version: 2.3.7, cluster version: 2.3]
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal systemd[1]: Started etcd2.
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: a3c26d075afd717e is starting a new election at term 2
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: a3c26d075afd717e became candidate at term 3
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: a3c26d075afd717e received vote from a3c26d075afd717e at term 3
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: a3c26d075afd717e became leader at term 3
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: raft.node: a3c26d075afd717e elected leader a3c26d075afd717e at term 3
Feb 09 21:09:32 ip-172-32-1-129.ec2.internal etcd2[815]: published {Name:db57595c09c94a13a0bd15c7f0423837 ClientURLs:[http://localhost:2379 http://localhost:4001]} to cluster a5ca89fce9cddded

However, if I simply systemctl restart etcd2, everything starts as expected.
$ journalctl -u etcd2

Feb 10 00:26:10 ip-172-32-1-129.ec2.internal systemd[1]: Starting etcd2...
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recognized and used environment variable ETCD_ADVERTISE_CLIENT_URLS=http://<IP_ADDRESS>:2379
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recognized and used environment variable ETCD_DATA_DIR=/var/lib/etcd2
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recognized and used environment variable ETCD_ELECTION_TIMEOUT=1200
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recognized and used environment variable ETCD_INITIAL_ADVERTISE_PEER_URLS=http://<IP_ADDRESS>:2380
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recognized and used environment variable ETCD_INITIAL_CLUSTER=master=http://<IP_ADDRESS>:2380
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recognized and used environment variable ETCD_INITIAL_CLUSTER_STATE=new
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recognized and used environment variable ETCD_INITIAL_CLUSTER_TOKEN=k8s_etcd
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recognized and used environment variable ETCD_LISTEN_CLIENT_URLS=http://<IP_ADDRESS>:2379
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recognized and used environment variable ETCD_LISTEN_PEER_URLS=http://<IP_ADDRESS>:2380
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recognized and used environment variable ETCD_NAME=master
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: etcd Version: 2.3.7
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: Git SHA: fd17c91
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: Go Version: go1.7.3
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: Go OS/Arch: linux/amd64
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: setting maximum number of CPUs to 1, total number of available CPUs is 1
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: the server is already initialized as member before, starting as etcd member...
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: listening for peers on http://<IP_ADDRESS>:2380
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: listening for client requests on http://<IP_ADDRESS>:2379
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: recovered store from snapshot at index 2320232
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: name = master
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: data dir = /var/lib/etcd2
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: member dir = /var/lib/etcd2/member
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: heartbeat = 100ms
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: election = 1200ms
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: snapshot count = 10000
Feb 10 00:26:10 ip-172-32-1-129.ec2.internal etcd2[2900]: advertise client URLs = http://<IP_ADDRESS>:2379
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: restarting member a3c26d075afd717e in cluster a5ca89fce9cddded at commit index 2321659
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: a3c26d075afd717e became follower at term 5
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: newRaft a3c26d075afd717e [peers: [a3c26d075afd717e], term: 5, commit: 2321659, applied: 2320232, lastindex: 2321659, lastterm: 5]
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: added member a3c26d075afd717e [http://<IP_ADDRESS>:2380] to cluster a5ca89fce9cddded from store
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: set the cluster version to 2.3 from store
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: starting server... [version: 2.3.7, cluster version: 2.3]
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal systemd[1]: Started etcd2.
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: a3c26d075afd717e is starting a new election at term 5
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: a3c26d075afd717e became candidate at term 6
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: a3c26d075afd717e received vote from a3c26d075afd717e at term 6
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: a3c26d075afd717e became leader at term 6
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: raft.node: a3c26d075afd717e elected leader a3c26d075afd717e at term 6
Feb 10 00:26:11 ip-172-32-1-129.ec2.internal etcd2[2900]: published {Name:master ClientURLs:[http://<IP_ADDRESS>:2379]} to cluster a5ca89fce9cddded

$ sudo systemctl cat etcd2: Output
$ sudo systemctl show etcd2: Output

Found similar issues in https://github.com/coreos/bugs/issues/396 and https://github.com/coreos/bugs/issues/947
But it's not solved or documented anywhere. I don't have any dependency on etcd2 in my systemd configs.

@Bekt It seems like whatever is booting etcd is losing the config before passing it as environment variables. Can you confirm that the etcd process is being given the right set of environment variables in the first place?
$ cat /proc/<ETCD-PID>/environ | tr '\000' '\n' | grep ETCD

On reboot (problematic case)
$ systemctl status etcd2: output
$ systemctl show etcd2: output
$ systemctl cat etcd2: output (notice how env variables are present here)
core@ip-172-32-1-129 ~ $ sudo cat /proc/697/environ | tr '\000' '\n'
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
NOTIFY_SOCKET=/run/systemd/notify
HOME=/dev/null
LOGNAME=etcd
USER=etcd
SHELL=/sbin/nologin
JOURNAL_STREAM=8:13694
ETCD_DATA_DIR=/var/lib/etcd2
ETCD_NAME=db57595c09c94a13a0bd15c7f0423837

After systemctl restart etcd2
$ systemctl status etcd2: Output
$ systemctl show etcd2: Output
$ systemctl cat etcd2: identical as the first case
core@ip-172-32-1-129 ~ $ sudo cat /proc/7008/environ | tr '\000' '\n'
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
NOTIFY_SOCKET=/run/systemd/notify
HOME=/dev/null
LOGNAME=etcd
USER=etcd
SHELL=/sbin/nologin
JOURNAL_STREAM=8:113812
ETCD_DATA_DIR=/var/lib/etcd2
ETCD_NAME=master
ETCD_ELECTION_TIMEOUT=1200
ETCD_ADVERTISE_CLIENT_URLS=http://<IP_ADDRESS>:2379
ETCD_INITIAL_ADVERTISE_PEER_URLS=http://<IP_ADDRESS>:2380
ETCD_INITIAL_CLUSTER=master=http://<IP_ADDRESS>:2380
ETCD_INITIAL_CLUSTER_STATE=new
ETCD_INITIAL_CLUSTER_TOKEN=k8s_etcd
ETCD_LISTEN_CLIENT_URLS=http://<IP_ADDRESS>:2379
ETCD_LISTEN_PEER_URLS=http://<IP_ADDRESS>:2380

I also have this unit in the cloud-config. From reading the two issues above, I still don't fully comprehend the relationship between coreos-cloudinit and systemd.
  units:
    - name: etcd2.service
      command: start

@bekt For the reboot case the process is not being given the right environment variables. What can etcd even do in that case? I don't think this is an etcd bug.

Do you think it's a lower level CoreOS issue? Either way, it is an unexpected behavior that should be noted somewhere or provide a work-around since it is very common.
There's also a possibility that etcd2 COULD get the right values from systemctl show etcd2 or systemctl cat etcd2. Imo it's a major etcd problem, whether root is from upstream or not.

Do you think it's a lower level CoreOS issue?

Yes. Please follow the advice on the coreos issues. It is related to the init configuration, not etcd itself.

There's also a possibility that etcd2 COULD get the right values from systemctl show etcd2 or systemctl cat etcd2. Imo it's a major etcd problem, whether root is from upstream or not.

Do any other daemons work like that?

We can of course blame it on other components, but at the end of the day the issue is happening with etcd2, not other daemons.
The issue was first reported 1.5 years ago, and still hasn't been addressed on that side. I'm sure the adults will make the right decision here; just wanted to note that this has not been the most pleasant user experience.

We can of course blame it on other components, but at the end of the day the issue is happening with etcd2, not other daemons.

Absolute nonsense. Any other daemon that relies on environment variables like etcd will be equally broken in this situation. Just because you've only observed it happening on etcd, that doesn't mean it's isolated to etcd or an etcd bug.
I'm feeling generous so I'll give you a free lesson on system design. etcd will do exactly what it is told. It will never second-guess the parameters provided by the init system. When system components try to make assumptions to work around misconfigurations, it becomes even more difficult to reason about the system because there is now an additional layer of "cleverness" papering over brokenness instead of being forthright with what it was given. By having etcd directly querying systemd to fetch environment variables, etcd would deftly violate in a single swoop both the principles of low coupling (it introduces a systemd assumption) and high cohesion (etcd isn't an init system).
There are deep usability issues. For example, suppose etcd boots direct from the command line or some shell script, but there is a unit file on the system. Should etcd pull the environment variables in that case? Or should it detect the direct execution case and not use the unit file? Suppose there are several unit files that may launch etcd, which should it choose? What is the idiomatic way to handle all of that? That's why I asked if other daemons work like that-- if it's a reasonable approach, it's likely other daemons have already done it.
Another way to do it: look at the initial boot variables, save them, then use those as the defaults. However, do other systems similar to etcd (key-value stores, databases, etc) work like that? I'm unaware of any that do. Even then, it seems like a lot of effort only to get around having a functioning init system in the first place.

The issue was first reported 1.5 years ago, and still hasn't been addressed on that side.

Solutions have already been offered for mitigating this problem; the system services are misconfigured and the upshot is etcd boots with the wrong arguments. Others have hit this problem and gladly fixed their broken configurations. The issue has been addressed at least twice. There could be more documentation around it (which seems to be in the works), but based on experience, I sense it will go unread.
The adult is closing this issue. Thanks for flying etcd.

👍
@heyitsanthony, I wasn't suggesting that was the correct approach or even remotely right.
The point was that these issues, specifically the relationship between cloudinit, coreos-cloudinit, and systemd, are not obvious and not documented. My suggestion was to spark CoreOS company internal discussions since the Github issues are just being discarded as "not our bug." Somebody has to take the responsibility.


EULA content seems to break iframes width

I'm not sure if this is even coming from the text we include there, maybe Valve messed something up on their own here.

Edit: Probably an Steam client issue itself.
Could be the additional padding in 'main'

Or an fixed with in 'eula_main'

We don't have that level of control over the EULA's presentation (it's just bbcode) so this is definitely on Valve's end.


Visualizer: would be great to accept 'SATISFIABLE' and 'UNSATISFIABLE' as meta-info in input

#4 the visualizer now prints unsatisfiable or satisfiable onto the console after receiving a solution via piping


best_street_address is not shown in the JSON result

Has anyone noticed ?
For example,
https://plus.codes/api?address=796RWF8Q+WF&key=YOURKEY
or
https://plus.codes/api?address=796RWF8Q%2BWF&key=YOURKEY
does not show street address anymore.
Document example: https://github.com/google/open-location-code/wiki/Plus-codes-API

Unfortunately the Plus Codes API doesn't return best_street_address as of a few months ago. It wasn't directly related to plus codes, and its functionality is available in other Google APIs.
For an alternative, see other geocoding APIs like Google Maps Platform (includes plus codes in results, large monthly free quota):
https://developers.google.com/maps/documentation/geocoding/start#reverse
Or Nominatim (free, see https://operations.osmfoundation.org/policies/nominatim/ for API usage etiquette or build your own server: https://nominatim.org/release-docs/latest/admin/Installation/):
https://nominatim.org/release-docs/develop/api/Reverse/


Hotfix: Decouple leadership calendar PDF template from base.html

While further troubleshooting PDF's, I discovered that PDFReactor was really choking on main.css. Removing it made the difference between painfully slow (takes multiple minutes, sometimes times out) to reasonably zippy.
What I've done here, is take the template and remove it from the "base.html" inheritance chain. I've added the necessary CSS directly to the template. This isn't front-end code that we'll be proud of, but with this change, this feature is now usable.
Testing

Review this PDF generated with this code:  cfpb-leadership (22).pdf

If you have a working PDF reactor, give it a try

(note that this PDF exposes a logic flaw in the application itself-- that event from March 14th should not appear there. This is not PDF-specific though)
Review

@cfpb/cfgov-backends

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

I think this is fine if it speeds it up; but I am curious why it was choking on main.css? Are there things we can do there to improve its performance?

Might also be worth tagging the @cfpb/cfgov-frontends here in case they have more insight into main.css performance issues.

I'm not sure how to investigate further-- This PDFReactor version might just predate the trend of stuffing a lot of CSS into a big minified file, or maybe we're using CSS3 features that were cutting edge circa 2013. The logs are pretty useless.

Hmm. Could this be related to some of the performance issues that @virginiacc and @contolini have been working on?

As a hotfix for PDFReactor I'm ok with this though, pending front-end thoughts.
I have not, ahem, tested it locally, however.

👍 , this is good.  We should have never been using main.css.

When I run this using my local version of PDFReactor, the generated PDF uses different fonts, and I see messages like this in the output log:

[150][09:20:40.516][WARNING] - Could not create font e (font-family: "AvenirNextLTW01-Regular"; src: _b (url: http://localhost/static/fonts/pdfreactor/46cf1067-688d-4aab-b0f7-bd942af6efd8.ttf, remote: true); bold: false; italic: false)
[150][09:20:40.517][WARNING] - Could not create font e (font-family: "AvenirNextLTW01-Demi"; src: _b (url: http://localhost/static/fonts/pdfreactor/a0f4c2f9-8a42-4786-ad00-fce42b57b148.ttf, remote: true); bold: true; italic: false)

I'm using version 6.3.6828.3 locally. I do have these fonts installed, so perhaps this is a Mac thing:

That's interesting-- but I don't think it should block us

I'm interpreting @willbarton  "pending front-end thoughts" and @sebworks 👍  as equalling 👍 👍  ;)

@chosak if PDFReactor depends on web fonts from origin http://www.consumerfinance.gov, they won't be available locally because of CORS


SAML Bearer Assertion flow

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

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/Microsoft/azure-docs/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Microsoft/azure-docs-pr/blob/master/articles/azure-portal-overview.md
We have closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions

@rwike77  -  created a pull request with the article. I am kind of new to articles in GitHub so did my best. Let me knowif its visible else I have also uploaded the same in my repo.
https://github.com/umeshbarapatre/docs/wiki/Azure-AD-Office-365-SAML-Bearer-Assertion-flow/_edit

@unmeshbarapatre thanks for writing this up. Looks like you're internal. I'm traveling this week and into next. I'll follow up end of next week.

Thanks Ryan ! Feel free to let me know if you need any other information.
From: Ryan Wike<EMAIL_ADDRESS>Sent: 22 June 2019 00:57
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: umeshbarapatre<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
@unmeshbarapatre thanks for writing this up. Looks like you're internal. I'm traveling this week and into next. I'll follow up end of next week.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWOL4LPISXPS4M5RI4LP3UTRLA5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYJMBAA#issuecomment-504545408, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWJLHEDB6S7K2BPGC4DP3UTRLANCNFSM4HYPSMAQ.

Hi
Did you get a chance to look at the article
Get Outlook for iOShttps://aka.ms/o0ukef

From: Umesh Barapatre
Sent: Tuesday, June 25, 2019 8:47:50 AM
To: MicrosoftDocs/azure-docs; MicrosoftDocs/azure-docs
Cc: Author
Subject: RE: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
Thanks Ryan ! Feel free to let me know if you need any other information.
From: Ryan Wike<EMAIL_ADDRESS>Sent: 22 June 2019 00:57
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: umeshbarapatre<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
@unmeshbarapatre thanks for writing this up. Looks like you're internal. I'm traveling this week and into next. I'll follow up end of next week.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWOL4LPISXPS4M5RI4LP3UTRLA5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYJMBAA#issuecomment-504545408, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWJLHEDB6S7K2BPGC4DP3UTRLANCNFSM4HYPSMAQ.

@unmeshbarapatre, I read through your article.  Thanks for writing it up, the graphics are a good addition.  I'm trying to get one of our engineers to look it over as well, since I'm very strong in this area.  He's also been out on vacation, I'll try to get this done this week.  Thanks for your patience.

Thanks Ryan
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ryan Wike<EMAIL_ADDRESS>Sent: Wednesday, July 3, 2019 3:27:03 AM
To: MicrosoftDocs/azure-docs
Cc: umeshbarapatre; Author
Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
@unmeshbarapatre, I read through your article. Thanks for writing it up, the graphics are a good addition. I'm trying to get one of our engineers to look it over as well, since I'm very strong in this area. He's also been out on vacation, I'll try to get this done this week. Thanks for your patience.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWODAJ7BIEEML4VDPFTP5PFK7A5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZCVHBA#issuecomment-507859844, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWN5YLW76Y72R4DLOETP5PFK7ANCNFSM4HYPSMAQ.

Hey Ryan,
I hope my article have some good info. Please lemme know the feedback
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ryan Wike<EMAIL_ADDRESS>Sent: Wednesday, July 3, 2019 3:27:03 AM
To: MicrosoftDocs/azure-docs
Cc: umeshbarapatre; Author
Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
@unmeshbarapatre, I read through your article. Thanks for writing it up, the graphics are a good addition. I'm trying to get one of our engineers to look it over as well, since I'm very strong in this area. He's also been out on vacation, I'll try to get this done this week. Thanks for your patience.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWODAJ7BIEEML4VDPFTP5PFK7A5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZCVHBA#issuecomment-507859844, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWN5YLW76Y72R4DLOETP5PFK7ANCNFSM4HYPSMAQ.

Hi Ryan
Did you guys get a chance to review this one ?
Get Outlook for iOShttps://aka.ms/o0ukef

From: Umesh Barapatre
Sent: Wednesday, July 10, 2019 11:55:09 PM
To: MicrosoftDocs/azure-docs; MicrosoftDocs/azure-docs
Cc: Author
Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
Hey Ryan,
I hope my article have some good info. Please lemme know the feedback
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ryan Wike<EMAIL_ADDRESS>Sent: Wednesday, July 3, 2019 3:27:03 AM
To: MicrosoftDocs/azure-docs
Cc: umeshbarapatre; Author
Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
@unmeshbarapatre, I read through your article. Thanks for writing it up, the graphics are a good addition. I'm trying to get one of our engineers to look it over as well, since I'm very strong in this area. He's also been out on vacation, I'll try to get this done this week. Thanks for your patience.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWODAJ7BIEEML4VDPFTP5PFK7A5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZCVHBA#issuecomment-507859844, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWN5YLW76Y72R4DLOETP5PFK7ANCNFSM4HYPSMAQ.

Hi, I found one of our engineers to review tomorrow hopefully.  Will let you know.  Thanks for your patience.

Thanks Ryan
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ryan Wike<EMAIL_ADDRESS>Sent: Thursday, July 18, 2019 5:06:35 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: umeshbarapatre<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
Hi, I found one of our engineers to review tomorrow hopefully. Will let you know. Thanks for your patience.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWPPLFSDGZDWWW57TYLP76UIHA5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2G4JCA#issuecomment-512607368, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWNQDE2QIPSRMO4PMDLP76UIHANCNFSM4HYPSMAQ.

Hi Ryan
Did your team got a chance to review ??
Get Outlook for iOShttps://aka.ms/o0ukef

From: Umesh Barapatre
Sent: Thursday, July 18, 2019 12:27:42 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
Thanks Ryan
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ryan Wike<EMAIL_ADDRESS>Sent: Thursday, July 18, 2019 5:06:35 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: umeshbarapatre<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
Hi, I found one of our engineers to review tomorrow hopefully. Will let you know. Thanks for your patience.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWPPLFSDGZDWWW57TYLP76UIHA5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2G4JCA#issuecomment-512607368, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWNQDE2QIPSRMO4PMDLP76UIHANCNFSM4HYPSMAQ.

@umeshbarapatre  Hi, we're moving ahead with this now.  It's been hard finding help with reviews, a lot of people are out right now.  I'll need to make some updates for spelling and to make sure it fits our style guidelines.  I'll start that work soon.  Are you a MSFT employee?  The PR bot closed this PR earlier because it says you're internal partner, but I haven't been able to look you up inside the company.  Thanks.

Hi Ryan,
Thanks for the update !
I am not a Microsoft employee. I tried forking the branch in github but every time I was submitting the PR is getting closed. I look forward for this article and please let me know in case you have any questions meanwhile.
Thanks
Umesh
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ryan Wike<EMAIL_ADDRESS>Sent: Thursday, July 25, 2019 5:01 AM
To: MicrosoftDocs/azure-docs
Cc: umeshbarapatre; Mention
Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
@umeshbarapatrehttps://github.com/umeshbarapatre Hi, we're moving ahead with this now. It's been hard finding help with reviews, a lot of people are out right now. I'll need to make some updates for spelling and to make sure it fits our style guidelines. I'll start that work soon. Are you a MSFT employee? The PR bot closed this PR earlier because it says you're internal partner, but I haven't been able to look you up inside the company. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWJB7LBTSGSU5ZBGU33QBDQ3ZA5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2X4QTA#issuecomment-514836556, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWMNFBDBR4J4ZWIREF3QBDQ3ZANCNFSM4HYPSMAQ.

Hi Ryan,
Please let me know if any other information is needed from my end.
Thanks
Umesh
Get Outlook for iOShttps://aka.ms/o0ukef

From: Umesh Barapatre
Sent: Thursday, July 25, 2019 9:31:29 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
Hi Ryan,
Thanks for the update !
I am not a Microsoft employee. I tried forking the branch in github but every time I was submitting the PR is getting closed. I look forward for this article and please let me know in case you have any questions meanwhile.
Thanks
Umesh
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ryan Wike<EMAIL_ADDRESS>Sent: Thursday, July 25, 2019 5:01 AM
To: MicrosoftDocs/azure-docs
Cc: umeshbarapatre; Mention
Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
@umeshbarapatrehttps://github.com/umeshbarapatre Hi, we're moving ahead with this now. It's been hard finding help with reviews, a lot of people are out right now. I'll need to make some updates for spelling and to make sure it fits our style guidelines. I'll start that work soon. Are you a MSFT employee? The PR bot closed this PR earlier because it says you're internal partner, but I haven't been able to look you up inside the company. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWJB7LBTSGSU5ZBGU33QBDQ3ZA5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2X4QTA#issuecomment-514836556, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWMNFBDBR4J4ZWIREF3QBDQ3ZANCNFSM4HYPSMAQ.

Hi @unmeshbarapatre, I sent you an invite for a repo where I put a draft of my updates:
https://github.com/rwike77/review/wiki
Would you take a look?  I added some more overview info.  I also updated some of the steps to use the new app registration portal.
One question: the app ID you get when you register the application, is that the client request ID that's used later on?  Thanks.

Thanks for putting this together Ryan ! This is much more structured now. The app Id which is registered is used when graph api calls are made and put as client-id parameter in the same call. However, the client-request-id can be any GUID while making a ADFS endpoint api call. The client-request-id is not related to the App-id and can be any unique guid.
Please let me know if you have any other questions.
Again ,thank you very much to put it together !

From: Ryan Wike<EMAIL_ADDRESS>Sent: Tuesday, August 6, 2019 5:05 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: umeshbarapatre<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
Hi @unmeshbarapatre, I sent you an invite for a repo where I put a draft of my updates:
https://github.com/rwike77/review/wiki
Would you take a look? I added some more overview info. I also updated some of the steps to use the new app registration portal.
One question: the app ID you get when you register the application, is that the client request ID that's used later on? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWIDDY74UGK2J4OAGRDQDC2L5A5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3TMCVY#issuecomment-518439255, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWIPIR5YIU7JTOPGJJ3QDC2L5ANCNFSM4HYPSMAQ.

Hi Ryan,
Hope you have all the information. Please let me know if you need any other details on request parameters.
Thanks
Umesh
Get Outlook for iOShttps://aka.ms/o0ukef

From: Umesh Barapatre<EMAIL_ADDRESS>Sent: Wednesday, August 7, 2019 8:22:22 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
Thanks for putting this together Ryan ! This is much more structured now. The app Id which is registered is used when graph api calls are made and put as client-id parameter in the same call. However, the client-request-id can be any GUID while making a ADFS endpoint api call. The client-request-id is not related to the App-id and can be any unique guid.
Please let me know if you have any other questions.
Again ,thank you very much to put it together !

From: Ryan Wike<EMAIL_ADDRESS>Sent: Tuesday, August 6, 2019 5:05 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: umeshbarapatre<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] SAML Bearer Assertion flow (#33396)
Hi @unmeshbarapatre, I sent you an invite for a repo where I put a draft of my updates:
https://github.com/rwike77/review/wiki
Would you take a look? I added some more overview info. I also updated some of the steps to use the new app registration portal.
One question: the app ID you get when you register the application, is that the client request ID that's used later on? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/33396?email_source=notifications&email_token=AKCNYWIDDY74UGK2J4OAGRDQDC2L5A5CNFSM4HYPSMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3TMCVY#issuecomment-518439255, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCNYWIPIR5YIU7JTOPGJJ3QDC2L5ANCNFSM4HYPSMAQ.

Hi,
Sorry for the slow reply, I was out sick for a few days.  Your article was published :)
https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-saml-bearer-assertion
There was some minor feedback from one of our engineers, but other than that it's looking good.  Thanks again for your contribution.
-Ryan

Thank you very much Ryan ! i hope you are doing well now. It's good to see this published. Again Thanks a ton !


feat: 🎸 form builder + components shared library

✅ Closes: #72
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: CONTRIBUTING.md
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
adds a library for shared components and a component for dynamic form
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
none
Issue Number: N/A
none
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
Example of Component Generator (not included in this pr)

We talked about not having a form-builder, what changed?

I agree with @Danieliverant about this, unless we make our own providers that wrap formly's providers and add extra functionality I don't see any reason to have this component


Can't make list of numbers

Describe the bug
Can't create list of numeric items. Discovered when trying to list versions of software
To Reproduce
>>> from mdutils.mdutils import MdUtils
>>> mdf = MdUtils('foo.md', title='Foo')
>>> mdf.new_list(['foo', 'bar'])
>>> mdf.new_list(['1.2', '1.3'])
>>> mdf.create_md_file()

results:
Foo
===

- foo
- bar

1.2
1.3

Expected behavior
Foo
===

- foo
- bar

- 1.2
- 1.3

Desktop (please complete the following information):

macOS 12.6.5 (21G531)
Python 3.11.1
mdutils-1.6.0

Thanks for reporting it, I'll take a look.


chore: narrow typescript range in consumer test

This PR reduces the range for typescript from ^4.4.4 to ~4.7.2 as it appears that versions >= 4.8.2 cause an issue with @types/styled-components. The goal of this PR is to get the consumer-test back to green and then PR the fix in afterwards to support TS versions >= 4.8.2
In order to support TS >= 4.8.2, I believe we'll need to update @types/styled-components to >= 5.1.26 along with some other types in the project

yaaay 🚀


When using a private instance .get_status still goes to webpagetest.org

This code:
config = {
      k: "API_KEY",
      options: {
        url: "http://private.wpt.instance/,
        request: :url_encoded,
        response: :logger,
        adapter: Faraday.default_adapter
      }
    }

wpt = Webpagetest.new(wptConfig)
test = wpt.test_result("TEST_ID")

test.get_status

Will return null because it is still going to the public WPT instance, which won't have the test information.

@iamcarrico At first this gem was built only for the public instance, so some things are still not ready for private instances. Of course I think that both public and private instances have to be covered by the gem, so I'd happily accept PRs that go in that direction. I'd do it myself but I don't have much time left for this. I'll try though.

I am working on some code for this one— but I wanted to share it first since I am trying to figure out how to best debug this one.

But I'll have a PR ready when I can as well.


Look in the correct location for HWE kernel

boot/grub/grub.cfg is located in a different folder.

great fix, thanks!


Change application entry point

Description
Change application entry point in package.json.

For reference, this PR is a follow-up of #9, as pointed out by this discussion.


Clear console before reload

Currently the UXP debug console history is kept after hot reloading, but I find myself clearing it manually after each reload to get a clean slate. Any logged objects lose their reference, so I don't think there's any reason to keep the history.

In propper DevTools this would be a tool responsibility and this checkbox would work.

Can confirm that works. In that case it would be nice if Bolt clears the console and users can toggle 'Preserve log' to keep it.

I would rather see change done by UXP team.

I have a console.clear() early in my code (after loading shims), and it works great. If you need to see something, you can enable that option in the debugger to preserve logs (ignore clear commands). Or just cmd-K or L to clear.


Move graph Generation Logic to a separate helper func

Refactor and move the graph generation logic
out of getDepInfo method to a separate helper func
Add test case for the helper based on a dummy
go mod output

Fixes #49

Also there are some formatting issues in the PR. You can see them by running gofmt -d . 🙂
Can you also please pull the latest code from main and merge it with your PR so that we can run gofmt on this PR in the CI (which was added in #52)? Please let me know if you need help doing this :)

/label tide/merge-method-squash

/lgtm
/approve
Thanks a lot for this @bishtsaurabh5, it was much needed!! :)


🐛 Camera orientation problem

What were you trying to do?
If all orientations are available for the device, the camera rotates with the device.
Reproduceable Code
import React, { memo, useEffect } from 'react';
import { StyleSheet } from 'react-native';
import Orientation from 'react-native-orientation-locker';
import { Camera as CameraVision, useCameraDevices } from 'react-native-vision-camera';

const Camera = () => {
  const devices = useCameraDevices();
  const device = devices?.back;

  useEffect(() => {
    Orientation.unlockAllOrientations();
    return () => {
      Orientation.lockToPortrait();
    };
  }, []);

  return <CameraVision style={StyleSheet.absoluteFill} device={device} isActive photo enableZoomGesture />;
};

export default memo(Camera);

What happened instead?
If all orientations are available for the device, the camera rotates with the device. The problem is reproduced only on version >= 2.15.3
https://user-images.githubusercontent.com/46136101/215867915-209860b5-a166-4d44-9ee4-635a5d43c464.MP4
Relevant log output
No response
Device
iPhone SE2
VisionCamera Version
2.15.3
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

<CameraVision
  style={StyleSheet.absoluteFill}
  device={device}
  isActive photo
  orientation="portrait" <---- this fixed it for me
  enableZoomGesture />;

I have the same issue and still could not fix it, even with the suggested solution above

Same issue.

@galkinsden  I have the same issue for IOS when I change camera rotation. For Android, the rotation is working fine.
@mrousavy  can you look into this issue? I know you worked on this library in your free time.

@mrousavy can you look into this issue? I know you worked on this library in your free time.

Sorry no I have other things to do right now. If you want this fixed, reach out to us for consulting services<EMAIL_ADDRESS>

Same issue

I am not sure I understand the orientation prop expected outcome.  If I read the docs, it appears that it impacts the captured "output".
By having the following snippet:
<Camera
  photo
  orientation={'portrait'}
  device={device}
  isActive={isActive}
  format={formats?.[0]}
 />

I understand the docs to say:  "If I have my device in landscape, the result will be a landscape picture rotated 90 degrees so that it's visible in portrait orientation.  Therefore I don't have to turn my head or device to see the photo since I am holding the phone in portrait mode after the picture is taken"
However, the result is not this:
On the web previewing my image is not portrait

and neither is it on my app when previewing image:

Closing as this is a stale issue - this might have been fixed with the full rewrite in VisionCamera V3 (🥳) - if not, please create a new issue.
If your issue has been fixed, consider sponsoring me on GitHub to say thanks 💖

Hey - I'm tracking Orientation in this feature request/issue now: https://github.com/mrousavy/react-native-vision-camera/issues/1891 ✨
Make sure to upvote or sponsor to support this feature, and leave a comment if you have any additional thoughts/ideas.

I Just made a module to handle the device orientation
https://www.npmjs.com/package/rn-device-orientation
the usage is pretty simple, and this module get de device orientation, not the interface orientation, so even if the interface is locked on portrait, it will work
to solve on vision camera a jus use like this


feat(calling): Add notification if User tries to call with no mic or speakers hooked up

Issue:
In order to make a call on blink you need to have a microphone and speakers hooked up to the computer. If you dont have this you cannot make a call. We should add a toast notification that says something like "you need a mic and headphones in order to call your friends!" that should appear whenever a user without a mic tries to accept or place a call.
OS:
All
Error that appears in log when trying to call without:
BlinkCmd::OfferCall failed: failed to build input stream: The requested stream configuration is not supported by the device., C:\Users\pprin\.cargo\git\checkouts\warp-2f0b6768b713aeb1\80a0ace\extensions\warp-blink-wrtc\src\host_media\audio\opus\source\mod.rs, 189: failed to create source track

@phillsatellite  I believe that this isn't related to a missing audio device but instead due to Blink using an audio configuration which is incompatible with your laptop. There's a tool in the Warp repository called blink-webrtc-cli. Could you run the following commands in the terminal and provide the output?
cargo build
target/debug/blink-webrtc-cli
supported-input-configs
supported-output-configs
show-input-config
show-output-config

@phillsatellite I believe that this isn't related to a missing audio device but instead due to Blink using an audio configuration which is incompatible with your laptop. There's a tool in the Warp repository called blink-webrtc-cli. Could you run the following commands in the terminal and provide the output? cargo build target/debug/blink-webrtc-cli /tmp/warp1 supported-input-configs supported-output-configs show-input-config show-output-config show-available-devices show-selected-devices

Will do. Was having some issues building warp due to not having openCV on that computer and getting errors when trying to install it. I can take a look at that this evening and run the commands when I get it working

the latest version of main doesn't require opencv. it was excluded from the workspace

@phillsatellite  following up on this

note that if there's a stack overflow on windows, run in release mode.

asking on discord


Add launchSettings.json to .gitignore

Hi @mikeharder, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

:shipit:


Add sub groups in status page

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
Other
🔖 Feature description
Actually in uptime-kuma it's possible to add groups in the status page. It will be nice if it can also be added sub groups for a better overview (eg. one sub group for dev machines, another sub group for testing machines etc...).
✔ Solution
Have another button in the status page that allows to add one or more sub groups (child of the main group).
❓ Alternatives
No response
📝 Additional Context
No response

Would love to see this added


Not working?

After I try to use waifu2x on art, the server tries to connect, but never actually ends and gives me the error that the site isn't available. Is it only on my side?

restarted, see #197


Remove react-dnd and move to native drag and drop instead

For just tags component along, we don't need really need react-dnd so it would be great if we can move to native drag and drop and this will also make the library very light weight as well.

Hey, I am ready to take this up. How do you plan to move this?

Hey @geekayush glad to know you are interested, I have started on this and will be pushing out the changes soon. How about we collaborate once I create the PR? Additionally here are few issues you might be interested in

Sure

Hey @geekayush I got busy with other tasks and haven't wrapped it up so if you are still interested in picking it up, let me know :)

Hey @ad1992 I would like to pick up this


Fix README version field for projects with dashes in tag

Some projects have a dash in their Git tag, and we can't use these directly in the badge URL template. Using two dashes renders the badge properly.
https://img.shields.io/badge/version-v0.4.5-rc3-blue:
https://img.shields.io/badge/version-v0.4.5--rc3-blue:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/retest

/cherrypick release-0.10


How do I delete a team??

I started a team I would like to delete. No one is in it but me.
I am a journalist, not an IT person so........I will not understand technical answer!

keybase team delete in terminal? Be aware that this team will be never available again.

I don't understand how to delete. Thank you for any help!

Terminal? The keybase.io pg? I have no idea & there is nothing to click on. What is the terminal?
Thank you!

My husband works in IT. I will see if he knows what this means. I really appreciate you answering me. Sorry, I know nothing with this stuff. We are a political activist group & love that Keybase is encrypted.

If you are using Mac OSX:
Type “Terminal” in the search bar and open the terminal app.
If you are using Windows 10 or 7:
Tap the window key (lower left of the keyboard near Ctrl) to open the start menu, then type “cmd” in search, and open the command prompt app (cmd)
Then once you have terminal or cmd open type “keybase team delete yourteamnamehere” and switch yourteamnamehere with your team name.
Hit enter
It will tell you to type a sentence.
Type the sentence exactly as it is written, and hit Enter.
Now your team will be deleted forever, and that team name is lost forever (you can never make a team with that name again)

I really appreciate you taking the time to try to help! I had someone who has some IT knowledge assist & I typed in exactly as instructed & I got -bash: Keybase:  command not found

Keybase and keybase are different commands
All lower cased
keybase

that was a typo in my email
I did both ways & got same answer
On Sat, Apr 28, 2018 at 3:04 AM, Dabura667<EMAIL_ADDRESS>wrote:

Keybase and keybase are different commands
All lower cased
keybase
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/11502#issuecomment-385147315,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkBESBoD2OI8AiWm1hJArKp8o2gbrN69ks5ttBR-gaJpZM4Texo1
.

Then you don’t have keybase installed.
If you’re on Windows and trying to use bash for windows, that won’t work. Bash for windows is a separate virtual computer within your Windows PC. You will need to open the cmd prompt and not bash.
Or are you on a Mac?

Mac
I do have Keybase installed, been using it for couple months now.
Thank you!
So confused!
On Sat, Apr 28, 2018 at 3:48 AM, Dabura667<EMAIL_ADDRESS>wrote:

Then you don’t have keybase installed.
If you’re on Windows and trying to use bash for windows, that won’t work.
Bash for windows is a separate virtual computer within your Windows PC. You
will need to open the cmd prompt and not bash.
Or are you on a Mac?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/11502#issuecomment-385150161,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkBESInknHYuxNzZNN9Sf-S7iRwOc11Zks5ttB7DgaJpZM4Texo1
.

Assuming you don't have anything important in the chats or filesystems of your team, you can add me, make me an owner of the team, and then I can delete it for you.
Adding someone and changing their role to Owner can be done through clicking buttons and menus.
Or you can just leave the team and ignore it. Deleting the team will nuke it anyways, maybe years from now you will want to use the same team name again... if you delete the team it will never be used again.

When I say "leave the team" I mean "leave it be"

This honestly indicates that the UI should provide a more clear-cut way to do this and this issue could be used to track adding that button somewhere (with proper confirmation dialogue unlike other options).

@Avamander I agree, with the GUI you can only leave teams, not delete them.

I think the confirmation screen should be simple question plus typing out “nuke myteamname and never let anyone including myself use the name again” (disable copy paste)
The simple question could be “what is the answer to the universe?”
“42”

$ keybase team list-memberships
keybase team delete
Error parsing command line arguments: team name argument required

NAME:
   keybase team delete - Delete a team.

(2) prevent "testings" from being used again as a team name.

** if you are sure, please type: "nuke testings" > nuke testings
Success! Team testings deleted.


lxd-images gives: error: [Errno 13] Permission denied

Required information

Distribution: Ubuntu
Distribution version: xenial (daily build)
The output of "lxc info" or if that fails:  error: Get http://unix.socket/1.0: dial unix /var/lib/lxd/unix.socket: connect: permission denied

Kernel version:  4.4.0-6-generic
LXC version:  2.0.0.beta3
LXD version:  2.0.0.beta3
Storage backend in use: dir

Issue description
Trying to follow the instructions on linuxcontainers.org and I get this error importing the images using lxd-images. https://linuxcontainers.org/lxd/getting-started-cli/#using-lxd-images-to-import-an-image
Steps to reproduce
$ lxd-images import ubuntu --alias ubuntu
Downloading the GPG key for http://cloud-images.ubuntu.com
Validating the GPG signature of /tmp/tmp06in1t45/download.json.asc

error: [Errno 13] Permission denied
usage: lxd-images [-h] [--quiet] {import,sync} ...

LXD: image store helper

positional arguments:
  {import,sync}
    import       Import images
    sync         Sync images

optional arguments:
  -h, --help     show this help message and exit
  --quiet        Silence all non-error output

Examples:
 To import the latest Ubuntu Cloud image with an alias:
    /usr/bin/lxd-images import ubuntu --alias ubuntu

 To import a basic busybox image:
    /usr/bin/lxd-images import busybox --alias busybox

 Some images can be kept in sync for you, use --sync for that:
    /usr/bin/lxd-images import ubuntu --alias ubuntu --sync

 Then make sure the following command is executed regularly (e.g. crontab):
    /usr/bin/lxd-images sync

Information to attach
The lxd daemon is running:
$ sudo service lxd status
● lxd.service - Container hypervisor based on LXC
   Loaded: loaded (/lib/systemd/system/lxd.service; indirect; vendor preset: enabled)
   Active: active (running) since Tue 2016-02-23 08:28:28 CST; 1h 6min ago
 Main PID: 4179 (lxd)
   CGroup: /system.slice/lxd.service
           ‣ 4179 /usr/bin/lxd --group lxd --logfile=/var/log/lxd/lxd.log

Feb 23 08:28:22 warhorse systemd[1]: Starting Container hypervisor based on LXC...
Feb 23 08:28:22 warhorse lxd[4179]: t=2016-02-23T08:28:22-0600 lvl=warn msg="CGroup memory swap accounting is disabl
Feb 23 08:28:28 warhorse systemd[1]: Started Container hypervisor based on LXC.

And my user is added to the lxd group.
$ groups
mbruzek adm cdrom sudo dip plugdev lpadmin sambashare docker libvirtd lxd

I am unable to use many lxc commands as well. But lxc image list images: works fine.
Please advise how to fix this or if you need more information.

That's gonna be the same problem as #1635, closing this one.


I need a composer!

Describe your problem here.
(Use soft girl voice for Opponent)
Song 1: Slow, Calm and nothing really happens
Song 2: Super slow, but gets suddenly fast near the end.
Song 3: A mix of Slow, Fast, And super fast
Song 4: Fast and Super fast song
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
what

????

bruh


Finder toolbar

I was wondering if the Finder toolbar is equally malleable? See this question on SO: http://apple.stackexchange.com/questions/197990/add-item-to-finder-toolbar-with-terminal

Thanks for the feedback.  I don't plan to add this capability to dockutil.  It would probably be a different tool.


404 at /engine/reference/commandline/compose_cp/

I found a broken link : https://docs.docker.com/engine/reference/commandline/compose_cp/
I arrived on this page through: https://docs.docker.com/engine/reference/commandline/compose_top/

Thanks for reporting; I opened https://github.com/docker/docker.github.io/pull/13256, which should fix this