Download videos from facebook with shortened links (fb.watch/123) not working

Checklist

[X] I'm reporting a site feature request
[X] I've verified that I'm running yt-dlp version 2021.12.27. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
Austria
Example URLs
https://fb.watch/a6Hq7Wq__5
Description
This kind of URL redirects to a supported facebook videos URL: https://www.facebook.com/165608444009109/videos/637638560246579/?extid=NS-UNK-UNK-UNK-AN_GK0T-GK1C&ref=sharing
The fb.watch part gets created when a video is shared via some other app. It's a simple redirect that is missing here.
Verbose log
$ yt-dlp -vU https://fb.watch/a6Hq7Wq__5
[debug] Command-line config: ['-vU', 'https://fb.watch/a6Hq7Wq__5']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, err utf-8, pref UTF-8
[debug] yt-dlp version 2021.12.27 [6223f67a8]
[debug] Python version 3.8.10 (CPython 64bit) - Linux-5.4.72-microsoft-standard-WSL2-x86_64-with-glibc2.29
[debug] exe versions: none
[debug] Optional libraries: Cryptodome, secretstorage, mutagen, sqlite, websockets
[debug] Proxy map: {}
Latest version: 2021.12.27, Current version: 2021.12.27
yt-dlp is up to date (2021.12.27)
[debug] [generic] Extracting URL: https://fb.watch/a6Hq7Wq__5
[generic] a6Hq7Wq__5: Requesting header
WARNING: [generic] Falling back on generic information extractor.
[generic] a6Hq7Wq__5: Downloading webpage
[generic] a6Hq7Wq__5: Extracting information
[debug] Looking for video embeds
[redirect] Following redirect to https://fb.watch/a6Hq7Wq__5?_fb_noscript=1
[debug] [generic] Extracting URL: https://fb.watch/a6Hq7Wq__5?_fb_noscript=1
[generic] a6Hq7Wq__5?_fb_noscript=1: Requesting header
WARNING: [generic] Falling back on generic information extractor.
[generic] a6Hq7Wq__5?_fb_noscript=1: Downloading webpage
[generic] a6Hq7Wq__5?_fb_noscript=1: Extracting information
[debug] Looking for video embeds
ERROR: Unsupported URL: https://fb.watch/a6Hq7Wq__5?_fb_noscript=1
Traceback (most recent call last):
  File "/home/ive/.local/lib/python3.8/site-packages/yt_dlp/YoutubeDL.py", line 1353, in wrapper
    return func(self, *args, **kwargs)
  File "/home/ive/.local/lib/python3.8/site-packages/yt_dlp/YoutubeDL.py", line 1423, in __extract_info
    ie_result = ie.extract(url)
  File "/home/ive/.local/lib/python3.8/site-packages/yt_dlp/extractor/common.py", line 599, in extract
    ie_result = self._real_extract(url)
  File "/home/ive/.local/lib/python3.8/site-packages/yt_dlp/extractor/generic.py", line 3829, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://fb.watch/a6Hq7Wq__5?_fb_noscript=1

Most likely, same underlying cause as https://github.com/yt-dlp/yt-dlp/issues/2140.
The issue can be temporarily worked around using --user-agent "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.47 Safari/537.36"
This is a regression introduced in #2023. It appears facebook redirects the URL differently for newer UAs than for the older ones.
cc @fstirlitz

Adding a Sec-Fetch-Mode: navigate header makes the redirect go through.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Mode explains it was added in Chrome 76.
Not sure about the best course of action now.

Since the older user-agents were not causing us any immediate issues, I think it's best to revert the change for the time being

Since the older user-agents were not causing us any immediate issues, I think it's best to revert the change for the time being

Most likely, same underlying cause as #2140.
The issue can be temporarily worked around using --user-agent "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.47 Safari/537.36"
This is a regression introduced in #2023. It appears facebook redirects the URL differently for newer UAs than for the older ones.
cc @fstirlitz

This is the only one working currently

