Extend Server json struct

Add more value in Server struct

Oups, sorry ^^
Removing values from Server. But expend ServerConnectionInfo.

@AnthoDingo any update on the questions?

There are not references in the server query manual to these values. Even the latest server download does not mention these.
The Query documentation isn't really that great. But it is easily testable via the telnet console.
If you need some reference output, I could provide that:

	```
		virtualserver_unique_identifier=redacted
		virtualserver_name=redacted
		virtualserver_welcomemessage
		virtualserver_platform=Linux
		virtualserver_version=3.9.1\s[Build:\s1562073443]
		virtualserver_maxclients=510
		virtualserver_password
		virtualserver_clientsonline=4
		virtualserver_channelsonline=54
		virtualserver_created=1360128690
		virtualserver_uptime=6679488
		virtualserver_codec_encryption_mode=2
		virtualserver_hostmessage
		virtualserver_hostmessage_mode=1
		virtualserver_filebase=files\/virtualserver_1
		virtualserver_default_server_group=8
		virtualserver_default_channel_group=8
		virtualserver_flag_password=0
		virtualserver_default_channel_admin_group=5
		virtualserver_max_download_total_bandwidth=8388608
		virtualserver_max_upload_total_bandwidth=8388608
		virtualserver_hostbanner_url=redacted
		virtualserver_hostbanner_gfx_url=redacted
		virtualserver_hostbanner_gfx_interval=0
		virtualserver_complain_autoban_count=7
		virtualserver_complain_autoban_time=1200
		virtualserver_complain_remove_time=7200
		virtualserver_min_clients_in_channel_before_forced_silence=100
		virtualserver_priority_speaker_dimm_modificator=-15.0000
		virtualserver_id=1
		virtualserver_antiflood_points_tick_reduce=5
		virtualserver_antiflood_points_needed_command_block=150
		virtualserver_antiflood_points_needed_ip_block=500
		virtualserver_client_connections=2524
		virtualserver_query_client_connections=82753
		virtualserver_hostbutton_tooltip=redacted
		virtualserver_hostbutton_url=redacted
		virtualserver_hostbutton_gfx_url=redacted
		virtualserver_queryclientsonline=4
		virtualserver_download_quota=107374182400
		virtualserver_upload_quota=107374182400
		virtualserver_month_bytes_downloaded=1047318809
		virtualserver_month_bytes_uploaded=347344634
		virtualserver_total_bytes_downloaded=17282436491
		virtualserver_total_bytes_uploaded=8719954284
		virtualserver_port=9987
		virtualserver_autostart=1
		virtualserver_machine_id
		virtualserver_needed_identity_security_level=8
		virtualserver_log_client=1
		virtualserver_log_query=0
		virtualserver_log_channel=1
		virtualserver_log_permissions=1
		virtualserver_log_server=1
		virtualserver_log_filetransfer=1
		virtualserver_min_client_version=1560850141
		virtualserver_name_phonetic=redacted
		virtualserver_icon_id=1674898333
		virtualserver_reserved_slots=2
		virtualserver_total_packetloss_speech=0.0000
		virtualserver_total_packetloss_keepalive=0.0000
		virtualserver_total_packetloss_control=0.0000
		virtualserver_total_packetloss_total=0.0000
		virtualserver_total_ping=0.0000
		virtualserver_ip=<IP_ADDRESS>,::
		virtualserver_weblist_enabled=1
		virtualserver_ask_for_privilegekey=0
		virtualserver_hostbanner_mode=2
		virtualserver_channel_temp_delete_delay_default=5
		virtualserver_min_android_version=1537790492
		virtualserver_min_ios_version=1559144369
		virtualserver_nickname
		virtualserver_antiflood_points_needed_plugin_block=0
		virtualserver_status=online
		connection_filetransfer_bandwidth_sent=0
		connection_filetransfer_bandwidth_received=0
		connection_filetransfer_bytes_sent_total=1118871906
		connection_filetransfer_bytes_received_total=383216474
		connection_packets_sent_speech=320432180
		connection_bytes_sent_speech=43805818511
		connection_packets_received_speech=174885295
		connection_bytes_received_speech=24127808273
		connection_packets_sent_keepalive=55230363
		connection_bytes_sent_keepalive=2264444883
		connection_packets_received_keepalive=55149547
		connection_bytes_received_keepalive=2316390993
		connection_packets_sent_control=2376088
		connection_bytes_sent_control=525691022
		connection_packets_received_control=2376138
		connection_bytes_received_control=227044870
		connection_packets_sent_total=378038631
		connection_bytes_sent_total=46595954416
		connection_packets_received_total=232410980
		connection_bytes_received_total=26671244136
		connection_bandwidth_sent_last_second_total=0
		connection_bandwidth_sent_last_minute_total=0
		connection_bandwidth_received_last_second_total=0
		connection_bandwidth_received_last_minute_total=0
	```

There are not references in the server query manual to these values. Even the latest server download does not mention these.
The Query documentation isn't really that great. But it is easily testable via the telnet console.
If you need some reference output, I could provide that:
ServerInfo result

Thanks that's really useful, just need to get the feedback addressed so we can get this merged.
If anyone wants to pick this up on a new PR, that's cool.

If anyone wants to pick this up on a new PR, that's cool.
Sweet I will see what I can come up with tonight :)

Committed via https://github.com/multiplay/go-ts3/pull/28


Remove Context from API

Expected Behavior
Context should be handled separately from domain objects. As per discussion in #453
Actual Behavior
Context is a property of request classes.
Steps to Reproduce the Problem
See the Request classes.
Release Note

RELEASE NOTE:  REMOVED Context from request and response objects.

@xiazuojie Please, comment on this issue so I can assign it to you.

I agree


⚠ SceneTime has degraded performance

In 10a681a, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1846 ms

Resolved: SceneTime performance has improved in e783434 after 8 minutes.


Enable Checkstyle properly

It is necessary to use Checkstyle properly in the workflow

It is necessary to explain to any contribute to use:
gradle checkstyleMain


refactor: unify oomcli table output

This pr

[x] implement get meta revision
[x] Unify output format handling
[x] Improve get meta subcommand error handling
[x] Simplify get meta yaml serialization

it would be better if you could reorganize commits to make review easier 😂


make self signed ca cert only when odf is enabled

Resolved with #24 as an alternative option.
Thanks for the contribution and raising the issue!


Allow transferring of pool ownership

Add a new method to transfer shares of one pool to an other principal

that's a token now


Clipped features in rotated view

Describe the bug
In a rotated view, features are clipped unnecessarily. This leads to features missing on the map, where they should actually be drawn. This only seems to affect non-square views.
To Reproduce
Steps to reproduce the behavior:

Go to the cluster example (Is there a way to fix 'latest' to '9.1.0'?)
Zoom in such that the entire view is filled with features
Rotate the view using alt+shift
Starting at a specific rotation (in my own case 59 degrees, but presumably dependent on the aspect ratio), the features can seen to be clipped

Expected behavior
The features should not disappear upon rotating.
Versions
As far as I can tell, this bug was introduced in version 9.1.0. Version 9.0.0 does seem to work as expected.
Screengrab:

See #15795

Ah I did look in open issues but forgot to search closed issues. Good to see it has been picked up.


coq_nvim - cannot import name 'batched' from 'std2.itertools'

Plugin affected: coq_nvim
Nixpkgs channel: unstable
Home-manager version: unstable
Description
this seems very similar to https://github.com/nix-community/nixvim/issues/400, upon launching nvim I get this
cannot import name 'batched' from 'std2.itertools' (/nix/store/440s2ivl3rk6kxxac5sdkgsww6px2cg1-python3-
3.11.5-env/lib/python3.11/site-packages/std2/itertools.py)

Please update dependencies using :COQdeps
-
-
Dependencies will be installed privately inside `/home/jacek/.cache/coq_nvim/vars`
`rm -rf gb8cpdfpg9y1z5bmcai09f25jm9wllxp-vimplugin-coq_nvim-2023-10-07` will cleanly remove everything
Press ENTER or type command to continue

and running :COQdeps gives me this
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/nix/store/gb8cpdfpg9y1z5bmcai09f25jm9wllxp-vimplugin-coq_nvim-2023-10-07/coq/__main__.py", line
 85, in <module>
    assert not _IN_VENV
AssertionError

[Process exited 1]

