weaveproxy is not able to allocate IP addresses

I'm not able to start any container with weave.  Here are details of my system
docer info
Containers: 2
Images: 41
Server Version: 1.9.0
Storage Driver: overlay
 Backing Filesystem: extfs
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.2.0-16-generic
Operating System: Ubuntu 15.10
CPUs: 24
Total Memory: 62.91 GiB
Name: hotelsoft-local2
ID: W3PS:ZWLR:45EY:CBEE:ANMZ:C7E2:UIAV:X2Z2:2Q6F:K2PB:3CES:GLPP
WARNING: No swap limit support

weave version
weave script 1.2.0
weave router 1.2.0
weave proxy  1.2.0

weave status

       Version: 1.2.0

       Service: router
      Protocol: weave 1..2
          Name: 32:51:fc:ed:2b:14(hotelsoft-local2)
    Encryption: enabled
 PeerDiscovery: enabled
       Targets: 0
   Connections: 3 (3 established)
         Peers: 4 (with 12 established connections)

       Service: ipam
     Consensus: achieved
         Range: [<IP_ADDRESS>-<IP_ADDRESS>)
 DefaultSubnet: <IP_ADDRESS>/12

       Service: dns
        Domain: weave.local.
           TTL: 1
       Entries: 0

       Service: proxy
       Address: unix:///var/run/weave/weave.sock

When I run any container it just hangs
docker run -it --rm phusion/baseimage bash -l
This command just hangs.
Here is the log of weaveproxy
INFO: 2015/11/05 05:28:15.689494 POST /v1.21/containers/create
INFO: 2015/11/05 05:28:15.689682 Creating container with WEAVE_CIDR ""
INFO: 2015/11/05 05:28:15.778038 POST /v1.21/containers/d45ecd3682a9240986d11be855ffe733ee0817a6d6163c1ce0b7b634dd279b51/attach?stderr=1&stdin=1&stdout=1&stream=1
INFO: 2015/11/05 05:28:15.779542 POST /v1.21/containers/d45ecd3682a9240986d11be855ffe733ee0817a6d6163c1ce0b7b634dd279b51/start
INFO: 2015/11/05 05:28:15.925320 Attaching container d45ecd3682a9240986d11be855ffe733ee0817a6d6163c1ce0b7b634dd279b51 with WEAVE_CIDR "" to weave network

Here is the output of ps -eaf | grep weave
root      1342   849  0 20:51 ?        00:00:14 /home/weave/weaver --port 6783 --name 32:51:fc:ed:2b:14 --nickname hotelsoft-local2 --datapath weave --iface veth-weave --ipalloc-range <IP_ADDRESS>/12 --dns-effective-listen-address <IP_ADDRESS> --dns-listen-address <IP_ADDRESS>:53 --docker-api unix:///var/run/docker.sock
root      1628   849  0 20:51 ?        00:00:08 /home/weave/weaveproxy -H unix:///var/run/weave/weave.sock
root      1753     1  0 20:51 ?        00:00:00 /usr/bin/docker logs -f weave
root      3865  1628  0 21:28 ?        00:00:00 /bin/sh ./weave --local attach --rewrite-hosts --or-die d45ecd3682a9240986d11be855ffe733ee0817a6d6163c1ce0b7b634dd279b51
root      3916  3865  0 21:28 ?        00:00:00 /bin/sh ./weave --local attach --rewrite-hosts --or-die d45ecd3682a9240986d11be855ffe733ee0817a6d6163c1ce0b7b634dd279b51

Looks like weave is not able to attach IP addresses.
Please provide me some instructions on how to make things work.
-Kesav

please send us the output of weave report.

{
    "Version": "1.2.0",
    "Router": {
        "Protocol": "weave",
        "ProtocolMinVersion": 1,
        "ProtocolMaxVersion": 2,
        "Encryption": true,
        "PeerDiscovery": true,
        "Name": "32:51:fc:ed:2b:14",
        "NickName": "hotelsoft-local2",
        "Port": 6783,
        "Interface": "veth-weave (via pcap)",
        "CaptureStats": {
            "PacketsDropped": 0,
            "PacketsIfDropped": 0,
            "PacketsReceived": 11
        },
        "MACs": null,
        "Peers": [
            {
                "Name": "32:51:fc:ed:2b:14",
                "NickName": "hotelsoft-local2",
                "UID":<PHONE_NUMBER>5616940483,
                "ShortID": 1120,
                "Version": 12,
                "Connections": [
                    {
                        "Name": "f6:f1:a1:20:85:49",
                        "NickName": "hotelsoft-local3",
                        "Address": "<IP_ADDRESS>:52806",
                        "Outbound": false,
                        "Established": true
                    },
                    {
                        "Name": "e2:f7:eb:e6:1d:05",
                        "NickName": "hotelsoft-local4",
                        "Address": "<IP_ADDRESS>:33188",
                        "Outbound": false,
                        "Established": true
                    },
                    {
                        "Name": "3a:a6:1b:6e:98:51",
                        "NickName": "c130",
                        "Address": "<IP_ADDRESS>:36315",
                        "Outbound": false,
                        "Established": true
                    }
                ]
            },
            {
                "Name": "3a:a6:1b:6e:98:51",
                "NickName": "c130",
                "UID":<PHONE_NUMBER>978504253,
                "ShortID": 0,
                "Version": 177,
                "Connections": [
                    {
                        "Name": "e2:f7:eb:e6:1d:05",
                        "NickName": "hotelsoft-local4",
                        "Address": "<IP_ADDRESS>:6783",
                        "Outbound": true,
                        "Established": true
                    },
                    {
                        "Name": "32:51:fc:ed:2b:14",
                        "NickName": "hotelsoft-local2",
                        "Address": "<IP_ADDRESS>:6783",
                        "Outbound": true,
                        "Established": true
                    },
                    {
                        "Name": "f6:f1:a1:20:85:49",
                        "NickName": "hotelsoft-local3",
                        "Address": "<IP_ADDRESS>:6783",
                        "Outbound": true,
                        "Established": true
                    }
                ]
            },
            {
                "Name": "f6:f1:a1:20:85:49",
                "NickName": "hotelsoft-local3",
                "UID":<PHONE_NUMBER>893196860,
                "ShortID": 1627,
                "Version": 8,
                "Connections": [
                    {
                        "Name": "e2:f7:eb:e6:1d:05",
                        "NickName": "hotelsoft-local4",
                        "Address": "<IP_ADDRESS>:43660",
                        "Outbound": false,
                        "Established": true
                    },
                    {
                        "Name": "32:51:fc:ed:2b:14",
                        "NickName": "hotelsoft-local2",
                        "Address": "<IP_ADDRESS>:6783",
                        "Outbound": true,
                        "Established": true
                    },
                    {
                        "Name": "3a:a6:1b:6e:98:51",
                        "NickName": "c130",
                        "Address": "<IP_ADDRESS>:55908",
                        "Outbound": false,
                        "Established": true
                    }
                ]
            },
            {
                "Name": "e2:f7:eb:e6:1d:05",
                "NickName": "hotelsoft-local4",
                "UID":<PHONE_NUMBER>217879103,
                "ShortID": 3538,
                "Version": 8,
                "Connections": [
                    {
                        "Name": "32:51:fc:ed:2b:14",
                        "NickName": "hotelsoft-local2",
                        "Address": "<IP_ADDRESS>:6783",
                        "Outbound": true,
                        "Established": true
                    },
                    {
                        "Name": "3a:a6:1b:6e:98:51",
                        "NickName": "c130",
                        "Address": "<IP_ADDRESS>:36264",
                        "Outbound": false,
                        "Established": true
                    },
                    {
                        "Name": "f6:f1:a1:20:85:49",
                        "NickName": "hotelsoft-local3",
                        "Address": "<IP_ADDRESS>:6783",
                        "Outbound": true,
                        "Established": true
                    }
                ]
            }
        ],
        "UnicastRoutes": [
            {
                "Dest": "32:51:fc:ed:2b:14",
                "Via": "00:00:00:00:00:00"
            },
            {
                "Dest": "3a:a6:1b:6e:98:51",
                "Via": "3a:a6:1b:6e:98:51"
            },
            {
                "Dest": "f6:f1:a1:20:85:49",
                "Via": "f6:f1:a1:20:85:49"
            },
            {
                "Dest": "e2:f7:eb:e6:1d:05",
                "Via": "e2:f7:eb:e6:1d:05"
            }
        ],
        "BroadcastRoutes": [
            {
                "Source": "e2:f7:eb:e6:1d:05",
                "Via": null
            },
            {
                "Source": "32:51:fc:ed:2b:14",
                "Via": [
                    "3a:a6:1b:6e:98:51",
                    "f6:f1:a1:20:85:49",
                    "e2:f7:eb:e6:1d:05"
                ]
            },
            {
                "Source": "3a:a6:1b:6e:98:51",
                "Via": null
            },
            {
                "Source": "f6:f1:a1:20:85:49",
                "Via": null
            }
        ],
        "Connections": [
            {
                "Address": "<IP_ADDRESS>:36315",
                "Outbound": false,
                "State": "established",
                "Info": "sleeve 3a:a6:1b:6e:98:51(c130)"
            },
            {
                "Address": "<IP_ADDRESS>:52806",
                "Outbound": false,
                "State": "established",
                "Info": "sleeve f6:f1:a1:20:85:49(hotelsoft-local3)"
            },
            {
                "Address": "<IP_ADDRESS>:33188",
                "Outbound": false,
                "State": "established",
                "Info": "sleeve e2:f7:eb:e6:1d:05(hotelsoft-local4)"
            }
        ],
        "Targets": null,
        "OverlayDiagnostics": {
            "sleeve": null
        }
    },
    "IPAM": {
        "Paxos": null,
        "Range": "[<IP_ADDRESS>-<IP_ADDRESS>)",
        "DefaultSubnet": "<IP_ADDRESS>/12",
        "Entries": [
            {
                "Token": "<IP_ADDRESS>",
                "Peer": "82:65:f9:36:ad:75",
                "Version": 34
            }
        ],
        "PendingClaims": null,
        "PendingAllocates": null
    },
    "DNS": {
        "Domain": "weave.local.",
        "Address": "<IP_ADDRESS>:53",
        "TTL": 1,
        "Entries": null
    }
}

So the entire IP allocation range is owned by 82:65:f9:36:ad:75, which doesn't seem to be alive.
The question is how you got into this state...
Did you do a "rolling" weave reset? See #1593
Did you shut down nodes without subsequently running weave rmpeer? See http://docs.weave.works/weave/latest_release/ipam.html#stop

I just installed all new version of weave on all 3 nodes and restarted the machines.  Is there any way to undo this state?

I just installed all new version of weave on all 3 nodes and restarted the machines.

Did you restart them one at a time?

Is there any way to undo this state?

Yes, see the rmpeer link above.

Just used ansible to restart all 3 nodes.  They were all restarted at the same time

they were all restarted at the same time

did all the nodes first get shut down, and then restarted? Or is it possible that some node restarted while another was still alive?

Yes the node was shutdown while others were running.  I was updating the storage drive to overlay so I did one node at a time.  Like restarting node one at a time.  So it could be possible during that time things might have got messed up.

