"wcf element" command hangs on "Building fresh packages..."

While running wcf element creating a "lit-element", the yarn install part hangs and doesn't fail. Could be my network, but I'm dumping my terminal output in case it helps.
Running yarn install myself after killing the process seemed to work fine.
~/S/w/my-company-name » wcf element

Only one factory, "my-company-name" selected.
? Custom element base class to use lit-element -- data binding ++, very small library. 1 dependencies
? Element name foop-doop
? Description / purpose of the element doop doop
? Do you want to use Sass in this element? No
? Do you want custom properties? (typically yes) Yes
? Auto build support for the HAX authoring system? No
? Add a new property? (Y/n) Y
? Add a new property? Yes
? Name (eg: title) first
? Name (eg: title) first
? type of value (the way it is used as data) (Use arrow keys)
? type of value (the way it is used as data) String, text based input
? Default value (leave blank for none)
? Default value (leave blank for none)
? Make available in css styles? [name="stuff"] { color: blue; } (y/N) y
? Make available in css styles? [name="stuff"] { color: blue; } Yes
? Notice changes to this property? (Y/n) Y
? Notice changes to this property? Yes
? Add a new property? (Y/n) n
? Add a new property? No
   create foop-doop/package.json
   create foop-doop/index.html
   create foop-doop/LICENSE.md
   create foop-doop/src/foop-doop-properties.json
   create foop-doop/src/foop-doop-hax.json
   create foop-doop/README.md
   create foop-doop/gulpfile.js
   create foop-doop/rollup.config.js
   create foop-doop/demo/index.html
   create foop-doop/test/foop-doop_test.html
   create foop-doop/test/index.html
   create foop-doop/foop-doop.story.js
   create foop-doop/.DS_Store
   create foop-doop/.editorconfig
   create foop-doop/.gitignore
   create foop-doop/.npmignore
   create foop-doop/.surgeignore
   create foop-doop/.travis.yml
   create foop-doop/polymer.json
   create foop-doop/src/foop-doop.css
   create foop-doop/src/foop-doop.html
   create foop-doop/src/foop-doop.js

I'm all done. Running yarn install for you to install the required dependencies. If this fails, try running the command yourself.

