[google_sign_in] Slight cleanup in GoogleSignInPlugin

Use switch instead of if/else and show all possible states
Handle the case of synchronous failure in signInSilently()
by checking isComplete() instead of isSuccessful()

Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [relevant style guides] and ran [the auto-formatter]. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the [CLA].
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy], or this PR is [exempt from version changes].
[x] I updated CHANGELOG.md to add a description of the change, [following repository CHANGELOG style].
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

@tvolkert Does this just need autosubmit, or were you planning on changing something before landing it?

I was naively thinking I could find time to add more tests, but I can do that in a separate PR -- this is ready to land.


Timed Inview shortcut

Implementation to be pushed :)

Thank you for the PR, but Waypoints is going to stick with handling only the core scroll use case it was designed for. Timing additions can be added at the user level in the handlers.

Okay :) maybe we could link it on the website so future users will not need
to redo it themselves :)
On Thu, Apr 16, 2015, 17:50 Caleb Troughton<EMAIL_ADDRESS>wrote:

Closed #397 https://github.com/imakewebthings/waypoints/pull/397.
—
Reply to this email directly or view it on GitHub
https://github.com/imakewebthings/waypoints/pull/397#event-283180434.

Such as creating a shortcut center :)
On Apr 16, 2015 7:14 PM, "Gabor Bernat"<EMAIL_ADDRESS>wrote:

Okay :) maybe we could link it on the website so future users will not
need to redo it themselves :)
On Thu, Apr 16, 2015, 17:50 Caleb Troughton<EMAIL_ADDRESS>wrote:

Closed #397 https://github.com/imakewebthings/waypoints/pull/397.
—
Reply to this email directly or view it on GitHub
https://github.com/imakewebthings/waypoints/pull/397#event-283180434.


Grab data from API

We need to pull the next 48 hours of data for the current location.

API docs https://api.carbonintensity.org.uk/


http://eudat-b2safe.github.io/B2HANDLE/authentication.html#using-client-certificates

The 3d method described is as follows:
By adding the usernames (300:foo/bar and 301:foo/bar) to any HS_VLIST entry referenced somewhere in 0.NA/foo. For example, if there is a HS_ADMIN at index 101 of 0.NA/foo which points to a HS_VLIST at the index 200 in 0.NA/foo, which points to a HS_VLIST at index 200 in foo/admin, which points to a HS_SECKEY at index 300 in ‘foo/bar’ - then 300:foo/bar is a username with all the permissions stated in the HS_ADMIN entry at the index 101 of 0.NA/foo.
Suddenly foo/admin is mentioned. And the example shown also talks about foo/bar. There seems to be a miscommunication here.
We might even add a fourth method. Which is a derivate of the 3th method. This makes sure the 0.NA/foo has to be updated only once. But gives even more flexibility:
For example, if there is a HS_ADMIN at index 101 of 0.NA/foo which points to a HS_VLIST at the index 200 in 0.NA/foo, which points to a HS_VLIST at index 200 in foo/admin, which points to several HS_VLIST at index 200 in for instance foo/user01, foo/user02. For each there is a HS_VLIST which points to a HS_SECKEY at index 300 in ‘foo/user01’ - then 300:foo/user1 is a username with all the permissions stated in the HS_ADMIN entry at the index 101 of 0.NA/foo.
 They either can use the default 200:0.NA/foo as the handle owner when generating handles or use 200:foo/user0{1,2} as the handle owner. This makes sure only the handle owner can change handles.

This looks like a documentation issue to me that has not been addressed in one of today's PRs. If you want it included in the v1.0.1 release, please create a PR, otherwise I will proceed with the release. I think it is safe to update the docs also after the release.

I think the documentation can be updated later for this.
Go ahead with the release.

Hi,
I've updated the documentation and created #PR 67. I guess this can be included in the next release 1.0.2.

PR #67 merged. Will be included in 1.0.2.


Testnet fix

It seems the testnet asset list is not matching what's on testnet @JeremyParish69

don't filter unverified assets from pools on testnet

We don't use the 'unverified' keyword for any testnet assets, so I don't expect this to change anything...


Remove /data/ folder

Update docs and fetch.sample_shp() to eliminate need the Disco_deep.zip and Roosevelt_Island.zip shapefiles.

[ ] remove /data folder
[ ] remove fetch.sample_shp()
[ ] fix functions that use fetch.sample_shp()

ignored sample shapefiles in PR #126

pretty sure this is already done, since the data/ folder should be automatically ignored.


How is positive branch being trained on Image + Text?

Looking at your model code from here in def model(), you treat x1 as Image and the remaining x2 , x3 both as a Text model while in your blog explanatio here, you have said that

The model takes 3 inputs: The image (which is the anchor), the image title+description ( the positive example) and the third input is some randomly sampled text (the negative example).

Can you please explain on this one?

Hello,
The image => x1
title+description => x2 => positive example
random text => x2 => negative example
Best,


improve detailed memory popup

as a follow-up to recent introduction of detailed memory popup I suggest to do:
1. paint yellow when SharedCache and MemTable have reached 100% of their limit
2. paint red when SharedCache and MemTable are over their limit more than 5%
...and be ready that consumption could be over limit.

Show the whole bar status as:

warn if exceed soft limit + 5%
danger if exceed soft limit + 5% and exceed hard limit - 15%

Theoretically it may be placed when we about to reach SoftLimit (and excess TargetUtilization)
Maybe somewhere in between (TargetUtilization + SoftLimit) / 2

Theoretically it may be placed when we about to reach SoftLimit (and excess TargetUtilization)
Maybe somewhere in between (TargetUtilization + SoftLimit) / 2

this is too complicated to implement on UI side. what is wrong with just SoftLimit alone?
and where did you get 5% number from? I don't think it's a good idea to keep that logic on UI either.

5% is just a reasonable epsilon to compare numbers, you may pick whatever you want
or just draw it red when it exceed without a gap

@adameat we didn't manage to estimate
what do you ask to be done?

@adameat we didn't manage to estimate what do you ask to be done?

nothing. I suggest to close it without any actions for now. let's have time to collect feedback about what we've already done.


"unsupported layout" error

When running swift build I'm getting following error:
$ swift build
error: the package has an unsupported layout, unexpected source file(s) found: Packages/AEXML-4.0.1/Tests/AEXMLTests.swift
fix: move the file(s) inside a module

mkdir Packages/AEXML-4.0.1/Tests/AEXMLTests
mv Packages/AEXML-4.0.1/Tests/AEXMLTests.swift Packages/AEXML-4.0.1/Tests/AEXMLTests
swift build

Thanks for reporting, this should be fixed now in 4.0.2.


CoE fails to install without Creator Kit Core

Please update the instructions to remind users to install the Creator Kit Core before attempting to import the Core kit. Right befoore this section.
https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#set-up-the-inventory-components-using-the-setup-wizard

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 9fe69498-a485-5379-97ff-53fbe029f11a
Version Independent ID: 5b3f9705-9e49-1575-4ae7-0293d12b739c
Content: Set up inventory components - Power Platform
Content Source: power-platform/guidance/coe/setup-core-components.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Thanks for your comment, @jdottdotmess. This issue has been assigned to the doc author for review.

Hello,
this is already highlighted here in the Before you Start section

https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#before-you-start


McMMO-like Skills

Not a huge fan of the various style and other small changes being included in this as their not related but it does all work

Yeah, I managed to forget to switch branches and rewriting history on github is bad practice.
The TODO for now is to simply add skills, which I'm leaving up to you. Let me know if you need help.

Closing for being outdated. I'll re-open this later once I get around to it.


New package: DataEnabledControl v1.0.0-DEV

Registering package: DataEnabledControl
Repository: https://github.com/msramada/DataEnabledControl.jl
Created by: @msramada
Version: v1.0.0-DEV
Commit: 7f18a13ce4e6e8b5f08796e3a55757e8af8de894
Git reference: HEAD
Description: This is the Julia implementation of the behavioral control DeePC algorithm.

ok


Adds wasm.Store API to get exported module and host functions

This adds this interface wasm.Store which gives access to functions in
a store without leaking an API to change the store. This is primarily to
support configuration use cases where post-initialization, there's no
need or desire to mutate the store. This also backfills codecs needed to
handle float results.
// Store allows access to instantiated modules and host functions
type Store interface {
	// ModuleExports returns exports from an instantiated module or false if it wasn't.
	ModuleExports(moduleName string) (ModuleExports, bool)

	// HostExports returns exported host functions for the moduleName or false there are none.
	HostExports(moduleName string) (HostExports, bool)
}

While ModuleExports are returned on wazero.InstantiateModule, they can also be accessed by module name later. Here's an example of decoupling where central configuration configures the store and plugins use it:
// Config wiring can instantiate the store and locate the name of the function desired
exports, _ := store.ModuleExports("math")
addFloat, _ := exports.Function("AddFloat")

// That function could be used directly or implement a friendlier interface.
results, _ := addFloat(context.Background(), wasm.EncodeF64(1.5),
wasm.EncodeF64(1.5))
res := wasm.DecodeF64(result[0])) // 3.0!

