DReyeVR Parser data output

Hi guys!
Um, so I ran the parser successfully. But there seem to be some issues.... The eye tracker works absolutely fine with DReyeVR. The output for gaze metrics and eye openess is missing. Here's the pic:

But it seems to collect pupil diameter:

Also, i assume the data is being collected correctly, because here it says 1 for valid:

Looks like the data is there but the parser didn't get the data for the gaze data. Can you make sure this is parsed correctly? Try printing the element of the dictionary.

So I tried printing the element "LeftEyeOpenness" and "RightGaze". All values come out as 0.
Do you mind giving a look at the human readable file?  Would be extremely helpful.  ^^"
Link (expires in 3 days): https://litter.catbox.moe/agbuji.txt

Been trying to trouble shoot this, but i am not able to understand where exactly is the issue. Tried deleting and re-cloning the parser and started all over again, but still the same issue :/
Files (rec and txt): test23ax.zip
The DReyeVR_logging.py data looks absolutely great. Is there's any way we can use this or simplify to a more readable representation?
File: test23.txt

Unfortunately this looks like a bug in the (DReyeVR) recorder rather than in the parser. Which is much more difficult to debug. I am away from a computer for a while and will be unable to debug for the time being. Hopefully you can use the raw logging variables for now.

Oh, I see. No problem though, I am working out a way to use the raw logging variables to convert them into csv format. Should serve the purpose ig.
But yeah, thanks a lot man for helping all the way out, this far. Truly appreciate it <3

Oh, I see. No problem though, I am working out a way to use the raw logging variables to convert them into csv format. Should serve the purpose ig.
But yeah, thanks a lot man for helping all the way out, this far. Truly appreciate it <3

Hi I have kind of this issue. However I am in VR mode itshows the gaze and pupil zero!!! COULD YOU HELP ME

There are two ways you can visualize data.

Using DReyeVR parser: Make sure its calibrated well for the subject using it. If its not calibrated properly, such issues can occur. If it doesn't work, try deleting the parser and loading again.

Using DReyeVR_logging.py: This is great if you wish to manually play around with the data. The output I presume is in python dictionary format. So you  need to find a way to convert into csv for manipulation.

Lemme know how it goes.

There are two ways you can visualize data.

Using DReyeVR parser: Make sure its calibrated well for the subject using it. If its not calibrated properly, such issues can occur. If it doesn't work, try deleting the parser and loading again.
Using DReyeVR_logging.py: This is great if you wish to manually play around with the data. The output I presume is in python dictionary format. So you  need to find a way to convert into csv for manipulation.

Lemme know how it goes.

Thanks for replying.
You mean the VR headset should be calibrate or something else.
Also, when I execute  DReyeVR_logging.py in anaconda prompt I just see some data and I do not know where the data was saved?

Yeah, the headset eye calibration must be done. Also, make sure you are using x64 Native Tools CMD for the scripts. To see the data, you need to jot it down in a .txt file. Below, I have explained how:
DReyeVR_logging.py can be used in two ways:

When you are actively running simulation, you simultaneously start the script in another CMD window. For this you just run py DReyeVR_logging.py > log.txt in a cmd window.

You simultaneously start this script when you are playing a recording (.rec file). For this, you run the logging first, and the recording immediately after that in two separate cmd windows.

first this py DReyeVR_logging.py > log.txt and then this py show_recorded_file_info.py -a -f /PATH_TO_.rec file
The log.txt will appear in the same folder where the DReyeVR.py script is present.


Update CMakeLists.txt and CHANGELOG for 2.17.0 Release

Description

Updates the CMakeLists.txt and CHANGELOG.md for a 2.17.0 release.
How Has This Been Tested?

I will test with GEOSgcm to make sure all is well.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Trivial change (affects only documentation or cleanup)

Checklist:

[ ] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[x] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

Adding blocking label until I can test.

Seems to be zero-diff. Merging!


Update token logo

Token Address
https://scan.tomochain.com/address/0x021d8b9647c9d19fb865931461eb85b6b4013e79
Token Symbol
IRAN
Token Name
IRAN
Token Logo
https://i.pinimg.com/originals/0b/eb/3b/0beb3b80ae3e5622db92f6ea21ea8b50.png
Token Description
Website
Social links

added logo


Issue with parsing ONNX models from onnx model zoo

Hi,
I am trying to use zigzag to parse the onnx models. While I was able to parse some nets, the following nets are not being parsed (with the respective errors reported as listed below):
Faster R-CNN R-50-FPN,
Mask R-CNN R-50-FPN:
File /imec/scratch/dtpatha/sahoo98/tools/conda/envs/sss_default/lib/python3.10/site-packages/zigzag/classes/io/onnx/conv.py:79, in ConvParser.generate_layer_node_for_conv..get_input_output_weight_data_type(node, model)
     76 # w_name = node.input[3]
     77 # Get the weight data type through the graph initializers
     78 initializer_names = [i.name for i in model.graph.initializer]
---> 79 w_data_type = model.graph.initializer[initializer_names.index(w_name)].data_type
     81 return ia_elem_type, oa_elem_type, w_data_type

ValueError: '2' is not in list

FCN ResNet-50,
SSD-MobilenetV1-12,
YOLOv3-12:
File /imec/scratch/dtpatha/sahoo98/tools/conda/envs/sss_default/lib/python3.10/site-packages/zigzag/classes/workload/layer_node.py:341, in LayerNode.extract_layer_info(self)
    339 operand_data_reuse: Dict[str, float] = {}
    340 for operand, size_in_elem in operand_size_elem.items():
--> 341     operand_data_reuse[operand] = total_MAC_count/size_in_elem
    342 self.operand_data_reuse = operand_data_reuse

ZeroDivisionError: division by zero

BERT-Squad:
File /imec/scratch/dtpatha/sahoo98/tools/conda/envs/sss_default/lib/python3.10/site-packages/zigzag/classes/io/onnx/matmul.py:64, in MatMulParser.generate_layer_node_for_matmul(self)
     60     return d
     62 ia_dimension_shape, oa_dimension_shape = get_node_input_output_dimension_shapes(self.node, self.onnx_model)
---> 64 assert len(ia_dimension_shape) == len(oa_dimension_shape) == 2  # First element is batch size, second is input/output channel
     65 assert ia_dimension_shape[0] == oa_dimension_shape[0]  # Batch size should be the same for input and output
     66 # If the batch size is 0, we discard it by setting it to 1 internally inside ZigZag

AssertionError:

Hi,
Thanks for the response. I did run shape inference on the models before the parsing.
The parser worked fine on the following models from the model zoo of onnx:

"AlexNet"
"CaffeNet"
"DenseNet-121-12"
"EfficientNet-Lite4"
"GoogleNet"
"Inception-1"
"MNIST-12"
"MobileNet v2-1.0"
"ResNet50"
"ShuffleNet-v2"
"SqueezeNet 1.0"
"VGG 16"
"ZFNet-512"
"ResNet101_DUC_HDC-12"
"SSD"

The errors were for the following  models that were not parsed as detailed in my previous comment:

"BERT-Squad"
"Faster R-CNN R-50-FPN"
"FCN ResNet-50"
"Mask R-CNN R-50-FPN"
"SSD-MobilenetV1-12"
"YOLOv3-12"

Thanks & Regards,
Siva

@asyms FYI: BERT not passing these checks is something I saw on MobileBERT too

I didn't find the time to check all the different models you list, but these checks will fail because there is some information lacking in the ONNX graph. Either there is shape information missing or some of the dimensions of the shapes are dynamic.
If you have fixed one the models you listed above, please feel free to submit a pull request with the model here: https://github.com/KULeuven-MICAS/zigzag/tree/master/zigzag/inputs/examples/workload
Kind regards,
Arne

It's possible at least the first case was fixed by https://github.com/KULeuven-MICAS/zigzag/pull/10, there were a lot of edge cases around getting tensor information by name.

Closing this due to inactivity. Feel free to re-open if there's any specific networks that still aren't working.


To identify file corruption after codeupdate

[ ] Check the content /etc/host*

[ ] Codeupdate

[ ] compare the content of /etc/host* what was capture before code update

[ ] https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/26074/


AWS Lambda example tests should use mock event server

LambdaClient is deprecated, so we should switch to testing with the mock event server.
https://github.com/apache/camel-quarkus-examples/blob/main/aws-lambda/src/test/java/org/acme/aws/lambda/AWSLambdaHandlerTest.java
https://quarkus.io/guides/amazon-lambda#live-coding-and-unitintegration-testing

Fixed here https://github.com/apache/camel-quarkus-examples/pull/82.


[WIP] Add gallery example for drawing keypoints

Follow up of #4216
Work in progress should be done in few hours :)

@oke-aditya I'm not sure from where you sourced the image you are using but I recommend finding an alternative picture from the Coco keypoint dataset used to train the keypoint model.

This image was sourced from COCO dataset. Is it a concern since it displays a human image?

@oke-aditya It's good you got it from COCO. My concern is that it seems to depict a minor so let's be extra careful and replace it. Do you think that we can reuse the standard Grace Hopper picture we already have? This might be interesting because on your example you might need to filter out keypoints that don't appear on the picture (and thus it's going to be a more realistic example of visualization). Thoughts?