I did exactly what you told pupbrained to do in that issue, just updated my flake, ran that python binary and tried importing batched there with this result:
~/niksos on  master [!+?] took 34s ❯ /nix/store/n8rjv7v0bw3yxbdpvmjnwwwh8h2swzd6-neovim-4d757bb/bin/nvim-python3
Python 3.11.5 (main, Aug 24 2023, 12:23:19) [GCC 12.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import std2
>>> import std2.itertools
>>> import std2.itertools.batched
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'std2.itertools.batched'; 'std2.itertools' is not a package
>>> import std2.itertools.batche
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'std2.itertools.batche'; 'std2.itertools' is not a package
>>> import std2.itertools.batch
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'std2.itertools.batch'; 'std2.itertools' is not a package
>>> from std2.itertools import batched
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'batched' from 'std2.itertools' (/nix/store/440s2ivl3rk6kxxac5sdkgsww6px2cg1-python3-3.11.5-env/lib/python3.11/site-packages/std2/itertools.py)
>>>

I also checked and ~/.local/share/nvim doesn't have any coq related directories and I already tried removing the entire directory
Config
            programs.nixvim = {
                enable = true;
                package = pkgs.neovim-nightly;
                enableMan = true;
                #colorscheme = "catppuccin";
                #colorschemes.catppuccin = {
                #    flavour = "mocha";
                #    transparentBackground = true;
                #};

                options = {
                    number = true;
                    relativenumber = true;
                    autoread = true;
                    so = 7;
                    cmdheight = 1;
                    ignorecase = true;
                    smartcase = true;
                    showmatch = true;
                    timeoutlen = 500;
                    encoding = "utf8";
                    smarttab = true;
                    shiftwidth = 4;
                    tabstop = 4;
                    expandtab = true;
                    linebreak = true;
                    smartindent = true;
                    updatetime = 300;
                    hidden = true;
                    background = "dark";
                    mousemoveevent = true;
                };

                globals = {
                    mapLeader = " ";
                    mapLocalLeader = " ";
                };

                plugins = {
                    airline = {
                        enable = true;
                        powerline = true;
                        #theme = "catppuccin";
                    };
                    fugitive.enable = true;
                    treesitter = {
                        enable = true;
                        ensureInstalled = [
                            "lua"
                            "rust"
                            "markdown"
                            "markdown-inline"
                            "python"
                            "cmake"
                            "cpp"
                            "c"
                        ];
                        folding = false;
                        indent = true;
                        nixvimInjections = true;
                        incrementalSelection.enable = true;
                    };
                    coq-nvim = {
                        enable = true;
                        autoStart = "shut-up";
                        installArtifacts = true;
                        recommendedKeymaps = true;
                    };
                    chadtree = {
                        enable = true;
                        keymap.openFileFolder.tertiary = [ "<leader>t" "<middlemouse>" ];
                    };
                    toggleterm = {
                        enable = true;
                        direction = "float";
                        openMapping = "<C-\\>";
                        shadeTerminals = true;
                        shadingFactor = 2;
                        size = 10;
                    };
                    # TODO laytan/cloak.nvim
                    gitsigns = {
                        enable = true;
                        currentLineBlame = true;
                        numhl = true;
                        signcolumn = true;
                        wordDiff = true;
                    };
                    lsp = {
                        enable = true;
                        servers = {
                            rust-analyzer.enable = true;
                            lua-ls.enable = true;
                            clangd.enable = true;
                            nil_ls.enable = true;
                            bashls.enable = true;
                        };
                        #onAttach = ''
                        #    vim.api.nvim_buf_set_option(bufnr, 'omnifunc', 'v:lua.vim.lsp.omnifunc')

                        #    local bufopts = { noremap = true, silent = true, buffer = bufnr }
                        #    vim.keymap.set('n', '<space>wl', function()
                        #        print(vim.inspect(vim.lsp.buf.list_workspace_folders()))
                        #    end, bufopts)
                        #    vim.keymap.set('n', '<C-f>', function() vim.lsp.buf.format { async = true } end, bufopts)
                        #'';
                        keymaps = {
                            lspBuf = {
                                gD = "declaration";
                                gd = "definition";
                                K = "hover";
                                gi = "implementation";
                                "<C-k>" = "signature_help";
                                "<leader>wa" = "add_workspace_folder";
                                "<leader>wr" = "remove_workspace_folder";
                                "<leader>wl" = "list_workspace_folders";
                                "<leader>D" = "type_definition";
                                "<leader>r" = "rename";
                                "<leader>a" = "code_action";
                                gr = "references";
                                "<C-f>" = "format";
                            };
                            diagnostic = {
                                "<leader>e" = "open_float";
                                "<leader>j" = "goto_prev";
                                "<leader>k" = "goto_next";
                                "<leader>q" = "setloclist";
                            };
                            # TODO maybe change
                            silent = false;
                        };
                    };
                    rust-tools = {
                        enable = true;
                        crateGraph = {
                            enabledGraphvizBackends = [ "png" "svg" ];
                            backend = "x11";
                        };
                        inlayHints = {
                            auto = true;
                            onlyCurrentLine = true;
                            showParameterHints = true;
                        };
                    };
                    leap.enable = true;
                    fidget.enable = true;
                    telescope = {
                        enable = true;
                        keymaps = {
                            "<leader>ff" = "find_files";
                            "<leader>fg" = "live_grep";
                            "<leader>fb" = "buffers";
                            "<leader>fh" = "help_tags";
                        };
                        # TODO maybe change
                        keymapsSilent = false;
                    };
                    comment-nvim.enable = true;
                    crates-nvim.enable = true;
                    harpoon = {
                        enable = true;
                        enableTelescope = true;
                        keymapsSilent = false;
                    };
                };
            };

Yes, this is "my fault".
I did not adapt the patch we apply to the coq_nvim source recently.
As the code has changed and the plugin was updated, the patch no longer has effect.
I have just opened a PR to fix that: https://github.com/NixOS/nixpkgs/pull/266859

And the python dependencies had not been updated for a while. This is, I think, the cause of your bug.

that was really quick, thank you! hope it gets merged soon :-)

Actually, I need to adapt the patch a bit more because the plugin author has changed the logic a bit...

The PR has been merged.
We now have to wait for it to land on nixos-unstable.

I could never find this, how quick do commits from master land in unstable?

It's usually a few days: https://status.nixos.org/

@jacekpoz can you update and retry ?
It should be fixed...

sorry for the long wait, I needed to fix my flake…
everything works fine here!

Great ! Closing then.


Add units symbols in converter

A nice enhancement would be to add standard unit symbols alongside the full name of the unit in the converter.
A good start would be to simply add it between parenthesis or brackets in the string describing the units.

Thanks for the idea. I have added the symbols and abbreviations corresponding to the units in the new update.
Added as of #61


From private repo

@huypub : Thanks for your contribution! The author(s) have been notified to review your proposed change. @daniellefoto


fixes FireAndForget to execute FF call

I think there was a small typo in line 91 of socket.go

Yep, it's a bug. Thanks for fixing it. 👍

My pleasure
On Sun, Apr 19, 2020 at 8:19 AM Jeffsky<EMAIL_ADDRESS>wrote:

Yep, it's a bug. Thanks for fixing it. 👍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rsocket/rsocket-go/pull/48#issuecomment-616021179,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW37NJ46FFTSQ2ZBXAQXA3RNJYFXANCNFSM4MK5BIWQ
.


trigger build as s390 package missing

trigger build as s390 dependency missing for opentelemetry-python-feedstock

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:18: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: clone/recipe/meta.yaml:31: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: clone/recipe/meta.yaml:44: http_url: http://opentracing.io is not https
ERROR: clone/recipe/meta.yaml:44: http_url: http://opentracing.io/documentation is not https
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:18: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: clone/recipe/meta.yaml:31: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: clone/recipe/meta.yaml:44: http_url: http://opentracing.io/documentation is not https
ERROR: clone/recipe/meta.yaml:44: http_url: http://opentracing.io is not https
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:18: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: clone/recipe/meta.yaml:31: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: clone/recipe/meta.yaml:44: http_url: http://opentracing.io is not https
ERROR: clone/recipe/meta.yaml:44: http_url: http://opentracing.io/documentation is not https
Errors were found


Hard-coded strings should be moved to nls

There are three places where English is hard-coded:  when the "Show results within x mins drive" is switched between "drive" and "walk", the app will only work in English.
this.sliderMessage.innerHTML = this.sliderMessage.innerHTML.replace("walk", "drive");
        :        :        :
this.sliderMessage.innerHTML = this.sliderMessage.innerHTML.replace("drive", "walk");

These should be moved into the nls.

@lindsayking We will provide this fix in next release.

LT- Verified that I can see the change has been made in the localizedstring.js (all occurrences)
Lt - I still need to holistically test this worked

Verified Holistically


Add heads with a command

Hello,
Could you add a system (it's important I think), where we can add heads that are not in the plugin, with a command.
For example : I have a christmas head, and I type /heads addhead !
Thanks ! :)

I don't know if it's possible, it would depend on the data of the head...
I'm already planning on making it so you can save your current skin as a permanent head, which would allow you to create custom heads more easily. I'm not sure if I can retrieve the data from a player head though... I'll look into it :smile:

Great ! :) It's a good feature. ;)

I will begin doing that once I have an in-game head creator and a categories system 😛

:D. Yep. :)

Alright, categories system is out in v1.4. This is my next big goal, although before I can get to it I have other projects to work on.

Perfect.

Any news ? :(

Sorry, I keep getting behind on projects! I will get to this, I promise.

Okay. :) Thanks ahain ! :)

How does this sound?
/decoheadsadmin add hand <name>

Adds the head you are currently holding under the given name

/decoheadsadmin add self <name>

Adds your current skin as a head under the given name

I'm not entirely sure if the self one will be easily possible, but it should be.

Added in e12dfc46ec4cbf43b0723c25ef33b7829c68d51a.


Unable to log in as root (docker-compose environment: ARANGO_ROOT_PASSWORD)

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 2.8
[ ] 3.0
[x] 3.1
[ ] 3.2 Beta1
[ ] self-compiled devel branch

On this operating system:

[ ] DCOS on

[ ] AWS
[ ] Azure
[ ] own infrastructure

[ ] Linux

[ ] Debian .deb
[ ] Ubuntu .deb
[ ] SUSE   .rpm
[ ] RedHat .rpm
[ ] Fedora .rpm
[ ] Gentoo
[x] docker - official docker library
[ ] other:

[ ] Windows, version:
[ ] MacOS, version:

this is a web interface-related issue:
I'm using the web interface with this browser:     running on this OS:

[x] authentication is enabled?
[ ] using the cluster?
[ ] _system database?

These are the steps to reproduce:
When running arangodb remotely behind a reverse proxy using docker-compose and setting the ARANGO_ROOT_PASSWORD environment variable, I'm unable to log in as root.  A "Login Failed!" message is returned when I try to log into the web interface.
docker-compose.yml:
version: '2'
services:
nginx-proxy:
image: jwilder/nginx-proxy
restart: always
ports:
- "80:80"
- "443:443"
volumes:
- ./certs:/etc/nginx/certs:ro
- /etc/nginx/vhost.d
- /usr/share/nginx/html
- /var/run/docker.sock:/tmp/docker.sock:ro
letsencrypt:
image: jrcs/letsencrypt-nginx-proxy-companion
restart: always
volumes:
- ./certs:/etc/nginx/certs:rw
- /var/run/docker.sock:/var/run/docker.sock:ro
volumes_from:
- nginx-proxy
www:
image: blah/www
restart: always
depends_on:
- nginx-proxy
- letsencrypt
environment:
- VIRTUAL_HOST=www.blah.com
- LETSENCRYPT_HOST=www.blah.com
-<EMAIL_ADDRESS>db:
image: arangodb
restart: always
depends_on:
- nginx-proxy
- letsencrypt
volumes:
- /mnt/volume1/database:/var/lib/arangodb3
environment:
- ARANGO_ROOT_PASSWORD=blah-blah-blah
- VIRTUAL_HOST=db.blah.com
- VIRTUAL_PORT=8529
- LETSENCRYPT_HOST=db.blah.com
-<EMAIL_ADDRESS>After running "docker-compose up" I see this on the console from arangodb:
db_1           | Initializing root user...Hang on...
db_1           | Initializing database...Hang on...
db_1           | Database initialized...Starting System...
db_1           | 2017-07-02T20:55:34Z [1] INFO ArangoDB 3.1.23 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1t  3 May 2016
db_1           | 2017-07-02T20:55:34Z [1] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
db_1           | 2017-07-02T20:55:34Z [1] INFO Starting up with role SINGLE
db_1           | 2017-07-02T20:55:34Z [1] INFO Authentication is turned on
db_1           | 2017-07-02T20:55:34Z [1] INFO Authentication system only
db_1           | 2017-07-02T20:55:34Z [1] INFO Authentication for unix sockets is turned on
db_1           | 2017-07-02T20:55:34Z [1] INFO file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576
db_1           | 2017-07-02T20:55:34Z [1] INFO JavaScript using startup '/usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
db_1           | 2017-07-02T20:55:35Z [1] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8529' for non-encrypted requests
db_1           | 2017-07-02T20:55:36Z [1] INFO ArangoDB (version 3.1.23 [linux]) is ready for business. Have fun!
I see no errors on the console, everything seems to start normally.  When I try to replicate this locally (using docker, NOT docker-compose) the arangodb image starts normally and I can log in using the same password as expected.  I also tried using a really simple password without any symbols, and I still couldn't log in to the remote db server.
I'm happy to provide more info if you need it.  Thanks!

