Bump dockerclient to match version in origin

I'm gonna need code that is in the version in origin and not in the old version we had here (AttachToContainerNonBlocking)
Sending as separate PR to not pollute the diff of #430 with all these changes.
@bparees ptal

lgtm [merge]

@bparees I've updated the commit making sure the patch is the same as what's here:
https://github.com/fsouza/go-dockerclient/compare/25bc220b299845ae5489fd19bf89c5278864b050...0099401a7342ad77e71ca9f9a57c5e72fb80f6b2.
Actually not a must-have for my other PR... I thought we were dealing with a relatively older version (coming from the bad assumption of what I've seen last time).

312 files down to 6.... do i want to know what happened the first time around? :)
[merge]

do i want to know what happened the first time around? :)

I want to know too :)
No way to trust godep...


Added new status READY_TO_DELIVER to OPEN DELIVERY

I just received the grocery goods, when the truck drive was drive to our home i see that status was changed to READY_TO_DELIVER. I do not know if that was the 15 minutes time frame. Otherwise I can make an automation to give a signal that the truck driver is on his way.

That's interesting! Would be very helpful if we could send a notification up front. Hate the fact it only sends a SMS to a single person.
I am thinking of separating the "open" and "being delivered" orders.

I'm not sure if we can use that, i will monitor that on my next order. Until then i would suggest first added it to open delivery.

Yeah I will do that also. Have to wait till next week though.
Will merge this one soon.


Matmul output mismatch

First qkv MM in stable diffusion produces an incorrect PCC when block sharded.
To repro, you can run pytest -svv tests/ttnn/integration_tests/stable_diffusion/test_sharded_attention.py::test_qkv on aknezevic/mm_pcc_repro

It looks like the mismatch is not due to the matmul but due to sharded output.
To repro, you can run:
pytest -svv tests/ttnn/integration_tests/stable_diffusion/test_sharded_attention.py::test_qkv on aknezevic/all_qkv_tests.
This has 8 tests, 4 that create sharded output in L1 which fail with bad pcc and 4 that place matmul output in interleaved DRAM which pass.
@tarafdarTT, can you please take a look?

Some discussion with @jvasilje on this and this is a critical enough to highlight the attention
@tarafdarTT / @TT-BrianLiu , please prioritize accordingly

It looks like the mismatch is not due to the matmul but due to sharded output.
To repro, you can run: pytest -svv tests/ttnn/integration_tests/stable_diffusion/test_sharded_attention.py::test_qkv on aknezevic/all_qkv_tests. This has 8 tests, 4 that create sharded output in L1 which fail with bad pcc and 4 that place matmul output in interleaved DRAM which pass.
@tarafdarTT, can you please take a look?

Hi @AleksKnezevic wanted to clarify one thing. When you said interleaved output is okay, does that mean that the matmul directly output interleaved data or did you take the data out of the matmul and put it through the sharded_to_interleaved op.
If you did the latter, then I think the bug is the same as: https://github.com/tenstorrent-metal/tt-metal/issues/6355
Just wanted to verify that since I'm currently working on the above bug.

When the matmul directly output interleaved, the data is correct. If the matmul directly outputs sharded, the data is incorrect.
If the matmul outputs interleaved and I then convert to sharded output is correct.
If the matmul outputs sharded and then I convert to interleaved, data is incorrect.

I see, looks like how the MM implemented sharding support is incorrect, @TT-BrianLiu can you look into this then?

