Incorrect encoding

I am have this schema
message Promo {
  string image = 1;
  string adUrl = 2;
  bool isAd = 3;
}

Used this data
promos=[Promo{image=https://djloboapp.com/main_images/djlobopromo_Android.jpg, isAd=false}, Promo{image=https://djloboapp.com/main_images/followDJLobo2_Android.jpg, adUrl=http://bit.ly/djloboinstagram, isAd=true}, Promo{image=https://djloboapp.com/main_images/djlobobooking_Android.jpg, isAd=false}]

Encoding this using exprotobuf produces
"=
9https://djloboapp.com/main_images/djlobopromo_Android.jpg"^
;https://djloboapp.com/main_images/followDJLobo2_Android.jpghttp://bit.ly/djloboinstagram"?
;https://djloboapp.com/main_images/djlobobooking_Android.jpg%

Any other implementation (I used google's implementation in Python & Golang) gives the following
";
9https://djloboapp.com/main_images/djlobopromo_Android.jpg"^
;https://djloboapp.com/main_images/followDJLobo2_Android.jpghttp://bit.ly/djloboinstagram"=
;https://djloboapp.com/main_images/djlobobooking_Android.jpg%

What is going wrong because of this:
I had no issues because of this until I decided to rewrite one part of the API in Go. The client was using Wire to decode response. Since Wire uses Boolean instead of boolean the response from any other library other than exprotobuf was making it null instead of false. Even though I wish other implementations follow what exprotobuf does, in current state, it does not follow the specification

I'm a bit unclear what exprotobuf should be doing here - do you have a reference to the spec for this, and perhaps a bit more detail pointing out what is different and what you think exprotobuf should be doing? It may be the case that this is something which needs to be addressed in gpb, but I'll definitely take a look at this if I know a bit more about what's wrong.


Add an option to --keep-debug

💡 Feature description
With https://github.com/rustwasm/wasm-bindgen/issues/2389, DWARF symbols work in wasm-bindgen when --keep-debug is passed. However, this cannot be passed from the wasm-pack interface (as far as I know)
💻 Basic example
Currently one manually has to do
cargo build --target wasm32-unknown-unknown &&  wasm-bindgen --keep-debug --web --out-dir pkg ./target/wasm32-unknown-unknown/

It would be better to add some wasm-pack build --keep-debug, or even make that the default for dev builds.

+1

While this is disabled by default in the Cargo.toml Configuration it can be enabled by adding the following to your Cargo.toml and running with the --dev profile:
[package.metadata.wasm-pack.profile.dev.wasm-bindgen]
dwarf-debug-info = true

if you run it with RUST_LOG=info wasm-pack build you should see that it adds the --keep-debug flag to the wasm-bindgen command.

Here is a small demo repo, for DWARF debugging:
https://github.com/haraldreingruber-dedalus/rust-wasm-dwarf-debugging
Happy to hear if that's useful for anybody, or if something can be improved. Also, PR's welcome!


Add new kubectl alias to list all contexts

Small tweak to add an alias for listing all contexts. Tried to use it and realised it wasn't here.

Hey there -- I really appreciate the contribution.
Cheers,
Robby


www/nginx: model was modified in 5a61822 but version not incremented

Nginx model was modified in 5a61822 but model version was not incremented.

Tested migration from 1.24.0 to 1.26.0 with, and without model migration from #2755

Merged, thanks!


added UserAction to get tweets from specific user (close #335)

Hi,
I just added a UserAction in my fork to get only the tweets from a specific user from the CLI and just noticed that there is an open issue for exactly this. Maybe you are interested in merging it?
This addition is the first time I even looked at the code, so I could be missing something obvious. But as far as I can see, this should work. It does at least for me.
Cheers!

Thanks!


Attach connections to latest need event

Currently, the first event in a connection (Hint or Connect) is linked to the need's Create message. This is ok for now as needs cannot be changed, but once that is possible, it makes sense to capture the state of the need at which the connection was created. Therefore, the first message in the connection should link to the latest message in the need's event container.

When we implement need modification, we won't get around that. This issue does not help.


Tutorial - Breaks when you get to "Deploying a next.js App"

Up until Deploying a next.js App, the tutorial takes you through one of the big selling points of Next.js - server side rendering.  We use a server.js file, Express, update our package.json accordingly, etc.
Then when you get to Deploying a next.js App" it suddenly assumes you didn't do any of these changes - and only shows you how to deploy a serverless app.
Can we add a link to relevant SSR docs / warning / something to let people know that they are not about to deploy the app they just built, but one that doesn't do SSR?

Can you elaborate on how and where do things break? Because after all it's just an npm start away on all platforms like Now and Heroku.


[Request] Music (Managed) Democracy

This one straddles https://discord.com/channels/188609066900127744/1191729647390560266/1219085521905516544
I know that Duck song/baby shark/diggy diggy hole/(insert meme song) here is very funny but after it being played 10+ times in a few days it becomes a bit silly.
Instead of banning etc, have it so that if a song has been played before, it is given a pre-weighting of downvotes so that the song selection is less abusable and repeatable

Probably falls under configuration - there is an option for the party to not repeat songs within a certain period of time, this was set to 30mins for SLAN, probably needs to be a few hours at least.


Windows notifications snap to FancyZones

Environment
Windows build number: 10.0.18362.535
PowerToys version: <IP_ADDRESS>
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce
Have the "Move newly created windows to their last known zone" setting enabled. Recieve a native Windows notification.
Expected behavior
Notifications should be excluded from auto-snapping, and appear in the bottom-right corner. Not sure if it is possible to exclude them via the exclusions list. I wouldn't know what name to enter.
Actual behavior
Notifications get snapped to a zone and make that whole area of the screen unclickable until they are dismissed.

Fix available in v0.15.1 https://github.com/microsoft/PowerToys/releases


add opa gatekeeper example for unique names

What does this PR do?
add opa gatekeeper example for unique names
Motivation
Came up in customer use case
More

[x] Yes, I have tested the PR using my local account setup  (Provide any test evidence report under Additional Notes)

[x] Yes, I have added a new example under examples to support my PR

[x] Yes, I have updated the docs for this feature

[ ] Yes, I have linked to an issue or feature request (applicable to PRs that solves a bug or a feature request)

Note:

Not all the PRs require examples and docs
We prefer small, well tested pull requests. Please ensure your pull requests are self-contained, and commits are squashed

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

@nabuskey thanks for the review PTAL when you have a chance

@nabuskey PTAL I added the new line


Custom routing endpoint metadata

Forked from https://github.com/microsoft/reverse-proxy/issues/87#issuecomment-620896307
Endpoint.Metadata is a custom collection with generic search functionality (via downcasting).
https://github.com/dotnet/aspnetcore/blob/600d5ff4978c84b42aa15a11a0fdb0dbd1cc8692/src/Http/Http.Abstractions/src/Routing/EndpointMetadataCollection.cs#L75
We need some way to add custom endpoint metadata. ProxyRoute is too low level for that, it's a raw config representation, you're not going to be able to represent complex objects like IAuthorizeData there. We likely need an event in RuntimeRouteBuilder that lets you customize the routes as we build them. You'd take some config metadata and translate it to complex objects like IAuthorizeData.
https://github.com/microsoft/reverse-proxy/blob/ea7164c689ea06343b99a30aa7feecef4eda215d/src/ReverseProxy.Core/Service/DynamicEndpoints/RuntimeRouteBuilder.cs#L51-L66
Note we've added first class auth support in #122, and CORS is proposed in #281
What other per-endpoint route metadata is there?

Triage: more flexible, but harder to use than just directly implementing Auth & CORS, but may be better in the long run.

I think MapReverseProxy should also return IEndpointConventionBuilder, so the client could add metadata for all routes.

I think MapReverseProxy should also return IEndpointConventionBuilder, so the client could add metadata for all routes.

What kind of metadata would you want to add for all routes? Hard coding authz or cors centrally?

Hard coding authz or cors centrally?

Yes and also any other third-party middleware that might want to use endpoint metadata.
Almost every Map method on IEndpointRouteBuilder returns IEndpointConventionBuilder, and I think YARP should too.


feat: add hook for optimizing series reads based on authorizer (#25207)

Closes #25212
Backport to 1.11

[x] I've read the contributing section of the project README.
[x] Signed CLA (if not already signed).

@devanbenz Can you include the commit hash this was cherry picked from?


Improve the ROI harness reproducibility

Things which confused me while trying to regenerate the ROI harnesses.

CI failed?

Make format still failing https://travis-ci.org/SymbiFlow/prjxray/jobs/511794918

Should be fixed now.


Optimize workflow instance page

Codecov Report

Merging #2589 into dev will decrease coverage by 0.10%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #2589      +/-   ##
============================================
- Coverage     36.18%   36.07%   -0.11%
+ Complexity     2426     2423       -3
============================================
  Files           424      424
  Lines         19624    19624
  Branches       2395     2395
============================================
- Hits           7100     7080      -20
- Misses        11893    11916      +23
+ Partials        631      628       -3

Impacted Files
Coverage Δ
Complexity Δ

.../server/worker/processor/TaskExecuteProcessor.java
10.71% <0.00%> (-28.58%)
1.00% <0.00%> (-2.00%)

...nscheduler/server/entity/TaskExecutionContext.java
73.26% <0.00%> (-5.95%)
53.00% <0.00%> (-3.00%)

...he/dolphinscheduler/common/thread/ThreadUtils.java
71.42% <0.00%> (-3.18%)
14.00% <0.00%> (ø%)

...e/dolphinscheduler/remote/NettyRemotingClient.java
53.95% <0.00%> (+2.87%)
11.00% <0.00%> (+2.00%)

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 d629d38...c01122b. Read the comment docs.


Pangeo TEM example

Part of #145.
This needs the fix in https://github.com/pydata/xarray/pull/7387 to work

Merging this since https://github.com/pydata/xarray/pull/7387 has been merged. Until the next version of xarray is released the notebook in this PR will need a custom install of xarray from the main branch.


Feature Request/Idea: Allow Changing Connections in SQL Notebooks Either Via the API,  Feature, or Both:

Hello! I’ve been working on an extension for Azure Data Studio that allows users to specify connections for code cells in SQL notebooks. The goal is to enable querying multiple databases within a single notebook. I’ve made significant progress, but there’s one crucial piece missing.
I’ve noticed that while you can change the kernel, there’s currently no direct way to switch the connection within the same notebook. Currently, I map code cells to connections based on user selections in a wizard. However, without the ability to change the connection dynamically, the solution won’t be complete.
I’m wondering if we’re allowed to contribute to the API for this functionality. After posting this, I’ll look into the guidelines. If everything aligns, I’d be more than happy to take a stab at contributing this as a full feature for ADS as well. Thank you for your time and consideration!

Contributions are welcome and the team is happy to review PRs :)


Handle rescheduled transaction close event via tunnel.

Addresses issue #3143.  Should unblock PR #3047.
@xf6wang found this issue while creating additional session/transaction open/close tests.  If the plugin lock cannot be obtained in the state_api_callout function the event is rescheduled.  The EVENT_INTERVAL will be sent to the tunnel handler which will then call the HttpSM handler with the HTTP_TUNNEL_EVENT_DONE event.  On the retry the HttpSM handler will have changed to state_api_callout.
State_api_callout already had the HTTP_TUNNEL_EVENT_DONE event, but it was assuming it was a transform tunnel (calling state_common_wait_for_transform_read).  Actually that logic seems to be scattered through HttpSM,  some with a check to see if we are in a transform but most like this do not.   Based on a look at git blame this logic has been there quite a while,  but I think it was added erroneously
What should be happening is that the HTTP_TUNNEL_EVENT_DONE event should be handled as a EVENT_INTERVAL (event retry).
The other thing we had to be careful of was canceling pending_actions that weren't used.  While testing, I'd see 103 events come through before the pending event.  That is fine, but we would need to cancel the pending event so it would not be dangling.
I added asserts to check for pending_action == null before reassign and caught a similar problem in HttpSM::state_cache_open_write that was exercised by the thread tests.

I tested this with 500 requests to force rescheduling and it works ok. No longer seg faults.

This doesn't cherry-pick cleanly to 7.1.x. If we need this for 7.1.x, can you make a PR against 7.1.x please?


Most edit methods print rpc with id=X not responded

Reproducing
~/rustWorkspace/xi-editor/rust(master ✔) cargo run
     Running `target/debug/xicore`
{"id":1,"method":"new_tab","params":[]}
to core: {"id":1,"method":"new_tab","params":[]}
{"id":1,"result":"0"}
{"id":2,"method":"edit","params":{"method":"scroll","params":[0,43],"tab":"0"}}
to core: {"id":2,"method":"edit","params":{"method":"scroll","params":[0,43],"tab":"0"}}
rpc with id=2 not responded

Why
When the edit method is called:

handle_rpc in tabs.rs is called
do_edit in tabs.rs is called
In do_edit if we provided some params respose is built:

let response = {
                if let Some(editor) = self.tabs.get_mut(tab) {
                    let method = params.get("method").unwrap().as_string().unwrap();
                    let params = params.get("params").unwrap();
                    editor.do_rpc(method, params)
                } else {
                    print_err!("tab not found: {}", tab);
                    None
                }
            };

response is either None or editor.do_rpc(method, params)
but editor.do_rpc is  None for all async edit methods
fn async(_: ()) -> Option<Value> {
    None
}

if let Some(response) = response {
                self.respond(response, id);
            } else if let Some(id) = id {
                print_err!("rpc with id={:?} not responded", id);
            }

Solution
Remove the print_err!("rpc with id={:?} not responded", id); call.
I'll send a pull request.

What front-end are you using? The Swift one bundled in the repo does not have this problem. I think your actual problem is that your front-end is sending a sync RPC when it should be sending an async one. In that case, the error message is appropriate.

I'm using xi_glium since I'm on linux. In its code for sending an async request it adds an id to the JSON object, which I believe it's the problem. Async requests don't have an id right?

Right, it shouldn't be sending an id on async requests. Right now, the only bad thing that happens is that error message, but that shouldn't be relied on.

Ok, thanks


feat(mito): Add cache manager

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
This PR adds a manager CacheManager to cache data for the mito engine. This is the first step to implement a cache component for the engine.
It implements a cache layer AsyncFileReaderCache for parquet's AsyncFileReader trait so we can return our cached metadata to ParquetRecordBatchStreamBuilder. The AsyncFileReaderCache also has local cached metadata. It is unused now but is useful when we implement row group readers that require building ParquetRecordBatchStreamBuilder multiple times.
Now the CacheManager only caches metadata of the parquet file. This might provide less improvement in performance. I'll start refactoring our ParquetReader to support caching other data after this PR is merged.
Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

sst_meta_cache_size doesn't take effect for now right?

It takes effect. The default value is a non-zero value.


Can't receive custom metrics "Prometheus" in EastAsia AzureVM  RedHat 7.9

Symptom:
Enabled telegraf agent on multiple Azure VMs. 2 VMs can’t show the customized metrics on the portal, but CPU and Memory is available.

Analysis:
Initially, I confirmed the region EastAsia and OS version RedHat 7.9 is supported.

First I run the 2 commands to check the agent status and debug log, they all looks good and no error reported.
   systemctl status telegraf
   telegraf -debug

Then I compared the configuration file in the 2 VMs of telegraf, and they are all the same.

Run the netstat -ntlp to check the port usage status, it looks good too:
Non-working:

Working:
   ![image](https://user-images.githubusercontent.com/66101176/103252629-8b9c0480-49b8-11eb-9024-c61de96135ce.png)

Checked the DNS name and all looks good.

I checked the backend server and also no data from the Prometheus namespace. But the basic CPU and MEM could sent to Azure successfully, we could confirm the connection between this VM and Azure is good.

I much appreciate your help!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9cea95e2-c775-c363-d468-2232c2b51f4a
Version Independent ID: c87ec30c-b0b7-d6e5-403b-a6d9991248b0
Content: Collect custom metrics for Linux VM with the InfluxData Telegraf agent - Azure Monitor
Content Source: articles/azure-monitor/platform/collect-custom-metrics-linux-telegraf.md
Service: azure-monitor
Sub-service: metrics
GitHub Login: @anirudhcavale
Microsoft Alias: ancav

Additionally, While waiting for influxdata support, I did another test to show that telegraf agent is scraping from Prometheus correctly. Therefore this is probably the link from telegraf to Azure, need to find out why the custom metric namespace is not appearing.
Please let me know if you need any logs.

@xuegao0112 Thanks for your comment. We will review the issue and get back to you shortly.

@xuegao0112 Can you please let me know if you have configured the Telegraf agent to collect metrics from input plugin Prometheus?  If you haven't, can you please follow the procedure mentioned in the document as shown below ?

Hi @SwathiDhanwada-MSFT , thanks for the help.
Yes I have deploy the Telegraf agent to collect metrics from input plugin Prometheus for all of the VMs, and just 2 of them doesn't work.
Attach my configuration here:
###############################################################################
Read metrics from one or many prometheus clients
[[inputs.prometheus]]
An array of urls to scrape metrics from.
urls = ['http://xxxxxxnonworkingVMname:9420/metrics']
metric_version = 2
response_timeout = "30s"
Metric version controls the mapping from Prometheus metrics into
Telegraf metrics.  When using the prometheus_client output, use the same
value in both plugins to ensure metrics are round-tripped without
modification.

example: metric_version = 1; deprecated in 1.13
metric_version = 2; recommended version
metric_version = 1
Url tag name (tag containing scrapped url. optional, default is "url")
url_tag = "scrapeUrl"
An array of Kubernetes services to scrape metrics from.
kubernetes_services = ["http://my-service-dns.my-namespace:9100/metrics"]
Kubernetes config file to create client from.
kube_config = "/path/to/kubernetes.config"
Scrape Kubernetes pods for the following prometheus annotations:
- prometheus.io/scrape: Enable scraping for this pod
- prometheus.io/scheme: If the metrics endpoint is secured then you will need to
set this to 'https' & most likely set the tls config.
- prometheus.io/path: If the metrics path is not /metrics, define it with this annotation.
- prometheus.io/port: If port is not 9102 use this annotation
monitor_kubernetes_pods = true
Restricts Kubernetes monitoring to a single namespace
ex: monitor_kubernetes_pods_namespace = "default"
monitor_kubernetes_pods_namespace = ""
label selector to target pods which have the label
kubernetes_label_selector = "env=dev,app=nginx"
field selector to target pods
eg. To scrape pods on a specific node
kubernetes_field_selector = "spec.nodeName=$HOSTNAME"
Use bearer token for authorization. ('bearer_token' takes priority)
bearer_token = "/path/to/bearer/token"
OR
bearer_token_string = "abc_123"
HTTP Basic Authentication username and password. ('bearer_token' and
'bearer_token_string' take priority)
username = ""
password = ""
Specify timeout duration for slower prometheus clients (default is 3s)
response_timeout = "3s"
Optional TLS Config
tls_ca = /path/to/cafile
tls_cert = /path/to/certfile
tls_key = /path/to/keyfile
Use TLS but skip chain & host verification
insecure_skip_verify = false
Please feel free to let me know if any.

By the way, attached by debugging log with comand below:
sudo tcpdump -A -s0 -i lo 'port 9420' -w output.pcap

-- Logs begin at Mon 2020-11-30 20:08:32 +08, end at Thu 2020-12-24 19:06:38 +08. --
Dec 24 02:40:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T18:40:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 02:40:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T18:40:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 04:53:00 hkprho3opsh30vf telegraf[40299]: 2020-12-23T20:53:00Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 04:53:00 hkprho3opsh30vf telegraf[40299]: 2020-12-23T20:53:00Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 05:10:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T21:10:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 05:10:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T21:10:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 05:11:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T21:11:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 05:11:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T21:11:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 05:12:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T21:12:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 05:12:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T21:12:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 05:13:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T21:13:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 05:13:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T21:13:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 06:26:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T22:26:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 06:26:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T22:26:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 07:37:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T23:37:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 07:37:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T23:37:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 07:38:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T23:38:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 07:38:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T23:38:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 07:39:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T23:39:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 07:39:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T23:39:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 07:40:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T23:40:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 07:40:30 hkprho3opsh30vf telegraf[40299]: 2020-12-23T23:40:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 07:50:00 hkprho3opsh30vf telegraf[40299]: 2020-12-23T23:50:00Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 07:50:00 hkprho3opsh30vf telegraf[40299]: 2020-12-23T23:50:00Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 08:40:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T00:40:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 08:40:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T00:40:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 08:41:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T00:41:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 08:41:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T00:41:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 08:42:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T00:42:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 08:42:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T00:42:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 08:43:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T00:43:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 08:43:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T00:43:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 10:10:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T02:10:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 10:10:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T02:10:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 10:49:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T02:49:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 10:49:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T02:49:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 12:56:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T04:56:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 12:56:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T04:56:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 13:02:00 hkprho3opsh30vf telegraf[40299]: 2020-12-24T05:02:00Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 13:02:00 hkprho3opsh30vf telegraf[40299]: 2020-12-24T05:02:00Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 13:17:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T05:17:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 13:17:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T05:17:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 13:19:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T05:19:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 13:19:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T05:19:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 13:23:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T05:23:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 13:23:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T05:23:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 13:26:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T05:26:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 13:26:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T05:26:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 14:31:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T06:31:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 14:31:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T06:31:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 15:04:00 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:04:00Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 15:04:00 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:04:00Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 15:09:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:09:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 15:09:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:09:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 15:28:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:28:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 15:28:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:28:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 15:34:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:34:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 15:34:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:34:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 15:36:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:36:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 15:36:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:36:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 15:37:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:37:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 15:37:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:37:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 15:38:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:38:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 15:38:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:38:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 15:39:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:39:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 15:39:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T07:39:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 16:02:00 hkprho3opsh30vf telegraf[40299]: 2020-12-24T08:02:00Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 16:02:00 hkprho3opsh30vf telegraf[40299]: 2020-12-24T08:02:00Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 17:38:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T09:38:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 17:38:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T09:38:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 17:51:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T09:51:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 17:51:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T09:51:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 18:14:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:14:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 18:14:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:14:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 18:25:00 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:25:00Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 18:25:00 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:25:00Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 18:31:00 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:31:00Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 18:31:00 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:31:00Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 18:36:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:36:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 18:36:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:36:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 18:50:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:50:30Z W! [inputs.prometheus] Collection took longer than expected; not complete after interval of 30s
Dec 24 18:50:30 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:50:30Z E! [inputs.prometheus] Error in plugin: error making HTTP request to http://hkprho3opsh30vf:9420/metrics: Get "http://hkprho3opsh30vf:9420/metrics": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Dec 24 18:54:30 hkprho3opsh30vf systemd[1]: Stopping The plugin-driven server agent for reporting metrics into InfluxDB...
Dec 24 18:54:39 hkprho3opsh30vf telegraf[40299]: 2020-12-24T10:54:39Z I! [agent] Hang on, flushing any cached metrics before shutdown
Dec 24 18:54:40 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:54:40 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:54:40 hkprho3opsh30vf telegraf[10687]: 2020-12-24T10:54:40Z I! Starting Telegraf 1.16.2
Dec 24 18:54:40 hkprho3opsh30vf telegraf[10687]: 2020-12-24T10:54:40Z E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: Error parsing prometheus, line 777: field corresponding to internal' is not defined in prometheus.Prometheus Dec 24 18:54:40 hkprho3opsh30vf systemd[1]: telegraf.service: main process exited, code=exited, status=1/FAILURE Dec 24 18:54:40 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state. Dec 24 18:54:40 hkprho3opsh30vf systemd[1]: telegraf.service failed. Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service holdoff time over, scheduling restart. Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:54:41 hkprho3opsh30vf telegraf[10713]: 2020-12-24T10:54:41Z I! Starting Telegraf 1.16.2 Dec 24 18:54:41 hkprho3opsh30vf telegraf[10713]: 2020-12-24T10:54:41Z E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: Error parsing prometheus, line 777: field corresponding to internal' is not defined in prometheus.Prometheus
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service: main process exited, code=exited, status=1/FAILURE
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state.
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service failed.
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service holdoff time over, scheduling restart.
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:54:41 hkprho3opsh30vf telegraf[10736]: 2020-12-24T10:54:41Z I! Starting Telegraf 1.16.2
Dec 24 18:54:41 hkprho3opsh30vf telegraf[10736]: 2020-12-24T10:54:41Z E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: Error parsing prometheus, line 777: field corresponding to internal' is not defined in prometheus.Prometheus Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service: main process exited, code=exited, status=1/FAILURE Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state. Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service failed. Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service holdoff time over, scheduling restart. Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:54:41 hkprho3opsh30vf telegraf[10760]: 2020-12-24T10:54:41Z I! Starting Telegraf 1.16.2 Dec 24 18:54:41 hkprho3opsh30vf telegraf[10760]: 2020-12-24T10:54:41Z E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: Error parsing prometheus, line 777: field corresponding to internal' is not defined in prometheus.Prometheus
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service: main process exited, code=exited, status=1/FAILURE
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state.
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service failed.
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service holdoff time over, scheduling restart.
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:54:41 hkprho3opsh30vf telegraf[10782]: 2020-12-24T10:54:41Z I! Starting Telegraf 1.16.2
Dec 24 18:54:41 hkprho3opsh30vf telegraf[10782]: 2020-12-24T10:54:41Z E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: Error parsing prometheus, line 777: field corresponding to internal' is not defined in prometheus.Prometheus Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service: main process exited, code=exited, status=1/FAILURE Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state. Dec 24 18:54:41 hkprho3opsh30vf systemd[1]: telegraf.service failed. Dec 24 18:54:42 hkprho3opsh30vf systemd[1]: telegraf.service holdoff time over, scheduling restart. Dec 24 18:54:42 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:54:42 hkprho3opsh30vf systemd[1]: start request repeated too quickly for telegraf.service Dec 24 18:54:42 hkprho3opsh30vf systemd[1]: Failed to start The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:54:42 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state. Dec 24 18:54:42 hkprho3opsh30vf systemd[1]: telegraf.service failed. Dec 24 18:55:26 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:55:26 hkprho3opsh30vf telegraf[11115]: 2020-12-24T10:55:26Z I! Starting Telegraf 1.16.2 Dec 24 18:55:26 hkprho3opsh30vf telegraf[11115]: 2020-12-24T10:55:26Z E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: Error parsing prometheus, line 777: field corresponding to internal' is not defined in prometheus.Prometheus
Dec 24 18:55:26 hkprho3opsh30vf systemd[1]: telegraf.service: main process exited, code=exited, status=1/FAILURE
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state.
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: telegraf.service failed.
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: telegraf.service holdoff time over, scheduling restart.
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:55:27 hkprho3opsh30vf telegraf[11139]: 2020-12-24T10:55:27Z I! Starting Telegraf 1.16.2
Dec 24 18:55:27 hkprho3opsh30vf telegraf[11139]: 2020-12-24T10:55:27Z E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: Error parsing prometheus, line 777: field corresponding to internal' is not defined in prometheus.Prometheus Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: telegraf.service: main process exited, code=exited, status=1/FAILURE Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state. Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: telegraf.service failed. Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: telegraf.service holdoff time over, scheduling restart. Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:55:27 hkprho3opsh30vf telegraf[11161]: 2020-12-24T10:55:27Z I! Starting Telegraf 1.16.2 Dec 24 18:55:27 hkprho3opsh30vf telegraf[11161]: 2020-12-24T10:55:27Z E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: Error parsing prometheus, line 777: field corresponding to internal' is not defined in prometheus.Prometheus
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: telegraf.service: main process exited, code=exited, status=1/FAILURE
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state.
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: telegraf.service failed.
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: telegraf.service holdoff time over, scheduling restart.
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:55:27 hkprho3opsh30vf telegraf[11190]: 2020-12-24T10:55:27Z I! Starting Telegraf 1.16.2
Dec 24 18:55:27 hkprho3opsh30vf telegraf[11190]: 2020-12-24T10:55:27Z E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: Error parsing prometheus, line 777: field corresponding to internal' is not defined in prometheus.Prometheus Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: telegraf.service: main process exited, code=exited, status=1/FAILURE Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state. Dec 24 18:55:27 hkprho3opsh30vf systemd[1]: telegraf.service failed. Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: telegraf.service holdoff time over, scheduling restart. Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB. Dec 24 18:55:28 hkprho3opsh30vf telegraf[11215]: 2020-12-24T10:55:28Z I! Starting Telegraf 1.16.2 Dec 24 18:55:28 hkprho3opsh30vf telegraf[11215]: 2020-12-24T10:55:28Z E! [telegraf] Error running agent: Error loading config file /etc/telegraf/telegraf.conf: Error parsing prometheus, line 777: field corresponding to internal' is not defined in prometheus.Prometheus
Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: telegraf.service: main process exited, code=exited, status=1/FAILURE
Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state.
Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: telegraf.service failed.
Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: telegraf.service holdoff time over, scheduling restart.
Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: Stopped The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: start request repeated too quickly for telegraf.service
Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: Failed to start The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: Unit telegraf.service entered failed state.
Dec 24 18:55:28 hkprho3opsh30vf systemd[1]: telegraf.service failed.
Dec 24 18:55:55 hkprho3opsh30vf systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB.
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z I! Starting Telegraf 1.16.2
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z I! Loaded inputs: prometheus
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z I! Loaded aggregators:
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z I! Loaded processors:
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z I! Loaded outputs: azure_monitor
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z I! Tags enabled: host=hkprho3opsh30vf
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z I! [agent] Config: Interval:10s, Quiet:false, Hostname:"hkprho3opsh30vf", Flush Interval:30s
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z D! [agent] Initializing plugins
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z D! [agent] Connecting outputs
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z D! [agent] Attempting connection to [outputs.azure_monitor]
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z D! Writing to Azure Monitor URL: https://eastasia.monitoring.azure.com/subscriptions/66bb2e7a-f536-433b-8e7a-cb2593074a11/resourceGroups/rsg-hkprho-prd-az2-rfsxvf/providers/Microsoft.Compute/virtualMachines/hkprho3opsh30vf/metrics
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z D! [agent] Successfully connected to outputs.azure_monitor
Dec 24 18:55:55 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:55:55Z D! [agent] Starting service inputs
Dec 24 18:56:48 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:56:48Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 18:57:21 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:57:21Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 869.458746ms
Dec 24 18:57:21 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:57:21Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 524.099783ms
Dec 24 18:57:22 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:57:22Z D! [outputs.azure_monitor] Wrote batch of 592 metrics in 429.278693ms
Dec 24 18:57:22 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:57:22Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 18:58:17 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:58:17Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 249.283354ms
Dec 24 18:58:18 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:58:18Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 457.425205ms
Dec 24 18:58:18 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:58:18Z D! [outputs.azure_monitor] Wrote batch of 592 metrics in 612.726082ms
Dec 24 18:58:18 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:58:18Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 18:58:56 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:58:56Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 18:59:33 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:59:33Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 551.752788ms
Dec 24 18:59:33 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:59:33Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 537.55788ms
Dec 24 18:59:34 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:59:34Z D! [outputs.azure_monitor] Wrote batch of 592 metrics in 500.448036ms
Dec 24 18:59:34 hkprho3opsh30vf telegraf[11368]: 2020-12-24T10:59:34Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 19:00:12 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:00:12Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 442.178182ms
Dec 24 19:00:12 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:00:12Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 483.860093ms
Dec 24 19:00:13 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:00:13Z D! [outputs.azure_monitor] Wrote batch of 592 metrics in 562.879951ms
Dec 24 19:00:13 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:00:13Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 19:00:46 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:00:46Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 19:01:33 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:01:33Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 590.522156ms
Dec 24 19:01:33 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:01:33Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 176.66579ms
Dec 24 19:01:34 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:01:34Z D! [outputs.azure_monitor] Wrote batch of 592 metrics in 509.181864ms
Dec 24 19:01:34 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:01:34Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 19:02:26 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:02:26Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 286.161895ms
Dec 24 19:02:27 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:02:27Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 483.135982ms
Dec 24 19:02:27 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:02:27Z D! [outputs.azure_monitor] Wrote batch of 592 metrics in 559.269098ms
Dec 24 19:02:27 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:02:27Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 19:03:21 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:03:21Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 369.168912ms
Dec 24 19:03:22 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:03:22Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 476.687387ms
Dec 24 19:03:22 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:03:22Z D! [outputs.azure_monitor] Wrote batch of 592 metrics in 477.096394ms
Dec 24 19:03:22 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:03:22Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 19:03:56 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:03:56Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 19:04:47 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:04:47Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 429.351794ms
Dec 24 19:04:48 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:04:48Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 336.690335ms
Dec 24 19:04:48 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:04:48Z D! [outputs.azure_monitor] Wrote batch of 592 metrics in 552.200195ms
Dec 24 19:04:48 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:04:48Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 19:05:19 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:05:19Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 440.980665ms
Dec 24 19:05:19 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:05:19Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 244.622986ms
Dec 24 19:05:19 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:05:19Z D! [outputs.azure_monitor] Wrote batch of 592 metrics in 255.214542ms
Dec 24 19:05:19 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:05:19Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 19:05:50 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:05:50Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics
Dec 24 19:06:28 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:06:28Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 472.701539ms
Dec 24 19:06:29 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:06:29Z D! [outputs.azure_monitor] Wrote batch of 2500 metrics in 553.267022ms
Dec 24 19:06:29 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:06:29Z D! [outputs.azure_monitor] Wrote batch of 592 metrics in 499.399331ms
Dec 24 19:06:29 hkprho3opsh30vf telegraf[11368]: 2020-12-24T11:06:29Z D! [outputs.azure_monitor] Buffer fullness: 0 / 10000 metrics

Hi @SwathiDhanwada-MSFT S, greetings, may I know if any update on our issue? Many thanks!

Hi @SwathiDhanwada-MSFT S, greetings, may I know if any update on our issue? Many thanks!

@xuegao0112  Apologies for late response. From the information provided, I could see the you weren't facing any issues with most of the virtual machines but with specific virtual machines. I would recommend engaging our technical support team for further detailed analysis. Please file a support case using these steps. If you do not have a support plan, send mail to<EMAIL_ADDRESS>include your subscription ID and a link to this GitHub thread (for context).
As there are no further documentation changes, we will close the issue for now. If there are further questions , please revert and we will be glad to assist you.

@xuegao0112  Apologies for late response. From the information provided, I could see the you weren't facing any issues with most of the virtual machines but with specific virtual machines. I would recommend engaging our technical support team for further detailed analysis. Please file a support case using these steps. If you do not have a support plan, send mail to<EMAIL_ADDRESS>include your subscription ID and a link to this GitHub thread (for context).
As there are no further documentation changes, we will close the issue for now. If there are further questions , please revert and we will be glad to assist you.


settings: Make bot-settings tabs look better in dark mode.

Fixes: #9230.
Here are two prototype one with the complete white border and one with a blue border for active tab. Which one looks better?

Currently, PR has the "complete white border" changes.

Can you check whether any of these changes improve day mode as well?  We just like to keep the night mode CSS as small as possible.

Can you check whether any of these changes improve day mode as well?

No all changes only night-mode specific and are just night-mode analogous to the one in bootstrap.css

We just like to keep the night mode CSS as small as possible.

Yeah, I've also tried keeping it as small as possible.
BTW here is the bootstrap css:
    color: #555555;
    cursor: default;
    background-color: #ffffff;
    border: 1px solid #ddd;
    border-bottom-color: transparent;

I've to use again border-color because blackening of border on hover.

Makes sense!


Add status checks for PR approval

Add checks to ensure that the PR raised meets the minimum standards for merging:

linter has no error
tests are passing (tests to be added first)

9daa88cb143f5150a21d24047fad1d9b48d59319


KAFKA-12239 Detail log 'Error getting JMX attribute'

When collecting bulk metrics, this warning message in logs is unhelpful, it is impossible to determine which MBean is missing this attribute and fix the metric collector:
``[2021-01-26T15:43:41,078][WARN ][org.apache.kafka.common.metrics.JmxReporter] Error getting JMX attribute 'records-lag-max'
javax.management.AttributeNotFoundException: Could not find attribute records-lag-max
This pull request just adds the MBean object name in the log to ease debugging.

@gquintana thanks for your patch. Could you share the new error message to me?


[Documentation] Refine extension release notes

Peer of https://github.com/Azure/azure-cli/pull/13960

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

add to S171


DotNetCoreWindowsHosting install corrupt after sysprep

From @elangelo on September 6, 2018 14:44
As part of our offering on Azure we have an API service that is running in dotnetcore 2.0
We use packer to create a custom image and install the dotnetcore windows hosting module.
The version we install is DotNetCore.2.0.0-WindowsHosting.exe
At the end of the packer process a sysprep gets run:
"& $env:SystemRoot\System32\Sysprep\Sysprep.exe /oobe /generalize /quiet /quit",
When i spin up a machine from this image and install our dotnet core service on it we always get 500s externally. browsing localhost we get:

The only way to fix this is to go to the control panel and find the dotnetcore hosting program and click on repair:

I have no idea why this even helps or why the installation wouldn't survive a sysprep in the first place. I would like to know

why does the installation not survive a sysprep
how can i figure out what the repair actually fixes and what is actually broken (so i can perhaps fix it manually with some powershell script instead of just having to manually run the 'repair' step.

Copied from original issue: aspnet/Home#3508

From what it looks like, Sysprep may be removing modifications to the C:\Windows\System32\inetsrv\config\applicationhost.config file. The windows hosting bundle modifies the applicationhost.config to include a new module ( <add name="AspNetCoreModule" image="%windir%\System32\inetsrv\aspnetcore.dll" />) and handler section (
).
To confirm my hypothesis, before clicking on the repair button, can you open the applicationhost.config file and see if aspnetcore is present?
To fix the issue manually, you should be able to make a quick powershell script to insert the removed elements (or file replace with a backup).

cc @joeloff

Confirmed that neither the module or the handler was present in the applicationHost.config file
Confirmed that repair added
a. <add name="AspNetCoreModule" image="%SystemRoot%\system32\inetsrv\aspnetcore.dll" /> in <configuration>\<system.webServer>\<globalModules>
b.
 in <configuration>\<configSections>\<sectionGroup name="system.webServer">
c. <add name="AspNetCoreModule" /> in <configuration>\<location path="" overrideMode="Allow">\<system.webServer>\<modules>\<add name="AspNetCoreModule" />

@shirhatti is there an external issue tracking this?


Hardware Environment?

@LinJM @bgshih @varun-suresh
Is the following hardware environment configuration  applicable?Thank you!

Core  i5 3.4GHz CPU @ 8G
Storage: 1TB Fusion Drive
Ideo Card：AMD R9 390, Retina 5K Screen

@LinJM @bgshih @varun-suresh
We want to build a set of environments. What kind of hardware environment should I choose?


Support broken /FitH destinations that are missing the "top" value (bug 1663390)

See https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/PDF32000_2008.pdf#G11.2095870
Fixes bug 1663390

/botio-linux preview

Thanks!


Material channel mixup

The blend file has separate grayscale images for metallic and roughness, but, the roughness ends up in R and the metallic ends up in both G and B, even after the fix in #139.  Not sure why.
Originally posted by @emackey in https://github.com/KhronosGroup/glTF-Blender-IO/issues/116#issuecomment-445265585

Confirmed, here's a copy of the .blend:
monkey_PBR_005.blend.zip
I'll move this to milestone VII since it appears to be an important regression, but let me know if it should not be there.


Parse integer and float values, add them to the AST

Could you update https://github.com/ruby/prism/blob/main/docs/serialization.md#types to include this new type, and whether it's most/least significant word first?

Could you update https://github.com/ruby/prism/blob/main/docs/serialization.md#types to include this new type, and whether it's most/least significant word first?

Done! This PR now includes FloatNode as well, which I've also updated.

Very nice, looking forward to adopt this.


Question: Is there API to identify DXVK?

I'm currently working on a library to allow swapchain image sharing across processes in a cross platform manner. For this to work while running under DXVK I'd need to first detect DXVK, then get the VkImage handles for the underlying Vulkan renderer.
Brute force method would just be to find some DXVK function that generally always exists and using GetProcAddress on it to detect DXVK. But if there's a cleaner way I'd like to know.

We have a COM interface for Vulkan interop, see https://github.com/doitsujin/dxvk/blob/4c09b006a5ce84b4707a0b175a800c56a28643f0/src/dxgi/dxgi_interfaces.h#L312.
Please note that the Vulkan swap chain itself can be recreated at any point in time, it's not safe to export those, and if you rely on current implementation details, we will break those in the future.

Not sure if it counts as cleaner or dirtier, but FWIW specialk just checks if the loaded api dll product name contains "DXVK".

I'd say checking the DXVK interop COM interfaces is a lot cleaner, especially since OP needs the Vulkan handles after that anyway.


google-music-scripts: 4.0.1 -> 4.3.0

Motivation for this change
going through r-ryantm logs
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

https://github.com/NixOS/nixpkgs/pull/84081
1 package marked as broken and skipped:
python38Packages.google-music

11 package built:
google-music-scripts python37Packages.audio-metadata python37Packages.google-music python37Packages.google-music-proto python37Packages.google-music-utils python37Packages.httpx python37Packages.tbm-utils python38Packages.audio-metadata python38Packages.google-music-proto python38Packages.google-music-utils python38Packages.tbm-utils

oh yea, forgot about that while i was fixing all the dependencies

removed


Improve the text at the top of the home page

Received the latest home page text from the product team.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: croncles sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


To Disable Smooth-Scrolling: use "--disable-smooth-scrolling"

Since Messenger for Desktop uses Chromium, you can start the main binary with flags. In this case, to disable smooth scrolling use the argument "--disable-smooth-scrolling".

The question is, why? What does this fix/improve?

Just to improve the user experience - since it's turned on by default (Chromium default flags), I thought I'd post it in case someone wants to know how to turn smooth scrolling off :)

So on Linux, at least for you, disabling smooth scrolling provides a better experience in the app?

I'm on Windows, but yeah it's far more easier for me to use lol

I'm sorry, you're the first to complain about this and I'd rather keep the Chromium default.

Oh well, at least it's there for people if they want to change it lol.


Multiple code improvements fix 1

This pull request is focused on resolving occurrences of Sonar rules
squid:S1172 - Unused method parameters should be removed.
squid:CommentedOutCodeLine - Sections of code should not be "commented out".
You can find more information about the issue here:
https://dev.eclipse.org/sonar/coding_rules#q=squid%3AS1172
https://dev.eclipse.org/sonar/coding_rules#q=squid%3ACommentedOutCodeLine
Please let me know if you have any questions.
George Kankava

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

ok to test

Thanks.


Update guidance for software with RRIDs

[x] Clarify whether software with RRIDs needs to be added as a software ref

@eLife-Exeter We have updated the guidance for when software references need to be added (see changelog on the software refs page).


BlobLoader.yield_blobs returns Iterable, it should be Iterator like in BaseLoader

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
class BlobLoader(ABC):
"""Abstract interface for blob loaders implementation.
Implementer should be able to load raw content from a storage system according
to some criteria and return the raw content lazily as a stream of blobs.
"""

@abstractmethod
def yield_blobs(
    self,
) -> Iterable[Blob]:
    """A lazy loader for raw data represented by LangChain's Blob object.

    Returns:
        A generator over blobs
    """

Error Message and Stack Trace (if applicable)
No response
Description
BlobLoader.yield_blobs returns Iterable, it should be Iterator like in BaseLoader
System Info
BlobLoader.yield_blobs returns Iterable, it should be Iterator like in BaseLoader

I tried it, and it does indeed return an Iterable object instead of an Iterator.
from collections.abc import Iterable, Iterator

from langchain_community.document_loaders.blob_loaders.youtube_audio import (
    YoutubeAudioLoader,
)
from langchain_core.documents.base import Blob

urls = ["https://www.youtube.com/watch?v=xxxxx"]
save_dir = r"your_save_dir"
loader = YoutubeAudioLoader(urls, save_dir)
for x in loader.yield_blobs():
    print(isinstance(x, Iterator))  # False
    print(isinstance(x, Iterable))  # True
    print(isinstance(x, Blob))  # True
    for i in x:
        print(i)  # ok
    next(x)  # TypeError: 'Blob' object is not an iterator

I see. I mistakenly thought Blob needed to be an Iterator.
It is indeed an Iterator because it's a generator.

If it's explicitly a generator, I'd prefer it to be written as Generator[Blob, None, None].
However, it seems that LangChain often writes generators as Iterator[...]?


⚠ Bofrost.de has degraded performance

In 9c1eea8, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1978 ms

Resolved: Bofrost.de performance has improved in ee918c5 after 35 minutes.


Add javadoc to core classes such as RetryParams and BackoffParams

Javadoc has been added to all core classes in b374d6949820e36b350c28f0a70f9ebe064fdcdd and c4b99a33c1c7453a1ff71386d9ec992f41a66e30.


Capture VM

Resource Provider
COMPUTE
Description of Feature or Work Requested
Customers can capture a VM to a shared image gallery
Minimum API Version Required

Swagger Link
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/compute/resource-manager/Microsoft.Compute/preview/2020-09-30/gallery.json

In SIG, it would automate a PUT Gallery, PUT GalleryImage and then PUT GalleryImageVersion

Target Date
Early Co

put in backlog firstly for Cobalt

@puicchan I want confirm that this issue introduces no new REST API and a new CLI command like az sig capture will be added. It simplifies steps to capture a VM into an image version.

This feature is canceled according to Yemi.

This feature is canceled according to Yemi.


Track alignment version

WIP, this will be rebased off of master after the latest_imgt branch.

This fixes #40


Add alwaysOpen option to Gui wrapper

Conditionally render last row
override the expanded state with prop bool

https://github.com/wwwtyro/dis-gui/issues/6

Merged and published as 2.1.0 - please update


Can JuiceFS be used as the underlying storage for traditional relational databases?

Hi JuiceFS developer ! Recently,GitHub has a MQ Product namely AutoMQ, it use similar storage theory just like JuiceFS to reduce storage price and improve storage effects, so I  have a question that if I can use JuiceFS as database storage , mount file ,then arrive similar effects, but I am not sure the performance is good and the way is recommend. I want to use public cloud object storage to store data, it’s so convenient  and infinity storage capacity feel like so good .

Functionally yes, JuiceFS can serve as the underlying storage. But it's not recommended considering the performance, as JuiceFS is optimized for sequential write/read. In other words, JuiceFS can be a very good choice for OLAP, but not best practice for OLTP.

Consider WeSQL for this use case.


Fix alignment of tag headers of Linodes list

I have a couple of Linodes grouped by their tags. The left padding of these headers' container td is inconsistent. The first header has left-padding of 15px, while the second's left-padding is 0px.
https://cloud.linode.com/linodes?view=list

Firefox 74.0

Good catch @jungaretti. I just opened a PR to address this.


Is it possible to run "after" middleware even when "before" middleware exits error?

I'm trying to add an "after" middleware that runs on every request for stats purposes (the example  below simply logs the response status code).
But I also have an authenticating "before" middleware, and when that blocks a request, my "after" middleware doesn't run.
Is there a way to make this work?
func main() {
	server := atreugo.New(&atreugo.Config{Addr: "<IP_ADDRESS>:8080"})

	// global "after" middleware to log response code
	server.UseAfter(func(ctx *atreugo.RequestCtx) error {
		ctx.Logger().Printf("status code: %d", ctx.Response.StatusCode())
		return ctx.Next()
	})

	// unauthorized in the handler - logging middleware runs
	server.GET("/401", func(ctx *atreugo.RequestCtx) error {
		return ctx.ErrorResponse(nil, fasthttp.StatusUnauthorized)
	})

	// authorized by Before middleware - logging middleware DOES run
	server.NewGroupPath("/unprotected").UseBefore(func(ctx *atreugo.RequestCtx) error {
		return ctx.Next()
	}).GET("/200", func(ctx *atreugo.RequestCtx) error {
		return ctx.ErrorResponse(nil, fasthttp.StatusOK)
	})

	// unauthorized by Before middleware - logging middleware DOES NOT run
	server.NewGroupPath("/protected").UseBefore(func(ctx *atreugo.RequestCtx) error {
		return ctx.ErrorResponse(nil, fasthttp.StatusUnauthorized)
	}).GET("/200", func(ctx *atreugo.RequestCtx) error {
		return ctx.ErrorResponse(nil, fasthttp.StatusOK)
	})

	log.Fatal(server.ListenAndServe())
}

Hi @pmahoney,
Do you want to return an error in "before" middleware, skip the view and runs "after" middlewares?

Hi @savsgio, yes, that's exactly what I would like to do (either with middleware or some other means).

In before middleware you could change to
// Set the error response
ctx.ErrorResponse(....)

// Not execute the view
ctx.SkipView()

// Continue to the next middleware
return ctx.Next()

Maybe you shouldn't execute all code in the following middlewares, so you could set a flag like ctx.SetUserValue("fail", true) and check it when you need:
...

if ctx.UserValue("fail").(bool){
    return ctx.Next()
}

...

Thanks!


Improve the error message when removing states still in use

Coverage remained the same at 99.459% when pulling 5444e604937ad78f0a5eca0633b45b24713d09ee on improve-state-removal-validation-error into 435e4c611e14a4510b04013726fb4f86d8c1949b on master.


r1.15 cherry-pick request: [Intel MKL] Upgrade MKL-DNN to 0.20.3

This fixes a critical bug that affects convergence of 3D-GANs, U-Net, V-NET, and most other 3D models.
Original PR: https://github.com/tensorflow/tensorflow/pull/31906 (merged in master).

@agramesh1 Could you please post "@googlebot I consent." to resolve the CLA issue? Thank you!

@googlebot I consent.


Update issue

About a week ago I've started to receive update failed messages. Restart did not help

Failed to perform the action update/install. Error updating Sunsynk/Deye Inverter Add-on (edge/dev): Can't install ghcr.io/kellerza/hass-addon-sunsynk-multi/aarch64:92dd837: 500 Server Error for http+docker://localhost/v1.47/images/create?tag=92dd837&fromImage=ghcr.io%2Fkellerza%2Fhass-addon-sunsynk-multi%2Faarch64&platform=linux%2Farm64: Internal Server Error ("manifest unknown")

I'm getting the same but with the DEV version.
There was a update available , it failed to update, I eventually uninstalled it , now it won't re install  ( manifest unknown)
"""Can't install ghcr.io/kellerza/hass-addon-sunsynk-multi/aarch64:92dd837: 500 Server Error for http+docker://localhost/v1.47/images/create?tag=92dd837&fromImage=ghcr.io%2Fkellerza%2Fhass-addon-sunsynk-multi%2Faarch64&platform=linux%2Farm64: Internal Server Error ("manifest unknown")
"""
I have patiently been waiting for it to get resolved

@maslyankov - should we build for more platforms, or can we point the addon config to the multi-platform build?
Today, in config.yml, we have
version: "92dd837"
image: ghcr.io/kellerza/hass-addon-sunsynk-multi/{arch}
arch:
  - aarch64
  - amd64
  - armhf
  - armv7
  - i386

and hass-addon-sunsynk-multi/aarch64 is not being updated

In the context of Docker images, aarch64 and arm64 are often used interchangeably because they both refer to the 64-bit ARM architecture. Technically, aarch64 is the architecture name defined by the ARM company, while arm64 is commonly used by many platforms, including Docker and Linux distributions, as an alias.
So, while aarch64 and arm64 may appear in different contexts, they refer to the same 64-bit ARM architecture. Docker will typically recognize both as equivalent, but when building multi-platform Docker images, it’s standard to use arm64 as the platform designation.
I think it's safe to point the addon config to the multiplatform image.

Thanks @maslyankov - I removed /{arch} from the edge addon
@Saurman @deondti - make sure you update the store info - "check for updates" should hopefully do it & then try again

@kellerza Mine has now download successfully , thank you for this project and all your efforts, I don't think you always get the gratitude for this, I'm sure I speak for many that we really appreciate this.

@kellerza fix confirmed, updated to 92dd837


'ImageData' object has no attribute 'texture'

when I run the file main.py it says that 'ImageData' object has no attribute 'texture' so what I should do please tell

Same problem here. :cry:

Just look through the code and replace .texture with get_texture()

@ajh123  It seemed to helped however now I am getting green bars across the screen? I should probably say that I used 2to3 to move everything over to python 3. Any idea what could be the reason?

You didn't need to use 2to3, it works. and just change any print "...". to. print("...")

I thought that the python3 branch was merged a while ago so that the master
branch was compatible with python3. It should be working fine.
On Mon, Dec 28, 2020 at 3:03 AM ajh123<EMAIL_ADDRESS>wrote:

You didn't need to use 2to3, it works. and just change any print "...".
to. print("...")
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/boskee/Minecraft/issues/113#issuecomment-751674722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKZAPOE6YT2XCY2JJTJ3GFLSXBQWZANCNFSM4TMU26JQ
.

@ajh123  Sorry that was my bad, I don't know why I didn't notice it was already in python 3. Once I change the textures to get_texture thats the program I get. Graphics drivers are up to date, same with python and all the python libraries.

@ajh123  Sorry that was my bad, I don't know why I didn't notice it was already in python 3. Once I change the textures to get_texture thats the program I get. Graphics drivers are up to date, same with python and all the python libraries.

Don’t know what’s gone on there, my solution works for me. Maybe the texture files got corrupted?

Don’t know what’s gone on there, my solution works for me. Maybe the texture files got corrupted?

It must be fault on my end then, thanks anyway!

It must be fault on my end then, thanks anyway!

Just look through the code and replace .texture with get_texture()

Ummm, where is it?

Everywhere

same problem here


Update stable manifest with latest eventing files

files as of 2018-08-30

lgtm, but will conflict with #709


Synthesis failed for Google.Cloud.Bigtable.Admin.V2

Hello! Autosynth couldn't regenerate Google.Cloud.Bigtable.Admin.V2. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth-Google.Cloud.Bigtable.Admin.V2'
Cloning into '/tmpfs/tmp/tmp2pux5k0j/googleapis'...
Note: checking out '88316b63a486002727e14032d104690541179fc9'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 88316b63a Generated synth.py files with multiple commits enabled
Note: checking out '7be2811ad17013a5ea24cd75dfd9e399dd6e18fe'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 7be2811a fix: Update gapic-generator version to pickup discogapic fixes
Switched to a new branch 'autosynth-Google.Cloud.Bigtable.Admin.V2-2'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-03-30 07:22:52,086 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.Bigtable.Admin.V2/synth.py.
Contents of preconfig file:
{"preclonedRepos": {"https://github.com/googleapis/google-cloud-dotnet.git": "/tmpfs/src/git/autosynth/working_repo", "https://github.com/googleapis/googleapis.git": "/tmpfs/tmp/tmp2pux5k0j/googleapis"}}Extracted repo location: /tmpfs/tmp/tmp2pux5k0j/googleapis
generateapis.sh: line 40: declare: GOOGLEAPIS: readonly variable
2020-03-30 07:22:52,138 synthtool > Failed executing /bin/bash generateapis.sh --check_compatibility Google.Cloud.Bigtable.Admin.V2:

None
2020-03-30 07:22:52,140 synthtool > Wrote metadata to synth.metadata.
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.Bigtable.Admin.V2/synth.py", line 22, in <module>
    hide_output = False)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '('/bin/bash', 'generateapis.sh', '--check_compatibility', 'Google.Cloud.Bigtable.Admin.V2')' returned non-zero exit status 1.
Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 482, in <module>
    main()
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 334, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 429, in _inner_main
    branch,
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 135, in synthesize_loop
    metadata_path, extra_args, deprecated_execution, environ, synthesize_py_path,
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 278, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Get rid of Pusher

As of today, the last repository requires Pusher to be installed.
BTW, composer require pusher/pusher-php-server needs to be called else it won't build.
I don't want to use Pusher for 2 reasons:

It's not free (as in free speech) (and if you have more than 100 clients, then it's also not gratis)
I don't want them to be aware of all messages/events my server will generate.

Please reconsider using that dependency.

I totally agree, this absolutely needs to be changed if possible

I attempted to run an install as well, and the build also failed. How do I modify the file so that it would install successfully? I tried editing composer.json to add the pusher file in with an version number of "*", but it still appears not to work.

Even trying the command composer require pusher/pusher-php-server does not seem to work:
koel@pattensen:~/koel$ composer require pusher/pusher-php-server ~2.0
./composer.json has been updated
> php artisan clear-compiled
PHP Fatal error:  Class 'Pusher' not found in /home/koel/koel/vendor/laravel/framework/src/Illuminate/Broadcasting/BroadcastManager.php on line 210

  [Symfony\Component\Debug\Exception\FatalErrorException]
  Class 'Pusher' not found

Script php artisan clear-compiled handling the pre-update-cmd event returned with error code 255

Installation failed, reverting ./composer.json to its original content.
koel@pattensen:~/koel$

Alright, for the sake of documentation - apparently retrying that command at the ~/koel/vendor/laravel/framework/src/Illuminate/Broadcasting/BroadcastManager.php location worked:
koel@pattensen:~/koel/vendor/laravel/framework/src/Illuminate/Broadcasting$ composer require pusher/pusher-php-server ~2.0
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
  - Installing composer/installers (dev-master d78064c)
    Cloning d78064c68299743e0161004f2de3a0204e33b804

  - Installing pusher/pusher-php-server (2.1.2)
    Downloading: 100%

  - Installing paragonie/random_compat (v2.0.2)
    Loading from cache

  - Installing illuminate/contracts (5.3.x-dev 3ec5442)
    Cloning 3ec5442bc509730dda95e7ecd6be0a52ecef017c

  - Installing doctrine/inflector (dev-master 803a2ed)
    Cloning 803a2ed9fea02f9ca47cd45395089fe78769a392

  - Installing illuminate/support (5.3.x-dev 26ae3cd)
    Cloning 26ae3cd16e97cfb569a96448457ad2940dec6e94

paragonie/random_compat suggests installing ext-libsodium (Provides a modern crypto API that can be used to generate random bytes.)
illuminate/support suggests installing illuminate/filesystem (Required to use the composer class (5.2.*).)
illuminate/support suggests installing symfony/process (Required to use the composer class (3.1.*).)
illuminate/support suggests installing symfony/var-dumper (Required to use the dd function (3.1.*).)
Writing lock file
Generating autoload files

You need to add BROADCAST_DRIVER=log into .env and run composer install.

The problem is that the env file is never generated, since composer install exits with an error. I ended up downloading a slightly older version of koel from the releases, and now it is working fantastically.

@peterpacz1 you could always create it manually.

@X-Ryl669

As of today, the last repository requires Pusher to be installed.

Did not require it for me, see https://github.com/phanan/koel/issues/465#issuecomment-249646934.

Ah, apologies - I did not knew I could do that. Thank you for the help anyways. :)

As @bdgold stated, you need to add BROADCAST_DRIVER=log into .env if you want to build the master branch. This has NOTHING to do with Pusher, but a Laravel 5.3 instead.
@X-Ryl669 No one is forcing you to use Pusher. Except for the core functionalities, no Koel features (YouTube, Last.fm, AWS) are ever required.

I want to stress as well, that by using master, you guys are basically living on the edge and willing to accept broken features and/or lack of documentation. So do me and yourselves a favor of researching before jumping into conclusions, or worse, giving commands. OS project owners don't owe you guys anything.

@bdgold If you are using production code, and you don't use broadcasting, then BROADCAST_DRIVER=log should probably be BROADCAST_DRIVER=null to avoid cluttering the logs.
@phanan I don't see where using log driver for event broadcasting (which is a no-op as you stated) is a Laravel 5.3 requirement, the default is Pusher in Laravel 5.3. Better choice would have been the null driver if you don't intend to use the feature.
You don't owe us anything, that's true. Same as I don't owe you anything, yet, I'm contributing back each of my changes (you're rejecting or not, I don't care, I do what I consider fair).
In all cases, that does not mean we can't say when something do not please us.
Here's a live example where I expressed my opinion politely. I did not "give command".
I did research and figure out how to solve the missing Pusher dependency, and without any other information.
I reported the issue, and said what I did to solve it. I did not know if you were aware of it, and I supposed you did not.
If you don't like being told that something's broken, great, I'll stop reporting.
If you don't like to know what your user like/don't like, great, I'll stop reporting too.
Very positive attitude...

Not to continue this very non-constructive debate, but if "Get rid of Pusher" doesn't sound like a demand, I don't know what does.
Now to the root of the issue, yes, I very much intend to use broadcast in the future.


ARROW-10407: [C++] Add BasicDecimal256 Division Support

Benchmark result after adding BasicDecimal256 Division support:
BinaryMathOp128                152 ns          152 ns      4284240 items_per_second=65.6334M/s
BinaryMathOp256                163 ns          163 ns      4186744 items_per_second=61.4706M/s
Benchmark result before adding BasicDecimal256 Division support:
BinaryMathOp128                154 ns          154 ns      4197814 items_per_second=65.0004M/s
BinaryMathOp256               34.5 ns         34.5 ns     20253709 items_per_second=290.14M/s

@Bei-z please ping me  once you've address @MingyuZhong's comments and I can do a final review/merge.

I didn't find any performance regression on an AMD Zen 2 CPU.

Thanks for the updates. Can you look at the errors on CI and fix them? Thanks!

Thanks for the updates. Can you look at the errors on CI and fix them? Thanks!

Thank you for reviewing! The errors on CI are fixed now.

Codecov Report

Merging #8542 (1df4d0c) into master (cf61fa1) will increase coverage by 0.30%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8542      +/-   ##
==========================================
+ Coverage   84.24%   84.54%   +0.30%
==========================================
  Files         152      177      +25
  Lines       42175    43647    +1472
==========================================
+ Hits        35529    36902    +1373
- Misses       6646     6745      +99

Impacted Files
Coverage Δ

rust/parquet/src/arrow/converter.rs
62.96% <0.00%> (-28.15%)
:arrow_down:

rust/parquet/src/util/io.rs
90.75% <0.00%> (-6.55%)
:arrow_down:

rust/parquet/src/arrow/array_reader.rs
76.88% <0.00%> (-5.59%)
:arrow_down:

rust/parquet/src/util/cursor.rs
84.78% <0.00%> (-4.97%)
:arrow_down:

rust/parquet/src/util/test_common/rand_gen.rs
80.00% <0.00%> (-4.22%)
:arrow_down:

rust/datafusion/src/physical_plan/group_scalar.rs
69.23% <0.00%> (-3.85%)
:arrow_down:

rust/arrow/src/util/integration_util.rs
67.48% <0.00%> (-2.55%)
:arrow_down:

rust/arrow/src/ipc/reader.rs
81.81% <0.00%> (-2.42%)
:arrow_down:

rust/arrow/src/util/buffered_iterator.rs
92.85% <0.00%> (-2.39%)
:arrow_down:

rust/datafusion/src/optimizer/filter_push_down.rs
95.95% <0.00%> (-2.28%)
:arrow_down:

... and 129 more

Continue to review full report at Codecov.

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

Hmm, I borked this PR while trying to merge changes. Let me open a new one :-S

New PR at #8696. I tried to conserve authorship.