[Feature Request]Add table of contents to each page

As far as I can tell, on any given page of a rulebook, to get to a different chapter you must go back to the Table of Contents, then go to the corresponding chapter. It would be nice if somewhere on the page, either at the top or along the side collapsible there were links to the other chapters in the rulebook

That is a good idea. I suffer from this myself XD. Added to the list of to do. Thanks.

I started working on this in my own fork  It works, but it definitely could be better designed. I'll work on it some more soon. Any suggestions would be appreciated.

That is amazing news! Thanks for the contribution! I will definitely take a look at it.

I just tested you PR, and it looks amazing! Thanks again for the contribution. I just found two small things (I will add the comments on PR), and I think we can merge it.

I changed my mind, just merged it. I will make the small changes XD. Basically I just added and empty array on TOCData for rules (it was trowing an ex for rule books). And on TOCService I just added a return if the book is not found on TOCData (It was removing the menu on books with no entry on data).
So it will be on the next release. Probably I will do this weekend after I finish the damn extra map refs XD.
Btw feel free to create more PRs if you want to change something.
Thanks again!


Remove initial input

This is a breaking change.
svu v1.9.0 now assumes an initial version of 0.0.0, so rely on
that functionality instead.
Removing initial also means you cannot start at a version other than
0.0.0 either.

Why not a major if this is a breaking change?

This was, hence a 2.0.0 release of the action.

Sorry, though this was an issue in svu, not the action, my bad.

FYI I've opened https://github.com/caarlos0/svu/pull/57 to hopefully make this functionality more flexible.
Hope this action has been helpful :-)


Fix az CI

fix CI az at latest 2.0.z (2.0.81) for now
rationale: >= 2.1.0 deprecates python 2.7 support, and for now it makes sense for us to keep testing that our extension works on older az releases and 2.7.
perhaps later we should test against multiple az releases (2.0.latest, 2.2.latest, etc.))

@julienstroheker wdyt?

@JackQuincy this should also fix the az version issue you mentioned in your demo


[AAP-15464] Schedule a recurring task to detect dead activation workers

Detect activations that connect to dead/inactive activation workers due to service restart or worker crashing.
Fail the activation if the rulebook container no longer exists, otherwise attempt to reconnect the container to an idle activation worker.
The original thought was to use a startup job to detect such activations, but it cannot detect the case when only one activation worker crashes but other server/works are working fine. So we append this work to the existing activation_monitor task.
Rename the activation's current_job_id column to worker_name to store the worker's name. There is no longer the need to store current_job_id because the job id is now uniquely determined by the activation_id.

@bzwei How do we guarantee that the worker name is unique, a user could start 1...n workers, when they come back up after a reboot or a restart how do we preserve the same names.
Since we are using process based jobs, wouldn't RQ handle these jobs and we could just query RQ to figure out if the job that it was running is alive? When the process ends for whatever reason I think RQ would trap it first before us.
https://python-rq.org/docs/jobs/#retrieving-jobs
I think we should depend as much as we can on RQ to for job management.
If we have an orphaned activation we should use RQ to delete the JOB or just attach to that podman instance to read the logs.

@bzwei How do we guarantee that the worker name is unique, a user could start 1...n workers, when they come back up after a reboot or a restart how do we preserve the same names. Since we are using process based jobs, wouldn't RQ handle these jobs and we could just query RQ to figure out if the job that it was running is alive? When the process ends for whatever reason I think RQ would trap it first before us.
https://python-rq.org/docs/jobs/#retrieving-jobs I think we should depend as much as we can on RQ to for job management.
If we have an orphaned activation we should use RQ to delete the JOB or just attach to that podman instance to read the logs.

@mkanoor The worker name is an uuid, so it is unique. Unfortunately the job status reported back from RQ is not accurate. I have tested multiple times when the worker is dead the job however is still reported as running even after timeout period.

@bzwei How do we guarantee that the worker name is unique, a user could start 1...n workers, when they come back up after a reboot or a restart how do we preserve the same names. Since we are using process based jobs, wouldn't RQ handle these jobs and we could just query RQ to figure out if the job that it was running is alive? When the process ends for whatever reason I think RQ would trap it first before us.
https://python-rq.org/docs/jobs/#retrieving-jobs I think we should depend as much as we can on RQ to for job management.
If we have an orphaned activation we should use RQ to delete the JOB or just attach to that podman instance to read the logs.

@mkanoor The worker name is an uuid, so it is unique. Unfortunately the job status reported back from RQ is not accurate. I have tested multiple times when the worker is dead the job however is still reported as running even after timeout period.

Have you experimented with DEFAULT_JOB_MONITORING_INTERVAL and DEFAULT_WORKER_TTL ? We are using the default values. In general I feel all the defaults of RQ quite higher

replaced by the rework https://github.com/ansible/eda-server/pull/551


fix: drop logging packages hard-coded

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Clean up hardcoded logging for packages in favor of a dynamically generated list which is already there
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

LGTM!
I'd like @alexeldeib to take a quick look too before merging.


AppBar actions getting partially duplicated in TabBar

Android

iOS
Code:
import 'package:firebase_auth/firebase_auth.dart';
import 'package:flutter/material.dart';
import 'package:pawfect/components/pawfect_dialogs.dart';

class PawfectAppBar extends StatelessWidget implements PreferredSizeWidget {
  final bool tabShow;
  final bool backButton;

  PawfectAppBar({@required this.tabShow, this.backButton});

  @override
  Size get preferredSize => Size.fromHeight(kToolbarHeight);

  @override
  AppBar build(BuildContext context) {
    return AppBar(
      centerTitle: false,
      automaticallyImplyLeading:
      (backButton != null && backButton == false) ? false : true,
      title: renderTitle(tabShow),
      bottom: renderTabs(tabShow),
      elevation: 2,

      actions: <Widget>[
        GestureDetector(
          onTap: () async {
            String selectedValue = '';
            FirebaseUser user = await FirebaseAuth.instance.currentUser();
            print('Show Popup');
            //TODO Use FutureBuilder here
            await PawfectDialogs().showComingSoonToYourCityDialog(
              userId: user.uid,
              context: context,
            );
          },
          child: Row(
            crossAxisAlignment: CrossAxisAlignment.center,
            children: <Widget>[
              Icon(
                Icons.location_on,
                size: 20,
                color: Colors.white,
              ),
              Padding(
                padding: const EdgeInsets.all(6.0),
                child: Text(
                  'Pune',
                  style: TextStyle(fontSize: 20),
                ),
              ),
              Icon(
                Icons.arrow_drop_down,
                size: 35,
                color: Colors.white,
              )
            ],
          ),
        ),
      ],
    );
  }

  renderTitle(bool tabShow) {
    if (!tabShow) return Image.asset('assets/just_paw_white.png', width: 30);
  }

  renderTabs(bool tabShow) {
    if (tabShow) {
      return TabBar(
        tabs: [Tab(text: 'IN PROGRESS'), Tab(text: 'COMPLETED')],
      );
    }
  }
}

Flutter Doctor Verbose (Including device details)
[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Mac OS X 10.15.2 19C58,
    locale en-IN)
    • Flutter version 1.12.13+hotfix.5 at /Users/uditchugh/Desktop/dev/flutter
    • Framework revision 27321ebbad (4 weeks ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
    • Android SDK at /Users/uditchugh/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling
      support)
    • Platform android-29, build-tools 29.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_202-release-1483-b49-5587405)
    • All Android licenses accepted.

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

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)

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

[✓] Connected device (2 available)
    • Android SDK built for x86 • emulator-5554                        •
      android-x86 • Android 10 (API 29) (emulator)
    • iPhone 11 Pro Max         • 4334EA3C-D72D-4AF1-BC73-5CA01156A5E4 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-13-3 (simulator)

• No issues found!

Issue still exist
flutter doctor -v
[✓] Flutter (Channel dev, v1.18.0, on Mac OS X 10.15.4 19E266, locale en-GB)
    • Flutter version 1.18.0 at /Users/taha/Code/flutter_dev
    • Framework revision de1e572916 (13 hours ago), 2020-04-06 16:15:07 -0700
    • Engine revision df257e59c2
    • Dart version 2.8.0 (build 2.8.0-dev.20.0 1210d27678)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/taha/Code/sdk
    • 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.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4, Build version 11E146
    • CocoaPods version 1.9.1

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

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.0.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

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

[✓] Connected device (5 available)
    • SM M305F      • 32003c30dc19668f          • android-arm64  • Android 10
      (API 29)
    • Taha’s iPhone • 00008020-001059882212002E • ios            • iOS 13.4
    • macOS         • macOS                     • darwin-x64     • Mac OS X
      10.15.4 19E266
    • Chrome        • chrome                    • web-javascript • Google Chrome
      80.0.3987.149
    • Web Server    • web-server                • web-javascript • Flutter Tools

• No issues found!

Hi @thecoffeehog
This no reproduced and also i modified the code sample to provide better height to fit all widgets in appbar

code sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      theme: ThemeData.dark(),
      home: Home(),
    );
  }
}

class Home extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return DefaultTabController(
      length: 2,
      child: Scaffold(
        appBar: CustomAppBar(),
        body: TabBarView(
          children: [
            Icon(Icons.directions_car),
            Icon(Icons.directions_transit),
          ],
        ),
        floatingActionButton: FloatingActionButton(
          child: Icon(Icons.add),
          onPressed: () {},
        ),
      ),
    );
  }
}

