Problem trying to create .apk file

First of all, congrats for the project!! I was looking for a budget tracker and found one that not only looks greate, but safe and I can check (and change) the code!!
I'm trying to generate the apk file for it, but after running
npm install
and
cd android/ ./gradlew assembleRelease
(I actually had problems for the second line, gradlew didn't have the necessary permissions, so I had to run a
chmod u+x gradlew
to solve it)
anyways, after running assembleRelease I receive this:
:ReactNative:Unexpected empty result of running '[node, -e, try {console.log(require('@react-native-community/cli').bin);} catch (e) {console.log(require('react-native/cli').bin);}]' command.
:ReactNative:Running '[node, -e, try {console.log(require('@react-native-community/cli').bin);} catch (e) {console.log(require('react-native/cli').bin);}]' command failed.

FAILURE: Build failed with an exception.

* Where:
Script<EMAIL_ADDRESS>line: 213

* What went wrong:
A problem occurred evaluating script.
 > /home/felipe/git/personal/Wallety/node_modules/metro/src/Server.js:376  processRequest = (req, res, next) => {                 ^SyntaxError: Unexpected token =    at Module._compile (internal/modules/cjs/loader.js:723:23)    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)    at Module.load (internal/modules/cjs/loader.js:653:32)    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)    at Function.Module._load (internal/modules/cjs/loader.js:585:3)    at Module.require (internal/modules/cjs/loader.js:692:17)    at require (internal/modules/cjs/helpers.js:25:18)    at Object.<anonymous> (/home/felipe/git/personal/Wallety/node_modules/metro/src/shared/output/bundle.js:14:16)    at Module._compile (internal/modules/cjs/loader.js:778:30)    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)

I tried to solve it by installing, via npm, the packages react-native, metro and react-native-community, cli-platform-android.
None of them fixed, so after reading more about the error, I tried to install gradle but unfortunately I couldn't fix it.
I'm looking foward to being able to generate the apk, mostly because I woudl really like to propose some changes (like adding Brazilian Real as curreny) but I would like to test it in the apk first.
Thanks!

hI @felipecampossantos !
Did you follow these steps before generating APK file ?
https://reactnative.dev/docs/signed-apk-android

Hi @blaiti !!! Thanks for your help. I haven't done that, but now I did and I'm finding another error.
:ReactNative:Unexpected empty result of running '[node, -e, try {console.log(require('@react-native-community/cli').bin);} catch (e) {console.log(require('react-native/cli').bin);}]' command.
:ReactNative:Running '[node, -e, try {console.log(require('@react-native-community/cli').bin);} catch (e) {console.log(require('react-native/cli').bin);}]' command failed.

FAILURE: Build failed with an exception.

* Where:
Script<EMAIL_ADDRESS>line: 213

* What went wrong:
A problem occurred evaluating script.
> /home/felipe/git/personal/Wallety/node_modules/@react-native-community/cli-plugin-metro/node_modules/metro/src/Server.js:376  processRequest = (req, res, next) => {                 ^SyntaxError: Unexpected token =    at Module._compile (internal/modules/cjs/loader.js:723:23)    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)    at Module.load (internal/modules/cjs/loader.js:653:32)    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)    at Function.Module._load (internal/modules/cjs/loader.js:585:3)    at Module.require (internal/modules/cjs/loader.js:692:17)    at require (internal/modules/cjs/helpers.js:25:18)    at Object.<anonymous> (/home/felipe/git/personal/Wallety/node_modules/@react-native-community/cli-plugin-metro/node_modules/metro/src/shared/output/bundle.js:14:16)    at Module._compile (internal/modules/cjs/loader.js:778:30)    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s


mapArray(XMLObject: Any?) -> [N]? bug

If we have XML something like
<Array>
<XMLMappable/>
</Array>
and try to map it like
var array = [XMLMappable]()
array <- map[Array.XMLMappable]
we have empty array instead of array with 1 item.
If think problem method is mapArray(XMLObject: Any?) -> [N]? in Core/XMLMapper.swift
Suggest add else if statement like this.
Before:
public func mapArray(XMLObject: Any?) -> [N]? {
if let XMLArray = XMLObject as? [[String: Any]] {
return mapArray(XMLArray: XMLArray)
}
return nil
}
After:
public func mapArray(XMLObject: Any?) -> [N]? {
if let XMLArray = XMLObject as? [[String: Any]] {
return mapArray(XMLArray: XMLArray)
} else if let object = XMLObject as? [String: Any] {
return mapArray(XMLArray: [object])
}
return nil
}

Yes, this is an issue (already referenced in #3 although closed)
This will be fixed in the next release, as soon as I find a little bit of time to test it.
Thank you for your suggestion.


setup the README.md

Configure the README.md file to provide comprehensive information about the project, including details on its purpose, guidelines for contributing, licensing information, and additional relevant content.

Closing this as we have enough content in README.md


Doesn't seem to work with RequireJS

I was getting issues with using Reactabular with RequireJS. I'm not sure if this was a configuration problem on my part, or if it just doesn't play well with webpack.
Uncaught Error: Script error for: react/addons
http://requirejs.org/docs/errors.html#scripterror
makeError (require.js:166)
context.onScriptError (require.js:1696)

requirejs.config({
    paths: {
      'reactabular': '/bower_components/reactabular/dist/reactabular'
    }
});

@eviltoylet Can you try changing config/webpack.common.dist.js 'react/addons': 'react/addons' to `'react/addons': 'react'?

Yeah that works, but it doesn't seem like the correct thing to do. The package layouts for react are different in bower and npm.
Maybe this is what I need to do? But ... I don't actually know :P
requirejs.config({
    paths: {
      'react': '/bower_components/react/react',
      'react/addons': '/bower_components/react/react-with-addons',
    }
});

Yeah, I understand better what's going on here now. Webpack will alias React as react/addons in our current build. In other words your config is correct and you can simplify it further:
requirejs.config({
    paths: {
      'react/addons': '/bower_components/react/react-with-addons',
    }
});

Now that I think of it, our current naming is correct. We depend on React with addons after all. The first part of Webpack config (`'react': 'react') is likely redundant. We shouldn't have any direct references to vanilla React anywhere given that breaks the tests (they end up with two instances of React).

Yup, I'm going to close this as a non issue. Thanks!


[BUG] Cant See Bloxstrap Menu

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
I cant see the bloxstrap menu app in my search bar.