This design also allows unwinding of function dependencies, ex where a host function needs to use another host function:
	// built-in WASI function to write a random value to memory
	randomGet := func(ctx wasm.ModuleContext, buf, bufLen uint32) wasi.Errno {
		panic("unimplemented")
	}

	goFunc := func(ctx wasm.ModuleContext) {
		// Write 8 random bytes to memory using WASI.
		errno := randomGet(ctx, 0, 8)
	--snip--

	// Configure WASI and implement the function to use it
	we, err := wazero.ExportHostFunctions(store, wasi.ModuleSnapshotPreview1, wazero.WASISnapshotPreview1())
	require.NoError(t, err)
	randomGetFn, ok := we.Function("random_get")
	require.True(t, ok)

	// Implement the function pointer. This mainly shows how you can decouple a host function dependency.
	randomGet = func(ctx wasm.ModuleContext, buf, bufLen uint32) wasi.Errno {
		res, err := randomGetFn(ctx, uint64(buf), uint64(bufLen))
		require.NoError(t, err)
		return wasi.Errno(res[0])
	}

Ancillary changes:

NewStoreWithConfig() no longer returns an error or takes host function config
HostFunctionCallContext has been renamed to ModuleContext
wasi.Errno was converted back to a uint32 alias to match mapped types

I added a comment to all the places we do manual NaN comparison which are ultimately caused by this "won't fix" https://github.com/stretchr/testify/issues/624

Thanks for the feedback and the help with the float bugs @mathetake and @nullpo-head!


Added Hindi translation.(Only Root READMe.md)

Added Hindi language with README.hi.md name.
Only the root READMe.md for now.

ok sure

pls tell where to enter it , as i am unable to find  where to add.

https://github.com/matteobruni/tsparticles/issues/895#issuecomment-702174175
Translation folder like in #897

done pls check

Pls merge it .

thanks to check .

Pls tell if can help

Don't worry, mistakes can happen to everyone 😉

I need to wait automated checks to merge the PR

Thank you very much

Thank you for your contribution


Calculate standard error of the intercept in linregress

Currently linregress from scipy.stats calculates standard error of the gradient, but not the intercept. The two are related, but would require re-calculating sum of x^2 outside of the linregress function. I propose this gets added to the body of linregress (where sum of x^2 is already known) and put into LinregressResult namedtuple.
I will submit a PR with my proposed solution just after I post this.

Looks like this was merged in #12983 so closing


Update DefaultPlayerUiController.kt

Adding an implemented method for progress bar . . . . Since a default progress bar cannot be disabled or hidden, a custom progress bar in a controlsContainer view can be hidden by implementing an overridden method. Also, making sure that method is declared in that interface class PlayerUiController

Both the default progress bar from YouTube and a customized progress bar within controlContainer view are spinning at the same time, and users may either get confused or may think something is behind going on. It would be better if a progress bar in a controlContainer should have been hidden.

Hi, starting from version 11 this shouldn't not be an issue anymore. Since the default UI is webUi. So there is only one progress bar.

Ok thanks, when you say version 11 do you mean android version 11 or your repository version 11 though? I have seen your latest repo version is 11.

Yes I meant version 11 of the library.


P.S.A Manifest schema 1.2 validation disabled

Description of the new feature/enhancement
YamlCreate was updated to generate 1.2 schema manifests.
wingetcreate was also updated to generate 1.2 schema manifests. (edit: 8/8)
These are currently blocked by validation and will be re-enabled after portable packages start being accepted.
The REST schema needs to be updated with the 1.2 schema (we're dual publishing) which is why this was disabled (in addition to portable packages).
Proposed technical implementation details (optional)
Please just switch the Manifest Version back to 1.1.0 in the PR after creating the manifest. (edit: 8/8)
FYI, I'm aiming to open up 1.2 schema validation in the community repository ~tomorrow August 9th, 2022 (EOD Pacific Time). (edit: 8/9)~ by Tuesday August 16th. (edit 9/13).

Hi, it seems that this not only affects YamlCreate but also wingetcreate for those that use the last release (version <IP_ADDRESS>) as updating with this will lead to the use of 1.2 schema manifests (see for example the files generated by the automated update of Ferdium.Nightly when using wingetcreate update).

@Alphrag thanks for the update. I edited the description above.

We hit a snag. It's looking more like the end of the week. We will get it out ASAP.

Updated to Tuesday August 16th.

Hi. So, is the validation pipeline is ready for a new schema yet?

Updated to Tuesday August 16th.

Hi. So, is the validation pipeline is ready for a new schema yet?

They will most likely start prepping in 2-3 hours, so hopefully everything will go as planed and be live tonight :)

Testing went well yesterday. I haven't heard any reason not to ship it today. As @OfficialEsco guessed, we will start the work in a couple of hours. Most of the engineers are in Pacific Time.

@denelon any updates?

I was out yesterday. I've just confirmed the team is working on deploying the changes now.

Manifest validation for the 1.2 schema is now enabled. We will run through open PRs to trigger builds. Our moderators can also trigger builds for these PRs.


When executing tests, make sure to leave off trailing slash.

Previously, when executing tasks, we added a trailing slash when hitting the URL that ran the tests.  There was a failure case where the user manually closed the modal (going to fix that in a separate PR), the user was left at a URL like .../Conformance/.  When clicking on the rerun button, it would just append Conformance to the previous URL, so it now hit .../Conformance/Conformance.
This fixes that by simply sending the user to ../Conformance instead, so using trailing slashes doesn't break anything.
You can test by allowing the SSL timeout issue to manifest itself, then click 'off' the modal, then click Rerun.  This fixes that problem, and shouldn't cause any other problems.

Fixed a merge conflict caused by another recent pull request


Contributors

It will be more attractive if we give contributors a box and also adding a arrow beside it..

ya sharing now give me 10 mins

first one

okay


Deleting PV in kubernetes is not deleting volume on gluster w/ heketi

i have a setup a storage class backed by gluster w/ heketi.
I have provisioned few volumes with this dynamic storage volume but when i delete PV its not deleting underlying volume automatically

@debianmaster can you provide me more details and logs ? also which version of kube is in use here ?

OpenShift Master:
v1.5.0+031cbe4
Kubernetes Master:
v1.5.2+43a9be4
My disks were 50GB previously and i got no storage error, (which seems right) , but now  i increased it to 100GB.  and restarted heketi pod,   i'm still getting following error.
Failed to provision volume with StorageClass "default": glusterfs: create volume err: error creating volume Error calling v.allocBricksInCluster: database is in read-only mode.

i have restarted gluster DaemonSets (by killing)  and also heketi still see that database ready only mode error

@debianmaster Can you restart the heketi pod and paste the logs from the point where it starts coming back up?

Heketi v4.0.0-57-g27e7ea4
[heketi] INFO 2017/04/24 11:32:18 Loaded kubernetes executor
[heketi] WARNING 2017/04/24 11:32:18 Unable to open database.  Retrying using read only mode
[heketi] INFO 2017/04/24 11:32:18 Loaded simple allocator
[heketi] INFO 2017/04/24 11:32:18 GlusterFS Application Loaded
Authorization loaded
Listening on port 8080
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 735.351µs
[asynchttp] INFO 2017/04/24 11:32:24 Started job 5ac838d25ba64ecfe7e08315674713c4
[heketi] INFO 2017/04/24 11:32:24 Creating volume 21dc2b01f95b207ccd224ab09a07954a
[heketi] INFO 2017/04/24 11:32:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:32:24 Completed job 5ac838d25ba64ecfe7e08315674713c4 in 2.078337ms
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 240.783µs
[asynchttp] INFO 2017/04/24 11:32:24 Started job 33692bcea29f867d165ccdeef20f6fbd
[heketi] INFO 2017/04/24 11:32:24 Creating volume 918a11c044201679511ead21dbfb182f
[heketi] INFO 2017/04/24 11:32:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:32:24 Completed job 33692bcea29f867d165ccdeef20f6fbd in 698.725µs
[negroni] Started GET /queue/5ac838d25ba64ecfe7e08315674713c4
[negroni] Completed 500 Internal Server Error in 88.756µs
[negroni] Started GET /queue/33692bcea29f867d165ccdeef20f6fbd
[negroni] Completed 500 Internal Server Error in 43.042µs
[heketi] ERROR 2017/04/24 11:32:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 169.386µs
[asynchttp] INFO 2017/04/24 11:32:39 Started job cb43ed7de7bc3bcb9cd34365d7038a41
[heketi] INFO 2017/04/24 11:32:39 Creating volume 86a96c805ef47e35e7cf514ee49e73fd
[heketi] ERROR 2017/04/24 11:32:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:32:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:32:39 Completed job cb43ed7de7bc3bcb9cd34365d7038a41 in 1.01767ms
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 104.023µs
[asynchttp] INFO 2017/04/24 11:32:39 Started job 84b1a9d3d5eaa0c7f5e3195ea6a272bd
[heketi] INFO 2017/04/24 11:32:39 Creating volume 9ba7cd1ae936acfa8e211faf9c7a833e
[heketi] INFO 2017/04/24 11:32:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:32:39 Completed job 84b1a9d3d5eaa0c7f5e3195ea6a272bd in 607.641µs
[negroni] Started GET /queue/cb43ed7de7bc3bcb9cd34365d7038a41
[negroni] Completed 500 Internal Server Error in 75.599µs
[negroni] Started GET /queue/84b1a9d3d5eaa0c7f5e3195ea6a272bd
[negroni] Completed 500 Internal Server Error in 67.341µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 181.19µs
[asynchttp] INFO 2017/04/24 11:32:54 Started job f42076002f8dde52b68463b5885b35ba
[heketi] INFO 2017/04/24 11:32:54 Creating volume 54f38956790fce0b5981f9defcfcfdbc
[heketi] INFO 2017/04/24 11:32:54 brick_num: 0
[asynchttp] INFO 2017/04/24 11:32:54 Completed job f42076002f8dde52b68463b5885b35ba in 4.385998ms
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 163.506µs
[asynchttp] INFO 2017/04/24 11:32:54 Started job c9658d6f9e9a5fb6fa954f39b794b5b5
[heketi] INFO 2017/04/24 11:32:54 Creating volume 69b3a566f6b013af7aa749d43b466f68
[heketi] INFO 2017/04/24 11:32:54 brick_num: 0
[asynchttp] INFO 2017/04/24 11:32:54 Completed job c9658d6f9e9a5fb6fa954f39b794b5b5 in 610.964µs
[negroni] Started GET /queue/f42076002f8dde52b68463b5885b35ba
[negroni] Completed 500 Internal Server Error in 83.412µs
[heketi] ERROR 2017/04/24 11:32:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:32:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started GET /queue/c9658d6f9e9a5fb6fa954f39b794b5b5
[negroni] Completed 500 Internal Server Error in 64.039µs
[negroni] Started POST /volumes
[heketi] ERROR 2017/04/24 11:33:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:09 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Completed 202 Accepted in 549.541µs
[asynchttp] INFO 2017/04/24 11:33:09 Started job 8b6b253f80de8afe06d741ab88d322e8
[heketi] INFO 2017/04/24 11:33:09 Creating volume c18795c0a62d0378d204fa9b0a676d23
[heketi] INFO 2017/04/24 11:33:09 brick_num: 0
[asynchttp] INFO 2017/04/24 11:33:09 Completed job 8b6b253f80de8afe06d741ab88d322e8 in 737.056µs
[negroni] Started GET /queue/8b6b253f80de8afe06d741ab88d322e8
[negroni] Completed 500 Internal Server Error in 92.453µs
[heketi] ERROR 2017/04/24 11:33:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:09 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 184.729µs
[asynchttp] INFO 2017/04/24 11:33:09 Started job fd5bf24afa83f977f448208b1a5d8507
[heketi] INFO 2017/04/24 11:33:09 Creating volume 58ebd326b87ff38f535ddf3a92dca362
[heketi] INFO 2017/04/24 11:33:09 brick_num: 0
[asynchttp] INFO 2017/04/24 11:33:09 Completed job fd5bf24afa83f977f448208b1a5d8507 in 727.503µs
[negroni] Started GET /queue/fd5bf24afa83f977f448208b1a5d8507
[negroni] Completed 500 Internal Server Error in 86.055µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 176.067µs
[asynchttp] INFO 2017/04/24 11:33:24 Started job 5b73e827dc21fac22ec342633bb4165c
[heketi] INFO 2017/04/24 11:33:24 Creating volume ce1d02813672a7aa433492012bf71ebb
[heketi] ERROR 2017/04/24 11:33:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:33:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:33:24 Completed job 5b73e827dc21fac22ec342633bb4165c in 1.003952ms
[negroni] Started GET /queue/5b73e827dc21fac22ec342633bb4165c
[negroni] Completed 500 Internal Server Error in 80.524µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 98.002µs
[asynchttp] INFO 2017/04/24 11:33:24 Started job 7639172d29537fc11390f723c82e2641
[heketi] INFO 2017/04/24 11:33:24 Creating volume 06bd6964d8a99856b240dd90fc544ea1
[heketi] ERROR 2017/04/24 11:33:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:33:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:33:24 Completed job 7639172d29537fc11390f723c82e2641 in 717.965µs
[negroni] Started GET /queue/7639172d29537fc11390f723c82e2641
[negroni] Completed 500 Internal Server Error in 59.848µs
[heketi] ERROR 2017/04/24 11:33:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 245.159µs
[asynchttp] INFO 2017/04/24 11:33:39 Started job 798c2ae3ba8b6480d43b6c11022b446f
[heketi] INFO 2017/04/24 11:33:39 Creating volume 5fb706cfdf55c5ef0bfd6c464d42455d
[heketi] INFO 2017/04/24 11:33:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:33:39 Completed job 798c2ae3ba8b6480d43b6c11022b446f in 844.851µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 147.371µs
[asynchttp] INFO 2017/04/24 11:33:39 Started job 44247a00d6b0ed7a93d59e1d26cf2abf
[heketi] INFO 2017/04/24 11:33:39 Creating volume c495a3009cb8761b0575d859b4a374bf
[heketi] INFO 2017/04/24 11:33:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:33:39 Completed job 44247a00d6b0ed7a93d59e1d26cf2abf in 632.587µs
[negroni] Started GET /queue/798c2ae3ba8b6480d43b6c11022b446f
[negroni] Completed 500 Internal Server Error in 85.886µs
[negroni] Started GET /queue/44247a00d6b0ed7a93d59e1d26cf2abf
[negroni] Completed 500 Internal Server Error in 75.35µs
[heketi] ERROR 2017/04/24 11:33:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 219.09µs
[asynchttp] INFO 2017/04/24 11:33:54 Started job ab96a60c47a7592fa8c8693c78ddba38
[heketi] INFO 2017/04/24 11:33:54 Creating volume 6785440ed64a6ee617d360f377ce37a7
[heketi] INFO 2017/04/24 11:33:54 brick_num: 0
[asynchttp] INFO 2017/04/24 11:33:54 Completed job ab96a60c47a7592fa8c8693c78ddba38 in 884.413µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 130.356µs
[asynchttp] INFO 2017/04/24 11:33:54 Started job 2e5e94b16e36ce3588910f0eea551acc
[heketi] INFO 2017/04/24 11:33:54 Creating volume 03e1ad5f5c02d99730608e7540dcfb26
[heketi] INFO 2017/04/24 11:33:54 brick_num: 0
[asynchttp] INFO 2017/04/24 11:33:54 Completed job 2e5e94b16e36ce3588910f0eea551acc in 705.094µs
[negroni] Started GET /queue/2e5e94b16e36ce3588910f0eea551acc
[negroni] Completed 500 Internal Server Error in 78.332µs
[negroni] Started GET /queue/ab96a60c47a7592fa8c8693c78ddba38
[negroni] Completed 500 Internal Server Error in 45.787µs
[heketi] ERROR 2017/04/24 11:33:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:33:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:09 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 178.808µs
[asynchttp] INFO 2017/04/24 11:34:09 Started job f2bf7860f572b0bc796e88333886a687
[heketi] INFO 2017/04/24 11:34:09 Creating volume eb2db6279f0e02236954550e827315c4
[heketi] INFO 2017/04/24 11:34:09 brick_num: 0
[asynchttp] INFO 2017/04/24 11:34:09 Completed job f2bf7860f572b0bc796e88333886a687 in 924.276µs
[negroni] Started GET /queue/f2bf7860f572b0bc796e88333886a687
[negroni] Completed 500 Internal Server Error in 75.65µs
[heketi] ERROR 2017/04/24 11:34:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:09 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 133.054µs
[asynchttp] INFO 2017/04/24 11:34:09 Started job d48f5fb0ffd46da615f3bc28bc4754b3
[heketi] INFO 2017/04/24 11:34:09 Creating volume 74978a5cfc4aa369b46839b70d88c142
[heketi] INFO 2017/04/24 11:34:09 brick_num: 0
[asynchttp] INFO 2017/04/24 11:34:09 Completed job d48f5fb0ffd46da615f3bc28bc4754b3 in 914.321µs
[negroni] Started GET /queue/d48f5fb0ffd46da615f3bc28bc4754b3
[negroni] Completed 500 Internal Server Error in 65.367µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 509.384µs
[asynchttp] INFO 2017/04/24 11:34:24 Started job 9d1a4333db1f9f67b0dac8d1566c1f4d
[heketi] INFO 2017/04/24 11:34:24 Creating volume 6d4c6f5a89cc92b2d40957ae6b76ac25
[heketi] ERROR 2017/04/24 11:34:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:34:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:34:24 Completed job 9d1a4333db1f9f67b0dac8d1566c1f4d in 1.169951ms
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 101.554µs
[asynchttp] INFO 2017/04/24 11:34:24 Started job 231ce63a4a9d985640d8848514cb3694
[heketi] INFO 2017/04/24 11:34:24 Creating volume 943e5fb8ff4fab389afbff6e4dcaeeae
[heketi] INFO 2017/04/24 11:34:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:34:24 Completed job 231ce63a4a9d985640d8848514cb3694 in 654.238µs
[negroni] Started GET /queue/9d1a4333db1f9f67b0dac8d1566c1f4d
[negroni] Completed 500 Internal Server Error in 75.882µs
[negroni] Started GET /queue/231ce63a4a9d985640d8848514cb3694
[negroni] Completed 500 Internal Server Error in 77.351µs
[heketi] ERROR 2017/04/24 11:34:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 176.093µs
[asynchttp] INFO 2017/04/24 11:34:39 Started job adbd582658367c9656f485e25698a4ed
[heketi] INFO 2017/04/24 11:34:39 Creating volume 57c7e3392c205a6eb5d8e58c52f5d119
[heketi] INFO 2017/04/24 11:34:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:34:39 Completed job adbd582658367c9656f485e25698a4ed in 843.757µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 116.165µs
[asynchttp] INFO 2017/04/24 11:34:39 Started job 4121196d91a554fb533092afa1def5d7
[heketi] INFO 2017/04/24 11:34:39 Creating volume 477d6f0a1023ec1a2c46fbd90a17401e
[heketi] INFO 2017/04/24 11:34:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:34:39 Completed job 4121196d91a554fb533092afa1def5d7 in 635.208µs
[negroni] Started GET /queue/adbd582658367c9656f485e25698a4ed
[negroni] Completed 500 Internal Server Error in 94.771µs
[negroni] Started GET /queue/4121196d91a554fb533092afa1def5d7
[negroni] Completed 500 Internal Server Error in 41.669µs
[negroni] Started POST /volumes
[heketi] ERROR 2017/04/24 11:34:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:34:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Completed 202 Accepted in 67.095634ms
[asynchttp] INFO 2017/04/24 11:34:54 Started job f9c1150695b709cccf49e53de579f211
[heketi] INFO 2017/04/24 11:34:54 Creating volume d7e7177c45b2bf90c9e6ab40a076eca5
[heketi] INFO 2017/04/24 11:34:54 brick_num: 0
[asynchttp] INFO 2017/04/24 11:34:54 Completed job f9c1150695b709cccf49e53de579f211 in 836.735µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 202.707µs
[asynchttp] INFO 2017/04/24 11:34:54 Started job f692c9a476109fee6fc9436ccd696e85
[heketi] INFO 2017/04/24 11:34:54 Creating volume 23c04ae3d36580b92fb2e9bf7da097fd
[heketi] INFO 2017/04/24 11:34:54 brick_num: 0
[asynchttp] INFO 2017/04/24 11:34:54 Completed job f692c9a476109fee6fc9436ccd696e85 in 650.293µs
[negroni] Started GET /queue/f9c1150695b709cccf49e53de579f211
[negroni] Completed 500 Internal Server Error in 88.178µs
[negroni] Started GET /queue/f692c9a476109fee6fc9436ccd696e85
[negroni] Completed 500 Internal Server Error in 40.837µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 613.505µs
[asynchttp] INFO 2017/04/24 11:35:09 Started job 21c7c7e96a5bfc62e054be7c7e934689
[heketi] INFO 2017/04/24 11:35:09 Creating volume 481456f74c49510ad7bbd0e32eb2a563
[heketi] INFO 2017/04/24 11:35:09 brick_num: 0
[asynchttp] INFO 2017/04/24 11:35:09 Completed job 21c7c7e96a5bfc62e054be7c7e934689 in 1.216958ms
[heketi] ERROR 2017/04/24 11:35:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:09 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 173.166µs
[asynchttp] INFO 2017/04/24 11:35:09 Started job 4be651549ddbc8cc657f47638c5ee3e6
[heketi] INFO 2017/04/24 11:35:09 Creating volume e72e2e1856d4989f7c65de6e1a332721
[heketi] ERROR 2017/04/24 11:35:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:09 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:35:09 brick_num: 0
[asynchttp] INFO 2017/04/24 11:35:09 Completed job 4be651549ddbc8cc657f47638c5ee3e6 in 767.981µs
[negroni] Started GET /queue/21c7c7e96a5bfc62e054be7c7e934689
[negroni] Completed 500 Internal Server Error in 78.358µs
[negroni] Started GET /queue/4be651549ddbc8cc657f47638c5ee3e6
[negroni] Completed 500 Internal Server Error in 42.179µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 168.881µs
[asynchttp] INFO 2017/04/24 11:35:24 Started job 1a3e19fbc3a1ba32c1e290bb1b712374
[heketi] INFO 2017/04/24 11:35:24 Creating volume c0f1803e5359e9430533986abd1afcd8
[heketi] ERROR 2017/04/24 11:35:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:35:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:35:24 Completed job 1a3e19fbc3a1ba32c1e290bb1b712374 in 1.109376ms
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 759.801µs
[heketi] ERROR 2017/04/24 11:35:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[asynchttp] INFO 2017/04/24 11:35:24 Started job 01fcdd0fb72c0943f059638e95c96126
[heketi] INFO 2017/04/24 11:35:24 Creating volume 0061d2b32cf18d12e7cc882c156e5568
[heketi] INFO 2017/04/24 11:35:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:35:24 Completed job 01fcdd0fb72c0943f059638e95c96126 in 865.098µs
[negroni] Started GET /queue/01fcdd0fb72c0943f059638e95c96126
[negroni] Completed 500 Internal Server Error in 99.422µs
[negroni] Started GET /queue/1a3e19fbc3a1ba32c1e290bb1b712374
[negroni] Completed 500 Internal Server Error in 74.521µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 352.344µs
[heketi] ERROR 2017/04/24 11:35:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[asynchttp] INFO 2017/04/24 11:35:39 Started job 139d045eff0289ded3251988b25eb0f9
[heketi] INFO 2017/04/24 11:35:39 Creating volume 4639880c01b30f616ad9eca2aeabc66c
[heketi] INFO 2017/04/24 11:35:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:35:39 Completed job 139d045eff0289ded3251988b25eb0f9 in 819.578µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 774.621µs
[heketi] ERROR 2017/04/24 11:35:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[asynchttp] INFO 2017/04/24 11:35:39 Started job 5401cad00308a3bfc8f1b301ede47631
[heketi] INFO 2017/04/24 11:35:39 Creating volume 0e8fb6bc6245f52a63f1b4bd4f922979
[heketi] INFO 2017/04/24 11:35:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:35:39 Completed job 5401cad00308a3bfc8f1b301ede47631 in 708.601µs
[negroni] Started GET /queue/139d045eff0289ded3251988b25eb0f9
[negroni] Completed 500 Internal Server Error in 106.851µs
[negroni] Started GET /queue/5401cad00308a3bfc8f1b301ede47631
[negroni] Completed 500 Internal Server Error in 43.412µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 172.159µs
[asynchttp] INFO 2017/04/24 11:35:54 Started job 4736e63d1795d994aae1d2a5f2c4303c
[heketi] INFO 2017/04/24 11:35:54 Creating volume 89425a5eb21019ae0675c225e313434f
[heketi] ERROR 2017/04/24 11:35:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:35:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:35:54 brick_num: 0
[asynchttp] INFO 2017/04/24 11:35:54 Completed job 4736e63d1795d994aae1d2a5f2c4303c in 1.003371ms
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 101.368µs
[asynchttp] INFO 2017/04/24 11:35:54 Started job 4930e85fd29def20576c3c46a77b4a6b
[heketi] INFO 2017/04/24 11:35:54 Creating volume cc3c9b565807c8f4e7c656bae2982cc4
[heketi] INFO 2017/04/24 11:35:54 brick_num: 0
[asynchttp] INFO 2017/04/24 11:35:54 Completed job 4930e85fd29def20576c3c46a77b4a6b in 716.502µs
[negroni] Started GET /queue/4930e85fd29def20576c3c46a77b4a6b
[negroni] Completed 500 Internal Server Error in 80.269µs
[negroni] Started GET /queue/4736e63d1795d994aae1d2a5f2c4303c
[negroni] Completed 500 Internal Server Error in 63.702µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 515.754µs
[asynchttp] INFO 2017/04/24 11:36:09 Started job 3d8820343f5ff2fa8b5b60e29f4a416b
[heketi] INFO 2017/04/24 11:36:09 Creating volume 99edcd2ee905ee9130a5009fb96cfe70
[heketi] ERROR 2017/04/24 11:36:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:09 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:36:09 brick_num: 0
[asynchttp] INFO 2017/04/24 11:36:09 Completed job 3d8820343f5ff2fa8b5b60e29f4a416b in 1.380268ms
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 181.663µs
[asynchttp] INFO 2017/04/24 11:36:09 Started job 95219ae40cd191c3a17ea271afb82b11
[heketi] INFO 2017/04/24 11:36:09 Creating volume 668106e46d644a828e6434acddbb0f55
[heketi] ERROR 2017/04/24 11:36:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:09 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:36:09 brick_num: 0
[asynchttp] INFO 2017/04/24 11:36:09 Completed job 95219ae40cd191c3a17ea271afb82b11 in 885.904µs
[negroni] Started GET /queue/3d8820343f5ff2fa8b5b60e29f4a416b
[negroni] Completed 500 Internal Server Error in 78.19µs
[negroni] Started GET /queue/95219ae40cd191c3a17ea271afb82b11
[negroni] Completed 500 Internal Server Error in 70.674µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 188.918µs
[asynchttp] INFO 2017/04/24 11:36:24 Started job 8161accbd0ebbe904fa04a5d5c6d92dc
[heketi] INFO 2017/04/24 11:36:24 Creating volume 2045bf9eef11d28aa32632fd7446521c
[heketi] ERROR 2017/04/24 11:36:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:36:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:36:24 Completed job 8161accbd0ebbe904fa04a5d5c6d92dc in 1.099057ms
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 647.185µs
[asynchttp] INFO 2017/04/24 11:36:24 Started job 1ee2370cd54f9fcd1dbc3f00650d6c7e
[heketi] INFO 2017/04/24 11:36:24 Creating volume 4e076ec13cc5052bd210bae74d5d2311
[heketi] ERROR 2017/04/24 11:36:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:36:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:36:24 Completed job 1ee2370cd54f9fcd1dbc3f00650d6c7e in 936.396µs
[negroni] Started GET /queue/8161accbd0ebbe904fa04a5d5c6d92dc
[negroni] Completed 500 Internal Server Error in 102.638µs
[negroni] Started GET /queue/1ee2370cd54f9fcd1dbc3f00650d6c7e
[negroni] Completed 500 Internal Server Error in 322.754µs
[heketi] ERROR 2017/04/24 11:36:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 169.805µs
[asynchttp] INFO 2017/04/24 11:36:39 Started job 93d88b7e03555b2999b152efcb01f667
[heketi] INFO 2017/04/24 11:36:39 Creating volume a771bdc21e7b66dd578c4383c0fa7780
[heketi] INFO 2017/04/24 11:36:39 brick_num: 0
[heketi] ERROR 2017/04/24 11:36:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[asynchttp] INFO 2017/04/24 11:36:39 Completed job 93d88b7e03555b2999b152efcb01f667 in 781.398µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 159.636µs
[asynchttp] INFO 2017/04/24 11:36:39 Started job 4854e7d420f42e5cb38550c92b61b586
[heketi] INFO 2017/04/24 11:36:39 Creating volume ddd53f2269b530be9c6105d0c8f35c64
[heketi] INFO 2017/04/24 11:36:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:36:39 Completed job 4854e7d420f42e5cb38550c92b61b586 in 625.261µs
[negroni] Started GET /queue/93d88b7e03555b2999b152efcb01f667
[negroni] Completed 500 Internal Server Error in 77.727µs
[negroni] Started GET /queue/4854e7d420f42e5cb38550c92b61b586
[negroni] Completed 500 Internal Server Error in 71.383µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 529.85µs
[heketi] ERROR 2017/04/24 11:36:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[asynchttp] INFO 2017/04/24 11:36:54 Started job 3cde3b0cc9a8a4f2d241345176a8ea28
[heketi] INFO 2017/04/24 11:36:54 Creating volume 5983d8c2e019b20946e7212ac29d4224
[heketi] INFO 2017/04/24 11:36:54 brick_num: 0
[asynchttp] INFO 2017/04/24 11:36:54 Completed job 3cde3b0cc9a8a4f2d241345176a8ea28 in 765.055µs
[negroni] Started GET /queue/3cde3b0cc9a8a4f2d241345176a8ea28
[negroni] Completed 500 Internal Server Error in 87.44µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 127.96µs
[asynchttp] INFO 2017/04/24 11:36:54 Started job 3a6080a63ec05714473a25466d14e48b
[heketi] INFO 2017/04/24 11:36:54 Creating volume b9b5ead78eaa876d23ee2d9676563770
[heketi] INFO 2017/04/24 11:36:54 brick_num: 0
[asynchttp] INFO 2017/04/24 11:36:54 Completed job 3a6080a63ec05714473a25466d14e48b in 632.469µs
[heketi] ERROR 2017/04/24 11:36:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:36:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started GET /queue/3a6080a63ec05714473a25466d14e48b
[negroni] Completed 500 Internal Server Error in 71.521µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 275.707µs
[asynchttp] INFO 2017/04/24 11:37:09 Started job f1d79f1503fb8c186469cb3ccb1aecb4
[heketi] INFO 2017/04/24 11:37:09 Creating volume<PHONE_NUMBER>09420268fc1d7d698a39ee
[heketi] ERROR 2017/04/24 11:37:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:09 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:37:09 brick_num: 0
[asynchttp] INFO 2017/04/24 11:37:09 Completed job f1d79f1503fb8c186469cb3ccb1aecb4 in 1.100964ms
[heketi] ERROR 2017/04/24 11:37:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:09 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:09 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 125.011µs
[asynchttp] INFO 2017/04/24 11:37:09 Started job 9bbeac8e22895b9aac49127f9864e51a
[heketi] INFO 2017/04/24 11:37:09 Creating volume 872f9d8c85328568a9683d859a7bd6b6
[heketi] INFO 2017/04/24 11:37:09 brick_num: 0
[asynchttp] INFO 2017/04/24 11:37:09 Completed job 9bbeac8e22895b9aac49127f9864e51a in 1.03045ms
[negroni] Started GET /queue/f1d79f1503fb8c186469cb3ccb1aecb4
[negroni] Completed 500 Internal Server Error in 115.502µs
[negroni] Started GET /queue/9bbeac8e22895b9aac49127f9864e51a
[negroni] Completed 500 Internal Server Error in 1.92336ms
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 251.474µs
[asynchttp] INFO 2017/04/24 11:37:24 Started job a88de7ab81a2807eb1be8ec25c9d598d
[heketi] INFO 2017/04/24 11:37:24 Creating volume cfe19ba109cf871b2e3814c144a80e7b
[heketi] ERROR 2017/04/24 11:37:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:37:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:37:24 Completed job a88de7ab81a2807eb1be8ec25c9d598d in 896.621µs
[negroni] Started GET /queue/a88de7ab81a2807eb1be8ec25c9d598d
[negroni] Completed 500 Internal Server Error in 82.529µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 130.861µs
[asynchttp] INFO 2017/04/24 11:37:24 Started job 1160009e6699c103ae2f74f6953b1f59
[heketi] INFO 2017/04/24 11:37:24 Creating volume 697cd65b8f94b0ec1bf0153920d849af
[heketi] ERROR 2017/04/24 11:37:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:24 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:24 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:37:24 brick_num: 0
[asynchttp] INFO 2017/04/24 11:37:24 Completed job 1160009e6699c103ae2f74f6953b1f59 in 750.409µs
[negroni] Started GET /queue/1160009e6699c103ae2f74f6953b1f59
[negroni] Completed 500 Internal Server Error in 69.751µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 192.712µs
[asynchttp] INFO 2017/04/24 11:37:39 Started job c641cac7b2f257b668ed26836aa09efe
[heketi] INFO 2017/04/24 11:37:39 Creating volume b40185487ab5b1719816dadfd41d6dd3
[heketi] ERROR 2017/04/24 11:37:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:39 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:39 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] INFO 2017/04/24 11:37:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:37:39 Completed job c641cac7b2f257b668ed26836aa09efe in 1.138811ms
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 224.507µs
[asynchttp] INFO 2017/04/24 11:37:39 Started job e7e6472b5376453372da25d2d8c533b6
[heketi] INFO 2017/04/24 11:37:39 Creating volume 36f33d0bcd0ba8335db19780534230ef
[heketi] INFO 2017/04/24 11:37:39 brick_num: 0
[asynchttp] INFO 2017/04/24 11:37:39 Completed job e7e6472b5376453372da25d2d8c533b6 in 662.948µs
[negroni] Started GET /queue/c641cac7b2f257b668ed26836aa09efe
[negroni] Completed 500 Internal Server Error in 117.395µs
[negroni] Started GET /queue/e7e6472b5376453372da25d2d8c533b6
[negroni] Completed 500 Internal Server Error in 51.534µs
[negroni] Started POST /volumes
[negroni] Completed 202 Accepted in 423.765µs
[asynchttp] INFO 2017/04/24 11:37:54 Started job ae9450ecfe2387fa8d4e0205b3ce648d
[heketi] INFO 2017/04/24 11:37:54 Creating volume 9e7c9b03acfe05d31e1ab3f0b687da63
[heketi] ERROR 2017/04/24 11:37:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:54 /src/github.com/heketi/heketi/apps/glusterfs/app_volume.go:148: Failed to create volume: Error calling v.allocBricksInCluster: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:61: database is in read-only mode
[heketi] ERROR 2017/04/24 11:37:54 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry.go:308: Error calling v.allocBricksInCluster: database is in read-only mode