yarn install v1.12.3
info No lockfile found.
$ bash scripts/preinstall.sh
[1/4] 🔍  Resolving packages...
warning @storybook/cli > jscodeshift ><EMAIL_ADDRESS>🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
warning @storybook/cli > jscodeshift ><EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
warning gulp-concat-util ><EMAIL_ADDRESS>gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
warning jest > jest-cli > prompts ><EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <https://github.com/lukeed/kleur/releases/tag/v3.0.0\> for migration path(s).
warning polymer-build > polymer-project-config > plylog ><EMAIL_ADDRESS>This is a stub types definition. winston provides its own type definitions, so you do not need this installed.
warning wct-browser-legacy > sinon ><EMAIL_ADDRESS>This package is unmaintained. Use @sinonjs/formatio instead
warning wct-browser-legacy > sinon ><EMAIL_ADDRESS>This package has been deprecated in favour of @sinonjs/samsam
warning wct-browser-legacy > sinon > formatio ><EMAIL_ADDRESS>This package has been deprecated in favour of @sinonjs/samsam
warning web-component-tester ><EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
warning web-component-tester > sinon ><EMAIL_ADDRESS>This package is unmaintained. Use @sinonjs/formatio instead
warning web-component-tester > sinon ><EMAIL_ADDRESS>This package has been deprecated in favour of @sinonjs/samsam
warning web-component-tester > sinon > formatio ><EMAIL_ADDRESS>This package has been deprecated in favour of @sinonjs/samsam
warning web-component-tester > sinon ><EMAIL_ADDRESS>no longer maintained
warning yo > fullname > passwd-user > execa ><EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead
warning yo > yeoman-doctor > bin-version-check > bin-version > execa ><EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead
warning workspace-aggregator-a3861a20-0ef6-476f-9887-83f49746dd6f > @my-company-name/foop-doop > polymer-cli ><EMAIL_ADDRESS>We don't recommend using Bower for new projects. Please consider Yarn and Webpack or Parcel. You can read how to migrate legacy project here: https://bower.io/blog/2017/how-to-migrate-away-from-bower/
warning workspace-aggregator-a3861a20-0ef6-476f-9887-83f49746dd6f > @my-company-name/foop-doop > polymer-cli ><EMAIL_ADDRESS>'github' has been renamed to '@octokit/rest' (https://git.io/vNB11)
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "@storybook/addon-a11y > @emotion/styled ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] 📃  Building fresh packages...
[10/13] ⠐ wct-local
[-/13] ⠐ waiting...
[-/13] ⠈ waiting...
[-/13] ⠈ waiting...
[5/13] ⠈ phantomjs-prebuilt

My guess is network hiccup. I've experienced this in general w. Large Yar. Builds especially on the first few times making something til it gets the lock file built

Yep, I tried creating another element with the same choices and there was no network hangup.


Remove fuzzy from dependencies

fuzzy is still a dependency in package.json even though we now use fuzzaldrin. The dependency must be removed.

@ovidiubute Ok!


Retry + backoff on GCS timeouts

Add GCS timeouts to the collection of exceptions that will be retried

How is ClientRequestException connected to RETRIABLE_EXCEPTIONS?

It is different. The ClientRequestException is a special handling of 400 responses (basically when a URL has expired). We can't do request retries on that one (since the URL is expired), so we have to handle it on the batch-level by re-trying the entire two-step process (get the URL + call the URL). This handles the special case of downloading a binary from a URL that has time expiration.
RETRIABLE_EXCEPTIONS will lead to requests being retried as is. This is the default retry + backoff mechanism.


samples per second output

When done, post the samples per second for the basecalling
Start the timer in the buttery-eel.py part before basecalling
grab the signal_len values and add them to a running tally for each client
push the values somewhere to be added together
end once it comes out
calculate samples per second taking the time and total samples
or something like that. Might help with getting an idea on speed between models as well as comparing to existing ONT samples/s outputs

Hi,
Thank you for your good job!Can you tell me how to start the timer in the buttery-eel.py part  .

Hey,
This is an issue to track a new feature that I have yet to implement. Once it's implemented, tested, and pushed into new release, it will be on by default.
James


How to use the conjugate function with variables

Hello,
i'm trying to use the conjugate function in spanish, i have an array with the adverb time so i want to do this.
palabras = [[]]
palabras[0].append("Ayer")
palabras[0].append("PAST")
palabras.append([])
palabras[1].append("Yo")
palabras[1].append("SG")

print conjugate('correr', palabras[0][1], 1, SG )

When i run the code i just get None, when i replace palabras[][] with PAST it works and shows "corría". I think it can be for the String data type, when i use print conjugate('correr',"PAST", 1, SG ) it also does not work, How can i make this work?
Hope you can help me!!!
Have a good day.

you need to pass the constants SG and PAST themselves (from the
pattern.es module), not string.
from pattern.es import SG, PAST, conjugate
print conjugate("correr", PAST, 1, SG).encode("utf-8") works with
pattern 2.6 and python 2.7.11
2016-05-24 19:57 GMT+02:00, elgamersitom<EMAIL_ADDRESS>
Hello,
i'm trying to use the conjugate function in spanish, i have an array with
the adverb time so i want to do this.
palabras = [[]]
palabras[0].append("Ayer")
palabras[0].append("PAST")
palabras.append([])
palabras[1].append("Yo")
palabras[1].append("SG")

print conjugate('correr', palabras[0][1], 1, SG )

When i run the code i just get None, when i replace palabras[][] with PAST
it works and shows "corría". I think it can be for the String data type,
when i use print conjugate('correr',"PAST", 1, SG ) it also does not work,
How can i make this work?
Hope you can help me!!!
Have a good day.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/clips/pattern/issues/148

--
Enrique Manjavacas.

Thanks,
I supposed it was a simple solution, it works pretty well.
2016-05-24 14:50 GMT-05:00 Enrique Manjavacas<EMAIL_ADDRESS>
you need to pass the constants SG and PAST themselves (from the
pattern.es module), not string.
from pattern.es import SG, PAST, conjugate
print conjugate("correr", PAST, 1, SG).encode("utf-8") works with
pattern 2.6 and python 2.7.11
2016-05-24 19:57 GMT+02:00, elgamersitom<EMAIL_ADDRESS>
Hello,
i'm trying to use the conjugate function in spanish, i have an array with
the adverb time so i want to do this.
palabras = [[]]
palabras[0].append("Ayer")
palabras[0].append("PAST")
palabras.append([])
palabras[1].append("Yo")
palabras[1].append("SG")

print conjugate('correr', palabras[0][1], 1, SG )

When i run the code i just get None, when i replace palabras[][] with
PAST
it works and shows "corría". I think it can be for the String data type,
when i use print conjugate('correr',"PAST", 1, SG ) it also does not
work,
How can i make this work?
Hope you can help me!!!
Have a good day.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/clips/pattern/issues/148

--
Enrique Manjavacas.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/clips/pattern/issues/148#issuecomment-221375334

--
Cristian Narváez.
Ingeniero en Multimedia.
Miembro grupo de investigación ACCEDER http://www.accederresearch.org/.
Universidad Militar Nueva Granada.
Bogotá-Colombia


rust starting path name demangling

E.g.:
echo '_ZN33_$LT$alloc..arc..Arc$LT$T$GT$$GT$9drop_slow17h9ed4cba808ccbc62E' | c++filt
<alloc::arc::Arc<T>>::drop_slow

echo '_ZN33_$LT$alloc..arc..Arc$LT$T$GT$$GT$9drop_slow17h9ed4cba808ccbc62E' | cppfilt
_$LT$alloc..arc..Arc$LT$T$GT$$GT$::drop_slow::h9ed4cba808ccbc62

Strangely, c++filt agrees with cppfilt on OSX :thinking: but has output as above on linux...

Strangely, c++filt agrees with cppfilt on OSX 🤔 but has output as above on linux...

Maybe different versions?  Extra demangling for Rust was added here: https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=242524 - a year ago now, I guess.

Thanks for filing an issue, @m4b.
However, I don't intend to support demangling Rust symbols in this crate. There's already https://crates.io/crates/rustc-demangle for that, and it should be easy enough to make a wrapper crate that is the union of these two crates if one needed.


Issue Encountered while Running PoPS

First and foremost, I would like to express my gratitude for developing FLAMES for GWAS gene prioritization. As I attempted to execute FLAMES with my dataset, I encountered a hurdle during the analysis step "3. Run PoPS on the generated MAGMA z-scores." Specifically, I faced the following error message: "raise KeyError(f"{not_found} not in index") KeyError: "['ENSG00000269831', 'ENSG00000269308', 'ENSG00000268179', ..., 'ENSG00000185973'] not in index".
Upon investigation, I realized that while my magma.genes.out file contains 19858 rows, the accompanying gene_annot.txt file only encompasses 18383 rows. Consequently, over a thousand ‘ENSGxxx’ entries cannot find a match, impeding the analysis process.
Given this discrepancy, I am reaching out to seek your guidance on resolving this issue. Do you have any recommendations or solutions to enable the successful execution of the analysis?
Your assistance in this matter would be greatly appreciated.

Hi Marijn,
Thank you for your swift response! It's clear now why my analysis was hitting roadblocks. I followed your suggestions today, but I had another questions.
Regarding the first option, how can I obtain a gene annotation file that matches my 19858 MAGMA genes?
As for the second option, I'm a bit unclear on how to proceed with running MAGMA by annotating the SNPs to the file (gene_annot_jun10.txt). Even after removing over 1000+ genes that couldn't be matched in the gene_annot.txt file, leaving me with 18k genes for analysis, the process still couldn't proceed.
Your insight and help are truly appreciated!
Best regards,
Zekai

Hi Zekai,
Option 1:
The PoPS github specifies that for munging the features you need a gene annot file with the following requirements "Path to gene annotation table. For the purposes of this script, only require that there is an ENSGID column". I guess you can use the MAGMA.genes.out file for this.
Option 2:
I have looked into removing output from a MAGMA genes.out as well , but PoPS also parses the genes.out.raw, which is a corresponding table and will throw errors saying that the two tables do not match. If you want to use my munged features then you would have to run MAGMA manually. Step1 when running MAGMA from scratch on your summary statistics is create a snp annotation file. For this you need your GWAS file and a gene location file. If you use the gene_annot_jun10.txt as the gene location file your MAGMA-Z scores will be compatible with the munged features I have provided.
Let me know if you get stuck on the execution of either of the two options.
Best,
Marijn

Hi Marijn,
Thank you for your further clarification. I tried Option 1 by downloading the raw PoPS features (i.e., PoPS.features.txt.gz) from the provided link and using the MAGMA.genes.out file for munging the features. However, I only obtained the results in pops_features.rows.txt format, which is insufficient to support subsequent analyses.
Regarding Option 2, I haven't attempted it yet. Using gene_annot_jun10.txt as the gene location file might result in the loss of information for over 1000 genes, potentially impacting the results.
As neither of the options seems to resolve the issue, I'm still unable to run FLAMES successfully. If you make any optimizations or adjustments to the documentation in the future to streamline the analysis process, it would be greatly appreciated.
Best regards,
Zekai

Dear Zekai,
Doing option two will indeed potentially impact the result as the likelihood of the missing genes being predicted will be lower. For option 1 I would refer you to the PoPS Github, where they document running PoPS for your own MAGMA output.

Dear Zekai,
I have now uploaded a new version of PoPS features that is compatible with FUMA MAGMA Z-scores, and protein coding ENSEMBL genes v102/v110.
This should resolve the problem.
Please reopen a ticket if you encounter new errors.
Best,
Marijn


Add support for the binary scanner checking the validity of the target versions for ee and mp

Support exceptions to be added to the binary scanner in a future version.

Fixes https://github.com/OpenLiberty/ci.maven/issues/1558


Prep beta.2 release

What does this PR do?

Prepare the beta.2 release
Review checklist
Please check relevant items below:

[ ] This PR includes all newly recorded cassettes for any modified tests.

[ ] This PR does not rely on API client schema changes.

[ ] The CI should be fully passing.

[ ] Or, this PR relies on API schema changes and this is a Draft PR to include tests for that new functionality.

Note: CI shouldn't be run on this Draft PR, as its expected to fail without the corresponding schema changes.

/azp run

/azp run

/azp run


appearance transfer

amazing work, when do you repo the new code of appearance transfer?

Hi @github-aaliu, we have updated the iPERCore with 0.2.0 which contains the scripts of appearance transfer.


Issue with snt.BatchApply in newer versions of TensorFlow

I'm having an issue with a recent version of TensorFlow and the latest version
of sonnet. Specifically, I am building TensorFlow from source
(commit ref 318e071f7cb9fd51ddf0dda1e285e140167b4b56 compiled with cuda 9.0 and
cudnn 7.0.3), and I am also building Sonnet from source
(commit ref 7da90b8e63fb684b91a12e1e9a42999962804e3a, again with gpu options.
I have removed the dependency on tensorflow-gpu in order to not overwrite the
newer version of TensorFlow in the environment).
Specifically, there seems to be an issue with BatchApply. When running with
TensorFlow 1.4 (which I compile under the same circumstances as the above
version I mention), the following code behaves as expected:
>>> import sonnet as snt
... import tensorflow as tf
...
... input = tf.placeholder(tf.float32, (None, 3, 5))
...
... linear = snt.Linear(output_size=7)
... linear_batch = snt.BatchApply(linear)
...
... output = linear_batch(input)
...
>>> output
<tf.Tensor 'batch_apply/Reshape_1:0' shape=(?, 3, 7) dtype=float32>

When using the new version, I find the following behaviour:
>>> import sonnet as snt
... import tensorflow as tf
...
... input = tf.placeholder(tf.float32, (None, 3, 5))
...
... linear = snt.Linear(output_size=7)
... linear_batch = snt.BatchApply(linear)
...
... output = linear_batch(input)
...
Traceback (most recent call last):
  File "<input>", line 9, in <module>
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/sonnet/python/modules/base.py", line 275, in __call__
    outputs, this_name_scope = self._template(*args, **kwargs)
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/tensorflow/python/ops/template.py", line 268, in __call__
    result = self._call_func(args, kwargs, check_for_new_variables=False)
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/tensorflow/python/ops/template.py", line 217, in _call_func
    result = self._func(*args, **kwargs)
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/sonnet/python/modules/base.py", line 202, in _build_wrapper
    output = self._build(*args, **kwargs)
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/sonnet/python/modules/basic.py", line 974, in _build
    flattened = nest.flatten_iterable([args, kwargs])
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/sonnet/python/ops/nest.py", line 153, in flatten_iterable
    return list(_yield_flat_nest_from_iterable(structure))
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/sonnet/python/ops/nest.py", line 103, in _yield_flat_nest_from_iterable
    for ni in _yield_flat_nest_from_iterable(n):
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/sonnet/python/ops/nest.py", line 103, in _yield_flat_nest_from_iterable
    for ni in _yield_flat_nest_from_iterable(n):
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/sonnet/python/ops/nest.py", line 101, in _yield_flat_nest_from_iterable
    for n in _yield_value_from_iterable(iterable):
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/sonnet/python/ops/nest.py", line 96, in _yield_value_from_iterable
    for value in iterable:
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 377, in __iter__
    "`Tensor` objects are not iterable when eager execution is not "
TypeError: `Tensor` objects are not iterable when eager execution is not enabled. To iterate over this tensor use `tf.map_fn`.

originally defined at:
  File "<input>", line 7, in <module>
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/sonnet/python/modules/basic.py", line 949, in __init__
    super(BatchApply, self).__init__(name=name)
  File "/home/dan/anaconda3/envs/env_crypto_master/lib/python3.6/site-packages/sonnet/python/modules/base.py", line 174, in __init__
    custom_getter_=self._custom_getter)

