conflicting revisions getting created instead of getting "conflict" error response within a node

Description
while trying to update a document in parallel within a node, conflicting revisions are created.
Running an application with a two node couchdb cluster (Node A and Node B). However, All the API traffic from the application has been directed only to the node A.
The application receives a multiple parallel requests which reads and updates a value from a single document. Have handled the race condition based on the conflict error response,
{"error"=>"conflict", "reason"=>"Document update conflict."}. In most cases this works fine but at some point instead of getting conflict error response, have created conflicting revisions 2-a and 2-b within node A.
Thereby race condition handling failed.
While trying to reproduce the same with a couchdb in stand alone mode conflicting revisions are not created.
Want to understand if conflicting revisions will be created within the same node. Thought it happens only when syncing with a different node.
Environment

CouchDB Version used: 2.3.0
Operating System and version: Ubuntu 16.04

This is an effect of quorum writes in a cluster. What happens during a clustered write is that the updates are sent to all nodes in the cluster and the responses are then collected and returned.
In your case what is happening is that you have two concurrent writes that are then distributed to all shard copies. Say you want to write both Rev1 and Rev2 concurrently. Depending on timing, those may arrive at nodes in different orders. I.e., node1 might see Rev1 first, while node2 might see Rev2 first. In that case both updates will be accepted and the result would then be a conflict written on both nodes.


I have example below:
// main.go

package main

import (
	"fmt"
)

var (
	v0 = constInitCheck()
	v1 = variableInit("v1")
	v2 = variableInit("v2")
)

const (
	c1 = "c1"
	c2 = "c2"
)

func constInitCheck() string {
	if c1 != "" {
		fmt.Println("main: const c1 has been initialized")
	}
	if c1 != "" {
		fmt.Println("main: const c2 has been initialized")
	}
	return ""
}

func variableInit(name string) string {
	fmt.Printf("main: var %s has been initialized\n", name)
	return name
}

func init() {
	fmt.Println("main: first init func invoked")
}

func init() {
	fmt.Println("main: second init func invoked")
}

func main() {
	// do nothing
}

What did you see happen?
Compile and run the code in go 1.22.0，I got this output:
$go run main.go
main: var v1 has been initialized
main: var v2 has been initialized
main: const c1 has been initialized
main: const c2 has been initialized
main: first init func invoked
main: second init func invoked

What did you expect to see?
According to the latest go spec:
Within a package, package-level variable initialization proceeds stepwise, with each step selecting the variable earliest in declaration order which has no dependencies on uninitialized variables.