i did restart couple of times

any pointers where i can look?

:question:

@debianmaster This comment might help you: https://github.com/heketi/heketi/issues/677#issuecomment-280082798
Restarting the heketi pod didn't help in our case but scaling down the heketi deployment, waiting for a few minutes, then scaling it up again fixed the underlying issue with BoltdDB file locks https://github.com/heketi/heketi/issues/731#issuecomment-290442598
kubectl scale --replicas=0 deploy/heketi

... wait a few minutes for the write file locks to be released, then
kubectl scale --replicas=1 deploy/heketi

@saidimu   thanks for your help, i will give a try.  closing for now.

https://github.com/heketi/heketi/issues/1215 looks related


Blacklist/whitelist light blocks from rising temperature (very useful)

Describe the feature
Add an option to blacklist/whitelist some blocks like LIGHT (very needed), GLOWSTONE, etc. (configurable) from rising player’s temperature
Right now players are sweating while standing on invisible light blocks on spawn and they are getting confused all the time...
It would be really useful to manage what blocks / other light sources (torches, etc.) have impact on the temperature

@GC-spigot can you possibly add this feature - as it is nonsense to make all light blocks rising a temperature - especially the LIGHT block...


Support Promises/A+ in nodeJsActions

This change adds support for returning promises to node.js actions.
It can be used like this.
function main() {
   return new Promise(function (resolve, reject) {
       setTimeout(function() {
           resolve({done: true});
       }, 100);
   })
}

