Given a pathname for a file, open() returns a file descriptor, a
       small, nonnegative integer for use in subsequent system calls
       (read(2), write(2), lseek(2), fcntl(2), etc.).  The file descriptor
       returned by a successful call will be the lowest-numbered file
       descriptor not currently open for the process.

       By default, the new file descriptor is set to remain open across an
       execve(2) (i.e., the FD_CLOEXEC file descriptor flag described in
       fcntl(2) is initially disabled); the O_CLOEXEC flag, described below,
       can be used to change this default.  The file offset is set to the
       beginning of the file (see lseek(2)).

       A call to open() creates a new open file description, an entry in the
       system-wide table of open files.  The open file description records
       the file offset and the file status flags (see below).  A file
       descriptor is a reference to an open file description; this reference
       is unaffected if pathname is subsequently removed or modified to
       refer to a different file.  For further details on open file
       descriptions, see NOTES.

       The argument flags must include one of the following access modes:
       O_RDONLY, O_WRONLY, or O_RDWR.  These request opening the file read-
       only, write-only, or read/write, respectively.

       In addition, zero or more file creation flags and file status flags
       can be bitwise-or'd in flags.  The file creation flags are O_CLOEXEC,
       O_CREAT, O_DIRECTORY, O_EXCL, O_NOCTTY, O_NOFOLLOW, O_TMPFILE, and
       O_TRUNC.  The file status flags are all of the remaining flags listed
       below.  The distinction between these two groups of flags is that the
       file creation flags affect the semantics of the open operation
       itself, while the file status flags affect the semantics of
       subsequent I/O operations.  The file status flags can be retrieved
       and (in some cases) modified; see fcntl(2) for details.

       The full list of file creation flags and file status flags is as
       follows:

       O_APPEND
              The file is opened in append mode.  Before each write(2), the
              file offset is positioned at the end of the file, as if with
              lseek(2).  The modification of the file offset and the write
              operation are performed as a single atomic step.

              O_APPEND may lead to corrupted files on NFS filesystems if
              more than one process appends data to a file at once.  This is
              because NFS does not support appending to a file, so the
              client kernel has to simulate it, which can't be done without
              a race condition.

       O_ASYNC
              Enable signal-driven I/O: generate a signal (SIGIO by default,
              but this can be changed via fcntl(2)) when input or output
              becomes possible on this file descriptor.  This feature is
              available only for terminals, pseudoterminals, sockets, and
              (since Linux 2.6) pipes and FIFOs.  See fcntl(2) for further
              details.  See also BUGS, below.

       O_CLOEXEC (since Linux 2.6.23)
              Enable the close-on-exec flag for the new file descriptor.
              Specifying this flag permits a program to avoid additional
              fcntl(2) F_SETFD operations to set the FD_CLOEXEC flag.

              Note that the use of this flag is essential in some
              multithreaded programs, because using a separate fcntl(2)
              F_SETFD operation to set the FD_CLOEXEC flag does not suffice
              to avoid race conditions where one thread opens a file
              descriptor and attempts to set its close-on-exec flag using
              fcntl(2) at the same time as another thread does a fork(2)
              plus execve(2).  Depending on the order of execution, the race
              may lead to the file descriptor returned by open() being
              unintentionally leaked to the program executed by the child
              process created by fork(2).  (This kind of race is in
              principle possible for any system call that creates a file
              descriptor whose close-on-exec flag should be set, and various
              other Linux system calls provide an equivalent of the
              O_CLOEXEC flag to deal with this problem.)

       O_CREAT
              If the file does not exist, it will be created.

              The owner (user ID) of the new file is set to the effective
              user ID of the process.

              The group ownership (group ID) of the new file is set either
              to the effective group ID of the process (System V semantics)
              or to the group ID of the parent directory (BSD semantics).
              On Linux, the behavior depends on whether the set-group-ID
              mode bit is set on the parent directory: if that bit is set,
              then BSD semantics apply; otherwise, System V semantics apply.
              For some filesystems, the behavior also depends on the
              bsdgroups and sysvgroups mount options described in mount(8)).

              The mode argument specifies the file mode bits be applied when
              a new file is created.  This argument must be supplied when
              O_CREAT or O_TMPFILE is specified in flags; if neither O_CREAT
              nor O_TMPFILE is specified, then mode is ignored.  The
              effective mode is modified by the process's umask in the usual
              way: in the absence of a default ACL, the mode of the created
              file is (mode & ~umask).  Note that this mode applies only to
              future accesses of the newly created file; the open() call
              that creates a read-only file may well return a read/write
              file descriptor.

              The following symbolic constants are provided for mode:

              S_IRWXU  00700 user (file owner) has read, write, and execute
                       permission

              S_IRUSR  00400 user has read permission

              S_IWUSR  00200 user has write permission

              S_IXUSR  00100 user has execute permission

              S_IRWXG  00070 group has read, write, and execute permission

              S_IRGRP  00040 group has read permission

              S_IWGRP  00020 group has write permission

              S_IXGRP  00010 group has execute permission

              S_IRWXO  00007 others have read, write, and execute permission

              S_IROTH  00004 others have read permission

              S_IWOTH  00002 others have write permission

              S_IXOTH  00001 others have execute permission

              According to POSIX, the effect when other bits are set in mode
              is unspecified.  On Linux, the following bits are also honored
              in mode:

              S_ISUID  0004000 set-user-ID bit

              S_ISGID  0002000 set-group-ID bit (see inode(7)).

              S_ISVTX  0001000 sticky bit (see inode(7)).

       O_DIRECT (since Linux 2.4.10)
              Try to minimize cache effects of the I/O to and from this
              file.  In general this will degrade performance, but it is
              useful in special situations, such as when applications do
              their own caching.  File I/O is done directly to/from user-
              space buffers.  The O_DIRECT flag on its own makes an effort
              to transfer data synchronously, but does not give the
              guarantees of the O_SYNC flag that data and necessary metadata
              are transferred.  To guarantee synchronous I/O, O_SYNC must be
              used in addition to O_DIRECT.  See NOTES below for further
              discussion.

              A semantically similar (but deprecated) interface for block
              devices is described in raw(8).

       O_DIRECTORY
              If pathname is not a directory, cause the open to fail.  This
              flag was added in kernel version 2.1.126, to avoid denial-of-
              service problems if opendir(3) is called on a FIFO or tape
              device.

       O_DSYNC
              Write operations on the file will complete according to the
              requirements of synchronized I/O data integrity completion.

              By the time write(2) (and similar) return, the output data has
              been transferred to the underlying hardware, along with any
              file metadata that would be required to retrieve that data
              (i.e., as though each write(2) was followed by a call to
              fdatasync(2)).  See NOTES below.

       O_EXCL Ensure that this call creates the file: if this flag is
              specified in conjunction with O_CREAT, and pathname already
              exists, then open() will fail.

              When these two flags are specified, symbolic links are not
              followed: if pathname is a symbolic link, then open() fails
              regardless of where the symbolic link points to.

              In general, the behavior of O_EXCL is undefined if it is used
              without O_CREAT.  There is one exception: on Linux 2.6 and
              later, O_EXCL can be used without O_CREAT if pathname refers
              to a block device.  If the block device is in use by the
              system (e.g., mounted), open() fails with the error EBUSY.

              On NFS, O_EXCL is supported only when using NFSv3 or later on
              kernel 2.6 or later.  In NFS environments where O_EXCL support
              is not provided, programs that rely on it for performing
              locking tasks will contain a race condition.  Portable
              programs that want to perform atomic file locking using a
              lockfile, and need to avoid reliance on NFS support for
              O_EXCL, can create a unique file on the same filesystem (e.g.,
              incorporating hostname and PID), and use link(2) to make a
              link to the lockfile.  If link(2) returns 0, the lock is
              successful.  Otherwise, use stat(2) on the unique file to
              check if its link count has increased to 2, in which case the
              lock is also successful.

       O_LARGEFILE
              (LFS) Allow files whose sizes cannot be represented in an
              off_t (but can be represented in an off64_t) to be opened.
              The _LARGEFILE64_SOURCE macro must be defined (before
              including any header files) in order to obtain this
              definition.  Setting the _FILE_OFFSET_BITS feature test macro
              to 64 (rather than using O_LARGEFILE) is the preferred method
              of accessing large files on 32-bit systems (see
              feature_test_macros(7)).

       O_NOATIME (since Linux 2.6.8)
              Do not update the file last access time (st_atime in the
              inode) when the file is read(2).

              This flag can be employed only if one of the following
              conditions is true:

              *  The effective UID of the process matches the owner UID of
                 the file.

              *  The calling process has the CAP_FOWNER capability in its
                 user namespace and the owner UID of the file has a mapping
                 in the namespace.

              This flag is intended for use by indexing or backup programs,
              where its use can significantly reduce the amount of disk
              activity.  This flag may not be effective on all filesystems.
              One example is NFS, where the server maintains the access
              time.

       O_NOCTTY
              If pathname refers to a terminal device—see tty(4)—it will not
              become the process's controlling terminal even if the process
              does not have one.

       O_NOFOLLOW
              If pathname is a symbolic link, then the open fails, with the
              error ELOOP.  Symbolic links in earlier components of the
              pathname will still be followed.  (Note that the ELOOP error
              that can occur in this case is indistinguishable from the case
              where an open fails because there are too many symbolic links
              found while resolving components in the prefix part of the
              pathname.)

              This flag is a FreeBSD extension, which was added to Linux in
              version 2.1.126, and has subsequently been standardized in
              POSIX.1-2008.

              See also O_PATH below.

       O_NONBLOCK or O_NDELAY
              When possible, the file is opened in nonblocking mode.
              Neither the open() nor any subsequent operations on the file
              descriptor which is returned will cause the calling process to
              wait.

              Note that this flag has no effect for regular files and block
              devices; that is, I/O operations will (briefly) block when
              device activity is required, regardless of whether O_NONBLOCK
              is set.  Since O_NONBLOCK semantics might eventually be
              implemented, applications should not depend upon blocking
              behavior when specifying this flag for regular files and block
              devices.

              For the handling of FIFOs (named pipes), see also fifo(7).
              For a discussion of the effect of O_NONBLOCK in conjunction
              with mandatory file locks and with file leases, see fcntl(2).

       O_PATH (since Linux 2.6.39)
              Obtain a file descriptor that can be used for two purposes: to
              indicate a location in the filesystem tree and to perform
              operations that act purely at the file descriptor level.  The
              file itself is not opened, and other file operations (e.g.,
              read(2), write(2), fchmod(2), fchown(2), fgetxattr(2),
              mmap(2)) fail with the error EBADF.

              The following operations can be performed on the resulting
              file descriptor:

              *  close(2); fchdir(2) (since Linux 3.5); fstat(2) (since
                 Linux 3.6).

              *  Duplicating the file descriptor (dup(2), fcntl(2) F_DUPFD,
                 etc.).

              *  Getting and setting file descriptor flags (fcntl(2) F_GETFD
                 and F_SETFD).

              *  Retrieving open file status flags using the fcntl(2)
                 F_GETFL operation: the returned flags will include the bit
                 O_PATH.

              *  Passing the file descriptor as the dirfd argument of
                 openat() and the other "*at()" system calls.  This includes
                 linkat(2) with AT_EMPTY_PATH (or via procfs using
                 AT_SYMLINK_FOLLOW) even if the file is not a directory.

              *  Passing the file descriptor to another process via a UNIX
                 domain socket (see SCM_RIGHTS in unix(7)).

              When O_PATH is specified in flags, flag bits other than
              O_CLOEXEC, O_DIRECTORY, and O_NOFOLLOW are ignored.

              If pathname is a symbolic link and the O_NOFOLLOW flag is also
              specified, then the call returns a file descriptor referring
              to the symbolic link.  This file descriptor can be used as the
              dirfd argument in calls to fchownat(2), fstatat(2), linkat(2),
              and readlinkat(2) with an empty pathname to have the calls
              operate on the symbolic link.

       O_SYNC Write operations on the file will complete according to the
              requirements of synchronized I/O file integrity completion (by
              contrast with the synchronized I/O data integrity completion
              provided by O_DSYNC.)

              By the time write(2) (and similar) return, the output data and
              associated file metadata have been transferred to the
              underlying hardware (i.e., as though each write(2) was
              followed by a call to fsync(2)).  See NOTES below.

       O_TMPFILE (since Linux 3.11)
              Create an unnamed temporary file.  The pathname argument
              specifies a directory; an unnamed inode will be created in
              that directory's filesystem.  Anything written to the
              resulting file will be lost when the last file descriptor is
              closed, unless the file is given a name.

              O_TMPFILE must be specified with one of O_RDWR or O_WRONLY
              and, optionally, O_EXCL.  If O_EXCL is not specified, then
              linkat(2) can be used to link the temporary file into the
              filesystem, making it permanent, using code like the
              following:

                  char path[PATH_MAX];
                  fd = open("/path/to/dir", O_TMPFILE | O_RDWR,
                                          S_IRUSR | S_IWUSR);

                  /* File I/O on 'fd'... */

                  snprintf(path, PATH_MAX,  "/proc/self/fd/%d", fd);
                  linkat(AT_FDCWD, path, AT_FDCWD, "/path/for/file",
                                          AT_SYMLINK_FOLLOW);

              In this case, the open() mode argument determines the file
              permission mode, as with O_CREAT.

              Specifying O_EXCL in conjunction with O_TMPFILE prevents a
              temporary file from being linked into the filesystem in the
              above manner.  (Note that the meaning of O_EXCL in this case
              is different from the meaning of O_EXCL otherwise.)

              There are two main use cases for O_TMPFILE:

              *  Improved tmpfile(3) functionality: race-free creation of
                 temporary files that (1) are automatically deleted when
                 closed; (2) can never be reached via any pathname; (3) are
                 not subject to symlink attacks; and (4) do not require the
                 caller to devise unique names.

              *  Creating a file that is initially invisible, which is then
                 populated with data and adjusted to have appropriate
                 filesystem attributes (fchown(2), fchmod(2), fsetxattr(2),
                 etc.)  before being atomically linked into the filesystem
                 in a fully formed state (using linkat(2) as described
                 above).

              O_TMPFILE requires support by the underlying filesystem; only
              a subset of Linux filesystems provide that support.  In the
              initial implementation, support was provided in the ext2,
              ext3, ext4, UDF, Minix, and shmem filesystems.  Support for
              other filesystems has subsequently been added as follows: XFS
              (Linux 3.15); Btrfs (Linux 3.16); F2FS (Linux 3.16); and ubifs
              (Linux 4.9)

       O_TRUNC
              If the file already exists and is a regular file and the
              access mode allows writing (i.e., is O_RDWR or O_WRONLY) it
              will be truncated to length 0.  If the file is a FIFO or
              terminal device file, the O_TRUNC flag is ignored.  Otherwise,
              the effect of O_TRUNC is unspecified.


