Add Clang Linux build to CI pipeline

The linux build is refactored to be able to switch between clang and gcc based builds of Velox.
The gcc based linux build is run on pull and push.
The clang based linux build is added to the scheduled jobs and executed on schedule
only.

The workflow isn't triggered. Maybe a chicken and egg problem?
@majetideepak FYI.
@assignUser Can you please take a look? Do you have any idea on how to test it?

@czentgr the job was triggerd but failed during parsing which means it doesn't show up in the check list (not a great choice on gh's part...) https://github.com/facebookincubator/velox/actions/runs/10411698998/workflow#L53
you'll have to use either full owner/repo@version syntax or local file syntaxt with ./... https://docs.github.com/en/actions/sharing-automations/reusing-workflows#calling-a-reusable-workflow

@assignUser Thank you! I fixed the path. I overlooked the part with the path in the doc.

@assignUser I hope it is nothing bad but got two odd issues in my recent run:
linux-adapter with clang (the one most interested in) failed with network issue (artifact read timed out).

Run gh run download $STASH_RUN_ID --name $STASH_NAME --dir "$STASH_DIR" -R "$REPO"
error downloading ccache-linux-adapters-10767_merge: error writing zip archive: read tcp <IP_ADDRESS>:52660-><IP_ADDRESS>:443: read: connection timed out

And MacOS14 failed during upload with
 node:events:497
      throw er; // Unhandled 'error' event
      ^

Error: EMFILE: too many open files, open '/Users/runner/work/velox/velox/.ccache/e/a/belcl8n03chag2f4bkp5u4di8puknssR'
Emitted 'error' event on ReadStream instance at:
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -24,
  code: 'EMFILE',
  syscall: 'open',
  path: '/Users/runner/work/velox/velox/.ccache/e/a/belcl8n03chag2f4bkp5u4di8puknssR'

I will retry later.

I have deleted all active caches for the mac 14 build (on main), that should fix this issue.

The build issue for ubuntu-clang Linux with adapters is fixed in PR https://github.com/facebookincubator/velox/pull/10800.

It seems the macos14 issues is related to a bug in the artifacts action, looking into it.

The release build with clang15 causes one of the tests in velox_dwio_common_test to SEGV. The issue only occurs with a release build.
Running main() from /builddir/build/BUILD/googletest-release-1.11.0/googletest/src/gtest_main.cc
Note: Google Test filter = ParallelForTest.E2E
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from ParallelForTest
[ RUN      ] ParallelForTest.E2E