You can also reject promises, causing them to be wrapped in an error.
function main() {
   return new Promise(function (resolve, reject) {
       setTimeout(function() {
           reject({msg: "oops"});
       }, 100);
   })
}

Returns this { error: { msg: "oops" } }
This fix uses the Bluebird promise library for now until a newer node versions is implemented. At which point we can remove the dependency and use ES6 promises. They both have the same resolve api so this will be a server change only and transparent to any users.
Note this commit makes use of the fact that calling Promise.resolve on a non-promise type (value/undefined) returns that value.
(See spec)
http://www.ecma-international.org/ecma-262/6.0/#sec-promise-objects
This fix resolves #56

Hello, thank you for the pull request, including the tests. We have internally discussed the question of supporting promises, and in general agree that this is the direction we want to follow. Rather than supporting promises in legacy environments, however, we decided that we will first move forward with supporting more recent versions of Node.js. We will most likely use (at least part of) the code in this pull request then, which is why I'm leaving it open. Thanks again for the contribution!

Will make it to master through #781. Thanks again!


Is it compatible with Xamarin.Mac (Cocoa App created with Visual Studio for Mac) ?

I just created a Cocoa App with Visual Studio for Mac and I don't have a lot of experience with that.
I'm on Mac OS Big Sur with .NET Core installed.
When I want to install nuget package Microsoft.SqlServer.SqlManagementObjects I have an error message with your package :
Could not install package 'Microsoft.Data.SqlClient.SNI.runtime 2.0.0'. You are trying to install this package into a project that targets 'Xamarin.Mac,Version=v2.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
I'm sad because I really appreciate your data provider and it works very well in .NET Core.
What's going on with Microsoft.Data.SqlClient.SNI for Cocoa App ?
I installed 4 others nuget package without problem...
Is it compatible or not ?
Did I missed something ?
[Edited]
Yes I missed something... Target framework was in Xamarin.Mac Modern !
I solved this problem by using Xamarin.mac Full .Net Framework 4.8 + Retarget nuget package.
New Challenge succeeded for this new year.
Next challenge : Sleep more !!!

