kitura / heliumlogger Goto Github PK

Compilation results in a warning from the compiler:

warning: PackageDescription API v3 is deprecated and will be removed in the future;

Swift Version: 4.1
Platform: macOS 10.14 Mojave
HeliumLogger Version: 1.7.1

In an app using multiple dispatch queues it may be worth logging current queue with every message.

Would you be willing to accept a PR if I consider adding this support? I am using HeliumLogger in multiple server side swift projects and would be willing to open a PR.

thanks for great and simple component...

How can I add logging settings like setting log file path limiting the size of log file path similar to winston logger for nodejs.

How to log to local file path?
Please forgive me that this maybe a dumb question.
Thanks:)

Hello developers. i realy can't found tutorials how to use (import in to project in xcode for example)your module or other modules from IBM Package Manager. i try to use founded here https://swiftpkgs.ng.bluemix.net/package/IBM-Swift/HeliumLogger in IBM Sandbox, but there only errors && crush :(. for example this link taken from IBM sandbox
https://swiftlang.ng.bluemix.net/#/repl?gitPackage=https:%2F%2Fgithub.com%2FIBM-Swift%2FHeliumLogger-Sample&swiftVersion=latest

Thanx for reply

Running the HeliumLogger sample in the Sandbox yields the output below. It would be nice if there is a programmatic way to turn off the code coloring, so that it looks more presentable.

�[0;39m VERBOSE: HeliumLogger_Sample main.swift line 23 - This is a verbose log message. �[0;39m
�[0;39m INFO: HeliumLogger_Sample main.swift line 25 - This is an informational log message. �[0;39m
�[0;33m WARNING: HeliumLogger_Sample main.swift line 27 - This is a warning. �[0;39m
�[0;31m ERROR: HeliumLogger_Sample main.swift line 29 - This is an error. �[0;39m
�[0;39m DEBUG: HeliumLogger_Sample main.swift line 31 - This is a debug message. �[0;39m
�[0;39m INFO: no func main.swift line 34 - This a dynamic message �[0;39m

Quick info, LoggerAPI latest release is 5, I noticed you still force here for .4 version

The usage example:

import HeliumLogger
Log.logger = HeliumLogger()
Log.verbose("This is a log message.")

doesn't actually compile.

import LoggerAPI

is required too. Can we remove the requirement to import LoggerAPI?

I'm getting that error when trying to do
swift package generate-xcodeproj
The xcode project is not updating after adding a coachDB package dependency.
Any idea??

not sure if i missed it, but i had to read through the code to find out where HeliumLogger logs to.

it is very nice that this is just a lightweight logger to stdout. would be great if it could be stated in the readme.

How can I add logging settings like setting log file path limiting the size of log file path similar to winston logger for nodejs?

Hi,
I tried to compile a simple hello world program using HeliumLogger and the swift compiler failed to compile due to an error with HeliumLogger.

Cheers,
Joe

.Package(url: "https://github.com/IBM-Swift/HeliumLogger.git", majorVersion: 1, minor: 6)

Here is the output:

Compile Swift Module 'SSLService' (1 sources)
Compile Swift Module 'HeliumLogger' (2 sources)
/home/user/hello-api/.build/checkouts/HeliumLogger.git-7972212279880105712/Sources/HeliumLogger/HeliumLogger.swift:116:39: error: use of undeclared type 'RegularExpression'
typealias RegularExpressionType = RegularExpression
^~~~~~~~~~~~~~~~~
/home/user/hello-api/.build/checkouts/HeliumLogger.git-7972212279880105712/Sources/HeliumLogger/HeliumLogger.swift:121:24: error: could not infer type for 'tokenRegex'
private static var tokenRegex: RegularExpressionType? = {
^
/home/user/hello-api/.build/checkouts/HeliumLogger.git-7972212279880105712/Sources/HeliumLogger/HeliumLogger.swift:116:39: error: use of undeclared type 'RegularExpression'
typealias RegularExpressionType = RegularExpression
^~~~~~~~~~~~~~~~~

Any native configuration for log rotation in the API ?

It would be great to support JSON formatted output, compatible with e.g. ElasticSearch / Kibana.

To support links between Package Catalog and Sandbox.

When running with the swift application https://github.com/IBM-Bluemix/Kitura-Starter, it is fine with HeliumLogger 1.6.x version.

But if I use majorVersion directly,
.Package(url: "https://github.com/IBM-Swift/HeliumLogger.git" , majorVersion: 1), then staging failed.

   Cloning https://github.com/IBM-Swift/HeliumLogger.git
   HEAD is now at 9b310ce IBM-Swift/Kitura#1047 Swift 3.1 changes

swift-build: error: The dependency graph could not be satisfied (https://github.com/IBM-Swift/LoggerAPI.git)
Failed to compile droplet
Exit status 223
Staging failed: Exited with status 223
Destroying container
Resolved version: 1.7.0
Successfully destroyed container

I am using the HeliumStreamLogger with Swift-log Logging. I followed the README and used LoggingSystem.bootstrap(myStreamlogger.makeLogHandler).
The LogHandler created from the above has a hard-coded .info level and it took me a long time to work out how to change it. Maybe there are easier ways, but the following code works and I think it should be included in the README.

var handler = myStreamLogger.makeHandler(label: "StreamLogger")
handler.logLevel = .debug
LoggingSystem.bootstrap({ name in {return handler})