MVC Controler and View

Good Day
I want to know if it is possible to have your own mvc controller and views in serenity, I already have a controller and views I am getting routing errors when I include them in my solution.

Yes it is possible if course.
If you check previous issues will find usefull information.

Thanks for pointing that out, I find that it is possible to do what I asked
through the  *Endpoint.cs *file,
On 5 April 2018 at 18:27, brunobola<EMAIL_ADDRESS>wrote:

Yes it is possible if course.
If you check previous issues will find usefull information.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/volkanceylan/Serenity/issues/3438#issuecomment-378995538,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF6wd6CbrycdY_b9lJjJ5-zDkYVSptUNks5tlkXYgaJpZM4TICn_
.


Add thread name logging using JVMTI data

This can help annotate the thread ids.

JavaThread::thread_from_jni_environment(env_id)) is the method to call.

Consider the following course of action:
Handle ThreadStart/End by agent
On ThreadStart: use a lock free map to map thread* and thread's jvmtiEnv*, notify log_writer via queue to log jthread info using GetThreadInfo (requires jthread and  jvmtiEnv*)
On ThreadEnd: remove thread* from map, notify log_writer via queue to log thread end
On PROF signal: use the map to get jvmtiEnv*, this would help resolve issues on JVMs where GetEnv is not async safe.
In log writer: emit thread start/end entries with threadId to name mapping
This seems like a more correct use of the JVMTI API to acquire the env and thread info.
This requires the inclusion of a lockfree c++ map in Honest-Profiler


Make Error on building plugin

I had an error building this plugin on Fedora 33.
go version go1.14.6 gccgo (GCC) 10.2.1 20201125 (Red Hat 10.2.1-9) linux/amd64
[hfenner@lenovo oc-compliance]$ make
go build -o ./bin/oc-compliance github.com/JAORMX/oc-compliance/cmd
# github.com/JAORMX/oc-compliance/cmd
/usr/bin/ld: $WORK/b075/_pkg_.a(_go_.o): in function `github.x2ecom..z2fmodern..z2dgo..z2freflect2.loadGo15Types':
/home/hfenner/oc-compliance/vendor/github.com/modern-go/reflect2/type_map.go:42: undefined reference to `reflect.typelinks'
/usr/bin/ld: $WORK/b075/_pkg_.a(_go_.o): in function `github.x2ecom..z2fmodern..z2dgo..z2freflect2.discoverTypes':
/home/hfenner/oc-compliance/vendor/github.com/modern-go/reflect2/type_map.go:74: undefined reference to `reflect.typelinks'
/usr/bin/ld: $WORK/b075/_pkg_.a(_go_.o): in function `reflect2.loadGo17Types':
/home/hfenner/oc-compliance/vendor/github.com/modern-go/reflect2/type_map.go:78: undefined reference to `reflect.resolveTypeOff'
collect2: error: ld returned 1 exit status
make: *** [Makefile:17: bin/oc-compliance] Error 2

The go version seems to have been the issue.  I was running go1.14.6, and when I ran dnf install go, it installed go version go1.15.8 linux/amd64.  I was able to build and use the binary after I fixed this.

Thanks for the update! Glad it worked out


feat: Pose detection

Is your feature request related to a problem? Please describe:

The ML Kit Pose Detection API is not yet supported.
Describe the solution you'd like:

Add a Pose Detection plugin.
Describe alternatives you've considered:

Additional context:

This issue can be sponsored if interested. Please contact us in advance by email and mention the issue. PRs are also welcome.

@robingenz, note: I think the API is ready now. Would love to see some progress on this one - especially because this would be a bit different in terms of the input to the plugin, as the use cases using pose detection would more often than not require it to work on a video stream (loaded video or webcam).  Considering, all the other plugins are using processImage (besides translate), this would be very helpful!


[Enhancement] Search bar onClear when empty

This is a (multiple allowed):

[x] bug

[x] enhancement

[ ] feature-discussion (RFC)

Framework7 Version: 1.5.2

Platform and Target: Win10 Chrome 55, crosswalk cordova

Live Link or JSFiddle/Codepen: https://codepen.io/anon/pen/rjGjXQ

What you did
Added a searchbar set customSearch as true to initialise own search commands.
2 Things -

Tried to initialise onClear event by selecting X icon when there is no text as clear X icon is available when focused on the search input.
Initialised onClear event by selecting X icon when there is a search text string available - onClear initialises but does not display s.value the text that was cleared just shows the s.value is empty.

Expected Behavior
EXPLAIN WHAT IS TO BE EXPECTED, HERE.

When selecting clear ie X icon -  if there is no value added then onClear does not appear to be triggered but out of the box actions like hide the X icon occur - it would be nice if onClear could trigger so developers could add custom behavior/actions like the automatic removal of the X to other elements of the app..
Expected onClear to clear the value which it did - however expected it to return the value that was cleared in s.value

Actual Behavior
EXPLAIN WHAT IS ACTUALLY HAPPENING, HERE.

onClear does not get triggered if the user just selects X icon with no search string value.
OnClear value is empty expecting onclear s.value to have text that was cleared.

Add previous value for onClear method. As for the 1st point, use onDisable method/event in this case


Scope and time scheduling of the meeting for concept of a stand for empirical testing of composite structures (issue #1067 related)

The goal is to schedule the meeting in Teams calendar on 2024.12.10 at 20:15.

Meeting has been scheduled.


Merge release 2.6.0 into master

🗃 Github Issue Or Explanation for this PR. (What is it supposed to do and Why is needed)
no issue
✅ Checklist

[x] Github issue details are up to date for people to QA.
[x] I have tested all my changes.

🕵♂ Notes for Code Reviewer
Merge release into master.
👯♀ Paired with
"nobody"

Curious if there's a reason for a new brach as opposed to merging directly from release/2.6.0? 🤓


🚀 [Feature Request] - Add styles to improve UI of contact form

Is your feature request related to a problem ? Please describe. ✍
We might want to improve UI for the contact form for better user exp.
adding some icons and styles to the form might help.
Could you please assign this task to me under GSSoC '23. Thank You !
Describe briefly how you would implement this enhancement.
Some steps to implement this enhancement-
1. Adding appropriate icons for the input fields
2. adding a suitable bg for the form
3. changes in style of overall form.

Additional context or screenshots

Are you contributing for a program?
GSSoC2023
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

It has been updated already. Please see develoop branch on local


Improve Documentation

Markdown format documentation is not correct as imported from other source.

We have fixed many issues we will continue to work on this but will close the issue for now and will open separate issues per specific problems


npmrc parser fails on boolean props

Sandworm version
1.36.0
Describe the bug
When audit reads out the npm configuration, it fails if you have boolean properties in the .npmrc configuration:
❌ Failed: str.replace is not a function
TypeError: str.replace is not a function
    at replaceEnvVars (/home/user/.nvm/versions/node/v18.6.0/lib/node_modules/@sandworm/audit/src/registry.js:10:14)
    at /home/user/.nvm/versions/node/v18.6.0/lib/node_modules/@sandworm/audit/src/registry.js:19:28
    at Array.forEach (<anonymous>)
    at getRegistriesInfo (/home/user/.nvm/versions/node/v18.6.0/lib/node_modules/@sandworm/audit/src/registry.js:18:27)
    at loadRegistriesInfo (/home/user/.nvm/versions/node/v18.6.0/lib/node_modules/@sandworm/audit/src/registry.js:71:20)
    at setupRegistries (/home/user/.nvm/versions/node/v18.6.0/lib/node_modules/@sandworm/audit/src/registry.js:75:3)
    at getReport (/home/user/.nvm/versions/node/v18.6.0/lib/node_modules/@sandworm/audit/src/index.js:44:9)
    at exports.handler (/home/user/.nvm/versions/node/v18.6.0/lib/node_modules/@sandworm/audit/src/cli/cmds/audit.js:164:15)

Manifest files
Just add a boolean configuration property to your .npmrc file:
always-auth=false

To Reproduce
Just add a boolean configuration property to your .npmrc file:
always-auth=false

Expected behavior
Sandworm-audit should parse AND respect the available configuration settings from the different package managers. But at least from npm.
System (please complete the following information):

Node Version [v18.6.0]
Package Manager [npm]
Package Manager Version [8.19.2]
OS: [Ubuntu 22.04, WSL2]

Additional context
Add any other context about the problem here.

Hi @petrakow, thank you for reporting this!
The issue should be fixed in v1.36.1, let me know if it works for you.

Works great, thanks for the fast fix!


Auto-detect invalid casing linting issues

From #607, it appears invalid casing (Id instead of ID) linting issues are not being reported by our golangci-lint configuration.
Expected solution
If an invalid casing is detected, such as:
type Foo struct {
  Id string
}

Then, the linter should error and require the casing to be fixed:
type Foo struct {
  ID string
}

It seems like the var-naming check from revive may be the one which does this? It appears to be enabled though. I've tried tweaking its configuration, to no success though.


Investigate differences in Common Services versions between NMF and MAL C generated stubs

This seems to be causing an issue when trying to decode a ServiceFilter messages when using the Directory Service to retrieve Provider Ids (lookupProvider operation). The issue in question happens when getting the buffer string length while decoding the service provider Identifier, here (a very large erroneous number is fetched):
https://github.com/esa/CCSDS_MO_TRANS/blob/7539001de3c46fcc82e018436a01edeb61733722/CCSDS_MAL_ENCODING_BINARY/src/main/java/esa/mo/mal/encoder/binary/fixed/FixedBinaryDecoder.java#L212-L215
Here are some of the noted differences in the generated ServiceFilter code between NMF and MAL C:
a) Different list type for the required capabilities set
It's a UShort List in the latest CCSDS MO Common XML Specs, which is used to generate the MAL C stubs:
https://github.com/ccsdsmo/xml-service-specifications/blob/fac03edae4821d148ab70924ed20bf8b30fb9cdf/xml-ccsds-mo-standards/src/main/resources/xml/area003-v001-Common.xml#L267-L270
But in ServiceFilter.java for the generated Java stubs used by the NMF Supervisor it's UInteger List:
https://gitlab.com/esa/NMF/nanosat-mo-framework/-/blob/0067fb0420f4d12b6618beef8ab41c9e375b5a90/core/mo-services-impl/ccsds-common-impl/src/main/java/esa/mo/common/impl/provider/DirectoryProviderServiceImpl.java#L323-331
It's UShort in the Blue Book standard, see section 4.2.6 COMPOSITE: ServiceFilter, here:
https://public.ccsds.org/Pubs/522x0b1.pdf
b) Differences in field names