Seems like issue got solved, closing.

Seems like issue got solved, closing.


conversion scripts should accept long or short file paths

Conversion scripts like sio_magic should be able to take long or short file names.  I.e.:
sio_magic.py -f infile.txt -WD path/to/

or
sio_magic.py -f path/to/infile.txt

or, of course, if you're in the path/to directory:
sio_magic.py -f infile.txt

To support this, I've added a pmag function resolve_file_name that takes the filename and the working directory (if available).  It prioritizes the long file name, then if that doesn't work tries to create a long file name with working directory + the filename, and if that fails create a long file name with "." + the filename.
Once implemented, this should be more flexible and less confusing.

All conversion scripts now work this way.  This same thing could be implemented in some other scripts as well, but I'll do that as needed later.


fix(travis): Release step

:tada: This PR is included in version 0.3.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Some links don't get parsed correctly

For example:

Example notebook for working with Sentinel-2 COGs served from AWS. Demonstrates raster loading and visualization on a map. Try it on [Binder](https://mybinder.org/v2/gh/opendatacube/odc-stac/develop?urlpath=lab/workspaces/demo).

see the "Access Sentinel-2 Data from AWS with odc-stac" tutorial.

Fixed


Doesn't compile

Tried to install using cargo install --locked gitmoji
OS: 6.3.7-arch1-1
rustc -V: rustc 1.72.0-nightly (d59363ad0 2023-06-01)

The compilation fails with the following message:
    Updating crates.io index
  Installing gitmoji v1.0.0
    Updating crates.io index
warning: package `bumpalo v3.1.2` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `futures-util v0.3.1` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `miow v0.2.1` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `net2 v0.2.33` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `pin-project v0.4.8` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `pin-project-lite v0.1.4` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
warning: package `structopt v0.3.9` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked
    Updating crates.io index
   Compiling libc v0.2.66
   Compiling cfg-if v0.1.10
   Compiling proc-macro2 v1.0.8
   Compiling unicode-xid v0.2.0
   Compiling syn v1.0.14
   Compiling lazy_static v1.4.0
   Compiling autocfg v1.0.0
   Compiling log v0.4.8
   Compiling pkg-config v0.3.17
   Compiling bitflags v1.2.1
   Compiling cc v1.0.50
   Compiling memchr v2.3.0
   Compiling rustversion v1.0.2
   Compiling bytes v0.5.4
   Compiling slab v0.4.2
   Compiling fnv v1.0.6
   Compiling version_check v0.9.1
   Compiling getrandom v0.1.14
   Compiling itoa v0.4.5
   Compiling pin-project-lite v0.1.4
   Compiling futures-core v0.3.1
   Compiling serde v1.0.104
   Compiling openssl v0.10.27
   Compiling unicode-width v0.1.7
   Compiling ppv-lite86 v0.2.6
   Compiling foreign-types-shared v0.1.1
   Compiling pin-utils v0.1.0-alpha.4
   Compiling foreign-types v0.3.2
   Compiling futures-sink v0.3.1
   Compiling matches v0.1.8
   Compiling native-tls v0.2.3
   Compiling indexmap v1.3.1
   Compiling futures-io v0.3.1
   Compiling unicase v2.6.0
   Compiling httparse v1.3.4
   Compiling futures-task v0.3.1
   Compiling http v0.2.0
   Compiling smallvec v1.2.0
   Compiling futures-util v0.3.1
   Compiling unicode-bidi v0.3.4
   Compiling ryu v1.0.2
   Compiling unicode-normalization v0.1.12
   Compiling c2-chacha v0.2.3
   Compiling openssl-probe v0.1.2
   Compiling unicode-segmentation v1.6.0
   Compiling quote v1.0.2
   Compiling iovec v0.1.4
   Compiling net2 v0.2.33
   Compiling num_cpus v1.12.0
   Compiling rand_core v0.5.1
   Compiling openssl-sys v0.9.54
   Compiling term_size v0.3.1
   Compiling mio v0.6.21
   Compiling atty v0.2.14
   Compiling dirs-sys v0.3.4
   Compiling regex-syntax v0.6.14
   Compiling try-lock v0.2.2
   Compiling rand_chacha v0.2.1
   Compiling unicode-xid v0.0.4
   Compiling synom v0.11.3
   Compiling idna v0.2.0
   Compiling rand v0.7.3
   Compiling want v0.3.0
   Compiling dirs v2.0.2
   Compiling textwrap v0.11.0
The following warnings were emitted during compilation:

warning: build/expando.c:4:24: error: pasting "RUST_VERSION_OPENSSL_" and "(" does not give a valid preprocessing token
warning:     4 | #define VERSION2(n, v) RUST_VERSION_##n##_##v
warning:       |                        ^~~~~~~~~~~~~
warning: build/expando.c:5:23: note: in expansion of macro ‘VERSION2’
warning:     5 | #define VERSION(n, v) VERSION2(n, v)
warning:       |                       ^~~~~~~~
warning: build/expando.c:10:1: note: in expansion of macro ‘VERSION’
warning:    10 | VERSION(OPENSSL, OPENSSL_VERSION_NUMBER)
warning:       | ^~~~~~~

error: failed to run custom build command for `openssl-sys v0.9.54`

Caused by:
  process didn't exit successfully: `/tmp/cargo-install0qx1v5/release/build/openssl-sys-f75fbb9c71127340/build-script-main` (exit status: 101)
  --- stdout
  cargo:rustc-cfg=const_fn
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_LIB_DIR
  X86_64_UNKNOWN_LINUX_GNU_OPENSSL_LIB_DIR unset
  cargo:rerun-if-env-changed=OPENSSL_LIB_DIR
  OPENSSL_LIB_DIR unset
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_INCLUDE_DIR
  X86_64_UNKNOWN_LINUX_GNU_OPENSSL_INCLUDE_DIR unset
  cargo:rerun-if-env-changed=OPENSSL_INCLUDE_DIR
  OPENSSL_INCLUDE_DIR unset
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_DIR
  X86_64_UNKNOWN_LINUX_GNU_OPENSSL_DIR unset
  cargo:rerun-if-env-changed=OPENSSL_DIR
  OPENSSL_DIR unset
  cargo:rustc-link-lib=ssl
  cargo:rustc-link-lib=crypto
  OPT_LEVEL = Some("3")
  TARGET = Some("x86_64-unknown-linux-gnu")
  HOST = Some("x86_64-unknown-linux-gnu")
  CC_x86_64-unknown-linux-gnu = None
  CC_x86_64_unknown_linux_gnu = None
  HOST_CC = None
  CC = None
  CFLAGS_x86_64-unknown-linux-gnu = None
  CFLAGS_x86_64_unknown_linux_gnu = None
  HOST_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
  running: "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "/usr/include" "-Wall" "-Wextra" "-E" "build/expando.c"
  cargo:warning=build/expando.c:4:24: error: pasting "RUST_VERSION_OPENSSL_" and "(" does not give a valid preprocessing token
  cargo:warning=    4 | #define VERSION2(n, v) RUST_VERSION_##n##_##v
  cargo:warning=      |                        ^~~~~~~~~~~~~
  cargo:warning=build/expando.c:5:23: note: in expansion of macro ‘VERSION2’
  cargo:warning=    5 | #define VERSION(n, v) VERSION2(n, v)
  cargo:warning=      |                       ^~~~~~~~
  cargo:warning=build/expando.c:10:1: note: in expansion of macro ‘VERSION’
  cargo:warning=   10 | VERSION(OPENSSL, OPENSSL_VERSION_NUMBER)
  cargo:warning=      | ^~~~~~~
  exit status: 1

  --- stderr
  thread 'main' panicked at '
  Header expansion error:
  Error { kind: ToolExecError, message: "Command \"cc\" \"-O3\" \"-ffunction-sections\" \"-fdata-sections\" \"-fPIC\" \"-m64\" \"-I\" \"/usr/include\" \"-Wall\" \"-Wextra\" \"-E\" \"build/expando.c\" with args \"cc\" did not execute successfully (status code exit status: 1)." }

  Failed to find OpenSSL development headers.

  You can try fixing this setting the `OPENSSL_DIR` environment variable
  pointing to your OpenSSL installation or installing OpenSSL headers package
  specific to your distribution:

      # On Ubuntu
      sudo apt-get install libssl-dev
      # On Arch Linux
      sudo pacman -S openssl
      # On Fedora
      sudo dnf install openssl-devel

  See rust-openssl README for more information:

      https://github.com/sfackler/rust-openssl#linux
  ', /home/maxv/.cargo/registry/src/index.crates.io-6f17d22bba15001f/openssl-sys-0.9.54/build/main.rs:126:13
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile `gitmoji v1.0.0`, intermediate artifacts can be found at `/tmp/cargo-install0qx1v5`

P.S.: Why tokio and openssl are even needed for this project? :laughing:

You tried to install a different crate. This is gimoji, not gitmoji. 😄 The latest version doesn't even do any http anymore as the emoji db is now part of our repo.

Thanks for pointing out!


[Exposure Request] Table 38 "Purchase Header" - DeletePurchCommentLines

Please make function DeletePurchCommentLines in table 38 "Purchase Header" externally available.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 42916.


Dataset

Can you make public the dataset you mentioned in your paper？

Hi @gjgjgjfff,
The dataset will be released in conjunction with the upcoming GigaVision challenge (the 3DRecon track).


Even though the wildcard matches, tests aren't discovered

Testing #18349
The following code:
import unittest

class TestSum2(unittest.TestCase):

    def test_sum2(self):
        self.assertEqual(sum([1, 2, 3]), 6, "Should be 6")

    def test_sum2_tuple(self):
        self.assertEqual(sum((1, 2, 2)), 6, "Should be 6")

if __name__ == '__main__':
    unittest.main()

in a file called some.test.py with the following configuration:
{
    "python.testing.unittestArgs": [
        "-v",
        "-s",
        ".",
        "-p",
        "*test.py"
    ],
    "python.testing.pytestEnabled": false,
    "python.testing.unittestEnabled": true,
    "python.linting.enabled": true,
    "python.linting.pylintEnabled": true
}

doesn't discover the tests. If I rename the file to sometest.py (note the removal of the .) then the tests are discovered.
Ubuntu 20.04
cc @TylerLeonhardt

This is the expected behavior, it is not a conda run execution problem.


Fix Travis CI integration

Describe the bug
Due to renaming patternpedia to patternatlas, the CI integration must be tested and corrected, if it is not working anymore
Additional context
Check the Travis Config files for backend/frontend

solved by recent commit: https://github.com/PatternAtlas/pattern-atlas-ui/commit/b95875024751ffd63a40478c88eca8a9185394ad


[Question] Package.json search process

Hi, not really an issue, more like a how-does-it-work question.
I have a monorepo with the following setup:
root --> package.json with prettier entry
root/package-a ---> package.json without prettier entry

I noticed when editing a file in the root/package-a path, the lsp does not format the code using prettier. I guess this happens because the plugin stops searching after the first package.json found, which does not contain the prettier entry, is this correct?
Great job btw, works flawlessly.

I have the same question. Is it possible to override the config to look for the package.json at the git root?

@sockthedev inspecting the code I think it starts checking from the folder vim was opened in.

To change the condition for starting prettierd server, you can do this:
prettier.setup({
  bin = "prettierd",
  ["null-ls"] = {
    condition = function()
      -- will always start
      return true
      -- will start if you open vim in a folder with `package.json` file
      -- i.e. for javascript/typescript projects
      require("lspconfig.util").find_package_json_ancestor(vim.fn.getcwd())
    end,
    -- ...
  },
  -- ...
})

The important thing is that the function pass to condition will only run once at startup.
Note that, even if prettierd server is not running, you can still execute :Prettier command to format the file manually.
I hope that helps.


Allow grouping contexts together

Hello, I think the ability to create named groups of contexts might be a useful addition. With that, you could create a context group called "pvp" and list contexts specifying the worlds and servers with pvp enabled. When a new world gets added, you could just add it as another entry to the existing context group, and all of the existing permissions would work perfectly.
Thanks.

Huh, interesting idea.
I'm guessing you're using Sponge?

I've seen that terminology used with Sponge, but I'm actually using Bukkit. It might also make it easier to migrate the mirrors from GroupManager.

World inheritance with LP is possible via a config option: https://github.com/lucko/LuckPerms/blob/master/bukkit/src/main/resources/config.yml#L185
Grouping contexts is probably going to be tricky. The best I could do is to allow you to define pre-made context sets in the config, but these would just be copied when commands are run.
e.g.
contexts:
  pvp:
    server: "something"
    world: "something-else"
  thing:
    server: "idk"

Then, when you run the commands, it would just query this and select the appropriate set of contexts. However, it would be a copy, and wouldn't refer back to this, so changing the config later wouldn't update stuff you'd set already.
I think the uses for this are really limited, especially on Bukkit. There are only two contexts, so you're only really saving yourself the time to type a couple of words.
Also remember that contexts are satisfied via AND, not OR, so having...
contexts:
  pvp:
    world: "something"
    world: "something-else"

... would make no sense, because you can't be in two worlds at the same time.
Idk, does that make sense?

World inheritance is probably good enough in most cases. The only real difference is that a world could belong to multiple context groups. That would be a neat feature, but I understand if it's more complex than it's worth.
I am a little confused by the last part. The way you explained the expansion when the command is run made me think we were on the same page, but the last part seems a little different. It would be more like
"contexts": {
      "pvp": [
         {"server":"server1", "world":"server1-world1"},
         {"server": "server2", "world": "server2-world2"}
      ]
   }

Sorry for switching to JSON, but the YAML syntax for a list of objects is a little funny.

I was looking into how to implement this in the hopes of creating a PR, but I can see why you said adding it would be complicated. A lot of the methods on Node, such as get(Full)Contexts(), getWorld(), and getServer(), would no longer make sense. However, I got an idea from how PEX handles its server-tags context. I've created a separate plugin that registers a ContextCalculator that adds context values under the "tag" key. For example, it turns the contextset
{"server": "server1", "world": "world1"}

into
{"server": "server1", "world": "world1", "tag":"pvp"}

It's not complete yet, but that's my problem. However, I'm not sure how to set a permission with a custom context. The set command only seems to take a server and a world. I'm going to go ahead and close the issue, though.

Yep, your example with the ContextCalculator is definitely the best way to achieve what you want. :)
Your other suggestion wouldn't be possible, as yeah, each "Node" only has one attached context set. If you wanted to attach multiple, then you'd just have to add multiple nodes.
And yeah, there currently isn't a way to attach contexts to permissions/parents using commands. It's been a low priority to-do for a long time, and I intend to get it added pretty soon. Some of the methods for it are already written. https://github.com/lucko/LuckPerms/blob/master/common/src/main/java/me/lucko/luckperms/common/commands/utils/ArgumentUtils.java#L139
It's just a case of modifying the command messages to support it, and then I'll be adding it. I also plan to combine that change with a chance to remove the exceptional behaviour from the setPermission methods. (a user/group already having a permission isn't really exceptional behaviour, so I want to fix that.)


has no method 'forEach'

Tried to use axis within Grunt, but got error, while compiling stylus files:
Warning: Object function (style){
    style.use(nib());         // include nib
    style.include(__dirname); // include axis

    if (implicit) {
      style.import('nib');
      style.import('axis');
    }
  } has no method 'forEach' Use --force to continue.

Aborted due to warnings.

My Grunfile:
module.exports = function(grunt)
{
	var axis = require('axis');
	...
	stylus: {
			main: {
				options: {
					compress: false,
					use: axis()
				},
				files: [{
					src: 'app/main.styl',
					dest: 'dist/css_temp/main.css'
				}]
			},
		},
	}
	...
}