Oh! So sorry for depicting a minor! I completely agree we should avoid this image.
Very very thankful to you @datumbox for pointing this out.
My apologies to the minor person depicted (who would have grown up by today :smiley: ) who might see this PR.
That's Good idea to add an example where we need to filter out keypoints. Both based on visibility and detection threshold.
But I feel that joining a complete skeleton is particular useful as for pose-detection / other tasks. So I will keep two examples.
First one just joining skeletons and next one helping to filter keypoints well

@oke-aditya Sounds good. Let's select  an alternative picture from COCO and do 2 examples as you proposed. Thanks!

Absolutely baffled still that every run with keypoint_rcnn_resnet50 with both pretrained=True and False, the visibility was always 1.00 for all the keypoints and instances.
Tried over 15 images from coco, of not just persons, dogs, cats, surfboards. :(
Is there really a case where visibility won't be 1 ? Can someone provide an image for such case.

@oke-aditya I had the same exact discussion with Francisco couple of days ago and he clarified that this is always 1. So I suggest to just ignore this column and move on.
@fmassa could you please confirm that this is the case?

I have added one single example showing plotting keypoints and joining them.
I felt that one detailed and simple example is necessary as keypoint rcnn involves little bit more processing and understanding to connect keypoints.
Let me know if an additional example such as batch of images or plotting multi instance images is needed.
I think it will be nice to have.

Thanks @oke-aditya , I just gave a brief look to the rendered example and it looks great. The only comment I have is about the first sentence in the example which is

This example illustrates some of the utilities that torchvision offers for visualizing images, bounding boxes, and segmentation masks.

and that could now be updated to

This example illustrates some of the utilities that torchvision offers for visualizing images, bounding boxes, segmentation masks, and keypoints.

Nice work! :)

This example illustrates some of the utilities that torchvision offers for visualizing images, bounding boxes, and segmentation masks.

Nice, catch. I will also update the visualization thumbnail to include this image too.

Nice work! :)

Thanks Nicolas :) once we finish supporting multiple colors, line colors, etc.
I will add one small example which shows multiple instances. The utility looks cool :sunglasses:  on multiple images.

Here is the final gallery. Feel free to suggest changes :)
https://980059-73328905-gh.circle-artifacts.com/0/docs/auto_examples/index.html

@oke-aditya Great job as always Oke. Thanks for contributing this and for your patience for the reviews on the original PR.


Just a heads up, https://gmlsupport.liaronce.win doesn't load, the domain doesn't resolve

Please feel free.
hey, just a heads up your site appears down:
https://wheresitup.com/demo/results/5e16270b51a5400da329b6b3

The new URL is: https://gmlsupport.liaronce.com


Test for dynamic content in Glimmer2

As suggested by @rwjblue this adds a test case for dynamic content updates inside a wormhole, which is currently broken with Glimmer2 as reported in #66. The newly added test currently fails as expected in all Glimmer2 based Ember versions (alpha, beta, canary).

Awesome, thank you!


Move op sweeps to pytest

To dos

[x] Create pytest wrapper test file which calls sweeps

[ ] #397

[ ] Uplift shape/case generation code to create dynamic pytest.mark.parametrize cases using pytest_generate_tests fixture

[x] Reset seeds for torch, numpy, and random in conftest for reproducibility

[x] Add script to CI ops/dnn commits

[ ] Update current ops sweeps with current list

[ ] Document procedure to add ops and enforce usage

Closing in favor of TTNN's new OP sweep infra which isn't pytest based


chore: Don't trigger comment-triage on PRs

Why:
Although PRs are treated as regular issues for this job, they end up failing on PRs and don't appear to the use case for this job
What's being changed:
Don't trigger the triage issues job when the issue_comment is triggered by a comment on a PR
Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging.
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

Thanks @nschonni! I'll get this triaged for review ⚡

Thank you! This one has been a leaky faucet!


Create a key/legend for what green vs yellow means in different sections

This info is available on hover so I'm inclined to reprioritise this significantly, though I agree it would be nice

Everything has explanatory hover text. But this is still doable
On Thu, 25 Aug 2022, 03:22 neil, @.***> wrote:

—
Reply to this email directly, view it on GitHub
https://github.com/loathers/greenbox/issues/28, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABL4LXLVQMQOD4SF2AR2JLV23KHBANCNFSM57RMOOYA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I sometimes want to check from my phone, which does not do hover.


sing-box: 1.4.0 -> 1.4.1

Diff: https://github.com/SagerNet/sing-box/compare/v1.4.0...v1.4.1
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 252745 run on x86_64-linux 1

1 package built:

sing-box


Can't acess an Ender IO when using a Chicken Chunks Chunk Loader and cannot access an ME System with a staff of travelling and an Ender IO

I used a Chicken Chunks chunk loader for my Ender IO, however when I go out of my Render Distance I can't access it. I have read on the FTB wiki and the Ender IO wiki that if I load the chunk the Ender IO is in, I can access it from anywhere with a Staff of Travelling. Also, I cannot use an ME Terminal or ME Crafting Terminal from an Ender IO as well. I can open my ME Drives, or anything with a GUI from another mod, just not the ME Terminal and Crafting Terminal. I am in 1.7.10 and am using Chicken Chunks <IP_ADDRESS>, AE2 RV2 Beta 9, and Ender IO <IP_ADDRESS>9.

The EnderIO (and Travel Anchors) must be in rendering range to be accessible. And there is a config option "enderIoMeAccessEnabled" which can disable the use of an ME terminal via the EnderIO.

Yes, this is not a bug. Chunk loaders load on the server, the Ender IO requires clientside rendering to function.


Fraction debug printings

Removed commented out debug printing from the Fraction class.

Coverage remained the same at 95.167% when pulling 8d61cab5592e239d732aaeb19418db77970fda7f on mureinik:cleanup into 187a05b8a4db364af9d1c8ff4eb422082c30a1ff on apache:master.

How is this code useful? It adds nothing to the functionality, nor does it help explain the code. It seems like the original author used it while developing this class, but once it's done, I see no value in keeping it.

debugging can be much effectively done with IDE, adding these kind of console output is discouraged.
I would recommend to use logging logger.debug(), but that's not the guidelines in commons.
so +1 to remove it.

I think what Gary meant is that that comment is harmless, and can be used by other developers that want/need to debug the code, and see what is going on. I've used it in some projects myself, to indicate to fellow developers parts of the code that may be a bit fuzzy or complicated. I'm OK if it's kept, but OK too if others prefer to remove it (if we replace it by a comment like "Here we can see variable x" I'm OK as well).


Adjust coding style of include path

Adjust the format of include path for all platforms according to the coding style. In the #include directive, only the header file name (or prefixed with the name of the subdirectory under the include path) is reserved.

Add header search paths to the project file and remove the redundant relative paths in headers, implementation and resource files
Update the #include directives for Windows, macOS, Linux and NetBSD platforms

Did you test NetBSD? param.h and types.h must go first.

Did you test NetBSD? param.h and types.h must go first.

Thanks for your attention. We don't have NetBSD environment to verify it yet. Do you have time to test it on NetBSD? If possible, you may base on my patch and complement the Makefile part for header search path and I will cancel my patch then. Thanks a lot.

Please revert all reordering of kernel headers for NetBSD and add CPPFLAGS+= -I$(src)/../../include -I$(src)/../../core/include in the Makefile. Then I will build test it.

Thanks for your reply. I have updated the patch for NetBSD. Could you help to build it? If there is any issue, please let me know. Thanks again.

@krytarowski, have you ever verified the build on NetBSD? May I merge this PR then? Thanks a lot.

@krytarowski, sorry for bothering you. As HAXM is approaching to release, if you do not have time to verify the build, could you review the updated patch? If the NetBSD code review passes, we can merge it first. Thanks a lot.

Testing now.

I had to do this on top of this pull-request in order to make it buildable.
diff --git a/platforms/netbsd/Makefile b/platforms/netbsd/Makefile
index 4b601de..8853550 100644
--- a/platforms/netbsd/Makefile
+++ b/platforms/netbsd/Makefile
@@ -2,7 +2,8 @@ S?=	/usr/src/sys

 KMOD=	haxm

-CPPFLAGS+= -I$(src)/../../include -I$(src)/../../core/include
+CFLAGS+=-Wno-error=address-of-packed-member
+CPPFLAGS+= -I../../include -I../../core/include

 # toplevel
 SRCS+=	components.c

@krytarowski, thanks for your verification. I have updated the patch of NetBSD and will merge it later. Thanks.


RPM versioning

As we might need to deploy a testing version due to https://github.com/k3s-io/k3s-selinux/issues/36 (via our own repos), we have a question about the exact strategy for release numbering, that is not clear to me from the README.
All the 1.2.*.2 tags are on the same commit, however 1.2.latest.1 and 1.2.testing.1 are different from each other.
Can we assume that 1.3.testing.10 will become 1.3.stable.10 (if released) and any future release in stable channel will have a higher RPM release number? Or will the first stable 1.3 release be 1.3-1 no matter what testing release it was before? The latter would mean some challenges for upgradeability when channel hopping.
I would be willing to come up with a PR to try to improve README when clarified here.
Thanks.