More precisely, a package-level variable is considered ready for initialization if it is not yet initialized and either has no [initialization expression](https://go.dev/ref/spec#Variable_declarations) or its initialization expression has no dependencies on uninitialized variables. Initialization proceeds by repeatedly initializing the next package-level variable that is earliest in declaration order and ready for initialization, until there are no variables ready for initialization.

v0、v1 and v2 all have initializaiton expression , and should be considered as "not ready for initialization"。their init order should be v0 -> v1 -> v2。but the real init order is v1 -> v2 -> v0。

If we place const declaration block before var declaration block, the init order will become v0 -> v1 -> v2：
$go run main.go // go1.22.0
main: const c1 has been initialized
main: const c2 has been initialized
main: var v1 has been initialized
main: var v2 has been initialized
main: first init func invoked
main: second init func invoked

constInitCheck() has a dependency on c1 and c2, which are uninitialized at that point.
variableInit has no dependency. this all appears consistent with the current spec.

@seankhliao thanks for instant reply. Go spec says "no dependencies on uninitialized variables" , but c1 and c2 are uninitialized constants.  there is a little bit of inconsistency.

This looks like it changed between 1.21 and 1.22.
I agree with the OP, constants are not variables.
@gri

@griesemer

Bisect points to https://go-review.googlesource.com/c/go/+/517617, switching to use types2 for init order, which makes sense. types2 always had this bug.
FYI @mdempsky

Just a curious BTW question: why is a initialized after b?
By my understanding of the spec, the order should be inverted.
package main

var x = 0
var a = foo()
var b = x

func foo() int {
	x++
	return x
}

func main() {
	println(a, b) // 1 0
}

Reopening for @griesemer to decide if anything needs to change in the spec.
@go101 I don't think this issue warrants backporting. The workaround is pretty easy.

@go101 Re: your question about this code:
package main

var x = 0
var a = foo()
var b = x

func foo() int {
	x++
	return x
}

func main() {
	println(a, b) // 1 1 for Go 1.23
}

The result should be 1 1: x is initialized first as it doesn't depend on any other variables and thus is ready for initialization and it's first in the source. Then a is initialized: it depends on f which depends on x but x is initialized, so f can proceed and the result is 1 for a. Then b is set to the value of a which is 1. This matches gccgo.
With respect to the original issue, constants are never "initialized", they have their values already at compile time. The bug was fixed with CL 575075.
(Technical aside: constants appear in the implementation code determining initialization order only because that code is also used to detect invalid cycles among constant declarations; constants don't have an impact on initialization order. The bug was that constants were treated like variables w/o dependencies and thus their source order influenced the initialization order. The fix was to prioritize a constant always before any variable which effectively removes them from the initialization order - they are "pre-initialized" if you will.)
With respect to the spec: I don't think anything needs to change. The spec explicitly talks about variables, not constants in this context.
With respect to backporting: I think we should backport this. It's easy enough and it is a bug with respect to the spec.
Closing this issue as fixed but will create a backport issue.

@gopherbot please consider this for backport to 1.22, it's a bug with respect to the spec.


sap_install_media_detect: Fix issue #859

@marcelmamula Thanks for reporting and providing diagnostics information, very helpful!


DISTRAINT: Deluxe Edition [PCSB01165]

App summary

App name: DISTRAINT: Deluxe Edition
App serial: PCSB01165
App version: 1.00

Vita3K summary

Version: v0.1.6
Build number: 3030
Commit hash: https://github.com/vita3k/vita3k/commit/d5162f6c
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: Zangetsu38
OS: Windows 11
CPU: AMD Ryzen 3900X
GPU: Nvidia RTX 2070 Super
RAM: 16 GB

Issues

text is dificult to read
some glitych on light effect
Game is tecnicaly palyable, for but text get hard to read

Screenshots

Log
vita3k.log

Vita3K summary

Version: v0.2.0
Build number: 3691
Commit hash: https://github.com/vita3k/vita3k/commit/31826697
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: Slade
OS: Microsoft Windows 10 Professional (build 19045)
CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
GPU: NVIDIA GeForce GTX 1060 6GB
RAM: 16 GB

Issues

Text does not render properly throughout (it should appear white, not black, as per the screenshots).
Colours are not rendered accurately.
No change from previous report.

Screenshots

Log
vita3k.log


feature Add meta service proto definition

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall


The comfyUI translation plugin cannot be applied in stableswarmUI |  关于 comfyUI翻译插件无法应用在stableswarmUI

https://github.com/AIGODLIKE/AIGODLIKE-ComfyUI-Translation
我在comfyUI中安装了这个插件，单独运行时是可以翻译的
I installed this plugin in comfyUI and it translates when run alone

如果是用stableswarmUI则无法应用该插件（软件功能可以正常运行但是无法翻译）
If you are using stableswarmUI, the plugin cannot be applied (the software functions work properly but cannot be translated)

我需要用网页插件才能翻译该软件很麻烦，有什么办法可以让comfyUI的插件应用到stableswarmUI
I need to use the web plugin to translate the software is very troublesome, is there any way to apply the comfyUI plugin to stableswarmUI

The plug-in cannot be installed through ComfyUI Manager

Same problem

I created a PR @ https://github.com/AIGODLIKE/AIGODLIKE-ComfyUI-Translation/pull/89 that fixes this

@mcmonkey4eva Merged, thanks!


[Feature request] read Environment variable to initialize tabnine pro

I am a heavy user of Cloud IDE gitpod, I wondering if you can read https://www.gitpod.io/docs/environment-variables/#using-the-account-settings (define a conventional name for key), so I don't need to paste my key all the time.
gz#3446

Hi @gengjiawen
We're working on improving Tabnine's integration with gitpod. Will follow on this post.

Hi @gengjiawen we've just released a basic support which persists Tabnine configs in gitpod env vars automatically. Would appreciate if you update the plugin and share your feedback.

any docs I can check ？

Hi @gengjiawen once you log in, the credentials saved automatically.

I am afraid latest tabnine not working on gitpods.

Can you share the logs of:

Console in dev tools
Set Tabnine Log Path in vscode settings and share its log?

The latest TabNine is basically unusable in gitpods. I don't think you have test it on gitpods before release it.

https://github.com/codota/tabnine-vscode/pull/578 should fix it. I will release it soon.

I have worry for the stability of Tabnine on gitpods. Will you consider make gitpods first-class support. This is kind of frustrating for users like me.

I understand your frustration.
Tabnine relies on the FS for persistence. You can figure why this is an issue with Gitpod. A complete support for such ephemeral environments requires a deep rewrite of the code and may take time - but this is indeed on our backlog. Keep sending us your feedback.

@gengjiawen sorry for the delay. Can you please check if this is working for you? note that it persists only on the project (repo) level

If it persists only on the project (repo) level, then it's pretty useless. Why can't it be user level ?

https://github.com/wakatime/vscode-wakatime/pull/220 use similar strategy, works great.

It's literally disaster

we're not using environment variables for a while now. you can safely remove these.

Is there an easy way to use tabnine pro on gitpods now ?


feat: [LW-6378] improve cip72 dapp registration script

This PR improves the flow of dapp registration.

It splits metadata URL greater than 64 characters into an array of strings max 64 characters each.
Removes unnecessary fields from the generated metadata
Cleanup the generated tx.draft and tx.sign after transaction has been submitted
Remove some unnecessary questions from the prompts
And a few other general improvements

Tested and works as expected! Let's merge it 🚀


Update cats-effect, cats-effect-laws to 3.2.7

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws

from 3.2.1 to 3.2.7.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, semver-patch

Superseded by #101.


Synchronisation

One of the things I racked my brain on when writing the parallel stuff was how to deal with next and done. ATM the synchronisation strategy is left to the consumer, i.e. if next is called synchronously, it will immediately call the next middleware. This has subtle but important effects, for instance:
function createParallel(name) {
	return function(next, done) {
		console.log(name + ' setup');
		setTimeout(function() {
			console.log(name + ' done');
			done();
		}, 0);
		next();// <------------------- next is called after the async stuff is fired off
	};
}

instance.pre('test', createParallel("A"), createParallel("B")).callHook('pre:test');

# output
A setup
B setup
A done
B done

However
function createParallel(name) {
	return function(next, done) {
		console.log(name + ' setup');
		next(); // <------------------- next is called before the async stuff is fired off
		setTimeout(function() {
			console.log(name + ' done');
			done();
		}, 0);
	};
}

instance.pre('test', createParallel("A"), createParallel("B")).callHook('pre:test');

# output
A setup
B setup
B done
A done

Now B finishes first. This has its pros and cons.
For a long time I wanted to next-tick the parallel next, to be sure all of the sync code would finish before the next middleware is called.
But then I realized that it makes next useless. It doesn't matter where you call it in your parallel middleware, the function will execute in full, which means we might as well leave out next (disregarding the fact we need it to recognize parallel middleware)
On the other hand: the above might lead to some unwanted side-effects. Granted, I can't come up with a case though. I mean, if you allow your function to execute in parallel with other, possibly unknown functions, it's your responsibility to make sure it really doesn't matter what the other functions are doing.
Now this is just for parallel middleware, but I had to ask myself the same question regarding the "final" callback. I.e. the one that's passed to callHook.
ATM if all your middleware is sync, the callHook call is finished sync as well. I'm not entirely sure this is ok.
@jedwatson any thoughts?
Or @JohnnyEstilles ?

Hmmmm .... http://blog.ometer.com/2011/07/24/callbacks-synchronous-and-asynchronous/

@creynders, regarding the parallel hooks, I've ran into both of the scenarios you mentioned. In my use-cases, while running them in parallel I had no expectation the tasks would end in any particular order. So, while I noticed the difference, I was mostly concerned with detecting when they were all completed.
Have you ran into any use-cases in which the completion order was important?
I'll check out that article ...

No I haven't. I think the only situation in which it really matters is when errors occur, e.g. parallel A calls next before calling its async operation, but the next middleware function errors synchronously (either by throwing if it's a sync function or by immediately calling next(err) if it's serial/parallel).

I did notice there are some situations in which the "final" callback in kareem is next-ticked. AFAICT it's when

pre: a synchronous function is last in line
pre: no middleware is registered
post: no middleware is registered

It should be noted pre and post middleware is handled differently in kareem though. Post middleware do not receive a next callback, i.e. if I'm not mistaken they're always considered sync. (even though they maybe do some async stuff)
So, it's really about not finishing the hook call synchronously.

Your assessment/comparison with kareem is spot on. I think you're middleware is much more elegant and user-friendly.  Do you test for erros in pre/post hooks in scenarios like the ones you mentioned above?

What do you mean with "test" and in which scenarios exactly? i.e. have I written tests to nail-down what should happen when for instance a synchronous function is last in line and explodes?

And, unless I misunderstood you with "Kareem does offer the ability to call the pre/post middlewares independently", but grappling-hook offers the same functionality through callHook, e.g.
grappling.callHook('pre:save');
// ~=
kareem.execPre('save');

So, it's really about not finishing the hook call synchronously.

This is absolutely vital. We need to make sure that the final callback is always async, and always runs after every other middleware (whether serial or parallel or not async) has completed.

Heheh, I had a feeling a very deep rabbit hole might lie hidden there...
Fixing this ASAP

I think i decapitated the monster

What do you mean with "test" and in which scenarios exactly?

I was referring to errors occurring during parallel calls. The question is mute now though.

grappling-hook offers the same functionality through callHook

I didn't realize! grappling-hook is ALMOST complete! (We just need to handle .thenable middleware ...

Hmmm, I'm starting to think this wasn't such a good idea...
 Obviously, in this case I can grab it in the "final" callback, but if this confuses me, I'm pretty certain it'll confuse others too.

I was referring to errors occurring during parallel calls.

Moot or not, they're tested :smile:

I didn't realize! grappling-hook is ALMOST complete!

It is complete! Just never finished :wink:

Fixed in 2.2.0


Federation Cleanup (1) doc: clean some outdate redirects and its associated content.

As the title said, this PR is going to mainly cleanup the federation content inside static/_redirects.
Something inside /docs/concepts/cluster-administration/federation.md has been kept in this PR since there is PR #19525 , and those content should be cleaned once that PR merged.
What's more, the api references part inside this file is skipped right now, it will be followed by another separate PR.
Thanks.

Besides, if there is no exception case, the federation relative l10n pages should be cleaned by each l10n team.

/cc @zacharysarah @kbhawkey  @sftim .
Since this PR will change the site redirects.

@Colstuwjx Thanks for opening this PR. It looks to me like it's headed in the right direction.
/lgtm

@kbhawkey I have the nagging feeling you were having a conversation with someone else about federation PR timing at the 1.18 release.
Is that correct, or am I hallucinating? 🍄 🥴

Yep with @sftim in the umbrella issue. Suggested that we should go ahead an clean up the federation content.
👍


fix: freeze .components when parsing ParamType

ParamType is supposed to be frozen and is checked for that on deepCopy(), but .components array itself was missed, even though each individual element was frozen.

Should probably report this upstream, as deepCopy operates incorrectly on those otherwise.
Our coherence check just outlined that, but the problem exists upstream.


Interesting in taking ownership of this project...

If possible, I'd like to chat a bit about it... please let me know if there is a preferred way of doing this.

@joltcoder This is not really an issue, so I'm going to close it. I can be contacted via email, on Twitter (@jimevansmusic), or in the Selenium project's IRC channel (#selenium on Freenode, but also mirrored via Slack).


feat: ensure .repo-metadata.json file is included in published jars

The .repo-metadata.json file in each repo includes useful metadata that should be included in published jars.
To test this change locally:

Pull down this change and run mvn clean install -Dskiptests to install a local copy of google-cloud-shared-config to your machine
Clone your favorite client library repo (say google-cloud-java) and run mvn clean package -DskipTests
Extract the generated jar and examine the contents. The .repo-metadata.json file should exist under the META-INF directory, next to the INDEX.LIST and MANIFEST.MF files.

Closing this as it's no longer needed


v1.14 Backports 2024-03-15

[ ] #31395 (@tklauser)
[ ] #31421 (@tklauser)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 31395 31421

/test-backport-1.14


ERROR: Error: image naver/pinpoint-hbase not found

Clone of the current master branch.
docker-compose up fails with the following error:
Pulling pinpoint-hbase (naver/pinpoint-hbase:1.6.0-SNAPSHOT)...
Trying to pull repository docker.io/naver/pinpoint-hbase ...
Pulling repository docker.io/naver/pinpoint-hbase
Error: image naver/pinpoint-hbase not found
ERROR: Error: image naver/pinpoint-hbase not found

You need to build whole project in order to have snapshot version. Or you can use my images bu using this docker-compose file: https://github.com/dawidmalina/docker-pinpoint/blob/master/docker-compose.yml

Thanks, I'll give that a try.

Thanks @dawidmalina, that solved it.


Submitting loop request did not return the correct number of loops

Bug report
When loop request is submitted with a loop count of  > 1, it will occasionally return a loop count of 1 instead.
Required information:

Operating system and version:

OpenRMF installation type:

OpenRMF version or commit hash

ROS distribution and version:

ROS installation type:

Package or library, if applicable:

Description of the bug

Steps to reproduce the bug

Expected behavior

Actual behavior

Screenshots

Additional information

fixed


Added RegexSubProcessor Attribute Processor

I created a new attribute processor that can substitute and reformat attribute values using using regex patterns. This PR adds a new AttributeProcessor class, and also includes an sample configuration.
All Submissions:

[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you added an explanation of what problem you are trying to solve with this PR?
[x] Have you added information on what your changes do and why you chose this as your solution?
[ ] Have you written new tests for your changes?
[ ] Does your submission pass tests?
[ ] This project follows PEP8 style guide.

Ideally, in the future, the core of satosa will be separated from the micro-services/plugins. The plugins will be their own package and can be provided by anyone (you can already do this). I am accepting this, but keep in mind that at some point, a new breaking release will come out which will be only about the core - details are not yet clear, but I'm giving you a direction of where we'll go moving forward.


Spatial reflection

@JuliaRegistrator register
Release notes:

New symmetry: SpatialReflection
new function: basissize

Comments on pull requests will not trigger Registrator, as it is disabled. Please try commenting on a commit or issue.


GitHub token

This fixes a problem where upload-charm-docs got the Charmhub token instead of the GitHub token
I thought about adding tests for this, it wouldn't be straight forward, I'll add it to our backlog. Since our CI is blocked by this not working I propose to merge this without adding an integration test initially

Ok, I tested this for Wordpress and it works as intended. It actually picked up some conflicting changes which is interesting: https://github.com/canonical/wordpress-k8s-operator/pull/66

Looks good, I assume that was a typo in the first place, passing in CHARMHUB_TOKEN to a github_token key?

yes thats right


Color handling for Button and Slider

Please don't change the formatting in ChromaView.kt. Just keep it as it is.

Please don't change the formatting in ChromaView.kt. Just keep it as it is.

sorry was an accident


shelley-test: epoch size of 10k/f not 10k

The Shelley era should use an epoch size of 10k/f, not just 10/k.

bors r+


Keras 2.4.3 test missing cases

System information

OS Platform and Distribution :Linux Ubuntu 16.04
TensorFlow installed from (source or binary): Source
TensorFlow version: 2.2.0
Python version: 3.8.5
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source): 5.4.0
CUDA/cuDNN version:  Cuda10.0, cudnn <IP_ADDRESS>
GPU model and memory: GTX1070 , 8G

Keras version 2.4.3
I have a mnist script to test my tensorflow installation
'''Trains a simple convnet on the MNIST dataset.
Gets to 99.25% test accuracy after 12 epochs
(there is still a lot of margin for parameter tuning).
16 seconds per epoch on a GRID K520 GPU.
'''

import keras
from keras.datasets import mnist
from keras.models import Sequential
from keras.layers import Dense, Dropout, Flatten
from keras.layers import Conv2D, MaxPooling2D
from keras import backend as K

batch_size = 128
num_classes = 10
epochs = 12

# input image dimensions
img_rows, img_cols = 28, 28

# the data, split between train and test sets
(x_train, y_train), (x_test, y_test) = mnist.load_data()

if K.image_data_format() == 'channels_first':
    x_train = x_train.reshape(x_train.shape[0], 1, img_rows, img_cols)
    x_test = x_test.reshape(x_test.shape[0], 1, img_rows, img_cols)
    input_shape = (1, img_rows, img_cols)
else:
    x_train = x_train.reshape(x_train.shape[0], img_rows, img_cols, 1)
    x_test = x_test.reshape(x_test.shape[0], img_rows, img_cols, 1)
    input_shape = (img_rows, img_cols, 1)

x_train = x_train.astype('float32')
x_test = x_test.astype('float32')
x_train /= 255
x_test /= 255
print('x_train shape:', x_train.shape)
print(x_train.shape[0], 'train samples')
print(x_test.shape[0], 'test samples')

# convert class vectors to binary class matrices
y_train = keras.utils.to_categorical(y_train, num_classes)
y_test = keras.utils.to_categorical(y_test, num_classes)

model = Sequential()
model.add(Conv2D(32, kernel_size=(3, 3),
                 activation='relu',
                 input_shape=input_shape))
model.add(Conv2D(64, (3, 3), activation='relu'))
model.add(MaxPooling2D(pool_size=(2, 2)))
model.add(Dropout(0.25))
model.add(Flatten())
model.add(Dense(128, activation='relu'))
model.add(Dropout(0.5))
model.add(Dense(num_classes, activation='softmax'))

model.compile(loss=keras.losses.categorical_crossentropy,
              optimizer=keras.optimizers.Adadelta(),
              metrics=['accuracy'])

model.fit(x_train, y_train,
          batch_size=batch_size,
          epochs=epochs,
          verbose=1,
          validation_data=(x_test, y_test))
score = model.evaluate(x_test, y_test, verbose=0)
print('Test loss:', score[0])
print('Test accuracy:', score[1])

Describe the current behavior
A lot of samples are lost, here is the output of running the script with keras 2.4.3 with tensoflow backend [in my setup python=python3] Comparing to expected behaviour below (with kereas 2.3.1), there are only 496 samples in an epoch instead of 6000
python /home/bernard/python-dev/test/mnist_cnn_demo.py
2020-07-31 21:34:53.674307: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
x_train shape: (60000, 28, 28, 1)
60000 train samples
10000 test samples
2020-07-31 21:34:55.075415: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1
2020-07-31 21:34:55.104800: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:34:55.105872: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce GTX 1070 computeCapability: 6.1
coreClock: 1.695GHz coreCount: 16 deviceMemorySize: 7.92GiB deviceMemoryBandwidth: 238.66GiB/s
2020-07-31 21:34:55.105894: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
2020-07-31 21:34:55.107057: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2020-07-31 21:34:55.107952: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10.0
2020-07-31 21:34:55.108219: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10.0
2020-07-31 21:34:55.109467: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0
2020-07-31 21:34:55.110373: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10.0
2020-07-31 21:34:55.113179: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-07-31 21:34:55.113334: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:34:55.113952: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:34:55.114509: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1703] Adding visible gpu devices: 0
2020-07-31 21:34:55.121289: I tensorflow/core/platform/profile_utils/cpu_utils.cc:102] CPU Frequency:<PHONE_NUMBER> Hz
2020-07-31 21:34:55.121631: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x42e2280 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-07-31 21:34:55.121650: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-07-31 21:34:55.182191: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:34:55.182711: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x436c5e0 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2020-07-31 21:34:55.182743: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): GeForce GTX 1070, Compute Capability 6.1
2020-07-31 21:34:55.182917: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:34:55.183371: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce GTX 1070 computeCapability: 6.1
coreClock: 1.695GHz coreCount: 16 deviceMemorySize: 7.92GiB deviceMemoryBandwidth: 238.66GiB/s
2020-07-31 21:34:55.183411: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
2020-07-31 21:34:55.183441: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2020-07-31 21:34:55.183470: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10.0
2020-07-31 21:34:55.183482: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10.0
2020-07-31 21:34:55.183493: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0
2020-07-31 21:34:55.183516: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10.0
2020-07-31 21:34:55.183545: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-07-31 21:34:55.183616: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:34:55.184210: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:34:55.184688: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1703] Adding visible gpu devices: 0
2020-07-31 21:34:55.184751: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
2020-07-31 21:34:55.665812: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1102] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-07-31 21:34:55.665860: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1108]      0
2020-07-31 21:34:55.665888: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1121] 0:   N
2020-07-31 21:34:55.666241: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:34:55.666841: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:34:55.667435: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1247] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 6988 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1070, pci bus id: 0000:01:00.0, compute capability: 6.1)
Epoch 1/12
2020-07-31 21:34:56.279338: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2020-07-31 21:34:56.477766: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
469/469 [==============================] - 4s 8ms/step - loss: 2.2858 - accuracy: 0.1543 - val_loss: 2.2619 - val_accuracy: 0.2190
Epoch 2/12
469/469 [==============================] - 3s 7ms/step - loss: 2.2462 - accuracy: 0.2411 - val_loss: 2.2135 - val_accuracy: 0.3888
Epoch 3/12
469/469 [==============================] - 3s 7ms/step - loss: 2.1951 - accuracy: 0.3359 - val_loss: 2.1482 - val_accuracy: 0.5546
Epoch 4/12
469/469 [==============================] - 3s 7ms/step - loss: 2.1254 - accuracy: 0.4195 - val_loss: 2.0573 - val_accuracy: 0.6437
Epoch 5/12
469/469 [==============================] - 3s 7ms/step - loss: 2.0294 - accuracy: 0.4904 - val_loss: 1.9342 - val_accuracy: 0.6910
Epoch 6/12
469/469 [==============================] - 3s 7ms/step - loss: 1.9057 - accuracy: 0.5410 - val_loss: 1.7749 - val_accuracy: 0.7224
Epoch 7/12
469/469 [==============================] - 3s 7ms/step - loss: 1.7500 - accuracy: 0.5860 - val_loss: 1.5826 - val_accuracy: 0.7497
Epoch 8/12
469/469 [==============================] - 3s 7ms/step - loss: 1.5807 - accuracy: 0.6156 - val_loss: 1.3772 - val_accuracy: 0.7735
Epoch 9/12
469/469 [==============================] - 3s 7ms/step - loss: 1.4153 - accuracy: 0.6406 - val_loss: 1.1840 - val_accuracy: 0.7954
Epoch 10/12
469/469 [==============================] - 3s 7ms/step - loss: 1.2699 - accuracy: 0.6618 - val_loss: 1.0213 - val_accuracy: 0.8093
Epoch 11/12
469/469 [==============================] - 3s 7ms/step - loss: 1.1508 - accuracy: 0.6834 - val_loss: 0.8939 - val_accuracy: 0.8220
Epoch 12/12
469/469 [==============================] - 3s 7ms/step - loss: 1.0579 - accuracy: 0.7003 - val_loss: 0.7974 - val_accuracy: 0.8316
Test loss: 0.7974222898483276
Test accuracy: 0.83160001039505

