Parents (Total: 45)

The searched file hash is included in 45 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	768D163FA79990FDD1326B3FC8E4FC22
PackageArch	x86_64
PackageDescription	Puma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageName	ruby2.6-rubygem-puma-1_6
PackageRelease	3.36
PackageVersion	1.6.3
SHA-1	0423BF61E2BEE582CEF203F5A7E6145E19D812EC
SHA-256	8815FA04611B2DC8B0563863C119B2BA363E85A80EF79C77DE86D8BA803B5380

Key	Value
MD5	2E97EE59A027C6773F45A2E157B20752
PackageArch	i586
PackageDescription	Puma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageName	ruby3.1-rubygem-puma-1_6
PackageRelease	3.303
PackageVersion	1.6.3
SHA-1	0D2820E9298B6E228DD0FB0AF85B353B8A6C0E23
SHA-256	BC29663469102CFD9BA5E4C10B6E65092295C5FF57E2358E677EA3ABF199555D

Key	Value
MD5	4030FEE0FD1AC4F0D5F24472757EF128
PackageArch	x86_64
PackageDescription	logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching).
PackageName	logstash
PackageRelease	1.1
PackageVersion	2.4.1
SHA-1	0FB5633CA3B47103AECFF28DACA4F1A7C853FB6F
SHA-256	1E085AF1447A079844D0B5D817C6FF0C04B70C9D63F14FA2528A8C43D458D5A1

Key	Value
MD5	B835C2E3729A9D8223ACB09A4A0FD1F3
PackageArch	x86_64
PackageDescription	Puma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageName	ruby2.6-rubygem-puma-1_6
PackageRelease	lp153.3.22
PackageVersion	1.6.3
SHA-1	11B8567316A9A47E3E91ED85F7C9AA110232F8D9
SHA-256	79424A1374CB35C508B9A8551B2AB3E56770648EDB664289D9479E2585ED8EC7

Key	Value
MD5	DC02202103B29A41DC5B9AAC5B215A7E
PackageArch	x86_64
PackageDescription	logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching).
PackageName	logstash
PackageRelease	lp152.5.6
PackageVersion	2.4.1
SHA-1	1F69FB46559B643FE05D6919FFFF43633E02A9FA
SHA-256	94DAE4EBFCEEFDE0A25FC74AA71D21ECF6B136691C2CC9F39FFD091784FAE993

Key	Value
SHA-1	2173C791F83932F667A009E43CD966C3BEF466F0
snap-authority	canonical
snap-filename	inHPJz1Odiq9ZuHPMxZSeXIfjS9Y1M7X_33.snap
snap-id	inHPJz1Odiq9ZuHPMxZSeXIfjS9Y1M7X_33
snap-name	firewallreports
snap-publisher-id	FySbOnFUWsRfJsLzIW1SHQcBZxIb06XE
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2018-05-16T11:26:27.131756Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/inHPJz1Odiq9ZuHPMxZSeXIfjS9Y1M7X_33.snap

Key	Value
MD5	D062165E23B4BBD3F3F93F1F521CB79E
PackageArch	x86_64
PackageDescription	Puma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageName	ruby3.1-rubygem-puma-1_6
PackageRelease	3.303
PackageVersion	1.6.3
SHA-1	2208B80BC41B5DEE1E83D3AE3FD4CEAD252F8A12
SHA-256	C687318FCD55BB07F1FCA05FFE018850A952AA4062A16F57E956EAB52DCDE05B

Key	Value
MD5	52FF4B6C4F95BEB130605DDE7AD92D28
PackageArch	x86_64
PackageDescription	Puma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageName	ruby2.7-rubygem-puma-1_6
PackageRelease	lp154.3.3
PackageVersion	1.6.3
SHA-1	297894D58C84D376B1DC3D39AF5A43C9CC64D0F9
SHA-256	2433BC9BA83A7E46EEB9C21CC6A39A42E80D247FB33F733DB5E54B398D5E123D

Key	Value
MD5	CC18580DB7CF6A6B7A96F9D802E8077A
PackageArch	x86_64
PackageDescription	Puma is a simple, fast, and highly concurrent HTTP 1.1 server for Ruby web applications. It can be used with any application that supports Rack, and is considered the replacement for Webrick and Mongrel. It was designed to be the go-to server for [Rubinius](http://rubini.us), but also works well with JRuby and MRI. Puma is intended for use in both development and production environments. Under the hood, Puma processes requests using a C-optimized Ragel extension (inherited from Mongrel) that provides fast, accurate HTTP 1.1 protocol parsing in a portable way. Puma then serves the request in a thread from an internal thread pool (which you can control). This allows Puma to provide real concurrency for your web application! With Rubinius 2.0, Puma will utilize all cores on your CPU with real threads, meaning you won't have to spawn multiple processes to increase throughput. You can expect to see a similar benefit from JRuby. On MRI, there is a Global Interpreter Lock (GIL) that ensures only one thread can be run at a time. But if you're doing a lot of blocking IO (such as HTTP calls to external APIs like Twitter), Puma still improves MRI's throughput by allowing blocking IO to be run concurrently (EventMachine-based servers such as Thin turn off this ability, requiring you to use special libraries). Your mileage may vary. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like [Rubinius](http://rubini.us) or [JRuby](http://jruby.org).
PackageName	ruby2.6-rubygem-puma-1_6
PackageRelease	3.50
PackageVersion	1.6.3
SHA-1	2D01DBD3964A4B8037550F0E13A1F1DD437FB998
SHA-256	62D0CFBC0EC2B5114EF8E90B6F8B3EBD8466B78B679190B0343BADE954612496

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.2/packages//amd64//logstash-2.4.0p1v0.tgz
MD5	4B8A08D7479E3A67DC36DB335A375538
SHA-1	2F7B0E8F581090739AEDE453B85EF04DFAC6C88A
SHA-256	1B0C0574E441546BC21808C317CD1339A81923C848476A65CFCFEDC4EE5C3F68
SSDEEP	1572864:0OFcc7HD5y79OP0vcQ6NKINEO1j3zTDBwiMhmzGQyhke8uuD1vAANQ8Qi/5:UaH1CO8vcVNK2Eej5l4fHJ8zvA/i/5
TLSH	T172083312A4379663C53DE3B036186FBB9670CDB87528EC2BFBDC51E0179E4D2275A122