Any suggestion?

You need to put axis in an array under use, as such:
options: {
                    compress: false,
                    use: [axis()]
                },

This is not an axis issue, it's a grunt usage issue, but that will almost certainly solve it.  Hope you enjoy axis!

Didn't help. :(
Warning: Cannot call method 'use' of undefined Use --force to continue.

Not sure what to tell you, I don't use grunt. This is not an axis issue though. I might try looking up some example configs or asking in a grunt community!

This one worked correct:
options: {
  compress: false,
  use: [axis]
}

Awesome, glad you got it working!


No input on mobile scrolling

When I use the keyboard for my mobile site, the keys are pressed if a user tries to scroll down the page with their finger on a key.
Ideally there would be an option to stop this behaviour. Not sure if this is possible but my other buttons use onClick and don't have this problem.

Hello @Tomo-Pavicic-Personal,
You can try this option: useMouseEvents.
Regards,
Francisco Hodge

Worked perfectly,
Thank you @hodgef


WIP: Add ViewHelper

I'm excited about this! 😄
This may be an opportunity for getting rid of the Axis helper thingy, as I believe we won't need it with these changes?

I'm excited about this! 😄

So am I, and as I mentioned it was not looking good before as it was messing with the scene by rendering it skewed. After good amount of time spent it's atleast looking better than that but still not in the best shape to be ready, there are a couple of issues which I'm wondering, why?
https://github.com/user-attachments/assets/502137ce-155a-4030-8965-7d7f8b57679f

