sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: decoded context and raw response should coincide
Labels: feature request

I made two requests.
The first one had the following params:
```
$payload = @{
    model = "llama3"
    prompt = "
user
Hey!

assistant
"
    stream = $false
    seed = 123
    temperature = 0
    raw = $true
} | ConvertTo-Json
```
And I got this:
```
{
  "model": "llama3",
  "created_at": "2024-05-23T15:48:39.9473937Z",
  "response": "\n\nHey! It's nice to chat with you. Is there something on your mind that you'd like to talk about, or are you just looking for some casual conversation? I'm here to listen and help if I can!",
  "done": true,
  "done_reason": "stop",
  "total_duration": 14993710800,
  "load_duration": 2539700,
  "prompt_eval_duration": 297100000,
  "eval_count": 47,
  "eval_duration": 14693012000
}
```
And the second one's parameters:
```
$payload = @{
    model = "llama3"
    prompt = "Hey!"
    stream = $false
    seed = 123
    temperature = 0
} | ConvertTo-Json
```
And the response:
```
{
  "model": "llama3",
  "created_at": "2024-05-23T15:49:20.9390008Z",
  "response": "Hey! It's nice to meet you. Is there something I can help you with, or would you like to chat?",
  "done": true,
  "done_reason": "stop",
  "context": [128006,882,128007,271,19182,0,128009,128006,78191,128007,271,19182,0,1102,596,6555,311,3449,499,13,2209,1070,2555,358,649,1520,499,449,11,477,1053,499,1093,311,6369,30,128009],
  "total_duration": 9436567800,
  "load_duration": 2744600,
  "prompt_eval_count": 8,
  "prompt_eval_duration": 1562642000,
  "eval_count": 26,
  "eval_duration": 7870476000
}
```
Now if I decode my context list with the llama3 tokenizer, I get:
```

user
\n\nHey!

assistant
\n\nHey! It's nice to meet you. Is there something I can help you with or would you like to chat?

```
So, the questions is: **Why the response with raw = true doesn't look like my decoded list?** Wouldn't that be more reasonable? If I'm to work with raw prompts, I want raw responses. Especially if I need to keep a chat history.
Repository: vscode
Issue: Make Tabs Multiselect Keyboard Accessible
Labels: feature-request,accessibility,workbench-tabs

Currently, it is not possible to select/unselect a tab by only using the keyboard.
Repository: flutter
Issue: Upgrade 1 arm64 and x86 macOS 14 devicelab bot in staging pool to iOS 18
Labels: team-infra,P2,triaged-infra

### Type of Request

infra task

### Infrastructure Environment

Devicelab

### What is happening?

Prerequisites

- [ ] iOS 18 has been released
- [ ] https://github.com/flutter/flutter/issues/148899
- [x] https://github.com/flutter/flutter/issues/148881

---

- [ ] Upgrade 1 [x86 macOS 14 staging devicelab bot](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.staging&f=cpu%3Ax86&f=os%3AMac-14&k=os&s=id) to iOS 18
- [ ] Upgrade 1 [arm64 macOS 14 staging devicelab bot](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.staging&f=cpu%3Aarm64&f=os%3AMac-14&k=os&s=id) to iOS 18

When ready to upgrade, file an issue with a list of explicit bots listed by name to upgrade and include the following additional instructions:
1. Before starting upgrade, quarantine the bot
2. After upgrading device
    1. Open Xcode 16 from /opt/flutter/xcode/[insert Xcode build version]/XCode.app
    2. In the top bar, open Window > Device and Simulators
    3. The window that opens should show the connected device
    4. Accept the Trust dialog on the iPhone device
    5. If you get the dialog on the device twice, you may need to accept it once, disconnect, reconnect, and accept again.
    6. Wait for the yellow bar at the top of the Device and Simulators window to go away - It should take a minute or so to Copy cache symbols
3. Unquarantine the bot

See https://github.com/flutter/flutter/issues/142326 as example.

### Steps to reproduce

_No response_

### Expected results

_No response_
Repository: flutter
Issue: RBE builds are using intel `llvm`
Labels: P2,team-engine,triaged-engine,e: rbe