class CustomAppBar extends StatelessWidget implements PreferredSize {
  @override
  Widget build(BuildContext context) {
    return AppBar(
      bottom: TabBar(
        tabs: [Tab(text: 'IN PROGRESS'), Tab(text: 'COMPLETED')],
      ),
      elevation: 2,
      actions: <Widget>[
        GestureDetector(
          onTap: () async {},
          child: Row(
            crossAxisAlignment: CrossAxisAlignment.center,
            children: <Widget>[
              Icon(
                Icons.location_on,
                size: 20,
                color: Colors.white,
              ),
              Padding(
                padding: const EdgeInsets.all(6.0),
                child: Text(
                  'Pune',
                  style: TextStyle(fontSize: 20),
                ),
              ),
              Icon(
                Icons.arrow_drop_down,
                size: 35,
                color: Colors.white,
              )
            ],
          ),
        ),
      ],
    );
  }

  @override
  Widget get child => throw UnimplementedError();

  @override
  Size get preferredSize => Size.fromHeight(kToolbarHeight + kTextTabBarHeight);
}

multiple flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on macOS 11.1 20C69 darwin-x64, locale
    en-GB)
    • Flutter version 1.22.5 at /Users/tahatesser/Code/flutter_stable
    • Framework revision<PHONE_NUMBER> (12 days ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • 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-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

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

[✓] Connected device (2 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D          • android-arm64 • Android
      10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios           • iOS
      14.3

! Doctor found issues in 1 category.

[✓] Flutter (Channel dev, 1.26.0-1.0.pre, on macOS 11.1 20C69 darwin-x64, locale
    en-GB)
    • Flutter version 1.26.0-1.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 63062a6443 (9 days ago), 2020-12-13 23:19:13 +0800
    • Engine revision 4797b06652
    • Dart version 2.12.0 (build 2.12.0-141.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • 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-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

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

[✓] Android Studio (version 4.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
      1.8.0_242-release-1644-b3-6915495)

[!] Android Studio
    • Android Studio at /Applications/Android/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
    ✗ Android Studio not found at /Applications/Android/Contents
    • Try updating or re-installing Android Studio.

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

[✓] Connected device (4 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D          • android-arm64  •
      Android 10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios            • iOS
      14.3
    • macOS (desktop)      • macos                     • darwin-x64     • macOS
      11.1 20C69 darwin-x64
    • Chrome (web)         • chrome                    • web-javascript • Google
      Chrome 87.0.4280.88

! Doctor found issues in 1 category.

Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Modified readme for pencil sketch implementation (Issue-364)

#370
Added Readme Improvement for pencil sketch implementation (Issue-364).
Folder consists of readme file and images.

already merged


update pm.variables.replaceIn to support custom variables

This is a follow-up to https://github.com/grafana/postman-to-k6/issues/91
In my postman tests, I am setting
pm.environment.set('name', 'somename')
in one pre-request, and then I use
pm.expect(pm.response.json()).eql(pm.variables.replaceIn('{{name}} whatever'))
in a latter test
The current version of shim/core.js  pm.variables.replaceIn only supports dynamic postman {{$variables}}, not the {{simple}} global/environment/collection ones set up before or during the test.
After reading the shim/core.js code, I have come to the conclusion this matches the functionality provided by shim/core.js evaluate so I copied the logic from there.
The updated code covers the previous use case, and also provides a simple variable support.

hi @RokoTechnology
Thanks for the PR. I'll review it in the coming days/weeks and see if we have tests to cover the behaviour.

Could run npm run format:fix to make sure the code is formatted according to the linting config?

@RokoTechnology I struggle to understand how this can work?
Since you removed the dynamicGenerator part, which is necessary to convert a dynamic Postman variable in a value?

@RokoTechnology As you might have noticed, your PR has landed. It was used & extended with the dynamic variables to support the replaceIn() for regular & dynamic Postman variables.
Thanks again for taking the time to contribute 👏 .


Add dynamically loaded images to Community page

the logic is done but I still need to add styling to the community page.

credit to this library: react-grid-gallery by ben howell


feat: scroll position keeper

Add a scroll position keeper to prevent the scroll from returning to the top when the output is refreshed.

@lentil1016 it is very good, thank you for update🎉

It is online now.
FYI: I updated little bit forcely my main branch de to I forget to ignore wasm file in my previous commit.

@rytsh Hi, sorry for bother. May I ask the reason downhere, that you chose to build this with svelte rather than those old-fashion frameworks like React or Vue?🧐 I'm kind of curious as a backend coder trying to learn very first js framework.

@lentil1016 I checked also react and vue but svelte is much more understandable for me and easy to start and making something on that. When reading some tutorials on their page it is ok to build it.


verifier: generate function is missing

i want to verifiy the received table via the onboard verification function:
flatcc_verify_field()
I generated the flatbuffer for C language.
The problem is that the prototype of the verify function is available in header flatcc_verifier.h but there is no function body.
Is the function body generation implemented for C?

I'm not sure I quite follow. As an example consider the following generated verifier:
https://github.com/dvidelabs/flatcc/blob/master/include/flatcc/reflection/reflection_verifier.h
Ignore reflection it is just some schema reflection.fbs that is already generated and checked in.
The verifier only verifies tables and structs. These are the only things that can be at the root of buffer. But the table verifiers are also not called directly under normal operation. Instead you call the _as_root version. This function is a thin helper to do additional work of reading and verifying the buffer header first. For example:
reflection_Schema_verify_as_root
A table verifier verifies fields, but there is no no generated field verifier. There is only one library function flatcc_verify_field that is called with different parameters. This function is not something you should call directly unless you really know what you are doing. It is defined in
https://github.com/dvidelabs/flatcc/blob/master/src/runtime/verifier.c
and its prototype is found in
https://github.com/dvidelabs/flatcc/blob/master/include/flatcc/flatcc_verifier.h

Maybe your problem is just that you need to link with the src/runtime/verifier.c code?

okey i copied the verifier.c into my project and now the code compiles.
i get allways the return code 2 of the function shema_verify_as_root(buffer, buffer_size)
my buffer is 100k big but the table i load is allways smaller so i give the verifier_as_root a pointer to the beginning of the buffer and the size of the loaded table.

 Not all tools support identifiers. If you do not are about the identifier being correct you can specify a null identifier to the verifier:
mytable_verify_as_root_with_identifier(buf, size, 0).
If this works you may have to use similar with_identifier calls to read the buffer.

I added a section to the README:
https://github.com/dvidelabs/flatcc#trouble-shooting

Thanks for the hint.
with the verifier "mytable_verify_as_root_with_identifier(buf, size, 0)" it works and i found failures in the table.
Thanks for help.


"Scroll to top" make "cursor position" move to top, therefore I can't Scroll to the "cursor position" before

"Scroll to bottom" didn't change the current cursor position, so I can "Scroll to cursor position".

Thanks for your great plugin.
I have a similar / the same issue.
Works

Set the cursor position into the note.
Scroll to bottom
Scroll to cursor position

I can scroll to the last cursor position.
Doesn't work

Set the cursor position  into the note.
Scroll to top
Scroll to cursor position

I cannot scroll to the last cursor position.

When I scroll to top, I cannot scroll back to the last cursor position afterwards.


Escape . from schema.table as schema[.]table

We're rewriting queries while building them so that we can build them in a staging schema. A bug crept in when a CTE had the same name as an upstream table on which the target table depended on.
Example:
WITH dw_fact AS (
  SELECT ...
  FROM dw.fact
)
SELECT ..
FROM dw_fact

Before this fix:
WITH etl_staging$dw.fact AS (
  SELECT ...
  FROM etl_staging$dw.fact
)
SELECT ..
FROM etl_staging$dw.fact

After this fix:
WITH dw_fact AS (
  SELECT ...
  FROM etl_staging$dw.fact
)
SELECT ..
FROM dw_fact

The test should follow the description of the bug: pick a transformation with a CTE and rename the CTE to be similar to a table that the transformation depends on. So if you start from the transformation dw.fact_order which depends on dw._dim_user, then make sure that the dw.fact_order transformation has a CTE called dw_dim_user (which could be just SELECT 1). Before this fix, this will get renamed to dw$dim_user but with this fix, its name will remain as dw_dim_user.
arthur.py sync dw.fact_order
arthur.py upgrade dw.fact_order --with-staging --dry-run --only-selected

Check the arthur.log file to confirm.
Before:
WITH etl_staging$dw.dim_user AS (SELECT 1)

After:
WITH dw_dim_user AS (SELECT 1)


Add support for alternative shells like zsh

By default, nvm writes this to the ~/.bashrc which gave me hell until I remembered I used ./zshrc
export NVM_DIR="/home/gilani/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm

This meant that after every logout or reboot, nvm, npm and node were no longer in the path. Consider support for shells other than bash?

@amingilani nvm works just fine with zsh, and is fully tested on it.
This is just an issue with detecting the right profile file, which is quite difficult.
Closing this as a duplicate of #649


reslove service 503 page hangs

This PR will  leads a Server Side Rendering Error: ReferenceError: document is not defined. But the origin demo page works. 🐶

fix: https://github.com/element-plus/element-plus-nuxt-starter/commit/98aa178d5031359d67653e1b5f5f7611ab94ca1f


1.9rc3 daemon cannot start on fresh RHEL7.1 vm in AWS

[ec2-user@ip-172-31-28-106 ~]$ sh
sh-4.2$ curl -sSL test.docker.com | sh
+ sudo -E sh -c 'sleep 3; yum -y -q install docker-engine'
warning: /var/cache/yum/x86_64/7Server/docker-testing-repo/packages/docker-engine-selinux-1.9.0-0.3.rc3.el7.centos.noarch.rpm: Header V4 RSA/SHA512 Signature, key ID 2c52609d: NOKEY
Public key for docker-engine-selinux-1.9.0-0.3.rc3.el7.centos.noarch.rpm is not installed
Importing GPG key 0x2C52609D:
 Userid     : "Docker Release Tool (releasedocker<EMAIL_ADDRESS> Fingerprint: 5811 8e89 f3a9 1289 7c07 0adb f762 2157 2c52 609d
 From       : https://yum.dockerproject.org/gpg

If you would like to use Docker as a non-root user, you should now consider
adding your user to the "docker" group with something like:

  sudo usermod -aG docker ec2-user

Remember that you will have to log out and back in for this to take effect!

sh-4.2$ docker version
Client:
 Version:      1.9.0-rc3
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   2100b94
 Built:        Wed Oct 28 01:42:24 UTC 2015
 OS/Arch:      linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
sh-4.2$ docker info
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
sh-4.2$ sudo /bin/systemctl start docker.service
Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
sh-4.2$ sudo systemctl status docker.service
docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled)
   Active: failed (Result: timeout) since Wed 2015-10-28 19:43:49 EDT; 1min 35s ago
     Docs: https://docs.docker.com
 Main PID: 10811

Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Starting Docker Application Container Engine...
Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal docker[10811]: time="2015-10-28T19:42:17.912940792-04:00" level=info msg="API listen on /var/run/docker.sock"
Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal docker[10811]: time="2015-10-28T19:42:17.997419286-04:00" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to r...hinpooldev section."
Oct 28 19:43:47 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: docker.service operation timed out. Terminating.
Oct 28 19:43:49 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Failed to start Docker Application Container Engine.
Oct 28 19:43:49 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Unit docker.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
sh-4.2$ sudo journalctl -xn
-- Logs begin at Wed 2015-10-28 19:34:55 EDT, end at Wed 2015-10-28 19:45:38 EDT. --
Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal docker[10811]: time="2015-10-28T19:42:17.912940792-04:00" level=info msg="API listen on /var/run/docker.sock"
Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal kernel: device-mapper: uevent: version 1.0.3
Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal kernel: device-mapper: ioctl: 4.29.0-ioctl (2014-10-28) initialised<EMAIL_ADDRESS>Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal kernel: loop: module loaded
Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal docker[10811]: time="2015-10-28T19:42:17.997419286-04:00" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev
Oct 28 19:43:47 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: docker.service operation timed out. Terminating.
Oct 28 19:43:49 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Oct 28 19:43:49 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Unit docker.service entered failed state.
Oct 28 19:45:24 ip-172-31-28-106.us-west-2.compute.internal sudo[10860]: ec2-user : TTY=pts/0 ; PWD=/home/ec2-user ; USER=root ; COMMAND=/bin/systemctl status docker.service
Oct 28 19:45:38 ip-172-31-28-106.us-west-2.compute.internal sudo[10863]: ec2-user : TTY=pts/0 ; PWD=/home/ec2-user ; USER=root ; COMMAND=/bin/journalctl -xn
sh-4.2$ uname -a
Linux ip-172-31-28-106.us-west-2.compute.internal 3.10.0-229.el7.x86_64 #1 SMP Thu Jan 29 18:37:38 EST 2015 x86_64 x86_64 x86_64 GNU/Linux
sh-4.2$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.1 (Maipo)

more logs:
sh-4.2$ sudo journalctl -xeu docker
-- Logs begin at Wed 2015-10-28 19:34:55 EDT, end at Wed 2015-10-28 20:20:29 EDT. --
Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal docker[10811]: time="2015-10-28T19:42:17.912940792-04:00" level=info msg="API listen on /var/run/docker.sock"
Oct 28 19:42:17 ip-172-31-28-106.us-west-2.compute.internal docker[10811]: time="2015-10-28T19:42:17.997419286-04:00" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev
Oct 28 19:43:47 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: docker.service operation timed out. Terminating.
Oct 28 19:43:49 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Oct 28 19:43:49 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Unit docker.service entered failed state.
Oct 28 20:08:29 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Oct 28 20:08:29 ip-172-31-28-106.us-west-2.compute.internal docker[10954]: time="2015-10-28T20:08:29.482643955-04:00" level=info msg="API listen on /var/run/docker.sock"
Oct 28 20:08:29 ip-172-31-28-106.us-west-2.compute.internal docker[10954]: time="2015-10-28T20:08:29.511076798-04:00" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev
Oct 28 20:09:25 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Stopping Docker Application Container Engine...
-- Subject: Unit docker.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun shutting down.
Oct 28 20:09:25 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: docker.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 28 20:09:25 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Stopped Docker Application Container Engine.
-- Subject: Unit docker.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has finished shutting down.
Oct 28 20:09:25 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Unit docker.service entered failed state.
Oct 28 20:15:29 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Oct 28 20:15:30 ip-172-31-28-106.us-west-2.compute.internal docker[20858]: time="2015-10-28T20:15:30.038030041-04:00" level=info msg="API listen on /var/run/docker.sock"
Oct 28 20:15:30 ip-172-31-28-106.us-west-2.compute.internal docker[20858]: time="2015-10-28T20:15:30.040180033-04:00" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev
Oct 28 20:16:59 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: docker.service operation timed out. Terminating.
Oct 28 20:18:29 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: docker.service stopping timed out (2). Killing.
Oct 28 20:18:29 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Oct 28 20:18:29 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Unit docker.service entered failed state.

ping @vbatts do you think devmapper issue or @mavenugo something w networking

so we're looking at a RHEL7.1 host, that is pulling down the dockerproject.org rpm. It times-out when starting the daemon?

The loopback warning doesn't fail launch presently. It may be worth a try to add -s overlay to the /etc/sysconfig/docker settings to try a different storage driver. Also -D for debug output.

yeah the service seems to be hanging when starting?

Yeah, wonder if it's devicemapper provisioning and it's taking too long?

Maybe similar to #17448 if that is the case?

after adding -s overlay -D it looks like things are working now. here's a link to the new logs from sudo journalctl -xeu docker: https://gist.github.com/donhcd/f6952a1f7203ee583ef9

@donhcd thanks. for debugging sake, would you mind switching it back, but keeping the debug flag (-s devicemapper -D). This way we might gain more needed information to investigate the root cause.

I changed the flags to -s devicemapper -D and ran sudo systemctl stop docker && sudo systemctl start docker. The start did not hang and appeared to succeed, but looks like the daemon immediately died after starting. Logs:
Oct 29 14:25:07 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Stopping docker.service...
-- Subject: Unit docker.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun shutting down.
Oct 29 14:25:07 ip-172-31-28-106.us-west-2.compute.internal docker[28271]: time="2015-10-29T14:25:07.608901731-04:00" level=info msg="Processing signal 'terminated'"
Oct 29 14:25:07 ip-172-31-28-106.us-west-2.compute.internal docker[28271]: time="2015-10-29T14:25:07.609436177-04:00" level=debug msg="starting clean shutdown of all containers..."
Oct 29 14:25:07 ip-172-31-28-106.us-west-2.compute.internal docker[28271]: time="2015-10-29T14:25:07.609650088-04:00" level=debug msg="Cleaning up old shm/mqueue mounts: start."
Oct 29 14:25:07 ip-172-31-28-106.us-west-2.compute.internal docker[28271]: time="2015-10-29T14:25:07.609986268-04:00" level=debug msg="Cleaning up old shm/mqueue mounts: done."
Oct 29 14:25:07 ip-172-31-28-106.us-west-2.compute.internal docker[28271]: time="2015-10-29T14:25:07.610051527-04:00" level=debug msg="Unix socket /var/lib/docker/network/files/36ca1c2f4072c9f3a5987aeb3f4a86791b1e4d92ef488a0e0407d9a829f9a5e6.sock doesnt exist. cannot accept client connections"
Oct 29 14:25:07 ip-172-31-28-106.us-west-2.compute.internal docker[28271]: time="2015-10-29T14:25:07.610071317-04:00" level=debug msg="Clean shutdown succeeded"
Oct 29 14:25:07 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Stopped docker.service.
-- Subject: Unit docker.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has finished shutting down.
Oct 29 14:25:10 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Starting docker.service...
-- Subject: Unit docker.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Oct 29 14:25:10 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Started docker.service.
-- Subject: Unit docker.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has finished starting up.
--
-- The start-up result is done.
Oct 29 14:25:10 ip-172-31-28-106.us-west-2.compute.internal docker[29584]: time="2015-10-29T14:25:10.328885124-04:00" level=fatal msg="No sockets found"
Oct 29 14:25:10 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Oct 29 14:25:10 ip-172-31-28-106.us-west-2.compute.internal systemd[1]: Unit docker.service entered failed state.

I'll try this from a fresh install and see what I get then

okay, from a fresh vm, I ran:
curl -sSL test.docker.com | sh
sudo sh -c 'echo -e "[Service]\nExecStart=/usr/bin/docker daemon -H fd:// -s devicemapper -D" > /etc/systemd/system/docker.service'
sudo systemctl daemon-reload
sudo systemctl start docker
sudo journalctl -xeu docker

the behavior was the same as above, and the logs returned by journalctl command seem to be the same:
Oct 29 14:34:51 ip-172-31-30-61.us-west-2.compute.internal systemd[1]: Starting docker.service...
-- Subject: Unit docker.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Oct 29 14:34:51 ip-172-31-30-61.us-west-2.compute.internal systemd[1]: Started docker.service.
-- Subject: Unit docker.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has finished starting up.
--
-- The start-up result is done.
Oct 29 14:34:51 ip-172-31-30-61.us-west-2.compute.internal docker[10811]: time="2015-10-29T14:34:51.466842286-04:00" level=fatal msg="No sockets found"
Oct 29 14:34:51 ip-172-31-30-61.us-west-2.compute.internal systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Oct 29 14:34:51 ip-172-31-30-61.us-west-2.compute.internal systemd[1]: Unit docker.service entered failed state.

I found #11135, so I tried removing the -H fd:// flags (they were there by default) and that got rid of the "No sockets found" error. Now, the startup logs look like this:
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal systemd[1]: Starting docker.service...
-- Subject: Unit docker.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal systemd[1]: Started docker.service.
-- Subject: Unit docker.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has finished starting up.
--
-- The start-up result is done.
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.068913666-04:00" level=debug msg="docker group found. gid: 995"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.069180650-04:00" level=debug msg="Server created for HTTP on unix (/var/run/docker.sock)"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.069492212-04:00" level=debug msg="[graphdriver] trying provided driver \"devicemapper\""
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.071825091-04:00" level=info msg="API listen on /var/run/docker.sock"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.092892749-04:00" level=debug msg="devicemapper: driver version is 4.29.0"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.093386645-04:00" level=debug msg="Generated prefix: docker-202:2-8390534"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.093408383-04:00" level=debug msg="devmapper: Checking for existence of the pool docker-202:2-8390534-pool"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.094396466-04:00" level=debug msg="Pool doesn't exist. Creating it."
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.094467325-04:00" level=debug msg="Creating loopback file /var/lib/docker/devicemapper/devicemapper/data for device-manage use"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.107812984-04:00" level=debug msg="Creating loopback file /var/lib/docker/devicemapper/devicemapper/metadata for device-manage use"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.166436287-04:00" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev s
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.166507559-04:00" level=debug msg="Initializing base device-mapper thin volume"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.169080704-04:00" level=debug msg="[devmapper] CreateDevice(poolName=/dev/mapper/docker-202:2-8390534-pool, deviceID=1)"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.172155668-04:00" level=debug msg="Registering device (id 1) with FS size<PHONE_NUMBER>00"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.172180963-04:00" level=debug msg="registerDevice(1, )"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.174891269-04:00" level=debug msg="Creating filesystem on base device-mapper thin volume"
Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.174911857-04:00" level=debug msg="activateDeviceIfNeeded()"

Then I tried some docker run commands, which all seemed to be hanging. I let one command run extra long and finally the engine pulled busybox and things worked mostly as expected:
[ec2-user@ip-172-31-20-21 ~]$ sudo docker run scratch
^C[ec2-user@ip-172-31-20-21 ~]$ sudo docker run -it scratch
^C[ec2-user@ip-172-31-20-21 ~]$ sudo docker run -it scratch bash
^C[ec2-user@ip-172-31-20-21 ~]$ sudo docker run -it busybox bash
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
ab2b8a86ca6c: Pull complete
2c5ac3f849df: Pull complete
Digest: sha256:5551dbdfc48d66734d0f01cafee0952cb6e8eeecd1e2492240bf2fd9640c2279
Status: Downloaded newer image for busybox:latest
exec: "bash": executable file not found in $PATH
Error response from daemon: Cannot start container 5b1ef600287a2c6837c327a25cfec909710f7bca786184394ef1231446522101: [8] System error: exec: "bash": executable file not found in $PATH
[ec2-user@ip-172-31-20-21 ~]$ sudo docker run scratch echo hi
Unable to find image 'scratch:latest' locally
Error response from daemon: 'scratch' is a reserved name
[ec2-user@ip-172-31-20-21 ~]$ sudo docker run busybox echo hi
hi
[ec2-user@ip-172-31-20-21 ~]$

coming back to the daemon logs, I saw these logs (I repeated the last line from the previous logs snippet to show the difference in time): https://gist.github.com/donhcd/5df51ae55eff6f1f8486
Why are there nearly 5 minutes between starting the daemon and the daemon actually being useful?

Looks like devicemapper is the culprit in the long startup:

Oct 29 17:16:13 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:16:13.174911857-04:00" level=debug msg="activateDeviceIfNeeded()"
Oct 29 17:21:30 ip-172-31-20-21.us-west-2.compute.internal docker[11065]: time="2015-10-29T17:21:30.190972667-04:00" level=debug msg="activateDeviceIfNeeded()"

I think it is slow xfs initialization on 100G device for a thin pool which  is on top of loop devices. We have noticed the instances of systemd timing out and as a stop gap measure, increasing systemd timeout from 90 seconds to 5 minutes.
Can you try passing option --storage-opt dm.basesize=10G to daemon command line and see if problem is resolved.

okay, so I can't repro the slow start on the same machine with systemctl stop docker && systemctl start docker, but I could when I spun up a new machine and repeated the steps. from a brand new vm, here's my history:
    1  export EDITOR=vi
    2
    3  curl -sSL test.docker.com | sh
    4  sudo sh -c 'echo -e "[Service]\nExecStart=/usr/bin/docker daemon -s devicemapper -D --storage-opt dm.basesize=10G" > /etc/systemd/system/docker.service'
    5  sudo systemctl daemon-reload
    6  sudo systemctl start docker

Right after, I ran a docker run and it worked as expected:
$ sudo docker run busybox
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
ab2b8a86ca6c: Pull complete
2c5ac3f849df: Pull complete
Digest: sha256:5551dbdfc48d66734d0f01cafee0952cb6e8eeecd1e2492240bf2fd9640c2279
Status: Downloaded newer image for busybox:latest

logs output from sudo journalctl -xeu docker here

I've seen the same and I see that mkfs.ext4 -E nodiscard,lazy_itable_init=0,lazy_journal_init=0 /dev/mapper/docker-202:1-25558685-base is running this CentOS 7 EC2 instance I am working on.
I could see that it was waiting on the mkfs.ext4 process to complete when checking the status while waiting for systemctl start docker to complete:
# systemctl status docker -l
docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled)
   Active: deactivating (final-sigterm) (Result: timeout)
     Docs: https://docs.docker.com
 Main PID: 10752
   CGroup: /system.slice/docker.service
           └─10789 mkfs.ext4 -E nodiscard,lazy_itable_init=0,lazy_journal_init=0 /dev/mapper/docker-202:1-25558685-base

Oct 31 15:32:13 ip-172-31-30-107 systemd[1]: Starting Docker Application Container Engine...
Oct 31 15:32:13 ip-172-31-30-107 docker[10752]: time="2015-10-31T15:32:13.695345145Z" level=info msg="API listen on /var/run/docker.sock"
Oct 31 15:32:13 ip-172-31-30-107 docker[10752]: time="2015-10-31T15:32:13.920344399Z" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` t
o refer to dm.thinpooldev section."
Oct 31 15:33:43 ip-172-31-30-107 systemd[1]: docker.service operation timed out. Terminating.

I'm seeing docker is taking forever to start up on Fedora Rawhide as well, and the process is actually hanging on activateDeviceIfNeeded

FWIW, I could reproduce not only with 1.9 but also with 1.8 :( So is there something that changed on AWS ? I could not reproduce this on DigitalOcean on Centos 7.1, neither with 1.8 nor 1.9.

I was thinking that problem is due to 100G device but looks like it has something to do with ext4. I changed my fs type to xfs and it seems to work well with both 10G and 100G base device size.
Those who are facing problems, can you try following as option to docker daemon.
-s devicemapper --storage-opt dm.fs=xfs
I just launched an fedora 22 instances in AWS and it is running docker 1.8 and by default ext4 is being used and systemd time out is happening. Even if I use dm.basesize=10G, it does not fix the problem for me. But if I force usage of xfs, it works just fine.
So this does not look like specific to docker 1.9.

@runcom from logs it looks like as if activateDeviceIfNeeded() is the problem but that's not the case. In this case somehow mkfs.ext4 takes a very long time and systemd times out. It is not clear though why does it take so long. May be slow cloud storage?

@rhvgoyal it worked for me

@rhvgoyal do you recommend this setting for all RHEL/CentOS setups or just the ones on AWS ?

@tiborvass we try to use xfs as default for all rhel/centos. docker-storage-setup enforces that.
https://github.com/projectatomic/docker-storage-setup/blob/master/docker-storage-setup.sh#L121
If docker-storage-setup fails because there is no free space to setup thin pool, then we are not able to override default fs (ext4) setting and that's where the problem with AWS seem to be visible.
I think it is a good idea to use xfs for all RHEL/CentOS.

@rhvgoyal forgot to say that the Fedora rawhide I tested with was a virtual machine if this could help further (virt install, virsh managed, qemu/kvm)

@runcom, I tested on a fedora 22 VM on my local machine both with ext4 and xfs  (on top of loop devices) an I can't reproduce the problem. So somehow problem is only visible with ext4 in AWS.

Mmm weird (vm's host is Fedora 22 on my laptop not AWS)

@runcom ok, so you have F22 host and rawhide VM and you are able to see the problem. Does using xfs as container fs make the problem go away?

I'll try to reproduce with xfs as the container fs and report here, thanks!

Ok, I removed options lazy_itable_init=0 and lazy_journal_init=0 and that fixes the problem for ext4 on AWS. docker initializes with-in 2 seconds.
So looks like it boils down to how much fs data gets created at mkfs time and how much of it is deferred. I am not sure why did we use these two options to begin with. What's the rationale. Why not stick with defaults.

So what's the way forward. I see two options.

Use xfs by default.

Drop mkfs.ext4 options lazy_itable_init=0 and lazy_journal_init=0. This seems to force initializaiton of all metadata at creation time and it does not seem to be default. If we don't initialize all metadata at mkfs time and let a thread do it later after mount, then downside seems to be that we will be doing it on containers (snapshots) and if there are N container from 1 image, then we will do it N times and use much more thin pool space. So in case of ext4 trade off seems to be initialization time vs thin pool usage.

@sandeen mentioned that XFS does not have knobs for preallocating metadata. It dynamically allocates it as needed.

@rhvgoyal which option do you prefer? XFS ?

@tiborvass we have been using xfs as default and we enforce it in docker-storage-setup. So I feel xfs should be a good default choice. So I prefer making xfs as default.

@rhvgoyal ok thank you, since this is an AWS specific issue, I think it's less intrusive right now for 1.9 to not change the default in docker, and change our install scripts instead. I'll open a PR to close this issue.

@tiborvass That's fine.

@alexlarsson I noticed that from the beginning we have been using options 'lazy_itable_init=0,lazy_journal_init=0' for mkfs.ext4. I am wondering why did you choose to do it that way. Pre-allocating all the metadata on slower storage is turning out to be slow. 10G base image itself took more then 3 minutes only my system. Now default base image size is 100G and we have no chance to initialize it in time.
I ran some blktrace and on 10G image, ext4 did around 300MB of writes and I got around 1.5MB/s as overall throughput. I see lots of writes are synchronous writes and that might be responsible for this or may be IO pattern is fairly random.
Anyway, I thought I will quickly ping you and understand what's your take on this issue.

https://github.com/docker/docker/issues/3280 has some background on using the lazy-* options. However, the thread later has an open ended discussion on why using lazy_itables_init might be poor use in this case.
" i.e. although its likely to work, it will cause a lot of writes in each snapshot making them unnecessarily different"
Any comments on this? Thanks.

@rhvgoyal I will forward you the internal thread wrt the lazy_init stuff.  It's 2 years old at this point.  Bottom line is that it's not terribly relevant these days -- your advice to use xfs is correct; which as you stated has been present in RHEL/Fedora packages for a long time.
Thank you @tiborvass for merging the change to xfs!

@rhvgoyal I used to be able to reproduce this, but now I can't. It took 28sec to boot, but it worked just fine.

@jeremyeder @rhvgoyal do you guys think it's safe to remove lazy_init=0 and lazy_journald=0 for 1.9.1 ? We can try to make xfs default for 1.10.

@tiborvass This will happen only during first time docker is started and loop files are setup and file system is created. On subsequent restart of docker, base image is already there with filesystem on it so one would not face this issue.

@tiborvass I don't think getting rid of 'lazy_init=0' is an option. Reason being that would mean that we will  create ext4 metadata per container and that will lead to huge pool usage.
For example, with 100G thin device and with ext4 lazy_init=0, thin pool usage is around 1.8GB. That means there is roughly around 1.8GB of metadata which will be initialized per container if we disable pre-allocation.
I verified this by launching two containers and slowly pool usage goes up by around 1.5GB per container instance.
So I don't think that making 'lazy_init=0' is really an option.

@tiborvass So we had some conversations about ext4 behavior internally. @sandeen looked into a possible ext4 optimization where zeroing is skipped if discards are issued and device advertizes discards_zeros_data. Thin devices set discards_zeros_data=0 hence ext4 optimization does not kick in.
Now thought is that there does not seem to be a good way to support discards_zeros_data=1. Discards themselves are optional and blkdev_issue_discard() interface can chop off some of the discard area in the beginning and at the end. So current thought is that discards_zeros_data=1
is very hard and it seems to be contradictory to the notion of discards being optional.
In my testing AWS is not always slow. Today 100G thin device initialized in 1.5 minute. (as compared to taking 3 minutes on a 10G device). So looks like this varies a lot.
So either we switch to xfs by default (and fall back to ext4 if mkfs.xfs is not there). Or we just live with ext4 being default and if somebody runs into issues, suggest them to use dm.fs=xfs.

@rhvgoyal Have you tried on a fresh RHEL VM on AWS ? It not only takes 1m30, it fails as explained in the issue. Try curl -SL https://get.docker.com/ | sh on a fresh RHEL on AWS and try sudo systemctl start docker and you'll see the failure.
I think we'll go with the xfs by default if mkfs.xfs is present. We just need to make sure to test it on all OSes.

@tiborvaas I tried on Fedora 23 with a modified systemd docker.service unit file with timeout set to 5 minutes instead of 1 minute.
Point I was raising was that this mkfs.ext4 time seems to vary a lot on AWS. So sometimes it will fail and sometimes it will pass.
Apart from mfs.xfs being present I think we will have to make sure kernel supports xfs too. Otherwise we could have a case where mkfs.xfs is installed but kernel has been compiled with xfs support.

@rhvgoyal I only care about the default AMIs provided on AWS console, that's the most important right now since that's what people seem to spawn. If you have issues creating VMs on AWS for various reasons, can you give me your public ssh key so you I can add you to a fresh VM? Also would be easier to communicate on IRC or Slack. Let me know.

Closed by #17903


test(plonky2): Acessing multi-dimentional array with prover variable

This is a test which outlines a bug/missing feature of array targets.
If we have a multidimensional array and access a non-last element (so, an element which isn't of type T but of type Array<Array<...<T>...>>), then we would get an "Internal Inconsistency Evaluators Error", or more specifically a "PLONKY2 backend ICE error: get_target called on a non-int, non-bool value".
As far as I can tell, we haven't fully implemented an ArrayTarget P2Target, meaning we haven't (fully?) implemented addressing of multidimensional arrays during proving.

That's true, we haven't.
Thanks for the test.


MAVlink forwarding

@sanderux This hopefully fixes the issues you were facing with forwarding. Could you cross-test and fix where required?

nice, i'll have a look

I added changes that allow relaying when it's from the same systemID but a different component. This is required to relay statustext messages and have them show up in the GCS

Tested, works

@LorenzMeier can you revert your camera changes so we can get this in?

Good to merge. I also verified memory footprint and made sure UAVCAN setups should still be fine.


Multiselect is annoying for me

What feature or improvement do you think would benefit Files?
First of all thank you for this amazing repository, I really LOVE IT. I would use just this file explorer and ditch the default one but I can not get over one thing: PLEASE add one more selection option to work like in the default windows files explorer.
Requirements
Will be more user friendly and not always thinking in what selection option i am. At least for me 😄
And maybe allow us to rearrange the"Home" sidebar the way you want. For example: "Drives" above then "WSL" then "Tags" ...
Files Version
Version: <IP_ADDRESS> OS
Windows Version
Windows 10 Pro 22H2 OS build 19045.2486
Comments

This was recently added and will be included in the next release.

@yaira2 thanks for your answer. The Microsoft Store and GitHub version is the same?


Add basic mutation endpoint to the API

Description
Added the basic mutation endpoint. This will act as a foundation for the advanced mutation API.
Mutations are GraphQL's way of creating, updating or deleting data. These mutation endpoints will update data in the DB.

@snowteamer Can you also look into this to see if I it LGT you?

Clsing and re-opening PR due to GitHub action stall.


Fixes #773, #789
/cc @ekmartin

My question is: -webkit-user-select is producing this side effect, or was my logic for deciding when to make text unselectable wrong?

@rauchg, I think it's the WebKit prefix. Moreover, it breaks pasting, not just text selection, which I don't understand 🤔 I'm limited on the debugging I can do on my daily Linux machine because my dev tools are broken.

The problem is that I took out the preventDefault that made us lose focus when performing terminal clicks, but in the process I lost the functionality of making text unselectable when doing so. This was an attempt to restore that. I was unaware of these side effects :|

I do agree with you that if we don't figure out something really soon, I'm down for sacrificing the text selection quirk when clicking and restoring copying and pasting :D

I can confirm that this indeed fixes both being able to paste in vim as well as mouse support in tmux.

Any chance that this will be merged soon and included in a release?

Please resolve the conflicts! Will merge it 😊

Done in https://github.com/zeit/hyper/commit/f96d02480df9f8fd6116805b68ba1afbead459e9


Return a 404 when the barcode was not found in alma

advances #1032
resolves https://app.honeybadger.io/projects/54497/faults/74581782

Coverage increased (+0.02%) to 82.508% when pulling 061dbf76615888f804c6cee7ec959748b7f3c4fd on 1032-barcode-not-found into 682b98acbb44bffa95c6e7b61e92c57cdfebb251 on alma.


Blocking not working properly in case of reconnections

There is this older issue https://github.com/luin/ioredis/issues/610 also created by me. But since this is rather important I would like to create a new one with a very specific code to reproduce the issue easily so that it can be resolved once and for all :).
This is the code:

async function main() {
  const client = new Redis();

  client.on('error', err => console.log('Redis error', err));
  client.on('reconnecting', msg => console.log('Redis reconnecting...', msg));
  client.on('close', () => console.log('Redis closed...'));
  client.on('connect', () => console.log('Redis connected...'));

  while (true) {
    try {
      console.log('going to block');
      const value = await client.brpoplpush('a', 'b', 4);
      console.log('unblocked', value);
    } catch (err) {
      console.error('ERROR', err);
    }
  }
}

main();

How to reproduce
Just run the code above with a local redis server. The while loop will run forever outputting the following:
going to block
Redis connected...
unblocked null
going to block
unblocked null
going to block
unblocked null
going to block

It just blocks for up to 4 seconds, then unblocks, and so on.
Now, while this program is running just stop the redis server, wait a couple of seconds and start it again:
Output would look like this:
Redis closed...
Redis reconnecting... 50
Redis connected...
Redis closed...
Redis reconnecting... 100
Redis error Error: connect ECONNREFUSED <IP_ADDRESS>:6379
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 6379
}
...
...
Redis closed...
Redis reconnecting... 700
Redis connected...

And thats all. The while loop will not continue running as if the call to client.brpoplpush has hanged forever.
Expected results
I expect that as soon as the the client disconnects the call to client.brpoplpush rejects the promise with a connection error. Client code should be able to handle calling again to this blocking command.
I am a bit surprised no one else has reported this issue, I wonder if there is some wrong expectation from my side or if I am using the library incorrectly, if so please let me know since this issue is quite severe for users of Bull/BullMQ libraries.

Hey @manast, thanks for raising this.
Actually, the code works as expected on my side:
Redis closed...
Redis reconnecting... 100
Redis error Error: connect ECONNREFUSED <IP_ADDRESS>:6379
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 6379
}
...
...
Redis closed...
Redis reconnecting... 2000
Redis connected...
unblocked null
going to block
unblocked null
...

The expected result is when the server is down, ioredis should try to reconnect (according to retryStrategy), and once connected again, all pending commands should be resent. If the server is down forever (or long enough, according to autoResendUnfulfilledCommands), the brpoplpush should be rejected (according to maxRetriesPerRequest) as you mentioned.
Did I miss anything?

ok, this is interesting. After reading your response I tried with a redis server running natively in my mac instead of using a docker container as before, and now I get the same result as you did, how is it possible?

Could you provide some instructions for a reproducible setup? Ex the cli command to run the docker container.

docker run --name redis -p 6379:6379 -d redis
run test snippet above
docker stop redis
wait a couple of seconds
docker start redis

Hmm...that's strange. I followed the steps but still got the same result as I posted above.
Did you notice the error when the server was down more than ~8s:

No I did not get the MaxRetriesPerRequestError either.
I tried with redis:latest and ioredis 4.22.0 still it is reproducible every time in my setup, intel MacOs Bigsur 11.1

I also experienced the same issue with bullmq causing memory leaks and high cpu load. And the while loop was the reason in some cases. There might really a bug in ioredis in the reconnecting state, but I haven't had the issue anymore since I checked the states manually:
function waitForReconnect (client) {
  let reconnectListener
  const promise = new Promise((resolve) => {
    readyListener = function () {
      client.removeListener('ready', reconnectListener)
      client.removeListener('end', reconnectListener)
      resolve()
    }
    client.once('ready', reconnectListener)
    client.once('end', reconnectListener)
  })

  promise.resolve = reconnectListener
  return promise
}

And adopt it in the loop:
  // call reconnectListener.resolve() during server/queue shutdown
  let reconnectListener = undefined

  while (true) {
    if (client.status === 'end') return

    try {
      console.log('going to block');
      const value = await client.brpoplpush('a', 'b', 4);
      console.log('unblocked', value);
    } catch (err) {
      // if redis got closed (by a stopping server, we can just return as the queue should be shut down)
      if (client.status === 'end') return
      console.error('ERROR', err);

      switch (client.status) {
        case 'wait':
        case 'connecting':
        case 'reconnecting':
          reconnectListener = waitForReconnect(client)
          await readyListener
          readyListener = undefined
      }
    }
  }

Anyone that can reproduce this issue can you enable the debug log (DEBUG=ioredis* node yourapp) and post the logs here? Also, we just updated a new version (v4.24.2) with a connection-related fix, I don't think they're related though but can you try with the latest version to make sure?

@luin like mentioned here by @manast, it's happening for me as well on Redis instance inside Docker on Mac.
<EMAIL_ADDRESS><EMAIL_ADDRESS>running on<EMAIL_ADDRESS>on Mac.

We are facing an issue of jobs getting stuck on a few productions instances too (non docker), I am guessing it could be because of the same but I am not sure.
Any thoughts ?

@luin attaching logs with DEBUG=ioredis* , it's simply stuck without any logs.
ioredis.log

I manage to reproduce this issue : it occurs when retryStrategy is returning values less than 50 (exp(0), exp(1), exp(2) in the code snippet below, BullMQ default)
Cannot reproduce with ioredis default retryStrategy  Math.min(times * 50, 2000); because returning always numbers >= 50
https://github.com/luin/ioredis/blob/0db2d4f5f27d7106832c934a798e616836d1d0a6/lib/redis/event_handler.ts#L181
import Redis from 'ioredis';

async function main() {

    // https://github.com/taskforcesh/bullmq/blob/0fb2964151166f2aece0270c54c8cb4f4e2eb898/src/classes/redis-connection.ts#L62
    const retryStrategy = (times: number) => Math.min(Math.exp(times), 20000);
    const client = new Redis({ retryStrategy });

    client.on('error', err => console.log('Redis error', err));
    client.on('reconnecting', msg => console.log('Redis reconnecting...', msg));
    client.on('close', () => console.log('Redis closed...'));
    client.on('connect', () => console.log('Redis connected...'));

    while (true) {
        try {
            console.log('brpoplpush');
            await client.brpoplpush('a', 'b', 4);
            console.log('brpoplpush end');
        } catch (err) {
            console.error('error', err);
        }
    }
}

main().catch();

Output :
brpoplpush
Redis connected...
Redis closed...
Redis reconnecting... 2.718281828459045
Redis connected...
Redis error Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
  errno: -104,
  code: 'ECONNRESET',
  syscall: 'read'
}
Redis closed...
Redis reconnecting... 7.38905609893065
Redis error Error: connect ECONNREFUSED <IP_ADDRESS>:6379
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 6379
}
Redis closed...
Redis reconnecting... 20.085536923187668
Redis error Error: connect ECONNREFUSED
Redis closed...
Redis reconnecting... 54.598150033144236
Redis error Error: connect ECONNREFUSED
Redis closed...
Redis reconnecting...<PHONE_NUMBER>025766
Redis error Error: connect ECONNREFUSED
Redis closed...
Redis reconnecting...<PHONE_NUMBER>927351
Redis error Error: connect ECONNREFUSED
Redis closed...
Redis reconnecting... 1096.6331584284585
Redis connected...


Evaluate the new mistral-large and other new closed mistral models

Re-evaluated all mistral and openai models.


Bloom Desktop version connectivity to PowerBI

We havent bought licensed version of Bloom yet , But we want to try if we can connect Bloom to Power BI .

Hello @rohinibaraskar !
Neo4j Bloom can only connect to a Neo4j database, so if you want to visualise that data in Bloom the first step is importing the data in a Neo4j database.
In order to import data from Power BI you can use the appropriate Neo4j Connector, which is available here Neo4j Download Center
If it is not what you're trying to do please describe your use case,
Thanks!

hi @GlacialBoy
Lets say , I have few "Search Phrases " saved query templates in Bloom and I want sperate URL for each that search phrase How can I achieve that.
I can render home page of bloom in browser but I wanted to load query output of particular search phrase in browser whenever I specify that particular URL
Could you please assist?

its working


Fixed the issues #40 and #41

This will fix the issue #40
This will fix the issue #41

I will change the way that input and input container handle classes. I will close this PR because those changes related to methods changing classes directly will become obsolete. Thank you!


Serverless asset compatibility (e.g. Firebase)

This pull request integrates a few weeks worth of work on @zeit/webpack-asset-relocator-loader to get it ready for usage in Next.js. 🙏
Notably, this pull request allows Firebase to work out of the box with Serverless!
This will likely be landed after Next.js 9.0.0 is released. It's missing its companion @now/next PR.

Closes #7512
Closes #7391
Closes #6655
Supersedes #6073

Hello, Will it solve this issue?
https://github.com/zeit/next.js/issues/7821

Hello, someone have an idea when this will be released ? :-)

👀

as per #8052  this seems to relate to issues loading jimp as well as react-ssr-prepass

I hate to be that guy, but I have a client with his hair on fire because I can't deploy, is there ANYTHING I can do to help this along?

testing?
merge conflict?
backrub?

@Pushplaybang u can implement same by your own just check how this PR works in files
U will need zeit/webpack-asset-relocator-loader

@Pushplaybang you can follow these instructions for the time being: https://github.com/zeit/next.js/issues/6073#issuecomment-467589586

@Timer the workaround in #6073 does not fix the issue mentioned in #8052 which is what led me here,   Once thats applied it fixes the grpc issue, and then I receive the following:
Jul 23 2019 09:33:28:793 | ...package.json | Module not found: Can't resolve 'iconv' in '/tmp/6c75a54f/node_modules/encoding/lib'
-- | -- | --
Jul 23 2019 09:33:29:413 | ...package.json | Warning: You have opted-out of Automatic Prerendering due to `getInitialProps` in `pages/_app`.
Jul 23 2019 09:33:29:413 | ...package.json | Read more: https://err.sh/next.js/opt-out-automatic-prerendering
Jul 23 2019 09:33:30:462 | ...package.json | > Build error occurred
Jul 23 2019 09:33:30:464 | ...package.json | { Error: Failed to load /tmp/6c75a54f/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc/grpc_node.node. Module did not self-register.
Jul 23 2019 09:33:30:464 | ...package.json | at Object.Module._extensions..node (internal/modules/cjs/loader.js:730:18)
Jul 23 2019 09:33:30:464 | ...package.json | at Module.load (internal/modules/cjs/loader.js:600:32)
Jul 23 2019 09:33:30:464 | ...package.json | at tryModuleLoad (internal/modules/cjs/loader.js:539:12)
Jul 23 2019 09:33:30:464 | ...package.json | at Function.Module._load (internal/modules/cjs/loader.js:531:3)
Jul 23 2019 09:33:30:464 | ...package.json | at Module.require (internal/modules/cjs/loader.js:637:17)
Jul 23 2019 09:33:30:464 | ...package.json | at require (internal/modules/cjs/helpers.js:22:18)
Jul 23 2019 09:33:30:464 | ...package.json | at Object.<anonymous> (/tmp/6c75a54f/node_modules/grpc/src/grpc_extension.js:32:13)
Jul 23 2019 09:33:30:464 | ...package.json | at Module._compile (internal/modules/cjs/loader.js:701:30)
Jul 23 2019 09:33:30:464 | ...package.json | at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10)
Jul 23 2019 09:33:30:464 | ...package.json | at Module.load (internal/modules/cjs/loader.js:600:32) type: 'Error', '$error': '$error' }

I have tried with both the specified version of the asset relocator, and the latest version

@Pushplaybang I don't think it's worth tracking these individually -- the latest version of these plugins have better static analysis capability (which should fix cases like iconv).
However, only versions 0.5.x are compatible with Next.js at the moment -- we're working on integrating the latest version in this PR.

@Timer great, having applied the fix mentioned  with the asset relocator is what I've been using for some time, though I'm still blocked on deployment having upgraded to v9.  As you;ve  closed one issue, and marked another comment as spam, could you please advise:

is there a current workaround,
should I attempt to use this branch
should I open another separate issue regarding iconv?

just to reiterate, I was able to deploy prior to v9.  Please tell me how I can either assist, or get help with this issue.

Hello. Any progress on this?

No progress to report. It has been prioritized to be done soon, however.

The latest Next.js canary should now work with Firebase when deployed to Now with the @now/next@canary builder! 😄

I'm still getting the error
Module not found: Can't resolve 'request' in '/tmp/e991867/node_modules/@firebase/database/dist'

on @now/next@canary with "firebase": "^6.2.4"

@antonmoiseev you have not provided any information for us to help diagnose this issue. We have integration tests ensuring firebase works, so we need to see your specific setup. Please open a new issue with a reproduction.


[bug] Identity - discord and teamspeak

Hi, I got a problem when I join the discord.
I link a screen shot step by step for explain my issue.

https://gyazo.com/3a167383d1d3166a2c97bdfd14029621

https://gyazo.com/8225564347733525acdd694e92ba3b04

https://gyazo.com/4e7c5aa19fd3d804652cdef13b4f6473

impossible for me to join the discord server.

This is seat-groups, regarding seat-connector related issues you should contact the author of that package.

Oh good, sorry. I delete.


[Release-1.28] - Etcd load-balancer on control-plane-only server may select removed etcd cluster member as default server

Backport fix for Etcd load-balancer on control-plane-only server may select removed etcd cluster member as default server

#9882

Validated on Version:
-$ k3s version v1.29.3+k3s-06b64449 (06b64449)

Environment Details
Infrastructure
Cloud EC2 instance
Node(s) CPU architecture, OS, and Version:
Ubuntu
AMD64
Cluster Configuration:
Split role:

3 cp only
3 workers
3 etcd only

Steps to validate the fix

start k3s on split role
get logs on cp only
Validate that the address of the server specified in the --server address is always reported as the server address in the etcd load-balancer log message

Reproduction Issue:

Validation Results:

 $ cat /etc/rancher/k3s/config.yaml
write-kubeconfig-mode: "0644"
tls-san:
  - <IP_ADDRESS>
server: https://<IP_ADDRESS>:6443

ip-172-31-14-50.us-east-2.compute.internal    Ready    etcd                   5m59s   v1.28.9-rc1+k3s1   <IP_ADDRESS>    <IP_ADDRESS>

~$ sudo journalctl --no-pager -u k3s | grep "Adding" -A2
Apr 16 23:36:51 ip-172-31-4-54 k3s[2052]: time="2024-04-16T23:36:51Z" level=info msg="Adding server to load balancer k3s-etcd-server-load-balancer: <IP_ADDRESS>:2379"

Apr 16 23:36:51 ip-172-31-4-54 k3s[2052]: time="2024-04-16T23:36:51Z" level=info msg="Running load balancer k3s-etcd-server-load-balancer <IP_ADDRESS>:2379 -> [<IP_ADDRESS>:2379] [default: <IP_ADDRESS>:2379]"


add build instructions and missing init flags

It'd be nice to mention this in README.

Mentioned! Thanks for the feedback.


AICamera caffe2 detentron andriod

andriod project：
https://github.com/caffe2/AICamera
model：
https://github.com/caffe2/models/tree/master/detectron/e2e_faster_rcnn_R-50-C4_1x
but use the model from the AICamera-Style-Transfer is  ok
https://github.com/caffe2/AICamera-Style-Transfer
loadToNetDef(mgr, &_initNet,   "init_net.pb");
loadToNetDef(mgr, &_predictNet,"predict_net.pb");
log as fllows:
03-08 21:13:50.756 23861-23907/facebook.f8demo E/F8DEMO: start load neural network.
03-08 21:13:50.757 23861-23907/facebook.f8demo E/F8DEMO: Attempting to load protobuf netdefs...
03-08 21:13:50.757 23861-23907/facebook.f8demo E/F8DEMO: Couldn't parse net from data.
03-08 21:13:50.757 23861-23907/facebook.f8demo E/F8DEMO: Couldn't parse net from data.
03-08 21:13:50.757 23861-23907/facebook.f8demo E/F8DEMO: success load protobuf netdefs done.
03-08 21:13:50.757 23861-23907/facebook.f8demo E/F8DEMO: Instantiating predictor...

How did you install Caffe2?
Can you post your cmake output? I'm looking for all of the output from the cmake command; if you used conda-build to build Caffe2 then the cmake command is called as part of the conda/no_cuda/build.sh script.
Did you pass any special flags such as -DCAFFE2_CUSTOM_PROTOC_EXECUTABLE? Building Caffe2 for android takes special instructions with protobuf.


Add support for large integers

erlang / elixir support integers of arbitrary size, however the erlang nif does not support this (if i read the docs correctly), I used the term to binary to extract this data.
So couple of questions:

do we want to support this in Rustler?
do we want to use num-bigint for this or another libary?
should it be behind a feature flag?
is the term to binary / binary to term functions the way to do this?

edit: maybe i can make this an external library to support this?

struct BigInt(num_bigint::Bigint)

// ... implement deref and deref_mut

// ... implement Decoder and Encoder

Thanks @thomas9911. Using the binary representation of a term is nice, do you know how stable that is? I'd think that the representation does not change ever, but is that guaranteed?

do we want to support this in Rustler?

I am not sure if the rustler crate is the right spot, maybe a rustler_bigint crate would expose this functionality more clearly and separate core erl_nif handling from extra features such as this. But if we add an extra crate, we need to add a newtype BigInt (as you also stated in the description). The ergonomics would be slightly worse, but retrieving the BigInt from the newtype is also trivial, so this might be ok. What do you think?

do we want to use num-bigint for this or another libary?

I haven't used a bigint library yet with Rust, but num-bigint seems to be the most popular option, so this should be a good choice.

should it be behind a feature flag?

That depends if we want this to be in a separate crate or not. If we don't use a separate crate, I think a feature flag would be good (to avoid pulling in num-bigint for users that don't actually need it).

is the term to binary / binary to term functions the way to do this?

That depends on the stability of the in-memory term representation. I guess that the external term format provides more stability guarantees, but if we use that, we lose the nice property of simply passing in a term, which can then be decoded. Maybe others in @rusterlium/core have more insight into this?

I'd think that the representation does not change ever, but is that guaranteed?
After a google search I could find docs of this of erts version 5.6.3 (we are now on 13.0) and it looks quite the same (or at least backwards compatible) and exactly the same for the types i used in this pull request. So indeed no guarantees, but strong suspicion.

I am not sure if the rustler crate is the right spot, maybe a rustler_bigint crate would expose this functionality more clearly

After creating this pull request I think indeed it is probably better to implement this in a seperate crate.

That depends on the stability of the in-memory term representation.

I looked at the nif and this uses exactly the external term format in these functions.

That sounds reasonable. So lets create rustler_bigint as part of the rustler repository with a newtype and use your approach with reading the binary directly?

Sounds good, shall i create a new folder ect. in this pull request, or do you want to do it?

Sounds good, shall i create a new folder ect. in this pull request, or do you want to do it?

You can create a new crate in this pull request.

Moved everything to rustler_bigint crate and added extra tests and documentation

This is amazing, I'm so happy this in! Thanks!
There is also a discussion here that touches on the topic above as well https://elixirforum.com/t/acceptance-of-erlangs-term-to-binary-and-vice-versa-in-elixir/11034


GH-43258: [C++][Flight] Use a Base CRTP type for the types used in RPC calls

Rationale for this change
Flight should eventually be buildable without a specific protobuf version. As such, all the protobuf types are wrapped in hand-written classes. Uniformity of the interface is not enforced even though it's desirable. Extending the interface requires adding functions to every struct. A common base class can mitigates risks and reduce the amount of hand-written code.
What changes are included in this PR?

Definition of a BaseType<> template (a CRTP)
Add constructors that aren't implicitly defined anymore
Having a default value for some fields that would be undefined values otherwise
Leverage this structure to add SerializeToBuffer to all the types
~30KiB in binary size reduction

Are these changes tested?
By existing tests.

GitHub Issue: #43258

bloaty report:
$ ninja libarrow_flight.a && bloaty -d symbols -C full -n 0 ./release/libarrow_flight.a -- BEFORE-libarrow_flight.a
[17/17] Linking CXX static library release/libarrow_flight.a
    FILE SIZE        VM SIZE
 --------------  --------------
  -1.0% -28.1Ki  [ = ]       0    [AR Non-ELF Member File]
  -1.0% -28.1Ki  [ = ]       0    TOTAL

It's small compared to the gigantic arrow library, but any reduction is good IMO.

I think I broke the MSVC build by merging this. I will try fixing it here -> https://github.com/apache/arrow/pull/43330


online book and 2nd edition do not match

Although the online book says that it is the 2nd edition, it isn't. It is, I guess, "second edition plus". While this might be obvious to those working on the book, it is not to the new comer. Best I can tell, there have been a lot of changes since the printed "second edition", at least the one I have. I am just suggesting that some text or warning be added to the initial web page linked below that makes us aware that the online book has changed since the hard-copy second edition was published.
Thanks for considering this suggestion.

https://git-scm.com/book
Problem

Operating system and browser

Steps to reproduce

Other details

Yeah, I'd agree that text could be updated. There are indeed a lot of changes: https://github.com/progit/progit2/compare/2.0.0...main (though I'm not 100% sure that the 2.0.0 tag represents what went to press).


Registering problems

Hej,
I have same problem as was writen 7 days ago by supermax69.
Everything looks good, WinPCap getting packages from Tera.
Casual meter is working and connecting to server properly
"2016-01-04 08:38:49,351 [13] INFO  CasualMeter.ShellViewModel - Connected to server Fraya."
but doesnt register or show any dmg at all, is there any log of registered dmg in application?
I have win 8.1 x64
and every softweare is updated.

Sorry for question.
It looks like my WinPCap doesn't catch outgoing packets from my computer.
Trying to fix the problem but with no luck


BAEL-7030

retest this please

The method name should be separated with an underscore given, when, and then.

done


Rename the "Delete" option in the FileSystem dock to "Move to Trash"

It actually moves files to the system trash instead of removing them completely.

It deletes files completely for me. KDE Plasma 5.19.4.

@dalexeev Do you get any errors in the terminal when doing so? (Make sure to start the editor from a terminal.)

@Calinou No errors.

I am not sure on Linux that it move the files to the trash.  It mostly amounts to checking some directories and moving files around.
The WINAPI way to do it is to call SHFileOperationA with a filled SHFILEOPSTRUCTA that specifies a deletion with an "FOF_ALLOWUNDO" flag (Documentation Here)
I'm not sure how to do this in MacOS. If somebody more familiar with MacOS can chime in, that'd be helpful.
I also think it would be helpful to allow the programmer to specify if a deletion should just move to trash or if it should be permanent.
Most of my development is on Linux, so I can work on the Linux part of it, if somebody more familiar with Windows or Mac can pick those platforms up.

@dalexeev Can you double check on your distro? The code does use OS::move_to_trash: https://github.com/godotengine/godot/blob/fc70f986b9a324fd0bf1707f2df7bfeabb2bb4d1/editor/dependency_editor.cpp#L499-L506
And it's implemented on Linux: https://github.com/godotengine/godot/blob/fc70f986b9a324fd0bf1707f2df7bfeabb2bb4d1/platform/linuxbsd/os_linuxbsd.cpp#L305
It might be that it doesn't actually work with the trash used in your distro/DE or lack thereof, but it shouldn't actually delete the files, they should end up either in the supported trash location, or in ~/.local/share/Trash/files/.

Not dalexeev, but I can confirm I deleted two files in Godot today and they aren't in my trash.
Linux Manjaro, KDE Plasma 5.19.5.

It might be that it doesn't actually work with the trash used in your distro/DE or lack thereof, but it shouldn't actually delete the files, they should end up either in the supported trash location, or in ~/.local/share/Trash/files/.

Yes this is true. I don't see the file in the trash can, but it is in the directory.
$ ls ~/.local/share/Trash/files/ | grep test_delete
test_delete.gd

Operating System: Kubuntu 20.10
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2

Tested on KDE 5.20.3 on Mageia 8 and I can confirm the issue too.
It looks like we put things in the correct Trash folder, but we don't populate the .trashinfo metadata:

This should likely be discussed/debugged further in #42840.

@dalexeev: Bingo, the same is true for me - ls ~/.local/share/Trash/files/ reveals the files deleted from Godot.

@dalexeev @groud Can you double check on your distro? The code does use OS::move_to_trash:

Ah yes, I have this path too. I guess this is implemented on my distro but I never use it.
The renaming makes sense then I guess.

I edited #42840 for clarity about this issue.
Let's merge this PR as it's correct, even if there's a related bug on Linux.

Thanks!

Cherry-picked for 3.2.4.

Note that this PR was reverted by https://github.com/godotengine/godot/pull/49519.


Fix Matomo tracking - hard coding URL and CSP policy

Fix hardcoding of Matomo URL into code and remove trailing slash
Fix
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Check Matomo snippet is correct in header
Checklist:

[X] My changes do not introduce any new linting errors
[X] I have performed a self-review of my own code
[N/A] I have commented my code, particularly in hard-to-understand areas
[N/A] I have made corresponding changes to the documentation and versioning
[N/A] My changes generate no new warnings
[N/A] I have added tests that prove my fix is effective or that my feature works
[N/A] New and existing unit tests pass locally with my changes
[X] I have rebased onto master and there are no code conflicts
[N/A ] I have checked deployments are working in all environments
[N/A ] I have updated the architecture diagrams as per Contribute.md

@bertrandmc - there's more things I need to change / bring over from our fork.  We were testing Matomo before Christmas and the CSP policies are set incorrectly.
Matomo tracking only works for non Javascript users.  If you go to https://www.prove-eligibility-foreign-government.service.gov.uk/thailand/uk-passport and open developer tools you'll see the error.

@bertrandmc - there's more things I need to change / bring over from our fork.  We were testing Matomo before Christmas and the CSP policies are set incorrectly.
Matomo tracking only works for non Javascript users.  If you go to https://www.prove-eligibility-foreign-government.service.gov.uk/thailand/uk-passport and open developer tools you'll see the error.

Sure thing @trevorrea. Please feel free to push changes to this PR and I'll review again when ready, just let me know.
I've added the "do not merge" label for the time being.

Sure thing @trevorrea. Please feel free to push changes to this PR and I'll review again when ready, just let me know.
I've added the "do not merge" label for the time being.

@bertrandmc - that's the CSP changes in now. To test set:-
        - name: MATOMO_URL
          value: https://web-analytics.fco.gov.uk
        - name: MATOMO_ID
          value: "37"

It won't track anything but you should see whether the CSP error is logged.

@bertrandmc - that's the CSP changes in now. To test set:-
        - name: MATOMO_URL
          value: https://web-analytics.fco.gov.uk
        - name: MATOMO_ID
          value: "37"

It won't track anything but you should see whether the CSP error is logged.

@jenbutongit could you please review the Blankie plugin changes, I am not too familiar with it. Thanks.

@jenbutongit could you please review the Blankie plugin changes, I am not too familiar with it. Thanks.

@trevorrea question about the script https://web-analytics.fco.gov.uk/piwik/piwik.js.
Is somehting custom for you guys or just a generic Matomo tracking script?
I am considering reviewing how this is implemented, TBH I don't like the unsafe-inline directive, the injection of an unkown script is an attach surface, if this is a generic matomo script then we can host it on the app or load from matomo and use the Hash directive instead of unsafe-inline?
ping @XGovFormBuilder/maintainers

@trevorrea question about the script https://web-analytics.fco.gov.uk/piwik/piwik.js.
Is somehting custom for you guys or just a generic Matomo tracking script?
I am considering reviewing how this is implemented, TBH I don't like the unsafe-inline directive, the injection of an unkown script is an attach surface, if this is a generic matomo script then we can host it on the app or load from matomo and use the Hash directive instead of unsafe-inline?
ping @XGovFormBuilder/maintainers

@bertrandmc - it's just the generic one but it changes occasionally so now you've now given yourself a maintenance task of checking the hash / updating the bundled version every time Matomo is upgraded.
See https://github.com/matomo-org/matomo/commits/4.x-dev/piwik.js for the history of it.
The Matomo site has an FAQ about how to host it yourself rather than loading it from the Matomo instance
https://matomo.org/faq/general/faq_20904/
or as you suggest using Hash would be much less work.  Although that page you linked says Hash is not supported by IE so probably this doesn't work for our purposes as not everybody is using Edge.

@bertrandmc - it's just the generic one but it changes occasionally so now you've now given yourself a maintenance task of checking the hash / updating the bundled version every time Matomo is upgraded.
See https://github.com/matomo-org/matomo/commits/4.x-dev/piwik.js for the history of it.
The Matomo site has an FAQ about how to host it yourself rather than loading it from the Matomo instance
https://matomo.org/faq/general/faq_20904/
or as you suggest using Hash would be much less work.  Although that page you linked says Hash is not supported by IE so probably this doesn't work for our purposes as not everybody is using Edge.

I think I heard someone (@jenbutongit was it you?) say the plan was to move to Google Analytics, in which case is a long term solution needed here?

I think I heard someone (@jenbutongit was it you?) say the plan was to move to Google Analytics, in which case is a long term solution needed here?

Yeah there is a long term plan to move to Google Analytics. It's been the long term plan for a long time.

Yeah there is a long term plan to move to Google Analytics. It's been the long term plan for a long time.

I think I heard someone (@jenbutongit was it you?) say the plan was to move to Google Analytics, in which case is a long term solution needed here?

possibly..? HO would like to use GA I believe, although we should support both depending on what departments use

I think I heard someone (@jenbutongit was it you?) say the plan was to move to Google Analytics, in which case is a long term solution needed here?

possibly..? HO would like to use GA I believe, although we should support both depending on what departments use

Loads of questions on this then, I'll raise a ticket for further discussion.
@trevorrea if you could please just address Jen's comments and I'll approve the PR, it is improving the actual implementation anyway. Thanks

Loads of questions on this then, I'll raise a ticket for further discussion.
@trevorrea if you could please just address Jen's comments and I'll approve the PR, it is improving the actual implementation anyway. Thanks

@bertrandmc  - I don't have the dev environment set up.  I'm only moonlighting as a developer.  If yourself or Jen can see what's wrong and easily fix it then fire ahead.  Or copy the changes to a branch in your repo and then run the lint checks and tests.  It'll be much quicker than if I try to do it.

@bertrandmc  - I don't have the dev environment set up.  I'm only moonlighting as a developer.  If yourself or Jen can see what's wrong and easily fix it then fire ahead.  Or copy the changes to a branch in your repo and then run the lint checks and tests.  It'll be much quicker than if I try to do it.

No problem, let me start a new branch and pull your changes, apologies for being blocked by these checks, we are evaluating changes to facilitate OSS collaboration without need for permissions etc, also thanks for the PR.

No problem, let me start a new branch and pull your changes, apologies for being blocked by these checks, we are evaluating changes to facilitate OSS collaboration without need for permissions etc, also thanks for the PR.


Bot not starting

/home/vHackXTBot# ./main.py
Traceback (most recent call last):
File "./main.py", line 146, in
r = run()
File "./main.py", line 43, in init
self.b = Botnet(self.player)
File "/home/vHackXTBot/botnet.py", line 21, in init
self._initbot()
File "/home/vHackXTBot/botnet.py", line 34, in _initbot
bot = Bot(i['bID'], i['bLVL'], i['bPRICE'], self.username, self.password, self.uhash)
KeyError: 'bID'

you are connected on discord ?

i closed, but i disabled functionality


Fix grammar error

Start using QGIS ... reads better than
Started using QGIS ...
The other two highlights start with:
Shape the future ...
Find training ...

Good catch! Thanks...