why remove thanos components from kube-prometheus  in  the new release-0.1 ?

What happened?
Recently, I apply the kube-rometheus in release-0.1 , and generate the thanos yaml with jb tool , when I apply all the manifests, I found the thanos compactor  have some overlap data in S3 object storage, and cause the pod of thanos-compactor-0 CrashLoopBackOff, below is the error log, so I want to know how to fix this problem ?
level=debug ts=2019-07-17T11:09:03.686836025Z caller=compact.go:278 msg="block is too fresh for now" block=01DFZSDMD8Q6198ZQ6CEQRR234
level=debug ts=2019-07-17T11:09:03.686979715Z caller=compact.go:278 msg="block is too fresh for now" block=01DFZSDHYCYPMEXFEBJM5NC781
level=debug ts=2019-07-17T11:09:03.687511345Z caller=compact.go:278 msg="block is too fresh for now" block=01DFZSDJF9M9BFZ0XFVDFHAXQV
level=info ts=2019-07-17T11:09:03.687588824Z caller=compact.go:1012 msg="start of GC"
level=info ts=2019-07-17T11:09:03.688727321Z caller=compact.go:1018 msg="start of compaction"
level=error ts=2019-07-17T11:09:03.690467923Z caller=main.go:182 msg="running command failed" err="error executing compaction: compaction failed: compaction failed for group 0@{cluster=\"tracey-test-k8s\",prometheus=\"monitoring/k8s\",prometheus_replica=\"tracey-test-replica\"}: pre compaction overlap check: overlaps found while gathering blocks. [mint:<PHONE_NUMBER>000, maxt:<PHONE_NUMBER>000, range: 2h0m0s, blocks: 2]: <ulid: 01DFZBP3W0XAWD3WQHKPV4MPA3, mint:<PHONE_NUMBER>000, maxt:<PHONE_NUMBER>000, range: 2h0m0s>, <ulid: 01DFZBP3EB9T5R5TD84QF70JVT, mint:<PHONE_NUMBER>000, maxt:<PHONE_NUMBER>000, range: 2h0m0s>\n[mint:<PHONE_NUMBER>000, maxt:<PHONE_NUMBER>000, range: 2h0m0s, blocks: 2]: <ulid: 01DFZJHTPBVCNNKKPB96J6D8PS, mint:<PHONE_NUMBER>000, maxt:<PHONE_NUMBER>000, range: 2h0m0s>, <ulid: 01DFZJHV40BDK2PRW7K6ST1YAJ, mint:<PHONE_NUMBER>000, maxt:<PHONE_NUMBER>000, range: 2h0m0s>"

Did you expect to see some different?
I hope we can use prometheus-operator combine with the thanos in the kube-prometheus project, and hope add thanos in the next coming release , also thanos  compactor works fine.

It's just separated into a separate project. Thanos support stays in the prometheus-operator and a new project is being worked on to encapsulate the Thanos pieces. @metalmatze sounds like we should move all of these things under a common org, wdyt?

thanos pieces are handled by https://github.com/thanos-io/kube-thanos


Bugfixes for Key Vault Insights

Fixed a bugged parameter in the at-resource workbook for Key Vault Insights.
Updated the gallery type for the at-resource workbook as well

you deleted a whole bunch of templates, you aren't loading them from inside groups?


How can I use dropout on input layer?

Hi everyone:
I try to combine softmax classifier and dropout algorithm, because there are only input layer and classfier. According tutorial, I want to use dropout on input layer like following:

But I got the following error:
Traceback (most recent call last):
File "softmax.py", line 255, in
Start_building_and_training(num_sample, x_data_merged_dnaid[:], y_label[:], num_batch)
File "softmax.py", line 213, in Start_building_and_training
prob = sess.run(y, feed_dict={x: batch_xs, y_: batch_ys})
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 717, in run
run_metadata_ptr)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 915, in _run
feed_dict_string, options, run_metadata)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 965, in _do_run
target_list, options, run_metadata)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 985, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors.InvalidArgumentError: You must feed a value for placeholder tensor 'Placeholder_1' with dtype float
[[Node: Placeholder_1 = Placeholderdtype=DT_FLOAT, shape=[], _device="/job:localhost/replica:0/task:0/gpu:0"]]
[[Node: Softmax/_5 = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/cpu:0", send_device="/job:localhost/replica:0/task:0/gpu:0", send_device_incarnation=1, tensor_name="edge_24_Softmax", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"]]
Caused by op u'Placeholder_1', defined at:
File "softmax.py", line 255, in
Start_building_and_training(num_sample, x_data_merged_dnaid[:], y_label[:], num_batch)
File "softmax.py", line 194, in Start_building_and_training
keep_x = tf.placeholder(tf.float32)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/array_ops.py", line 1270, in placeholder
name=name)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/gen_array_ops.py", line 1530, in _placeholder
name=name)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/op_def_library.py", line 703, in apply_op
op_def=op_def)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 2334, in create_op
original_op=self._default_original_op, op_def=op_def)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 1253, in init
self._traceback = _extract_stack()
Can anyone help me ? Thanks a lot!

Hi @JohnnyY8!  The concept behind dropout is to randomly drop some nodes from the hidden layer while training.  In the code you've highlighted above, you're applying dropout to the input layer, which is the problem.
For an example of how to apply dropout see this:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/examples/tutorials/mnist/mnist_with_summaries.py#L109
Hope this helps!  FYI we primarily use github issues to track bugs and installation issues; in the future please ask these types of questions on StackOverflow and tag it with the tensorflow tag.  Thanks!

From the error message and the code, I think the problem is rather that the keep_x placeholder is not fed into session.run. Giving a name to the placeholder should make the error message more obvious.

@tatatodd Hi:
Thanks for your answer. But applying dropout to the input layer maybe not the root problem, I think it is good for input and hidden layer. Thank you for your help again.

@fwalch Hi:
Thank you, I am just a beginner for tensorflow and do not understand how to feed the placeholder into session.run?

@tomermeged Truly thanks!


rajamangala university of technology isan khon kaen campus

มหาวิทยาลัยเทคโนโลยีราชมงคลอีสาน วิทยาเขตขอนแก่น
rajamangala university of technology isan khon kaen campus
rmuti

@doome972545 I am sorry, the domain rmuti.ac.th is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Pack at https://education.github.com/discount_requests/application. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


support spree 2.4-stable ?

This is not compatible with spree 2.4-sable

I have tried to fix that but, the specs are failing. I could not look into that. Please refer - https://github.com/stefansenk/spree_multi_tenant/pull/15

i have successfully integrate it with 2.4 stable.


Panicking after upgrade

After upgrading to version 1, we got the following panic message:
Error: `panic: panicked at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/backon-1.0.0/src/sleep.rs:33:9:
no sleeper has been configured, consider enabling features or provide a custom implementation` (on utils/src/tracers.rs:44)

IMO making it "silently" panicking (that is, there's no explicit API for picking the sleeper) is a pretty bad problem if you want to build a production-worthy library, and none of the examples make it clear that a sleeper impl must be configured.

Thank you for the report. I have added an upgrade guide for version 0.5: https://github.com/Xuanwo/backon/releases/tag/v0.5.0. However, it doesn't seem sufficient.
Do you think it would be better to include tokio-sleep in the default feature?

Adding the default features is a much better solution, thanks.
Typically I suggest that Cargo features should be necessary but not sufficient to change (significant) behavior (that is not caught by compilation failures). Even more so because Cargo features can be implicitly changed by other crates pulled into your dependency graph. So I would suggest that your API take an explicit argument for the sleeper impl used. For example, ExponentialBuilder::default() could become ExponentialBuilder::tokio() instead, or you could expose wrapper types (I prefer to avoid type aliases) as like backon::tokio::ExponentialBuilder.


feat(sbb-table-wrapper): initial implementation

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the pull request tracker for a Pull Request (PR) that matches the one I want to submit, without success.

Issue
This PR Closes #2670
Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)

See Review Guidelines for more information what is checked during review process.
Changes
Changes in this pull request:

Table styles and mixins
sbb-table-wrapper implementation

Browsers
I tested the build on the following browsers:

[x] Firefox Desktop
[x] Chrome Desktop
[ ] Edge Desktop
[x] Safari Desktop
[ ] Chrome Mobile
[ ] Safari Mobile

Screen readers
I tested the build on the following browsers:

[ ] JAWS Firefox Desktop
[ ] JAWS Chrome Desktop
[ ] NVDA Firefox Desktop
[ ] NVDA Chrome Desktop
[ ] VoiceOver Safari Desktop
[ ] VoiceOver Chrome Desktop
[ ] VoiceOver Safari Mobile
[ ] Android Accessibility Suite Chrome Mobile

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

Generally LGTM 👍 Some open topics:

Should the default width of the table be 100%? This was previously the case in the sbb-angular library. Thoughts @TomMenga, @jeripeierSBB, @mcilurzo?
The shadow logic can be compared with the sbb-angular implementation. Basically add a scroll listener to the wrapper and use the resize event from the window to calculate shadow necessity. https://github.com/sbb-design-systems/sbb-angular/blob/main/src/angular/table/table/table-wrapper.ts
Maybe for the wrapper story, add more columns to demonstrate the responsiveness.

I'll reply point by point:

In the first implementation I set the width to 100% but then I thought that the table layout (whether fixed or auto) and size should be in charge of the consumer. I'm not against having a default 100% width though.
It's not the same, unfortunately. We do not have a problem understanding when to show the shadow (we already do that in the sticky header for example). The problem stands in the shadow effect itself since we do not have any element that could cast that shadow from the table borders. The angular wrapper only has a shadow effect on fixed columns (because the column itself can cast it). I've tried different approaches but none of them worked 100%.
The closest thing I found was by simulating a shadow using backgrounds (Codepen). The drawback is that the appearance is bound to the scroll and that's not an actual shadow. Maybe we can deep down on it in a call
On it 👍

If you wonder why tests are failing, it seems that the spec file was formatted wrongly somehow. new generation of it could solve it.

If you wonder why tests are failing, it seems that the spec file was formatted wrongly somehow. new generation of it could solve it.

yeah :/ thanks


[3.x] Add option to toggle visibility of position gizmos in 2D editor

Backport of #75005

Thanks!


Spring Boot plugin requires Gradle 6.8.x, 6.9.x, or 7.x. The current version is Gradle 6.4 (On Gradle 7.4!)

I am using spring boot 2.6.2.  The filter is wrong.
Spring Boot plugin requires Gradle 6.8.x, 6.9.x, or 7.x. The current version is Gradle 6.4
--
And this is after i typed:
"gradle wrapper --gradle-version 7.4"
Which is weird because it's saying 6.4, but it should be detecting 7.4.

Ah. This does work, and changing the property file directly works too!
./gradlew wrapper --gradle-version 7.4

Seems like the problem is solved, pls. let us know otherwise.

Hmm, I still think it may be gradle
private void verifyGradleVersion() {
	GradleVersion currentVersion = GradleVersion.current();
	if (currentVersion.compareTo(GradleVersion.version("6.8")) < 0) {
		throw new GradleException("Spring Boot plugin requires Gradle 6.8.x, 6.9.x, or 7.x. "
				+ "The current version is " + currentVersion);
	}
}

If this says 6.4, then GradleVersion.current() is what is returning that value.