I am running these tests on a grayskull and the sharded versions hang for me instead of bad PCC. After the hang, the interleaved version hangs too (so device was probably in a bad state and resetting doesn't help)

Did you manage to repro on wormhole?

I can try on wormhole and debug there, but I wasn't expecting it to hang on Grayskull.

Ok I think interleaved is fine for both Grayskull and Wormhole. For sharded output, Grayskull hangs and Wormhole has bad PCC.

I think I know what the issue is. It's related to uneven output shards in the last core. I need to double check how sharded infra is handling this, but for example for N=2304 on 5 cores, per_core_N should be set tp 15 (2304 / 32 / 5 rounded up). This means each core's shard width will be 15 tiles, with last core "padded" up. For interleaved, this is not an issue since we write to a separate tensor allocator.
@AleksKnezevic Side note, what is this piece of code trying to do here? For the example above, this gives me per_core_N=17. It should work but 15 is better.

What should the calculation be?

What should the calculation be?

It should be some from of divup. We have these implemented in various helper functions, but this is how we typically do it:

workaround will fix the mismatch but is slow. Also need to understand the root cause (or understand it & assert on it). P1

I simplified the test to have smaller shapes and confirmed that the output sharded buffers on each core looks correct after the matmul. I think something may be messed up for how the output sharded tensor is being interpreted.

The source of the bug is with BLOCK_SHARDED tensors with padding. You can reproduce by just creating BLOCK_SHARDED tensors and reading them back. @tarafdarTT is taking a look at fixing this.

@TT-BrianLiu could you try cherry-picking my commit (aa8f406e29a3c02b5b0b54f2f2c0550b6f438a63) and running the matmul test. Sorry I tried but I think the test is only for wormhole .

I tested it myself, turns out I was using a smaller shape on the height and when I use the same height I see hangs.
I will debug this rn and get it working. @TT-BrianLiu is ooo but he has given me blessings to use his wormhole machine.
CC @AleksKnezevic @jliangTT

@AleksKnezevic @jliangTT @davorchap @jvasilje @TT-BrianLiu
The PCC issue is actually caused by two things. Uneven shards for direct sharded reads and writes, and uneven shards from sharded_to_interleaved. I have a fix for the former that increases PCC greatly but is still not perfect (around 0.9 ) for 2/3 cases (the other case is perfect). I can push that fix in today, and the other fix I can get to Thursday. (I am off Wednesday for Eid).
I was also able to make a unit test where I see pcc failures for a single tile for interleaved_to_sharded.

This is the PR that improves PCC and covers the direct read write case https://github.com/tenstorrent-metal/tt-metal/pull/7196

Update, after addressing one bug in interleaved_to_sharded we did see PCC improve and are close, 0.94 and 0.97 on the two failing sizes and the rest is working. We are investigating what else could be the problem at the moment.
@jliangTT @AleksKnezevic @TT-BrianLiu

Seems like a matmul issue with sharded output. Compute always produces the number of subblocks needed and writer would handle the output tiles. For interleaved, we respect padding for block and subblocks. For sharded, we just do a dummy wait. However, we need to do similar logic in the writer so that output sharded cb is properly padded, otherwise we will have contiguous useful data in spaces that will be treated as garbage.
On the left is what we have now which is incorrect. On the right is what it's supposed to be. We have to "insert" dummy padded tiles, so our shard write interprets padded shards correctly.

Looked into it a bit more and what's happening is exactly backwards ^_^. Sharded read always reads pages back in row major order without respecting padding, while output CB from matmul has the padded tiles. We need to augment sharded struct to keep track of padded cores for both write/read so it matches what our op produces.

Addressed in PR: https://github.com/tenstorrent/tt-metal/pull/7658


[Template picker] Add more filtering capabilities

Fix https://github.com/adobe/express-website-issues/issues/192 and https://github.com/adobe/express-website-issues/issues/328
Added filtering capabilities (sort, type, animated and locale) but display now the size / aspect ration, creation date and remix count on the template cards.
Still need to find a solution for the filtering by aspect ratio. And certainly some visual love.
Preview: https://extend-picker--express-website--adobe.hlx3.page/tools/templates/picker.html

Authors seem to be happy with current state, let's merge it.


SyncBot: Should no longer close tickets

Front native rules have caught up with our use case, and native is better than coded.

https://www.flowdock.com/app/rulemotion/user_happiness/threads/b4_3Ow7e6xnsPwQguNm09AhdSzl


Use Enum name "None" instead of empty string to prevent crash

Fixes: https://github.com/PrecisionGazeMouse/PrecisionGazeMouse/issues/46

Thanks for fixing this!


update README with usage instruction

 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.


The JS/TS language service crashed 5 times in the last 5 Minutes.

Type: Bug
When I open VS Code I get the following error:
The JS/TS language service crashed 5 times in the last 5 Minutes.
Has happened 3-4 times till now.
VS Code version: Code 1.94.2 (Universal) (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Darwin arm64 24.1.0
Modes:
Remote OS version: Linux arm64 6.8.0-1018-aws

System Info

Item
Value

CPUs
Apple M2 (8 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
3, 2, 2

Memory (System)
8.00GB (0.16GB free)

Process Argv
--crash-reporter-id 129787a2-41be-4459-8686-d3a80c982a2c

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: staging-new

OS
Linux arm64 6.8.0-1018-aws

CPUs
Neoverse-N1 (8 x 0)

Memory (System)
30.63GB (14.66GB free)

VM
0%

Extensions (22)

Extension
Author (truncated)
Version

jupyter-keymap
ms-
1.1.2

remote-ssh
ms-
0.116.2024102915

remote-ssh-edit
ms-
0.87.0

remote-explorer
ms-
0.4.3

vscode-icons
vsc
12.9.0

JavaScriptSnippets
xab
1.8.0

vscode-tailwindcss
bra
0.12.13

npm-intellisense
chr
1.4.5

vscode-eslint
dba
3.0.10

githistory
don
0.6.20

prettier-vscode
esb
11.0.0

black-formatter
ms-
2024.4.0

debugpy
ms-
2024.12.0

isort
ms-
2023.10.1

python
ms-
2024.3.10741005

vscode-pylance
ms-
2024.3.1

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.9

vscode-jupyter-slideshow
ms-
0.1.6

vscode-typescript-next
ms-
5.8.20241110

vscode-yaml
red
1.15.0

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
impr_priority:31102340
nativerepl2:31139839
refactort:31108082
pythonrstrctxt:31112756
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
h409b430:31177055

Hi @mjbvz , still facing this VS Code Insiders: https://github.com/microsoft/vscode/issues/233125
I can share the logs but tell me what the safe manner to share the log file as it contains sensitive data.

I'm seeing this with 1.95.3.
Disabling and re-enabling the copilot extension fixes it for a little while.

@MarkJBenson  even happening to me in the latest Insiders build ver-1..96.0 as well.

I'm also seeing this on 1.95.3, also with copilot extension.
Disabling the extension is a workaround at the moment.

@sainjay Please email the log to me at matb at microsoft dot com
For everyone else, please test in VS Code insiders. 1.95 does not have the potential fix

TSServer crashing for me also very often:
Typescript output:
024-11-15 22:31:33.732 [info] Using tsserver from: xxxxxxxxxxxxxxxxxxxxxxx\node_modules\typescript\lib\tsserver.js
2024-11-15 22:31:33.732 [info] <syntax> Forking...
2024-11-15 22:31:33.732 [info] <syntax> Starting...
2024-11-15 22:31:33.732 [info] <semantic> Forking...
2024-11-15 22:31:33.732 [info] <semantic> Starting...
2024-11-15 22:31:33.734 [error] TSServer exited. Code: null. Signal: SIGTERM
2024-11-15 22:31:33.766 [info] Killing TS Server
2024-11-15 22:31:33.766 [info] Starting TS Server
2024-11-15 22:31:33.766 [info] Using tsserver from: xxxxxxxxxxxxxxxxxxxxx\node_modules\typescript\lib\tsserver.js
2024-11-15 22:31:33.766 [info] <syntax> Forking...
2024-11-15 22:31:33.766 [info] <syntax> Starting...
2024-11-15 22:31:33.766 [info] <semantic> Forking...
2024-11-15 22:31:33.766 [info] <semantic> Starting...
2024-11-15 22:31:33.781 [error] TSServer exited. Code: null. Signal: SIGTERM
2024-11-15 22:35:16.020 [error] TSServer exited. Code: 134. Signal: null
2024-11-15 22:36:03.031 [info] Starting TS Server
2024-11-15 22:36:03.031 [info] Using tsserver from: xxxxxxxxxxxxxxxxxxxxx\node_modules\typescript\lib\tsserver.js
2024-11-15 22:36:03.031 [info] <syntax> Forking...
2024-11-15 22:36:03.031 [info] <syntax> Starting...
2024-11-15 22:36:03.031 [info] <semantic> Forking...
2024-11-15 22:36:03.031 [info] <semantic> Starting...
2024-11-15 22:38:20.156 [error] TSServer exited. Code: 134. Signal: null
2024-11-15 22:38:20.156 [info] Starting TS Server
2024-11-15 22:38:20.156 [info] Using tsserver from: xxxxxxxxxxxxxxxxxxxxx\node_modules\typescript\lib\tsserver.js
2024-11-15 22:38:20.156 [info] <syntax> Forking...
2024-11-15 22:38:20.156 [info] <syntax> Starting...
2024-11-15 22:38:20.156 [info] <semantic> Forking...
2024-11-15 22:38:20.156 [info] <semantic> Starting...

Note: I'm not running any command or killing the server manually, it's doing it by itself.

@muchisx Please test using VS Code insiders and then open a new issue  if you're still seeing problems. You can follow this guide to diagnose this issue and collect relevant logs so we can investigate. Thanks!


trying OS demo

PR Fixes:

1
2

Resolves #[Issue Number if there]
Checklist before requesting a review

[ ] I have performed a self-review of my code
[ ] I assure there is no similar/duplicate pull request regarding same issue

#673

was trying OS contribution


chore: update package dependencies

#115  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gneiru and the rest of your teammates on  Graphite


MissingPluginException on iOS

Encountered this exception on iOS. Is it because startReceiver is only implemented on Android in Kotlin? Any nice way to avoid this exception on iOS?

Hi,
Same here.

did you find a solution?

Same here

It is nit yet implemented here. If you just want to avoid the exception, them you just need to fix the channel name from flutter_broadcasts to de.kevlatus.flutter_broadcasts and return nil instead of platform version to hide this issue. The better approach is to implement BroadcastManager in Swift similar to manager implemented in Kotlin. I did these steps in my fork, but I am not sure for now, that everything works fine (and it has some additional log behavior that should avoided in production code)


Wz/feature/pypi distribution

Change Summary

updated gitignore to ignore distribution and packaging files

closing this one - updating the readme as well


Unifi Network Application error

I am getting this error in logs on Unifi Network Application's container:
s6-rc-compile: fatal: invalid /etc/s6-overlay/s6-rc.d/ci-service-check/type: must be oneshot, longrun, or bundle
MongoDB container is working as intended.

No idea about what that may be😕... can you give more context? Have you already tried googling the issue?

Regarding context, I am trying to set it up inside a Debian VM on Proxmox. I tried googling this issue but nothing relevant came up.

It seems that deleting the image and redownloading it solved my problem. Thanks!

I'm happy you found your solution! Don't forget to leave a star, we are getting to 50 😂


Feature/ucd 831 horizon submission

Ticket Number

UCD-831
Description of change

Submit completed appeal to Horizon
Checklist

[x] Requires infrastructure changes
[x] If adding or remove environment variables (e.g. in docker-compose.yaml) then I have updated the appropriate Helm chart
[x] I have updated the documentation accordingly
[x] My commit history in this PR is linear
[x] New features have tests
[ ] Breaking change (team conversation required)

Important
Please do not merge from master (please only rebase). This keeps the history linear and easier to debug.

I was able to trigger repeated messages on the queue for the same Appeal by using the PATCH endpoint to change the Appeal state from SUBMITTED to DRAFT and back again. Are we happy with this behaviour?

I was able to trigger repeated messages on the queue for the same Appeal by using the PATCH endpoint to change the Appeal state from SUBMITTED to DRAFT and back again. Are we happy with this behaviour?

My understanding is that we need to be able to modify the appeal after the submission somehow. The PATCH is a technical endpoint and not used by the forms web app. Maybe the solution should be to have a specific submit endpoint and push the queue only in this part and not mix all the needs in the same flow.  I really struggled to clean the controller to be more flexible now that we might have other interactions with horizon.

Here goes nothing


npm run start fails on windows

For windows users using visual studio code if you are getting errors that sleep is not an internal or external command. Locate package.json, scripts and remove sleep 2 && in start:js

This repository is not in general availability. We will not be providing support to run this service until it is ready.
May i know what you are trying to achieve by running this repo though?

I'm trying to understand the Tradetrust protocol as I would like to try and do integration with it to a blockchain project that I'm working on to better understand the possibilities of document storage within blockchain.

None of our code stores the document on the blockchain. Feel free to implement any type of object storage for your project. Will be closing this issue.


ImportError: No module named google.protobuf Command exited with non-zero status 1

I facing the problem while training the model.
ImportError: No module named google.protobuf
Command exited with non-zero status 1
When I try to install protobuf I got
pip install protobuf
Requirement already satisfied: protobuf in /usr/local/lib/python2.7/dist-packages

Can you provide full trace.

This is the full trace

set -e
export PYTHONUNBUFFERED=True
PYTHONUNBUFFERED=True
GPU_ID=1
DATASET=pascal_voc
NET=vgg16
array=($@)
len=3
EXTRA_ARGS=
EXTRA_ARGS_SLUG=
case ${DATASET} in
TRAIN_IMDB=voc_2007_trainval
TEST_IMDB=voc_2007_test
STEPSIZE='[50000]'
ITERS=70000
ANCHORS='[8,16,32]'
RATIOS='[0.5,1,2]'
++ date +%Y-%m-%d_%H-%M-%S
LOG=experiments/logs/vgg16_voc_2007_trainval__vgg16.txt.2017-09-17_23-58-58
exec
++ tee -a experiments/logs/vgg16_voc_2007_trainval__vgg16.txt.2017-09-17_23-58-58
echo Logging output to experiments/logs/vgg16_voc_2007_trainval__vgg16.txt.2017-09-17_23-58-58
Logging output to experiments/logs/vgg16_voc_2007_trainval__vgg16.txt.2017-09-17_23-58-58
set +x
'[' '!' -f output/vgg16/voc_2007_trainval/default/vgg16_faster_rcnn_iter_70000.pth.index ']'
[[ ! -z '' ]]
CUDA_VISIBLE_DEVICES=1
time python ./tools/trainval_net.py --weight data/imagenet_weights/vgg16.pth --imdb voc_2007_trainval --imdbval voc_2007_test --iters 70000 --cfg experiments/cfgs/vgg16.yml --net vgg16 --set ANCHOR_SCALES '[8,16,32]' ANCHOR_RATIOS '[0.5,1,2]' TRAIN.STEPSIZE '[50000]'
Traceback (most recent call last):
File "./tools/trainval_net.py", line 11, in
from model.train_val import get_training_roidb, train_net
File "/users/gpu/vinod1/code_detection/pytorch/state_ot_art_code/pytorch-faster-rcnn-master/tools/../lib/model/train_val.py", line 10, in
import tensorboardX as tb
File "/usr/local/lib/python2.7/dist-packages/tensorboardX/init.py", line 4, in
from .writer import FileWriter, SummaryWriter
File "/usr/local/lib/python2.7/dist-packages/tensorboardX/writer.py", line 24, in
from .src import event_pb2
File "/usr/local/lib/python2.7/dist-packages/tensorboardX/src/event_pb2.py", line 6, in
from google.protobuf import descriptor as _descriptor
ImportError: No module named google.protobuf
Command exited with non-zero status 1
0.09user 0.60system 0:00.08elapsed 849%CPU (0avgtext+0avgdata 19268maxresident)k
0inputs+0outputs (0major+4777minor)pagefaults 0swaps

Did you install tensorflow or tensorflow-tensorboard?

Try conda install protobuf

Yes I have install tensorflow ..

Is this problem related with Tensorflow ??  I am new in python so not fully aware of protobuf stuff.
I didn't  use the anaconda environment, I use pip
Thanks for your quick response :)

Try google the solution. It may be just the problem of protobuf.


delete_keychain stopped working recently

New Issue Checklist

[X] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
Action delete_keychain stopped working recently, fails with error code 162. Last time it was known to work was 28/FEB/2017.
Complete output when running fastlane, including the stack trace and command used
[20:46:18][Step 2/2] INFO [2017-03-07 15:46:18.93]: --------------------
[20:46:18][Step 2/2] INFO [2017-03-07 15:46:18.93]: --- Step: hockey ---
[20:46:18][Step 2/2] INFO [2017-03-07 15:46:18.93]: --------------------
[20:46:18][Step 2/2] INFO [2017-03-07 15:46:18.93]: Starting with file(s) upload to HockeyApp... this could take some time.
[20:46:18][Step 2/2] DEBUG [2017-03-07 15:46:18.93]: Taking value for 'api_token' from environment variable 'FL_HOCKEY_API_TOKEN'
[20:46:29][Step 2/2] INFO [2017-03-07 15:46:29.19]: Public Download URL: https://rink.hockeyapp.net/apps/3cb7390ea256421c87bca8084b60b4c2
[20:46:29][Step 2/2] INFO [2017-03-07 15:46:29.19]: Build successfully uploaded to HockeyApp!
[20:46:29][Step 2/2] INFO [2017-03-07 15:46:29.19]: -----------------------------
[20:46:29][Step 2/2] INFO [2017-03-07 15:46:29.19]: --- Step: delete_keychain ---
[20:46:29][Step 2/2] INFO [2017-03-07 15:46:29.19]: -----------------------------
[20:46:29][Step 2/2] WARN [2017-03-07 15:46:29.25]: Lane Context:
[20:46:29][Step 2/2] INFO [2017-03-07 15:46:29.25]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios production_adhoc", :ORIGINAL_DEFAULT_KEYCHAIN=>"\"/Users/admin/iphone-front-end/ci.keychain\"", :SIGH_PROFILE_TYPE=>"ad-hoc", :BUILD_NUMBER=>"There does not seem to be a CURRENT_PROJECT_VERSION key set for this project.  Add this key to your target's expert build settings.", :HOCKEY_DOWNLOAD_LINK=>"https://rink.hockeyapp.net/apps/3cb7390ea256421c87bca8084b60b4c2", :HOCKEY_BUILD_INFORMATION=>{"title"=>"Grocerkey Production", "bundle_identifier"=>"com.grocerkey.shopperapp", "public_identifier"=>"3cb7390ea256421c87bca8084b60b4c2", "platform"=>"iOS", "release_type"=>3, "custom_release_type"=>"", "created_at"=>"2016-09-05T06:30:41Z", "updated_at"=>"2017-03-07T20:46:29Z", "featured"=>false, "id"=>386292, "config_url"=>"https://rink.hockeyapp.net/manage/apps/386292/app_versions/46", "public_url"=>"https://rink.hockeyapp.net/apps/3cb7390ea256421c87bca8084b60b4c2", "minimum_os_version"=>"9.1", "device_family"=>"iPhone/iPod/iPad", "status"=>2, "visibility"=>"private", "owner"=>"Daniel Glucksman", "owner_token"=>"2e7e9a059d3f3adcc97aff7d27bce433fbe2f772", "company"=>"Grocerkey"}}
[20:46:29][Step 2/2] ERROR [2017-03-07 15:46:29.25]: Shell command exited with exit status 162 instead of 0.
[20:46:29][Step 2/2] INFO [2017-03-07 15:46:29.25]: Successfully generated documentation at path '/Users/admin/buildAgent_production/work/ceb617dede3b303a/fastlane/README.md'
[20:46:29][Step 2/2]
[20:46:29][Step 2/2] +------+---------------------------------------------------------------+-------------+
[20:46:29][Step 2/2] |                                  fastlane summary                                  |
[20:46:29][Step 2/2] +------+---------------------------------------------------------------+-------------+
[20:46:29][Step 2/2] | Step | Action                                                        | Time (in s) |
[20:46:29][Step 2/2] +------+---------------------------------------------------------------+-------------+
[20:46:29][Step 2/2] | 1    | Verifying required fastlane version                           | 0           |
[20:46:29][Step 2/2] | 2    | default_platform                                              | 0           |
[20:46:29][Step 2/2] | 3    | update_fastlane                                               | 5           |
[20:46:29][Step 2/2] | 4    | security list-keychains -s                                    | 0           |
[20:46:29][Step 2/2] | 5    | create_keychain                                               | 0           |
[20:46:29][Step 2/2] | 6    | register_devices                                              | 4           |
[20:46:29][Step 2/2] | 7    | fastlane sigh manage --force --clean_pattern ".*"             | 2           |
[20:46:29][Step 2/2] | 8    | match                                                         | 24          |
[20:46:29][Step 2/2] | 9    | env                                                           | 0           |
[20:46:29][Step 2/2] | 10   | Switch to ios set_version lane                                | 0           |
[20:46:29][Step 2/2] | 11   | increment_build_number                                        | 1           |
[20:46:29][Step 2/2] | 12   | xcodebuild -jobs 4 -workspace /Users/admin/buildAgent_product | 893         |
[20:46:29][Step 2/2] | 13   | fastlane sigh manage --force --clean_pattern "match\ AdHoc\ \ | 2           |
[20:46:29][Step 2/2] | 14   | xcodebuild -verbose -exportArchive -archivePath /Users/admin/ | 33          |
[20:46:29][Step 2/2] | 15   | zip -r '/Users/admin/buildAgent_production/work/ceb617dede3b3 | 2           |
[20:46:29][Step 2/2] | 16   | hockey                                                        | 10          |
[20:46:29][Step 2/2] |       | delete_keychain                                               | 0           |
[20:46:29][Step 2/2] +------+---------------------------------------------------------------+-------------+
[20:46:29][Step 2/2]
[20:46:29][Step 2/2] ERROR [2017-03-07 15:46:29.26]: fastlane finished with errors
[20:46:29][Step 2/2] /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane_core/lib/fastlane_core/ui/interface.rb:146:in `user_error!': [!] Shell command exited with exit status 162 instead of 0. (FastlaneCore::Interface::FastlaneError)
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane_core/lib/fastlane_core/ui/ui.rb:14:in `method_missing'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/helper/sh_helper.rb:55:in `sh_control_output'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/helper/sh_helper.rb:10:in `sh'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/actions/delete_keychain.rb:20:in `run'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:243:in `block (2 levels) in execute_action'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:221:in `block in execute_action'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:217:in `chdir'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:217:in `execute_action'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:139:in `trigger_action_by_name'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/fast_file.rb:146:in `method_missing'
[20:46:29][Step 2/2] 	from Fastfile:350:in `block (2 levels) in parsing_binding'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/lane.rb:33:in `call'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:45:in `chdir'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/runner.rb:45:in `execute'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/lane_manager.rb:52:in `cruise_lane'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/command_line_handler.rb:30:in `handle'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/commands_generator.rb:105:in `block (2 levels) in run'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:38:in `run!'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/commands_generator.rb:302:in `run'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/fastlane/lib/fastlane/cli_tools_distributor.rb:65:in `take_off'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/fastlane-2.19.3/bin/fastlane:15:in `<top (required)>'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/bin/fastlane:22:in `load'
[20:46:29][Step 2/2] 	from /Users/admin/.rbenv/versions/2.3.3/bin/fastlane:22:in `<main>'
[20:46:29][Step 2/2] Process exited with code 1
[20:46:29][Step 2/2] Step Fastlane production build (Command Line) failed

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
10.11.6

Ruby
2.3.3

Bundler?
false

Git
git version 2.7.4 (Apple Git-66)

Installation Source
~/.rbenv/versions/2.3.3/bin/fastlane

Host
Mac OS X 10.11.6 (15G1217)

Ruby Lib Dir
~/.rbenv/versions/2.3.3/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
7.3.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "1.108.0"

default_platform :ios

platform :ios do
  before_all do
    # Frequent updates of fastlane as necessary due to ever changing Apple Developer portal interface.
    update_fastlane
    #
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
    # cocoapods
  end

##### Private lane: set_version
  desc "Set build number"
  lane :set_version do
    build_id = ENV['CI_BUILD_ID']
    puts("Setting build number to #{build_id}")
    # increment_version_number(version_number: build_id)
    increment_build_number(build_number: build_id)
end

##### Lane: SHENV ########################
  desc "Test sh(env) current directory"
  lane :shenv do
    puts("Call of sh('env')")
    sh('env')
    puts("Call of sh('pwd')")
    sh('pwd')
    puts("Call of sh('env')")
    sh('env')
  end

##### Lane: RELEASE ########################
  desc "Deploy a new version to the App Store"
  lane :release do
    # match(type: "appstore")
    # snapshot
    gym # Build your app - more options available
    deliver(force: true)
    # frameit
  end

##### Lane: DEVELOPMENT ########################
desc "Development fastlane"
lane :development do

  keychain_path = "#{ENV['PWD']}/ci.keychain"
  puts("Keychain path will be: #{keychain_path}")
  team_id = "U5CS3T9JSF"
  target = "GrocerKey Dev"

  # Delete possible leftover keychain file, otherwise creation of a new temporary keychain would fail
  # Not needed if we can have a keychain file in the current working directory
  if File.exists?(keychain_path)
    puts("Deleting old keychain file: #{keychain_path}")
    FileUtils.rm_f(keychain_path)
  end

  # Cleanup keychain search list
  sh('security list-keychains -s')

  # Creating temporary keychain
  create_keychain(
    path: keychain_path,
    default_keychain: true,
    unlock: true,
    timeout: false,
    password: SecureRandom.base64
  )

  # Provision devices from file Provisioning/devices to Apple developer portal; optimistic provisioning applies
  register_devices(
    devices_file: "./devices"
  )

  # Remove all existing local provisioning profiles and all distribution provisioning profiles on the development portal
  sh('fastlane sigh manage --force --clean_pattern ".*"')

  # Assure we have right adhoc distribution certificates and provisioning profiles
  match(
    git_url: "git@github.com:GrocerKey/ios-repository.git",
    git_branch: "master",
    type: "adhoc",
    app_identifier: [ "com.grocerkey.shopperapp.development", "*" ],
    username<EMAIL_ADDRESS>    keychain_name: keychain_path,
    team_id: team_id,
    verbose: true,
    force: true,
    shallow_clone: true,
  )

  ENV['sigh_wildcard_adhoc'] = ENV['sigh_*_adhoc']
  puts "Provisioning profile 'sigh_wildcard_adhoc' UUID is: #{ENV['sigh_wildcard_adhoc']}"
  sh('env')

  # Set version and build number
  set_version

  # Building and archiving the project with wildcard provisioning profile, to avoid problems with signining of Cocoa pods, due to https://github.com/CocoaPods/CocoaPods/issues/4331
  # While lane is executed in the current directory, 'sh' action executes in ./fastlane/ subdirectory
  sh("xcodebuild -jobs 4 -workspace #{ENV['PWD']}/GrocerKey.xcworkspace -scheme '#{target}' -destination generic/platform=iOS -sdk iphoneos9.3 -archivePath #{ENV['PWD']}/build/gkdev.xcarchive clean build archive PROVISIONING_PROFILE=$sigh_wildcard_adhoc")

  # Remove wildcard provisioning profile to make sure it is not used during the export
  sh('fastlane sigh manage --force --clean_pattern "match\ AdHoc\ \*"')

  # Exporting the archive with com.grocerkey.shopperapp provisioning profile
  sh("xcodebuild -verbose -exportArchive -archivePath #{ENV['PWD']}/build/gkdev.xcarchive -exportOptionsPlist '#{ENV['PWD']}/exportOptions.#{target}.plist' -exportPath #{ENV['PWD']}/build")

=begin
  # BLOCK COMMENTED OUT
  # gym compilation would work if pods can be built with com.grocerkey.shopperapp provisioning profile
  gym(
    workspace: "./GrocerKey.xcworkspace",
    scheme: "GrocerKey",
    clean: true,
    output_directory: './build/',
    export_method: 'ad-hoc',
    export_options: './exportOptions.plist',
    build_path: './build/',
    sdk: 'iphoneos9.3',
    destination: 'generic/platform=iOS'
  )
=end

# Zipping symbols to be uploaded to Hockey for symbolication
  sh("zip -r \'#{ENV['PWD']}/build/#{target}.app.dSYM.zip\' \'#{ENV['PWD']}/build/gkdev.xcarchive/dSYMs\'")

# Uploading to Hockey. The name of IPA file is the same as the name of a target/scheme
  hockey(
    ipa: "./build/#{target}.ipa",
  )

  # Deleting temporary keychain, cleanup
  delete_keychain(
    name: keychain_path
  )

end

##### Lane: STAGING ########################
desc "Staging fastlane"
lane :staging do

  keychain_path = "#{ENV['PWD']}/ci.keychain"
  puts("Keychain path will be: #{keychain_path}")
  team_id = "U5CS3T9JSF"
  target = "GrocerKey Staging"

  # Delete possible leftover keychain file, otherwise creation of a new temporary keychain would fail
  # Not needed if we can have a keychain file in the current working directory
  if File.exists?(keychain_path)
    puts("Deleting old keychain file: #{keychain_path}")
    FileUtils.rm_f(keychain_path)
  end

  # Cleanup keychain search list
  sh('security list-keychains -s')

  # Creating temporary keychain
  create_keychain(
    path: keychain_path,
    default_keychain: true,
    unlock: true,
    timeout: false,
    password: SecureRandom.base64
  )

  # Provision devices from file Provisioning/devices to Apple developer portal; optimistic provisioning applies
  register_devices(
    devices_file: "./devices"
  )

  # Remove all existing local provisioning profiles and all distribution provisioning profiles on the development portal
  sh('fastlane sigh manage --force --clean_pattern ".*"')

  # Assure we have right adhoc distribution certificates and provisioning profiles
  match(
    git_url: "git@github.com:GrocerKey/ios-repository.git",
    git_branch: "master",
    type: "adhoc",
    app_identifier: [ "com.grocerkey.shopperapp.staging", "*" ],
    username<EMAIL_ADDRESS>    keychain_name: keychain_path,
    team_id: team_id,
    verbose: true,
    force: true,
    shallow_clone: true,
  )

  ENV['sigh_wildcard_adhoc'] = ENV['sigh_*_adhoc']
  puts "Provisioning profile 'sigh_wildcard_adhoc' UUID is: #{ENV['sigh_wildcard_adhoc']}"
  sh('env')

  # Set version and build number
  set_version

  # Building and archiving the project with wildcard provisioning profile, to avoid problems with signining of Cocoa pods, due to https://github.com/CocoaPods/CocoaPods/issues/4331
  # While lane is executed in the current directory, 'sh' action executes in ./fastlane/ subdirectory
  sh("xcodebuild -jobs 4 -workspace #{ENV['PWD']}/GrocerKey.xcworkspace -scheme '#{target}' -destination generic/platform=iOS -sdk iphoneos9.3 -archivePath #{ENV['PWD']}/build/gkdev.xcarchive clean build archive PROVISIONING_PROFILE=$sigh_wildcard_adhoc")

  # Remove wildcard provisioning profile to make sure it is not used during the export
  sh('fastlane sigh manage --force --clean_pattern "match\ AdHoc\ \*"')

  # Exporting the archive with com.grocerkey.shopperapp provisioning profile
  sh("xcodebuild -verbose -exportArchive -archivePath #{ENV['PWD']}/build/gkdev.xcarchive -exportOptionsPlist '#{ENV['PWD']}/exportOptions.#{target}.plist' -exportPath #{ENV['PWD']}/build")

=begin
  # gym compilation would work if pods can be built with com.grocerkey.shopperapp provisioning profile
  gym(
    workspace: "./GrocerKey.xcworkspace",
    scheme: "GrocerKey",
    clean: true,
    output_directory: './build/',
    export_method: 'ad-hoc',
    export_options: './exportOptions.plist',
    build_path: './build/',
    sdk: 'iphoneos9.3',
    destination: 'generic/platform=iOS'
  )
=end

# Zipping symbols to be uploaded to Hockey for symbolication
  sh("zip -r \'#{ENV['PWD']}/build/#{target}.app.dSYM.zip\' \'#{ENV['PWD']}/build/gkdev.xcarchive/dSYMs\'")

# Uploading to Hockey. The name of IPA file is the same as the name of a target/scheme
  hockey(
    ipa: "./build/#{target}.ipa",
  )

  # Deleting temporary keychain, cleanup
  delete_keychain(
    name: keychain_path
  )

end

##### Lane: PRODUCTION ADHOC ########################
desc "Production Adhoc fastlane"
lane :production_adhoc do

  keychain_path = "#{ENV['PWD']}/ci.keychain"
  puts("Keychain path will be: #{keychain_path}")
  team_id = "U5CS3T9JSF"
  target = "GrocerKey Production"

  # Delete possible leftover keychain file, otherwise creation of a new temporary keychain would fail
  # Not needed if we can have a keychain file in the current working directory
  if File.exists?(keychain_path)
    puts("Deleting old keychain file: #{keychain_path}")
    FileUtils.rm_f(keychain_path)
  end

  # Cleanup keychain search list
  sh('security list-keychains -s')

  # Creating temporary keychain
  create_keychain(
    path: keychain_path,
    default_keychain: true,
    unlock: true,
    timeout: false,
    password: SecureRandom.base64
  )

#=begin
  # Provision devices from file Provisioning/devices to Apple developer portal; optimistic provisioning applies
  register_devices(
    devices_file: "./devices"
  )
#=end

  # Remove all existing local provisioning profiles and all distribution provisioning profiles on the development portal
  sh('fastlane sigh manage --force --clean_pattern ".*"')

  # Assure we have right adhoc distribution certificates and provisioning profiles
  match(
    git_url: "git@github.com:GrocerKey/ios-repository.git",
    git_branch: "master",
    type: "adhoc",
    app_identifier: [ "com.grocerkey.shopperapp", "*" ],
    username<EMAIL_ADDRESS>    keychain_name: keychain_path,
    team_id: team_id,
    verbose: true,
	# Next line must be commented out if we want to use readonly param, otherwise it would not find the provisioning profile
    force: true,
    shallow_clone: true,
	# The following option is useful while Apple developer portal is experiencing issues.
	# It allows to use profiles and certificates from git and does not fail on developer portal error.
	# Also, register_devices must be commented out
	# readonly: true
  )

  ENV['sigh_wildcard_adhoc'] = ENV['sigh_*_adhoc']
  puts "Provisioning profile 'sigh_wildcard_adhoc' UUID is: #{ENV['sigh_wildcard_adhoc']}"
  sh('env')

  # Set version and build number
  set_version

  # Building and archiving the project with wildcard provisioning profile, to avoid problems with signining of Cocoa pods, due to https://github.com/CocoaPods/CocoaPods/issues/4331
  # While lane is executed in the current directory, 'sh' action executes in ./fastlane/ subdirectory
  sh("xcodebuild -jobs 4 -workspace #{ENV['PWD']}/GrocerKey.xcworkspace -scheme '#{target}' -destination generic/platform=iOS -sdk iphoneos9.3 -archivePath #{ENV['PWD']}/build/gkdev.xcarchive clean build archive PROVISIONING_PROFILE=$sigh_wildcard_adhoc")

  # Remove wildcard provisioning profile to make sure it is not used during the export
  sh('fastlane sigh manage --force --clean_pattern "match\ AdHoc\ \*"')

  # Exporting the archive with com.grocerkey.shopperapp provisioning profile
  sh("xcodebuild -verbose -exportArchive -archivePath #{ENV['PWD']}/build/gkdev.xcarchive -exportOptionsPlist '#{ENV['PWD']}/exportOptions.#{target}.plist' -exportPath #{ENV['PWD']}/build")

=begin
  # gym compilation would work if pods can be built with com.grocerkey.shopperapp provisioning profile
  gym(
    workspace: "./GrocerKey.xcworkspace",
    scheme: "GrocerKey",
    clean: true,
    output_directory: './build/',
    export_method: 'ad-hoc',
    export_options: './exportOptions.plist',
    build_path: './build/',
    sdk: 'iphoneos9.3',
    destination: 'generic/platform=iOS'
  )
=end

# Zipping symbols to be uploaded to Hockey for symbolication
  sh("zip -r \'#{ENV['PWD']}/build/#{target}.app.dSYM.zip\' \'#{ENV['PWD']}/build/gkdev.xcarchive/dSYMs\'")

# Uploading to Hockey. The name of IPA file is the same as the name of a target/scheme
  hockey(
    ipa: "./build/#{target}.ipa",
  )

  # Deleting temporary keychain, cleanup
  delete_keychain(
    name: keychain_path
  )

end

##### Lane: PRODUCTION APPSTORE ########################
desc "Production Appstore fastlane"
lane :production_appstore do

  keychain_path = "#{ENV['PWD']}/ci.keychain"
  puts("Keychain path will be: #{keychain_path}")
  team_id = "U5CS3T9JSF"
  target = "GrocerKey AppStore"

  # Delete possible leftover keychain file, otherwise creation of a new temporary keychain would fail
  # Not needed if we can have a keychain file in the current working directory
  if File.exists?(keychain_path)
    puts("Deleting old keychain file: #{keychain_path}")
    FileUtils.rm_f(keychain_path)
  end

  # Cleanup keychain search list
  sh('security list-keychains -s')

  # Creating temporary keychain
  create_keychain(
    path: keychain_path,
    default_keychain: true,
    unlock: true,
    timeout: false,
    password: SecureRandom.base64
  )

#=begin
  # Provision devices from file Provisioning/devices to Apple developer portal; optimistic provisioning applies
  register_devices(
    devices_file: "./devices"
  )
#=end

  # Remove all existing local provisioning profiles and all distribution provisioning profiles on the development portal
  # How to remove undesired provisioning profiles from match repo?
  # TODO; to avoid Xcode select wrong profile
  sh('fastlane sigh manage --force --clean_pattern ".*"')

  # Assure we have right adhoc distribution certificates and provisioning profiles
  match(
    git_url: "git@github.com:GrocerKey/ios-repository.git",
    git_branch: "master",
    type: "appstore",
    app_identifier: [ "com.grocerkey.shopperapp.woodmans", "*" ],
    username<EMAIL_ADDRESS>    keychain_name: keychain_path,
    team_id: team_id,
    verbose: true,
	# Next line must be commented out if we want to use readonly param, otherwise it would not find the provisioning profile
    force: true,
    shallow_clone: true,
	# The following option is useful while Apple developer portal is experiencing issues.
	# It allows to use profiles and certificates from git and does not fail on developer portal error.
	# Also, register_devices must be commented out
	# readonly: true
  )

  ENV['sigh_wildcard_appstore'] = ENV['sigh_*_appstore']
  puts "Provisioning profile 'sigh_wildcard_appstore' UUID is: #{ENV['sigh_wildcard_appstore']}"
  sh('env')

  # Set version and build number
  set_version

  # Building and archiving the project with wildcard provisioning profile, to avoid problems with signining of Cocoa pods, due to https://github.com/CocoaPods/CocoaPods/issues/4331
  # While lane is executed in the current directory, 'sh' action executes in ./fastlane/ subdirectory
  sh("xcodebuild -jobs 4 -workspace #{ENV['PWD']}/GrocerKey.xcworkspace -scheme '#{target}' -destination generic/platform=iOS -sdk iphoneos9.3 -archivePath #{ENV['PWD']}/build/gkdev.xcarchive clean build archive PROVISIONING_PROFILE=$sigh_wildcard_appstore")

  # Remove wildcard provisioning profile to make sure it is not used during the export
  sh('fastlane sigh manage --force --clean_pattern "match\ AdHoc\ \*"')

  # Exporting the archive with com.grocerkey.shopperapp provisioning profile
  sh("xcodebuild -verbose -exportArchive -archivePath #{ENV['PWD']}/build/gkdev.xcarchive -exportOptionsPlist '#{ENV['PWD']}/exportOptions.#{target}.plist' -exportPath #{ENV['PWD']}/build")

=begin
  # gym compilation would work if pods can be built with com.grocerkey.shopperapp provisioning profile
  gym(
    workspace: "./GrocerKey.xcworkspace",
    scheme: "GrocerKey",
    clean: true,
    output_directory: './build/',
    export_method: 'ad-hoc',
    export_options: './exportOptions.plist',
    build_path: './build/',
    sdk: 'iphoneos9.3',
    destination: 'generic/platform=iOS'
  )
=end

# Zipping symbols to be uploaded to Hockey for symbolication
  sh("zip -r \'#{ENV['PWD']}/build/#{target}.app.dSYM.zip\' \'#{ENV['PWD']}/build/gkdev.xcarchive/dSYMs\'")

# Uploading to Hockey. The name of IPA file is the same as the name of a target/scheme
  hockey(
    ipa: "./build/#{target}.ipa",
  )

  # Deleting temporary keychain, cleanup
  delete_keychain(
    name: keychain_path
  )

end

######################################################################################################
### FINAL COMMON BLOCK
######################################################################################################
  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md

# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
app_identifier "com.grocerkey.shopperapp" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "U5CS3T9JSF"  # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.19.3
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.2

slack-notifier
1.5.1

i18n
0.7.0

json
1.8.3

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.9.1

activesupport
<IP_ADDRESS>

CFPropertyList
2.3.4

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.1

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

terminal-table
1.4.5

plist
3.2.0

addressable
2.3.8

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

highline
1.7.8

commander
4.4.0

excon
0.54.0

faraday
0.10.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
1.6.8

gh_inspector
1.0.2

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
<IP_ADDRESS>

google-api-client
0.9.20

mini_magick
4.5.1

multi_xml
0.5.5

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.1.1

bundler
1.13.6

faraday_middleware
0.10.1

io-console
0.4.6

rubyzip
1.2.0

generated on: 2017-03-07

Hm. #8003 would be the change to be suspicious about.
Can you please show us how you're calling the action in your Fastfile?

@mfurtak Thanks for your quick response. Fastfile is attached in the original post, please see "fastlane environment", unfold it and inside you will find "fastlane files:" section.
All lanes are affected. The Fastfile has not been changed when the issue started to happen.
Relevant parts cited below:
##### Lane: PRODUCTION APPSTORE ########################
desc "Production Appstore fastlane"
lane :production_appstore do

  keychain_path = "#{ENV['PWD']}/ci.keychain"
  puts("Keychain path will be: #{keychain_path}")
  team_id = "U5CS3T9JSF"
  target = "GrocerKey AppStore"

  # Delete possible leftover keychain file, otherwise creation of a new temporary keychain would fail
  # Not needed if we can have a keychain file in the current working directory,
  # because we always perform clean git checkout.
  if File.exists?(keychain_path)
    puts("Deleting old keychain file: #{keychain_path}")
    FileUtils.rm_f(keychain_path)
  end

  # Cleanup keychain search list
  sh('security list-keychains -s')

  # Creating temporary keychain
  create_keychain(
    path: keychain_path,
    default_keychain: true,
    unlock: true,
    timeout: false,
    password: SecureRandom.base64
  )

[truncated]
  # Deleting temporary keychain, cleanup
  delete_keychain(
    name: keychain_path
  )

end

Of course - I should know that by now! Thanks :smile:

I very much welcome and appreciate your help!
Let me add that I believe it must have been caused by some change released on Feb 28 or later, as all our lanes include auto-update of fastlane.

Yeah, it's because of the change I linked above. I had concerns about it, but I let it through anyway 🙁  The regression is not acceptable, and I apologize for it.
For the code that exists now now, you can work around this by using:
delete_keychain(
  keychain_path: keychain_path
)

I'll discuss with the team, and we will potentially roll that change back, or try to find a different way to preserve everyone's workflow.

My issue is now solved, the proposed change has made it working again. Thanks for your help. I am not sure whether you want to keep this issue opened or not - please feel free to do whatever is best for you.
I do not mind to evolve the workflow, as long as it serves an important purpose, e.g. development of bright future :)
Maintaining backward compatibility forever is too much burden.

Thanks for your understanding - I'm glad that you're working again 🙌
I think we are going to make another change to try to make it so that both previous and current code will work correctly 👍  I'll close this when that is done.

I've merged https://github.com/fastlane/fastlane/pull/8467 to address this, so I'll close this for now. Thanks again!


Bracers of the First Men attack speed bonus not affecting Hammer of the Ancients

The Bracers of the First Men should provide a 50% attack speed bonus to the Hammer of the Ancients skill, but that is not occurring on D3Planner.  Note: this was working correctly on the PTR version of D3Planner before 2.6.1 went live.
See attached screenshots showing the attack speed/breakpoints being unaffected by the item:

Fixed.

Thanks.
Unfortunately, now the Breakpoint tooltip is showing information as though you are one breakpoint ahead of what you should be.  Specifically, the Next Breakpoint info is actually for two breakpoints ahead, the Previous Breakpoint info is actually for the current breakpoint (as can be seen by it being a positive ASI number instead of negative, with +0% DPS), and the highlighted info in the table is for the next breakpoint instead of the current one.
This appears to only be an issue with the barbarian class, but it affects all barbarian skills, whether or not Bracers of the First Men is equipped.
See attached screenshot with tooltip info for the 19 frames breakpoint even though the current breakpoint is 20 frames:


Force the markdown filter for Obsidian documents.

Close #9

It could be nice to have a documentation of all possible values of laReponse.filtreActif.
Obsidian main target is Markdown, but users can also open any kind of file (text or binary), so, only forcing Markdown is not the best solution IMHO.

We are currently working on an official documentation for the API.
If the "filtreActif" option is not set, Antidote will try to detect the best filter to apply to the document.
Otherwise, you can choose one of the following filters to be applied :
"texte"
"markdown"
"latex"
"subrip"

I do not have the right to push to your branch, so, can you apply the following path, to support all supported format:
Update_DonneTypeDocument_to_support_all_Antidote_supported_format.patch
Furthermore, I tested on my side, and the formatting does not work.
macOS: 13.1 (22C65)
Antiode: 11.2.4317
Connectix: 11.2.1 (1102.46.27)

Thank you for the update.
I tested on my side, and the formatting still does not work.
macOS: 13.1 (22C65)
Antiode: 11.2.4317
Connectix: 11.2.1 (1102.46.27)

Is a specific version of Connectix needed?

We'll be including the fix in the upcoming update - 11 v3.2, due next week.


cubear/finder not matching minimum-stability

Hi,
We're running docker.io/bitnami/drupal:8.6.3 (in a kubernetes cluster).
When I try to install finder, I get an error.
composer require cubear/finder
[InvalidArgumentException]
Could not find a version of package cubear/finder matching your minimum-stability (stable). Require it with an explicit version constraint allowing it
s desired stability.
Any suggestions?
Thanks,
Ron

My mistake, I wasn't in the drupal directory.
Sorry

My mistake


[W5.7][W14-2] Leong Eng Sea

src/seedu/addressbook/Main.java: List all persons automatically after an add or delete command.

Hey Eng Sea, good attempt at enhancing the add/delete command. I have some suggestions:

Structure the enhancement in a more systematic way, don't just introduce it using bootstrap code inside main.java. Code might become highly unsustainable after a few iterations of this.
Update your test cases, both JUnit and I/O. When Travis fails, I think it indicates that at least one of these tests have failed. Commits with failing tests should be fixed quickly to reduce the cost of fixing them later.
Using the Parser as such to simulate commands should be avoided. The Parser's main role is to parse actual input from the user, keeping its Single Responsibility.
Please consider my suggestions, it is really beneficial for you and our team.


Link checkpoint user_ids to SaaS users

Our checkpoint data in Segment uses a node ID as the user_id. If we include node IDs in the RPCs issued by the dotmesh server behind push/pull operations, then in the SaaS, we can log the relationship between that node ID and the SaaS user (this depends on issue https://github.com/dotmesh-io/dothub/issues/32 so wel know their Segment UUID) into segment so we can tie those two identities together.
This is part of epic https://github.com/dotmesh-io/non-coding-tasks/issues/34

How we record that relationship between UUID and node ID needs to be investigated.

We have a generic Metadata property for SaaS users now that contains the distributed trackingID - we can add a list of seen node-ids that can be combined with the trackingID to identify a checkpoint ping with a hub user


Flink 1745

I added a quadtree data structure for the knn algorithm.  The quadtree scales very well with the number of training + test points, but scales poorly with the dimension.  I added a flag that is automatically determines whether or not to use the quadtree.  My implementation needed to use the Euclidean or SquaredEuclidean distance since I needed a specific notion of the distance between a test point and a box in the quadtree.  I added another test KNNQuadTreeSuite in addition to Chiwan Park's KNNITSuite, since C. Park's parameters will automatically choose the brute-force non-quadtree method.
For more details on the quadtree + how I used it for the KNN query, please see another branch I created that has a README.md:
https://github.com/danielblazevski/flink/tree/FLINK-1745-devel/flink-staging/flink-ml/src/main/scala/org/apache/flink/ml/nn

@danielblazevski Hi, Thanks for your contribution. But you should send this pull request to apache/flink repository.


amend load print

Add a final print to log at the end of init.lua to indicate the mod was loaded successfully. This idea was derived from other mods which are specifically aimed at MT servers.
This could be useful not only for player support (e.g. in the MT forum) but would certainly be useful for MT server admins using the CLI and reading their server logs.

This only prints to stdout. If you want a proper log entry, consider using minetest.log.

Closing for the following reasons:

print does not log to debug.txt (what headless server owners likely use)
The "info" log level already logs all mods.
The chat command /mods lists them (also works with ncurses admin prompt, what server owners also could use)
Recent Minetest versions no longer start up when mod dependencies are not fulfilled. All specified mods must load.


context color easy access

now that the context colors are defined in components/types and have the type enum it's a bit difficult to reference it,
so I think either types should be exported in the Components object, or the type should be altered so that simply predefined string could be used

is it solved in https://github.com/nexys-system/tailwind-react-ui/blob/master/src/lib/components/type.ts#L17 @NatalieKapitonova


Get rid of obsolete notifications on package details view

Fixes https://github.com/NuGet/NuGetGallery/issues/4788 (see issue for details)

I see your comment to @anangaur, but it seems weird to leave the "edit failed" message if we are removing the "pending edit". I think we should remove both at the same time, but your call!

@joelverhagen the thing is that edits may still be pending at the time of deployment, so we may need to remove this particular Edit-Failed notification in a second deployment?

@joelverhagen the thing is that edits may still be pending at the time of deployment, so we may need to remove this particular Edit-Failed notification in a second deployment?

Seems fine. I think failed edits are a very rare occurrence.


Couldn't find node when building

Whenever I try to build the driver myself, ROS is unable to find the node and launch it.
If I try to start it with the launch file it simply states that the ellipse node can't be found. If I try to launch the node manually I still can't find it.
Note: I've been sourcing after building
I managed to get over this issue simply by adding catkin_package() in the CmakeList.
Is this expected behaviour or should I submit a pull request?

No: it is not the expected behavior. Did you checkout to the 1.0.7 version (the last version on the repo doesn't work) ?
I'm currently restarting the whole node (see devel branch): a stable version should be release this week.

I used the master branch (seems to be v1.0.6).
Just tested v1.0.7 and it doesn't have this issue. Is the new stable version you spoke of meant to have any major changes?

Yes there will be major changes: it will better implement the SBG library. New messages and topics as been created. It will be possible to configure the IMU with a yaml file and to proceed to a magnetic calibration throw a ROS service.


Exposure Key TTL is Too Short/Should be Handled by Clients Not Server

Caveat: I’m a golang novice and am not an epidemiologist, so perhaps this issue will be nonsensical. If so, I apologize.
After reading through this out of curiosity, I noticed something that doesn’t quite make sense to me. Currently, exposure keys effectively “expire” after a certain amount of time (default 336h/14 days), so whenever the cleanup routine is run keys older than that will be removed from the database. My understanding is that those keys only reflect people who are positive for the virus, thus creating a database that my phone can check against to see if I’ve been in contact with any of them.
I’m wondering if the 14-day rule should be a “client” concern and not a server concern. To explain: as far as I understand it, the incubation period for COVID-19 is believed to be no longer than 14 days, so if I’m more than 14 days out from being exposed to someone who was positive, I’m in the clear. However, that doesn’t necessarily work the other way around. If I’m positive for the virus, presumably there are a certain number of days for which I’m shedding the virus and therefore an exposure risk to anyone who encounters me. That number is probably variable from person to person, so let’s call the last day that I’m shedding the virus f (for final). So after day f I’m no longer a potential vector for transmission and after day f + 14 no one who has encountered me is at any risk (from me). But we don’t necessarily know what f is, which means removing my key from the database after 14 days is almost certainly too soon: I was probably still a potential transmitter for some number of days after my first report. That said, for an individual client on someone’s phone, it would be safe to ignore my key if the last time they encountered me was more than 14 days ago.
I understand we don’t want the database to grow exponentially, so there needs to be some way of removing keys that are no longer relevant. There’s two ways I see to do this. The easy way would be to just change the default TTL to 14 + whatever the longest expected duration of someone shedding the virus is. The harder but probably more epidemiologically correct way would be to offer a “removal” mechanism parallel to the publishing process whereby I can certify that I am no longer positive and have my key marked as “deprecated” and set to be removed 14 days later. This should also probably result in the key being treated differently by the clients (ie, they only care about this key if their exposure was prior to the deprecation date, not after it).
Hope that’s helpful, thanks for all the work on this.

Hi @apmarshall - thank you for the feedback. 14 days is the current guidance from epidemiologists, but we designed the system to be configurable. If guidance should change, we can increase or decrease that number.
/kind question

14 days is a hard number in the device (iOS + Android) APIs. They will ignore keys that are older than 14 days when matching is requested.
Reference: Android API documentation v1.3.2
Our system allows for configurable storage, if an operator wanted to retain that information for longer, but after a key has aged bast the 14 day mark it can't be used for matching.

On further reading, I may have figured out how this works and found the answer to my own question. Correct me if I’m wrong:
Devices refresh their exposure keys at regular intervals. So a given device may be represented by multiple exposure keys in the database. This means that a given key doesn’t just represent a device, it represents that device at that time (interval). Therefore, deleting the key isn’t the same thing as marking a device “clean,” it’s more akin to saying “this contact window with this device is now too old to trigger notification.” Do I have that right?
So presumably (and maybe this is based on client implementations?) an individual who had been verified as positive will continue submitting exposure keys to the database for as long as they are “positive,” thereby updating the time intervals during which contact with them might be an “exposure event.” Assuming I’m understanding how this is supposed to work correctly, now, then the 14-day window makes sense, as each key is a little more specific (device + time) than I initially understood (just device).

Devices get new temporary exposure keys every day.
This reference server doesn't have a protocol implemented for continuously updating keys after the initial diagnosis. That's not to say that is prohibited in this model, but we haven't yet accounted for it.
/close
Feel free to reopen if you feel something has gone unanswered here. Thanks!


33-svg-mocks

Fixes #33
Creator

[x] Build relevant tests if any apply
[x] Ensure there are no new warnings
[x] Upload an animated GIF showcasing the solution (if it applies)
[x] Set a relevant reviewer

Reviewer

[ ] Run test and make sure all tests pass
[ ] Review function and form on iOS
[ ] Review function and form on Android
[ ] Review function and form on Web
[ ] Review new test logic

I ended up using this, the only open PR on jest-expo that basically does what I was going to do

@conrad-vanl ready


Any plans to write a guide for adding new origins? [Enhancement]

Hi there!
Fantastic datapack, I'm planning to use it on my server as a serverside alternative to Origins. That being said, I wanted to ask if you have any plans to write a guide for adding new origins?
Thanks a lot!

I plan on doing this, however I'm a little unsure how to go about it, whether that be having a function file with attribute modifiers that can be modified, or allowing for more customized abilities, so any suggestions would be great!


[WIP] Homepage with shared cursors

 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.


FancyZones snap without mouse

I would like to move/snap windows into fancyzones with a user-specified shorcut like Ctrl + Alt + 1 for zone 1 and Ctrl + Alt + 2 for zone 2 as addition to existing mouse drag+ shift combination.
I've never find useful windows' default key combination windows + arrow buttons. I would like to arrange windows with one hand not two.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Duplicate of https://github.com/microsoft/PowerToys/issues/492


Fix integration tests on Macs with mixed case hostnames

Also fix race conditions on status sync loops which can result in sporadic failures.
Fixes #5757

Yuck, lots of code using os.Hostname()...

I've cleaned up pkg/kubelet/config/* to not use os.Hostname() and instead take the Kubelets hostname as an argument.

LGTM
Thanks for those changes @smarterclayton

It seems that Shippable failure is a flake.

Addressed nit, will merge on green.

The shippable failure is either a timing problem (slow) or a race in the integration test.  Will look a bit more through it to double check.

Ah ha!  There was a bug in podRunning.  That was fun... this should go green now.

LGTM, just waiting

One shippable flaked, the other passed.

Travis will probably run sometime before next Monday.

1/2 shippable is done.  only took 15 minutes

Green


petitions and take_action pages have boiler plate text

http://go.brandnewcongress.org/petition
To change this content, click "Edit this page" in the Supporter Nav on the right,
or from your Control Panel navigate to Websites > [take_action] > Subpages > [petition] > Petition settings > Intro/Content.
http://go.brandnewcongress.org/take_action
To change this content, click "Edit this page" in the Supporter Nav on the right,
or from your Control Panel navigate to Websites > [take_action] > Content.

Yeah those pages shouldn't exist.  The template for the teams page got messed up and a bunch of nationbuilder cruft got put into it.  Closing this issue for now in favor of #102


wasm-tools: 1.214.0 -> 1.215.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bytecodealliance/wasm-tools/releases.
meta.description for wasm-tools is: Low level tooling for WebAssembly in Rust
meta.homepage for wasm-tools is: https://github.com/bytecodealliance/wasm-tools
Updates performed

Rust version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.215.0 with grep in /nix/store/hd2g687rfrbih428p2kxqg0h17rbp4l6-wasm-tools-1.215.0
found 1.215.0 in filename of file in /nix/store/hd2g687rfrbih428p2kxqg0h17rbp4l6-wasm-tools-1.215.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

wasm-tools

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/90928184b6cafe9cf1c13ada7355c28ecc517633#wasm-tools

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hd2g687rfrbih428p2kxqg0h17rbp4l6-wasm-tools-1.215.0
ls -la /nix/store/hd2g687rfrbih428p2kxqg0h17rbp4l6-wasm-tools-1.215.0/bin

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

1 package built:

wasm-tools

Maintainer pings
cc @ereslibre for testing.

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

1 package built:

wasm-tools


core dump when runs graphsage with ppi data

euler version: euler_gl-0.1.2-py2.7
I generate ppi example with ppi_data.py. And then run the command
python -m tf_euler \
>   --data_dir ppi \
>   --max_id 56944 --feature_idx 1 --feature_dim 50 --label_idx 0 --label_dim 121 \
>   --model graphsage --mode train

The output is below:
I0917 03:12:03.831502 24604 graph_builder.cc:81] Load Done: ppi/ppi_data.dat
I0917 03:12:03.831904 24554 graph_builder.cc:127] Each Thread Load Finish! Node Count:56944 Edge Count:1612348
I0917 03:12:03.831966 24554 graph_builder.cc:135] Graph Loading Finish!
I0917 03:12:04.269271 24554 graph_builder.cc:147] Graph Load Finish! Node Count:56944 Edge Count:1612348
I0917 03:12:04.511008 24554 graph_builder.cc:159] Done: build all sampler
I0917 03:12:04.511050 24554 graph_builder.cc:162] Graph build finish
WARNING:tensorflow:From /usr/local/lib/python2.7/dist-packages/euler_gl-0.1.2-py2.7.egg/tf_euler/python/encoders.py:354: The name tf.logging.warning is deprecated. Please use tf.compat.v1.logging.warning instead.

W0917 03:12:04.512913<PHONE_NUMBER>66944 deprecation_wrapper.py:119] From /usr/local/lib/python2.7/dist-packages/euler_gl-0.1.2-py2.7.egg/tf_euler/python/encoders.py:354: The name tf.logging.warning is deprecated. Please use tf.compat.v1.logging.warning instead.

WARNING:tensorflow:use_feature is deprecated and would not have any effect.
W0917 03:12:04.513195<PHONE_NUMBER>66944 encoders.py:354] use_feature is deprecated and would not have any effect.
Segmentation fault (core dumped)

The py-bt information of core file is
(gdb) py-bt
Traceback (most recent call first):
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 1864, in _create_c_op
    c_op = c_api.TF_FinishOperation(op_desc)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 2027, in __init__
    control_input_ops)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 3616, in create_op
    op_def=op_def)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
    op_def=op_def)
  File "<string>", line 74, in sample_node
  File "/usr/local/lib/python2.7/dist-packages/euler_gl-0.1.2-py2.7.egg/tf_euler/python/run_loop.py", line 104, in run_train
    count=batch_size, node_type=flags_obj.train_node_type)
  File "/usr/local/lib/python2.7/dist-packages/euler_gl-0.1.2-py2.7.egg/tf_euler/python/run_loop.py", line 357, in run_network_embedding
    run_train(model, flags_obj, master, is_chief)
  File "/usr/local/lib/python2.7/dist-packages/euler_gl-0.1.2-py2.7.egg/tf_euler/python/run_loop.py", line 368, in run_local
    run(flags_obj, master='', is_chief=True)
  File "/usr/local/lib/python2.7/dist-packages/euler_gl-0.1.2-py2.7.egg/tf_euler/python/run_loop.py", line 405, in main
    run_local(flags_obj, run_network_embedding)
  File "/usr/local/lib/python2.7/dist-packages/absl/app.py", line 250, in _run_main
    sys.exit(main(argv))
  File "/usr/local/lib/python2.7/dist-packages/absl/app.py", line 299, in run
    _run_main(main, args)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 40, in run
    _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
  File "/usr/local/lib/python2.7/dist-packages/euler_gl-0.1.2-py2.7.egg/tf_euler/__main__.py", line 28, in <module>
    tf.app.run(run_loop.main)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)

Do you have any suggestions about the core-dump problem?
Thank you!

I solved the problem, try to use tensorflow 1.12 via pip --no-cache-dir install tensorflow==1.12

有可能需要指定train_edge_type，默认是0
具体参考https://github.com/alibaba/euler/blob/e5387e1a4e8345ffd6f7e39fc4052a7abf6f7b56/tf_euler/python/run_loop.py#L283

Yes, the docker install tensorflow with the lastest version default. We should install the version==1.12.0
You should update the pandas packages and so on or that will happen with a tf.estimator package not installed problem during installation.

@@better629 @yangsiran  Hello, I have met the same problem,  have any solution for this problem ?

@Yang-HangWA


Adsk Contrib - Fix some TruelightOp issues

While implementing the bit-depth support, I found issues around the TruelightOp implementation. That op was not correctly updated following the latest refactoring #699 . As there are no unit test, it will certainly happen again.

This PR qualifies for single approver rule and could be merged end next week unless there is feedback.

Please review by the end of the week as we have another PR that this is blocking.  Thanks!


Sign in as guest

Hey there! So you want to contribute to FirebaseUI? Before you file this pull request, follow these steps:

Read the contribution guidelines.
Run ./gradlew check to ensure the Travis build passes.
If this has been discussed in an issue, make sure to mention the issue number here. If not, go file an issue about this to make sure this is a desirable change.
If this is a new feature please co-ordinate with someone on FirebaseUI-iOS to make sure that we can implement this on both platforms and maintain feature parity.

foxxzimgrrporn
On Thu, Jul 4, 2019, 4:41 AM Tasheena Papin<EMAIL_ADDRESS>wrote:

On Thursday, July 4, 2019, foxharleycartwright13<EMAIL_ADDRESS>wrote:

@foxharleycartwright13 commented on this pull request.
In auth/src/main/res/values/strings.xml
https://github.com/firebase/FirebaseUI-Android/pull/1651#discussion_r300317415
:

@@ -21,6 +21,7 @@
Sign in with GitHub
Sign in with email
Sign in with phone

Continue as guest

Yay
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/FirebaseUI-Android/pull/1651?email_source=notifications&email_token=AMQXN4PMF34SH6LCOFPQTKTP5XAR3A5CNFSM4H5WKO5KYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB5P5KTQ#pullrequestreview-257938766,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMQXN4IV4QWMMKICCF6KGF3P5XAR3ANCNFSM4H5WKO5A
.

https://www.google.com/url?q=http://mail-io1-f46.google.com&source=gmail&ust=1562341767771000&usg=AFQjCNG8y0i55zQH_9Dy-xepAbrbdbGxqg
<EMAIL_ADDRESS>

<EMAIL_ADDRESS>On Thu, Jul 4, 2019, 9:59 AM foxharleycartwright13<EMAIL_ADDRESS>wrote:

https://www.google.com/url?q=http://mail-io1-f46.google.com&source=gmail&ust=1562341767771000&usg=AFQjCNG8y0i55zQH_9Dy-xepAbrbdbGxqg
<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/FirebaseUI-Android/pull/1651?email_source=notifications&email_token=AMQXN4IGPLROUKYO75Q2G7DP5YM5LA5CNFSM4H5WKO5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZHYEMY#issuecomment-508527155,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMQXN4IWGXWJKJF4LDF2LMDP5YM5LANCNFSM4H5WKO5A
.

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>On Thu, Jul 4, 2019, 10:19 AM foxharleycartwright13 <
<EMAIL_ADDRESS>wrote:

<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/FirebaseUI-Android/pull/1651?email_source=notifications&email_token=AMQXN4KWP6Y4HXQOB3NTEQLP5YPITA5CNFSM4H5WKO5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZHZICI#issuecomment-508531721,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMQXN4OOFYFT34PA4DGDA5LP5YPITANCNFSM4H5WKO5A
.


Output video is not seekable if I am saving the video using writestream() or pipe() in s3.

Version information

fluent-ffmpeg version:"^2.1.2"
ffmpeg version : 4.2.9
OS: Windows

Code to reproduce

const { spawn } = require('child_process');
const ffmpeg = require('fluent-ffmpeg');
const AWS = require('aws-sdk');
const stream = require("stream");
const fs = require('fs');
// Configure AWS
AWS.config.update({
  accessKeyId: configData.accessKeyId,
  secretAccessKey: configData.secretAccessKey,
  region: configData.region
});
const bucketNameOfS3 = configData.bucketNameOfS3
const s3 = new AWS.S3({
  apiVersion: '2006-03-01',
  signatureVersion: 'v4',
  accessKeyId: configData.accessKeyId,
  secretAccessKey: configData.secretAccessKey,
  region: configData.region
});

const command = ffmpeg(inputVideoURL)
  .videoCodec('libx264')
  .audioCodec('aac')
  .size('854x480') // set the desired resolution (480p)
  .outputFormat('mp4')
  .addOption('-movflags', 'frag_keyframe+empty_moov')
  .on('progress',(p)=>{
    console.log(p)
  })
  .on('stderr',(err)=>console.log(err))
  .on('start', commandLine => console.log('Spawned FFmpeg with command: ' + commandLine))
  .on('end', () => console.log('Transcoding finished.'))
  .on('error', err => console.error('Error:', err))

//=>To save file into s3 using write steam.
const outputPathInS3 = 'StreamCheck/output2.mp4'
command.writeToStream(uploadFolderFileWriteStream(outputPathInS3));

/*
* This function will store the output file into the "StreamCheck" folder of s3 bucket using the write stream.
*/
function uploadFolderFileWriteStream(fileName) {
  try {
    const pass = new stream.PassThrough();

    const params = {
      Bucket: bucketNameOfS3,
      Key: fileName,
      Body: pass,
      ACL: "public-read",
      ContentType:'video/mp4' ,
    };

    const upload = s3.upload(params);

    upload.on('error', function(err) {
      console.log("Error uploading to S3:", err);
    });

    upload.send(function(err, data) {
      if(err) console.log(err);
      else console.log("Upload to S3 completed:", data);
    });

    return pass;
  } catch (err) {
    console.log("[S3 createWriteStream]", err);
  }
}

(note: if the problem only happens with some inputs, include a link to such an input file)
Expected results
I am expecting the output video should play without loading whole video into the browser. Let say output video size is of 10GB and as I hitting the object URL of that into the browser then on that case the video should start playing without loading whole 10GB data.
Observed results
If the output video is of size 10GB and I am hitting the object url of the same in the browser on that case video is not playing until it is completely loaded mean whole 10GB of video is being loaded then after video will start playing. I think there is the problem with
'moov' atom positioning.
If I am saving the output vidoe without using the writestream or pipe then the uploading that video to s3 then after playing the video using the object url then It plays without loading completely.
Checklist

[x] I have read the FAQ
[x] I tried the same with command line ffmpeg and it works correctly (hint: if the problem also happens this way, this is an ffmpeg problem and you're not reporting it to the right place)
[x] I have included full stderr/stdout output from ffmpeg

have you resolved the issue ?

https://ffmpeg.org/ffmpeg-formats.html#Fragmentation
The ‘mov’, ‘mp4’, and ‘ismv’ muxers support fragmentation. Normally, a MOV/MP4 file has all the metadata about all packets stored in one location.
This data is usually written at the end of the file, but it can be moved to the start for better playback by adding +faststart to the -movflags, or using the qt-faststart tool).
movflags action runs AFTER convertation, you can't use stream to save during converting

have you resolved the issue ?
i have same problem on pipe stream mode
i try qt-faststart tool convert and -movflags frag_keyframe+faststart but these way does not slove my problem 🥲

By saving the output file locally in the file system and then uploading it
into S3 or any cloud bucket I was able to solve this problem. You can also
tryout webm format for output video with write stream approach, bz this
format preserves the seeking capability of the video.
On Tue, 9 Jul 2024, 4:51 am kiaxseventh, @.***> wrote:

have you resolved the issue ?
i have same problem on pipe stream mode
i try qt-faststart tool convert and -movflags frag_keyframe+faststart but
these way does not slove my problem 🥲
—
Reply to this email directly, view it on GitHub
https://github.com/fluent-ffmpeg/node-fluent-ffmpeg/issues/1253#issuecomment-2215510522,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP6XL5NVE4IM4PTP5O6AVBLZLMNIJAVCNFSM6AAAAABDUGZQK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJVGUYTANJSGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


appland.appmap/milestone:open_webview

:tada: This issue has been resolved in version 0.18.0 :tada:
The release is available on:

v0.18.0
GitHub release

Your semantic-release bot :package::rocket:


1.18.2 Port

Hey, it's me again. I'm making a server with some friends (now in forge) and we would like to use the mod but it's not for the version we need it :(
I wanted to ask if you plan to make a port for 1.18.2

I'll give it a shot after making the 1.19.2 version.

Sorry it took me so long, it's been done for a while but I wanted to make it better, for some reason the model's edges in 1.18 are not smoothed out as in 1.19, wanted to fix that, couldn't. But it's good enough and done: https://modrinth.com/mod/maxwell-the-placeable-cat/version/EvWvvYSA


refactor(autoware_launch): clean up component launch

Description
clean up autoware.launch.xml regarding component launch call.

planning: https://github.com/autowarefoundation/autoware_launch/pull/185
control: https://github.com/autowarefoundation/autoware_launch/pull/186

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

planning simulator worked well


[Uniform] Uniform tables cannot be created through API

Describe the bug
Via API, TableInfoDAO.uniform_iceberg_metadata_location property cannot be set for a table, which means that creating Uniform tables are not possible.
To Reproduce
Steps to reproduce the behavior:

Send a POST http://localhost:8080/api/2.1/unity-catalog/tables request with uniform_iceberg_metadata_location property in the request body

Expected behavior
uniform_iceberg_metadata_location should be set for the table through the API.
Additional context
TableInfo does not have uniform_iceberg_metadata_location, in my opinion, this property could be passed to  TableInfoDAO from TableInfo.properties as well.

@tmater I could not find  uniform_iceberg_metadata_location CreateTable request object. Are you passing it inside property field?
I think we need to add uniform_iceberg_metadata_location field in CreateTable object and pass it till TableInfoDAO. I was thinking to make it more explicit with a field parameter instead of picking it up from property field, let me know if this make sense, I can raise PR for this issue.

@tmater I could not find uniform_iceberg_metadata_location CreateTable request object. Are you passing it inside property field?
I think we need to add uniform_iceberg_metadata_location field in CreateTable object and pass it till TableInfoDAO. I was thinking to make it more explicit with a field parameter instead of picking it up from property field, let me know if this make sense, I can raise PR for this issue.

@SubhamSinghal, TableInfoDAO object does not interact with this field in from()/toTableInfo(), I think it does not matter where I specify this field, it will be skipped.
In the Databricks UniForm documentation [1] the UniForm related configurations are passed as table properties, that is why I proposed this solution. (This is how I fixed it locally as well.)
[1] https://docs.databricks.com/en/delta/uniform.html


Fixes enableOnReadOnly bug when datepicker is of type component

Hi @gabriel, thanks for this patch! Can you provide a jsfiddle example to show the current bug?

@acrobat sure, here it is: https://jsfiddle.net/c1tc6ztq/10/

Thanks @jonssonth!

Test cases?

Hmm yes indeed I forgot to ask.. @jonssonth can you provide a test for this fix?

@acrobat  i'll fix the test.

Ok great, just create a separate pr for the missing tests!