yup, that's it!

<img width="1311" alt="screen shot 2017-08-05 at 09 02 52" src="https://user-images.githubusercontent.com/719722/28994073-07fadb52-79bd-11e7-9da1-bcff448063e7.png">


No changes made


global seems fine; I would cast the bool to an int to make it clearer since it wasn't obvious to me that would work at all


close() closes a file descriptor, so that it no longer refers to any
       file and may be reused.  Any record locks (see fcntl(2)) held on the
       file it was associated with, and owned by the process, are removed
       (regardless of the file descriptor that was used to obtain the lock).

       If fd is the last file descriptor referring to the underlying open
       file description (see open(2)), the resources associated with the
       open file description are freed; if the file descriptor was the last
       reference to a file which has been removed using unlink(2), the file
       is deleted.


Slightly cleaner if you say something like for letter, count in hand.items()


Huh I didn't know that would do that... I would generally have been more explicit about it by printing a \n directly


Created multidev environment [ci-example-d8-composer#ci-693](https://dashboard.pantheon.io/sites/c401fd14-f745-4e51-9af2-f30b45146a0c#ci-693).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-693-ci-example-d8-composer.pantheonsite.io/)


the for loop elements are super verbose, maybe `auto` can be used on `it` declaration?

So it wasn't an off by one, but an off by `i` error :)


Haha I just realized that some of this is probably helper code... I guess I just disagree


Thanks! x)


Yeah, this is really hard to parse. Can't you just iterate over the values in frequency and update hand directly?


Added Posts CRUD abilities


Hmm another way to do this would be to just get the letter frequency of word (they defined get_frequency_dict for you), and then check that each letter is represented in hand.


You don't need to do list(word) here, strings are iterable


The else is unnecessary here; when there are returns I prefer to avoid them so to avoid the indentation


Wonderful


Whoops this wasn't supposed to sneak in.


Don't you want to use your display_hand helper?


This else is doing nothing


This continue is unnecessary


Are you using this return value at all?


The log is different because it's a newer switch driver in my tree.

Could you capture a log when it auto restarts after a while?


It seems weird since you aren't mutating hand at all, you're passing it in as an argument and then passing it back out. You should be able to maintain that state just fine in the outer function.


You can save the hand here, current_hand = deal_hand(HAND_SIZE)


Unnecessary?


@md678685 Noticed clicking the helmet slot only equips items as a hat in while in survival. Intentional behavior?


Thanks! Build on travis is now green again. :)


My first Git


hello


First commit


@jef-n thanks!