idem
https://fb.watch/gcmxkm0Qeb/
:(


Redisson Tomcat Session manager slow recovery on connecting to Redis when failover happen

Slow recovery on connecting to Redis when failover happens
Scenario:

Failover on AWS MemoryDB (only 2 node MASTER+SLAVE) ~ took around 8 seconds
Our app getting RedisResponseTimeoutException
The app keep failing after whole minute even though the failover only 8 seconds

Question

Why it took so long for the app to recover when the failover is quite fast?
Is there a configuration to make the recovery time/check faster?

What we used:

Redisson tomcat session manager version 3.17.7 (first time we used) -> 3.19.1 (upgraded but still persist)
AWS Memory DB
We only use Redis for the tomcat session at this app
config that might be affecting this:

    "failedSlaveReconnectionInterval": 3000,
    "failedSlaveCheckInterval": 60000,
    "readMode": "SLAVE",
    "subscriptionMode": "SLAVE",

Typical Exception we got:
{"time": "2023-01-16 15:07:50,499", "level": "ERROR", "message": "Unable to execute (CLUSTER NODES)org.redisson.client.RedisTimeoutException: Command execution timeout for command: (CLUSTER NODES), Redis client: [addr=some-ip-here]"}

{"@timestamp":"2023-01-16T15:08:04.926Z","thread_name":"http-nio-8080-exec-10","level":"ERROR","stack_trace":"o.r.c.RedisResponseTimeoutException: Redis server response timeout (3000 ms) occured after 3 retry attempts, is non-idempotent command: false Check connection with Redis node: some-ip-here for TCP packet drops.  Try to increase nettyThreads and/or timeout settings. Command: (HMSET), params: [some-params-here"}

{"@timestamp":"2023-01-16T15:08:04.938Z","@version":"1","message":"RedisResponseTimeoutException occurred when processing request: [GET] /alive/json\nRedis server response timeout (3000 ms) occured after 3 retry attempts, is non-idempotent command: false Check connection with Redis node: some-ip-here for TCP packet drops.  Try to increase nettyThreads and/or timeout settings. Command: (HMSET)"}

you can adjust scanInterval and retryAttempts settings to survive failover.


APyFixed conversion to floating-point

Subnormal numbers do not seem be generated correctly when converting from APyFixed.  Consider for example the smallest subnormal number in double-precision $x = 2^{1-1023} \times (0 + 1 \times 2^{-52}) = 2^{-1074}$:
from apytypes import APyFixed
x = APyFixed(1, int_bits=1, frac_bits=1074)
float(x) # Becomes 1.596672247627776e+293
float(x << 51) # Becomes 0.0
float(x << 50) # Becomes inf
float(x << 52) # Works correctly, smallest normal number

The conversion also doesn't overflow to infinity, for example:
float(APyFixed(2**1024, int_bits=1100, frac_bits=0)) # Becomes 1.0

#512

How does this turn out for arrays? Are we using different conversion methods? If so, should they be the same?

The same conversion method is reused for APyFixed and APyFixedArray.

Can this be closed?

Not yet. Overflowing still has to be properly handled when converting APyFixed(Array) to float.


Create skeleton on app which allows people to easily extend it.

[ ] Write a basic entrypoint into the app, this should be a function called main.
[ ] Check for command line arguments and call the correct functions (avoid using a switch/series of if statements if possible as this is not easily extendable)
[ ] Print a help message to the console if the command line argument does not match any of the known features, it should detail all the possible arguments and any possible values those arguments need.
[ ] Help message should also be shown if the -h or --Help arguments are given
[ ] Write a unit test to check that a help message is shown.
[ ] Write a unit test and mock module to check a module can be added without changing the "main" function/file.
[ ] Change any existing code to function with the new entry point.

Hi Ray, would this be something like click?
import click

@click.command()
@click.option('--count', default=1, help='Number of greetings.')
@click.option('--name', prompt='Your name',
              help='The person to greet.')
def hello(count, name):
    """Simple program that greets NAME for a total of COUNT times."""
    for x in range(count):
        click.echo(f"Hello {name}!")

if __name__ == '__main__':
    hello()


ARROW-10265: [CI] Use smaller build when cache doesn't exist on Travis CI

Because Travis CI has "No output has been received in the last 10m0s"
limitation. If we build many modules, we will reach the limitation.

Tricky!

I hope that this fixes "C++ on ARM" failure only on master.

+1
I want to try this on master.

@kou can we use travis_wait to get around this? https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

Thanks for the suggestion.
In my experience, travis_wait may introduce other problem. I don't remember but the output may be lost on timeout.
Anyway, it's worth a try. Because this approach works https://travis-ci.org/github/apache/arrow/builds but is tricky.


OpenEBS with Rancher failed

This issue:
openebs
Can use OpenEBS with Rancher?
Rancher versions:
rancher/server: 1.6.14

Please let us know in a comment if you can still reproduce the issue, and we'll reopen it


MTC-Migration stuck in StageRestoreCreated Phase.

Moved from https://github.com/konveyor/mig-operator/issues/610
CC @ganesan-cmd
Hi Team,

We are trying to migrate the mssql application from source 3.11 to target 4.6 IBM ROKS cluster but the mig-migration got stuck in the StageRestoreCreated Phase.
Please check the below Migplan and migmigration logs and help us to fix the issue.
mig-plan-log.txt
mig-migration-log.txt

Thanks
Ganesan

Hi Team,
Please suggest the solution to fix the subjected issue ( Migration stuck in StageRestoreCreated phase ).
Thanks,
Ganesan

Hi ,
Could you please let me know when this bug can be fixed.. any approx ETA available ?

Hi @ganesan-cmd. It seems like you have some PodVolumeRestore that has not completed based on:
# Snippet from mig-migration-log.txt
    Progress:
      Restore openshift-migration/mig-migration-mssql-l65q4: InProgress
      PodVolumeRestore openshift-migration/mig-migration-mssql-l65q4-7492w: Waiting for ongoing volume restore(s) to complete

Would you be able to run this command on your target cluster?
oc get podvolumerestore mig-migration-mssql-l65q4-7492w -n openshift-migration -o yaml

Feel free to reach out to me at<EMAIL_ADDRESS>so I can help troubleshoot further, it might be useful for us to look at the output of a must-gather run against your target OCP cluster, but this can contain sensitive info so don't want you to post it to GitHub.
https://github.com/konveyor/must-gather


Unable to run tests with 2.7.7+

It looks like this commit broke my tests.
I am using framework Ts.ED that got build in inherited methods that are named like:
async $afterInit(): Promise<void> {
    // Logic
}

As $ is special character it looks like it is not detected correctly by RegEx used in this commit.

Its working on version 2.6.6


Can't delete playlists

Literally have like 20 "New Playlist" due to this hyper vigilant auto-save. HOW DO YOU DELETE THEM!!!?????

The playlist files were saved in your google drive root folder. You can go to your google drive to delete them.

# THANKYOU


Add support for long filenames on windows - fixes #716

This has been fixed in the latest edge release. See https://github.com/cloudfoundry/cli/issues/564#issuecomment-163785073


test: provide a failing test for ssrTransform error

Description
This PR is a base for a fix for #19096 containing a failing edge case (not that edgy actually!)
Feel free to use it as base for fixing the problem.
I've tried in several ways but wasn't able to find a way in the time I had (+ keeping the ; + binding strategy)
(cc @hi-ogawa)

/ecosystem-ci run


Maps: Custom GeoJson Support in Region Maps

Is your feature request related to a problem? Please describe.
Ability to provide custom GeoJson to have custom vector maps.
Describe the solution you'd like
Should be able to upload GeoJson files and use them in the regional Maps dashboard.
Describe alternatives you've considered
None
Additional context
None

Since related PRs merged to geospatial and dashboards-maps repos for 2.2.0 release, going to close this issue.


Found 0 GPUs for rendering. Using device 0.

Hi,
I have encountered some problems with MetaWorld evaluation on a headless server. I suspect that MuJoCo is failing to find a GPU for rendering. However, I have confirmed that my GPUs work properly during training. Have you encountered this issue when deploying DP3 on a remote server? Looking forward to your reply!
Here is the error message:

Found 0 GPUs for rendering. Using device 0.
Device id outside of range of available devices.
Traceback (most recent call last):
File "test.py", line 27, in
img = sim.render(12, 12, camera_name='corner2', depth=False, device_id=-1,mode='offscreen',)
File "mjsim.pyx", line 156, in mujoco_py.cymj.MjSim.render
File "mjsim.pyx", line 158, in mujoco_py.cymj.MjSim.render
File "mjrendercontext.pyx", line 46, in mujoco_py.cymj.MjRenderContext.init
File "mjrendercontext.pyx", line 114, in mujoco_py.cymj.MjRenderContext._setup_opengl_context
File "opengl_context.pyx", line 130, in mujoco_py.cymj.OffscreenOpenGLContext.init
RuntimeError: Failed to initialize OpenGL

Additionally, I referred to another issue, but it did not solve my problem.
Thank you for your help!

This seems to be a problem in metaworld/mujoco/opengl. like this?
https://github.com/openai/mujoco-py/issues/187

@ggggfff1 Have you handled this problem? I've met the same problem. Any suggestions?
Thank you.

@ggggfff1 Have you handled this problem? I've met the same problem. Any suggestions? Thank you.

Hi, I found a solution, is to use
self.viewer = mujoco_py.MjRenderContextOffscreen(self.env.sim, None, device_id=self.device_id)
self.viewer.render(self.image_size, self.image_size, self.env.sim.model.camera_name2id("corner2"))
img = self.viewer.read_pixels(self.image_size, self.image_size, depth=False)

instead of
img = self.env.sim.render(width=self.image_size, height=self.image_size, camera_name="corner2", device_id=self.device_id)
in 3D-Diffusion-Policy/diffusion_policy_3d/env/metaworld/metaworld_wrapper.py line130
but it will occur new problems. The eval speed will become slower and the result will become bad. @wut19

This seems to be a problem in metaworld/mujoco/opengl. like this? openai/mujoco-py#187

I have tried this method, but it doesn't work. @YanjieZe


ERROR: OracleCloud::Exception::HTTPNotFound: Instance<EMAIL_ADDRESS>does not exist.

Hi,
When I execute knfie oraclecloud server list I use to receive ERROR: OracleCloud::Exception::HTTPNotFound: Instance<EMAIL_ADDRESS>does not exist. All the other command seems to be working fine.
Best,
Lukasz Feldman

Thanks for this report. They must have changed something in their backend then.
We are in the process of getting another test environment, and when I can verify this I'll comment here.

I'm pretty sure this gem isn't designed for dbaas. Can you connect to the Compute URI?

Hi,
I understand. Does it mean it is not planned to integrate dbaas area?
Best,
Luke

It was out of the original scope of this knife plugin. If you read about knife: https://docs.chef.io/knife.html you'll notice that the idea of controlling a DBaaS seems out of scope.
On the other hand there is no reason why one couldn't extend this plugin to control DBaaS; though we'd need the community to write that code.

If there isn't anything else, please close this ticket :metal:


Added the Ghost Writer

The Ghost Writer should be in the list.

Thank you. That's a good idea! 😄

Love that! Thanks!


timestamp loglines

mainly so that I can see how long it was running before core dropped the gui

added with pull #49 or in the logging-timestamp branch as preview


Tests missing during execution

New Issue Checklist

[x] Updated fastlane to the latest version
NOTE: The logs below show the version as not being up to date but I did update to 2.2.0 and reran the build, experiencing the same issues. I can grab a fresh build log if needed but it took me some time to redact specific app information that my employers might not want me sharing.
[x] I have read the Contribution Guidelines

Issue Description
We use Atlassian Bamboo and have noticed that each of our builds has a different number of executed tests. During the last 6 builds, we have gotten results for 241, 265, 262, 271, 269, and 267 tests. There should have been the same number of tests for each. The last two builds (269 and 267) had identical source code - I just kicked off a new build without adding any new commits. None of these include all of the tests - there should be 306. I have only been able to consistently reproduce this problem on our build machine, though when developing, I run tests via Xcode rather than fastlane.
Complete output when running fastlane, including the stack trace and command used
Command:
bundle exec fastlane test --env development
The test lane is:
scan(scheme: "UnitTests", custom_report_file_name: "junit_unittests.xml", skip_build: true)
Bamboo build log:
simple	19-Dec-2016 17:07:15	Starting task 'test app' of type 'com.atlassian.bamboo.plugins.scripttask:task.builder.script'
command	19-Dec-2016 17:07:15	Beginning to execute external process for build 'My Build - Default Job #6 (MYBUILD-JOB1-6)'\n ... running command line: \n/bin/sh /Users/me/bamboo-agent-home/temp/MYBUILD-JOB1-6-ScriptBuildTask-239867205140649615.sh\n ... in: /Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1\n ... using extra environment variables: \nbamboo_planRepository_1_branch=mybranch\nbamboo_ServerList=\nbamboo_repository_revision_number=6b107cb05c518ec8af1a850b292508356ac4bebb\nbamboo_resultsUrl=https://bamboo.mycompany.com/browse/MYBUILD-JOB1-6\nbamboo_repository_66683133_previous_revision_number=54e7e131baf9ea7fc0bc0a20f55d5854b0bae5d2\nbamboo_capability_system_builder_xcode_iOS_9_3=iphoneos9.3\nbamboo_repository_66683133_git_branch=mybranch\nbamboo_capability_system_builder_xcode_OS_X_10_11=macosx10.11\nbamboo_capability_system_jdk_JDK_1_8_0_77=/Library/Java/JavaVirtualMachines/jdk1.8.0_77.jdk/Contents/Home/jre\nbamboo_planRepository_1_name=myapp-ios\nbamboo_build_working_directory=/Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1\nbamboo_buildKey=MYBUILD-JOB1\nbamboo_ReleaseName=None\nbamboo_DeployConfiguration=\nbamboo_shortPlanName=MyBranch\nbamboo_repository_66683133_branch_name=mybranch\nbamboo_planRepository_name=myapp-ios\nbamboo_buildNumber=6\nbamboo_DeployAppPoolName=\nbamboo_shortJobName=Default Job\nbamboo_buildResultsUrl=https://bamboo.mycompany.com/browse/MYBUILD-JOB1-6\nbamboo_repository_66683133_name=myapp-ios\nbamboo_planRepository_repositoryUrl=ssh://git@<IP_ADDRESS>:7999/at/myapp-ios.git\nbamboo_agentId=56131585\nbamboo_planName=MyTeam - myapp-ios - MyBranch\nbamboo_shortPlanKey=MYBUILD109\nbamboo_build_commandline_com_atlassian_bamboo_plugins_scripttask_task_builder_script_8=/bin/sh /Users/me/bamboo-agent-home/temp/MYBUILD-JOB1-6-ScriptBuildTask-3863247250435492791.sh\nbamboo_shortJobKey=JOB1\nbamboo_planRepository_revision=6b107cb05c518ec8af1a850b292508356ac4bebb\nbamboo_repository_previous_revision_number=54e7e131baf9ea7fc0bc0a20f55d5854b0bae5d2\nbamboo_buildTimeStamp=2016-12-19T16:31:03.959-05:00\nbamboo_BUILD_CHANGE_LOG_PATH=CHANGELOG.md\nbamboo_planRepository_previousRevision=54e7e131baf9ea7fc0bc0a20f55d5854b0bae5d2\nbamboo_build_commandline_com_atlassian_bamboo_plugins_scripttask_task_builder_script_3=/bin/sh /Users/me/bamboo-agent-home/temp/MYBUILD-JOB1-6-ScriptBuildTask-2351542363174470548.sh\nbamboo_buildResultKey=MYBUILD-JOB1-6\nbamboo_repository_git_branch=mybranch\nbamboo_repository_branch_name=mybranch\nbamboo_buildPlanName=MyTeam - myapp-ios - MyBranch - Default Job\nbamboo_planRepository_1_revision=6b107cb05c518ec8af1a850b292508356ac4bebb\nbamboo_repository_name=myapp-ios\nbamboo_BuildConfiguration=Debug\nbamboo_DeployServer=\nbamboo_RunAutomation=no\nbamboo_capability_system_builder_xcode_Simulator___iOS_10_0=iphonesimulator10.0\nbamboo_planRepository_branch=mybranch\nbamboo_capability_system_builder_xcode_iOS_10_0=iphoneos10.0\nbamboo_agentWorkingDirectory=/Users/me/bamboo-agent-home/xml-data/build-dir\nbamboo_capability_system_git_executable=/usr/bin/git\nbamboo_planRepository_1_previousRevision=54e7e131baf9ea7fc0bc0a20f55d5854b0bae5d2\nbamboo_repository_git_username=\nbamboo_repository_66683133_git_username=\nbamboo_planRepository_1_type=stash-rep\nbamboo_planRepository_branchName=mybranch\nbamboo_TestConfiguration=Debug\nbamboo_capability_system_jdk_JDK=/Library/Java/JavaVirtualMachines/jdk1.8.0_77.jdk/Contents/Home/jre\nbamboo_capability_system_builder_xcode_Simulator___iOS_9_3=iphonesimulator9.3\nbamboo_IISAppName=None\nbamboo_planRepository_type=stash-rep\nbamboo_planRepository_1_username=\nbamboo_repository_66683133_git_repositoryUrl=ssh://git@<IP_ADDRESS>:7999/at/myapp-ios.git\nbamboo_repository_git_repositoryUrl=ssh://git@<IP_ADDRESS>:7999/at/myapp-ios.git\nbamboo_capability_system_builder_node_Node_js=/usr/local/Cellar/node/6.3.1/bin/node\nbamboo_working_directory=/Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1\nbamboo_planKey=MYBUILD\nbamboo_planRepository_1_repositoryUrl=ssh://git@<IP_ADDRESS>:7999/at/myapp-ios.git\nbamboo_planRepository_username=\nbamboo_repository_66683133_revision_number=6b107cb05c518ec8af1a850b292508356ac4bebb\nbamboo_DeployAppName=\nbamboo_JUnit_TestsPath=build/reports/*.xml\nbamboo_capability_system_jdk_JDK_1_8=/Library/Java/JavaVirtualMachines/jdk1.8.0_77.jdk/Contents/Home/jre\nbamboo_planRepository_1_branchName=mybranch\n
build	19-Dec-2016 17:07:16	+---------------------------+---------+-------------------+
build	19-Dec-2016 17:07:16	|                      Used plugins                       |
build	19-Dec-2016 17:07:16	+---------------------------+---------+-------------------+
build	19-Dec-2016 17:07:16	| Plugin                    | Version | Action            |
build	19-Dec-2016 17:07:16	+---------------------------+---------+-------------------+
build	19-Dec-2016 17:07:16	| fastlane-plugin-changelog | 0.6.0   | emojify_changelog |
build	19-Dec-2016 17:07:16	|                           |         | read_changelog    |
build	19-Dec-2016 17:07:16	|                           |         | stamp_changelog   |
build	19-Dec-2016 17:07:16	|                           |         | update_changelog  |
build	19-Dec-2016 17:07:16	+---------------------------+---------+-------------------+
build	19-Dec-2016 17:07:16
build	19-Dec-2016 17:07:16	[17:07:16]: -------------------------------------------------
build	19-Dec-2016 17:07:16	[17:07:16]: --- Step: Verifying required fastlane version ---
build	19-Dec-2016 17:07:16	[17:07:16]: -------------------------------------------------
build	19-Dec-2016 17:07:16	[17:07:16]: Your fastlane version 2.1.1 matches the minimum requirement of 1.100.0  ?
build	19-Dec-2016 17:07:16	[17:07:16]: ------------------------------
build	19-Dec-2016 17:07:16	[17:07:16]: --- Step: default_platform ---
build	19-Dec-2016 17:07:16	[17:07:16]: ------------------------------
build	19-Dec-2016 17:07:16	[17:07:16]: Loading from './fastlane/.env.development'
build	19-Dec-2016 17:07:16	[17:07:16]: Driving the lane 'ios test' ?
build	19-Dec-2016 17:07:16	[17:07:16]: ------------------
build	19-Dec-2016 17:07:16	[17:07:16]: --- Step: scan ---
build	19-Dec-2016 17:07:16	[17:07:16]: ------------------
build	19-Dec-2016 17:07:16	[17:07:16]: Successfully loaded '/Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1/fastlane/Scanfile' ?
build	19-Dec-2016 17:07:16
build	19-Dec-2016 17:07:16	+----------------------+---------------------+
build	19-Dec-2016 17:07:16	| Detected Values from './fastlane/Scanfile' |
build	19-Dec-2016 17:07:16	+----------------------+---------------------+
build	19-Dec-2016 17:07:16	| output_directory     | build/reports       |
build	19-Dec-2016 17:07:16	| clean                | true                |
build	19-Dec-2016 17:07:16	| skip_slack           | true                |
build	19-Dec-2016 17:07:16	| configuration        | Release             |
build	19-Dec-2016 17:07:16	| code_coverage        | true                |
build	19-Dec-2016 17:07:16	| device               | iPad 2              |
build	19-Dec-2016 17:07:16	+----------------------+---------------------+
build	19-Dec-2016 17:07:16
build	19-Dec-2016 17:07:16	[17:07:16]: $ xcodebuild -list -project ./myapp.xcodeproj -configuration Release
build	19-Dec-2016 17:07:16	[17:07:16]: $ xcodebuild clean -showBuildSettings -scheme UnitTests -project ./myapp.xcodeproj -configuration Release
build	19-Dec-2016 17:07:17	[17:07:17]: Successfully loaded '/Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1/fastlane/Scanfile' ?
build	19-Dec-2016 17:07:17	[17:07:17]: No values defined in './fastlane/Scanfile'
build	19-Dec-2016 17:07:17	[17:07:17]: $ xcodebuild -list -project ./myapp.xcodeproj -configuration Release
build	19-Dec-2016 17:07:18	[17:07:18]: $ xcodebuild clean -showBuildSettings -scheme UnitTests -project ./myapp.xcodeproj -configuration Release
build	19-Dec-2016 17:07:19
build	19-Dec-2016 17:07:19	+-------------------------+------------------------------------------------------------------------+
build	19-Dec-2016 17:07:19	|                                      Summary for scan 2.1.1                                      |
build	19-Dec-2016 17:07:19	+-------------------------+------------------------------------------------------------------------+
build	19-Dec-2016 17:07:19	| scheme                  | UnitTests                                                              |
build	19-Dec-2016 17:07:19	| custom_report_file_name | junit_unittests.xml                                                    |
build	19-Dec-2016 17:07:19	| skip_build              | true                                                                   |
build	19-Dec-2016 17:07:19	| output_directory        | build/reports                                                          |
build	19-Dec-2016 17:07:19	| clean                   | true                                                                   |
build	19-Dec-2016 17:07:19	| skip_slack              | true                                                                   |
build	19-Dec-2016 17:07:19	| configuration           | Release                                                                |
build	19-Dec-2016 17:07:19	| code_coverage           | true                                                                   |
build	19-Dec-2016 17:07:19	| device                  | iPad 2                                                                 |
build	19-Dec-2016 17:07:19	| project                 | ./myapp.xcodeproj                                                   |
build	19-Dec-2016 17:07:19	| derived_data_path       | /Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1/De... |
build	19-Dec-2016 17:07:19	| address_sanitizer       | false                                                                  |
build	19-Dec-2016 17:07:19	| output_types            | html,junit                                                             |
build	19-Dec-2016 17:07:19	| buildlog_path           | ~/Library/Logs/scan                                                    |
build	19-Dec-2016 17:07:19	| open_report             | false                                                                  |
build	19-Dec-2016 17:07:19	| slack_only_on_failure   | false                                                                  |
build	19-Dec-2016 17:07:19	| use_clang_report_name   | false                                                                  |
build	19-Dec-2016 17:07:19	| fail_build              | true                                                                   |
build	19-Dec-2016 17:07:19	| xcode_path              | /Applications/Xcode.app                                                |
build	19-Dec-2016 17:07:19	+-------------------------+------------------------------------------------------------------------+
build	19-Dec-2016 17:07:19
build	19-Dec-2016 17:07:19	[17:07:19]: $ set -o pipefail && env NSUnbufferedIO=YES xcodebuild -scheme UnitTests -project ./myapp.xcodeproj -configuration Release -destination 'platform=iOS Simulator,id=4BFE000A-04CD-4B69-82BB-E4B61DDDB2FC' -derivedDataPath '/Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1/DerivedData/myapp' -enableCodeCoverage YES clean test | tee '/Users/me/Library/Logs/scan/MyApp-UnitTests.log' | xcpretty
build	19-Dec-2016 17:07:19	[17:07:19]: ? Loading...
build	19-Dec-2016 17:07:20	[17:07:20]: ? Cleaning myapp/MyAppModel [Release]
build	19-Dec-2016 17:07:20	[17:07:20]: ? Check Dependencies
build	19-Dec-2016 17:07:20	[17:07:20]: ? Cleaning myapp/MyAppViewModel [Release]
build	19-Dec-2016 17:07:20	[17:07:20]: ? Check Dependencies
build	19-Dec-2016 17:07:20	[17:07:20]: ? Cleaning myapp/MyAppView [Release]
build	19-Dec-2016 17:07:20	[17:07:20]: ? Check Dependencies
build	19-Dec-2016 17:07:20	[17:07:20]: ? Cleaning myapp/MyApp [Release]
build	19-Dec-2016 17:07:20	[17:07:20]: ? Check Dependencies
build	19-Dec-2016 17:07:20	[17:07:20]: ? /var/folders/ys/szvd1t697xn8vf1g4g8dwpyw0000gr/T/SchemeScriptAction-pxYJrZ: line 2: : command not found
build	19-Dec-2016 17:07:20	[17:07:20]: ? Clean Succeeded
build	19-Dec-2016 17:07:20	[17:07:20]: ? 2016-12-19 17:07:20.270 xcodebuild[14132:9247730]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
build	19-Dec-2016 17:07:20	[17:07:20]: ? /Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1/DerivedData/myapp/Logs/Test/5801C679-4BE1-4E39-9D0E-902383857DC4/Session-MyAppViewModelTests-2016-12-19_170720-CjjTwn.log
build	19-Dec-2016 17:07:20	[17:07:20]: ? 2016-12-19 17:07:20.271 xcodebuild[14132:9247678] [MT] IDETestOperationsObserverDebug: (41CBE38C-701A-42F7-AD2A-3BC328D40E58) Beginning test session MyAppViewModelTests-41CBE38C-701A-42F7-AD2A-3BC328D40E58 at 2016-12-19 17:07:20.270 with Xcode 8A218a on target <DVTiPhoneSimulator: 0x7fa3fc276500> {
build	19-Dec-2016 17:07:20	[17:07:20]: ? SimDevice: SimDevice : iPad 2 (4BFE000A-04CD-4B69-82BB-E4B61DDDB2FC) : state={ Booted } deviceType={ SimDeviceType : com.apple.CoreSimulator.SimDeviceType.iPad-2 } runtime={ SimRuntime : 9.3 (13E233) - com.apple.CoreSimulator.SimRuntime.iOS-9-3 }
build	19-Dec-2016 17:07:20	[17:07:20]: ? } (9.3 (13E233))
build	19-Dec-2016 17:07:20	[17:07:20]: ? 2016-12-19 17:07:20.299 xcodebuild[14132:9247678] [MT] IDETestOperationsObserverDebug: (E08695C2-DAE1-4B36-8584-B3CB196B71A0) Beginning test session MyAppModelTests-E08695C2-DAE1-4B36-8584-B3CB196B71A0 at 2016-12-19 17:07:20.299 with Xcode 8A218a on target <DVTiPhoneSimulator: 0x7fa3fc276500> {
build	19-Dec-2016 17:07:20	[17:07:20]: ? SimDevice: SimDevice : iPad 2 (4BFE000A-04CD-4B69-82BB-E4B61DDDB2FC) : state={ Booted } deviceType={ SimDeviceType : com.apple.CoreSimulator.SimDeviceType.iPad-2 } runtime={ SimRuntime : 9.3 (13E233) - com.apple.CoreSimulator.SimRuntime.iOS-9-3 }
build	19-Dec-2016 17:07:20	[17:07:20]: ? } (9.3 (13E233))
build	19-Dec-2016 17:07:20	[17:07:20]: ? 2016-12-19 17:07:20.300 xcodebuild[14132:9247738]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
build	19-Dec-2016 17:07:20	[17:07:20]: ? /Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1/DerivedData/myapp/Logs/Test/5801C679-4BE1-4E39-9D0E-902383857DC4/Session-MyAppModelTests-2016-12-19_170720-xKf4in.log
build	19-Dec-2016 17:07:20	[17:07:20]: ? 2016-12-19 17:07:20.322 xcodebuild[14132:9247678] [MT] IDETestOperationsObserverDebug: (6FE34F0A-558D-451D-941A-9AA0EC82DE06) Beginning test session MyAppViewTests-6FE34F0A-558D-451D-941A-9AA0EC82DE06 at 2016-12-19 17:07:20.322 with Xcode 8A218a on target <DVTiPhoneSimulator: 0x7fa3fc276500> {
build	19-Dec-2016 17:07:20	[17:07:20]: ? SimDevice: SimDevice : iPad 2 (4BFE000A-04CD-4B69-82BB-E4B61DDDB2FC) : state={ Booted } deviceType={ SimDeviceType : com.apple.CoreSimulator.SimDeviceType.iPad-2 } runtime={ SimRuntime : 9.3 (13E233) - com.apple.CoreSimulator.SimRuntime.iOS-9-3 }
build	19-Dec-2016 17:07:20	[17:07:20]: ? } (9.3 (13E233))
build	19-Dec-2016 17:07:20	[17:07:20]: ? 2016-12-19 17:07:20.322 xcodebuild[14132:9247790]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
build	19-Dec-2016 17:07:20	[17:07:20]: ? /Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1/DerivedData/myapp/Logs/Test/5801C679-4BE1-4E39-9D0E-902383857DC4/Session-MyAppViewTests-2016-12-19_170720-p3eDoc.log
build	19-Dec-2016 17:07:20	[17:07:20]: ? Building myapp/MyAppModel [Release]
build	19-Dec-2016 17:07:20	[17:07:20]: ? Check Dependencies
build	19-Dec-2016 17:07:20	[17:07:20]: ? Processing Info.plist
build	19-Dec-2016 17:07:30	[17:07:30]: ? Compiling MyAppModel_vers.c
build	19-Dec-2016 17:07:30	[17:07:30]: ? Compiling MyAppModel_vers.c
build	19-Dec-2016 17:07:30	[17:07:30]: ? Linking MyAppModel
build	19-Dec-2016 17:07:30	[17:07:30]: ? Linking MyAppModel
build	19-Dec-2016 17:07:30	[17:07:30]: Running Tests: ? Touching MyAppModel.framework
build	19-Dec-2016 17:07:30	[17:07:30]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyAppModel.framework
build	19-Dec-2016 17:07:30	[17:07:30]: ? Building myapp/MyAppModelTests [Release]
build	19-Dec-2016 17:07:30	[17:07:30]: ? Check Dependencies
build	19-Dec-2016 17:07:30	[17:07:30]: ? Processing Info.plist
build	19-Dec-2016 17:07:48	[17:07:48]: ? Compiling MyAppModelTests_vers.c
build	19-Dec-2016 17:07:48	[17:07:48]: ? Compiling MyAppModelTests_vers.c
build	19-Dec-2016 17:07:48	[17:07:48]: ? Linking MyAppModelTests
build	19-Dec-2016 17:07:48	[17:07:48]: ? Linking MyAppModelTests
build	19-Dec-2016 17:08:08	[17:08:08]: ? Copying Carthage/Build/iOS/Quick.framework
build	19-Dec-2016 17:08:08	[17:08:08]: ? Copying Carthage/Build/iOS/Haneke.framework
build	19-Dec-2016 17:08:08	[17:08:08]: ? Copying Carthage/Build/iOS/Nimble.framework
build	19-Dec-2016 17:08:08	[17:08:08]: ? Copying Carthage/Build/iOS/Alamofire.framework
build	19-Dec-2016 17:08:08	[17:08:08]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppModelTests.xctest/Frameworks/Haneke.framework
build	19-Dec-2016 17:08:08	[17:08:08]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppModelTests.xctest/Frameworks/Alamofire.framework
build	19-Dec-2016 17:08:08	[17:08:08]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppModelTests.xctest/Frameworks/Quick.framework
build	19-Dec-2016 17:08:08	[17:08:08]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppModelTests.xctest/Frameworks/Nimble.framework
build	19-Dec-2016 17:08:08	[17:08:08]: Running Tests: ? Touching MyAppModelTests.xctest
build	19-Dec-2016 17:08:08	[17:08:08]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppModelTests.xctest
build	19-Dec-2016 17:08:09	[17:08:09]: ? Building myapp/MyAppViewModel [Release]
build	19-Dec-2016 17:08:09	[17:08:09]: ? Check Dependencies
build	19-Dec-2016 17:08:09	[17:08:09]: ? Processing Info.plist
build	19-Dec-2016 17:08:09	[17:08:09]: ? Compiling MyAppViewModel_vers.c
build	19-Dec-2016 17:08:09	[17:08:09]: ? Compiling MyAppViewModel_vers.c
build	19-Dec-2016 17:08:09	[17:08:09]: ? Linking MyAppViewModel
build	19-Dec-2016 17:08:09	[17:08:09]: ? Linking MyAppViewModel
build	19-Dec-2016 17:08:09	[17:08:09]: Running Tests: ? Touching MyAppViewModel.framework
build	19-Dec-2016 17:08:09	[17:08:09]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyAppViewModel.framework
build	19-Dec-2016 17:08:09	[17:08:09]: ? Building myapp/MyAppView [Release]
build	19-Dec-2016 17:08:09	[17:08:09]: ? Check Dependencies
build	19-Dec-2016 17:08:09	[17:08:09]: ? Compiling MyAppView_vers.c
build	19-Dec-2016 17:08:09	[17:08:09]: ? Compiling MyAppView_vers.c
build	19-Dec-2016 17:08:09	[17:08:09]: ? Linking MyAppView
build	19-Dec-2016 17:08:09	[17:08:09]: ? Linking MyAppView
build	19-Dec-2016 17:08:09	[17:08:09]: ? Processing Info.plist
build	19-Dec-2016 17:08:09	[17:08:09]: Running Tests: ? Touching MyAppView.framework
build	19-Dec-2016 17:08:09	[17:08:09]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyAppView.framework
build	19-Dec-2016 17:08:09	[17:08:09]: ? Building myapp/MyApp [Release]
build	19-Dec-2016 17:08:09	[17:08:09]: ? Check Dependencies
build	19-Dec-2016 17:08:11	[17:08:11]: ? Compiling MyApp_vers.c
build	19-Dec-2016 17:08:11	[17:08:11]: ? Compiling MyApp_vers.c
build	19-Dec-2016 17:08:19	[17:08:19]: ? Linking MyApp
build	19-Dec-2016 17:08:19	[17:08:19]: ? Linking MyApp
build	19-Dec-2016 17:08:19	[17:08:19]: ? Copying Settings.plist
build	19-Dec-2016 17:08:19	[17:08:19]: ? Processing Info.plist
build	19-Dec-2016 17:08:20	[17:08:20]: ? Copying DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyAppModel.framework
build	19-Dec-2016 17:08:20	[17:08:20]: ? Copying DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyAppViewModel.framework
build	19-Dec-2016 17:08:20	[17:08:20]: ? Copying DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyAppView.framework
build	19-Dec-2016 17:08:20	[17:08:20]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/Frameworks/MyAppViewModel.framework
build	19-Dec-2016 17:08:20	[17:08:20]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/Frameworks/MyAppModel.framework
build	19-Dec-2016 17:08:20	[17:08:20]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/Frameworks/MyAppView.framework
build	19-Dec-2016 17:08:20	[17:08:20]: ? Running script 'Copy Carthage Frameworks'
build	19-Dec-2016 17:08:29	[17:08:29]: ? Running script 'SwiftLint'
build	19-Dec-2016 17:08:34	[17:08:34]: ? Running script 'Run fabric crashlytics'
build	19-Dec-2016 17:08:35	[17:08:35]: Running Tests: ? Touching MyApp.app
build	19-Dec-2016 17:08:35	[17:08:35]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app
build	19-Dec-2016 17:08:36	[17:08:36]: ? Building myapp/MyAppViewModelTests [Release]
build	19-Dec-2016 17:08:36	[17:08:36]: ? Check Dependencies
build	19-Dec-2016 17:08:36	[17:08:36]: ? Processing Info.plist
build	19-Dec-2016 17:08:36	[17:08:36]: ? Compiling MyAppViewModelTests_vers.c
build	19-Dec-2016 17:08:36	[17:08:36]: ? Compiling MyAppViewModelTests_vers.c
build	19-Dec-2016 17:08:36	[17:08:36]: ? Linking MyAppViewModelTests
build	19-Dec-2016 17:08:36	[17:08:36]: ? Linking MyAppViewModelTests
build	19-Dec-2016 17:08:36	[17:08:36]: ? Copying Carthage/Build/iOS/Alamofire.framework
build	19-Dec-2016 17:08:36	[17:08:36]: ? Copying Carthage/Build/iOS/Quick.framework
build	19-Dec-2016 17:08:36	[17:08:36]: ? Copying Carthage/Build/iOS/Nimble.framework
build	19-Dec-2016 17:08:36	[17:08:36]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppViewModelTests.xctest/Frameworks/Alamofire.framework
build	19-Dec-2016 17:08:36	[17:08:36]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppViewModelTests.xctest/Frameworks/Quick.framework
build	19-Dec-2016 17:08:36	[17:08:36]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppViewModelTests.xctest/Frameworks/Nimble.framework
build	19-Dec-2016 17:08:36	[17:08:36]: ? /var/folders/ys/szvd1t697xn8vf1g4g8dwpyw0000gr/T/SchemeScriptAction-oHFvuL: line 2: : command not found
build	19-Dec-2016 17:08:36	[17:08:36]: Running Tests: ? Touching MyAppViewModelTests.xctest
build	19-Dec-2016 17:08:36	[17:08:36]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppViewModelTests.xctest
build	19-Dec-2016 17:08:36	[17:08:36]: ? Building myapp/MyAppViewTests [Release]
build	19-Dec-2016 17:08:36	[17:08:36]: ? Check Dependencies
build	19-Dec-2016 17:08:36	[17:08:36]: ? Compiling MyAppViewTests_vers.c
build	19-Dec-2016 17:08:36	[17:08:36]: ? Compiling MyAppViewTests_vers.c
build	19-Dec-2016 17:08:36	[17:08:36]: ? Linking MyAppViewTests
build	19-Dec-2016 17:08:36	[17:08:36]: ? Linking MyAppViewTests
build	19-Dec-2016 17:08:36	[17:08:36]: ? Processing Info.plist
build	19-Dec-2016 17:08:36	[17:08:36]: ? Copying Carthage/Build/iOS/Quick.framework
build	19-Dec-2016 17:08:36	[17:08:36]: ? Copying Carthage/Build/iOS/Nimble.framework
build	19-Dec-2016 17:08:36	[17:08:36]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppViewTests.xctest/Frameworks/Nimble.framework
build	19-Dec-2016 17:08:36	[17:08:36]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppViewTests.xctest/Frameworks/Quick.framework
build	19-Dec-2016 17:08:36	[17:08:36]: Running Tests: ? Touching MyAppViewTests.xctest
build	19-Dec-2016 17:08:36	[17:08:36]: ? Signing DerivedData/myapp/Build/Intermediates/CodeCoverage/Products/Release-iphonesimulator/MyApp.app/PlugIns/MyAppViewTests.xctest
build	19-Dec-2016 17:08:40	[17:08:40]: ? All tests
build	19-Dec-2016 17:08:40	[17:08:40]: ? Quick.framework
build	19-Dec-2016 17:08:40	[17:08:40]: ? Test Suite MyAppViewModelTests.xctest started
build	19-Dec-2016 17:08:40	[17:08:40]: ? MyPageViewModelSpec
build	19-Dec-2016 17:08:40	[17:08:40]: ? ? active_instances_returned_from_service_on_construction (0.039 seconds)
...
build	19-Dec-2016 17:08:41	[17:08:41]: ? 	 Executed 70 tests, with 0 failures (0 unexpected) in 0.156 (0.211) seconds
build	19-Dec-2016 17:08:41	[17:08:41]: ?
build	19-Dec-2016 17:08:44	[17:08:44]: ? All tests
build	19-Dec-2016 17:08:44	[17:08:44]: ? Quick.framework
build	19-Dec-2016 17:08:44	[17:08:44]: ? Test Suite MyAppModelTests.xctest started
build	19-Dec-2016 17:08:44	[17:08:44]: ? MyPageServiceSpec
build	19-Dec-2016 17:08:44	[17:08:44]: ? ? service_specs__active_instances_are_correctly_returned (0.007 seconds)
...
build	19-Dec-2016 17:08:46	[17:08:46]: ? 	 Executed 144 tests, with 0 failures (0 unexpected) in 1.288 (1.401) seconds
build	19-Dec-2016 17:08:46	[17:08:46]: ?
build	19-Dec-2016 17:08:49	[17:08:49]: ? All tests
build	19-Dec-2016 17:08:49	[17:08:49]: ? Test Suite MyAppViewTests.xctest started
build	19-Dec-2016 17:08:50	[17:08:50]: ? HtmlLabelSpec
build	19-Dec-2016 17:08:50	[17:08:50]: ? ? HtmlLabel__stringFrom_html__works_with_special_characters (0.005 seconds)
...
build	19-Dec-2016 17:08:50	[17:08:50]: ? 	 Executed 92 tests, with 0 failures (0 unexpected) in 0.457 (0.538) seconds
build	19-Dec-2016 17:08:50	[17:08:50]: ?
build	19-Dec-2016 17:08:50	[17:08:50]: ? Quick.framework
build	19-Dec-2016 17:08:51	[17:08:51]: ? Test Succeeded
build	19-Dec-2016 17:08:52	+--------------------+-----+
build	19-Dec-2016 17:08:52	|       Test Results       |
build	19-Dec-2016 17:08:52	+--------------------+-----+
build	19-Dec-2016 17:08:52	| Number of tests    | 269 |
build	19-Dec-2016 17:08:52	| Number of failures | 0   |
build	19-Dec-2016 17:08:52	+--------------------+-----+
build	19-Dec-2016 17:08:52
build	19-Dec-2016 17:08:53	[17:08:53]: Successfully generated report at '/Users/me/bamboo-agent-home/xml-data/build-dir/MYBUILD-JOB1/build/reports/junit_unittests.xml'
build	19-Dec-2016 17:08:53
build	19-Dec-2016 17:08:53	+------+-------------------------------------+-------------+
build	19-Dec-2016 17:08:53	|                     fastlane summary                     |
build	19-Dec-2016 17:08:53	+------+-------------------------------------+-------------+
build	19-Dec-2016 17:08:53	| Step | Action                              | Time (in s) |
build	19-Dec-2016 17:08:53	+------+-------------------------------------+-------------+
build	19-Dec-2016 17:08:53	| 1    | Verifying required fastlane version | 0           |
build	19-Dec-2016 17:08:53	| 2    | default_platform                    | 0           |
build	19-Dec-2016 17:08:53	| 3    | scan                                | 96          |
build	19-Dec-2016 17:08:53	+------+-------------------------------------+-------------+
build	19-Dec-2016 17:08:53
build	19-Dec-2016 17:08:53	[17:08:53]: fastlane.tools finished successfully ?
simple	19-Dec-2016 17:08:54	Finished task 'test app' with result: Success
command	19-Dec-2016 17:08:54	Substituting variable: ${bamboo.BUILD_CHANGE_LOG_PATH} with CHANGELOG.md
command	19-Dec-2016 17:08:54	Substituting variable: ${bamboo.JUnit_TestsPath} with build/reports/*.xml

Environment
Other software:

Quick: 0.10.0
Nimble: 5.1.1
Xcode Version: 8.0 (8A218a)
xcode-select: 2343
Swift Version: Xcode Default
Carthage: 0.17.2
iOS 9.3, iPad 2 simulator

✅ fastlane environment ✅
Stack

Key
Value

OS
10.11.6

Ruby
2.3.1

Bundler?
true

Git
git version 2.8.4 (Apple Git-73)

Installation Source
~/.gem/ruby/2.3.0/bin/fastlane

Host
Mac OS X 10.11.6 (15G31)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.3.1/lib

OpenSSL Version
OpenSSL 1.0.2h  3 May 2016

Is contained
false

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

Xcode Version
8.0

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

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.100.0"

default_platform :ios

platform :ios do
  before_all do
  end

  desc "Installs FixCode which disables the \"Fix Issue\" button in Xcode"
  lane :xcode do
    install_xcode_plugin(
      url: "https://github.com/fastlane/FixCode/releases/download/0.5.0/FixCode.xcplugin.zip"
    )
  end

  desc "Runs unit tests"
  lane :test do

    scan(scheme: "UnitTests", custom_report_file_name: "junit_unittests.xml", skip_build: true)		#uses defaults from GymFile

  end

  desc "Run Integration tests"
  lane :integration do

      scan(scheme: "UITests", custom_report_file_name: "junit_uitests.xml", skip_build: true)

  end

  private_lane :build_dependencies do

    carthage(command: "bootstrap", # One of: build, bootstrap, update, archive. (default: bootstrap)
      verbose: false,
  		platform: "iOS",
  		configuration: "Release")

  end

  lane :build_ci do |options|

    branch = options[:branch] || git_branch

    if branch == "master"
      build_ci_beta(changelog: options[:changelog], build_number: options[:build_number])
    else
      build_ci_development(build_number: options[:build_number])
    end

  end

  desc "Build application"
  lane :build do |options|

    pre_build

    match(type: "development", app_identifier: ENV["APP_IDENTIFIER"])

    gym 		#uses defaults from GymFile

  end

  desc "pre build steps"
  lane :pre_build do
  	build_dependencies
    swiftlint
  end

  desc "for running in CI environment"
  lane :build_ci_development do |options|

		build_number = options[:build_number] || get_build_number
    increment_build_number(
        build_number: build_number
    )

    match(type: "development", app_identifier: ENV["APP_IDENTIFIER"])

    gym 		#uses defaults from GymFile

  end

  desc "for running in CI environments"
  lane :build_ci_beta do |options|

    build_number = options[:build_number] || get_build_number
    increment_build_number(
        build_number: build_number
    )
    set_info_plist_value( # Change the Display Name of your app
  		path: "MyApp/Info.plist",
  		key: "CFBundleDisplayName",
  		value: ENV["BUNDLE_DISPLAY_NAME"]
		)
		set_info_plist_value( # Change the App Identifier of your app
  		path: "MyApp/Info.plist",
  		key: "CFBundleIdentifier",
  		value: ENV["APP_IDENTIFIER"]
		)
		set_info_plist_value(
		  path: "MyApp/Settings.plist",
			key: "MySvcUrl",
			value: ENV["MY_SERVICE_URL"]
		)

    #need to run match and gym
    match(type: "appstore", app_identifier: ENV["APP_IDENTIFIER"])
    gym(output_name: ENV["IPA_FILE"]) 		#uses defaults from GymFile

  end

  def write_changelog(path)
    out_file = File.new(path, "w")
    changelog = change_log_since_last_tag
    out_file.puts(changelog)
    out_file.close
  end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do |options|

    changelog = "Update for MyApp iOS"

    if options[:changelog] && File.file?(options[:changelog])
      file = File.open(options[:changelog])
      changelog = file.read
      file.close
    end

    pilot(skip_submission:true, skip_waiting_for_build_processing:true, changelog: changelog, ipa: ENV["IPA_FILE"], app_identifier: ENV["APP_IDENTIFIER"])

  end

end

def change_log_since_last_tag
    # http://git-scm.com/docs/pretty-formats
    # <short hash> <commit title>
    return changelog_from_git_commits(pretty: '%h %s')
end

def version_string(version_number, build_number)
    "#{version_number} (#{build_number})"
end

def tag_name(build_type, version_number, build_number)
    "#{build_type}/#{version_number}/#{build_number}"
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`
apple_id<EMAIL_ADDRESS># Your Apple email address
team_id "REDACTED"  # Developer Portal Team ID

#use different bundle identifiers per lane
app_identifier "com.mycompany.myapp-dev" # The bundle identifier of your app

for_lane 'beta' do
	app_identifier "com.mycompany.myapp-beta" # The bundle identifier of your app
end

# 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.2.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-changelog
0.6.0
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.0.0

executable-hooks
1.3.2

bundler-unload
1.0.2

rubygems-bundler
1.4.4

bundler
1.13.6

io-console
0.4.5

i18n
0.7.0

json
1.8.3

minitest
5.10.1

thread_safe
0.3.5

tzinfo
1.2.2

activesupport
<IP_ADDRESS>

public_suffix
2.0.4

addressable
2.5.0

awesome_print
1.7.0

babosa
1.0.2

claide
0.9.1

fuzzy_match
2.0.4

nap
1.1.0

cocoapods-core
0.39.0

cocoapods-downloader
0.9.3

cocoapods-plugins
0.4.2

cocoapods-search
0.1.0

cocoapods-stats
0.6.2

netrc
0.7.8

cocoapods-trunk
0.6.4

cocoapods-try
0.5.1

colored
1.2

escape
0.0.4

molinillo
0.4.5

xcodeproj
0.28.2

cocoapods
0.39.0

highline
1.7.8

commander
4.4.2

diff-lcs
1.2.5

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

dotenv
2.1.1

excon
0.54.0

multipart-post
2.0.0

faraday
0.10.0

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.10.1

fastimage
2.0.1

gh_inspector
1.0.2

jwt
1.5.6

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

hurley
0.2

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.0.15

representable
2.3.0

retriable
2.1.0

google-api-client
0.9.20

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.2.0

rubyzip
1.2.0

security
0.1.3

slack-notifier
1.5.1

terminal-notifier
1.7.1

unicode-display_width
1.1.2

terminal-table
1.7.3

word_wrap
1.0.0

rouge
1.11.1

xcpretty
0.2.4

xcpretty-travis-formatter
0.0.4

fastlane-plugin-changelog
0.6.0

find_a_port
1.0.1

rack
2.0.1

rack-test
0.6.3

randexp
0.1.7

rspec-support
3.5.0

rspec-core
3.5.4

rspec-expectations
3.5.0

rspec-mocks
3.5.0

rspec
3.5.0

tins
1.13.0

term-ansicolor
1.4.0

thor
0.19.4

pact-support
0.6.0

webrick
1.3.1

pact-mock_service
0.12.0

generated on: 2016-12-22

I don't believe the issue is related to code signing.

I'm having the same issue. Only the first two test files alphabetically seem to get run before it suddenly completes. Most of our tests are with Quick but there's one file that's just an XCTestCase and that one doesn't run either.

Fastlane 2.7.0
Quick 1.0.0
Nimble 5.1.1
Swift 3.0.1

[01:10:35]: ▸ All tests
[01:10:35]: ▸ Quick.framework
[01:10:35]: ▸ Test Suite FIXDTests.xctest started
[01:10:35]: ▸ ApiModelSpec
[01:10:35]: ▸ ✓ ApiError__should_be_deserializable_from_JSON (0.007 seconds)
[01:10:35]: ▸ ✓ ApiPaginationInfo__should_be_deserializable_from_JSON (0.003 seconds)
[01:10:35]: ▸ ✓ ApiPagedCollection__should_be_creatable_from_first_load (0.003 seconds)
[01:10:35]: ▸ ✓ ApiPagedCollection__should_accept_subsequent_loads (0.003 seconds)
[01:10:35]: ▸ ✓ ApiPagedCollection__should_load_empty_pages_without_effect (0.003 seconds)
[01:10:35]: ▸ ✓ Date_Converter__should_convert_valid_dates (0.007 seconds)
[01:10:35]: ▸ ✓ Date_Converter__should_not_convert_invalid_strings (0.004 seconds)
[01:10:35]: ▸ ✓ Date_Converter__should_not_convert_other_objects (0.004 seconds)
[01:10:35]: ▸ ✓ ApiQuery__should_generate_URLRequests (0.007 seconds)
[01:10:35]: ▸ ✓ ApiRequest__should_generate_show_requests (0.005 seconds)
[01:10:35]: ▸ ✓ ApiRequest__should_generate_create_requests (0.007 seconds)
[01:10:35]: ▸ ✓ ApiRequest__should_generate_update_requests (0.004 seconds)
[01:10:35]: ▸ ✓ ApiRequest__shouldgenerate_delete_requests (0.004 seconds)
[01:10:35]: ▸ ApiSpec
[01:10:35]: ▸ ✓ Api__should_auto_deserialize_requests_for_ApiRequestable_models (0.008 seconds)
[01:10:35]: ▸ ✓ Api__should_auto_deserialize_queries_for_ApiRequestable_models (0.005 seconds)
[01:10:35]: ▸ ✓ Api__should_auto_deserialize_ApiErrors (0.005 seconds)
[01:10:36]: ▸ ✓ Api__Auth__setAuth_and_clearAuth_should_update_headers (0.007 seconds)
[01:10:36]: ▸ ✓ Api__URL_generation__should_correctly_generate_urls_without_query_params (0.005 seconds)
[01:10:36]: ▸ ✓ Api__URL_generation__should_correctly_generate_query_requests_with_query_params (0.004 seconds)
[01:10:36]: ▸ ✓ Api__URL_generation__should_correctly_generate_query_requests_with_encoded_query_params (0.005 seconds)
[01:10:36]: ▸ ✓ Api__URL_generation__should_correctly_generate_query_requests_with_blank_query_params (0.006 seconds)
[01:10:36]: ▸ ✓ Api__URL_generation__should_correctly_generate_query_requests_with_empty_query_params (0.008 seconds)
[01:10:36]: ▸ ✓ Api__URL_generation__should_allow_overriding_the_relative_path_with_a_leading__ (0.003 seconds)
[01:10:36]: ▸ AppSpec
[01:10:41]: ▸ Test Succeeded

We have both Quick and XCTestCase as well. I haven't noticed that any XCTestCases are missing but that doesn't mean they are. The interesting bit of this log is the following, which I should have pointed out...
build	19-Dec-2016 17:08:41	[17:08:41]: ? �[35m�[32;1m	 Executed 70 tests, with 0 failures (0 unexpected) in 0.156 (0.211) seconds�[0m
...
build	19-Dec-2016 17:08:46	[17:08:46]: ? �[35m�[32;1m	 Executed 144 tests, with 0 failures (0 unexpected) in 1.288 (1.401) seconds�[0m
...
build	19-Dec-2016 17:08:50	[17:08:50]: ? �[35m�[32;1m	 Executed 92 tests, with 0 failures (0 unexpected) in 0.457 (0.538) seconds�[0m
build	19-Dec-2016 17:08:52	+--------------------+-----+
build	19-Dec-2016 17:08:52	|       Test Results       |
build	19-Dec-2016 17:08:52	+--------------------+-----+
build	19-Dec-2016 17:08:52	| Number of tests    | 269 |

70+144+92 = 306, which is the number of tests I have. The number of tests listed in test results is only 269. Are you seeing the same sort of thing?

No, mine reports the number of tests as the 23 tests that it ran. These may be separate issues

It turns out my issue is related to a certain file/test. When I commented it out, it completed the rest of the suite. I will investigate and may open a separate issue

This is still a major problem for us.

I did notice that the tests that aren't counted are not showing in the build log. It seems to coincide with when some logging interrupts the test. I think maybe xcpretty is unable to parse those test results that are interrupted. Some piece still knows the number of tests that executed but that number doesn't make it to the results.


Tune Rule

Background
Tuning changes to our slowest rule
Changes
Filter earlier, explicitly define actions
Testing
Unit Testing

@lindsey-w  this is the one I was talking about with you
Still planning the new string set operation, but want to do that internally for a bit first. Figured this was worth publishing before


Jw/add number of loaders

What are the relevant tickets?

Description (What does it do?)

Screenshots (if appropriate):

[ ] Desktop screenshots
[ ] Mobile width screenshots

How can this be tested?

Additional Context

@pdpinch I commented here: https://github.com/mitodl/hq/issues/3663#issuecomment-2009703781 Pretty sure this work is no longer needed after the most recent deploy.


Mention that running both cargo watch and a language server might be bad

Actually, I'm not entirely sure if that's the case with RA. But as of my last experience with RLS it definitely was! My understanding:
Builds (and similar: checks, tests (because they have to build), etc) take a lock on the project, so if two builds try to run at the same time, they'll contend. And locks are released and taken "between" steps (not super sure how that goes in RLS, but with e.g. cargo watch -x check -x test the lock will be released briefly between check and test). And language servers want to run a whole lot more often. Kinda creates a mess: cargo watch feels slow, RLS feels slow, because they're often fighting for the lock.
Dunno how to word that in a nice simple friendly way for this guide, but it may be helpful to know given they're both mentioned.

@passcod that's a fair point! -- my understanding is however that currently there's not much that can be done here, and active steps are being taken to solve this (by making rust-analyzer and rustc use the same infrastructure). Personally I do run both together all the time, and while not ideal, it beats trying to figure out how to shut down the lang server when doing a local check.
I think what you're saying is not wrong. But I'm also not sure how to share it since there's not really much actionable that can be done here. I'll think about this for a bit; but thanks either way!

That's fair :+1:

I've been thinking about this a bit more, and I'm still unsure what we could do to improve here. I think waiting for the tooling to catch up is probably right.
Going to go ahead and close this. Thanks again!


Fix version typo in CVE-2024-35184

I noticed the MITRE data had:
      "affected": [
        {
          "vendor": "paperless-ngx",
          "product": "paperless-ngx",
          "versions": [
            {
              "status": "affected",
              "version": ">= 2.5.0, < 2.8.6"
            }
          ]
        }
      ],

But the CISA enrichment had:
            "versions": [
              {
                "status": "affected",
                "version": "2.50",
                "lessThan": "2.8.6",
                "versionType": "custom"
              }
            ],

Which looks to me to be a typo of 2.5.0 -> 2.50. Simple enough to fix.

@j-baines thank you for the report. I've asked the analysts to take a look at this and update on our end as appropriate. I'm going to accept this merge, but be aware that the file will get updated again during the next data update later today with our changes from upstream.


Please add ZetaIpc to misc section

https://github.com/UweKeim/ZetaIpc

Read https://github.com/quozd/awesome-dotnet/blob/master/CONTRIBUTING.md

ok, will do it through pr


Angular change detection and ix-tabs

What happened?
It looks like the change detection mechanizm is triggered by the ix-tabs component continuously.
My comp.html:
<ix-tabs></ix-tabs>

My comp.ts:
@Component({ ... })
export class Component {
  isTabActive() {
    console.log(1);
    return true;
  }
}
It starts writing 1 to the console continuously. Could you check it?
What type of frontend frameware are you seeing the problem on?
Angular
Which version of iX do you use?
v2.0.3
Code to produce this issue.
<ix-tabs></ix-tabs>

You should not use function expression inside the angular template (https://medium.com/showpad-engineering/why-you-should-never-use-function-calls-in-angular-template-expressions-e1a50f9c0496).
tl;dr:
Because Angular cannot predict whether the return value of fullName() has changed, it needs to execute the function every time change detection runs.
Our angular wrappers uses the onPush mode https://github.com/siemens/ix/blob/main/packages/angular/src/components.ts#L1951

Thank you, that article is very useful. But I'm still a little bit puzzled.
I removed the <ix-tabs> and after that I only see 30 logs in the console. But when I turn the <ix-tabs> on then the logs flow is endless.
So again: without ix-tabs it is triggered so many times, but it is okay. Angular is strong and optimized framework and we can also fine-tune it (e.g. using models instead of functions - although in some cases we simple can't...). BUT when we use ix-tabs the triggering is endless.
The updated html:
<button (click)="showTab = true;">Toggle: {{showTab}}</button>
<ix-tabs *ngIf="showTab"></ix-tabs>

So it is crystal clear your component does something which triggers the change cycle.
As for the onPush: this applies to the component where it is set, but it can trigger the parent as I tested it. If we set the changeDetection to onPush in our components as well, it will solve the problem but in some cases it is just not working for us - the default behavior is needed...
If you have a special action which is continuously create events, you can use ngZone:
https://angular.io/api/core/NgZone

Okay will have a look on it, but in your updated example you are using a function expression again in the angular template.

Found the problem the component us the arequestAnimationFrame which leets in more change detections. Good call!
https://github.com/siemens/ix/blob/main/packages/core/src/components/tabs/tabs.tsx#L247

beta version for testing -> https://github.com/siemens/ix/releases/tag/v2.1.0-beta.0

I couldn't repro the problem above with this version, so it looks fine for me, thank you :-)


Thoughts on enforcing "Insert imports for nested classes"?

IntelliJ has a preference in "Code Style → Kotlin → Imports" called "Insert imports for nested classes."
This changed the default import behavior from this:
import android.support.v7.widget.RecyclerView

class VerticalOffsetItemDecoration() : RecyclerView.ItemDecoration() {
    // ...
}

To this:
import android.support.v7.widget.RecyclerView
import android.support.v7.widget.RecyclerView.ItemDecoration

class VerticalOffsetItemDecoration() : ItemDecoration() {
    // ...
}

The default behavior optimizes for fewer imports. If you've already imported RecyclerView a new import will not be added.
However, the second optimizes for horizontal line length. It will also add an explicit import for ItemDecoration.
I personally prefer and recommend the second option, but I'm curious what others think.

I'd say it depends. Sometimes you want to make connection between the nested and containing classes explicit (e.g. Map.Entry) (especially considering that inner classes tend to have more generic names), other times it doesn't matter. I think it's up to developer to decide, not ktlint.


build: Add support for Windows

Maybe I should add an optional GitHub Action which triggers a Windows build.

The fix for warnings is not correct, because the problem is more so that the toolchain is not getting picked up correctly on Windows.


Add example of configuring memory for Checkstyle workers

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


doc: fix generic auth doc examples to not use async or throw

Description
Fixes the documentation of @envelop/generic-auth to reflect the fact that validateUser can't return a promise and that validation errors should preferably be returned instead of thrown.
Fixes #1753
Type of change

[x] Documentation change

Checklist:

[x] I have followed the CONTRIBUTING doc and the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@n1ru4l The CI is failing with the algolia check. I don't know what it is but is seems like a misconfiguration.


[DOCFIX] Update Configuring-Alluxio-with-OBS.md

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18649/
Test PASSed.

Merged build finished. Test PASSed.


Change ceph_stable_repo to use download.ceph.com

(cherry picked from commit 426d168f8fc80bf04151023007aa055a1cab1710)
Connects https://github.com/rcbops/u-suk-dev/issues/1000

recheck_ceph

👍 LGTM. Seems to be a straightforward backport.


Add secure secret management

Ala Azure Key Vault or Hashicorp Vault

Design should address supporting multiple approaches.  Specifically:

Azure KeyVault
Hashicorp Vault

Docs should contain information on how secrets are accessed within the vault.

@jmspring
This can be useful documentation for the key vault flex volume implementation,
https://github.com/shwetams/containers-rest-cosmos-aks-java/blob/master/infrastructure/AKSconfiguration.md
with complimentary helm chart to enable the ENV vars from the volume mount
https://github.com/shwetams/containers-rest-cosmos-aks-java/blob/b3925f27415346b470cce064ae49613d1ecb3f60/gitops/charts/chakraview/templates/deployment.yaml#L31
https://github.com/shwetams/containers-rest-cosmos-aks-java/blob/b3925f27415346b470cce064ae49613d1ecb3f60/gitops/charts/chakraview/templates/deployment.yaml#L42-L53


error on parsing and reading feed

Hi and thanks for commafeed, it seems great so far.
I've been getting this error trying to pull some feeds, any ideas on what's going on?
Error while loading this feed : Unable to refresh feed https://hips.seas.harvard.edu/blog/feed/ : Could not parse feed from http://lips.cs.princeton.edu/ : Invalid XML: Error on line 15: The entity name must immediately follow the '&' in the entity reference.

Also the parsing is really bad on some occasions, for instance compare this parsed blog post shown in commafeed:
<- Confounding Probabilistic vs. Causal inference This post revisits the confounding phenomenon under the angle of probabilistic reasoning with conditional probabilities and Bayes' theorem. This analysis reveals what sets probabilistic and causal inference apart. It also shows how probabiistic models and causal models formulate assumptions of a fundamentally different nature.$Y$$X$$Z$$Z$$Y$$(Z,X)$$P(Z,X,Y)$$P(Y|Z,X)$$Z$$X$$P(Y|Z,X)$$(Z,X)$$Z$\begin{equation} \label{eq:xyz} P(Z,X,Y) =…

with the original feed here
There's an error parsing and correctly displaying latex from blog posts with mathjax rendering.

Your first URL is no longer a valid feed, it seems it is now https://lips.cs.princeton.edu/feed/

Thanks a lot I noticed a bit late, what about the latex-mathjax rendering are there any plans to incorporate that?

The parsing is correct. This is the text found in https://leon.bottou.org/feed.php
There's no plan to execute JavaScript from feeds for obvious seurity reasons.


bump deps

cc @jarofghosts

👍

Coverage increased (+0.08%) to 85.417% when pulling 7e68d52499da28db685d6e9e6243e1ccd49e87b8 on bump-deps into 97381fd49613c6610ba3ef3ea0634f184275e407 on master.


The adjustment value of the slide bar of the light sensor is abnormal.

The adjustment value of the slide bar of the light sensor is abnormal.
The amount of change between the front and back is too different.

The slide bar changes a range within from 1 to 0xfffe. And the value is converted to an exponential of 10 and represents to 1 through 3576000. The formula used follows from the Matter specification.

Even if MaxMeasuredValue is set, SmartThings set the max value to 100000 on its UI.
I will change Max value on ioter like SmartThings


Build production

Hi !
I run "npm run build" and i get main.bundle.js and main.map in dist folder. I thought I would have an index.html, ...
How can I put my project in production ?
( I'm beginner in angular2 and also npm )

Just copy your index.html in dist folder and it should work. It might through error for base url in head tag.
I know it is not ideal solution but it should work.
Other way to handle this is to write a copy command in package.json 'script' object.

Hey guys just a heads up, my PR here: https://github.com/angular/angular2-seed/pull/158 fixes this issue, and also updates Angular to a newer version as this repository is just a tad behind. Hopefully that can get merged in soon :)


Make 'make check' more consistent across projects

Makefile:
build, re-build => build-test-image, rebuild-test-image
Add check-in-container target.
Containerfile:
install findutils, make, python3-flexmock, python3-pytest
README.md:
build, re-build => build-test-image, rebuild-test-image
Add description of 'make check' & 'make check-in-container'
Add CONTRIBUTING.md stub with pointer back to README.md.
Signed-off-by: Ben Crocker<EMAIL_ADDRESS>

@bcrocker15 I've amended your commit with the fixes for my last comments, and marked this to be merged.


[question] best way for external log file.

Hi all,
I know it might sound silly. But I do need some help regarding how to log users "requests" into a file with an async mode.
Could you please spend a moment to describe the process for me?

Hey @tobenary 👋🏻 this is definitely not a silly question. Off the top of my head, I don't have an answer for asynchronous logging but let me look into it for you!

Hey @tobenary 👋🏻 this is definitely not a silly question. Off the top of my head, I don't have an answer for asynchronous logging but let me look into it for you!

@tobenary You may already know a lot of this content, but I'll include it anyways to share my own discovery and learning process.
TL;Dr;
The main takeaway is that we'd recommend using the built-in logger module and setting it to write to a file. This aligns with the official asyncio documentation's suggest and would work reliably with Bolt. When asyncio supports async logging, we'd be super happy to add support for it as well!
Below are a few of my learnings and research into aiologger:
1. Writing logs to a file:
Bolt uses Python's standard logging module, so you can write logs to a file using Python's standard approach:
import logging
logging.basicConfig(filename='example.log', encoding='utf-8', level=logging.DEBUG)

2. Python's logger is sync-only:
Unfortunately, Python's logger is I/O Blocking. Even when using Bolt's Async methods based on asyncio, the logger will block with sync calls. This of course could be quite slow if you're writing to a file.
Interestingly, the official asyncio documentation suggests using the built-in Python sync logger module.
3. Logging with middleware:
You can use Bolt's middleware to log user requests. This would allow you to use a library such as aiologger to asynchronous log the requests.
However, this middleware will not capture Bolt's internal logs which will still use the built-in Python logger.
4. Using aiologger inside Bolt:
Bolt allows you to pass in your own Logger instance. Since aiologger uses the standard logging syntax, you could pass it into Bolt.
import logging
import os
from aiologger import Logger
from slack_bolt.async_app import AsyncApp

# Workaround: must use log level > INFO for now
logger = Logger.with_default_handlers(level=logging.WARNING)

# Initializes your app with your bot token and signing secret
app = AsyncApp(
    token=os.environ.get("SLACK_BOT_TOKEN"),
    signing_secret=os.environ.get("SLACK_SIGNING_SECRET"),
    logger=logger,
)

However, I've came across some limitations:

.start() is a sync method, so Bolt will fail when using aiologger with a log level above INFO. We can discuss fixing this in a patch release if this is a method you'd like to use.
It appears that the aiologger instance isn't passed down to the slack_sdk client. The result is that slack_sdk logs would not use your async logger that writes to a file. This is unexpected behaviour, but we'd need to look into whether it's something that we can improve.

@tobenary You may already know a lot of this content, but I'll include it anyways to share my own discovery and learning process.
TL;Dr;
The main takeaway is that we'd recommend using the built-in logger module and setting it to write to a file. This aligns with the official asyncio documentation's suggest and would work reliably with Bolt. When asyncio supports async logging, we'd be super happy to add support for it as well!
Below are a few of my learnings and research into aiologger:
1. Writing logs to a file:
Bolt uses Python's standard logging module, so you can write logs to a file using Python's standard approach:
import logging
logging.basicConfig(filename='example.log', encoding='utf-8', level=logging.DEBUG)

2. Python's logger is sync-only:
Unfortunately, Python's logger is I/O Blocking. Even when using Bolt's Async methods based on asyncio, the logger will block with sync calls. This of course could be quite slow if you're writing to a file.
Interestingly, the official asyncio documentation suggests using the built-in Python sync logger module.
3. Logging with middleware:
You can use Bolt's middleware to log user requests. This would allow you to use a library such as aiologger to asynchronous log the requests.
However, this middleware will not capture Bolt's internal logs which will still use the built-in Python logger.
4. Using aiologger inside Bolt:
Bolt allows you to pass in your own Logger instance. Since aiologger uses the standard logging syntax, you could pass it into Bolt.
import logging
import os
from aiologger import Logger
from slack_bolt.async_app import AsyncApp

# Workaround: must use log level > INFO for now
logger = Logger.with_default_handlers(level=logging.WARNING)

# Initializes your app with your bot token and signing secret
app = AsyncApp(
    token=os.environ.get("SLACK_BOT_TOKEN"),
    signing_secret=os.environ.get("SLACK_SIGNING_SECRET"),
    logger=logger,
)

However, I've came across some limitations:

.start() is a sync method, so Bolt will fail when using aiologger with a log level above INFO. We can discuss fixing this in a patch release if this is a method you'd like to use.
It appears that the aiologger instance isn't passed down to the slack_sdk client. The result is that slack_sdk logs would not use your async logger that writes to a file. This is unexpected behaviour, but we'd need to look into whether it's something that we can improve.

Hi @tobenary, was the above comment helpful to you? As we've already provided an answer, let me close this issue after waiting for your response for a few more days.

Hi @tobenary, was the above comment helpful to you? As we've already provided an answer, let me close this issue after waiting for your response for a few more days.

We can discuss fixing this in a patch release if this is a method you'd like to use.
@seratch , @mwbrooks , What is my current options here?

Wait for @seratch fix in 10 days ( just writing a number )?
Have a workaround / patch as you suggested?

We can discuss fixing this in a patch release if this is a method you'd like to use.
@seratch , @mwbrooks , What is my current options here?

Wait for @seratch fix in 10 days ( just writing a number )?
Have a workaround / patch as you suggested?

@tobenary

What is my current options here?

The short answer is that you can use the standard logging module as the asyncio document suggests. We do not recommend using aiologger or similar solutions along with Bolt at this point.

Wait for @seratch fix in 10 days ( just writing a number )?
Have a workaround / patch as you suggested?

No, we are not planning to apply any changes in months or probably years.

When asyncio supports async logging, we'd be super happy to add support for it as well!

As @mwbrooks mentioned the possibility of updates in the future, if the asyncio/logging module comes up with some solutions for this, we may be able to apply some changes. Nevertheless, as far as I know, we don't have any information about the probability.

.start() is a sync method, so Bolt will fail when using aiologger with a log level above INFO. We can discuss fixing this in a patch release if this is a method you'd like to use.

Regarding this possibility of this patch, I'm not planning to apply anything in the short term. Indeed, it's possible to resolve the specific error in the start() method. However, this does not mean we can enable aiologger to properly work for all loggings.

@tobenary

What is my current options here?

The short answer is that you can use the standard logging module as the asyncio document suggests. We do not recommend using aiologger or similar solutions along with Bolt at this point.

Wait for @seratch fix in 10 days ( just writing a number )?
Have a workaround / patch as you suggested?

No, we are not planning to apply any changes in months or probably years.

When asyncio supports async logging, we'd be super happy to add support for it as well!

As @mwbrooks mentioned the possibility of updates in the future, if the asyncio/logging module comes up with some solutions for this, we may be able to apply some changes. Nevertheless, as far as I know, we don't have any information about the probability.

.start() is a sync method, so Bolt will fail when using aiologger with a log level above INFO. We can discuss fixing this in a patch release if this is a method you'd like to use.

Regarding this possibility of this patch, I'm not planning to apply anything in the short term. Indeed, it's possible to resolve the specific error in the start() method. However, this does not mean we can enable aiologger to properly work for all loggings.


Doc updates

Could you please put a link to the VS Code extension ( https://marketplace.visualstudio.com/items?itemName=LuisAlvesMartins.markdown-code-to-png ) somewhere.
Also, please make it clear that this extension depends on  HTTP requests to a 3rd party server ( mermaid.ink ) to run. Unfortunately, that means I can't use this for my company projects ... I'm sure it's possible to extract the logic from https://github.com/jihchi/mermaid.ink , but not sure if that's something you think would be useful

Thank you bbkane. Will do.


how to display the bandwith graphs (overlib) on the left side of the mouse?

I have a rather large map with several nodes and links on the right side of the map. when i mouse-over the link, tha bandwith graphs are "hidden" outside of the browser window. If I resize the browser window i see the whole graph.
Is there a config option to display the overlib graph on the left side of the mouse?

I'm using the phpweathermap V0.97c on a FreeBSD System

Depending on how much is hidden...
http://network-weathermap.com/manual/0.97b/pages/faq.html#overliboffscreen
But this works based on where the graph is relative to the centre of the map image, not the screen.

Hi Howard
Thank you very much for the help. I read the FAQ but dond't find that command usefull. Know that O know the reason behin this it all makes sense.
Thank you very much for your help


Action button not working on new B5600

Action button not working until watch registered in official application.
To Reproduce
Steps to reproduce the behavior:

Reset pairing info from watch

Open CasioGShockPhoneSync
Press mode button for 3 seconds -- it works
Press action button -- nothing happens

Expected behavior
Looks like need to save some pairing info on watch to be able to use action button
Additional context
I know that it is low priority issue, just to capture the problem

I cannot reproduce the problem on my watch. What is the model of your watch?
In general, you should not have to re-pair the watch. Make sure you have pressed the Action button for a very short time (short press). You should see the the read spinner some appear, actions will be run and the watch will disconnect. Wait until the app goes back to the initial screen, and you can run actions again.
By default, only the "set time" action is enabled.
If still does not, you may go to settings and clear the app's storage, and re-run the app again:

If this does not fix it, please add more add info here.

Actually, now that I think of it, re-pairing might have caused the problem. Each time the watch or re-paired, it generates a new BT ID. So from the phones settings, just clear the storage as in the screenshot above, re-run the app, and just press the buttons without doing anything special between.

GW-B5600-2
Did you tried to reset "pairing info" on the watch? After that (D) button is not working and doesn't even make a sound on press. Until I pair with the official app. After that it works as expected

Yes, I see this could be a problem, and I will try to address it. But I think it is not the usual way the app is used. Here is what happens:

First time you connect the watch, a new Bluetooth ID is created for the name of the watch. This ID is saved on the phone to be re-used in the future for a quick connection. This is similar to saving your WiFi connection, so you do not have to discover this connection in the future.
What you re-pair the watch, a new BT id is generated, but the phone tries to use the saved ID, and the connection is not established.
The official app requires an explicit registration for each watch, which I think is not convenient. So my approach is to make this process transparent for 99% of the users, which have one watch, and use it with the app with it, without having to register it.
But I understand your point, and will take a look if the re-pairing case can be handled better.
Thanks for your comments.

From the name of your watch, seems like you are paring two watches (thus the -2 at the end of the name).

No, it is index of color
Thank you for describing connection flow.
Looks like watches save some state after pairing with official app and without that "Action" button is not working. It is not a big problem, just can be an issue for users with a new watches who tries to use this application.

The issue was resolved. It turns out we need to send another command "Application Info" (0x22 34 88 F4 E5 D5 AF C8 29 E0 6D 02) to the watch to enable button D after watch reset. This value is read from the watch first, and then sent back.


ovos.utterance.cancelled should abort get_response

ovos.utterance.cancelled should abort get_response
otherwise ovos-utterance-plugin-cancel doesnt stop get_response from retrying

closing this one, on second thought i think get_response should retry the question if it was configured to do so, the num_retries kwarg is there for a reason
might revisit again after 0.0.8


Disable per file

Is there a way to disable harper per file? Thanks!

I'm somewhat confused by your question. Do you mean to disable it for a given buffer or filetype?

I should've been more specific. Yes, I meant per buffer. For example in markdownlint, I can do something along the lines of:
<!-- markdownlint-disable-file MD033 -->

I am curious if I can do something like this with harper.


Breakpoints not working with sourceMaps client

Breakpoints are not stopping on function calls when we debug with sourceMaps set to client.
Browser Version 59.0.2 (64-bit)
Webpack Version 4 (with babel)
Sourcemaps Type inline-source-map
Related issues: #62
Here is a repo with a minimal test case. More Information can be found in the Readme.
https://github.com/JSteitz/bug-vscode-firefox-debug-breakpoints-not-working

Thanks for the test case, it saved me a lot of time!
This seems to be a Firefox issue that has already been fixed in the nightlies: I could reproduce it in FF 59.0.2 but when I tried with the current developer edition (60.0b10), all breakpoints started working.


assign data.path where undefined

Just a suggestion for a solution to the conflict with metalsmith-path and metalsmith-paths, and maybe more acceptable solution than #62
I get that plugins should do one thing well, but I don't think this plugin is trying to be a replacement for those other plugins just by adding path to the meta data. the behaviour of this plugin pretty much requires the path property in the meta.

Hi @leviwheatcroft -
I did have this idea as well, but I think the problem with this is there might be conflicts as to which one is loaded first - and there is no guarantee that it would be loaded in any particular order.
The other thing is that each plugin in metalsmith is supposed to be as simple as possible - so you can use multiple plugins instead of having one behemoth plugin that tries to do too many things.

Hey @bashaus,
Regarding the load order, I don't really see the problem... if another plugin like metalsmith-path is called earlier then path property isn't overwritten, and calling another plugin after this one would have no effect regardless. Yes someone might expect this plugin to over write the path property, but that would be counter intuitive given that they would have explicitly set the path property with another plugin.
I understand your perspective regarding simple plugins, and tried to address this in my top comment. You could say plugins should be as simple as possible, but I think it's more apt to say plugins should do one thing. In that context, if metalsmith-collections does not set data.path then it fails this requirement, because while it may create the collection object in global meta that object isn't useful without the path property for most use cases.
Simplifying a plugin to the point at which an additional plugin is imposed on users is, in my opinion, the antithesis of simple plugins.
In any case, I'm a newcomer to metalsmith so more than happy to defer to your and the maintainer's experience here.

Merged, Conflicts resolved


Custom domain issue

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d2qb4xwieziuir
AWS Region
us-west-2
Amplify Hosting feature
Not Applicable
Describe the bug
I deployed my site using amplify a few days ago and bound my domain name (allonsygamma.com) in router53, then I reported the problem in GitHub. The next day, in my aws, my previous app disappeared. Today I tried to open a new app with my personal domain name and I got an error:
Error message: [CNAMEAlreadyExistsException] The following CloudFront distributions or Amplify Apps are already using one or more of your domains: [Distribution: *******J7CH77T in AWS Account: ******171576, Distribution: *******J7CH77T in AWS Account: ******171576].
Expected behavior
Bind domain to my new app.
Reproduction steps
none
Build Settings
none

Log output

# Put your logs below this line

Additional information
No response

I keep getting this issue too. Can assign my domain to a new app after the old one was deleted. I tried a few times during the last couple of days.

I had to update my existing CNAME records to point to the *.amplifyapp.com domain of my new app. From there, Amplify gave me new CNAME records to swap in in my DNS. After that I just had to wait for DNS records to propagate.

I had to update my existing CNAME records (from the old app) to point to the *.amplifyapp.com domain of my new app. From there, Amplify gave me new CNAME records to swap in in my DNS. After that I just had to wait for DNS records to propagate.

If your old APP is existing, you can solve this issue. But mine does not exist.

I had to update my existing CNAME records (from the old app) to point to the *.amplifyapp.com domain of my new app. From there, Amplify gave me new CNAME records to swap in in my DNS. After that I just had to wait for DNS records to propagate.

If your old APP is existing, you can solve this issue. But mine does not exist.

My app did not exist at the time.

I had to update my existing CNAME records (from the old app) to point to the *.amplifyapp.com domain of my new app. From there, Amplify gave me new CNAME records to swap in in my DNS. After that I just had to wait for DNS records to propagate.

If your old APP is existing, you can solve this issue. But mine does not exist.

My old app did not exist at the time.

In my router 53, I have 2 CNAME, did you change all your CNAME?

Yes, I had to change all related CNAME records.

Yes, I had to change all related CNAME records.

I will take a try, thx!

Hi @yinxiangshi the app that your custom domain is currently connected to still exists. When you say the app "disappeared" did you attempt to delete the app or is it just not visible in the console? We can see on our end that your app still exists and is still connected to the custom domain. Try running aws amplify list-apps to see if you are able to still interact with that application.

Hi @yinxiangshi the app that your custom domain is currently connected to still exists. When you say the app "disappeared" did you attempt to delete the app or is it just not visible in the console? We can see on our end that your app still exists and is still connected to the custom domain. Try running aws amplify list-apps to see if you are able to still interact with that application.

Hi, I didn't delete the app. In my dashboard, I can only see an app named "homepage"

Hi @yinxiangshi the app that your custom domain is currently connected to still exists. When you say the app "disappeared" did you attempt to delete the app or is it just not visible in the console? We can see on our end that your app still exists and is still connected to the custom domain. Try running aws amplify list-apps to see if you are able to still interact with that application.

I just find that my old app appears, and my new app disappears...


Conflicting limits in MockServer association and Gateway Modeller association

According to https://openui5.hana.ondemand.com/#docs/guide/c9a91ddaef47461c9c44bfc2198ea3f0.html „Due to a limitation of the mock server, you can not use the same association to describe a two-way navigation. If the navigation shall work for both directions, you need to define an appropriate association for each direction.”
according to http://help.sap.com/saphelp_gateway20sp10/helpdata/en/b0/03dd7114824a53b5cc2865d6784985/content.htm „Principal Key: Enter a key property of the principle Entity Type. Use the input help to select an existing property.” i.e. in the SAP Gateway modelling transaction SEGW the fromRole of a association can only use key properties for referential integrity constraints, thus I can define the association only in one direction.
Unfortunately these conflicting limitation make building OPENUI5/SAPUI5 based applications accessing sap gateway odata services modelled with SEGW hard.
We currently add the referential constraints for the reverse direction manually with statements like
oMockServer._mEntitySets.AssignmentSet.navprops.DemandItem.from.propRef = ["DemandItemKey"];
oMockServer._mEntitySets.AssignmentSet.navprops.DemandItem.to.propRef = ["DemandItemKey"];

after starting the MockServer which seems to work but is not very nice...
Couldn't you relax this MockServer restriction and make the use of a association for both direction be available out-of-the-box?

Hi guter Wolf,
thanks for reporting. I opened internal incident<PHONE_NUMBER> for this. We will come back to you when there is news on this one.
Best Regards,
Martin

Hi,
We are making sure to incorporate all feedback into the product, in hope of getting to it as soon as possible. We are treating your reported issue as a enhancement request, since it is not a regression from the delivered functionality.
Regards,
Gal

Hi all,
colleagues regard this issue as and enhancement request. I asked them to provide an estimate as to when it will make it into the backlog.
Best Regards,
Martin

@machwitt : What was the result of your question to the colleagues regarding time frame?

Hey @DerGuteWolf !
I just had a look into the internal incident and it actually states that this should be fixed with 28e1e7bb990399619eb9ea7bfcda3263aeabb623.
Could you please check if this fits to your reported issue?

Hi @DerGuteWolf ,
I'll close the issue because of its fix.
Feel free to reopen it if needed.
Thanks and Kind Regards,
Diana, openui5 dispatcher

At least then the documentation is still wrong cf referenced page in the openui5 documentation.
So please reopen the issue to fix at least the documentation. I will also recheck if the commit really fixes the problem.

You're right, sorry.
Reopened here, reopened in our tracking system.
Thanks and Kind Regards,
Diana,

Documentation was updated but the issue was not closed. Thanks to all of you bringing up this issue.

@flovogt unfortunately I do not see a change in the documentation. The ui5 documentation page linked above still has the sentence I cited. The problem with testing was/is that without documentation change I don't know exactly to expect and what not...

@DerGuteWolf Most of the UI5 documentation topics are open for contribution! :)
Here I created a PR to remove that outdated sentence: https://github.com/SAP/openui5-docs/pull/75


Problems view: filtering does not read out data about items found

Environment Details:
VSCode Version : 1.23.1
OS Version : Win10
MAC OS Version: HighSierra10.13.5
Repro Steps:

Launch VS Code while NVDA/VoiceOver is ON.
Go to View menu and Select Problems.
Tab till Filter textbox.

Actual:
VoiceOver does not read the text whatever we type in the Filter textbox and also does not announce any information about how many results found. Count issue is also observed with NVDA.
Expected:
VoiceOver or any screenreader  should read the text whatever we type in the textbox and also should give information about the data found.
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
Attachment for reference:
A11y VSCode Problems NVDAVoiceOver not readinmg filter items.pptx
Does this issue occur when all extensions are disabled?: Yes

For me, It reads the letters you type. But agreed it does not read the filtered count.

For me it also reads the letters, but some general information about the filtered count is missing.

I do not think we read the letters we type anywhere in other input boxes. What is important is the results after typing.
Now it reads the result after typing.