I also tried setting the ARANGO_RANDOM_ROOT_PASSWORD=1 environment variable and I don't see anything in the console output telling me what the random password is.  It's as thought arangodb just doesn't see then environment vars when using docker-compose.  Setting ARANGO_RANDOM_ROOT_PASSWORD=1 with a local docker instance and it worked as you'd expect.

The docker container you use is built from:
https://github.com/arangodb/arangodb-docker/tree/official/jessie/3.1.23
I suggest that you try to build it locally (it basically installs the .deb from arangodb.com - so you can simply do that), but add a plain set to the docker-entrypoint.sh so you can check back the actual environment whether it contains any of the environment variables you set.

I am having the same issue and reported it under https://github.com/arangodb/arangodb/issues/2538

Thanks @dothebart I think that's a reasonable approach, but instead of doing that, I ran a bash shell within the docker container in question and verified the environment variables were set according to my docker-compose.yml file.  They are being set:
root@Instance-1:~/github/admin/docker-compose# docker exec -i -t 8ba2 /bin/bash
root@8ba2f751957e:/# echo $ARANGO_RANDOM_ROOT_PASSWORD
1
But when you check the log, the random password is not being output:
root@Instance-1:~/github/admin/docker-compose# docker logs 8ba2
2017-07-03T22:14:25Z [1] INFO ArangoDB 3.1.23 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1t  3 May 2016
2017-07-03T22:14:25Z [1] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-07-03T22:14:25Z [1] INFO Starting up with role SINGLE
2017-07-03T22:14:25Z [1] INFO Authentication is turned on
2017-07-03T22:14:25Z [1] INFO Authentication system only
2017-07-03T22:14:25Z [1] INFO Authentication for unix sockets is turned on
2017-07-03T22:14:25Z [1] INFO file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576
2017-07-03T22:14:26Z [1] INFO JavaScript using startup '/usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-07-03T22:14:27Z [1] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2017-07-03T22:14:28Z [1] INFO ArangoDB (version 3.1.23 [linux]) is ready for business. Have fun!

Initializing database...Hang on...
Database initialized...Starting System...
2017-07-04T14:14:13Z [1] INFO ArangoDB 3.1.23 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1t  3 May 2016
2017-07-04T14:14:13Z [1] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-07-04T14:14:13Z [1] INFO Starting up with role SINGLE
2017-07-04T14:14:13Z [1] INFO Authentication is turned on
2017-07-04T14:14:13Z [1] INFO Authentication system only
2017-07-04T14:14:13Z [1] INFO Authentication for unix sockets is turned on
2017-07-04T14:14:13Z [1] INFO file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576
2017-07-04T14:14:13Z [1] INFO JavaScript using startup '/usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-07-04T14:14:14Z [1] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2017-07-04T14:14:15Z [1] INFO ArangoDB (version 3.1.23 [linux]) is ready for business. Have fun!

docker --version
Docker version 17.05.0-ce, build 89658be

After banging my head for a while I took the drastic step of just deleting the data directory... and after that it recreated it's data directory and the random password setting started working.  So either something was corrupted on the file system, or switching the root password environment variable several times exercised a bug.  Since I can't tell, or give exact steps to recreate, this issue should be closed.

@phal0r since this seems to be somewhat related to what docker keeps, can you try to docker ps -a  and docker images and purge all containers in conjunction with arangodb and retry?

I was struggling with the very same issue last night. Purging images or the containers had no effect, so based on @johnvcoleman suggestion I took the extreme measure and removed the data directory and that did the job

This was closed a while ago, but I just came across a similar issue, not with docker compose, but running a standalone container with persistent data via a docker volume.
I had accidentally run it at first without saving the root password, so I wanted to go through the procedure indicated here to recover.
I stopped and removed the container and started a new one (with the same data volume) using the env var ARANGO_NO_AUTH=1 and authentication was turned off, which made me hopeful.
I then removed the container again, but when I reran it with ARANGO_ROOT_PASSWORD it didn't work, I couldn't use the password I had set.
I retried with ARANGO_RANDOM_ROOT_PASSWORD=1 and it didn't show any password.
I kept trying a few times with different options, but always removing the container and NOT the data volume.
I then finally decided to reset ARANGO_NO_AUTH=1 and change the password via UI.
But this makes me think the environment variable is not enough to actually CHANGE a root password that has already been set. It must be done via the arangosh or the UI. But this should at least avoid having to delete the data volume.

I'm running into the same issue as everyone else and there's definitely a bug in which when you create a new docker container with arangodb whatever environment variable was initially set using ARANGO_ROOT_PASSWORD will persistent for every arangodb docker container thereafter. And once this glitch happens the env variable ARANGO_RANDOM_ROOT_PASSWORD=1 will no longer output a randomly generated password, because it is using the password that was set for ARANGO_ROOT_PASSWORD.
Seeing that the repo is very basic, I'm surprised that more people haven't run into this issue because it seems like it's fairly serious.
I'm running docker on MacOs - Big Sur Version 11.6 in case that has anything to do with it. If anyone could confirm that they are having this same issue on a Windows or Linux machine that would be super helpful in eliminating some possible causes.

Do you mount the same volume to the new containers? Than I think, that this is expected.

exactly. if you have the same database volume as before you expect to find your data again including your credentials when restarting a docker container.

Alright yea that makes perfect sense! I wasn't thinking about the problem in the right way.
Thank you guys for the help, I was pulling my hair our trying to figure out what I was doing wrong 😅


GROOVY-9462: print placeholder using getUnresolvedName()

https://issues.apache.org/jira/browse/GROOVY-9462

Merged. Thanks.


Merge nmirror to master

The Windows Debug failure is caused by David's new assert that is triggering in multimodule tests. I understand the problem - I just need to come up with a good fix.

Superseded by #2925.


Synchronize counts for link and unlink

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

The output of linking and unlinking a formula can give different counts in some cases, as mentioned in #239:
$ brew link neovim
Linking /usr/local/Cellar/neovim/0.1.4... 40 symlinks created
$ brew unlink neovim
Unlinking /usr/local/Cellar/neovim/0.1.4... 66 symlinks removed

Investigation confirms that the links created and removed are the same, but unlink counts also directories among symlinks removed. This PR improves the situation to synchronize link and unlink, getting both to talk about 40 symlinks. Verbose logs confirm this is the amount of links created/removed (see below). This PR also takes care to not affect statistics used by other commands, which specifically mention directories.
If desired, one could also log the count of created and removed directories in link/unlink's output.
Furthermore, this PR restores logging of mkdir operation during verbose linking, which was removed in https://github.com/Homebrew/legacy-homebrew/commit/f899878220668c7c7f0fcf43c6d294a52b7e79ed without a specific rationale. Logging both creations and removals appears more symmetric.
In previous discussion in #239, @mikemcquaid explained the issue was known and low-priority, while @xu-cheng claimed this was not an issue and offered an alternative explanation. I investigated the alternative explanation in more detail, and was unable to find confirming evidence, at least in this instance.
$ brew -v unlink neovim
Unlinking /usr/local/Cellar/neovim/0.1.4...
rm /usr/local/bin/nvim
rm /usr/local/share/locale/af/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/ca/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/cs/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/cs.cp1250/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/de/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/en_GB/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/eo/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/es/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/fi/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/fr/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/ga/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/it/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/ja/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/ja.euc-jp/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/ja.sjis/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/ko/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/ko.UTF-8/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/nb/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/nl/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/no/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/pl/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/pl.UTF-8/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/pl.cp1250/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/pt_BR/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/ru/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/ru.cp1251/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/sk/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/sk.cp1250/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/sv/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/uk/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/uk.cp1251/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/vi/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/zh_CN/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/zh_CN.UTF-8/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/zh_CN.cp936/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/zh_TW/LC_MESSAGES/nvim.mo
rm /usr/local/share/locale/zh_TW.UTF-8/LC_MESSAGES/nvim.mo
rm /usr/local/share/man/man1/nvim.1
rm /usr/local/share/nvim
rmdir /usr/local/share/locale/zh_TW.UTF-8/LC_MESSAGES
rmdir /usr/local/share/locale/zh_TW.UTF-8
rmdir /usr/local/share/locale/zh_CN.cp936/LC_MESSAGES
rmdir /usr/local/share/locale/zh_CN.cp936
rmdir /usr/local/share/locale/zh_CN.UTF-8/LC_MESSAGES
rmdir /usr/local/share/locale/zh_CN.UTF-8
rmdir /usr/local/share/locale/uk.cp1251/LC_MESSAGES
rmdir /usr/local/share/locale/uk.cp1251
rmdir /usr/local/share/locale/sk.cp1250/LC_MESSAGES
rmdir /usr/local/share/locale/sk.cp1250
rmdir /usr/local/share/locale/ru.cp1251/LC_MESSAGES
rmdir /usr/local/share/locale/ru.cp1251
rmdir /usr/local/share/locale/pl.cp1250/LC_MESSAGES
rmdir /usr/local/share/locale/pl.cp1250
rmdir /usr/local/share/locale/pl.UTF-8/LC_MESSAGES
rmdir /usr/local/share/locale/pl.UTF-8
rmdir /usr/local/share/locale/no/LC_MESSAGES
rmdir /usr/local/share/locale/no
rmdir /usr/local/share/locale/ko.UTF-8/LC_MESSAGES
rmdir /usr/local/share/locale/ko.UTF-8
rmdir /usr/local/share/locale/ja.sjis/LC_MESSAGES
rmdir /usr/local/share/locale/ja.sjis
rmdir /usr/local/share/locale/ja.euc-jp/LC_MESSAGES
rmdir /usr/local/share/locale/ja.euc-jp
rmdir /usr/local/share/locale/cs.cp1250/LC_MESSAGES
rmdir /usr/local/share/locale/cs.cp1250
40 symlinks removed
$ brew -v link neovim
Linking /usr/local/Cellar/neovim/0.1.4...
ln -s ../Cellar/neovim/0.1.4/bin/nvim nvim
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/af/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/ca/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/cs/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/cs.cp1250
mkdir /usr/local/share/locale/cs.cp1250/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/cs.cp1250/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/de/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/en_GB/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/eo/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/es/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/fi/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/fr/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/ga/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/it/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/ja/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/ja.euc-jp
mkdir /usr/local/share/locale/ja.euc-jp/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/ja.euc-jp/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/ja.sjis
mkdir /usr/local/share/locale/ja.sjis/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/ja.sjis/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/ko/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/ko.UTF-8
mkdir /usr/local/share/locale/ko.UTF-8/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/ko.UTF-8/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/nb/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/nl/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/no
mkdir /usr/local/share/locale/no/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/no/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/pl/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/pl.UTF-8
mkdir /usr/local/share/locale/pl.UTF-8/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/pl.UTF-8/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/pl.cp1250
mkdir /usr/local/share/locale/pl.cp1250/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/pl.cp1250/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/pt_BR/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/ru/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/ru.cp1251
mkdir /usr/local/share/locale/ru.cp1251/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/ru.cp1251/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/sk/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/sk.cp1250
mkdir /usr/local/share/locale/sk.cp1250/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/sk.cp1250/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/sv/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/uk/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/uk.cp1251
mkdir /usr/local/share/locale/uk.cp1251/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/uk.cp1251/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/vi/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/zh_CN/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/zh_CN.UTF-8
mkdir /usr/local/share/locale/zh_CN.UTF-8/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/zh_CN.UTF-8/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/zh_CN.cp936
mkdir /usr/local/share/locale/zh_CN.cp936/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/zh_CN.cp936/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/zh_TW/LC_MESSAGES/nvim.mo nvim.mo
mkdir /usr/local/share/locale/zh_TW.UTF-8
mkdir /usr/local/share/locale/zh_TW.UTF-8/LC_MESSAGES
ln -s ../../../../Cellar/neovim/0.1.4/share/locale/zh_TW.UTF-8/LC_MESSAGES/nvim.mo nvim.mo
ln -s ../../../Cellar/neovim/0.1.4/share/man/man1/nvim.1 nvim.1
ln -s ../Cellar/neovim/0.1.4/share/nvim nvim
40 symlinks created

