Adding integration tests for search backpressure

Description
This commit adds integrations tests to tests that SearchBackpressureService is correctly cancelling the tasks.
Issues Resolved
#1181
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.
Signed-off-by: PritLadani<EMAIL_ADDRESS>

Codecov Report

Merging #5308 (7c34657) into main (a0f022b) will increase coverage by 0.09%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #5308      +/-   ##
============================================
+ Coverage     70.98%   71.08%   +0.09%
- Complexity    58121    58138      +17
============================================
  Files          4704     4704
  Lines        277312   277312
  Branches      40149    40149
============================================
+ Hits         196854   197126     +272
+ Misses        64356    64016     -340
- Partials      16102    16170      +68

Impacted Files
Coverage Δ

...ava/org/opensearch/action/NoSuchNodeException.java
0.00% <0.00%> (-50.00%)
:arrow_down:

...h/action/ingest/SimulateDocumentVerboseResult.java
60.71% <0.00%> (-39.29%)
:arrow_down:

...n/admin/indices/readonly/AddIndexBlockRequest.java
35.71% <0.00%> (-35.72%)
:arrow_down:

...ion/admin/cluster/node/info/PluginsAndModules.java
53.12% <0.00%> (-34.38%)
:arrow_down:

...r/src/main/java/org/opensearch/http/HttpUtils.java
33.33% <0.00%> (-33.34%)
:arrow_down:

.../java/org/opensearch/index/reindex/RemoteInfo.java
51.37% <0.00%> (-28.45%)
:arrow_down:

.../admin/indices/readonly/AddIndexBlockResponse.java
15.38% <0.00%> (-22.12%)
:arrow_down:

...n/decider/SnapshotInProgressAllocationDecider.java
34.78% <0.00%> (-21.74%)
:arrow_down:

...ter/coordination/CoordinationStateTestCluster.java
73.78% <0.00%> (-21.35%)
:arrow_down:

...earch/suggest/completion/CompletionSuggestion.java
66.66% <0.00%> (-20.71%)
:arrow_down:

... and 505 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Game submission: Mallard

Thanks for organizing all of this and being a welcoming community! I'm excited to learn more and do more moving forward!

Thank you for your submission!

Merged to main into the unified ROM.


bonus-unit1: using gdown of version 4.5.4 to download from google drive instead of wget

The file cannot be downloaded from google drive using wget like this:
!wget --load-cookies /tmp/cookies.txt \"https://docs.google.com/uc?export=download&confirm=$(wget --quiet --save-cookies /tmp/cookies.txt --keep-session-cookies --no-check-certificate 'https://docs.google.com/uc?export=download&id=1zv3M95ZJTWHUVOWT6ckq_cm98nft8gdF' -O- | sed -rn 's/.*confirm=([0-9A-Za-z_]+).*/\\1\\n/p')&id=1zv3M95ZJTWHUVOWT6ckq_cm98nft8gdF\" -O ./trained-envs-executables/linux/Huggy.zip && rm -rf /tmp/cookies.txt

using gdown==4.5.4 instead is working

Works for me, thanks! The old wget method didn't work anymore.

Hey there 👋 thanks for pointing this out, we just updated with #474 #473 by moving the demos to GitHub instead of Google Drive 🤗


Issue with response descriptor matching