What if you look for it manually in your application list instead of using the search bar for it?


Allow custom validation rules access all parameters

So basically I'm working on a project where we need to validate the amount of days between two timestamps. Because this may vary based on the front end, I want to make this dynamic but also cap the maximum amount to prevent possible abuse.
I was looking through the code how the required_if validation is working, because it looks a lot like the custom rule I described above.  I noticed that this method has access to a $this->data property. This is exactly what I need in my custom validation, but I don't see any "support" for this in the validator.
So right now it doesn't look like it's possible by creating a custom validation rule right? I think there are some similar use cases where the custom rule needs access to all provided data and validate on certain attributes being there or not. There are some ways to get access in the custom rule, e.g. by using a trait + interface and check if it needs all data. But maybe I'm all alone in this, what do you guys (and girls) think about this?
Possible usage
I think an example of how I want to use my custom rule might explains it even better.
$input = $request->validate([
    'from' => ['required', 'date', new DateRangeRule('to', 7, 'days')],
    'to'   => ['required', 'date',  new DateRangeRule('from', 7, 'days')],
]);

$input = $request->validate([
    'from' => ['required', 'date', new DateRangeRule('to', 1, 'week')],
    'to'   => ['required', 'date',  new DateRangeRule('from', 1, 'week')],
]);

You could pass the other field's value in the custom rule's constructor, like this:
$input = $request->validate([
    'from' => ['required', 'date', new DateRangeRule($request->get('to'), 7, 'days')],
    'to'   => ['required', 'date',  new DateRangeRule($request->get('from'), 7, 'days')],
]);

I think that would work

@rodrigopedra Yes, that's definitely a nice workaround! Although I prefer to use Laravel's $request->input instead of Symfony's $request->get method. For custom rules that require even more attributes you can also just drop the $request instance or $request->all() array in the constructor. Definitely fair points! But I was wondering if this is something that should be fixed in Laravel or worked around in projects 😄

If you come up with an elegant solution feel free to submit a PR.

Just in case someone is trying to access the request inside a custom rule; you can use the global request helper request() like so
<?php

public function rules()
{
    return [
        'field' => [
            // ...
            new CustomRule(request()->field, request()->another_field)
        ]
    ];
}

You could pass the other field's value in the custom rule's constructor, like this:
$input = $request->validate([
    'from' => ['required', 'date', new DateRangeRule($request->get('to'), 7, 'days')],
    'to'   => ['required', 'date',  new DateRangeRule($request->get('from'), 7, 'days')],
]);

I think that would work

This solutions is limiting, it does not allow to validate data that does not come from the request and it ties the rules to the request, so they cannot be defined apart from it.
I would suggest that the Validator@passes method passes an instance of the validator as the third parameter.

No sure if this was mentioned, but the closure version does pass the validator instance as the 4th parameter:
$this->$method($attribute, $value, $parameters, $this)

@photonite I tried adding passes($attribute, $value, $validator), but that changes the Rule contract and probably breaks all existing validators.
The other way to go is assigning $rule->validator = $this before calling $rule-passes(...):
    protected function validateUsingCustomRule($attribute, $value, $rule)
    {
        $rule->validator = $this;  // Assign validator here
        if (! $rule->passes($attribute, $value)) {
            $this->failedRules[$attribute][get_class($rule)] = [];

            $this->messages->add($attribute, $this->makeReplacements(
                $rule->message(), $attribute, get_class($rule), []
            ));
        }
    }

@tillkruss any thoughts on this? Adding the 3rd parameter would be consistent with the closure version.

Sorry for ninja edit...
@photonite I tried adding passes($attribute, $value, $attributes), but that changes the Rule contract and breaks all existing validators on earth.
@tillkruss any thoughts on this?
I'm happy to do a PR for it, just want to get comments first :)

Any suggestion to workaround this?
Stumbled over the same problem, when it comes to building a custom validation rule, where I need to pass some request values (in my case other input values) into.
Currently still breaking:

Declaration of App\Rules\CustomPricing::passes($attribute, $value, $parameters) must be compatible with Illuminate\Contracts\Validation\Rule::passes($attribute, $value)

Pass the fields you need through the constructor

But how can I pass the fields when not using the request() as source?

You can use $validator->getData() method to get the data under the validation...
I don't want to use request() helper method inside of the validation class because then I can only use that class for validating params sent over http requests...

To solve this issue I created a value object for passing Rule Parameters. One for raw values and one for request values.
class RequestValueRuleParameter extends AbstractRuleParameter
{
    public function __construct( string $name, string $label = null)
    {
        $this->value = request()->input($name);
        $this->label = $label ?? str_replace('_', ' ', $name);
    }
}

class ValueRuleParameter extends AbstractRuleParameter
{
    public function __construct($value, string $label)
    {
        $this->value = $value;
        $this->label = $label;
    }
}

Now I can do something like this:
Validator::make($data, [
            'current_password' => ['required', new MustMatchExistingPassword(
                new ValueRuleParameter($user->password, 'existing password')
            )]]);

Validator::make($data, [
            'new_password' => ['required'],
            'current_password' => ['required', new MustNotMatchNewPassword(
                new RequestValueRuleParameter('password', 'new password')
            )]]);

In the rule, I pass the object through the constructor, type hinting the interface
    public function __construct(RuleParameter $existingPassword)
    {
        $this->existingPassword = $existingPassword;
    }

Abstract Rule Parameter class
abstract class AbstractRuleParameter implements RuleParameter
{
    protected $label;
    protected $value;

    /**
     * @return mixed
     */
    public function getValue()
    {
        return $this->value;
    }

    /**
     * @return string
     */
    public function getLabel(): string
    {
        return $this->label;
    }
}


Change ReflectMapEntities to operate on components before insertion

Previous PR https://github.com/bevyengine/bevy/pull/14549 was closed in error and couldn't be reopened since I had updated the branch :crying_cat_face:
Objective
Fixes #14465
Solution
Change Scene and DynamicScene to use ReflectVisitEntities instead of ReflectMapEntities to remap entities prior to insertion. This ensures that observers will only ever see real live world entities, rather than scene entities.
Changes all instances where components and resources were providing ReflectMapEntities and ReflectMapEntitiesResource to now provide the unified and more generic ReflectVisitEntities.
Removes the now-unused ReflectMapEntities and ReflectMapEntitiesResource.
Testing

New unit test for Observers + DynamicScenes
New unit test for Observers + Scenes
Open to suggestions for other tests!