So the introduction of eager execution seems to have altered some of the default
behaviours that snt.BatchApply depends on. I know it's stated that sonnet is
only advertised as being compatible with TensorFlow 1.3, so I know this may
be strictly out of scope, however, I thought it would be useful to raise the
issue anyway to prepare for changes coming in TensorFlow  1.5.
Many thanks in advance!

@dbusbridge Hi, thanks for the report. This is due to a recent change in whether Tensors are iterable or not, which isn't reflected in our current nest library. As you say, Sonnet is supported against one specific version of TF, and that won't necessarily be in sync with GitHub HEAD, or in this case the current stable version which arrived last week.
This is fixed internally and we should be pushing a new Sonnet version this week, I'll close this ticket once we've done that.

Cool - thanks @malcolmreynolds!

@dbusbridge If you reinstall Sonnet from either GitHub head, or pip, you should have a version that works with TF 1.4.0. Please let me know whether this is fixed for you!

@malcolmreynolds That fixed it - thanks!


Is it possible to change toolbar title text in Ucrop activity

Hi!
Thank you for awesome library.
I want to change toolbar title in ucrop activity(need use russian lang).
Is it possible?

This help me find string keys to change text -
https://github.com/Dhaval2404/ImagePicker/pull/117


HBASE-27371 Bump spotbugs version

Let's give it a try.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4783/1/console in case of problems.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4783/1/console in case of problems.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
0m  8s
Docker failed to build yetus/hbase:92fe6090c2.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/4783

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4783/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
0m  8s
Docker failed to build yetus/hbase:92fe6090c2.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/4783

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4783/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
docker
0m  8s
Docker failed to build yetus/hbase:92fe6090c2.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/4783

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4783/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4783/2/console in case of problems.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4783/2/console in case of problems.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4783/2/console in case of problems.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 41s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
shelldocs
0m  1s
Shelldocs was not available.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 26s
master passed

+1 :green_heart:
compile
5m 56s
master passed

+1 :green_heart:
spotless
0m 38s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m  2s
the patch passed

+1 :green_heart:
compile
5m 53s
the patch passed

+1 :green_heart:
javac
5m 53s
the patch passed

+1 :green_heart:
hadolint
0m  1s
There were no new hadolint issues.

+1 :green_heart:
shellcheck
0m  0s
There were no new shellcheck issues.

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
hadoopcheck
7m 57s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 36s
patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 10s
The patch does not generate ASF License warnings.

32m 30s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4783/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4783

Optional Tests
dupname asflicense spotless hadolint shellcheck shelldocs javac hadoopcheck xml compile

uname
Linux 537ffd96556c 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b3a04899a4

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
138 (vs. ulimit of 30000)

modules
C: . U: .

 U: .

 U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4783/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Are these samples outdated?

Hi there.
sorry for my English. I try the undersatnd the Microsoft Bot Builder and the Dialogs methods.
In the samples the Microsoft Bot Builder <IP_ADDRESS> is used.
In the namespace Microsoft.Bot.Builder.Dialogs there is a class called PromptStyler
The void method "Apply"  uses IList option.
In the new assembly <IP_ADDRESS>  there is IReadOnlyList options.
When I updated the solution I can't build the Bot.   Why is there a change from IList to IReadOnlyList?
And how can I fix the issue?
-->Sample I used: SearchPowerBots  > Project "Search.Dialogs"
Many thanks
Arash

They are, but they are being updated. PR #50 takes care of updating the C# samples. That being said, the issue you are having is pretty straightforward to fix; just update the references to be IReadOnlyList. At some point BotBuilder introduced that breaking change.

Thanks. I give it a try tomorrow.
Regards
Arash
On Thu, Jan 12, 2017 at 9:14 PM +0100, "Ezequiel Jadib"<EMAIL_ADDRESS>wrote:
They are, but they are being updated. PR #50 takes care of updating the C# samples. That being said, the issue you are having is pretty straightforward to fix; just update the references to be IReadOnlyList. At some point BotBuilder introduced that breaking change.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I had to do some messing around also with the 'SettingsScorable' IScorable implementation in the ContosoFlowers sample to get it to work with the latest IScorable also. Guess I should be looking more closely at the pull requests!

The PR with the updated C# samples was already merged!

Nice one, thanks E, I must have last pulled just before the merge.

DirectLine Sample has outdated code as well. It could be great if you fix it :)

The DirectLine sample was also updated to use DirectLine V3. What part is outdated?


Support enums with xrn values

This change allows for enums to have : characters in the values, and still generate language-safe names for each enum.

:tada: This PR is included in version 1.4.1-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.6.2-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


MSID: 101760 Version: 1 DOI: 10.1101/2<IP_ADDRESS>7555

MSID: 101760
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>7555
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=101760
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>7555

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/101760v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>7555
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/101760/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

@acollings There's no evidence term for this assessment. Is that OK?

WoS question asked.

Thanks @JGilbert-eLife I've edited this


40branch - don't merge yet

Do not merge yet:
It is working but the identity manager still looks messed up.
Also need to re-organize to have a 3.x and a 4.x sample and library

reorganized to include 3.x and 4.x examples

@nixta How do you want to update the doc for this? Should there be separate doc for 4.x and 3.x or a combined doc?
The only real difference between the two is 4.x uses "esri/identity/IdentityManager", while 3.x uses "esri/IdentityManager"

Hey @zxwandrew - great stuff. Thanks for doing this.
Let's clean up some structure.
I think it would be better to have a single top-level lib folder. How does something like this strike you?
lib
  dojo
    3
    4

And how does naming the 4.0 example index.html and the 3.16 example index_jsapi3.html sound to you?
WRT the docs: maybe we modify the README.md to work with the 4.0 API by default and a separate section for setting up for the 3.x API.

Hey @zxwandrew. I took your changes (thank you!) and after conferring a little with @alaframboise about the naming, ended up with what's in the gh-pages branch now. Thanks for all the help! Let me know if you see any issues.
The one thing that still needs to be resolved is the IdentityManager styling in 4.0. It seems to be broken by default and needs some work (bug fix?), but for now this will do.


Ban keywords from crate names

Dearest Reviewer,
This pull request extends the banned list of project names to include
all of the current keywords for rust. I got the list of keywords from
https://doc.rust-lang.org/grammar.html#keywords . This
closes #2699 . The original ticket said warn but I figured how test is
handled is most likely how all banned names should be handled.
Oddly enough a few keywords have made their way to the crates.io. fn and
proc are both examples I found spot checking keywords. I do not there is
any action to take on those crates.
Thanks
Becker

r? @wycats
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks! Could you add a comment with a link to that page as well? Other than that r=me

Updated. Thanks!

@bors: r+ 466c74a996458c288aa526cb1514319a7f7b86fd

:hourglass: Testing commit 466c74a with merge 42bce5c...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


Rename groups in command palette from Remote Repositories to Git

@jrieken had interesting feedback that he does not use vscode.dev with Remote Repos as much as he should because he searches for Pull and sees Remote Repositories: Pull instead of Git: Pull, and it feels unfamiliar compared to desktop. To make things more familiar to users I wonder if we should change the command group name to also be Git? The hypothesis is that making such a change would encourage more users to use git commands via the command palette.
cc @lszomoru for feedback

