Add colored margin in Inspector for arrays and dictionaries

Closes https://github.com/godotengine/godot-proposals/issues/2018.
Closes https://github.com/godotengine/godot-proposals/issues/6987.
This PR aims to enhance readability of nested data by adding a colored border for arrays and dictionaries as it was done for Resources in #45907.

I've updated a bit this PR to have better readability for dictionaries especially or the Panel around the element to add. Here is how it nows looks like with multiple nested data (Resources, Arrays and Dictionaries) :

Thanks for the contribution!
I am not 100% against the idea, but I kind of find useful that only sub-resources are highlighted. It is kind of making clear which parts of the properties might be things that are not part of the current scene. Thus adding highlighting to dictionaries is a bit confusing to me, and adds a lot of noise.
I'd think I'd rather have bit more feedback on that solution before merging it, and that it might require a dedicated proposal to be sure it has enough baking.
But that being said, I don't have a better solution for now to solve the readability issue, so it might be an acceptable solution for now.

So I've updated this PR according to https://github.com/godotengine/godot-proposals/issues/6987#issuecomment-1940142900 . I think the implementation is ot really good yet but wanted some feedback on visual aspects
I've created two editor settings :

an enum indicating which EditorProperty should be colored (Containers & Resources, All Resources, External Resources)
a boolean indicating wether to add a border or not to all containers and resources even when they are not colored.

I feel like the boolean setting could be removed and always set to true but maybe some people might like it without it so I decided to keep the posibility to change for now.
Here are in the order :

Containers & Resources
Containers & Resources (with borders)
All Resources
All Resources (with borders)
External Resources
External Resources (with borders)

You could format those previews in your reply using tables https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables

I like the nested_color_mode I'll fill the doc once we are fixed on an implementation
For the other parameter I'm in favor of making it go away. I kept it as it acts as it used to before this PR this is like a legacy mode. I could make it true except for the all resources and rename this mode Legacy?

I finally came back to this hopefully for the last time I reduced the size when there is no border (see comparison below). I also changed the name of the setting and added description for both settings. I'm not sure of how to integrate inside the other setting.

Changing color mode to Resources has no effect on built-in resources.

Changing color mode to Resources has no effect on built-in resources. EDIT: Though looking at the code, it does not make sense 🤔