Migration Guide

Users should now #[derive(IterEntities)] and #[reflect(VisitEntities)] where they were previously implementing MapEntities and #[reflect(MapEntities)]
In cases where the derived trait isn't usable (enums, internal mutexes), either IterEntities or VisitEntities should be implemented by hand.

I've rebased this on #15425 since it's gaining traction and I like its approach way better than what I had here previously.

Welp, this has now been un-rebased on #15425 after realizing the approach there wouldn't work for HashSets. So now we're back to the original plan.

@alice-i-cecile This is ready for review once more!


Potential secutiry vulnerabilities in the shared libraries which rovio-ingest depends on.

Hi, @juhoautio , @jorgeramirezcarrasco-rovio , I'd like to report a vulnerability issue in com.rovio.ingest:rovio-ingest:1.0.0_spark_3.0.1.
Issue Description
com.rovio.ingest:rovio-ingest:1.0.0_spark_3.0.1 directly or transitively depends on 45 C libraries (.so) cross many platforms(such as x86-64, x86, arm64, armhf). However, I noticed that some C libraries are vulnerable, containing the following CVEs:
llibzstd-jni.so from C project zstd(version:1.4.4) exposed 1 vulnerabilities:
CVE-2021-24032
liblz4-java.so from C project lz4(version:1.9.1) exposed 1 vulnerabilities:
CVE-2019-17543
Suggested Vulnerability Patch Versions
zstd has fixed the vulnerabilities in versions >=1.4.9
lz4 has fixed the vulnerabilities in versions >=1.9.2
Java build tools cannot report vulnerable C libraries, which may induce potential security issues to many downstream Java projects.
Could you please upgrade the above shared libraries to their patch versions?
Thanks for your help~
Best regards,
Helen Parr

Those CVEs don't seem to affect rovio-ingest.
From https://github.com/luben/zstd-jni/issues/163, "Question about CVE-2021-24032":

The CVE applies only to the Zstd CLI, the library (and therefore bindings of the library to other languages) is unaffected.

And https://github.com/lz4/lz4-java/issues/170, "lz4-java-1.7.1.jar is identified as Vulnerable dependency on Dependency Check":

It must be a false positive. lz4-java 1.7.1 is based on lz4 1.9.2, which includes a fix to CVE-2019-17543.


Change Input Directory from a single path to a list of paths

Suggested by @Monk_The_OCD_Engie.  Would speed up Top Level Assembly searches.

In my opinion, the way the list of files is created has to be changed; at the moment the list is reloaded many times during the process.
We need methods to add files to the list: from directory, subdirectory, list or drag&drop
We need a method to remove files from the lists (select and delete key)
We need a method to clean the list (a button)
The listview recently introduced is capable to store the full path of each element so the process file will read the full path from there.

This issue will be solved with #15 that I'm working on, you can close it

Will be solved as part of Issue #15


Socket closed when looking for seed in ubuntu