Saving this output to ~/foo and counting link creations and removal with grep confirms they're both indeed 40, and that both directory creations and removals are here 26. This fits the explanation that "66 symlinks removed" counted both symlinks and directories.
$ grep '^ln ' ~/foo|wc -l
      40
$ grep '^rm ' ~/foo|wc -l
      40
$ grep '^rmdir ' ~/foo|wc -l
      26
$ grep '^mkdir ' ~/foo|wc -l
      26

Nice work here. A suggestion but otherwise 👍. Thanks for jumping on this!

LGTM. Will wait for any other maintainer thoughts and otherwise 🚢

LGTM. but FYI, this won't fix all the synchronized number problem. Because depending on your other files in the prefix, how the symlink will be created will be varied.(See Keg#resolve_any_conflicts for more detail.

Because depending on your other files in the prefix, how the symlink will be created will be varied.(See Keg#resolve_any_conflicts for more detail.

Ah, thanks for the pointer! I think I see what you mean, but it seems that cannot keep happening if I keep repeating link/unlink as in #239.
Just to make sure I get it: For each conflict, brew link foo will replace a symlink to a directory pertaining to another formula to symlinks to individual files; brew unlink foo will not remove symlinks for other formulas, and it will not "merge" the symlinks to a directory back into one to a folder, so we arrive at a slightly different situation (which is fine).
However, it appears that repeating immediately brew link foo/brew unlink foo will not find again the same conflicts, so there the counts should match. And that's good: otherwise, just repeated linking and unlinking (certainly an odd operation) would "leak" inodes. That's why I opened #239.
Anyway:  I'm satisfied with the result after this PR.

Thanks for your contribution to Homebrew!  You rock!


Dev to Master, update 2020-01-13 release note

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @astuteape,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


improve minification steps

a special kind of glob expansion needs to be happen in the windows CI pipeline and maybe something like this could be used https://superuser.com/questions/460598/is-there-any-way-to-get-the-windows-cmd-shell-to-expand-wildcard-paths#answer-829556

closed at https://github.com/iambumblehead/esmock/pull/79


Implement a QueueView with buckets

There are several QueueView being used in the chain code of linera.
This is suboptimal since that gets use several loops with loops like
        while let Some(h) = self.queue.front().await? {
            if h > height {
                break;
            }
            self.queue.delete_front();
            updates.push(h);
        }

The solution to that problem is to use a QueView with buckets. This works well, since the size of the data in the QueueView used in the protocol is constant, so we can make efficient used of a QueueView with buckets.

@MathieuDutSik Do we need a separate task for LogView?

Yes, will create it.


ImportError: cannot import name 'PolymorphicModel'

With the upgrade to v0.8, I began getting this error while using polumorphic in conjunction with django-filer. Reverting back to v0.7.2 fixed the issue, but here's the error output. I'm on Windows 10 using Python 3.5
(env) U:\project\intranet>python manage.py runserver
Unhandled exception in thread started by <function check_errors.<locals>.wrapper at 0x0000003437941BF8>
Traceback (most recent call last):
  File "U:\project\env\lib\site-packages\django\utils\autoreload.py", line 229, in wrapper
    fn(*args, **kwargs)
  File "U:\project\env\lib\site-packages\django\core\management\commands\runserver.py", line 107, in inner_run
    autoreload.raise_last_exception()
  File "U:\project\env\lib\site-packages\django\utils\autoreload.py", line 252, in raise_last_exception
    six.reraise(*_exception)
  File "U:\project\env\lib\site-packages\django\utils\six.py", line 685, in reraise
    raise value.with_traceback(tb)
  File "U:\project\env\lib\site-packages\django\utils\autoreload.py", line 229, in wrapper
    fn(*args, **kwargs)
  File "U:\project\env\lib\site-packages\django\__init__.py", line 18, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "U:\project\env\lib\site-packages\django\apps\registry.py", line 108, in populate
    app_config.import_models(all_models)
  File "U:\project\env\lib\site-packages\django\apps\config.py", line 198, in import_models
    self.models_module = import_module(models_module_name)
  File "U:\project\env\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 986, in _gcd_import
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 673, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 662, in exec_module
  File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
  File "U:\project\env\lib\site-packages\filer\models\__init__.py", line 3, in <module>
    from filer.models.clipboardmodels import *  # flake8: noqa
  File "U:\project\env\lib\site-packages\filer\models\clipboardmodels.py", line 9, in <module>
    from filer.models import filemodels
  File "U:\project\env\lib\site-packages\filer\models\filemodels.py", line 14, in <module>
    from polymorphic import PolymorphicModel, PolymorphicManager
ImportError: cannot import name 'PolymorphicModel'

Getting this also under Ubuntu 15.10 with latest Python 3.5.0+

Confirming this issue as well. Core Models should not be removed since it can introduce breaking changes. This update should have been labeled 1.. since it has core restructuring.

If you update django-filer to 1.0.5 the requirement is fixed to request polymorphic 0.7<

For versions (> 0.8) you must use from polymorphic.models import PolymorphicModel

You'll have to update some imports. there are a few backwards incompatible changes in 0.8:
http://django-polymorphic.readthedocs.org/en/latest/changelog.html#version-0-8-2015-12-28


init that works with precompile (and fixes non initialization)

Codecov Report

Merging #27 into master will decrease coverage by 7.41%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #27      +/-   ##
=========================================
- Coverage   65.11%   57.7%   -7.42%
=========================================
  Files           5       5
  Lines         883     844      -39
=========================================
- Hits          575     487      -88
- Misses        308     357      +49

Impacted Files
Coverage Δ

src/CUBLAS.jl
13.79% <100%> (+3.07%)
:arrow_up:

src/blas.jl
85.1% <0%> (-9.69%)
:arrow_down:

src/libcublas.jl
0% <0%> (-0.45%)
:arrow_down:

Continue to review full report at Codecov.

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


migration banner disappeared after cancelling

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
https://ap-northeast-2.console.aws.amazon.com/amplify/home?region=ap-northeast-2#/db4hy11ovq43d
AWS Region
ap-northeast-2
Amplify Hosting feature
Frontend builds
Describe the bug
I was intended to migrate the beta branch of our app from Next11 to Next12. However, I noticed that the migration task has been started over all branches including master branch, so I canceled the task that was going on in the master branch.
The problem is, even though I cancelled the migration, the banner section shows nothing and it seems there's no ways to see a 'migrate' button again. Moreover, when I retry to re-build the beta branch, the build terminal shows an error like this because the migration task has been not completed:
 !! CustomerError: Please update your Next.js version to 12 or newer and re-run your build to migrate to Amplify Hosting Compute. Learn More: https://docs.aws.amazon.com/amplify/latest/userguide/server-side-rendering-

My question is:
Is there any way to re-run the migration process on amplify console?
Is it possible to selectively migrate the branch on the console?
Expected behavior
App should be migrated to Next12 from Next11 and deployed.
Reproduction steps

Press the migration button in the banner
Cancel the migration process
Go back to app page and there would be loading banner but doesn't shows anything

Build Settings
No response
Log output

# Put your logs below this line

Additional information
No response

Hi @heejin617 thank you for opening this issue. I'm currently investigating this and I'll follow up soon.

Hi, It turned out the beta branch was pointing the older commit that includes next11 version in package.json and that's why the build script showed the version error. And found that the migration process was already completed when canceling the build.


Unit test 2.7.3

fix unit test

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.7.3-release@69a0483). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             2.7.3-release    #4434   +/-   ##
================================================
  Coverage                 ?   62.78%
  Complexity               ?      453