One potential issue with using "Git" would be that users might assume that all the git functionality that is available on desktop is now available in the web, while at the moment we only support GiHub and Azure Repos on the web. Ideally we would want to use either GitHub: ... or Azure Repos: ... for the commands through I am not sure that is feasible since the commands are defined in the Remote Repositories extension.

One potential issue with using "Git" would be that users might assume that all the git functionality that is available on desktop is now available in the web

My brain is weird and I simply press F1, type "pull" and when I don't see "Git: Pull" atop I am confusing and give up. I share your concern about giving a false impression but AFAIK can tell git-pull does the same on web and desktop so could make this a case by case thing. Alternatively we could call it "Git: Pull from Remote Repository". I guess my takeaway is that the category-label, like "Git:", shouldn't name extensions but features

We haven't heard similar feedback in a year so I'm not persuaded to change this for everyone. With the semantic similarity work though, maybe we can get Remote Repos to match Git in command palette search results? @TylerLeonhardt do you think that would make sense?


TNO-1148: Build My Minister view and functionality

tno-core update to 0.0.251
db-migration v1.0.19
Includes:

New My Minister section that allows a user to choose which minister they would like to "follow" (just one for now)
Clicking the My Minister option will be a quick link to a filtered list of contents for said minister
Moved several controllers to their own subscriber sections
New column added to user table called preferences that contains a json object of preferences

Known bug (sidebar):

on click only working when clicking on the label after allowing for more than one clickable area - ticket will be created

@jdtoombs You'll have to update your DB migration again.  Cello submitted another one and it's merged.


Moment is not a dev dependency

Hi there,
I couldn't run the plugin and realised that it was because it required moment as a devDependency!
Cheers,
Jun

Just ran into this myself on first attempt to use it.


install a newer gcc

should fix the build
r? @rust-embedded/resources
cc @andre-richter

@andre-richter bors only reads normal comments; it doesn't read review comments so you always need an extra comment. (Annoying, I know)
bors r=andre-richter

Oh wait, it worked with the review comment. Maybe they fixed it.


Drop Ruby 2.6 runtime support

This PR drops Ruby 2.6 runtime support. The next release will be the time to drop Ruby 2.6 support:
https://www.ruby-lang.org/en/downloads/branches/
https://docs.rubocop.org/rubocop/compatibility.html#support-matrix
Follow up: https://github.com/rubocop/rubocop/pull/11791

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with main (if not - rebase it).
[x] Squashed related commits together.
[-] Added tests.
[-] Updated documentation.
[x] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

@bquorning Could you removed the Ruby 2.6 part of our main branch protection?

Thank you✨


Acceptance tests at Gradle level run before release against real Nexus

To verify that at least happy path is working.

Implemented with https://gitlab.com/nexus-at/nexus-at-minimal and specific Nexus configuration.


Git - Git Blame - Reduce opacity

I've tried to replace GitLens by the new feature from the Git extension.
It does the job pretty well, however I'd like make the message less invasive.
The font opacity and color are too much standing out imho .

Did you try customising the git.blame.editorDecorationForeground theme color mentioned in the release notes?

Oh thanks! I missed that, adding the following in my settings.json did the job.
  "workbench.colorCustomizations": {
    "git.blame.editorDecorationForeground": "#43454e"
  },


Fix formatting, rename Destination.swift

In accepted SE-0387 "destinations" were renamed to "Swift SDKs". Based on that it feels more suitable to rename Destination.swift to SwiftSDKMetadata.swift. Also taking this as an opportunity to apply formatting cleanups and to update Utilities/soundness.sh to exclude the generated ./Bundles directory from scanning.

@swift-ci test


Benchmark report

Hello tcmalloc!
I am KanameShiki.
Same memory allocator as you.
I hope that various ideas will merge to create a better memory allocator.
I believe it will benefit all people who use computers.

Hello to you too. Can you elaborate what exactly are you proposing ?


Expose three ROMol methods which were not previously exposed to SWIG wrappers

@greglandrum As you may remember, this is something that we noticed while updating the KNIME depiction nodes. We worked around the missing methods in the current KNIME nodes by creating an RWMol copy of the ROMol, which is suboptimal for performance reasons.
This PR obviates the problem.

@ptosco @greglandrum along these lines I was thinking of making something like:
  RWMol & ROMol::AsRWMol();

for advanced usage in the wrappers so we could avoid copies in some cases.

@ptosco @greglandrum along these lines I was thinking of making something like:
  RWMol & ROMol::AsRWMol();

for advanced usage in the wrappers so we could avoid copies in some cases.

If this is just going to be doing something like calling dynamic_cast on the molecule itself and returning the result, I don't like the idea at all.
We could do a method which moves the ROMol into the RWMol, but a simple cast seems like asking for trouble.


Add support for ECS utilization metrics and dashboard

Description
Allow monitoring of ECS (incl. Fargate) cluster/service memory and CPU utilisation
Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING.md document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Coverage remained the same at 96.591% when pulling fc68fd51662aa5f0a6048dbefd425a9c4f82a929 on ecs-metrics into 330037daf205ca367378ccb2a22ab228dd402ce2 on main.


PHOENIX-6397 Implement TableMetricsManager class and its associated functions for select. upsert and Delete Queries

PHOENIX-6397 Implement TableMetricsManager class and its associated functions for select. upsert and Delete Queries

@yanxinyi

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m 18s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

+1 :green_heart:
mvninstall
16m 14s
master passed

+0
hbaserecompile
23m  5s
HBase recompiled.

+1 :green_heart:
compile
1m  4s
master passed

+1 :green_heart:
checkstyle
3m  6s
master passed

+1 :green_heart:
javadoc
0m 53s
master passed

+0 :ok:
spotbugs
3m  5s
phoenix-core in master has 959 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
8m  6s
the patch passed

+0
hbaserecompile
17m 45s
HBase recompiled.

+1 :green_heart:
compile
1m  2s
the patch passed

+1 :green_heart:
javac
1m  2s
the patch passed

-1 :x:
checkstyle
3m 27s
phoenix-core: The patch generated 690 new + 6087 unchanged - 74 fixed = 6777 total (was 6161)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 50s
the patch passed

-1 :x:
spotbugs
3m 18s
phoenix-core generated 6 new + 959 unchanged - 0 fixed = 965 total (was 959)

_ Other Tests _

-1 :x:
unit
111m 38s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 45s
The patch does not generate ASF License warnings.

174m 34s

Reason
Tests

FindBugs
module:phoenix-core

org.apache.phoenix.monitoring.NoOpTableMetricsManager.noOpsTableMetricManager isn't final but should be  At NoOpTableMetricsManager.java:be  At NoOpTableMetricsManager.java:[line 25]

Load of known null value in org.apache.phoenix.monitoring.TableMetricsManager.getInstance()  At TableMetricsManager.java:in org.apache.phoenix.monitoring.TableMetricsManager.getInstance()  At TableMetricsManager.java:[line 87]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.options from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 56]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.isMetricPublisherEnabled from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 68]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.isTableLevelMetricsEnabled from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 57]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.tableClientMetricsMapping from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 60]

Failed junit tests
phoenix.end2end.PermissionNSEnabledWithCustomAccessControllerIT

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1224

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaserebuild hbaseanti checkstyle

uname
Linux 8bc81b8daec8 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / 5265164

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/1/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/1/artifact/yetus-general-check/output/new-spotbugs-phoenix-core.html

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/1/testReport/

Max. process+thread count
14526 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 29s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

+1 :green_heart:
mvninstall
15m 41s
master passed

+0
hbaserecompile
22m 31s
HBase recompiled.

+1 :green_heart:
compile
1m  1s
master passed

+1 :green_heart:
checkstyle
3m  6s
master passed

+1 :green_heart:
javadoc
0m 52s
master passed

+0 :ok:
spotbugs
3m  7s
phoenix-core in master has 959 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
8m 13s
the patch passed

+0
hbaserecompile
18m 14s
HBase recompiled.

+1 :green_heart:
compile
1m  2s
the patch passed

+1 :green_heart:
javac
1m  2s
the patch passed

-1 :x:
checkstyle
3m 29s
phoenix-core: The patch generated 723 new + 6054 unchanged - 107 fixed = 6777 total (was 6161)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 49s
the patch passed

-1 :x:
spotbugs
3m 12s
phoenix-core generated 6 new + 959 unchanged - 0 fixed = 965 total (was 959)

