Error: No Bugsnag API Key set

AndroidManifest.xml
<meta-data              android:name="com.bugsnag.android.API_KEY"              android:value="<<MYCODE>>" />
Version "@bugsnag/react-native": "^7.6.1",
Problem in Android!!!

@mattdyoung in MyApplication.java i call, but when i run android yarn it crash the app
@Override   public void onCreate() {     super.onCreate();     SoLoader.init(this, /* native exopackage */ false);     Bugsnag.start(this);     initializeFlipper(this, getReactNativeHost().getReactInstanceManager());   }

I'm unable to reproduce this issue on a new project using @bugsnag/react-native v7.6.1:
$ npx react-native init MyProject
$ cd MyProject
$ npx @bugsnag/react-native-cli init
$ yarn android

Is the API key definitely specified correctly in the correct section of your android/app/src/main/AndroidManifest.xml?
https://docs.bugsnag.com/platforms/android/#basic-configuration
If so are you able to cut this down to a minimal reproduction example so we can investigate further? Feel free to email this to<EMAIL_ADDRESS>if you'd rather not share on the public github issue.

Yes, it is configured correctly. In my version, production in stores is working, but when I send it to run it shows the error.
My file:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
  package="br.com.inku.inkyou"
  xmlns:tools="http://schemas.android.com/tools">

    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.CAMERA"/>
    <uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
    <uses-permission android:name="android.permission.VIBRATE" />
    <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>

    <application
      android:name=".MainApplication"
      android:label="@string/app_name"
      android:icon="@drawable/icon"
      android:roundIcon="@drawable/icon"
      android:allowBackup="false"
      android:theme="@style/AppTheme">
      <activity
        android:name=".MainActivity"
        android:label="@string/app_name"
        android:configChanges="keyboard|keyboardHidden|orientation|screenSize|uiMode"
        android:launchMode="singleTask"
        android:windowSoftInputMode="adjustResize"
        android:screenOrientation="portrait">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
      </activity>
      <activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
      <meta-data android:name="com.bugsnag.android.API_KEY"
             android:value="77da530935e738e0e5a63cd4194ac1c4"/>
      <meta-data
            android:name="com.google.firebase.messaging.default_notification_icon"
            android:resource="@drawable/ic_notification" />

        <meta-data
            android:name="com.google.firebase.messaging.default_notification_color"
            android:resource="@android:color/white"
            tools:replace="android:resource" />
    </application>

</manifest>

I use codepush, does it have to do with the problem?

Hi @yuriedmundo, Codepush is supported and shouldn't have an effect on this.
Your AnroidManifest.xml config looks correct too - would you be able to provide us with a simple reproduction case so we can investigate further?

Closing this issue out as it's gone stale, but please let us know if this issue is persisting.

still get issue

Hi @romreed, do you have the following dependency in your app/build.gradle file?
implementation "com.bugsnag:bugsnag-android:5.+"
If so, please can you remove that line and see if that resolves the issue?

@yousif-bugsnag i just add firebase notification service and all work. thank you

Hi @romreed, do you have the following dependency in your app/build.gradle file?
implementation "com.bugsnag:bugsnag-android:5.+"
If so, please can you remove that line and see if that resolves the issue?

It worked for us @yousif-bugsnag
Thank you.
I don't know why it happened, we have not changed anything in the project that would cause this since our last release couple weeks ago.


Are there any options for producing linearized PDFs from PDFkit?

Hello, I'm supporting a customer who uses pdfkit 0.6.3 in node.js to write PDF files to disk.  We then run the PDF through a pdf-to-text filter in a Java app and apply regexes to extract important metadata from the file.  Most of the time, this sytem works, but for a small number of files per ~1000 PDFs, the Java app produces bad metadata from the file.  I opened some repesentative files in my test harness and saw that the "bad" PDFs consistently are NOT linearized and the output of the pdf-to-text filter has the text in the wrong place; that is, where I'd expect to see "Name                 Value" in the text, I get "Nameffkghblah       Value".  The "good" files are consistently linearized and have the correct "Name Value" pairing in the filtered text.
My working theory is that the linearization process forces the text objects to be in the correct semantic order, and as a result, the filtered text has the correct nanme-value pairing.  the files that are not linearized may have the text objects commingled such that name-value pairing is broken.
My question is: are there any options for producing linearized files through PDFKit?  I've looked through the documentation and the code, and I couldn't see anything, but I wanted to ask this question here before pursuing other angles.

+1

bump

I would also like to see this feature


Support person data in rollbar.js

@jondeandres This works but it's automatic, ie you don't need to list it in the config.js_options, - should this be optional or is it ok as is?

I made it optional, but I can take it out

@rokob I think it's fixed now

@jondeandres Looks good. I had :person_tracking so that someone could turn rollbar.js person tracking on or off, rather than have it be automatic.

Mmmm @and-megan, we even don't have that option in the gem itself, so I think it will be ok sending that information automatically. Using an external option would be the way to do it.


arc: west: mdb: reverse the launch order for multi cores

The Inter-core Debug Unit (ICD) provides additional debug
assist features in multi-core scenarios.
In master core(core 0) initial stage, we will program ICD to halt
all other cores based on a halt occurring in one ore more core.
And all cores are in halt mode on reset, so we need to make
sure other slave cores have launched and in running mode
before we enable ICD in master core.
Currently we launch master first, Let's reverse the launch
order, launch master last, to make sure slave cores have
launched before we program and enable ICD.
Signed-off-by: Watson Zeng<EMAIL_ADDRESS>fix: #36467

without fix:
runners.mdb-hw: mdb -pset=1 -psetname=core0 '' -nooptions -nogoifmain -toggle=include_local_symbols=1 -digilent '' 'zephyr.elf'
runners.mdb-hw: mdb -pset=2 -psetname=core1 -prop=download=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -digilent '' 'zephyr.elf'
runners.mdb-hw: mdb -pset=3 -psetname=core2 -prop=download=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -digilent '' 'zephyr.elf'
runners.mdb-hw: mdb -pset=4 -psetname=core3 -prop=download=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -digilent '' 'zephyr.elf'
runners.mdb-hw: mdb -multifiles=core0,core1,core2,core3 -run '-cmd=-nowaitq run' -cmd=quit -cl

with fix:
runners.mdb-hw: mdb -pset=4 -psetname=core3 -prop=download=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -digilent '' zephyr.elf'
runners.mdb-hw: mdb -pset=3 -psetname=core2 -prop=download=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -digilent '' 'zephyr.elf'
runners.mdb-hw: mdb -pset=2 -psetname=core1 -prop=download=2 -nooptions -nogoifmain -toggle=include_local_symbols=1 -digilent '' 'zephyr.elf'
runners.mdb-hw: mdb -pset=1 -psetname=core0 '' -nooptions -nogoifmain -toggle=include_local_symbols=1 -digilent '' 'zephyr.elf'
runners.mdb-hw: mdb -multifiles=core3,core2,core1,core0 -run '-cmd=-nowaitq run' -cmd=quit -cl

Relying on the start order by the debugger feels not very robust- can't the ICD init not be postponed till arch_start_cpu has been called for all CPUs? Though it looks like that would require adding a new arch callout in z_smp_init(), or some other mechanism to signal all cores have been brought up.

Relying on the start order by the debugger feels not very robust- can't the ICD init not be postponed till arch_start_cpu has been called for all CPUs? Though it looks like that would require adding a new arch callout in z_smp_init(), or some other mechanism to signal all cores have been brought up.

@ruuddw note this is only needed when we start Zephyr with JTAG preparing and kick-starting all cores in the cluster one-by-one. And since all operations conducted via JTAG are relatively slow, there's a huge difference in where a core may get to while others are not yet started.
In real-life all cores would be unhalted/started simultaneously and that problem won't happen.
And for the record, we've done the same fix for OpenOCD runner quite some time ago, see https://github.com/zephyrproject-rtos/zephyr/pull/22602/commits/57fea86925ed29faf405bd313f5afa66fec53943.
Now addressing your suggestion on fixing that problem in Zephyr's code... we did fix that in the Linux kernel with each slave core  re-programming ICD adding its own bit in the mask of "to be halted" cores, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f3205de98db2fc8083796dd5ad81b191e436fab8.
But in case of Linux we were trying to solve a bit another problem: running of the image capable of supporting up-to 4 cores on a cluster with say 1 or 2 cores or some of the cores halted.
In case of Zephyr this is most probably not a problem at all since we build an image for a particular configuration rather than universal something ;)
That said, to keep things simple let's fix a debugger commands invocation order rather than implementing more complex solutions in the target code.

note this is only needed when we start Zephyr with JTAG preparing and kick-starting all cores in the cluster one-by-one.