================================================
  Files                    ?      769
  Lines                    ?    33012
  Branches                 ?     5208
================================================
  Hits                     ?    20725
  Misses                   ?     9894
  Partials                 ?     2393

Continue to review full report at Codecov.

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


'expect(promise).resolves' with no matcher causes strange side effects on node version < 12.

🐛 Bug Report
When using resolves expectation on a promise without a matcher and the promise modifies some state, the state is reverted after the expectation finishes. This is tested to happen on node 10 & 11 but not on 12 & 13.
To Reproduce
Run the following on node v10 or v11.
let number = 1

async function func(){
	await Promise.resolve() //If you ommit this promise call the test succeeds
	number = 2
	console.log(number) //returns 2 correctly
}

test('test', async() => {
	/*
		If we ommit this assertion and await the func() call only, the test succeeds
		If we continue the statment with a '.toBe(undefined)', the test succeeds
	*/
	await expect(func()).resolves
	expect(number).toBe(2) //obj.number is unchanged (i.e. returns 1)
})

Expected behavior
On node 10 & 11, the test fails showing number to be 1 (not 2). Running this snippet on node 12 & 13, the test succeeds.
Link to repl or repo
The previous description is all that is offered.
envinfo
[hadichahine@mashmach jest-issue]$ npx envinfo --preset jest
npx: installed 1 in 57.004s

  System:
    OS: Linux 5.5 Arch Linux
    CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
  Binaries:
    Node: 11.15.0 - ~/.nvm/versions/node/v11.15.0/bin/node
    Yarn: 1.22.0 - /usr/bin/yarn
    npm: 6.7.0 - ~/.nvm/versions/node/v11.15.0/bin/npm
  npmPackages:
    jest: ^26.0.1 => 26.0.1

from the code: https://github.com/facebook/jest/blob/81712ba847c7a886d58d890e181b4036b2a9d398/packages/expect/src/index.ts#L94

.resolves alone is a container for matchers.

you can try something like: .resolves.toBeUndefined() or .resolves.not.toThrow() to have at least 1 matcher, so the await will await.

Yes sure. But what is strange is that it's working on node 12 & 13 but not on node 11. Using resolves without the matchers is more descriptive than the examples you mentioned. The fact that resolves isn't intended to work alone should better be mentioned in the documentation (imo).
Thanks.

Yes, Actually when i tried to make a default for this issue.

For .resolves, it can easily defaults to .not.toThrow,

But for .rejects, it can't be done easily. since Promise.reject() without giving any error, not actually throwing anything. so .toThrow is not the answer.

All the following condition must be rejected:
  await jestExpect(async () => {
      foo = 'bar';
      throw new Error('Test');
    }).rejects
  await jestExpect(Promise.reject()).rejects;
  await jestExpect(Promise.reject("str value")).rejects;
  await jestExpect(Promise.reject(111)).rejects;
  await jestExpect(Promise.reject(new Error())).rejects;

The problem is .reject(value), can be any value including undefined.
But, anything() in jest, matches anything but null or undefined. https://jestjs.io/docs/en/expect#expectanything
If anyone have better idea, it will be good


Deprecate legacy glTF 1.0 assets and KHR_techniques_webgl

In the future, ModelExperimental will replace the old Model implementation for rendering glTF assets. As part of this, we are choosing not to implement the legacy glTF 1.0 assets as some details like techniques are non-trivial to implement
This also deprecates the KHR_techniques_webgl glTF 2.0 extension (an archived extension for backwards compatibility with glTF 1.0). For custom GLSL code, CustomShader can be used instead.
For a glTF 1.0 asset, see this local sandcastle which loads one of the models in Specs/Data/Models
For a glTF 2.0 asset with KHR_techniques_webgl, see the 3D Tiles BIM Sandcastle
@lilleyse could you review?

Thanks @ptrgags


Not able to overwrite lambda function name when deploy

Debian 8:
Apex version 0.10.3:
Python function

Try to overwrite lambda function name , by default apex set it to python_yourFunctionName
Using below command to test overwrite default LAMBDA_FUNCTION_NAME , it works when build a zip file .
apex build -s LAMBDA_FUNCTION_NAME=foo bar > test.zip

test.zip/.env.json
{"APEX_FUNCTION_NAME":"bar","LAMBDA_FUNCTION_NAME":"foo"}

However try to use same way to deploy with no luck
apex deploy -s LAMBDA_FUNCTION_NAME=foo bar
   • creating function         env= function=bar
   • created alias current     env= function=bar version=1
   • function created          env= function=bar name=python_bar version=1

What's the use-case for giving a custom name?

We have some naming standard for all the aws resource we created .
Also apex build seems handle the name changes , but deploy command not pick it up

Ahh I see, yeah LAMBDA_FUNCTION_NAME is hard-coded to pass the generated name, but it has no effect on the Lambda function name itself.
I'm against overrides personally, it's confusing if they don't match the directory name. The project can be stripped via re-defining nameTemplate to {{.Function.Name}} http://apex.run/#structuring-projects.

You right , that is all I need . didn't read through document clearly .
Thanks tj

It's a weird option haha :D hard to find.
cheers


flutterwave-react-v3 payment pop-up does not load on production server but loads on local host

Issue :
The payment dialog/pop works normally when working on localhost but when I deployed  the pop does not show when I click the button that triggers the pop-up, hence I cannot test the payment flow :putting card details and all card related information.
This is occurring on the latest version which is 1.2.0 . I haven't tested on the prior versions if the issue is present.
I can't provide the screenshot since the pop is not showing at all.

was this ever resolved?

was this ever resolved?

I doubt it

Hi, @xolanimaphumulo can you state the production environment you deployed to that you faced this issue? So we can replicate it. Thanks

@ugwumadu116  I'm currently facing this issue while staging on heroku

I had the same issue while using the hook, I had to do a workaround and check if window.FlutterwaveCheckout exists or not before calling handleFlutterPayment


refactor: Update dependencies so path-to-regexp gets to a version without CVE

Description
Updates our transitive dependencies on path-to-regexp to versions that fixed https://nvd.nist.gov/vuln/detail/CVE-2024-45296 . Accomplished by updating our direct dependencies on sinon to a mix of version 18 and 19, since that's the main way in which we get transitive dependencies on path-to-regexp.
@types/sinon was also opportunistically updated to the latest version where it wasn't already up to date.
Reviewer Guidance
The review process is outlined on this wiki page.
sinon@19 introduced a breaking change related to fake timers that affects some of our tests and was tricky to work around quickly, so I left the relevant packages (all of client release group and common-utils) on sinon@18 for now.

/azp run server-routerlicious


Crash when Restart song/enter in Charting Mode

Describe your bug here.
since i updated the psych engine to update 0.7.1h when i enter a song and restart it or enter charting mode it just crashes
I have tested this in mods installed in the engine and in the songs of the Vanilla FNF
Command Prompt/Terminal logs (if existing)
This appears if I restart the song:

objects/Note.hx (line 296)
objects/Note.hx (line 224)
states/editors/ChartingState.hx (line 2792)
states/editors/ChartingState.hx (line 2709)
states/editors/ChartingState.hx (line 2259)
states/editors/ChartingState.hx (line 272)
flixel/FlxGame.hx (line 642)
flixel/FlxGame.hx (line 729)
flixel/FlxGame.hx (line 682)
flixel/FlxGame.hx (line 556)
openfl/events/EventDispatcher.hx (line 402)
openfl/display/DisplayObject.hx (line 1399)

Uncaught Error: Null Object Reference
Please report this error to the GitHub page: https://github.com/ShadowMario/FNF-PsychEngine

> Crash Handler written by: sqirra-rng

This appears if i enter charting mode:

objects/Note.hx (line 296)
objects/StrumNote.hx (line 27)
states/editors/ChartingState.hx (line 294)
flixel/FlxGame.hx (line 642)
flixel/FlxGame.hx (line 729)
flixel/FlxGame.hx (line 682)
flixel/FlxGame.hx (line 556)
openfl/events/EventDispatcher.hx (line 402)
openfl/display/DisplayObject.hx (line 1399)

Uncaught Error: Null Object Reference
Please report this error to the GitHub page: https://github.com/ShadowMario/FNF-PsychEngine

> Crash Handler written by: sqirra-rng

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

Bro, I experienced something similar!

I'm having the same error as well but only when I try loading up my json file for my chart.


Accordion steps: 1 - robot calibration

Background
After a user uploads a protocol, they will be greeted to a series of accordion steps to ensure robot and deck are set up correctly.  The first accordion and focus of this ticket is robot calibration.  Follow link to frame here: https://www.figma.com/file/JCQNOTTK9tTmYPhRqeOfSj/Labware-Calibration?node-id=3205%3A47
Please note, screen below is for easy reference only. Consult the source link above to ensure you're looking at the most up to date screens
Step 1 Accordion

Acceptance Criteria

If user expands Step 1 accordion, they will see a title section with a header, sub-header copy, and a right-justified link to robot calibration help modal.
"Proceed to Module Setup" Button is enabled if users have completed all calibration steps. This button is disabled if any calibration steps are not successfully completed. (User is gated from proceeding to next step until all calibration steps are complete)
Clicking the "Proceed to Module Setup" button (or any CTA in an accordion) will collapse the current section and proceed user to the next section
A green check icon is displayed with accompanying text on the collapsed step if that calibration step is complete (see figma frame)
For each calibration step within the Step 1 accordion, a green check icon is displayed if that step has been completed successfully. If not, an empty circle icon is displayed.
At any point that user clicks the top right "x" to close out of the protocol, they will get a confirm close confirmation screen / modal

Deck Calibration

If deck has been calibrated, user will see a green check icon with a timestamp of last calibration

Outstanding deck calibration questions

When if at all does a calibration "expire"? (i dont think it does, but want to confirm)
What happens if deck is not calibrated? does this launch a deck calibration workflow, and if so, what does that look like?
How do we know when to display a check or an empty circle?

Required Pipettes

This section displays required pipettes as determined by the uploaded protocol. The user will see green check icons if pipettes have been successfully calibrated.

Outstanding required pipettes questions

Does left mount / right mount always display, and if no pipette display "none"? Or do we only display Left/Right mount if there is a pipette?
If a Left or Right pipette has not been calibrated, do we kick off that flow here?
How do we know whether to display a check or an empty circle?