Loading...
(0/6) Loading siad...
(1/6) Loading gateway...
(2/6) Loading consensus...
(3/6) Loading transaction pool...
(4/6) Loading wallet...
(5/6) Loading host...
(6/6) Loading renter...
Finished loading in 1.73934769 seconds
2017/07/20 21:13:15 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:18 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:18 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:18 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:18 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:18 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:18 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:18 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:18 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:18 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:20 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:20 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:20 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:21 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:21 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:21 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:21 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:21 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:21 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:21 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:21 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:21 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:22 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:23 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:24 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:25 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:25 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:26 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:27 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:27 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:27 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:27 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:27 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:27 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:27 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:28 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:28 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:28 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:29 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:30 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:31 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:32 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:33 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:34 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:35 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:35 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:35 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:35 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:35 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:35 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:35 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:35 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:35 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:35 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:36 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:36 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:37 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:38 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:38 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:38 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:38 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:38 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:38 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:38 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:38 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:39 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:39 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:40 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:41 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:42 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:43 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:43 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:43 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:43 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:43 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:43 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:43 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:43 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:43 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:44 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:44 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:45 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:45 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:45 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:45 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:45 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:45 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:46 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:46 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:47 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:48 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:48 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:48 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:48 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:48 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:48 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:48 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:48 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:48 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:48 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:49 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:50 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:51 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:52 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:52 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:52 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:52 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:52 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:52 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:52 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:52 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:52 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:53 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:53 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:54 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:55 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:55 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:55 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:55 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:55 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:56 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:57 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:13:58 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:13:58 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:13:58 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:13:58 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:13:58 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:13:58 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:13:58 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:13:59 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:13:59 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:14:00 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:14:00 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:14:00 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:14:00 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:14:00 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:14:00 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:14:00 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:14:00 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:14:00 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:14:01 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
2017/07/20 21:14:01 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
2017/07/20 21:14:02 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:14:03 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
goroutine 31889 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc43b874d68)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc43b874ec0, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc43b874ec0, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit.func1(0xc42bc367c0, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:167 +0x227
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:184 +0x15d
Severe error: Unable to open temporary settings file for writing: open /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json_temp: too many open files
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 5ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 10ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 20ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 40ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 80ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 160ms
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 320ms
goroutine 31903 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc4208f0dc8)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc4208f0f60, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc4208f0f60, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources.func1(0xc43bd8eb80, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:32 +0x269
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:52 +0x93
Severe error: ERROR: unable to sync the contract manager settings: invalid argument
goroutine 31903 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc4208f0dc8)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc4208f0f20, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc4208f0f20, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources.func1(0xc43bd8eb80, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:50 +0x4ea
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:52 +0x93
Severe error: ERROR: unable to atomically copy the contract manager settings: rename /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json_temp /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json: no such file or directory
goroutine 31905 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc43b875d68)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc43b875ec0, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc43b875ec0, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit.func1(0xc43bd8eb90, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:167 +0x227
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:184 +0x15d
Severe error: Unable to open temporary settings file for writing: open /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json_temp: too many open files
2017/07/20 21:14:04 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 640ms
goroutine 31939 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc43b874dc8)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc43b874f60, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc43b874f60, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources.func1(0xc43bd8eca0, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:32 +0x269
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:52 +0x93
Severe error: ERROR: unable to sync the contract manager settings: invalid argument
goroutine 31939 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc43b874dc8)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc43b874f20, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc43b874f20, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources.func1(0xc43bd8eca0, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:50 +0x4ea
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:52 +0x93
Severe error: ERROR: unable to atomically copy the contract manager settings: rename /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json_temp /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json: no such file or directory
goroutine 31941 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc43b874d68)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc43b874ec0, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc43b874ec0, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit.func1(0xc43bd8ecb0, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:167 +0x227
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:184 +0x15d
Severe error: Unable to open temporary settings file for writing: open /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json_temp: too many open files
2017/07/20 21:14:05 http: Accept error: accept tcp <IP_ADDRESS>:9980: accept4: too many open files; retrying in 1s
goroutine 31823 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc43b875dc8)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc43b875f60, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc43b875f60, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources.func1(0xc421ad81d0, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:32 +0x269
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:52 +0x93
Severe error: ERROR: unable to sync the contract manager settings: invalid argument
goroutine 31823 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc43b875dc8)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc43b875f20, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc43b875f20, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources.func1(0xc421ad81d0, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:50 +0x4ea
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:52 +0x93
Severe error: ERROR: unable to atomically copy the contract manager settings: rename /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json_temp /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json: no such file or directory
goroutine 31825 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc43b875d68)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc43b875ec0, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc43b875ec0, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit.func1(0xc421ad81e0, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:167 +0x227
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:184 +0x15d
Severe error: Unable to open temporary settings file for writing: open /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json_temp: too many open files
goroutine 31943 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc420c31dc8)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc420c31f60, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc420c31f60, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources.func1(0xc424486020, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:32 +0x269
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:52 +0x93
Severe error: ERROR: unable to sync the contract manager settings: invalid argument
goroutine 31943 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc420c31dc8)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc420c31f20, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc420c31f20, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources.func1(0xc424486020, 0xc4201d0668)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:50 +0x4ea
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).syncResources
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:52 +0x93
Severe error: ERROR: unable to atomically copy the contract manager settings: rename /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json_temp /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.json: no such file or directory
goroutine 31946 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc421c8cc80)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc421c8ce78, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc421c8ce78, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit.func2(0xc424486030, 0xc4201d0668, 0x0, 0x0, 0x0, 0xebc2b0, 0x0, 0x0)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:196 +0x236
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:209 +0x1e5
Severe error: ERROR: unable to create write-ahead-log: open /home/chera/.config/Sia-UI/sia/host/contractmanager/contractmanager.wal_temp: too many open files
goroutine 31946 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc421c8cc80)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc421c8ce58, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc421c8ce58, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit.func2(0xc424486030, 0xc4201d0668, 0x0, 0x0, 0x0, 0xebc2b0, 0x0, 0x0)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:201 +0x357
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:209 +0x1e5
Severe error: Unable to properly initialize WAL file, crashing to prevent corruption: unable to write WAL metadata: invalid argument
goroutine 31946 [running]:
runtime/debug.Stack(0x445617, 0x0, 0xc421c8caa0)
/usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
/usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/NebulousLabs/Sia/build.Severe(0xc421c8cc18, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/build/critical.go:32 +0x92
github.com/NebulousLabs/Sia/persist.(*Logger).Severe(0xc42026e000, 0xc421c8cc18, 0x2, 0x2)
/home/jrh/go/src/github.com/NebulousLabs/Sia/persist/log.go:71 +0xe0
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).appendChange(0xc4201d0668, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlog.go:151 +0x46e
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit.func2(0xc424486030, 0xc4201d0668, 0x0, 0x0, 0x0, 0xebc2b0, 0x0, 0x0)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:208 +0x423
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:209 +0x1e5
Severe error: Unable to write state change to WAL: invalid argument
panic: unable to append a change to the WAL, crashing to prevent corruption
goroutine 31946 [running]:
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).appendChange(0xc4201d0668, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlog.go:152 +0x4b8
github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit.func2(0xc424486030, 0xc4201d0668, 0x0, 0x0, 0x0, 0xebc2b0, 0x0, 0x0)
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:208 +0x423
created by github.com/NebulousLabs/Sia/modules/host/contractmanager.(*writeAheadLog).commit
/home/jrh/go/src/github.com/NebulousLabs/Sia/modules/host/contractmanager/writeaheadlogsync.go:209 +0x1e5

duplicate of #1840


[HCA DX] Track clicks on "Request File Manifest" export method button

Need
See similar "Analyze in Terra" ticket.
Definition of Done
Clicks on "Request File Manifest" data button are accessible in the query explorer for both prod and staging:

[ ] data.humancellatlas.org - GA4
[ ] data.humancellatlas.dev.clevercanary.com - GA4

Hi @jpaten, the corresponding PR has been merged and deployed to dev.

Thanks @MillenniumFalconMechanic! I'll work on the GTM configuration now.

@MillenniumFalconMechanic, would you be able to review version 60 on GTM

Hi @jpaten, version 60 LGTM!

@MillenniumFalconMechanic This issue is now showing up on Query Explorer!

Thanks @jpaten!


Error when creating instance of between relationship using a contained entity

The following error is thrown when there is an attempt to create an instance - using REST API or dataflow - of between relationship between entities where:

Both entities are contained inside the same entity.
One entity is contained and another isn't.

Error:
[{"status":"error","result":null,"message":"Check failed, invalid value MyDocument1 for :Document"}]
Code:
(component :WordCount.Core)

(entity :WordCount.Core/User
        {:Email {:type :Email :guid true}
         :Name :String
         :MemberSince {:type :Date :optional true}})

(entity :WordCount.Core/Document
        {:Name {:type :String :guid true} ;; tried :id too
         :Content :String
         :Summary :String
         :LastUpdated {:type :DateTime :optional true}})

(entity :WordCount.Core/Tag
        {:Id {:type :Int :guid true}
         :Name :String})

(entity :WordCount.Core/Page
        {:Id {:type :Int :id true}
         :Name :String})

;; RELATIONSHIPS

(relationship :WordCount.Core/UserDocuments
              {:meta {:contains [:WordCount.Core/User :WordCount.Core/Document]}})

(relationship :WordCount.Core/DocumentPages
              {:meta {:contains [:WordCount.Core/Document :WordCount.Core/Page]}})

(relationship :WordCount.Core/UserTags
              {:meta {:between [:WordCount.Core/User :WordCount.Core/Tag]}})

(relationship :WordCount.Core/DocumentTags
              {:meta {:between [:WordCount.Core/Document :WordCount.Core/Tag]}})

(relationship :WordCount.Core/DocumentDocument
              {:meta {:between [:WordCount.Core/Document :WordCount.Core/Document :as [:Document1 :Document2]]}
               :Details :String}

Curls to reproduce:

Create User

 curl -X POST http://localhost:8080/_e/WordCount.Core/User -H 'Content-Type: application/json' -d '{
"WordCount.Core/User": {
"Email"<EMAIL_ADDRESS>"Name": "John Doe"}
}'

Create Document

curl -X POST<EMAIL_ADDRESS>-H 'Content-Type: application/json' -d '{
     "WordCount.Core/Document": {
       "Name": "MyDocument1",
       "Content": "This is the content of my document.",
       "Summary": "This is a summary of my document."
     }
   }'