_ Other Tests _

-1 :x:
unit
113m  6s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 46s
The patch does not generate ASF License warnings.

171m 58s

Reason
Tests

FindBugs
module:phoenix-core

org.apache.phoenix.monitoring.NoOpTableMetricsManager.noOpsTableMetricManager isn't final but should be  At NoOpTableMetricsManager.java:be  At NoOpTableMetricsManager.java:[line 25]

Load of known null value in org.apache.phoenix.monitoring.TableMetricsManager.getInstance()  At TableMetricsManager.java:in org.apache.phoenix.monitoring.TableMetricsManager.getInstance()  At TableMetricsManager.java:[line 87]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.options from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 56]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.isMetricPublisherEnabled from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 68]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.isTableLevelMetricsEnabled from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 57]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.tableClientMetricsMapping from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 60]

Failed junit tests
phoenix.end2end.PermissionNSEnabledWithCustomAccessControllerIT

phoenix.end2end.AuditLoggingIT

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1224

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaserebuild hbaseanti checkstyle

uname
Linux 6e26c388b449 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / 5265164

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/2/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/2/artifact/yetus-general-check/output/new-spotbugs-phoenix-core.html

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/2/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/2/testReport/

Max. process+thread count
13827 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/2/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 30s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

+1 :green_heart:
mvninstall
16m 46s
master passed

+0
hbaserecompile
23m  9s
HBase recompiled.

+1 :green_heart:
compile
1m  2s
master passed

+1 :green_heart:
checkstyle
3m  6s
master passed

+1 :green_heart:
javadoc
0m 50s
master passed

+0 :ok:
spotbugs
3m  5s
phoenix-core in master has 959 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
8m  6s
the patch passed

+0
hbaserecompile
17m 31s
HBase recompiled.

+1 :green_heart:
compile
1m  4s
the patch passed

+1 :green_heart:
javac
1m  4s
the patch passed

-1 :x:
checkstyle
3m 19s
phoenix-core: The patch generated 694 new + 6087 unchanged - 74 fixed = 6781 total (was 6161)

+1 :green_heart:
whitespace
0m  1s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 52s
the patch passed

-1 :x:
spotbugs
3m 18s
phoenix-core generated 5 new + 959 unchanged - 0 fixed = 964 total (was 959)

_ Other Tests _

-1 :x:
unit
114m 14s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 49s
The patch does not generate ASF License warnings.

173m 38s

Reason
Tests

FindBugs
module:phoenix-core

Load of known null value in org.apache.phoenix.monitoring.TableMetricsManager.getInstance()  At TableMetricsManager.java:in org.apache.phoenix.monitoring.TableMetricsManager.getInstance()  At TableMetricsManager.java:[line 88]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.options from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 57]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.isMetricPublisherEnabled from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 69]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.isTableLevelMetricsEnabled from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 58]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.tableClientMetricsMapping from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 61]

Failed junit tests
phoenix.end2end.BackwardCompatibilityIT

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/9/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1224

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaserebuild hbaseanti checkstyle

uname
Linux b03a595dfbf2 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / 6c22b43

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/9/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/9/artifact/yetus-general-check/output/new-spotbugs-phoenix-core.html

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/9/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/9/testReport/

Max. process+thread count
14460 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/9/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

+1 :green_heart:
mvninstall
17m  8s
master passed

+0
hbaserecompile
24m 17s
HBase recompiled.

+1 :green_heart:
compile
1m  4s
master passed

+1 :green_heart:
checkstyle
2m 42s
master passed

+1 :green_heart:
javadoc
0m 50s
master passed

+0 :ok:
spotbugs
3m  9s
phoenix-core in master has 959 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
8m 11s
the patch passed

+0
hbaserecompile
18m 48s
HBase recompiled.

+1 :green_heart:
compile
1m  7s
the patch passed

+1 :green_heart:
javac
1m  7s
the patch passed

-1 :x:
checkstyle
2m 55s
phoenix-core: The patch generated 694 new + 6087 unchanged - 74 fixed = 6781 total (was 6161)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 57s
the patch passed

-1 :x:
spotbugs
3m 39s
phoenix-core generated 5 new + 959 unchanged - 0 fixed = 964 total (was 959)

_ Other Tests _

-1 :x:
unit
113m 26s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 45s
The patch does not generate ASF License warnings.

174m 34s

Reason
Tests

FindBugs
module:phoenix-core

Load of known null value in org.apache.phoenix.monitoring.TableMetricsManager.getInstance()  At TableMetricsManager.java:in org.apache.phoenix.monitoring.TableMetricsManager.getInstance()  At TableMetricsManager.java:[line 88]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.options from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 57]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.isMetricPublisherEnabled from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 69]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.isTableLevelMetricsEnabled from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 58]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.tableClientMetricsMapping from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 61]

Failed junit tests
phoenix.end2end.PermissionNSEnabledWithCustomAccessControllerIT

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/10/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1224

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaserebuild hbaseanti checkstyle

uname
Linux 4f3a0c5839f8 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / 6c22b43

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/10/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/10/artifact/yetus-general-check/output/new-spotbugs-phoenix-core.html

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/10/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/10/testReport/

Max. process+thread count
15826 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/10/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 3 new or modified test files.

_ master Compile Tests _

+1 :green_heart:
mvninstall
16m  8s
master passed

+0
hbaserecompile
22m 53s
HBase recompiled.

+1 :green_heart:
compile
1m  4s
master passed

+1 :green_heart:
checkstyle
3m  6s
master passed

+1 :green_heart:
javadoc
0m 59s
master passed

+0 :ok:
spotbugs
3m  5s
phoenix-core in master has 960 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
8m 12s
the patch passed

+0
hbaserecompile
18m  8s
HBase recompiled.

+1 :green_heart:
compile
1m  2s
the patch passed

+1 :green_heart:
javac
1m  2s
the patch passed

-1 :x:
checkstyle
3m 29s
phoenix-core: The patch generated 701 new + 6087 unchanged - 74 fixed = 6788 total (was 6161)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 49s
the patch passed

-1 :x:
spotbugs
3m 20s
phoenix-core generated 5 new + 960 unchanged - 0 fixed = 965 total (was 960)

_ Other Tests _

-1 :x:
unit
113m  1s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 46s
The patch does not generate ASF License warnings.

172m 30s

Reason
Tests

FindBugs
module:phoenix-core

Load of known null value in org.apache.phoenix.monitoring.TableMetricsManager.getInstance()  At TableMetricsManager.java:in org.apache.phoenix.monitoring.TableMetricsManager.getInstance()  At TableMetricsManager.java:[line 88]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.options from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 57]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.isMetricPublisherEnabled from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 69]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.isTableLevelMetricsEnabled from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 58]

Write to static field org.apache.phoenix.monitoring.TableMetricsManager.tableClientMetricsMapping from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:from instance method new org.apache.phoenix.monitoring.TableMetricsManager(QueryServicesOptions)  At TableMetricsManager.java:[line 61]

Failed junit tests
phoenix.end2end.PermissionNSEnabledWithCustomAccessControllerIT

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/11/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1224

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaserebuild hbaseanti checkstyle

uname
Linux f66894b3dc95 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / df32aec

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/11/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/11/artifact/yetus-general-check/output/new-spotbugs-phoenix-core.html

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/11/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/11/testReport/

Max. process+thread count
16027 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1224/11/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


ValueError: staleness option can't be changed while a transaction is in progress

Environment details

OS: Linux uname -a 5.11.0-46-generic #51~20.04.1-Ubuntu
Language runtime version: Python 3.8.10
Package versions:

google-cloud-spanner        3.12.1
sqlalchemy-spanner          1.0.0
grpc-google-iam-v1          0.12.3
grpcio                      1.42.0
grpcio-status               1.42.0
grpcio-tools                1.38.0
google-api-client           3.14.159265359.post1
google-api-core             2.3.0
google-api-python-client    2.0.2
google-auth                 1.28.0
google-auth-httplib2        0.1.0
google-cloud-core           2.2.1
googleapis-common-protos    1.53.0
grpc-google-iam-v1          0.12.3

Steps to reproduce
Running this script:
from sqlalchemy import create_engine

engine = create_engine(
    "spanner:///projects/X/instances/Y/databases/Z"
)

print(engine.execute("SELECT 1").scalar())