serviceProviderName (NMF) vs serviceProviderId
requiredCapabilities (NMF) vs requiredCapabilitySets

Notes

It seems like NMF implements a previous standard of the Commons Service, e.g. the implementation used by NMF matches the ServiceFilter specification in the Red Book standard:
https://public.ccsds.org/Lists/CCSDS 5220R1/522x0r1.pdf

Note that the are also differences in attribute names:

serviceProviderName vs serviceProviderId
requiredCapbilities vs requiredCapabilitySets

Most likely NMF is using a previous version of the Common services. In which case should NMF be updated or should the generated MAL C stubs match the previous version used by NMF?

Raise the issue on the NMF issue tracker:
https://gitlab.com/esa/NMF/nmf-issues/-/issues/1164


AttributeError for simple search_author() query

I had strange problem with a query for "KEVIN KORDANA"
>>> first = "kevin"
>>> last = "kordana"
>>> query_dict = {'authfirst': first, 'authlast': last}
>>> author_results = scopus.search_author(query_dict)
A total number of  2  records for the query.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "build/bdist.linux-x86_64/egg/pyscopus/pyscopus.py", line 67, in search_author
  File "build/bdist.linux-x86_64/egg/pyscopus/utils.py", line 38, in _parse_author
AttributeError: 'NoneType' object has no attribute 'find'

I'm on Ubuntu 14.04 using  with Python 2.7. I however don't know which version of pyscopus I am on as __version__ is not defined.

Updated version fixed this issue.


FR: Support repeated pack export

I looking at pack as something like a library. While developing it in local saltcorn installation I can export it several times. But in current implementation I have to select objects I want to export each time.
I want to have previous selection saved and prefilled on export page at least.
Even better could be named templates with such selections.
Somehow related thing is versioning of packs, but I'm not sure what implementation would be better.

I think tags interface could be used to fix this problem.
PS: I have gathered several pack-related issues and random thoughts together: https://wiki.saltcorn.com/view/ShowPage/packs-proposal


Update README.md

ADDING

@all-contributors please add @sudhanshutiwari264 for maintenance, review, doc and code

@all-contributors please add @archithdwij  for maintenance, review, doc and code

@all-contributors please add @Ak-Shaw  for maintenance, review, doc and code

@all-contributors please add @kiranbeeyes for eventOrganizing, maintenance, review, doc and code

@all-contributors please add @CrioDo  for eventOrganizing, maintenance, review, doc and code


Removed usage of deprecated React lifecycle methods

Updated code to work without using the now deprecated methods of componentWillMount and componentWillReceiveProps.
Fixes #118

Is this project still being actively maintained?

@oblador any chance of getting this merged and released?

@oblador bump, we would appreciate if you could merge this :)

This PR should be merged @oblador


API Problem translation based on Accept-Language?

I was wondering, would it make sense for apigiliy and api-problem in general to support a translator service, so as to translate all messages in the ApiProblem response based on the Accept-Language HTTP header?
This way in theory a multilingual rest client could get different error messages per language set in the request.
What do you think is the best way to go about it?

This repository has been closed and moved to laminas-api-tools/api-tools-api-problem; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-api-problem/issues/3.


Added support for disabling tracking via localStorage(umami.disabled=1)