Describe the expected behavior
Downgraded keras to version 2.3.1 and run the script again, the outcome is consistent with older versions of keras before
Note that Train on 60000 samples, validate on 10000 samples is missing from the output above using keras 2.4.3.
python /home/bernard/python-dev/test/mnist_cnn_demo.py
Using TensorFlow backend.
x_train shape: (60000, 28, 28, 1)
60000 train samples
10000 test samples
2020-07-31 21:17:44.616490: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1
2020-07-31 21:17:44.641796: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:17:44.643804: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce GTX 1070 computeCapability: 6.1
coreClock: 1.695GHz coreCount: 16 deviceMemorySize: 7.92GiB deviceMemoryBandwidth: 238.66GiB/s
2020-07-31 21:17:44.644032: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
2020-07-31 21:17:44.645151: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2020-07-31 21:17:44.646009: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10.0
2020-07-31 21:17:44.646247: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10.0
2020-07-31 21:17:44.647392: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0
2020-07-31 21:17:44.648247: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10.0
2020-07-31 21:17:44.650968: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-07-31 21:17:44.651097: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:17:44.651925: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:17:44.652674: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1703] Adding visible gpu devices: 0
2020-07-31 21:17:44.658691: I tensorflow/core/platform/profile_utils/cpu_utils.cc:102] CPU Frequency:<PHONE_NUMBER> Hz
2020-07-31 21:17:44.659154: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x5cb4a20 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-07-31 21:17:44.659167: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-07-31 21:17:44.718817: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:17:44.719399: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x5d43f30 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2020-07-31 21:17:44.719434: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): GeForce GTX 1070, Compute Capability 6.1
2020-07-31 21:17:44.719622: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:17:44.720238: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1561] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce GTX 1070 computeCapability: 6.1
coreClock: 1.695GHz coreCount: 16 deviceMemorySize: 7.92GiB deviceMemoryBandwidth: 238.66GiB/s
2020-07-31 21:17:44.720286: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
2020-07-31 21:17:44.720299: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2020-07-31 21:17:44.720330: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10.0
2020-07-31 21:17:44.720343: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10.0
2020-07-31 21:17:44.720354: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0
2020-07-31 21:17:44.720379: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10.0
2020-07-31 21:17:44.720390: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-07-31 21:17:44.720463: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:17:44.721061: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:17:44.721531: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1703] Adding visible gpu devices: 0
2020-07-31 21:17:44.721574: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
2020-07-31 21:17:44.722447: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1102] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-07-31 21:17:44.722457: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1108]      0
2020-07-31 21:17:44.722479: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1121] 0:   N
2020-07-31 21:17:44.722716: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:17:44.723177: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-07-31 21:17:44.724393: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1247] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 7088 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1070, pci bus id: 0000:01:00.0, compute capability: 6.1)
**Train on 60000 samples, validate on 10000 samples**
Epoch 1/12
2020-07-31 21:17:45.945316: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2020-07-31 21:17:46.131405: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
Epoch 1/12
2020-07-31 21:24:25.101205: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2020-07-31 21:24:25.295790: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
60000/60000 [==============================] - 5s 91us/step - loss: 0.2614 - accuracy: 0.9188 - val_loss: 0.0578 - val_accuracy: 0.9811
Epoch 2/12
60000/60000 [==============================] - 4s 67us/step - loss: 0.0910 - accuracy: 0.9730 - val_loss: 0.0411 - val_accuracy: 0.9857
Epoch 3/12
60000/60000 [==============================] - 4s 67us/step - loss: 0.0656 - accuracy: 0.9805 - val_loss: 0.0407 - val_accuracy: 0.9862
Epoch 4/12
60000/60000 [==============================] - 4s 67us/step - loss: 0.0538 - accuracy: 0.9837 - val_loss: 0.0311 - val_accuracy: 0.9898
Epoch 5/12
60000/60000 [==============================] - 4s 67us/step - loss: 0.0483 - accuracy: 0.9850 - val_loss: 0.0288 - val_accuracy: 0.9904
Epoch 6/12
60000/60000 [==============================] - 4s 67us/step - loss: 0.0412 - accuracy: 0.9878 - val_loss: 0.0291 - val_accuracy: 0.9905
Epoch 7/12
60000/60000 [==============================] - 4s 67us/step - loss: 0.0381 - accuracy: 0.9888 - val_loss: 0.0283 - val_accuracy: 0.9902
Epoch 8/12
60000/60000 [==============================] - 4s 67us/step - loss: 0.0354 - accuracy: 0.9892 - val_loss: 0.0286 - val_accuracy: 0.9914
Epoch 9/12
60000/60000 [==============================] - 4s 68us/step - loss: 0.0330 - accuracy: 0.9900 - val_loss: 0.0275 - val_accuracy: 0.9916
Epoch 10/12
60000/60000 [==============================] - 4s 74us/step - loss: 0.0314 - accuracy: 0.9909 - val_loss: 0.0276 - val_accuracy: 0.9916
Epoch 11/12
60000/60000 [==============================] - 5s 77us/step - loss: 0.0300 - accuracy: 0.9907 - val_loss: 0.0248 - val_accuracy: 0.9917
Epoch 12/12
60000/60000 [==============================] - 5s 77us/step - loss: 0.0264 - accuracy: 0.9920 - val_loss: 0.0292 - val_accuracy: 0.9907
Test loss: 0.02923813719809523
Test accuracy: 0.9907000064849854