This is a screenshot after integrating LookupFile into 'auto_update_cscope_ctags_database':
![abc](https://user-images.githubusercontent.com/25523678/28994160-2c5a4068-79fa-11e7-8000-ec42a9513c1d.png)


第二次更改


Thank Ur advices!  I have  integrated the 'LookupFile' function to your 'auto_update_cscope_ctags_database' plugin, following details:
![abc](https://user-images.githubusercontent.com/25523678/28993358-0eb10d70-79e7-11e7-8832-e64d1a8452c9.png)
![abc](https://user-images.githubusercontent.com/25523678/28993436-e61bee96-79e8-11e7-83a4-aa01e2d2234f.png)
![abc](https://user-images.githubusercontent.com/25523678/28993449-1834fbb6-79e9-11e7-9f13-81f6c1585621.png)

This is a screenshot after integrating LookupFile into 'auto_update_cscope_ctags_database':
![abc](https://user-images.githubusercontent.com/25523678/28994168-63196598-79fa-11e7-8413-c40130b7fe57.png)


Great, this is also leftover on current 'devel' branch


The objective of this project is to perform linear regression using batch gradient descent manually. Applying iterative batch gradient descent to the house price dataset. The dataset has following columns - house area, the number of bedrooms and price.

Creating a function that takes input as - predictor variables as a data frame, response variable, no. of iterations and alpha (learning rate) and returns theta (coefficients of variables) and Jtheta (cost of each iteration)

Creating a plot to view the cost of each iteration against its coefficients i.e. Jtheta vs theta.


I feel for you. Working late again.
Your knowledge of the code is impressive.


Hi @michaelsauter, I've released [`1.1.3`](https://rubygems.org/gems/elasticsearch/versions/1.1.3) a while ago. Thank you _so much_ for the patience and responsiveness, it is very rare these days :) And thank you very much for the repeated pings!


Can anyone please provide me congig/apikey.php file,


Question here... My understanding is that the recommended practice was to use one logger per function so it's initiated with the function name so logger reports on it.

As we're importing functions like 'docitellus' from magui, this also helped to track the status.

Am I wrong?


darkneo


Woohoo! Thank you so much for pushing a release for such an ancient version!


Thank Ur advices!  I have  integrated the 'LookupFile' function to your 'auto_update_cscope_ctags_database' plugin, following details:

Modified auto_update_cscope_ctags.vim:
![auto_update_vim](https://user-images.githubusercontent.com/25523678/28994256-185cda7e-79fc-11e7-9a19-c177a6b1d318.png)

Modified auto_update_cscope_ctags_backup_run.py:
![run_py](https://user-images.githubusercontent.com/25523678/28994276-b1f123a2-79fc-11e7-89a8-6536129d189e.png)

This is a screenshot after integrating LookupFile into 'auto_update_cscope_ctags_database':
![abc](https://user-images.githubusercontent.com/25523678/28994280-c90fc8c2-79fc-11e7-918e-7dfa108a3394.png)


Thank haolongzhangm's advices! I have integrated the 'LookupFile' function to your 'auto_update_cscope_ctags_database' plugin, following details:

Modified auto_update_cscope_ctags.vim:
![auto_update_vim](https://user-images.githubusercontent.com/25523678/28994293-38c09e9e-79fd-11e7-903c-124feb6aae91.png)

Modified auto_update_cscope_ctags_backup_run.py:
![run_py](https://user-images.githubusercontent.com/25523678/28994295-451ddd82-79fd-11e7-8785-8c9e36361eec.png)

This is a screenshot after integrating LookupFile into 'auto_update_cscope_ctags_database':
![abc](https://user-images.githubusercontent.com/25523678/28994297-52ca634c-79fd-11e7-9570-6c0b81557d93.png)


О да, я когда-то тоже сражался с точностью float-a. Я тогда использовал позиции объектов в double3+origin мира в double3, но это было до Urho.

В Urho же... Не знаю. Можно сэмулировать что-то похожее с помощью сетки корневых нод. Каждая такая нода является родителем для всех объектов в некотором большом регионе. Когда камера сдвигается достаточно далеко от центра, вся сетка смещается в нужную сторону, регионы выгружаются и догружаются. Динамические объекты вверху иерархии стоит периодически пере-привязывать к новым родителям. Это все, скорее всего, придется реализовывать на стороне пользователя, не влезая в ядро.

А вот с навигацией тут проблемка. Я хотел на нее забить до поры до времени, но раз ты вспомнил, подумаю еще. Detour, похоже, не умеет склеивать навмеши по ребрам. А Urho, в довесок к этому, не поддерживает больше одного активного навмеша для CrowdManager. Поэтому тут не получится так просто стримить, как все остальное.


@mibby I'm planning on reworking this PR to work properly in 1.12+ at some point.


`CRYPTO_THREAD_lock_free` is unnecessary here and causes double-free of s->lock


#If you want to write unit test then you code shouldn't have any dependencies. This code shows how to decouple your code to write quality unit tests


@duhon: what is the reason why this setPathInfo method in 2.1.x has diverged so much from the code in 2.2.0-preview or the develop branch? What was the purpose of this change?
We run into issues with multiple query strings being added to the url, because they aren't stripped out properly because of this change.

Let me add some more context:
We tried to backport MAGETWO-64885 onto 2.1.7, so we can get multiple domainnames to work properly with them endlessly redirecting you to another domainname and then back to the original domainname, which MAGETWO-64885 fixes.
But after applying MAGETWO-64885 on 2.1.7, we get incorrect store switcher url's because of the change above, see my comment over here: https://github.com/magento/magento2/commit/508f1ef93558c40f96cc9524e6a205494f90a7ba#commitcomment-23479499

The change above was **not** performed on the develop branch or the 2.2.0-preview branch, so I'm not sure why it was done on 2.1.x ?


2月份正規化忘了做


Just found out that in Magento 2.1.7, the Magento\Framework\App\Request\Http::setPathInfo method has changed drastically, which causes the above issue. See: https://github.com/magento/magento2/commit/a2f289363069605d0d9eb5e4fa7d6cb4198df485#commitcomment-23494452


I don't know how to get the detailed log. but I notice that the wireless is very slow, My net is about 50Mbps, but this can only get 10Mbps. The dmesg:
```
[    0.000000] Linux version 4.9.40 (liao@ubuntu) (gcc version 5.4.0 (LEDE GCC 5.4.0 r0-b3cd66d) ) #0 SMP Thu Aug 3 18:59:11 2017
[    0.000000] CPU: ARMv7 Processor [512f04d0] revision 0 (ARMv7), cr=10c5787d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] OF: fdt:Machine model: Netgear Nighthawk X4S R7800
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 122880
[    0.000000] free_area_init_node: node 0, pgdat c07af340, node_mem_map dda39000
[    0.000000]   Normal zone: 960 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 122880 pages, LIFO batch:31
[    0.000000] percpu: Embedded 13 pages/cpu @dda03000 s21260 r8192 d23796 u53248
[    0.000000] pcpu-alloc: s21260 r8192 d23796 u53248 alloc=13*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 121920
[    0.000000] Kernel command line:
[    0.000000] Bootloader command line (ignored): console=ttyHSL1,115200n8
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 478912K/491520K available (3920K kernel code, 247K rwdata, 1248K rodata, 240K init, 241K bss, 12608K reserved, 0K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xde800000 - 0xff800000   ( 528 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xde000000   ( 480 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0208000 - 0xc05dc498   (3922 kB)
[    0.000000]       .init : 0xc0736000 - 0xc0772000   ( 240 kB)
[    0.000000]       .data : 0xc0772000 - 0xc07afc40   ( 248 kB)
[    0.000000]        .bss : 0xc07b1000 - 0xc07ed6e8   ( 242 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] clocksource: dg_timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 305801671480 ns
[    0.000008] sched_clock: 32 bits at 6MHz, resolution 160ns, wraps every 343597383600ns
[    0.000021] Switching to timer-based delay loop, resolution 160ns
[    0.000248] Calibrating delay loop (skipped), value calculated using timer frequency.. 12.50 BogoMIPS (lpj=62500)
[    0.000270] pid_max: default: 32768 minimum: 301
[    0.000373] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000387] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.001064] CPU: Testing write buffer coherency: ok
[    0.001351] Setting up static identity map for 0x42208280 - 0x422082d8
[    0.004677] Brought up 2 CPUs
[    0.004692] SMP: Total of 2 processors activated (25.00 BogoMIPS).
[    0.004703] CPU: All CPU(s) started in SVC mode.
[    0.018292] VFP support v0.3: implementor 51 architecture 64 part 4d variant 2 rev 0
[    0.018572] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.018595] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.018680] pinctrl core: initialized pinctrl subsystem
[    0.020056] NET: Registered protocol family 16
[    0.020305] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.051773] cpuidle: using governor ladder
[    0.082790] cpuidle: using governor menu
[    0.135604] msm_bus_fabric_init_driver
[    0.136627] usbcore: registered new interface driver usbfs
[    0.136715] usbcore: registered new interface driver hub
[    0.136796] usbcore: registered new device driver usb
[    0.136853] pps_core: LinuxPPS API ver. 1 registered
[    0.136865] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.136897] PTP clock support registered
[    0.138847] clocksource: Switched to clocksource dg_timer
[    0.143568] NET: Registered protocol family 2
[    0.144171] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.144216] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.144275] TCP: Hash tables configured (established 4096 bind 4096)
[    0.144327] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.144349] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.144540] NET: Registered protocol family 1
[    0.144585] PCI: CLS 0 bytes, default 64
[    0.146341] No memory allocated for crashlog
[    0.146702] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[    0.152987] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.153001] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.159689] io scheduler noop registered
[    0.159706] io scheduler deadline registered (default)
[    0.161521] 1b500000.pci supply vdda not found, using dummy regulator
[    0.161621] 1b500000.pci supply vdda_phy not found, using dummy regulator
[    0.161708] 1b500000.pci supply vdda_refclk not found, using dummy regulator
[    0.162449] OF: PCI: host bridge /soc/pci@1b500000 ranges:
[    0.162491] OF: PCI:    IO 0x0fe00000..0x0fefffff -> 0x0fe00000
[    0.162515] OF: PCI:   MEM 0x08000000..0x0fdfffff -> 0x08000000
[    0.270153] qcom-pcie 1b500000.pci: link up
[    0.272299] qcom-pcie 1b500000.pci: PCI host bridge to bus 0000:00
[    0.272322] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.272341] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfe00000-0xfefffff])
[    0.272356] pci_bus 0000:00: root bus resource [mem 0x08000000-0x0fdfffff]
[    0.272372] pci_bus 0000:00: scanning bus
[    0.272426] pci 0000:00:00.0: [17cb:0101] type 01 class 0x060400
[    0.272520] pci 0000:00:00.0: calling pci_fixup_ide_bases+0x0/0x3c
[    0.272596] pci 0000:00:00.0: supports D1
[    0.272605] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    0.272623] pci 0000:00:00.0: PME# disabled
[    0.272932] pci_bus 0000:00: fixups for bus
[    0.272956] PCI: bus0: Fast back to back transfers disabled
[    0.272978] pci 0000:00:00.0: scanning [bus 01-01] behind bridge, pass 0
[    0.273149] pci_bus 0000:01: scanning bus
[    0.273323] pci 0000:01:00.0: [168c:0046] type 00 class 0x028000
[    0.273553] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[    0.274000] pci 0000:01:00.0: calling pci_fixup_ide_bases+0x0/0x3c
[    0.274641] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[    0.274681] pci 0000:01:00.0: PME# disabled
[    0.275055] pci_bus 0000:01: fixups for bus
[    0.275126] PCI: bus1: Fast back to back transfers disabled
[    0.275140] pci_bus 0000:01: bus scan returning with max=01
[    0.275159] pci 0000:00:00.0: scanning [bus 01-01] behind bridge, pass 1
[    0.275175] pci_bus 0000:00: bus scan returning with max=01
[    0.275319] pci 0000:00:00.0: fixup irq: got 136
[    0.275329] pci 0000:00:00.0: assigning IRQ 136
[    0.275410] pci 0000:01:00.0: fixup irq: got 136
[    0.275419] pci 0000:01:00.0: assigning IRQ 136
[    0.275483] pci 0000:00:00.0: BAR 8: assigned [mem 0x08000000-0x081fffff]
[    0.275507] pci 0000:01:00.0: BAR 0: assigned [mem 0x08000000-0x081fffff 64bit]
[    0.275632] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.275653] pci 0000:00:00.0:   bridge window [mem 0x08000000-0x081fffff]
[    0.275694] pci 0000:00:00.0: calling qcom_pcie_fixup_final+0x0/0x88
[    0.276053] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[    0.276070] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[    0.276089] pcie_pme 0000:00:00.0:pcie001: service driver pcie_pme loaded
[    0.276290] aer 0000:00:00.0:pcie002: service driver aer loaded
[    0.276398] pci 0000:01:00.0: calling qcom_pcie_fixup_final+0x0/0x88
[    0.276775] 1b700000.pci supply vdda not found, using dummy regulator
[    0.276873] 1b700000.pci supply vdda_phy not found, using dummy regulator
[    0.276974] 1b700000.pci supply vdda_refclk not found, using dummy regulator
[    0.277705] OF: PCI: host bridge /soc/pci@1b700000 ranges:
[    0.277739] OF: PCI:    IO 0x31e00000..0x31efffff -> 0x31e00000
[    0.277762] OF: PCI:   MEM 0x2e000000..0x31dfffff -> 0x2e000000
[    0.388081] qcom-pcie 1b700000.pci: link up
[    0.390197] qcom-pcie 1b700000.pci: PCI host bridge to bus 0001:00
[    0.390215] pci_bus 0001:00: root bus resource [bus 00-ff]
[    0.390232] pci_bus 0001:00: root bus resource [mem 0x2e000000-0x31dfffff]
[    0.390244] pci_bus 0001:00: scanning bus
[    0.390282] pci 0001:00:00.0: [17cb:0101] type 01 class 0x060400
[    0.390358] pci 0001:00:00.0: calling pci_fixup_ide_bases+0x0/0x3c
[    0.390424] pci 0001:00:00.0: supports D1
[    0.390435] pci 0001:00:00.0: PME# supported from D0 D1 D3hot
[    0.390448] pci 0001:00:00.0: PME# disabled
[    0.390729] pci_bus 0001:00: fixups for bus
[    0.390746] PCI: bus0: Fast back to back transfers disabled
[    0.390764] pci 0001:00:00.0: scanning [bus 01-01] behind bridge, pass 0
[    0.390935] pci_bus 0001:01: scanning bus
[    0.391121] pci 0001:01:00.0: [168c:0046] type 00 class 0x028000
[    0.391361] pci 0001:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[    0.391839] pci 0001:01:00.0: calling pci_fixup_ide_bases+0x0/0x3c
[    0.392531] pci 0001:01:00.0: PME# supported from D0 D3hot D3cold
[    0.392574] pci 0001:01:00.0: PME# disabled
[    0.392950] pci_bus 0001:01: fixups for bus
[    0.393025] PCI: bus1: Fast back to back transfers disabled
[    0.393039] pci_bus 0001:01: bus scan returning with max=01
[    0.393056] pci 0001:00:00.0: scanning [bus 01-01] behind bridge, pass 1
[    0.393072] pci_bus 0001:00: bus scan returning with max=01
[    0.393134] pcieport 0000:00:00.0: fixup irq: got 136
[    0.393143] pcieport 0000:00:00.0: assigning IRQ 136
[    0.393220] pci 0000:01:00.0: fixup irq: got 136
[    0.393229] pci 0000:01:00.0: assigning IRQ 136
[    0.393354] pci 0001:00:00.0: fixup irq: got 169
[    0.393363] pci 0001:00:00.0: assigning IRQ 169
[    0.393444] pci 0001:01:00.0: fixup irq: got 169
[    0.393453] pci 0001:01:00.0: assigning IRQ 169
[    0.393507] pci 0001:00:00.0: BAR 8: assigned [mem 0x2e000000-0x2e1fffff]
[    0.393529] pci 0001:01:00.0: BAR 0: assigned [mem 0x2e000000-0x2e1fffff 64bit]
[    0.393658] pci 0001:00:00.0: PCI bridge to [bus 01]
[    0.393676] pci 0001:00:00.0:   bridge window [mem 0x2e000000-0x2e1fffff]
[    0.393708] pci 0001:00:00.0: calling qcom_pcie_fixup_final+0x0/0x88
[    0.394026] pcieport 0001:00:00.0: Signaling PME through PCIe PME interrupt
[    0.394041] pci 0001:01:00.0: Signaling PME through PCIe PME interrupt
[    0.394059] pcie_pme 0001:00:00.0:pcie001: service driver pcie_pme loaded
[    0.394249] aer 0001:00:00.0:pcie002: service driver aer loaded
[    0.394352] pci 0001:01:00.0: calling qcom_pcie_fixup_final+0x0/0x88
[    0.397167] L2 @ QSB rate. Forcing new rate.
[    0.397360] L2 @ 384000 KHz
[    0.397534] CPU0 @ 800000 KHz
[    0.397547] CPU1 @ QSB rate. Forcing new rate.
[    0.397670] CPU1 @ 384000 KHz
[    0.402986] gsbi 16300000.gsbi: GSBI port protocol: 6 crci: 0
[    0.404488] gsbi 1a200000.gsbi: GSBI port protocol: 3 crci: 0
[    0.406130] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.407172] msm_serial 16340000.serial: msm_serial: detected port #0
[    0.407274] msm_serial 16340000.serial: uartclk = 7372800
[    0.407353] 16340000.serial: ttyMSM0 at MMIO 0x16340000 (irq = 170, base_baud = 460800) is a MSM
[    0.407389] msm_serial: console setup on port #0
[    1.117294] console [ttyMSM0] enabled
[    1.122194] msm_serial: driver initialized
[    1.133724] loop: module loaded
[    1.135761] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xa1
[    1.135795] nand: AMD/Spansion S34MS01G2
[    1.142379] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.146279] 10 ofpart partitions found on MTD device qcom_nand.0
[    1.153644] Creating 10 MTD partitions on "qcom_nand.0":
[    1.159803] 0x000000000000-0x000000c80000 : "qcadata"
[    1.170158] random: fast init done
[    1.187628] 0x000000c80000-0x000001180000 : "APPSBL"
[    1.197689] 0x000001180000-0x000001200000 : "APPSBLENV"
[    1.200691] 0x000001200000-0x000001340000 : "art"
[    1.205940] 0x000001340000-0x000001480000 : "artbak"
[    1.210771] 0x000001480000-0x000001680000 : "kernel"
[    1.217103] 0x000001680000-0x000003480000 : "ubi"
[    1.274462] 0x000003480000-0x000007900000 : "netgear"
[    1.401972] 0x000007900000-0x000008000000 : "reserve"
[    1.416811] 0x000001480000-0x000003480000 : "firmware"
[    1.479849] no rootfs found after FIT image in "firmware"
[    1.481210] spi_qup 1a280000.spi: IN:block:16, fifo:64, OUT:block:16, fifo:64
[    1.486333] m25p80 spi32766.0: unrecognized JEDEC id bytes: 00, 00, 00
[    1.491483] m25p80: probe of spi32766.0 failed with error -2
[    1.499219] libphy: GPIO Bitbanged MDIO: probed
[    1.513465] mdio_bus gpio-0:10: mdio_device_register
[    1.515277] libphy: Fixed MDIO Bus: probed
[    1.517508] libphy: mdio_driver_register: qca8k
[    1.527395] stmmac - user ID: 0x10, Synopsys ID: 0x37
[    1.527433]  Ring mode enabled
[    1.531545]  DMA HW capability register supported
[    1.534385]  Enhanced/Alternate descriptors
[    1.540145] 	Enabled extended descriptors
[    1.542986]  RX Checksum Offload Engine supported
[    1.547154] 	COE Type 2
[    1.551923]  TX Checksum insertion supported
[    1.554096]  Wake-Up On Lan supported
[    1.558612]  Enable RX Mitigation via HW Watchdog Timer
[    1.564907] stmmac - user ID: 0x10, Synopsys ID: 0x37
[    1.567206]  Ring mode enabled
[    1.572528]  DMA HW capability register supported
[    1.575367]  Enhanced/Alternate descriptors
[    1.581007] 	Enabled extended descriptors
[    1.583963]  RX Checksum Offload Engine supported
[    1.588133] 	COE Type 2
[    1.592908]  TX Checksum insertion supported
[    1.595076]  Wake-Up On Lan supported
[    1.599689]  Enable RX Mitigation via HW Watchdog Timer
[    1.604403] i2c /dev entries driver
[    1.609670] Calibration not found.
[    1.611668] qcom-tsens 900000.thermal-sensor: tsens calibration failed
[    1.616955] Speed bin: 0
[    1.621749] PVS bin: 4
[    1.627009] cpuidle: enable-method property 'qcom,kpss-acc-v1' found operations
[    1.627125] cpuidle: enable-method property 'qcom,kpss-acc-v1' found operations
[    1.634626] sdhci: Secure Digital Host Controller Interface driver
[    1.641114] sdhci: Copyright(c) Pierre Ossman
[    1.647248] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.654556] NET: Registered protocol family 10
[    1.659983] NET: Registered protocol family 17
[    1.662098] 8021q: 802.1Q VLAN Support v1.8
[    1.666168] Registering SWP/SWPB emulation handler
[    1.688325] qcom_rpm 108000.rpm: RPM firmware 3.0.16777364
[    1.711831] s1a: Bringing 0uV into 1050000-1050000uV
[    1.712386] s1b: Bringing 0uV into 1050000-1050000uV
[    1.716367] s2a: Bringing 0uV into 775000-775000uV
[    1.721443] s2b: Bringing 0uV into 775000-775000uV
[    1.727593] DSA: switch 0 0 parsed
[    1.730277] DSA: tree 0 parsed
[    1.890300] libphy: dsa slave smi: probed
[    1.895237] Generic PHY gpio-0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=gpio-0:00, irq=-1)
[    1.899553] Generic PHY dsa-0.0:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=dsa-0.0:01, irq=-1)
[    1.907946] Generic PHY dsa-0.0:02: attached PHY driver [Generic PHY] (mii_bus:phy_addr=dsa-0.0:02, irq=-1)
[    1.917540] Generic PHY dsa-0.0:03: attached PHY driver [Generic PHY] (mii_bus:phy_addr=dsa-0.0:03, irq=-1)
[    1.927252] Generic PHY dsa-0.0:04: attached PHY driver [Generic PHY] (mii_bus:phy_addr=dsa-0.0:04, irq=-1)
[    1.937300] of: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:0, -19
[    1.943449] of: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:1, -19
[    1.952398] UBI: auto-attach mtd6
[    1.958487] ubi0: attaching mtd6
[    1.997989] random: crng init done
[    2.253252] ubi0: scanning is finished
[    2.264441] ubi0: attached mtd6 (name "ubi", size 30 MiB)
[    2.264461] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.268808] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.275654] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.282492] ubi0: good PEBs: 240, bad PEBs: 0, corrupted PEBs: 0
[    2.289276] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    2.295459] ubi0: max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 498806857
[    2.302549] ubi0: available PEBs: 0, total reserved PEBs: 240, PEBs reserved for bad PEB handling: 20
[    2.311609] ubi0: background thread "ubi_bgt0d" started, PID 89
[    2.321316] block ubiblock0_0: created from ubi0:0(rootfs)
[    2.326534] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[    2.332167] hctosys: unable to open rtc device (rtc0)
[    2.342386] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    2.342572] Freeing unused kernel memory: 240K (c0736000 - c0772000)
[    2.348595] This architecture does not have kernel memory protection.
[    2.678060] init: Console is alive
[    2.678168] init: - watchdog -
[    3.609870] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    3.686959] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.692652] SCSI subsystem initialized
[    3.698859] libata version 3.00 loaded.
[    3.704349] ahci 29000000.sata: forcing port_map 0x0 -> 0x1
[    3.704441] ahci 29000000.sata: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode
[    3.708751] ahci 29000000.sata: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
[    3.719222] scsi host0: ahci
[    3.725892] ata1: SATA max UDMA/133 mmio [mem 0x29000000-0x2900017f] port 0x100 irq 95
[    4.062460] ata1: SATA link down (SStatus 0 SControl 300)
[    4.066923] ehci-platform: EHCI generic platform driver
[    4.075300] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.076826] ohci-platform: OHCI generic platform driver
[    4.213688] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    4.213757] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[    4.218295] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228f065 hci version 0x100 quirks 0x02010010
[    4.225819] xhci-hcd xhci-hcd.0.auto: irq 172, io mem 0x11000000
[    4.235483] hub 1-0:1.0: USB hub found
[    4.240860] hub 1-0:1.0: 1 port detected
[    4.244488] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    4.248251] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[    4.253715] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    4.261764] hub 2-0:1.0: USB hub found
[    4.269522] hub 2-0:1.0: 1 port detected
[    4.273343] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    4.277024] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
[    4.282566] xhci-hcd xhci-hcd.1.auto: hcc params 0x0228f065 hci version 0x100 quirks 0x02010010
[    4.289983] xhci-hcd xhci-hcd.1.auto: irq 173, io mem 0x10000000
[    4.299243] hub 3-0:1.0: USB hub found
[    4.304817] hub 3-0:1.0: 1 port detected
[    4.308694] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    4.312513] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
[    4.317821] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    4.325946] hub 4-0:1.0: USB hub found
[    4.333694] hub 4-0:1.0: 1 port detected
[    4.341178] usbcore: registered new interface driver usb-storage
[    4.341331] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    4.353497] init: - preinit -
[    5.336689] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[    5.360887] usb-storage 2-1:1.0: USB Mass Storage device detected
[    5.361079] scsi host1: usb-storage 2-1:1.0
[    6.411735] scsi 1:0:0:0: Direct-Access     Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
[    6.414334] sd 1:0:0:0: [sda] 60555264 512-byte logical blocks: (31.0 GB/28.9 GiB)
[    6.419757] sd 1:0:0:0: [sda] Write Protect is off
[    6.426285] sd 1:0:0:0: [sda] Mode Sense: 45 00 00 00
[    6.426756] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    6.563085]  sda: sda4
[    6.566473] sd 1:0:0:0: [sda] Attached SCSI removable disk
[    8.088739] mount_root: loading kmods from internal overlay
[    8.113515] kmodloader: loading kernel modules from //etc/modules-boot.d/*
[    8.115576] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
[    8.152724] blk_update_request: I/O error, dev mtdblock0, sector 0
[    8.153243] blk_update_request: I/O error, dev mtdblock0, sector 8
[    8.158281] blk_update_request: I/O error, dev mtdblock0, sector 16
[    8.164514] blk_update_request: I/O error, dev mtdblock0, sector 24
[    8.170876] blk_update_request: I/O error, dev mtdblock0, sector 0
[    8.176367] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[    8.184220] blk_update_request: I/O error, dev mtdblock1, sector 0
[    8.190636] blk_update_request: I/O error, dev mtdblock1, sector 8
[    8.196770] blk_update_request: I/O error, dev mtdblock1, sector 16
[    8.203012] blk_update_request: I/O error, dev mtdblock1, sector 24
[    8.209197] blk_update_request: I/O error, dev mtdblock1, sector 0
[    8.214655] Buffer I/O error on dev mtdblock1, logical block 0, async page read
[    8.869357] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 184
[    8.960147] UBIFS (ubi0:1): recovery needed
[    9.213016] UBIFS (ubi0:1): recovery completed
[    9.213083] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[    9.216348] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    9.224304] UBIFS (ubi0:1): FS size: 14094336 bytes (13 MiB, 111 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
[    9.234205] UBIFS (ubi0:1): reserved for root: 665709 bytes (650 KiB)
[    9.244453] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID 3E6A79D0-6E87-4FB4-9F0F-D39CD1C67463, small LPT model
[    9.252011] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[    9.269887] block: extroot: not configured
[    9.319472] UBIFS (ubi0:1): un-mount UBI device 0
[    9.319524] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops
[    9.353826] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 185
[    9.522176] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[    9.522207] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    9.528985] UBIFS (ubi0:1): FS size: 14094336 bytes (13 MiB, 111 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
[    9.538968] UBIFS (ubi0:1): reserved for root: 665709 bytes (650 KiB)
[    9.549122] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID 3E6A79D0-6E87-4FB4-9F0F-D39CD1C67463, small LPT model
[    9.562314] mount_root: loading kmods from internal overlay
[    9.583526] kmodloader: loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
[    9.592363] kmodloader: done loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
[    9.601352] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[    9.604413] Buffer I/O error on dev mtdblock1, logical block 0, async page read
[   10.087820] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[   10.097114] block: extroot: not configured
[   10.133408] mount_root: switching to ubifs overlay
[   10.167789] urandom-seed: Seeding with /etc/urandom.seed
[   10.271561] procd: - early -
[   10.271617] procd: - watchdog -
[   10.960118] procd: - watchdog -
[   10.960511] procd: - ubus -
[   11.129811] procd: - init -
[   11.453732] kmodloader: loading kernel modules from /etc/modules.d/*
[   11.493452] RPC: Registered named UNIX socket transport module.
[   11.493475] RPC: Registered udp transport module.
[   11.498167] RPC: Registered tcp transport module.
[   11.503120] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   11.510062] ntfs: driver 2.1.32 [Flags: R/O MODULE].
[   11.517753] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[   11.526962] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   11.529820] Netfilter messages via NETLINK v0.30.
[   11.532199] ip_set: protocol 6
[   11.544375] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
[   11.544397] Backport generated by backports.git backports-20160324-13-g24da7d3c
[   11.573117] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
[   11.573232] ath10k_pci 0000:01:00.0: enabling bus mastering
[   11.573795] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[   12.097543] ath10k_pci 0000:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
[   12.097588] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   12.111106] ath10k_pci 0000:01:00.0: firmware ver 10.4-3.4-00082 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast crc32 f301de65
[   14.380336] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id 0:1 crc32 751efba1
[   20.236708] ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
[   20.326972] ath: EEPROM regdomain: 0x0
[   20.326981] ath: EEPROM indicates default country code should be used
[   20.326989] ath: doing EEPROM country->regdmn map search
[   20.327002] ath: country maps to regdmn code: 0x3a
[   20.327012] ath: Country alpha2 being used: US
[   20.327020] ath: Regpair used: 0x3a
[   20.333939] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142)
[   20.334068] ath10k_pci 0001:01:00.0: enabling bus mastering
[   20.334682] ath10k_pci 0001:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[   20.512645] ath10k_pci 0001:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
[   20.512686] ath10k_pci 0001:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   20.525644] ath10k_pci 0001:01:00.0: firmware ver 10.4-3.4-00082 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast crc32 f301de65
[   22.844151] ath10k_pci 0001:01:00.0: board_file api 2 bmi_id 0:2 crc32 751efba1
[   28.744289] ath10k_pci 0001:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
[   28.840659] ath: EEPROM regdomain: 0x0
[   28.840672] ath: EEPROM indicates default country code should be used
[   28.840681] ath: doing EEPROM country->regdmn map search
[   28.840699] ath: country maps to regdmn code: 0x3a
[   28.840711] ath: Country alpha2 being used: US
[   28.840721] ath: Regpair used: 0x3a
[   28.969388] u32 classifier
[   28.969403]     input device check on
[   28.970975]     Actions configured
[   28.975562] Mirror/redirect action on
[   28.981611] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
[   28.983872] fuse init (API version 7.26)
[   28.990107] ip_tables: (C) 2000-2006 Netfilter Core Team
[   28.993624] ctnetlink v0.93: registering with nfnetlink.
[   29.024323] xt_time: kernel timezone is -0000
[   29.027460] PPP generic driver version 2.4.2
[   29.028292] NET: Registered protocol family 24
[   29.033372] kmodloader: done loading kernel modules from /etc/modules.d/*
[   30.468781] blk_update_request: 10 callbacks suppressed
[   30.468804] blk_update_request: I/O error, dev mtdblock0, sector 0
[   30.473383] blk_update_request: I/O error, dev mtdblock0, sector 8
[   30.479622] blk_update_request: I/O error, dev mtdblock0, sector 16
[   30.485702] blk_update_request: I/O error, dev mtdblock0, sector 24
[   30.492563] blk_update_request: I/O error, dev mtdblock0, sector 0
[   30.497635] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[   30.504597] blk_update_request: I/O error, dev mtdblock1, sector 0
[   30.511692] blk_update_request: I/O error, dev mtdblock1, sector 8
[   30.517839] blk_update_request: I/O error, dev mtdblock1, sector 16
[   30.524065] blk_update_request: I/O error, dev mtdblock1, sector 24
[   30.530255] blk_update_request: I/O error, dev mtdblock1, sector 0
[   30.535914] Buffer I/O error on dev mtdblock1, logical block 0, async page read
[   30.942284] dwmac1000: Master AXI performs any burst length
[   30.942336] ipq806x-gmac-dwmac 37400000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported
[   30.946868] ipq806x-gmac-dwmac 37400000.ethernet eth1: registered PTP clock
[   30.955946] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   30.974247] br-lan: port 1(lan1) entered blocking state
[   30.974277] br-lan: port 1(lan1) entered disabled state
[   30.981839] device lan1 entered promiscuous mode
[   30.983478] device eth1 entered promiscuous mode
[   30.993208] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   31.010739] br-lan: port 2(lan2) entered blocking state
[   31.010762] br-lan: port 2(lan2) entered disabled state
[   31.019703] device lan2 entered promiscuous mode
[   31.037928] br-lan: port 3(lan3) entered blocking state
[   31.037955] br-lan: port 3(lan3) entered disabled state
[   31.048023] device lan3 entered promiscuous mode
[   31.065046] br-lan: port 4(lan4) entered blocking state
[   31.065071] br-lan: port 4(lan4) entered disabled state
[   31.077008] device lan4 entered promiscuous mode
[   31.101932] dwmac1000: Master AXI performs any burst length
[   31.101972] ipq806x-gmac-dwmac 37200000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
[   31.106444] ipq806x-gmac-dwmac 37200000.ethernet eth0: registered PTP clock
[   31.115592] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   31.167236] IPv6: ADDRCONF(NETDEV_UP): wan: link is not ready
[   31.544576] ath: EEPROM regdomain: 0x809c
[   31.544594] ath: EEPROM indicates we should expect a country code
[   31.547556] ath: doing EEPROM country->regdmn map search
[   31.553723] ath: country maps to regdmn code: 0x52
[   31.559016] ath: Country alpha2 being used: CN
[   31.563682] ath: Regpair used: 0x52
[   31.568037] ath: regdomain 0x809c dynamically updated by user
[   31.571511] ath: EEPROM regdomain: 0x809c
[   31.577326] ath: EEPROM indicates we should expect a country code
[   31.581404] ath: doing EEPROM country->regdmn map search
[   31.587398] ath: country maps to regdmn code: 0x52
[   31.592862] ath: Country alpha2 being used: CN
[   31.597383] ath: Regpair used: 0x52
[   31.601940] ath: regdomain 0x809c dynamically updated by user
[   32.017211] qca8k gpio-0:10 lan2: Link is Down
[   32.021942] qca8k gpio-0:10 lan1: Link is Down
[   32.022048] ipq806x-gmac-dwmac 37400000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[   32.025367] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   32.091425] qca8k gpio-0:10 lan3: Link is Down
[   32.093594] qca8k gpio-0:10 lan4: Link is Down
[   32.172529] ipq806x-gmac-dwmac 37200000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   32.172595] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   32.254232] qca8k gpio-0:10 wan: Link is Down
[   33.295035] qca8k gpio-0:10 wan: Link is Up - 100Mbps/Full - flow control rx/tx
[   34.103155] qca8k gpio-0:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[   36.174664] qca8k gpio-0:10 lan1: Link is Down
[   37.223072] qca8k gpio-0:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[   39.152439] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[   39.154378] br-lan: port 5(wlan1) entered blocking state
[   39.157167] br-lan: port 5(wlan1) entered disabled state
[   39.163087] device wlan1 entered promiscuous mode
[   39.168072] br-lan: port 5(wlan1) entered blocking state
[   39.172694] br-lan: port 5(wlan1) entered forwarding state
[   39.178086] IPv6: ADDRCONF(NETDEV_CHANGE): wan: link becomes ready
[   39.187526] br-lan: port 1(lan1) entered blocking state
[   39.189578] br-lan: port 1(lan1) entered forwarding state
[   39.195776] br-lan: port 5(wlan1) entered disabled state
[   39.200478] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   40.381620] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[   40.381759] br-lan: port 5(wlan1) entered blocking state
[   40.387047] br-lan: port 5(wlan1) entered forwarding state
[   92.827224] qca8k gpio-0:10 lan1: Link is Down
[   92.827429] br-lan: port 1(lan1) entered disabled state
[   94.898500] qca8k gpio-0:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[   94.905704] br-lan: port 1(lan1) entered blocking state
[   94.905754] br-lan: port 1(lan1) entered forwarding state
[   96.996453] qca8k gpio-0:10 lan1: Link is Down
[   96.999526] br-lan: port 1(lan1) entered disabled state
[  106.342630] qca8k gpio-0:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[  106.354647] br-lan: port 1(lan1) entered blocking state
[  106.354704] br-lan: port 1(lan1) entered forwarding state
[  109.466517] qca8k gpio-0:10 lan1: Link is Down
[  109.468561] br-lan: port 1(lan1) entered disabled state
[  112.587901] qca8k gpio-0:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[  112.592133] br-lan: port 1(lan1) entered blocking state
[  112.594044] br-lan: port 1(lan1) entered forwarding state
[  114.654639] qca8k gpio-0:10 lan1: Link is Down
[  114.658840] br-lan: port 1(lan1) entered disabled state
[  117.789138] qca8k gpio-0:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[  117.793744] br-lan: port 1(lan1) entered blocking state
[  117.795386] br-lan: port 1(lan1) entered forwarding state
[  141.702727] qca8k gpio-0:10 lan1: Link is Down
[  141.710302] br-lan: port 1(lan1) entered disabled state
[  143.785380] qca8k gpio-0:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[  143.791718] br-lan: port 1(lan1) entered blocking state
[  143.791765] br-lan: port 1(lan1) entered forwarding state
[  145.875004] qca8k gpio-0:10 lan1: Link is Down
[  145.875201] br-lan: port 1(lan1) entered disabled state
[  163.537931] qca8k gpio-0:10 lan1: Link is Up - 100Mbps/Full - flow control rx/tx
[  163.546200] br-lan: port 1(lan1) entered blocking state
[  163.546252] br-lan: port 1(lan1) entered forwarding state
```


Added a text file


Looks like incorrect selector: no closing ']'.


@md678685 Sorry for ignoring that. I presumed this was all that was necessary. Feel free to amend this.


oh god


因为网上都没有brian的教程，那我就尝试做一些微小的贡献好了。有兴趣一起做的可以加微信 luoxikang1997 联系


Looks good, send me Patch via email:
```
to: progyanb@acm.org
cc: bytes-club@googlegroups.com
```
For commit styling, follow: https://bytesclub.github.io/contributing/


О, я вспомнил. Навигацию на уровне detour-a я понятия не имею, как патчить.
Но можно подготовить отдельные навмеши (построенные около нуля координат) и переключаться между ними. Будет оверхед по памяти в несколько раз, зато оно потом не выстрелит в самом неожиданном месте.


![](https://github.trello.services/images/mini-trello-icon.png) [Test for github](https://trello.com/c/WMl5gHzp/28-test-for-github)


Ffgo


private **_ #String_** stringValue;


ya~


we want `foldDyn` here, holding a queue (list) of notifications. So here must be `[]`


I know, I built that, but we can't use that in the stdenv.


`render` should render a list of notifications. Each notification item should have a "close" button.


`wait()` may cause problems and the process never terminate: https://docs.python.org/3.5/library/subprocess.html?highlight=subprocess%20popen#subprocess.Popen.wait

I will try to use `communicate()` instead as suggested in the docs.


Please update your golex to the latest version.


auto closing should be optional and used only when explicitly asked for


ok this is a great edition!


Syntax: int sys_waitpid(pid_t pid,unsigned int * stat_addr, int options)

Source: kernel/exit.c

Action: wait for process termination


why isnt the MembershipType noe defined here in the DbSet?, but it creates the table, how is that possible


sink should be polymorphic


Bluemix [toolchain](https://console-regional.ng.bluemix.net/devops/toolchains/98950311-cd74-44cb-99d1-240125fefc9f "simple-toolchain-20170804185201145"): [Delivery Pipeline](https://console-regional.ng.bluemix.net/devops/pipelines/fedbdb29-3814-4f7f-b6f4-70b98632ca33 "simple-toolchain-20170804185201145") deployed [simple-toolchain-20170804185201145](https://github.com/priyamagi/simple-toolchain-20170804185201145/releases/tag/deploy-ibm-yp-us-south-kanchana2468-gmail.com-kanchana-20170805-092802 "deploy-ibm-yp-us-south-kanchana2468-gmail.com-kanchana-20170805-092802") to [kanchana](https://console.bluemix.net/apps/4f228de8-25a2-410f-80b3-b454ab5ad846?env_id=ibm:yp:us-south "ibm:yp:us-south:kanchana2468@gmail.com:kanchana"), including this commit


no need to show full tweets here - the feed is used for this. Notifications are meant to be used for notifications - error messages (mostly), warnings, result reports (for retweets, when posting new tweets etc).


@gabro No, doesn't work. I've just tried again removing `node_modules` and following the instructions in the README... not a blocker for now, just wanted to share this info :smile:


Syntax: int sys_creat(const char * pathname, int mode)

Source: fs/open.c

Action: create a file or device


FYI, I recently fixed this in the main branch!


there's not need for this, check [this](https://stackoverflow.com/questions/41923069/assigning-typescript-constructor-parameters).


we can use just strings for now

or make a typeclass `NotificationMessage` with method like `getDisplayContent`, and implement it for different types, incl. Tweets if needed


so should using Dagger 0.2.0 force a downgrade of JuliaDB to 0.1.x (and IndexedTables to 0.2.x) ?


AS long as sessions are based on a non-ciphered JWT token, there is no need to ask the server, simple do a decode of this.token.


usually imports are sorted in some logical order, with own modules on the bottom


Updated golex and commited the new version of the scanner. Hopefully things
look good now.

On Sat, Aug 5, 2017 at 2:22 AM, cznic <notifications@github.com> wrote:

> Please update your golex to the latest version.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/corywalker/wl-1/commit/46a5094e00a8faa4d8bc9021645772654dbb9939#commitcomment-23494607>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAEaMoTgi8KqmCIJ7oaCzKhAopo5CSYrks5sVDRygaJpZM4OuacK>
> .
>


Test 1


Creating WebApi Rount, set defualt output for JSON


odd, I must have screwed something up. Let me double check, in the meantime thanks for testing it!


the idea of frp components is implemented correctly, minor fixes to do


fgsgssfgsfgds


@jaapio several times (not every time) I'm getting on this line this error: `Uninitialized string offset: 0` on this line

It fails this way in my case 50% of times, without code being changed, just repeatedly rerun the same code


What's the big problem if Dagger updated to v0.2.1??? It's not a breaking upgrade.


what is that git ignore youu always do i don't understand it


or rather not polymorphic, but constrained to String, or NotificationMessage typeclass


navigate between _settings_


Set glyphicon different  to differnt size


> so should using Dagger 0.2.0 force a downgrade of JuliaDB to 0.1.x (and IndexedTables to 0.2.x) ?

I'm fine with that, actually. My priority is getting things working for people who haven't pinned Dagger at 0.2.0.


Load all accounts data


Material diameter in Machine Settings


if it's pinned or locally modified, Pkg won't upgrade it. JuliaPro has pinned Dagger at 0.2.0, btw.


WebApi, Insert new record into db


Thanks Sloped-soarer, I've some insomnia this time !

We have build a "universal" base to use all kind of protocols :-) Thanks !

I'm not sure about PPM & DSM Cmd choice.

Next step is moving Supiiik code into Multi Cmd .....

Have a good day.

Christophe

2017-08-05 10:26 GMT+02:00 sloped-soarer <notifications@github.com>:

> I feel for you. Working late again.
> Your knowledge of the code is impressive.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/Ingwie/OpenAVRc_Dev/commit/f52859687c232bb8a4c61aaf6ad80ab82b763d83#commitcomment-23494288>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ALU11Ft5rB7yJkRAJYPMHetECgsbnoAYks5sVCcsgaJpZM4OuZu5>
> .
>


WebApi,Delete record from Account db


I tried this:

- cloned the repo fresh
- npm install
- npm run
- install from VSIX

and it seems to be working:

![](http://g.recordit.co/1vOi38QdH6.gif)


Can't understand, why would a Panel (component) extend a Model Class (User)?


when all request are complete, this method works to dispose any remaining requests


Nope.


port variable should be change based on current port in you testing/dev environment


Index method, to load all accounts data from api


load all the account's details


create a new account record


post insert for coming account's record


Try to issue a command
`sysctl -w net.ipv4.tcp_congestion_control=yeah`

And try the wifi test again.

By the way it seems like you have problems with cable, connected to lan port 1 - it constantly reconnects and falls back to slower speed


And JuliaDB isn't in JuliaPro, it's separate at the moment. So if someone installs JuliaPro but not the separate JuliaDB installed (which we'll need to be careful about what version it's using), they can do `Pkg.add("JuliaDB")`. Which version should they get?


Edit account record


post edit for account record


The one that works with v0.2.0 without a name clash.


based on account id , the delete request  will be sent to api


adding Auto mapper


here migration data, created based on task context


@AdrianDC Since you're constantly upto date with master branch, just want to ask, is there any change in UI or major APIs (like background restriction and all)?


Account class


AccountClass Class


Sua loi :V


AccountType class


Define the automapper map


I think it's a problem with the current setup of JuliaPro that we pin packages. Could be fixed by having a JuliaPro metadata maintained by JC when we can do that.


define DTO objects based on classes


created context based on classes


Hello, Edwin!

Interesting script.
I wanted to clarify. I write that there is no such file when I enter the command Chmod the sp_lang folder chmod 777 -R sp_lang      ?

And if there is no such file, then it needs to be created?

Add this line in /etc/lighttpd/lighttpd.conf
url.rewrite = ("^ / (. *) \. (. +) $" => "$ 0", "^ / (. +) /? $" => "/index.php/$1")

It does not work yet if there is a domain.com/blog/
I can not get to http: // (your_blog_url) /blog/backstage
Maybe because the file about which you wrote above is not configured?

What rules need to be created in .htaccess   ?

And here's another question: Can I solve the problem with the ru_RU locale?

P.S. Domain apparently does not work sedot.space

(I'm writing through Google translator)


All comments has been added


It's a nonsense :scream: Only Home, Debts and Users should extend LoggedUser class


So... why do you say "User" is a component?


This function renames all files in a directory and its subdirectories.

It takes three parameters:
        path: the string representing the path of the directory where the files have to be renamed
	pattern: the regular expression which has to be found in the files
	replacement_str: the string which will replace the matched regular expression


There's no name clash with Dagger 0.2.0 though if distribute doesn't exist there?

It's the best solution we currently have to Pkg.update resulting in arbitrarily changing API's and the possibility of everything breaking.


marshaler  => **marshalers**


@noname007 支持cookie的条件判断和变量提取，可以测测


Is there a pull request for this? Sorry if I missed it.


Bluemix [toolchain](https://console-regional.ng.bluemix.net/devops/toolchains/de742651-8462-4286-b78d-3e94ac013f9f "compromisos"): [Delivery Pipeline](https://console-regional.ng.bluemix.net/devops/pipelines/0d0e8b6d-930b-40fc-ac1c-2a7d8ad5ef0b "compromisos") deployed [compromisos](https://github.com/eschuler7/compromisos/releases/tag/deploy-ibm-yp-us-south-eschuler-pe.ibm.com-dev-20170806-000408 "deploy-ibm-yp-us-south-eschuler-pe.ibm.com-dev-20170806-000408") to [dev](https://console.bluemix.net/apps/6f3a0e56-815a-41fc-aa5f-5ec09678068d?env_id=ibm:yp:us-south "ibm:yp:us-south:eschuler@pe.ibm.com:dev"), including this commit


No rule to make target XD curl.h


Estudo sobre Banco de dados PostgreSQL


Deleted these lines by accident


I wonder if anybody is actually using this for anything.


![](https://github.trello.services/images/mini-trello-icon.png) [UI Work](https://trello.com/c/o0DJODbi/24-ui-work)


adding theme


Because `ctrl + shift + f` triggers the full screen modal. It shouldn't prevent `ctrl + f` though, so that needs to be fixed.


oops?


Ahh, I see. Great, I hadn't discovered this feature yet. Will play around with the shortcuts a bit. 🙂
Do you want me to open an issue about `ctrl + f`?


Ooh, I see an obvious mistake here! Not your fault, it's whoever wrote the original commented code.


Ah thanks! Seems to crash on rebuilding though. Has he uploaded the source code? I've taken a look at his fork though seems to be the same as the master build.


🙂 typo.


Hi, playlistloader from kodi jarvis 16.1 on fire tv stick does not load channels from my playlists, i experience this problem only from Android fire tv stick , from my windows pc it works normaly.
Is there any solution for this problem?


No more Jekyll?


o


![screen_2017-08-05 17 44 10](https://user-images.githubusercontent.com/18017741/28999690-a8a7753e-79fd-11e7-9140-9517584d522c.jpg)


Code changes without whitespaces: https://github.com/Bara20/TroubleinTerroristTown/commit/51e89886b2c591ffd829b6ceb6977bac7001a836?w=1


Not entirely sure yet. I basically just cleared out the repository (and only on a branch) so that me and my new webmaster could start brainstorming. Just not a huge fan of static site generators, we may end up using something like Django for blog/event posts!


fixed stupid mistake.


You mean the case where u->attacks().size() == 0 gives "No attack" when "No attacks" would be more appropriate?


@NicolasGraph, you could simplify the regex, as there is no need to escape some special characters (like `/`, when it's not being used as delimiter, and like `&`, `?` and also `/`, when inside character classes). As you are using `#` as delimiter, you could rewrite this regex like this (which seems more readable to me):

```
#^(http|https)://(www.)?(youtube\.com/(watch\?v=|embed/|v/)|youtu\.be/)(([^&?/]+)((&|\?)list=[^&?/]+)?)#
```
I've tested it and it seems to work as expected (generating the same matches than the current regex).


Update https://forums.lanik.us/viewtopic.php?p=122250#p122250


Sure, agree on that.

The context: Shared configuration items where in code. I moved them to a shared *code* file (`.py`, a module). The "final" stage will be to create a config object with an accompanying config file (YML, JSON, whatever static format).

My current position is that it is low priority, and still on a good track toward a good structure.

How do you think?


Thank you!


Erik
I forked your code and found it to work well!  Thanks for the 6 pin association on the D PORT! I have Tested on T_3.1 and 3.5 and 3.6.


メンバー追加されたことをかくにんしました。


The only reason I chose this format over `isoformat` is that it is "enough" and shorter.

No problem in S3, but I can't remember testing (there are problems with MySQL, though).


Please push this commit Into the next version. The cordova app has been unusable without dodgy hacks for nearly a year because of this :( I've got it merged In my custom fork but I can't imagine the pain it's causing for everyone else


Okay, I understand. How about I put the packet struct in crtp.h? That seems to be an appropriate location.


Note that timestamps recorded are in UTC ISO.


Il faut doubler ton apostrophe ici : l'´Intendant


@tsherif How does this work? After trying to debug this I can't figure out why each cube returns just 255 in either the Red or Blue value


It's ok for you to nuke the branch. Retesting showed that I had misinterpreted the executable being used and indeed changing the path around was not necessary.


That's related, yeah, but more generally it's using the wrong gettext function - it should be using the plural string function. (Already fixed this locally.)


Edit: é a letra B da questão 10, não dá 8, como está no commit.


Wonderful addition to your collection, Neel Sankaran.


I almost was able to compile removing curl stuff from .pro file but hit a road block in upgrader the curl/curl.h wasn't found. was able to use ../curl/curl.h but other issues obv in defined stuff.  u broke u fix XD


@kvetinac97 will check it out later


If a rook gets captured, and the rook on the other side moved to the captured rook's original position, you could still castle.


@leonahu seems you forgot to go from a regular class component to a functional component, where  `this` doesn't exist.


Made huge strides today! Good work, me. :P


поиграемся ???


Yes, that would be a good place for it.


Then I'll let you push the commit when you're ready.


This commit breaks local world, I'll revert


nope


hi, @vlm,

I tried to compile RRC example with newest commit https://github.com/vlm/asn1c/commit/7268f33f6a8122a9c521fe36faaf365c643ee86f but got the following error message.
It seems that only NativeInter_oer.c was copied to destination but INTEGER_oer.c (and OCTECT_STRING_oer.c in J2735's case) not copied.

FYI.
```
INTEGER.o:(.data.rel+0x48): undefined reference to `INTEGER_decode_oer'
INTEGER.o:(.data.rel+0x50): undefined reference to `INTEGER_encode_oer'
NativeInteger.o:(.data.rel+0x48): undefined reference to `NativeInteger_decode_oer'
NativeInteger.o:(.data.rel+0x50): undefined reference to `NativeInteger_encode_oer'
converter-sample.o: In function `main':
converter-sample.c:(.text+0xd4b): undefined reference to `oer_encode'
converter-sample.o: In function `data_decode_from_file':
converter-sample.c:(.text+0x1ea9): undefined reference to `oer_decode'
collect2: error: ld returned 1 exit status
Makefile:4749: recipe for target 'rrc-dump' failed
make: *** [rrc-dump] Error 1
```


It will be sent when all the prerequisites are likely to have been merged.
If you need to use it now, just use my branch.


나의 기억으로는 1. self.dismiss블럭은 View가 사라지는 작업(UI작업)이므로 main thread로 실행시켜야하고
2. NotificationCenter.default.post는 그것을 받는 Controller들이 UserSignInSuccess를 받으면 tableView.reload()같은 UI작업이 있을 것이기 때문에 메인으로 넘겨주었음.

하지만 지금 코드를 다시 보니.. 두개다 main.async에서 빼도 아주 잘 실행이 되는 것을 확인하였음...
또한 post를 메인으로 넘겨주었는데 다시 networking작업을 하는데 reload를 메인으로 안하고 있었음...(의도실패)

결론: 로그인 결과가 있으면 그 결과를 받는 리스트 컨트롤러들의 selector들이 즉각 실행되는 것이 의도였으나 의미를 발휘하고 있지않음을 포착 ㅠㅠ


@renanlmd
E se eu trocasse pra aspas simples no echo? O resultado seria o mesmo?


Подскажите, как проверить что "HTML компрессор" мешает жить. Жалко его выпиливать :)


异团异色会影响属性强度提升和技能强度之间的比率，如果不考虑这点会导致宝石配置错误


change banner for android tv


Thanks!
Why did you remove the explicit casts to boolean?
IMO that just makes it vague but perhaps that's just me