Resolved by removing dead peer.
Thanks @rade for the inputs.


Windows lit test runner is showing tests passed that failed

Noticed this because the lit tests have a bug where they have the wrong path in the test definition, and they were showing as passed on Windows (when installed). Picking one:
ctest -R unused_args.mlir.test -V
UpdateCTestConfiguration  from :D:/temp/iree/tests/DartConfiguration.tcl
UpdateCTestConfiguration  from :D:/temp/iree/tests/DartConfiguration.tcl
Test project D:/temp/iree/tests
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 65
    Start 65: iree/test/e2e/regression/unused_args.mlir.test

65: Test command: D:\temp\iree\tests\bin\run_lit.bat "D:/a/iree/iree/main_checkout/iree/test/e2e/regression/unused_args.mlir"
65: Test timeout computed to be: 10000000
65: Get-Content : Cannot find path 'D:\a\iree\iree\main_checkout\iree\test\e2e\regression\unused_args.mlir' because it does not exist.
65: At D:\temp\iree\tests\bin\run_lit.ps1:67 char:15
65: + $test_lines = Get-Content -Path $test_file
65: +               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
65:     + CategoryInfo          : ObjectNotFound: (D:\a\iree\iree\...nused_args.mlir:String) [Get-Content], ItemNotFoundException
65:     + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetContentCommand
65:
1/1 Test #65: iree/test/e2e/regression/unused_args.mlir.test ...   Passed    0.32 sec

The following tests passed:
        iree/test/e2e/regression/unused_args.mlir.test

It may be time to kill this hoakey script.

Probably due to the run_lit.bat not checking the errorlevel of the called powershell script? Or some other such silliness that is a throwback to 1980?

Probably due to the run_lit.bat not checking the errorlevel of the called powershell script? Or some other such silliness that is a throwback to 1980?

We have killed the hoaky script with https://github.com/google/iree/pull/9405


Propagate newlines correctly on error messages

This resolves #345 for me. It's not ideal as I think the fix can happen upstream in shaderc, however this provides a more mature way to deal with error output. If it's appropriate or there is interest I can add color/bold terminal codes to make the error output more clear.
I'm a bit confused exactly what is happening here. I believe the issue is in shaderc. This is also bit of a hacky fix to correct the output of shaderc so there is a newline after the initial message: 22 compilation error(s):
The newline characters are outputting on my Linux terminal, but they're not actually causing a newline to happen? I tried it every which way and this is the simplest solution which works for me.
When I have more time I will try and fix this upstream in shaderc.

Reading up on:
https://github.com/vulkano-rs/vulkano/issues/345
Binearo says that they cannot reproduce the issue.  Is this still alive or should we close the PR as fixed in upstream?

I've reproduced this since several times.  Especially when there are 3-4 error messages, it's hard to see through.  Newlines are coming out escaped I believe.

Is this still a thing and does this patch still work?

haven't tested in awhile. I'll check in a couple days
On Sun, Oct 20, 2019 at 11:50 PM Austin Johnson<EMAIL_ADDRESS>wrote:

Is this still a thing and does this patch still work?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vulkano-rs/vulkano/pull/1172?email_source=notifications&email_token=AAF5FXWPPMMAVPIW3UXZBG3QPU7JLA5CNFSM4GY3UKP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBZEFMA#issuecomment-544359088,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAF5FXR52325X5I72A2JD6LQPU7JLANCNFSM4GY3UKPQ
.


Investigate formatting over LSP

I was able to get a prototype of formatting over LSP working with black.


Add negative test case for Clocks equality check

I'm not sure what to make of the appveyor error, everything is working fine locally. Has anyone seen this before?

@mattcbaker We also have the same error;. It appears AppVeyor changed their paths sometime recently. I will try to look at it this weekend.
It's a good thing we have the Travis build too, as the build is successful there. I'll merge this PR. Thanks a lot! :tada:

@mattcbaker I've just merged this PR which fixes the AppVeyor build error.


system calls are vulnerable to Spectre V1 attacks on CPUs with speculative execution

Describe the bug
This paper is a good summary:
https://arxiv.org/pdf/1902.05178.pdf
We have, either in-tree or in code review, mitigations for Meltdown, Foreshadow, Spectre V2, Spectre V4. Although recent research has a poor prognosis on ever mitigating all of these attacks on affected CPUs, we would like to at least ensure that bounds-check-bypass style attacks (Spectre V1) cannot be performed with system call arguments which index some array.

I spent much time looking at system calls.
For drivers, in my analysis the only APIs that seemed concerning were:

DMA driver channel argument
GPIO pin arguments
Flash driver offsets/lengths

For x86 minnowboard and upsquared apollo lake, didn't find any relevant drivers except apollo lake GPIO, which I patched.
Socket syscall fds also needed to be patched.


rerun if RUSTC changes

Currently rustversion uses RUSTC to determine which executable to ask for a version. If RUSTC changes, then it is possible that the version information changes as well, so should rerun in that case.

One such situation in which rustversion does the wrong thing is when you run:
cargo run then change to RUSTC=rustc_with_other_version_or_nightlyness cargo run. The second run will not pickup on the changed version because rustversion does not currently think it should rerun if RUSTC changed.

Cargo already runs $RUSTC -vV and re-runs all build scripts when the rustc version is changed. The relevant thing is the rustc version, not the $RUSTC environment variable. If $RUSTC changes but the rustc version does not, there is no need to rebuild. If $RUSTC does not change but the rustc version does, we do rebuild.
If the only issue is that your wrapper only recognizes -V and not -vV, then I would prefer not to accept this change.

Ah, indeed the wrapper started out not supporting "-vV". I will retest with that support. Thanks for the tip!


Think of a good TOC and layout of the docs

Current docs structure looks a bit odd - starting with dev/cont part and then intro. We should rehash this at one stage

@gregorgorjanc  Below is what I come up with
AlphaPeel/
├─ Introduction/
│  ├─ Availability
│  ├─ Conditions of use
│  ├─ Disclaimer
├─ Getting started/
│  ├─ Install AlphaPeel (add later)
│  ├─ Graphical representation (add later)
│  ├─ An example (add later)
├─ Usage/
│  ├─ Program options
│  │  ├─ ...
│  ├─ File formats
│  │  ├─ Input file formats
│  │  │  ├─ ...
│  │  ├─ Output file formats
│  │  │  ├─ ...
├─ Contribution and Development Guide/
│  ├─ Fork the repository
│  ├─ Clone your forked repository
│  ├─ Make changes in your clone
│  ├─ Update submodules?
│  ├─ Create a pull request
│  ├─ Update the version of the package to publish the package

@XingerTang looks great to me! It would be good to discuss this with Audrey too https://github.com/AudreyAAMartin - will ask her on Slack to weigh in here


Code Gist provided for Android on the Integrating Existing Projects Page does not work

[ ] Review the documentation: https://docs.viromedia.com/
[ ] Search for existing issues: https://github.com/viromedia/viro
[ ] Use the latest ViroReact release: https://docs.viromedia.com/docs/releases

Environment
Please provide the following information about your environment:

Development OS: Mac, Windows, Linux
Device OS & Version: What Android OS version (7.0, 8.0, etc.) or iOS version (11.0, 11.2) is your device running on?
Version: ViroReact version and React Native version
Device(s): What device(s) are you are seeing the issue on (i.e. iPhone X, Samsung Note 8, etc)

Description
Describe your issue in detail. Include screenshots if needed. If this is a regression, let us know.
Reproducible Demo
Let us know how to reproduce the issue. Include a code sample, screen capture, video recording. The more information you provide, the better we can support you.
The Instructions provided on the Integrating with Existing RN Pages link -> https://docs.viromedia.com/docs/integrating-with-react-native-projects
might need to be updated. Particularly this Gist, which does not appear to be working -> https://gist.github.com/achuvm/fe0136818158bec2cdf4d1cd11053f6d

The gist has since been updated to reflect the latest changes.


Install dependencies on system Python, not in a virtualenv (for Docker)

[x] I have searched the issues of this repo and believe that this is not a duplicate.

Issue
I would like to be able to install dependencies directly in the system Python library, not in a virtualenv. It's specifically targeted at Docker use-cases.
Previously with pipenv I was doing RUN pip install pipenv && pipenv install --system. It was very useful because:

it avoids the overhead of a virtualenv (we are already isolated in a container)
it allows to run commands without poetry shell or poetry run, as commands are directly available on the PATH.

I really don't know the internals of Poetry so I'm not sure if this is easily feasible, but I would absolutely love such a feature.

Actually I just saw this issue: https://github.com/sdispater/poetry/issues/218, and it seems to work fine, sorry!


System.UnauthorizedAccessException: Access to the path 'C:\Users\hello\AppData\Local\Bloxstrap\Bloxstrap.exe' is denied.

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] My answer given in the checkbox above is a lie.

What problem did you encounter?
System.UnauthorizedAccessException: Access to the path 'C:\Users\hello\AppData\Local\Bloxstrap\Bloxstrap.exe' is denied.

Read the Wiki.


As a host, I want to be able to copy my poll-ID with a simple button click

E.g. a button in the LQRunningPollView

Implemented


openwrt version

Looks like a great script, would be nice to have a version of it for openwrt. I think it might need a bit of modification as openwrt is quite minimal and doesnt have getent. Please consider it :) thanks!

Hi @juoza. Thanks for the suggestion. I never thought of it, but it sounds like a nice idea. I don't currently own an OpenWRT-based device, but I could just use a VM, I guess. I'm between holidays right now, so I won't look at this for a while, but I will get around to it eventually.

Depends on #32.


Expression: rewrite with antlr4

Use Antlr4 to rewrite ExpressionEngine. For
1.Reduce the development difficulty caused by new requirements
2.Reduce development effort with multi-language sdk support ( js, python, java)

As I stated in teams channel, the reason to rewrite with antlr4, is to gain a more readable, maintainable, portable code base. By doing so, we now be able to

remove the hacks put into ExpressionEngine to support member function in LG
a more readable grammar definition easy to understand and maintain, you would say it's very natural with the support of antlr4, without worrying about left recursion. Even a new hire without any related background can reason over it.
we also delegate the operations (add, sub, mul..) to functions, which means a+b is equivalent to add(a, b), and also means operator can even be overloaded.

Overall I believe this will set a good foundation to further feature enrichment .


Compliance smoke test suite for stateful resources

There's copy/paste code today. Centralize that in WolverineFx.Compliance and reuse

Nah, don't worry about this one


update novelupdates & lightnovelpub & kolnovel

add lightnovelstranslations to chapterText check
add inoveltranslation to chapterText check (fixes https://github.com/LNReader/lnreader-sources/issues/483)

fixes https://github.com/LNReader/lnreader-sources/issues/494

Add a search to lightnovelpub

added a fix (maybe) for KoLnovel's AI text
https://github.com/LNReader/lnreader-sources/issues/504
https://github.com/LNReader/lnreader-sources/issues/508
cant confirm since I cant read Arabic but it's consistent in 3 novels i've tested.

refactor indowebnovel (fixes https://github.com/LNReader/lnreader-sources/issues/470)
remove adsbygoogle message in sakuranovel description

my pr not updating, i go delete my repo and make new pr


[TalkBack] Semantics sortKey not honored in stacks in certain situations on Android

When using a Stack with an element top aligned, and above other elements in the Z-space, sortKey is honored on iOS but not on Android.
The following code reproduces this issue.
import 'package:flutter/material.dart';
import 'package:flutter/rendering.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: SemanticsOrderingHomePage(),
    );
  }
}