ends up running the query, but also throwing an error -- output from the CLI:
Exception during reset or similar
Traceback (most recent call last):
  File "/home/alex/.local/lib/python3.8/site-packages/sqlalchemy/pool/base.py", line 671, in _finalize_fairy
    fairy._reset(pool)
  File "/home/alex/.local/lib/python3.8/site-packages/sqlalchemy/pool/base.py", line 847, in _reset
    pool.dispatch.reset(self, self._connection_record)
  File "/home/alex/.local/lib/python3.8/site-packages/sqlalchemy/event/attr.py", line 259, in __call__
    fn(*args, **kw)
  File "/home/alex/.local/lib/python3.8/site-packages/google/cloud/sqlalchemy_spanner/sqlalchemy_spanner.py", line 51, in reset_connection
    dbapi_conn.connection.staleness = None
  File "/home/alex/.local/lib/python3.8/site-packages/google/cloud/spanner_dbapi/connection.py", line 203, in staleness
    raise ValueError(
ValueError: `staleness` option can't be changed while a transaction is in progress. Commit or rollback the current transaction and try again.
1

Now, if I use:
with engine.begin() as connection:
    print(sql(connection, "SELECT 1 + 1").scalar())

it's all good. Any idea?

@odino, this PR is going to fix the failure: https://github.com/googleapis/python-spanner-sqlalchemy/pull/188/files
Are using the released version?

@odino, oh, I guess I know what's happening. By default, you're in SERIALIZABLE mode, which means you should commit your operations manually, or use a context manager, like:
with engine.begin() as connection:
    connection.execute(...)

Otherwise you're returning a connection back to connections pool, but there is a transaction in progress on the connection.

@IlyaFaer thanks for your pointer -- I do assume that is the problem. Though I see you're working on a PR, as it would be convenient not having to commit / roll it back manually eg. when you're executing just some random selects. I actually did not realize everything ran in the context of a tx here.

BTW one thing to note, when I switch to AUTOCOMMIT I still see some funky warning:
/home/alex/.local/lib/python3.8/site-packages/google/cloud/sqlalchemy_spanner/sqlalchemy_spanner.py:947: UserWarning: This method is non-operational in autocommit mode
  dbapi_connection.rollback()

The issue is resolved now, will do a release with the fix and update here.

The fix is now released with the latest version.

When v1.1.0 will be available at PyPI ?
https://pypi.org/project/sqlalchemy-spanner/#history

Hi @kazshinohara,
It looks like the release failed which is why it is not available on PyPI. Unfortunately, the issue for the failure was closed by a bot before we saw it so we weren't aware of this until now. I'm looking into this issue now and will let you know when it has been successfully published to PyPI.
Apologies for the inconvenience!

@larkee Thanks !!  I'm planning to talk about this ORM at an user community in Japan next month, hopefully the release wil be landed soon.

hey @vi3k6i5 -- as @kazshinohara mentioned, the v1.1.0 release has failed, any tentative date it woud be released?
We are facing this issue even after using engine.begin()
with engine.begin() as connection:
    sql(connection, "SELECT a from b").scalar()

Hi any update on this ?

Hi @asthamohta , please take a look.

Hi @kazshinohara, @IlyaFaer has figured out the issue and will push a solution by tomorrow so hopefully by early next week we will have a release :)

I've checked the error on the current main branch - everything seems to be in order, no error messages:

Fixed by #214
Closing the issue. In case the error remains after the next release, feel free to re-open.

Hey @IlyaFaer, the customer is facing the following issues:
The first one is, it seems not to be able to pick up the sqlalchemy-spanner dialect unless I change the database URL from something like this:
"spanner:///projects/project-id/instances/instance-id/databases/database-id"
to this
"spanner+spanner:///projects/project-id/instances/instance-id/databases/database-id"
so, specifying the driver like that fixed the first issue.
and my current database URL setup look like this:
SQLALCHEMY_DATABASE_URI = f"mysql+pymysql://{PRIMA_DB_USERNAME}:{PRIMA_DB_PASSWORD}@{PRIMA_PROC_DB_HOST}/prima_processing"
SQLALCHEMY_BINDS = {
"jefe-jobs": "spanner+spanner:///projects/hpc-sandbox-268519/instances/jefe-spanner-instance/databases/jefe-jobs"
}
The second one is similar to the initial error (not the above one), but this time I get it every time I make a mysql related query it throws this error.
[2022-06-08 10:59:13,949] ERROR in base: Exception during reset or similar
Traceback (most recent call last):
File "/pdata/devsrc/amhadest/wavepipe-service/venv/lib/python3.8/site-packages/sqlalchemy/pool/base.py", line 697, in _finalize_fairy
fairy._reset(pool)
File "/pdata/devsrc/amhadest/wavepipe-service/venv/lib/python3.8/site-packages/sqlalchemy/pool/base.py", line 874, in _reset
pool.dispatch.reset(self, self._connection_record)
File "/pdata/devsrc/amhadest/wavepipe-service/venv/lib/python3.8/site-packages/sqlalchemy/event/attr.py", line 261, in call
fn(*args, **kw)
File "/pdata/devsrc/amhadest/wavepipe-service/venv/lib/python3.8/site-packages/google/cloud/sqlalchemy_spanner/sqlalchemy_spanner.py", line 51, in reset_connection
if dbapi_conn.connection.inside_transaction:
AttributeError: 'Connection' object has no attribute 'inside_transaction'

The second one is similar to the initial error (not the above one), but this time I get it every time I make a mysql related query it throws this error

But, wait, when you create a connection to a Spanner database, SQLAlchemy uses our dialect for all the operations. It's not possible to use this dialect with MySQL, because Spanner and MySQL are different. If I understand your case correctly, you should use two different connections for two different databases - one for Spanner, another one for MySQL. By looking at the database URL prefixes, SQLAlchemy will understand what kind of a connection and dialect should be used. But it must be two separate connections/engines/dialects.
I can add a condition into the reset mechanism not to do anything with no-Spanner connections, but I don't think it'll allow to run MySQL queries on Spanner dialect.