Required Tip Length Calibrations

User will see tipracks contained in the protocol sectioned underneath the appropriate pipette
Calibrated tipracks will have a green check icon, with last calibrated timestamp displayed, as well as calibrations measurements
Calibrated tipracks have a link directing users to recalibrate if they so desire. This kicks off the calibration workflow
Non-calibrated tipracks have an empty circle icon, and a button with CTA to "Calibrate Now." This triggers calibration workflow
Load state is displayed when loading required tip length calibrations (see figma frame)

Outstanding tip cal questions

How does the App know which tipracks are associated with which pipette?
What measurements are displayed for calibrated tipracks?

Outstanding tip cal questions
tip length calibration is different than tip rack calibration. Tip length calibration is the z distance between the top of the tip and the bottom of the pipette nozzle. the value is meant to establish the value that is required for the tip to adhere to the nozzle. this is a value associated with Robot Calibration.
The measurement displayed for a tip length calibration is the z value.
Tip rack calibration is part of the labware setup experience and is not part of robot calibration.

Outstanding deck calibration questions
When if at all does a calibration "expire"? (i dont think it does, but want to confirm)
It does not expire. If a user initiates a factory reset it will clear the deck cal and the user will have to redo it before they can proceed to upload protocols.
What happens if deck is not calibrated? does this launch a deck calibration workflow, and if so, what does that look like?
if the deck is not calibrated we have gating scenarios that prevent the user from proceeding. See this figma link
How do we know when to display a check or an empty circle?
empty circle:

there is not a store calibration value for the deck, a given pipette or a required tip length
the correct pipette is not attached

green check:

there is a stored calibration value for the item

Outstanding required pipettes questions
Does left mount / right mount always display, and if no pipette display "none"? Or do we only display Left/Right mount if there is a pipette?
please hold, trying to get this info for you
If a Left or Right pipette has not been calibrated, do we kick off that flow here?
Yes
How do we know whether to display a check or an empty circle?
if the correct pipette is attached (and in the correct mount), and the app has stored values, it will display a green check mark.
@b-cooper i am not sure how we handle robot calibration check on the protocol upload page today, do you happen to know?

@emilywools, currently we don't expose the Robot Calibration Check anywhere in the protocol upload page. It is only accessible from the Calibration Card on the robot page.
One part of the existing Protocol Info page that isn't yet captured in the new designs is the different callouts for missing pipettes or inexact matches (e.g. p300 Single GEN1 specified in protocol, p300 GEN2 attached).
A missing pipette currently has a CTA to the attach pipette flow like this:

An inexact match has an info link to an article explaining things.  link is here for reference


Fix for DataFrame str column created as List of Optional values

Hello @kozlov-alexey! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file sdc/tests/test_dataframe.py:

Line 1669:9: E306 expected 1 blank line before a nested definition, found 0

@densmirn are you ok with this PR?


BUG Fix major segfault on PDOConnector after any DDL / Issue in PDOQuery::first()

A huge amount of testing indicated that the caching of statements will cause a segfault if not cleared after every DDL, since any prepared statement is automatically invalidated.
This could open the door to restoring statement caching for MySQLiConnector, but we can look at that in 3.2-beta2 :D
Also fixed a bug in PDOQuery::first()

@dhensby this should make everyone happy. :) Is this ok?

Related test failures?

Yeah those test failures look pretty directly related to this change, so we'll need to fix those. Are they happening locally for you, Damian?
Although I can see that bundling the code into previewWrite() is functionally correct, it feels a bit ganky, since we're introducing state manipulation into a function that claims to just be providing information. It's not clear to me why we can't put this code into PDOConnector::exec() after its previewWrite() check, as that would seem to be much better. A specific weakness of the current code is that if the previewWrite() functionality is removed, it would break an unrelated feature, the cache cleanup. I think this blocks merge.
While we're on the subject, the structure of the previewWrite() function is a little concerning, but I don't think this blocks merge. I've noted that issue in #4289.

It's not clear to me why we can't put this code into PDOConnector::exec()

Unfortunately we can't force users to use exec for DDL queries; In fact this method is specific to PDO so even less so.
I'll break it out into a preQuery and call previewWrite from there if that's cleaner?

Ok discussion with @sminnee and @assertchris yields a desire to move previewWrite and benchmarkQuery into the controller class.

ok, done. I'll update the other connectors to match this change.

PostgreSQL update at https://github.com/silverstripe/silverstripe-postgresql/pull/42
Suggestion: Merge postgresql first then restart these tests :D

SQL Server update at https://github.com/silverstripe/silverstripe-mssql/pull/23

SQLite3 update at https://github.com/silverstripe-labs/silverstripe-sqlite3/pull/11

Hopefully this is the last ORMey component to change before 3.2.
@sminnee does this seem to work with you? Happy for you to take over merging all of these if you're happy. ;D

Thanks for that, all merged now :-)


Make "use my location" button more prominent in filters

Here is the svg icon
gps.svg.zip

This change is live!
https://foodoasis.la/search/


(docs) Update doris-future.md

Change doris to Doris
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Mouse focus not switched on workspace changes

While keyboard focus does get switched, mouse focus does not unless mouse is moved. So scroll wheel events get sent to the client on the other workspace.

Meant to go in sway, nevermind


修复createPropertyReport右值引用引发的意外破坏栈内存的bug

在Args模版参数被实例化成PropertyReport::avg时
decltype(std::forward(args)) 的类型会变成 PropertyReport::avg&&
进而导致PropertyReportImp中的_propertyReportData成员变量会变成std::tuplePropertyReport::avg&& 类型，这时new出来的PropertyReportImp对象中的成员变量的一部分内存会指向栈顶内存，如果这时调用report接口会以外修改栈上的内存，会使栈损坏

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Already updated.


error in transfer learning solution

Hi i tried the solution for transfer learning
codes = codes.reshape((len(labels), -1))
got the error
i got this i reduced the number of images as a poc on my PC.
running windows and 3.5.2 python cpu no gpus.
i added print (len(codes )) to verify info.
 in ()
10     codes = np.fromfile(f, dtype=np.float32)
11     print(len(codes))
---> 12     codes = codes.reshape((len(labels),-1))
ValueError: cannot reshape array of size 9187328 into shape (2244,newaxis)

Hi alain, I had a similar issue. In my case, the original code below...
    labels = np.array([each for each in reader]).squeeze()

...resulted in the last label being in empty label:
labels[-1]
>>> []  #the last label should either be 'daisy', 'dandelion', 'roses', 'sunflowers', or 'tulips'

The result was like yours in that the array of codes could not be reshaped evenly by the length of labels because of the erroneous addition of the last label that was empty.
So i added a conditional  if len(each) > 0 to the original list comprehension to only read in the line if it was not empty:
    labels = np.array([each for each in reader if len(each) > 0]).squeeze()

This prevented any empty lines from being read in to labels; result was the the length of codes was now evenly divisible by length of labels and the reshape was successful.
Below is the block of code that appears works in my case in the "Building the Classifier" section:
# read codes and labels from file
import csv

with open('labels') as f:
    reader = csv.reader(f, delimiter='\n')
    labels = np.array([each for each in reader if len(each) > 0]).squeeze()

with open('codes') as f:
    codes = np.fromfile(f, dtype=np.float32)
    codes = codes.reshape((len(labels), -1))

thanks navyg8r worked for me in my case

@navyg8r Would you submit a PR? That would be good to share in the notebook.

thanks erip. i'm still a noob at this git so I don't know what PR means (PR=pull request?). i'm still learning git so i'm not yet comfortable with how to do it without breaking something (i almost lost my project 3 work after issuing some git command); since it looks like mat's been assigned this issue, i will wait for mat to fix. i'll research how to do a PR in the meantime.

I'm at the same level as Navyg8r  concerning the usage of Git.

Hi all, I'm on it!

Fixed: https://github.com/udacity/deep-learning/commit/8730e18ab1b8aedb3ea5715bd31c53d9d7cd01e7


[FEATURE]: Add two sounds

[ ] First sound to be added is for the home page, which would automatically run once the application is executed and would run till the game is begun.
[ ] The Second sound would be a game over sound which would occur when the game over text pops up in front of the user's screen

@TusharSharmaIN Any updates on this? Or should I unassign it to you?


Update KeepAliveD cookbook to reflect new options for keepalived.conf

Cookbook version
https://supermarket.chef.io/cookbooks/keepalived/versions/3.0.1
Chef-client version
Chef-Client 12.18.31 RHEL 6.8 x86_64
Platform Details
Red Hat Enterprise Linux 6.8 x86_64
Scenario:
Attempting to use new settings in KeepAliveD Configuration to allow scripts to be executed with KeepAliveD 1.3.2. KeepAliveD 1.2.13, the one in most Yum Repositories, has issues with SELinux allowing it to execute scripts. After building from source for 1.3.2, scripts are attempting to be executed, but there are no spots for settings listed here.
https://github.com/acassen/keepalived/blob/master/doc/keepalived.conf.SYNOPSIS
Steps to Reproduce:
Build KeepAliveD 1.3.2 from source. Attempt to input user into vrrp_script, chef-client run fails.
Expected Result:
This should add the user to the vrrp_script block allowing KeepAliveD to execute vrrp_scripts, as well as notifiy scripts.
Actual Result:
16:52:39 # chef-client -z -o recipe[zabbix_keepalived::default]
[2017-02-07T16:52:49+00:00] WARN: No config file found or specified on command line, using command line options.
Starting Chef Client, version 12.18.31
[2017-02-07T16:52:53+00:00] WARN: Run List override has been provided.
[2017-02-07T16:52:53+00:00] WARN: Original Run List: []
[2017-02-07T16:52:53+00:00] WARN: Overridden Run List: [recipe[zabbix_keepalived::default]]
resolving cookbooks for run list: ["zabbix_keepalived::default"]
Synchronizing Cookbooks:
  - keepalived (3.0.1)
  - zabbix_keepalived (0.1.0)
Installing Cookbook Gems:
Compiling Cookbooks...

================================================================================
Recipe Compile Error in /root/.chef/local-mode-cache/cache/cookbooks/zabbix_keepalived/recipes/default.rb
================================================================================