Ah!  You are right, sorry for the confusion.  my installed gradle happened to be 6.4.  After updating that version, I have no issues. Thanks!

Thanks, the solution works fine for me!!


ProtocolMapper not applying config section properly

Based on the documentation example examples/protocol-mappers.yaml
Since this provider uses Terraform in background I'm trying to also add the following options:
"add.to.id.token": "true"
"add.to.access.token": "true"

But it seems not to be noticing the changes. I'm wondering if I'm doing something wrong or if it is failing somehow
Thanks!

According to the keycloak sourcecode it should be

access.token.claim and
id.token.claim

https://github.com/keycloak/keycloak/blob/cc558b4090eb6707e269d9a581945a6424d0adbc/services/src/main/java/org/keycloak/protocol/oidc/mappers/OIDCAttributeMapperHelper.java#L57
https://github.com/keycloak/keycloak/blob/cc558b4090eb6707e269d9a581945a6424d0adbc/services/src/main/java/org/keycloak/protocol/oidc/mappers/OIDCAttributeMapperHelper.java#L60
Does that work for you?
If not i'll implement https://registry.terraform.io/providers/Arkaniad/keycloak/latest/docs/resources/openid_audience_protocol_mapper
as ressource

Hey @Breee
It works!
Much appreciated

Great, i'll soon work on some docs that explain everything So people can
also contribute. However, i'm still evaluating on How to restructure the
whole Provider in order to fix all existing issues and issues I faced so
far
On Mon, May 20, 2024, 20:17 Juan Manuel Vera @.***>
wrote:

Hey @Breee https://github.com/Breee
It works!
Much appreciated
—
Reply to this email directly, view it on GitHub
https://github.com/crossplane-contrib/provider-keycloak/issues/90#issuecomment-2120961940,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC3JPMIAEWLY4PT4GJQR353ZDI42JAVCNFSM6AAAAABH75RND6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQHE3DCOJUGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Is it possible to attach lsp to all clients buffer?

Very cool project! Thanks for that.
When pair programming with a colleague we encountered that first the person who opens a new buffer, has the lsp client attached to that buffer and gets all the code completion, warnings, etc. The other client, has the buffer open as well but without an lsp attached to it.
Is it possible to attach the lsp for all clients, so all clients can enjoy the lsp features?

this would probably also fix the issue of some language servers which only work on the saved file and not on the buffer, like rust-analyzer


Emit polygon path

For 2D pathfinding, the current Path type works fine, but if you want to do 3D pathfinding (with multiple overlapping floors etc.), the current interface is insufficient. In particular, I'm imagining that you project out the X and Y positions of each point in a mesh, which may result in duplicate points. Polyanya supports duplicate points and overlapping/zero-area triangles, at least from my experimentation, but since it only outputs a list of positions it's impossible to know which of many overlapping triangles a given element in a path is from (and therefore what its Z position is). If the indices of polygons traversed were included in the Path then this wouldn't be an issue.

Hmm, looks like I was mistaken and Polyanya only supports duplicate points and zero-area triangles, but not overlapping triangles.

Polyanya with overlapping meshes!
output.webm
This is on a local fork where I've converted everything to use indices to uniquely identify points instead of Vec2s. The purpose of this demo was actually just to double check that that was working as expected.

I also have something working for overlapping meshes in https://github.com/vleue/polyanya/pull/62
https://github.com/user-attachments/assets/108136da-4b41-4f79-be85-877ba048ec6f
This is still working with Vec2s. @gmorenz did you continue with your demo? Did you put it somewhere on GitHub?

I didn't continue with my demo. The math I thought would work to generalize this to non-uniform-cost movement didn't pan out as I expected (which was actually what I was more interested in at the time), and after hitting a dead end there I moved on for the time being.
I'm happy to push the non-planar demo to github tomorrow

The math I thought would work to generalize this to non-uniform-cost movement didn't pan out as I expected (which was actually what I was more interested in at the time), and after hitting a dead end there I moved on for the time being.

I have something that works for that now, see this test: https://github.com/vleue/polyanya/blob/c74391be7a14c8070c188664560c4c3872a785ea/src/stitching.rs#L899
it's setting up a navmesh with 5 layers like so:
00
13
23
44
``
with layers 1 and 2 having a higher cost of traversal than layer 3, then for 20 points equally distributed in a line in layer 0, find the path to the corresponding points in layer 4. The path correctly goes either through slower layers or around them depending on the cost.

@taktoa to support overlapping polygons I added the notion of "layer" that can be connected at some of their vertices. The path with the layer information can be retrieved when feature `detailed-layers` is enabled, as it can be costly
https://github.com/vleue/polyanya/blob/c74391be7a14c8070c188664560c4c3872a785ea/src/lib.rs#L64-L66
Does that work for you?


Create Top 10 Movie Rankings.md

📝 Description
Add a brief description.
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information
lol

Hey @PR-Peri
Thank you for contributing to our project. We just reviewed your AI Agent, the prompt is too simple to be a valued AI Agent to our community.
We suggest you to check out our Youtube channel for PR reviews, you can take some suggestions from there.
Meanwhile, you can also join our discord community to communicate and learn how to improve your AI Agent. If you can make this better, we would be happy to get it merged ASAP.

Hey @donqu1xotechina ,
Done made some changes. #3047


encode special characters in Dropbox-API-Arg

This PR fix issue #86 and it is based on response on dropbox forum https://www.dropboxforum.com/t5/API-support/HTTP-header-quot-Dropbox-API-Arg-quot-could-not-decode-input-as/m-p/195155#M8876 (posted by @MaxwellK in #86)

Thank you @adam187 for this fix!


Daf's "login" feature implementation update

[ ] I have read the Contributor Guide

Closes issue #15

Resolves issue #16

Fixes bug #20


Взаимодействие с сервером telegram

@0crat in

@0crat in (here)

@DronMDF Job gh:dronmdf/telebot#10 is in scope.

+15 points just awarded to @dronmdf, total is +150.

Job gh:dronmdf/telebot#10 assigned to @paddox, please go ahead (policy).

Нужно написать небольшой документик,
Где кратко описать - как получить сообщения с сервера. url, формат запроса, формат ответа.
То же самое - как послать сообщение.

@0crat assign me

@0crat assign me (here)

@DronMDF Job gh:dronmdf/telebot#10 assigned to @dronmdf, please go ahead (policy).

Oops! You need to have one of these roles in order to do what you're trying to do: ARC, PO. I'm sorry to say this, but at the moment you've got no roles in this project (your GitHub login is "0crat").

Oops! You need to have one of these roles in order to do what you're trying to do: ARC, PO. I'm sorry to say this, but at the moment you've got no roles in this project (your GitHub login is "0crat").

Manual assignment of issues is discouraged, see par.19: -5 points just awarded to @dronmdf, total is +475.

Job gh:dronmdf/telebot#10 is now out of scope.


Bug: WASM not training?

No change to structure except enabling/disabling the WASM...
Here's the (slow) JS version training:

And now the WASM version:

Note
The WASM does not appear to be training/updating based on the cost/loss output...
Ideas?

Hmm.. Did you use Conv/Pool Layers, or just FC?