@beew
Could you please try "tf.keras" instead of "keras" and let us know.

@Saduf2019
No change. But may be I get you wrong, replace keras by tf.keras where? Everywhere?

@beew
Yes beew everywhere in the code.

I have updated the script but there is no change, still missing lots of cases.
But the interesting thing is with this script even keras2.3.1 gave the same wrong result so maybe the problem is tf.keras (and for keras 2.4.3 it somehow switches to that but keras-2.3.1 doesn't unless it is explicit like in the modified script)
Here is the updated script
import tensorflow as tf

from tensorflow.keras.datasets import mnist
from tensorflow.keras.models import Sequential
from tensorflow.keras.layers import Dense, Dropout, Flatten
from tensorflow.keras.layers import Conv2D, MaxPooling2D
from tensorflow.keras import backend as K

batch_size = 128
num_classes = 10
epochs = 12

# input image dimensions
img_rows, img_cols = 28, 28

# the data, split between train and test sets
(x_train, y_train), (x_test, y_test) = mnist.load_data()

if K.image_data_format() == 'channels_first':
    x_train = x_train.reshape(x_train.shape[0], 1, img_rows, img_cols)
    x_test = x_test.reshape(x_test.shape[0], 1, img_rows, img_cols)
    input_shape = (1, img_rows, img_cols)
else:
    x_train = x_train.reshape(x_train.shape[0], img_rows, img_cols, 1)
    x_test = x_test.reshape(x_test.shape[0], img_rows, img_cols, 1)
    input_shape = (img_rows, img_cols, 1)

x_train = x_train.astype('float32')
x_test = x_test.astype('float32')
x_train /= 255
x_test /= 255
print('x_train shape:', x_train.shape)
print(x_train.shape[0], 'train samples')
print(x_test.shape[0], 'test samples')

# convert class vectors to binary class matrices
y_train = tf.keras.utils.to_categorical(y_train, num_classes)
y_test = tf.keras.utils.to_categorical(y_test, num_classes)

model = Sequential()
model.add(Conv2D(32, kernel_size=(3, 3),
                 activation='relu',
                 input_shape=input_shape))
model.add(Conv2D(64, (3, 3), activation='relu'))
model.add(MaxPooling2D(pool_size=(2, 2)))
model.add(Dropout(0.25))
model.add(Flatten())
model.add(Dense(128, activation='relu'))
model.add(Dropout(0.5))
model.add(Dense(num_classes, activation='softmax'))

model.compile(loss=tf.keras.losses.categorical_crossentropy,
              optimizer=tf.keras.optimizers.Adadelta(),
              metrics=['accuracy'])

model.fit(x_train, y_train,
          batch_size=batch_size,
          epochs=epochs,
          verbose=1,
          validation_data=(x_test, y_test))
score = model.evaluate(x_test, y_test, verbose=0)
print('Test loss:', score[0])
print('Test accuracy:', score[1])

@ymodak
I am able to replicate this, please find the gist here

I think this is correct since we have steps_per_epoch as 469;
steps_per_epoch (469) = #total no of samples (60000) / batch_size (128)
I earlier version only the number of samples are shown (60000).

I tested with keras 2.3.1 and get similar accuracy of 83%.
See the gist for your reference.
Closing this issue since the original topic is resolved. Thanks!

I tested with keras 2.3.1 and get similar accuracy of 83%.
See the gist for your reference.
Closing this issue since the original topic is resolved. Thanks!
Well I don't think you really resolve the issue, it probably just means there is something wrong in using tf.keras in place of keras and it still seems like something wrong considering that the error and loss cases are much bigger than before.

@beew Can you please share a gist showing the discrepancy in accuracy across various versions?
I have tested with Keras 2.3.1 and got accuracy of 83%, whereas with TF 2.3 and Keras - 2.4.3 it is 86% . Thus, I see better accuracy with later version.
Also which error did you encounter?
May be I am missing something here. Thanks!

I think this is correct since we have steps_per_epoch as 469;
steps_per_epoch (469) = #total no of samples (60000) / batch_size (128)
In earlier versions only the number of samples are shown (60000).

Does that mean it is trained 60000 time or do we have to change batch size to 1 to train 60000 time ?


Makes computers and machines use power.

You shouldn't be able to clone a living person with 5W.
Also makes light bulbs use even more power.
:cl: moony

tweak: Nanotrasen has run out of space magic that allows them to make computers and machines use only 5W. Station power usage has greatly increased, and engineers only have 7-8 minutes to get power up and running before things start to get a bit hairy.
tweak: Lightbulbs are now 120W industrial bulbs, instead of 40W high efficiency ones.
remove: AME no longer requires APC power to start, to make it a bit easier to pick up after engineers who refuse to engineer.

lgtm, BUT how do the stations powernets fare against this sudden increase in powerconsumption?

Measured it in #contributors last night, Packed stays recoverable until 18 min into the round, and departments begin to lose power 8min in.
Saltern seemed to follow the same pattern, though i didn't sit around for 20min to see what dept depowers last, i just know it's fine for about 7-8 minutes.

lgtm, BUT how do the stations powernets fare against this sudden increase in powerconsumption?

Measured it in #contributors last night, Packed stays recoverable until 18 min into the round, and departments begin to lose power 8min in. Saltern seemed to follow the same pattern, though i didn't sit around for 20min to see what dept depowers last, i just know it's fine for about 7-8 minutes.

thats way to fast for being unrecoverable imo

Happy to pick this up at some point if you're busy / not available @moonheart08, up to you :)


Cannot read property '0' of null

I have ran to this issue when run redis-commander on cmd. My Os version is Windows 10
Full report

I got the same problem after a full fresh install
Windows 10
Node version: 12.16.1 LTS

duplicate of #388


Adding a React front end

Has anyone successfully added a React SSR front end to this? Any tips and/or pointers on it? How hard is it?

Honestly, just use Next.js. Hackathon Starter isn't designed for SPAs with SSR. Sure, you can build a React app to use with Hackathon Starter, but you'll end up throwing out all of the default views etc. If you were to use Hackathon Starter, you'd be best to use it purely as a backend API server (add JWT support etc.), and use Next.js as a separate frontend, but I feel that there's already far better solutions out there for this and this approach is not the goal of this project.

@niallobrien thanks for the suggestions... what other solutions are out there that would be better suited.

And cant be this somehow remade for nextjs? Because in nextjs there is missing something like this.

Is it easy to utilize this starter pack just as API and create fron-end separately either with next.js or create react app or any other front-end?

It depends on you really. Something like StrapiJS might be better suited -
again it depends on you and your needs.
On Tue 24 Dec 2019, 00:40 ertejaspatel<EMAIL_ADDRESS>wrote:

Is it easy to utilize this starter pack just as API and create fron-end
separately either with next.js or create react app or any other front-end?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sahat/hackathon-starter/issues/1023?email_source=notifications&email_token=AALUPJLW4WVPFXS3G4WI2M3Q2FK7DA5CNFSM4JZHB4HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHSF6QI#issuecomment-568614721,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALUPJI3RHRGVZU3UHEBUHLQ2FK7DANCNFSM4JZHB4HA
.

Is it easy to utilize this starter pack just as API and create front-end separately either with next.js or create react app or any other front-end?

next.js is using its own API routes (in version 9+) which is try to remove express. Which is a little bit harder to remake. Anyway, if anybody did this. Please share it. Merry Christmas :)