NoMethodError
-------------
undefined method `user' for ChefKeepalived::Resource::VrrpScript

Cookbook Trace:
---------------
  /root/.chef/local-mode-cache/cache/cookbooks/zabbix_keepalived/recipes/default.rb:24:in `block in from_file'
  /root/.chef/local-mode-cache/cache/cookbooks/zabbix_keepalived/recipes/default.rb:18:in `from_file'

Relevant File Content:
----------------------
/root/.chef/local-mode-cache/cache/cookbooks/zabbix_keepalived/recipes/default.rb:

 17:
 18:  keepalived_vrrp_script 'chk_zabbix' do
 19:    interval 2
 20:    weight 20
 21:    fall 3
 22:    rise 1
 23:    script '/etc/keepalived/notify.sh chk'
 24>>   user 'root' 'root'
 25:    init_fail
 26:  end
 27:
 28:  keepalived_vrrp_instance 'ccf_1' do
 29:    notify_master '"/etc/keepalived/notify.sh start" root root'
 30:    notify_backup '"/etc/keepalived/notify.sh stop" root root'
 31:    notify_fault '"/etc/keepalived/notify.sh stop" root root'
 32:    smtp_alert true
 33:    state 'MASTER'

Platform:
---------
x86_64-linux

Running handlers:
[2017-02-07T16:52:53+00:00] ERROR: Running exception handlers
Running handlers complete
[2017-02-07T16:52:53+00:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 03 seconds
[2017-02-07T16:52:53+00:00] FATAL: Stacktrace dumped to /root/.chef/local-mode-cache/cache/chef-stacktrace.out
[2017-02-07T16:52:53+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2017-02-07T16:52:53+00:00] ERROR: undefined method `user' for ChefKeepalived::Resource::VrrpScript
[2017-02-07T16:52:53+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)```

thanks for the heads up!


Wr/docker

What does this PR do?
copies/modifies the docker build scripts from sfdx-cli to be used for sf
Acceptance Criteria
Testing Notes
Checklist

[x] This change has been approved by the CLI Review Board or approval isn't required. Anything that adds/changes/deletes commands, flags, output, or json output has to be reviewed.
[x] Does this follow the deprecation policy?

What issues does this PR fix or reference?
@W-12176426@

closed in favor of the other 2 PRs linked above


Error running ionic serve v2 sample app

From @barocsi on November 20, 2016 18:23
Ionic version:  (check one with "x")
[ x] 2.x
I'm submitting a ...  (check one with "x")
[x ] bug report
Just updated ionic, started v2 sample app
receiving
src\pages\tabs\tabs.ts:1Uncaught Error: Module build failed: TypeError: Cannot read property 'content' of

 at Object.typescriptSourcemapLoaderMemory (\node_modules\@ionic\app-scripts\dist\webpack\typescript-sourcemap-loader-memory.js:21:34)

Copied from original issue: driftyco/ionic#9253

From @tycho01 on November 21, 2016 11:48
A similar report here stated an npm cache clean then reinstall of ionic did it.

Cleaning npm cache and reinstalling ionic does not help me to resolve this issue when running ionic serve. Unfortunately I was force to revert to older version of ionic(app-script and ionic-angular).

I did npm cache clean -> sudo npm uninstall ionic -g -> sudo npm install ionic@latest
But it did NOT help. I still see the exact same error mentioned here.
I used to have ionic-cli version 2.1.4. Now it's updated to version 2.1.13.
Here is the result of running ionic info:

Your system information:

Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.3
Ionic CLI Version: 2.1.13
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 0.0.44
ios-deploy version: 1.9.0
ios-sim version: 5.0.9
OS: macOS Sierra
Node Version: v6.2.2
Xcode version: Xcode 8.1 Build version 8B62

Here are parts of my package.json which may help you find the root of this problem:
"private": true,
  "scripts": {
    "ionic:build": "ionic-app-scripts build",
    "ionic:serve": "ionic-app-scripts serve"
  },
  "dependencies": {
    "@angular/common": "2.1.1",
    "@angular/compiler": "2.1.1",
    "@angular/compiler-cli": "2.1.1",
    "@angular/core": "2.1.1",
    "@angular/forms": "2.1.1",
    "@angular/http": "2.1.1",
    "@angular/platform-browser": "2.1.1",
    "@angular/platform-browser-dynamic": "2.1.1",
    "@angular/platform-server": "2.1.1",
    "@ionic/storage": "1.1.6",
    "ionic-angular": "2.0.0-rc.3",
    "ionic-native": "^2.2.6",
    "ionicons": "3.0.0",
    "ng2-translate": "3.1.3",
    "rxjs": "5.0.0-beta.12",
    "zone.js": "0.6.26"
  },
  "devDependencies": {
    "@ionic/app-scripts": "0.0.44",
    "typescript": "2.0.9"
  },

AND
"cordovaPlatforms": [
    "ios",
    "android"
  ],

Solved my issue
Okay... I finally figured it out. This problem was showing up after updating to version 0.0.40.
So I added some debug statements to the newly added typescript-sourcemap-loader-memory.js file.
Turns out that I had a misspelling in one of the import statements:
import {Constants} from "../../lib/Constants";
instead of:
import {Constants} from "../../lib/constants";
This was wrong since the letter 'c' was uppercase. For some unknown reason it was just running fine on version 0.0.39 and below. With the update, webpack was looking for "/lib/Constants.js" and "/lib/Constants.js.map" , which did not exist.
The strange thing is that it was %100 functional before this update!
But anyway, I really expected a more intuitive error message than that.
Hope this saves other people some time!

I have the same issue
ionic info:

Cordova CLI: 6.3.1
Ionic Framework Version: 2.0.0-rc.3
Ionic CLI Version: 2.1.14
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 0.0.45
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.0.0
Xcode version: Not installed

@Maziar-Fotouhi I can't find import {Constants} from "../../lib/constants"; in typescript-sourcemap-loader-memory.js
I can see in my typescript-sourcemap-loader-memory.js  -
var context = helpers_1.getContext();

@dm-grinko import {Constants} from "../../lib/constants"; was a custom code from my project.
You might be misspelling another import in one of your files. I can try to help you debug this.
Could you please provide your console error logs from the browser?

@Maziar-Fotouhi
ok, but I haven't any custom code in this project because it is my first app.
I got this issue before I start do something.
I repeat steps from youtube tutorial of Mirko Nasato
https://www.youtube.com/watch?v=qdeD9rYlBU4&t=288s

@dm-grinko You can expand the error log in the console and see the origin. At least in Chrome, you can. Try to open the app in Chrome and paste the whole error log here, please.

@Maziar-Fotouhi

@dm-grinko How did you find this out? What was your previous webpack version? What is your current version after update?
You could have clicked on the small triangle just on the left hand side of the word "Error". This would have expanded the error logs and probably showed the origin.

Yes, the small triangle helped me. I didn't have the Webpack before. Thanks

This should be resolved now.
Thanks,
Dan


JSON.stringify cannot serialize cyclic structures.

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
I'm getting JSON.stringify cannot serialize cyclic structures. on mutations
If the current behavior is a bug, please provide the steps to reproduce.
export default new Vuex.Store({
  plugins: [createPersistedState()],
  state: {
    user: null,
    events: null,
    organisation: null,
    token: null
  },
  mutations: {
    setUser: function(data){
      this.state.user = data;
    },
    setToken: function(data){
      this.state.token = data;
    },
    setOrganisation: function(data){
      this.state.organisation = data;
    },
    setEvents: function(data){
      this.state.events = data;
    },
  },
})

This looks more like a bug in your application's code than with this plugin. Please check if you're not serializing nested references to other objects or itself.

I have exactly the same problem and only when I use vuex-persistedstate. If I remove it Vuex and everything in my app is working well.
This error is returned at every $store.commit or emit with an object payload.
For example this piece of code give this error
this.$emit('domainAdded', {
  name: this.domain.toLowerCase(),
  totalSent: 0,
  totalBounce: 0,
  totalComplain: 0,
  status: 0,
});

I don't know what in this piece of code can produce a cyclic structure.


Sim-telarray and corsika

From the sim_telarray package:

do we need only the exectutables in sim_telarray/bin/ or any other file?

For those applications which rely on CORSIKA only (so don't need sim_telarray): do need the CORSIKA as provided in the sim_telarray package, or can we use e.g., the corsika package as distributed by KIT?

We still need the simtel directory because of some cfg files. This will change soon when I start pointing simtel to our local directory with the cfg files created from the DB.
About CORSIKA: there is still no application that uses CORSIKA at all, by the moment. So I never actually thought about it.
I honestly don't see any reason to allow for a standalone CORSIKA distribution. Yes, there will be (few) applications that uses only CORSIKA, and not simtel. However, which kind of user would be interested only on these applications?
I wouldn't spend any time on this so soon, for the sake of time optimization.

OK - just wanted to make sure that we have thought about this.


WebSockets and HTTP/2

I think we need to review our use of Websockets.
Now, Websockets are supported in a standalone package, which has not received much attention. The use cases that motivates Websocket, could to a great extent be done using HTTP/2 and SSE, even though HTTP/2 doesn't entirely replace Websockets.
We should discuss whether we should bring such use cases under the HTTP umbrella, support HTTP/2 for Solid and integrate SSE into the platform.

:+1: I suggested SSE in #11
Also in https://github.com/solid/solid/issues/116 I asked what advantage globing gives in HTTP/2 world

Just a short note on SSE, since I just read the spec, and I didn't quite like what I read. SSE does not maintain orthogonality is a principle, and as a result, it defines both an API and a media type.
The media type does not seem to make much sense from a Solid perspective, but if we had an RDF-based format for the same thing, which I think is something the academic community has been working on (citation needed, I don't have it), it would make sense.
I ended up concluding that SSE didn't make sense for Solid, but an extension where EventSource is specified separately from the media type would. So, perhaps that is something we should look into, even though that's quite a lot larger.

The media type does not seem to make much sense from a Solid perspective, but if we had an RDF-based format for the same thing, which I think is something the academic community has been working on (citation needed, I don't have it), it would make sense.

I don't understand your critique. RDF is a data model, right? Not a data serialization. How is this text/event-stream document not sufficiently "RDF-based"?:
event: https://www.w3.org/ns/activitystreams#Create
data: {"@context":"https://www.w3.org/ns/activitystreams","summary":"Sally created a note","type":"Create","actor":{"type":"Person","name":"Sally"},"object":{"type":"Note","name":"A Simple Note","content":"This is a simple note"}}

event: https://www.w3.org/ns/activitystreams#Update
data: "{"@context":"https://www.w3.org/ns/activitystreams","summary":"Sally updated her note","type":"Update","actor":{"type":"Person","name":"Sally"},"object":"http://example.org/notes/1"}"
``

> I ended up concluding that SSE didn't make sense for Solid, but an extension where EventSource is specified separately from the media type would.

but then it wouldn't work in all [these browsers](https://caniuse.com/#search=EventSource) implementations... What would be the point?

It seems reeeeaaally inappropriate to dismiss these widely implemented protocols and user-agent API implementations just because you disagree with an editorial decision on how the spec was authored [10 years ago](https://www.w3.org/TR/2009/WD-eventsource-20090423/).

HTTP/2 is cool but 20 years of user-agents won't support it. SSE is over HTTP (unlike WebSocket) and can be polyfilled all the way back to IE8. I don't think WebSocket or HTTP2 can do the same without resorting to insecure plugin things like Flash.

The media type does not seem to make much sense from a Solid perspective, but if we had an RDF-based format for the same thing, which I think is something the academic community has been working on (citation needed, I don't have it), it would make sense.

How does SSE differ in this regard from current Solid Websockets API?
https://github.com/solid/solid-spec/blob/master/api-websockets.md

If a change occurs and the client is subscribed to that resource, it will receive a WebSocket message composed of the keyword pub, followed by an empty space and the URI of the resource that has changed:
pub https://example.org/data/test

I don't see this format having anything to do with RDF.

I don't understand your critique. RDF is a data model, right?

Indeed, and I wrote "RDF-based" for exactly that reason.

Not a data serialization. How is this text/event-stream document not sufficiently "RDF-based"?:

Because, the media type is then given as "text/event-stream", and not as an RDF serialization.

event: https://www.w3.org/ns/activitystreams#Create
data: {"@context":"https://www.w3.org/ns/activitystreams","summary":"Sally created a note","type":"Create","actor":{"type":"Person","name":"Sally"},"object":{"type":"Note","name":"A Simple Note","content":"This is a simple note"}}

event: https://www.w3.org/ns/activitystreams#Update
data: "{"@context":"https://www.w3.org/ns/activitystreams","summary":"Sally updated her note","type":"Update","actor":{"type":"Person","name":"Sally"},"object":"http://example.org/notes/1"}"

Right, so you have to make assumptions about what the serialization is without having any metadata to rely on. That's not nice, but yeah, an assumption that it is JSON is likely to go a long way.

It seems reeeeaaally inappropriate to dismiss these widely implemented protocols and user-agent API implementations just because you disagree with an editorial decision on how the spec was authored 10 years ago.

It is more than an editorial decision. It is a violation of one of the core architectural principles of the Web dating back to its birth. If HTML and HTTP had been in the same spec, it would probably never have taken off.
But hey, it is just about making something that works. If stuffing some JSON-LD in there will keep people happy and productive, I'm not going to be in the way, I'm just saying this could have been done better, and possibly, we should.

Because, the media type is then given as "text/event-stream", and not as an RDF serialization..

Is there a source of truth for the blessed set of "RDF Serializations" you can link me to, or is that assertion just your opinion? If I define "text/event-stream+rdf" and add it to this wiki page, would that make it one?

Right, so you have to make assumptions about what the serialization is without having any metadata to rely on. That's not nice, but yeah, an assumption that it is JSON is likely to go a long way.

I thought that might be the nature of your concern. What if the aforementioned text/event-stream document had come from a request with headers:
Content-Type: text/event-stream;
Sec-Event-Stream-Protocol: application/ld+json

(or, to keep it as a parameter in the same IANA media type registration, add a media type parameter like Content-Type: text/event-stream; dataMediaType=application/ld+json
(Where Sec-Event-Stream-Protocol is like the WebSocket Subprotocol Header)
A corollary is that this could also be a thing
Headers
Content-Type: text/turtle;
Sec-Event-Stream-Protocol: text/turtle

(or Content-Type: text/event-stream; dataMediaType=text/turtle)
Response
event: https://www.w3.org/ns/activitystreams#Create
data:  <http://example.org/person/Mark_Twain>
data:    <http://example.org/relation/author>
data:    <http://example.org/books/Huckleberry_Finn> .

It seems like this would bring back the orthogonality you value by making text/event-stream 'generic' like HTTP itself. But, as always, I could be misunderstanding.

Because, the media type is then given as "text/event-stream", and not as an RDF serialization..

Is there a source of truth for the blessed set of "RDF Serializations" you can link me to, or is that assertion just your opinion?

I am aware of no blessed set of RDF serializations, but I do know what the media types of those that have been implemented are. Generally, there is an open world assumption around these things. So, if you assert that "text/event-stream" is one, please show how it conforms to the RDF abstract syntax.

If I define "text/event-stream+rdf" and add it to this wiki page, would that make it one?

No, since RDF can be serialized in many ways. So, you could in principle define "text/event-stream+turtle", etc.

Right, so you have to make assumptions about what the serialization is without having any metadata to rely on. That's not nice, but yeah, an assumption that it is JSON is likely to go a long way.

I thought that might be the nature of your concern. What if the aforementioned text/event-stream document had come from a request with headers:
Content-Type: text/event-stream;
Sec-Event-Stream-Protocol: application/ld+json

Yeah, that could be a reasonable direction to go in.

(or, to keep it as a parameter in the same IANA media type registration, add a media type parameter like Content-Type: text/event-stream; dataMediaType=application/ld+json

Yup, that too could work.

A corollary is that this could also be a thing
Headers
Content-Type: text/turtle;
Sec-Event-Stream-Protocol: text/turtle

Indeed, but then you'd need to define media types, protocols and APIs orthogonally.

It seems like this would bring back the orthogonality you value by making text/event-stream 'generic' like HTTP itself. But, as always, I could be misunderstanding.

Indeed, it could be done.

I think https://www.w3.org/TR/rdf11-new/#section-serializations lists all the official RDF1.1 serializations.
I also stumbled upon https://profilenegotiation.github.io/I-D-Accept--Schema/I-D-accept-schema which I understand addresses different problem but maybe based on experience in that work @RubenVerborgh has some suggestions how text/event-stream could work with varous RDF serializations.

I think https://www.w3.org/TR/rdf11-new/#section-serializations lists all the official RDF1.1 serializations.

Yeah, but there is a bunch of binary serializations too, and I think people have been working on serializations of event streams specifically, so I would prefer to assume an open world :-)


Create subdirectories in "images" for each chapter

New GitHub users will not have to push to the repo to work on the edX transition if the subdirectories are present.

It looks like someone else is making PRs on this so taking my self off.


Google analytics id not added to pages

Version
2.2.0
Reproduction link
https://github.com/syonip/nuxt-ga-bug
Steps to reproduce
npx create-nuxt-app nuxt-test
cd nuxt-test
npm i @nuxtjs/google-analytics

add following to nuxt.config.js:
modules: [
    ['@nuxtjs/google-analytics', {
      id: 'UA-****'
    }]
  ]

run
npm run dev

What is expected ?
I expect to see activity in GA realtime page.
I expect the html page to contain the 'UA-****' string somewhere but it doesn't.
What is actually happening?
I don't see any activity in GA realtime page when browsing to localhost:3000.
Generated html contains  but not the required call to gtag function with my id.

This bug report is available on Nuxt community (#c37)

I'm also having this bug in Nuxt 2.7.1 with @nuxtjs/google-analytics 2.2.0. I tried using both configuration options in the README.

Update: in production it seems to work.
So maybe it's just the configuration for dev mode that's not taking effect

Yes, I just checked and the UA string is present when generating in production, but not in dev mode. Is there a way to enable it in dev mode for sanity checking?

Hi @syonip , @azigler
Have tried this?
https://matteogabriele.gitbooks.io/vue-analytics/content/docs/turn-off-development.html
Or
https://matteogabriele.gitbooks.io/vue-analytics/content/docs/console-logs.html

Thanks @ricardogobbosouza, I've tried this setting and it works in dev:
debug: {
          enabled: true,
          sendHitTask: true
        }

so I guess the only problem is that the docs say:
You can disable module for nuxt dev by setting dev: false option in module options,
but it seems the default is for it to be disabled in dev mode.
What should the default be for dev mode?

@syonip
In mode dev sendHitTask is disabled

Think we can close this?

The documentation seems unclear, like @syonip says. Setting dev: true in the module options doesn't execute sendHitTask, which is the expected behavior.

The documentation in the vue-analytics repo is exclusively for vue-analytics. The package was created standalone and just wrapped in a Nuxt component to be boot up and start doing certain things automatically.
You won't find anything about Nuxt in the documentation so if something specifically about Nuxt is working adding or removing a boolean here or there, is just a casual :)

It may be necessary to update the documentation or enable sendHitTask in dev mode, what do you think @pi0 ?

@ricardogobbosouza I agree! I just spent too long trying to figure out why it wasn't working locally, and it turns out that it was because I wasn't setting debug.sendHitTask to true. The readme doesn't really make that clear, and I feel like it should default to true anyway?

@Anaphase 	@ricardogobbosouza
A hint in the docs would make sense from my POV. Please also take into consideration that changes are only made in nuxt dev which makes sense as you usually don't want to have development traffic.
https://github.com/nuxt-community/analytics-module/blob/master/lib/module.js#L14-L24

@manniL
I believe a tip in the documentation would help

I'd accept a PR ☺

Made a PR: #54


side-by-side scikit-learn and h2o4gpu

Include side by side examples of scikit and h2o4gpu. Can start of with comparing GLM in scikit vs GLM in h2o4gpu, XGBoost, and K-Means in scikit vs K-Means in h2o4gpu .
Show results and timing for each.
kmeans: @mdymczyk
glm: @navdeep-G
gbm: @pseudotensor

Do the side-by-side examples need to be in README or in a separate notebook?

Hi Karen, Ask Angela.  Should be like h2o-3 docs where you can click button on webpage and see either (say) python or R versions.  For us it would be scikit or ours.  It should also show results as pasted in.


Explicitly use UTC timezone.

Otherwise datetime.now() will return the local time, which may not be UTC.
This was probably missed since most servers run with in the UTC timezone.
Without this, when I tried to input UTC timestamps less than 1 hour ahead (I am UTC+1), it gave an error saying that the time was in the past. This fixes this and releases at the correct time.

You are right, thanks for the PR!