There's this strange offset to the viewHelper you can notice while i hover over it & inspite of me giving it top-right position, the div container of viewHelper is in top right but viewHelper in the scene is not.

ViewHelper is not visible when left panel is on and even if it's off it's still not fully visible maybe due to still some space in the left?

This may be an opportunity for getting rid of the Axis helper thingy, as I believe we won't need it with these changes?

Yes I agree, this can be a good option for axis helper too. :)

Superseded by #440


Update sample psp to reflect sidecar capability changes in 1.4

Since istio 1.4 the sidecar requires the NET_RAW capability to work.
This should be reflected in the sample psp.

Hi @exi. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@exi: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


add release workflow to publish binaries

This PR adds a new workflow.
When you push a git tag with the format
v#.#.# i.e. v0.2.4 it will trigger this workflow.
When the workflow is run it will build on linux and mac and publish the following binaries.
fastplong_darwin_arm64
fastplong_darwin_i386
fastplong_linux_x86_64

Tested on my own repo and the repo looks like this:
https://github.com/chinwobble/CppCMakeVcpkgTemplate/releases/tag/v0.1.0
Users can download the built binaries using CLI like this
# specific version
curl https://github.com/OpenGene/fastplong/releases/download/v0.1.0/fastplong_linux_x86_64 --output fastplong
# latest version
curl https://github.com/OpenGene/fastplong/releases/download/latest/fastplong_linux_x86_64 --output fastplong
chmod +x fastplong
./fastplong