fetch-client with aurelia cli - build errors

I'm submitting a bug report

Library Version:
0.17.0

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
4.4.5

NPM Version:
2.15.5 (npm -v)
3.9.6  (npm3 -v)

JSPM OR Webpack AND Version
JSPM 0.16.39

Language:
TypeScript 2.0.0

Current behavior:
Running an asp.net core app with Aurelia CLI
Trying to use aurelia-fetch-client (is present in node_modules)
Note: same process using aurelia-http-client builds fine.
au build throws the following errors:
$ au build
Starting 'readProjectConfiguration'...
Finished 'readProjectConfiguration'
Starting 'processMarkup'...
Starting 'processCSS'...
Starting 'configureEnvironment'...
Finished 'processCSS'
Finished 'configureEnvironment'
Starting 'buildTypeScript'...
Finished 'processMarkup'
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(17,23): error TS2304: Cannot find name 'Request'.
[11:32:13] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(17,23): error TS2304: Cannot find name 'Request'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(17,35): error TS2304: Cannot find name 'Request'.
[11:32:13] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(17,35): error TS2304: Cannot find name 'Request'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(17,45): error TS2304: Cannot find name 'Response'.
[11:32:13] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(17,45): error TS2304: Cannot find name 'Response'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(17,64): error TS2304: Cannot find name 'Request'.
[11:32:13] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(17,64): error TS2304: Cannot find name 'Request'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(17,74): error TS2304: Cannot find name 'Response'.
[11:32:13] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(17,74): error TS2304: Cannot find name 'Response'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(27,34): error TS2304: Cannot find name 'Request'.
[11:32:13] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(27,34): error TS2304: Cannot find name 'Request'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(27,44): error TS2304: Cannot find name 'Response'.
[11:32:13] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(27,44): error TS2304: Cannot find name 'Response'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(27,63): error TS2304: Cannot find name 'Request'.
[11:32:13] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(27,63): error TS2304: Cannot find name 'Request'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(27,73): error TS2304: Cannot find name 'Response'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(27,73): error TS2304: Cannot find name 'Response'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(36,25): error TS2304: Cannot find name 'Response'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(36,25): error TS2304: Cannot find name 'Response'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(36,45): error TS2304: Cannot find name 'Request'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(36,45): error TS2304: Cannot find name 'Request'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(36,57): error TS2304: Cannot find name 'Response'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(36,57): error TS2304: Cannot find name 'Response'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(36,76): error TS2304: Cannot find name 'Response'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(36,76): error TS2304: Cannot find name 'Response'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(47,42): error TS2304: Cannot find name 'Request'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(47,42): error TS2304: Cannot find name 'Request'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(47,54): error TS2304: Cannot find name 'Response'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(47,54): error TS2304: Cannot find name 'Response'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(47,73): error TS2304: Cannot find name 'Response'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(47,73): error TS2304: Cannot find name 'Response'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(68,13): error TS2304: Cannot find name 'Headers'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(68,13): error TS2304: Cannot find name 'Headers'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(73,43): error TS2304: Cannot find name 'URLSearchParams'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(73,43): error TS2304: Cannot find name 'URLSearchParams'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(258,16): error TS2304: Cannot find name 'Request'.
[11:32:14] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(258,16): error TS2304: Cannot find name 'Request'.
path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(258,63): error TS2304: Cannot find name 'Response'.
[11:32:15] gulp-notify: [Error running Gulp] Error: path-to-app/node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(258,63): error TS2304: Cannot find name 'Response'.
[11:32:15] TypeScript: 20 semantic errors
[11:32:15] TypeScript: emit succeeded (with errors)
Finished 'buildTypeScript'
Starting 'writeBundles'...
Tracing environment...
Tracing main...
...

What is the expected behavior?
au build with no errors

I have the exact same issue, using the current commit.

Check https://github.com/aurelia/fetch-client/issues/71

I'm observing the same issue as @AdrianBathurst with an identical environment. The functionality works as expected, despite the compiler errors. Switching to aurelia-http-client builds and runs without error.

Closing as duplicate.


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 40e7486:
:clock10: Pending: waiting for processors (27 builds ahead of you)
:warning: Docs Build is busy, currently there are 27 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 40e7486:
:clock10: Full build: the average full build time is 7 min(s) 23 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 40e7486:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Outline not working with rescript project

Describe the bug
Nothing happens using the Lspsaga outline command in a Rescript project.
If the command is executed again the message [lspsaga.nvim] there is already a request for outline please wait shows in the status line.
Steps to reproduce
Using rescriptls as language server, run Lspsaga outline in a rescript file with any kind of data inside.
Expected behavior
The outline to shows up
Neovim version (nvim -v)
0.9.0 release
lspsaga commit
76696bed4397c3b58563c246dc1f7856ed4af023
Terminal name/version
Iterm 2 in macos Ventura

does it works well with other projects in your local ?


Nomenclature for IO (and MFA/LCA?)

Hi
Richard just asked me if we are discussing terminology in our group.
After a short discussion, I am quite convinced that we should also make an effort to recommend a common nomenclature for variables commonly used in IndEcol. For example, currently L or B are used for the Leontief, S or F for the satellite accounts, ... I am not quite sure about the experiences in LCA/MFA but I suspect the same problems are present there.
For MRIO, I tried to summarize my understanding of the variable names here
http://pymrio.readthedocs.io/en/latest/terminology.html
We can not enforce a specific nomenclature (its not biology...), but we can give strong recommendations.
I know, that the whole matter is quite confusing for students and it would also help to quicker grasp algorithm in papers (and in code). Probably its also a good first starting point towards an ontology. Richard had/will also bring it up in the EEIO section of ISIE.

Hi Konstantin,
I use exactly the same terminology, except for SY, what is that? FY per unit of Y?

Exactly, needed if you change the demand in the model


[DialogActions] Add missing TypeScript property

Closes #10668

@franklixuefei Thanks for the review
@youngnicks It's a great first-time pull request 👌🏻. Thank you for giving it a shot!


Atom said to report this error

Atom said to report this error. Please reply why this came. My scss files r not compiling properly is that has to do with this error
Atom Version: 1.9.8
System: Microsoft Windows 10 Pro
Thrown From: Atom Core
Stack Trace
Uncaught Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
at ObjectsRegistry.get (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\electron.asar\browser\objects-registry.js:44:28)
at EventEmitter. (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\electron.asar\browser\rpc-server.js:309:31)
at emitMany (events.js:121:13)
at EventEmitter.emit (events.js:195:7)
at EventEmitter. (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\electron.asar\browser\api\web-contents.js:141:25)
at emitTwo (events.js:100:13)
at EventEmitter.emit (events.js:185:7)
At C:\Users\username\AppData\Local\atom\app-1.9.8\resources\electron.asar\renderer\api\remote.js:178

Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
    at ObjectsRegistry.get (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\electron.asar\browser\objects-registry.js:44:28)
    at EventEmitter.<anonymous> (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\electron.asar\browser\rpc-server.js:309:31)
    at emitMany (events.js:121:13)
    at EventEmitter.emit (events.js:195:7)
    at EventEmitter.<anonymous> (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\electron.asar\browser\api\web-contents.js:141:25)
    at emitTwo (events.js:100:13)
    at EventEmitter.emit (events.js:185:7)
    at metaToValue (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\electron.asar\renderer\api\remote.js:178:13)
    at undefined.remoteMemberFunction (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\electron.asar\renderer\api\remote.js:112:18)
    at AtomEnvironment.module.exports.AtomEnvironment.getWindowDimensions (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\app.asar\src\atom-environment.js:631:29)
    at AtomEnvironment.module.exports.AtomEnvironment.storeWindowDimensions (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\app.asar\src\atom-environment.js:665:36)
    at WindowEventHandler.module.exports.WindowEventHandler.handleWindowBlur (C:\Users\username\AppData\Local\atom\app-1.9.8\resources\app.asar\src\window-event-handler.js:182:35)
    at C:\Users\username\AppData\Local\atom\app-1.9.8\resources\app.asar\src\window-event-handler.js:3:61