I think your question was answered by a release: https://github.com/k3s-io/k3s-selinux/releases/tag/v1.3.stable.1


Router confusion

Thanks for all this work. A great effort.
However I'm confused.
The front controller(index.php) calls $router->dispatch($_SERVER['QUERY_STRING']);
I thought that QUERY_STRING only contains the string after the ? in the URL.
How can it be used to route a URL
Also $router->dispath() is defined with $url as the parameter. Yet you passed QUERY_STRING into it.
Quick explaination would be much appreciated.

Ok, please close this.
I can see your htaccess file is sending all requests to index.php with the url as the query string.
I was not using apache - using PHP internal server which of course does not process htaccess file.


[Operator WG] Operator Lifecycle Management

"Operator Lifecycle Management" section on Operator white paper.

"Operator Lifecycle Management" section on Operator white paper.

https://github.com/cncf/sig-app-delivery/blob/master/operator-wg/whitepaper/06_Lifecycle.md


limit chat input size

@keybase/react-hackers

Curious what the long term solution is? Convert and upload as an attachment (text file)?

Yeah. Similar to slack snippets
On Thu, Dec 22, 2016 at 2:02 PM Gabriel Handford<EMAIL_ADDRESS>wrote:

Curious what the long term solution is? Convert and upload as an
attachment (text file)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/pull/5200#issuecomment-268867438, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAfhUw97I1GdiIlzZuc_46NNOs6e4k8Vks5rKslQgaJpZM4LUNFG
.


Verb form needs a lot of work to enable handling of all field types

Create a single input form which the user can input JSON request payloads
Hopefully, we can get this structure from the backend from protobuf definitions. Either generate the json from proto on the backend or generate from proto on the console

This should generate the JSON schema on the backend so that it can be used, shared by other things that might need it.

Using Monaco instead.


Update mobile-device-sdk.md

Link to FAQ Current versions no longer valid. Updated to Repository Link.

I have merged this change into the corporate repo and it will be published later today.


fix(java): initialize netty-shaded at run-time and add reflection configurations for netty classes

Build initialization of netty causes inconsistent behavior when an application is run locally versus on Cloud Run. One such case as discovered in https://github.com/mutianf/graalvm-test is when a bigtable application works fine with native image compilation locally but times out on Cloud Run.
More details:
Netty System.nanoTime() as a memoized static start_time variable when the native image is being build. System.nanoTime() is an arbitrary value and platform specific so when the start_time compared against another System.nanoTime() at run time on the container, the comparison may not always be consistent. Netty is initialized at native image build time by default for netty 4.x but we can adjust this by setting --initialize-at-run-time=io.grpc.netty.shaded.io.netty in a META-INF/native-image/native-image.properties file.
Additionally, build time initialization of netty also causes build time issues when third party logging libraries like SLF4J are used:
Fatal error: com.oracle.graal.pointsto.util.AnalysisError$ParsingError: Error encountered while parsing io.grpc.netty.shaded.io.netty.util.internal.SystemPropertyUtil.getBoolean(java.lang.String, boolean)
Parsing context:
   at io.grpc.netty.shaded.io.netty.util.internal.SystemPropertyUtil.getBoolean(SystemPropertyUtil.java:96)
   at io.grpc.netty.shaded.io.netty.channel.epoll.Epoll.<clinit>(Epoll.java:33)
   at org.graalvm.nativeimage.pointsto/com.oracle.graal.pointsto.util.AnalysisError.parsingError(AnalysisError.java:153)
...
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Caused by: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: No instances of org.slf4j.jul.JDK14LoggerAdapter are allowed in the image heap as this class should be initialized at image runtime. To see how this object got instantiated use --trace-object-instantiation=org.slf4j.jul.JDK14LoggerAdapter.

It is important to note that this may result in a performance cost depending on the code path the application follows but given the persistence of these issues as a result of build-time netty initialization, run-time initialization of netty provides a more out-of-the-box experience.

The downstream checks are failing due to:
Failed to execute goal on project google-cloud-kms: Could not resolve dependencies for project com.google.cloud:google-cloud-kms:jar:2.13.0-SNAPSHOT: Could not find artifact com.google.cloud:google-cloud-core:jar:2.9.5-SNAPSHOT in google-maven-central-copy (https://maven-central.storage-download.googleapis.com/maven2) -> [Help 1]
[ERROR] Failed to execute goal on project google-cloud-os-login: Could not resolve dependencies for project com.google.cloud:google-cloud-os-login:jar:2.9.0-SNAPSHOT: com.google.cloud:google-cloud-core:jar:2.9.5-SNAPSHOT was not found in https://maven-central.storage-download.googleapis.com/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of google-maven-central-copy has elapsed or updates are forced -> [Help 1]


Fe: hero text copywriting

An open virtual world built with existing communities.

The sample size is small but we've heard this expressed as a confusing wording -- what are the communities?

Now the hero text is "An Internet Scale Cinematic Universe" -- this + the hero image are worth testing to see what new users initial impressions are.

https://www.youtube.com/watch?v=S2xHZPH5Sng


Installation of Kubernetes.github.io/ingress-nginx results a timeout.

Environmental Info:
K3s Version:

k3s version v1.25.4+k3s1 (0dc63334)
go version go1.19.3

Node(s) CPU architecture, OS, and Version:

Linux projectoc 6.0.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 16 Nov 2022 17:01:17 +0000 x86_64 GNU/Linux
Cluster Configuration:

1 Server, Master+Worker
Describe the bug:

Following https://www.suse.com/support/kb/doc/?id=000020082 results in a timeout as described in https://github.com/kubernetes/ingress-nginx/issues/9091.
I have a similiar Issue with Flux2 - "flux reconcile" results in a timeout with kubernetes.github.io/ingress-nginx.
 IN A

;; ANSWER SECTION:
kubernetes.github.io. 30 IN A <IP_ADDRESS>
kubernetes.github.io. 30 IN A <IP_ADDRESS>
kubernetes.github.io. 30 IN A <IP_ADDRESS>
kubernetes.github.io. 30 IN A <IP_ADDRESS>

;; Query time: 0 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>) (UDP)
;; WHEN: Tue Nov 29 13:10:23 UTC 2022
;; MSG SIZE rcvd: 205

~ # curl -vvv -L https://kubernetes.github.io/ingress-nginx > /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying <IP_ADDRESS>:443...

Connected to kubernetes.github.io (<IP_ADDRESS>) port 443 (#0)

ALPN: offers h2

ALPN: offers http/1.1

CAfile: /etc/ssl/certs/ca-certificates.crt

CApath: none

TLSv1.0 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]

TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
0 0 0 0 0 0 0 0 --:--:-- 0:00:10 --:--:-- 0

0 0 0 0 0 0 0 0 --:--:-- 0:00:11 --:--:-- 0

0 0 0 0 0 0 0 0 --:--:-- 0:00:38 --:--:-- 0

Installed K3s:

Expected behavior:

Successfully Download of the index.yaml
Actual behavior:

Timeout Error

Are you doing this curl test from within a pod, or on the node itself? It looks like it's connecting, but then the TLS handshake is failing. This usually indicates that there is a firewall, proxy, or some other device in your network that is interfering with the communication. Do you need to use a proxy, or open up access through a firewall?

No, no need of proxy. I turned off firewall as the environment is only for testing purpose

You didn't answer my question about whether this is happening in a pod, or on the node, but something is blocking your access to github. I'm not aware of any issues with K3s itself that would cause your TLS handshake to time out as your test is demonstrating.

It is happening only in the pod. Sorry forgot to answer your question

Reinstallation of the k3s installation seems to be the solution. I cannot explain what the issue has been exactly.


Alignment for /chooser boxes is off