Just FC (this is still previous network).  Did not implement the new InputLayer if that matters... just a bunch of FC layers.
This is using relu activation, crossEntropy and a softmax output (although I left the code as-is from before updating to 3.3.1, so perhaps I have to declare softmax output explicitly?

So just updated to InputLayer & OutputLayer... says OutputLayer is not a constructor, and does not appear to be exported/exposed from the webassembly() output (console.log shows it as undefined, where as InputLayer is showing correctly as a class extending FCLayer)
Am I missing something?

You may have an out of date version, OutputLayer came right after InputLayer. But both extend FCLayer, so I don't think that is the matter. Did you use a volume for the input, in the end, or 1D array?

Still 1D array... I wanted to get the WASM version working identically first before I started down the Conv/3D path

Ok, updated to 3.3.2 and the OutputLayer issue goes away... but the network still doesn't appear to train like when I switch it back to js()

Strange. I can try stepping through the values to catch discrepancies if you give me your config and a data sample.

Seem to have narrowed it down... the failure to learn appears to be introduced when using RMSProp with the webassembly version
let net = window.net = new Network({
    Module,
    activation: 'relu',
    cost: 'crossEntropy',
    updateFn: 'RMSProp', // commenting this out shows the error in fact declining
    layers: [
      new InputLayer(inputLength),
      new FCLayer(round(inputLength * 0.5)),
      new FCLayer(round(inputLength * 0.3)),
      new FCLayer(round(inputLength * 0.2)),
      new FCLayer(round(inputLength * 0.1)),
      new OutputLayer(outputLength, { activation: 'sigmoid', softmax: true })
    ]
  })

Ah, nice one. I'll have a play with it. I'll get back to you on that.

From a little trial and error, the optimizers appear to fall into the following categories (with the WASM version at least)
###Working

vanillasgd
adagrad

###Not Working

momentum
RMSProp (or RMS_Prop, as I see it referenced once in the docs)
adam
adadelta
gain

That said, I'm using adagrad at the moment and it's working... just figured RMS would be faster 🤷♂

Turns out there was a bug in assigning default learning rate values to WebAssembly (was checking for undefined, but should have checked 0, because C++), so the learning rate was 0 unless defined. Explains why tests didn't catch it. Not too sure about adadelta/gain, as they seemed to work for me. I'll keep digging.
In reference to the RMSProp/RMS_Prop comment, the string configs are case/space/underscore insensitive.

odd... regarding the learning rate - pretty sure I've had learning rate defined the entire time.  I'll keep poking around though!  I will say, the speed boost makes iterating sooooo much better 🥇
Also, random, but regarding dropout - might want to check with other libs on this, but you define it opposite to what I'd assume:
A dropout of 1 to me would mean 100% dropped connections, as a 0.3 would imply a 30% dropout rate/dropped connections.  I think you define it as the inverse (0.3 means keep 30% of the connections)

I see. I've mostly been following the cs231n course for learning things (http://cs231n.github.io/neural-networks-2/), and they had been referring to dropout using probability of keeping.
I was on the fence about this one, and it did indeed used to be the other way around, but then I saw Tensorflow also has it as probability of keeping (http://cs231n.github.io/neural-networks-2/), and changed it.

hmmm, well if TensorFlow does it that way, prob best to keep it as-is.  Seems counterintuitive, but most examples people will be following currently will be TF ones.
Also, I love the confusion matrix printout... so nice to tack that at the callback of the train session to compare training/test!  Having now tested virtually every major ML package on NPM (ConvNet, Synaptic, Neataptic, Nen, DNN, Deeplearn.js, etc) - I'm pretty sure you are on track to have the most robust one of all, once/if you add some of the competing architectures (LSTM, RNN, GRU, NARX, etc)

I agree with the counter-intuitiveness, but doing it my own way would probably not be a good idea, haha.
Thank you, I do hope to keep extending this as much as I can. Currently working on a GPU version, though first. Feed-forward FC layers are done so far, but GLSL and WebAssembly contexts are not making it easy for me 😥.
Once that's done, I hope to (learn and) add more things.


Revert "pull request #1407 from bstatcomp/matrix_cl_refactor"

This reverts commit 6723f81778f3ba939a95908c70d1514bfd322713, reversing
changes made to 6455b691681c11e11c3c6ecc6de39a9cf5c3c206.
Checklist

[x] Math issue #1407

[x] Copyright holder: Steve Bronder

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

Trying to think of the longer term fix testing wise to catch these things earlier

@serban-nicusor-toptal this keeps getting errors like the below on windows
g++ -std=c++1y -m64 -D_REENTRANT -Wall -Wno-unused-function -Wno-uninitialized -Wno-unused-but-set-variable -Wno-unused-variable -Wno-sign-compare -Wno-unused-local-typedefs     -I lib/tbb_2019_U8/include -O3  -I . -I lib/eigen_3.3.3 -I lib/boost_1.69.0 -I lib/sundials_4.1.0/include -I lib/gtest_1.8.1/include -I lib/gtest_1.8.1 -I lib/gtest_1.8.1/include -I lib/gtest_1.8.1    -D_USE_MATH_DEFINES  -DBOOST_DISABLE_ASSERTS        -c -o test/unit/math/mix/mat/fun/log_mix_test.o test/unit/math/mix/mat/fun/log_mix_test.cpp

cc1plus.exe: out of memory allocating 65536 bytes

Do you know why windows would run out of mem? I think it could be because of too many parallel jobs being run at once. I slammed it down to 4 atm. If that works maybe we should change the jenkins setup so it only runs like half as many possible parallel jobs on windows or something
https://jenkins.mc-stan.org/blue/organizations/jenkins/Math Pipeline/detail/reverts%2FPR-1407/2/pipeline

That seemed to do the trick, though things did not break all the time. So its hard to say if its a false positive. 4 does seem a bit low. Mind changing that to half and we can use that for some time, if things break again we can think come back to it.

Hey, do we need beefier machines for windows because of this?

Do we need beefier machines for windows because of this? It currently has m5d.12xlarge (48 vCPU, 192 GB RAM).

I think that is plenty enough, I would say its overkill on the RAM.

I looked for a way to allocate more memory for cc1plus.exe but didn't find anything, do you know how can I fix this on Jenkins @rok-cesnovar ? Thanks

Is it possible its that same issue we had before with how much RAM Jenkins can use? That came up for one of the tests some time ago. What is it set at currently? Maybe we should try setting a larger limit? By default its 1GB, the test that failed was usign 3GB or something.

It's set to 32GB on Jenkins ( java process)

I dont really have an idea on how RAM usage scales with multiple jobs, but I guess is just (RAM usage for single core) * jobs. Compiling on single core easily takes up a few GB of RAM. If we multiply that with 24 we get over that limit. Can we try setting it to 64GB for a test?

Give it a try, it's on 64 GB now.

Thanks!! restarted the tests, lets see.

It looks fine now. Can we check if this ran on a EC2 instance?

@serban-nicusor-toptal can you tell me which GPUs we use on the Mac machine and which one is used on the Linux machine? Would probably help find the reason for the failures that lead to this PR.

It's not running on EC2 now. To check on what's running either look on the main page, you'll see the job under the machine name or go to Job Console Logs and CTRL + F after 'Running on '
I will send you an email with the GPU info later when I get home.

@rok-cesnovar can you approve?

Or should we bump this back up to -j${env.PARALLEL} on windows then merge?

Nah lets try with this for now.


Granular axis tick label formatting based on timeunit

In pure JSON without elm
When you write the vega-lite specification in json by hand you can give an axis formatting string for each time-unit (see TimeMultiFormat) as in the following example (open in online vega editor):
{
  "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
  "width": 700,
  "data": {
    "sequence": {
      "start": -11000000,
      "stop": 10000000,
      "step": 100000,
      "as": "time"
    }
  },
  "mark": "tick",
  "encoding": {
    "x": {
      "field": "time",
      "type": "temporal",
      "axis": {
        "format": {
          "year": "'%Y",
          "hours": "kl %-H",
          "minutes": "%H:%M"
          }
      },
      "scale": {"type": "utc"}
    }
  }
}

This yields the following visualization (notice the different tick label formats depending on the granularity context):

This kind of formatting option is especially useful in visualizations with zoom, e.g. you don't have to write both year and seconds (and everything in between) on every tick label).
In elm-vegalite
I tried to give axFormat the whole json map as a string:
timeExample : Spec
timeExample =
    let
        data_ =
            dataSequenceAs -11000000 10000000 100000 "time"

        myAxis =
            pAxis
                [ axFormatAsTemporal
                , axFormat """{ "year": "`%Y", "hours": "kl %-H", "minutes": "%H:%M" }"""
                ]

        myScale =
            pScale [ scType scUtc ]

        enc =
            encoding
                << position X
                    [ pName "time"
                    , pTemporal
                    , myAxis
                    , myScale
                    ]
    in
    toVegaLite [ width 700, data_, enc [], tick [] ]

But then the map is just used as a regular format string:

Proposal
We probably want to leave axFormat as is and introduce some new functions and types like:
axFormatMulti : List TimeUnitFormat -> AxisProperty
tufYear : String -> TimeUnitFormat
tufQuarter : String -> TimeUnitFormat
tufMonth : String -> TimeUnitFormat
tufWeek : String -> TimeUnitFormat
tufDay : String -> TimeUnitFormat
tufDayOfYear : String -> TimeUnitFormat
tufHours : String -> TimeUnitFormat
tufMinutes : String -> TimeUnitFormat
tufSeconds : String -> TimeUnitFormat
tufMilliseconds : String -> TimeUnitFormat

Then the api could look like this:
 pAxis
    [ axFormatAsTemporal
    , axFormatMulti
        [ tufYear "`%Y"
        , tufHours "kl %-H"
        , tufMinutes "%H:%M"
        ]
    ]

Notes
I also tried to get a 24-hour clock formatting without AM/PM with just a localization config but that doesn't seem to be possible at the moment: https://github.com/vega/vega/issues/3116

Thanks for spotting this (I think the object version of format appeared in a recent update that I didn't spot).
I agree we should support multi-format objects for temporal axes. I am keen to keep the expansion of the API to a minimum, so suggest the following, which I think would meet your needs:
axFormats : List (TimeUnit, String) -> AxisProperty

Having a list of time unit and format tuples allows us to reuse TimeUnit without the need for new formatting functions. So your example would be:
pAxis [ axFormats [ ( year, "`%Y" ), ( hours, "kl %-H" ), ( minutes, "%H:%M" ) ] ]

Or perhaps axTimeFormats would be a better name as this only ever applies to temporal formatting (for multiple conditional number formatting we can already use axDataCondition).
Would that work for you?

Yeah, that sounds great!
Thank you for the rapid response!

OK, will implement this now. On balance I think axTemporalFormats is a better name given its time-specific context.

Now available  as axTemporalFormats in version 5.3.0

Wow, that was quick. It works like a charm!
Thank you so much!


XDP program not work well with container's veth

I wanna load XDP program to container’s veth.
Firstly, I created two containers:
docker run -d --name host1 -h host1 exp:v1.0, and
docker run -d --name host2 -h host2 exp:v1.0,
where exp:v1.0 is the image I had created from training/webapp. And now host1 was binded to veth02b9ec2 with IP address <IP_ADDRESS>, and host2 to vethf2e33b9 with ip_addr <IP_ADDRESS>.
My XDP program is as follows:
#include <linux/bpf.h>
#include “bpf_helpers.h”
#define u32 unsigned int
#define u16 unsigned short
#define u64 unsigned long long
SEC(“test_xdp”) int test_xdp_main(struct xdp_md *ctx)
{
return XDP_DROP;
}
char license[] SEC(“license”) = “GPL”;
which means all the arriving packets will be dropped.
Then, I compiled it with clang and loaded it to veth02b9ec2:
clang -O2 -Wall -target bpf -c test_xdp.c -o test_xdp.o, and
ip link set dev veth02b9ec2 xdp obj test_xdp.o section test_xdp verbose.
And the XDP program successfully loaded in veth02b9ec2.
But when I ping <IP_ADDRESS> in host1 whose IP is <IP_ADDRESS>, it seemed that XDP didn’t work at all. However, when I loaded this XDP program in docker0, and ping <IP_ADDRESS> or the address outside the container network at host1, the XDP program worked very well and ping failed.
My iproute2 version is ss180129, clang version is 4.0.0 and docker version is 1.12.6. I hope someone can help me out.

Closing due to exact duplicate of #3077.


Update README.md

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

1 out of 2 committers have signed the CLA.:white_check_mark: @WilliamDavidHarrison:x: @andrewstechYou can retrigger this bot by commenting recheck in this Pull Request

I have read the CLA Document and I hereby sign the CLA


Has Many not working as I expected. Bug or feature?

type Interests []Interest
type Interest struct {
	UserID     int64 `db:"user_id" json:"user_id"`
	InterestID uint8 `db:"interest_id" form:"interest_id" json:"interest_id"`
}
type User struct {
        Interests   Interests   `has_many:"user_interests" fk_id:"user_id"`
}

POP doesn't searches user_interests table, as documented:

Books        Books     has_many:"books" order_by:"title asc"
has_many: will load all records from the books table that have a column named user_id or the column specified with fk_id that matches the User.ID value.

Instead it looks in: "interests". Even if I make the user hold UserInterests UserInterests -> then still it INSERTs into table interests. So it looks like it uses the singular type and adds an S? What is "has_many" used for then?

In your type User do you have a field ID ? Is it a int64 (by default pop is creating UUID for ID, but you can change it of course)?
Making something more reproducible (maybe with the commands you used to generates those models or a link to a project where we can see your code could be useful).
Having only part of your code make it really difficult to debug.

Hi! Thanks for the quick reply. Yes, it has an ID and it is an int64. But the problem is that it guesses the table from the type Interest struct +s and it does not use the has_many as table name. I now renamed that type to UserInterest and it works. The bad thing is that I can not reuse that type to reference from another entity. To store that in another table I would need to create another type.
Sorry but don't have an example at the moment. But is it correct that has_many: should be able to contain the table name where it needs to store/read it from?

are you looking for many-to-many?
this associate involve third table
has_many only support for belongs to between child and parent without third table

@u007 no, I understand what has_many needs to do, but I assumed that the meta data would be used for table name and foreign key but that seems not the case. If I remember correctly, I saw ".id" hardcoded in the code.

@jtorvald, if you mean support for primary_key option, yes this will be interesting option to supp Rt

I will look into making primary_key option


Best way to use SHAP for text without losing word position

Hi,
There are a few comments about using SHAP for text, such as https://github.com/slundberg/shap/issues/40 or the notebook https://slundberg.github.io/shap/notebooks/linear_explainer/Sentiment Analysis with Logistic Regression.html
However, it is still not clear to me what is the best way to input the text.
It seems like with the notebook approach we lose the position of the words. The solution in https://github.com/slundberg/shap/issues/40 was to append the position to the word, but this seems to lose the importance of a single word (which I don't fully understand but I guess it may come from the change in the reference value?). The alternative would be using a 1-hot vector, but it's not clear how to input it. Blindly trying to input a 1-hot vector would raise the following error:
Traceback (most recent call last):
  File "explain_one_hot.py", line 140, in <module>
    shap_values = explainer.shap_values(x_batch_one_hot, nsamples=num_samples)
  File "/home/anaconda2/envs/py27/lib/python2.7/site-packages/shap/explainers/kernel.py", line 179, in shap_values
    assert len(X.shape) == 1 or len(X.shape) == 2, "Instance must have 1 or 2 dimensions!"
AssertionError: Instance must have 1 or 2 dimensions!

@slundberg also mentioned the DeepExplainer (that is now implemented) as a way to deal with all of the above. If that's the case, does anyone have a notebook on how to use it on text?
Thanks,
Oana

Check out https://slundberg.github.io/shap/notebooks/deep_explainer/Keras LSTM for IMDB Sentiment Classification.html


Make the level badge below profile images less black (gray?) on Light theme

I have seen people complain about the badge level badge below profile pictures, I think most of the people that are complaining about it are on the light theme, it probably sticks out a little bit too much in light theme?

Yep, this one is on the list. We also need to decide if we want levels when memberships come...may be confusing with both


Select and pull a devfile using Alizer

What type of PR is this:
/kind feature
What does this PR do / why we need it:

Add an alizer module
Adds support for Alizer in odo init command
Adds support for Alizer in odo deploy command
Remove --context flag from odo deploy command

Which issue(s) this PR fixes:
Fixes #5422
Fixes #5408
PR acceptance criteria:

[x] Unit test

[x] Integration test

[x] Documentation

How to test changes / Special notes to the reviewer:

/test v4.9-integration-e2e
infra errors

/approve


DOC-2828: moves target mgmt up a level, related fixes

fixed images, links, redirects

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


python 2to3 and PEP8 changes for tools.py

I was getting import errors related to some lines in tools.py that were formatted for python2. I've updated using the python 2to3 function, and I went through and made some PEP8 updates for readability.

Armin, does this look ok to you? I was able to successfully import the updated code.


[DOC] Hugepage-2Mi recommended

What's the document you plan to update? Why? Please describe
Hello, teams.
Currently, it has been found that the size setting of hugepage-2mi affects the number of v2 PVC creations. Can you provide a recommended list or calculation formula in the document so that we can understand our own needs and set an appropriate size for hugepage-2mi before using it?
Additional context

cc @shuo-wu @DamiaSan as well


[REQUEST] Implement stop times time and distance verification for a trip

Is your feature request related to a problem? Please describe.
Stop times in a trip should be have increasing time and distance. This is a GTFS rule implemented in Google Python validator as ValidateStopTimesSequenceHasIncreasingTimeAndDistance.
Describe the solution you'd like
Actual Google GTFS validator behaviour : verifies the time and distance travelled at a stop time in a trip is greater than the previous ones. (verifies the stop time and the distance travelled according to the shape)
https://github.com/google/transitfeed/blob/d727e97cb66ac2ca2d699a382ea1d449ee26c2a1/transitfeed/trip.py#L595
Describe alternatives you've considered
Additional context
Line 203 in Error support priorities https://docs.google.com/spreadsheets/d/1vqe6wq7ctqk1EhYkgtZ0_TbcQ91vccfs2daSjn20BLE/edit#gid=0

cc @timMillet
Note that the Python validator allows sequential arrival and departure times in a trip to be the same - so you can have:
1, 12:00:00, 12:00:00
2, 12:10:00, 12:10:00
3, 12:10:00, 12:10:00
4, 12:15:00, 12:15:00

The Python validator only flags times that go backwards in time. This caught us in the GTFS-RT validator, as we initially implemented a rule that said that predictions needed to move forward in time for each stop (see https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/365).
Allowing sequential times being the same dates back to a major scheduling software package called HASTUS rounding times to the nearest minute:
https://github.com/google/transitfeed/blob/d727e97cb66ac2ca2d699a382ea1d449ee26c2a1/transitfeed/trip.py#L733
I don't know for sure if HASTUS still has this issue, although someone flagged that issue with our GTFS-RT validator, so I assume it (or another GTFS exporter) does.
It would be nice to update the validator to be more strict rules for this if the state of the industry allows. If not, we may have to implement some of the same heuristics in the Python validator:

# HASTUS makes it hard to output GTFS with times to the nearest second
# it rounds times to the nearest minute. Therefore stop_times at the
# same time ending in :00 are fairly common. These times off by no more
# than 30 have not caused a problem. See
# https://github.com/google/transitfeed/issues/193
# Show a warning if times are not rounded to the nearest minute or
# distance is more than max_speed for one minute.

Time travel verification is already implemented:

check arrival_time < departure_time
https://github.com/MobilityData/gtfs-validator/blob/1d5dab841bfefbb0c08fd8b45ab2596ee3866244/usecase/src/main/java/org/mobilitydata/gtfsvalidator/usecase/ValidateStopTimeDepartureTimeAfterArrivalTime.java#L31

check bad combination of arrival_time and departure_time of timepoints:
https://github.com/MobilityData/gtfs-validator/blob/12d6ff27de2921ef3858035526de08dc226b4833/usecase/src/main/java/org/mobilitydata/gtfsvalidator/usecase/ValidateBackwardsTimeTravelForStops.java#L30


Friend names and Preferred servant

Preparation

[X] I read the Troubleshooting Guide
[X] My question isn't answered in any other issues (even the closed ones)

Your question
Is there any way to make Automata pick A servant from specific friends?
What I'm trying to do is pick a specific servant with high NP level, since automata doesn't have this feature yet I used to use the Support Image Maker to grab the name of my friends that had said servant at NP3 or above.
But with the implementation of triple supports other servants can appear in the list first, and since automata only checks the friend name it will pick the first servant under that name instead of the one I want.
I'm aware that "Friends Only" is an option in the Preferred section, but that option will pick any friend with that servant, regardless of its NP level.

I guess the only long-term solution is combining Friend selection with Servant and CE selection.
As a workaround, you could try sorting their servants by HP or Attack, but if they swap any servant, FGA will pick the incorrect one again.


cannot run backfill

i can run all the others except the backfill.
when run backfill:

Hmm it looks like the pod is maybe loading a pre-python 3.5 version
Are you using the full kubernetes / tilt setup?

Hmm it looks like the pod is maybe loading a pre-python 3.5 version
Are you using the full kubernetes / tilt setup?

thanks for your reply.
i go step by step in the Readme.

If you run
./mev exec python --version

what do you see?

Python 3.9.9

We were using the default python instead of poetry installed python for the backfill script
This PR fixes the issue: https://github.com/flashbots/mev-inspect-py/pull/200

Fixed - Thanks @simple4016 for reporting!


PBIX instance, Error “A connection cannot be made. Ensure that the server is running.”

Sometimes Tabular Editor gets mixed up and cannot find the correct Port Number for the PBIX file. Sometimes I get the error, “A connection cannot be made. Ensure that the server is running.”.
When I look at the computer processes for the msmdsrv.exe task, there are multiple Local Addresses and different Port Numbers. Why are there multiple port numbers, and how do I connect to the PBIX file when there are multiple ports?  Is there a way to manually enter the port number so Tabular Editor can use the correct port number, instead of the incorrect port number detected? Is it possible to make the PBIX file have only a single local port number?
I don't have this problem all the time.  But it happens from time to time.  Tabular Editor cannot connect when this happens.

Power BI Desktop will use a new port number for each running instance - there is no way to control this, nor can we have multiple PBIX files share the same port number, as each instance of Desktop spins up its own instance of Analysis Services (msmdmsrv.exe).
I'm not able to reproduce the behaviour of Tabular Editor not picking up the correct port numbers. If a port number isn't showing, you can still connect by typing "localhost:xxxxx" in the "Server" field, where "xxxxx" is the port number you want to connect to.

I'm not able to reproduce but I guess the issue may be caused by this hack:
https://github.com/otykier/TabularEditor/blob/494c0198d581882d6d3165f9dc98eb5d6290c817/TabularEditor/UIServices/ManagedIpHelper.cs#L174-L176

Thank you for your response, @albertospelta and @otykier.  I was able to manually enter the connection string as described, “localhost:xxxxx”.  Thanks for sharing this tip.  I'm not having the issue today.  I tried recreating it by restoring the problem file.  It was a composite model (CSV, SQLAZ), and I figured maybe that had something to do with it.  Alas, I was unable to recreate the issue.  The dropdown connection is working today.  If it happens again I will try manually entering the server connection string.

Fixed in 2.9.7


Escaping characters

I could add this to some page:
Escaping ' characters in logical definitions
When a GO term contains ' in its name (e.g. RNA-directed 5'-3' RNA polymerase activity), when you enter it in the logical definition window (even if you auto-complete with tab), Protege won't let you accept because you have introduced extra quotes. You can escape them with \. As in Protegé 5.5, the \ characters will show up in the logical definition, and when hovering over the term in the logical definition, you won't be able to click on it and be redirected to the right go term. However, when you save the relationship is saved correctly. You can double-check by going to the fypo-edit.owl file and seeing that the GO-term (or any term) is mentioned in a relationship.

@matentzn

That would be great @manulera. I just ran into that problem yesterday, actually!

Where should this section go?

reference/protege-tips.md?

I went for protege-faw.md like for git.
https://github.com/OBOAcademy/obook/pull/229

@manulera can this be closed?

Closed with https://github.com/OBOAcademy/obook/pull/229


[WIP] snmp metadata_from_profile

Yes, we definitely need something like this… Keeping track of which metric comes with which profile is a pain, and it should be generated directly from the profiles.
There's a bit of extra logic required because metrics are de-duped with the list of profiles embedded in the description. Also not sure where we want to define things like units and descriptions - profile make sense to have them in the profiles, but YAML doesn't allow inspecting comments. 😕 So we might need e.g. an additional meta field…

/azp run

I think in the end, it might not worth it :)
I'm closing the PR for now.


Electronic structure Fortran projects

Some other projects regarding electronic structure methods. Maybe a few of them are interesting as well, let me know and I will collect the necessary meta data.

name
url

DFT-D4
https://github.com/dftd4/dftd4

ELPA
https://gitlab.mpcdf.mpg.de/elpa/elpa

ELSI
https://gitlab.com/elsi_project/elsi_interface

FortJSON
https://gitlab.com/elsi_project/fortjson

libnegf
https://github.com/libnegf/libnegf

NTPoly
https://github.com/william-dawson/NTPoly

MBD
https://github.com/jhrmnn/libmbd

mpifx
https://github.com/dftbplus/mpifx

OpenMolcas
https://gitlab.com/Molcas/OpenMolcas

scalapackfx
https://github.com/dftbplus/scalapackfx

@awvwgk I would suggest to add any that have Fortran as the main programming language.


Support BYE response status

This example code:
fn main() {
    print!("{}", fetch_inbox_top().unwrap().unwrap());
}

fn fetch_inbox_top() -> imap::error::Result<Option<String>> {
    let domain = "imap.wp.pl";
    let tls = native_tls::TlsConnector::builder().build().unwrap();

    // we pass in the domain twice to check that the server's TLS
    // certificate is valid for the domain we're connecting to.
    let client = imap::connect((domain, 993), domain, &tls).unwrap();

    // the client we have here is unauthenticated.
    // to do anything useful with the e-mails, we need to log in
    let mut imap_session = client
        .login("<USERNAME>", "<PASSWORD>")
        .map_err(|e| e.0)?;

    // we want to fetch the first email in the INBOX mailbox
    imap_session.select("INBOX")?;

    // fetch message number 1 in this mailbox, along with its RFC822 field.
    // RFC 822 dictates the format of the body of e-mails
    let messages = imap_session.fetch("1", "RFC822")?;
    let message = if let Some(m) = messages.iter().next() {
        m
    } else {
        return Ok(None);
    };

    // extract the message's body
    let body = message.body().expect("message did not have a body!");
    let body = std::str::from_utf8(body)
        .expect("message was not valid utf-8")
        .to_string();

    // be nice to the server and log out
    imap_session.logout()?;

    Ok(Some(body))
}

throws exception on the statement imap_session.logout()?;:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Parse(Invalid([97, 52, 32, 66, 89, 69, 32, 73, 77, 65, 80, 52, 114, 101, 118, 49, 32, 83, 101, 114, 118, 101, 114, 32, 108, 111, 103, 103, 105, 110, 103, 32, 111, 117, 116, 13, 10]))'

After decoding content of Parse(Invalid([...])) as ASCII:
a4 BYE IMAP4rev1 Server logging out

It looks like the BYE response status is not supported.

That certainly seems unintended! Does this happen with the latest alpha? My guess here is that the logout command generates a BYE response, which is technically an error response, but in the specific case of logout it isn't. Can you verify that that is indeed where the error occurs by changing .logout()? to .logout().unwrap(), and then seeing that the panic points to that line? Perhaps we should special-case handling BYE in logout @mordak?

Hm. I cannot reproduce on master, but it could also just be a difference between servers. I am working with Dovecot.
@piotrwalkusz1 : Can you enable debugging on the session? It's just adding imap_session.debug = true; before the imap_session.logout()?; line in your example there. When I do this, I get:
C: a4 LOGOUT
S: * BYE Logging out
S: a4 OK Logout completed (0.001 + 0.000 secs).

And this doesn't throw an error for me - it returns normally. But a different server could give something different.
@jonhoo We could certainly add a check for BYE in logout() specifically. That should be easy.

Today I confirmed that the error occurs on version "3.0.0-alpha.4" on line imap_session.logout(). I run this code:
fn main() {
    print!("{}", fetch_inbox_top().unwrap().unwrap());
}

fn fetch_inbox_top() -> imap::error::Result<Option<String>> {

    let client = imap::ClientBuilder::new("imap.wp.pl", 993).native_tls()?;

    // the client we have here is unauthenticated.
    // to do anything useful with the e-mails, we need to log in
    let mut imap_session = client
        .login("<USERNAME>", "<PASSWORD>")
        .map_err(|e| e.0)?;

    // we want to fetch the first email in the INBOX mailbox
    imap_session.select("INBOX")?;

    // fetch message number 1 in this mailbox, along with its RFC822 field.
    // RFC 822 dictates the format of the body of e-mails
    let messages = imap_session.fetch("1", "RFC822")?;
    let message = if let Some(m) = messages.iter().next() {
        m
    } else {
        return Ok(None);
    };

    // extract the message's body
    let body = message.body().expect("message did not have a body!");
    let body = std::str::from_utf8(body)
        .expect("message was not valid utf-8")
        .to_string();

    // be nice to the server and log out
    imap_session.debug = true;
    imap_session.logout().unwrap();

    Ok(Some(body))
}

and get:
C: a4 LOGOUT
S: a4 BYE IMAP4rev1 Server logging out
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Parse(Invalid([97, 52, 32, 66, 89, 69, 32, 73, 77, 65, 80, 52, 114, 101, 118, 49, 32, 83, 101, 114, 118, 101, 114, 32, 108, 111, 103, 103, 105, 110, 103, 32, 111, 117, 116, 13, 10]))', src/main.rs:35:27
stack backtrace:
   0: rust_begin_unwind
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/std/src/panicking.rs:493:5
   1: core::panicking::panic_fmt
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/core/src/panicking.rs:92:14
   2: core::result::unwrap_failed
             at /rustc/53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b/library/core/src/result.rs:1355:5
   3: core::result::Result<T,E>::unwrap
             at /home/piotr/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/result.rs:1037:23
   4: imap_test::fetch_inbox_top
             at ./src/main.rs:35:5
   5: imap_test::main
             at ./src/main.rs:2:18
   6: core::ops::function::FnOnce::call_once
             at /home/piotr/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Ah, the difference seems to be that in your case @mordak, the response is untagged:
S: * BYE Logging out

Whereas in @piotrwalkusz1's case, it's tagged:
S: a4 BYE IMAP4rev1 Server logging out

Hmm. That behaviour is explicitly against the RFC, which says the BYE MUST be untagged.
But special casing this is kind of easy, so I don't see why we can't do it.
@piotrwalkusz1 Do you know what server this is? We can comment it so future us remembers why we have the special case.

https://www.wp.pl/ is a popular Polish email server. Unfortunately, I don't know what software they use.


feat: 🎸 Remove material-ui

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Consistently use record.new_record?.

be_a_new(model_class) and be_new_record were
inconsistent in that one of them checked !persisted?
and one checked new_record?. The docs also said that
both checked !persisted? even only one did.
This changes both to use new_record? and to be documented
as such.
Fixes #1801.
Note that I'm not sure this is the right fix but I figured I'd offer to get the conversation on #1801 rolling.  My book has an rspec-rails cheat sheet and documents the current inconsistency which is confusing some readers, so I'd like to get this fixed by publication if possible.
/cc @rspec/rspec

LGTM


Cast

Codecov Report

Merging #170 (769aee0) into master (7267fd4) will decrease coverage by 0.00%.
The diff coverage is 89.09%.

@@            Coverage Diff             @@
##           master     #170      +/-   ##
==========================================
- Coverage   91.87%   91.86%   -0.01%
==========================================
  Files         117      117
  Lines       13251    13269      +18
==========================================
+ Hits        12174    12190      +16
- Misses       1077     1079       +2

Impacted Files
Coverage Δ

unified_planning/model/state.py
77.77% <33.33%> (ø)

unified_planning/__init__.py
35.71% <40.00%> (+2.38%)
:arrow_up:

unified_planning/interop/to_tarski.py
78.06% <72.00%> (-0.36%)
:arrow_down:

...fied_planning/engines/compilers/tarski_grounder.py
93.50% <100.00%> (-0.09%)
:arrow_down:

unified_planning/engines/factory.py
82.05% <100.00%> (+0.71%)
:arrow_up:

unified_planning/engines/plan_validator.py
91.04% <100.00%> (ø)

unified_planning/interop/from_tarski.py
85.54% <100.00%> (ø)

unified_planning/io/pddl_reader.py
82.65% <100.00%> (-0.04%)
:arrow_down:

unified_planning/io/pddl_writer.py
88.56% <100.00%> (+0.06%)
:arrow_up:

unified_planning/model/htn/hierarchical_problem.py
69.56% <100.00%> (ø)

... and 8 more

Continue to review full report at Codecov.

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


make back arrow in settings visible

I noticed you ported my previous change back into the Style.css file, so I changed both files this time. I don't see a build process, so I hope that's helpful. Also thanks for responding so quickly! :+1:
Before:

After:

Original:

Thank you for fixing this bug.
How did you record such small animated GIFs?

I use peek on Ubuntu. https://github.com/phw/peek
Thanks for the quick merge!


refactor(claim): disable register button if not enough ae

Tested, LGTM.

depends on https://github.com/aeternity/aepp-sdk-js/issues/1328

fixed in https://github.com/aeternity/superhero-wallet/pull/2186


setResource is broken when the resource contains only 1 data element

$resource = new Nocarrier\Hal('/post/1',[/*some data here*/]);
$author = new Nocarrier\Hal('/user/1', [
    'name' => 'John',
]);
$resource->setResource('user', $author);

$resource->asJson();

Will fail with Notice: Undefined offset: 0 here:
if (count($embedded) === 1 && !in_array($rel, $resource->getArrayResourceRels())) {
    $embedded = $embedded[0];
}

This fails because:

$author only contains 1 field, which triggers the condition count($embedded) === 1
setResource does not register refs in arrayResourceRels, which triggers the condition !in_array($rel, $resource->getArrayResourceRels())

I don't fully understand the logic here, so I'm not sure what the solution is, but it was extremely confusing to find out that having a resource with a single field was not supported. I had to add a second (unnecessary) field to make it work.

The reason for this is to (by default) prevent a single resource from being added as an array. I'll try to reproduce the issue and provide a fix for it.

Yeah ok - having actually read the code this is the same bug that was fixed in #49. But this was not merged into master. I have created a new release, 0.9.12 that contains the fix. If you update your composer.json you should be good.

Thanks!


smart contract Getter method undefined in Reactjs

I am getting the below error while I was calling my getter method in componentDidMount(){}. Below is the error description and my app.js component. Any idea or any help on the below issue:

Uncaught (in promise) TypeError: Cannot read property 'getMsg' of undefined
at App._callee$ (App.js:26)
at tryCatch (runtime.js:62)
at Generator.invoke [as _invoke] (runtime.js:296)
at Generator.prototype.(:3000/anonymous function) [as next] (http://localhost:3000/static/js/bundle.js:42838:21)
at step (App.css?9a66:26)
at App.css?9a66:26
at new Promise ()
at App. (App.css?9a66:26)
at App.componentDidMount (App.js:29)
at commitLifeCycles (react-dom.development.js:14248)
at commitAllLifeCycles (react-dom.development.js:15342)
at HTMLUnknownElement.callCallback (react-dom.development.js:100)
at Object.invokeGuardedCallbackDev (react-dom.development.js:138)
at invokeGuardedCallback (react-dom.development.js:187)
at commitRoot (react-dom.development.js:15481)
at completeRoot (react-dom.development.js:16496)
at performWorkOnRoot (react-dom.development.js:16440)
at performWork (react-dom.development.js:16358)
at performSyncWork (react-dom.development.js:16330)
at requestWork (react-dom.development.js:16230)
at scheduleWork$1 (react-dom.development.js:16096)
at scheduleRootUpdate (react-dom.development.js:16663)
at updateContainerAtExpirationTime (react-dom.development.js:16690)
at updateContainer (react-dom.development.js:16717)
at ReactRoot../node_modules/react-dom/cjs/react-dom.development.js.ReactRoot.render (react-dom.development.js:17000)
at react-dom.development.js:17140
at unbatchedUpdates (react-dom.development.js:16557)
at legacyRenderSubtreeIntoContainer (react-dom.development.js:17136)
at Object.render (react-dom.development.js:17195)
at Object../src/index.js (index.js:7)
at webpack_require (bootstrap 23e77afa643c168e549a:678)
at fn (bootstrap 23e77afa643c168e549a:88)
at Object.0 (registerServiceWorker.js:117)
at webpack_require (bootstrap 23e77afa643c168e549a:678)
at ./node_modules/ansi-regex/index.js.module.exports (bootstrap 23e77afa643c168e549a:724)
===============================================
My app.js file :
import React, { Component } from 'react';
import logo from './logo.svg';
import './App.css';
import Web3 from 'web3';
//import web3 from './web3';
//import Allo from './AlloWorld';
//const provider = new Web3.providers.HttpProvider('http://localhost:7545');
const myweb3 = new Web3(new Web3.providers.HttpProvider("http://<IP_ADDRESS>:7545"));
const address = '0x3d49d1ef2ade060a33c6e6aa213513a7ee9a6241';
const abi = [{"constant":true,"inputs":[],"name":"getMsg","outputs":[{"name":"","type":"string"}],"payable":false,"stateMutability":"view","type":"function"},{"constant":false,"inputs":[{"name":"inmsg","type":"string"}],"name":"setMsg","outputs":[],"payable":false,"stateMutability":"nonpayable","type":"function"},{"constant":true,"inputs":[],"name":"message","outputs":[{"name":"","type":"string"}],"payable":false,"stateMutability":"view","type":"function"},{"inputs":[],"payable":false,"stateMutability":"nonpayable","type":"constructor"}];
const myinstance = myweb3.eth.contract(address,abi);
//const myinstance = myweb3.eth.contract(abi).at(address);
class App extends Component {
constructor(props){
super(props);
this.state = {
mymsg:'test'
};
}
async componentDidMount(){
console.log(myinstance);
const mymsg = await myinstance.methods.getMsg().call();
console.log('return is:');
console.log(mymsg);
}
render() {
//console.log(web3.version.api);
return (

return from blockchain is : {this.state.mymsg}

);

}
}
export default App;

myinstance.methods is null.

This doesn’t look related to Create React App itself so I’ll close.

Hi,
If myinstance.methods is null, then how to verify and fix it?

From: Joe Haddad<EMAIL_ADDRESS>Sent: Friday, May 25, 2018 8:36 AM
To: facebook/create-react-app
Cc: cnusrini; Author
Subject: Re: [facebook/create-react-app] smart contract Getter method undefined in Reactjs (#4516)
myinstance.methods is null.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/create-react-app/issues/4516#issuecomment-392059797, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATQwMJ_oDuVqGAbm79l_FPtt-N9-skgmks5t2AjzgaJpZM4UNogl.

You didn't provide enough information for us to help you with that, you'd need to provide a more complete example.
I suggest you ask this question (and others like it) on various, excellent community resources.
Good luck!

You can read the docs here, tho: https://web3js.readthedocs.io/en/1.0/web3-eth-contract.html
It looks like you need to do the following:
const myinstance = new myweb3.eth.Contract(abi, address);

Hi Joe,
Thank you for the response.
I have followed the same steps as you have captured in the 2 part series .
But, let me share my project so that you can help be better.

From: Joe Haddad<EMAIL_ADDRESS>Sent: Friday, May 25, 2018 9:33 AM
To: facebook/create-react-app
Cc: cnusrini; Author
Subject: Re: [facebook/create-react-app] smart contract Getter method undefined in Reactjs (#4516)
You can read the docs here, tho: https://web3js.readthedocs.io/en/1.0/web3-eth-contract.html
web3.eth.Contract — web3.js 1.0.0 documentationhttps://web3js.readthedocs.io/en/1.0/web3-eth-contract.html
web3js.readthedocs.io
Creates a new contract instance with all its methods and events defined in its json interface object.
It looks like you need to do the following:
const myinstance = new myweb3.eth.Contract(abi, address);
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/create-react-app/issues/4516#issuecomment-392076845, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATQwMCeUWEwLqqQvKJsNcmvUGRqI0KIZks5t2BY9gaJpZM4UNogl.


Dynamic evaluation of GroupBy Initial Capacity

Summary
For GroupBy queries, the default size of the GroupByResultHolder is set to 10K, which can lead to inefficient resource usage in cases where fewer group-by keys are expected, such as in queries with highly selective filters.
select column1, sum(column2) from testTable where column1 in ("123") group by column1 limit 20000
Description
This update dynamically adjusts the initial capacity of the GroupByResultHolder based on the filter predicates for such queries. By aligning the result holder size with the filter, we aim to optimize resource allocation and improve performance for filtered group-by queries.
Testing

Benchmark                              (_numRows)                                                                                (_query)  (_scenario)  Mode  Cnt   Score   Error  Units
BenchmarkMaxGroupByResultHolder.query     1500000  SELECT INT_COL, COUNT(*) FROM MyTable WHERE INT_COL IN (0, 1, 2) GROUP BY INT_COL LIMIT 10000     EXP(0.5)  avgt  100  12.355 ± 0.178  ms/op

Codecov Report
Attention: Patch coverage is 0% with 18 lines in your changes missing coverage. Please review.

Project coverage is 27.93%. Comparing base (59551e4) to head (d6e0cae).
Report is 1036 commits behind head on master.

Files with missing lines
Patch %
Lines

...ry/aggregation/groupby/DefaultGroupByExecutor.java
0.00%
18 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (d6e0cae). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (d6e0cae)

integration
7
0

integration2
3
0

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
0

unittests
5
1

unittests1
2
0

java-11
5
0

unittests2
3
1

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14001       +/-   ##
=============================================
- Coverage     61.75%   27.93%   -33.82%
- Complexity      207      213        +6
=============================================
  Files          2436     2613      +177
  Lines        133233   143286    +10053
  Branches      20636    21998     +1362
=============================================
- Hits          82274    40026    -42248
- Misses        44911   100179    +55268
+ Partials       6048     3081     -2967

Flag
Coverage Δ

custom-integration1
?

integration
?

integration1
?

integration2
?

java-11
?

java-21
27.93% <0.00%> (-33.70%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
27.93% <0.00%> (+0.20%)
:arrow_up:

temurin
27.93% <0.00%> (-33.82%)
:arrow_down:

unittests
27.93% <0.00%> (-33.82%)
:arrow_down:

unittests1
?

unittests2
27.93% <0.00%> (+0.20%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

These queries are very uncommon, and I don't know if it is worth taking the overhead for all group-by queries. Alternatively, we might just add a query option to override the initial capacity if desired

These queries are very uncommon, and I don't know if it is worth taking the overhead for all group-by queries. Alternatively, we might just add a query option to override the initial capacity if desired

Thanks you for your input! We currently optimize this behavior specifically for GROUP BY queries with filters, and based on our limited performance testing, the overhead was comparable. However, I see your concern and can certainly add a query option to enable this optimization

Discussed offline. I think a more general problem here is when we group by on columns that partially/none have constraints (in filter clause), but themselves low cardinality. @praveenc7 could you maybe try to explore if it is easy to do some thing like min(cartesian_product, default_min_value). The cartesian_product part can be product of the in/eq filter size or column cardinality? In this sense I feel it would probably more generally applicable. In https://github.com/apache/pinot/pull/9420/files we made some of the cardinality accessible, you can maybe take a look.

@jasperjiaguo Looking more closer at the code, it looks like this condition is already handled inDictionaryBasedGroupKeyGenerator and when intializing the size we do we the min(cardinality_product, default_product) in DefaultGroupByResultHolder

@praveenc7 I see, thanks for checking! I think the only (small) gap here is that when we have
select ... where A in (a1, a2, a3) group by A,B

Do we currently handle this mixture of bounded + unbounded?
ideally the effective card estimation could be calculated with cardinality_product/card(A) * filterlen(A)

@praveenc7 I see, thanks for checking! I think the only (small) gap here is that when we have
select ... where A in (a1, a2, a3) group by A,B

Do we currently handle this mixture of bounded + unbounded? ideally the effective card estimation could be calculated with cardinality_product/card(A) * filterlen(A)

@jasperjiaguo  Agree this might create a more tighter bound, currently the cardinality is available for DictionaryBasedGroupKey so the unbounded case would be mostly applicable to this, might need some more change to support this. Was thinking of doing in a follow up PR

Let's think about the edge case of
select ... where (A in (a1, a2, a3) or C > c) group by A

Let's think about the edge case of
select ... where (A in (a1, a2, a3) or C > c) group by A

@jasperjiaguo Added condition that checks for top-level AND and also added mixed support for both bounded & unbounded


GitLens was unable to find Git. Please make sure Git is installed. Also ensure that Git is either in the PATH, or that 'git.path' is pointed to its installed location. Can't fix it..

GitLens Version: 9.5.1
VSCode Version: 1.32.2
OS Version: 10.14.3 Mojave
Tried xcode-select --install, installed it but still the error.
Tried sudo xcodebuild -license agreed and still got the error.
I can't seem to find the problem here

Fixed! In the Settings I put in the search bar this line "git.path": "/usr/bin", clicked on edit in settings.json and added this line:
"git.path": "/usr/bin"/


Gradle 6 deprecation warnings

Running jdeps under Gradle 6 results in the following warnings:
> Task :backend:jdeps
Property 'failOnError' has redundant getters: 'getFailOnError()' and 'isFailOnError()'. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'jdkinternals' has redundant getters: 'getJdkinternals()' and 'isJdkinternals()'. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'profile' has redundant getters: 'getProfile()' and 'isProfile()'. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'recursive' has redundant getters: 'getRecursive()' and 'isRecursive()'. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'summary' has redundant getters: 'getSummary()' and 'isSummary()'. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.
Property 'failures' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.

Fixed with release 0.8.0.


[BACKLOG-35866] VariableSubstitution for pvfs

:x: Build failed in 6m 26s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
core,plugins/connections/ui,plugins/file-open-save-new/api,plugins/file-open-save-new/core

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message

:x: Build failed in 9m 40s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
core,plugins/connections/ui,plugins/file-open-save-new/api,plugins/file-open-save-new/core,ui

:exclamation: No tests found!
Errors:
Filtered log (click to expand)

script returned exit code 1

:information_source:  This is an automatic message

:x: Build failed in 29s
Build command:
mvn clean verify -B -e -Daudit -amd

:exclamation: No tests found!
:information_source:  This is an automatic message

:white_check_mark: Build finished in 9m 27s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
core,plugins/connections/ui,plugins/file-open-save-new/api,plugins/file-open-save-new/core,ui

:exclamation: No tests found!
:information_source:  This is an automatic message


Fix minor bugs and tidy up existing work on new views

Just fixing some bugs and inconsistencies I found while going through the new views.

Looks like the acceptance tests are failing because of some asset build issue. Can take a look later on.


Update Prometheus common

Oauth2 supports proxy URL
HTTP2 can be disabled

Signed-off-by: Julien Pivotto<EMAIL_ADDRESS>

Test error seems real.

Tests are fixed


Cannot set status bar color and autohide on Android

Godot version
3.3.4
System information
Windows 10
Issue description
I need status bar to be visible all time, not only after swipe from top and make it blue color. (I have @color/blue in the another .xml, its ok)
I`v tried to add:
<item name="statusBarColor">@color/blue</item>
in android/build/res/values/themes.xml. Nothing happend.
The other problem is, that with selected"Immersive mode" it also shows the navigation bar. Need just a status bar. Is it a bug? I cannot show just a status bar without navigation bar?
Steps to reproduce
Start some Android emulator with notch, for example "Pixel 3 XL API 30" by Android studio -> go to android/build/res/values/themes.xml and remove .Fullscreen from  -> switch on immersive mode in export -> build on Android
Minimal reproduction project
No response

Related to https://github.com/godotengine/godot/issues/48811.


The problem with absent value attribute

I'm using vee-validate and I'm binding the value like this :value="someValue". The problem is that vee-validate checks only changes of value attribute. The main issue is when someValue is empty then the attribute will not appear at all! That means that the first time user changes input the value sets and only after second change it will be checked by vee-validate.
To fix the issue I had to set the value without v-bind like this:
<input type="text" :name="someName" value="" />
And then change the value with pure js

For package to work correctly it needs to treat the absence of value attribute the same as value=""

The v-validate directive does not check the value attribute, it relies on events to report the input value, and it uses the DOM API to do so so absent values should not pose a problem.
This could be related to another known issue of the directive
I suggest you try using ValidationProvider component instead as it doesn't have the downsides of the directive.


Method to run recipe

Create method to run recipe directly from Python scipt

fixed in pull request #8


Change vendoring script to bash from sh

Change to bash for compatibility with bash, zsh, fish, etc.

Ok so can't merge it from phone, @cdrage you do the honour!


Remove displayedLayers

This feels redundant and ends up breaking situations where you have multiple timelines on a map. If displayedLayers is kept it would be good to know what purpose it serves.

One test failing because it used displayedLayers but I've made a change to fix it.


deriving Equals() uses class comparison on final classes

Imho, this part could be omitted when using the "final" statement on classes / VO's
 if (\get_class($this) !== \get_class($otherCartItem)) {
            return false;
        }

I know, and next week someone complains there are final and cannot be extended... :) You can't satisfy all.

Ist there a manual possibility to mark classes non-final?
Sascha-Oliver Prolic<EMAIL_ADDRESS>schrieb am Do., 9. Aug.
2018, 16:42:

I know, and next week someone complains there are final and cannot be
extended... :) You can't satisfy all.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prolic/fpp/issues/82#issuecomment-411782093, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAJI-K5HozH5expWCwIM0l-6eWjb6fzQks5uPEpKgaJpZM4V1aAf
.

Will do when I have time, feel free to submit a PR.


Program page: Filter and highlight indicators not on track

NOTE: This ticket is dependent on queries described in ticket #463. This is an instance of the "band of variance" component #577
Story
When I learn the percentage of program indicators that are within target range, I want to zoom in on the indicators that are NOT within the target range, so that I can quickly dig into the data and see whether a course correction is in order.

Acceptance criteria
The "indicators on track" metric includes two links:

Percentage of indicators that are > 15% above target
Percentage of indicators that are > 15% below target

When you click either of these two links, the following occurs:

[x] The list of indicators refreshes to display only the ones that meet the criteria.
[x] The filtered list is visually connected to the metric, so that it's obvious you're looking at a subset of the total, and how that subset was determined. (Doesn't need to be a yellow box of course -- just my 2-second solution.)
[x] The "# indicators" header refreshes to read "## indicators are > 15% above target" or "## indicators are > 15% below target".  I suggest we use the same warning icon up top and next to this string, to further reinforce the visual connection.
[x] The "Add indicator" button is replaced with a "Show all indicators" button that restores the full list.

Housekeeping

[ ] Unit test written
[ ] i18n strings included

Pull request #712 includes the query logic for identifying these indicators, when it's merged it can be wired up to the filter logic

I would think hiding them with JS would be a heck of a lot faster.

They're all there already, we can hide them with JQuery
We could even piggyback on Bootstrap, e.g. Tabs

Makes sense - I'll add data- elements for the various filter items and then
one of us can add the jQuery hide logic
Thanks!
Cameron McFee

On Thu, Oct 25, 2018 at 4:05 PM PJ Souders<EMAIL_ADDRESS>wrote:

> They're all there already, we can hide them with JQuery
>
> We could even piggyback on Bootstrap, e.g. Tabs
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub
> <https://github.com/mercycorps/TolaActivity/issues/561#issuecomment-433234365>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AHks6yp1QcNdCrbuiGM2GxO4ynLr1cnsks5uokPDgaJpZM4V-8Kg>
> .
>

This is probably not the right place for this, but here's how I've built the layout for gauges per our convo this morning:

@camgnostic Just noticed in passing, as I was testing a different ticket: The "unavailable" filter has some issues.

Even though 13% are unavailable, no indicators show up when I click to filter.
It's a bit inconsistent to reproduce. For example, in the Afghanistan program WUA Capacity Building and Strengthening, I get one indicator when I click on "9% unavailable". However, the number of indicators is not filled in in the "X indicators have data unavailable string.
I am not going to move the ticket into Failed QA because Marie is the assigned tester and might find additional issues.

Actually, rereading the ticket, I don't see any requirement for "Unavailable to be a filter at all -- only the two 15% above and below target metrics.
So I think the easy fix is: Unlink the "unavailable" metric. Only the tooltip is clickable.

that's super easy. I spiked it in commit 62b60f7. But is this is a potentially useful filter — “show me all my indicators that are nonspecifically janky”
Also curious as to the biz logic behind what is a “nonreporting” indicator (or “data unavailable” or whatever)

that's super easy. I spiked it in commit 62b60f7. But is this is a potentially useful filter — “show me all my indicators that are nonspecifically janky”

The problem I see with an "unavailable" filter is that it's a sort of mystery meat filter, and you have to become a detective, unnecessarily. Unnecessarily because data can be unavailable for totally fine reasons, like the first target period not yet being comleted. Or it might be that you are in fact behind on your M&E tasks... but which one/s for any given indicator? The other three filters cover that.

Also curious as to the biz logic behind what is a “nonreporting” indicator (or “data unavailable” or whatever)

Do you mean why we have that gray section of the graph at all? I think just to visually account for the indicators that don't fall into any of the other three buckets.
As for the terminology, I did a little research and found that "non-reporting" has a very specific meaning from an NGO accounting standpoint, and usually refers to an entire organization, not an indicator. Like, "This NGO is non-reporting because it doesn't meet these criteria and so it is not required to report to the IRA." I think "unavailable" is more neutral, and our tool-tip explains what circumstances lead to that designation.

Validated -- "Unavailable" no longer works as a filter, just plain text.


fix CI related failures

This PR makes a change to fix the ceph and other repository related errors.
Fixes #703

This is probably quicker to check on a local machine. Everything should be fine if the provisioning succeeds.

@dojacobs @jojimt @rhim The status of this PR is green. Please take a look when you have the time.


Fix missing close on t_gender

Regenerating the survey causes the following:
[9/14] survey.sociodemography FAIL
Traceback (most recent call last):
File "/home/vagrant/international-survey-2018/lib/run.py", line 40, in run
importlib.import_module(m).run()
File "/home/vagrant/international-survey-2018/lib/report.py", line 79, in func
(Path(REPORT_PATH) / (filename)).write_text(chevron.render(fp, report))
File "/home/vagrant/international-survey-2018/venv/lib/python3.8/site-packages/chevron/renderer.py", line 308, in render
for tag in tokens:
File "/home/vagrant/international-survey-2018/venv/lib/python3.8/site-packages/chevron/tokenizer.py", line 220, in tokenize
raise ChevronError('Trying to close tag "{0}"\n'
chevron.tokenizer.ChevronError: Trying to close tag "countries"
This PR fixes a mislabelled {{#t_gender}} which should be {{/t_gender}} in templates/sociodemography.md.

Thanks!


Dynamic offset for Affix is not actually dynamic

I was trying to set a dynamic offset using a function for the Affix plugin, but it seems to me that the value is only dynamic the very first time setPosition is called. I wasn't sure if this was done intentionally or if it is a bug.
If you follow the Affix documentation and example and set a top or bottom offset to a function like so:
$('#myAffix').affix({
  offset: {
    top: 100,
    bottom: function () {
      return (this.bottom = $('.footer').outerHeight(true))
    }
  }
})

I would expect that every time setPosition is called when I scroll, it will evaluate the bottom offset to be $('.footer').outerHeight(true).
I then stepped through Affix's checkPosition() (relevant snippet below).
var offset       = this.options.offset
var offsetTop    = offset.top
var offsetBottom = offset.bottom
var scrollHeight = $('body').height()

if (typeof offset != 'object')         offsetBottom = offsetTop = offset
if (typeof offsetTop == 'function')    offsetTop    = offset.top(this.$element)
if (typeof offsetBottom == 'function') offsetBottom = offset.bottom(this.$element)

var affix = this.getState(scrollHeight, height, offsetTop, offsetBottom)

I noticed that the FIRST time this is run,
var offsetBottom = offset.bottom

sets offsetBottom to the function that was defined above.
However, when
if (typeof offsetBottom == 'function') offsetBottom = offset.bottom(this.$element)

is run, the function is overwritten by the return value, which is an integer. The problem I am seeing is that this line overwrites the value in this.options.offset. On subsequent calls of checkPosition, this.options.offset.bottom is the integer value, and the function I had originally defined is never called again.
I was wondering if there could be clarification if this was intended behavior or a bug. Thanks!

I think I figured this out. To get the behavior I wanted, offset bottom should just not set itself to the return value.
In other words
bottom: function () {
      return ($('.footer').outerHeight(true))
    }

instead of
bottom: function () {
      return (this.bottom = $('.footer').outerHeight(true))
    }


Registry S3 driver failed to upload images to Swift3 (S3 compatible API entry) with both v2 and v4 signature

In my testing with registry 2, 2.6, 2.6.1. The s3 drvier doesn't work properly with OpenStack Swift's S3 API.
With v2, the push image always got http: no Host in request URL error.
root@ubuntu1404-base:~# docker push localhost:5000/bbox
The push refers to a repository [localhost:5000/bbox]
3a1dff9afffd: Pushing [==================================================>]  1.309MB
http: no Host in request URL

For S3 v4 signature, the Invalid path: http%3A//<IP_ADDRESS>%3A80/docker-s3/docker/reg one comes from the aws-go-sdk that we discovered and reported to aws-go-sdk before. It was fixed in aws-go-sdk 1.5+. I pulled the latest docker registry and it's using go sdk 1.2.4 which has this issue. The AWS S3 can handle the encoded path but not Swift's Swift3 API. https://github.com/aws/aws-sdk-go/issues/944
v2 signature registry instance configuration as below.
root@ubuntu1404-base:~# cat registry-container/local-aws-config.yml
version: 0.1
log:
  level: debug
  accesslog:
    disabled: false
fields:
  service: registry
storage:
  cache:
    blobdescriptor: inmemory
  s3:
    accesskey: docker
    secretkey: 847093a6840a944244c69eedcf379e4a
    region: US
    regionendpoint: http://rrdns.openstack.com.tw
    bucket: docker-s3
    encrypt: false
    #keyid:
    secure: false
    v4auth: false
    chunksize: 5242880
    multipartcopychunksize: 33554432
    multipartcopymaxconcurrency: 100
    multipartcopythresholdsize: 33554432
    rootdirectory: /
http:
  addr: :5000
  headers:
    X-Content-Type-Options: [nosniff]
health:
  storagedriver:
    enabled: true
    interval: 10s
    threshold: 3

v4 signature registry instance configuration as below :
version: 0.1
log:
  level: debug
  accesslog:
    disabled: false
fields:
  service: registry
storage:
  cache:
    blobdescriptor: inmemory
  s3:
    accesskey: docker
    secretkey: 847093a6840a944244c69eedcf379e4a
    region: us-east-1
    regionendpoint: rrdns.openstack.com.tw
    bucket: docker-s3
    encrypt: false
    #keyid:
    secure: false
    v4auth: true
    chunksize: 5242880
    multipartcopychunksize: 33554432
    multipartcopymaxconcurrency: 100
    multipartcopythresholdsize: 33554432
    rootdirectory: /
http:
  addr: :5000
  headers:
    X-Content-Type-Options: [nosniff]
health:
  storagedriver:
    enabled: true
    interval: 10s
    threshold: 3

From the commits logs, the aws-go-sdk was bumped to 1.6+. We gave a quick test by building the registry binary from the master of this repository on mac. Then run the registry server from mac.
The s3 driver with v4 signature works for Swift's S3 API. May I know the release cycle of registry image in official docker hub?

I just built docker registry with ws-sdk-go/1.6.12 and go1.8.1 on my mac and it's running well with v4auth: true. But I have the same issue in v4auth: false.

Closing as wildly outdated. Besides, the Swift driver has been deprecated in the latest release and is no longer supported.


Compilation fails in master Cuda 10.1 GCC 7.4 Ubuntu 18.04

Description

[74/524] Building NVCC (Device) object CMakeFiles/cuda_compile_1.dir/src/operator/contrib/cuda_compile_1_generated_bounding_box.cu.o
FAILED: CMakeFiles/cuda_compile_1.dir/src/operator/contrib/cuda_compile_1_generated_bounding_box.cu.o
cd /home/piotr/mxnet_master/build/CMakeFiles/cuda_compile_1.dir/src/operator/contrib && /usr/local/bin/cmake -E make_directory /home/piotr/mxnet_master/build/CMakeFiles/cuda_compile_1.dir/src/operator/contrib/. && /usr/local/bin/cmake -D verbose:BOOL=OFF -D build_configuration:STRING=Debug -D generated_file:STRING=/home/piotr/mxnet_master/build/CMakeFiles/cuda_compile_1.dir/src/operator/contrib/./cuda_compile_1_generated_bounding_box.cu.o -D generated_cubin_file:STRING=/home/piotr/mxnet_master/build/CMakeFiles/cuda_compile_1.dir/src/operator/contrib/./cuda_compile_1_generated_bounding_box.cu.o.cubin.txt -P /home/piotr/mxnet_master/build/CMakeFiles/cuda_compile_1.dir/src/operator/contrib/cuda_compile_1_generated_bounding_box.cu.o.Debug.cmake
/home/piotr/mxnet_master/include/dmlc/./thread_local.h: In instantiation of ‘static T* dmlc::ThreadLocalStore<T>::Get() [with T = std::unordered_set<std::__cxx11::basic_string<char> >]’:
/home/piotr/mxnet_master/src/operator/contrib/./../../common/utils.h:461:28:   required from here
/home/piotr/mxnet_master/include/dmlc/./thread_local.h:46:15: error: cannot call member function ‘void dmlc::ThreadLocalStore<T>::RegisterDelete(T*) [with T = std::unordered_set<std::__cxx11::basic_string<char> >]’ without object
       Singleton()->RegisterDelete(ptr);
       ~~~~~~~~^~~~~
CMake Error at cuda_compile_1_generated_bounding_box.cu.o.Debug.cmake:279 (message):
  Error generating file
  /home/piotr/mxnet_master/build/CMakeFiles/cuda_compile_1.dir/src/operator/contrib/./cuda_compile_1_generated_bounding_box.cu.o

To Reproduce
Building with the following config:
rev: ef5633448...
./dev_menu.py build
--- # CMake configuration
USE_CUDA: "ON" # Build with CUDA support
USE_OLDCMAKECUDA: "OFF" # Build with old cmake cuda
USE_NCCL: "ON" # Use NVidia NCCL with CUDA
USE_OPENCV: "ON" # Build with OpenCV support
USE_OPENMP: "PLATFORM" # Build with Openmp support
USE_CUDNN: "ON" # Build with cudnn support) # one could set CUDNN_ROOT for search path
USE_SSE: "ON" # Build with x86 SSE instruction support IF NOT ARM
USE_F16C: "ON" # Build with x86 F16C instruction support) # autodetects support if "ON"
USE_LAPACK: "ON" # Build with lapack support
USE_MKL_IF_AVAILABLE: "OFF" # Use MKL if found
USE_MKLML_MKL: "OFF" # Use MKLDNN variant of MKL (if MKL found) IF USE_MKL_IF_AVAILABLE AND (NOT APPLE)
USE_MKLDNN: "OFF" # Use MKLDNN variant of MKL (if MKL found) IF USE_MKL_IF_AVAILABLE AND (NOT APPLE)
USE_OPERATOR_TUNING: "ON" # Enable auto-tuning of operators IF NOT MSVC
USE_GPERFTOOLS: "ON" # Build with GPerfTools support (if found)
USE_JEMALLOC: "ON" # Build with Jemalloc support
USE_DIST_KVSTORE: "OFF" # Build with DIST_KVSTORE support
USE_PLUGINS_WARPCTC: "OFF" # Use WARPCTC Plugins
USE_PLUGIN_CAFFE: "OFF" # Use Caffe Plugin
USE_CPP_PACKAGE: "OFF" # Build C++ Package
USE_MXNET_LIB_NAMING: "ON" # Use MXNet library naming conventions.
USE_GPROF: "OFF" # Compile with gprof (profiling) flag
USE_CXX14_IF_AVAILABLE: "OFF" # Build with C++14 if the compiler supports it
USE_VTUNE: "OFF" # Enable use of Intel Amplifier XE (VTune)) # one could set VTUNE_ROOT for search path
ENABLE_CUDA_RTC: "ON" # Build with CUDA runtime compilation support
BUILD_CPP_EXAMPLES: "ON" # Build cpp examples
INSTALL_EXAMPLES: "OFF" # Install the example source files.
USE_SIGNAL_HANDLER: "ON" # Print stack traces on segfaults.
USE_TENSORRT: "OFF" # Enable infeference optimization with TensorRT.
USE_ASAN: "OFF" # Enable Clang/GCC ASAN sanitizers.
ENABLE_TESTCOVERAGE: "OFF" # Enable compilation with test coverage metric output
CMAKE_BUILD_TYPE: "Debug"
CMAKE_CUDA_COMPILER_LAUNCHER: "ccache"
CMAKE_C_COMPILER_LAUNCHER: "ccache"
CMAKE_CXX_COMPILER_LAUNCHER: "ccache"

Steps to reproduce
(Paste the commands you ran that produced the error.)

What have you tried to solve it?

Environment
We recommend using our script for collecting the diagnositc information. Run the following command and paste the outputs below:
http://ix.io/1ZL6

Looks like it could be the commit after 91bb39898e6b12fb45451852019939f694e54f71
@anirudh2290

Was able to build it successfully for ef56334
with following build flags
$ python -c "from mxnet.runtime import feature_list; print(feature_list())"
[ ✔ CUDA, ✔ CUDNN, ✖ NCCL, ✔ CUDA_RTC, ✖ TENSORRT, ✔ CPU_SSE, ✔ CPU_SSE2, ✔ CPU_SSE3, ✔ CPU_SSE4_1, ✔ CPU_SSE4_2, ✖ CPU_SSE4A, ✔ CPU_AVX, ✖ CPU_AVX2, ✔ OPENMP, ✖ SSE, ✔ F16C, ✖ JEMALLOC, ✔ BLAS_OPEN, ✖ BLAS_ATLAS, ✖ BLAS_MKL, ✖ BLAS_APPLE, ✖ LAPACK, ✖ MKLDNN, ✖ OPENCV, ✖ CAFFE, ✖ PROFILER, ✖ DIST_KVSTORE, ✖ CXX14, ✔ INT64_TENSOR_SIZE, ✔ SIGNAL_HANDLER, ✔ DEBUG, ✖ TVM_OP]

Something off coz of NCCL?

Its probably because of the gcc version not supporting __thread construct. Looking into this.

My earlier theory related to __thread was wrong. I am not able to reproduce it with :
mkdir build && cd build && cmake -DVERBOSE=1 -DUSE_CUDA=ON -DUSE_CUDNN=ON -DUSE_OPENMP=ON -DCMAKE_BUILD_TYPE=Debug -DUSE_DIST_KVSTORE=0 -DUSE_OPENCV=0 -DCUDA_TOOLKIT_ROOT_DIR=/usr/local/cuda-10.1 -DCUDNN_ROOT=/usr/local/cuda-10.1 -DUSE_MKLDNN=0 -DUSE_MKL_IF_AVAILABLE=0 -DUSE_MKLML_MKL=0 -DUSE_ASAN=0 -GNinja -DUSE_OPERATOR_TUNING=1 -DUSE_CPP_PACKAGE=ON -DCUDA_ARCH_NAME=Auto -DUSE_INT64_TENSOR_SIZE=OFF -DUSE_TENSORRT=OFF -DUSE_NCCL=ON ..
ninja -v

Since CI passed without issues and my local build also passed with g++ 7.4 I am suspecting some issue with your setup. Can you omit ccache and run the build directly? Did you do the submodule update?

Could be related to nvvc:
piotr@54-198-120-41:0:~/mxnet_master ((ef5633448...))+$ /usr/local/cuda-10.1/bin/nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2019 NVIDIA Corporation
Built on Fri_Feb__8_19:08:17_PST_2019
Cuda compilation tools, release 10.1, V10.1.105

My environment is here:
https://github.com/larroy/ec2_launch_scripts
Tried gcc 6 and happened as well.

I have removed the "Bug" label for now. This requires more evidence to be classified as a "MXNet" bug. I have requested an AMI from @larroy offline to reproduce the issue on the specific version of nvcc. Currently, I have tried to build with CUDA 10.0 and CUDA 10.1 and haven't been able to reproduce on ubuntu 18.04 and g++ 7.4. Also, this issue wasn't reproduced on our supported environments checked by CI.

Hi @anirudh2290 you can repro the environment in AWS Ec with the following:
https://github.com/larroy/ec2_launch_scripts
Just execute launch.py  all the environment is coded and coming from NVidia. Let me know if you have any issues.
Would be great if we could fix this issue.

Hi @larroy, I currently don't have the time to debug custom scripts and custom environments. You provided the CUDA version gcc version ubuntu version. I tried with this configuration for cmake build and haven't been able to reproduce the issue. Also, the issue has not been reproduced in the CI builds. With the current evidence, I highly suspect the issue to be specific to something happening in your environment.
Having said that, I can continue my work even if https://github.com/apache/incubator-mxnet/pull/16526 is reverted, though it may cause slightly additional work for frontend developers, developing on top of https://github.com/apache/incubator-mxnet/pull/16654 . So, if you can convince a committer about this revert, i won't be blocking it. Also, if this is going to be reverted, a CI stage should be added in the future, which would make #16526 fail the build.

Thanks for your help @anirudh2290 I think this is a bug with the NVCC that comes with Cuda 10.1.105 as seems to work with 10.1.243.

I got a similar issue with ArchLinux, cuda 10.1.243, gcc 8.3.0, opencv 4.1.2. Here is my build log.
mxnet-buildlog.txt

@hubutui Looks like your issue is unrelated.  I don't see issue related to ThreadLocalStore in your log.

Yes, I believe this is a problem present in the original cuda 10.1 release (10.1.105), fixed by 10.1 Update 1 (10.1.168).  Are you able to upgrade at least to this version, or are we looking for a work-around for 10.1.105?

I was able to upgrade and the problem went away with the updated CUDA.

And FYI, if you feel it worth trying to correct this for MXNet users on the original cuda 10.1, the fix to the problematic line in dmlc-core is:
      // nvcc fails to compile 'Singleton()->' on first cuda 10.1 release, fixed with update 1.
      (*Singleton()).RegisterDelete(ptr);

Worth a PR?

I think it would be user friendly to avoid obscure compilation errors for users if we can avoid it.

I agree, it would be worth opening a PR to dmlc-core. Thanks @DickJC123 !