Added support for disabling tracking via localStorage(umami.disabled=1)  (#103)

Thank you, Mario.
Looks great, I'll review and merge as soon as I can 👍.

LGTM :+1:.
Changes I made were mostly to the playground (changed the button to a toggle).
Let's merge when you're ready.

Looks good to me (just see the comment I'm not sure about the difference between the localStorage call via window and without, but if it works it's fine for me!)


⚠ Thumbnails API Endpoint has degraded performance

In 3de730d, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 3046 ms

Resolved: Thumbnails API Endpoint performance has improved in eafb172 after 7 minutes.


Fix some typos

These are just the ones noticed by codespell, plus whatever else I saw while getting there. There's definitely others I haven't caught, but this should be a good enough start :)
I wasn't sure what some of the typos are intended to be - see below:
https://github.com/neondatabase/neonvm/blob/3efd95a9b9f0379735d22bad0729965f4fcd4cdf/controllers/virtualmachine_controller.go#L523
(not sure whether it's "or" or "not")
https://github.com/neondatabase/neonvm/blob/3efd95a9b9f0379735d22bad0729965f4fcd4cdf/controllers/virtualmachinemigration_controller.go#L221
(not sure whether it's "what" or "want")
@cicdteam any ideas?

https://github.com/neondatabase/neonvm/blob/3efd95a9b9f0379735d22bad0729965f4fcd4cdf/controllers/virtualmachine_controller.go#L523
(not sure whether it's "or" or "not")

should be "or"

https://github.com/neondatabase/neonvm/blob/3efd95a9b9f0379735d22bad0729965f4fcd4cdf/controllers/virtualmachinemigration_controller.go#L221
(not sure whether it's "what" or "want")

should be "wait"

https://github.com/neondatabase/neonvm/blob/3efd95a9b9f0379735d22bad0729965f4fcd4cdf/controllers/virtualmachine_controller.go#L523

(not sure whether it's "or" or "not")

Probably it's "to"
https://github.com/neondatabase/neonvm/blob/3efd95a9b9f0379735d22bad0729965f4fcd4cdf/controllers/virtualmachinemigration_controller.go#L221

(not sure whether it's "what" or "want")

I think it's "wait"

Will be merged in https://github.com/neondatabase/autoscaling/pull/102


logwatch not reporting on asterisk

This is an example.
Subject: Logwatch for futel-stage (Linux)
Date: Fri,  3 Jun 2016 03:31:02 -0400 (EDT)
################### Logwatch 7.3.6 (05/19/07) ####################
Processing Initiated: Fri Jun  3 03:31:02 2016
Date Range Processed: yesterday
( 2016-Jun-02 )
Period is day.
Detail Level of Output: 0
Type of Output: unformatted
Logfiles for Host: futel-stage
##################################################################
--------------------- Postfix Begin ------------------------
5.756K  Bytes accepted                             5,894

10.808K  Bytes delivered                           11,067
========   ================================================
    2   Accepted                                 100.00%

    2   Total                                    100.00%

========   ================================================
    2   Removed from queue
    1   Delivered
    2   Sent via SMTP

---------------------- Postfix End -------------------------
--------------------- Disk Space Begin ------------------------
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        20G  2.0G   17G  11% /
---------------------- Disk Space End -------------------------
###################### Logwatch End #########################

we were getting duplicate script and conf dirs in /etc/logwatch


Can't resolve Kotlin extension due to type mismatch when upgrading to AGP 3.3.0-alpha06

I'm seeing the following compile error on view.clicks():
Unresolved reference. None of the following candidates is applicable because of receiver type mismatch:
public inline fun `MenuItem;`.clicks(): `Observable;`<Unit> defined in com.jakewharton.rxbinding2.view
public inline fun `MenuItem;`.clicks(handled: `Predicate;`<in `MenuItem;`>): `Observable;`<Unit> defined in com.jakewharton.rxbinding2.view
public inline fun `View;`.clicks(): `Observable;`<Unit> defined in com.jakewharton.rxbinding2.view

I've tested with both android.view.View and android.widget.TextView.
This error appeared when upgrading from AGP version 3.2.0-beta05 to 3.3.0-alpha06. I'm on Kotlin version 1.2.61.

This is similar to https://issuetracker.google.com/112806420 which likely means it's not a problem with this library or the KTX libraries but symptomatic of a larger problem. Please file a bug against the Android Gradle plugin, preferably with a small reproduction project.

Did you update Kotlin recently as well?


Use cpp_bin_float instead of cpp_dec_float

Since your research indicated that these methods both use integer math, I think cpp_dec_float would be better for currency applications.  What are your thoughts?


movies: stylistic changes

use cat instead of multiple echo
spacing
alignment

Will you be going through all of the tools one by one to add these changes? Still going to merge the two that you have submitted but was just curious.

I did the ones I used. If you wish so, I can go through all in the next couple of days.

If you are willing to do that, I would appreciate it and will merge the requests as they come through :+1:


CPP/error/ReverseNumber.cpp

rectify the error in the code.
NOTE:- Screenshot of the code and output is required.

Hello. Please Assign this to me

Please this assign this issue!

Done with the code! Check PR #301


nsq_to_file: SIGTERM not exiting

Hello! I'm using default implementation of nsq_to_file example and I have notices strange behavior of catching SIGTERM.
In my opinion, after catching SIGTERM, process should stop receiving new messages, sync opened files, close them and than stop. But it doesn't stop in real life, seems it opens new connections and continue working. Here are example of logs:
2015/07/09 15:24:07 INFO: opening FILENAME.log.gz
2015/07/09 15:24:07 INF    2 [stats_request/debug] stopping...
2015/07/09 15:24:07 INF    2 [stats_request/debug] (app_host:4152) received CLOSE_WAIT from nsqd
2015/07/09 15:24:07 INF    2 [stats_request/debug] (app_host:4152) beginning close
2015/07/09 15:24:07 INF    2 [stats_request/debug] (app_host:4152) readLoop exiting
2015/07/09 15:24:07 INF    2 [stats_request/debug] (app_host:4152) breaking out of writeLoop
2015/07/09 15:24:07 INF    2 [stats_request/debug] (app_host:4152) writeLoop exiting
2015/07/09 15:24:07 INF    2 [stats_request/debug] (app_host:4152) finished draining, cleanup exiting
2015/07/09 15:24:07 INF    2 [stats_request/debug] (app_host:4152) clean close complete
2015/07/09 15:24:08 INF    2 [stats_request/debug] stopping handlers
2015/07/09 15:24:08 INF    2 [stats_request/debug] rdyLoop exiting
2015/07/09 15:24:08 INF    2 [stats_request/debug] exiting lookupdLoop
2015/07/09 15:24:41 INF    1 [stats_request/debug] querying nsqlookupd http://loockup_host:4163/lookup?topic=topic_name
2015/07/09 15:25:01 INFO: new filename FILENAME2.log.gz, need rotate
2015/07/09 15:25:01 INFO: opening FILENAME2.log.gz

@shuler thanks for the report
Can you provide a larger section of the logs, if possible?  I'm a little confused by the output and need more context.  It looks like you might have found a bug, though.
I'll try to do some testing on my end as well, thanks.

@mreiferson Thank you for your response!
First of all, here are the arguments I use to run nsq_to_file:
--lookupd-http-address=loockup_host:4161 --output-dir=/Users/eugeneshulepin/nsq --topic=stats_request --gzip=true --consumer-opt=output_buffer_size,1024000 --max-in-flight=20000 --channel=debug --filename-format="<TOPIC>.<HOST>.1.<DATETIME>.<GZIPREV>.log" --datetime-format="%Y-%m-%d_%H-%M" --gzip --host-identifier=debug
And here is full log of output:
2015/07/09 23:13:45 INF    1 [stats_request/debug] querying nsqlookupd http://loockup_host:4161/lookup?topic=stats_request
2015/07/09 23:13:45 INF    1 [stats_request/debug] (n02-dc01-r05-u12-app-01:4152) connecting to nsqd
2015/07/09 23:13:45 INF    1 [stats_request/debug] (n02-dc01-r05-u13-app-02:4152) connecting to nsqd
2015/07/09 23:13:45 INF    1 [stats_request/debug] (n02-dc01-r05-u12-app-01:4150) connecting to nsqd
2015/07/09 23:13:45 INF    1 [stats_request/debug] (n02-dc01-r05-u12-app-01:4154) connecting to nsqd
2015/07/09 23:13:45 INF    1 [stats_request/debug] (n02-dc01-r05-u13-app-02:4154) connecting to nsqd
2015/07/09 23:13:45 INF    1 [stats_request/debug] (n02-dc01-r05-u13-app-02:4150) connecting to nsqd
2015/07/09 23:13:45 INF    1 [stats_request/debug] (n02-dc01-r05-u10-app-03:4152) connecting to nsqd
2015/07/09 23:13:45 INF    1 [stats_request/debug] (n02-dc01-r05-u10-app-03:4150) connecting to nsqd
2015/07/09 23:13:46 INF    1 [stats_request/debug] (n02-dc01-r05-u10-app-03:4154) connecting to nsqd
2015/07/09 23:13:46 INF    1 [stats_request/debug] (n02-dc01-r05-u11-app-04:4154) connecting to nsqd
2015/07/09 23:13:46 INF    1 [stats_request/debug] (n02-dc01-r05-u11-app-04:4150) connecting to nsqd
2015/07/09 23:13:46 INF    1 [stats_request/debug] (n02-dc01-r05-u11-app-04:4152) connecting to nsqd
2015/07/09 23:13:46 INF    1 [stats_request/debug] (n02-dc01-r05-u09-app-05:4152) connecting to nsqd
2015/07/09 23:13:46 INF    1 [stats_request/debug] (n02-dc01-r05-u09-app-05:4150) connecting to nsqd
2015/07/09 23:13:46 INF    1 [stats_request/debug] (n02-dc01-r05-u09-app-05:4154) connecting to nsqd
2015/07/09 23:13:46 INF    2 [stats_request/debug] querying nsqlookupd http://loockup_host:4161/lookup?topic=stats_request
2015/07/09 23:13:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4152) connecting to nsqd
2015/07/09 23:13:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4152) connecting to nsqd
2015/07/09 23:13:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4150) connecting to nsqd
2015/07/09 23:13:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4154) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4154) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4150) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4152) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4150) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4154) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4154) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4150) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4152) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4152) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4150) connecting to nsqd
2015/07/09 23:13:47 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4154) connecting to nsqd
2015/07/09 23:14:16 INFO: opening /Users/eugeneshulepin/nsq/stats_request.debug.1.2015-07-09_23-14.-000000.log.gz
2015/07/09 23:14:17 INFO: file already exists: /Users/eugeneshulepin/nsq/stats_request.debug.1.2015-07-09_23-14.-000000.log.gz
2015/07/09 23:14:17 INFO: opening /Users/eugeneshulepin/nsq/stats_request.debug.1.2015-07-09_23-14.-000001.log.gz
2015/07/09 23:14:46 INF    2 [stats_request/debug] stopping...
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4150) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4152) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4150) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4152) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4152) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4154) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4150) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4154) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4150) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4152) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4152) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4154) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4154) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4154) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4154) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4152) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4150) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4150) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4154) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4154) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4154) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4152) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4150) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4154) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4150) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4150) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4150) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4152) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4152) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4152) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4150) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4150) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4150) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4150) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4150) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4154) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4154) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4154) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4154) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4154) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4152) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4152) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4152) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4152) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4152) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4150) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4150) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4154) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4150) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4152) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4154) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4150) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4150) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4152) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4154) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4152) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4154) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4152) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4152) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4152) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4150) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4152) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4152) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4154) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4152) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4154) received CLOSE_WAIT from nsqd
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4150) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4152) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4154) beginning close
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4150) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4154) readLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4154) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4154) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4150) breaking out of writeLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4150) writeLoop exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4152) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4152) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4154) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4150) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4150) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4152) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4152) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4150) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4154) clean close complete
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 14 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4154) clean close complete
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 13 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4154) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4152) clean close complete
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4152) clean close complete
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4152) clean close complete
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 10 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4154) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4154) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4154) clean close complete
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 9 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4150) clean close complete
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 8 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4152) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4150) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4150) clean close complete
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 7 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4154) clean close complete
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 6 connections left alive
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 12 connections left alive
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 11 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4150) clean close complete
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 5 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u13-app-02:4150) clean close complete
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u12-app-01:4150) clean close complete
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4154) finished draining, cleanup exiting
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4152) clean close complete
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 3 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u09-app-05:4150) finished draining, cleanup exiting
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 4 connections left alive
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 2 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u11-app-04:4152) clean close complete
2015/07/09 23:14:46 INF    2 [stats_request/debug] (n02-dc01-r05-u10-app-03:4154) clean close complete
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 0 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] stopping handlers
2015/07/09 23:14:46 WRN    2 [stats_request/debug] there are 1 connections left alive
2015/07/09 23:14:46 INF    2 [stats_request/debug] exiting lookupdLoop
2015/07/09 23:14:46 INF    2 [stats_request/debug] rdyLoop exiting
2015/07/09 23:14:55 INF    1 [stats_request/debug] querying nsqlookupd http://loockup_host:4161/lookup?topic=stats_request
2015/07/09 23:15:16 INFO: new filename stats_request.debug.1.2015-07-09_23-15.<REV>.log.gz, need rotate
2015/07/09 23:15:16 INFO: opening /Users/eugeneshulepin/nsq/stats_request.debug.1.2015-07-09_23-15.-000000.log.gz
2015/07/09 23:15:55 INF    1 [stats_request/debug] querying nsqlookupd http://loockup_host:4161/lookup?topic=stats_request
2015/07/09 23:16:16 INFO: new filename stats_request.debug.1.2015-07-09_23-16.<REV>.log.gz, need rotate
2015/07/09 23:16:16 INFO: opening /Users/eugeneshulepin/nsq/stats_request.debug.1.2015-07-09_23-16.-000000.log.gz

what version of nsq_to_file are you using?

@mreiferson i'm using the latest one from repo https://github.com/bitly/nsq/blob/master/apps/nsq_to_file/nsq_to_file.go
In logs i can see that sigterm was caught properly, Consumer.Stop() was also called, but for some reason even after lookupdLoop exited, it seem to continue querying nsqlookupd.