https://creativecommons.org/choose/
See screenshot (Chrome Version 43.0.2357.134 (64-bit)

We changed the chooser layout so this was no longer an issue.


RAC-1984 fixed flawed CIT test. Should expect 404 instead of []

Jenkins: depends on https://github.com/RackHD/on-http/pull/551
This is necessary for this PR to pass - https://github.com/RackHD/on-http/pull/551
The api this CIT test is testing was broken and always returned [] no matter what it was given as input. The above PR corrects for this. The Cit test that this PR changes was built expecting [] which is wrong. The test now expects a 404 response when provided a bad id.

BUILD RackHD #1219 : FAILURE

** BUILD build-config-setup  #1227: SUCCESS
** BUILD CIT  #802: FAILURE
** BUILD FIT  #663: FAILURE

test this please

BUILD RackHD #1224 : UNSTABLE

** BUILD build-config-setup  #1237: SUCCESS
** BUILD CIT  #814: UNSTABLE
** BUILD FIT  #676: SUCCESS

BUILD CIT  #814  Error Logs  ▼Test Name: test_node_workflows_get
Error Details: did not raise exception
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/home/jenkins/workspace/RackHD/build/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/home/jenkins/workspace/RackHD/build/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/home/jenkins/workspace/RackHD/build/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/v2_0/nodes_tests.py", line 301, in test_node_workflows_get
    fail(message='did not raise exception')
  File "/home/jenkins/workspace/RackHD/build/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: did not raise exception

BUILD RackHD #1322 : UNSTABLE

** BUILD Install-Ubuntu-14-04  #130: SUCCESS
** BUILD SmokeTest-FIT  #166: SUCCESS
** BUILD Install-CentOs-6.5  #152: SUCCESS
** BUILD SmokeTest-CIT  #361: UNSTABLE

BUILD SmokeTest-CIT  #361  Error Logs  ▼Test Name: test_node_workflows_get
Error Details: did not raise exception for nodes_get_workflow_by_id with bad id
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/tests/api/v2_0/nodes_tests.py", line 301, in test_node_workflows_get
    fail(message='did not raise exception for nodes_get_workflow_by_id with bad id')
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: did not raise exception for nodes_get_workflow_by_id with bad id

Jenkins: test this please

BUILD on-multi #76 : ABORTED

** BUILD build-config-setup  #1535: SUCCESS
** BUILD on-http  #3231: SUCCESS

** BUILD build-config-setup  #1536: SUCCESS
** BUILD unit-tests  #11581: SUCCESS

** BUILD Install-CentOs-6.5  #154: ABORTED
** BUILD SmokeTest-CIT  #363: ABORTED
** BUILD SmokeTest-FIT  #168: SUCCESS
** BUILD Install-Ubuntu-14-04  #132: ABORTED

test this please

BUILD on-multi #77 : UNSTABLE

** BUILD build-config-setup  #1538: SUCCESS
** BUILD on-http  #3233: SUCCESS

** BUILD build-config-setup  #1539: SUCCESS
** BUILD unit-tests  #11583: SUCCESS

** BUILD SmokeTest-FIT  #173: SUCCESS
** BUILD Install-CentOs-6.5  #159: SUCCESS
** BUILD Install-Ubuntu-14-04  #137: SUCCESS
** BUILD SmokeTest-CIT  #368: UNSTABLE

BUILD SmokeTest-CIT  #368  Error Logs  ▼Test Name: test_node_workflows_post
Error Details: local variable 'data' referenced before assignment
-------------------- >> begin captured logging << --------------------
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=20)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=19)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=18)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=17)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=16)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=15)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=14)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=13)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=12)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=11)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=10)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=9)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=8)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=7)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=6)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=5)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=4)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=3)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=2)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=1)
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/tests/api/v2_0/nodes_tests.py", line 318, in test_node_workflows_post
    resps.append({'data': data, 'id':id})
"local variable 'data' referenced before assignment\n-------------------- >> begin captured logging << --------------------\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=20)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=19)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=18)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=17)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=16)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=15)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=14)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=13)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=12)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=11)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=10)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=9)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=8)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=7)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=6)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=5)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=4)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=3)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=2)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589d274376695c26088439e9 (status=succeeded,timeout=1)\n--------------------- >> end captured logging << ---------------------"

test this please

BUILD on-multi #78 : FAILURE

** BUILD build-config-setup  #1547: SUCCESS
** BUILD on-http  #3235: SUCCESS

** BUILD build-config-setup  #1548: SUCCESS
** BUILD unit-tests  #11591: SUCCESS

** BUILD SmokeTest-CIT  #371: FAILURE
** BUILD Install-Ubuntu-14-04  #140: ABORTED
** BUILD Install-CentOs-6.5  #162: ABORTED
** BUILD SmokeTest-FIT  #178: ABORTED

test this please

BUILD on-multi #79 : FAILURE

** BUILD build-config-setup  #1557: SUCCESS
** BUILD on-http  #3237: FAILURE

** BUILD build-config-setup  #1558: SUCCESS
** BUILD unit-tests  #11600: FAILURE

** BUILD Install-CentOs-6.5  #167: ABORTED
** BUILD Install-Ubuntu-14-04  #145: ABORTED
** BUILD SmokeTest-FIT  #181: FAILURE
** BUILD SmokeTest-CIT  #376: ABORTED

test this please

BUILD on-multi #80 : FAILURE

** BUILD build-config-setup  #1559: SUCCESS
** BUILD on-http  #3238: SUCCESS

** BUILD build-config-setup  #1560: SUCCESS
** BUILD unit-tests  #11601: SUCCESS

** BUILD Install-CentOs-6.5  #170: ABORTED
** BUILD SmokeTest-FIT  #184: FAILURE
** BUILD Install-Ubuntu-14-04  #148: ABORTED
** BUILD SmokeTest-CIT  #379: ABORTED

test this please

BUILD on-multi #81 : ABORTED

** BUILD build-config-setup  #1569: SUCCESS
** BUILD on-http  #3241: ABORTED

** BUILD build-config-setup  #1570: SUCCESS
** BUILD unit-tests  #11610: ABORTED

** BUILD Install-Ubuntu-14-04  #151: ABORTED
** BUILD SmokeTest-CIT  #382: ABORTED
** BUILD Install-CentOs-6.5  #173: FAILURE
** BUILD SmokeTest-FIT  #188: ABORTED

test this please

test this please

BUILD on-multi #82 : ABORTED

** BUILD build-config-setup  #1584: SUCCESS
** BUILD on-http  #3243: UNSTABLE

** BUILD build-config-setup  #1586: SUCCESS
** BUILD unit-tests  #11625: UNSTABLE

** BUILD Install-Ubuntu-14-04  #163: ABORTED
** BUILD SmokeTest-CIT  #394: ABORTED
** BUILD Install-CentOs-6.5  #185: ABORTED

BUILD unit-tests  #11625  Error Logs  ▼Test Name: Http.Api.Profiles "before each" hook: set up mocks for "should send a 500 if profileApiService.getNode fails"
Error Details: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.
Test Name: Http.Api.Lookup "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.

BUILD on-multi #83 : FAILURE

** BUILD build-config-setup  #1587: SUCCESS
** BUILD on-http  #3244: UNSTABLE

** BUILD build-config-setup  #1588: SUCCESS
** BUILD unit-tests  #11626: UNSTABLE

** BUILD Install-Ubuntu-14-04  #165: ABORTED
** BUILD Install-CentOs-6.5  #187: FAILURE
** BUILD SmokeTest-CIT  #396: ABORTED
** BUILD SmokeTest-FIT  #201: ABORTED

BUILD unit-tests  #11626  Error Logs  ▼Test Name: Redfish Registries "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Test Name: Redfish Schemas "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
at bound (domain.js:287:14)
at runBound (domain.js:300:12)
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues [as _onImmediate] (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Redfish TaskService "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
at bound (domain.js:287:14)
at runBound (domain.js:300:12)
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues [as _onImmediate] (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Http.Api.Skus "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Test Name: Http.Api.Nodes v1.1 "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
at bound (domain.js:287:14)
at runBound (domain.js:300:12)
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues [as _onImmediate] (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Http.Api.Tags "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
at bound (domain.js:287:14)
at runBound (domain.js:300:12)
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues [as _onImmediate] (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Http.Api.Schemas "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
at bound (domain.js:287:14)
at runBound (domain.js:300:12)
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:128:12)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues [as _onImmediate] (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Http.Api.Tasks "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Test Name: Http.Api.Files "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
at bound (domain.js:287:14)
at runBound (domain.js:300:12)
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues [as _onImmediate] (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)
Test Name: Http.Api.Notification "before all" hook: start HTTP server
Error Details: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
Stack Trace: Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
at bound (domain.js:287:14)
at runBound (domain.js:300:12)
at tryCatcher (node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (node_modules/on-core/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (node_modules/on-core/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues [as _onImmediate] (node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)

test this please

BUILD on-multi #84 : FAILURE

** BUILD build-config-setup  #1589: SUCCESS
** BUILD on-http  #3245: SUCCESS

** BUILD build-config-setup  #1590: SUCCESS
** BUILD unit-tests  #11627: SUCCESS

** BUILD Install-CentOs-6.5  #191: ABORTED
** BUILD SmokeTest-CIT  #400: ABORTED
** BUILD Install-Ubuntu-14-04  #169: FAILURE
** BUILD SmokeTest-FIT  #205: ABORTED

test this please

BUILD on-multi #85 : FAILURE

** BUILD build-config-setup  #1591: SUCCESS
** BUILD on-http  #3246: SUCCESS

** BUILD build-config-setup  #1592: SUCCESS
** BUILD unit-tests  #11628: SUCCESS

** BUILD SmokeTest-FIT  #213: FAILURE
** BUILD SmokeTest-CIT  #408: ABORTED
** BUILD Install-CentOs-6.5  #199: ABORTED
** BUILD Install-Ubuntu-14-04  #177: ABORTED

test this please

BUILD on-multi #86 : FAILURE

** BUILD build-config-setup  #1593: SUCCESS
** BUILD on-http  #3247: SUCCESS

** BUILD build-config-setup  #1594: SUCCESS
** BUILD unit-tests  #11629: SUCCESS

** BUILD SmokeTest-FIT  #216: ABORTED
** BUILD Install-Ubuntu-14-04  #180: FAILURE
** BUILD Install-CentOs-6.5  #202: ABORTED
** BUILD SmokeTest-CIT  #411: ABORTED

test this please

BUILD on-multi #87 : UNSTABLE

** BUILD build-config-setup  #1595: SUCCESS
** BUILD on-http  #3248: SUCCESS

** BUILD build-config-setup  #1596: SUCCESS
** BUILD unit-tests  #11630: SUCCESS

** BUILD SmokeTest-CIT  #413: UNSTABLE
** BUILD SmokeTest-FIT  #218: SUCCESS
** BUILD Install-CentOs-6.5  #204: SUCCESS
** BUILD Install-Ubuntu-14-04  #182: SUCCESS

BUILD SmokeTest-CIT  #413  Error Logs  ▼Test Name: test_node_workflows_post
Error Details: local variable 'data' referenced before assignment
-------------------- >> begin captured logging << --------------------
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=20)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=19)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=18)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=17)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=16)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=15)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=14)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=13)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=12)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=11)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=10)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=9)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=8)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=7)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=6)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=5)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=4)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=3)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=2)
tests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=1)
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/Templates/SmokeTest-CIT/RackHD/test/tests/api/v2_0/nodes_tests.py", line 318, in test_node_workflows_post
    resps.append({'data': data, 'id':id})