Create Tag

curl -X POST http://localhost:8080/_e/WordCount.Core/Tag -H 'Content-Type: application/json' -d '{
      "WordCount.Core/Tag": {
        "Id": 1,
        "Name": "Important"
      }
    }'

Finally, create Between relationship instance:

curl -X POST http://localhost:8080/_e/WordCount.Core/DocumentTags -H 'Content-Type: application/json' -d '{                                                        "WordCount.Core/DocumentTags": {
        "Document": "MyDocument1",
        "Tag": 1
      }
    }'

This throws the error.

For between relationships, the convention is to use :Identity - UUIDs with a default value type:
(entity :WordCount.Core/Document
        {:Id :Identity
         :Name {:type :String :id true}
         :Content :String
         :Summary :String
         :WordCount :String
         :LastUpdated {:type :DateTime :optional true}})

This doesn't lead to error. Closing the issue.


coercion operations to add more unit tests

Which issue does this PR close?
Closes #.
Rationale for this change
coercing to add more unit tests
What changes are included in this PR?

Are there any user-facing changes?

I am trying to clean up the list of PRs to review in DataFusion so marking old ones as stale. Please let us know if you plan to work on this soon. Otherwise we will close it down and reopen it when the time is right.

Closing stale PRs -- please reopen if that was a mistake


Insiders build no longer active

This is a big one. The insiders build was expected to have a -dev flag at the end of the version in package.json. We somehow forgot to have the -dev flag back in package.json in the master branch, due to which insiders build no longer has that flag.
So for all of the users insiders setting is now turned to "off" (because insiders build is recognized as stable, and setting was set to "weekly" or "daily" --- Which is a conflict). So no one is using the insiders build anymore.
SOLUTION

We need to do a point release ASAP, showing the first time prompt again asking the users to enroll in the insiders program again.

if we do the point release, will users who are in the insiders build get that update?