Apologies for the late response. @IlyaFaer that make sense. It seems the changes made in this fork  and this change both can fix the issue I was having even though I’m using a single engine for both Spanner and MySQL (Thank you for that).
Although the error is gone, if possible, I’m trying to create two different engines and connections, one for Spanner and one for MySQL. The problem is I’m using Flask-SQLAlchemy, and as far as I understand Flask-SQLAlchemy accepts only one SQLALCHEMY_DATABASE_URI and if one need to connect to multiple database, it has to be done through the SQLALCHEMY_BINDS method (as it shown in the code snippet above).
I understand as it is mentioned in this issue (#221 ), even creating separate engines throws the same error but I thought it would be preferable to have separate engines and connections. So, Is there a way to create separate connections using Flask-sqlalchemy so that they can use different engine and their own dialect?

@amha19, if you'll do something like this:
engine = create_engine( "spanner+spanner:///...")
engine2 = create_engine("mysql+mysql:///...")

Engines and connections will be separate (and it's what Flask is doing, as far as I can tell). But all the connections will be using the same reset mechanism. That was the problem of the original issue - connections reset mechanism is global for all the engines and connections on your machine - that's something we didn't expect.
Thus, if I understand correctly what you mean, it's already working like this. Connections are separate, it's the connections reset mechanism which brings confusion because of its globality (but from now on this mechanism first checks what kind of a connection it got before doing the actual reset).


Fails to build under Python 3.7

Currently, under Python 3.7, in _ts, the exc_ members are no longer present, however in a few places, there's still references to them buried deep.
This should be addressed by -- I think -- using the curexc_ members instead of the exc_ members.

Looking at https://github.com/dls-controls/cothread/issues/9 it seems that the solution is a little less elegant, and requires some version-specific wrangling:

Python (  … , 3.7) uses the exc_type and friends to specifically refer to current routine and coroutine information. This is not the same as curexc_* as I had thought previously.
Python [3.7,  … ) uses a stack to define the current (and other) exception data, _th->exc_state, which replaced the _th->exc_type fields (see https://github.com/python/cpython/pull/1773 and https://github.com/python/cpython/blob/3.7/Include/pystate.h#L248 )

This means a python-3.7 and above specific version for the changes in CPython, if I'm reading the tea leaves properly.

Turns out all this was handled by newer versions of Cython.
This means making sure that url/url.cpp never gets checked in if we can avoid it and a dependency to cython is added. This will make sure that python 3.8's quirks and features are kept.


Document otel for logging and tracing policies

Description
This was added recently but doesn't have docs yet.

its https://github.com/kumahq/kuma/pull/5999 right?

https://github.com/kumahq/kuma/pull/5992 too


Project picker page

Added a page to select a project type from a drop-down. The only current option is an afghan as that is part of the mvp.

Looks good 😄


Fix Netflix sync time

The Netflix watched date is always when the user began watching, not when they finished. We should change that by adding the length of the episode/movie to the watch date, so it's more accurate.

Possible as an user option?

Well, I can't see why anyone would want it to behave like it does currently, since the watch time is always wrong. But sure, we can add it as an option, enabled by default.

I think this is a case with pretty much all streaming services. It records the last time the play-button was clicked, or similar. The problem is of course if you watch a part of the title at one point, and resumes at another time. Not sure if it's worth making a lot of UI for, but at least it is a concern.
Also there are a few similar off situations.
If you use trakt "add on release date"-feature, it would record the start time. Scrobling and checkins would record the end time. I guess it is a matter of definition, and not sure if it is important. I don't have any strong opinions of this.


Typo: Backslash vs Forward Slash in List.cshtml

Noticed in the video & current code, when you reference the Edit page on the Add New button, your slash is a backslash, where everywhere else in the code it's a forward slash. It actually still works fine, probably through ASP.NET magic, but thought I'd mention it for consistency.
Add New

Good catch, fixed!


'Something went wrong error' on attempt to edit visual

It's hard to recall what exactly I was doing with a visual before (basically I was copy-pasting Deneb visuals, editing Vega code and replacing data fields to create multiple different charts). Now some copies of the visual seem to be broken. So far I noticed that it happened with visuals that still contain Vega code but no data fields (Values field on Visualizations pane is empty). Now when I choose 'Edit' Power BI shows a error message 'Something went wrong', then visual becomes invisible and appears again after switching to another page and back. See https://dl.dropboxusercontent.com/s/8y01efs386pq684/PowerToys_2lXrSgoEnH.mp4
error details

I don't know without further context, but copy/pasting will attempt to include persisted properties and if you don't have data fields present in the dataset, then we run into some issues working with them from the visual side. This is a known issue with custom visuals and has been requested for the team to fix since 2019. I periodically remind the team about this, as I would like to be able to create custom visuals that don't need data, or even allow Deneb to function without a bound dataset (for scenarios like static visuals or custom shapes), but it would seem that it isn't important enough for them to address.
Deneb relies heavily on this feature to keep the specification persisted without the user trying to intervene. However, if no data is present then this workflow is not triggered, so I'm not 100% sure if this is actually what might be going wrong here.
Given that the main window is throwing an error, this suggest an issue with Power BI itself and there may not be much we can do here (particularly as we can't easily fire our own logic until we get data from the main window). I'll have to try and investigate this further if we can get reliable reproduction steps, so I'll keep open for now.

I already have about 70 Deneb visuals in that report (5-15 instances of the visual per page). All instances have been switched to the actual AppSource version, all other Deneb version have been removed from the report, all instances are connected to the dataset and contain Vega code, and there are no issues with Vega visualizations.
But some instances of the visual still have the problem, although it's a bit different now:
When I click "Edit" there is no any error message but the entire report page becomes blank

I've found that enabling and then disabling 'Mobile Layout' restores normal page view.

I believe that it's somehow related to the past history of the problematic instances of the visual (in the past I was switching some of the instances between multiple version of the visual, including standalone and alpha, disconnecting them from the dataset (removing everything from Values field) and copy pasting them with old Vega code inside but with no data and so on).
Is it possible that despite removing all old versions of the visual form the report and switching to the latest AppSource version, some instance of the visual still have some artefacts of their history? I don't think the blank page issue happens with the instances of the visual without such history (recently inserted ones).

Suppose a visual has been swapped over time and reconfigured with a different visual ID, etc. In that case, there may be an accrual of objects and properties that could be causing issues, but this is a Power BI thing, and I don't know of a way to 'refresh' this metadata for existing visuals in a report. With the new .pbip format, there might be a way to analyze and process them procedurally, but this would require R & D to explore, and we'd still need to ascertain the root cause.
What may be more telling is the white-out you get when you open the editor. Does this happen when you publish to the web and attempt the service? Opening your developer tools and inspecting the JavaScript console may be possible. An error message will likely explain what went wrong when opening the editor.
If we find such an error, in combination with your workbook configuration, we may be able to isolate and fix a root cause and possibly harden it in Deneb if these situations potentially occur, but I would need both pieces of info to be able to investigate further. If you can't analyze this service, I can have a go if you send your affected workbook and provide the specific visual we see this on so that I can reproduce myself.


style: reformatted using vs

:tada: This PR is included in version 1.1.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add documentation for /namespace API

Documentation should be added to the namespaces API.  Current plan is to use sinatra-docdsl mixed in with the sinatra routes.
This allows us to tie our documentation to our route definition code.  This could make it easier to test our documentation against our code.

Documentation moved to RAML specification.


Provide a way to supply stdin to Process.runSync

Right now, the only way to supply stdin to a process is to use the static Process.start(), and then add to the returned Process's stdin stream.
This is nice when you want to stream large amount of data without blocking, but if all you want to do is supply a little input to a process, it's overkill, especially because of the viral nature of async/await. If I want to add a simple process call that takes some stdin deep in some API, it means that the entire call chain to that API needs to all of a sudden change to be async, which is not always feasible.
Ideally, I'd like to see something like this:
class Process {
  //...
  ProcessResult runSync (
    String executable,
    List<String> arguments, {
    String workingDirectory,
    Map<String, String> environment,
    bool includeParentEnvironment: true,
    bool runInShell: false,
    Encoding stdoutEncoding: systemEncoding,
    Encoding stderrEncoding: systemEncoding,

    // New API:
    Encoding stdinEncoding: systemEncoding,
    Iterable<int> stdin,
  })
  // ...
}

Where the entire contents of the stdin Iterable is supplied to the called process when invoked.
[It may or may not need to have an encoding specified, but I think it probably should have one, and transform it before sending it down to the process.]
Imagine needing to supply a "y" to a command that waits for user confirmation: do you really want to rewrite your entire API as async because of that one "y"? :-)

+1, bumping this!


Some Sentry messages seem to be truncated

Example https://sentry.io/poldracklab/fmriprep/issues/768434032/events/36874332501/
Note that both "message" as well as "traceback" are truncated, but the latter is twice as long as the former.

Traceback seems to be truncated at 16384 characters.

Maybe the way to go about fixing this is to give nipype a config option to display the final N characters of stdout? It will probably be generally true that the relevant lines will be the final lines.

I'm not sure how this looks on the console. For Sentry I was planning to split traceback into multiple chunks each at most 16384 characters.


[BUG] Unable to add Grafana repository

Describe the bug
Epicli fails on downloading requirements due to the issue with adding Grafana repository that has been occuring for about one week.
How to reproduce

Try to deploy any cluster using epicli.

Expected behavior
All requirements should be downloaded with no issues.
Environment

Cloud provider: [all]
OS: [RHEL, Ubuntu, CentOS]

epicli version: [epicli --version] dev, probably all epicli versions are affected
Additional context
AWS RHEL / CentOS / Azure RHEL
Adding repository: grafana
Executing: rpm --import https://packages.grafana.com/gpg.key
Importing GPG key 0x24098CB6:
 Userid     : \"Grafana<EMAIL_ADDRESS> Fingerprint: 4e40 ddf6 d76e 284a 4a67 80e4 8c8c 34c5 2409 8cb6
 From       : https://packages.grafana.com/gpg.key
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana
Trying other mirror.

 One of the configured repositories failed (grafana),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work \"fix\" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=grafana ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable grafana
        or
            subscription-manager repos --disable=grafana

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=grafana.skip_if_unavailable=true

failure: repodata/repomd.xml from grafana: [Errno 256] No more mirrors to try.
https://packages.grafana.com/oss/rpm/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for grafana"

Azure Ubuntu
deb https://packages.grafana.com/oss/deb stable main
Warning: apt-key output should not be parsed (stdout is not a terminal)
OK

Get:33 https://packages.grafana.com/oss/deb stable/main amd64 Packages [23.7 kB]
Err:33 https://packages.grafana.com/oss/deb stable/main amd64 Packages
  File has unexpected size (23500 != 23695). Mirror sync in progress? [IP: <IP_ADDRESS> 443]
  Hashes of expected file:
   - Filesize:23695 [weak]
   - SHA512:2777cc785ce2602ca181384db126d9f8b6ba1fe4646c406a8b3ce3420dddcb5ad0bd183da6f0aa3b3a8171368fde6c2a49443b110f6432b98344209e0f6186bd
   - SHA256:8efd16d6a802dc874143eeba53e79c2ecfdf946b32536d10f33db8b948b2cabc
   - SHA1:b4c0c38fe69119c749981163fbceb771310f1387 [weak]
   - MD5Sum:a7e1e78a0bade6fc3d25d2101cb42d92 [weak]
  Release file created at: Thu, 15 Jul 2021 11:20:36 +0000
Fetched 24.3 MB in 6s (4259 kB/s)
Reading package lists...
E: Failed to fetch https://packages.grafana.com/oss/deb/dists/stable/main/binary-amd64/Packages.bz2  File has unexpected size (23500 != 23695). Mirror sync in progress? [IP: <IP_ADDRESS> 443]
   Hashes of expected file:
    - Filesize:23695 [weak]
    - SHA512:2777cc785ce2602ca181384db126d9f8b6ba1fe4646c406a8b3ce3420dddcb5ad0bd183da6f0aa3b3a8171368fde6c2a49443b110f6432b98344209e0f6186bd
    - SHA256:8efd16d6a802dc874143eeba53e79c2ecfdf946b32536d10f33db8b948b2cabc
    - SHA1:b4c0c38fe69119c749981163fbceb771310f1387 [weak]
    - MD5Sum:a7e1e78a0bade6fc3d25d2101cb42d92 [weak]
   Release file created at: Thu, 15 Jul 2021 11:20:36 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.

What's strange I'm able to deploy AWS Ubuntu \ Azure CentOS clusters with no issues (usually).

DoD checklist

[x] Changelog updated (if affected version was released)
[x] COMPONENTS.md updated / doesn't need to be updated
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[x] Case covered by automated test (if possible)
[ ] Idempotency tested
[x] Documentation updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Backport tasks created / doesn't need to be backported

Its already reported: https://github.com/grafana/grafana/issues/36935

We should ensure that workaround with GPG check disabling will work. If yes, we discussed adding explicit --do-not-check-gpg flag. Another option is to start #2293

We should also consider downloading packages as standalone binaries (files).
https://grafana.com/grafana/download/7.3.5?platform=linux
https://dl.grafana.com/oss/release/grafana_7.3.5_amd64.deb
https://dl.grafana.com/oss/release/grafana-7.3.5-1.x86_64.rpm
https://dl.grafana.com/oss/release/grafana-7.3.5-1.aarch64.rpm
https://dl.grafana.com/oss/release/grafana-7.3.5.linux-amd64.tar.gz

yum related issue: grafana/grafana#37274

Tested:
✔ epicli apply: AWS / Azure x RHEL / CentOS / Ubuntu x64
✔ epicli apply: AWS CentOS aarch64
For testing purposes I also modified the condition > to >= to verify upgrades as there was no other way to test it as we have the same Grafana version since epicli v0.7). It also went smoothly :)
      when:
        - grafana_defaults.grafana_version is version(ansible_facts.packages['grafana'][0].version, '>')

      when:
        - grafana_defaults.grafana_version is version(ansible_facts.packages['grafana'][0].version, '>=')


feat: enable textarea counter

Changelog
New

Enable text area counter

Q: is this still WIP?
When testing in storybook, the fluid layout seems broken

The counter does also not update when typing.

Q: is this still WIP? When testing in storybook, the fluid layout seems broken

@brampeirs Yes, I verified this in other implementations, seems like counter isn't compatible with fluid states as of now - fluid states are still experimental.

@Akshat55 Counter isnt updating for me.
I've set maxlength to 100 and enabled enableCounter.
When I toggle enableCounter, the counter is updated but it isnt updating as I type.


java.lang.NoClassDefFoundError: BaseThirdEyeApplication on Thirdeye Quickstart

I am following https://thirdeye.readthedocs.io/en/latest/quick_start.html and the steps mentioned in the documentation is failing for me. I have tried the same on two different systems & they still don't seem to work:
on running
./run-frontend.sh
I am getting
******************************************************
Launching ThirdEye Dashboard in demo mode
*******************************************************
Error: Could not find or load main class org.apache.pinot.thirdeye.dashboard.ThirdEyeDashboardApplication
Caused by: java.lang.NoClassDefFoundError: org/apache/pinot/thirdeye/common/BaseThirdEyeApplication

Can you please help?

+1 same issue here

@bountyx I was able to run this by following https://medium.com/@gregsimons_84/apache-pinot-thirdeye-quickstart-helper-b5d8a95a22eb
Hope this helps!


Backport: Add in Kubernetes 1.13.9, 1.14.5, 1.15.2

#21977

Tested with - v2.2.7-rc5
Following are the Ks8 version that are available for deploying cluster:
v1.13.9
v1.14.5
v1.15.2

All existing automation runs succeeded when create cluster with 1 control , 3 etcd and 3 worker nodes:
v1.13.9
v1.14.5
v1.15.2


Change debug tags and make sure sni is printed on certain logs

[approve ci]

[approve ci autest]

[approve ci].

[approve ci].

[approve ci].

[approve ci].

[approve ci]

Changing tag is probably ok, but changing Warning to Debug may be not. Warnings are printed regardless of diags.debug.enabled and diags.debug.tags, and those would be disappeared on prod. If those warnings are not really important on prod then I'm ok with making them debug log, but users watching the warnings would be surprised. We might want to mark this incompatible. I didn't check how SSLError works but I have the same concern on it as well.

I thought about that too, but the message logged in Diags also seems reasonable to be in debug logs as well. We will have our ops team test this out for a few days and see what they prefers, I'll make adjustments according to their comments.

Oh, I didn't catch that the Warning messages were going away.  I thought you were just adding Debug messages in parallel so in the more detailed case all would show up in traffic.out.
I know that our ops guys rely on the certificate verification messages always showing up.  They use that to check when to yell at origins for having bad certs.  They don't run with debug enabled enough for that to be equivalent.

[approve ci]

@randall is going to review this

[approve ci autest]


<IP_ADDRESS> tag missing

We are using gem version <IP_ADDRESS> and there does not appear to be a corresponding tag in this github repo.
A bunch of other releases seem to also be missing (e.g. anything between <IP_ADDRESS> and <IP_ADDRESS>).

This release is also not on rubygems.

Hey @p-decoraid
I reviewed all logs and <IP_ADDRESS> was never released, the last version for 2.1.x is <IP_ADDRESS> and after is 2.2.0.
Anyhow I published  this version <IP_ADDRESS> into ruby gems.
Regards,

Okay thanks, that's interesting. I wonder where this <IP_ADDRESS> version came from then.


Fix ability to store errors from GlobalSign

Thanks a lot to myself in the past for using a MongoDB schema package that would
later confuse me greatly. On the whole, though, good choice.

I'm pretty +1 on SimpleSchema as compared to blind faith that you'll get the shapes right every time. :)