class SemanticsOrderingHomePage extends StatefulWidget {
  const SemanticsOrderingHomePage();

  _SemanticsOrderingHomePageState createState() => _SemanticsOrderingHomePageState();
}

class _SemanticsOrderingHomePageState extends State<SemanticsOrderingHomePage> {

  Widget buildWorkingSemantics(context) {
    return Scaffold(
        body: Center(
            child: Column(
              mainAxisSize: MainAxisSize.min,
              children: <Widget>[
                Semantics(
                    sortKey: OrdinalSortKey(2.0),
                    child: Text("Test 1")
                ),
                Semantics(
                    sortKey: OrdinalSortKey(1.0),
                    child: Text("Test 2")
                )
              ],
            )
        )
    );
  }

  Widget buildNonWorkingSemantics(context) {
    return Scaffold(
        body: Stack(
          alignment: Alignment.topCenter,
          children: <Widget>[
            Semantics(
              container: true,
              explicitChildNodes: true,
              sortKey: OrdinalSortKey(1),
              child: Container(
                color: Colors.red,
                child: Center(
                    child: Column(
                      mainAxisSize: MainAxisSize.min,
                      children: <Widget>[
                        Text("Test 11"),
                        Text("Test 22")
                      ],
                    )
                ),
              ),
            ),
            Semantics(
                container: true,
                explicitChildNodes: true,
                sortKey: OrdinalSortKey(2),
                child: Padding(
                    padding: EdgeInsets.only(top: 48.0),
                    child: Semantics(
                      label: "Test top semantics",
                      button: true,
                      container: true,
                      enabled: true,
                      child: GestureDetector(
                          onTap: () {
                            if (mounted) {
                              print("pressed");
                            }
                          },
                          child: Container(
                              height: 48.0,
                              decoration: BoxDecoration(
                                color: Colors.grey,
                                borderRadius: BorderRadius.circular(10.0),
                              )
                          )
                      ),
                    )
                )
            ),
          ],
        )
    );
  }

  @override
  Widget build(BuildContext context) {
    //return buildWorkingSemantics(context);
    return buildNonWorkingSemantics(context);
  }
}

Basically, when building the buildNonWorkingSemantics() tree, it can be seen that it works as expected on iOS but not on Android. Expected result is that the "Test top semantics" is the last element to be read/focused, but on Android it's the first.
Building the buildWorkingSemantics() tree, columns work fine on Android.

flutter doctor -v
[✓] Flutter (Channel dev, v1.16.2, on Mac OS X 10.14.6 18G4032, locale en-US)
• Flutter version 1.16.2 at /Users/danny.valente/Library/flutter/1.16.2-dev
• Framework revision 58cad787d8 (11 days ago), 2020-03-23 08:33:41 -0700
• Engine revision 2d42c74a34
• Dart version 2.8.0 (build 2.8.0-dev.16.0 ba8baa46b4)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/danny.valente/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
• All Android licenses accepted.
[!] Xcode - develop for iOS and macOS (Xcode 11.3.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.3.1, Build version 11C505
! CocoaPods 1.7.5 out of date (1.8.0 is recommended).
CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
Without CocoaPods, plugins will not work on iOS or macOS.
For more info, see https://flutter.dev/platform-plugins
To upgrade:
sudo gem install cocoapods
[✓] Android Studio (version 3.6)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 44.0.2
• Dart plugin version 192.7761
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

Issue replicable on latest stable (1.20.4).
On Android, the accessibility focus on top widget first, while on iOS, it focuses as last (as expected).

flutter doctor -v
[✓] Flutter (Channel stable, 1.20.4, on Mac OS X 10.15.4 19E2269, locale en-IN)
    • Flutter version 1.20.4 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision fba99f6cf9 (3 days ago), 2020-09-14 15:32:52 -0700
    • Engine revision d1bc06f032
    • Dart version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.46.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (2 available)
    • Deepti 's iPhone (mobile)           •
      0554e90e563e81fd41bfd2ff9a2c6960595b9825 • ios • iOS 12.4.5
    • iPhone SE (2nd generation) (mobile) • 312977A7-2DB1-4737-AEBB-35FA6522A309
      • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-5 (simulator)

• No issues found!

Hi @dannyvalentesonos, this issue seems to have been fixed on the latest stable channel as I cannot reproduce it there. See the demo below. Verified on Realme 6, Android 11.

Demo video
https://user-images.githubusercontent.com/104349824/224279002-57454f64-187a-4a5f-b8b5-5649ecebc4d6.mp4

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.7.7, on macOS 13.0.1 22A400 darwin-x64, locale en-EE)
    • Flutter version 3.7.7 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2ad6cd72c0 (10 hours ago), 2023-03-08 09:41:59 -0800
    • Engine revision 1837b5be5f
    • Dart version 2.19.4
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.76.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.60.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 110.0.5481.177

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.9.0-1.0.pre.144, on macOS 13.0.1 22A400 darwin-x64, locale en-EE)
    • Flutter version 3.9.0-1.0.pre.144 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ac550c6356 (39 minutes ago), 2023-03-09 21:59:21 -0500
    • Engine revision e9ca7b2c45
    • Dart version 3.0.0 (build 3.0.0-313.0.dev)
    • DevTools version 2.22.2
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.76.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.60.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 110.0.5481.177

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

I'll be closing this issue since it has already been fixed on the stable channel. If you still experience this issue on the stable channel, kindly leave a comment below and I will reopen this. Thank you!


Add named default async export test case

Adds a test case that currently breaks:

To test this out in a CLI:
node /Users/keving/Uber/fusionjs/fusion-cli/bin/cli.js dev --port=63840 --no-open --dir=/Users/keving/Uber/fusionjs/fusion-cli/test/fixtures/named-async-main

Rolling this into the new webpack4 branch.


Implement Specification of file path

Implementing #54

Coverage increased (+0.6%) to 78.039% when pulling 2b832b43b0683336561258e6fa156d9396273ef8 on features/specify_path into a8b01bfcf148d5b80662475527d451c37c016b49 on master_V0.4.


cuda>=12.1 error running TGI using docker on 2x A100s

System Info
1.3.4 TGI Docker image on a runpod 2x A100
Information

[X] Docker
[ ] The CLI directly

Tasks

[ ] An officially supported command
[ ] My own modifications

Reproduction
Run this Runpod template on 2x A100s.
Error
2024-01-02T23:56:01Z Digest: sha256:b68d9f4bd3a4e3978d23ea188bded199dca8fd72ad377b156c8398e92644ae2e
2024-01-02T23:56:01Z Status: Downloaded newer image for ghcr.io/huggingface/text-generation-inference:latest
2024-01-02T23:56:02Z create container ghcr.io/huggingface/text-generation-inference:latest
2024-01-02T23:56:02Z latest Pulling from huggingface/text-generation-inference
2024-01-02T23:56:02Z Digest: sha256:b68d9f4bd3a4e3978d23ea188bded199dca8fd72ad377b156c8398e92644ae2e
2024-01-02T23:56:02Z Status: Image is up to date for ghcr.io/huggingface/text-generation-inference:latest
2024-01-02T23:56:02Z start container
2024-01-02T23:56:03Z error starting container: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: requirement error: unsatisfied condition: cuda>=12.1, please update your driver to a newer version, or use an earlier cuda container: unknown

Expected behavior
This runs fine on A6000 and also on the latest H100.

You probably selected a host with old drivers. Try an A100 host in secure cloud on KS-1 or KS-2 data centers.

Thanks, appreciate that.
I suppose I could try to manually upgrade the drivers via a custom docker image? Or that's not possible from a docker image?

No, they are the drivers on the host. If you run nvidia-smi on the host you can see the driver version. Pay attention to the CUDA version on the top right.
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.129.03             Driver Version: 535.129.03   CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+


FAIL: testSet (settings_datastore_test.DatastoreSettingsTest)

For a while now this Simian test has been failing for me. I think it's a DST timezone issue.
I get this output:
Testing settings_datastore_test
...F
======================================================================
FAIL: testSet (settings_datastore_test.DatastoreSettingsTest)
testSet (settings_datastore_test.DatastoreSettingsTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "src/tests/simian/settings_datastore_test.py", line 98, in testSet
    datetime.timedelta(seconds=1), datetime.datetime.now() - stamp)
AssertionError: datetime.timedelta(0, 1) not greater than datetime.timedelta(0, 3600, 3474)

The issue is that the timestamp returned by models.Settings.GetItem('long_name') is an hour in the past. I temporarily fixed it by changing this line to:
datetime.timedelta(seconds=3601), datetime.datetime.now() - stamp)

Does changing datetime.datetime.now() to datetime.datetime.utcnow() helps?

@maximermilov: Yes - that works

Fixed in https://github.com/google/simian/commit/2a3f021f9c17b8cf11c29b8d32324a76be37dac1


Issue with subfolder image search with graph

Category

[ ] Question
[ ] Documentation issue
[X] Bug

Expected or Desired Behavior
The search within subfolders should return also images.
Observed Behavior
I have an issue when searching for images scoped on a subfolder and it's children. The same issue does not seem to occur when searching for text files. I've noticed this issue both on OneDrive and Teams drives.
Steps to Reproduce
Example: My OneDrive looks like this:
Root/
    subdirectory/
        image.png
        textfile.txt

If I query:
/me/drive/items/{id-of-subdirectory}/search(q='textfile')
my result will contain the file that I'm searching for (with the addition of the subdirectory itself):
"value": [
    {
        "id": "id-of-subdirectory",
        "name": "subdirectory"
    },
    {
        "id": "id-of-textfile.txt",
        "name": "textfile.txt"
    }
]

But if I query for the image:
/me/drive/items/{id-of-subdirectory}/search(q='image')
my result doesn't contain the image (only the subdirectory)
"value": [
    {
        "id": "id-of-subdirectory",
        "name": "subdirectory"
    }
]

What is the reason for why the image isn't showing up in the search result?
Is there another way to perform searching scoped to a particular subfolder and it's children?
Note: I posted this question some time ago on StackOverflow without any response:
https://stackoverflow.com/questions/49534903/microsoft-graph-issue-with-onedrive-subfolder-image-search

Thanks for your feedback. Unfortunately this is a known issue that is on our backlog to address.