sudo install fastplong /usr/local/bin/fastplong

Can you try push a new tag v0.2.3 to test this pipeline?


#1712 Allow to reuse nginx ingress

Closes https://github.com/keptn/keptn/issues/1712
This PR implements the reuse of an existing NGINX ingress installation.
Therefore, the flag istio-install-optionof the install command of the CLI was renamed into ingress-install-option, which is now used for NGINX as well as Istio. The supported values for ingress-install-option are Reuse, StopIfInstalled, and Overwrite.

Codecov Report

Merging #1722 into master will decrease coverage by 0.01%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##           master    #1722      +/-   ##
==========================================
- Coverage   29.20%   29.18%   -0.02%
==========================================
  Files          94       94
  Lines        7195     7195
==========================================
- Hits         2101     2100       -1
- Misses       4832     4833       +1
  Partials      262      262

Impacted Files
Coverage Δ

cli/cmd/install.go
24.44% <85.71%> (ø)

cli/cmd/ingress_install_option.go
100.00% <100.00%> (ø)

distributor/cmd/main.go
57.77% <0.00%> (-1.12%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f7dfca2...429c7d5. Read the comment docs.


fix filestats period passing

Its currently not possible to pass a period to file stats
e.g. http://mirrors.kodi.tv/releases/win32/kodi-15.1-Isengard.exe?stats=2015_08_18 results in "Invalid period"

hm, my bad. the format is supposed to be YYYY-MM-DD, which is working fine


add API for crates.io to trigger rebuilds

relates to #2442.

adds config variable DOCSRS_TRIGGER_REBUILD_TOKEN /
Config.trigger_rebuild_token

adds build_trigger_rebuild_handler and route
"/crate/:name/:version/rebuild"

Note: does not yet contain any kind of rate limiting!

I think I've handled all of your suggestions, but I forgot about Clippy. I'll need to get back to that another evening.

Oh build failures:

error: set DATABASE_URL to use query macros online, or run cargo sqlx prepare to update the query cache

Not sure right now what to do about this (need to stop for tonight).

Oh build failures:

error: set DATABASE_URL to use query macros online, or run cargo sqlx prepare to update the query cache

Not sure right now what to do about this (need to stop for tonight).

I've put the necessary command into our Justfile, so calling just sqlx-prepare is fine

Thank you for all the work! This will be awesome for crate authors

I've so far avoided to force-push and instead pushed 3 commits (those with subject lines starting with "sq", standing for squash) with changes that I will squash into the earlier commits where they belong; the idea is that this makes it easier for you to see what I changed; this assumes that diffing is easier as a last step after I do the squashing together with the right commits and force-pushing at the end. Let me know once you're happy and I'll do that. And if that was useful or rather a  complication.

I've realized that you can still see the commit from before me squashing the commits anyway and have now force-pushed db8b3636...b7deb0d7 (i.e. if you'd like to see the incremental changes I did easily, look at db8b3636, for the state I wish to be merged b7deb0d7).

I've pushed 3 commits with (a) the 'optimized' SQL query, FWIW, (b)+(c) add and use the constant_time_eq crate for token comparisons. Without it, it would likely be possible for attackers to find the token via response times.

@pflanze do you want to squash some commits before I merge?

@pflanze do you want to squash some commits before I merge?

@syphar, yes, some more squashing was warranted. I think now it's at the proper resolution.

This looks really awesome, thank you for the continued work on this.

Thank you, too, for your help during https://rustfest.ch/ and your feedback afterwards! It was the perfect introduction.
Now I just need to get a bit more time.


feat(security): added request info

This allows us to handle situational/complex security situations. For example delegating auth logic to OPA.

I see that custom security option was added.
Closing this.


Open daterangepicker on input focus

Is there an easy way to open the DateRangepicker when a user clicks the input it is attached to? I attempted to tie into the focus event to call the "_open()" function on the date toggler, but it did not work.

https://material.angular.io/components/datepicker/overview#manually-opening-and-closing-the-calendar


OSS Sync | Thu Apr 23 15:50:05 UTC 2020

#autorebase

FYI @or-shachar @liucijus

How could have this be prevented?

the public version does not support @main_repository_name
Here you can see what is currently synced: https://github.com/wix-private/core-server-build-tools/blob/master/scripts/oss-sync/copy.bara.sky
and if you want to update it: https://github.com/wix-private/velocity-infra/tree/master/rnd-tools/github-tools/osynchronotron#changing-existing-configuration

My question is more general - syncing workspace rules will always be a problem if we don't do a proper automation. I don't even know where to learn if such copy pastes exist.

osynchronotron is the proper automation.
what to sync, what to replace, what to create locally - these are the key questions


InfluxDB Cloud: single stat stopped working for non-numeric data

Steps to reproduce:

Have a meausurement with string tag
Create dashboard cell with Single Stat visualization
Use query to select that string tag

Expected behavior:
Single string value displayed.
Actual behavior:
NaN displayed.
Additional info:
It worked fine yesterday (June 13) but today Single Stat for string is suddenly broken.
I use this query:
from(bucket: "XXX")
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> filter(fn: (r) => r["_measurement"] == "yyyy" and r["_field"] == "zzz")
  |> group(columns: [])
  |> map(fn: (r) => ({ version: r.version }))
  |> sort(columns: ["version"])
  |> last(column: "version")

If we use Table visualization, we'll see:

All looks fine.
Then switch to Single Stat:

@melanchall thanks for the issue. I think this should be fixed now if you'd like to confirm.

Yes. now it's fixed.


Switched from krkn_lib_kubernetes to krkn_lib v1.0.0

updated requirements.txt
changed all the references from krkn_lib_kubernets to krkn_lib and its subpackages

/funtest


[FR] - if requested item is already on the server, let requester know

Rather than having multiple people requesting the same thing multiple times, let people know if it has been requested already or that it already exists on the media server.

Hey,
This already happens, if I request something then you request the same thing before it is added to the server, your request button turns into a notify button, and you will get notified when it is available.
If it is already on the server, your request button changes to "Available" and is disabled.

I did not know this. Great to know!

From: thomst08 @.>
Sent: April 15, 2024 12:17 AM
To: thomst08/requestrr @.>
Cc: bullmoose20 @.>; Author @.>
Subject: Re: [thomst08/requestrr] [FR] - if requested item is already on the server, let requester know (Issue #29)
Hey,
This already happens, if I request something then you request the same thing before it is added to the server, your request button turns into a notify button, and you will get notified when it is available.
If it is already on the server, your request button changes to "Available" and is disabled.
—
Reply to this email directly, view it on GitHubhttps://github.com/thomst08/requestrr/issues/29#issuecomment-2054943393, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC7XXKLYO3RNLUPAPIGBIDTY5NIGDAVCNFSM6AAAAABGGRW65GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJUHE2DGMZZGM.
You are receiving this because you authored the thread.Message ID: @.***>