"local variable 'data' referenced before assignment\n-------------------- >> begin captured logging << --------------------\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=20)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=19)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=18)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=17)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=16)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=15)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=14)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=13)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=12)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=11)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=10)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=9)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=8)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=7)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=6)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=5)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=4)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=3)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=2)\ntests.api.v2_0.nodes_tests: WARNING: Workflow status for Node 589db7d7c5b42b580827e33d (status=succeeded,timeout=1)\n--------------------- >> end captured logging << ---------------------"

http://rackhdci.lss.emc.com/job/Templates/job/SmokeTest-CIT/413/
one test case error test_node_workflows_post.test_node_workflows_post

test this please

test this please

jenkins: test this please

Please hold off on merging this for the time being.

*** BUILD RackHD #60 ***

This PR should be green when this ticket is merged
https://github.com/RackHD/on-http/pull/551
Please show it some love when the pipeline is cleared :)

test this please

@RackHD/corecommitters
Please merge this when you have the chance.

BUILD rackhd #5 : FAILURE

BUILD rackhd #5  Error Logs  ▼Test Name: test_node_workflows_get
Error Details: did not raise exception for nodes_get_workflow_by_id with bad id
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/home/jenkins/workspace/rackhd/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/home/jenkins/workspace/rackhd/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/home/jenkins/workspace/rackhd/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/rackhd/RackHD/test/tests/api/v2_0/nodes_tests.py", line 286, in test_node_workflows_get
    fail(message='did not raise exception for nodes_get_workflow_by_id with bad id')
  File "/home/jenkins/workspace/rackhd/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: did not raise exception for nodes_get_workflow_by_id with bad id

BUILD on-http #34 : FAILURE

BUILD on-http #34  Error Logs  ▼Test Name: test_node_workflows_get
Error Details: did not raise exception for nodes_get_workflow_by_id with bad id
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/home/jenkins/workspace/on-http/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/home/jenkins/workspace/on-http/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/home/jenkins/workspace/on-http/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/nodes_tests.py", line 286, in test_node_workflows_get
    fail(message='did not raise exception for nodes_get_workflow_by_id with bad id')
  File "/home/jenkins/workspace/on-http/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: did not raise exception for nodes_get_workflow_by_id with bad id

test this please

BUILD RackHD #2 : FAILURE

BUILD RackHD #2  Error Logs  ▼Test Name: test_node_workflows_get
Error Details: did not raise exception for nodes_get_workflow_by_id with bad id
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/home/jenkins/workspace/RackHD/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/home/jenkins/workspace/RackHD/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/home/jenkins/workspace/RackHD/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/RackHD/test/tests/api/v2_0/nodes_tests.py", line 286, in test_node_workflows_get
    fail(message='did not raise exception for nodes_get_workflow_by_id with bad id')
  File "/home/jenkins/workspace/RackHD/RackHD/test/.venv/on-build-config/local/lib/python2.7/site-packages/proboscis/asserts.py", line 220, in fail
    raise ASSERTION_ERROR(message)
AssertionError: did not raise exception for nodes_get_workflow_by_id with bad id

CIT tests are all being converted to FIT framework.  Therefore, this has become obsolete and the originator is no longer active on the project.  Please recreate as a FIT test.


While SQL Statement Contains lateral view  explode JSQLParser throw an exception

Hi there
My SQL statement like this
    select
      order_id,
      comment_label_id2,
      create_time,
      score,
      remark
    FROM
      (
        select
          score,
          remark,
          create_time,
          order_id,
          comment_label_id
        from
          bi_ods.t_scd_order_comment
        where
          create_time >= '2016-03-01'
          AND create_time < '2016-03-02'
      ) as t lateral view explode(
        split(comment_label_id, ',')
      ) e as comment_label_id2

lateral view explode is supported by mysql and hiveql
Thank you

Have you solved this??


Add ERC20_ENABLED to make the contract optional

Looks good, but don't we want some/all of the search tests to use hackatom?

That would be nice indeed. The fewer dependencies we have on ERC20, the better. I only commented on the easiest/most critical ones.


Forbid using ! in import paths