Commands
     -5:34.2.0 sass-autocompile:compile-to-file (atom-text-editor.editor.is-focused)
     -4:27.8.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:25.8.0 tree-view:copy-full-path (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)

Config
{
  "core": {
    "disabledPackages": [
      "sass-autocompile"
    ],
    "themes": [
      "one-dark-ui",
      "spacegray-atom-dark-syntax"
    ]
  },
  "editor": {
    "fontFamily": "roboto mono",
    "fontSize": 13,
    "scrollPastEnd": true,
    "showIndentGuide": true
  }
}

Installed Packages
# User
emmet, v2.4.3 (active)
fonts, v1.6.0 (active)
language-robotc, v0.3.4 (active)
linter, v1.11.16 (active)
linter-sass-lint, v1.7.0 (active)
pigments, v0.31.2 (active)
sass-autocompile, v0.12.8 (inactive)
sass-compiler, v0.4.0 (active)
spacegray-atom-dark-syntax, v1.1.1 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.51.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.43.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.3.2 (active)
one-light-ui, v1.3.2 (inactive)
one-dark-syntax, v1.2.0 (inactive)
one-light-syntax, v1.2.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.2 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.0 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.0 (active)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.39.0 (active)
fuzzy-finder, v1.3.0 (active)
git-diff, v1.1.0 (active)
find-and-replace, v0.198.0 (inactive)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v0.53.1 (active)
notifications, v0.64.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.238.2 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (active)
status-bar, v1.4.1 (active)
styleguide, v0.46.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.98.1 (active)
timecop, v0.33.1 (active)
tree-view, v0.208.0 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (active)
whitespace, v0.32.2 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.0 (active)
language-csharp, v0.12.1 (active)
language-css, v0.36.2 (active)
language-gfm, v0.86.0 (active)
language-git, v0.13.0 (active)
language-go, v0.42.0 (active)
language-html, v0.44.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.22.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.0 (active)
language-less, v0.29.3 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.0 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.68.5 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.52.0 (active)
language-shellscript, v0.22.3 (active)
language-source, v0.9.0 (active)
language-sql, v0.21.1 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.8 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

This is a duplicate of #11692 - feel free to subscribe there for updates.


[BUG] Interpolate bads ignores ECoG and sEEG channels

Description of the problem
Interpolate bads silently ignores ecog and seeg channels.
Steps to reproduce
import mne

misc_path = mne.datasets.misc.data_path()

raw = mne.io.read_raw(misc_path / 'ecog' / 'sample_ecog_ieeg.fif')
raw.info['bads'] = ['G10', 'G51']
raw.load_data()
raw.interpolate_bads()

Link to data
No response
Expected results
Channels should be interpolated
Actual results
Setting channel interpolation method to {}.
<ipython-input-10-fe35daf7ae7f>:2: RuntimeWarning: No bad channels to interpolate. Doing nothing...

Additional information
I think for ecog the existing spherical interpolation is reasonable. Perhaps seeg should interpolate per lead but I think raising a NotImplementedError would be more helpful.

Tagging @mscheltienne @adam2392 @jasmainak for thoughts

I think for ecog the existing spherical interpolation is reasonable. Perhaps seeg should interpolate per lead but I think raising a NotImplementedError would be more helpful.

I am +1 for both. Tho, perhaps the real challenge for us is showing the spherical interpolation is useful at all for users.

Tho, perhaps the real challenge for us is showing the spherical interpolation is useful at all for users.

In my particular use case there are a few pops and wayward sensors on an ECoG grid with very limited trials because it was intraoperative. I think in that case, tossing the whole epoch or the whole channel are not ideal so an interpolation seems like the best choice.

I think for ecog the existing spherical interpolation is reasonable. Perhaps seeg should interpolate per lead

+1 for both, I never worked with intracranial data, do we store information about the grid and lead geometry?
Raising a NotImplementedError could be detrimental in an edge-case with a Raw containing multiple channel types that can be interpolated. For instance, combined stereo-EEG with scalp-EEG or with MEG recordings. I would however improve the RuntimeWarning to mention the channel types and bad channels that were not interpolated.

Maybe I'll just add a spline interpolation on an sEEG shaft at the same time, shouldn't be too hard.


(style) adding docstrings to the synthetic data generator class

Thanks @fsndzomga ! just removed the signature instruction since it is not entirely separate from the descriptions present in the input and output fields already and would be handled by the default dspy.Predict template.

That's perfect ! Thank you @arnavsinghvi11 !


Multiple file uploads Callback.

When workin 'allowMultiple` is there a callback when all files have been uploaded successfully?

Hi, there currently is not, you’d have to check if all files are processed when a new file is processsd.

Hey rik.
First, thank you for the nice uploader.
Second, is there any function I can query to get the items in the queue and the status of those?

i implemented it like this:
<script>
    function getUploadStatus(){
      var totalFiles = $('.filepond--item').length;
      var completedFiles = $('.filepond--item[data-filepond-item-state="processing-complete"]').length;
      console.log('totalFiles: '+totalFiles);
      console.log('completedFiles: '+completedFiles);
      if(completedFiles == totalFiles){
        alert('done');
      }
    }
</script>

<script>
pond.onprocessfile = (error, file) => {
            if (error) {
                console.log('Oh no');
                return;
            }
            getUploadStatus();
        }
</script>

To add to this, you can use the item.status property and then compare it using the FilePond.


Add Speaker readonly API

what is this for?

@anicolaspp dotNet Miami API. This issue and the others were an attempt to organize the effort into small task sand get the community engaged. I failed to make much progress on Core...time, time, time.
But I am actually changing a few things, which I will share soon, probably right after Orlando Code Camp this coming weekend. Maybe the weekend after?
If you are happy to join this effort I could tell you more :)

Sure


Color bleeds out of outline despite masking enabled

Color seems to bleed out when using multiple masked containers with borders. The problem seems to become more obvious as resolution is lowered.

The drawable to recreate this problem:
new CircularContainer
{
	Scale = Vector2.Zero,
	Position = new Vector2(0, -26),
	Anchor = Anchor.Centre,
	Origin = Anchor.BottomCentre,
	Size = new Vector2(80),
	Alpha = 0,
	Masking = true,
	BorderThickness = 15,
	BorderColour = Color4.Crimson,
	Children = new Drawable[]
	{
    		new Box
    		{
        		RelativeSizeAxes = Axes.Both,
        		Alpha = 0,
        		AlwaysPresent = true,
        		Colour = Color4.Transparent,
    		},
    		new CircularContainer
    		{
        		RelativeSizeAxes = Axes.Both,
        		BorderThickness = 3f,
        		BorderColour = Color4.Black,
        		Masking = true,
        		Child = new Box
        		{
            			RelativeSizeAxes = Axes.Both,
            			Alpha = 0,
            			AlwaysPresent = true,
            			Colour = Color4.Transparent,
        		}
    		}
	}
}

Ah, this is quite a different scenario than I imagined. It's unlikely we'll ever be fixing this one - it's due to edge smoothing which has transparency.
These scenarios could probably be improved by using hard edges and an antialiasing shader, as a final pass but we don't have that and there are other ways that this can be avoided before that.
One such way is to inset the crimson border via the following:
new Container // Positioning + sizing
{
    Position = new Vector2(0, -26),
    Anchor = Anchor.Centre,
    Origin = Anchor.BottomCentre,
    Size = new Vector2(80),
    Children = new Drawable[]
    {
        new Container // Container to inset the crimson border
        {
            RelativeSizeAxes = Axes.Both,
            Padding = new MarginPadding(1),
            Child = new CircularContainer // The crimson border
            {
                RelativeSizeAxes = Axes.Both,
                Masking = true,
                BorderThickness = 15,
                BorderColour = Color4.Crimson,
                Child = new Box
                {
                    RelativeSizeAxes = Axes.Both,
                    Alpha = 0,
                    AlwaysPresent = true,
                    Colour = Color4.Transparent,
                }
            }
        },
        new CircularContainer // The black border
        {
            RelativeSizeAxes = Axes.Both,
            BorderThickness = 3f,
            BorderColour = Color4.Black,
            Masking = true,
            Child = new Box
            {
                RelativeSizeAxes = Axes.Both,
                Alpha = 0,
                AlwaysPresent = true,
                Colour = Color4.Transparent,
            }
        }
    }
}

I'm going to close this issue on the basis that we don't have a path forward for this, and may never will.


修改 Pages 页面为 md 文件

https://jekyllrb.com/docs/pages/

Jekyll already used Liquid templating language to process templates, which means some logic inside the HTML templates, so that it's not necessary to use Markdown mixing Liquid.


It won't work with default "$ctrl" in component view

I was not declaring controllerAs in my component and using default $ctrl in template. sv-root would be just empty div.
After couple of hours I discovered that you have to use controllerAs: 'something' and use it in your template in order to have this directive working.
Hope that helps someone.