@shuler for some reason it's opening a second Consumer instance - you can see this by the int increasing after the log severity, i.e. INF    1 vs. INF    2.  It's only supposed to do this when/if it finds multiple topics, but you're specifying only a single topic (stats_request) on the command line.
Can you double check the command line args you pasted and confirm they're correct?  Also, can you paste the output of curl -s http://<nsqlookupd_host>:4161/lookup?topic=stats_request?
Thanks!

@mreiferson It seems I've found a bug in flag parsing. I use nsq_to_file as part of my program, so flag.Parse() was called double times (one in my main.go and one if nsql_to_file), and there was duplicates of data in local variables lookupdHTTPAddrs and topics.
I will try to fix it locally, but I think that Consumer.Stop() should also work correct with several topics and lookups.

Ok, I tested it and the main bug was exactly in duplicate values in lookupdHTTPAddrs and topics slices. Even if I use nsq_to_file with several different topics and lookups - everything works great, seems there is some bug when you provide duplicates topics or lookupdHTTPAddrs

https://github.com/bitly/nsq/blob/master/apps/nsq_to_file/nsq_to_file.go#L535
Yes, nsq_to_file doesn't check duplicate topic names in arguments, and discoverer store only unique topics loggers

And another problem of course than https://github.com/bitly/nsq/blob/master/internal/app/string_array.go does not have idempotency like other flags

I will try to fix it locally, but I think that Consumer.Stop() should also work correct with several topics and lookups.

There is a 1:1 relationship between a Consumer and an NSQ topic - so Consumer.Stop() can't actually "stop" consumption of multiple topics.
You'll need to make sure you iterate over all your running Consumer instances and Stop each one.
Going to close this since it's not actually a bug in nsq_to_file.  Thanks!


Fixing some typos

Type of change

Documentation update

Description

Fixing some typos.

Thanks for the contribution!
Please sign your commit and re-push so that DCO passes. For instructions see https://github.com/hyperledger/fabric/pull/3175/checks?check_run_id=4844885423


[Addon]Fix: add upgrade crds parameter when upgrading addon

Description of your changes

Fixes #https://github.com/kubevela/kubevela/issues/3692
Checklist

I have:

[x] Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
[ ] Updated/Added any relevant documentation and examples.
[ ] New addon should be put in experimental.
[x] Update addon should modify the version in metadata.yaml to generate a new version.

Verified Addon promotion rules
If this pr wants to promote an experimental addon to verified, you must check whether meet these conditions too:

[ ] This addon must be tested by addon's e2e-test to guarantee this addon can be enabled successfully.
This addon must have some basic but necessary information.

[ ] An accessible icon url and source url defined in addon's metadata.yaml.
[ ] A detail introduction include a basic example about how to use and what's the benefit of this addon in README.md.
[ ] Also provide an introduction in KubeVela documentation.
[ ] It's more likely to be accepted if useful examples provided in example dir.

The CI environment has changed. Please rebase this pr with the master branch.


Fix: #8, Update diagrams to target sprout only

Keep only content related to Sprout and drop the rest for all C4 diagrams. Still WIP though.
Related to #8

@lwjohnst86 This PR has been open quite long. Should it be merged in or closed?

Yea, I'll close it for now and come back to it later.


Collections 763: Remove BloomFilter constructors that create initial entry

Removed constructors that took initial entry.
Added merge() methods for IndexProducer and BitMapProducer.
Added CountingBloomFilter.remove() methods for IndexProducer and BitMapProducer.
Moved implementations of ArrayCountingBloomFilter.merge() to default implementations in CountingBloomFilter
Moved implementations of ArrayCOuntingBloomFilter.remove() to default implementations in CountingBloomFilter
Updated tests accordingly
Added merge() tests.
Added remove() tests.

Codecov Report

Merging #331 (2264487) into master (fe783da) will decrease coverage by 0.05%.
The diff coverage is 82.85%.

@@             Coverage Diff              @@
##             master     #331      +/-   ##
============================================
- Coverage     86.01%   85.96%   -0.06%
+ Complexity     4675     4666       -9
============================================
  Files           288      289       +1
  Lines         13473    13444      -29
  Branches       1980     1978       -2
============================================
- Hits          11589    11557      -32
- Misses         1323     1327       +4
+ Partials        561      560       -1

Impacted Files
Coverage Δ

...ections4/bloomfilter/ArrayCountingBloomFilter.java
100.00% <ø> (ø)

.../collections4/bloomfilter/CountingBloomFilter.java
76.00% <76.00%> (ø)

.../commons/collections4/bloomfilter/BloomFilter.java
100.00% <100.00%> (ø)

...ns/collections4/bloomfilter/SimpleBloomFilter.java
92.64% <100.00%> (-1.61%)
:arrow_down:

...ns/collections4/bloomfilter/SparseBloomFilter.java
100.00% <100.00%> (+3.33%)
:arrow_up:

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

@Claudenw I merged this locally and was doing some minor code clean-up. It seems that there is a flaky test:
DefaultIndexProducerTest.testAsIndexArray
In AbstractIndexProducerTest.testAsIndexArray the producer is written to a list using asIndexArray. Then the producer forEach is called to remove entries from the list. However the default implementation of IndexProducer.asIndexArray removes duplicates (as it uses a BitSet to collate the indices). So the List can have less entries than the number produced by forEach (which contains the duplicates).
You are generating 10 values in the range [0, 512). The likelihood of no duplicates is (512)(511)(510)...(504)(503) / 512^10 = 0.915. So the probability of a duplicate is around 8.5%. If you checkout this current PR branch and run the DefaultIndexProducerTest repeatedly you will need to do it about 10 times to see a failure. This is low enough that the 4 CI builds may not hit a failure.
Q. Should asIndexArray eliminate duplicates? If this is the correct functionality then I can fix this test to handle the duplicates in forEach and complete the merge.

there is a method in defaultindexprovidertest that will remove dups from
the original array and sort it so that assert array equals can work.
In other tests I ran the main test in a loop 5k times to try to hit such
problems.  I must have missed this one
On Fri, Sep 9, 2022, 23:12 Alex Herbert @.***> wrote:

@Claudenw https://github.com/Claudenw I merged this locally and was
doing some minor code clean-up. It seems that there is a flaky test:
DefaultIndexProducerTest.testAsIndexArray
In AbstractIndexProducerTest.testAsIndexArray the producer is written to a
list using asIndexArray. Then the producer forEach is called to remove
entries from the list. However the default implementation of
IndexProducer.asIndexArray removes duplicates (as it uses a BitSet to
collate the indices). So the List can have less entries than the number
produced by forEach (which contains the duplicates).
You are generating 10 values in the range [0, 512). The likelihood of no
duplicates is (512)(511)(510)...(504)(503) / 512^10 = 0.915. So the
probability of a duplicate is around 8.5%. If you checkout this current PR
branch and run the DefaultIndexProducerTest repeatedly you will need to do
it about 10 times to see a failure. This is low enough that the 4 CI builds
may not hit a failure.
Q. Should asIndexArray eliminate duplicates? If this is the correct
functionality then I can fix this test to handle the duplicates in forEach
and complete the merge.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/commons-collections/pull/331#issuecomment-1242519168,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASTVHWX2B24XKAENBCDRC3V5OY55ANCNFSM57K4LUZQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I have found the index sorting and duplicate elimination routines. I know how to fix the test. The question is whether the test is indicating a problem. I think it is.
The default implementation of:

IndexProducer.forEach will return duplicates
IndexProducer.asIndexArray will not return duplicates

Is this the functionality we wish to support? If so then it should be documented. Currently there is no indication in the javadoc that asIndexArray is either sorted or distinct.
I can fix the test; I can add the documentation; but should this be done?
Looking at the overrides for asIndexArray:

ArrayCountingBloomFilter: will not return duplicates
EnhancedDoubleHasher: will return duplicates
HasherCollection: will return duplicates

Note that the two hashers have a code comment that they need to return duplicates.
So we have a contradictory functionality. BloomFilters and a default IndexProducer will produce sorted distinct indices for asIndexArray. Hashers will be unsorted and may contain duplicates. The HasherCollection can output a complete jumble of indices which make no practical sense. It could be modified to make the indices from each hasher unique, then duplicates will indicate multiple hashers produced the same index. However this is not supported in the forEach method and would be a performance overhead. Currently the HasherCollection thus acts as if one item but it is built from multiple hashers. This should be in the documentation to prevent the mistake that the collection will act as if it represents multiple items.
So is the suggested fix:

document that the default asIndexArray method will output distinct indices (current behaviour, but no contract for overrides)
update the test in DefaultIndexProducerTest.testAsIndexArray to remove duplicates from the expected array. This will then enforce the default behaviour that the indices are distinct

Note: this does not mandate that asIndexArray must always return no duplicates, only that the default implementation does.
Or:

document the asIndexArray method to state that indices may be duplicates (current behaviour)
update the test in DefaultIndexProducerTest.testAsIndexArray to be robust to duplicates

I would favour the second approach as it avoids a commitment to certain functionality and highlights that duplicates are possible. This has minimum impact on the rest of the code. I am happy to make the second change now and finish this merge.