Program received signal SIGSEGV, Segmentation fault.
0x0000000000cfe2a0 in folly::InlineLikeExecutor::InlineLikeExecutor (this=0x10b8318 <folly::InlineExecutor::instance_slow()::instance>, __vtt_parm=0x8, __in_chrg=<optimized out>) at /root/deps/folly/folly/executors/InlineExecutor.h:27
27      class InlineLikeExecutor : public virtual Executor {
Missing separate debuginfos, use: dnf debuginfo-install cyrus-sasl-lib-2.1.27-21.el9.x86_64 double-conversion-3.1.5-6.el9.x86_64 gflags-2.2.2-9.el9.x86_64 glibc-2.34-120.el9.x86_64 gmock-1.11.0-1.el9.x86_64 gtest-1.11.0-1.el9.x86_64 keyutils-libs-1.6.3-1.el9.x86_64 krb5-libs-1.21.1-3.el9.x86_64 libatomic-11.5.0-2.el9.x86_64 libbrotli-1.0.9-6.el9.x86_64 libcom_err-1.46.5-5.el9.x86_64 libcurl-7.76.1-29.el9.x86_64 libdwarf-0.3.4-1.el9.1.x86_64 libevent-2.1.12-6.el9.x86_64 libgcc-11.5.0-2.el9.x86_64 libgsasl-1.10.0-3.el9.x86_64 libicu-67.1-9.el9.x86_64 libidn-1.38-4.el9.x86_64 libidn2-2.3.0-7.el9.x86_64 libnghttp2-1.43.0-6.el9.x86_64 libpsl-0.21.1-5.el9.x86_64 libselinux-3.6-1.el9.x86_64 libsodium-1.0.18-8.el9.x86_64 libssh-0.10.4-13.el9.x86_64 libunistring-0.9.10-15.el9.x86_64 libxml2-2.9.13-6.el9.x86_64 libzstd-1.5.1-2.el9.x86_64 lz4-libs-1.9.3-5.el9.x86_64 openssl-libs-3.2.2-2.el9.x86_64 pcre2-10.40-6.el9.x86_64 re2-20211101-20.el9.x86_64 xz-libs-5.2.5-8.el9.x86_64 zlib-1.2.11-41.el9.x86_64
(gdb) bt
#0  0x0000000000cfe2a0 in folly::InlineLikeExecutor::InlineLikeExecutor (this=0x10b8318 <folly::InlineExecutor::instance_slow()::instance>, __vtt_parm=0x8, __in_chrg=<optimized out>)
    at /root/deps/folly/folly/executors/InlineExecutor.h:27
#1  0x0000000000cfe302 in folly::InlineExecutor::InlineExecutor (this=0x10b8318 <folly::InlineExecutor::instance_slow()::instance>, __in_chrg=<optimized out>, __vtt_parm=<optimized out>)
    at /root/deps/folly/folly/executors/InlineExecutor.h:35
#2  0x0000000000cfe356 in folly::Indestructible<folly::InlineExecutor>::Storage::Storage<, folly::InlineExecutor>(std::in_place_t) (this=0x10b8318 <folly::InlineExecutor::instance_slow()::instance>)
    at /root/deps/folly/folly/Indestructible.h:152
#3  0x0000000000cfe28c in folly::Indestructible<folly::InlineExecutor>::Indestructible<folly::InlineExecutor, folly::InlineExecutor> (this=0x10b8318 <folly::InlineExecutor::instance_slow()::instance>)
    at /root/deps/folly/folly/Indestructible.h:73
#4  0x0000000000cfe1ed in folly::InlineExecutor::instance_slow () at /root/deps/folly/folly/executors/InlineExecutor.cpp:24
#5  0x0000000000952ca6 in ParallelForTest_E2E_Test::TestBody() ()
#6  0x00007ffff796ee0c in void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) [clone .constprop.0] () from /lib64/libgtest.so.1.11.0
#7  0x00007ffff794f826 in testing::Test::Run() () from /lib64/libgtest.so.1.11.0
#8  0x00007ffff794f9f0 in testing::TestInfo::Run() () from /lib64/libgtest.so.1.11.0
#9  0x00007ffff794faf9 in testing::TestSuite::Run() () from /lib64/libgtest.so.1.11.0
#10 0x00007ffff795efc5 in testing::internal::UnitTestImpl::RunAllTests() () from /lib64/libgtest.so.1.11.0
#11 0x00007ffff795c7c8 in testing::UnitTest::Run() () from /lib64/libgtest.so.1.11.0
#12 0x00007ffff7fac154 in main () from /lib64/libgtest_main.so.1.11.0
#13 0x00007ffff6229590 in __libc_start_call_main () from /lib64/libc.so.6
#14 0x00007ffff6229640 in __libc_start_main_impl () from /lib64/libc.so.6
#15 0x00000000008f8395 in _start ()

(gdb) p $_siginfo
$1 = {si_signo = 11, si_errno = 0, si_code = 1, _sifields = {_pad = {8, 0 <repeats 27 times>}, _kill = {si_pid = 8, si_uid = 0}, _timer = {si_tid = 8, si_overrun = 0, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _rt = {si_pid = 8,
      si_uid = 0, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _sigchld = {si_pid = 8, si_uid = 0, si_status = 0, si_utime = 0, si_stime = 0}, _sigfault = {si_addr = 0x8, _addr_lsb = 0, _addr_bnd = {_lower = 0x0, _upper = 0x0}},
    _sigpoll = {si_band = 8, si_fd = 0}}}

A SEGV at signal address 0x8. So a nullptr that tries to access at offset 0x8.
Perhaps some optimization in clang that causes the issue from the test due to instruction reordering.

The current fuzzer failures are a known issue for which an issue is already open:
Reason: Unicode characters are not supported for conversion to integer types

@assignUser @majetideepak FYI. I believe this is ready for review. We want this merged so we can also automatically get the C++20 PR run with Clang 15 (I've done this manually but would be nice to confirm in the pipeline).

@assignUser Not sure you can help with this but there is a problem with the pipeline (Build and Push Adapters job) and accessing a container image
Pulling binfmt Docker image
  /usr/bin/docker pull tonistiigi/binfmt:latest
  Error response from daemon: unauthorized: authentication required
Error: The process '/usr/bin/docker' failed with exit code 1

CI is green, looks good to me I just want to repeat a comment from my last review about the additional CI time this brings (+4hs on cold cache!).

I agree. Should we run this as part of the nightly runs instead?

I've moved the Clang build job to the scheduled workflow file.

I have one comment here https://github.com/facebookincubator/velox/pull/10767#discussion_r1804504051
I will add the merge label once that is addressed.

I have one comment here #10767 (comment) I will add the merge label once that is addressed.

@majetideepak I did re-check this earlier (a while back) and the issue still exists even with the new folly version.

@czentgr CI is red.

@mbasmanova Yes. Two flaky tests failed that seem to have been fixed recently (aka within the last 24h). I can rebase again. Does this cause an issue with the fact that you already imported it?

@czentgr I'm seeing merge conflict with "Add gcc11 to Ubuntu20.04 setup and add PkgConfig install". Would you rebase?

@mbasmanova Odd you see a conflict. "Add gcc11 to Ubuntu20.04 setup and add PkgConfig install" did touch setup-ubuntu.sh but in different places and should not cause a conflict. I've rebased so hopefully your conflict is gone.

@czentgr There is Spark Fuzzer failure. Would you take a look?
CC: @rui-mo

This change should not affect the fuzzer. I created an issue: https://github.com/facebookincubator/velox/issues/11462
In it there is a reference to an issue that was closed earlier with the same error. Maybe it resurfaced for some reason?

@czentgr Something happening and land got stuck. Would you rebase so I can try again?

@mbasmanova The fuzzer failure was some intermittend network issue. It failed to upload artifacts
With the provided path, there will be 6 files uploaded
Artifact name is valid!
Root directory input is valid!
Attempt 1 of 5 failed with error: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact. Retrying request in 3000 ms...
Attempt 2 of 5 failed with error: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact. Retrying request in 5792 ms...
Attempt 3 of 5 failed with error: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact. Retrying request in 9578 ms...
Attempt 4 of 5 failed with error: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact. Retrying request in 10563 ms...
Error: Failed to CreateArtifact: Failed to make request after 5 attempts: Request timeout: /twirp/github.actions.results.api.v1.ArtifactService/CreateArtifact

The fuzzer run itself was successful. I think we are good and you merged the PR :)


Remove legacy code regarding fmap

Description
This removes a lot of legacy code involving fmap.

Removes Control.Applicative imports for (<$>), (<*>), (<$), pure, and Applicative as these are in base now.
Replaces all infix occurences of fmap and liftM with <$>.
Replaces liftM2 with liftA2.
Replaces all remaining (prefix) occurences of liftM with fmap (I decided to not replace anything with <$> here, so as to preserve the original authors style).
Applies the functor laws (in just one case) and replaces constructs of the form fmap f $ fa with f <$> fa.
Replaces join . fmap (as well as things like join $ io $ fmap) with =<<.
Cleans up all Control.Monad imports of liftM and liftM2 (as those are no longer needed).

Checklist

[x] I've read CONTRIBUTING.md

[ ] I tested my changes with xmonad-testing
Will try to get to this as soon as I can.

[ ] I updated the CHANGES.md file
I did not think this necessary.

Wow, thanks so much!
While skimming through the changes I noticed a few places with the keyword do followed by a single line of code.  It might be worth going through and getting rid of those too (not that I'm saying you have to do it!).


allow showing any content-type in calendar

I am still testing this (I can't make this addon work in Volto 17 because of some Webpack issues which I don't understand), but I think that with these changes we can make this plugin more flexible and allow showing any content object in the calendar view of a listing provided the integrator/developer implements a function with the information to show on it.

I have been testing this and it works perfectly in Volto 17 after fixing the webpack issues (See #12)

Thanks @stevepiercy!

@erral it looks the docs are still OK with this change. Can you verify?

This is not a collective repo, so it's up to the repo owner @mbarde to accept a catch fix for a poor backend implementation.
IMHO Event like objects do have IEventBasic attributes.
An opening to event like objects is OK and needed.
This just needs a change in the filter condition  from
if (i['@type'] !== 'Event')
to
if (!i.start)

I don't think that my implementation is poor because I am not using IEventBasic attributes in my content-type.
That implementation is my choice and I am not forced to use IEventBasic behavior to model my content-type.
I think I have provided a very extensible implementation to show anything on this calendar, not being tied to use IEventBasic (which I didn't think of initially). I have also updated the PR with your suggestion, allowing items that provide start and end.
Ok. I am not going to argue more on this. If the repo owner is happy, fair enough. If not, I don't mind. I have my branch where I can keep working on.

I agree with @ksuess and removed the type restriction in the newest release (1.0.0) as suggested.
I wont add "official" support for content-types which do not implement IEventBasic.
@erral A suggested approach to go without a custom fork: Shadow the  Listing/FullCalendar  component and build a wrapper around the original component which transforms items and feeds the transformed array into the original (see https://community.plone.org/t/volto-composition-to-customize-components/14059/3).
(I will have to do this for a project within the next days, where we have the requirement that single objects should result in multiple events in the calendar. So if you are interested I could provide a code example for this.)
Furthermore,  I added support for easily passing custom props to the FullCalendar component, which could useful to cover special use-cases as well: https://github.com/mbarde/volto-fullcalendar-block?tab=readme-ov-file#customize-fullcalendar-options

@erral Possible way to do data transformation without modifying the original components: https://github.com/mbarde/volto-fullcalendar-block?tab=readme-ov-file#customize-listing-block-variation


'$ref' in basePath does not pass validation command

Problem statement
Using $ref is not supported by validate command, while swagger UI works with this spec.
Swagger specification
swagger.yml:
swagger: '2.0'
info:
  version: "1.0.0"
basePath:
  $ref: basepath-ref-src.json
paths:
  /foo/:
    get:
      responses:
        "200":

basepath-ref-src.json:
"/abc"

Steps to reproduce
Place both files in a folder, run this command from bash in the same folder:
docker run --rm -v $(pwd):/home -w /home quay.io/goswagger/swagger:0.13.0 validate swagger.yml
2018/03/26 15:54:51 json: cannot unmarshal object into Go struct field SwaggerProps.basePath of type string

Environment
swagger version: 0.13.0
go version: 1.9.4
OS:   Linux ef5acc98e0b3 4.9.87-linuxkit-aufs #1 SMP Wed Mar 14 15:12:16 UTC 2018 x86_64 Linux

yes it's not supported by the spec.


Auto-detect changes to map size (and invalidateSize)

I have a map that's styled like this:
#map {position: absolute; top: 10px; left: 10px; right: 10px; bottom: 90px;}

... i.e. it has no explicit height.  So, of course, leaflet isn't rendering all of the tiles.  However I do setTimeout(map.invalidateSize.bind(map)), after creating the map it renders properly.
This has me thinking that it's not actually necessary for the map to have an explicit height - it's just a question of insuring Leaflet is smart about detecting the height at the appropriate time.

My two cents:
I think a minor fix would help in order to prevent a bug I had: keep trying to get the size if it is 0,0.
getSize: function () {
		if (!this._size || this._sizeChanged || (this._size && this._size.x == 0 && this._size.y == 0) {
			this._size = new Point(
				this._container.clientWidth || 0,
				this._container.clientHeight || 0);

			this._sizeChanged = false;
		}
		return this._size.clone();
	},

The element could be initialized with zero size but later change without calling resize (I think, at least this is what I think happened in the scenario I had to fix).

I appreciate that this issue has been closed; I had this issue today and reading this discussion inspired my fix (bare in mind that my case is VERY simple- just a map with a view and a marker)
It might help a fellow noob like myself:
$('#tab').click(function()     {setTimeout(function(){setView|tileLayer|add to map|add markers},200);}
This prevents the default none display of tab content interfering with the tiling process (I'm sure this has probably been mentioned though!) :)


update openapi generation and linting

Codecov Report

Merging #308 (63f33dc) into master (828d37a) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 63f33dc differs from pull request most recent head faef806. Consider uploading reports for the commit faef806 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #308   +/-   ##
=======================================
  Coverage   87.73%   87.73%
=======================================
  Files          36       36
  Lines        5015     5015
=======================================
  Hits         4400     4400
  Misses        406      406
  Partials      209      209


@conda-forge-admin, rerender

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/pari-feedstock#17.


Crashes with Essential server list

Description
When installed with Essential, clicking on "Featured" in the multiplayer menu causes the game to crash. Also crashes in "Friends" if there is a friend playing on a server
Crash report: crash-2024-03-23_23.05.58-client.txt
System info
M1 MacBook Pro
Bundled ARM64 Java
1.20.4 Fabric
How to reproduce

Install the latest version of these mods for 1.20.4:

Fabric API
Numeral Ping
Essential
YACL

Go to "Multiplayer"
And then click on "Featured", or "Friends" if there is a friend playing on a server
Game crashes

If this is an issue with Essential, then I will file a report with them, too

fixed from essential


Ads back on on Volume up during interdimensional cable

-One Plus 7 Pro
-Oxygen OS 9.5.11 (Android 9.x port)
-Phone is connected to bluetooth speaker/headset.
-Interdimensinal cabel setting
On changing volume it also changes the mute setting for ads:
--->I can hear spotify ads as well as interdimensional cable
to reproduce:
turn on interdimensional cable
listen to spotify and wait for ads
turn volume louder -->ads  and interdimensional cable plays simultaneously
Note; This setting is also saved, so next time ads show up it still plays simultaneously
Temporary fix:

turn off spotify,
open ad-free
re-apply the setting

Hi mordeng,
This is a side effect of how playback of music in Ad-Free is currently implemented. If you adjust volume during ad blocking, your phone will change the volume of STREAM_MUSIC, ie the channel through which Spotify plays ads. As a result STREAM_MUSIC is unmuted and you get your described behavior.

You can adjust playback volume of Ad-Free in the settings of the interdimensional cable or the music plugin.


Change In UI of HomePage

The whole website's UI will be changed, so provide some best modern design alternatives for the whole website, keeping in mind the user experience.
As of now , apply the design in the home page only, and if possible provide some design alternatives.

Can you assign the respective task. I have some doubt also. Now, after running the project, we will see a table. We have to make a new home page, which sections are required in the home page?

go ahead!

any updates?

is this issue still open?

yes

Can I be assigned to this issue then, please?

go ahead! and if you have any doubt please let us know on discord. Also, asking you are participating from swoc21 right ?

Yes,I am


I can't load textural inversions saved as .safetensors

Did you try to load the file specifically, or just a folder with all the textural inversions?
I fixed a bug when loading a folder skipped .safetensors files, so now loading them should work one way or the other. Unless there is an error with file itself.


Update install

Problem

Close #176

Solution

MongoDB is not fully supported on arm64

PR Status

[ ] Code finished and ready to be reviewed/tested
[ ] The fix/enhancement were manually tested (if applicable)

Automatic tests
Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)

!testme


[Event Request] codeunit 10821 "Export DEB DTI" - OnAfterAddNode

Hi, would it be possible to get an event OnAfterAddNode codeunit 10821 "Export DEB DTI", like this :
        end;

        if IntrastatJnlLine."Transport Method" <> '' then
            XMLDomMgt.AddNode(XMLNode, 'modeOfTransportCode', IntrastatJnlLine."Transport Method");

        OnAfterAddNode(XMLNode,XMLDomMgt, CompanyInfo);
    end;

    [IntegrationEvent(false, false)]
    local procedure OnAfterAddNode(var XMLNode: DotNet XMLNode;var XMLDomMgt: Codeunit "XML DOM Management";var CompanyInfo: Record "Company Information")
    begin
    end;

Thanks!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


[BUG] Restore vault cause app to crash

Sometimes when restore a vault , it cause the app to crash

https://github.com/vultisig/vultisig-ios/pull/528


EXEC_BAD_ACCESS in failable init when a key does not exist

I was evaluating ObjectMapper to see if we can use it instead of 'vanilla' JSON parsing, but ran into a crash when checking if it gives a readable error if it's missing a required field. This issue occurs in my case when implementing Mappable on a struct with immutable members, as shown in "Mapping Immutable Properties" in the readme. The issue occurs in version 0.17 and 0.16, in both a unit test environment (like the demo code) and running the app (in debug mode). It happens both when I change the key used in map[], or a key in the source json file. Done in Swift 2, XCode 7, under iOS 9.
Demo code (can probably be converted to a storyboard, but this is how I reproduced it) https://gist.github.com/fwielstra/dd02aaac645ac7445653

What I expected to happen was the '!map.isValid' branch being called; a bonus would be if ObjectMapper said "I did not find this required field in the response object".

Actually, nested objects and nested arrays of mappables don't seem to work properly when using the failable init method, similar errors. Is that one tested properly? I don't see it being used in the tests much. I'd rather not make large changes to my data model (i.e. make my fields mutable and explicitly unwrapped) to make this library work.

@fwielstra support for immutable properties is a relatively new feature and definitely has not been tested as throughly the standard mapping.


Fix paragraphs not being applied in journal posts

Fixes #3204
Paragraphs were not being applied when in between 2 sections of tables, lists or preformatted text.
This was because the regex used was greedy, and would include everything between the first and last of one of those tags, rather than stop matching after the first end tag it finds.
Fix was to apply the non-greedy ? modifier to the *s.
Issue was also visible on messages as well as journal posts.

Thanks, @seanclifford!


LND has unexpectedly quit: Error Code: 2

After installing Peach Desktop wallet and open at the same time

Expected Behavior
Zap Desktop wallet should open normally
Actual Behavior
Zap could not reopen anymore
Possible Fix
Not sure how to fix it
Steps to Reproduce
DEBUG=zap* DEBUG_LEVEL=debug /Applications/ZapDesktop.app/Contents/MacOS/ZapDesktop
Context
Last login: Sat Dec 29 08:45:05 on ttys000
JCs-MacBook-Pro:~ jcawe$ DEBUG=zap* DEBUG_LEVEL=debug /Applications/ZapDesktop.app/Contents/MacOS/ZapDesktop
(node:1382) ExperimentalWarning: The http2 module is an experimental API.
zap:main [LOG]  Time until app is ready: 77.528513ms +0ms
zap:main [DBG]  Fetching user settings from indexedDb (using database "ZapDesktop.production") +55ms
zap:main [DBG]  Got user settings: [ { key: 'activeWallet', value: 2 }, { key: 'isWalletOpen', value: true }, { key: 'locale', value: 'en' }, { key: 'theme', value: 'dark' } ] +263ms
2018-12-29 09:00:14.203 ZapDesktop[1382:53499] *** WARNING: Textured window <AtomNSWindow: 0x7f92a05420d0> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.
zap:updater [INF]  Checking for update +16ms
zap:i18n [ 'Determined language as +0ms', 'Bulgarian' ]
zap:i18n [ 'Determined language as +1ms', 'Czech' ]
zap:i18n [ 'Determined language as +0ms', 'German' ]
zap:i18n [ 'Determined language as +1ms', 'English' ]
zap:i18n [ 'Determined language as +1ms', 'Castilian' ]
zap:i18n [ 'Determined language as +0ms', 'French' ]
zap:i18n [ 'Determined language as +1ms', 'Irish' ]
zap:i18n [ 'Determined language as +9ms', 'Croatian' ]
zap:i18n [ 'Determined language as +0ms', 'Japanese' ]
zap:i18n [ 'Determined language as +0ms', 'Dutch' ]
zap:i18n [ 'Determined language as +0ms', 'Portuguese' ]
zap:i18n [ 'Determined language as +1ms', 'Moldavian' ]
zap:i18n [ 'Determined language as +0ms', 'Russian' ]
zap:i18n [ 'Determined language as +0ms', 'Swedish' ]
zap:i18n [ 'Determined language as +0ms', 'Turkish' ]
zap:i18n [ 'Determined language as +0ms', 'Ukrainian' ]
zap:main [DBG]  [FSM] onOnboarding... +544ms
zap:main [DBG]  [FSM] onStartOnboarding... +451ms
zap:main [INF]  Sending message to renderer process: { msg: 'startOnboarding', data: undefined } +0ms
zap:main [INF]  Starting lnd with options: { alias: 'MoveblockOTC', autopilot: true, autopilotAllocation: 0.6, autopilotMaxchannels: 5, autopilotMaxchansize: 16777215, autopilotMinchansize: 20000, autopilotMinconfs: 0, autopilotPrivate: true, binaryPath: '/Applications/ZapDesktop.app/Contents/Resources/bin/lnd', cert: '/Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2/tls.cert', chain: 'bitcoin', configPath: '/Applications/ZapDesktop.app/Contents/Resources/resources/lnd.conf', host: 'localhost:11009', id: 2, lndDir: '/Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2', macaroon: '/Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2/data/chain/bitcoin/testnet/admin.macaroon', name: 'ZAP LND Moveblock Wallet - Testnet', network: 'testnet', rpcProtoPath: '/Applications/ZapDesktop.app/Contents/Resources/resources/rpc.proto', type: 'local' } +77ms
zap:lnd-config Constructor called with options: { id: 2, type: 'local', chain: 'bitcoin', network: 'testnet', settings: { name: 'ZAP LND Moveblock Wallet - Testnet', alias: 'MoveblockOTC', autopilot: true, autopilotMaxchannels: 5, autopilotAllocation: 0.6, autopilotMinchansize: 20000, autopilotMaxchansize: 16777215, autopilotPrivate: true, autopilotMinconfs: 0 } } +0ms
zap:lnd-config Setting settings as: { name: 'ZAP LND Moveblock Wallet - Testnet', autopilot: true, autopilotMaxchannels: 5, autopilotMinchansize: 20000, autopilotMaxchansize: 16777215, autopilotAllocation: 0.6, autopilotPrivate: true, autopilotMinconfs: 0, alias: 'MoveblockOTC' } +1ms
zap:lnd-config Connection type is local. Assigning settings as: { host: 'localhost:10009', cert: '/Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2/tls.cert', macaroon: '/Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2/data/chain/bitcoin/testnet/admin.macaroon' } +0ms
zap:main [DBG]  [FSM] onBeforeStartLocalLnd... +2ms
zap:main [INF]  Starting new lnd instance +1ms
zap:main [INF]   > alias: MoveblockOTC +0ms
zap:main [INF]   > autopilot: true +0ms
zap:main [INF]  Starting Neutrino... +0ms
zap:main [INF]  Starting lnd in neutrino mode +0ms
zap:main [INF]   > binaryPath /Applications/ZapDesktop.app/Contents/Resources/bin/lnd +1ms
zap:main [INF]   > rpcProtoPath: /Applications/ZapDesktop.app/Contents/Resources/resources/rpc.proto +0ms
zap:main [INF]   > host: localhost:10009 +0ms
zap:main [INF]   > cert: /Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2/tls.cert +0ms
zap:main [INF]   > macaroon: /Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2/data/chain/bitcoin/testnet/admin.macaroon +0ms
zap:main [INF]  Spawning Neutrino process: /Applications/ZapDesktop.app/Contents/Resources/bin/lnd --configfile=/Applications/ZapDesktop.app/Contents/Resources/resources/lnd.conf --lnddir=/Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2 --listen=<IP_ADDRESS>:9735 --rpclisten=localhost:11009 --restlisten=localhost:8180 --alias=MoveblockOTC --autopilot.active --autopilot.private --autopilot.maxchannels=5 --autopilot.minchansize=20000 --autopilot.maxchansize=16777215 --autopilot.allocation=0.6 --autopilot.minconfs=0 --neutrino.connect=testnet1-btcd.zaphq.io --neutrino.connect=testnet2-btcd.zaphq.io +5ms
zap:main [INF]  Sending message to renderer process: { msg: 'lndStarted', data: e { id: 2, type: 'local', chain: 'bitcoin', network: 'testnet', host: [Getter/Setter], cert: [Getter/Setter], macaroon: [Getter/Setter], string: [Getter/Setter], name: 'ZAP LND Moveblock Wallet - Testnet', alias: 'MoveblockOTC', autopilot: true, autopilotMaxchannels: 5, autopilotMinchansize: 20000, autopilotMaxchansize: 16777215, autopilotAllocation: 0.6, autopilotPrivate: true, autopilotMinconfs: 0, wallet: [Getter], binaryPath: [Getter], lndDir: [Getter], configPath: [Getter], rpcProtoPath: [Getter] } } +22ms
zap:lnd [INF]  2018-12-29 09:00:15.379 [INF] LTND: Version: 0.5.1-beta commit=, build=production, logging=default +65ms
zap:lnd [INF]  2018-12-29 09:00:15.379 [INF] LTND: Active chain: Bitcoin (network=testnet) +0ms
zap:lnd [INF]  2018-12-29 09:00:15.380 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7 +1ms
zap:lnd [INF]  2018-12-29 09:00:15.390 [INF] RPCS: password gRPC proxy started at <IP_ADDRESS>:8180 +8ms
zap:lnd [INF]  2018-12-29 09:00:15.390 [INF] RPCS: password RPC server listening on <IP_ADDRESS>:11009 +0ms
zap:main [INF]  Wallet unlocker gRPC active +0ms
zap:main [INF]  Establishing connection to Wallet Unlocker gRPC interface... +1ms
zap:main [INF]  Connecting to WalletUnlocker gRPC service +1ms
zap:lnd [INF]  2018-12-29 09:00:15.390 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it. +6ms
zap:main [INF]  Sending message to renderer process: { msg: 'walletUnlockerGrpcActive', data: e { id: 2, type: 'local', chain: 'bitcoin', network: 'testnet', host: [Getter/Setter], cert: [Getter/Setter], macaroon: [Getter/Setter], string: [Getter/Setter], name: 'ZAP LND Moveblock Wallet - Testnet', alias: 'MoveblockOTC', autopilot: true, autopilotMaxchannels: 5, autopilotMinchansize: 20000, autopilotMaxchansize: 16777215, autopilotAllocation: 0.6, autopilotPrivate: true, autopilotMinconfs: 0, wallet: [Getter], binaryPath: [Getter], lndDir: [Getter], configPath: [Getter], rpcProtoPath: [Getter] } } +84ms
zap:updater [INF]  Update for version 0.3.2-beta is not available (latest version: 0.3.2-beta, downgrade is disallowed). +2s
zap:main [INF]  Calling walletUnlocker method 'unlockWallet' +20s
zap:lnd [INF]  2018-12-29 09:00:38.434 [INF] LNWL: Opened wallet +846ms
zap:main [INF]  Establishing connection to Lightning gRPC interface... +50ms
zap:main [INF]  Connecting to Lightning gRPC service +1ms
zap:lnd [INF]  2018-12-29 09:00:38.511 [INF] LTND: Primary chain is set to: bitcoin +25ms
zap:lnd [INF]  2018-12-29 09:00:38.689 [INF] BTCN: Loaded 1980 addresses from file '/Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2/data/chain/bitcoin/testnet/peers.json' +178ms
zap:lnd [INF]  2018-12-29 09:00:38.689 [INF] BTCN: Waiting for more block headers, then will start cfheaders sync from height 1449938... +1ms
zap:lnd [INF]  2018-12-29 09:00:38.689 [INF] BTCN: Starting cfheaders sync from (block_height=1449938, block_hash=00000000000000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f) to (block_height=1449939, block_hash=0000000000000054a97167fb41df6dade429f556fbdf1103776a643b1aeb6edb) +0ms
zap:lnd [INF]  2018-12-29 09:00:38.690 [INF] BTCN: Starting cfheaders sync for filter_type=0 +0ms
zap:lnd [DBG]  2018-12-29 09:00:38.690 [DBG] BTCN: Getting filter checkpoints up to height=1449939, hash=0000000000000054a97167fb41df6dade429f556fbdf1103776a643b1aeb6edb +1ms
zap:lnd [WRN]  2018-12-29 09:00:38.690 [WRN] BTCN: Unable to fetch set of candidate checkpoints, trying again... +0ms
zap:lnd [DBG]  2018-12-29 09:00:38.690 [DBG] CMGR: Attempting to connect to <IP_ADDRESS>:18333 (reqid 1) +0ms
zap:lnd [DBG]  2018-12-29 09:00:38.689 [DBG] CMGR: Attempting to connect to <IP_ADDRESS>:18333 (reqid 2) +1ms
zap:main [DBG]  waiting for file: /Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2/data/chain/bitcoin/testnet/admin.macaroon +7ms
zap:main [DBG]  found file: /Users/jcawe/Library/Application Support/Zap/lnd/bitcoin/testnet/wallet-2/data/chain/bitcoin/testnet/admin.macaroon +0ms
zap:lnd [INF]  2018-12-29 09:00:38.698 [INF] CMGR: DNS discovery failed on seed testnet-seed.bitcoin.schildbach.de: lookup testnet-seed.bitcoin.schildbach.de: no such host +37ms
zap:lnd [INF]  2018-12-29 09:00:38.745 [INF] CMGR: 3 addresses found from DNS seed testnet-seed.bluematt.me +9ms
zap:lnd [DBG]  2018-12-29 09:00:38.890 [DBG] CMGR: Connected to <IP_ADDRESS>:18333 (reqid 1) +145ms
zap:lnd [DBG]  2018-12-29 09:00:38.890 [DBG] BTCN: Sending version (agent /btcwire:0.5.0/neutrino:0.0.4-beta/, pver 70013, block 1449939) to <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [DBG]  2018-12-29 09:00:38.891 [DBG] CMGR: Connected to <IP_ADDRESS>:18333 (reqid 2) +2ms
zap:lnd [DBG]  2018-12-29 09:00:38.892 [DBG] BTCN: Sending version (agent /btcwire:0.5.0/neutrino:0.0.4-beta/, pver 70013, block 1449939) to <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [INF]  2018-12-29 09:00:38.905 [INF] CMGR: DNS discovery failed on seed x49.testnet-seed.bitcoin.jonasschnelli.ch: lookup x49.testnet-seed.bitcoin.jonasschnelli.ch: no such host +13ms
zap:lnd [INF]  2018-12-29 09:00:38.976 [INF] CMGR: DNS discovery failed on seed x49.seed.tbtc.petertodd.org: lookup x49.seed.tbtc.petertodd.org: no such host +71ms
zap:lnd [DBG]  2018-12-29 09:00:39.091 [DBG] BTCN: Received version (agent /btcwire:0.5.0/btcd:0.12.0/, pver 70013, block 1449940) from <IP_ADDRESS>:18333 (outbound) +115ms
zap:lnd [DBG]  2018-12-29 09:00:39.091 [DBG] BTCN: Negotiated protocol version 70013 for peer <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.091 [DBG] BTCN: Added time sample of -1s (total: 1) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.091 [DBG] BTCN: Connected to <IP_ADDRESS>:18333 +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.091 [DBG] BTCN: Received verack from <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.091 [DBG] BTCN: New peer <IP_ADDRESS>:18333 (outbound) +1ms
zap:lnd [DBG]  2018-12-29 09:00:39.091 [DBG] BTCN: Sending verack to <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [INF]  2018-12-29 09:00:39.091 [INF] BTCN: New valid peer <IP_ADDRESS>:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/) +0ms
zap:lnd [INF]  2018-12-29 09:00:39.096 [INF] BTCN: Syncing to block height 1449940 from peer <IP_ADDRESS>:18333 +5ms
zap:main [INF]  Neutrino sync started +0ms
zap:main [INF]  Sending message to renderer process: { msg: 'lndSyncStatus', data: 'in-progress' } +0ms
zap:main [INF]  Sending message to renderer process: { msg: 'currentBlockHeight', data: 1449940 } +1ms
zap:main [INF]  Fetching current block height from https://testnet-api.smartbit.com.au/v1/blockchain/blocks?limit=1 +0ms
zap:main [INF]  Fetching current block height from https://tchain.api.btc.com/v3/block/latest +1ms
zap:main [INF]  Fetching current block height from https://api.blockcypher.com/v1/btc/test3 +0ms
zap:lnd [INF]  2018-12-29 09:00:39.096 [INF] BTCN: Fetching set of headers from tip (height=1449939) from peer <IP_ADDRESS>:18333 +2ms
zap:main [INF]  Sending message to renderer process: { msg: 'lndBlockHeight', data: 1449939 } +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.096 [DBG] BTCN: Sending getheaders (locator<PHONE_NUMBER>000054a97167fb41df6dade429f556fbdf1103776a643b1aeb6edb, stop<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000) to <IP_ADDRESS>:18333 (outbound) +1ms
zap:lnd [DBG]  2018-12-29 09:00:39.096 [DBG] BTCN: Received version (agent /btcwire:0.5.0/btcd:0.12.0/, pver 70013, block 1449940) from <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.096 [DBG] BTCN: Negotiated protocol version 70013 for peer <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.096 [DBG] BTCN: Added time sample of -1s (total: 2) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.097 [DBG] BTCN: Connected to <IP_ADDRESS>:18333 +0ms
zap:lnd [INF]  2018-12-29 09:00:39.098 [INF] BTCN: New valid peer <IP_ADDRESS>:18333 (outbound) (/btcwire:0.5.0/btcd:0.12.0/) +21ms
zap:lnd [DBG]  2018-12-29 09:00:39.098 [DBG] BTCN: New peer <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.099 [DBG] BTCN: Received verack from <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.099 [DBG] BTCN: Sending verack to <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.298 [DBG] BTCN: Received headers (num 1) from <IP_ADDRESS>:18333 (outbound) +175ms
zap:lnd [INF]  2018-12-29 09:00:39.513 [INF] LNWL: The wallet has been unlocked without a time limit +215ms
zap:lnd [INF]  2018-12-29 09:00:39.513 [INF] LTND: LightningWallet opened +1ms
zap:lnd [DBG]  2018-12-29 09:00:39.513 [DBG] LNWL: Birthday block has already been verified: height=1411264, hash=00000000000000243dbe79cb6a0af0b97e6375fb77777890ef1533b9d99d0103 +0ms
zap:lnd [INF]  2018-12-29 09:00:39.516 [INF] HSWC: Restoring in-memory circuit state from disk +2ms
zap:lnd [INF]  2018-12-29 09:00:39.517 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0 +1ms
zap:lnd [INF]  2018-12-29 09:00:39.518 [INF] HSWC: Trimming open circuits for chan_id=1449934:4:1, start_htlc_id=0 +1ms
zap:lnd [INF]  2018-12-29 09:00:39.520 [INF] LTND: Waiting for chain backend to finish sync, start_height=1449938 +2ms
zap:main [INF]  Neutrino sync waiting +1ms
zap:main [INF]  Sending message to renderer process: { msg: 'lndSyncStatus', data: 'waiting' } +0ms
zap:lnd [INF]  2018-12-29 09:00:39.520 [INF] RPCS: RPC server listening on <IP_ADDRESS>:11009 +0ms
zap:lnd [INF]  2018-12-29 09:00:39.520 [INF] RPCS: gRPC proxy started at <IP_ADDRESS>:8180 +0ms
zap:lnd [INF]  2018-12-29 09:00:39.523 [INF] LNWL: Started rescan from block<PHONE_NUMBER>0000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f (height 1449938) for 23 addresses +2ms
zap:lnd [DBG]  2018-12-29 09:00:39.523 [DBG] BTCN: Waiting for filter headers (height=1449938) to catch up the rescan start (height=1449938) +0ms
zap:main [INF]  Neutrino sync started +0ms
zap:main [INF]  Sending message to renderer process: { msg: 'lndSyncStatus', data: 'in-progress' } +0ms
zap:lnd [INF]  2018-12-29 09:00:39.523 [INF] LNWL: Catching up block hashes to height 1449938, this might take a while +1ms
zap:lnd [DBG]  2018-12-29 09:00:39.524 [DBG] BTCN: Waiting for filter headers (height=1449938) to catch up the rescan start (height=1449938) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.524 [DBG] BTCN: Starting rescan from known block 1449938<PHONE_NUMBER>0000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f) +0ms
zap:lnd [DBG]  2018-12-29 09:00:39.524 [DBG] BTCN: Rescan became current at 1449938<PHONE_NUMBER>0000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f), subscribing to block notifications +1ms
zap:lnd [INF]  2018-12-29 09:00:39.524 [INF] LNWL: Done catching up block hashes +0ms
zap:lnd [INF]  2018-12-29 09:00:39.524 [INF] LNWL: Finished rescan for 23 addresses (synced to block<PHONE_NUMBER>0000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f, height 1449938) +0ms
zap:main [INF]  Subscribing to Lightning gRPC streams +230ms
zap:main [INF]  Sending message to renderer process: { msg: 'lightningGrpcActive', data: e { id: 2, type: 'local', chain: 'bitcoin', network: 'testnet', host: [Getter/Setter], cert: [Getter/Setter], macaroon: [Getter/Setter], string: [Getter/Setter], name: 'ZAP LND Moveblock Wallet - Testnet', alias: 'MoveblockOTC', autopilot: true, autopilotMaxchannels: 5, autopilotMinchansize: 20000, autopilotMaxchansize: 16777215, autopilotAllocation: 0.6, autopilotPrivate: true, autopilotMinconfs: 0, wallet: [Getter], binaryPath: [Getter], lndDir: [Getter], configPath: [Getter], rpcProtoPath: [Getter] } } +2ms
zap:lnd [DBG]  2018-12-29 09:00:39.759 [DBG] CRTR: New graph topology client subscription, client 1 +2ms
zap:main [INF]  Calling lnd method: { msg: 'info', data: undefined } +15ms
zap:main [INF]  Fetched block height as 1449940 from: https://testnet-api.smartbit.com.au/v1/blockchain/blocks?limit=1 +162ms
zap:main [INF]  Fetched block height as 1449940 from: https://api.blockcypher.com/v1/btc/test3 +188ms
zap:lnd [INF]  2018-12-29 09:00:40.527 [INF] LTND: Chain backend is fully synced (end_height=1449938)! +404ms
zap:main [INF]  Neutrino sync finished +0ms
zap:main [INF]  Sending message to renderer process: { msg: 'lndSyncStatus', data: 'complete' } +0ms
zap:lnd [DBG]  2018-12-29 09:00:40.528 [DBG] BTCN: Waiting for filter headers (height=1449938) to catch up the rescan start (height=1449938) +1ms
zap:lnd [DBG]  2018-12-29 09:00:40.528 [DBG] BTCN: Starting rescan from known block 1449938<PHONE_NUMBER>0000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f) +0ms
zap:lnd [DBG]  2018-12-29 09:00:40.529 [DBG] BTCN: Rescan became current at 1449938<PHONE_NUMBER>0000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f), subscribing to block notifications +0ms
zap:lnd [INF]  2018-12-29 09:00:40.532 [INF] HSWC: Starting HTLC Switch +3ms
zap:lnd [INF]  2018-12-29 09:00:40.532 [INF] NTFN: New block epoch subscription +2ms
zap:lnd [INF]  2018-12-29 09:00:40.532 [INF] NTFN: New block epoch subscription +0ms
zap:lnd [INF]  2018-12-29 09:00:40.540 [INF] CNCT: Creating ChannelArbitrators for 1 active channels +6ms
zap:lnd [INF]  2018-12-29 09:00:40.540 [INF] NTFN: New block epoch subscription +2ms
zap:lnd [DBG]  2018-12-29 09:00:40.541 [DBG] CNCT: New ChainEventSubscription(id=0) for ChannelPoint(bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1) +0ms
zap:lnd [INF]  2018-12-29 09:00:40.541 [INF] NTFN: New block epoch subscription +0ms
zap:lnd [DBG]  2018-12-29 09:00:40.542 [DBG] CNCT: Starting chain watcher for ChannelPoint(bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1) +0ms
zap:lnd [DBG]  2018-12-29 09:00:40.542 [DBG] NTFN: Using height hint 1449934 retrieved from cache for bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1 +0ms
zap:lnd [INF]  2018-12-29 09:00:40.542 [INF] NTFN: New spend subscription: spend_id=1, outpoint=bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1, height_hint=1449934 +1ms
zap:lnd [DBG]  2018-12-29 09:00:40.542 [DBG] BTCN: Enqueuing request for bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1 with birth height 1449938 +1ms
zap:lnd [DBG]  2018-12-29 09:00:40.542 [DBG] BTCN: Fetching block height=1449938 hash=00000000000000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f +0ms
zap:lnd [DBG]  2018-12-29 09:00:40.542 [DBG] BTCN: Sending getdata (witness block<PHONE_NUMBER>0000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f) to <IP_ADDRESS>:18333 (outbound) +0ms
zap:main [INF]  Calling lnd method: { msg: 'balance', data: undefined } +57ms
zap:lnd [DBG]  2018-12-29 09:00:40.605 [DBG] RPCS: [walletbalance] Total balance=0.23356625 BTC +6ms
zap:main [INF]  Calling lnd method: { msg: 'payments', data: undefined } +1ms
zap:main [INF]  Calling lnd method: { msg: 'invoices', data: undefined } +1ms
zap:main [INF]  Calling lnd method: { msg: 'transactions', data: undefined } +2ms
zap:main [INF]  Calling lnd method: { msg: 'channels', data: undefined } +5ms
zap:main [INF]  Calling lnd method: { msg: 'peers', data: undefined } +3ms
zap:lnd [DBG]  2018-12-29 09:00:40.621 [DBG] RPCS: [listpeers] yielded [] peers +4ms
zap:lnd [DBG]  2018-12-29 09:00:40.621 [DBG] RPCS: [ListPayments] +0ms
zap:lnd [INF]  2018-12-29 09:00:40.624 [INF] RPCS: [listchannels] fetched 1 channels from DB +9ms
zap:lnd [DBG]  2018-12-29 09:00:40.632 [DBG] RPCS: [pendingchannels] +1ms
zap:main [INF]  Calling lnd method: { msg: 'describeNetwork', data: undefined } +20ms
zap:main [INF]  Calling lnd method: { msg: 'balance', data: undefined } +59ms
zap:lnd [DBG]  2018-12-29 09:00:40.721 [DBG] RPCS: [walletbalance] Total balance=0.23356625 BTC +9ms
zap:main [INF]  Calling lnd method: { msg: 'info', data: undefined } +16ms
zap:lnd [DBG]  2018-12-29 09:00:40.743 [DBG] BTCN: Received block (hash<PHONE_NUMBER>0000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f, ver 536870912, 31 tx, 2018-12-29 08:38:18 +0800 HKT) from <IP_ADDRESS>:18333 (outbound) +6ms
zap:lnd [DBG]  2018-12-29 09:00:40.744 [DBG] BTCN: Processing block height=1449938 hash=00000000000000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f +1ms
zap:lnd [DBG]  2018-12-29 09:00:40.744 [DBG] BTCN: Adding outpoint=bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1 height=1449938 to watchlist +0ms
zap:lnd [ERR]  2018-12-29 09:00:40.744 [ERR] BTCN: Failed to find outpoint bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1 -- txid not found in block +0ms
zap:lnd [DBG]  2018-12-29 09:00:40.744 [DBG] BTCN: Finished batch, 1 unspent outpoints +0ms
zap:lnd [INF]  2018-12-29 09:00:40.756 [INF] CNCT: Close observer for ChannelPoint(bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1) active +12ms
zap:lnd [DBG]  2018-12-29 09:00:40.756 [DBG] CNCT: Starting ChannelArbitrator(bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1), htlc_set=(contractcourt.htlcSet) { +1ms
zap:lnd [DBG]   incomingHTLCs: (map[uint64]channeldb.HTLC) { +0ms
zap:lnd [DBG]   }, +0ms
zap:lnd [DBG]   outgoingHTLCs: (map[uint64]channeldb.HTLC) { +0ms
zap:lnd [DBG]   } +0ms
zap:lnd [DBG]  } +0ms
zap:lnd [DBG]   +0ms
zap:lnd [INF]  2018-12-29 09:00:40.757 [INF] CNCT: ChannelArbitrator(bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1): starting state=StateDefault +1ms
zap:lnd [DBG]  2018-12-29 09:00:40.757 [DBG] CNCT: ChannelArbitrator(bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1): new block (height=1449938) examining active HTLC's +0ms
zap:lnd [DBG]  2018-12-29 09:00:40.757 [DBG] CNCT: ChannelArbitrator(bc0a23fe76dfa5a0847c845825c912f0d08e8837a5f7d6811bbdf30d93b21cf8:1): checking chain actions at height=1449938 +0ms
zap:lnd [INF]  2018-12-29 09:00:40.757 [INF] DISC: Authenticated Gossiper is starting +0ms
zap:lnd [INF]  2018-12-29 09:00:40.757 [INF] CRTR: FilteredChainView starting +0ms
zap:lnd [INF]  2018-12-29 09:00:40.758 [INF] BRAR: Starting contract observer, watching for breaches. +1ms
zap:lnd [INF]  2018-12-29 09:00:40.759 [INF] NTFN: New block epoch subscription +0ms
zap:lnd [ERR]  2018-12-29 09:00:40.759 [ERR] DISC: Unable to rebroadcast stale channels: unable to retrieve outgoing channels: Channel from self node has no policy +0ms
zap:lnd [DBG]  2018-12-29 09:00:40.759 [DBG] BTCN: Waiting for filter headers (height=1449938) to catch up the rescan start (height=1449938) +0ms
zap:lnd [DBG]  2018-12-29 09:00:40.759 [DBG] BTCN: Starting rescan from known block 1449938<PHONE_NUMBER>0000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f) +0ms
zap:lnd [DBG]  2018-12-29 09:00:40.759 [DBG] BTCN: Rescan became current at 1449938<PHONE_NUMBER>0000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f), subscribing to block notifications +0ms
zap:lnd [INF]  2018-12-29 09:00:40.797 [INF] CRTR: Filtering chain using 4755 channels active +38ms
zap:lnd [INF]  2018-12-29 09:00:40.802 [INF] CRTR: Prune tip for Channel Graph: height=1449938, hash=00000000000000da53cb40da20776312c728970d5bb81ea7c942b1b679ea3e0f +5ms
zap:lnd [INF]  2018-12-29 09:00:40.809 [INF] CMGR: Server listening on [::]:9735 +7ms
zap:lnd [INF]  2018-12-29 09:00:40.809 [INF] BTCN: Lost peer <IP_ADDRESS>:18333 (outbound) +0ms
zap:lnd [INF]  2018-12-29 09:00:40.809 [INF] LTND: New invoice subscription client: id=0 +1ms
zap:lnd [INF]  2018-12-29 09:00:40.809 [INF] LTND: Cancelling invoice subscription for client=0 +0ms
zap:main [DBG]  CHANNELGRAPH STATUS: [object Object]
zap:main Inspected object #1
zap:main { code: 0,
zap:main   details: '',
zap:main   metadata: l { internalRepr: { 'content-type': [Array] } } } +0ms
zap:main [INF]  CHANNELGRAPH END +1ms
zap:main [INF]  TRANSACTION STATUS:  [object Object]
zap:main Inspected object #1
zap:main { code: 0,
zap:main   details: '',
zap:main   metadata: l { internalRepr: { 'content-type': [Array] } } } +0ms
zap:main [INF]  TRANSACTION END +0ms
zap:main [INF]  INVOICE STATUS: [object Object]
zap:main Inspected object #1
zap:main { code: 0,
zap:main   details: '',
zap:main   metadata: l { internalRepr: { 'content-type': [Array] } } } +1ms
zap:main [INF]  INVOICE END +0ms
zap:lnd [INF]  2018-12-29 09:00:40.813 [INF] BTCN: Syncing to block height 1449940 from peer <IP_ADDRESS>:18333 +1ms
zap:lnd [INF]  2018-12-29 09:00:40.813 [INF] BTCN: Fetching set of headers from tip (height=1449940) from peer <IP_ADDRESS>:18333 +1ms
zap:lnd [INF]  2018-12-29 09:00:40.822 [INF] BTCN: Lost peer <IP_ADDRESS>:18333 (outbound) +8ms
zap:lnd [WRN]  2018-12-29 09:00:40.824 [WRN] BTCN: No sync peer candidates available +2ms
zap:main [INF]  Calling lnd method: { msg: 'balance', data: undefined } +342ms
zap:main [INF]  Calling lnd method: { msg: 'balance', data: undefined } +1ms
zap:lnd [INF]  2018-12-29 09:00:40.860 [INF] BTCN: Block manager shutting down +2ms
zap:lnd [INF]  2018-12-29 09:00:40.860 [INF] BTCN: Address manager shutting down +0ms
zap:lnd [INF]  2018-12-29 09:00:40.868 [INF] LTND: Shutdown complete +0ms
zap:lnd [ERR]  panic: runtime error: invalid memory address or nil pointer dereference +0ms
zap:lnd [ERR]  [signal SIGSEGV: segmentation violation code=0x1 addr=0x60 pc=0x193663a] +0ms
zap:lnd [ERR]   +0ms
zap:lnd [ERR]  goroutine 1 [running]: +0ms
zap:lnd [ERR]  main.(*server).establishPersistentConnections.func1(0xc000496ee0, 0xc010ff4000, 0x0, 0xc011708120, 0xc010ff4058, 0x21) +0ms
zap:lnd [ERR]  	/Users/tom/.go/src/github.com/lightningnetwork/lnd/server.go:1649 +0x3a +0ms
zap:lnd [ERR]  github.com/lightningnetwork/lnd/channeldb.(*LightningNode).ForEachChannel.func1(0xc000496ee0, 0x1d39c88, 0xc000496ee0) +0ms
zap:lnd [ERR]  	/Users/tom/.go/src/github.com/lightningnetwork/lnd/channeldb/graph.go:2017 +0x591 +0ms
zap:lnd [ERR]  github.com/lightningnetwork/lnd/vendor/github.com/coreos/bbolt.(*DB).View(0xc0000bc1e0, 0xc01170ecf0, 0x0, 0x0) +0ms
zap:lnd [ERR]  	/Users/tom/.go/src/github.com/lightningnetwork/lnd/vendor/github.com/coreos/bbolt/db.go:699 +0x90 +1ms
zap:lnd [ERR]  github.com/lightningnetwork/lnd/channeldb.(*LightningNode).ForEachChannel(0xc011016000, 0x0, 0xc010a30780, 0x0, 0xc000207198) +0ms
zap:lnd [ERR]  	/Users/tom/.go/src/github.com/lightningnetwork/lnd/channeldb/graph.go:2029 +0xbf +0ms
zap:lnd [ERR]  main.(*server).establishPersistentConnections(0xc01093e300, 0x0, 0x0) +0ms
zap:lnd [ERR]  	/Users/tom/.go/src/github.com/lightningnetwork/lnd/server.go:1644 +0x33e +0ms
zap:lnd [ERR]  main.(*server).Start(0xc01093e300, 0x1bf4411, 0x2e) +0ms
zap:lnd [ERR]  	/Users/tom/.go/src/github.com/lightningnetwork/lnd/server.go:991 +0x231 +0ms
zap:lnd [ERR]  main.lndMain(0x0, 0x0) +0ms
zap:lnd [ERR]  	/Users/tom/.go/src/github.com/lightningnetwork/lnd/lnd.go:417 +0x10b8 +0ms
zap:lnd [ERR]  main.main() +0ms
zap:lnd [ERR]  	/Users/tom/.go/src/github.com/lightningnetwork/lnd/lnd.go:449 +0x26 +0ms
zap:main [DBG]  Neutrino process received "exit" event with code 2 and signal null +1ms
zap:main [INF]  Lnd process has shut down (code: 2, signal: null) +0ms
zap:main [INF]  Sending message to renderer process: { msg: 'lndStopped', data: undefined } +0ms
zap:main [DBG]  [FSM] onTerminated... +17s
zap:main [DBG]  [FSM] onTerminate... +1ms
zap:main [ERR]  balance: Error
zap:main Stack trace #1
zap:main Error
zap:main     at t.Http2CallStream.Function (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/client.js:94:1)
zap:main     at t.Http2CallStream.emit (events.js:187:15)
zap:main     at t.Http2CallStream.[object Object] [as endCall] (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/call-stream.js:72:1)
zap:main     at t.Http2CallStream.Status (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/call-stream.js:300:1)
zap:main     at Generator.next ()
zap:main     at resolve (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/call-stream.js:6:32)
zap:main     at process._tickCallback (internal/process/next_tick.js:68:7) +18ms
zap:main [ERR]  balance: Error
zap:main Stack trace #1
zap:main Error
zap:main     at t.Http2CallStream.Function (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/client.js:94:1)
zap:main     at t.Http2CallStream.emit (events.js:187:15)
zap:main     at t.Http2CallStream.[object Object] [as endCall] (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/call-stream.js:72:1)
zap:main     at t.Http2CallStream.Status (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/call-stream.js:300:1)
zap:main     at Generator.next ()
zap:main     at resolve (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/call-stream.js:6:32)
zap:main     at process._tickCallback (internal/process/next_tick.js:68:7) +1ms
zap:main [INF]  Calling lnd method: { msg: 'describeNetwork', data: undefined } +18ms
zap:main [ERR]  describeGraph: Error: Getting metadata from plugin failed with error: New streams cannot be created after receiving a GOAWAY
zap:main Stack trace #1
zap:main Error: Getting metadata from plugin failed with error: New streams cannot be created after receiving a GOAWAY
zap:main     at t.Http2CallStream.Function (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/client.js:94:1)
zap:main     at t.Http2CallStream.emit (events.js:187:15)
zap:main     at t.Http2CallStream.[object Object] [as endCall] (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/call-stream.js:72:1)
zap:main     at t.Http2CallStream.deadline (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/call-stream.js:341:1)
zap:main     at Generator.next ()
zap:main     at resolve (/Applications/ZapDesktop.app/Contents/Resources/app.asar/webpack:/node_modules/@grpc/grpc-js/build/src/call-stream.js:6:32)
zap:main     at process._tickCallback (internal/process/next_tick.js:68:7) +2ms
zap:main [WRN]  Unable to fetch block height from https://tchain.api.btc.com/v3/block/latest: timeout of 5000ms exceeded +13ms
Your Environment
MAC OS

Zap Desktop version:
Operating System and version:

@qjawe - your instance of lnd is crashing.
You may want to search through the lnd issue queues to see if one of the many reported instances of this issue matches your scenario:
https://github.com/lightningnetwork/lnd/search?q=invalid+memory+address&unscoped_q=invalid+memory+address&type=Issues
If not, I would suggest that you open up an issue in the lnd issues queues since the issue relates directly to lnd rather than to Zap.
Are you updating from an older version of Zap/lnd? When did you create your wallet? I know there have been similar issues for people in the past when upgrading older wallets to a newer version of lnd. In order to get past thew issue, you could delete your wallet and start afresh (since your wallet is testnet only anyway).

Are you updating from an older version of Zap/lnd?
upgrade to the latest version
When did you create your wallet?
import the previous wallet
I know there have been similar issues for people in the past when upgrading older wallets to a newer version of lnd. In order to get past thew issue, you could delete your wallet and start afresh (since your wallet is testnet only anyway).
yup delete the old ones still the same problem

I will create another wallet and let's see how it goes...
Wallet address: 2MyHh4UgayWPyP2bzJZ19XK5iFoCxmbSAeM

I will create another wallet and let's see how it goes...
Wallet address: 2MyHh4UgayWPyP2bzJZ19XK5iFoCxmbSAeM

https://live.blockcypher.com/btc-testnet/address/2MyHh4UgayWPyP2bzJZ19XK5iFoCxmbSAeM/

I'm going to close this issue due to lack of activity. If the issue persists for you with the latest release of Zap - 0.3.4-beta please feel free to reopen this issue. Thanks.


Add message to NonUniqueResultException

@Alfredao can you please add a minimal unit test for this? Although the code is brutally simple, it is still a requirement.

Hello @Ocramius
Today a coworker asked me for help identifying what was wrong with his code. No error message was displayed. Then I realized that this was about this exception with no text message
As he is starting with Doctrine developmet, it could have been difficult for him to identify the problem by himself
This PR has been open for a long time. Will the merge be done? Is there anything that needs to be done yet?
Thank you!

@Alfredao didn't see that tests were pushed: added milestone, will check it as soon as possible

@Alfredao @Ocramius I've rebased this branch but made a small mistake so I'm opening a new PR with your changes.


perf: use normalized path as a key in document registry

Closing this PR in favor of forthcoming revision of path related API


Update config.yml

I run the sample with the below error ,but I used Pthon ,it works!
cmd.exe : Python was not found but can be installed from the Microsoft Store: https://go.microsoft.com/fwlink?linkID=2082640
所在位置 C:\Users\xinsh\nni\experiments\sVPyAII6\trials\Ik1oq\run.ps1:11 字符: 1

cmd.exe /c python3 main.py 2>"C:\Users\xinsh\nni\experiments\sVPyAII6 ...

  + CategoryInfo          : NotSpecified: (Python was not ...?linkID=2082640:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

Hi @xinshouke, the reason why your cmd.exe can not find python maybe is that python is not in your Path env. When you type python in cmd or powershell, do you see >>> or "cannot found python" ?

I suspect you are correct!


Getting warning for jsx on a regular js file

On all my es6 files file I'm getting this warning  on the first line, although they have nothing to do with jsx

Warning text (to make this issue easier to find via search):

Definition for rule 'react/jsx-no-duplicate-props' was not found (react/jsx-no-duplicate-props)at line 1 col 1

Only happens when using standard or semi-standard, not when using happiness. Occurs on all non-empty js files.
Maybe one can copy the happiness rule list over to the other lists.

This is fixed in semistandard 7.0.3, so all that is needed for linter-js-standard is to update dependency to newer version
Pull request https://github.com/ricardofbarros/linter-js-standard/pull/76 solves this, but it has not been merged yet.
In the meantime, if you want to get rid of this, as a workaround you can change version of semistandard dependency in .atom/packages/linter-js-standard/package.json
and do:
npm install

in that directory (.atom/packages./linter-js-standard)

Actually both of the open pull requests solves this.


Construct an estimate of intervention disease reduction

In order to test whether disease prevalence in intervention really is 'incorrect', we should form our own estimates from first principles. We know the equation for new disease probability (below), and we know the relative risk coefficients.
P_disease = incidence * (mean_risk_current / mean_risk_initial)

We need to set up a simulation and find:

[ ] the mean combined risk for a disease in our starting population
[ ] the mean combined risk for that disease at one or more future points of interest
[ ] our estimate of probability of disease, using the equation above, the mean risk values and existing incidence data
[ ] the actual simulated incidence of that disease at these points of interest

Estimate of adjusted incidence rate based on IHME epidemiological data
Simulated incidence rate (income group 1 - 500 simulations)

| Estimate | Simulated
-- | -- | --
Min | 0.000 | 0.000
1st Q | 0.000 | 0.0002135
Median | 0.002 | 0.0034862
Mean | 0.014 | 0.0094834
3rd Q | 0.029 | 0.0203051
Max | 0.059 | 0.0399933

Simulated and expected incidence rates of seven diseases
Note: Interaction with other diseases is not considered in expected incidence rate.

 Nice one. Many thanks @jzhu20.

I'm closing this, as I'm under he impression that it is now resolved. Reopen if not.


SILALL

"Okmo ke silall" is a common expression which means "if you had waited". Therefore, I think SILALL is the past tense of MSALL.

it seems to be the past form of HALL or MSALL we already have in DB,

"Okmo ke silall" is a common expression which means "if you had waited". Therefore, I think SILALL is the past tense of MSALL.

Agree. Silall; waited/paused/held off.


Null option are now effected with l option.

refs: https://github.com/monochromegane/the_platinum_searcher/pull/143

I think this should have an effect when passed -l option.
Because xargs -0 option expect filenames.

A short option -0 are now added.

Great! I plan to write a blog about why this is useful.

Sounds good !


Identity: SqlServer adding a string ForeignKey throws exception regarding length

Both properties are strings, so I'm not sure what the issue is. (Note: the foreignkeys work fine using InMemoryDataStore)
    protected override void OnModelCreating(ModelBuilder builder)
    {
        builder.Entity<TUser>()
            .Key(u => u.Id)
            .Properties(ps => ps.Property(u => u.UserName))
            .ToTable("AspNetUsers");

        builder.Entity<IdentityUserClaim>()
            .Key(uc => uc.Id)
            // TODO: this throws a length exception currently, investigate
            .ForeignKeys(fk => fk.ForeignKey<TUser>(f => f.UserId))
            .ToTable("AspNetUserClaims");
    }

Results in:
System.Data.SqlClient.SqlException : Column 'AspNetUsers.Id' is not the same length or scale as referencing column
'AspNetUserClaims.UserId' in foreign key 'FK_AspNetUserClaims_AspNetUsers_UserId'. Columns participating in a foreign k
ey relationship must be defined with the same length and scale.\r\nCould not create constraint. See previous errors.
public class IdentityUserClaim : IdentityUserClaim<string> { }
public class IdentityUserClaim<TKey> where TKey : IEquatable<TKey>
{
    /// <summary>
    ///     Primary key
    /// </summary>
    public virtual int Id { get; set; }

    /// <summary>
    ///     User Id for the user who owns this login
    /// </summary>
    public virtual TKey UserId { get; set; }

public class User
{
    public virtual string Id { get; set; }

public class Department
{
    [Key]
    [Required]
    [MaxLength(50)]
    [Display(Name = "Department")]
    public String DeptName { get; set; }

    [MaxLength(6)]
    [Display(Name = "Fund")]
    public String FundID { get; set; }

    [MaxLength(6)]
    [Display(Name = "Department Number")]
    public String DeptNumber { get; set; }
}

public class Department_AKA
{
[Key]
[Required]
[MaxLength(50)]
[Display(Name = "AKA Department Desc/Name")]
public String AKA { get; set; }
    [Required]
    [MaxLength(50)]
    [Display(Name = "Department")]
    public String DeptName { get; set; }
    public virtual IEnumerable<Department> lstDepartment { get; set; }

}

Throws error :
SqlException: Column 'Department_AKAs.AKA' is not the same length or scale as referencing column 'Departments.Department_AKAAKA' in foreign key 'FK_Departments_Department_AKAs_Department_AKAAKA'. Columns participating in a foreign key relationship must be defined with the same length and scale.
Am I missing something?


storage controller: use Utilization in scheduling decisions

Currently, the scheduler orders nodes according to constraints, and then within nodes which have the same AffinityScore, we select the one with the fewest shards assigned to it.
That works pretty well at small scale and when we're mainly dealing with big tenants who have big shards such that disk space and shard count are strongly correlated.
In order to make the storage controller work well with large numbers of tiny tenants, we'll need to use the Utilization of a pageserver (already stored in Node courtesy of the heartbeater) in the scheduling.
This ticket isn't about making the scheduler perfect, just to make sure that we do something sensible if we have e.g. one node with 10 shards whose utilization is full, and another node with 1000 shards whose utilization is really low because all those 1000 shards are little 32mb ones.

If layer visiblity materializes by the we are looking into this, it would make sense to update the utilization endpoint to use it.


Automated Package Upgrade

:tada: This PR is included in version 12.0.53 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update test suite and migrate it to new design.

This PR migrates the test suite to the new design.
It also adds some testing functionality for the DCS transforms for PSS.
Finally it also adds testing support for each individual version of matlab from R2021b to R2024a (the currently supported range, minimum due to verification functions, and maximum due to the known bug causing vdx to fail in R2024b).


Update "Clone Git Repository" to confirm if and when clone operation is successful

Signed-off-by: Pranav Suryawanshi<EMAIL_ADDRESS>

https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/job/rhods-ci-pr-test/665/console
Result : passed

@pranavsuryaw Thanks, looks good. Please run the full Sanity job with this PR since you are modifying a keyword a lot of test cases are using

https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/job/rhods-ci-pr-test/677/console

@pranavsuryaw there are 52 failures, clearly something went wrong with that run. Please run it again next week on an isolated cluster.

https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/job/rhods-ci-pr-test/682/console

@jgarciao I have made the requested changes in that keyword in temp file, if it looks good then i will update in the JupyterLabLauncher.robot file

I have made changes to the temp.robot file, I will update the keywords in the JupyterLabLauncher.robot file if it is correct.

I don't see any failures due to git clones in the sanity run logs, I think this can be merged. @jgarciao @bdattoma can you also take a look?

lgtm. @jgarciao pls have a look since there are some conversations open who might need to close

Just in case, I think we should merge this once the RHODS 1.12 RC build smoke job has been run successfully.
I've temporally added the "do not merge" tag

@jgarciao Build has been handed off, should we merge this?


Remove v1 records api

A lot of this is also updating the functional tests.
When doing assertions, it would check which is is persisted in Hoverfly, but it was using the v1 records endpoint.


AOM appears and disappears

I have AOM set as hidden. It randomly appears and disappears. Using Chrome.

Thanks for the report, we're currently working to fix this one.

I'm going to go ahead and close this as it's a duplicate of #64.
Rest assured we'll fix it, just want to track it all in one place.


MCParticle Energy at Detector Bounds

As mentioned in this forum post, it would be useful to get the energy of particles as they pass through a sensor. This PR adds getTotalEnergyArrival and getKineticEnergyArrival functions to the MCParticle object, to return a particle's total or kinetic energy as it arrives at a detector.

Thanks for your comments Simon. I've made the changes you suggested — getTotalEnergyArrival is now getTotalEnergyStart etc.

Thanks @sam-sw for the changes, I cloned your MR to here for a full run in our CI and for merging it directly upstream. Thanks a lot for your contribution!
(Fun feature: Github will mark this MR automatically as merged once the commits arrive in the repo :) )


Areis RFC link attachment and format improvement

Referenced aries-framework-javascript.
Signed-off-by: kukgini<EMAIL_ADDRESS>

Cool. Thanks.


Implement fault tolerant GRIB2/PP loading.

This PR allows loading of all convertible GRIB2 messages from a file even if some of the messages in the file cannot be converted to a cube. Since GRIB is inherently message based and there is not really a proper concept of a GRIB file, it seems unreasonable for Iris to fail completely when it meets a message it can't understand and fail to load the messages it does understand.
The implementation is relatively straightforward, an extra attribute fault_tolerant is added to the object iris.fileformats.rules.Loader which then allows iris.fileformats.rules.load_cubes to determine if it should try to carry on if it encounters a TranslationError. In principle this can be extended to any file format using iris.fileformats.rules.load_cubes as a handler, but only GRIB is implemented so far.
Remaining tasks:

[ ] Push an integration test when the iris-test-data repository is updated with a suitable file.

apologies for being late to the party
I support this change, I think it is a useful capability.  I would like to be clear that this is opt-in behaviour, I would expect to get exceptions from a load, and have to manually specify that I am happy to lose fields during load.
I think there should be a comment in the user guide section on loading data explaining this behaviour

I would like to be clear that this is opt-in behaviour, I would expect to get exceptions from a load, and have to manually specify that I am happy to lose fields during load.

As long as translation errors result in visual feedback, I would expect opt-out to be more useful.

Hello
I'd like to revitalise this PR
The comments have converged to an extent on this being a fault tolerant approach that just runs, then it is not backwards compatible.
If we can get this fixed and have slightly richer information on why a field is skipped I'm minded to get this in
So, is there life in this one? what do you think @ajdawson ?

I'd like to get this in, but I'm not entirely clear on how I should proceed here. What are your requirements for information about skipped fields @marqh? Would we really want a separate warning for each field? Or a warning with a list of fields (containing what information?)?
I need to update this anyway to account for backwards compatibility in Loader. I'm not particularly keen on users having to go through the warnings system to generate exceptions, but I'm not sure what other options would be satisfactory.

Just realised I already had a go at fixing this up, but hadn't pushed it up. I've rebased to catch up with master, and added a new commit that stores the exception from each skipped TranslationError. These messages are then raised as warnings of type FieldLoadFault. You can then use the warnings mechanism to control how many warnings you see, or turn them into exceptions (with warnings.simplefilter('error', iris.exceptions.FieldLoadFault)).

many thanks for the updates @ajdawson
please may you confirm that you think this is a backwards-compatible change, as discussed in
https://github.com/SciTools/iris/pull/1703#discussion_r35311225
(it looks like it to me)

I'd like to get this in, but I'm not entirely clear on how I should proceed here. What are your requirements for information about skipped fields @marqh? Would we really want a separate warning for each field? Or a warning with a list of fields (containing what information?)?

As long as there is enough information for a user to understand that they have lost something, I am happy
It would be good for me, as a user, to be able to browse the translation error reports
Does
https://github.com/SciTools/iris/pull/1703/files#diff-71a6ac4e2a835fb3910a8a8a8045474eR924
give me the report from the exception so I can get a clue about what I have lost?
Do i get enough information that I could run a
grib_dump -O
on  the message and see what it looks like
Perhaps having the filename and the message number so I can go hunting is enough
I hope this gives a few clues on what I have in mind.  Are any of these fairly easy to implement?
mark

If you turn warnings into exceptions, then it will fails at the first warning, which will be the first field, so no you would not be able to browse the full list of skipped fields. This sounds like a reasonable goal, but needs some thought on implementation.
An alternative would be one (possibly enormous) warning message detailing each skipped field, raising one warning would mean you'd get all the information if you turned warnings into exceptions. Other suggestions welcome.

@marqh & I have been kicking around a slightly different idea:
# Default behaviour just prints a single warning
>>> iris.load_cube(...)
__main__:1: FieldLoadFault

# Use a provided context manager to catch more detail.
# Detail could include filename, full exception/traceback, etc.
>>> with iris.fileformats.catch_faults() as faults:
...     iris.load_cube(...)
>>> print faults
[FieldLoadFault(filename='foo', message_id=3, error=<TranslationError....>),
FieldLoadFault(filename='foo', message_id=14, error=<TranslationError....>), ...]

# Can also use a context manager to state that no warnings are expected/wanted.
>>> with iris.fileformats.catch_faults(explode=True) as faults:
...     iris.load_cube(...)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TranslationError: ...

It doesn't seem possible to support this just by using warnings emitted from iris.fileformats.rules.load_cubes() (warnings don't preserve any non-standard attributes). But it does seem possible with slightly more custom handling within load_cubes().
The whole thing could be controlled via a completely independent FUTURE flag (e.g. "soft_translation") and would work with any format that used iris.fileformats.rules (removing the need for the new fault_tolerant argument).
@ajdawson - your thoughts on this are very welcome!

I like this idea, it makes for a nice simple way to handle the various cases. However, I've hit difficulties implementing it. I've got the whole structure working: a non-trivial subclass of warning with extra useful information attached, a context manager to catch the warnings if desired, all controlled by an iris.FUTURE option. The potential stumbling block I've hit is illustrated by this simple example:
import warnings

def foo():
    print('the function ran')
    warnings.warn('and produced a warning!', UserWarning)

if __name__ == '__main__':
    foo()
    warnings.simplefilter('always', UserWarning)
    foo()

You might expect this to produce two warnings, but it doesn't on Python 2. I believe this is to do with http://bugs.python.org/issue4180, which was closed by application of a fix to Python 3.4+. Indeed the above works as expected on Python 3. This is a problem in the context of this work, in fact your example above is a use case that wouldn't actually work:
# Default behaviour just prints a single warning
>>> iris.load_cube(...)
__main__:1: FieldLoadFault

# Use a provided context manager to catch more detail.
# Detail could include filename, full exception/traceback, etc.
>>> with iris.fileformats.catch_faults() as faults:
...     iris.load_cube(...)
>>> print faults
[]

Once the warning has been emitted once by the first load and registered, the filters are no longer checked by the warnings mechanism (it short circuits) so even though my implementation of catch_faults() sets the filter to "always" for FieldLoadFault I never get them again, so the list of reported faults would be empty even though there could be many faults...

For reference: https://github.com/SciTools/iris/compare/master...ajdawson:fault-tolerant-load-wip.

I don't think there's a (good) way to use warnings as the signal for all the different behaviours we want. Instead I'd add some explicit logic of our own and only raise warnings when they are wanted as the user-visible end result.
So after iris.fileformats.rules.load_cubes() has collected all the translation errors in skipped_fields perhaps something vaguely like:
if skipped_fields:
    if _translation_mode == _WARNING:
        warnings.warn('{} fields could not be ...'.format(len(skipped_fields)), ...)
    else:
        _translation_errors.extend(skipped_fields)

... where _translation_mode and _translation_errors are globals (thread-local if we're feeling keen) which are controlled by the context manager. (The context manager wouldn't do anything with warnings at all.)
We could also refer to _translation_mode as we're catching the original translation errors and re-raise if _translation_mode == _ERROR.

I don't think I'm going to be able to take this further for a good while. If someone else wants to take it forward in the mean time I have no objections.

I don't think I'm going to be able to take this further for a good while. If someone else wants to take it forward in the mean time I have no objections.

understood; I will try to get stuck in and see if I can implement the logic
thank you for all the efforts to date @ajdawson

Closing as this has become stale.


Hmusum/do not set health status up if redeploying apps at startup fails

First commit makes the unit tests work, but breaks unit tests in node-repository (RestApiTest).

Reverted MockLock change and @Ignored unit tests that is not working without fixing/changing MockLock.


Type {children} has no properties in common with type 'IntrinsicAttributes & ScrollViewProps'

Describe the bug
When using NestableScrolContainer with NestableDraggableFlatList,
Error occurs in NestableScrollContainer, but it's still working on iOS Simulator & Android Device.
Error : Type {children: Element[]} has no properties in common with type 'IntrinsicAttributes & ScrollViewProps'
Code Example:
<NestableScrollContainer>
    <View />
    // FlatList 1
    <View />
    <NestableDraggableFlatList>
    </NestableDraggableFlatList>
    // FlatList 2
    <View />
    <NestableDraggableFlatList>
    </NestableDraggableFlatList>
</NestableScrollContainer>

Platform & Dependencies
Please list any  applicable dependencies in addition to those below (react-navigation etc).

react-native-draggable-flatlist version: 3.1.0
Platform: Both
React Native or Expo version: 0.64.1
Reanimated version: 2.4.1
React Native Gesture Handler version: 1.10.3

can you create a snack that displays the issue? I cannot reproduce, and am confused about whether or not your example is complete--i.e. rendering a DraggableFlatList using opening/closing jsx with no props would throw an error for other reasons:
    <NestableDraggableFlatList>
    </NestableDraggableFlatList>

Sorry for confuse you, actual source code is written like this.
<NestableScrollContainer>
    <View />
    // FlatList 1
    <View />
    <NestableDraggableFlatList
        ...props
     />
    </NestableDraggableFlatList>
    // FlatList 2
    <View />
    <NestableDraggableFlatList
        ...props
     />
</NestableScrollContainer>

I'm at work right now, so it can be delayed, but i will create a snack ASAP.


Hash the appliance root password fails when password contains special characters

As the password argument to openssl is unescaped this command will fail when the password contains special characters.

Fixed in https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/pull/159


Create gx

@Kexw I have to close the request without merging. Please ensure you are familiar with this repository rules located at the bottom of this page and submit a new request with correct information. Thank you for the understanding!


What are the intentions and status of this project ?

This is currently the most complete implementation of something like the  Xamarin Forms and MAUI "Shell" for Avalonia.
But is this just an experiment ?
Is it still being developed?
Are there any future plans?
Is there something better or with a more promising future?
No judgement - I'd just like to know before I invest in using it too much.

Hello, Thanks for your interest.
. Let's say not experiment with the last version.
. Yes, it is still develop but I iterating my projects one by one. And I would like to receive PR for this.
. I still thinking of more platform UI experiments.
. Depends on what is the meaning of better. This library has already been used for several productions.
Any PR is welcome ...

I close this ticket because there is no activity for long time. Feel free to reopen it if you still have problem.


simulation.hpp and simulation_cec.hpp

Hi, please work on the branch v2021-cec in your fork, instead of master.

I specified commint  into EPFL-CS-472:v2021-cec from annaburds:master

Now is okay after you merged v2021-cec into master, though not a good practice. (You can leave it like this)

Okay,  I just got confused, but for sure I will not merge to master next time, Thank you!


styles: top search should use icon instead of text

Describe the bug
The top search bar on the search bar is using a button with the text "Search" instead of a magnifier glass.
Currently looks like this:

It should look like this:

Result when using the two linked PRs (cookiecutter and invenio-search-ui)


Gpf fixes

route server endpoints added to service bridge
service bridge ids filter support

Codecov Report

Merging #94 (03d1c57) into prep-release (0f9d5e0) will decrease coverage by 0.11%.
The diff coverage is 75.60%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@               Coverage Diff                @@
##           prep-release      #94      +/-   ##
================================================
- Coverage         78.45%   78.35%   -0.11%
================================================
  Files                42       43       +1
  Lines              1337     1377      +40
================================================
+ Hits               1049     1079      +30
- Misses              288      298      +10

Impacted Files
Coverage Δ

src/django_ixctl/rest/views/ixctl.py
86.46% <50.00%> (-1.14%)
:arrow_down:

...rc/django_ixctl/rest/serializers/service_bridge.py
76.92% <69.23%> (-3.85%)
:arrow_down:

src/django_ixctl/rest/views/service_bridge.py
66.25% <83.33%> (+3.01%)
:arrow_up:

src/django_ixctl/admin.py
70.96% <100.00%> (+0.96%)
:arrow_up:

...l/migrations/0015_alter_internetexchange_pdb_id.py
100.00% <100.00%> (ø)

src/django_ixctl/models/ixctl.py
75.00% <100.00%> (+0.06%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[BUG?] Newly-created-table has read-only grid

Creating a new table, then selecting and trying to change the value is not possible. I had to right-clink on the schema name and call "refresh" to have datagrid in read-write.

thanks for the bug report

It is not a bug. DBeaver doesn't refresh database metamodel on SQL exeucte.
We have a feature request for that: #7924


Update CC Workflow document as per walkthrough notes

I've attempted to update CC Workflow as per walkthrough notes
CC Issue template

CC issue template instructions were designed around the notion that the actual CC article would be submitted in the issue body.

I reduced this to very basic instructions, requesting a few pieces of specific details

I removed Pat as automatic assignee as we haven't had a discussion about this

Workflow document

After @rinkug walk-through, it was obvious there were many steps in the workflow where it was not clear who was responsible for making that step happen.
I tried to address above by adding Somehow as the designator of that task
Based on @rinku notes and simply re-reading, I wound up with several Somehows and that was not satisfying.
I feel like I am not sure what we are aiming for in this document now? Is it simply to explain to new EB Members how things work? To communicate with Submitters how content ideas get accepted or rejected? To document to Authors how to create content?
I feel like it kinda sorta touches on all these issues but not too well either and am wondering what is really essential here.
It feels like too many different people/roles are involved at too many different points in the workflow. It feels more complicated that issue work on actual software projects I work on.
More importantly, I feel that if we agreed to two things; a) bi-weekly content meetings in which we simply discuss new issues and b) assigning a responsible owner to marshall an issue from acceptance to completion, then while it is important to document how things are marshalled for newbies, it is easier to do that than it has been to get a final draft of this workflow document in place.

I like the new process for the following reasons:

I don't think relying on the EB to deal with requests on an add-hoc basis will work. Scheduling regular work sessions seems the best way to make sure that things actually get done.

It separates what needs to happen from how it is going to happen. I don't think we should get hung up on details about things like automation or we'll never get started.

I think a discussion about whether issues that have not received sufficient interest get closed as wontdo or just left in a pending state is warranted, but otherwise I think this is a good workflow.

Thank you for removing me as an assignee. I believe that happened during a walk through for illustration. I'm wondering about the points where we have wontdo's and also the point about waiting two weeks.
I like the idea of a bi weekly meeting, and think we could appoint someone to be looking at the pull requests during each two weeks so something that is ready to go early in the period gets the proper attention, i.e. a pull request gets merged in a timely fashion.

I've updated the alternative CC workflow as per today's discussion. Its easies to view the current version of that document but if you wanna leave comments or request revision, please do it here in the PR.
Here is summary of chnages

Added introductory remarks about the document essentially representing state transition squence of CC issues
Replaced use of wontdo label for content that did not ganer enough interest with a no-interest label (which has yet to be created)
Changed name of Development Backlog column here in the document with In Progress (thought we have to change the project board for this too)
Changed use of insufficient development label with no-development
Expanded the set of steps after PR is approved by reviewer but before it is merged to include editorial assistance review, possible author review of ea changes, etc.
Spell checked and corrected typos


Feature - Add TransactionLineItem.find_all/1

This creates the TransactionLineItem module and implements the find_all/1 action as documented here: https://developers.braintreepayments.com/reference/response/transaction-line-item/ruby
Tried to mostly stick with the style of the codebase :p.

Thanks for the PR! It's great to get the library closer to parity with the official versions.

Thanks @MainShayne233!


Temporary dir for gpu collection is not always unique among users

Short summary about the issue/question:
When running NNI, it puts the gpu metrics collector in /tmp/nni/script, which is not unique among users. So two people cannot run NNI simultaneously (for example on different GPU).
Brief what process you are following:
User 1: runs NNI fine
User 2: runs NNI on different port, but it'll give status error: "Training service error: EACCES: permission denied, open '/tmp/nni/script/gpu_metrics_collector.sh'"
How to reproduce it:
See above
nni Environment:

nni version: 1.0 (but also present in HEAD)
nni mode(local|pai|remote): local
OS: Ubuntu 18.04LTS
python version: 3.6
is conda or virtualenv used?:  Yes (conda)
is running in docker?: We run it in Singularity (github.com/sylabs/singularity/), with mounted /tmp as our containers itself are read-only. Redefining /tmp is not an option unfortunately (breaks too many other things it seems). Our containers are self-made from a ubuntu base, with conda, then pip install nni

need to update document(yes/no):
Maybe
Anything else we need to know:
Bug can be traced to line 435 - 437 of /src/nni_manager/training_service/remote_machine/remoteMachineTrainingService.ts
Clearly path.basename(os.homedir()); doesn't expand to username in our configuration, even though os.homedir() should work in our containers (homedir is mounted).
A solution would be to use either (/var)/run/user/$PID/, create a /tmp/$PID/ or add a random nonce to the path (for example trial id). Another solution would be allowing to specify your own temporary dir. Upstream at nodejs there might also be a fix possible to use the temporary dir supplied by systemd.

fixed, close.


optional command part at start not supported

Some instruments support optional command parts at the start of the command.
Example below is from BK Precision 8600 series:
[SOURce:]CURRent[:LEVel][:IMMediate] <NRf+>
The scpi lib supports the optional clauses LEVel and IMMediate.
I can't seem to make it work with the SOURce part at the start.
Error returned when I define the lib with the optional [SOURce:]
 -113,"Undefined header"

Try this pattern
[:SOURce]:CURRent[:LEVel][:IMMediate]

Perfect. That worked, Jan
Jan


Permalink sharing take two

This includes the frontend of the share that was previously merged & unmerged in
As well as a feature flag to hide sharing if merged into prod.
@DoSomething/front-end
@aaronschachter

Shippy ship ship. :shipit:

@aaronschachter added setting for facebook id & an update hook to remove the unused setting

:+1:


Fix fallback language ordering

Fixes a bug where dev language translations were taking precedence over other languages with translations earlier in the fallback ordering. The actual fix is just reversing the order of the language hierarchy array before spreading it here.
Have added some tests for this case too.

@mattcompiles Updated the changeset wording so it better represents what was actually fixed


cache wordpress admin wp-admin

very nice script but it cache wordpress admin.

Thanks, this script is made to reduce the burden of caching static files,
like css, js, png, jpg, because when you design, there are lot of files,
which reduce page loading speed.
But you can use gzip code to reduce the size of response
On 04-May-2017 10:35 PM, "Maxime Marquette"<EMAIL_ADDRESS>wrote:

very nice script but it cache wordpress admin.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/davinder17s/easy-gzip-cache/issues/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AEzb_dgYyq0XQiiR0pfiH2_ZqM0WOFejks5r2gVmgaJpZM4NQ9Lp
.

yes i know that but it should not cache wp-admin is there a way to take advantage of this but not make it cache wp-admin cause it break the wp-admin then.
Uncaught SyntaxError: Unexpected token <
i got that from gzip.php in my wp-admin.

Well, i guess you have not used .htaccess rewrite correctly

Please check example .htaccess in repository


PageError when page exists

import wikipedia

wikiResults = wikipedia.search("megaman 64")
result = wikiResults[0]
page = wikipedia.page(result)

When you run and access the first page which exists you get this error:
wikipedia.exceptions.PageError: Page id "mega man legends video games" does
not match any pages. Try another id!

Set auto_suggest to false to fix this issue.

https://github.com/goldsmith/Wikipedia/pull/177 to fix


Attempt to use history.pushState() more than 100 times per 30 seconds

Link to the question:
https://chat.bitcoinsearch.xyz/?author=holocat&question=What%2520is%2520OP_CODESEPARATOR

closed by #35


Better icons

Feature request
There are several Material Design Icons that could be used to give the *_status more visual distinctiveness, e.g. mdi:dishwasher and mdi:washing-machine. This could be extended to the binary sensors for info and error (there's a corresponding -alert variant, e.g. mdi:dishwasher-alert). Similar icons also exist for fridges, while for freezers, mdi:snow could be used (there are both -off and -alert variants of it).
Unfortunately, I've only found one icon for stovetops (mdi:stove) which does not have any of the variants. There also doesn't appear to be a specific icon for ovens (although the stove icon could be used, I guess).
What version of the integration are you using?
miele-0.0.10
Anything in the logs that might be useful for us?
No response
Additional information
No response

Most of this is taken care of on v0.1.4


Fix possible "IndexError" in "best_matching_lyric_url_from_query"

Not sure about the code-style your prefer (checking the length with if instead of try / catch, using else: instead of continue). Let me know if you want me to change it.
Fixes #807.

We aren't fixing v2. So sorry. We do appreciate the contributions though. Why no help make v3 better?
Consider you did anything for v2 is great (considering just how mucky v2 got)
So 👍👍👍


Sort functions and modules in documentation pages

Should be in the same order that they appear in the header files.

Disconnected from "Stable Setup" milestone, good enough for now.

Covered by #17, won't fix.


some train problem

Thanks for your work, I use kitty dataset and your method  to train a model.lr=0.0005,120000 iter,stepsize=20000,but i have the 48% auccury.can you give some advice?Thanks

@dlyldxwl hi, do you find the reason why the accuracy isn't high? I meet the similar problem.

@mna12478  i add input resolution to 416，and get some of conf layer weight as pretrain model，then acc still less 70，but improve to 65。finally，you can prune tradional conv layer weight  to ensure inference speed

@dlyldxwl thanks for your reply, but I have some questions and needs your help:

I follow the step in 'Train your own dataset' in https://github.com/chuanqi305/MobileNet-SSD, should I add some extra operation or should I change some deploy in the deploy files? For example, should I change the train.protxt file? I noticed that someone proposed to delete the '_new' in 'conv11_mbox_conf_new', 'conv13_mbox_conf_new','conv14_2_mbox_conf_new'.
When I finetune the model on MSCOCO, the training is very slow, or about 4 second an epoch, did you meet this problem?
I test the finetuned model on VOC0712, the result is shown in detect_eval, so what's the difference between the detect_eval and accuracy?

I'm a beginner in object detection.  I would very appreciate if you can help me.


Update machine-controller to v1.1.7

What this PR does / why we need it:
Updates the machine-controller to v1.1.7. The Cluster-API version is the same as for v1.1.5.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #416
Release note:
Update machine-controller to v1.1.7

/assign @kron4eg

/retest

There is a braking change in MC 1.1.7, I'm going to work on fix, in the meantime it makes sense to defer this PR until 1.1.8.

Also, in v1.1.7 — machine-controller got few GCE config expansions which we'd need to introduce also. So closing this PR for better support of MC.


Update example nginx configuration to ensure A+ SSL rating

Update example nginx configuration to ensure A+ rating using https://www.ssllabs.com/ssltest/

Merged; thanks!


Variable changes

Added keepalived_backup_priority variable
Made the config template actually use the priority variable(s)
Updated README and defaults to reference the new keepalived_backup_priority variable

Merging dozure changes


Cant change color icon and background tabbar preview and code

I try using light and dark mode,  but Cant change color icon and background Tab bar preview and code, because any colors.white, in  package  Tab(
child: ListTile(
leading: Icon(Icons.phone_android, color: Colors.white),
title: Text('Preview', style: TextStyle(color: Colors.white)),
),
),

and in the WidgetWithCodeView, codeLinkPrefix value can't  open website link url, just 404 not found?


Tab completion using powershell-git-aliases

System Details

posh-git version/path:1.1.0
PowerShell version:7.3.7
Git version:  2.35.1.windows.2
Operating system name and version: Windows 10

Issue Description
I am experiencing a problem with git Tab completion when using Powershell-git-aliases module , POSH-git is installed at user level.
Order of imports in Profile

Actual
gco [tab] -> It shows file names
Expected
gco [tab] -> should show branch names

I have the same problem. posh-git does not seems to know git-alias alias


Content research questions

Here’s the running content list just to track these: https://docs.google.com/document/d/1nUAVu_w3S6r57Urb3XWdJV2ci-JzG4_4nuq7veJWn6M/edit

@kenieh i think this topic also in design backlog, might want to pick one to delete
cc: @lauraykerr


Publish releases to maven central

Using Jitpack has the "small" inconvenient of making agile-architecture-documentation-system unusable from CI systems in big companies. That's sad, no?

Look at that ! https://mvnrepository.com/artifact/io.github.Riduidel.agile-architecture-documentation-system


Feature/6

What is this PR for?

[ ] Just updating content and/or documentation
[ ] This fixes issue #_____
[ ] Spot fix (no issue #)
[ ] Merging WIP feature #_____
[x] Merging done feature #6
[ ] This is a merge from a version branch
[ ] Adding/Updating tests
[ ] This is a conflict resolution
[ ] This is a branch cleanup
[ ] Other: ________________

I verify that...

[x] I have logged my time in the commits
[x] I have logged my time in this PR
[x] I have tagged all the relevant issues
[x] I am using VS Code for type checks and linting, or
[x] I have ran npm run test with no errors
[x] I have manually checked that this bug or feature is working

versioning 10m.