Note that people using the insiders release will have to manually update (e.g. change their setting back to "daily" or "weekly".  We will also need the following fixes:

[ ] add a test to ensure master always have the "-dev" tag in version (and not in release branch)
[ ] notify user when "insiders" setting changed
[ ] ...

Can I see m suggest considering throwing away the dev suffix.
Having this would mean we have to always ensure the dev flag exhaust exists in master (insiders) before we release. Ie we need a bullet proof way to ensure this never happens again. E.g. automated release process is blocked until an insiders version is available on azure storage that is of a higher version. Or similar.
Or consider another way to differentiate release vs insiders versions. It's possible we might come back to this same slack, but I think it's best we explore this avenue (alternatives).

We should only need a test that ensures the version has a "-dev" suffix (or doesn't if the release branch).

FYI, I've queued up a CI build which, if it passes, will give us an up-to-date insiders build to upload.

Tweet is out: https://twitter.com/pythonvscode/status/1174384517907271684. @ericsnowcurrently  are we good to close this one?

Yep, closing this.


Legend is out of the chart window

ScottPlot Version: <IP_ADDRESS>
Operating System: Window 10
Application Type: WPF
Question: In my project, it had 43 different series and when it show the lengend, the legend is out of the scope of the chart window, it only shows 10-33 series and some lengends can't be displayed on the chart area.   I had searched with the searching engine, but it seems that there no methods to resolve this problem.

I think this huge number of legend entries are not really good to show on the plot itself. This is just not practical at this level, it is a big mess. I advise you to develop your own "legend UI" as a separate control.
When I had to show lots of curves on a single Plot, for example, I used to make a separate Listbox with checkboxes, labels and other useful items. When you interact with the Listbox, you can use some Events to show/hide, highlight, etc the curves on your Plot.

Thank you very much. In my project, it must put the series in one chart. I will put the legend in one seperate control as description in Q&A #1280.

Note that there's also GetLegendBitmap() which will let you get the legend as a bitmap then display it elsewhere in your window
Bitmap bmp = formsPlot1.Plot.GetLegendBitmap();
pictureBox1.Image = bmp;


feat: issue-5712 add sleep tool

Fixes # 5712 added sleep tool

Who can review?
@vowelparrot

Thanks for the PR! one main request - I'm also curious what you've found this useful for :)


Add AIP v1 and v2 to the list of Supported Profiles

Can the Aries interoperability profiles  1 and 2 be added to the Supported Profiles dropdown on submission form ?
AIP supports peer-to-peer interactions via DIDComm in addition to AnonCreds credential and presentation exchanges.

I see now that the Form input maps to the credentialProfiles object in the resulting JSON
...
 "credentialProfiles": [
    "AnonCreds with did:indy",
    "AnonCreds with did:web"
  ],
...

Perhaps the SIG can consider adding a separate field to capture Wallet interoperability profiles such as AIP 1 and 2

Hi @jorgefl0 ,
do you know if there are more wallet interoperability profiles out there?
But yeah, we would add it as a new category.


Restoring CVO overrides

Hello All,
I'm installing 4.11, when I log into the bootstrap node and run (journalctl -b -f -u release-image.service -u bootkube.service).
I see the following error, any idea's?  I noticed this resolves to "ec2-34-206-39-153.compute-1.amazonaws.com"
This is an IPI install all firewalls have been turned off.  This is a local vsphere install, should this be reaching out to aws?
Sep 23 01:46:30 localhost.localdomain bootkube.sh[1331]: Starting cluster-bootstrap...
Sep 23 01:46:30 localhost.localdomain bootkube.sh[1331]: Restoring CVO overrides
Sep 23 01:50:01 localhost.localdomain bootkube.sh[2943]: Unable to connect to the server: dial tcp <IP_ADDRESS>:6443: i/o timeout
Sep 23 01:50:11 localhost.localdomain bootkube.sh[1331]: Trying again to restore CVO overrides
Sep 23 01:53:41 localhost.localdomain bootkube.sh[3744]: Unable to connect to the server: dial tcp <IP_ADDRESS>:6443: i/o timeout
Sep 23 01:53:51 localhost.localdomain bootkube.sh[1331]: Trying again to restore CVO overrides
Sep 23 01:57:21 localhost.localdomain bootkube.sh[4418]: Unable to connect to the server: dial tcp <IP_ADDRESS>:6443: i/o timeout
Sep 23 01:57:31 localhost.localdomain bootkube.sh[1331]: Trying again to restore CVO overrides
Sep 23 02:01:02 localhost.localdomain bootkube.sh[5113]: Unable to connect to the server: dial tcp <IP_ADDRESS>:6443: i/o timeout
Sep 23 02:01:12 localhost.localdomain bootkube.sh[1331]: Trying again to restore CVO overrides

api-int...


Add new Project : Travel Website

Description :
Hello Sir,
I want to add my new project of Travel website in this repo under APERTRE'24.
Web stack
HTML , CSS
Screenshot

Additional Context
please assign me this issue under APERTRE'24
Best of Luck and Happy Coding.
Arpan Chowdhury

@SandipPalit @debarshee2004 please assign me this issue under APERTRE'24

hey @apu52 you have assigned this project keep coding....


Player videos

Does ArKOS play video files? For example .mp4
RGB10

https://github.com/christianhaitian/arkos/wiki/ArkOS-Emulators-and-Ports-information#movie-video-player


13 MAR 2023 - InnerSource SIG Meeting Minutes

Date
Monday 13 MAR 2023 - 11:00am EST / 4:00pm UK
Untracked attendees

Fullname, Affiliation, (optional) GitHub username
...

Meeting notices

FINOS SIG Leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS SIG meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve past meeting minutes
[ ] Review FINOS Slack InnerSource SIG Channel - https://finos-lf.slack.com/archives/C01SYB503QT
[ ] Discuss tentative plans for Inner Source SIG in 2023 - Co-Leads
[ ] Update on joint events with Inner Source Commons - Clare
[ ] Update on next steps in Licensing Working Group and call for vue.js contributors - Chamindra
[ ] Welcome inputs from FinOS community for event/activies they like to see from Inner Source SIG - All
[ ] Discuss allocations of housekeeping work amongst co-leads and other interested contributors
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Zoom Details

https://zoom.us/j/94949043746?pwd=WnBFQjhpUnBjMWE0OUhqUGhhb0ZOdz09
Meeting ID: 949 4904 3746
Passcode: 067897

Join by phone
Find your local number: https://zoom.us/u/adJnH9JOiY
Mailing List
Email<EMAIL_ADDRESS>to subscribe to the InnerSource SIG
mailing list.

Here.

Hey there 👋🏻

Greetings and salutations

👋

Hello

👋


fix value popups displaying under other elements

Terms

THIS SOFTWARE IS CONTRIBUTED SUBJECT TO THE TERMS OF THE TERMS OF THE CCLA DATED 2017-11-07 WITH FINOS/LINUX FOUNDATION (FORMERLY THE SYMPHONY SOFTWARE FOUNDATION CCLA).
  THIS SOFTWARE MAY BE REDISTRIBUTED TO OTHERS ONLY BY EFFECTIVELY USING THIS OR ANOTHER EQUIVALENT DISCLAIMER IN ADDITION TO ANY OTHER REQUIRED LICENSE TERMS.

I moved the z-index into the VisualState part of the config, and changed the variable backgrounds from filter to simple background, so we have to deal with the zIndex in less places now


Fix some Cubit warnings

It looks like #3870 introduced some new warnings (unused variables, use of variable length arrays, comparison of integers of different signs).
I believe these warnings did not show up in the CI because MFEM is not built with MFEM_USE_NETCDF enabled in the GitHub actions.
This PR fixes those warnings, and does some other minor clean-up:

Fixes the above-mentioned warnings.
Changes the new Cubit-related Mesh member functions to be free functions in the cubit namespace. The Mesh class is already a huge monolith, I think we should avoid bulking it up more.
Change Mesh::ReadCubit to take the filename as const std::string &, which is consistent with the rest of the Mesh API.
Uses std::vector instead of dynamic arrays (created with new[]).

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#3982
@pazner
@tzanio
@bslazarov + @jandrej
11/16/23
11/19/23
⌛due 12/7/23

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Thanks for fixing these @pazner... Apologies for missing the warnings in https://github.com/mfem/mfem/pull/3870!

Merged in next for testing...


Feature Request: Change tree item name with setting

When using with markdown file, all symbols displayed in same level with different number of #.
(It's better if vscode can produce a better symbol tree for markdown file, but it didn't now...)
It looks like:

It will be better if I can replace # with something looks more clear.
I tried to edit the symbolOutline.js with some simple change in getTreeItem():
name.replace(/^(##|#)/, '').replace(/^#+/, function(m){ return m.replace(/#/g, '　　');})

Then the outline tree looks like:

I hope it could be something in setting that user can use JavaScript to
change item's name.

I'd rather avoid special-casing certain formats.

@patrys Yes. I think this setting could be used in a more generate way:

Change "AxxxBxxxCxxx" to "axxx_bxxx_cxxx"
Trim useless prefix
Some kind of translating
...

@patrys Do you consider to accept PR for this issue?

I'm open for all proposals but I'd like to discuss this through before you spend time on an implementation. I don't think it's a good idea for someone to have to write code in setting files. JSON is not really suitable to express logic and evaluating random strings is a bad idea as there is no way to prevent the function from erasing all of your files (and it's not uncommon to track workspace config in git).

How about user can provide multiple pairs string to run replace for item name?
    "ItemNameReplace" : [
        {"pattern":"/^(##|#)/", "replacement":""},
        {"pattern":"/^#/", "replacement" : "　"}
    ]


Add missing filter primitives to collections

Ref https://github.com/svg/svgo/issues/1045#issuecomment-510208768 https://github.com/svg/svgo/issues/1193
This should prevent feDropShadow from removing.

Don't you also want to add some specs testing these primitives?

Not really. Too much work to cover whole svg spec. I'd go another way and implement spec parser or just look into mdn-data as source of truth for "collections". But later.


refactor classpath to use pluggable strategies

This work is described in #299. It refactored the classpath engine to use pluggable strategy objects, which will allow us to add additional mechanisms for computing classpath.

To see how this feature is implemented, search for usages of the primary (and currently only) strategy impl: BazelAspectJvmClasspathStrategy


[main] Format Go code

Cron -knative-prow-robot
/cc knative-sandbox/async-component-approvers
/assign knative-sandbox/async-component-approvers
Produced by: knative-sandbox/knobots/actions/update-gofmt
Details:

@AngeloDanducci integration tests are failing on the eventing-redis install:
++ cd ./eventing-redis
++ ko apply -f ./source/config
2022/11/18 14:06:51 Error enumerating files: lstat ./source/config: no such file or directory
++ fail_test

looking at https://github.com/knative-sandbox/eventing-redis/tree/main/config , should it be ko apply -f ./config/source instead?

/lgtm


Sites not found or blog removed from Blogger

amateurcreampie.org
camcordersex.com
casadoscornos.blogspot.com
creampieinternal.com
depositodevideos.com.br
incestland.com
triplexangels.com

@abbbw what are you saying here? Can you please clarify?  We don't carry most of these domains.

I'm sorry, I think I made a mistake. Well, just these ones (all are on the list):
depositodevideos.com.br
incestland.com
triplexangels.com
casadoscornos.blogspot.com
It seems that the browser is unable to connect to these domains, so I believe they can be removed from the list.

@abbbw we do not remove domains because browsers cannot connect to them. This is about so much more than browsers.
Closing.


[hotfix][docs] Fix page display errors and improve page Jump mode

1.Repair page display
2.Page Jump can jump normally in my local and GitHub tests, but it can't jump normally in the official website page. Therefore, I changed the jump related code. I can test the jump here, but I can't guarantee whether the official website page can jump normally
@leonardBang
I need help

@rookiegao The display issue is due to missed blank lines, I think you've fixed it. About the link that contains Chinese you can use in following way:

这是一个中文锚点测试[注意事项](#a-id-custom-text-a)

注意事项
--------------------------

I hope there is a practical case. The above reference does not work in my local test
The following is a practical case:

        MySQL type
        Flink SQL type
        NOTE

       GEOMETRY

       POINT

       LINESTRING

       POLYGON

       MULTIPOINT

       MULTILINESTRING

       MULTIPOLYGON

       GEOMETRYCOLLECTION

        STRING

      MySQL 中的空间数据类型将转换为具有固定 Json 格式的字符串。请参考 MySQL
      空间数据类型映射
       章节了解更多详细信息。

### 空间数据类型映射

This is the example of Chinese anchor you provided:
这是一个中文锚点测试[空间数据类型映射](#a-id-custom-text-a)

空间数据类型映射

How to apply this example to the above case？

@rookiegao Could you investigate the link in html element of markdown like

  is different with others?

@rookiegao Could you investigate the link in html element of markdown like

 is different with others?

@leonardBang
Modify the previous writing

Revised writing

Both writing methods are recognized by markdown (preview in GitHub source code can successfully jump to anchor point).
However, the first type of HTML does not know what it means. HTML recognizes the second type.
That is to say, there should be no problem with my current modification.
Jump link before modification (HTML unrecognized):
https://github.com/ververica/flink-cdc-connectors/blob/release-2.2/docs/content/connectors/mysql-cdc(ZH).md#空间数据类型映射
Modified jump link (HTML normal recognition):
https://github.com/rookiegao/flink-cdc-connectors/blob/fix_docs_Page_anchor_repair/docs/content/connectors/mysql-cdc(ZH).md#003

You can also verify this by clicking these two links. After the first click, you will just jump to the current page. After the second click, you will directly jump to the relevant anchor point.

Thanks @rookiegao for the detail investigation, but I found we need some adjustment even we use id=003 in my local env, could you have a double check?

You can also verify this by clicking these two links. After the first click, you will just jump to the current page. After the second click, you will directly jump to the relevant anchor point.

Thanks @rookiegao for the detail investigation, but I found we need some adjustment even we use id=003 in my local env, could you have a double check?

@leonardBang Fixed

With pleasure


[Feature request] Support update-image-vars on machines which do not have local copies of images

I'm happy to raise a PR to implement this, but wanted to raise it as a feature request first to see if it is functionality that you would actually like in artefactor.
Problem
We have the issue described in the README under "Content Adressable Repo Digests" - images are downloaded and pushed from one machine, and deployments happen from another machine which cannot contact the first.
Without publishing a list of 'new' image names from the machine which runs artefactor publish, we end up re-implementing the logic of update-image-vars in our own deploy scripts to generate the new image names before we pull the images.
This is well-documented and understandable behaviour, and can be worked around - but it would be useful to have update-image-vars be able to do this for us.
Proposal
Add a flag --from-remote-registry (or similar) to the update-image-vars command. When called, this would read the existing ARTEFACTOR_IMAGE_VARS and, for each image:

If the image was referenced without a SHA digest, simply transform to the new registry name (update-image-vars already does this)
If the image references a specific SHA digest, transform to <new_registry_name>:repoDigest-<original_SHA>
Fetch the manifest from the remote registry and confirm that images with these names/tags exist
Return the updated image values (as update-image-vars already does)

Does that sound reasonable / is this a useful PR for us to submit?

Hi Owen,
It's been a few months since I was working on this so I may be need to refresh my own memory.
Lets figure this out, given a machine which has not had images imported, just has the manifests and meta-data file, and has env vars of the required images, if a sha is used, transform it to <new_registry_name>:repoDigest-<original_SHA>
We might want to adjust that since we cant amend the original_sha to the end of a new sha since that would no longer be a content addressable repo digest.
you would need knowledge of the originating images and know how to address them on the new registry, i dont see a way to relate these without maintaining new meta-data outside of the process.
for example
take nginx:latest from docker hub, nginx:latest@sha256:a93c8a0b0974c967aebe868a186e5c205f4d3bcb5423a56559f2f9599074bbcd
we then translate this to new-registry/nginx@sha256:<newsha>
I think in fact the tag from the original source is also preserved, i'd have to review the code again to check.
the trouble is, unless the host running this process has the origin and destination sha metadata in the docker local store, it can't relate the two images. If you can point out how to do this without having the source and destination data and explain that to me we can find a way to do this. Otherwise i fear the slightly broken concept of using content addressable sha's to map an image from one registry to another is actually just the wrong approach.
Anyway, let me know what you think.

Thanks for replying so quickly.
In essence I think what I'm describing is similar to a dry run mode?
ie, given:

a list of image names (as ARTEFACTOR_IMAGE_VARS)
a registry URL

Output the names we would have used to upload them (minus the new SHA because we don't know it), and optionally check the remote manifest to see if they actually exist.
... if that makes sense?
Regarding security properties, I agree it's sadly a bit broken and that's just the way things have to work since we can never guarantee SHA consistency across repos.
The existing workaround for that (in artefactor) is to add a tag containing the original SHA digest:
https://github.com/appvia/artefactor/blob/70fe6bfe4e77e26cd80df5f4fcd6db3eb876006b/pkg/docker/docker.go#L88-L91
This is a (necessary) hack but useful and is what lets us download nginx if we know the original SHA of a93c8a0b0974c967aebe868a186e5c205f4d3bcb5423a56559f2f9599074bbcd without knowing the new SHA.
However as you've pointed out, we also can't verify (on our machine with no other knowledge of the source images) that it's exactly the same image because the tag can be applied by anybody with access and is not actually tied to the content. So it weakens the security proposition quite a bit.
In our case, that's unfortunate but we're willing to place enough trust on the machine which runs publish to accept that if it has tagged something as having a SHA, we will believe in it. It's a bit naff but it's slightly better than just running docker pull with no SHA at all.
Not everybody will be willing to take that risk, and so I think it's worth asking whether adding this and documenting it is enough, or whether that's adding too many sharp edges.
Overall, I think it would be a useful option but I don't want to add this upstream if you feel that the benefits are not justified by the complexity.

oh amazing, thanks for the PR, i'll review as soon as i have a chance.

Closing as per PR - we worked around this and I'm not sure anyone else is interested in this feature, so let's leave it alone. Thanks for the time spent discussing/reviewing.


Prevent generating git repo for Ember application

Following the original documentation, I accidentally created a Git repo for the Ember application inside the existing Git repo for the Rails app.  However, if you specify --skip-git when you create the Ember app, this can be avoided.

Merged in https://github.com/thoughtbot/ember-cli-rails/commit/7badc2581e0158bb8017cf5a24a39ea8d50b77df
Thanks!


Nespi4 Ubuntu install' scripts

Scripts specific to Nespi4 case and Ubuntu.
The install script downloads all required components and add an entry on Ubuntu's systemd, to run the SafeShutdown script at startup.
Also, there is a change on SafeShutdown.py, to add a visual feedback after press the Reset button.

Creating an updated Pull Request


Codecov github action

Summary
This PR introduces codecov.io as a tool to track codebase test coverage.
Description
In the #1 I tried setting up https://coveralls.io/ as a PHP project coverage tracking service. After a number of tries, I changed focus and tried how the process would be setup with https://about.codecov.io/ with success.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@3a58cd9). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop       #2   +/-   ##
==========================================
  Coverage           ?   85.71%
  Complexity         ?       24
==========================================
  Files              ?        1
  Lines              ?       49
  Branches           ?        0
==========================================
  Hits               ?       42
  Misses             ?        7
  Partials           ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3a58cd9...760e54e. Read the comment docs.


[release + cherry-pick] Switching over from iOS-15 to iOS-16 in .ci.yaml. (#118807)

fix post submit failures on beta hotfix release
This will run tests on new iphone11 devicelab devices which are running iOS-16.
Bug:https://github.com/flutter/flutter/issues/117237

Do not land until we can discuss on Monday.
We should change the devices that are being tested in release branches. Instead, we should look at reverting the infra changes to make it compatible for the release.

Thanks for the instructions Casey!

@XilaiZhang can you link to the GitHub issue here with the context why this change is needed?

@XilaiZhang can you link to the GitHub issue here with the context why this change is needed?

\cc @yusuf-goog @jmagman


Exclude *.map files from shipped extension

Extension Version: 2020.8.109390
I was looking into why Python was taking a little while to download on my machine. From a quick investigation, it looks like the datascience-ui  folder in the shipped extension contains three large .map files:
du -ah . | sort -rh | grep '\.map'

14M	./out/client/extension.js.map.disabled
7.1M	./out/datascience-ui/notebook/commons.initial.bundle.js.map
3.4M	./out/datascience-ui/viewers/commons.initial.bundle.js.map
216K	./out/datascience-ui/notebook/nativeEditor.js.map
128K	./out/datascience-ui/notebook/interactiveWindow.js.map
8.0K	./out/datascience-ui/viewers/plotViewer.js.map
8.0K	./out/datascience-ui/viewers/dataExplorer.js.map

These should usually be excluded as they are only needed during development

Although these files are explicitly allowed in the vscodeignore so this seems intentional: https://github.com/microsoft/vscode-python/blame/main/.vscodeignore#L4
Still these are around 1/5 of the extensions's side on disk so just want to confirm these are really required for the extension to work

Hey @mjbvz It's actually necessary, we have a setting which uses that logic. I'll post more details as soon as I can.

We ship source maps so we get the exact line numbers in our code. This was crucial for instances when we had unhandled exceptions.
Back in the early days we used to rename the source maps files as it used to adversely impact loading of the extension. I.e. if we had a *.js.map file, then extension loading times was very slow, hence we decided to rename it to *.js.map.disabled.
I tested this yesterday & couldn't find any per degradation anymore. I guess we can just ship it as is.
As for the source maps for the datascience-ui, we need that again to determine the exact line & file that threw an exception.
FYI - common.initial.bundle.js was excluded, as these this source map file contained source maps for 3rd party depedencies from npm packages, and we didn't need them, hence they were excluded. Looks like they have crept back into the extension.

@rchiodo @IanMatthewHuff Do we need the source maps for the DS ui code?

No I don't think so. We only need them when debugging, not when getting logs from users.

Summary

DS source map files can be removed from vsix
Core extension source map files - TBD

I set "python.diagnostics.sourceMapsEnabled": true in user settings, and activated the extension. I get Failed to initialize source map support in extension message and I don't get exact file and line numbers.

But when debugging the extension, I still get Failed to initialize source map support in extension, but get exact line & file which threw the errors.

Is this a bug? Is it only meant to work when debugging? I think source maps is not working for extensions in the marketplace.

We should remove the map files from the vsix
We should remove the setting (python.diagnostics.sourceMapEnabled)
Update our issue documentation to stop asking people to use the setting
Generate source map during build (and save them along the relesed vsix)