IndexProducers may return duplicates and make no order guarantees.  (there used to be an order guarantee but we removed that).
Hasher based IndexProducers, by their nature, generally return unordered and possible duplicate values.  There is a hasher method to produce an IndexProducer that guaranteed uniqueness.
BloomFilter based IndexProducers, by their nature, generally return ordered and unique values, though I can think of implementations where the order may not be true, we don't have one.
The default implementation of IndexProducer uses BitSet in its implementation to simplify the code to produce the index list.  So the uniqueness is an artefact of the implementation.  If you have a fast implementation that can take the forEachIndex() and convert it to an array without imposing the uniqueness constraint then please implement that.
In short I concur with your assessment.
The HasherCollection is intended to simplify creation of some filters.  In practice it is that same as calling functions with hasher arguments once for each hasher in the collection.  Due to the difference between classes of Bloom filters (e.g. standard, counting, stable) there are times when the duplicates are required.
HasherCollections work well in distributed systems where an object is represented in a Bloom filter by hashes of multiple properties.  A for query across the systems a HasherCollection is constructed and passed to the endpoints.  The endpoints can then build filters based on the shape at the endpoint.  So the specific back end systems do not have to agree on shape, but do agree on Hash algorithm.

I have merged this in commit: 9a58c1bbdf7c65e71b33ab1ba406f1de5a8191df
I have made some further modifications. I updated the IndexProducer to document that the forEach and asIndexArray that Indices ordering and uniqueness is not guaranteed.
I have refactored the IndexProducer test so that the distinct and ordering behaviour can be asserted. Please check the current master. I found one bug which is currently disabled in BitCountProducerFromIndexProducerTest. If you create a BitCountProducer from an IndexProducer that has duplicates then the counts are not correct. Can you have a look and consider how to fix this, either by documentation that duplicate indices are ignored, or by actually correcting the counts.
Since an IndexProducer makes no guarantee on duplicates it may be fair to just state that the BitCountProducer will create a count of 1 even in the event of duplicates.


Migrate to new project system

The time has come to migrate away from the old *.csproj and project.json formats in favour of the new and improved *.csproj format that is supported by Visual Studio 2017 and Visual Studio Code
Todo
The following steps are required to be done on each repository