I'm making a request to this url
https://myserver.com/api/users/53a8d8d7e4b06b32f108c4f3/settings
and sometimes this request succeeds, and sometimes it fails. When it fails, the error code from RestKit is RKMappingErrorNotFound. I get a helpful debug log from Restkit:
14:49:37 2015-01-30 14:49:38.243 MyProject[65072:60b] Error fetchng user settings: Error Domain=org.restkit.RestKit.ErrorDomain Code=1001 "No response descriptors match the response loaded." UserInfo=0x84c80760 {NSErrorFailingURLStringKey=https://myserver.com/api/users/53a8d8d7e4b06b32f108c4f3/settings, NSLocalizedFailureReason=A 200 response was loaded from the URL 'https://myserver.com/api/users/53a8d8d7e4b06b32f108c4f3/settings', which failed to match all (26) response descriptors:
...
It then prints out the response descriptors, which:
<RKResponseDescriptor: 0x83a76af0 baseURL=https://myserver.com pathPattern=/api/users/:uniqueId/settings statusCodes=200-299> failed to match: response path '/api/users/53a8d8d7e4b06b32f108c4f3/settings' did not match the path pattern '/api/users/:uniqueId/settings'.
This error message does not make sense to me, since it seems that it DID match. I looked into the source for how RKMappingErrorNotFound could be generated, and it seems like it only matches on the keypaths, which look correct to me.
Can anyone shed some light?

GitHub Issues is for reporting bugs in RestKit and discussing changes to RestKit itself. Please check the documentation, wiki, and existing issues before opening a new issue.
Additionally, please do not post general usage questions to Issues, but instead take them to Stack Overflow.


App Hanging: App hanging for at least 2000 ms. Happens for iOS devices only.

Environment
System:
  OS: macOS 14.1
  CPU: (12) arm64 Apple M3 Pro
  Memory: 70.22 MB / 18.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 21.2.0
    path: /opt/homebrew/bin/node
  Yarn:
    version: 1.22.21
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.2.3
    path: /opt/homebrew/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.14.3
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.0
      - iOS 17.0
      - macOS 14.0
      - tvOS 17.0
      - watchOS 10.0
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.11090377
  Xcode:
    version: 15.0.1/15A507
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.21
    path: /usr/bin/javac
  Ruby:
    version: 3.2.2
    path: /opt/homebrew/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.6
    wanted: 0.72.6
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Platforms
iOS only
Versions

Android: -
iOS: 16 and above
@react-native-clipboard/clipboard: 1.12.1
react-native: 0.72.6
react: 18.2.0

Description
Since I've updated this package from 1.11.1 to 1.12.1 (together with a react native update from 0.71.2 to 0.72.6) I have been getting App Hanging: App hanging for at least 2000 ms error from Sentry, see https://docs.sentry.io/platforms/react-native/configuration/app-hangs/.
Reproducible Demo
Through the breadcrumbs in Sentry I have pinned this down to this package, this seems to happen when I navigate to another app (background event) and then focus again on my app (foreground event) with an updated clipboard.

I have the same issue with v1.12.1 and RN 0.72.7. I will try to revert it and send the result here.

This seems to be an issue w/ false reporting by sentry when the user is prompted for permissions.  See https://github.com/getsentry/sentry-cocoa/discussions/2715#discussioncomment-6603068


Error opening file  beguining with "["

Sample [Author] - Serie #Numer - Title (Tag, Tag, Tag) (English)
Fails when execute comictagger .exe "[Author] - Serie #Number - Title (Tag, Tag, Tag) (English)"
Works in file without "[": "Author - Serie #Number - Title (Tag, Tag, Tag) (English)"
Works too: "(Author) - Serie #Number - Title (Tag, Tag, Tag) (English)"

Didn't know this before but ComicTagger does it's own globbing on files passed through on the command line specifically for windows, so that [0].zip becomes 0.zip this however only happens when it is an argument so as a workaround you can either open it in the gui or open the folder the file is in

There is now an explicit option to enable globing -g, --glob so by default these filenames will now work,
added in #306


A number of refactorings failing

I'm getting these when working on the DasBlog source code. I'm in SharedBasePage.cs. It's lousy code, but it's still interesting I'm getting errors.

I take you were testing https://github.com/shanselman/dasblog - we'll take a look.

At least some issues seen with DasBlog solution have been addressed in 73b7f1fd387b4f03fc74d48ec01d671663d4cca5.

The error messages seen in screenshot will be fixed as soon as VS 2015 RTM is out.

I'll check that as well - next week I've some time working on RE. This week I was too busy :/


Add audio and video transcoding

Add media transcoding using the Brightcove Zencoder service.
To test this, you need a Zencoder API key, which requires a free signup. You can use your account's "integration" key to ensure that only test (non-billable) transcodings are performed.  Check settings.local for new fields that have been added.
Known potential issues:

I'm not sure if the view helpers for the audio and video tags are ideal, because you have to specify raw when you call them from views, because they return strings of HTML.  But not that this has to hold things up right now.
This is tied in to Zencoder.  The file upload in an earlier commit was also tied in to Amazon S3.  At least the meta fields and the generically-labeled transcoding_job fields of the audios and videos tables might make it not too hard to migrate if we ever have to.

More known issues:
I added a number of methods to ApplicationController that I realize now should be Concerns in the concerns directory. It would be best if that could be done as a later refactor.  Related to that, there would be tests to change.
There is a test I've labeled FIXME, which needs to be moved to a spec for ZencoderAuthentication concern, but I'm not sure how to go about that at the moment.
I think it would be safe to take care of the shortcomings above with one or more post-launch tickets, to stay on schedule.

I think this is ready to :squash:, rebase, and :merge:

OK, I'll do that, if you're sure you don't want to merge https://github.com/dpla/primary-source-sets/pull/29 first.


P.S.A. Publishing Pipelines are down

Public Service Announcement
Publishing pipelines are down. We're working to mitigate the issue.
We will test the fix and perform a rebuild.

Pipelines should be up again.


anyone using redux-form with react-toolbox?

I can get the input component of react-toolbox to work but the date-picker and time-component I cannot.

update: if i pass down error = {error} into the Field component I see the errors but only after  i have clicked submit on a valid email addres

I'm trying right now to get working redux-form and react-toolbox and this is being time consuming bring all together.. :(
Seems that the new api to fields is a pain for using with a library of components like React Toolbox. Can anyone help out ?

I was able to successfully combine the two. I created a transition component for each input type. I was already wrapping the react-toolbox components for custom styling consistency.
import React from 'react';
import { MyTextInput } from './';

// Designed for use with redux-form
const FormInput = ({ input, meta: { touched, error }, ...custom }) => (
  <MyTextInput
    error={touched && error ? error : ''}
    {...input}
    {...custom}
  />
);

export default FormInput;

I also initialized my dropdown options from the redux store and set initial values for my form.
To use FormInput:
import { connect } from 'react-redux';
import { Field, reduxForm } from 'redux-form';

const MyForm = ({ customDropdownOptions }) => (
  <form>
    <Field
       component={FormInput}
       name="myName"
       label="myLabel"
       // if component is a dropdown component
       source={customDropdownOptions}
    />
  </form>
)

function mapStateToProps(state) {
  const { myPage } = state.foo.bar;
  return {
    customDropdownOptions: myPage.myCustomDropdownOptions,
    // initialValues is an optional prop used by redux-form
    // You don't have to manually set the form field default values yourself if you do this
    initialValues: myPage.myInitialFormValueObject
  };
}

const form = reduxForm({ form: 'myForm' });

export default connect(mapStateToProps)(form(MyForm));

state.foo.bar would be the standard redux path for pulling out the piece you want from the store.
I love how using redux-form eliminates the need for creating my own actions and reducers for input fields. Wonderful job!

DatePicker works for me. I had to remove onBlur prop tho, it was causing pointless dispatches when selecting a date on calendar.
export const renderDatePicker = ({ input: { onBlur, ...inputForm }, label, ...custom }) => (
  <DatePicker
    label={label}
    {...inputForm}
    {...custom}
  />
);

<Field type="text" name="startDate" label="Start date" component={renderDatePicker} />

In fact, it works, as I'm using it (not very advanced usages so far), and folks provided some good examples here!


No module named pyquaternion

When I try to run "python px4_mavros_run.py",there is a error named "No module named ptquaternion".

Run "sudo pip2 install pyquaternion" can solve the problem.

@MasterPa I think this issue is resolved. Can we close it?

@wzz644534561 Thank you for sharing your problem and the solution with us all! As you have provided the solution, we will close it for now. But the record will remain on GitHub for other people to refer to.


How can I run my own dataset with this network

How can I run my own dataset with this network

Have you solved this problem

any progress?


autoBackupSettings not found on Microsoft.SqlVirtualMachine/sqlVirtualMachines

Package Name: @azure/arm-sqlvirtualmachine
Package Version<EMAIL_ADDRESS>Operating system: linux
[x] nodejs

version: v12.16.1

[ ] browser

name/version:

[x] typescript

version: Version 4.0.2

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[X] SDK API docs on https://docs.microsoft.com

Describe the bug
A clear and concise description of what the bug is.
SQLVirtualMachine.autoBackupSettings is not present. I provisioned a test Azure SQL server on VMs and can see my SQL VM using await sqlVMClient.sqlVirtualMachines.listByResourceGroup(resourceGroupName).
I configured the VM's auto backup like this:

I'm unable to see this info from the API results.
To Reproduce
Steps to reproduce the behavior:

Provision a new Azure SQL server for Virtual Machines
Set the the client
Get a list of VMs (using listByResourceGroup)
See that autoBackupSettings is not a property on the returned results:

{
  "id": "/subscriptions/<REDACTED>/resourceGroups/<REDACTED>_group/providers/Microsoft.SqlVirtualMachine/sqlVirtualMachines/<REDACTED>",
  "location": "westus",
  "name": "<REDACTED>",
  "provisioningState": "Succeeded",
  "sqlImageOffer": "SQL2019-WS2019",
  "sqlImageSku": "Developer",
  "sqlManagement": "Full",
  "sqlServerLicenseType": "PAYG",
  "type": "Microsoft.SqlVirtualMachine/sqlVirtualMachines",
  "virtualMachineResourceId": "/subscriptions/<REDACTED>/resourceGroups/<REDACTED>_group/providers/Microsoft.Compute/virtualMachines/<REDACTED>"
}

Expected behavior
A clear and concise description of what you expected to happen.
vm.autoBackupSettings.retentionPeriod should show 20 days.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

I can also repro this in Azure CLi. looks like the service backend list result has missed the autoBackupSettings. add service-attention label.

Get SQL VM List by Resource Group call returns the list of SQL VM in the resource group.
To get the properties of individual SQL VM, Please use Get SQL Vm call

With Expand call : will return the autoBackupSettings, GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.SqlVirtualMachine/sqlVirtualMachines/{sqlVirtualMachineName}?$expand=autoBackupSettings&api-version=2017-03-01-preview,

@qiaozha I understand that json lists the entire properties of the SQL VM https://github.com/Azure/azure-rest-api-specs/blob/master/specification/sqlvirtualmachine/resource-manager/Microsoft.SqlVirtualMachine/preview/2017-03-01-preview/sqlvm.json#L1456. However the List operation do not include the Properties to get that we need to make another call for that specific VM.

@qiaozha  Autobackup settings is pulled in via expand as it is extension level property. Since, it is not stored in Metadatastore it is costly to expose such properties on GET calls. ListByResourceGroup falls in similar territory where we only want to return properties stored in Metadatstore vs making a call to Compute extensions.

@qiaozha  Autobackup settings is pulled in via expand as it is extension level property. Since, it is not stored in Metadatastore it is costly to expose such properties on GET calls. ListByResourceGroup falls in similar territory where we only want to return properties stored in Metadatstore vs making a call to Compute extensions.

@hdavidzhu Does the solution of get the autobackup settings via GET calls work for you?

@hdavidzhu Does the solution of get the autobackup settings via GET calls work for you?

It's not ideal, b/c we perform regular scans on this endpoint. So individual API calls would also be expensive on our end. For now, the feature I'm building is ignoring this field, and we likely won't pull it in if its expensive.
At a minimum, I'd love it if the documentation calls this out, as it's not clear by this or in the generated types that this property won't show up on listByResourceGroup!
Alternatively:

Autobackup settings is pulled in via expand as it is extension level property. Since, it is not stored in Metadatastore it is costly to expose such properties on GET calls. ListByResourceGroup falls in similar territory where we only want to return properties stored in Metadatstore vs making a call to Compute extensions.

It would be cool if this info is cached onto the Metadatastore so that we can read it via listByResourceGroup and other list commands.
Thanks folks for taking a look 🙌

It's not ideal, b/c we perform regular scans on this endpoint. So individual API calls would also be expensive on our end. For now, the feature I'm building is ignoring this field, and we likely won't pull it in if its expensive.
At a minimum, I'd love it if the documentation calls this out, as it's not clear by this or in the generated types that this property won't show up on listByResourceGroup!
Alternatively:

Autobackup settings is pulled in via expand as it is extension level property. Since, it is not stored in Metadatastore it is costly to expose such properties on GET calls. ListByResourceGroup falls in similar territory where we only want to return properties stored in Metadatstore vs making a call to Compute extensions.

It would be cool if this info is cached onto the Metadatastore so that we can read it via listByResourceGroup and other list commands.
Thanks folks for taking a look 🙌

We understand your concern, we would definitely update the document

We understand your concern, we would definitely update the document

@qiaozha we have created the repair item to update the document. We would triage and prioritize to amend the document.

@qiaozha we have created the repair item to update the document. We would triage and prioritize to amend the document.

@qiaozha if we are agreed upon the action item around documentation, I would recommend to close the issue.

@qiaozha Are we OK to close this now? @NivedhaChellam has created a repair item for us to update the document.

@bluefooted added need author feedback label. which will automatically close this issue if the issue author doesn't have any objections in 7 days.

Just so I understand, this will be in-the-works? Looking at the docs just now, I don't see it updated.
Thanks!

@hdavidzhu Yes we have filed an internal tracking item to get the documentation updated.


Trytond integration

Sentry SDK integration for the Trytond ERP framework

Waiting for Tryton community feedback https://discuss.tryton.org/t/sentry-sdk-integration/1925

Regarding the failed checks:

the Python-3.5 fail is due to a str vs bytes issue
the Python-3.4 fail is due to the trytond>5.0 package not being distributed for that version
the Python-2.7 and the PyPy failures are rather unexpected because AFAIU they were out of the contributed dependency matrix

If the community agrees, I would settle for the easy solution: only supporting python>=3.6

@n1ngu it's ok to remove py3.4-trytond-5.0 from the matrix by having multiple lines (see django)

I still can't understand why the trytond submodule tests are being run with the Python-2.7 and PyPy interpreters. What am I missing?

@n1ngu have a look at tests/integrations/*/__init__.py :)

I'd like to invoke @pokoli the maintainer of a former trytond raven integration

@n1ngu do you have any documentation on how this can be run on trytond? Which are the current steps to run the integration? I will like to test it but I do not now how to configure it.

@n1ngu do you have any documentation on how this can be run on trytond? Which are the current steps to run the integration? I will like to test it but I do not now how to configure it.

Cleaning the repo before making the PR I removed my test script :cry: but it should be as easy as the wsgi script stub depicted here https://discuss.tryton.org/t/sentry-sdk-integration/1925 and loading it with your favorite wsgi server. As discussed in that very thread, that server can't be the trytond binary since the wsgi module can't be chosen.
Soon enough, I'll also share a logging configuration to test the hacky "not TrytondCronIntegration" present here as a logging handler.

So as to wrap it here, while the documentation of this integration is not written, a wsgi.py script is needed to test it:
# mywsgi.py
import sentry_sdk
import sentry_sdk.integrations.trytond

sentry_sdk.init(
<EMAIL_ADDRESS>    integrations=[sentry_sdk.integrations.trytond.TrytondWSGIIntegration()]
)

from trytond.application import app as application

# WATCH-IT! trytond>=5.4 only:
from trytond.exceptions import TrytonException
from trytond.exceptions import UserError

@application.error_handler
def _(app, request, e):
    if isinstance(e, TrytonException):
        return
    else:
        event_id = sentry_sdk.last_event_id()
        data = UserError('Custom Message', f'{event_id}\n{e}')
        return app.make_response(request, data)

Then run it with $ gunicorn mywsgi or your favorite wsgi server.
@cedk stated that a built-in trytond mechanism to use arbitrary wsgi middleware is on the way. Soon enough it will be interesting to wrap this integration in a dummy middleware and ship it (also with adequate documentation) so that it can be used in the most trytonic way without a wsgi script.

In my eyes there should be no reason to call init() from an integration. This is something we want to enforce for all stable integrations as doing otherwise requires us to replicate the API of init() somewhere else. If people use your logging handler to initialize the SDK, how do they configure before_send or any other option that takes more complex arguments than a DSN?

In my eyes there should be no reason to call init() from an integration. This is something we want to enforce for all stable integrations as doing otherwise requires us to replicate the API of init() somewhere else. If people use your logging handler to initialize the SDK, how do they configure before_send or any other option that takes more complex arguments than a DSN?

That's a good point. This handler should be understood not as a framework integration but as a mean to inject code in tools that won't allow it. Obviously, if the default sdk initialization does not suffice for a particular purpose, neither will this handler. If this is a concern and such a feature was not acceptable for the core sdk I will retire it from this PR so we can focus on the actual trytond wsgi integration above! (but I'll still vendor it in my deployments :grin:)
Regarding complex init() options: The "ignored_loggers" feature is already beyond my initial will, it is present because I felt it was extremely straightforward. With a similar schema, other init() options could be exposed, but obviously its complexity grows as with a need for a fair amount of documentation.
That's why I'd settle for the "use this only if the default init() suffices you" as an out-of-the-box mechanism to power people to use Sentry with not easily-hackable tools, even if the Sentry setup is not fully customizable.

@untitaker Stated with different words: this handler could be shipped alongside the EventHandler and BreadcrumbHandler in the sentry_sdk.integrations.logging module. Not to power full Sentry customization but to ease a naive Sentry initialization in honor to your own documentation:

Usually, you don’t need this. You can use this together with default_integrations=False if you want to opt into what the Sentry Python SDK captures. However, correctly setting up logging is difficult. Also, an opt-in approach to capturing data will miss errors you may not think of on your own.
( https://docs.sentry.io/platforms/python/logging/#handler-classes )
The alternative for this kind of not easily-hackable tools is a tedious logging config setup with the EventHandler, and still with the problem of "where to state the DSN"

@n1ngu I would much rather separate the discussion of alternative initialization methods from getting this integration merged. The former is more controversial imo

@n1ngu could you open a pr against https://github.com/getsentry/sentry-docs?

Example PR: https://github.com/getsentry/sentry-docs/pull/867

I think it would be fine to omit the request data as well if you think it
cannot be useful in the context of trytond. I do not know what Tryton does
On Wed, Nov 27, 2019, 11:21 Ningú<EMAIL_ADDRESS>wrote:

@n1ngu commented on this pull request.
In sentry_sdk/integrations/trytond.py
https://github.com/getsentry/sentry-python/pull/548#discussion_r351203929
:

@@ -0,0 +1,35 @@
+import sentry_sdk
+import sentry_sdk.integrations

+from trytond.exceptions import TrytonException  # type: ignore
+from trytond.wsgi import app  # type: ignore
+
+
+# TODO: trytond-worker, trytond-cron and trytond-admin intergations
+
+
+class TrytondWSGIIntegration(sentry_sdk.integrations.Integration):
I'll check it out and I'll also assert that passwords do not get leaked.
But this also raises a concern about leaking bearer authorization headers,
the default auth mechanism for Tryton APIs. Can we set the integration to
skip those by default?
Also, Tryton has a pluggable auth system so you can easily tweak the
login. It can be used for 2FA with temporary secrets, but the default
password login can be completely overridden by other systems that could
request secrets in arbitrary keys (am I wrong, @cedk
https://github.com/cedk ?). I'd vote for completely masking
request/response bodies for the Tryton login endpoint. Is that feasible?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/getsentry/sentry-python/pull/548?email_source=notifications&email_token=AAGMPRPRK64XVMSLLVY3YHTQVZCZVA5CNFSM4JKV4VSKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCNETNFQ#discussion_r351203929,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGMPRP2AMIUM2DPNATAYEDQVZCZVANCNFSM4JKV4VSA
.

I tried to push this but failed bc the PR is not editable for me:
diff --git a/sentry_sdk/integrations/trytond.py b/sentry_sdk/integrations/trytond.py
index 152e879..c1a669a 100644
--- a/sentry_sdk/integrations/trytond.py
+++ b/sentry_sdk/integrations/trytond.py
@@ -4,10 +4,14 @@ import sentry_sdk.hub
 import sentry_sdk.utils
 import sentry_sdk.integrations
 import sentry_sdk.integrations.wsgi
+from sentry_sdk._types import MYPY

 from trytond.exceptions import TrytonException  # type: ignore
 from trytond.wsgi import app  # type: ignore

+if MYPY:
+    from typing import Any
+

 # TODO: trytond-worker, trytond-cron and trytond-admin intergations

@@ -25,12 +29,19 @@ class TrytondWSGIIntegration(sentry_sdk.integrations.Integration):

         def error_handler(e):  # type: (Exception) -> None
             hub = sentry_sdk.hub.Hub.current
+
             if hub.get_integration(TrytondWSGIIntegration) is None:
                 return
             elif isinstance(e, TrytonException):
                 return
             else:
-                (event, hint) = sentry_sdk.utils.event_from_exception(sys.exc_info())
+                # If an integration is there, a client has to be there.
+                client = hub.client  # type: Any
+                event, hint = sentry_sdk.utils.event_from_exception(
+                    sys.exc_info(),
+                    client_options=client.options,
+                    mechanism={"type": "trytond", "handled": False},
+                )
                 hub.capture_event(event, hint=hint)

         # Expected error handlers signature was changed

could you apply it manually?

fwiw this is blocked on the doc changes

My bad. I am aware the ball is in my court. I can only spend here some spare work hours, plus I've been on vacation. But hopefully I'll have the documentation sorted in the short term!

Gonna get this out and document later


Can't seem to get one of two Win 10 machines to work

Hey Bob, as if you don't have enough on your plate I can get one of two machines to operate, the one that won't obey is at <IP_ADDRESS> with a mac of 50:eb:f6:56:fb:87. Here is the complete string with the log attached:
BTW nice work on Russound!!
Security-Bill-2 = 50:eb:f6:56:fb:87/<IP_ADDRESS> value = 1
Wake-On-Lan_10-11-2023_55305_PM.zip

The log shows an error trying to parse one of the configuration parameters.


gvt restore issue in hmake build (rebuilds entire dep on change in vendor/manifest)

either sort this in gvt restore or shift to go dep.
ref: https://gitter.im/truechain-net/engg-foss-global?at=5b45b9413d8f71623d6e9357

Fixed manully but reorg the manifest.
https://github.com/truechain/truechain-consensus-core/pull/63

@hixichen this issue is about "rebuilding entire deps structure" if just a couple changes are seen in vendor manifest. It's about not building the entire dep chain. I don't think it should be closed?
gvt restore still functions the same way, doesn't it ?

Not sure I fully understand your question.
For dep management, you only need to restore them for the first time when you git clone the project.
It is developer's job to maintain the manifest file.
why do we need to rebuild the entire deps structure?

@hixichen here's the thing - we do it first time. Then we git pull in some changes after some time. So the vendor manifest changes.
So the next time we build with hmake, it rebuilds deps, because it watches over manifest. This build, triggers gvt restore.


Finish Introduction tour

This PR adds the missing contents of the Introduction tour.
I decided to create it given that this was @goanpeca's work, so I'd like to know his thoughts about my additions.

Hey @ccordoba12 thanks for working on this. It looks fine on a quick look, but there is an issue that needs to be solved, maybe the ipython console is not intalled, so we need to include this in the logic of the tours.py

What should be the default behavior when a widget is not there?
skip it? make it non-selectable? make it like grayed out in the combobox?
Depending on this I can make a PR to correct this, and also include the suggestion of @Nodd of using a dummy dockwidget instead of making it transparent to events (the temporal fix used right now...)

It would be bad to skip it completely since the tour is there to show all features of spyder to new users.
Maybe add a warning that the corresponding widget it not active ?

The only plugin that can be missing right now is the IPython console (which is loaded on demand). All other plugins (even the Pylint one) load fine.
But @Nodd has a good point: if the IPython Console is missing, the tour should show a warning and guide the user on how to install it.

There is also the case where a panel is not enabled. Is this manager ? (if I remember well, @goanpeca told me it was working, but it was a long time ago)

If the panel is not enabled, it should be a problem... as far as I remember (it will be enabled and brought to the front)
Sure, we can then display a replacement content indicating how to install ipython.

intro I want to make clear that the purpose of this PR is only to add missing contents to the tutorial.
I'm not going to touch the other issues mentioned by @goanpeca and @Nodd to keep things simple :-)

@goanpeca, this is ready for a review. I added reasonable contents to all the Intro tour slides.

Cool, will test it later on :-)

@goanpeca, I think this is ready for merge too ;-)

Go for it!

Oki doki! ;-)


astro-compress is gone from NPM registry

Like the title suggest. It is gone from the NPM registry.
https://www.npmjs.com/package/astro-compress

#162

How long will it take? My website is down now... because my pipeline can't do a rebuild.

same problem here.

same problem for me as well :(

Guess this is the life with open source. I suggest you :

temporarily remove the package from your project (I did it this evening.)
Use another similar package for now.

same here

@itaispector
https://www.npmjs.com/package/@otterlord/astro-compress

@itaispector https://www.npmjs.com/package/@otterlord/astro-compress

thanks buddy 🙏

@NikolaRHristov can you take a look at this please?

Ok, I have regained access to the astro-compress, critters, rome and files-pipe packages. These will be republished.

After I have republished I will transfer over the packages to @FredKSchott, if that's okay.

@NikolaRHristov Why is version 2.0.0 empty in NPM? Can you please fix it?

Build seems to fail when using v2.0.0.
 error   Failed to resolve entry for package "astro-compress". The package may have incorrect main/module/exports specified in its package.json.
  File:
    /Users/path/to/astro.config.mjs

I'm receiving the same error as @jmblog

Can you please release 1.1.50?

Hello, @zoxon, version 2.0 is empty as to not get malwared. @jmblog, @benstegink just use @otterlord/astro-compress in the meantime while this gets fixed. @Igloczek, no because it uses files-pipe which is currently missing. These will all be resolved by the end of the day. NPM does not allow republishing of packages over 24 hours so I have to wait and their support haven't answered me still. This is why I'm republishing empty packages as to them not getting malwared and everything will be fixed. I have the source code offline.

+1

What happened to astro-compress and atstro-critters?

+1

The author closed their NPM account; they'll make a new one shortly #162

why?

@aetherclouds Bro wok up in the morning and choose violence. 😂

@aetherclouds Bro wok up in the morning and choose violence. 😂

just genuinely curious, sorry if it came off the wrong way!

Hi, I'm exiting Open-Source, if that's a thing, and just did it the wrong way. I thought it would archive the packages leaving everything intact. Now two more days days of pressure 😅.
Progress so far:

The build scripts have been recreated - https://npmjs.org/baxast
The files-pipe component is also up - https://npmjs.org/files-pipe

I should get astro-compress, astro-critters and astro-rome up in a few hours, as well. Just testing a few more things and making sure everything is working correctly.

@aetherclouds Bro wok up in the morning and choose violence. 😂

just genuinely curious, sorry if it came off the wrong way!

Hi, I'm exiting Open-Source, if that's a thing, and just did it the wrong way. I thought it would archive the packages leaving everything intact. Now two more days days of pressure 😅.
Progress so far:

The build scripts have been recreated - https://npmjs.org/baxast
The files-pipe component is also up - https://npmjs.org/files-pipe

I should get astro-compress, astro-critters and astro-rome up in a few hours, as well. Just testing a few more things and making sure everything is working correctly.

don't down on yourself I'm sure nobody would predict something like that happening right upon deleting their account :)
good luck on your new ventures and thanks for the neat libraries!

😅 Thank you! @aetherclouds

@NikolaRHristov so if I understand it correctly, you removed your NPM account before transfer that packages to @FredKSchott but what about this you said  "Hello, @zoxon, version 2.0 is empty as to not get malwared". Before the packages had malware?

I setup a script to automatically re-publish those packages. The packages were empty because some things were not working correctly and I just didn't want to publish broken packages, so just empty ones seemed a better alternative.
You can still see the source online there is no malware there.
Also, I publish all of my packages with Provenance, which means that they are verified by a commit and published from GitHub. You can still see the little box at the bottom https://www.npmjs.com/package/files-pipe

This is how astro-compress, astro-critters and astro-rome were and will also be published in the future, as well.

I setup a script to automatically re-publish those packages. The packages were empty because some things were not working correctly and I didn't want to publish broken packages, so just empty ones seemed a better alternative.
You can still see the source online. There is no malware there.
Also, I publish all of my packages with Provenance, which means that they are verified by a commit and published from GitHub. You can still see the little box at the bottom https://www.npmjs.com/package/files-pipe
This is how astro-compress, astro-critters and astro-rome were and will also be published in the future, as well.

Okay I understand, you republished the package to prevent some get the package name and distribute malware. And not that your package had malware.

Okay I understand, you republished the package to prevent some get the package name and distribute malware. And not that your package had malware.

Yes, correct, as a per-emptive measure.

@aetherclouds Bro wok up in the morning and choose violence. 😂

just genuinely curious, sorry if it came off the wrong way!

Hi, I'm exiting Open-Source, if that's a thing, and just did it the wrong way. I thought it would archive the packages leaving everything intact. Now two more days days of pressure 😅.
Progress so far:

The build scripts have been recreated - https://npmjs.org/baxast

The files-pipe component is also up - https://npmjs.org/files-pipe

I should get astro-compress, astro-critters and astro-rome up in a few hours, as well. Just testing a few more things and making sure everything is working correctly.

you deserve an award, honestly

@aetherclouds Bro wok up in the morning and choose violence. 😂

just genuinely curious, sorry if it came off the wrong way!

Hi, I'm exiting Open-Source, if that's a thing, and just did it the wrong way. I thought it would archive the packages leaving everything intact. Now two more days days of pressure 😅.
Progress so far:

The build scripts have been recreated - https://npmjs.org/baxast
The files-pipe component is also up - https://npmjs.org/files-pipe

I should get astro-compress, astro-critters and astro-rome up in a few hours, as well. Just testing a few more things and making sure everything is working correctly.

you deserve an award, honestly

That would be @TheOtterlord, he pulled up and created a backup, archive and published everything almost the next day, so that nothing is lost and transitions can be made.

Thanks for the healthy reminder to always check the issues page haha
Tried to remove the compress package out of fear of malware and our CI bundle went from 26mb to 156mb 🤣

astro-compress v2.0.1 has been restored with Provenance
This repository https://github.com/baxast/astro-compress will soon be synchronized with the official astro-community one https://github.com/astro-community/astro-compress.
You can submit issues in either.
astro-critters and astro-rome coming up next.

Thanks for the hustle! Well done 👍

Pog

astro-critters up too - https://github.com/astro-community/astro-critters/issues/137 v2.0.2

I tried v2.0.2, but the exclude option appears to be ignored. I recall that it worked in the previous version.
import compress from "astro-compress";

export default {
    integrations: [
        compress({
            exclude: [
                'dist/images/articles/*',
                'dist/images/banners/*',
                'dist/images/experts/*',
                'dist/images/top_banners/*',
            ],
        }),
    ],
};

I tried v2.0.2, but the exclude option appears to be ignored. I recall that it worked in the previous version.
import compress from "astro-compress";

export default {
    integrations: [
        compress({
            exclude: [
                'dist/images/articles/*',
                'dist/images/banners/*',
                'dist/images/experts/*',
                'dist/images/top_banners/*',
            ],
        }),
    ],
};

Try Exclude

@NikolaRHristov hey, I add astro-compress v2.0.2 to my app and got such errors:

The package "stream" wasn't found on the file system but is built into node.
The package "stream" wasn't found on the file system but is built into node.
'etc...'  into node.

If I remove  astro-compress v2.0.2  and add @otterlord/astro-compress everything is fine in local but the issue is nothing appears on the app (white blank page after Cloudflare deployment)

stream

Hi, does this happen with the latest version v2.0.5?

Hi, does this happen with the latest version v2.0.5?

I update it to the latest version and yes the issue still there

Hi, does this happen with the latest version v2.0.5?

I update it to the latest version and yes the issue still there

Could you please share your tsconfig.json or some more information like build logs, etc. so we can debug this further. You can do message me privately on Discord at nikolahristov


3D model black in EDGE and fine in CHROME

Description
Using the same link to the same website, the shark appears black in Edge and OK in Chrome
https://web.dev/model-viewer/
I am having the same issues with my website also, its just easier to show the problem with the demo above.
Live Demo
https://web.dev/model-viewer/ open in Edge and Chrome
Browser Affected

[ ] Chrome, version: xx.x.xxxx.xx
[x] Edge
[ ] Firefox
[ ] IE
[ ] Safari

OS

[ ] Android
[ ] iOS
[ ] Linux
[ ] MacOS
[x] Windows

That's not ideal! Since I don't have a windows machine handy, could you paste in any errors/warnings you see in the JS console? Also, do you have the same problem on https://modelviewer.dev/?

OK this is somewhat odd, I get the error below on the demo site, and also my site... but not on model-viewer site. For the most part no matter what site I go to it mostly works....
model-viewer.js:26890
THREE.WebGLRenderer: A WebGL context could not be created. Reason:  Could not create a WebGL context, VENDOR = 0x15ad, DEVICE = 0x0405, GL_VENDOR = Google Inc. (VMware), GL_RENDERER = ANGLE (VMware, VMware SVGA 3D Direct3D11 vs_4_0 ps_4_0, D3D11-<IP_ADDRESS>), GL_VERSION = <IP_ADDRESS>, Sandboxed = yes, Optimus = no, AMD switchable = no, Reset notification strategy = 0x8252, ErrorMessage = bindToCurrentThread failed: .

The site you linked is quite old and still has our legacy fallback version for IE. That's been deprecated for some time; does your site have it as well by chance? If so, try removing it. Just a shot in the dark...

On my site, all I add is

Would you mind trying to build a minimal repro by remixing the glitch link in our issue template? That would go a long way toward helping us fix this, since you have the repro.


remove outdated data param

fix discussion https://github.com/pikapkg/snowpack/discussions/971

👍 👍 👍


Node shutting down because error in main method

Background
I had power outage of my network storage with LND data folder (.lnd/data), so LND node lost connection to it, but continue to run. I restored power supply and restarted LND. After restart, node shutting down with error.
Your environment

version of lnd
0.15.0-beta commit=v0.15.0-beta
which operating system (uname -a on *Nix)
Ubuntu
version of btcd, bitcoind, or other backend
bitcoind 230000

`Version: 0.15.0-beta commit=v0.15.0-beta-146-g87f4f03fc, build=production, logging=default, debuglevel=info
2022-08-23 07:40:39.230 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2022-08-23 07:40:39.231 [INF] RPCS: RPC server listening on <IP_ADDRESS>:10009
2022-08-23 07:40:39.235 [INF] RPCS: gRPC proxy started at <IP_ADDRESS>:8080
2022-08-23 07:40:39.236 [INF] LTND: Opening the main database, this might take a few minutes...
2022-08-23 07:40:39.237 [INF] LTND: Opening bbolt database, sync_freelist=true, auto_compact=false
2022-08-23 07:40:39.593 [INF] LTND: Creating local graph and channel state DB instances
2022-08-23 07:40:39.868 [INF] CHDB: Checking for schema update: latest_version=29, db_version=29
2022-08-23 07:40:39.906 [INF] LTND: Database(s) now open (time_to_open=669.553511ms)!
2022-08-23 07:40:39.907 [INF] LTND: We're not running within systemd or the service type is not 'notify'
2022-08-23 07:40:39.907 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
2022-08-23 07:40:58.325 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
2022-08-23 07:41:25.714 [INF] LNWL: Opened wallet
2022-08-23 07:41:25.763 [INF] CHRE: Primary chain is set to: bitcoin
2022-08-23 07:41:25.903 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on <IP_ADDRESS>:28332
2022-08-23 07:41:25.903 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on <IP_ADDRESS>:28333
2022-08-23 07:41:25.903 [INF] CHRE: Initializing bitcoind backed fee estimator in CONSERVATIVE mode
2022-08-23 07:41:26.498 [INF] LNWL: The wallet has been unlocked without a time limit
2022-08-23 07:41:26.518 [INF] CHRE: LightningWallet opened
2022-08-23 07:41:26.540 [INF] SRVR: Onion services are accessible via Tor! NOTE: Traffic to clearnet services is not routed via Tor.
2022-08-23 07:41:26.540 [INF] TORC: Starting tor controller
2022-08-23 07:41:26.823 [INF] HSWC: Cleaning circuits from disk for closed channels
2022-08-23 07:41:26.988 [INF] HSWC: Finished cleaning: num_closed_channel=36, num_circuits=0, num_keystone=0
2022-08-23 07:41:26.988 [INF] HSWC: Restoring in-memory circuit state from disk
2022-08-23 07:41:27.119 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0
2022-08-23 07:41:27.257 [ERR] LTND: Shutting down because error in main method: unable to create server: unable to read bucket for chain=616c6961732d6275636b6574
2022-08-23 07:41:27.258 [INF] TORC: Stopping tor controller
2022-08-23 07:41:27.258 [ERR] TORC: DEL_ONION got error: invalid arguments: unexpected code
2022-08-23 07:41:27.258 [ERR] LTND: error stopping tor controller: invalid arguments: unexpected code
2022-08-23 07:41:27.263 [INF] LTND: Shutdown complete`

Do you perhaps have the logs for the time at which the power outage happened? Would be useful to see how LND responded to that.

Sorry, I don't know, how logging work, so I can find only lnd.log contained logs after restart. And another file named lnd,log.1, that contain only one minute repeating message (while connection was lost):
2022-08-22 13:13:16.442 [ERR] BTCN: Can't accept connection: accept tcp [::]:9735: accept4: too many open files

Do you perhaps have the logs for the time at which the power outage happened? Would be useful to see how LND responded to that.

Sorry, I don't know, how logging works, so I can find only lnd.log contained logs after restart. And another file named lnd.log.1, that contain only one minute repeating message (while connection was lost): 2022-08-22 13:13:16.442 [ERR] BTCN: Can't accept connection: accept tcp [::]:9735: accept4: too many open files

Out of curiosity, what does cat /proc/sys/fs/file-max display to you? (Shows the number of allowed open files).

Out of curiosity, what does cat /proc/sys/fs/file-max display to you? (Shows the allowed max number of open files).
9223372036854775807

Also see https://github.com/lightningnetwork/lnd/issues/6231#issuecomment-1072213156

ok @9414286 , so next step would be to try a db compaction. You can do this either by turning on auto-compaction in LND by setting the db.bolt-auto-compact=true option. Or you can manually do it by using a tool like chantools compactdb.
If after doing this you still get this error, then you will need to do an SCB recovery.

Also see #6231 (comment)

I set DefaultLimitNOFILE=1024000:5120000, rebooted ubuntu, but result is the same:
2022-08-23 21:46:52.572 [ERR] LTND: Shutting down because error in main method: unable to create server: unable to read bucket for chain=616c6961732d6275636b6574

Also see #6231 (comment)

I set DefaultLimitNOFILE=1024000:5120000, rebooted ubuntu, but result is the same: 2022-08-23 21:46:52.572 [ERR] LTND: Shutting down because error in main method: unable to create server: unable to read bucket for chain=616c6961732d6275636b6574

`2022-08-23 22:40:11.016 [INF] LTND: Version: 0.15.0-beta commit=v0.15.0-beta-146-g87f4f03fc, build=production, logging=default, debuglevel=info
2022-08-23 22:40:11.016 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2022-08-23 22:40:11.016 [INF] RPCS: RPC server listening on <IP_ADDRESS>:10009
2022-08-23 22:40:11.018 [INF] RPCS: gRPC proxy started at <IP_ADDRESS>:8080
2022-08-23 22:40:11.018 [INF] LTND: Opening the main database, this might take a few minutes...
2022-08-23 22:40:11.018 [INF] LTND: Opening bbolt database, sync_freelist=true, auto_compact=true
2022-08-23 22:40:11.037 [INF] CHDB: Compacting database file at /mnt/synology/.lnd/data/graph/mainnet/channel.db
2022-08-23 22:40:59.654 [INF] LTND: Shutdown complete
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xb1614e]
goroutine 1 [running]:
go.etcd.io/bbolt.(*Bucket).Sequence(...)
/home/vnc/go/pkg/mod/go.etcd.io/bbolt@v1.3.6/bucket.go:340
github.com/lightningnetwork/lnd/kvdb.(*compacter).walkBucket.func1({0x7ff04d75b180, 0xc, 0xc}, {0x0?, 0x9e?, 0x9e?})
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/bolt_compact.go:277 +0xee
go.etcd.io/bbolt.(*Bucket).ForEach(0xc0008a16c0, 0xc0005e05e8)
/home/vnc/go/pkg/mod/go.etcd.io/bbolt@v1.3.6/bucket.go:390 +0xa4
github.com/lightningnetwork/lnd/kvdb.(*compacter).walkBucket(0xc0005e0eb0, 0xc0008a16c0, {0xc00075d1e8?, 0x1, 0x1}, {0x7ff0278fc2d4, 0x21, 0x21}, {0x0, 0x0, ...}, ...)
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/bolt_compact.go:273 +0x1cb
github.com/lightningnetwork/lnd/kvdb.(*compacter).walkBucket.func1({0x7ff0278fc2d4, 0x21, 0x21}, {0x0?, 0x0?, 0x0?})
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/bolt_compact.go:276 +0x148
go.etcd.io/bbolt.(*Bucket).ForEach(0xc0008a0c80, 0xc0005e0788)
/home/vnc/go/pkg/mod/go.etcd.io/bbolt@v1.3.6/bucket.go:390 +0xa4
github.com/lightningnetwork/lnd/kvdb.(*compacter).walkBucket(0xc0005e0eb0, 0xc0008a0c80, {0x0?, 0x0, 0x0}, {0x7ff00bc1f186, 0x10, 0x10}, {0x0, 0x0, ...}, ...)
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/bolt_compact.go:273 +0x1cb
github.com/lightningnetwork/lnd/kvdb.(*compacter).walk.func1.1({0x7ff00bc1f186, 0x10, 0x10}, 0xc0008a0c80)
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/bolt_compact.go:226 +0x145
go.etcd.io/bbolt.(*Tx).ForEach.func1({0x7ff00bc1f186, 0x10, 0x10}, {0x0?, 0x0?, 0x100e8?})
/home/vnc/go/pkg/mod/go.etcd.io/bbolt@v1.3.6/tx.go:129 +0x63
go.etcd.io/bbolt.(*Bucket).ForEach(0xc0004ae2b8, 0xc0005e0918)
/home/vnc/go/pkg/mod/go.etcd.io/bbolt@v1.3.6/bucket.go:390 +0xa4
go.etcd.io/bbolt.(*Tx).ForEach(0xc0000fc880?, 0xc0000fc8a0?)
/home/vnc/go/pkg/mod/go.etcd.io/bbolt@v1.3.6/tx.go:128 +0x49
github.com/lightningnetwork/lnd/kvdb.(*compacter).walk.func1(0x0?)
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/bolt_compact.go:220 +0x4b
go.etcd.io/bbolt.(*DB).View(0xc0000fcac0?, 0xc0005e09f0)
/home/vnc/go/pkg/mod/go.etcd.io/bbolt@v1.3.6/db.go:772 +0x82
github.com/lightningnetwork/lnd/kvdb.(*compacter).walk(0x0?, 0x0?, 0x0?)
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/bolt_compact.go:219 +0x46
github.com/lightningnetwork/lnd/kvdb.(*compacter).compact(0xc0005e0eb0, 0xc0000fc900, 0xc0005e0bb0?)
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/bolt_compact.go:147 +0x125
github.com/lightningnetwork/lnd/kvdb.(*compacter).execute(0xc0005e0eb0)
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/bolt_compact.go:117 +0x6ea
github.com/lightningnetwork/lnd/kvdb.compactAndSwap(0xc0005e1298)
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/backend.go:179 +0x74f
github.com/lightningnetwork/lnd/kvdb.GetBoltBackend(0xc0005e1298)
/home/vnc/go/pkg/mod/github.com/lightningnetwork/lnd/kvdb@v1.3.1/backend.go:101 +0x87
github.com/lightningnetwork/lnd/lncfg.(*DB).GetBackends(0xc000122000, {0x18775f8?, 0xc0004b0f00}, {0xc0006a6270, 0x25}, {0xc000519d70, 0x2d}, {0xc0006a62a0, 0x2e}, 0x1, ...)
/home/vnc/go/src/github.com/lightningnetwork/lnd/lncfg/db.go:392 +0x1fd1
github.com/lightningnetwork/lnd.(*DefaultDatabaseBuilder).BuildDatabase(0xc0004d8dc8, {0x18775f8, 0xc0004b0f00})
/home/vnc/go/src/github.com/lightningnetwork/lnd/config_builder.go:813 +0x325
github.com/lightningnetwork/lnd.Main(0xc00011aa00, {{0x0?, 0xc0000021a0?, 0x300000002?}}, 0xc000480cc0, {0xc00009b320, 0xc0000a6840, 0xc0000a68a0, 0xc0000a6900, {0x0}})
/home/vnc/go/src/github.com/lightningnetwork/lnd/lnd.go:355 +0x1810
main.main()
/home/vnc/go/src/github.com/lightningnetwork/lnd/cmd/lnd/main.go:38 +0x205
`

... then you will need to do an SCB recovery.

In my opinion, it is totally wrong way because it means, that you can't operate node at home because power outage is very common. I can't remember any case when any application or database was corrupted to zero by power outage (if HD wasn't damage). It have to be way to close one or couple LN "bad" channels, from SCB, but not all of them.
Another way is to tell the truth to the people: LN nodes are only for Industrial dataсenter, not for kitchens. So lightning will become a centralized service.

@9414286 , what hardware are you running on? both LND & data folder

@9414286 , what hardware are you running on? both LND & data folder
Thanks for truing to help. Main proccesor with LND daemon is I7+16gb memory+500gb HD, data folder in Synology RAID1 5TB+5TB (WD Red) (I added it after previous SCB with HD hardware problem). Synology shows me, that file system is ok.

unfortunately it does seem like SCB is your best option here. From the error you have posted, there is clearly some db corruption that occurred. Perhaps in future, consider using a Postgres backend as well as investing in a UPS.

unfortunately it does seem like SCB is your best option here. From the error you have posted, there is clearly some db corruption that occurred. Perhaps in future, consider using a Postgres backend as well as investing in a UPS.

I already have two UPS (LND node have way more lifetime than Synology ). It sounds very sad, because I thought I invested enough to prevent SCB. Maybe it is a good reason to give up with Lightning after 3,5 years of operating. Thank you for your help.


Is there an option to disable the RTC overlay text in the top right hand corner?

I am using go2rtc through Frigate.  When I stream my cameras I get an "RTC" in the top right hand corner.  Is there a switch to disable this?  Thanks.

I think this question not to this project. Go2rtc writes this label only in the own WebUI. You can write custom WebUI if you want: https://github.com/AlexxIT/go2rtc#module-api

Hi, im using go2rtc with the HomeAssistant Integration. On my HA UI i also see the annoying "RTC" Text - how can i disable / hide it? Where is it coming from? Thanks!

I think this question not to this project. Go2rtc writes this label only in the own WebUI. You can write custom WebUI if you want: https://github.com/AlexxIT/go2rtc#module-api

I see that someone else has asked the same question.  I didn't fully understand your response but seek to clarify here.  You state that "Go2rtc writes this label only in the own WebUI".  Not sure what this means.  Go2rtc writes this label in MY own WebUI, or in Go2rtc's WebUI?
Since Go2rtc was installed with Frigate and I made only Frigate specific configuration - I am not clear where I would start to discuss this to see if it is possible to remove it?  The link is to commands for writing a custom UI - a custom UI for what - go2rtc?  I am not using any WebUI - all I am getting is a simple camera feed and want to get rid of the RTC.
If there is a place that is better to discuss this then please suggest where that might be.  Thanks.

You both need to figure out what project is being used to display this overlay. And write in the repository of that project

HI @AlexxIT : Im using HomeAssistant and the default Card from your Project: https://github.com/AlexxIT/WebRTC#configuration

So it is not Frigate - already confirmed there?  It is not Go2rtc - confirmed here?  So no ideas where it might be coming from?  Seems like a mystery?

@Marcwa19197 how to remove mode label for WebRTC Camera project described in the readme

Worked - thanks! So @simondsmason: In your case it must be on the frigate side (?)
Adding style: '.mode {display: none}' to the card-config fixed it for my side, thank you!

Where exactly in the configuration did you make this change?  I will have to look for that in my Frigate setup as I didn't configure anything specific for go2rtc - it was all done with the frigate docker install.  Currently I am only configuring go2rtc in the frigate config file so don't have anywhere at present to add in this command.  Thanks for helping.

On the UI Settings which displays the camera feed - im not using frigate (but nice tip - will look into this). Is there a way to change the settings how the UI is displaying the camera feed? (Or adding some custom CSS-Commands?)

Thanks - don't know about settings on the go2rtc feed - will check in the Frigate docker files.  Frigate is great.  I used to use Blue Iris - very powerful but a nightmare to setup and maintain and in my situation was very unstable.  Frigate has a steep learning curve but truly set and forget once it is running.


Check for pending buffer

I had some problems with resizing of windows. After some time of debugging I found maybe the problem. I am little bit unsure if this the correct way to handle it.
The problem seems to be that the frame_done_cb has not yet been called at the time of if-breaking.
My fix had the problem, that it is possible that the change of width/height will be not used, because there is a pending buffer, a timer could fix the problem but I think that is not the nice way.
Issue: https://github.com/FreeRDP/FreeRDP/issues/6349

I am not quite sure if the problem is solved. But I think the PR can be closed.


NNBD. No static warning for using null-aware operators on non-nullable receiver

According to the NNBD specification

It is a warning to use a null aware operator (?., ?.., ??, ??=, or ...?) on a non-nullable value.

class A {
}
class C extends A {}

main() {
  A? a = A();
  C c = C();
  if (a is Object) {
    a?.toString();
    a?..toString();
    a ?? c;
    a ??= c;
  }
}

The code above produces no any errors or warnings in dartanalyzer version 2.7.0-dev.2.1
See also #39598

@leafpetersen Is this kind of promotion supported by the flow analysis? It does not look so to me. instance check uses promote(E, T, M), which requires T <: S. In this case Object is not a subtype of A?, so no promotion.

@scheglov I agree with your interpretation.  I would expect that any of the following would work:

a is! Null
a is A
a != null

But a is Object is not a promotable instance check.


[Bug] echarts tooltip when triggerOn is 'none' but actually triggered at yAxis.axisPointer item

Version
5.4.2
Link to Minimal Reproduction
https://quska45.github.io/onTuneChart/?path=/story/example-v5-ontunechart--primary
Steps to Reproduce

How do you create the chart.

I created a chart with options like below.

What's the chart option
`let eChartOption: TEChartOption = {
title: {
id: onTuneChartConfig.title.text,
show: false,
text: onTuneChartConfig.title.text,
textStyle: {
fontSize: 18
},
},
animation: false,
grid: {
top: gridTop,
bottom: gridBottom,
left: gridLeft,
right: gridRight
},
xAxis: [
{
type: 'category',
boundaryGap: true,
min: seriesTerm - onTuneChartConfig.xAxis.timeRange,
max: seriesTerm,
axisLabel: {
interval: onTuneChartConfig.xAxis.labelInterval,
formatter: function( value, index ){
// console.log( 'moment(value)', moment(new Date()) );
// console.log( 'moment(value).format("HH:mm:ss")', moment(new Date()).format('HH:mm:ss') );
return value;
},
// rotate: 90,
showMaxLabel: true,
showMinLabel: true
},
axisTick: {
alignWithLabel: true,
},
}
],
yAxis: [
{
id: 'yAxis',
type: 'value',
show: onTuneChartConfig.yAxis.show,
min: onTuneChartConfig.yAxis.min,
max: onTuneChartConfig.yAxis.max,
position: echartOptionMaker.getYAxisPosition( onTuneChartConfig.yAxis.position ),
splitLine: {
show: true,
lineStyle: {
type: 'dashed'
},
},
axisLabel: {
formatter: ( value: number ) => {
if( typeof value !== 'number' ){
return '{value}'
};
                 const result = value <= 1000 ? value : `${value / 1000}K`;
                 return result.toString();
             }
         },
         triggerEvent: false,
         axisPointer: {
             triggerTooltip: false,
             triggerOn: 'none',
         }
     },
     {
         id: 'secondYAxis',
         type: 'value',
         show: onTuneChartConfig.secondYAxis.show,
         min: onTuneChartConfig.secondYAxis.min,
         max: onTuneChartConfig.secondYAxis.max,
         position: echartOptionMaker.getYAxisPosition( onTuneChartConfig.secondYAxis.position ),
         axisLabel: {
             formatter: ( value: number ) => {
                 if( typeof value !== 'number' ){
                     return '{value}'
                 };

                 const result = value <= 1000 ? value : `${value / 1000}K`;
                 return result.toString();
             }
         },
         triggerEvent: false,
         axisPointer: {
             triggerTooltip: false,
             triggerOn: 'none',
         }
     },
     {
         id: 'eventIndicatorYAxis',
         type: 'value',
         min: 0,
         max: 10000,
         position: 'left',
         show: true,
         axisLabel: {
             formatter: function(){
                 return '';
             }
         },
         triggerEvent: false,
         axisPointer: {
             triggerTooltip: false,
             triggerOn: 'none',
             z: 30,
             label: {
                 show: true,
                 formatter: function (params) {
                     return Math.floor(params.value as number).toString();
                 },
             },
             value: 2000,
             show: true,
             type: 'line',
             status: 'show',
             lineStyle:{
                 color:'red',
             },
             handle: {
                 show: true,
                 size: 1
             }
         },
     }
 ],
 series: OnTuneChartSeries2.getConditionCheckedSeries( series ),
 toolbox: {
     feature: {
         saveAsImage: {},
         // dataZoom: {}
     },
 },
 tooltip: [
     {
         show: true,
         trigger: 'axis',
         showContent: true,
         axisPointer: {
             type: 'cross',
         },
     },
 ],
 graphic: {
     elements: [
         {
             id: 'line1',
             type: 'line',
             shape: {
                 x1: 0,
                 y1: gridTop,
                 x2: 0,
                 y2: 0,
             },
             z: 10,
             style: {
                 stroke: 'red',
                 lineWidth: 2,
             },
             invisible: true,
         }
     ],
 }

};`

User interactions before the error happens.

If you look at options, you can see that options such as triggerTooltip and triggerOn of yAxis.axisPointer are false and 'none'. But when mouse move happens, axisPointer of yaxis moves. What I consider to be a bug is that the options in the tooltip affect the yaxis.axisPointer. If you change the tooltip's triggerOn to 'none', yaxis.axisPointer will not be affected.
Attached the link below for a similar issue. It was closed because it did not fit the issue presentation format, but it is similar to the question I want to ask.
https://github.com/apache/echarts/issues/13343

Current Behavior
If you look at options, you can see that options such as triggerTooltip and triggerOn of yAxis.axisPointer are false and 'none'. But when mouse move happens, axisPointer of yaxis moves. What I consider to be a bug is that the options in the tooltip affect the yaxis.axisPointer. If you change the tooltip's triggerOn to 'none', yaxis.axisPointer will not be affected.

Attached the link below for a similar issue. It was closed because it did not fit the issue presentation format, but it is similar to the question I want to ask.

Expected Behavior
It looks like yAxis.axisPointer and tooltip's triggerOn property should work separately. What I want is a function that allows yAxis.axisPointer to always be displayed at a specific value, and tooltip's axisPointer to follow the mouse and display crossHair and tooltip.
Environment
- OS:window 11
- Browser:chrome
- Framework:svelte

Any additional comments?
please fix or modify this option. help me (T_T)

The Minimal Reproduction and Steps to Reproduce are unusable. Frameworks like Storybook and unknown objects like onTuneChartConfig are showstoppers. Please make an effort to create a simple Minimal Reproduction with ECharts and Javascript only.

The Minimal Reproduction and Steps to Reproduce are unusable. Frameworks like Storybook and unknown objects like onTuneChartConfig are showstoppers. Please make an effort to create a simple Minimal Reproduction with ECharts and Javascript only.

What I want is a function that allows yAxis.axisPointer to always be displayed at a specific value, and tooltip's axisPointer to follow the mouse and display crossHair and tooltip.

Demo Code

What I want is a function that allows yAxis.axisPointer to always be displayed at a specific value, and tooltip's axisPointer to follow the mouse and display crossHair and tooltip.

Demo Code

thanks for the sample code I'm thinking about changing the code in this way too. But if possible, I want to implement the function I want through yAxis rather than adding one series.


Gradle: Upgrade Maven resolver to version 1.3.3

The recent upgrade to 1.3.2, see 2e9eb96, broke the analyzer because that
release has accidentally been built with Java11 rendering it unusable for
Java8 which we currently use, see:
https://issues.apache.org/jira/browse/MRESOLVER-67
As result the analyzer runs into the following consistently:
java.lang.NoSuchMethodError:
java.nio.ByteBuffer.rewind()Ljava/nio/ByteBuffer;
As that problem has already been addressed with the release of
version 1.3.3 fix the issue by upgrading again instead of reverting
to 1.3.1.
Signed-off-by: Frank Viernau<EMAIL_ADDRESS>

This change is

Commit message nits: "Java 11" and "Java 8" (with spaces in between). I'll merge afterwards directly as it PR will anyway probably fail as https://github.com/heremaps/oss-review-toolkit/pull/1374 is not merged yet.


merge unneeded branch v0.3.0 into master

Originally I wanted to work on new features for v0.3.0 in a separate branch, but it makes more sense to have a separate branch for the upcoming v0.2.0 that is based off v0.2.0-rc0.

Assuming the tests are a good indicator already. merging :-)


cube.convert_units: raise exception when unit is unknown

Fix for #1977.  If the units on a cube are unknown, the convert_units method should raise an exception.  I consider the current behaviour of just setting the units to be a bug.  If a user has not realised the metadata in the data file is incomplete, then the cube could end up with spurious data values.
A couple of things I'm not sure of:

I couldn't figure out if the class definitions in iris.exceptions were in any particular order, so just put the new one at the end.

Did I put the whatsnew in the right place?

Travis is telling me it can't find Cartopy.  I'm pretty sure my changes didn't cause this!

Travis is telling me it can't find Cartopy. I'm pretty sure my changes didn't cause this!

Internet pixies... they've been cleared out now.

Did I put the whatsnew in the right place?

This is really an incompatible change rather than a bugfix, although this may be a matter of opinion. I can imagine someone writing code that relies on this behaviour though.

Thanks @ajdawson, I've now moved the whatsnew to the incompatible changes section.

Hi @rcomer - thanks for this proposed change, which looks to improve some odd silent behaviour in Iris. You've also chosen a good time to propose this incompatible change just in time for Iris v2.0!
I've made some comments on some things that will need changing, which are all minor but I think necessary. I'd also like you to make the same set of changes again but for coord.convert_units - so the same logic change to this method, a test and a whatsnew entry. Then I think we'll be done!

Thanks for the feedback @dkillick.  I'm actually on leave for the next two weeks (browsing GitHub from my sofa, as you do).  So, assuming there's no major hurry, I'll address it properly when I get back.

OK, I think I have covered everything now.  The Travis errors appear to all be timeouts.  Do I need to do anything about the CLA?  The Met Office already owns all my work...

Do I need to do anything about the CLA? The Met Office already owns all my work...

You don't need to sign the document but you do need to add your name to the contributors.json file in the SciTools/scitools.org.uk repository via PR.

Thanks @ajdawson, I've had a notification that suggests @pelson has now added me in his branch.

I did a rebase to pick up #2757, but I think the internet pixies might be playing again:
urllib2.URLError: <urlopen error [Errno -2] Name or service not known>

The command "python -c 'import cartopy; cartopy.io.shapereader.natural_earth()'" failed and exited with 1 during .

@dkillick - are you able to go through your review again and confirm the items that are outstanding please? I think there have been a few changes since your last comments, and they may now be addressed.
Thanks 😄

@rcomer thanks for pressing on with this – it's a very beneficial addition 👍


Plumbing of StartPeriod field in container HealthConfig

Plumbing of StartPeriod field in container HealthConfig.
See https://github.com/docker/docker/pull/28938 for more information regarding the StartPeriod field.
This requires vendoring of a newer docker in order to work!

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:elifa/swarmkit.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Feel free to vendor a newer Docker. You only need to update the commit hash in vendor.conf and run vndr github.com/docker/docker (make setup should install vndr).

@aaronlehmann Do you want me to do it in this PR or in a separate one?

Either way is fine. If you do it in this PR, it's best to put it in a separate commit, but it doesn't really matter to me.

Latest docker is now vendored in a separate commit.

LGTM

LGTM

Hello, a quick question since I'm still a little bit confused by the new release model: in which docker-ce version will this PR appear? or is it already in 17.04 ?


revel support go mod build projects？

This is a feature that is being prepared for.

thanks. that's what I'm looking forward to. do you have a specific schedule?

+1  I'm looking forward to.

sure need support go mod!

https://github.com/revel/cmd/issues/177

Revel does support go mod now

If anyone has further questions or feedback, feel free to comment. Closing due to age and the fact that Revel does now support go modules.