@srokatonie, did you use 1.5 component in your case?

@vlio20 Yes, Angular 1.5.7

Thanks a lot! It works! :)

Being forced to use controllerAs: "somethingOtherThan$ctrl" is obviously not a good idea. I think sv-part directive should use an isolated scope. to prevent scope collision.

@srokatonie, why did you close it?

why close??

Stumbled again upon this 😞


Implement approved pill styling change

In 2018 and 2020 we approved new styling for the pill component. This issue will implement this change in the Design System.

Approval: https://github.cfpb.gov/CFPB/hubcap/issues/90#issuecomment-266484

As part of the React component work we have already implemented this update. We would now like to push the change to the Design System. Satellite apps will have to be handled separately but the risk is low given that satellite apps are currently using different styling than the CFPB core website.
Describe the solution you'd like
Updated styling:

background-color: Teal/20
border-color: Teal/100
Add here

Existing CSS for pills
.o-multiselect_choices button {
border: none;
background: none;
padding: 0;
.o-multiselect_choices li {
display: inline-block;
margin-right: 0.625em;
}
.o-multiselect_choices label {
display: inline-block;
padding: 2px 5px;
padding-right: 1.78571429em;
background-color: #5674a3;
border-radius: 0.28571429em;
color: #ffffff;
cursor: pointer;
font-size: 0.875em;
position: relative;
}
.o-multiselect_choices label .cf-icon-svg {
position: absolute;
top: 2px;
right: 5px;
fill: #d3daeb;
}
.cf-icon-svg {
height: 1.1875em;
vertical-align: text-top;
fill: currentcolor;
Describe alternatives you've considered
Full exploration here: https://github.cfpb.gov/CFPB/hubcap/issues/90#issuecomment-186734
Mock-up of approved implementation:

@jenn-franklin
In reviewing the implementation here: https://github.cfpb.gov/CFPB/hubcap/issues/90#issuecomment-266484 I am realizing that a few things have changed since this component change was approved. So I decided to conduct a quick exploration so that we can nail things down.
Button styles:

Height: 35px
Background color: #0072ce (Pacific 100)
Text: Avenir Next, Medium

Existing pills (live on the site):

Height: 22px
Background color: #5674a3 (Navy 80)
Text: Avenir Next, Regular or Medium (confirming now)

Buttons
Pills

Notes:

We deprecated the "Microcopy" level of text. The pills in my original product design used the "Microcopy" text style contained in the Figma template. In order to stay true to the current state I have switched out the text in the pill styling to paragraph text.
Buttons use Medium instead Regular text. In the mock-ups you can see that difference between the pill only designs (use Medium) and the example designs (use Regular).
I noticed that our standard button with icon component uses a pipe character to separate the text from the icon. I wanted to be sure to explore this so that we can be certain we don't want to include it (generally I was trying to use as much from the core button styles as possible and to be deliberate about deviating). My specific use case uses a pipe character to separate 2 values within the label so it's unfortunate. But I think that we should think more broadly and globally about this component.

No pipe separator
Includes pipe separator

Height: 30px

Do we have guidance on touch target sizes? My understanding is they are recommends to be a minimum of 44px x 44px. (See https://github.com/material-components/material-components-android/issues/1279, for example.) Does that affect the height we want for the pills?

@anselmbradford
We do have some general guidance on touch target sizes within the large target checkbox and radio button pages: https://cfpb.github.io/design-system/components/checkboxes#behavior.
What is the touch target for our standard button component? Standard buttons are 35px in height (visually) but do you know what we have the touch target size set to? Increasing the touch target for standard buttons is out of scope for this specific effort but I can open a separate issue if that is something you want to explore at this time.
What I am suggesting here is an increase in the existing height of the pills from 22px to 30px. So the touch target would improve with this change, and we could look at extending the area that responds to user input outside of that visual area, if possible, to more closely align with the guidance.

@anselmbradford @jenn-franklin
I think what I'll do is start building this out using the following specs. Then we can see how it's working.
Specs for R1:

Button height: 30px
Touch target size (height) - 45px
Background color: Team 20 (#d4e7e6) (see other states in mock-up)
Text: Avenir Next, Regular, 16px
Pipe separator (between icon and text): No

@natalia-fitzgerald Thanks for working on this and 👍 to all the specs you've chosen. Before reading your spec preferences, I had decided I preferred Teal 20, 30px height and no pipe separator. I was intrigued by Avenir Next Medium, but I don't think it's needed or particularly helpful. Regular weight is accessible and will help keep the design's footprint small. Great to seeing about making the touch target 45px. I think you can do that without going larger than 30px with the visual design. I agree with your comment that this should have less visual prominence than our button.
I like the idea of calling this a tag. Seems like a fitting description to me, and I like aligning with USWDS's naming conventions when possible. It doesn't feel right to me to group this with buttons.  That all makes sense and provides what I need to get started.
So if we separate this into a "Tag" component do we need to we need to think bigger picture about what these other tag-related components should be and should be called? That is out of scope for my effort - and it might be that these particular components (3 and 4 below) only appear in the context of the filterable list/post preview. But it's good to be thinking about it/discussing it while we're exploring the tag component.
My effort will address the styling of 1 and 2 below, the "Tag" component for the Multiselect component. In a separate effort we could update the post preview topic tag link to match the teal styling (so that these components seem more visually related (currently the tag/pill is Navy and the topic tag is Gold).

Category tag - Multiselect/Filter (button)
Topic tag - Multiselect/Filter (button)
Meta header - Post preview (label)
Topic tag - Post preview (link)

Blog


check input.size() > 0 before comparison

when input.size() is 0, CHECK_EQ(input.size(), time_stamp.size()); causes crash.
before comparison, make sure input.size() is not empty

You mean CHECK_EQ(0, 0) crash?

You mean CHECK_EQ(0, 0) crash?

No, I noticed input.size will be 0 and time_stamp.size will be a non-zero positive number and cause crash

Could help to figure out why the time_stamp is not zero?

Sure. I could debug further but this stopped the crash. I will see if I can pinpoint why the values are not equal

closing this, as problem seems to be resolved in latest code

Is there a conclusion to this question?
@robin1001 @eschmidbauer

Is there a conclusion to this question? I also got this crash @robin1001 @eschmidbauer

i have not been able to reproduce it in the latest code but i suspect it was related to sending "bad" data to the decoder.

Thanks for your reply.

Is there a conclusion to this question? I also got this crash @robin1001 @eschmidbauer

i have not been able to reproduce it in the latest code but i suspect it was related to sending "bad" data to the decoder.

Thanks for your reply.

@robin1001 I got this error even in the latest version of wenet. But the input data is just recording from Android device, I didn't save them and can't reproduce the error, I think it's should be caused by abnormal data.
So before comparison, I also make sure input.size() is not empty as  @eschmidbauer did.

same problem:
asr_decoder.cc:143] Check failed: input.size() == time_stamp.size() (0 vs. 9)

same problem in latest code: asr_decoder.cc:143] Check failed: input.size() == time_stamp.size() (0 vs. 9)

Have you figured it out?

same problem in latest code: asr_decoder.cc:143] Check failed: input.size() == time_stamp.size() (0 vs. 9)

Have you figured it out?

I'm working on it.

When the endpint is triggered, the next chunk we don't have enough feature  for model->forward ，
and then we have hyp vector which has empty vector , and times.size() == 0, const std::vector& time_stamp = times[0] is a undefined behavior


React to releases and discussions

As per https://docs.github.com/en/rest/reference/reactions#create-reaction-for-a-release

Release reactions:

👍
😄
🎉
❤
🚀
👀

Discussion reactions:

👍
👎
😄
🎉
😕
❤
🚀
👀

TL;DR on how to do the discussion reactions:
query {
  repository(owner:"eloquent-fixtures",name:"github-release-action-ci") {
    discussion(number:30) {
      id
    }
  }
}

mutation {
  addReaction(input:{subjectId:"D_kwDOG4Ywls4APnMy",content:HOORAY}) {
    reaction {
      content
    }
    subject {
      id
    }
  }
}


[Event Request] report 10115 "Vendor 1099 Magnetic Media" - WriteTRec event request

Hello, we are needing an event at the end of the WriteTRec procedure in this report so we can add some additional information and touch up other data from our application.  Thanks.
report 10115 "Vendor 1099 Magnetic Media"
....
    procedure WriteTRec()
    begin
        // T Record - 1 per transmission, 750 length
        IncrementSequenceNo();
....
          StrSubstNo('#1######################################', VendContactName) +
          StrSubstNo('#1#############', VendContactPhoneNo) +
          StrSubstNo('#1##################', VendorInfo."E-Mail") + // 20 chars
          StrSubstNo('                          '));

      //NEW EVENT
        OnAfterWriteTRec(IRSData, VendorInfo);
    end;

    procedure WriteARec()
    begin
        // A Record - 1 per Payer per 1099 type, 750 length
....
    // NEW EVENT DEFINITION
    [IntegrationEvent(false, false)]
    local procedure OnAfterWriteTRec(var IRSData: File; VendorInfo: Record "Company Information")
    begin
    end;

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: 11820.


Installation on Windows 7

I downloaded the Lean zip file for Windows, unfolded it in C:\. But every time I try to run  lean.exe, a DOS window appears and suddenly disappears very quickly, nothing happens. I am using Windows 7.
I also attempted to configure Lean emacs mode to see if it would work. I installed Python v.3.5.0 and emacs <IP_ADDRESS> both in C:\. I have set the command lines
> setx PATH "%PATH%;c:\Python35-32\"
> setx PATH "%PATH%;c:\emacs\bin"
as well. But I keep having the problem when I try to start the emacs mode by executing the leanemacs.bat. Sometimes I can see there's some message in the window (although it disappears so quickly I can't even see what it is saying). I wonder what is going on.