That is assuming all cores start/are taken out of reset at the same time in the SoC design. I think the purpose of the Zephyr 'arch_start_cpu' function is to allow systems to also work differently, where one CPU starts and manages the other CPUs, takes them out of reset or whatever mechanism to start.
If this synchronous start is something that all ARC HS SMP clusters share (i.e. other SoCs using HS SMP would also have a single reset starting all cores, individual cores don't have different 'halt-on-reset' values) then it is ok rely on this. At least, I think adding some warnings in the code initializing ICD on this assumption would make sense to avoid others debugging the same issue in the future.

If this synchronous start is something that all ARC HS SMP clusters share (i.e. other SoCs using HS SMP would also have a single reset starting all cores, individual cores don't have different 'halt-on-reset' values) then it is ok rely on this. At least, I think adding some warnings in the code initializing ICD on this assumption would make sense to avoid others debugging the same issue in the future.

It's not strictly an SoC feature, but rather a design decision for a particular product. I.e. in case of ARC each core might be configured to either run on reset or halt. So we may even in theory have cores 0 & 2 running on reset and cores 1 & 3 halted :)
What's more it might be a boot-ROM or whatever bootloader is executed before Zephyr who stops/starts certain cores. For example in case of HSDK only core 0 is configured to run on reset, while all the rest are halted. And when we boot Linux on HSDK in an autonomous way (true unmanned boot w/o debugger) it's U-Boot who sets an entry point & kick-starts all slave cores (again, slave cores start to execute Linux binary a bit ahead of the master, but that's just an implementation detail here).
That said, it's not an easy and straight-forward topic and a lot might go wrong. Still given relative simplicity of the improvement we did in the Linux kernel here (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f3205de98db2fc8083796dd5ad81b191e436fab8) we may in fact do the same here. But maybe as a complimentary improvement to this one. What do you think?

Looks like this need to be reverted as the proper fix is #36633


Add a license file

Hi, in package.json you have key "license": "MIT", but there is no license file in project.
Can you be so kind and add it? Thanks you a lot.

@satya164 Please accept pr #245 or give me a feedback. I can't use this component without this.
Otherwise I will have to write this component by myself🙄

Since the license is already mentioned in package.json, why is it important to add the file? I'm not very familiar with the licensing.

Thx you a lot. It's a best practice  https://help.github.com/articles/licensing-a-repository/


protoc autogenerated files should not be in the git repository

When running make, the following error message is thrown
[  6%] Building CXX object
src/CMakeFiles/distributions_shared.dir/io/schema.pb.cc.o In file included from
/distributions/src/io/schema.pb.cc:4:0:
distributions/src/../include/distributions/io/schema.pb.h:17:2: error: #error
This file was generated by an older version of protoc which is
incompatible with your Protocol Buffer headers Please regenerate this
file with a newer version of protoc.

distributions/src/../include/distributions/io/schema.pb.h:18:2: error: #error
This file was generated by an older version of protoc which is
incompatible with your Protocol Buffer headers Please regenerate this
file with a newer version of protoc.

/distributions/src/../include/distributions/io/schema.pb.h:19:2: error: #error
This file was generated by an older version of protoc which is
incompatible with your Protocol Buffer headers Please regenerate this
file with a newer version of protoc.

make[3]: *** [src/CMakeFiles/distributions_shared.dir/io/schema.pb.cc.o] Error 1
make[3]: Leaving directory `distributions/build/python' make[2]: ***
[src/CMakeFiles/distributions_shared.dir/all] Error 2 make[2]: Leaving directory
`distributions/build/python' make[1]: *** [all] Error 2 make[1]: Leaving
directory `distributions/build/python' make: *** [python_cc] Error 2

The solution is to remove the offending file, and rebuild schema.pb.h using make protobuf:
$ rm distributions/include/distributions/io/schema.pb.h
$ make protobuf

Now running make is successful.

Feel free to submit a pr. You'll probably need to apt-get install protobuf-compiler in .travis.yml to make the build work on travis ci. https://github.com/posterior/distributions/blob/master/.travis.yml#L11

This issue explains the failures happening on Travis with DISTRIBUTIONS_USE_PROTOBUF=1: https://travis-ci.org/posterior/distributions/jobs/297802278#L654

travis_fold:start:worker_info
Worker information
hostname<EMAIL_ADDRESS>version: v3.3.1 https://github.com/travis-ci/worker/tree/1153e5010ef9863bf96264b75fba506109633460
instance: travis-job-0fa185c9-4112-4512-92cf-173340739556 travis-ci-garnet-trusty-1503972833 (via amqp)
startup: 21.19508917s
travis_fold:end:worker_info
travis_fold:start:system_info
Build system information
Build language: python
Build group: stable
Build dist: trusty
Build id: 297802275
Job id: 297802278
Runtime kernel version: 4.4.0-93-generic
travis-build version: d1a96d134
Build image provisioning date and time
Tue Aug 29 02:48:34 UTC 2017
Operating System Details
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.5 LTS
Release:	14.04
Codename:	trusty
Cookbooks Version
4642454 https://github.com/travis-ci/travis-cookbooks/tree/4642454
git version
git version 2.14.1
bash version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
gcc version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
docker version
Client:
Version:      17.03.1-ce
API version:  1.27
Go version:   go1.7.5
Git commit:   c6d412e
Built:        Mon Mar 27 17:10:36 2017
OS/Arch:      linux/amd64
Server:
Version:      17.03.1-ce
API version:  1.27 (minimum version 1.12)
Go version:   go1.7.5
Git commit:   c6d412e
Built:        Mon Mar 27 17:10:36 2017
OS/Arch:      linux/amd64
Experimental: false
clang version
clang version 3.9.0 (tags/RELEASE_390/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/clang-3.9.0/bin
jq version
jq-1.5
bats version
Bats 0.4.0
shellcheck version
0.4.6
shfmt version
v1.3.1
ccache version
ccache version 3.1.9
Copyright (C) 2002-2007 Andrew Tridgell
Copyright (C) 2009-2011 Joel Rosdahl
This program is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free Software
Foundation; either version 3 of the License, or (at your option) any later
version.
cmake version
cmake version 3.2.2
CMake suite maintained and supported by Kitware (kitware.com/cmake).
heroku version
heroku-cli/6.13.19-6cd27b3 (linux-x64) node-v8.3.0
imagemagick version
Version: ImageMagick 6.7.7-10 2017-07-31 Q16 http://www.imagemagick.org
md5deep version
4.2
mercurial version
Mercurial Distributed SCM (version 4.2.2)
(see https://mercurial-scm.org for more information)
Copyright (C) 2005-2017 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
mysql version
mysql  Ver 14.14 Distrib 5.6.33, for debian-linux-gnu (x86_64) using  EditLine wrapper
openssl version
OpenSSL 1.0.1f 6 Jan 2014
packer version
Packer v1.0.2
Your version of Packer is out of date! The latest version
is 1.0.4. You can update by downloading from www.packer.io
postgresql client version
psql (PostgreSQL) 9.6.4
ragel version
Ragel State Machine Compiler version 6.8 Feb 2013
Copyright (c) 2001-2009 by Adrian Thurston
subversion version
svn, version 1.8.8 (r1568071)
compiled Aug 10 2017, 17:20:39 on x86_64-pc-linux-gnu
Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/
The following repository access (RA) modules are available:

ra_svn : Module for accessing a repository using the svn network protocol.

with Cyrus SASL authentication
handles 'svn' scheme

ra_local : Module for accessing a repository on local disk.

handles 'file' scheme

ra_serf : Module for accessing a repository via WebDAV protocol using serf.

using serf 1.3.3
handles 'http' scheme
handles 'https' scheme

sudo version
Sudo version 1.8.9p5
Configure options: --prefix=/usr -v --with-all-insults --with-pam --with-fqdn --with-logging=syslog --with-logfac=authpriv --with-env-editor --with-editor=/usr/bin/editor --with-timeout=15 --with-password-timeout=0 --with-passprompt=[sudo] password for %p:  --without-lecture --with-tty-tickets --disable-root-mailer --enable-admin-flag --with-sendmail=/usr/sbin/sendmail --with-timedir=/var/lib/sudo --mandir=/usr/share/man --libexecdir=/usr/lib/sudo --with-sssd --with-sssd-lib=/usr/lib/x86_64-linux-gnu --with-selinux
Sudoers policy plugin version 1.8.9p5
Sudoers file grammar version 43
Sudoers path: /etc/sudoers
Authentication methods: 'pam'
Syslog facility if syslog is being used for logging: authpriv
Syslog priority to use when user authenticates successfully: notice
Syslog priority to use when user authenticates unsuccessfully: alert
Send mail if the user is not in sudoers
Use a separate timestamp for each user/tty combo
Lecture user the first time they run sudo
Root may run sudo
Allow some information gathering to give useful error messages
Require fully-qualified hostnames in the sudoers file
Visudo will honor the EDITOR environment variable
Set the LOGNAME and USER environment variables
Length at which to wrap log file lines (0 for no wrap): 80
Authentication timestamp timeout: 15.0 minutes
Password prompt timeout: 0.0 minutes
Number of tries to enter a password: 3
Umask to use or 0777 to use user's: 022
Path to mail program: /usr/sbin/sendmail
Flags for mail program: -t
Address to send mail to: root
Subject line for mail messages: *** SECURITY information for %h ***
Incorrect password message: Sorry, try again.
Path to authentication timestamp dir: /var/lib/sudo
Default password prompt: [sudo] password for %p:
Default user to run commands as: root
Value to override user's $PATH with: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
Path to the editor for use by visudo: /usr/bin/editor
When to require a password for 'list' pseudocommand: any
When to require a password for 'verify' pseudocommand: all
File descriptors >= 3 will be closed before executing a command
Environment variables to check for sanity:
TZ
TERM
LINGUAS
LC_*
LANGUAGE
LANG
COLORTERM
Environment variables to remove:
RUBYOPT
RUBYLIB
PYTHONUSERBASE
PYTHONINSPECT
PYTHONPATH
PYTHONHOME
TMPPREFIX
ZDOTDIR
READNULLCMD
NULLCMD
FPATH
PERL5DB
PERL5OPT
PERL5LIB
PERLLIB
PERLIO_DEBUG
JAVA_TOOL_OPTIONS
SHELLOPTS
GLOBIGNORE
PS4
BASH_ENV
ENV
TERMCAP
TERMPATH
TERMINFO_DIRS
TERMINFO
RLD*
LD*
PATH_LOCALE
NLSPATH
HOSTALIASES
RES_OPTIONS
LOCALDOMAIN
CDPATH
IFS
Environment variables to preserve:
JAVA_HOME
TRAVIS
CI
DEBIAN_FRONTEND
XAUTHORIZATION
XAUTHORITY
PS2
PS1
PATH
LS_COLORS
KRB5CCNAME
HOSTNAME
HOME
DISPLAY
COLORS
Locale to use while parsing sudoers: C
Directory in which to store input/output logs: /var/log/sudo-io
File in which to store the input/output log: %{seq}
Add an entry to the utmp/utmpx file when allocating a pty
PAM service name to use
PAM service name to use for login shells
Create a new PAM session for the command to run in
Maximum I/O log sequence number: 0
Local IP address and netmask pairs:
<IP_ADDRESS>/<IP_ADDRESS>
<IP_ADDRESS>/<IP_ADDRESS>
Sudoers I/O plugin version 1.8.9p5
gzip version
gzip 1.6
Copyright (C) 2007, 2010, 2011 Free Software Foundation, Inc.
Copyright (C) 1993 Jean-loup Gailly.
This is free software.  You may redistribute copies of it under the terms of
the GNU General Public License http://www.gnu.org/licenses/gpl.html.
There is NO WARRANTY, to the extent permitted by law.
Written by Jean-loup Gailly.
zip version
Copyright (c) 1990-2008 Info-ZIP - Type 'zip "-L"' for software license.
This is Zip 3.0 (July 5th 2008), by Info-ZIP.
Currently maintained by E. Gordon.  Please send bug reports to
the authors using the web page at www.info-zip.org; see README for details.
Latest sources and executables are at ftp://ftp.info-zip.org/pub/infozip,
as of above date; see http://www.info-zip.org/ for other sites.
Compiled with gcc 4.8.2 for Unix (Linux ELF) on Oct 21 2013.
Zip special compilation options:
USE_EF_UT_TIME       (store Universal Time)
BZIP2_SUPPORT        (bzip2 library version 1.0.6, 6-Sept-2010)
bzip2 code and library copyright (c) Julian R Seward
(See the bzip2 license for terms of use)
SYMLINK_SUPPORT      (symbolic links supported)
LARGE_FILE_SUPPORT   (can read and write large files on file system)
ZIP64_SUPPORT        (use Zip64 to store large files in archives)
UNICODE_SUPPORT      (store and read UTF-8 Unicode paths)
STORE_UNIX_UIDs_GIDs (store UID/GID sizes/values using new extra field)
UIDGID_NOT_16BIT     (old Unix 16-bit UID/GID extra field not used)
[encryption, version 2.91 of 05 Jan 2007] (modified for Zip 3)
Encryption notice:
The encryption code of this program is not copyrighted and is
put in the public domain.  It was originally written in Europe
and, to the best of our knowledge, can be freely distributed
in both source and object forms from any country, including
the USA under License Exception TSU of the U.S. Export
Administration Regulations (section 740.13(e)) of 6 June 2002.
Zip environment options:
ZIP:  [none]
ZIPOPT:  [none]
vim version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 24 2016 16:43:18)
Included patches: 1-52
Extra patches: 8.0.0056
Modified by<EMAIL_ADDRESS>Compiled by buildd@
Huge version without GUI.  Features included (+) or not (-):
+acl             +farsi           +mouse_netterm   +syntax
+arabic          +file_in_path    +mouse_sgr       +tag_binary
+autocmd         +find_in_path    -mouse_sysmouse  +tag_old_static
-balloon_eval    +float           +mouse_urxvt     -tag_any_white
-browse          +folding         +mouse_xterm     -tcl
++builtin_terms  -footer          +multi_byte      +terminfo
+byte_offset     +fork()          +multi_lang      +termresponse
+cindent         +gettext         -mzscheme        +textobjects
-clientserver    -hangul_input    +netbeans_intg   +title
-clipboard       +iconv           +path_extra      -toolbar
+cmdline_compl   +insert_expand   -perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    +keymap          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python          +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con      -lua             +rightleft       +windows
+diff            +menu            -ruby            +writebackup
+digraphs        +mksession       +scrollbind      -X11
-dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     -xim
+emacs_tags      -mouseshape      -sniff           -xsmp
+eval            +mouse_dec       +startuptime     -xterm_clipboard
+ex_extra        +mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    -xpm
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim        -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl    -L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions
iptables version
iptables v1.4.21
curl version
curl 7.35.0 (x86_64-pc-linux-gnu) libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
wget version
GNU Wget 1.15 built on linux-gnu.
rsync version
rsync  version 3.1.0  protocol version 31
gimme version
v1.2.0
nvm version
0.33.2
perlbrew version
/home/travis/perl5/perlbrew/bin/perlbrew  - App::perlbrew/0.80
phpenv version
rbenv 1.1.1-4-g4ebd1bd
rvm version
rvm 1.29.2 (latest) by Michal Papis, Piotr Kuczynski, Wayne E. Seguin [https://rvm.io/]
default ruby version
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
CouchDB version
couchdb 1.6.1
ElasticSearch version
5.5.0
Installed Firefox version
firefox 55.0.2
MongoDB version
MongoDB 3.2.16
Pre-installed PostgreSQL versions
9.2.22
9.3.18
9.4.13
9.5.8
9.6.4
RabbitMQ Version
3.6.11
Redis version
redis-server 4.0.1
riak version
2.2.3
Pre-installed Go versions
1.7.4
ant version
Apache Ant(TM) version 1.9.3 compiled on April 8 2014
mvn version
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T19:39:06Z)
Maven home: /usr/local/maven-3.5.0
Java version: 1.8.0_144, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-81-generic", arch: "amd64", family: "unix"
gradle version

Gradle 4.0.1
Build time:   2017-07-07 14:02:41 UTC
Revision:     38e5dc0f772daecca1d2681885d3d85414eb6826
Groovy:       2.4.11
Ant:          Apache Ant(TM) version 1.9.6 compiled on June 29 2015
JVM:          1.8.0_144 (Oracle Corporation 25.144-b01)
OS:           Linux 4.4.0-81-generic amd64
lein version
WARNING: You're currently running as root; probably by accident.
Press control-C to abort or Enter to continue as root.
Set LEIN_ROOT to disable this warning.
Leiningen 2.7.1 on Java 1.8.0_144 Java HotSpot(TM) 64-Bit Server VM
Pre-installed Node.js versions
v4.8.4
v6.11.2
v6.9.4
v7.4.0
v8.4
phpenv versions
system
5.6

5.6.31 (set by /home/travis/.phpenv/version)
7.0
7.0.22
hhvm
hhvm-stable
composer --version
Composer version 1.4.2 2017-05-17 08:17:52
Pre-installed Ruby versions
ruby-2.2.7
ruby-2.3.4
ruby-2.4.1
travis_fold:end:system_info

removed ‘/etc/apt/sources.list.d/basho_riak.list’
Executing: /tmp/tmp.RhR32dJ0kj/gpg.1.sh --keyserver
hkp://keyserver.ubuntu.com:80
--recv
EA312927
gpg: requesting key EA312927 from hkp server keyserver.ubuntu.com
gpg: key EA312927: "MongoDB 3.2 Release Signing Key<EMAIL_ADDRESS>1 new signature
gpg: Total number processed: 1
gpg:         new signatures: 1
W: http://dl.hhvm.com/ubuntu/dists/trusty/InRelease: Signature by key 36AEF64D0207E7EEE352D4875A16E7281BE7A449 uses weak digest algorithm (SHA1)
W: http://ppa.launchpad.net/couchdb/stable/ubuntu/dists/trusty/Release.gpg: Signature by key 15866BAFD9BCC4F3C1E0DFC7D69548E1C17EAB57 uses weak digest algorithm (SHA1)
travis_fold:start:git.checkout
travis_time:start:09dca95c
$ git clone --depth=50 --branch=2.2.1 https://github.com/posterior/distributions.git posterior/distributions
Cloning into 'posterior/distributions'...
remote: Counting objects: 1087, done.

Note: checking out '9895f413e96681ff68b1aa4c5693b1385421394e'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
travis_time:end:09dca95c:start=1509942300056845581,finish=1509942300766065593,duration=709220012
$ cd posterior/distributions
$ git checkout -qf 2.2.1
travis_fold:end:git.checkout

Setting environment variables from .travis.yml
$ export FLAVOR=_cc
$ export DISTRIBUTIONS_USE_PROTOBUF=1
travis_time:start:02d38637
$ source ~/virtualenv/python2.7_with_system_site_packages/bin/activate
travis_time:end:02d38637:start=1509942300789750965,finish=1509942300796661104,duration=6910139
$ python --version
Python 2.7.6
$ pip --version
pip 9.0.1 from /home/travis/virtualenv/python2.7_with_system_site_packages/local/lib/python2.7/site-packages (python 2.7)
travis_fold:start:before_install.1
travis_time:start:214ed71c
$ pip uninstall numpy -y || echo 'numpy not installed'
Uninstalling numpy-1.13.1:
Successfully uninstalled numpy-1.13.1
travis_time:end:214ed71c:start=1509942301387531675,finish=1509942301914607143,duration=527075468
travis_fold:end:before_install.1
travis_fold:start:before_install.2
travis_time:start:1f0ea6fe
$ sudo add-apt-repository -y ppa:cython-dev/master-ppa
gpg: keyring /tmp/tmpbbvsj2tp/secring.gpg' created gpg: keyring /tmp/tmpbbvsj2tp/pubring.gpg' created
gpg: requesting key 6CA77592 from hkp server keyserver.ubuntu.com
gpg: /tmp/tmpbbvsj2tp/trustdb.gpg: trustdb created
gpg: key 6CA77592: public key "Launchpad PPA for Cython-dev" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
OK
travis_time:end:1f0ea6fe:start=1509942301919284233,finish=1509942304463991089,duration=2544706856
travis_fold:end:before_install.2
travis_fold:start:before_install.3
travis_time:start:1846d640
$ sudo apt-get update -qq
W: http://dl.hhvm.com/ubuntu/dists/trusty/InRelease: Signature by key 36AEF64D0207E7EEE352D4875A16E7281BE7A449 uses weak digest algorithm (SHA1)
W: http://ppa.launchpad.net/couchdb/stable/ubuntu/dists/trusty/Release.gpg: Signature by key 15866BAFD9BCC4F3C1E0DFC7D69548E1C17EAB57 uses weak digest algorithm (SHA1)
travis_time:end:1846d640:start=1509942304468827416,finish=1509942308702620995,duration=4233793579
travis_fold:end:before_install.3
travis_fold:start:before_install.4
travis_time:start:008589b4
$ sudo apt-get install -qq cython python-numpy python-scipy
Selecting previously unselected package libamd2.3.1:amd64.
(Reading database ...

Preparing to unpack .../libamd2.3.1_1%3a4.2.1-3ubuntu1_amd64.deb ...
Unpacking libamd2.3.1:amd64 (1:4.2.1-3ubuntu1) ...
Selecting previously unselected package libcamd2.3.1:amd64.
Preparing to unpack .../libcamd2.3.1_1%3a4.2.1-3ubuntu1_amd64.deb ...
Unpacking libcamd2.3.1:amd64 (1:4.2.1-3ubuntu1) ...
Selecting previously unselected package libccolamd2.8.0:amd64.
Preparing to unpack .../libccolamd2.8.0_1%3a4.2.1-3ubuntu1_amd64.deb ...
Unpacking libccolamd2.8.0:amd64 (1:4.2.1-3ubuntu1) ...
Selecting previously unselected package libblas3.
Preparing to unpack .../libblas3_1.2.20110419-7_amd64.deb ...
Unpacking libblas3 (1.2.20110419-7) ...
Selecting previously unselected package libcolamd2.8.0:amd64.
Preparing to unpack .../libcolamd2.8.0_1%3a4.2.1-3ubuntu1_amd64.deb ...
Unpacking libcolamd2.8.0:amd64 (1:4.2.1-3ubuntu1) ...
Selecting previously unselected package libgfortran3:amd64.
Preparing to unpack .../libgfortran3_4.8.4-2ubuntu1~14.04.3_amd64.deb ...
Unpacking libgfortran3:amd64 (4.8.4-2ubuntu1~14.04.3) ...
Selecting previously unselected package liblapack3.
Preparing to unpack .../liblapack3_3.5.0-2ubuntu1_amd64.deb ...
Unpacking liblapack3 (3.5.0-2ubuntu1) ...
Selecting previously unselected package libcholmod2.1.2:amd64.
Preparing to unpack .../libcholmod2.1.2_1%3a4.2.1-3ubuntu1_amd64.deb ...
Unpacking libcholmod2.1.2:amd64 (1:4.2.1-3ubuntu1) ...
Selecting previously unselected package libumfpack5.6.2:amd64.
Preparing to unpack .../libumfpack5.6.2_1%3a4.2.1-3ubuntu1_amd64.deb ...
Unpacking libumfpack5.6.2:amd64 (1:4.2.1-3ubuntu1) ...
Selecting previously unselected package libwebp5:amd64.
Preparing to unpack .../libwebp5_0.4.0-4_amd64.deb ...
Unpacking libwebp5:amd64 (0.4.0-4) ...
Selecting previously unselected package libwebpmux1:amd64.
Preparing to unpack .../libwebpmux1_0.4.0-4_amd64.deb ...
Unpacking libwebpmux1:amd64 (0.4.0-4) ...
Selecting previously unselected package cython.
Preparing to unpack .../cython_0.20.1+git90-g0e6e38e-1ubuntu2_amd64.deb ...
Unpacking cython (0.20.1+git90-g0e6e38e-1ubuntu2) ...
Selecting previously unselected package python-decorator.
Preparing to unpack .../python-decorator_3.4.0-2build1_all.deb ...
Unpacking python-decorator (3.4.0-2build1) ...
Selecting previously unselected package python-pil.
Preparing to unpack .../python-pil_2.3.0-1ubuntu3.4_amd64.deb ...
Unpacking python-pil (2.3.0-1ubuntu3.4) ...
Selecting previously unselected package python-imaging.
Preparing to unpack .../python-imaging_2.3.0-1ubuntu3.4_all.deb ...
Unpacking python-imaging (2.3.0-1ubuntu3.4) ...
Selecting previously unselected package python-numpy.
Preparing to unpack .../python-numpy_1%3a1.8.2-0ubuntu0.1_amd64.deb ...
Unpacking python-numpy (1:1.8.2-0ubuntu0.1) ...
Selecting previously unselected package python-scipy.
Preparing to unpack .../python-scipy_0.13.3-1build1_amd64.deb ...
Unpacking python-scipy (0.13.3-1build1) ...
Processing triggers for man-db (<IP_ADDRESS>-1ubuntu1) ...
Setting up libamd2.3.1:amd64 (1:4.2.1-3ubuntu1) ...
Setting up libcamd2.3.1:amd64 (1:4.2.1-3ubuntu1) ...
Setting up libccolamd2.8.0:amd64 (1:4.2.1-3ubuntu1) ...
Setting up libblas3 (1.2.20110419-7) ...
update-alternatives: using /usr/lib/libblas/libblas.so.3 to provide /usr/lib/libblas.so.3 (libblas.so.3) in auto mode
Setting up libcolamd2.8.0:amd64 (1:4.2.1-3ubuntu1) ...
Setting up libgfortran3:amd64 (4.8.4-2ubuntu1~14.04.3) ...
Setting up liblapack3 (3.5.0-2ubuntu1) ...
update-alternatives: using /usr/lib/lapack/liblapack.so.3 to provide /usr/lib/liblapack.so.3 (liblapack.so.3) in auto mode
Setting up libcholmod2.1.2:amd64 (1:4.2.1-3ubuntu1) ...
Setting up libumfpack5.6.2:amd64 (1:4.2.1-3ubuntu1) ...
Setting up libwebp5:amd64 (0.4.0-4) ...
Setting up libwebpmux1:amd64 (0.4.0-4) ...
Setting up cython (0.20.1+git90-g0e6e38e-1ubuntu2) ...
Setting up python-decorator (3.4.0-2build1) ...
Setting up python-pil (2.3.0-1ubuntu3.4) ...
Setting up python-imaging (2.3.0-1ubuntu3.4) ...
Setting up python-numpy (1:1.8.2-0ubuntu0.1) ...
Setting up python-scipy (0.13.3-1build1) ...
 Done
Building dependency tree... 0%
Building dependency tree... 0%
Building dependency tree... 50%
Building dependency tree... 50%
Building dependency tree
Reading state information... 0%
Reading state information... 0%
Reading state information... Done
The following additional packages will be installed:
libprotobuf-lite8 libprotobuf8
Suggested packages:
libeigen3-doc libmrpt-dev
The following NEW packages will be installed:
libeigen3-dev libprotobuf-dev libprotobuf-lite8 libprotobuf8
0 upgraded, 4 newly installed, 0 to remove and 106 not upgraded.
Need to get 1,264 kB of archives.
After this operation, 8,447 kB of additional disk space will be used.
0% [Working]
Get:1 http://us-central1.gce.archive.ubuntu.com/ubuntu trusty/main amd64 libprotobuf-lite8 amd64 2.5.0-9ubuntu1 [52.7 kB]
1% [1 libprotobuf-lite8 8,192 B/52.7 kB 16%]
8% [Working]
Get:2 http://us-central1.gce.archive.ubuntu.com/ubuntu trusty/main amd64 libprotobuf8 amd64 2.5.0-9ubuntu1 [296 kB]
9% [2 libprotobuf8 8,042 B/296 kB 3%]
32% [Working]
Get:3 http://us-central1.gce.archive.ubuntu.com/ubuntu trusty/universe amd64 libeigen3-dev all 3.2.0-8 [494 kB]
33% [3 libeigen3-dev 12.3 kB/494 kB 2%]
68% [Working]
Get:4 http://us-central1.gce.archive.ubuntu.com/ubuntu trusty/main amd64 libprotobuf-dev amd64 2.5.0-9ubuntu1 [421 kB]
69% [4 libprotobuf-dev 7,496 B/421 kB 2%]
100% [Working]
Fetched 1,264 kB in 0s (38.6 MB/s)
Selecting previously unselected package libprotobuf-lite8:amd64.
(Reading database ...

Preparing to unpack .../libprotobuf-lite8_2.5.0-9ubuntu1_amd64.deb ...
Unpacking libprotobuf-lite8:amd64 (2.5.0-9ubuntu1) ...
Selecting previously unselected package libprotobuf8:amd64.
Preparing to unpack .../libprotobuf8_2.5.0-9ubuntu1_amd64.deb ...
Unpacking libprotobuf8:amd64 (2.5.0-9ubuntu1) ...
Selecting previously unselected package libeigen3-dev.
Preparing to unpack .../libeigen3-dev_3.2.0-8_all.deb ...
Unpacking libeigen3-dev (3.2.0-8) ...
Selecting previously unselected package libprotobuf-dev:amd64.
Preparing to unpack .../libprotobuf-dev_2.5.0-9ubuntu1_amd64.deb ...
Unpacking libprotobuf-dev:amd64 (2.5.0-9ubuntu1) ...
Setting up libprotobuf-lite8:amd64 (2.5.0-9ubuntu1) ...
Setting up libprotobuf8:amd64 (2.5.0-9ubuntu1) ...
Setting up libeigen3-dev (3.2.0-8) ...
Setting up libprotobuf-dev:amd64 (2.5.0-9ubuntu1) ...
Processing triggers for libc-bin (2.19-0ubuntu6.13) ...
travis_time:end:076f0e50:start=1509942316570843531,finish=1509942318067147477,duration=1496303946
travis_fold:end:before_install.5
travis_fold:start:before_install.6
travis_time:start:1c600c2c
$ pip install cpplint
Collecting cpplint
/home/travis/virtualenv/python2.7_with_system_site_packages/local/lib/python2.7/site-packages/pip/vendor/requests/packages/urllib3/util/ssl.py:318: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/security.html#snimissingwarning.
SNIMissingWarning
/home/travis/virtualenv/python2.7_with_system_site_packages/local/lib/python2.7/site-packages/pip/vendor/requests/packages/urllib3/util/ssl.py:122: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/security.html#insecureplatformwarning.
InsecurePlatformWarning
Downloading cpplint-1.3.0.tar.gz (71kB)

    14% |████▋                           | 10kB 3.8MB/s eta 0:00:01
    28% |█████████▏                      | 20kB 1.9MB/s eta 0:00:01
    42% |█████████████▊                  | 30kB 2.3MB/s eta 0:00:01
    57% |██████████████████▎             | 40kB 2.1MB/s eta 0:00:01
    71% |██████████████████████▉         | 51kB 2.3MB/s eta 0:00:01
    85% |███████████████████████████▍    | 61kB 2.7MB/s eta 0:00:01
    99% |████████████████████████████████| 71kB 3.0MB/s eta 0:00:01
    100% |████████████████████████████████| 81kB 2.7MB/s
Building wheels for collected packages: cpplint
Running setup.py bdist_wheel for cpplint ... - done
  Stored in directory: /home/travis/.cache/pip/wheels/f5/ba/81/00c14f0d4606c2f5de5273d2c35efa6355bb6fa6e5fa8ca104
Successfully built cpplint
Installing collected packages: cpplint
Successfully installed cpplint-1.3.0
travis_time:end:1c600c2c:start=1509942318071501283,finish=1509942319353283188,duration=1281781905
travis_fold:end:before_install.6
travis_fold:start:install.1
travis_time:start:146a5d84
$ make install$FLAVOR
mkdir -p lib
mkdir -p build/python
cd build/python && cmake -DCMAKE_BUILD_TYPE=Python -DCMAKE_INSTALL_PREFIX=/home/travis/virtualenv/python2.7_with_system_site_packages ../..
-- The C compiler identification is GNU 4.8.4
-- The CXX compiler identification is GNU 4.8.4
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CXX_FLAGS = -mfpmath=sse -fPIC -std=c++0x -Wall -Wextra -Werror -Wno-unused-parameter -Wno-strict-aliasing -O3 -msse4.1 -ffast-math -funsafe-math-optimizations
-- Found Eigen3: /usr/include/eigen3 (Required is at least version "2.91.0")
-- Finding YEPPP library
locate: can not stat () `/var/lib/mlocate/mlocate.db': No such file or directory
--   missing YEPPP library
-- Finding AMD LibM library
locate: can not stat () `/var/lib/mlocate/mlocate.db': No such file or directory
--   missing AMD LibM
-- Finding Intel MKL library
locate: can not stat () `/var/lib/mlocate/mlocate.db': No such file or directory
--   missing Intel MKL
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found PROTOBUF: /usr/lib/x86_64-linux-gnu/libprotobuf.so
-- Using Google Protocol Buffers
-- Configuring done
-- Generating done
-- Build files have been written to: /home/travis/build/posterior/distributions/build/python
cd build/python && make
make[1]: Entering directory `/home/travis/build/posterior/distributions/build/python'
make[2]: Entering directory `/home/travis/build/posterior/distributions/build/python'
make[3]: Entering directory `/home/travis/build/posterior/distributions/build/python'
Scanning dependencies of target distributions_shared
make[3]: Leaving directory `/home/travis/build/posterior/distributions/build/python'
make[3]: Entering directory `/home/travis/build/posterior/distributions/build/python'
[  6%] Building CXX object src/CMakeFiles/distributions_shared.dir/io/schema.pb.cc.o
In file included from /home/travis/build/posterior/distributions/src/io/schema.pb.cc:4:0:
/home/travis/build/posterior/distributions/src/../include/distributions/io/schema.pb.h:17:2: error: #error This file was generated by an older version of protoc which is
#error This file was generated by an older version of protoc which is
^
/home/travis/build/posterior/distributions/src/../include/distributions/io/schema.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers. Please
#error incompatible with your Protocol Buffer headers.  Please
^
/home/travis/build/posterior/distributions/src/../include/distributions/io/schema.pb.h:19:2: error: #error regenerate this file with a newer version of protoc.
#error regenerate this file with a newer version of protoc.
^
make[3]: *** [src/CMakeFiles/distributions_shared.dir/io/schema.pb.cc.o] Error 1
make[3]: Leaving directory `/home/travis/build/posterior/distributions/build/python'
make[2]: *** [src/CMakeFiles/distributions_shared.dir/all] Error 2
make[2]: Leaving directory `/home/travis/build/posterior/distributions/build/python'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/travis/build/posterior/distributions/build/python'
make: *** [python_cc] Error 2
travis_time:end:146a5d84:start=1509942319357795598,finish=1509942321608630892,duration=2250835294

The command "make install$FLAVOR" failed and exited with 2 during .
Your build has been stopped.


Enhancement: WP multisites

Hi dear all, i'm trying to squeeze every single bit of juice out from a single heroku dyno.
I tried to install WP multisites under Nginx subdomains.
However, i failed terribly, i cannot seem to write in the correct configurations in the nginx.inc.conf  file.
Has anyone tried to do the same and succeeded? Or any pointers.
I tried using this.

The dyno will listen to any hostname so you should be able to just add domains to your Heroku app then configure the mappings of domains to sites in WP. Having said that I have never run a multisite install so I'm not quite sure if there's anything else that's needed.

+1 I think possible multisite install would be an excellent feature for heroku-wp

i've tried a few other ways to deploy wp since i started this thread, but none seems as easy or as fun as this repo. So far nothing is as fast to provision and edit (at least not aws, not kubernetes or docker). (I am not a coder, just a hobbyist).
Anyway, i did manage to make some headway into this project.

Add the following lines in wp-config.php

/* Multisite */ define( 'WP_ALLOW_MULTISITE', true ); define('MULTISITE', true); define('SUBDOMAIN_INSTALL', false); define('DOMAIN_CURRENT_SITE', 'wpmuats.herokuapp.com'); define('PATH_CURRENT_SITE', '/'); define('SITE_ID_CURRENT_SITE', 1); define('BLOG_ID_CURRENT_SITE', 1);

Log into your wordpress installation and select SUBDIRECTORY INSTALL

Add the following lines to nginx.rewrites.conf

` if (!-e $request_filename) {
rewrite /wp-admin$ $scheme://$host$uri/ permanent;
rewrite ^(/[^/]+)?(/wp-.) $2 last;
rewrite ^(/[^/]+)?(/..php) $2 last;
}
set $cache_uri $request_uri;
# Don't cache uris containing the following segments

if ($request_uri ~* "(/wp-admin/|/xmlrpc.php|/wp-(app|cron|login|register|mail).php|wp-.*.php|/feed/|index.php|wp-comments-popup.php|wp-links-opml.php|wp-locations.php|sitemap(index)?.xml|[a-z0-9-]+-sitemap([0-9]+)?.xml)") {
set $cache_uri 'NULL';
}
# Don't use the cache for logged in users or recent commenters

if ($http_cookie ~* "comment_author|wordpress_[a-f0-9]+|wp-postpass|wordpress_logged_in") {
set $cache_uri 'NULL';
}`

Yay! You can add a few more sites, i think... So far i've only done it with a fresh install, haven't added any users or functions or themes onto it yet.

Next i will try domain mapping probably using this in nginx.inc.conf

server {   ##DM - uncomment following line for domain mapping    #listen 80 default_server;   server_name yourdomain.com;   ##DM - uncomment following line for domain mapping   #server_name_in_redirect off;
I will let u know if i am able to succeed.
References:
Wordpress multisite

Nginx redirect loop

yes, it succeeded! After that just point your whatevercustomdomain.com--> blahblah.herokudns.com and www.whatevercustomdomain.com-->www.blahblah.herokudns.com, then change the WP address of the particular site in the wordpress installation, and thats all!, so easy.
A few catch:

Separate cookie generated for each site. ie. login multiple times, small problem.
Can experience slowing, especially when a lot of things are happening at the same time, i mean, how much can you push 1 heroku dyno? So try to offload everything, S3, SMTP, cron whatever.
Watch the database size, once it reaches 5MB, there will be no warning, just crash and there goes your database. Thanks autobus.io for keeping a copy of my db...

Really having trouble Implementing this one.
Need help


Updated RDS for SQL Server supported versions

Can we also remove the RDS SQL Server "Gotchas and Limitations" that says storage cannot be expanded for existing databases?  That is no longer true.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PIOPS.StorageTypes.html#USER_PIOPS.ModifyingExisting


Creating a new Python ML project is confusing.

Currently there is no "sign" that says that a cookiecutter feature will start instead of creating a the project/solution.
Recommendation 1: Update the text here to say that the cookiecutter feature will start and help guide through the project.

Recommendation 2: The cookiecutter start button should say "create" or "create with wizard", something along those lines. Currently it is confusing that my attempt to create a project is now forcing me to run some random template.

Yeah, we planned for it but I ended up postponing.
https://github.com/Microsoft/PTVS/issues/2989
We should definitely do 1) at a minimum

These names should have Cookiecutter in there somewhere:

Classifier Project (cookiecutter), perhaps?


Adding Agente Milvus Core version <IP_ADDRESS>.

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/issues/128757


Fix generate HRQ CRD from markers

While working on https://github.com/kubernetes-sigs/hierarchical-namespaces/pull/285, I noticed that running make manifests updates the HRQ CRD. This also happens on the master branch, which I think is not intentional and wrong. This PR fixes this by regenerating the HRQ CRD.
The PR also marks the current HRQ as the storage version - which I discovered as missing when comparing the kubebuilder markers for the CRDs.
I think the difference is caused by a minor bug in controller-gen, and is related to the recently added print columns on HRQ. The columns include fields from the HRQ status, and I think there is some code in controller-gen assuming the CRD has a status subresource when including fields from status as print columns.
I really think we should have status as subresources - especially on HRQ, but I don't have the bandwidth to fix that.
/cc @adrianludwin

@erikgb

I think the difference is caused by a minor bug in controller-gen, and is related to the recently added print columns on HRQ.

Thank you for your fix. It may have been caused by my fix #295 ...

I really think we should have status as subresources - especially on HRQ, but I don't have the bandwidth to fix that.

As you may know that, if we make status subresource, we can independently update status field using StatusClient which is member of client.Client.
(ex. we can update only status field using r.Status().Update().)
Although this use case dosn't seems to exist in HNC, it is generally recommended to make status subresource.
So it might be good to do it.

@mochizuki875 We use the status subresource in all other controllers I am involved in, so HNC is quite special in this sense. I have earlier looked at doing this in HNC, and I think it is not a simple task..... But good luck if you make an attempt! 👍

@erikgb
That's for sure.
Although I don't think it's so important task at this point, I'll check the implementation and if it looks doable, I'll do it:)

/lgtm
@adrianludwin ?

/approve


Added TS definition for Router onChange prop

The onChange prop was not mapped in the definitions file. This is a possible change.

Yep! Missed that!


fix: Return early when elastic search provides no query object

Elasticsearch does not return a LoggedQuery object when performance tracking is enabled.
Currently results in a fatal error being produced - This PR fixes that.
To track the Elasticsearch queries this would need a major refactoring.

Thanks, release is now out there.
Also for the next time: You can execute composer cs-fix, composer cs-check and composer stan to get the last CI step to green 😉


Fix SearchPage update headerMessage in debounce.updateOptions

Details

We update headerMessage earlier than sections, which will cause data inconsistency, so we modify to update them at the same time
Fixed Issues

$ https://github.com/Expensify/App/issues/17200
$ https://github.com/Expensify/App/issues/17200#issuecomment-1502612538
Tests

Open the app
Open search
Search for long invalid number eg:<PHONE_NUMBER>111 (1 of 13 repetitions)
Continue to enter a 1 to become<PHONE_NUMBER>1111 (1 of 14 repetitions)
Verify that headerMessage and sections do not appear at the same time

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as the Others

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://user-images.githubusercontent.com/20135674/232930705-0a293504-6154-4bd3-b4b2-3f5ca00664d7.mov

Mobile Web - Chrome

https://user-images.githubusercontent.com/20135674/232930720-8d2f2ea0-469c-4f32-a2f5-7c07938531e0.mp4

Mobile Web - Safari

https://user-images.githubusercontent.com/20135674/232930729-b6584657-1489-4b1c-bb4e-93d961dca350.mp4

Desktop

https://user-images.githubusercontent.com/20135674/232930740-dd3b9333-0bb9-4a43-8cd5-102d7fe53d60.mov

iOS

https://user-images.githubusercontent.com/20135674/232930750-483558d7-9f48-4825-b02b-f4bb34609e1c.mp4

Android

https://user-images.githubusercontent.com/20135674/232930756-f4d2b986-b317-470a-9d06-e429e15f7418.mp4

@chiragsalian @fedirjh One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/chiragsalian in version: 1.3.3-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.3-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


vue-cli-service lint --format junit is unhelpful

Version
4.4.6
Environment info
'vue' is not recognized as an internal or external command, operable program or batch file.

Steps to reproduce
npx vue-cli-service lint --max-warnings 0 --no-fix --silent --format junit > junit.xml
What is expected?
I would expect the junit output to be consistent and helpful to finding which .vue component has linting issues.
Secondary gripe: I would also expect a -o option to output to a file. Output redirection is a pain here because if the tests fail then invalud XML (plain text) is generated.
What is actually happening?
The vue-cli-service lint command creates unhelpful output in junit format. In particular the fact that the name attribzte of a failed testcase is not set to the path is very confusing especially to Azure Devops Pipelines which parse the test results. They show the name attribute and for failed tests this is the eslint rule name. So you see "org.eslint.no-trailing-spaces" but have no idea where that rule was broken.
For passed tests the name attribute is the path to the component - this should always be the case.
<testsuites>
  <testsuite package="org.eslint" time="0" tests="1" errors="0" name="/home/vsts/work/1/s/hybris/bin/custom/applicationstyleguide/src/src/common/components/add-to-template-dropdown/AddToTemplateDropdown.vue">
    <testcase time="0" name="/home/vsts/work/1/s/hybris/bin/custom/applicationstyleguide/src/src/common/components/add-to-template-dropdown/AddToTemplateDropdown.vue" classname="/home/vsts/work/1/s/hybris/bin/custom/applicationstyleguide/src/src/common/components/add-to-template-dropdown/AddToTemplateDropdown" />
  </testsuite>
  <testsuite package="org.eslint" time="0" tests="1" errors="1" name="/home/vsts/work/1/s/hybris/bin/custom/applicationstyleguide/src/src/common/components/buy-box/BuyBox.vue">
    <testcase time="0" name="org.eslint.no-trailing-spaces" classname="/home/vsts/work/1/s/hybris/bin/custom/applicationstyleguide/src/src/common/components/buy-box/BuyBox"><failure message="Trailing spaces not allowed."><![CDATA[line 147, col 23, Error - Trailing spaces not allowed. (no-trailing-spaces)]]></failure></testcase>
  </testsuite>
</testsuites>

More details and screenshots here:
https://github.com/microsoft/azure-pipelines-tasks/issues/13905


docs: add hyperlinks to directories and improve navigation

End-user friendly description of the problem this fixes or functionality that this introduces

[ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

Give a summary of what the PR does, explaining any non-trivial design decisions

Link of any specific issues this addresses

Thank you for the contribution! A few comments.

Thanks for the docs philosophy insight!

@openhands-agent
Would ./tests/runtime be the right link for integration? If not, could you point me in the right direction? IMPORTANT: The only thing you need to do is adding the proper hyperlink for integration in CONTRIBUTING.md.

@young010101 Sorry, if you want to see how fun openhands-agent is in real use, please take a look at this guide to set it up:
OpenHands Github Issue Resolver
It will work on your repositories, or repositories where you have permissions to push. For example, you can set it up and call it - like you did - on your repo https://github.com/young010101/OpenHands

(Lets try with the label!)
Integration tests have been moved out of the tests directory in openhands repo. Find them and fix the CONTRIBUTING.md documentation as pointed out in comments above.

It failed. 🤔
I posted an issue on it: https://github.com/All-Hands-AI/OpenHands/issues/5292
I suspect it failed because your branch is external to the repository (a fork) - for now.
Back to your question: integration tests really were in the same place, near unit tests, but they have been rewritten and moved, and now they are here:
https://github.com/All-Hands-AI/OpenHands/tree/main/evaluation/integration_tests

@young010101 Sorry, if you want to see how fun openhands-agent is in real use, please take a look at this guide to set it up: OpenHands Github Issue Resolver
It will work on your repositories, or repositories where you have permissions to push. For example, you can set it up and call it - like you did - on your repo https://github.com/young010101/OpenHands

Thank you for the clarification and the link to the guide. I'll review the setup steps and see how it works on my repository. Appreciate the guidance!

It failed, lol. 🤔
I posted an issue on it: #5292
I suspect it failed because your branch is external to the repository (a fork) - for now, that doesn't seem to work.
Back to your question: integration tests were in the same place, indeed a part of /tests, but they have been rewritten and moved, and now they are here: https://github.com/All-Hands-AI/OpenHands/tree/main/evaluation/integration_tests

Thanks for identifying the issue and sharing the new location of the integration tests! I’ll adjust my branch and workflow accordingly.


How would I use huggingface models?

I was told this library would work with node.js and is similar to https://github.com/rustformers/llm

There is only RWKV model implemented at the moment. You cannot use it with huggingface models without doing a conversion. Look in the examples/ folder. I will eventually implement more models and add examples there.


Add plugin.toml to silence failure messages on deploy

When I deploy I get errors like the following:
$ g push production master
Total 0 (delta 0), reused 0 (delta 0)
remote: 2015/11/19 12:47:43 open /var/lib/dokku/plugins/available/deployment-keys/plugin.toml: no such file or directory
remote: 2015/11/19 12:47:43 open /var/lib/dokku/plugins/available/deployment-keys/plugin.toml: no such file or directory
remote: 2015/11/19 12:47:43 open /var/lib/dokku/plugins/available/hostkeys-plugin/plugin.toml: no such file or directory
-----> Cleaning up...
-----> Building app from herokuish...
-----> Adding BUILD_ENV to build environment...
remote: 2015/11/19 12:47:52 open /var/lib/dokku/plugins/available/deployment-keys/plugin.toml: no such file or directory
remote: 2015/11/19 12:47:52 open /var/lib/dokku/plugins/available/hostkeys-plugin/plugin.toml: no such file or directory
remote: 2015/11/19 12:47:53 open /var/lib/dokku/plugins/available/deployment-keys/plugin.toml: no such file or directory
remote: 2015/11/19 12:47:53 open /var/lib/dokku/plugins/available/hostkeys-plugin/plugin.toml: no such file or directory

So I added a .toml file to make it stop.
I also deleted a redundant command from the examples in the explanation and the readme.

Awesome! Thx.

This still doesn't fix compatibility with dokku 0.4.x. The plugin trigger name changed

I am in the midst of making it compatible, just a little patience while I tame my vagrant box

No worries. I see you merged the other one two after I commented.

Yep, time to dust off the two plugins :)


Broadlink rm3

version 0.64 update on HASSIO docker
broadlink rm3 component stop working with the new release
it disapear broadlink learn command etc.. from the services
errors on about tab:
`Log Details (ERROR)
Mon Feb 26 2018 20:13:00 GMT+0000 (GMT Standard Time)
Error while setting up platform broadlink
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/broadlink/init.py", line 5, in
from Crypto.Cipher import AES
File "/usr/lib/python3.6/site-packages/Crypto/Cipher/init.py", line 3, in
from Crypto.Cipher._mode_ecb import _create_ecb_cipher
File "/usr/lib/python3.6/site-packages/Crypto/Cipher/_mode_ecb.py", line 29, in
from Crypto.Util._raw_api import (load_pycryptodome_raw_lib,
File "/usr/lib/python3.6/site-packages/Crypto/Util/_raw_api.py", line 32, in
from Crypto.Util.py3compat import byte_string
ImportError: cannot import name 'byte_string'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 84, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
return fut.result()
File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result
raise self._exception
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.6/site-packages/homeassistant/components/switch/broadlink.py", line 74, in setup_platform
import broadlink
File "/usr/lib/python3.6/site-packages/broadlink/init.py", line 7, in
import pyaes
ModuleNotFoundError: No module named 'pyaes'`

Probably the same as #12682.

@ahknight thanks for pointing out


Async iterable support?

I think it would be a good idea to include async iterable function support along with regular async function. An example of use case would be streaming large amounts of data from the main process to the renderer process for display. Async iterables are especially important to keep memory usage low when sending large amounts of data between main and renderer process.

Sounds like a great addition, looking forward to your PR :)


Ignored folder is not ignored

Type: Bug
Not sure what's happening here but seems like my ignored folders are actually NOT ignored by git. The first obvious one was the .vscode directory that is added automatically as default but doesn't matter what I add here it still gets listed as tracked.
I have another machine with the same settings (sync) and that one works perfectly. Any idea what's going on? I tried removing git cache, tried different regex patterns but nothing worked so far.

VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:29:14.590Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.87GB (22.72GB free)

Process Argv
--crash-reporter-id 9e80de22-9a8a-4654-872e-69670f9cd8ec

Screen Reader
no

VM
0%

Extensions (50)

Extension
Author (truncated)
Version

better-comments
aar
3.0.2

html-end-tag-labels
ant
0.9.0

vscode-color-picker
Ant
0.0.4

quitcontrol-vscode
art
4.0.0

vscode-custom-css
be5
7.1.0

vscode-log-viewer
ber
0.12.2

vscode-intelephense-client
bme
1.8.2

simple-react-snippets
bur
1.2.7

run-cy
cor
0.1.1

vscode-mysql-client2
cwe
6.0.4

dart-code
Dar
3.54.1

flutter
Dar
3.54.0

vscode-eslint
dba
2.2.6

gitlens
eam
13.1.1

prettier-vscode
esb
9.10.3

auto-close-tag
for
0.5.14

auto-rename-tag
for
0.1.10

vscode-env
Iro
0.1.0

vscode-gutter-preview
kis
0.30.0

vscode-fix-checksums
leh
1.1.0

inline-parameters
lia
0.2.1

vscode-pastery
max
0.0.4

twig-language-2
mbl
0.9.2

rainbow-csv
mec
3.5.0

php-namespace-resolver
Meh
1.1.9

git-graph
mhu
1.30.0

vscode-checkpoints
mic
1.3.3

vscode-language-pack-hu
MS-
1.48.3

isort
ms-
2022.8.0

python
ms-
2022.20.1

vscode-pylance
ms-
2022.12.20

jupyter
ms-
2022.11.1003412109

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.12

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

remote-ssh
ms-
0.94.0

remote-ssh-edit
ms-
0.84.0

remote-explorer
ms-
0.0.3

vsliveshare
ms-
1.0.5788

color-highlight
nau
2.5.0

vetur
oct
0.36.1

material-icon-theme
PKi
4.23.0

vscode-data-preview
Ran
2.3.0

LiveServer
rit
5.7.9

synthwave-vscode
Rob
0.1.15

vscode-cy-helper
She
1.2.2

highlight-matching-tag
vin
0.10.1

php-debug
xde
1.29.1

markdown-all-in-one
yzh
3.5.0

(3 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1cf:30587006
3biah626:30602489
gswce1:30612156
iaj6b796:30613358
89544117:30613380
fim-prod:30623723
vscsbc:30628655

@bodydisplaynone, the git.ignoredRepositories setting that you are highlighting in your screenshot is meant to contain a list of git repositories that should be ignored by VS Code when scanning for git repositories. It is not meant to ignore folders in a git repository. To ignore folders in a git repository you would have to use a .gitignore file.

@lszomoru thanks for the reply. My main issue is that I have another machine right here, which has the same project opened and VS sync enabled, so technically, they should behave the same. The .gitignore file in the project does not have the .vscode directory added.
My new machine lists the launch.json as pictured above. My old machine does not, as if it's ignoring the folder properly for some reason. I'm wondering if there is another setting I do not see, maybe a global .gitignore config I added back in the day to exclude this folder from ALL git projects but I don't remember, so every help is appreciated. I also checked my old machine if there is a .gitignore file under userprofile/config/git but I do not.

@bodydisplaynone, the contents of the "Source Control" view are rendered based on the output of the git status command. Could you open a terminal window on both machines, navigate to the folder and execute git status -uall in both and see if the output matches. You can also check the value of the git.untrackedChanges setting as that also has an impact on how untracked changes are being shown in the "Source Control" view.

I literally checked all the settings you mentioned. All settings are the same on both machines.
The new machine lists launch.json as untracked when calling git status.
The old machine says no changes.
At this point, I have zero ideas what I did on the old machine to make git "forget" and untrack this file/folder. For now, I added the folder to the .git exclude within the project. The old machine has no entries in this file at all. My idea is still that somehow I added that folder as a global ignore or something, but not sure how or where I did it back in the day.

Thanks again for your help and being so responsive! Because it's not really a bug according to the above, more like a git-related question or setting, I'm closing this issue.


arping: 2.21 -> 2.22

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/arping/versions.
meta.description for arping is: "Broadcasts a who-has ARP packet on the network and prints answers"
meta.homepage for arping is: "https://github.com/ThomasHabets/arping"
meta.changelog for arping is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/39zflsz7hssy0vg2845mybnln3wwcfc4-arping-2.22/bin/arping passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 2.22 with grep in /nix/store/39zflsz7hssy0vg2845mybnln3wwcfc4-arping-2.22

found 2.22 in filename of file in /nix/store/39zflsz7hssy0vg2845mybnln3wwcfc4-arping-2.22

directory tree listing: https://gist.github.com/9ceed182587616251925ebcefb5d365d

du listing: https://gist.github.com/9ab49bdf01e73b7cc7841288590399a4

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
arping

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/39zflsz7hssy0vg2845mybnln3wwcfc4-arping-2.22 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A arping https://github.com/r-ryantm/nixpkgs/archive/219b69ed9ec991df9128aa45427b5f617fc66c14.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/39zflsz7hssy0vg2845mybnln3wwcfc4-arping-2.22
ls -la /nix/store/39zflsz7hssy0vg2845mybnln3wwcfc4-arping-2.22/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

arping

Maintainer pings
cc @michalrus for testing.

Result of nixpkgs-review pr 128752 run on x86_64-linux 1

1 package built:

arping


[WIP] render: Halt logic on undefined table name.

This prevents a long-standing, seemingly non-deterministic error that caused the poll widget to appear to sometimes fail to render.
But because it is only the recent topics list that excludes a table name, and because no messages are rendered in the recent conversations view, it makes sense to avoid the processing overhead incurred by going through the motions of rendering a message view that never actually makes it into the DOM.
CZO discussion

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Closing in favor of https://github.com/zulip/zulip/pull/27110 for this bug.


handle IOT events with raw payload

Is it possible to receive IOT events with raw payload? I am able to receive events with JSON payload but in my use case I want to process IOT messages that contain a raw (binary payload) which doesn't seem possible now?
If I use []byte for the event type instead of a JSON struct, I'm getting this error message:
json: cannot unmarshal object into Go value of type []uint8: UnmarshalTypeError

To clarify, this works:
type IoTEvent struct {
    A   string `json:"a"`
    B   string `json:"b"`
}
func router(ctx context.Context, event IoTEvent) { ... }

And this doesn't work:
func router(ctx context.Context, event []byte) { ... }

Got it to work by using this SELECT rule: SELECT encode(*, 'base64') AS a FROM 'my-topic'
This will encode the raw payload as base64 which then is accessible in lambda as event.A.
Closing.

Hi @dschnabel , could you provide an example code , please ! Im really new on this and Im facing the same problem . Thanks in advance !

@Marcelo-Rodriguez-Teracode
Is this helpful?


Support Groovy DSL

this is very controversial issue, because plugin source is written in Kotlin so that it is perfectly working with Kotlin DSL.
however  method signatures need to be adapted to be working with both Groovy DSL and Kotlin DSL (by using actions, with SAM annotations  / @HasImplicitReceiver / supported by Kotlin compiler).
e.g when we have
fun someService(options: SomeService.() ->Unit) = someService.apply(options)
then it is needed to be replaced by:
fun someService(options: Action<in SomeService>) = someService.apply { Actions.with(options) }
all methods containing lambas in GAP source (param: MyClass.() -> Unit) need to be rewritten in above manner.
when rewritten method is used internally somewhere, the more code could be affected / need adaptation.

GAP currently is highly configurable, there are many hooks / lambdas (209) that could be passed

I am worried if  number of such points to refactored worth costs of further maintenance of supporting / testing 2 DSL's

@sabberworm upvoted for adding support or maybe for agreeing that's not trivial? :)

found nice feature https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.jvm/-jvm-overloads/index.html
adding that to methods with default values make them callable via groovy
adding second method signature e.g

    @Nested
    val vaultDefinition = VaultDefinition(aem)

    fun vaultDefinition(options: VaultDefinition.() -> Unit) {
        vaultDefinition.apply(options)
    }

    fun vaultDefinition(action: Action<in VaultDefinition>) = action.execute(vaultDefinition)

makes it callable in both kotlin and groovy

GAP, GEP are now even more complex so closing / effort not worth it


bug(installer): Ansible failures on Ubuntu 18.04

Issue/Feature Description:
I had some ansible errors following the QuickStart Guide:

https://docs.sodafoundation.io/soda-gettingstarted/quickstart/

I handled one in the documentation:

https://github.com/sodafoundation/documentation/pull/109

This issue discusses the failed keystone task:
Why this issue to fixed / feature is needed(give scenarios or use cases):
Quickstart - running the installer.
  Aborti
ng..."]}
        to retry, use: --limit @/home/vagrant/installer-v1.0.0/ansible/site.retry

PLAY RECAP ***************************************************************************************************************************************************
localhost                  : ok=16   changed=6    unreachable=0    failed=1

root@ubuntu1804:~/installer-v1.0.0/ansible# ansible-playbook site.yml -i local.hosts
Segmentation fault
root@ubuntu1804:~/installer-v1.0.0/ansible# ansible-playbook site.yml -i local.hosts
Segmentation fault

root@ubuntu1804:~/installer-v1.0.0/ansible# ansible --version
Segmentation fault

Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)

Full log attached:
soda-quickstart-failures-ubuntu18-full-log.log


west.yml: Update hal_silabs module to SiLabs SDK v2.7.3

This commit updates west.yml to point hal_silabs module to SiLabs SDK v2.7.3.
Depends on zephyrproject-rtos/hal_silabs/pull/5.

Shippable failed due to EFM32HG series SoCs including the following in the device header file (e.g. Device/SiliconLabs/EFM32HG/Include/efm32hg308f64.h)
#define ARM_MATH_CM0PLUS
#include "arm_math.h"     /* To get __CLZ definitions etc. */

arm_math.h is part of CMSIS-DSP library which is not included in the list of Zephyr modules.
As the comment suggests arm_math.h was included to get __CLZ, however __CLZ is provided by the standard CMSIS library and not CMSIS-DSP. The fact that arm_math.h is included at all is likely an error. Especially that EFM32HG series is the only one doing so. I'll double check with my contact at Silabs unless someone form SiLabs team (@stevew817) will comment first. Most likely it will be enough to patch the header files.

As the comment suggests arm_math.h was included to get __CLZ, however __CLZ is provided by the standard CMSIS library and not CMSIS-DSP. The fact that arm_math.h is included at all is likely an error.

https://github.com/zephyrproject-rtos/cmsis/blob/a2b82e79bd8ac156fb283d5f52fa0a2373962cf9/CMSIS/Core/Include/cmsis_gcc.h#L1078
__CLZ is indeed provided by CMSIS-Core, and there is no need to include a CMSIS-DSP header just to get that.
FYI, if it does require CMSIS-DSP for whatever reason though, this is currently WIP (#21600).

As the comment suggests arm_math.h was included to get __CLZ, however __CLZ is provided by the standard CMSIS library and not CMSIS-DSP. The fact that arm_math.h is included at all is likely an error.

This was also an issue in the previously/currenlty used gecko sdk, see commit https://github.com/zephyrproject-rtos/hal_silabs/commit/fca4c5a0e8a1f8087e011fc9243f998ff5fc71fd
Maybe this was necessary for an older CMSIS version?