same issue here.
we have a Business license.
we use an account just to serve images through API from a OneDrive shared folder of another account;
it seemed to be working, until we moved all images directly in the service account, and now search doesn't work properly.
while at first it seemed it didn't find any image at all, after several sample checks i noticed that a few in some folders are returned; i haven't been able to pin down what's so special about these lucky ones:
i double checked app permissions ( though i'm troubleshooting directly with the graph explorer ) and items sharing;
i waited hours and days hoping that maybe they needed to be indexed, but nothing; also i can't find a pattern in created/lastModified DateTime, because no image after December 2019 is returned, but just a few of last year images are.
i managed to get some result for the first time searching just "jpg", instead than by name, but right now while i'm writing i searched again, and no result any more.
in addition, unless i missed something, querying a specific drive and/or folder is pointless, because i've always got results from the whole account, shared files included.
link to duplicated issue
https://github.com/microsoftgraph/microsoft-graph-docs/issues/4209

same issue here...
When listing all files via '/children" in a folder the images are present. Only when i am using the "/search" on the same folder i am not getting any results.

This issue is open since nearly a year. Any progress ?

@chackman Any update on this?

Hi @chackman , I'm also facing same issue. do you have any updates on this?

I used POST api to search the image files and it is working.
API end point:
https://graph.microsoft.com/beta/search/query
Method: POST
Body: {
"requests": [
{
"entityTypes": [
"driveItem"
],
"query": {
"queryString": "test.png parentLink::"\https://tescoo365dev.sharepoint.com/sites/HUB1/Shared Documents/folder1""
}
}
]
}

Any updates? Having the same issue

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Doesn't work on Obsidian

neofetch --stdout output
OS: Fedora Linux 38 (Workstation Edition) x86_64
Host: Zenbook 15 UM3504DA_UM3504DA 1.0
Kernel: 6.5.5-200.fc38.x86_64
Shell: zsh 5.9
Resolution: 2880x1620
DE: GNOME 44.5
WM: Mutter
WM Theme: Sweet
Theme: Sweet [GTK2/3]
Icons: candy-icons [GTK2/3]
Terminal: gnome-terminal
CPU: AMD Ryzen 7 7735U with Radeon Graphics (16) @ 4.819GHz
GPU: AMD ATI Radeon 680M

Sorry I can't give more details even launching Obsidian in the Terminal doesn't tell much

The Obsidian plugin is up and running if you haven't tried that. I got it running pretty easily running Xorg via Debian


Add support for predefined locations

Add defaultLocations (Or fixtures) optional prop to provide a predefined locations in the dropdown

I've just implemented something similar this morning on my fork. (Note that this branch is built off my other pull request that fixes IE11 missed key events)
We're implementing these changes in production later this week as we need preferred results to appear at the top, would be great if we could merge all changes upstream so I don't have to maintain the fork.
Happy to discuss the changes and make more if needed.
https://github.com/stevokk/react-places-autocomplete/tree/feature/preferred-locations

Just as a note on this, you'll see I had issues around clearItemsOnError due to it reprocessing results when used with onSearch. I've added documentation about not combining these parameters but am yet to solve the underlying issue in a nice way.. My only idea right now is to keep a cache of the google predictions result so that when ZERO_RESULTS comes back and they want the keep the results, it doesn't pass back in the possibly modified result set to onSearch.
I'm rambling but just wanted to give you some context as to the changes.


Question: Does Accelerate support pipeline parallelism?

I want to implement pipeline parallelism for large language(does not fit to single gpu) models pretrained and saved in huggingface hub.
Does accelerate support pipeline parallelism for large LM saved in huggingface hub?
I'm also wondering whether is there any stronger way than pipeline parallelism to make large LM that does not fit to single gpu to load in multi gpu?

Please use the forums for questions like this :-)
Accelerate does not support pipeline parallelism for models yet.

Thanks!


Incompatible with Flutter's most recent version

Error (Xcode): ../../.pub-cache/hosted/pub.dev/blinking_text-1.0.2/lib/src/blinking_text.dart:196:20: Error: Member not found: 'MediaQuery.boldTextOverride'.

Please update to the latest version to address the issue.


Add slack-email-digest tool to infra scripts.

Original script from mmerli's personal repo to be added to pulsar test infra.

@eolivelli instead of creating diff repo, we could also copy the folder in bookkeeper/.test-infra/

Yes!


API error - /api/Users/{id}/RoleClaims

Hi,

Requested to fetch Role claims using user Id, it showing mapper error

Hi,
Thanks for reporting this issue, I will check it.

Do you use the latest version of Admin UI?

I'm using - New release 1.0.0-rc1

Thanks, let me check it

@skoruba @anthonynewlineinfo If you use AutoMapper with DI like services.AddAutoMapper(), mapper error will heppen. I have encountered this error and use custom servive code solved this problem.
sample code

Hi @anthonynewlineinfo,
You can fix it temporarily by adding code below in IdentityMapperProfile.cs
CreateMap<TRoleClaimsDto, RoleClaimsApiDto>(MemberList.Source);
CreateMap<TRoleClaimDto, RoleClaimApiDto>(MemberList.Destination);
CreateMap<TRoleClaimsDto, RoleClaimApiDto>(MemberList.Destination);
Thanks!

Thanks for reminder for this, I will add it into next release.


#N/A Add a new rule git_branch_exists

Coverage decreased (-0.4%) to 90.355% when pulling 0c98053f743f8fcf6c8e248827b08e52a1ee13a4 on scorphus:git-branch-exists into 17b2fba48d241d7ff44838a4aa3e28682c57b460 on nvbn:master.

Thanks!
I've changed rule a bit.

Cool! I like your changes, thanks!


[Person] More

Not parsing anymore

Hey I don't know if this is apart of this issue or not but the person's website value is sometimes corrupted with html data, for example:
http://jikan.me/api/person/692
or
http://jikan.me/api/person/873

After some googling and playing around I think what might work best is if you use the "non-greedy" flag in your groups, e.g.:
Website: (.*?)
Here's an example of it working:
https://regex101.com/r/edmRQB/1

Hi @nicharesuk , thank you for bringing this to my attention and providing a solution. Allow me a few days to address this issue!

Another, and potentially cleaner, option other than using regex would be to use an HTML parser. I think PHP has one built in that could be used. That way you don't have to worry about regex doing something unexpected and you can be sure it's MAL whose changed things.

@nicharesuk I've pushed a hotfix for these the website issues and some other malformed data.
https://jikan.me/api/v1.2/person/692
The non-greedy flag did the trick, kindly use endpoint v1.2
https://jikan.me/api/v1.2/{request}/{param}
I used ReGex since I had more experience with it, but you're right. ReGex is not the way to go with web parsing. I will definitely change it in the future - just not now due to lack of time.

Finally fixed! It's working amazingly good.
Available in JikanPHP 1.0.0+ or REST 2.0+


Come up with a good injectivity story for PolyKinds

Richard suggests that we need a good story how kinds fit into the injectivity story. Here's Richard's comment from Phab:
<<<<<<<<<<
Consider
type family Foo (a :: k) (b :: *) = (r :: k) | r -> b

That family is injective in k, but you have to be careful to discover this fact.
And, what about
type family Bar (a :: k) = r | r -> a

Here, the family is still injective in k, but you need to make sure to note it when recording the partial injectivity.
Do you allow
type family Baz (a :: k) = r | r -> k

?
Such a thing is reasonable to want! You're saying that result determines the kind of the input, though perhaps not the type.
<<<<<<<<<<
Another interesting example was given by heisenbug on trac:
Just a side question. I have a type level Map:
type family Map (f :: k -> l) (ks :: [k]) :: [l] where ...

When I declare this as injective (presumably) with
type family Map (f :: k -> l) (ks :: [k]) = result :: [l] | result -> ks where ...

then f must be injective for this to work. Concretely, will this invocation be considered injective by GHC (:set -XDataKinds) ?
Map IO '[Int, (), Bool]

Re-opening as there are some thoughts to discuss with Richard:

We use injectivity to resolve type ambiguity. In that case what would be the purpose to have injectivity only in kinds? Even if we declare kinds as injective, without injectivity in types we won't prevent type ambiguity.

Another question is whether we should mark kinds an injective once we know a respective type variable is injective? I believe we should although not doing it does not seem to cause harm. Then again we don't want #10109 to happen for injective type families.

Closing in favour of #120 and #121.


cannot change ip address of wireguard network on terraform

update did not work
even if we decide to delay certain of the update functions we should clearly document per resource e.g. VM what is supported and what not in upgrade paths
see below, ip address was same
# grid_network.net1 will be updated in-place
~ resource "grid_network" "net1" {
id = "b7f52371-609a-4230-aef2-3370218b3a8d"
~ ip_range = "<IP_ADDRESS>/16" -> "<IP_ADDRESS>/16"
name = "network"
# (9 unchanged attributes hidden)
}

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.

 Resources: 0 added, 1 changed, 0 destroyed.

Outputs:

node1_vm1_ip = "<IP_ADDRESS>"
node1_vm2_ip = "<IP_ADDRESS>"
public_ip = "<IP_ADDRESS>/24"
wg_config = <<EOT

[Interface]
Address = <IP_ADDRESS>
PrivateKey = sGkZ1nFIvAOntWeIuONJlkZLmmasSdoP0DhwZ9njeFI=
[Peer]
PublicKey = SjsSY9qp7LRK5DG5dG+jol++zrSry2Th1/CkTS5VuBw=
AllowedIPs = <IP_ADDRESS>/16, <IP_ADDRESS>/16
PersistentKeepalive = 25
Endpoint = <IP_ADDRESS>:6689

EOT

main.zip

Moved from: https://circles.threefold.me/project/test-tfgrid3/issue/94

It's not supported


Fluid Detector, Gas Detector / Flow Detector

Describe your idea
A Fluid Detector would work the same as a Energy Detector but instead of energy it would detect the flow and type of a fluid. The same is for a Gas Detector, where it could detect Mekanism gas flow.
Describe alternatives you've considered if you've any
Another idea was to combine these detectors into one block for like universal pipes, which allow flow of multiple types (energy, items, fluids, gas) in one pipe/block, but maybe having it all in one new block could cause legacy code problems and maybe other ones too.
Additional context
No response
Linked Issues
No response

Good feature, not sure if I do it in 0.7 or 0.8. So the milestone will be empty


use org.jbibtex.LaTeXParser to handle BibTeX diacritics

References

Fixes #8453

Description
Use org.jbibtex.LaTeXParser to handle BibTeX diacritics; also handle mixed-case BibTeX keys.
Instructions for Reviewers
List of changes in this PR:

Use LaTeXParser to handle, for example, BibTeX diacritics (still common in Germany)
convert BibTeX keys to lower case to handle some input files we've seen

An example file is included in #8453.
Checklist

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[x] My PR passes Checkstyle validation based on the Code Style Guide.
n/a My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[x] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
n/a If my PR includes new, third-party dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
n/a If my PR modifies the REST API, I've linked to the REST Contract page (or open PR) related to this change.

As for the case sensitivity of BibTeX tags: http://www.bibtex.org/Format/ states "The tag's name is not case-sensitive", so I think the .toLower() is the right thing to do.

@philipprumpf : I haven't had a chance to test this yet, but I gave it a quick code review.  The code looks fine, but I did want to point out that it might be improved by adding an automated test to verify/prove that DSpace can handle a BibTeX with diacritics.  This would ensure that we don't accidentally break this feature in the future with any future changes we make.
It shouldn't be hard, as we already have some BibTeX tests in place:

We already have a few BibTeX Integration tests...here's the main one: https://github.com/DSpace/DSpace/blob/main/dspace-server-webapp/src/test/java/org/dspace/app/rest/WorkspaceItemRestRepositoryIT.java#L912
It uses a very simplistic BibTeX sample file stored at https://github.com/DSpace/DSpace/blob/main/dspace-server-webapp/src/test/resources/org/dspace/app/rest/bibtex-test.bib

So, you might consider updating that sample bibtext-test.bib to be a bit more complex (maybe make it more like your sample in #8453).  You could then update the main test method to prove that some field with diacritics is saved properly to the submission form, similar to how this tests that the Title is parsed properly to dc.title in DSpace: https://github.com/DSpace/DSpace/blob/main/dspace-server-webapp/src/test/java/org/dspace/app/rest/WorkspaceItemRestRepositoryIT.java#L946-L947
This same idea could also be applied for your other BibTeX related PRs (#8456 and #8461)... you might be able to further enhance that sample bibtex-test.bib with more complex data & add a check to that IT method to verify the data is parsed as you'd expect into the submission form.
Overall, I really appreciate your work on improving our BibTeX parsing.  If you feel you won't have time to create these tests, let me know... but it's our recommended process for all v7 development, as tests help ensure we don't accidentally break anything with future code changes. Thanks!

Thanks for the response! I've added a test for diacritics and will add tests to the other PRs as suggested.


run-prod.sh is wrong

Since all the data seems to be in /opt, the following is correct:
docker run --name rcs --volume `pwd`/data:/data --volume `pwd`/data/letsencrypt:/etc/letsencrypt --volume `pwd`/logs:/var/log --publish 80:80 --publish 443:443 --rm alexcrichton/rust-central-station

The data under ~ should be nuked as well.

We're not using RCS anymore, so closing this issue.


🐛 Example app error on Android

I am encountering the following error when running the example app on Android.
BUILD SUCCESSFUL in 25s
187 actionable tasks: 2 executed, 185 up-to-date
info Connecting to the development server...
info Starting the app on "03157df32b9ac92d"...
Starting: Intent { cmp=com.mrousavy.camera.example/.MainActivity }
Error type 3
Error: Activity class {com.mrousavy.camera.example/com.mrousavy.camera.example.MainActivity} does not exist.
✨  Done in 31.25s.

What worked for me is this answer: https://stackoverflow.com/a/25633115/9375533
I made the following changes in https://github.com/cuvent/react-native-vision-camera/blob/main/example/android/app/build.gradle#L135
- applicationId "com.mrousavy.camera"
+ applicationId "com.mrousavy.camera.example"

Perhaps, we should update it? Or am I using it incorrectly?

Oh, looks like I missed that when I changed the names. Could you create a small PR for this?


Fixed typo

place holders -> placeholders

Hi @LayZeeDK, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Thanks for fixing this


Ignore docblock comments within arrays

When checking that the last line of an array ends in a comma, both whitespace ( T_WHITESPACE) and regular comments (T_COMMENT) were ignored, but not docblock comments (those beginning with /**, T_DOC_COMMENT). This fixes that.
Fixes #230

@JDGrimes can you wait to merge at least until Travis finishes its checks? :smile:

@JDGrimes can you wait to merge at least until Travis finishes its checks? :smile:

Oops. Yes. Next time I'll just open the PR and add #reviewmerge at the bottom—then someone else can review and merge at will.

Beauty. Perfect.

Next time I'll just open the PR and add #reviewmerge at the bottom—then someone else can review and merge at will.

I've just added the option of a reviewmerge label, so you can add that instead.


Added I AM auth for Opensearch

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[X] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

To access Opensearch with IAM auth, request needs to be signed with IAM auth. This change will allow users requests to be signed if OPENSEARCH_USE_AWS_IAM_AUTH is set to true.


Eliminate warnings(assigned but unused) and remove unnecessary to_s

Since we support back to Ruby 1.8.7 right now, we can't have keyword arguments without writing ruby version specific code.

@rochefort thank you for these improvements!


PrincipalExtensions.cs subject problems

should be changed to
public static string GetSubjectId(this IIdentity identity)
{
var id = identity as ClaimsIdentity;
var claim = id.FindFirst(JwtClaimTypes.Subject);
if (claim == null)
claim = id.FindFirst(ClaimTypes.NameIdentifier);
if (claim == null) throw new InvalidOperationException("sub claim is missing");
return claim.Value;
}
otherwise  the following error is going to happen
An unhandled exception was thrown by the application.
System.InvalidOperationException: sub claim is missing
at IdentityServer4.Extensions.PrincipalExtensions.GetSubjectId(IIdentity identity)

Can you elaborate when/why this happens for you? Our requirement in IS is that when you issue the cookie, you must provide a sub claim type.

switch to dotnet 2.2 and you'll see that it doesn't work. Instead the name identifyer is working.


B 18085 identify create values 7 12 integration Kickback

B-18085 Kickback
Summary
MilMove needs to provide the PPM Closeout Counselor with a complete view/listing of PPM Costing Calculations upon PPM Closeout. This PR adds a null check for SIT items and checks if there has been an aoa requested. This should stop the tool from crashing when those fields are null.
This PR handles values 7-12:

Gross Incentive
Government Constructive Cost(GCC)
Advance Operating Allowance(AOA)
Remaining Incentive
Linehaul/short haul price
Linehaul/short haul fsc

Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

How to test

Use any PPM move that has a sit or use testharness "MoveWithPPMShipmentReadyForFinalCloseoutWitSIT"*
Log in as a service counselor and review and submit move
Log in as user for that move
Upload documents
(This should set the PPM move status to  "NEEDS_PAYMENT_APPROVAL")
In postman go to the Get ppmCloseout endpoint and use that move's PPM ID as the "ppmShipmentID"
Verify that fields 7-12 are populated

*TestHarnessData:
locator = "XPXQQD" ppmshipmentId ="f52adef1-0263-45d1-a39a-e77d153122a2"
Screenshots
no advance requested and no SIT

advanced recieved and has SIT

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 15ebe6567e67a7ad5f40e4c3f0832b2512b637ff


AAS 3.0.0 is implemented in IRS API Swagger docu

As PO
I want api updated to currrent aas version 3.0.0,
so that that the API reflects always the current state.
Hints / Details

...

Outcome / Acceptance Criteria

Swagger documentation examples were updated. In consultation with @ds-jhartmann we decided to compare with the data from DEV because the examples in the above-mentioned docs are incomplete. There are some attributes that we do not have on the IRS side but as we don't need them we decided not to add them (would have involved adding quite a few new classes under irs-models\src\main\java\org\eclipse\tractusx\irs\component\assetadministrationshell which is beyond the scope of the acceptance criteria, escpecially as we don't need these new attributes...).

Outcome

...

Acceptance Criteria

[ ] IRS API Swagger docu is aligned with aas 3.0.0 (Responses and Samples)

Out of Scope

...

https://github.com/eclipse-tractusx/sldt-digital-twin-registry/blob/87c51d73f04445ea67c38148305e5eb41f644576/docs/README.md

Outcome: Swagger documentation examples were updated. In consultation with @ds-jhartmann we decided to compare with the data from DEV because the examples in the above mentioned docs are incomplete. There are some attributes that we do not have on the IRS side but as we don't need them we decided not to add them (would have involved adding quite a few new classes under irs-models\src\main\java\org\eclipse\tractusx\irs\component\assetadministrationshell which is beyond the scope of the acceptance criteria, escpecially as we don't need these new attributes...).

Hello @dsmf  and @ds-jhartmann
I have checked https://irs.int.demo.catena-x.net/api/swagger-ui/index.html?configUrl=/api/api-docs/swagger-config#/Item Relationship Service/getJobForJobId and it differs from the one here https://raw.githubusercontent.com/eclipse-tractusx/sldt-digital-twin-registry/87c51d73f04445ea67c38148305e5eb41f644576/docs/README.md

@dsmf  please create a new pbis story. Link this story to this one. Add label PO Review and assign story to @jzbmw.

JobResponse provides complete aas (as we receive from dDTR) in shell array


SMT failed timeline uses the wrong timestamp field

SMT failed timeline uses the wrong timestamp field (start_time instead of end_time)

Trello card: [#177] SMT failed timeline uses the wrong timestamp field


set images size

how to set the size of the image ?
I set <img src="../assets/img/assets/envelope-solid.svg" width="18px"> .
It doesn't work.

You need to use:


Missing letters

Always On availability groups relies on the Windows Server Failover Cluste(WSFC)
Cluster (WSFC)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b6df874b-bf51-b8de-9b24-d9301469dfaf
Version Independent ID: f013e112-bef0-a20b-add8-5ed39bb254ef
Content: Combine a failover cluster instance with availability groups - SQL Server Always On
Content Source: docs/database-engine/availability-groups/windows/failover-clustering-and-always-on-availability-groups-sql-server.md
Product: sql
Technology: high-availability
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

Hi @YanumVlad , thanks for contacting Microsoft! It may be faster for you to edit the content yourself via a Pull Request (PR). To do so, please do the following:

Navigate to the page of interest
Select the "Edit" button at the top right of the page
Select the "Pencil" icon on the right
Modify the text within the text box in markdown format - more info: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
Name your file change and provide a description, if necessary
Select "Propose file change"
Select "Create pull request" on the 'Comparing changes' page
Select "Create pull request" on the 'Open a pull request' page

Thanks!

Thanks again for contacting Microsoft!  We've submitted a documentation change based on your suggestion, and it should be live at this point. Please let us know if there is anything more we can do for you? If not, we'll proceed with closing out this Git Issue in a few business days.
Thanks again and hope you have a wonderful rest of your day!


Add parameters to hello-world example for authentication.

-u | --user user to use for request.
-p | --password password to use for request.

resolve #112

Thanks!  I'll test tonight.

Glad to help.


Added tic tac toe game in C language and added Hello World in Shell Script

Added tic tac toe game in C language and added Hello World in Linux Shell Script.
Peace 👍🏻

Amazing work! Keep Contributing!

Thanks


bug: Toast says Comment upvoted even when we remove upvote

Describe the bug
Toast says Comment upvoted even when we remove upvote
To Reproduce
Steps to reproduce the behavior:

upvote any comment
remove your upvote
see error

Screenshots or GIFs

Assign me, I would love to work on this.

Can I work on this issue ? #1320

I have solved this specific issue.
Waiting for you to assign me.
Adding the code snippet's to show my approach.
Original Code

My Approach

Can you please assign me this issue so that I can submit a PR Request.

@hkirat No one is responding Sir :(
Should I submit PR or not?
I have fixed this particular bug

This is done in https://github.com/code100x/cms/pull/1323

@iamhvsharma you don't need to ask to create a pr. Just create it will be reviwed in few days

Oh, I didn't know!
In the contributor's guidelines, it was mentioned that you should only submit a PR after the assigning.


typo- send > sends

Docs Build status updates of commit 3af2549:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/actionable-messages/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thank you!


Created_Hello_World_Page

#6 created basic hello world page with header and footer
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have carefully reviewed my own code
[ ] I have commented my code
[ ] I have updated any documentation

you done!


Affinity computation

why the affinity computation is different from the formulation in the paper? Here, why comment out the c = qk.pow(2).sum(1).unsqueeze(1)?

See point (1) in #50

The code also handles the batch dimension while the paper left it out.


Don't restore from storage after reboot

If the device clock changes after reboot before Kronos is updated, the "trusted" time will be wrong since we'll apply the offset to the wrong ground time. This breaks the "trusted" guarantee.

What are your thoughts on making this a configurable option? Aka have a way to configure Kronos to either return nil or try best-effort in the case where we restore from storage after reboot.

I'm indifferent to whether you merge this or not. However, I'd just like to explain why we did this in the first place.
The system clock cannot be trusted because the user might be doing all sorts of weird things, like setting it to the wrong time zone, or purposely setting it nine minutes forward to keep themselves on time.
However, the assumption that this is making is that the weird offset of the system clock is going to be the same between reboots.  If that is the case, then the existing code guesses right.  The phone that's always nine minutes fast will work for this code.
Obviously the tradeoff is that we could be wrong, and nil is a safer bet.
I just wanted to give the reasoning from last year.

I'll add that I'm also indifferent, although I think we should at least consider whether it makes sense to make this a configurable option in Kronos.

FYI Leo is ok with this change on Android as well so we can go forward. I still think making this configurable on Kronos is the best answer in terms of this PR, but am also OK with landing this as-is.


dashmate setup local fails with Database already exists

I did this all as root because I couldn't get rootless docker to work (possibly some kernel or shadow-utils bug or incompatibility).

Install docker (pretending like it's not a shell pipe):curl -fsSL https://get.docker.com -o get-docker.sh; sh get-docker.sh

Download and install the latest dashmate on Ubuntu 22.04 LTS x64:#!/bin/sh
set -e
set -u

g_rel="v1.0.0-dev.6"
g_file="dashmate-v1.0.0-dev.6-0c3f75f7c-linux-x64.tar.gz"
if ! test -f "${g_file}"; then
    curl -L -O 'https://github.com/dashpay/platform/releases/download'/"${g_rel}"/"${g_file}"
fi
echo "Extracting ${g_file}"
tar xf "${g_file}"

Run dashmatepushd ./dashmate/
./bin/dashmate setup --verbose --node-count=3 --debug-logs --miner-interval=2.5m local

Get error'd...
[STARTED] Create local group configs
warn: Running on a NodeJS env without any specified adapter. Data will not persist.
warn: Running on a NodeJS env without any specified adapter. Data will not persist.
warn: Running on a NodeJS env without any specified adapter. Data will not persist.
warn: Running on a NodeJS env without any specified adapter. Data will not persist.
warn: Running on a NodeJS env without any specified adapter. Data will not persist.
...
[DATA] 1010 blocks generated
[SUCCESS] Activating DIP3 [10s]
[STARTED] Create wallet
[FAILED] Wallet file verification failed. Failed to create database path '/home/dash/.dashcore/regtest/wallets/main'. Database already exists.
[FAILED] Wallet file verification failed. Failed to create database path '/home/dash/.dashcore/regtest/wallets/main'. Database already exists.
[FAILED] Wallet file verification failed. Failed to create database path '/home/dash/.dashcore/regtest/wallets/main'. Database already exists.
[FAILED] Wallet file verification failed. Failed to create database path '/home/dash/.dashcore/regtest/wallets/main'. Database already exists.

Hey AJ.
I tried your instructions and couldn't reproduce your issue. Very possibly you have not properly cleaned out previous local environment and dashcore docker volumes left with some content leading you to the Database already exists message.
Sharing you a video with me putting your commands from the issue.
https://www.youtube.com/watch?v=qJ2475L3vyQ

@pshenmic what are the specific directories that need to be removed?
I removed ~/.dashmate/ and I ran a series of commands to completely purge docker of all instances:
rm -rf ~/.dashmate

# q is quiet, as in just the IDs
docker service rm $(docker service ls -q)

# a is for all
docker container stop $(docker container ls -aq)
docker container kill $(docker container ls -aq)
docker container rm --force $(docker container ls -aq)
# just aliases of the above
docker stop $(docker ps -aq)
docker kill $(docker ps -q)
docker rm --force $(docker ps -a -q)

docker image rm --force $(docker images -q)
# again, an alias
docker rmi --force $(docker images -q)

# prune all containers images, networks, and volumes - to the max
docker container prune --force
docker image prune --all --force
docker network prune --force
docker volume prune --force

# prune HARDER
docker system prune --all --force --volumes

What else do I need to remove to get back to a fresh slate?
(I'll try again in another fresh container too)

Try to look at what you have after your deleted all containers, networks and volumes

I ran again in another fresh container, with another fresh install of docker and dashmate and... this time it worked.
🤷♂
./bin/dashmate setup --verbose --node-count=3 --debug-logs --miner-interval=2.5m local

[STARTED] System requirements
[SUCCESS] System requirements [0.9s]
[STARTED] Configuration preset
[DATA] local
[SUCCESS] Configuration preset [0.0s]
[STARTED] Task without title.
[STARTED] Create local group configs
warn: Running on a NodeJS env without any specified adapter. Data will not persist.
warn: Running on a NodeJS env without any specified adapter. Data will not persist.
warn: Running on a NodeJS env without any specified adapter. Data will not persist.
warn: Running on a NodeJS env without any specified adapter. Data will not persist.
warn: Running on a NodeJS env without any specified adapter. Data will not persist.
[DATA] DPNS Private Key: tprv8ZgxMBicQKsPd8G5YsH8EV7dmJxzCsBSdY71q2KgwyMeBQFKdPM81FwLV7ZHc2mavSB5ACUiNXAVhif4FYjN7ieFbSczxCPG2TbbuaVteDQ
[DATA] Feature Flags Private Key: tprv8ZgxMBicQKsPd2JZYxQamRYf9RPDiYLRiveKR3y6KXakqsmXAkaoN4RxfsbrccEWqTs95xptk97D1u1SHVP43ZoQvX2jcvD87SDSdiePU15
[DATA] Dashpay Private Key: tprv8ZgxMBicQKsPeiB5QcwNrDZipCvmoCdZFr786hu1YWD9JR4qMo9qygkZpSLdwSjwyYWDhG34udR7DFyNobYXDMhis79LQtKmaJPxauNhymZ
[DATA] Masternode Reward Shares Private Key: tprv8ZgxMBicQKsPczgb3Z8p1ern4EmYnaATiiYqqg4t8VkdwxMd1psRvng1jTDotC4MKz52C841gNnbp4iKkAobpTcfq8PTzqiqx4PSkuJ6e6S
[DATA] Withdrawals Private Key: tprv8ZgxMBicQKsPebQ63XQS3QGu2gi3Wu4KU1TaDM6ei1dpFqZATBHx5myJhPpE1UATfZinigd1vwcoYf2pLSW7kPmUMViDqssiBnZonquSYav
[STARTED] Create local_1 config
[SUCCESS] Create local_1 config [0.0s]
[STARTED] Create local_2 config
[SUCCESS] Create local_2 config [0.0s]
[STARTED] Create local_3 config
[SUCCESS] Create local_3 config [0.0s]
[STARTED] Create local_seed config
[SUCCESS] Create local_seed config [0.0s]
[SUCCESS] Create local group configs [7s]
[STARTED] Configure Core nodes
[STARTED] Task without title.
[STARTED] Starting seed node as a wallet
[SUCCESS] Starting seed node as a wallet [17s]
[STARTED] Activating DIP3
[DATA] 10 blocks generated
[DATA] 20 blocks generated
[DATA] 30 blocks generated
[DATA] 40 blocks generated
[DATA] 50 blocks generated
[DATA] 60 blocks generated
[DATA] 70 blocks generated
[DATA] 80 blocks generated
[DATA] 90 blocks generated
[DATA] 100 blocks generated
[DATA] 110 blocks generated
[DATA] 120 blocks generated
[DATA] 130 blocks generated
[DATA] 140 blocks generated
[DATA] 150 blocks generated
[DATA] 160 blocks generated
[DATA] 170 blocks generated
[DATA] 180 blocks generated
[DATA] 190 blocks generated
[DATA] 200 blocks generated
[DATA] 210 blocks generated
[DATA] 220 blocks generated
[DATA] 230 blocks generated
[DATA] 240 blocks generated
[DATA] 250 blocks generated
[DATA] 260 blocks generated
[DATA] 270 blocks generated
[DATA] 280 blocks generated
[DATA] 290 blocks generated
[DATA] 300 blocks generated
[DATA] 310 blocks generated
[DATA] 320 blocks generated
[DATA] 330 blocks generated
[DATA] 340 blocks generated
[DATA] 350 blocks generated
[DATA] 360 blocks generated
[DATA] 370 blocks generated
[DATA] 380 blocks generated
[DATA] 390 blocks generated
[DATA] 400 blocks generated
[DATA] 410 blocks generated
[DATA] 420 blocks generated
[DATA] 430 blocks generated
[DATA] 440 blocks generated
[DATA] 450 blocks generated
[DATA] 460 blocks generated
[DATA] 470 blocks generated
[DATA] 480 blocks generated
[DATA] 490 blocks generated
[DATA] 500 blocks generated
[DATA] 510 blocks generated
[DATA] 520 blocks generated
[DATA] 530 blocks generated
[DATA] 540 blocks generated
[DATA] 550 blocks generated
[DATA] 560 blocks generated
[DATA] 570 blocks generated
[DATA] 580 blocks generated
[DATA] 590 blocks generated
[DATA] 600 blocks generated
[DATA] 610 blocks generated
[DATA] 620 blocks generated
[DATA] 630 blocks generated
[DATA] 640 blocks generated
[DATA] 650 blocks generated
[DATA] 660 blocks generated
[DATA] 670 blocks generated
[DATA] 680 blocks generated
[DATA] 690 blocks generated
[DATA] 700 blocks generated
[DATA] 710 blocks generated
[DATA] 720 blocks generated
[DATA] 730 blocks generated
[DATA] 740 blocks generated
[DATA] 750 blocks generated
[DATA] 760 blocks generated
[DATA] 770 blocks generated
[DATA] 780 blocks generated
[DATA] 790 blocks generated
[DATA] 800 blocks generated
[DATA] 810 blocks generated
[DATA] 820 blocks generated
[DATA] 830 blocks generated
[DATA] 840 blocks generated
[DATA] 850 blocks generated
[DATA] 860 blocks generated
[DATA] 870 blocks generated
[DATA] 880 blocks generated
[DATA] 890 blocks generated
[DATA] 900 blocks generated
[DATA] 910 blocks generated
[DATA] 920 blocks generated
[DATA] 930 blocks generated
[DATA] 940 blocks generated
[DATA] 950 blocks generated
[DATA] 960 blocks generated
[DATA] 970 blocks generated
[DATA] 980 blocks generated
[DATA] 990 blocks generated
[DATA] 1000 blocks generated
[DATA] 1010 blocks generated
[SUCCESS] Activating DIP3 [10s]
[STARTED] Create wallet
[SUCCESS] Create wallet [1s]
[STARTED] Generating funds to use as a collateral for masternodes
[STARTED] Create a new address
[DATA] Address: yQvRzkwfyk37e62QqxkVe8fAgob1qhS3xp
[DATA] Private key: cQTW5kk2jttf2fxfc1kzRzwDM36u1fHXbdfWL1kJRCUw941R1XeG
[SUCCESS] Create a new address [0.0s]
[STARTED] Generate �16000 dash to address
[TITLE] Generate �16000 dash to address yQvRzkwfyk37e62QqxkVe8fAgob1qhS3xp
[DATA]<PHONE_NUMBER>6 dash generated
[DATA]<PHONE_NUMBER>2 dash generated
[DATA]<PHONE_NUMBER>8 dash generated
[DATA] 1153.88998744 dash generated
[DATA] 1442.3624843 dash generated
[DATA] 1730.83498116 dash generated
[DATA] 2019.30747802 dash generated
[DATA] 2307.77997488 dash generated
[DATA] 2596.25247174 dash generated
[DATA] 2884.7249686 dash generated
[DATA] 3173.19746546 dash generated
[DATA] 3461.66996232 dash generated
[DATA] 3750.14245918 dash generated
[DATA] 4038.61495604 dash generated
[DATA] 4327.0874529 dash generated
[DATA] 4615.55994976 dash generated
[DATA] 4904.03244662 dash generated
[DATA] 5192.50494348 dash generated
[DATA] 5480.97744034 dash generated
[DATA] 5769.4499372 dash generated
[DATA] 6057.92243406 dash generated
[DATA] 6346.39493092 dash generated
[DATA] 6634.86742778 dash generated
[DATA] 6923.33992464 dash generated
[DATA] 7211.8124215 dash generated
[DATA] 7500.28491836 dash generated
[DATA] 7788.75741522 dash generated
[DATA] 8077.22991208 dash generated
[DATA] 8365.70240894 dash generated
[DATA] 8654.1749058 dash generated
[DATA] 8942.64740266 dash generated
[DATA] 9231.11989952 dash generated
[DATA] 9519.59239638 dash generated
[DATA] 9808.06489324 dash generated
[DATA] 10096.5373901 dash generated
[DATA] 10385.00988696 dash generated
[DATA] 10673.48238382 dash generated
[DATA] 10961.95488068 dash generated
[DATA] 11250.42737754 dash generated
[DATA] 11538.8998744 dash generated
[DATA] 11806.76719292 dash generated
[DATA] 12074.63451144 dash generated
[DATA] 12342.50182996 dash generated
[DATA] 12610.36914848 dash generated
[DATA] 12878.236467 dash generated
[DATA] 13146.10378552 dash generated
[DATA] 13413.97110404 dash generated
[DATA] 13681.83842256 dash generated
[DATA] 13949.70574108 dash generated
[DATA] 14217.5730596 dash generated
[DATA] 14485.44037812 dash generated
[DATA] 14753.30769664 dash generated
[DATA] 15021.17501516 dash generated
[DATA] 15289.04233368 dash generated
[DATA] 15556.9096522 dash generated
[DATA] 15824.77697072 dash generated
[DATA] 16092.64428924 dash generated
[DATA] Generated 16092.64428924 dash
[SUCCESS] Generate �16000 dash to address yQvRzkwfyk37e62QqxkVe8fAgob1qhS3xp [2s]
[STARTED] Wait for balance to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 16092.64428924 dash to confirm
[DATA] 15804.17179238 dash to confirm
[DATA] 15515.69929552 dash to confirm
[DATA] 15227.22679866 dash to confirm
[DATA] 14938.7543018 dash to confirm
[DATA] 14650.28180494 dash to confirm
[DATA] 14361.80930808 dash to confirm
[DATA] 14073.33681122 dash to confirm
[DATA] 13784.86431436 dash to confirm
[DATA] 13496.3918175 dash to confirm
[DATA] 13207.91932064 dash to confirm
[DATA] 12919.44682378 dash to confirm
[DATA] 12630.97432692 dash to confirm
[DATA] 12342.50183006 dash to confirm
[DATA] 12054.0293332 dash to confirm
[DATA] 11765.55683634 dash to confirm
[DATA] 11477.08433948 dash to confirm
[DATA] 11188.61184262 dash to confirm
[DATA] 10900.13934576 dash to confirm
[DATA] 10611.6668489 dash to confirm
[DATA] 10323.19435204 dash to confirm
[DATA] 10034.72185518 dash to confirm
[DATA] 9746.24935832 dash to confirm
[DATA] 9457.77686146 dash to confirm
[DATA] 9169.3043646 dash to confirm
[DATA] 8880.83186774 dash to confirm
[DATA] 8592.35937088 dash to confirm
[DATA] 8303.88687402 dash to confirm
[DATA] 8015.41437716 dash to confirm
[DATA] 7726.9418803 dash to confirm
[DATA] 7438.46938344 dash to confirm
[DATA] 7149.99688658 dash to confirm
[DATA] 6861.52438972 dash to confirm
[DATA] 6573.05189286 dash to confirm
[DATA] 6284.579396 dash to confirm
[DATA] 5996.10689914 dash to confirm
[DATA] 5707.63440228 dash to confirm
[DATA] 5419.16190542 dash to confirm
[DATA] 5130.68940856 dash to confirm
[DATA] 4842.2169117 dash to confirm
[DATA] 4553.74441484 dash to confirm
[DATA] 4285.87709632 dash to confirm
[DATA] 4018.0097778 dash to confirm
[DATA] 3750.14245928 dash to confirm
[DATA] 3482.27514076 dash to confirm
[DATA] 3214.40782224 dash to confirm
[DATA] 2946.54050372 dash to confirm
[DATA] 2678.6731852 dash to confirm
[DATA] 2410.80586668 dash to confirm
[DATA] 2142.93854816 dash to confirm
[DATA] 1875.07122964 dash to confirm
[DATA] 1607.20391112 dash to confirm
[DATA] 1339.3365926 dash to confirm
[DATA] 1071.46927408 dash to confirm
[DATA]<PHONE_NUMBER>6 dash to confirm
[DATA]<PHONE_NUMBER>4 dash to confirm
[DATA]<PHONE_NUMBER>2 dash to confirm
[DATA] 0 dash to confirm
[SUCCESS] Wait for balance to confirm [1s]
[SUCCESS] Generating funds to use as a collateral for masternodes [4s]
[STARTED] Register masternodes
[STARTED] Register local_1 masternode
[STARTED] Generate a masternode operator key
[SUCCESS] Generate a masternode operator key [0.3s]
[STARTED] Task without title.
[STARTED] Import funding private key
[DATA] cQTW5kk2jttf2fxfc1kzRzwDM36u1fHXbdfWL1kJRCUw941R1XeG imported.
[SUCCESS] Import funding private key [0.3s]
[STARTED] Check funding address balance
[TITLE] Check funding address yQvRzkwfyk37e62QqxkVe8fAgob1qhS3xp balance
[SUCCESS] Check funding address yQvRzkwfyk37e62QqxkVe8fAgob1qhS3xp balance [0.0s]
[STARTED] Create a new collateral address
[DATA] Address: yaEC1q4HnkghqBt6EshJySZz2T3Mm5G8Bf
[DATA] Private key: cMhtXnzveNhrxcJ7dEEzdths5RiYxaxV1R4PYhgVaafCcsfWta28
[SUCCESS] Create a new collateral address [0.0s]
[STARTED] Create a new owner addresses
[DATA] Address: yeh4EesN8rmmtqJLX2BTeq4GpMUtqoS1g9
[DATA] Private key: cSpPmjPys8CHgsxDBKwKMsM6TziiavzJEdFs9iGPZw9gpaGA2Pzk
[SUCCESS] Create a new owner addresses [0.0s]
[STARTED] Create a new reward addresses
[DATA] Address: yVYBos6vnS1tpNTKFA3wfzpWhNeDJtQ1X9
[DATA] Private key: cUqxk3ckj8CSuSCqx3cvxFfn86NAXvftehUUMCzVK2vsPRZsHHB3
[SUCCESS] Create a new reward addresses [0.0s]
[STARTED] Send 0.1 dash from funding address to reward address
[SUCCESS] Send 0.1 dash from funding address to reward address [0.0s]
[STARTED] Wait for balance to confirm
[DATA] 0 dash to confirm
[SUCCESS] Wait for balance to confirm [0.0s]
[STARTED] Send 4000 dash from funding address to collateral address
[DATA] Collateral transaction ID: fb3b9c0cd03e79ca8d06dd6464fba42d1b7be3e5b0908d830f0a777b4798fb35
[SUCCESS] Send 4000 dash from funding address to collateral address [0.3s]
[STARTED] Wait for balance to confirm
[DATA] 0 dash to confirm
[SUCCESS] Wait for balance to confirm [0.0s]
[STARTED] Broadcast masternode registration transaction
[DATA] ProRegTx transaction ID: d199411bae804ebdc3d1b426759a6649f446947020003cf057326c97b223a8e7
[DATA] Owner Private Key: cSpPmjPys8CHgsxDBKwKMsM6TziiavzJEdFs9iGPZw9gpaGA2Pzk
[SUCCESS] Broadcast masternode registration transaction [0.1s]
[STARTED] Mine 1 block to confirm
[DATA] 1 block mined
[SUCCESS] Mine 1 block to confirm [0.0s]
[SUCCESS] Task without title. [1s]
[SUCCESS] Register local_1 masternode [1s]
[STARTED] Register local_2 masternode
[STARTED] Generate a masternode operator key
[SUCCESS] Generate a masternode operator key [0.2s]
[STARTED] Task without title.
[STARTED] Import funding private key
[DATA] cQTW5kk2jttf2fxfc1kzRzwDM36u1fHXbdfWL1kJRCUw941R1XeG imported.
[SUCCESS] Import funding private key [0.3s]
[STARTED] Check funding address balance
[TITLE] Check funding address yQvRzkwfyk37e62QqxkVe8fAgob1qhS3xp balance
[SUCCESS] Check funding address yQvRzkwfyk37e62QqxkVe8fAgob1qhS3xp balance [0.0s]
[STARTED] Create a new collateral address
[DATA] Address: yhU8cDm5wfoH1X83pZ9TF8CRNjQ4Pmyn3v
[DATA] Private key: cPwaWMh5Wt1sQsqJXkzDjDyQrLjX7zrqaCpbe2aakozu7Bz91aRS
[SUCCESS] Create a new collateral address [0.1s]
[STARTED] Create a new owner addresses
[DATA] Address: yNotaNbdLa2D8g7beNAjYcq9EavuCkEaaS
[DATA] Private key: cRW5qWCcNPUsR4VfKyaCWnXUL4EnnMHPNm4aqnqQZtPM9P8AN6Pg
[SUCCESS] Create a new owner addresses [0.0s]
[STARTED] Create a new reward addresses
[DATA] Address: yUr5sZK1TQYHLsvqDcbwAnYhRwPaEfKV7N
[DATA] Private key: cNhx9ZdZdQt1o4v1N245Rc7WBABfGueMp5BYDqxf5VQxX2ei9RoG
[SUCCESS] Create a new reward addresses [0.0s]
[STARTED] Send 0.1 dash from funding address to reward address
[SUCCESS] Send 0.1 dash from funding address to reward address [0.0s]
[STARTED] Wait for balance to confirm
[DATA] 0 dash to confirm
[SUCCESS] Wait for balance to confirm [0.0s]
[STARTED] Send 4000 dash from funding address to collateral address
[DATA] Collateral transaction ID: 6d3319f9ee620996622d1b3c0d07971ec5fc148c162dbd54e6e26d09c8827756
[SUCCESS] Send 4000 dash from funding address to collateral address [0.2s]
[STARTED] Wait for balance to confirm
[DATA] 0 dash to confirm
[SUCCESS] Wait for balance to confirm [0.0s]
[STARTED] Broadcast masternode registration transaction
[DATA] ProRegTx transaction ID: cc94e34dd367a79b4fb6f2f858c3bf1cb56edfe7ee10287aa519b182af8b3416
[DATA] Owner Private Key: cRW5qWCcNPUsR4VfKyaCWnXUL4EnnMHPNm4aqnqQZtPM9P8AN6Pg
[SUCCESS] Broadcast masternode registration transaction [0.1s]
[STARTED] Mine 1 block to confirm
[DATA] 1 block mined
[SUCCESS] Mine 1 block to confirm [0.0s]
[SUCCESS] Task without title. [1s]
[SUCCESS] Register local_2 masternode [1s]
[STARTED] Register local_3 masternode
[STARTED] Generate a masternode operator key
[SUCCESS] Generate a masternode operator key [0.3s]
[STARTED] Task without title.
[STARTED] Import funding private key
[DATA] cQTW5kk2jttf2fxfc1kzRzwDM36u1fHXbdfWL1kJRCUw941R1XeG imported.
[SUCCESS] Import funding private key [0.3s]
[STARTED] Check funding address balance
[TITLE] Check funding address yQvRzkwfyk37e62QqxkVe8fAgob1qhS3xp balance
[SUCCESS] Check funding address yQvRzkwfyk37e62QqxkVe8fAgob1qhS3xp balance [0.0s]
[STARTED] Create a new collateral address
[DATA] Address: yQmdU44kVEh3Fv3YG9hFkQuSrdS4Cm8uda
[DATA] Private key: cTdsEQy7mf6macEJrndc1qHR5f543N8oAPfSPsBBa6gbABitGTyS
[SUCCESS] Create a new collateral address [0.0s]
[STARTED] Create a new owner addresses
[DATA] Address: yQfkrBtQCJ93BTpDnS2kLX49vBmfA4UYPD
[DATA] Private key: cTnuAZAQR6cfVucdRNeWXGBFgtSvLx4NiMRbY95S635UY6oqkVGX
[SUCCESS] Create a new owner addresses [0.0s]
[STARTED] Create a new reward addresses
[DATA] Address: ybh9o4pXvAqV5i6fgpHrpmr7okEhgDGEft
[DATA] Private key: cQqGLQdXXg5YKBmyBxLB8pHSChxNTL5yobnL5KUEgo7g2tX5RQuz
[SUCCESS] Create a new reward addresses [0.0s]
[STARTED] Send 0.1 dash from funding address to reward address
[SUCCESS] Send 0.1 dash from funding address to reward address [0.0s]
[STARTED] Wait for balance to confirm
[DATA] 0 dash to confirm
[SUCCESS] Wait for balance to confirm [0.0s]
[STARTED] Send 4000 dash from funding address to collateral address
[DATA] Collateral transaction ID: 9cc23fea5f2d9216efa16837549472fb6499d7077011c9aed006199b132d8b76
[SUCCESS] Send 4000 dash from funding address to collateral address [0.2s]
[STARTED] Wait for balance to confirm
[DATA] 0 dash to confirm
[SUCCESS] Wait for balance to confirm [0.0s]
[STARTED] Broadcast masternode registration transaction
[DATA] ProRegTx transaction ID: 981cdd801f8262626344e287df2235cdf2641f07bf0897d5ae88e643a6deddd2
[DATA] Owner Private Key: cTnuAZAQR6cfVucdRNeWXGBFgtSvLx4NiMRbY95S635UY6oqkVGX
[SUCCESS] Broadcast masternode registration transaction [0.1s]
[STARTED] Mine 1 block to confirm
[DATA] 1 block mined
[SUCCESS] Mine 1 block to confirm [0.0s]
[SUCCESS] Task without title. [1s]
[SUCCESS] Register local_3 masternode [1s]
[SUCCESS] Register masternodes [4s]
[STARTED] Stopping wallet
[SUCCESS] Stopping wallet [6s]
[STARTED] Starting nodes
[SUCCESS] Starting nodes [5s]
[STARTED] Force masternodes to sync
[SUCCESS] Force masternodes to sync [0.8s]
[STARTED] Set initial mock time
[SUCCESS] Set initial mock time [0.0s]
[STARTED] Wait for nodes to have the same height
[SUCCESS] Wait for nodes to have the same height [1m11s]
[STARTED] Enable sporks
[SUCCESS] Enable sporks [0.0s]
[STARTED] Wait for nodes to have the same sporks
[SUCCESS] Wait for nodes to have the same sporks [0.0s]
[STARTED] Activating DIP8 to enable ChainLocks
[DATA] DIP8 has been activated at height 432
[SUCCESS] Activating DIP8 to enable ChainLocks [0.0s]
[STARTED] Wait for nodes to have the same height
[SUCCESS] Wait for nodes to have the same height [0.0s]
[STARTED] Make sure masternodes are enabled
[SUCCESS] Make sure masternodes are enabled [0.0s]
[STARTED] Wait for quorums to be enabled
[STARTED] Task without title.
[SUCCESS] Task without title. [0.0s]
[STARTED] Start DKG session
[SUCCESS] Start DKG session [0.4s]
[STARTED] Waiting for phase 1 (init)
[SUCCESS] Waiting for phase 1 (init) [1s]
[STARTED] Waiting for phase 2 (contribute)
[SUCCESS] Waiting for phase 2 (contribute) [0.1s]
[STARTED] Waiting for phase 3 (complain)
[SUCCESS] Waiting for phase 3 (complain) [0.0s]
[STARTED] Waiting for phase 4 (justify)
[SUCCESS] Waiting for phase 4 (justify) [0.0s]
[STARTED] Waiting for phase 5 (commit)
[SUCCESS] Waiting for phase 5 (commit) [0.0s]
[STARTED] Waiting for phase 6 (mining)
[SUCCESS] Waiting for phase 6 (mining) [0.0s]
[STARTED] Waiting final commitment
[SUCCESS] Waiting final commitment [0.1s]
[STARTED] Mining final commitment
[DATA] New quorum mined: height: 1224, quorum hash: 5fffb6b98c8abc7e3a4b5a6269ee365839164f973a7b718fa2c4fc1d20f3fa70, mined in block: 673763ca38bc0db4f428a22d45540a784fa5f728ca69733d87b95a3ac61c665e
[SUCCESS] Mining final commitment [9s]
[SUCCESS] Wait for quorums to be enabled [11s]
[STARTED] Setting initial core chain locked height
[DATA] Initial chain locked core height is set to: 1243
[SUCCESS] Setting initial core chain locked height [0.0s]
[STARTED] Activating V20 fork
[DATA] V20 fork has been activated at height 1200
[SUCCESS] Activating V20 fork [0.0s]
[STARTED] Stopping nodes
[SUCCESS] Stopping nodes [7s]
[SUCCESS] Task without title. [2m21s]
[SUCCESS] Configure Core nodes [2m21s]
[STARTED] Configure Tenderdash nodes
[STARTED] Task without title.
[STARTED] Task without title.
[SUCCESS] Task without title. [0.0s]
[SUCCESS] Task without title. [0.0s]
[SUCCESS] Configure Tenderdash nodes [0.0s]
[STARTED] Configure SSL certificates
[STARTED] Generate certificate for local_1
[STARTED] Task without title.
[STARTED] Save certificates
[SUCCESS] Save certificates [0.0s]
[SUCCESS] Task without title. [1s]
[SUCCESS] Generate certificate for local_1 [1s]
[STARTED] Generate certificate for local_2
[STARTED] Task without title.
[STARTED] Save certificates
[SUCCESS] Save certificates [0.0s]
[SUCCESS] Task without title. [0.7s]
[SUCCESS] Generate certificate for local_2 [0.7s]
[STARTED] Generate certificate for local_3
[STARTED] Task without title.
[STARTED] Save certificates
[SUCCESS] Save certificates [0.0s]
[SUCCESS] Task without title. [0.5s]
[SUCCESS] Generate certificate for local_3 [0.5s]
[SUCCESS] Configure SSL certificates [2s]
[SUCCESS] Task without title. [2m31s]


[PWS] Added Physical Web User Agent

Some websites rely on the "Mozilla5/0" part of the User-Agent string to serve web content. Let's add a Physical Web User Agent to fix that issue.
Moreover, this could lead websites in general to serve specific content (small and fast) for those who examine HTTP Headers User-Agent. What do you think?

LGTM

Can we update url-caster.appspot.com and url-caster-dev.appspot.com as well with this change?

Guys I'm not sold on this change.
Specifically, there will be many user agents acting as the physical web metadata resolver, and I'm not sure we should be making the promise that this will be the user agent to web servers.
Imagine someone wants to make an app that resolves from the phone directly, doesn't want to use a middleman -- should they get different results?  Or a company wants to make a private proxy for their employees, or whatever..

..I think instead we may in the future  support a custom data type (perhaps), and signal that fact by passing the Accept header, so that the web server could return a custom manifest or something.
Speculative at this point, but just throwing this out there.

@mmocny feel free to revert if you're not convinced by this change.

Reverted in 293a902536e9f7a8038232396d0c06a960fa0f45.
Sorry I just want to consider the implications before committing to this.

How about we remove the (compatible; PhysicalWeb/1.0; +http://physical-web.org) part of the Physical Web Service User Agent and simply leave Mozilla/5.0 part so that servers that rely on it to show web content to their users could still be parsed. An example of this is french ISP: http://www.orange.fr

Sure, thats a fair initial value, we can iterate from there.
On Mon, May 18, 2015 at 9:59 AM François Beaufort<EMAIL_ADDRESS>wrote:

How about we remove the (compatible; PhysicalWeb/1.0; +
http://physical-web.org) part of the Physical Web Service User Agent and
simply leave Mozilla/5.0 part so that servers that rely on it to show web
content to their users could still be parsed. An example of this is french
ISP: http://www.orange.fr
—
Reply to this email directly or view it on GitHub
https://github.com/google/physical-web/pull/380#issuecomment-103069011.

Here's a PR which adds only the Mozilla/5.0 User Agent: https://github.com/google/physical-web/pull/390/files


support Parse.Relation

#11 support Parse.Relation
UPDATE_OPERATORS add Batch, AddRelation, RemoveRelation
QUERY_OPERATORS add $relatedTo

close it, change to branch #17


Hashicorp Vault Integration

@vitalied I would try both first this and if fail your apprach. Waht do  you think?