This must be related to #835. Could you try to set the environment variables via GUI?

Yeah, I was following this Win 10 issue, but couldn't reproduce the solution.
It works now -  when I went to the System Variables I realized that only the directory ;C:\Python35-32 was present at the end of the listed path. Then I manually included c:\emacs\bin and successfully started the Lean emacs mode.
Thanks!


Publisher

https://www.linkedin.com/pulse/pacx-command-line-utility-power-platform-dynamics-365-danilo-capuano-bzxlf

https://learn.microsoft.com/en-us/power-platform/alm/solution-api

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/reference/entities/publisher


:version takes about a second to display MacVim version info

I'm on MacOS 10.14.2 and Xcode 10.1 and have configured MacVim as follows:
./configure --with-features=huge --enable-rubyinterp --enable-pythoninterp --enable-python3interp --enable-perlinterp --enable-cscope --with-compiledby="Mario Grgic" --enable-terminal

When you issue :version command in the GUI , there is now a noticeable delay before the command displays the version information. Command line version prints the version info instantly.
This is a regression from versions built with macOS 10.13 SDK.

It's related to the new Mojave renderer. Will need to take a look. Probably some de-generate case with tons of text draw calls all done at once.

I notice a delay too, but it's definitely not one second.  It's much shorter (like less than .25 seconds).  I had to run it a few times in comparison to the console version to even be sure that a delay existed.  Either way, it should be fixed.
FWIW, I don't have any of the scripting languages compiled in.

It's also really bad if you run and sort of :! command that has a lot of output - for example a :!git pull that then spawns a ton of lines of text. I've had the entire app become completely unresponsive for about 10 seconds due to this.
The new renderer needs some pretty significant performance improvements I think.
Random thought - would there be any way we could copy the implementation from like iTerm2 or something? I imagine it's open source, it's pretty damn fast, could be really nice, but I imagine not a simple drop in replacement either.

As tagged in this issue, there should be some basic improvements to :version/:! by next snapshot (154), just to alleviate the situation, and I'm hoping to be able to revamp the renderer by snapshot-155.
When the new renderer was implemented it was mostly to make Mojave work again to unblock people so I didn't really have time to go and improve it, so now that it's somewhat usable that will be next.
I have looked at iTerm2 before and it's not a drop-in replacement and their Metal renderer doesn't support certain features like ligatures or transparency. My gut feeling from browsing through it is it would take more time to use it as well as re-adding features we have always supported than writing a new Metal renderer from scratch. The question is whether we want to completely accelerate the text drawing using a glyph cache (which would be faster but harder to support things like ligatures) or simply use the GPU to accelerate scrolling and compositing.

This issue should now be fixed. It's not a general fix for the renderer but will make commands that echo as fast as before now (e.g. :ls, :version, :!, :echo).


Measurement precision on Tank capacity entity

PLease mofidy the Unit of measure to 3 digit or more

com.victronenergy.tank
Tank capacity
3001
uint32
10000
0 to<PHONE_NUMBER>

Hello and thank you for opening this issue.
Both the remaining and the capacity registers have the same decoding scheme definition (as can be seen in the screenshot).

Since the remaining sensor does report values with 3 digits after the . it seems that the capacity is 0.100 and it is being shorted by ha to 0.1.
Could you confirm if the capacity is set to 0.1m3 in the gx device configuration?
In order for me to further troubleshoot this I will need to setup a test venus OS device.
However, currently I do not have a lot of time available so this will have to wait until the end of februari / beginning of march

I believe this might be fixed by changing the display precision setting in home assistant.
Since it defaults to displaying 1 number after the decimal.
Changing this to a precision of 3 numbers after the decimal should provide you with what you are looking for.


openssl fails with Tiny Core

I was trying to get Tiny Core linux working on with v86, and at first everything is fine: it boots, I can install packages. Problems show up with openssl: even with the additional installation of ca-certificates, I cannot get encrypted connections. Similarly, I cannot get ssh connections: they fail with bad certificates.
When running a standard test such as
tc@box:~$ openssl  s_client -quiet -connect www.google.com:443
I get
depth=2 OU = GlobalSign Root CA - R2, O = GlobalSign, CN = GlobalSign
verify return:1
depth=1 C = US, O = Google Trust Services, CN = GTS CA 1O1
verify error:num=7:certificate signature failure
verify return:1
depth=1 C = US, O = Google Trust Services, CN = GTS CA 1O1
verify return:1
depth=0 C = US, ST = California, L = Mountain View, O = Google LLC, CN = www.google.com
verify error:num=7:certificate signature failure
verify return:1
depth=0 C = US, ST = California, L = Mountain View, O = Google LLC, CN = www.google.com
verify return:1
3081258752:error:1417B07B:SSL routines:tls_process_cert_verify:bad signature:ssl/statem/statem_lib.c:504:
The test however succeed:

with TinyCore on VirtualBox (so it does not look like a problem uniquely related to TinyCore)
with the Arch snapshot available at https://copy.sh/v86/ (after running ./net.sh)

Would you have any idea of what to try out ?
Thank you!

This should be fixed now. Let me know if you can still reproduce.

This should be fixed now. Let me know if you can still reproduce.


deps: update grpc to 1.42.1

deps: update protobuf version to 3.19.1

ci / bazel failed:
ERROR: /github/home/.cache/bazel/_bazel_root/9e4dde399fac32001b99efa92054490b/external/io_grpc_grpc_java/alts/BUILD.bazel:82:18: in _java_grpc_library rule @io_grpc_grpc_java//alts:handshaker_java_grpc:
Traceback (most recent call last):
	File "/github/home/.cache/bazel/_bazel_root/9e4dde399fac32001b99efa92054490b/external/io_grpc_grpc_java/java_grpc_library.bzl", line 100, column 36, in _java_rpc_library_impl
		java_info = java_common.compile(
Error in compile: compile() missing 1 required named argument: host_javabase
ERROR: Analysis of target '//gax-grpc:gax_grpc_testlib' failed; build aborted: Analysis of target '@io_grpc_grpc_java//alts:handshaker_java_grpc' failed

Retrying.

GRPC 1.42.0 drops support for bazel 1-3 in this PR. The github action runner on this repo runs bazel 3.7.2, conseqently teh bazel check fails.

This error happened when the check was run in the googleapis container
Bazel: 4.0.0
ERROR: /github/home/.cache/bazel/_bazel_root/9e4dde399fac32001b99efa92054490b/external/com_google_protobuf/java/util/BUILD:7:13: no such package '@maven//': The repository '@maven' could not be resolved and referenced by '@com_google_protobuf//java/util:util'
ERROR: /github/home/.cache/bazel/_bazel_root/9e4dde399fac32001b99efa92054490b/external/com_google_protobuf/java/util/BUILD:7:13: no such package '@maven//': The repository '@maven' could not be resolved and referenced by '@com_google_protobuf//java/util:util'
ERROR: /github/home/.cache/bazel/_bazel_root/9e4dde399fac32001b99efa92054490b/external/com_google_protobuf/java/util/BUILD:7:13: no such package '@maven//': The repository '@maven' could not be resolved and referenced by '@com_google_protobuf//java/util:util'
ERROR: /github/home/.cache/bazel/_bazel_root/9e4dde399fac32001b99efa92054490b/external/com_google_protobuf/java/util/BUILD:7:13: no such package '@maven//': The repository '@maven' could not be resolved and referenced by '@com_google_protobuf//java/util:util'
ERROR: /github/home/.cache/bazel/_bazel_root/9e4dde399fac32001b99efa92054490b/external/com_google_protobuf/java/util/BUILD:7:13: no such package '@maven//': The repository '@maven' could not be resolved and referenced by '@com_google_protobuf//java/util:util'
ERROR: Analysis of target '//gax-grpc:gax_grpc_testlib' failed; build aborted: Analysis failed

This has been resolved and merged.
On Tue, Nov 30, 2021 at 9:48 AM Chanseok Oh @.***>
wrote:

@Neenu1995 https://github.com/Neenu1995 what's the status of this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googleapis/gax-java/pull/1559#issuecomment-982706326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFICH3DOPM7MCKNYTX3VO3UOTP3VANCNFSM5IE77EEA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Neenu Shaji
@.***
Developer Programs Engineer
51 Breithaupt St., Kitchener, Canada


import / export BUG

Hello, I have some BUGs that I want to submit.
When using the import and export function, the export encoding defaults to ANSI format.However, when importing, there will be garbled code.
If I open a file in ANSI format, it works fine.
When I open a file in UTF-8 format, it works fine.
But: when I imported SQL, he scrambled.
I changed the text to UTF-8 (I changed the default encoding format), and it worked.
I tried to locate BUG:
The encoding and decoding of the system are two different function modules with different key positions.When one party's code is modified, the other will not follow the update, so there will be some problems with import and export functionality.
Import and export modules and open files are similar but different modules.Developers add judgment rules to common modules, but ignore this less common feature.
Much of the uncommon BUG functionality is normal, isn't it?XD
There are no more BUGs.
Thank you!

Hi @lxkplus ,
could you provide more clear steps to reproduce? Screenshots or video can be very helpful
Thanks in advance

there is no update on the issue for a long time.
If it is still actual for you - feel free to reopen it with an additional info