I've heard a few reports that people use Webpack import extension syntax (like !!file!./stuff) to customize Create React App loaders. We don't support this officially, and we may accidentally (or on purpose) break this in the future. This also couples apps to Webpack resolution mechanism too hard.
We need to write a Webpack plugin that throws in parsing stage (https://github.com/webpack/docs/wiki/plugins#the-parser-instance-compilerparser) if you attempt to require or import something with ! in the path.

I'm not certain but I'm pretty sure you can't do that because many loaders, use this syntax internally, as part of their implementation. Not sure you could distinguish between those requests and the user made ones, maybe if you plugin before the loaders run? You may also not be using loaders that do this, but some of "core" ones used to at least

Yeah, we'd need to limit this error to the code in user app folder.

Yeah, we'd need to limit this error to the code in user app folder.

even still, the loaders will actively change that code, if you run a plugin after the code has been through the laoder it doesn't matter where it's original location on disk is. Tho I think if you are just throwing an error you probably can run the plugin before any loader activity.

Maybe it would be an idea to write / use an ESLint plugin for this then? Maybe eslint-plugin-import would be a good place for that.

Good idea, @SpaceK33z. I think eslint-plugin-import would be an easy and logical place to add this, and this way it also applies to user code.
I opened a PR in eslint-plugin-import that implements this: https://github.com/benmosher/eslint-plugin-import/issues/586

Nice work @fson!

eslint-plugin-import 2.0.0 was released yesterday with this new rule. I'm making a pull request to add it in our config today.

Awesome! Note you'll need to update every place where we hardcoded the versions in docs.
😞


Pyfakefs case-sensitive rename behavior different from OS on Windows

On Windows 7, renaming a file to the same name with a different case succeeds, but on pyfakefs it fails with the exception: WindowsError: [Error 17] Fake filesystem object: can not rename to existing file: '\FOO'
See reproduction below:
import pyfakefs.fake_filesystem

import os

with open('foo', 'w') as f:
    pass

os.rename('foo', 'foo')

#success
os.rename('foo', 'FOO')

with open('bar', 'w') as f:
    pass

try:
    os.rename('bar', 'foo')
except WindowsError as e:
    pass

os.remove('foo')

fake_filesystem = pyfakefs.fake_filesystem.FakeFilesystem()
fake_os = pyfakefs.fake_filesystem.FakeOsModule(fake_filesystem)

fake_filesystem.CreateFile('foo')
fake_os.rename('foo', 'foo')

#fails WindowsError: [Error 17] Fake filesystem object: can not rename to existing file: '\\FOO'
fake_os.rename('foo', 'FOO')

Good finding, thanks! I actually didn't know such a rename was possible,


Alamofire Network Handler sample file

Include a sample network handler that interacts with the Alamofire networking library v 4.0.

Added a sample handler. It's located in the Examples/Handlers folder.


chore: Move smaller Entity Explorer components into ADS

Description
Moves the following Entity Explorer components into ADS/Templates/EntityExplorer

EmptyState
NoSearchResults
ExplorerContainer

Fixes #38281
Fixes #37609
Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

/build-deploy-preview

/build-deploy-preview


Random 500 Error returned by Traefik

Report a bug
What version of Traefik are you using (traefik version)?
v1.3.0
What did you do?
We are using Traefik as a load balancer using Marathon provider in our Production
Below is our setup
Edge Proxy - Haproxy
Internal proxy Layer - Traefik
We use Haproxy as our edge proxy due to complex rewrites/ redirects and the backends are configured configured with Traefik servers.
Also all our internal service to service communication happens via Traefik.
Here is our traffic flow
API Call --> Haproxy --> Traefik Servers --> Docker containers
Initially when we introduced Traefik in Prod, we just switched the inter service communication that used to happen via internal haproxy load balancers, we did not see any issues.
So we decided to move the Edge Proxy Traffic via Traefik instead of sending directly to app containers. We made this change only to send 10% of our traffic to observe before we switch all traffic.
So out of 3 Edge Haproxy Servers, only one server sends traffic via Traefik and other 2 servers send directly to app containers.
What did you expect to see?
No Change in Behavior
What did you see instead?
After we made this change, we started observing random 500 Errors returned by the Haproxy server sending Traffic via Traefik server. But we dont see that issue on Proxy servers for similar api calls. We dont the see those failed requests reaching the Backend app containers as we dont see any events in the logs during this time
Log Event from Haproxy
Aug 6 22:56:52 localhost.localdomain haproxy[118832]: ::ffff:12:23:234:12:35449 [06/Aug/2017:22:56:51.741] HTTPS~ appname/traefik-80 345/0/0/231/576 500 157 - - ---- 35/34/0/0/0 0/0 {api.abc.cloud||||okhttp/3.4.2} "GET /v1.1/abc/c45f21be84824984b34c8538bd8b519a/abc?offset=1000&count=100 HTTP/1.1"

Log Event from Traefik
<IP_ADDRESS> - - [06/Aug/2017:22:56:52 -0700] "GET /api/abc/c45f21be84824984b34c8538bd8b519a/abc HTTP/1.1" 500 21 "" "okhttp/3.4.2" 44609802 "appname" "http://hostname:31020" 229ms

What is your environment & configuration (arguments, toml, provider, platform, ...)?

configuration
################################################################
# Global configuration
################################################################

# Timeout in seconds.
# Duration to give active requests a chance to finish during hot-reloads
#
# Optional
# Default: 10
#
graceTimeOut = 10

# Traefik logs file
# If not defined, logs to stdout
#
# Optional
#
traefikLogsFile = "/var/log/traefik/traefik.log"

# Access logs file
#
# Optional
#
accessLogsFile = "/var/log/traefik/traefik-access.log"

# Log level
#
# Optional
# Default: "ERROR"
#
logLevel = "DEBUG"

# Backends throttle duration: minimum duration between 2 events from providers
# before applying a new configuration. It avoids unnecessary reloads if multiples events
# are sent in a short amount of time.
#
# Optional
# Default: "2s"
#
ProvidersThrottleDuration = 1

# If non-zero, controls the maximum idle (keep-alive) to keep per-host.  If zero, DefaultMaxIdleConnsPerHost is used.
# If you encounter 'too many open files' errors, you can either change this value, or change `ulimit` value.
#
# Optional
# Default: http.DefaultMaxIdleConnsPerHost
#
MaxIdleConnsPerHost = 200

# If set to true invalid SSL certificates are accepted for backends.
# Note: This disables detection of man-in-the-middle attacks so should only be used on secure backend networks.
# Optional
# Default: false
#
InsecureSkipVerify = false

# Entrypoints to be used by frontends that do not specify any entrypoint.
# Each frontend can specify its own entrypoints.
#
# Optional
# Default: ["http"]
#
defaultEntryPoints = ["http"]

################################################################
# Web configuration backend
################################################################

[web]
address = ":8080"

################################################################
# Mesos/Marathon configuration backend
################################################################

# Enable Marathon configuration backend
#
# Optional
#
#[marathon]
[marathon]

# Marathon server endpoint.
# You can also specify multiple endpoint for Marathon:
# endpoint := "http://<IP_ADDRESS>:8080,<IP_ADDRESS>:8080,<IP_ADDRESS>:8080"
#
# Required
#
endpoint = "http://<IP_ADDRESS>:8080,<IP_ADDRESS>:8080,<IP_ADDRESS>:8080"

# Enable watch Marathon changes
#
# Optional
#
watch = true

# Default domain used.
#
# Required
#
domain = "traefik.service.consul"

# Override default configuration template. For advanced users :)
#
# Optional
#
# filename = "marathon.tmpl"
filename = "/opt/traefik/conf/marathon.tmpl"

# Expose Marathon apps by default in traefik
#
# Optional
# Default: false
#
exposedByDefault = false

# Convert Marathon groups to subdomains
# Default behavior: /foo/bar/myapp => foo-bar-myapp.{defaultDomain}
# with groupsAsSubDomains enabled: /foo/bar/myapp => myapp.bar.foo.{defaultDomain}
#
# Optional
# Default: false
#
groupsAsSubDomains = false

# Enable Marathon basic authentication
#
# Optional
#
[marathon.basic]
httpBasicAuthUser = "xxx"
httpBasicPassword = "xxxxxxx"

# To enable more detailed statistics
[web.statistics]
   RecentErrors = 10
# To enable Traefik to export internal metrics to Prometheus
[web.metrics.prometheus]
   Buckets=[0.1,0.3,1.2,5.0]

# TLS client configuration. https://golang.org/pkg/crypto/tls/#Config
#
# Optional
#
# [marathon.TLS]
# InsecureSkipVerify = true

[retry]

We use Traefik Healthcheck and below is the Marathon Labels for one of the service where we see the failure
  "labels": {
    "consul": "servicename-5654",
    "external": "tag",
    "internal": "tag",
    "prod": "tag",
    "5654": "tag",
    "traefik.backend.healthcheck.path": "/healthcheck",
    "traefik.backend.healthcheck.interval": "10s",
    "traefik.frontend.rule": "PathPrefixStrip:/servicename",
    "traefik.backend": "-servicename",
    "traefik.portIndex": "0",
    "traefik.enable": "true"
  },

We are not able to identify a pattern. We were running Traefik serveres in C4.xlarge and changed the Instance Type to c4.2xlarge to check if any network bandwidth/ resource issue. Appreciate if your help in troubleshooting this issue.

Thanks for your interest in Traefik !
Could you try with the latest version (1.3.5) ?

@idez I am testing version 1.3.5 in preprod. Will update this issue with my result in a day

@ldez tested with 1.3.5 and it broke all the websocket connection related to this change https://github.com/containous/traefik/issues/1930. So i can't say for sure if the version 1.3.5 fixed my original reported issue.
I tried the patch mentioned in https://github.com/containous/traefik/issues/1930 and the wbsocket issue is fixed. So I am going to apply the patch in rest of my preprod stack and test.
Do you have any timelines on when #1930 will be merged and released?

@ldez After applying the patch mentioned in #1930, i dont see the websocket issue but back to the old random failures on other http requests as i described in my bug.

could you provide more logs? traefik --debug

@ldez Are you looking for any specific events so i can filter out those events. Below the some of the log events for which we received 500 status code.
Haproxy
Aug 21 10:09:12 localhost.localdomain haproxy[31211]: ::ffff:<IP_ADDRESS>:41450 [21/Aug/2017:10:08:12.613] HTTPS~ app/traefikserver-80 0/0/0/60001/60001 500 157 - - ---- 1/1/0/0/0 0/0 {api.abc.cloud||||Apache-HttpClient/4.3.6 (java 1.5)} "GET /v1.1/abc/applications?offset=0 HTTP/1.1"
Aug 21 10:16:51 localhost.localdomain haproxy[31211]: ::ffff:<IP_ADDRESS>:41818 [21/Aug/2017:10:15:51.368] HTTPS~ app/traefikserver-80 0/0/0/60001/60001 500 157 - - ---- 1/1/0/0/0 0/0 {api.abc.cloud||||Apache-HttpClient/4.3.6 (java 1.5)} "GET /v1.1/abc/applications?offset=0 HTTP/1.1"
Aug 21 10:32:53 localhost.localdomain haproxy[31211]: ::ffff:<IP_ADDRESS>:42757 [21/Aug/2017:10:31:53.376] HTTPS~ app/traefikserver-80 0/0/0/60004/60004 500 157 - - ---- 1/1/0/0/0 0/0 {api.abc.cloud||||Apache-HttpClient/4.3.6 (java 1.5)} "GET /v1.1/applications HTTP/1.1"
Aug 21 10:41:51 localhost.localdomain haproxy[31211]: ::ffff:<IP_ADDRESS>:43500 [21/Aug/2017:10:40:51.598] HTTPS~ app/traefikserver-80 0/0/0/60001/60001 500 157 - - ---- 1/1/0/0/0 0/0 {api.abc.cloud||||Apache-HttpClient/4.3.6 (java 1.5)} "GET /v1.1/abc/applications HTTP/1.1"
Aug 21 10:43:53 localhost.localdomain haproxy[31211]: ::ffff:<IP_ADDRESS>:43625 [21/Aug/2017:10:42:53.851] HTTPS~ app/traefikserver-80 0/0/0/60001/60001 500 157 - - ---- 1/1/0/0/0 0/0 {api.abc.cloud||||Apache-HttpClient/4.3.6 (java 1.5)} "GET /v1.1/api/3c19537140ed438f83ce423c4e6a4701/applications?offset=0&count=100 HTTP/1.1"
Aug 21 11:07:30 localhost.localdomain haproxy[31211]: ::ffff:<IP_ADDRESS>:45088 [21/Aug/2017:11:07:18.893] HTTPS~ app/traefikserver-80 0/0/0/12044/12044 500 157 - - ---- 1/1/0/0/0 0/0 {api.abc.cloud|||142|Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.3} "PUT /v1.1/api/dt7e29b491d8fb4ad79ca9beccd7d21a96 HTTP/1.1"

Traefik-access.log
<IP_ADDRESS> - - [21/Aug/2017:10:08:12 -0700] "GET /abc/applications HTTP/1.1" 500 21 "" "Apache-HttpClient/4.3.6 (java 1.5)" 153198 "appfrontendA" "http://hostname:31574" 60000ms
<IP_ADDRESS> - - [21/Aug/2017:10:15:51 -0700] "GET /abc/applications HTTP/1.1" 500 21 "" "Apache-HttpClient/4.3.6 (java 1.5)" 153384 "appfrontendA" "http://hostname:31574" 60000ms
<IP_ADDRESS> - - [21/Aug/2017:10:31:53 -0700] "GET /applications HTTP/1.1" 500 21 "" "Apache-HttpClient/4.3.6 (java 1.5)" 153818 "appfrontendA" "http://hostname:31485" 60000ms
<IP_ADDRESS> - - [21/Aug/2017:10:40:51 -0700] "GET /abc/applications HTTP/1.1" 500 21 "" "Apache-HttpClient/4.3.6 (java 1.5)" 154226 "appfrontendA" "http://hostname" 60000ms
<IP_ADDRESS> - - [21/Aug/2017:10:42:53 -0700] "GET /api/3c19537140ed438f83ce423c4e6a4701/applications HTTP/1.1" 500 21 "" "Apache-HttpClient/4.3.6 (java 1.5)" 154308 "appfrontendA" "http://hostname:31574" 60000ms
<IP_ADDRESS> - - [21/Aug/2017:11:07:18 -0700] "PUT api/dt7e29b491d8fb4ad79ca9beccd7d21a96 HTTP/1.1" 500 21 "https://URI/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36" 155003 "appfrontendA" "http://hostname:31485" 12042ms

Traefik Log
time="2017-08-21T10:09:12-07:00" level=warning msg="Error forwarding to http://hostname:31574, err: context canceled"
time="2017-08-21T10:16:51-07:00" level=warning msg="Error forwarding to http://hostname:31574, err: context canceled"
time="2017-08-21T10:32:53-07:00" level=warning msg="Error forwarding to http://hostname:31485, err: context canceled"
time="2017-08-21T10:41:51-07:00" level=warning msg="Error forwarding to http://hostname:31574, err: context canceled"
time="2017-08-21T10:43:53-07:00" level=warning msg="Error forwarding to http://hostname:31574, err: context canceled"
time="2017-08-21T11:07:30-07:00" level=warning msg="Error forwarding to http://hostname:31485, err: context canceled"

@karthimohan that's weird :thinking:
Could you try commenting these sections ?
[web.statistics]
   RecentErrors = 10
# To enable Traefik to export internal metrics to Prometheus
[web.metrics.prometheus]
   Buckets=[0.1,0.3,1.2,5.0]

[retry]

@emilevauge Not sure how relevant is to remove those. But I just did the suggested change in my preprod and going to monitor it for a day and update here

I am seeing the context canceled error as well. this is extremely noticeable when under heavy load.
i ran a, performance test with wrk
wrk -t10 -c100 -d20s --latency
here are the results:
10 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency   527.92ms  218.30ms   1.89s    65.72%
    Req/Sec    19.46     11.15    60.00     82.91%
  Latency Distribution
     50%  517.02ms
     75%  684.67ms
     90%  800.57ms
     99%    1.06s
  3023 requests in 20.09s, 3.21MB read
  Socket errors: connect 0, read 0, write 0, timeout 99
Requests/sec:    150.48
Transfer/sec:    163.84KB

notice the 99 timeouts these are all time="2017-10-27T21:44:46Z" level=warning msg="Error forwarding to http://<IP_ADDRESS>:80, err: context canceled"
if i increase the connections it gets much worse sometimes to the point all requests are failing
are there some settings that need to be tweaked for heavier load?

One reason why this can apparently happen is due to disappearing clients (see also golang/go#20071). Is there a chance that Traefik is running out of capacity or backends cannot keep up with the request rate causing clients to eventually lose patients and prematurely terminate the request to Traefik?

I got same problem. It's too weird. Most of all backend behind is ok but one of them always return 500 with err: context canceled.
Running 20s test @ https://xyz.abc/services/health_check
  10 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency   513.82ms  141.49ms   1.29s    73.54%
    Req/Sec    20.66     12.13    80.00     82.34%
  3696 requests in 20.05s, 1.59MB read
  Non-2xx or 3xx responses: 3696
Requests/sec:    184.38
Transfer/sec:     81.03KB```

hey, we're experiencing the same issue.
it seems that sometimes traefik returns a lot of 500 with the following message: "Error forwarding to http://IP:PORT, err: context canceled".
The servers weren't under unusual load and it's becoming OK after a couple of minutes.
any suggestions?

I suggest to start traefik with the following env var: GODEBUG="http2debug=2". Then look for 500s and check if you see a RST_STREAM right before that. These are requests that are being reset by the (web)client.

I think that issue lies in vulcand/oxy library. The default error handler does this:
func (e *StdHandler) ServeHTTP(w http.ResponseWriter, req *http.Request, err error) {
	statusCode := http.StatusInternalServerError
	if e, ok := err.(net.Error); ok {
		if e.Timeout() {
			statusCode = http.StatusGatewayTimeout
		} else {
			statusCode = http.StatusBadGateway
		}
	} else if err == io.EOF {
		statusCode = http.StatusBadGateway
	}
	w.WriteHeader(statusCode)
	w.Write([]byte(http.StatusText(statusCode)))
	log.Debugf("'%d %s' caused by: %v", statusCode, http.StatusText(statusCode), err)
}

so it for ContextCancelled error tries to write 500 SC which is then catched by metrics middleware in Traefik and reported as 500. The question is should it be fixed in Traefik by using custom ErrorHandler or in oxy? It drives our Monitoring crazy so I would like to help with PR I just want to know the preference where and how to fix it.

I want to confirm @mrnugget's findings. I'm able to reproduce this error when running siege and cancelling it midway.
An example:
echo "GET https://example.com" | vegeta attack -duration=600s -rate=10 | tee results.bin | vegeta report -reporter=json | jq

I'm able to reproduce the issue if I CTRL+C midway through the stress test (the same effect as constantly refreshing a page in the browser before the client has received a response).
It doesn't seem to affect our users in any way, feels more like a "false alarm" by how Traefik is logging these errors.

Submitted https://github.com/vulcand/oxy/pull/155 with the fix to oxy, and confirmed that it no longer reports those false alarms using wrk.

Closed by #3777.


Use unsigned int in glDrawElement function.

For face_geometry and gl_animation ... of objectron.

Refer this link.
https://stackoverflow.com/questions/4974507/gldrawelements-not-working-on-iphone-but-gldrawarrays-works
But, I can't use this extension.


DOC: circle should ignore gh-pages

1 try but config.yml will still not be in gh-pages branch

Codecov Report

Merging #144 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #144   +/-   ##
=======================================
  Coverage   79.52%   79.52%
=======================================
  Files          11       11
  Lines         972      972
  Branches      145      145
=======================================
  Hits          773      773
  Misses        157      157
  Partials       42       42

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 31dd3c2...5d75e16. Read the comment docs.


Devtooling 217

Also you need to run the go generate command and then check in the generated markdown file.

Done


Question: Quick way to check if key exists?

Hello!
Great wrapper, I accidenlty found it, I think "toolkit" a little bit misleading on go-awesome, but may be it's just me...
If there a short cut to check if a key exists? Without creating a struct and pointer there?
I understand it may be not a big deal, but still?

Hello !

Great wrapper, I accidenlty found it, I think "toolkit" a little bit misleading on go-awesome, but may be it's just me...

Yes, thanks for your feedback, it's kinda hard to find an accurate definition

If there a short cut to check if a key exists? Without creating a struct and pointer there?

There is no builtin way to check if a key exists in Bolt or in Storm but there are a few tricks:
Using GetBytes:
_, err := db.GetBytes("YourStruct", "TheKey")
if err == storm.ErrNotFound {
  // doesn't exists
}
...

GetBytes copies the data returned by Bolt so it can be accessible even after the transaction is closed. When testing if a key exists, this copy is unnecessary.
Using Bucket, you can directly access the Bolt API:
v := db.Bucket("YourStruct").Get([]byte("YourKey"))
if v == nil {
  // doesn't exists
}
...
...

Hello,
Thanks a lot, cool trick I will proceed with this :-)


TF: Tungsten Fabric needs a Public IP per service, ACS UI allows to try to place more than 1 service per public IP.

ISSUE TYPE

Bug Report

COMPONENT NAME

UI (maybe API as well)

CLOUDSTACK VERSION

4.18

CONFIGURATION

N/A
OS / ENVIRONMENT

KVM on Centos 7 , Tungsten Fabric
SUMMARY

In a normal isolated network a user can add multiple services with the same public IP (sourceNAT, Port Forwarding, etc...).
With the Tungsten Fabric Plugin that's not possible (no conserve mode equivalent). But the UI doesn't stop an end user from trying (and getting errors)
STEPS TO REPRODUCE

Add isolated network, go to the source nat public IP, try to add a service (e.g. port forwarding).

EXPECTED RESULTS

UI shouldn't allow to place more than 1 service per public IP

ACTUAL RESULTS

UI allows to attempt to place more than 1 service per public IP. Action fails without proper explanation

fixed by #7511


12 introduce admin authentication

Closes #12

What remains:

[ ] Use local storage to retrieve the connected user on page refresh
[ ] Introduce illustrations from unDraw with a Nothing here page at index (/)
[ ] Introduce rooting to /admin pages:

/admin/login - login page currently at /login
/admin/school - schools page currently at /school
/admin - admin home page redirecting to schools page

[ ] Add general links to

Github repository (as source code)
Swagger and Redoc UI (as API documentations)
Admin panel (i.e. /admin/)


Circle radius is incorrect

With increasing latitude from the equator, polygon generated by Terraformer.Circle uses smaller radius than it is in reality.
See this comparison with @turf/circle library of circles with 250km radius on latitudes 0, 10, 20, ...

Turf - grey, Terraformer - blue
Please excuse my layman's description, I just compared the two libraries and Turf's output seems more correct by visual inspection.

that definitely looks like a bug to me.
if you're interested in putting together a PR, I adapted a JS implementation of Vicenty's Formulae a couple years ago that you're welcome to steal.
https://github.com/Esri/geotrigger-editor/pull/225

I have used another library meanwhile.

published as<EMAIL_ADDRESS>


Build test cases in parallel

I think this would currently be blocked by Cargo. Concurrent invocations of cargo build on different binaries in the same project seem to execute one at a time. There may be alternative ways to implement this instead.

I tried this code:
let mut threads = vec![];
for i in 0..3 {
    let t = trybuild::TestCases::new();
    threads.push(std::thread::spawn(move || {
        t.compile_fail(format!("tests/ui/name{}*.rs", i));
    }));
}
for thread in threads {
    thread.join().unwrap();
}

Though, it does not work, as the second thread to run uses the same stderr file of the first one.

Implemented in #168.

When running code coverage I need to pass --test-threads 1 to cargo, but trybuild still runs in parallel now that I've upgraded. Could trybuild somehow honor this?

@jhpratt I think you can set RUST_TEST_THREADS=1 environment variable.
That said, it seems to be an issue of the -C instrument-coverage itself (https://github.com/rust-lang/rust/issues/91092), so I think we need to set that environment variable on the coverage tool (probably cargo-llvm-cov in this case) side.

RUST_TEST_THREADS=1 does not help here. For the time being, at least, I'm probably going to do separate runs and merge them.


allows the client to use self signed certificates with strict ssl.

This allows user to have self signed certificates verified.

Would generally want to see test coverage for this, but seeing as it's a simple curl opt addition, we can mover forward.


Stuck in a loop.

$ grind github.com/btcsuite/btcd gets stuck in a loop swapping var declarations:
EDIT: cpuminer.go
@@ -73,8 +73,8 @@ func (m *CPUMiner) speedMonitor() {
        defer ticker.Stop()

 out:
-       var hashesPerSec float64
        var totalHashes uint64
+       var hashesPerSec float64
        for {
                select {
                // Periodic updates from the workers with how many hashes they

36
EDIT: cpuminer.go
@@ -73,8 +73,8 @@ func (m *CPUMiner) speedMonitor() {
        defer ticker.Stop()

 out:
-       var totalHashes uint64
        var hashesPerSec float64
+       var totalHashes uint64
        for {
                select {
                // Periodic updates from the workers with how many hashes they

Should be fixed by most recent push; go get -u rsc.io/grind


Null coalescing operator is not accepted

Power Query includes a hidden null coalescing operator: ??
This syntax is accepted:
Value??OtherValue
It would be nice if this was accepted by the parser, which throws the problem "Expected to find a right parenthesis ... but a question mark was found instead powerquery(Error.Parse) [7,70]"
See more here

Tracked in the parser repo - https://github.com/microsoft/powerquery-parser/issues/173
This operator was a recent addition to the M language. I'm not sure it is has been fully documented or is available in all Power Query environments, but we should have it added to the current parser.

This isn't supported for folding yet, unfortunately. I was going to hold off on documenting it until that was possible.


Added Helsingborg middle school

Rydebäcksskolan is one of several middle school (grundskola) in Helsingborg, Sweden https://rydebacksskolan.helsingborg.se/
List of all schools in Helsingborg on the City of Helsingborg website
https://helsingborg.se/forskola-och-utbildning/grundskola/grundskolor-i-helsingborg-2/
Portal for schools of City of Helsingborg
https://skolportalen.helsingborg.se/

@nicmar First stage of verification passed, official domain is facebook.com as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.facebook.com/CityPhonei/

@nicmar Thank you for the request and the details. Would you please tell us where the city or the school mention utb.helsingborg.se as an official email domain for the teachers or students of the school?

@nicmar You might miss my previous comment. Please react.

@nicmar I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


[Signing 2] Add sign badge to collection card

here
before

^ Seems like we get inconsitent card sizing now, and title and company don't get cut off with ellipsis.
Is that something you can fix, or should we just add the badge to the existing cards without changing how they work?

I think we can replace this by https://github.com/ansible/ansible-hub-ui/pull/1763 , looks like adding SignatureBadge to the existing CardHeader works fine by itself :)

I probably just missed a PF prop on the card. But your PR seems smaller, we can roll with that.
Closing in favour of #1763


Better Component testing helpers

Applications often want to write tests that assert against something in a component, in test mode a component will render a test version, containing the arguments passed to it as JSON (not fetching anything from static).
Currently apps tend to do a substring match on the JSON within the component wrapper, which is a bit hacky. Ideally there would be test helpers that can assert a specific argument was passed to the component, without having to parse the JSON out of the markup in each application.
eg,
assert_component('title', 'context', 'foo')

This requires writing helpers for a set of testing frameworks, but as we standardised our rails frontends that should be easier, and at the least we could add a helper for the most common one.
Heres an example for an application implementing these helpers itself: https://github.com/alphagov/government-frontend/blob/master/test/test_helper.rb#L24-L83
It would be nice if this was re-usable in other apps.

Frontend uses:
assert page.has_selector?(shared_component_selector('beta_label'))

government-frontend has a selection of component asserts now: https://github.com/alphagov/government-frontend/blob/master/test/test_helper.rb#L39-L121
If this does get standardised that would be a good place to pick from.

This has been helpful in collections for testing arguments to components:
def within_static_component(component)
    within(shared_component_selector(component)) do
      component_args = JSON.parse(page.text).with_indifferent_access
      yield component_args
    end
  end

https://github.com/alphagov/collections/blob/61c18b335770a93b154686addca27313aea5737c/test/integration_test_helper.rb#L19-L24
Based on:
https://github.com/alphagov/government-frontend/blob/master/test/test_helper.rb#L91-L96


Discrepancy Between Manifest & Catalog - Non-Defined Columns Missing

While looking at the results of this last version 0.7.0, I noticed that one of my models only had a single column defined within the LookML.  I dug into it and realized that this is because I only defined a single column within my schema.yml for that model. I dug into the manifest of the specific model model using this command cat target/manifest.json | jq '.nodes["model.my_project_name.model_name"]' and noticed that only a single column is returned in the manifest.
I then pulled up the catalog with this command cat target/catalog.json | jq '.nodes["model.my_project_name.model_name"]'  and there were 229 columns returned.
I'm not sure if this is an opinionated stance that has been taken (ie, columns that make it to the Looker view should be defined within the corresponding schema.yml) but wanted to highlight just in case it wasn't intentional.

Thanks for raising this one (came up even earlier than I thought!)
So this is an intentional decision so that only resources declared in dbt appear in looker. This really suits the way we work but might not be for everyone.
I'm quite curious though what would be most useful for your team? I guess you were at least expecting columns to appear for models declared in dbt. What about tables in the warehouse but not in the dbt schema?

I'm a big fan of this decision. My personal ethos is that teams should aim for 100% column coverage, as thats the best way to pass on domain knowledge.
That being said, 100% column coverage is a bit of an aspirational thing and could potentially impact teams that want to iterate model --> lookml creation quickly and programmatically with dbt2looker. I'm imagining a scenario where someone has model_1 and model_2 that create model_3. They use dbt_utils.star in model_3 to get all columns from both models. If they added 2 columns to model_1 and didn't document them, I could see that potentially being an issue that isn't caught until some raises a flag with the new dimensions not appearing in the LookML.
I think the best solution (and probably the most work to be honest) would be the creation of a dbt2looker.yml file where this could be defined at the project level. Default setting would be the current as-is state of not bringing in fields that aren't declared but this could be changed to include everything. That gives different teams the flexibility to choose an option that fits their style of development and documentation.

perhaps this could be another meta option, eg a default like infer-looker-dimensions=false and then if you flip the switch, automatically generate column descriptions indicating that the field was machine generated, because fundamentally we want some sort of guard to caution users when they interact with data that has not been explicitly documented.
I think this might solve for the open question discussed in dbt slack


find-reference: display row:column instead of absolute character offset

more ideas to make find refs a real swiss army knife:

Open the results in separate tab such as atom's Project Find Results to have more room.
Show the source line for context, with the reference itself highlighted inside.
Make the clickable area bigger (css block) instead of just the file name as a link which is currently very very small to click.
Add keyboard shortcuts to go to next/prev in reference list.

The commit does not include all your ideas.
Please open a separate issue for every enhancement. :)
tststs