Migrate to the new project system using dotnet migrate (including adding missing projects and verify all tests) (@thecodejunkie)
Add Directory.build.props file and update all * .csproj files (see MiniProfiler for an example)
Add DisableImplicitFrameworkReferences element to all *.csproj for full-framework builds (see OwinHttpMessageHandler for an example)
Migrate back to netstandard1.3 again (need to update build.cake to reflect this, i.e all references of netstandard1.6)
Update build.cake to support running on Mono with the new project SDK (@akoeplinger confirmed that xbuild will no longer be able to build the new project format on mono`)
Update all test projects to use xunit 2.2.0 and xunit.runners.visualstudio 2.2.0

Adopting usage of NETStandard.Library

Add the DisableImplicitPackgeReference element and set it to true
Remove all our explicit package references for netstandard1.x TFM
Add an explicit reference to NETStandard.Library v1.6.1
Add what ever additional packages that we need that will not be part of NETStandard.Library

Demo projects
The only Nancy.Demo.* project that was ported to project.json was the new Nancy.Demo.Hosting.Kestrel project. Because of this, all other demo projects ends up with very bloated *.csproj files after dotnet migrate has been run on the projects. We need to clean these up and make them use the new, lighter, format
http://rehansaeed.com/cleaning-up-csproj/
Extra
Investigate using a single MSBuild invocation to speed up the execution time. Look at example https://gist.github.com/dasMulli/69f5303aa79a8cd4060e44891c90fd2d that was suggested by @dasmulli
Build script
Since we no longer can use xbuild to build using Mono on *nix, we are going to have to resort to using FrameworkPathOverride and defined at https://github.com/dotnet/netcorecli-fsc/wiki/.NET-Core-SDK-rc4#using-net-framework-as-targets-framework-the-osxunix-build-fails i.e we need to update build.sh to include
export FrameworkPathOverride=$(dirname $(which mono))/../lib/mono/4.5/

It needs to point to 4.5 because of how Mono is formed to store their artificats http://www.mono-project.com/docs/about-mono/releases/4.4.0/#class-libraries

Note: The 4.5 folder contains the actual assemblies that are used during runtime. We’re considering these the latest assemblies from now on, i.e. right now they’re implementing .NET 4.6.1. Unfortunately, we couldn’t rename this folder as too many apps and libraries hardcoded checks for this path.

Repositories
We need to go through all repositories and migrate them + update the build scripts

[ ] Nancy
[ ] Nancy.Bootstrappers.Autofac
[ ] Nancy.Bootstrappers.Ninject
[ ] Nancy.Bootstrappers.StructureMap
[ ] Nancy.Bootstrappers.Unity
[ ] Nancy.Bootstrappers.Windsor
[ ] Nancy.Serialization.JsonNet
[ ] Nancy.Serialization.ProtBuf
[ ] Nancy.Serialization.ServiceStack

This looks like a hell of an epic

@thecodejunkie If you can point me to a branch  where you have done one, I can help out.

@Sphiecoh I'm currently exploring a bit on my machine to get an idea of exactly what we want to do and how we do it. Once I've nailed all of that down, then I will complete the main Nancy repo and then we can take community help for the remaining repositories. 👍

@cemremengu I'm using this as a semi-structured brain dump of stuff I can think of or come across while working on this 😄


Make it easy to spot missing-import errors

One type of error is fairly common with Polymer; forgetting to import a component definition. In most programming languages, this results in an "undefined" error, but since Custom components allows registering after the fact, there is no clue. And the element is simply rendered as nothing.
It would be nice to have a debug/linting mode where unresolved elements are printed to the console, or highlighted in the DOM somehow. It could be triggered by a timer set at page load to account somewhat for delayed registrations. Or in "polymer-ready". The output would be just a list of unresolved elements (and possibly their source location, if possible.)
BTW, this is somewhat similar to the problem of printing error messages for unhandled exception in Twisted Python's Deferreds... They do it in the destructor, so if nothing has handled the exception, it will likely get shown at some point.

@addyosmani @ebidel Does polylint cover this case?

Yep! github.com/polymerlabs/polylint covers this


rat is too loud

@chrischrischris complains that rat is listing all excludes each time and i stumbled on https://issues.apache.org/jira/browse/RAT-241.
Will bump the version.

Fixed with #50


Issue #52872 Update text and hint for

Learn localStorage by Building a Todo App - Step 58: Specify code requirement
Checklist:

[x] I have read and followed the contribution guidelines.
[ ] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #52872

Update the text and hint for all languages and tested in gitpod
Screenshots Of Updates Text And Hint For Reference

Make Changes In English File As Mentioned , Please do review and let me know if any other changes required .

Hi @v-i-k-a-s !
I have updated the title of your post to something more descriptive so the maintainers will know what this PR is about at first glance.
You want to avoid creating PR titles like "Issue #xxxx" because there are close to 300 open issues and it doesn't really describe what this PR is about.
It is always best to be descriptive in your PR titles and follow the conventions laid out by the project.
You can learn more about that here
https://contribute.freecodecamp.org/#/how-to-open-a-pull-request?id=prepare-a-good-pr-title
Hope that helps


Services settings

Modifies services.py.j2 for services and for filter

Has this been tested? I can't immediately see where the db_host and db_port variables are set for the lasair_service role (for the filter they are set in deploy.yaml)

Tested with the settings.py in pace. But not the templating part, I dont know how to do that except when deploying an entire cluster. I thought db_port and db_host were available for all the templating operations.


Add Azure DevCenter Package

Packages impacted by this PR
@azure-rest/developer-devcenter
Issues associated with this PR
https://github.com/Azure/azure-sdk/issues/4702
Describe the problem that is addressed by this PR
There is not an existing package for the Azure DevCenter service :)
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
N/A
Are there test cases added in this PR? (If not, why?)
Yes, test coverage for service hero scenarios
Provide a list of related PRs (if any)
N/A
Command used to generate this PR:**(Applicable only to SDK release request PRs)
N/A
Checklists

[x] Added impacted package name to the issue description
[x] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the Autorest/typescript repository and link it here)_No, but linked issue for the test recorder: https://github.com/Azure/azure-sdk-for-js/issues/23420.
[x] Added a changelog (if necessary)

@MaryGao Let us know of any other issues we can resolve! Appreciate your feedback here :)

@qiaozha Could you help provide your comments? Thanks!

/azp run prepare-pipelines

/azp run js - devcenter - ci

/azp run js - devcenter - ci

If your package is the first time to enable pipeline pls run the above command to trigger it.
I notice there exists the ci error https://dev.azure.com/azure-sdk/public/_build/results?buildId=1922720&view=logs&j=b70e5e73-bbb6-5567-0939-8415943fadb9&t=a880e989-7d1a-5c96-a41f-d540b383cc43.
This is caused the unknown keyword devcenter and devboxes.  @chrissmiller Could you confirm that these keywords are reviewed and agreed in arch board review?
If so please add them to file https://github.com/Azure/azure-sdk-for-js/blob/main/.vscode/cspell.json#L203-L206 to bypass this check.

/azp run js - devcenter - ci

If your package is the first time to enable pipeline pls run the above command to trigger it.
I notice there exists the ci error https://dev.azure.com/azure-sdk/public/_build/results?buildId=1922720&view=logs&j=b70e5e73-bbb6-5567-0939-8415943fadb9&t=a880e989-7d1a-5c96-a41f-d540b383cc43.
This is caused the unknown keyword devcenter and devboxes. @chrissmiller Could you confirm that these keywords are reviewed and agreed in arch board review?
If so please add them to file https://github.com/Azure/azure-sdk-for-js/blob/main/.vscode/cspell.json to bypass this check. You could read more here https://github.com/Azure/azure-sdk-tools/blob/main/doc/common/spellcheck.md.

@MaryGao FYI, those terms were approved by Arch Board, so I will proceed with adding them to cspell.json. (cc @chrissmiller as well)

/azp run js - devcenter - ci

/azp run js - devcenter - ci

/azp run js - devcenter - ci

Please notice you don't need to run the pipeline manually if you set up them correctly. The ci will be triggered automatically if you push any change in your pr.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-rest-developer-devcenter


Need .isDistinctFrom / .isNotDistinctFrom query expression operators

Is your feature request related to a problem? Please describe.
The SQL operator "column" <> 'value' fails to match any NULL value, even though NULL is not equal to 'value'. You need to use IS DISTINCT FROM to cause not-equals matching to succeed against NULL values.
This is not supported in the query expression syntax right now. We need a .isDistinctFrom query operator. (The opposite is .isNotDistinctFrom, and this should be supported too.)
I guess the alternative is to automatically use IS NOT DISTINCT FROM for nullable types when calling .equals, and use IS DISTINCT FROM for nullable types when calling .notEquals...

We actually already use your suggested solution. When calling .notEquals on a nullable column with a not NULL value we create an IS DISTINCT FROM  expression that also ensures that NULL values are matched.
Link to code: https://github.com/serverpod/serverpod/blob/534a76241c4349780b8cb39b86914e67784d4803/packages/serverpod/lib/src/database/columns.dart#L274C4-L274C4
Did you run into an issue while using the .notEquals(..) operator?

Oops, sorry, I missed that...
No, I was trying to write queries by hand in SQL and then translate them to the Serverpod API, and I needed IS DISTINCT FROM at one point. I wrongly assumed that .equals would just be the standard equals operator (and same for not equals). This should be clearly documented if it's not already.


Align logos nicely with attribution text

Currently, when not using Bootstrap and a css like the one we use in the examples, logos in the attribution do not align nicely with the attribution text.
Before:

After:

LGTM @ahocevar

This has bugged me quite a while! Thanks @ahocevar !

Three years of work, and we have aligned the logo!!  Thanks @ahocevar.


[read-fonts] capture full range of image data in cblc

These can be sparse which requires reading offset and offset +1 to compute the full range.
ref https://skia-review.googlesource.com/c/skia/+/809056

👍  thanks for the fix! I guess it's time for me to roll some versions, into Chromium as well, with bytemuck and all.


Removed 'partners' as few other .json files had 'partners' in them.

Thanks for submitting a pull request! Below are a few things you can do to help us more quickly review your changes.
Checklist
I have…

[x] run the application locally (./scripts/serve) and verified that my changes behave as expected.
[x] run the build process locally (./scripts/build) and make sure it builds correctly.
[x] run the test suite (./scripts/test) and verified that all tests pass.
[x] summarized below my changes and noted which issues (if any) this pull request fixes or addresses.
[ ] thoroughly outlined below the steps necessary to test my changes.
[ ] attached screenshots illustrating relevant behavior before and after my changes.
[ ] read, understand, and agree to the terms described in CONTRIBUTING.md.
[ ] added my name, email address, and copyright date to CONTRIBUTORS.md.

Summary of Changes
This pull request…

Summarize change number one.
Summarize change number two.
etc. etc. etc.

Testing
To verify the changes proposed in this pull request…

Describe testing step one.
Describe testing step two.
etc. etc. etc.

Screenshots
Attach relevant before and after screenshots here.

Heh... fun story, I have a separate PR in for this field because it doesn't follow the proper code.gov format. Would you rather fix it or remove it?

May as well remove it to be consistent with all the other projects.  I don't have email addresses for the organizations either.
-Morris Berman
<EMAIL_ADDRESS>Morris Berman
(301)394-4188 (V, ALC)
(301)873-7975 (Mobile)
(301)394-1801 (FAX)
U.S. Army Research Laboratory
ATTN: FCDD-RLS-DP (Power Conditioning Branch) (Morris Berman)
2800 Powder Mill Road
Adelphi, Maryland 20783-1145
-----Original Message-----
From: Jordan Kasper<EMAIL_ADDRESS>Sent: Wednesday, November 13, 2019 10:11 AM
To: Code-dot-mil/code.mil<EMAIL_ADDRESS>Cc: Berman, Morris S CIV USARMY FUTURES COMMAND (USA<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: [Non-DoD Source] Re: [Code-dot-mil/code.mil] Removed 'partners' as few other .json files had 'partners' in them. (#259)
All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.

Heh... fun story, I have a separate PR in for this field because it doesn't follow the proper code.gov format. Would you rather fix it or remove it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub < Caution-https://github.com/Code-dot-mil/code.mil/pull/259?email_source=notifications&email_token=ANJNMNQWIA45UZ2JXEUVGMDQTQKILA5CNFSM4JM4VQTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED6ORBQ#issuecomment-553445510 > , or unsubscribe < Caution-https://github.com/notifications/unsubscribe-auth/ANJNMNQRZQ3TW57R2MIDKJTQTQKILANCNFSM4JM4VQTA > . Caution-https://github.com/notifications/beacon/ANJNMNS6RX46HUC6VBDQCZLQTQKILA5CNFSM4JM4VQTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED6ORBQ.gif

Don't worry about consistency, be a trend setter! The field exists in the schema for a reason. :)
That said, happy to remove it if you want.

I don't want to be the nail that sticks up and gets hammered back down! :-)
I'm good with removal.
-Morris Berman
<EMAIL_ADDRESS>Morris Berman
(301)394-4188 (V, ALC)
(301)873-7975 (Mobile)
(301)394-1801 (FAX)
U.S. Army Research Laboratory
ATTN: FCDD-RLS-DP (Power Conditioning Branch) (Morris Berman)
2800 Powder Mill Road
Adelphi, Maryland 20783-1145
-----Original Message-----
From: Jordan Kasper<EMAIL_ADDRESS>Sent: Wednesday, November 13, 2019 10:20 AM
To: Code-dot-mil/code.mil<EMAIL_ADDRESS>Cc: Berman, Morris S CIV USARMY FUTURES COMMAND (USA<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: [Non-DoD Source] Re: [Code-dot-mil/code.mil] Removed 'partners' as few other .json files had 'partners' in them. (#259)
All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.

Don't worry about consistency, be a trend setter! The field exists in the schema for a reason. :)
That said, happy to remove it if you want.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub < Caution-https://github.com/Code-dot-mil/code.mil/pull/259?email_source=notifications&email_token=ANJNMNXRWQXS5I3DPIL7OP3QTQLLFA5CNFSM4JM4VQTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED6PRLY#issuecomment-553449647 > , or unsubscribe < Caution-https://github.com/notifications/unsubscribe-auth/ANJNMNTOGDVNRM3HREJ3RELQTQLLFANCNFSM4JM4VQTA > . Caution-https://github.com/notifications/beacon/ANJNMNVIJAM6HKY6DE6MGY3QTQLLFA5CNFSM4JM4VQTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED6PRLY.gif


Improve benchmark script - add other vector search libraries and download full results

What
Improve benchmark script:

Add other vector search libraries.
Download full results.
Use env variable for your key name and path.
Update to 30GB of storage b/c otherwise we would OOM when installing and running all the other vector search libraries.
Update the results dir to store a new directory with the datetime in the path for each run.

Testing
It was working, but something changed and now the tiledb docker install fails. I think it's still nice to move forward with getting this checked in, as once I fix that issue in ann-benchmarks it will work again.

Looks good! Just wondering why some of the benchmarks are failing?

Some seem to be failing even in their CI (sample run here) and for others I believe we may need to pin specific Python packages, though not quite sure.


functionapp: Proxy returns 407 when default credentials supplied

Describe the bug
While behind a corporate proxy as defined in the HTTP_PROXY and HTTPS_PROXY environment variables as defined as "http://proxyhost:port", I am able to login using az login but as soon as I try to deploy a functionapp using something like az functionapp deployment source config-zip -g resourceGroup -n \functionAppName --src zipfile.zip I receive a 407 proxy authentication required stacktrace. The full stacktrace is as follows:
HTTPSConnectionPool(host='hostobfiscatedhereonpurpose', port=443): Max retries exceeded with url: /api/zipdeploy?isAsync=true (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 407 authenticationrequired',)))
Traceback (most recent call last):
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\urllib3\urllib3\connectionpool.py", line 594, in urlopen
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\urllib3\urllib3\connectionpool.py", line 805, in _prepare_proxy
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\urllib3\urllib3\connection.py", line 308, in connect
  File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\http\client.py", line 919, in _tunnel
    message.strip()))
OSError: Tunnel connection failed: 407 authenticationrequired

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\requests\requests\adapters.py", line 449, in send
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\urllib3\urllib3\connectionpool.py", line 638, in urlopen
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\urllib3\urllib3\util\retry.py", line 398, in increment
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='hostobfiscatedhereonpurpose', port=443): Max retries exceeded with url: /api/zipdeploy?isAsync=true (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 407 authenticationrequired',)))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\knack\knack\cli.py", line 206, in invoke
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\azure-cli-core\azure\cli\core\commands\__init__.py", line 346, in execute
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\six\six.py", line 693, in reraise
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\azure-cli-core\azure\cli\core\commands\__init__.py", line 320, in execute
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\azure-cli-core\azure\cli\core\commands\__init__.py", line 169, in __call__
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\azure-cli-core\azure\cli\core\__init__.py", line 440, in default_command_handler
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\azure-cli-appservice\azure\cli\command_modules\appservice\custom.py", line 262, in enable_zip_deploy
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\requests\requests\api.py", line 116, in post
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\requests\requests\api.py", line 60, in request
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\requests\requests\sessions.py", line 533, in request
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\requests\requests\sessions.py", line 646, in send
  File "C:\Users\VSSADM~1\AppData\Local\Temp\pip-install-e5ce5s7r\requests\requests\adapters.py", line 510, in send
requests.exceptions.ProxyError: HTTPSConnectionPool(host='hostobfiscatedhereonpurpose', port=443): Max retries exceeded with url: /api/zipdeploy?isAsync=true (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 407 authenticationrequired',)))

However, if I set environment variables to "http://username:password@proxyhost:port" I am able to deploy without issue. While I agree that I have a workaround, I would prefer to not specify my username and password in my environment variables due to my organizations rotating password requirements.
To Reproduce

Install latest Azure CLI on Windows 10 (as of posting, 2.0.52)
Set HTTP_PROXY and HTTPS_PROXY environment variables to a proxy server which doesn't require username and password to be defined (an NTLM proxy?)
Login to the cli using az login
Attempt to deploy using az functionapp deployment source config-zip -g resourceGroup -n \functionAppName --src zipfile.zip

Expected behavior
az functionapp should honor authentication on the proxy the same way that the az login command works. A 407 proxy authentication required error should not be thrown
Environment summary
Install Method: MSI
CLI Version: 2.0.52
OS: Windows 10
Console: Powershell

Recommended labels: Functions-cli, Workaround
Recommended priority: Minor (since there is a workaround).

This workaround does not work for me.  With proxy environment variables defined, attempting to login az login I get:
Please ensure you have network connection. Error detail: HTTPSConnectionPool(host='login.microsoftonline.com', port=443): Max retries exceeded with url: /common/oauth2/token (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 407 authenticationrequired',)))

@jonlorusso, using HTTP_PROXY and HTTPS_PROXY requires the proxy to work without authentication or with basic authentication. They don't work with NTLM authentication.

Due to the poor support of NTLM in Python community, this 407 issue has been mentioned in all 3 libraries which Azure CLI relies on: https://github.com/pypa/pip/issues/1182, https://github.com/psf/requests/issues/2036, https://github.com/urllib3/urllib3/issues/242
Adding requests-ntlm in msrest is not practical at the moment. cc @lmazuel
There seems to be these solutions (I don’t have an NTLM environment so I can’t do the test):

cntlm, mentioned by https://github.com/pypa/pip/issues/1182#issuecomment-40735838, but this project has been out of maintenance for years
ISA firewall client, mentioned by https://github.com/pypa/pip/issues/1182#issuecomment-40759312, but the download link is down and it doesn't seem to support Windows 10
Fiddler, mentioned by https://github.com/pypa/pip/issues/1182#issuecomment-104512031, but Python doesn’t trust Fiddler’s root certificate which requires extra steps to configure root CA on Azure CLI for Fiddler's root certificate
Use Cloud Shell on Azure Portal (recommended)
Use an Azure VM as a jump server and install Azure CLI on that machine (recommended)

Please let us know if you can get unblocked.


not compiling for windows

Hi! Can you elaborate? What kind of errors do you see?

right now it misses
 #include <CRTDEFS.H>

yesterday i had even more issues though.


feat(elements): <Loading> component

Description
Adds a <Loading> component. Access the loading state of a chosen scope. Scope can refer to a step, a provider, or the global loading state. The global loading state is true when any of the other scopes are loading.
Example:
<Step name="start">
  <Submit>
    <Loading scope="step:start">
      {(isLoading) => isLoading ? "Loading..." : "Submit"}
    </Loading>
  </Submit>
</Step>

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

!snapshot

Hey @LekoArts - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
1.0.1-snapshot.vc487a9b

@clerk/chrome-extension
1.0.1-snapshot.vc487a9b

@clerk/clerk-js
5.0.1-snapshot.vc487a9b

@clerk/clerk-expo
1.0.1-snapshot.vc487a9b

@clerk/fastify
1.0.1-snapshot.vc487a9b

gatsby-plugin-clerk
5.0.1-snapshot.vc487a9b

@clerk/localizations
2.0.1-snapshot.vc487a9b

@clerk/nextjs
5.0.1-snapshot.vc487a9b

@clerk/clerk-react
5.0.1-snapshot.vc487a9b

@clerk/remix
4.0.1-snapshot.vc487a9b

@clerk/clerk-sdk-node
5.0.1-snapshot.vc487a9b

@clerk/shared
2.0.1-snapshot.vc487a9b

@clerk/themes
2.0.1-snapshot.vc487a9b

@clerk/types
4.0.1-snapshot.vc487a9b

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/backend
npm i<EMAIL_ADDRESS>--save-exact

@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@clerk/fastify
npm i<EMAIL_ADDRESS>--save-exact

gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>--save-exact

@clerk/localizations
npm i<EMAIL_ADDRESS>--save-exact

@clerk/nextjs
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-react
npm i<EMAIL_ADDRESS>--save-exact

@clerk/remix
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>--save-exact

@clerk/shared
npm i<EMAIL_ADDRESS>--save-exact

@clerk/themes
npm i<EMAIL_ADDRESS>--save-exact

@clerk/types
npm i<EMAIL_ADDRESS>--save-exact


"Cannot have same delimiter and list delimiter of \u0001"

When I used hadoop to absorb data, I used DelimitedParser to parse the row. The delimiter I set was \u0001, but the following error was reported to me:"Cannot have the same delimiter and list delimiter of \u0001".
I looked at the source code of the DelimitedParser and found that in the constructor, the delimiter and listDelimiter are checked to see if they are equal, and if so, an error will be reported.I did not set the value of listDelimiter, which is also the default value: \u0001, so this error was reported.To solve this problem, I specifically specified other values in the listDelimiter so that the program could pass.
May I ask if there is any problem with the design of this piece?

Hi @aoeiuvb,
This behavior is intentional and is due to the fact that we have two kinds of delimiters: the field delimiter and a "list delimiter" within a field (in case your field is actually a list of separate values). The delimiters cannot be the same, since then we can't parse a row. I think setting the listDelimiter to some other value, like you did, is a good way to go.

Btw, I closed this since I think I answered your question, but feel free to post again if you are wondering something.


Adding a 3D LUT (.cube file) to a MTLTexture?

Checklist

[x] I've read the README
[x] I've searched for existing GitHub issues

I am currently playing around with FxPlug - the effects engine for Apple's Final Cut Pro and Motion.
I am currently exploring if I can use MetalPetal to apply a 3D LUT (i.e. a .cube file) to a MTLTexture in Swift.
It looks like I might be able to use MTIColorLookupFilter() to apply a LUT - but it looks like it only accepts a LUT as a MTIImage - not a LUT file.
So I'd need to use something like CocoaLUT to convert the LUT file into an image. It looks like CocoaLUT can also generate Core Image Filters (VVLUT1DFilter / CIColorCube) from LUTs.
Have anyone played with using file-based LUTs with MetalPetal? Any words of wisdom?

I used CocoaLUT to get a CI image filter from a .cube file:
let lut: LUT = LUT(from: Bundle.main.url(forResource: "TestLUT", withExtension: "cube")!)!
let filter = lut.coreImageFilterWithCurrentColorSpace()

Then to process the LUT:
  let filter = MTICoreImageUnaryFilter()
  filter.filter = LUTManager.shared.filter
 filter.inputImage = inputImage
let result = filter.outputImage

Amazing, thank you! Will check it out!


Fixed minor coding style issues

What changes were made:
Refactored code to adhere to Coding Style sheet
What are the relevant JIRA tickets:
The relevant JIRA ticket is 95.
How can these changes be tested(test #?):
These changes should not have to be tested. Only coding style was fixed.
Comments:

Did this add white space between comments above methods? I don’t like that...


Added Biohacking list in Security

[https://github.com/mafiaguy/awsome-biohacking]
[This is a primer with the maximum amount of data as I may realize on completely different aspects of the biohacking community.]
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Hi,
@mafiaguy  Please lint your list with this command  awesome-lint https://github.com/mafiaguy/awsome-biohacking and resolve your issues, currently there are these issues in your list:
 ×    1:1    Git repository must be at least 30 days old                     remark-lint:awesome-git-repo-age
  ×    1:1    The repository should have a description                        remark-lint:awesome-github
  ×    1:1    The repository should have "awesome" as a GitHub topic          remark-lint:awesome-github
  ×    1:1    The repository should have "awesome-list" as a GitHub topic     remark-lint:awesome-github
  ×    1:1    License was not detected by GitHub                              remark-lint:awesome-github
  ×    1:1    Missing content headers                                         remark-lint:awesome-toc
  ×   16:4    Text "Youtube" should be written as "YouTube"                   remark-lint:awesome-spell-check
  ×   23:1    Don’t use multiple top level headings (1:1)                     remark-lint:no-multiple-toplevel-headings
  ×   23:1    List can only have one heading                                  remark-lint:awesome-heading
  ×   24:93   List item link and description must be separated with a dash    remark-lint:awesome-list-item
  ×   24:249  "’" is used without matching "‘"                                remark-lint:match-punctuation
  ×   26:112  List item link and description must be separated with a dash    remark-lint:awesome-list-item
  ×   28:101  List item link and description must be separated with a dash    remark-lint:awesome-list-item
  ×   30:63   List item link and description must be separated with a dash    remark-lint:awesome-list-item
  ×   32:34   List item link and description must be separated with a dash    remark-lint:awesome-list-item
  ×   34:72   List item link and description must be separated with a dash    remark-lint:awesome-list-item
  ×   36:92   List item link and description must be separated with a dash    remark-lint:awesome-list-item
  ×   38:1    Don’t use multiple top level headings (1:1)                     remark-lint:no-multiple-toplevel-headings
  ×   38:1    List can only have one heading                                  remark-lint:awesome-heading
  ×   66:1    Don’t use multiple top level headings (1:1)                     remark-lint:no-multiple-toplevel-headings
  ×   66:1    Main heading must be in title case                              remark-lint:awesome-heading
  ×   66:1    List can only have one heading                                  remark-lint:awesome-heading
  ×   67:3    Don’t pad link with inner spaces                                remark-lint:no-inline-padding
  ×   85:6    "’" is used without matching "‘"                                remark-lint:match-punctuation
  ×   87:1    Don’t use multiple top level headings (1:1)                     remark-lint:no-multiple-toplevel-headings
  ×   87:1    List can only have one heading                                  remark-lint:awesome-heading
  ×   91:1    Don’t use multiple top level headings (1:1)                     remark-lint:no-multiple-toplevel-headings
  ×   91:1    List can only have one heading                                  remark-lint:awesome-heading
  ×   93:62   List item description must end with proper punctuation          remark-lint:awesome-list-item
  ×   97:60   List item description must end with proper punctuation          remark-lint:awesome-list-item
  ×   99:80   List item description must end with proper punctuation          remark-lint:awesome-list-item
  ×   99:116  Should not repeat "."                                           remark-lint:no-repeat-punctuation
  ×   99:117  Should not repeat "."                                           remark-lint:no-repeat-punctuation
  ×  101:62   List item description must end with proper punctuation          remark-lint:awesome-list-item
  ×  103:58   List item description must end with proper punctuation          remark-lint:awesome-list-item
  ×  105:58   List item link and description must be separated with a dash    remark-lint:awesome-list-item
  ×  107:62   List item description must end with proper punctuation          remark-lint:awesome-list-item
  ×  109:76   List item link and description separated by invalid whitespace  remark-lint:awesome-list-item
  ×  112:66   List item link and description must be separated with a dash    remark-lint:awesome-list-item
  ×  114:1    Don’t use multiple top level headings (1:1)                     remark-lint:no-multiple-toplevel-headings
  ×  114:1    List can only have one heading                                  remark-lint:awesome-heading
  ×  116:50   List item link and description must be separated with a dash    remark-lint:awesome-list-item
  ×  118:1    Don’t use multiple top level headings (1:1)                     remark-lint:no-multiple-toplevel-headings
  ×  118:1    List can only have one heading                                  remark-lint:awesome-heading
  ×  125:1    Don’t use multiple top level headings (1:1)                     remark-lint:no-multiple-toplevel-headings
  ×  125:1    List can only have one heading                                  remark-lint:awesome-heading


ADM-831:[frontend]feat: add future time check for metrics step

Summary
...
Before
Description
Screenshots
If applicable, add screenshots to help explain behavior of your code.
After
Description
Screenshots
If applicable, add screenshots to help explain behavior of your code.
Note
Null

https://sonarcloud.io/project/issues?resolved=false&sinceLeakPeriod=true&id=au-heartbeat-heartbeat-frontend&open=AY4MokmNBzss7mO_gya9
@weiraneve

https://sonarcloud.io/project/issues?resolved=false&sinceLeakPeriod=true&id=au-heartbeat-heartbeat-frontend&open=AY4MokmNBzss7mO_gya9 @weiraneve

In my ADM-831 branch, this has not appeared again


test(*): enforce go fmt

This PR enforces and suggests that the codebase should follow a specific
style using a combination of gofmt, golint and go vet. gofmt is
enforced; the latter are suggested and displayed.
deis/publisher also now uses godep go build to build the binary,
similar to our other components.
closes #2827
closes #2412

ha, case and point ;)

Code LGTM, but change should probably be separated into 3 commits as discussed:

Changing publisher over to Godep
Removing the client.yaml code
Enforcing gofmt

We missed that there was a 4th change in here, which was to remove the logspout Dockerfile which we no longer use.

The publisher fix here is the important one. Ideally these would be separate PRs, but I'm fine with all the changes. Code LGTM.

:ship:


fix #89

still need to update for https://github.com/textileio/go-textile/pull/821
will knock that off now

For some reason, textile block file QmUYvtwsGnRrJK2faAkc1hvaEdkbqWv2yQ2EWgp8RdEUua --path=file is failing with Marshal called with nil and
2019/06/11 14:49:47 [Recovery] 2019/06/11 - 14:49:47 panic recovered:
GET /api/v0/blocks/QmUYvtwsGnRrJK2faAkc1hvaEdkbqWv2yQ2EWgp8RdEUua/files/0/file/content HTTP/1.1
Host: <IP_ADDRESS>:40600
Accept-Encoding: gzip
User-Agent: Go-http-client/1.1

runtime error: invalid memory address or nil pointer dereference
/usr/local/Cellar/go/1.12.5/libexec/src/runtime/panic.go:82 (0x40474d0)
	panicmem: panic(memoryError)
/usr/local/Cellar/go/1.12.5/libexec/src/runtime/signal_unix.go:390 (0x40472ff)
	sigpanic: panicmem()
/Users/balupton/Projects/textile/go-textile/core/files.go:241 (0x4df47f5)
	(*Textile).FileIndexContent: fd, err := ipfs.DataAtPath(t.node, file.Hash)
/Users/balupton/Projects/textile/go-textile/core/api_blocks.go:225 (0x4dc2b2c)
	(*api).getBlockFileContent: reader, err := a.node.FileIndexContent(file)
/Users/balupton/go/pkg/mod/github.com/gin-gonic/gin@v1.3.0/context.go:108 (0x46b2652)
	(*Context).Next: c.handlers[c.index](c)
/Users/balupton/go/pkg/mod/github.com/gin-gonic/gin@v1.3.0/recovery.go:48 (0x46c3bd9)
	RecoveryWithWriter.func1: c.Next()
/Users/balupton/go/pkg/mod/github.com/gin-gonic/gin@v1.3.0/context.go:108 (0x46b2652)
	(*Context).Next: c.handlers[c.index](c)
/Users/balupton/go/pkg/mod/github.com/gin-gonic/gin@v1.3.0/logger.go:84 (0x46c2f9e)
	LoggerWithWriter.func1: c.Next()
/Users/balupton/go/pkg/mod/github.com/gin-gonic/gin@v1.3.0/context.go:108 (0x46b2652)
	(*Context).Next: c.handlers[c.index](c)
/Users/balupton/go/pkg/mod/github.com/gin-gonic/gin@v1.3.0/gin.go:361 (0x46bb096)
	(*Engine).handleHTTPRequest: c.Next()
/Users/balupton/go/pkg/mod/github.com/gin-gonic/gin@v1.3.0/gin.go:326 (0x46ba8d3)
	(*Engine).ServeHTTP: engine.handleHTTPRequest(c)
/usr/local/Cellar/go/1.12.5/libexec/src/net/http/server.go:2774 (0x42f6bb7)
	serverHandler.ServeHTTP: handler.ServeHTTP(rw, req)
/usr/local/Cellar/go/1.12.5/libexec/src/net/http/server.go:1878 (0x42f27a0)
	(*conn).serve: serverHandler{c.server}.ServeHTTP(w, w.req)
/usr/local/Cellar/go/1.12.5/libexec/src/runtime/asm_amd64.s:1337 (0x4061270)
	goexit: BYTE	$0x90	// NOP

So perhaps this is what @andrewxhill was running into. Need to look into it. But that shouldn't hold up review and merging of this PR.

so updated textileio/go-textile#821 to give better debug output, for some reason 	file, ok := files.Files[index].Links[path] is failing, however, it shouldn't... as the output is correct:
file:<mill:"/blob" checksum:"EPBRa7eDzgoXyvDXqRYuXLkRoZqMizZ4R8QkZyF8n9DP" source:"EPBRa7eDzgoXyvDXqRYuXLkRoZqMizZ4R8QkZyF8n9DP" opts:"G7x9bf74kcvU7aBVnToCMAeVhcsuxuHag8gKgav6cGcN" hash:"QmVQD8PXikg9jgqn8ruMjsX2ZoQfSqPDeCHq7hTnFE7enV" key:"x5sa9iwyTMkMZKnmtrjst9h9XgR51xthmUuVnJs7WutgAAT2d9y7njGvEDQ7" media:"text/plain; charset=utf-8" name:"stdin" size:14 added:<seconds:1559787180 nanos:620280000 > meta:<> targets:"QmVikPYj5PXsuYH9TtQ2GHFSWMcC31gC5zaKEhJF1mUBAy" > ^CInterrupted
Shutting down...^Cdone

so no idea

Ready for another review.