I inverted Resource and External Resource in the list because realized it made more sense in this order thought I had done the same inversion in the enum but in fact did not :( Fixed it.

External Resources coloring does not work if the external resource is inside internal resource (e.g. AtlasTexture with texture). Nor sure if intended 🤔

External Resources coloring does not work if the external resource is inside internal resource (e.g. AtlasTexture with texture). Nor sure if intended 🤔

This is not the expected behavior. I'll try to investigate

I couldn't reproduce what you described but discover the color wouldn't disappear when closing the editors which I fixed.

The last update added a merge commit, could you rebase on master to remove it?

Thanks!


Error when compiling: 'TORCH_CHECK_ARG' was not declared in this scope

Hi,
My environment is PyTorch 1.8.1+cu101 and CUDA 10.1.
When I compiled DCNv2, an error was encounted:
/DCNv2_latest/src/cpu/dcn_v2_cpu.cpp: In function 'std::vector<at::Tensor> dcn_v2_cpu_backward(const at::Tensor&, const at::Tensor&, const at::Tensor&, const at::Tensor&, const at::Tensor&, const at::Tensor&, int, int, int, int, int, int, int, int, int)':
/DCNv2_latest/src/cpu/dcn_v2_cpu.cpp:141:5: error: 'TORCH_CHECK_ARG' was not declared in this scope
     TORCH_CHECK_ARG(input.is_contiguous(), 1, "input tensor has to be contiguous");
     ^~~~~~~~~~~~~~~
/DCNv2_latest/src/cpu/dcn_v2_cpu.cpp:141:5: note: suggested alternative: 'TORCH_CHECK_MSG'
     TORCH_CHECK_ARG(input.is_contiguous(), 1, "input tensor has to be contiguous");
     ^~~~~~~~~~~~~~~
     TORCH_CHECK_MSG

I wonder how to solve this problem.
Thanks a lot.

Accordingly to the latest README.md. Try to checkout the last commit. e.g
git checkout fa9b2fd740ced2a22e0e7e913c3bf3934fd08098

i encountered the same problem. do u figure it out now?

I encountered the same. Still no clue to solve
` error: 'TORCH_CHECK_ARG' was not declared in this scope
TORCH_CHECK_ARG(input.is_contiguous(), 1, "input tensor has to be contiguous");
........
........
/{my_prokect_dir}/src/lib/models/networks/DCNv2_latest-master/src/cpu/dcn_v2_cpu.cpp:235:65: warning: 'T* at::Tensor::data() const [with T = float]' is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
columns.data<scalar_t>());
^
In file included from /usr/local/lib/python3.6/dist-packages/torch/include/ATen/Tensor.h:3:0,
from /usr/local/lib/python3.6/dist-packages/torch/include/ATen/Context.h:4,
from /usr/local/lib/python3.6/dist-packages/torch/include/ATen/ATen.h:9,
from /data/aif/hongyu/may_compare_task/centernet/centernet-master/src/lib/models/networks/DCNv2_latest-master/src/cpu/dcn_v2_cpu.cpp:4:
/usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/TensorBody.h:395:7: note: declared here
T * data() const {
^
error: command 'g++' failed with exit status 1
                                                                              ^

`

I encountered the same. Still no clue to solve

error: 'TORCH_CHECK_ARG' was not declared in this scope
TORCH_CHECK_ARG(input.is_contiguous(), 1, "input tensor has to be contiguous");
........
........
/{my_prokect_dir}/src/lib/models/networks/DCNv2_latest-master/src/cpu/dcn_v2_cpu.cpp:235:65: warning: 'T* at::Tensor::data() const [with T = float]' is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
columns.data<scalar_t>());
^
In file included from /usr/local/lib/python3.6/dist-packages/torch/include/ATen/Tensor.h:3:0,
from /usr/local/lib/python3.6/dist-packages/torch/include/ATen/Context.h:4,
from /usr/local/lib/python3.6/dist-packages/torch/include/ATen/ATen.h:9,
from /data/aif/hongyu/may_compare_task/centernet/centernet-master/src/lib/models/networks/DCNv2_latest-master/src/cpu/dcn_v2_cpu.cpp:4:
/usr/local/lib/python3.6/dist-packages/torch/include/ATen/core/TensorBody.h:395:7: note: declared here
T * data() const {
^
error: command 'g++' failed with exit status 1

                                                                              ^

I encountered the same problem. Do you figure it out now?

One possible solution to the error is to downgrade PyTorch to version 1.6.x. This problem may be caused by incompatible versions of DCNV2 with PyTorch.


jvm.options can be populated with duplicated jvm options.

If the build pack configuration adds a jvm option that is already set in the jvm.option file, the jvm option is duplicated.

fixed by #280


Thin Server Not Starting Fake

I'm doing something wrong here... hopefully something simple.  I'm try to run the pusher-fake in development with the rails s command. I'm running rails 4.2.9 with pusher-fake 1.8.0 and pusher 0.18.0.
In my config/environments/development.rb, I have:
  require 'pusher'

  # Ensure Pusher configuration is set if you're not doing so elsewhere.
  Pusher.app_id = "MY_TEST_ID"
  Pusher.key    = "MY_TEST_KEY"
  Pusher.secret = "MY_TEST_SECRET"

  # Require the base file, which immediately starts the socket and web servers.
  #
  # If you're including this file in multiple processes, you may want to add an
  # additional check or even possibly hard code the socket and web ports.
  require "pusher-fake/support/base"
  PusherFake.configuration.verbose = true
  PusherFake.configuration.logger  = Rails.logger

In my application code I have:
    <%- if defined?(PusherFake) -%>
      var pusher = <%= PusherFake.javascript %>;
    <%- else -%>
      var PusherOptions = { encrypted: <%= Settings.pusher.encrypted %> };
      var pusher = new Pusher('<%= Settings.pusher.key %>', PusherOptions);
      pusher.port = 443;
    <%- end -%>

When I start the server with rails s, I get:
=> Booting Thin
=> Rails 4.2.9 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server
Thin web server (v1.7.2 codename Bachmanity)
Maximum connections set to 1024
Listening on localhost:3000, CTRL+C to stop

Notice there is no mention of the pusher-fake running.
When I try to run it in irb (bundle exec irb), then:
require 'pusher'
Pusher.app_id = "MY_TEST_ID"
Pusher.key    = "MY_TEST_KEY"
Pusher.secret = "MY_TEST_SECRET"
require "pusher-fake/support/base"

I get this error:
NameError: uninitialized constant PusherFake
Did you mean?  Pusher

What am I missing?

The uninitialized constant error is because you need to require "pusher-fake". When running bundle exec irb it's not actually loading anything from your Gemfile. If you have the dependency in the test group, then it also won't work if you run bundle exec rails console unless you run RAILS_ENV=test bundle exec rails console.
Perhaps I should add require "pusher-fake" to the base support file, instead of assuming it's being loaded elsewhere. Not sure, since that could also be confusing in some cases.
That being said, it seems like you should be seeing the same error when running the server. Can you provide the group and line for pusher-fake in your Gemfile?

You are correct.
I fixed the problem by putting require 'pusher-fake' before the require 'pusher-fake/support/base'
Additionally I had to escape the html in the application:
      var pusher = <%= PusherFake.javascript.html_safe %>;

@debaillie Awesome. Let me know if I can help out with anything else.

FYI added a warning for this case: https://github.com/tristandunn/pusher-fake/commit/29d2e4c7aabd93395c41dd99129330c725ac8177


local STT

/claim #322
PR:Enhance Local Speech-to-Text (STT) Functionality
#Summary
This PR addresses the issue of excessive noise, such as unnecessary "thank you" phrases, in the local Speech-to-Text (STT) output when using the Whisper model. It introduces a new -a argument to the CLI, allowing users to select the appropriate Whisper model variant (Tiny) while mitigating unwanted noise in transcriptions.
#Key Changes
Model Configuration Enhancement:
Added -a argument to switch between different Whisper model variants tiny.
Implemented logic to reduce or eliminate extraneous phrases like "thank you" based on the chosen model variant.
Performance Optimization:
Optimized Whisper model performance to ensure that the application remains efficient on consumer-grade hardware.
Reduced resource consumption to prevent significant degradation of system performance during STT processing.
Compatibility and Build Integration:
Ensured that the application can still be compiled and built seamlessly in GitHub Actions and other CI/CD environments.
Verified that the new configuration does not introduce any build issues or break existing functionality.
#Future Work
Explore additional optimizations for Whisper models to further refine transcription quality and performance.
Monitor user feedback and make iterative improvements based on real-world usage scenarios.
#Checklist
Code compiles and runs without issues.
Passed all tests and verified performance metrics.
Ensured compatibility with existing build pipelines and CI/CD processes.

You joking right?


Settings panel unusable with notebook trackpad

The settings panel is unusable on a small screen laptop without external mouse.
Why?
The only way to see all settings on a configuration-section, scrolling is required due to the small screen.
But this is only possible by dragging the very small indicator/handlebar of the vertical-scrollbar using the trackpad of the notebook.
And this is moving way to fast due to the scrollabe pagesize.
I tried clicking in the scrollable area and then use my cursor keys on the keyboard,
unfortunately this is not working..

https://github.com/microsoft/vscode/issues/66237


when i'm useing websocket, there are error : "write response failed, error: http: connection has been hijacked"

My problem
In msg gateway service , after the websocket conn is builded, i send the message, there sender is recevied response, and recipient also receive the messgage. But the second send message is failed
There are error :"httpx/responses.go:78","content":"write response failed, error: http: connection has been hijacked"
To Reproduce
Steps to reproduce the behavior, if applicable:

The code is
func ws() {
 var wsConfig wsconfig.Config
 conf.MustLoad(*wsConfigFile, &wsConfig)
 serveCtx := servectx.NewServiceContext(wsConfig)
 wsConfig.RestConf.Timeout = 0
 server := rest.MustNewServer(wsConfig.RestConf)
 defer server.Stop()

 handler.RegisterHandler(server, serveCtx)
 utils.PrintlnSuccess("Starting websocket server at")
 server.Start()
}

 func RegisterHandler(server *rest.Server, serveCtx *servectx.ServiceContext) {
     logic.NewMsgGatewayLogic(context.Background(), serveCtx)
     server.AddRoutes([]rest.Route{
 	    {
 		    Method:  http.MethodGet,
 		    Path:    "/login",
 		    Handler: MsgGatewayHandler(serveCtx),
 	    },
     })
  }

 func MsgGatewayHandler(serveCtx *servectx.ServiceContext) http.HandlerFunc {
     return func(writer http.ResponseWriter, request *http.Request) {
 	    var req types.Request
 	    if err := httpx.Parse(request, &req); err != nil {
 		    httpx.Error(writer, err)
 		    return
 	    }
 	    ws := logic.NewMsgGatewayLogic(context.Background(), serveCtx)
                 // verify token
 	    resp, ok := ws.MsgGatewayVerify(&req)
 	    if ok {
 		    logx.Info("resp uid is", resp.Uid)
 		    err := ws.WsUpgrade(resp.Uid, writer, request, nil)
 		    if err != nil {
 			    return
 		    }
 		    httpx.WriteJson(writer, http.StatusOK, resp)
 	    } else {
 		    http.Error(writer, http.StatusText(http.StatusUnauthorized), http.StatusUnauthorized)
 	    }
     }
 }

The error is

  2022/07/08 10:44:34 http: response.WriteHeader on hijacked connection from github.com/zeromicro/go-zero/rest/handler.
  (*loggedResponseWriter).WriteHeader (loghandler.go:66)

 2022/07/08 10:44:34 http: response.Write on hijacked connection from github.com/zeromicro/go-zero/rest/handler.
 (*loggedResponseWriter).Write (loghandler.go:62)

 {"@timestamp":"2022-07-08T10:44:34.266+08:00","caller":"httpx/responses.go:78","content":"write response failed, error: http:
 connection has been hijacked","level":"error"}

Environments :

OS: window
go-zero version 1.3.4
goctl version 1.3.8

Please give a runnable example, thanks!

ok, there is a example of my project: https://github.com/Tony-Jack2017/work-test.git。

https://github.com/zeromicro/zero-examples/tree/main/chat
Please try this to see if anything wrong.


no longer use unsafe package for string/bytes conversion

Codecov Report

:exclamation: No coverage uploaded for pull request base (fix-unsafe@fd92fd2). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 561bc5b differs from pull request most recent head 14ce35f. Consider uploading reports for the commit 14ce35f to get more accurate results

@@              Coverage Diff              @@
##             fix-unsafe    #1775   +/-   ##
=============================================
  Coverage              ?   70.68%
=============================================
  Files                 ?      381
  Lines                 ?    32478
  Branches              ?        0
=============================================
  Hits                  ?    22957
  Misses                ?     7904
  Partials              ?     1617

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 fd92fd2...14ce35f. Read the comment docs.


update(outputs): add configuration option for tags in json outputs

What type of PR is this?
/kind cleanup
/kind feature
Any specific area of the project related to this PR?
/area engine
/area tests
What this PR does / why we need it:
Since the recent merge of https://github.com/falcosecurity/falco/pull/1714, tags and source fields are now part of both the grpc and json outputs. However, the semantic of the json output is not clear in some corner cases, such as when no tags are defined in a rule. Also, users can't configure whether to include tags in the json outputs or not, which instead is possible for the output field. Moreover, no test cases are yet present for asserting the expected outcome of these corner cases. These issues were reported in https://github.com/falcosecurity/falco/pull/1714#issuecomment-924800821 by @leodido (thank you!!)
As such, this PR contributes with the following:

Adding the json_include_tags_property configuration option, so that users can decide whether to include tags in the json outputs or not. By default this is set to true to not introduce breaking changes for clients that currently expect the field to be present.
Clarifying the expected outcome in the corner cases arising when a rule has no defined tags.
Adding test cases asserting the expected outcomes of the corner cases, and updating the test suite to support the new configuration option.

Additional Context:
The table below describes the expected outcomes in the json outputs by using the new configuration option.

 json_include_tags_property = true
 json_include_tags_property = false

Rule with no tags
(1) json has a field tags=[]
(2) json has no tags field

Rule with tags
(3) json has a field tags=[...]
(4) json has no tags field

These cases are covered by the following tests:

json_output_empty_tags_property: Case (1)
json_output_no_tags_property: Cases (2) and (4)
stdout_output_json_strict: Case (3)

Does this PR introduce a user-facing change?:

update(outputs): add configuration option for tags in json outputs

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jasondellaluce
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.30.0
/cc @leodido
/cc @Issif

LGTM label has been added.  Git tree hash: 42163e871e0526a78dcab56258b75f3182c27bbf

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[BUG] error message duplicated for command rudr system:info

[root@iZj6cc54ecpc3pm8t9yctuZ Rudrx]# vela system:info
fail to get cluster version, err: oam-kubernetes-runtime not found in your kubernetes cluster, try `vela system:init` to install.
Error: oam-kubernetes-runtime not found in your kubernetes cluster, try `vela system:init` to install.

please help fix this minor issue， thanks

Fixed in #303 by @mosesyou .


Add styling for Square Image Hero

Includes gold "ribbon" style for the H1 and a few responsive tweaks for layout and font sizing.

Pending a request to OTS to add <span> element inside h1


Update start.sh

changes made cause on each docker container restart, the config was lost and a restore is necessary... with this was the config is persistent on the mapped folder.
for information I use it on synology.

Merged sorry first time i've had to go over this stuff.


addNewBlock, initial

In the example for adding an image, the addNewBlock function has a parameter for data (the third parameter) seen here:
if (response.status === 200) {
          // Assuming server responds with
          // `{ "url": "http://example-cdn.com/image.jpg"}`
          return response.json().then(data => {
            if (data.url) {
              this.props.setEditorState(addNewBlock(
                this.props.getEditorState(),
                Block.IMAGE, {
                  src: data.url,
                }
              ));
            }
          });

I've been going through the source and it looks like you can add several different types, like Block.UNSTYLED or Block.H1. However, I can't figure out what the data object should be for other types. I was thinking something like {text:'hello') for Block.H1.
Any recommendations would be greatly appreciated! Thanks

addNewBlock adds an empty block of type given by 2nd argument. 3rd arg is the metadata associated with the block. This cannot be used to add blocks with initial text. This is what you want
const addNewBlockWithText = (editorState, newType = Block.UNSTYLED, text) => {
  const selectionState = editorState.getSelection();
  if (!selectionState.isCollapsed()) {
    return editorState;
  }
  const contentState = editorState.getCurrentContent();
  const key = selectionState.getStartKey();
  const blockMap = contentState.getBlockMap();
  const currentBlock = getCurrentBlock(editorState);
  if (!currentBlock) {
    return editorState;
  }
  if (currentBlock.getLength() === 0) {
    if (currentBlock.getType() === newType) {
      return editorState;
    }
    const newBlock = currentBlock.merge({
      type: newType,
      data: getDefaultBlockData(newType, initialData),
      text: text // <- this is the change that you want
    });
    const newContentState = contentState.merge({
      blockMap: blockMap.set(key, newBlock),
      selectionAfter: selectionState,
    });
    return EditorState.push(editorState, newContentState, 'change-block-type');
  }
  return editorState;
};

Hey there, any update on this? I am in a similar situation in that I would like to force a focus/new block of text after a successful image upload. Currently when users upload an image they need to hit the enter key in order to proceed writing a narrative. Is there any way to force this enter-key or automatically add an empty text block after image upload? @brijeshb42  @niwaa


what is the meaning of the self.temperature used in the binarization process of weights?

Thanks for your attention to this work.
As described in the paper, we use the progressive weight binarization technique [0] and the self.temperature in HardBinaryConv class controls the binarization degree during training. It starts from 1.0 and evolves to 0.0 following an exponential decay scheme.
Wish this is helpful for you.
[0] BoolNet: Minimizing The Energy Consumption of Binary Neural Networks


📃:  Weather Dashboard

🔴 Title: Weather Dashboard
🔴 Tech stack:
Frontend: HTML, CSS, JavaScript (React optional)
API: OpenWeatherMap API
🔴 Objective:
To create a web-based weather dashboard that displays current weather conditions and a 5-day forecast for a specific location.
🔴 Summary:
The Weather Dashboard fetches real-time weather data using the OpenWeatherMap API and displays current temperature, humidity, and weather conditions. Users can search for weather by city and view a 5-day forecast. The app also includes an option to switch between Celsius and Fahrenheit.
📸 Screenshots:
N/A
✅ Details to Include When Taking the Issue:
Name : Rahul Bamaniya
Participant Role, GSSOC, Hacktoberfest,gssoc-extd

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

Sorry, someone is already working on this. Do not be demotivated and raise a new issue.


Connect to Microsoft OneDrive - "Token cache is empty"

I have just installed the add-on and wanted to configure it.
The web interface says initializing permanently.
In the protocol section it says the following:
  11/19/2024 20:25:16 [4] Info: Anonymous Telemetry Disabled
  11/19/2024 20:25:16 [4] Info: Backup interval configured to every 24 hours
  11/19/2024 20:25:16 [4] Warning: Token cache is empty

Unfortunately, I don't have a code or link to verify with OneDrive anywhere. Am I doing something wrong or is it a bug?

I just saw that I`m not the only one with this issue. You are already duscussing in the previous issue.


feat: common eval pipeline

Our current common evaluation code is all in pandas, and some functions are quite tightly coupled to the old EvalDataset. I wonder if it's worth redoing or just going with the old, as there's a fairly substantial amount of functionality that needs to be rewritten.
Also unsure where the speed bottleneck is. Bootstrapping, other transformations?


Less trace output

Please don't pollute the cds server's bootstrapping output

Thanks.. I might replace the console logs by cds.log in a separate PR.

Published with 0.3.0


refresh information

only refresh wifi sstate, sound slider state, 3ds slider state, battery % and battery volt.

Lol but you delete the screenshots feature without mentioning that anywhere in the description.

it's fixed now.

I was gonna merge anyway cause I'm going to be coming up with a new way of taking screenshots, but thanks!


AWS Cloudwatch log problem

I have reviewed 2 other closed cases involving AWS Cloudwatch where stuff was fixed:
https://github.com/darold/pgbadger/issues/581
https://github.com/darold/pgbadger/issues/521
https://github.com/darold/pgbadger/issues/609
So it appears pgbadger works fine after fixes in those cases, but it doesn't work fine in my scenario. I am using today's master.zip file for pgbadger, version 11.5 on CentOS 8.
We are using Aurora 11 for Postgres.  We export logs from aurora to cloudwatch and then to S3 with a command like this which generates a full day worth of logs:
aws logs create-export-task --task-name <my task name-200508> --log-group-name "/aws/rds/cluster/<my task name>/postgresql"  --log-stream-name-prefix "<my task name>-0." --from<PHONE_NUMBER>000 --to<PHONE_NUMBER>000 --destination "<my-policy-test" --destination-prefix "<my task name>/20200508"
Cloudwatch created 4 streams for day, May 8 , 2021,  so we download them from S3 like this:
aws s3 cp s3://<my-policy-test>/<my task name>/20200508/<cloudwatch value>/<my task name>-0.0/000000.gz ./0000001.gz
aws s3 cp s3://<my-policy-test>/<my task name>/20200508/<cloudwatch value>/<my task name>-0.1/000000.gz ./0000002.gz
aws s3 cp s3://<my-policy-test>/<my task name>/20200508/<cloudwatch value>/<my task name>-0.2/000000.gz ./0000003.gz
aws s3 cp s3://<my-policy-test>/<my task name>/20200508/<cloudwatch value>/<my task name>-0.3/000000.gz ./0000004.gz

The downloaded files:
336960495 May 12 18:25 0000001
340586794 May 12 18:25 0000002
330253873 May 12 18:25 0000003
329645054 May 12 18:25 0000004
I tried to use pgbadger with all of them and separately with one of them.  No errors reported, but the output html file is "NO DATASET" result for all cases.
pgbadger 000000* -j 2 -p '%t:%r:%u@%d:[%p]:'  -o ./000000.html
pgbadger 0000001 -j 2 -p '%t:%r:%u@%d:[%p]:'  -o ./000001.html
pgbadger 0000001 -f rds -j 2 -p '%t:%r:%u@%d:[%p]:'  -o ./000002.html

Would really like to know what is different between my results and the  other 2 issues above that got resolved.
I understand Cloudwatch prepends each timestamp line in the log file with another leading timestamp like this, in which you fixed in the previous cases:
2021-05-08T08:49:39.000Z 2021-05-08 08:49:39 UTC:<IP_ADDRESS>(52554):me@mydb:[31043]:LOG:  duration: 17.815 ms  statement:
Interesting, I removed the prepended timestamp that cloudwatch added like how was shown in #609
perl -p -i -e 's/^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3}Z //' 0000001
Then when i run it, it generates the html file successfully with data!  So why is the current version of PGBadger not fixing it?
Also, just curious, but the downloaded logs from S3 derive from asynchronous streams for the given time frame.  So each of the 4 log files has data from the same minute for the entire 24 hour period, but each works with a different seconds value for a given minute.  It seems like PGBadger is able to handle that where the input logs are not chronologically ordered.  Is that true?

To give you some idea about the log files overlapping but not at the second level, check this out:
-rw-rw-r--. 1 centos centos 14916892 May 14 18:46 pg_20210512_000000_1.log
-rw-rw-r--. 1 centos centos 15343266 May 14 18:46 pg_20210512_000000_2.log
-rw-rw-r--. 1 centos centos 15326793 May 14 18:46 pg_20210512_000000_3.log
-rw-rw-r--. 1 centos centos 14615869 May 14 18:46 pg_20210512_000000_4.log

grep '2021-05-12 07:34:3*' pg_20210512_000000*.log
pg_20210512_000000_1.log:2021-05-12 07:34:36 UTC::@:[30368]:LOG:  automatic analyze of table "rdsadmin.public.rds_heartbeat2" system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
pg_20210512_000000_1.log:2021-05-12 07:34:38 UTC:<IP_ADDRESS>(49430):entityservices_app@conceptdb:[30241]:LOG:  duration: 5547.893 ms  execute <unnamed>: select
pg_20210512_000000_1.log:2021-05-12 07:34:38 UTC:<IP_ADDRESS>(49430):entityservices_app@conceptdb:[30241]:DETAIL:  parameters: $1 = '1979362815', $2 = '0.6'
pg_20210512_000000_1.log:2021-05-12 07:34:55 UTC:<IP_ADDRESS>(64080):[unknown]@[unknown]:[31452]:LOG:  connection received: host=<IP_ADDRESS> port=64080
pg_20210512_000000_1.log:2021-05-12 07:34:55 UTC:<IP_ADDRESS>(64080):concepttool_app@conceptdb:[31452]:LOG:  connection authorized: user=concepttool_app database=conceptdb
pg_20210512_000000_1.log:2021-05-12 07:34:55 UTC:<IP_ADDRESS>(64080):concepttool_app@conceptdb:[31452]:LOG:  disconnection: session time: 0:00:00.008 user=concepttool_app database=conceptdb host=<IP_ADDRESS> port=64080
pg_20210512_000000_1.log:2021-05-12 07:34:55 UTC:<IP_ADDRESS>(64081):[unknown]@[unknown]:[31453]:LOG:  connection received: host=<IP_ADDRESS> port=64081
pg_20210512_000000_1.log:2021-05-12 07:34:55 UTC:<IP_ADDRESS>(64081):concepttool_app@conceptdb:[31453]:LOG:  connection authorized: user=concepttool_app database=conceptdb
pg_20210512_000000_1.log:2021-05-12 07:34:55 UTC:<IP_ADDRESS>(64081):concepttool_app@conceptdb:[31453]:LOG:  disconnection: session time: 0:00:00.008 user=concepttool_app database=conceptdb host=<IP_ADDRESS> port=64081
pg_20210512_000000_1.log:2021-05-12 07:34:12 UTC:<IP_ADDRESS>(63190):[unknown]@[unknown]:[29226]:LOG:  connection received: host=<IP_ADDRESS> port=63190
pg_20210512_000000_1.log:2021-05-12 07:34:12 UTC:<IP_ADDRESS>(63190):mappingtool_app@conceptdb:[29226]:LOG:  connection authorized: user=mappingtool_app database=conceptdb
pg_20210512_000000_2.log:2021-05-12 07:34:46 UTC::@:[30708]:LOG:  automatic vacuum of table "rdsadmin.public.rds_heartbeat2": index scans: 0
pg_20210512_000000_2.log:2021-05-12 07:34:25 UTC:<IP_ADDRESS>(52457):entityservices_app@conceptdb:[18151]:LOG:  duration: 6139.617 ms  execute <unnamed>: select
pg_20210512_000000_2.log:2021-05-12 07:34:25 UTC:<IP_ADDRESS>(52457):entityservices_app@conceptdb:[18151]:DETAIL:  parameters: $1 = '4270764503', $2 = '0.6'
pg_20210512_000000_3.log:2021-05-12 07:34:41 UTC:<IP_ADDRESS>(52457):entityservices_app@conceptdb:[18151]:LOG:  disconnection: session time: 0:04:32.079 user=entityservices_app database=conceptdb host=<IP_ADDRESS> port=52457
pg_20210512_000000_3.log:2021-05-12 07:34:41 UTC:<IP_ADDRESS>(52047):entityservices_app@conceptdb:[13437]:LOG:  disconnection: session time: 0:06:13.817 user=entityservices_app database=conceptdb host=<IP_ADDRESS> port=52047
pg_20210512_000000_3.log:2021-05-12 07:34:41 UTC:<IP_ADDRESS>(58320):entityservices_app@conceptdb:[24381]:LOG:  disconnection: session time: 0:02:14.150 user=entityservices_app database=conceptdb host=<IP_ADDRESS> port=58320
pg_20210512_000000_3.log:2021-05-12 07:34:41 UTC:<IP_ADDRESS>(57717):entityservices_app@conceptdb:[18152]:LOG:  disconnection: session time: 0:04:32.425 user=entityservices_app database=conceptdb host=<IP_ADDRESS> port=57717
pg_20210512_000000_3.log:2021-05-12 07:34:58 UTC:<IP_ADDRESS>(49751):bulkedit_app@conceptdb:[26841]:LOG:  duration: 7021.685 ms  execute <unnamed>: WITH BASE_SQL AS ( SELECT * FROM (
pg_20210512_000000_3.log:2021-05-12 07:34:58 UTC:<IP_ADDRESS>(49751):bulkedit_app@conceptdb:[26841]:DETAIL:  parameters: $1 = '432703474', $2 = '{1514,1462,1858}', $3 = '7706'
pg_20210512_000000_3.log:2021-05-12 07:34:58 UTC:<IP_ADDRESS>(53638):[unknown]@[unknown]:[31532]:LOG:  connection received: host=<IP_ADDRESS> port=53638
pg_20210512_000000_3.log:2021-05-12 07:34:58 UTC:<IP_ADDRESS>(53638):entityservices_app@conceptdb:[31532]:LOG:  connection authorized: user=entityservices_app database=conceptdb
pg_20210512_000000_3.log:2021-05-12 07:34:16 UTC::@:[29335]:LOG:  automatic vacuum of table "rdsadmin.public.rds_heartbeat2": index scans: 0
pg_20210512_000000_3.log:2021-05-12 07:34:17 UTC:<IP_ADDRESS>(57717):entityservices_app@conceptdb:[18152]:LOG:  duration: 32058.996 ms  execute <unnamed>: WITH BASE_SQL AS (SELECT * FROM (
pg_20210512_000000_3.log:2021-05-12 07:34:17 UTC:<IP_ADDRESS>(57717):entityservices_app@conceptdb:[18152]:DETAIL:  parameters: $1 = '3'
pg_20210512_000000_3.log:2021-05-12 07:34:17 UTC:<IP_ADDRESS>(57717):entityservices_app@conceptdb:[18152]:LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp18152.1", size 366731264
pg_20210512_000000_4.log:2021-05-12 07:34:01 UTC:<IP_ADDRESS>(59063):[unknown]@[unknown]:[28917]:LOG:  connection received: host=<IP_ADDRESS> port=59063
pg_20210512_000000_4.log:2021-05-12 07:34:01 UTC:<IP_ADDRESS>(59063):concepttool_app@conceptdb:[28917]:LOG:  connection authorized: user=concepttool_app database=conceptdb
pg_20210512_000000_4.log:2021-05-12 07:34:01 UTC:<IP_ADDRESS>(59063):concepttool_app@conceptdb:[28917]:LOG:  disconnection: session time: 0:00:00.010 user=concepttool_app database=conceptdb host=<IP_ADDRESS> port=59063
pg_20210512_000000_4.log:2021-05-12 07:34:01 UTC:<IP_ADDRESS>(59064):[unknown]@[unknown]:[28918]:LOG:  connection received: host=<IP_ADDRESS> port=59064
pg_20210512_000000_4.log:2021-05-12 07:34:01 UTC:<IP_ADDRESS>(59064):concepttool_app@conceptdb:[28918]:LOG:  connection authorized: user=concepttool_app database=conceptdb
pg_20210512_000000_4.log:2021-05-12 07:34:01 UTC:<IP_ADDRESS>(59064):concepttool_app@conceptdb:[28918]:LOG:  disconnection: session time: 0:00:00.008 user=concepttool_app database=conceptdb host=<IP_ADDRESS> port=59064
pg_20210512_000000_4.log:2021-05-12 07:34:01 UTC::@:[28919]:LOG:  automatic analyze of table "rdsadmin.public.rds_heartbeat2" system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
pg_20210512_000000_4.log:2021-05-12 07:34:31 UTC:<IP_ADDRESS>(52442):[unknown]@[unknown]:[30196]:LOG:  connection received: host=<IP_ADDRESS> port=52442
pg_20210512_000000_4.log:2021-05-12 07:34:31 UTC:<IP_ADDRESS>(52442):concepttool_app@conceptdb:[30196]:LOG:  connection authorized: user=concepttool_app database=conceptdb
pg_20210512_000000_4.log:2021-05-12 07:34:31 UTC:<IP_ADDRESS>(52442):concepttool_app@conceptdb:[30196]:LOG:  disconnection: session time: 0:00:00.005 user=concepttool_app database=conceptdb host=<IP_ADDRESS> port=52442
pg_20210512_000000_4.log:2021-05-12 07:34:31 UTC:<IP_ADDRESS>(52443):[unknown]@[unknown]:[30197]:LOG:  connection received: host=<IP_ADDRESS> port=52443
pg_20210512_000000_4.log:2021-05-12 07:34:31 UTC:<IP_ADDRESS>(52443):concepttool_app@conceptdb:[30197]:LOG:  connection authorized: user=concepttool_app database=conceptdb
pg_20210512_000000_4.log:2021-05-12 07:34:31 UTC:<IP_ADDRESS>(52443):concepttool_app@conceptdb:[30197]:LOG:  disconnection: session time: 0:00:00.005 user=concepttool_app database=conceptdb host=<IP_ADDRESS> port=52443
pg_20210512_000000_4.log:2021-05-12 07:34:32 UTC:<IP_ADDRESS>(49430):[unknown]@[unknown]:[30241]:LOG:  connection received: host=<IP_ADDRESS> port=49430
pg_20210512_000000_4.log:2021-05-12 07:34:32 UTC:<IP_ADDRESS>(49430):entityservices_app@conceptdb:[30241]:LOG:  connection authorized: user=entityservices_app database=conceptdb
pg_20210512_000000_4.log:2021-05-12 07:34:51 UTC:<IP_ADDRESS>(49451):mappingreview_app@conceptdb:[27061]:LOG:  disconnection: session time: 0:25:00.815 user=mappingreview_app database=conceptdb host=<IP_ADDRESS> port=49451

Again to be clear,  CloudWatch creates these s3 logs in an unusual way, with timestamps within each file not in sequential order:
grep '2021-05-12 07:34:' pg_20210512_000000_2.log
-->
2021-05-12 07:34:46 UTC::@:[30708]:LOG:  automatic vacuum of table "rdsadmin.public.rds_heartbeat2": index scans: 0
2021-05-12 07:34:25 UTC:<IP_ADDRESS>(52457):entityservices_app@conceptdb:[18151]:LOG:  duration: 6139.617 ms  execute <unnamed>: select
2021-05-12 07:34:25 UTC:<IP_ADDRESS>(52457):entityservices_app@conceptdb:[18151]:DETAIL:  parameters: $1 = '4270764503', $2 = '0.6'

Furthermore, the time is overlapping in each log file for the same minute, but not for the same second:
pg_20210512_000000_1.log:2021-05-12 07:34:36 UTC::@:[30368]:LOG:  automatic analyze of table "rdsadmin.public.rds_heartbeat2" system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
pg_20210512_000000_1.log:2021-05-12 07:34:12 UTC:<IP_ADDRESS>(63190):[unknown]@[unknown]:[29226]:LOG:  connection received: host=<IP_ADDRESS> port=63190

pg_20210512_000000_2.log:2021-05-12 07:34:46 UTC::@:[30708]:LOG:  automatic vacuum of table "rdsadmin.public.rds_heartbeat2": index scans: 0
pg_20210512_000000_2.log:2021-05-12 07:34:25 UTC:<IP_ADDRESS>(52457):services_app@mydb:[18151]:LOG:  duration: 6139.617 ms  execute <unnamed>: select

pg_20210512_000000_3.log:2021-05-12 07:34:41 UTC:<IP_ADDRESS>(52457):services_app@mydb:[18151]:LOG:  disconnection: session time: 0:04:32.079 user=services_app database=mydb host=<IP_ADDRESS> port=52457
pg_20210512_000000_3.log:2021-05-12 07:34:58 UTC:<IP_ADDRESS>(49751):bulke_app@mydb:[26841]:LOG:  duration: 7021.685 ms  execute <unnamed>: WITH BASE_SQL AS ( SELECT * FROM (
pg_20210512_000000_3.log:2021-05-12 07:34:16 UTC::@:[29335]:LOG:  automatic vacuum of table "rdsadmin.public.rds_heartbeat2": index scans: 0

pg_20210512_000000_4.log:2021-05-12 07:34:01 UTC:<IP_ADDRESS>(59063):[unknown]@[unknown]:[28917]:LOG:  connection received: host=<IP_ADDRESS> port=59063
pg_20210512_000000_4.log:2021-05-12 07:34:31 UTC:<IP_ADDRESS>(52442):[unknown]@[unknown]:[30196]:LOG:  connection received: host=<IP_ADDRESS> port=52442
pg_20210512_000000_4.log:2021-05-12 07:34:51 UTC:<IP_ADDRESS>(49451):myreviewtool_app@mydb:[27061]:LOG:  disconnection: session time: 0:25:00.815 user=review_app database=mydb host=<IP_ADDRESS> port=49451

Putting these in time order you got this order of log files:
pg_20210512_000000_4.log:2021-05-12 07:34:01 UTC:<IP_ADDRESS>(59063):[unknown]@[unknown]:[28917]:LOG:  connection received: host=<IP_ADDRESS> port=59063
pg_20210512_000000_1.log:2021-05-12 07:34:12 UTC:<IP_ADDRESS>(63190):[unknown]@[unknown]:[29226]:LOG:  connection received: host=<IP_ADDRESS> port=63190
pg_20210512_000000_3.log:2021-05-12 07:34:16 UTC::@:[29335]:LOG:  automatic vacuum of table "rdsadmin.public.rds_heartbeat2": index scans: 0
pg_20210512_000000_2.log:2021-05-12 07:34:25 UTC:<IP_ADDRESS>(52457):services_app@mydb:[18151]:LOG:  duration: 6139.617 ms  execute <unnamed>: select
pg_20210512_000000_4.log:2021-05-12 07:34:31 UTC:<IP_ADDRESS>(52442):[unknown]@[unknown]:[30196]:LOG:  connection received: host=<IP_ADDRESS> port=52442
pg_20210512_000000_1.log:2021-05-12 07:34:36 UTC::@:[30368]:LOG:  automatic analyze of table "rdsadmin.public.rds_heartbeat2" system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
pg_20210512_000000_3.log:2021-05-12 07:34:41 UTC:<IP_ADDRESS>(52457):services_app@mydb:[18151]:LOG:  disconnection: session time: 0:04:32.079 user=services_app database=mydb host=<IP_ADDRESS> port=52457
pg_20210512_000000_2.log:2021-05-12 07:34:46 UTC::@:[30708]:LOG:  automatic vacuum of table "rdsadmin.public.rds_heartbeat2": index scans: 0
pg_20210512_000000_4.log:2021-05-12 07:34:51 UTC:<IP_ADDRESS>(49451):myreviewtool_app@mydb:[27061]:LOG:  disconnection: session time: 0:25:00.815 user=review_app database=mydb host=<IP_ADDRESS> port=49451
pg_20210512_000000_3.log:2021-05-12 07:34:58 UTC:<IP_ADDRESS>(49751):bulke_app@mydb:[26841]:LOG:  duration: 7021.685 ms  execute <unnamed>: WITH BASE_SQL AS ( SELECT * FROM (

It seems like PGBadger is able to handle that where the input logs are not chronologically ordered. Is that true?

I have a counter-example here: Suppose you have a multiple-line log entry (for example this one here). If the log lines are out-of-order (which we know they can't be for CloudWatch) but with the same timestamp, then pgBadger can't know the exact order in which those lines arrived because there is no sequence number (at least in the log lines you show), so the initial claim doesn't seem to hold.
There's one exception like for example let's say the multiline log entry is just 3-4 lines, to recover the original order, run all the permutations through a query parser, see which one turns out to be valid and pick that, but not unambiguously.

I am closing this issue since it cannot be resolved.  I have created another issue as an informational one that perhaps you can get into pgbadger docs so folks don't spend endless hours trying to use PGBadger with AWS.
See issue, https://github.com/darold/pgbadger/issues/657

If I take your log and you command perl pgbadger -p '%t:%r:%u@%d:[%p]:' logfile.log I have no problem with the log line you have pasted. And yes pgbadger don't care about the log timestamp order provide that they are all given as parameter of a sing pgbadger command. I don't understand the problem here, it should works. If you want you can send the log file to my private email I will try to reproduce your issue.


Add zfs to bluefin image

Describe the package
Hello, thanks for the great work on this project, I'm excited to try it out. I forked the template repo and see this in containerfile
# SOURCE_IMAGE arg can be anything from ublue upstream which matches your desired version:
# See list here: https://github.com/orgs/ublue-os/packages?repo_name=main
# - "silverblue"
# - "kinoite"
# - "sericea"
# - "onyx"
# - "lazurite"
# - "vauxite"
# - "base"
#
#  "aurora", "bazzite", "bluefin" or "ucore" may also be used but have different suffixes.
ARG SOURCE_IMAGE="bluefin"

## SOURCE_SUFFIX arg should include a hyphen and the appropriate suffix name
# These examples all work for silverblue/kinoite/sericea/onyx/lazurite/vauxite/base
# - "-main"
# - "-nvidia"
# - "-asus"
# - "-asus-nvidia"
# - "-surface"
# - "-surface-nvidia"
#
# aurora, bazzite and bluefin each have unique suffixes. Please check the specific image.
# ucore has the following possible suffixes
# - stable
# - stable-nvidia
# - stable-zfs
# - stable-nvidia-zfs
# - (and the above with testing rather than stable)
ARG SOURCE_SUFFIX="-dx-nvidia"

But when I try to pull bluefin-stable-nvidia-zfs I get 403/4, which I think probably just amounts to this tag not being available. I see zfs in the ucore repo and I'm brand new so I'm not sure how all the image flow in and out of each other, but I'm a developer and would love to have zfs available in the base images that magically take care of nvidia and container setup too :D
I'll probably try to get it installed myself in the build script but for the time being wanted to request/ask if zfs in bluefin is a possibility?
Image
Ubuntu

This won't work today, the zfs stuff for ucore doesn't work in bluefin.
This is something I'd love to do long term but it would depend on us using the coreos kernel, which is on the roadmap.

amazingly fast response!
so in the time being can I ask for a recommendation? I'm a dev and I do a lot of stable diffusion + python stuff at home so I definitely want the Nvidia stuff and dev stuff all baked into an immutable image... question is, would it be feasible for me to build off the ucore image to get zfs and then setup the containerfile to install all the dev tools?
otherwise I might look for another storage solution since this project feels so promising!

Ucore is an excellent storage solution option.
If what you are looking for is a GUI, ucore comes with a web application called cockpit to manage your server.
Note, ucore doesn't support root on zfs at this time so your zpool needs to be at the bare minimum a different partition or more likely separate disks.

Work has started on shipping the coreOS Kernel.

CoreOS kernel is now being shipped.
GTS and Stable will have zfs included. We will build and include it; however, the coreOS kernel is a leading edge kernel and there may be the possibility that a kernel release occurs before a zfs release is made.
Follow this PR #1456

GTS and Stable will have zfs included

Will there be separate "-zfs" tags, or stable tag will eventually include it?

https://universal-blue.discourse.group/t/bluefin-and-aurora-3-0/2650
This is shipping now, ymmv, etc.


Issue Template

Too many people don't know how to properly check checkboxes. I was thinking if we can make the template more self-explanatory so people can have an easier time creating issues (and we might have less dumb issues).
Mainly I want to add a example check so people can follow, and some more explanatory text saying which section can be deleted and which ones should stay.

I just saw this: Creating issue forms.
This would be so awesome once it gets out of Beta.

I would personally just use Github Forms, even if it's in beta

Whoa that seem nice! I'll take a look tomorrow and see if I can come up with something. Thanks!

See #823 for a Github forms solution


Windriver, CNFGHandleInput, PeekMessage should use HWND 0.

I consistently see four HWND where messages get sent to. The current windriver in CNFGHandleInput() only checks CNFGlsHWND, but this misses most events. Especially keyboard events.
I added some output to CNFGHandleInput() of processed and ignored events. So ignored events here are ignored because the HWND isn't CNFGlsHWND.
PROC    HWND    260710  other
PROC    HWND    260710  other
PROC    HWND    260710  other
IGN     HWND    3a062e  other
IGN     HWND    3a062e  other
IGN     HWND    3a062e  other
IGN     HWND    0       other
IGN     HWND    3a062e  other
IGN     HWND    0       other
IGN     HWND    0       other
IGN     HWND    260710  key
IGN     HWND    3a062e  other
IGN     HWND    1d061a  other
PROC    HWND    260710  mouse
PROC    HWND    260710  other
IGN     HWND    260710  other
IGN     HWND    3a062e  other
IGN     HWND    260710  key
IGN     HWND    260710  other
IGN     HWND    3a062e  other
PROC    HWND    260710  key
IGN     HWND    3a062e  other
IGN     HWND    3a062e  other
IGN     HWND    260710  key
IGN     HWND    260710  other
IGN     HWND    3a062e  other
PROC    HWND    260710  key
IGN     HWND    3a062e  other
IGN     HWND    3a062e  other
IGN     HWND    260710  key
IGN     HWND    260710  other
IGN     HWND    3a062e  other
PROC    HWND    260710  key
IGN     HWND    3a062e  other
IGN     HWND    3a062e  other
IGN     HWND    3a062e  other
IGN     HWND    0       other
IGN     HWND    1d061a  other

I added a commit to my previous pull request that sets the second argument of PeekMessage to NULL, which fixes this.

This was merged into that request.


NVIDIA Driver Failure on GPU Nodes: Driver/Library Version Mismatch Error

Title: NVIDIA Driver Failure on GPU Nodes: Driver/Library Version Mismatch Error
Description:
On the GPU nodes, the NVIDIA driver intermittently fails, causing the following error:
ubuntu@node:~$ nvidia-smi
Failed to initialize NVML: Driver/library version mismatch
NVML library version: 535.216

We have currently instaled the following nvidia driver
NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.183.06  Wed Jun 26 06:46:07 UTC 2024
GCC version:  gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)

From Nomads point of view, running a GPU job on a faulty node throws the following error:
Failed to start container <container ID>: API error (500): failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #1: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: initialization error: nvml error: driver/library version mismatch: unknown

Current Workaround:
The only solution identified so far is to restart the node, which temporarily resolves the issue. However, this is not a viable long-term solution, as it disrupts active Docker containers for users, causing data loss and downtime.
Observations:
This issue generally occurs simultaneously across all nodes at a specific site, suggesting that a common event may be triggering it. Additionally, we do not know how the nodes will behave after updating the NVIDIA driver version, as we have no clear way to reproduce this error.

May be the nodes are upgraded and installs a new version of the drivers.
We can try to set "hold" to avoid updating the drivers.

It can be made manually or https://github.com/ai4os/ai4-ansible/pull/48


STAGING - Verification SMS for phone number was not received.

Added phone number and also tried a resend 2 minutes later.
No SMS was ever received, using a +32 belgian nr

Was a problem with our SMS service provider. Seems to be fixed now.

Edited some of the texting logic, should be fine now. Fixed on staging and production.


Error in installation

After installation, I ran the command "pyeth" and got the following error. Please suggest.
/usr/lib/python2.7/dist-packages/pkg_resources.py:1031: UserWarning: /home/vibhor/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
warnings.warn(msg, UserWarning)
INFO:app	starting	version='0.8.52_113_ga6f6299-py2.7.egg'
INFO:eth.chainmgr	opening chain	db_path='/home/vibhor/.pyethereum/statedb'
Traceback (most recent call last):
File "/usr/local/bin/pyeth", line 9, in
load_entry_point('pyethereum==0.8.52-113-ga6f6299', 'console_scripts', 'pyeth')()
File "/usr/local/lib/python2.7/dist-packages/pyethereum-0.8.52_113_ga6f6299-py2.7.egg/pyethereum/eth.py", line 145, in main
config_ready.send(sender=None, config=config)
File "/usr/local/lib/python2.7/dist-packages/pyethereum-0.8.52_113_ga6f6299-py2.7.egg/pyethereum/dispatch/dispatcher.py", line 197, in send
response = receiver(signal=self, sender=sender, **named)
File "/usr/local/lib/python2.7/dist-packages/pyethereum-0.8.52_113_ga6f6299-py2.7.egg/pyethereum/chainmanager.py", line 222, in config_chainmanager
chain_manager.configure(config)
File "/usr/local/lib/python2.7/dist-packages/pyethereum-0.8.52_113_ga6f6299-py2.7.egg/pyethereum/chainmanager.py", line 49, in configure
self.chain = Chain(db, genesis, new_head_cb=self._on_new_head)
File "/usr/local/lib/python2.7/dist-packages/pyethereum-0.8.52_113_ga6f6299-py2.7.egg/pyethereum/chain.py", line 100, in init
log.debug('chain @', head_hash=self.head)
File "/usr/local/lib/python2.7/dist-packages/pyethereum-0.8.52_113_ga6f6299-py2.7.egg/pyethereum/chain.py", line 120, in head
return blocks.get_block(self.blockchain, ptr)
File "/usr/local/lib/python2.7/dist-packages/repoze.lru-0.6-py2.7.egg/repoze/lru/init.py", line 287, in lru_cached
val = f(*arg)
File "/usr/local/lib/python2.7/dist-packages/pyethereum-0.8.52_113_ga6f6299-py2.7.egg/pyethereum/blocks.py", line 1300, in get_block
blk = rlp.decode(db.get(blockhash), Block, db=db)
File "/usr/local/lib/python2.7/dist-packages/rlp-0.3.3-py2.7.egg/rlp/codec.py", line 164, in decode
return sedes.deserialize(item, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/rlp-0.3.3-py2.7.egg/rlp/sedes/lists.py", line 145, in deserialize
values = cls.get_sedes().deserialize(serial)
File "/usr/local/lib/python2.7/dist-packages/rlp-0.3.3-py2.7.egg/rlp/sedes/lists.py", line 54, in deserialize
for element, sedes in izip(serial, self)]
File "/usr/local/lib/python2.7/dist-packages/rlp-0.3.3-py2.7.egg/rlp/sedes/lists.py", line 145, in deserialize
values = cls.get_sedes().deserialize(serial)
File "/usr/local/lib/python2.7/dist-packages/rlp-0.3.3-py2.7.egg/rlp/sedes/lists.py", line 52, in deserialize
raise DeserializationError('List has wrong length', serial)
rlp.exceptions.DeserializationError: List has wrong length

@vibhor1403 is this still an issue?


Can injection use in Xcode 9 to develop iOS11?

Can injection use in Xcode 9 to develop iOS11?
Thx

There is a  separate version for Xcode 9 http://johnholdsworth.com/injection.html

Works like a charm for me.

Greatttt!


Add a guide for ALB-based Kubernetes Ingresses

What happened?
The article here: https://www.pulumi.com/blog/kubernetes-ingress-with-aws-alb-ingress-controller-and-pulumi-crosswalk/
Is no longer current, and the chart URL used no longer exists. Would be nice with an updated guide, as this particular topic is very hard to get working.
Expected Behavior
I expected a notice in the top of the blog post to link to a more updated article.
Steps to reproduce
N/A
Output of pulumi about
N/A
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Renamed the issue to cover adding the requested guide. As part of this, we should point the blog post to this new guide when it's available.


Update pixiu readme

What this PR does:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Codecov Report

Merging #477 (61f368a) into dev-istio-1.14 (7a4a38d) will increase coverage by 0.01%.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           dev-istio-1.14     #477      +/-   ##
==================================================
+ Coverage           54.93%   54.94%   +0.01%
==================================================
  Files                 662      662
  Lines               77404    77404
==================================================
+ Hits                42519    42528       +9
+ Misses              31258    31250       -8
+ Partials             3627     3626       -1

Impacted Files
Coverage Δ

pilot/pkg/config/memory/monitor.go
71.79% <0.00%> (-7.70%)
:arrow_down:

pilot/pkg/model/addressmap.go
63.23% <0.00%> (-4.42%)
:arrow_down:

pkg/istio-agent/xds_proxy_delta.go
49.22% <0.00%> (-4.15%)
:arrow_down:

security/pkg/nodeagent/sds/sdsservice.go
84.76% <0.00%> (-2.65%)
:arrow_down:

pkg/test/framework/resource/version.go
18.42% <0.00%> (-1.76%)
:arrow_down:

pkg/wasm/cache.go
88.48% <0.00%> (-1.05%)
:arrow_down:

pilot/pkg/bootstrap/server.go
53.11% <0.00%> (-0.46%)
:arrow_down:

.../pkg/serviceregistry/kube/controller/controller.go
72.53% <0.00%> (+0.60%)
:arrow_up:

pilot/pkg/model/jwks_resolver.go
79.06% <0.00%> (+0.77%)
:arrow_up:

pilot/pkg/xds/discovery.go
85.89% <0.00%> (+0.96%)
:arrow_up:

... and 7 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


branch key

custom GUI for the private key.

I am so sorry.  This issue was meant for my personal repo.


Unable to load target module react-navigation/native

I have a problem with my app that it doesn't start anymore after adding the react-navigation packages. In order to fix my issue I decided to try it out on a new app and followed the documentation of the getting started page And after doing that and starting the app I still get the same issue.

Hey @stefan0905,
make sure to install @react-navigation/native like mentioned on the docs https://reactnavigation.org/docs/getting-started/#installation


Update to TypeScript 4.x

The project uses TypeScript version 2.5.3 while the current latest version is 3.6.3 (with 3.7 beta just becoming available).
While there's a number of updates to the language that may be beneficial there's also updates to the core definitions. One definition update in particular would be useful to address the definition patching required for #1070.

Because of the length of time this has been taking, I'm changing this to jump to TypeScript v4.x -- hopefully we can complete this before TS 5 comes out 😅

Any help you need @MSNev?

I don't think so, it's mostly a matter of timing and juggling with internal teams, tasks and compatibility issues. As there has been issues with the generated code (previously) especially the *.d.ts, I've since tasks for the apigenerator to mitigate this aspect and make it easier to identify and validate any possible breaks.

v2.7.0 is not fully deployed to NPM and all CDN endpoints -- 🎆 🥳 🍾


Could not fire next() in the cached view when route changes

Version
3.0.1
Reproduction link
https://github.com/icesman/bug-demo
Steps to reproduce

have two components A and B, a list, and two routes of them, such as 'pathA' for A and 'pathB' for B;
and then have a component such as C, when click item in A or B then jump to C, use the same component but with different routes, such as 'pathCForA' and 'pathCForB'
component C is cached used by the directive of 'include' via name
when click different items in A , items would be updated when redirect to 'pathCForA' , but when back from 'pathCforA' to 'pathA', and then to 'pathB', click the item in C. Now the route is 'pathCForB', but the next function wouldn't trigger.

What is expected?
the next function of the beforeRouteEnter is fired
What is actually happening?
the next function of the beforeRouteEnter is not fired

Wehen components can be re-used between routes, beforeRouteEnter will not
be called - that's documented behaviour.
You should use beforeRouteUpdate instead.
Alternatively, you could turn C Into its own component with its own name by simply extending he base component
Import CosmpA from '. /CompA'

export default {
  name: 'CompC',
  extends: CompA

}

@LinusBorg actually the 'beforeRouteEnter' is called but the 'next()' is not fired, which doesn't make the data updated.
I resolved it but I am curious about why the next is no fired


SQLAlchemy: Add Python-based test module for integration tests

At https://github.com/crate/crate-python/pull/464#discussion_r1044549726, we observed that

We currently have no place where Python-based SQLAlchemy integration tests are conducted. Currently, there are only Python-based unit tests exercising the CrateDB dialect using corresponding mocks to work around needing a real database. On the other hand, there are integration test cases with SQLAlchemy and CrateDB, but they are only written as doctests.

In order to conduct special test scenarios which don't fit having them written as a doctest, and for improved capabilities to run specific test cases selectively, it may make sense to add a module which fills the gap on running Python-based SQLAlchemy integration test cases against a real database.

Integration tests can be written in Python now. Example:
https://github.com/crate/sqlalchemy-cratedb/blob/da977d9a294714feb2ee66144088dce922352604/tests/vector_test.py#L218-L249


ENH/FIX: GAT cv scores

FIX: Addresses issue raised by @dengemann  in https://github.com/mne-tools/mne-python/issues/3125, related to the fact that the current behavior of the decoding algorithm is to apply the score outside the cross-validation, which is not the conventional sklearn way
changes default scoring mode
ENH: allows retrieving fold-specific scores

Some empirical tests here. tl;dr: At the exception of f1_score (for which I need to think a bit more, I actually never use this metrics), the scoring metrics, if anything, is overestimated when applied per fold (as compared to across trials) when there is information (there isn't a systematic bias when X can't predict y). Additional simulations could be done to test different X distributions.

You have a docstring problem:
https://travis-ci.org/mne-tools/mne-python/jobs/124450410#L2697

@fraimondo do you have time to look?

I'll take a look tomorrow. Did not see this today.
Le 20 avr. 2016 10:54 PM, "Alexandre Gramfort"<EMAIL_ADDRESS>a
écrit :

@fraimondo https://github.com/fraimondo do you have time to look?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/pull/3143#issuecomment-212602465

It would be good to get this into 0.12 as a fix, @kingjr do you have time to work on it once @fraimondo takes a look?

Changes Unknown when pulling 9528fc7931bca101c9608b48cfcbed053d95f539 on kingjr:gat_cv_scores into ** on mne-tools:master**.

@fraimondo ready on my side

Otherwise LGTM.
@dengemann do you have time to look too?

@jona-sassenhagen @cmoutard @teonlamont do you have any comment ? it s quite a substantial change. Since we'll release soon , I'd be more confident if several people checked that nothing looks weird.
( The new default approach will be n_fold slower.)

( The new default approach will be n_fold slower.)

Only aggregation of the scores will be slower right? And the part that's actually slow is creating the scores, not aggregating them?
It looks fine to me.

@jona-sassenhagen running the score across each fold is slower than running the score once across all y_pred. It slightly less than n_fold slower, because there is less data per fold.

Changes Unknown when pulling bdda7804a82baad09f9e402bcca5b50d2fd581ae on kingjr:gat_cv_scores into ** on mne-tools:master**.

Changes Unknown when pulling ef9253cba37bfaca2ad19ebed847b1182471070c on kingjr:gat_cv_scores into ** on mne-tools:master**.

@Eric89GXL is this what we want? I'm not sure. I'm about to take take off, feel free to take over to fix the doc.

@jona-sassenhagen running the score across each fold is slower than running the score once across all y_pred. It slightly less than n_fold slower, because there is less data per fold.

Sorry, I have to ask again. You're saying gat.score() will actually be ~n_fold slower?

@jona-sassenhagen gat.predict() is unchanged but yes, by default gat.score() will be slower. If you want the fast but non-conventional approach, you'll need to set score_mode='no-cv', for which we only score once across all y_pred, as opposed to averaging n_fold scores.
In other we used to do:
for train, test in cv:
    y_pred[test] = clf.predict(X[test])
return scorer(y_pred, y_true)

By default, we now do (as in sklearn):
for train, test in cv:
    y_pred = clf.predict(X[test])
    scores.append(scorer(y_pred, y_true[test]))
return np.mean(scores)

Ah okay, I get the misunderstanding. I had implicitly referred to the case where you don't explicitly predict, but just call gat.score() and let it do the predictions (which would not be n_folds slower), sorry for the confusion.

(My point was, if you don't explicitly call gat.predict, most of the work of gat.score will be predicting, which will be unaffected by the changes. But it's clear that if you have predictions, gat.score will in fact be slower by some_factor * n_folds.)

@kingjr yeah the docs looks good now

@fraimondo ping :]

I can take a look + run some tests tomorrow.
On Tue, Apr 26, 2016 at 1:12 PM Jean-Rémi KING<EMAIL_ADDRESS>wrote:

@fraimondo https://github.com/fraimondo ping :]
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/pull/3143#issuecomment-214705374

No internet here. Can’t really test it right now. I can only reply emails and takes a long time to send.
I’ll be back to the civilisation this friday.

On 26 Apr 2016, at 13:13, Denis A. Engemann<EMAIL_ADDRESS>wrote:
I can take a look + run some tests tomorrow.
On Tue, Apr 26, 2016 at 1:12 PM Jean-Rémi KING<EMAIL_ADDRESS>wrote:

@fraimondo https://github.com/fraimondo ping :]
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/pull/3143#issuecomment-214705374

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/mne-tools/mne-python/pull/3143#issuecomment-214705555

Thanks for the update @fraimondo. Sounds like @dengemann has you covered :)

Ok will take over then, don't worry Fede, JR.
On Tue, Apr 26, 2016 at 9:30 PM Federico Raimondo<EMAIL_ADDRESS>wrote:

No internet here. Can’t really test it right now. I can only reply emails
and takes a long time to send.
I’ll be back to the civilisation this friday.

On 26 Apr 2016, at 13:13, Denis A. Engemann<EMAIL_ADDRESS>wrote:
I can take a look + run some tests tomorrow.
On Tue, Apr 26, 2016 at 1:12 PM Jean-Rémi KING<EMAIL_ADDRESS>wrote:

@fraimondo https://github.com/fraimondo ping :]
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
<
https://github.com/mne-tools/mne-python/pull/3143#issuecomment-214705374>

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub <
https://github.com/mne-tools/mne-python/pull/3143#issuecomment-214705555>

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/pull/3143#issuecomment-214859995

rebased. Not sure what's going on with appveyor.

Coverage decreased (-8.9%) to 81.959% when pulling 2c0fa419e56dd3ab6a5fe679b573acda56d21bf0 on kingjr:gat_cv_scores into 5346d694acc187c5407cd2356db31eba9721f1f7 on mne-tools:master.

Coverage decreased (-0.02%) to 90.803% when pulling efca4fae9ae2a0f48e8a188267d48a0a7cb9346a on kingjr:gat_cv_scores into 5346d694acc187c5407cd2356db31eba9721f1f7 on mne-tools:master.

Ok on my side

merge with you have 2 +1
I'll skip

merge with you have 2 +1. I'll skip

I didn't get that, can you explain ?

Merge when two people give +1 for merge, he's not going to review (I think)

ITT: Alexegesis.

My comments are mostly aesthetic, +1 for merge once they're taken care of

Coverage decreased (-0.1%) to 90.696% when pulling c4c34061b193ce9badd40226e666ea7c1cfc5d06 on kingjr:gat_cv_scores into 5346d694acc187c5407cd2356db31eba9721f1f7 on mne-tools:master.

Coverage decreased (-8.9%) to 81.947% when pulling 57de54461a1523d2e7fedbe276fba878f3cf7850 on kingjr:gat_cv_scores into 5346d694acc187c5407cd2356db31eba9721f1f7 on mne-tools:master.

Coverage decreased (-0.1%) to 90.696% when pulling 2e0e36b8d0f876ef7523863d9aded18f205a09ff on kingjr:gat_cv_scores into 5346d694acc187c5407cd2356db31eba9721f1f7 on mne-tools:master.

@dengemann feel free to try it out and merge if you're happy

Ok I'm on it now.

Coverage decreased (-0.006%) to 90.818% when pulling ea21fca869ac64f54f4e2fe93ed0938bd7a65dcd on kingjr:gat_cv_scores into 5346d694acc187c5407cd2356db31eba9721f1f7 on mne-tools:master.

Thank you @kingjr!


Getting the ERROR #85923  GRAPHQL.. lots of google, can't fix!

Hi @EmaSuriano and community. I've been using this for 1.5 years (THANK YOU!) and added a little unique code to add my resume in. I'm nervous I can't deploy anymore (I want to push a new update). My package.json code is different, I assume older, I assume my plugins may be outdated and there's a new way to do it. I know Ema pushed new code but I don't know how to incorporate his fixes into mine (I'm a bit timid as a dev of a few years!).
Here's my github repo: My Repo
Here's my package.json
{
  "name": "gatsby-starter-mate",
  "version": "2.5.1",
  "description": "Gatsby v2 starter to create a top notch portfolio!",
  "main": "index.js",
  "scripts": {
    "build": "gatsby clean && gatsby build",
    "develop": "gatsby clean && gatsby develop",
    "start": "npm run develop",
    "serve": "npm run build && gatsby serve -p 9000",
    "lint": "eslint ./src",
    "setup": "node ./bin/setup.js",
    "e2e:open": "cypress open",
    "e2e:ci": "DETERMINISTIC=true start-server-and-test serve http://localhost:9000 'percy exec -- cypress run'"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/EmaSuriano/gatsby-starter-mate.git"
  },
  "keywords": [
    "gatsby",
    "starter",
    "contentful",
    "PWA",
    "portfolio"
  ],
  "author": "Ema Suriano",
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/EmaSuriano/gatsby-starter-mate/issues"
  },
  "homepage": "https://github.com/EmaSuriano/gatsby-starter-mate#readme",
  "dependencies": {
<EMAIL_ADDRESS>"^2.2.3",
    "chalk": "^2.4.1",
    "contentful": "^7.0.3",
    "contentful-import": "^7.4.0",
    "dotenv": "^7.0.0",
    "envfile": "^3.0.0",
    "gatsby": "^2.3.27",
    "gatsby-plugin-google-analytics": "^2.0.18",
    "gatsby-plugin-manifest": "^2.0.29",
    "gatsby-plugin-offline": "^2.0.25",
    "gatsby-plugin-preload-link-crossorigin": "^1.0.2",
    "gatsby-plugin-react-helmet": "^3.0.12",
    "gatsby-plugin-styled-components": "^3.0.7",
    "gatsby-plugin-web-font-loader": "^1.0.4",
    "gatsby-source-contentful": "^2.0.52",
    "gatsby-source-medium": "file:gatsby-source-medium-2.1.6-patch.tgz",
    "gatsby-transformer-remark": "^2.3.10",
    "inquirer": "^6.2.0",
    "prop-types": "^15.6.2",
    "react": "^16.7.0",
    "react-dom": "^16.7.0",
    "react-fontawesome": "^1.6.1",
    "react-headroom": "^2.2.4",
    "react-helmet": "^5.2.0",
    "react-markdown": "^4.0.3",
    "react-reveal": "^1.2.2",
    "react-scroll-section": "^1.3.0",
    "react-text-loop": "^2.0.1",
    "rebass": "^3.0.0",
    "styled-components": "^4.0.2"
  },
  "devDependencies": {
    "@percy/cypress": "^2.1.1",
    "@testing-library/cypress": "^5.0.0",
    "axe-core": "^3.3.2",
    "cypress": "^3.4.1",
    "cypress-axe": "^0.5.1",
    "eslint": "^5.6.0",
    "eslint-config-airbnb": "^17.1.0",
    "eslint-config-prettier": "^4.1.0",
    "eslint-plugin-cypress": "^2.6.1",
    "eslint-plugin-import": "^2.17.2",
    "eslint-plugin-jsx-a11y": "^6.1.1",
    "eslint-plugin-react": "^7.12.3",
    "husky": "^1.3.1",
    "lint-staged": "^8.1.0",
    "prettier": "^1.18.2",
    "start-server-and-test": "^1.10.0"
  },
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "lint-staged": {
    "*.{js,json,css,md}": [
      "prettier --write",
      "git add"
    ]
  }
}

I've been running the npm run start command and I get the error.
I've tried going through all the different fixes that are posted in other issues, and I'm posting here as a last resort. I'm sorry I can't get it on my own. Hoping the community can help! I don't know where to start.
Here's the error that is not letting me compile:
`ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "contentfulAbout" on type "Query".
If you don't expect "contentfulAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "contentfulAbout" to exist there are a couple of solutions to common
problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js,
please try a restart of your development server
The field might be accessible in another subfield, please try your query in GraphiQL and use the
GraphiQL explorer to see which fields you can query and what shape they have
You want to optionally use your field "contentfulAbout" and right now it is not used anywhere.
Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at
least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This
way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can
define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src/components/Helmet.js:11:9
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "contentfulAbout" on type "Query".
If you don't expect "contentfulAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "contentfulAbout" to exist there are a couple of solutions to common
problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js,
please try a restart of your development server
The field might be accessible in another subfield, please try your query in GraphiQL and use the
GraphiQL explorer to see which fields you can query and what shape they have
You want to optionally use your field "contentfulAbout" and right now it is not used anywhere.
Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at
least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This
way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can
define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src/components/Footer.js:31:9
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "contentfulAbout" on type "Query".
If you don't expect "contentfulAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "contentfulAbout" to exist there are a couple of solutions to common
problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js,
please try a restart of your development server
The field might be accessible in another subfield, please try your query in GraphiQL and use the
GraphiQL explorer to see which fields you can query and what shape they have
You want to optionally use your field "contentfulAbout" and right now it is not used anywhere.
Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at
least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This
way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can
define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src/sections/About.js:50:11
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "contentfulAbout" on type "Query".
If you don't expect "contentfulAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "contentfulAbout" to exist there are a couple of solutions to common
problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js,
please try a restart of your development server
The field might be accessible in another subfield, please try your query in GraphiQL and use the
GraphiQL explorer to see which fields you can query and what shape they have
You want to optionally use your field "contentfulAbout" and right now it is not used anywhere.
Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at
least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This
way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can
define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src/sections/Landing.js:49:11
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "deterministicBehaviour" on type "SiteSiteMetadata".
If you don't expect "deterministicBehaviour" to exist on the type "SiteSiteMetadata" it is most
likely a typo.
However, if you expect "deterministicBehaviour" to exist there are a couple of solutions to common
problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js,
please try a restart of your development server
The field might be accessible in another subfield, please try your query in GraphiQL and use the
GraphiQL explorer to see which fields you can query and what shape they have
You want to optionally use your field "deterministicBehaviour" and right now it is not used
anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is
to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This
way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can
define the schema for "SiteSiteMetadata":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src/sections/Landing.js:61:15
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "contentfulAbout" on type "Query".
If you don't expect "contentfulAbout" to exist on the type "Query" it is most likely a typo.
However, if you expect "contentfulAbout" to exist there are a couple of solutions to common
problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js,
please try a restart of your development server
The field might be accessible in another subfield, please try your query in GraphiQL and use the
GraphiQL explorer to see which fields you can query and what shape they have
You want to optionally use your field "contentfulAbout" and right now it is not used anywhere.
Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at
least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This
way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can
define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src/sections/Projects.js:184:11
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "isMediumUserDefined" on type "SiteSiteMetadata".
If you don't expect "isMediumUserDefined" to exist on the type "SiteSiteMetadata" it is most
likely a typo.
However, if you expect "isMediumUserDefined" to exist there are a couple of solutions to common
problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js,
please try a restart of your development server
The field might be accessible in another subfield, please try your query in GraphiQL and use the
GraphiQL explorer to see which fields you can query and what shape they have
You want to optionally use your field "isMediumUserDefined" and right now it is not used
anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is
to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This
way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can
define the schema for "SiteSiteMetadata":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src/sections/Writing.js:141:13
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "allMediumPost" on type "Query".
If you don't expect "allMediumPost" to exist on the type "Query" it is most likely a typo.
However, if you expect "allMediumPost" to exist there are a couple of solutions to common
problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js,
please try a restart of your development server
The field might be accessible in another subfield, please try your query in GraphiQL and use the
GraphiQL explorer to see which fields you can query and what shape they have
You want to optionally use your field "allMediumPost" and right now it is not used anywhere.
Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at
least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This
way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can
define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src/sections/Writing.js:144:9
ERROR #85923  GRAPHQL
There was an error in your GraphQL query:
Cannot query field "mediumUser" on type "Query".
If you don't expect "mediumUser" to exist on the type "Query" it is most likely a typo.
However, if you expect "mediumUser" to exist there are a couple of solutions to common problems:

If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js,
please try a restart of your development server
The field might be accessible in another subfield, please try your query in GraphiQL and use the
GraphiQL explorer to see which fields you can query and what shape they have
You want to optionally use your field "mediumUser" and right now it is not used anywhere.
Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at
least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This
way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can
define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: src/sections/Writing.js:162:9
failed extract queries from components - 0.640s
The terminal process "/bin/bash '-c', 'npm run serve'" terminated with exit code: 1.
Terminal will be reused by tasks, press any key to close it.`

Ema told me to re-clone the project and start over... I have now and it's probably all I can do


fix(Theory): use compare_dim, not compare

@jonsterling Is... this... it? :rofl:

Actually, I don't think this could be the entire problem.


Font problem

after merging "footer" to "develop", some icons disappeared

[x] to make those icons visible again

bugs were found & solved


Tapping on log entry doesn't open anything

Noticed on 3.2.0 and 3.3.0 on iPad and iPhone.
Long press reveals some small window from where I can share details, but just tapping doesn't opens new view as it did before (to see request/response details).

Hi, which iOS version are you using?

Latest.
Seems it was my problem - I just replaced the deprecated MainView with ConsoleView and didn't noticed some other changes are required.


No masking for one-hop angles

Hi! Is it intended that one-hop angles are not masked similarly to two-hop angles? If so, could you explain why?
https://github.com/zetayue/MXMNet/blob/2205f6cdf9c6c9793a02839e1a31b1f21d37ebd5/model.py#L59-L81
I would imagine it could look like this:
mask = idx_i_2 != idx_j2
idx_i_2, idx_j1, idx_j2 = idx_i_2[mask], idx_j1[mask], idx_j2[mask]

idx_ji_2 = adj_t_col.storage.row()[mask]
idx_jj = adj_t_col.storage.value()[mask]

I belive that such masking would remove only trivial angles, ie. A-B-A, which are present in one-hop indices

Is it intended that one-hop angles are not masked similarly to two-hop angles? If so, could you explain why?

Yes, this considers a corner case for molecules like A-B. If the one-hop angles are masked, then there would be no message passing between A and B in A-B when doing local message passing.
Empirically, we find that removing the self-loops (just like the example code you suggested to add mask) actually doesn't affect the performance on QM9, since the corner case is rare.

I see. Indeed, the performance does not change when the self-loops are removed. Thank you!


Create bundled Plaster template(s)

Seems like we should include at least one template with Plaster so that there's something to use out of the box.  I'd say we could take the existing example template and polish it up a bit so that it becomes a real starting point for a module.
What else would we need to add to that template to make it a decent starting point for a first initial release?

By the way, I'm thinking of putting the bundled templates inside of the Templates path under the module folder (a subfolder of src in the repo).  Thoughts?

Another template we should include by default is one that can create a basic Plaster template.  Since there will be some module manifest info that needs to be added to mark the module as containing a Plaster template, it'd be good to streamline that process so that template authors don't need to add everything manually.

For the New Module template I have a couple of questions.  First should it be called New Module or New PowerShell Module? I'm leaning towards the latter just to be a bit more specific.
Also, for preparing/building a module do we want to put the output in the current .publish folder?  It's a little weird to call it .publish because it gets created as a result of "building" not publishing.  And many folks will create modules that they'll never publish.  I'm thinking maybe we use Out or perhaps as @jaykul suggests <version-number>.  For a module that uses a .psd1 we could grab the version number from it. However some modules may fore-go a psd1 and have only a psm1 and then there's no version number (perhaps just default to 1.0.0?).
On the plus side, you could do your development directly under ~\Documents\WindowsPowerShell\Modules\<modulename>\<version-number>  and by the build script building "into" that version number dir, the module author can easily import their module under development.  That said, how do we encode this folder into .gitignore.  Can you specify a regex in a gitignore file?

Hmm, looks like we can use something like [0-9].[0-9].[0-9]* in the .gitignore file.

I like "New PowerShell Module" too.  On second thought, is it worth distinguishing between "Script Module" and "DSC Module"?  Is that even a valid distinction?
For publishing, I'd avoid using the version number for folder naming for the reasons you mentioned.  I'm not sure if there's an established pattern in the community yet for where you put your "built" files during development, but it might make sense to have a folder called release (similar to the out suggestion) with a subfolder which has the module's name so that Publish-Module can be used on it.
We could have a psake task called 'install' which will drop the files in the current user's module path if they want to test it that way.  The upside of that vs always building into the module path is that the developer can choose when it happens.

AFAICT the only difference between an "empty" PowerShell module workspace and a DSC module workspace is the existence of the tags DSC, DSCResource, DesiredStateConfiguration in the module manifest.  Probably not worth a separate template.  We could just ask the user for tags during Template processing or just ask if the template is for DSC.  Then we can prepopulate the tags with the common tags for DSC.

folder called release (similar to the out suggestion) with a subfolder which has the module's name so that Publish-Module can be used on it.

Check.  I'll work on that.

We could have a psake task called 'install'

Ooh, I like that.  Sort of like a "publish local". I'll see if I can get that worked into the build script.

The install/deploy local task would definitely be useful. I tend to use that kind of task a lot in my own psake workflow.

I had a quick look into what it would take to perform the "publish local" action. The existing psake script for the plaster module was easy enough, which is always nice for testing, but the example NewModuleTemplate needed a bit of fiddling as the psake script threw some errors.

The build.psake.ps1 script needs updating to reflect recent decisions/changes we've made.  It's on the TODO list.  :-)

I've started a topic branch for this work specifically for the official NewModuleTemplate.  It's time to start thinking about what we really want to have in this template.  For instance, do we want to require the user to enter a Module description at this time?  The example template does but I'm not sure we should for the official new module template.
I also don't think we should ask about the editor. If the module is launched from an editor, we should be able to query an environment variable or something to detect we are running inside VSCode (or ISE).  And if the user runs this from the command line, they may not care about a specific editor or use an editor we might not have support for, so why ask this question.

Agreed, module description probably isn't necessary.  Also agreed that the template probably shouldn't ask which editor they use, but maybe we could ask "Would you like VS Code tasks to be created?" since there is some value there.
Alternatively, we could add some intelligence to the PowerShell extension to detect when a build.psake.ps1 script is present and then ask the user to generate a tasks file for it?  That'd keep us from needing such logic in the template and it'd also allow the extension to refresh the tasks.json later if we figure out a better configuration.


Performance on LIVE-VQC

Hi Dingquan, I am wondering do you have the results on LIVE-VQC [1]? I'd like to simply refer to your results, if available, such that I don't need to test by myself. Thanks!
[1] Z.  Sinno and  A.  C.  Bovik,  “Large-scale study of perceptual video quality,” IEEE Trans. Image Process., vol. 28, no. 2, pp. 612–627, 2018

@vztu Hi Zhengzhong, I do not have the results of VSFA on LIVE-VQC.
You may refer to MDTVSFA for results of LS-VSFA and MDTVSFA on LIVE-VQC.
I have left PKU, and if you are not in a hurry, I can later run the experiments to get the results of VSFA on LIVE-VQC for you.

@vztu Hi Zhengzhong, I do not have the results of VSFA on LIVE-VQC.
You may refer to MDTVSFA for results of LS-VSFA and MDTVSFA on LIVE-VQC.
I have left PKU, and if you are not in a hurry, I can later run the experiments to get the results of VSFA on LIVE-VQC for you.

Hi @lidq92, thanks for your replies and happy new year!
I did check your MDTVSFA, specifically in Table 6, but didn't find the train-test results of VSFA on LIVE-VQC. Table 5 did contain LS-VSFA but did not include LIVE-VQC. Please let me know whether I missed it.
It would be great if you can append the results of VSFA on LIVE-VQC on your VSFA Github repo or elsewhere, but you can just take your time cause I am not in a hurry. It would be very useful if you could also follow the formats of mean (std) as shown in https://github.com/lidq92/VSFA#reproduced-results.

Hi @lidq92, thanks for your replies and happy new year!
I did check your MDTVSFA, specifically in Table 6, but didn't find the train-test results of VSFA on LIVE-VQC. Table 5 did contain LS-VSFA but did not include LIVE-VQC. Please let me know whether I missed it.
It would be great if you can append the results of VSFA on LIVE-VQC on your VSFA Github repo or elsewhere, but you can just take your time cause I am not in a hurry. It would be very useful if you could also follow the formats of mean (std) as shown in https://github.com/lidq92/VSFA#reproduced-results.

@vztu Happy new year, too!
I would update the results in VSFA#reproduced-results.
I just realized 2000 epochs may take too much training time, and I am currently set the epoch number to 300 and re-run the experiments.

@vztu Happy new year, too!
I would update the results in VSFA#reproduced-results.
I just realized 2000 epochs may take too much training time, and I am currently set the epoch number to 300 and re-run the experiments.

Hi thanks, take your time

Hi thanks, take your time

@vztu The results of VSFA on LIVE-VQC (when I set epochs=300) are shown as follows.
And the train-val-test splits information is from here. The exp_id ranges from 0 to 9.
SROCC: 0.6978±0.0340 KROCC: 0.5094±0.0312 PLCC: 0.7426±0.0404 RMSE: 11.6495±0.7385

@vztu The results of VSFA on LIVE-VQC (when I set epochs=300) are shown as follows.
And the train-val-test splits information is from here. The exp_id ranges from 0 to 9.
SROCC: 0.6978±0.0340 KROCC: 0.5094±0.0312 PLCC: 0.7426±0.0404 RMSE: 11.6495±0.7385

Thanks @lidq92!

Thanks @lidq92!


Fix agent payload version check

What does this PR do?
If we are making changes in agent-payload, we sometimes need to use a specific version of that module in the agent-repo based on a commit hash. That breaks the version extraction code.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Describe your test plan
>>> import re
>>> line1 = "github.com/DataDog/agent-payload v4.40.0+incompatible"
>>> line2 = "github.com/DataDog/agent-payload v4.42.1-0.20200826134834-1ddcfb686e3f+incompatible"
>>> version_split = re.split(r'[ +]', line1)
>>> version = version_split[1].split("-")[0].strip()
>>> re.search(r"^v\d+(\.\d+){2}$", version)
<_sre.SRE_Match object at 0x1097904b0>
>>> version
'v4.40.0'
>>> version_split = re.split(r'[ +]', line2)
>>> version = version_split[1].split("-")[0].strip()
>>> re.search(r"^v\d+(\.\d+){2}$", version)
<_sre.SRE_Match object at 0x1097904b0>
>>> version
'v4.42.1'

The run_tests_windows-x86 is throwing a payload-related error, I don't think it is related to this change but could you have a look?

The run_tests_windows-x86 is throwing a payload-related error, I don't think it is related to this change but could you have a look?

Sorry for the n00b question - but how do I look it up?   Usually for other tests, I use the Details link.

The run_tests_windows-x86 is throwing a payload-related error, I don't think it is related to this change but could you have a look?

Sorry for the n00b question - but how do I look it up? Usually for other tests, I use the Details link.

Never mind, I was able to find the link by going to Gitlab. After merging latest master, only the macos build test failed. The error seems unrelated:
Verification for liblzma failed due to a checksum mismatch:

    expected: 19d924e066b6fff0bc9d1981b4e53196
    actual:   afd33cb888461aae3bfd05b80c9e42a8

Ok to merge?

Sure, go ahead! 👍


Composer-Samples (javascript_nodejs) Fails to start the bot. Unable to get a value for host from state. undefined

Context
For more information, see the parent issue. #3436.
Sample information

Sample type: Samples
Sample language: csharp_dotnetcore
Sample name: OrchestratorSchoolNavigator/SchoolNavigator

Describe the bug
While testing these bots, we found out that it Fails to start the bot with error: Unable to get a value for host from state. undefined.
Here's a list of all the cases we found

Bots
Status

javascript_nodejs/projects/qna-sample/qnasample
• Fails to start the bot with error: Unable to get a value for host from state. undefined. •The bot doesn’t work either locally or in Azure.

More context
The following error is thrown in the OnTurn Trace:
"name": "DialogContextError",
"message": "Unable to get a value for host from state. undefined",
"dialogContext": {
"activeDialog": "qnasample",
"stack": [
{
"id": "qnasample",
"state": {
"eventCounter": 9,
"_adaptive": {
"actions": []
},
"lastEvent": "endOfActions"
},
"version": "553652994"
}
]
}
Expected behavior
Bots work out the box using the provided deployment templates and configuration.
Actual behavior
The bot doesn’t work either locally or in Azure

Closing issue as it couldn't be reproduced. The bot is working ok. It's an empty bot that doesn't have any intent configured.


Bulk unit tests fail because of the NATS server

The NATS server gets started on the same port in multiple tests from different packages so Go will run the tests concurrently. This does not appear to happen on the CI server, but happens locally when multiple cpus are available.
Error: unable to start a NATS Server on localhost:4222
Usage:
  run [flags]

Flags:
      --assets-path string         override default assets by serving from a specific directory (developer mode)
      --bolt-path string           path to boltdb database (default "/Users/jsternberg/.influxdbv2/influxd.bolt")
      --e2e-testing                add /debug/flush endpoint to clear stores; used for end-to-end tests
      --engine-path string         path to persistent engine files (default "/Users/jsternberg/.influxdbv2/engine")
  -h, --help                       help for run
      --http-bind-address string   bind address for the REST HTTP API (default ":9999")
      --log-level string           supported log levels are debug, info, and error (default "info")
      --protos-path string         path to protos on the filesystem (default "/Users/jsternberg/.influxdbv2/protos")
      --reporting-disabled         disable sending telemetry data to https://telemetry.influxdata.com every 8 hours
      --secret-store string        data store for secrets (bolt or vault) (default "bolt")
      --store string               backing store for REST resources (bolt or memory) (default "bolt")
      --tracing-type string        supported tracing types are log, jaeger

--- FAIL: TestStorage_WriteAndQuery (10.70s)
    storage_test.go:15: unable to start a NATS Server on localhost:4222
Error: unable to start a NATS Server on localhost:4222
Usage:
  run [flags]

Flags:
      --assets-path string         override default assets by serving from a specific directory (developer mode)
      --bolt-path string           path to boltdb database (default "/Users/jsternberg/.influxdbv2/influxd.bolt")
      --e2e-testing                add /debug/flush endpoint to clear stores; used for end-to-end tests
      --engine-path string         path to persistent engine files (default "/Users/jsternberg/.influxdbv2/engine")
  -h, --help                       help for run
      --http-bind-address string   bind address for the REST HTTP API (default ":9999")
      --log-level string           supported log levels are debug, info, and error (default "info")
      --protos-path string         path to protos on the filesystem (default "/Users/jsternberg/.influxdbv2/protos")
      --reporting-disabled         disable sending telemetry data to https://telemetry.influxdata.com every 8 hours
      --secret-store string        data store for secrets (bolt or vault) (default "bolt")
      --store string               backing store for REST resources (bolt or memory) (default "bolt")
      --tracing-type string        supported tracing types are log, jaeger

--- FAIL: TestLauncher_Task (11.15s)
    tasks_test.go:19: unable to start a NATS Server on localhost:4222

These should be starting on ports other than the default and, preferably, on :0 if the tests don't need to utilize the NATS server.

@mark-rushakoff pointed out to me that adding -p 1 works as it prevents running multiple programs in parallel.

Me too https://circleci.com/gh/influxdata/influxdb/45950?utm_campaign=workflow-failed&utm_medium=email&utm_source=notification

I think this is still an issue. I will confirm today and close if it isn't.

@jsternberg for me it is, I get failures locally.


Broken link from contributing file

Broken link:  https://azure.github.com/guidelines.html
Updating to: https://azure.github.io/azure-sdk/policies_opensource.html

How did you discover the link was broken? Did link verification indicate it?