I 95% agree, which rounds up to 100% agree.
However, SimpleSchema was silently dropping my writes, seemingly, in this case.


wagtailimages.Image - 'NoneType' object has no attribute 'size'

Found a bug? Please fill out the sections below. 👍
Issue Summary
wagtailimages.Image - 'NoneType' object has no attribute 'size'
Steps to Reproduce

Upload Image 'A' to AWS S3
Remove 'A' from AWS S3
Edit 'A' on Wagtail admin
Error ''NoneType' object has no attribute 'size''

Technical details

boto==2.46.1
Django==1.10.6
django-storages==1.5.2
wagtail==1.9

The error occur from here.
    def get_file_size(self):
        if self.file_size is None:
            try:
                self.file_size = self.file.size
            except OSError:
                # File doesn't exist
                return
            self.save(update_fields=['file_size'])

I had this issue with using the s3boto3.S3Boto3Storage backend in Storages - switching to  storages.backends.s3boto.S3BotoStorage solved it.

I really use it.
DEFAULT_FILE_STORAGE = 'storages.backends.s3boto.S3BotoStorage'

This is expected behaviour - if you delete a file (from S3 or anywhere else) that Wagtail is using as an image, then naturally it's going to throw an error when Wagtail tries to access the file again.
(If I've misunderstood, please clarify and I'll be happy to re-open...)