When RBE fails to distribute its builds (frequent), it falls back to intel binaries for local compilation.

cc @zanderso 

## screenshot
<img width="1920" alt="Screenshot 2024-05-23 at 9 04 07 AM" src="https://github.com/flutter/flutter/assets/30870216/ef2915bb-7e78-49bc-a9ce-7d7ede52771b">
Repository: flutter
Issue: ☂️ Tracking issue for any infra or test failures with iOS 18 physical devices
Labels: P2,team-ios,triaged-ios

## Test failures:

### flutter/flutter

- [ ] 

## Infra Issues:

- [ ]
Repository: flutter
Issue: Run all flutter/flutter iOS devicelab tests using iOS 18 physical device
Labels: P2,team-ios,triaged-ios

## Prerequisites

- [ ]  Xcode 16 is available in [CIPD](https://chrome-infra-packages.appspot.com/p/infra_internal/ios/xcode)
- [ ]  https://github.com/flutter/flutter/issues/148963

## Instructions to run via led
[Update to latest depot_tools](https://chromium.googlesource.com/chromium/tools/depot_tools/+/HEAD/README.md#updating) by running gclient:

To run manual led test on a Mac-14, iOS-18 staging bot:
1. `led get-builder "luci.flutter.staging:Mac_ios flutter_gallery_ios__start_up" > properties.json`
2. Replace `"sdk_version": "15a240d"` with new Xcode build version (case sensitive with CIPD version)
3. `cat properties.json | led edit -d os=Mac-14 | led edit -d device_os=iOS-18 | led edit-recipes-bundle | led launch`

❗ File issues for tests that fail and add links to the issues in https://github.com/flutter/flutter/issues/148966. This is important so we can track any fixes that need to be cherrypicked to beta/stable and so steps that are steps are not completed before issues are resolved.
Repository: flutter
Issue: Update .ci.yaml in flutter/flutter to use iOS 17 or 18
Labels: P2,team-ios,triaged-ios

## Prerequisites

- [ ] https://github.com/flutter/flutter/issues/148907
- [ ] Ensure no open issues in https://github.com/flutter/flutter/issues/148966

---

https://github.com/flutter/flutter/blob/master/.ci.yaml

```diff
- device_os: iOS-17
+ device_os: iOS-17|iOS-18

- ["device_os=iOS-17","os=Mac-14", "cpu=x86"]
+ ["device_os=iOS-17|iOS-18","os=Mac-14", "cpu=x86"]
Repository: flutter
Issue: Upgrade 25% of iOS devices to iOS 18
Labels: team-infra,P2,triaged-infra

### Type of Request

infra task

### Infrastructure Environment

Devicelab

### What is happening?

Prerequisites

- [ ] https://github.com/flutter/flutter/issues/148888
- [ ] https://github.com/flutter/flutter/issues/148968
- [ ] https://github.com/flutter/flutter/issues/148907
- [ ] Ensure no open issues in https://github.com/flutter/flutter/issues/148966

---

Upgrade ~25% of bots to iOS 18 per arch per pool (always leave at least 2 bots per arch in the try and prod pools on iOS 17 to maintain beta/stable)

- [ ] [Try pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.try&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Try pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.try&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)
- [ ] [Staging pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.staging&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Staging pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.staging&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)
- [ ] [Prod pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.prod&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Prod pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.prod&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)

When ready to upgrade, file an issue with a list of explicit bots listed by name to upgrade and include the following additional instructions:
1. Before starting upgrade, quarantine the bot
2. After upgrading device
    1. Open Xcode 16 from /opt/flutter/xcode/[insert Xcode build version]/XCode.app
    2. In the top bar, open Window > Device and Simulators
    3. The window that opens should show the connected device
    4. Accept the Trust dialog on the iPhone device
    5. If you get the dialog on the device twice, you may need to accept it once, disconnect, reconnect, and accept again.
    6. Wait for the yellow bar at the top of the Device and Simulators window to go away - It should take a minute or so to Copy cache symbols
3. Unquarantine the bot

See https://github.com/flutter/flutter/issues/142326 as example.

Note: This can create noise in iOS benchmarks as multiple iOS versions are being tested and probably should be mentioned in a PSA

### Steps to reproduce

_No response_

### Expected results

_No response_
Repository: flutter
Issue: Upgrade 50% of iOS devices to iOS 18
Labels: team-infra,P2,triaged-infra

### Type of Request

infra task

### Infrastructure Environment

Devicelab

### What is happening?

Prerequisites

- [ ] https://github.com/flutter/flutter/issues/148969 as been landed for 1-2 releases
- [ ] Ensure no open issues in https://github.com/flutter/flutter/issues/148966

---

Upgrade ~50% of bots to iOS 18 per arch per pool (always leave at least 2 bots per arch in the try and prod pools on iOS 17 to maintain beta/stable)

- [ ] [Try pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.try&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Try pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.try&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)
- [ ] [Staging pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.staging&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Staging pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.staging&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)
- [ ] [Prod pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.prod&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Prod pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.prod&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)

When ready to upgrade, file an issue with a list of explicit bots listed by name to upgrade and include the following additional instructions:
1. Before starting upgrade, quarantine the bot
2. After upgrading device
    1. Open Xcode 16 from /opt/flutter/xcode/[insert Xcode build version]/XCode.app
    2. In the top bar, open Window > Device and Simulators
    3. The window that opens should show the connected device
    4. Accept the Trust dialog on the iPhone device
    5. If you get the dialog on the device twice, you may need to accept it once, disconnect, reconnect, and accept again.
    6. Wait for the yellow bar at the top of the Device and Simulators window to go away - It should take a minute or so to Copy cache symbols
3. Unquarantine the bot

See https://github.com/flutter/flutter/issues/142326 as example.

Note: This can create noise in iOS benchmarks as multiple iOS versions are being tested and probably should be mentioned in a PSA

### Steps to reproduce

_No response_

### Expected results

_No response_
Repository: flutter
Issue: CP iOS 18 fixes for beta and stable
Labels: P2,team-ios,triaged-ios

## Prerequisites 

- [ ] https://github.com/flutter/flutter/issues/148971 has been completed for a week or 2
- [ ] Ensure all issues are fixed in https://github.com/flutter/flutter/issues/148966

## Instructions

CP any fixes made to resolve issues in https://github.com/flutter/flutter/issues/148966. This may include recipe fixes.
Repository: flutter
Issue: CP ci.yaml to use iOS 17 or 18 for beta and stable
Labels: P2,team-ios,triaged-ios

## Prerequisites 

- [ ] https://github.com/flutter/flutter/issues/148971
- [ ] https://github.com/flutter/flutter/issues/148972 - may want to wait for one release to be successful with those changes before doing this

## Instructions

CP the following:

- [ ] https://github.com/flutter/flutter/issues/148968
Repository: flutter
Issue: Upgrade remaining iOS devices to iOS 18
Labels: team-infra,P2,triaged-infra

### Type of Request

infra task

### Infrastructure Environment

Devicelab

### What is happening?

Prerequisites

- [ ] https://github.com/flutter/flutter/issues/148973 as been landed for 1-2 releases
- [ ] Ensure no open issues in https://github.com/flutter/flutter/issues/148966

---

Upgrade all remaining of bots to iOS 18 per arch per pool

- [ ] [Try pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.try&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Try pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.try&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)
- [ ] [Staging pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.staging&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Staging pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.staging&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)
- [ ] [Prod pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.prod&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Prod pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=device_os&c=os&c=status&d=asc&f=device_os%3AiOS&f=pool%3Aluci.flutter.prod&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)

When ready to upgrade, file an issue with a list of explicit bots listed by name to upgrade and include the following additional instructions:
1. Before starting upgrade, quarantine the bot
2. After upgrading device
    1. Open Xcode 16 from /opt/flutter/xcode/[insert Xcode build version]/XCode.app
    2. In the top bar, open Window > Device and Simulators
    3. The window that opens should show the connected device
    4. Accept the Trust dialog on the iPhone device
    5. If you get the dialog on the device twice, you may need to accept it once, disconnect, reconnect, and accept again.
    6. Wait for the yellow bar at the top of the Device and Simulators window to go away - It should take a minute or so to Copy cache symbols
3. Unquarantine the bot

See https://github.com/flutter/flutter/issues/142326 as example.

### Steps to reproduce

_No response_

### Expected results

_No response_
Repository: flutter
Issue: Update .ci.yaml in flutter/flutter to use iOS 18 only
Labels: P2,team-ios,triaged-ios

## Prerequisites

- [ ] https://github.com/flutter/flutter/issues/148974

---

https://github.com/flutter/flutter/blob/master/.ci.yaml

```diff
- device_os: iOS-17|iOS-18
+ device_os: iOS-18

- ["device_os=iOS-17","os=Mac-14", "cpu=x86"]
+ ["device_os=iOS-18","os=Mac-14", "cpu=x86"]
```
Repository: ollama
Issue: [Website] Library - Newest doesn't really sort with the newest releases
Labels: feature request,ollama.com

I'm not sure if it's the right place to post it, but the [https://ollama.com/library?sort=newest](https://ollama.com/library?sort=newest) **newest** sort is kinda misleading, as it doesn't take into account the last update of the model. 

For exemple with the recent Mistral update (v3), I expect the Mistral to be one of the most recent models on the list if I sort by date, but it's way further down the list.

Exemple using the **newest** sort
![image](https://github.com/ollama/ollama/assets/35169816/37359611-09ff-42c6-b0a7-dc8bf4af392c)

The current implementation of **newest** sort doesn't make sense as the only date we can see on a model page is the date of the last update. I understand that newest sort probably use some internal `created_at` field, but this somewhat feels wrong.
Repository: angular
Issue: docs: add docs for outputPath configurations
Labels: P3,area: docs

### Describe the problem that you experienced

Having to search github issues instead of docs for outputPath configurations

https://github.com/angular/angular-cli/issues/26304
https://github.com/angular/angular-cli/pull/26675

### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

How to configure the outputPath config in angular.json

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

_No response_

### If the problem is browser-specific, please specify the device, OS, browser, and version

_No response_

### Provide any additional information here in as much as detail as you can

_No response_
Repository: PowerToys
Issue: PowerToys Run: Unit converter DATA UNITS - binary issue
Labels: Issue-Bug,Status-In progress,Run-Plugin

### Microsoft PowerToys version

0.81.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

### typing ` %% 5GB in MB ` in the panel
or any other data unit conversion


### ✔️ Expected Behavior

### **4768.4MB**
Why would I even use the conversion when it's just decimal shift by the amount of zeros.
I am aware that Microsoft is still using decimal for conversion but using "mebi" etc. is something I never knew until today. I looked it up not to look like an idiot while writing this. For most power-users that glanced it over ages ago it won't make sense. 

Two possible solutions on this: 
1. Providing each results per environment with explanation to educate
2. Give the user the ability to choose how to convert data units un default and move on. 

While we're still in "transition period" for another few years (whilst being fed MB>KB decimal conversions daily) nobody would use conversion for that, you would just know or boot up a calc (or type `= 5*1000`)

Imagine that you do have this implementation and the output is:
```
5 GB = 5,000 MB  - Storage (SI System, 1960):
```
```
5 GiB = 5,120 MiB  - RAM (IEC System, 1998): 
```
```
5 GiB = 5,120 MiB  - VRAM (IEC System, 1998): 
```
```
Networking (ITU Standards, various dates): Data transfer rates typically use the decimal system (e.g., 1 Mbps = 1,000,000 bps).
Databases, Cloud Services,Software Development*: Generally follows the same SI and IEC standards as storage and RAM.
*depending on the platform and context.
```


### ❌ Actual Behavior

### **5000MB**
writing MiB is resulting in the correct thing

### Other Software

_No response_
Repository: flutter
Issue: Upgrade remaining bots in dart-internal to macOS 14.5
Labels: team-release

### Type of Request

infra task

### Infrastructure Environment

Devicelab

### What is happening?

Prerequisites
- [ ] https://github.com/flutter/flutter/issues/148893 has been completed for 1-2 releases
- [ ] Ensure no open issues in https://github.com/flutter/flutter/issues/148882

--- 
Upgrade remaining bots per arch in `luci.dart-internal.flutter` to macOS 14.5.

- [ ] [arm64 bots](https://chrome-swarming.appspot.com/botlist?c=id&c=task&c=cpu&c=os&c=status&d=asc&f=pool%3Aluci.dart-internal.flutter&f=os%3AMac&f=cpu%3Aarm&k=cpu&s=id)
- [ ] [x86 bots](https://chrome-swarming.appspot.com/botlist?c=id&c=task&c=cpu&c=os&c=status&d=asc&f=pool%3Aluci.dart-internal.flutter&f=os%3AMac&f=cpu%3Ax86&k=cpu&s=id)

When ready to upgrade, file an issue with a list of explicit bots listed by name to upgrade. See b/326078082 as example. Include request to ensure the Flutter Devicelab cert is installed as well after reimage in the issue.

### Steps to reproduce

_No response_

### Expected results

_No response_
Repository: transformers
Issue: Add Nomic Embed Code to Transformers
Labels: New model

### Model description

[Nomic Embed](https://arxiv.org/abs/2402.01613) embedding models are high performing long-context embedding models. 

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

https://huggingface.co/nomic-ai/nomic-embed-text-v1
https://huggingface.co/nomic-ai/nomic-embed-text-v1.5
https://github.com/nomic-ai/contrastors
Repository: go
Issue: runtime: memhash: use simple loop for short strings 
Labels: Performance,NeedsInvestigation,compiler/runtime

I noticed in the course of developing [starlark-go](https://github.com/google/starlark-go) that [maphash.String](https://pkg.go.dev/hash/maphash#String), which wraps `runtime.memhash` and thus `runtime.aeshashbody`, is slower than a trivial loop-based hash such as FNV for short strings (len <= 12). You might want to see whether there are gains to be made by changing `runtime.memhash`.

In the M1 benchmark below, "hard" is the AES 128-bit hash, soft is the FNV byte-at-a-time hash.
```
BenchmarkStringHash/hard-1-8         	425380128	         2.724 ns/op // slower
BenchmarkStringHash/soft-1-8         	968800584	         1.253 ns/op
BenchmarkStringHash/hard-2-8         	285782469	         4.155 ns/op // slower
BenchmarkStringHash/soft-2-8         	482670777	         2.543 ns/op
BenchmarkStringHash/hard-4-8         	238793694	         5.426 ns/op // slower
BenchmarkStringHash/soft-4-8         	359522328	         3.318 ns/op
BenchmarkStringHash/hard-8-8         	180634999	         6.658 ns/op // slower
BenchmarkStringHash/soft-8-8         	241373414	         4.995 ns/op
BenchmarkStringHash/hard-16-8        	205045033	         5.823 ns/op
BenchmarkStringHash/soft-16-8        	144273086	         8.322 ns/op
BenchmarkStringHash/hard-32-8        	206178392	         5.844 ns/op
BenchmarkStringHash/soft-32-8        	80871846	        14.96 ns/op
BenchmarkStringHash/hard-64-8        	175336156	         6.891 ns/op
BenchmarkStringHash/soft-64-8        	42610798	        28.30 ns/op
BenchmarkStringHash/hard-128-8       	125781333	         9.542 ns/op
BenchmarkStringHash/soft-128-8       	18739946	        64.47 ns/op
BenchmarkStringHash/hard-256-8       	59081041	        20.63 ns/op
BenchmarkStringHash/soft-256-8       	10185776	       118.5 ns/op
BenchmarkStringHash/hard-512-8       	23744743	        51.08 ns/op
BenchmarkStringHash/soft-512-8       	 5342551	       224.6 ns/op
BenchmarkStringHash/hard-1024-8      	10823535	       111.2 ns/op
BenchmarkStringHash/soft-1024-8      	 2731977	       438.0 ns/op
```