Buffer Underflow

Added audio-gain to have remote volume control of speaker system and after a file is done playing i'm getting a buffer underflow error repeated until i press CTL + C
Node: 10.9.0
OS: mac
main OS this will run on is arm Linux but i haven't pushed to the running device yet as this issue might mess up stability.
[../deps/mpg123/src/output/coreaudio.c:81] warning: Didn't have any audio data in callback (buffer underflow)

oops, sorry!


fix: Generalize react-refresh preamble logic to virtualize all inline scripts

Basically, the react plugin was adding an inline script to the HTML page to enable HMR:
<script type="module">
  import RefreshRuntime from "/@react-refresh"
  RefreshRuntime.injectIntoGlobalHook(window)
  window.$RefreshReg$ = () => {}
  window.$RefreshSig$ = () => (type) => type
  window.__vite_plugin_react_preamble_installed__ = true
</script>

However, this doesn't work for chrome extensions because inline scripts are blocked by the CSP, in dev and production.
Before this PR, I had written specific code to find and virtualize this react-refresh "preamble" inline script so it could be loaded from http://localhost:3000/@wxt:virtualized-react-refresh. So originally, I wanted to extract this logic into @wxt-dev/module-react. But since the devServerPrerender plugin (where this react-refresh logic is) is added in a kinda special place, there wasn't a hook for adding a similar plugin in the module yet.
Instead, I realized a better solution would be to generalize the logic in case another plugin adds inline scripts in the future, it would be handled automatically! So that's what this PR does.


minor : some leftover I2C stuff

Cool project !
I took about 15 minutes to port it to my F042 board, seems to be working so far.
Looking through the code :
  PeriphClkInit.PeriphClockSelection = RCC_PERIPHCLK_USB|RCC_PERIPHCLK_I2C1;
  PeriphClkInit.UsbClockSelection = RCC_USBCLKSOURCE_HSI48;
  PeriphClkInit.I2c1ClockSelection = RCC_I2C1CLKSOURCE_HSI;
  HAL_RCCEx_PeriphCLKConfig(&PeriphClkInit);

We can probably remove everything related to I2C ? Unless there's a non-obvious usage that I missed...

Thanx @fenugrec !

We can probably remove everything related to I2C ?

Yeh it is rudiment part,it do nothing here.. you can remove it, but it will not change anything.

done


test: Refine Bank Customer Support Example

@vitalii-dynamiq, do we want to replicate the behavior here without using orchestrators?
@maksDev123

@vitalii-dynamiq, do we want to replicate the behavior here without using orchestrators?
@maksDev123

Orchestrator sometimes do not use documentation and goes straight to call API.


Implement params logic in refactored IF

Story
As a user, I want to have confidence in the params I am inheriting from IF and also freedom to override them as needed.
Rationale
We implemented some params logic in the original IF that has not been carried over into the refactor. Specifically, the ability to add params via the manifest file or to provide a params file on the command line.
Implementation details
Replicate the params logic from the original IF. Also add checks in IF that all params are listed in the canonical set.
Priority
4/5
Scope
tbc - could affect several core IF features
Size
1 day
What does "done" look like?
Refactored IF behaves similarly to original IF in terms of params logic
Does this require updates to documentation or other materials??
Probably not, but tbc
What testing is required?
manual testing
Is this a known/expected update?
Expected in sprint 7

Closing as completed by https://github.com/Green-Software-Foundation/if/pull/472


[Event Request] Table "Reminder Header" event OnBeforeInsertReminderTextLine

I would like to request that the event OnBeforeInsertReminderTextLine on the "Reminder Header" table passes the Reminder header parameter by reference.
 [IntegrationEvent(false, false)]
 local procedure OnBeforeInsertReminderTextLine(var ReminderLine: Record "Reminder Line"; var ReminderText: Record Reminder Text"; **var** ReminderHeader: Record "Reminder Header")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Question about @return [self]

Should @return [self] generally be expected to return an instance of the method's parent, or should it be expected to return the class from a class method? Example:
class Foo
  # @return [self]
  def self.bar; end
end
Foo.bar # <= Should the return type resolve to Foo or Class<Foo>?

If it's the latter, how should we document a class method that returns an instance of itself? My first instinct was Object<self>.

Using self is just a shortcut for the class name. If YARD had better support of unrolling type specifiers, it would probably unroll self to be Foo in the above example in docs, and would probably not handle the edge case of Class<Foo>. That said, it's a little misleading to use @return [self] at a class level method, since it's unclear to a reader at the source layer what the intent is-- in other words, it's not clear if you are relying on the existing the semantics of the doc tool or if you are incorrectly documenting the method.
The more straightforward path would be to simply use @return [Foo].

Yeah, that's exactly my concern. The existing semantics behave the way I want, but it's ambiguous to the reader. The issue with @return [Foo] is that I want the return type to be transitive; e.g., if Foo2 extends Foo, it can be inferred that Foo2.bar returns Foo2.
I take it there's no official way to express that? Should I just make up my own keyword, like @return [this] or something?

You could use Class<Foo> to communicate that the return type is a subclass of Foo, which should provide sufficient inference that it is of the type of class alongside some prose to clarify in the docstring.

I was under the impression that Class<Foo> would return the class itself instead of the instance, e.g., String#class would return Class<String>.

You're correct-- I misspoke and got confused by the very thing I mentioned above.

My first instinct was Object<self>

This is what I was trying to concur with. I think this would be the best way to go in the absence of any Ruby keywords to help communicate intent. You can, of course, invent your own (like instanceof<self> or instanceof<Foo>) but I think without precedent in the language it won't necessarily be any better understood than the above.
So yes, your first instinct was the correct one.

Perfect. Thanks for the clarification.


Application Errors bubbled up to user

Task to refactor apollo client error handling to capture extensions field and perform logic based on error type

user errors: show full message in error toast
server errors: show generic message (from api) in error toast
gql errors: show generic message (from client) in error toast. (edge case that shouldn’t be possible to reach) (Make a sentry report on this error only!)

context

issue where gql errors are throwing an exception in the apollo client and "throwing out" response data needed to perform error handling logic.
apollo client throws exception on gql errors when onError apollo link is not present.

completed with last merge


Add initial dashboard network protocol definition file

This .proto file defines a contract between the server Aspire.Hosting and client Aspire.Dashboard.
It supports:

Getting basic information about the server (name and version).
Subscribing to resources, receiving both an initial snapshot and a stream of updates as they happen.
~A heartbeat mechanism, to detect when the connection has dropped and allow prompting the user and/or reconnecting.~
Support for arbitrary kinds of resources. Not limited to known types (project, container, executable).
Support for arbitrary commands on resources, intended for actions such as start/stop/refresh/restart/etc. The server defines the commands available for each resource, and the UI can show them.

It's added to both the server and client projects, and code generation is enabled.

/azp run


Update Lab01[PL-600]_ALM.md

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by thecrmninja on behalf of MOC Labs Review

Closed as this lab was removed in the latest update.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

 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: jackratcliffe sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[Coverity CID :188741]Control flow issues in /subsys/shell/shell_utils.c

Static code scan issues seen in File: /subsys/shell/shell_utils.c
Category: Control flow issues
Function: shell_str_similarity_check
Component: Other
CID: 188741
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

obsolete, file refactored, marked as fixed in coverity


api: add grpc php support

closes #430

Thank you :+1: I think what is still missing is an update to: https://github.com/chirpstack/chirpstack/blob/master/Makefile#L16.
This make command is used to update the version number. This should also update composer.json.


Update tests/ConformanceTest-report.txt

Update after pulling in main into main-eisop.

The conformanceTests don't actually run on CI here, because minimal test fails first. I manually checked and with this change the conformanceTests pass.


Autofocus- looks like it treats current position as the "top" rather than the center

When I click on the autofocus button in the GUI, it appears that it treats the current position as the "top" rather than the "center".
Is this the expected behavior?  I would this it would/should use the current position as the center of the AF scan, not the top?
(Legacy Lumaview treats the initial position as the center, so that is what my expectation is...)
I.e. here we start at 4200 (and the _actual" focus level is @ 4470. (4x objective, in brightfield)>
But you can see it goes to 4050 and goes around but never exceeds the initial value (4200).
TrinamicBoard.move_abs_pos(Z,4200.0) succeeded
VerticalControl.update_gui()
TrinamicBoard.target_pos(Z) succeeded
VerticalControl.autofocus()
TrinamicBoard.move_abs_pos(Z,4049.9967799999995) succeeded
Clock.schedule_interval(self.focus_iterate, 0.01)
VerticalControl.focus_iterate()
VerticalControl.focus_function()
difference      6605811.0
TrinamicBoard.move_rel_pos(Z,72.0) succeeded
VerticalControl.update_gui()
TrinamicBoard.target_pos(Z) succeeded
VerticalControl.focus_iterate()
VerticalControl.focus_function()
difference      6935799.0
TrinamicBoard.move_rel_pos(Z,72.0) succeeded
VerticalControl.update_gui()
TrinamicBoard.target_pos(Z) succeeded
VerticalControl.focus_iterate()
VerticalControl.focus_function()
difference      6367926.0
VerticalControl.focus_best()
0       4193.98442      6367926.0
TrinamicBoard.move_abs_pos(Z,4049.9884599999996) succeeded
VerticalControl.update_gui()
TrinamicBoard.target_pos(Z) succeeded
VerticalControl.focus_iterate()
VerticalControl.focus_function()
difference      7019908.0
TrinamicBoard.move_rel_pos(Z,24.0) succeeded
VerticalControl.update_gui()
TrinamicBoard.target_pos(Z) succeeded
VerticalControl.focus_iterate()
VerticalControl.focus_function()
difference      6386560.0
VerticalControl.focus_best()
1       4073.9833399999998      6386560.0
TrinamicBoard.move_abs_pos(Z,4025.9866399999996) succeeded
VerticalControl.update_gui()
TrinamicBoard.target_pos(Z) succeeded
VerticalControl.focus_iterate()
VerticalControl.focus_function()
difference      6799135.0
TrinamicBoard.move_rel_pos(Z,20.0) succeeded
VerticalControl.update_gui()
TrinamicBoard.target_pos(Z) succeeded
VerticalControl.focus_iterate()
VerticalControl.focus_function()
difference      6383684.0
VerticalControl.focus_best()
2       4045.9784       6383684.0
TrinamicBoard.move_abs_pos(Z,4025.9840799999997) succeeded
Clock.unschedule(self.focus_iterate)
Clock.unschedule(self.focus_iterate)
VerticalControl.update_gui()
TrinamicBoard.target_pos(Z) succeeded

It is supposed to use the current position as center.
It starts at the bottom (center - range) and moves up
As it moves up, once the score starts to decrease, it skips the rest of the vertical steps and starts with smaller steps below.
This strategy may need to change now that the z axis is much faster.

Maybe the display is lagging the actual position but I think the initial scan should at least get to the current position and not stop prematurely.  If the actual focus level is above the current position, as it is in my example, you never get there.  And subsequent autofocus runs lower it even more.

I am attaching before and after AF screenshots along with a text file of the relevant transactions. After I found and focused a BF image, I set the x,y,z coordinates and then clicked on AF.
It appeared to me that the initial position was indeed used as the center. First image is after AF
Autofocus Test Results from Terminal Window20230216.txt

I think it would be very helpful to have a AF log that only has:
XY position (or well location), Z position, focus score.  (with time stamp)
(maybe as something that we can enable?)

Yes. You can enable in line 111 in lumaviewpro.py by changing the line from "if False:" to if True:"

Attempt to speed up autofocus caused this error. We will try to dev a better AF but for now, the issue is fixed.


Removes table-responsive div from components/navs

.table-responsive is deprecated in v4. I've removed an instance where it's used in the docs. It causes the code copy button to be misplaced as shown in the screenshot. This pull request removes the <div class="table-responsive> wrapper around the table.

Here's what it looks like after:

It's not deprecated: https://github.com/twbs/bootstrap/blob/v4-dev/scss/_tables.scss#L103-L119. It's just no longer a parent class—instead add it to the table itself.

@cvrebert can I reopen this and just add the table-responsive class to the table? By what @mdo said the docs are still broken. The new pull request would still remove the extra table-responsive div, but add the class to the table... ?

@abitdodgy Yes, of course, by all means.


patch can conflict on not activated packages

What does this PR try to resolve?
In the resolver there is a data structure called a conflicting_activations, which records all the reasons a "better" version was not picked for the package being resolved. Normally, these are packages that are currently active that for one reason or another block one of the other versions. Several optimizations assumed that this was always true, even going so far as to use .expect. This was a mistake because when there's a patch involved there can be conflicts on a version that is not selected. So the correct behavior is to fall back to skip the optimizations and try all versions when a conflicting_activations are not active.
How should we test and review this PR?
This adds two automated tests based on the reproductions in #7463 and #11336. So the test suite now covers this case. It can also be tested by reconstructing the repositories originally reported in those issues.
Additional information
It could be that in the long term the correct fix is to figure out how to support patch without having a conflicting activation that is not activated. But that would be a much bigger change. And for now this assumption is only used in optimizations, so this gets people unstuck.

:pushpin: Commit 4369d8a34ecb953da83966baaaf2746780ad97aa has been approved by Eh2406
It is now in the queue for this repository.

@bors r-

@bors r-

Sorry r+ commented on the wrong thread.

@bors r+

:pushpin: Commit 2c712d5d46c0c852b219e69facd9a5ab2fe6f9b3 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 2c712d5d46c0c852b219e69facd9a5ab2fe6f9b3 with merge c61b0f06807f3da60b7bbfa61455871d681e5eb5...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing c61b0f06807f3da60b7bbfa61455871d681e5eb5 to master...


RGBD camera points cloud

Hi,
I'm trying to get the point clouds given by the depth camera, however I'm finding trouble extracting the rgb values correctly.
I'm subscribing to the /quadrotor_1/slot3/points topic. In the respective PointField[] fields there is a description of the channels and their layout in the binary data blob (as shown in the picture below).

The 'point_step' field in the PointCloud2 message is equal to 24, meaning that each point cloud is represented by 24 bytes. Considering the description in the picture, i would expect that the x-y-z value are 4 bytes each and the remaining 12 are given by r-g-b values. Hence, looking at the last channel, 'rgb', I would expect it to start at offset 12 and having count = 3, meaning that there are 4 bytes for each channel, instead  of having offset=16 and count = 1.

the rgb values are 1 byte per channel. They are packed into 4 byte data type (7). So the first byte is r, second byte is g, etc.

Yeah that was my guess, however since the point_step is 24 (bytes) and the rgb channel starts at offset 16, there should be something wrong.

I think the rgb value could in theory start at offset 12 and occupy the next 4 bytes. We won't change the behavior now though. In any case, the each point cloud occupies 16 out of 24 bytes and the rest are just padding. You'll just need to get the rgb values from offset 16 instead of offset 12.


build: adds migration support to servicing-station

Allows the servicing station container to automatically run database migrations by setting the MIGRATION environment variable.

I do not want auto-migration.
Migration of DB schemas should always be intentional.  Not a side effect of a deployment.
All migrations should entail:

Bringing down EVERY service that is using the DB and schema.
When the DB is stable, FULL back up.
Migrate schema.
Run any tests that exist on the schema to ensure the migration was successful.
Redeploy all services that use the new schema.

Regardless of if there is 1 or more services,  the above should be the process.
Also,  vit-ss currently defines its schema.  But that will change immediately after the SVE.  For fund 10, vit-ss will use a common database that multiple services are using/updating and will not OWN its schema.  The DB/Schema will be their own thing.

For clarity, this is only automatic insofar as the appropriate environment variable is set. By default, it will not be set, it's really just a flag that we can invoke to run a migration from inside of the VPC network. It's important to realize that:

The RDS instance is inaccessible from the internet
The only way to access it locally is to forward a connection using socat and kubectl port-forward
Applying migrations may be a semi-routine activity during testing periods when clusters are being set up and/or databases are being nuked.

I don't mind keeping migrations relegated to a script at this point. The purpose of this change was to allow applying a migration without relying on local port-forwarding (i.e., just deploy the service with MIGRATE set).
We can table this for now.


Set logging level for requests via new Server options

Relating to https://github.com/gaqzi/gocd-cli/issues/14, this PR will allow client to set logging level for requests via the new Server options using request_debug_level key which defaults to 0.
This should be helpful for debugging.
Sad to say my Python knowledge is very limited so I don't know how to unit test this. :sweat:
Any suggestion?

This appears to be fine on first look, but looking deeper request_debug_level is only used by _add_basic_auth and that is only used if you pass a user and password.
As for test, I'd say the important piece is that request_debug_level reaches urllib. So I suggest you mock the part of urllib that receives the debug level and then assert that it received the correct value.

@sushengloong this is the wrong place for this, since I know your use case, it should be handled in gocd-cli. Although adding this as an option and making it more available is a good idea!
The more pythonic way would be to have it as an argument with a default value, as the options = {} pattern can be handled completely with keyword arguments (which have been part of Python for a long time). :)


Two transformation functions do not return the transformed dictionary

Summary
While running a transformation function named remove_doi_slots from within a Python notebook that imports the containing Python class from the nmdc-schema Python package on PyPI, Python raised an AttributeError exception because a value of None doesn't have an attribute named get.
Screenshot

Related snippets
This is where the exception was raised:
https://github.com/microbiomedata/nmdc-schema/blob/918056b61508b2094433abb15fbb0e1578fd014f/nmdc_schema/migration_recursion.py#L382-L384
These two transformation functions don't return the transformed dictionary (i.e. they implicitly return None since they don't have return statements):
https://github.com/microbiomedata/nmdc-schema/blob/918056b61508b2094433abb15fbb0e1578fd014f/nmdc_schema/migration_recursion.py#L316-L327
https://github.com/microbiomedata/nmdc-schema/blob/918056b61508b2094433abb15fbb0e1578fd014f/nmdc_schema/migration_recursion.py#L368-L376
As a result, transformation functions "further down the pipeline" won't receive a dictionary as input.
Proposal
End each transformation function with:
return study

As a short-term workaround, in the notebook, I ignored the return values after confirming (by reviewing the source code) all the transformation functions modify the dictionary "in place."

I created the following PR which contains the permanent fix: https://github.com/microbiomedata/nmdc-schema/pull/1312

@turbomam Yes! I just approved the PR. I think you already changed it? Or @eecavanna did. Thanks for the quick fix. Sorry about this.


RestClient uses the deprecated registration_ids message property

The sender in the rest client uses "registration_ids" instead of "to" when sending a single message.
In the target section of the downstream doc this field is said to be deprecated for general use.

Additionally, because the "to" field is unsupported the rest-client can't be used to send topic messages.

registration_ids is not deprecated.

@kroikie
Then what does "Though for general purposes it is deprecated, you can use registration_ids as a target for multicast messages to more than one device (up to 1000)." mean on https://developers.google.com/cloud-messaging/concept-options#notifications_and_data_messages?

Thanks @secondsun for the heads up on that, these docs are misleading and should be clearer, but registration_ids is not deprecated.

@kroikie Gotcha. Where is the issues page for docs?  I would like to file/track this bug there.

@secondsun we have an internal issue open for this. In the future, if you want to send feedback about the docs you can use the Send Feedback button that you can find on the right of the docs' navigation bar.
GCM doesn't have a public issue tracker (this one is not meant to be for gcm product or docs, just for the content of this repo).


Export Calendar View Content to Calendar App Via .ics Subscription

Parcel has this feature that allows me to view my upcoming deliveries through the Calendar app as it provides date information for intended receipt of a package. However, this is accomplished through their parcel.app website.

I think *arr already supply calendar links.

Ah shit, I gotta find out where this is then when I get my server back up. Thanks!


[BUG] After the last update 3.0.8 I can no longer convert audio

After the last update, when I record and try to covert audio I got this error
" File "H:\A.I. Software\Apollo RVC\Applio\env\lib\site-packages\gradio\processing_utils.py", line 102, in hash_file
with open(file_path, "rb") as f:
FileNotFoundError: [Errno 2] No such file or directory: 'H:\A.I. Software\Apollo RVC\Applio\assets\audios\2024-02-29_07-34-57_output.wav'"

Yeah, I was just about to report the same issue. Bummer.

me too

Duplicated https://github.com/IAHispano/Applio/issues/214


siebel tech ref updates

@MandiOhlinger,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-oracle-database/use-the-servicemodel-metadata-utility-with-the-oracle-db-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/TOC.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-siebel/configure-a-port-using-the-wcf-custom-adapter-and-siebel-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/configure-a-port-using-the-wcf-siebel-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/configure-the-soap-action-for-siebel.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/glossary9.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/messages-and-message-schemas-for-siebel-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/metadata-node-ids1.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/microsoft-biztalk-adapter-for-siebel-ebusiness-applications-developer-reference.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-siebel/microsoft-biztalk-adapter-for-siebel-ebusiness-applications-documentation.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/origTOC.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/technical-reference-for-the-siebel-adapter.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-siebel/troubleshoot-operational-issues-with-the-siebel-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/use-the-servicemodel-metadata-utility-with-the-siebel-adapter.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-oracle-database/use-the-servicemodel-metadata-utility-with-the-oracle-db-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/TOC.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-siebel/configure-a-port-using-the-wcf-custom-adapter-and-siebel-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/configure-a-port-using-the-wcf-siebel-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/configure-the-soap-action-for-siebel.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/glossary9.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/messages-and-message-schemas-for-siebel-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/metadata-node-ids1.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/microsoft-biztalk-adapter-for-siebel-ebusiness-applications-developer-reference.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-siebel/microsoft-biztalk-adapter-for-siebel-ebusiness-applications-documentation.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/origTOC.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/technical-reference-for-the-siebel-adapter.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-siebel/troubleshoot-operational-issues-with-the-siebel-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-siebel/use-the-servicemodel-metadata-utility-with-the-siebel-adapter.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Remove api, lib, domain from global typings

Listed namespaces will be defined in application typings
Closes: https://github.com/metarhia/impress/issues/1376

[x] tests and linter show no problems (npm t)
[x] code is properly formatted (npm run fmt)

Landed in https://github.com/metarhia/impress/commit/bac94a68f944deda71ea062795e712df0ec8dca9


Blog: May heartbeat

Publish today? 😬. If not, tomorrow, but one item will need to be dropped.

[x] Header Image correct
[x] There are no grammatical errors, jargon, or obvious stylistic issues. (For reviewer)
[x] Have images been run through tiny.png?
[x] Are all lines 80 characters or less?
[x] Are Oxford commas observed?
[x] Content Creator has done a complete review for typos/language after taking a break from content
[ ] links checked in piece
[x] Have reviewed what the piece looks like on your own machine using yarn develop
[x] Needs a Twitter link

@julieg18 @rogermparent Does this new gatsby thing check the links, or is it turned off and I need to go through them one by one?

Unfortunately, our link checker is tied to the Heroku deploys and hasn't been updated to work with Gatsby Cloud since we had thought the Heroku issue was going to be more temporary than it has turned out to be. I'll locally run a check on this PR's diff so you don't have to do so manually.

Sorry for the delay! Here's the check.
yarn link-check-diff -f -r localhost:3000
yarn run v1.22.18
$ repo-link-check -c config/link-check/config.yml -d master -f -r localhost:3000

content/blog/2022-05-16-may-22-heartbeat.md

https://dvc.org/doc/start/visualization (404)
https://www.udemy.com/course/dvc-and-git-for-data-science/ (403)

This can also be done locally on your end with yarn link-check-diff -f (-f to only show failing links), but I took it on myself just to ensure

this hacky library still works like this
the results are interpreted in a useful way as quickly as possible

I'll make inline comments on what changes are needed

Can I get approval on this so it can be merged? It's ready. @shcheklein @flippedcoder @rogermparent


Apply personalization on portlet chrome title

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines

Description of change
History in #2283 .
Personalization is now applied to Portlet chrome titles.

@cbeach47 could you run ./gradlew goJF?

ah yes thx @ChristianMurphy


Update the Multiplexer Docs for Multplexed HTTPS Connections

This updates the Multiplexer docs to describe the need for remap.config
entries for the multiplexed hosts. It also describes how these
remap.config rules can be used to establish HTTPS requests to those
hosts.

In case it's helpful, you can view the rendered docs from the github PR job here:
https://jenkins.trafficserver.org/job/Github_Builds/job/docs/156/artifact/output/8440/docbuild/html/admin-guide/plugins/multiplexer.en.html

Cherry-picked to v9.2.x


[DNM] Use imagen's new Node::Base#human_name when formatting

Blocked by:

[ ] Releasing updated version of imagen

Things to consider:

[ ] Adding a test that would faild shall a method that does not exists be used in Undercover::Formatter

resolves #4

Released imagen 0.1.1 to rubygems 🎉

@grodowski ready to be 👀 at

Thx! 👏


Wrong Surburb

Ballygall should not be in the address for 9PR3+25 Finglas East, Ballygall, Dublin. The address is "Finglas East, Dublin 11".

This one I think I've tracked down - it's not when you search for the plus code, but it is what is displayed on some businesses in Google Maps. I'll forward it on to the team responsible for formatting addresses.


Unable to replicate Database limitation

When is not finding a bug a bad thing?  When the bug is in our limitation page.
I tried to exercise the bug using an example from a sqlite tutorial.  No issues were found other than cygwin does not pass environment variables.
import os
import jpype
import jpype.imports

jpype.startJVM(jpype.getDefaultJVMPath(),'-Djava.io.tmpdir=%s'%os.environ['USERPROFILE'], classpath="sqlite-jdbc-<IP_ADDRESS>.jar")

import java.lang
from java.lang import Class
from java.util import Properties
from java.sql import Connection, DriverManager, SQLException

cls=Class.forName("org.sqlite.JDBC").newInstance();
connection = DriverManager.getConnection("jdbc:sqlite:testdb.db");

Can you reproduce it with the the bug-loaded 0.6.2 version?

I tried it with JPype 0.6.2 at one point and couldn't get it there either.  This is my second bite at the apple.. However, I believe this is just like the forName issue.  When calling a static class method that accesses the classloader, if called from within JPype it gets the system Boot ClassLoader (the one used to load java.lang.*) rather than the running SystemClassLoader.  The boot loader doesn't know anything about the jars that have been loaded, so it just returns ClassNotFound.  The problem with replicating it is that it likely is tied not just to our version but rather to the JVM and which path in the code the call hits.  Class forName always hits the bug, but I don't know the magic required to make DriverManager hit the bug.
My plan is that given that this particular call structure (call a static method that accesses ClassLoader) is a really rare pattern, I would just add a JPype class customizer that forwards the call to a JPype internal call where I can execute the method with the given arguments.  As I am calling from within a Java class method the ClassLoader would be correct.  The limitation would still exist because I am just removing the common cases that hit the bug.

Fixed by #509


JSON Formatted Output Support

Description of the new feature/enhancement
To enable automation and consumption via other tools, it'd be great if current and future commands supported a JSON output mode.

Modern-day Windows command line apps output structured objects. These can already be converted to JSON, Excel, CSV, or whatever other format is preferred. The issue is that winget doesn't output any structured data. See #196

@mikemaccana As mentioned on the other two issues, PowerShell isn't available in all Windows SKUs which this is targeting. For native PowerShell support, you're looking for https://github.com/microsoft/winget-cli/issues/221.

@RichiCoder1 Could you list all target SKUs and/or a link to the requirements spec, please?

It's been mentioned multiple times across multiple sources:

https://github.com/microsoft/winget-cli/issues/221#issuecomment-632985508
https://twitter.com/richturn_ms/status/1262973495559876608?s=20

@RichiCoder1 I'm going through the backlog as a part of our planning exercise for the next few milestones. I'm going to close this as a Duplicate of #221.

I'm cool with that as long as the ultimate functionality is still flexible enough to be consumed from other tools

Yes, that is the intent. Rather than building some kind of --output-JSON flag, the native PowerShell implementation will provide objects that may be used, and will not have the truncated output string behavior currently exhibited in the winget.exe client.

Woo native powershell implementation! That’s exactly what I personally
wanted.
On Fri, 6 Aug 2021 at 18:42, denelon @.***> wrote:

Yes, that is the intent. Rather than building some kind of --output-JSON
flag, the native PowerShell implementation will provide objects that may be
used, and will not have the truncated output string behavior currently
exhibited in the winget.exe client.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/winget-cli/issues/184#issuecomment-894415550,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABKEMVUDJYX6DY7FV2S6V3T3QNJNANCNFSM4NFFGNDQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

I'm going to re-open this issue. It's not high-priority (unless we see a lot of 👍) since we have the option in PowerShell, but I can see value in what is being asked for.
We still have more work to completely move everything the CLI is calling into the COM APIs, and once that's done, providing some kind of output type/format "should" be a bit easier to implement.

I'm going to re-open this issue. It's not high-priority (unless we see a lot of 👍) since we have the option in PowerShell, but I can see value in what is being asked for.
We still have more work to completely move everything the CLI is calling into the COM APIs, and once that's done, providing some kind of output type/format "should" be a bit easier to implement.

I'd like to note one thing in reference to powershell. Until the winget powershell module can be used in system context there is a gap in functionality that could be filled if winget output could be json formatted. That would make converting winget output to a powershell object very easy.

Can we get an update on this?  It would be a very beneficial feature to output structured data like most other modern cli's.

Hey everyone, we've been publishing the Microsoft.WinGet.Client PowerShell module for the last several months with each WinGet release. It now works on Windows PowerShell and it works in system context (depending on the installer one is trying to use, and the scope is "System").


[QUESTION] How to use Library with AWS Lambda under JAVA

Include kinesis-video-stream-producer library in JAVA AWS LAmbda project
Hello,
I build these library under an EC2 instance from "amzn-ami-hvm-2<IP_ADDRESS>81129-x86_64-gp2" which is the environment from AWS lambda. After this I try to add the resulted .so file to my aws lambda java project by including it into the Library path. But when i upload it to Lambda it says "unsatisfied Link error". Do you have an Idea why this is not working?
Best regards Julia

Can you run ldd on the so file to see what libraries it needs to link to?  Here is an example we have using the C library in Java with JNI:  https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-java
The readme in the "Prerequisites" section explains if the pre-build libs don't work, how you can build them yourself.
In particular you'll find the .so files here for various platforms: https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-java/tree/master/src/main/resources/lib

I am going to close this issue as there are no action items. Please cut a new issue with more scoped questions or if you have an issue then please provide detailed information and the verbose logs.


[FR] Add ability to inherit starting directory when launching from the context of other apps

Description of the new feature/enhancement
Just as the title say, inherit the working directory from the context of the app that launches it if possible.
For example, Total Commander has a command line you can launch default cmd from and it will inherit current working/active directory.
Proposed technical implementation details (optional)

You can already do this with the commandline args to wt.exe. If you launch wt.exe -d . it will inherit the CWD of the caller. wt -d c:\windows\system32 and it'll launch in c:\windows\system32. Does that work for you?

Yes it works albeit not exactly the way current cmd does it.
Hmm, is there a way to set config up so if Terminal is called directly via shortcut on desktop or tile in Start it will use startingDirectory, otherwise, it will use -d . by default. Basically, is there way to somehow distinguish context?
I know I can use -d . as a default startup command but this will apply to every single launch, which is not always desirable.

Unfortunately, no. There's no good way to distinguish between those types of launches. #3547, https://github.com/microsoft/terminal/issues/878#issuecomment-538511693 and https://github.com/microsoft/terminal/issues/878#issuecomment-579508860 have more details.

At least you could have alias -d . to empty -d or another flag that will do -d . automatically to reduce the crumblesomeness of the approach.


Unit conversion is not adhering to the specification

Our SDK performs unit equivalency for syntactic date units by normalizing them immediately to their UCUM counterparts.
For example, CqlDate line 208
This behavior is contrary to the Author's Guide §4.2.1 Quantities.
In all cases, we should preserve the original unit and instead whenever it is required to compare units as equal or equivalent, we should invoke a not yet implemented UnitComparer that will compare UCUM and syntactic units per the specification.
Here's some CQL that could reproduce it:
define function "Is year precision"(quantity System.Quantity): quantity.unit = 'a'
define "Year equal to 'a'": "Is year precision"(1 year)

In our current implementation, Year not equal to 'a' returns true where pursuant to the specification, it should return false:

1 year is not equal (=) to 1 'a' (defined in UCUM as 365.25 'd'), but it is equivalent (~) to 1 'a'.

Note:
define "Alpha": 1 day = 1 'd'
define "Beta": (1 day).unit = 'd'

"Alpha" is true in both the JavaScript and Java engines.
"Beta" is false in both the JavaScript and Java engines.
My proposed fix for this problem would result in "Beta" returning true, since we would do all unit comparisons with unit comparers, and day would be equal to 'd'.
Relevant zulip discussion thread here.

That's right, in the current SDK Quantity I do not normalize, but I have instead introduced a system specifically for calendar durations (since they don't exist in UCUM).
https://github.com/FirelyTeam/firely-net-sdk/blob/develop/src/Hl7.Fhir.Base/ElementModel/Types/Quantity.cs
   public static Quantity ForCalendarDuration(decimal value, string calendarUnit)
        {
            return calendarUnit is not null
                ? new Quantity(value, calendarUnit, QuantityUnitSystem.CalendarDuration)
                : throw new ArgumentNullException(nameof(calendarUnit));
        }

Here, we introduced a QuantityUnitSystem.CalendarDuration - which also means that this CQL Quantity type can have a system that is not UCUM.
This way, I don't have to normalize immediately, and can keep track of the "actual" unit.

Maybe we should use this system for it, which is specifically for calendar units: https://build.fhir.org/ig/HL7/FHIRPath/CodeSystem-calendar-units.html


problem GETing endpoint https://api.ring.com/clients_api/

Hi,
i get these error trying to start the ring instance:

ring.0
2019-03-08 17:41:12.453
info
Could not get ring instance in method getRing(). Error: ring gave a seemingly valid authentication/authorisation, but the failed --caused-by-> problem GETing endpoint https://api.ring.com/clients_api/

ring.0 | 2019-03-08 17:40:10.021 | info | Could not get ring instance in method getRing(). Error: ring gave a seemingly valid authentication/authorisation, but the failed --caused-by-> problem GETing endpoint https://api.ring.com/clients_api/
ring.0 | 2019-03-08 17:39:52.447 | info | Could not get ring instance in method getRing(). Error: ring gave a seemingly valid authentication/authorisation, but the failed --caused-by-> problem GETing endpoint https://api.ring.com/clients_api/
ring.0 | 2019-03-08 17:39:50.029 | info | Starting Adapter ring.0 in version 1.0.2
ring.0 | 2019-03-08 17:39:50.028 | info | starting. Version 1.0.2 in
/opt/iobroker/node_modules/iobroker.ring, node: v8.14.0

I have the same problem. I cannot connect with the ring iPhone eather.

Okay, ring app is running now. But I got still the connection errors with the adapter. I talked to ring.com . They do not have connections problems. Probably they changed the authorisation routine. Unfortunately there is no official ring.com API.

same as here... the doorbell works fine, ifft works also with the same doorbell but the adapter cant connect

did you try these:
https://ring.com/partners
?

Yes I tried https://ring.com/partners . It works without problems.
I will change the API in the ioBroker ring Adapter too doorbot. This API still works. I need a few days to change everything. It is a lot of work

I changed everything :-) It would be great if you could the new Version of the ring Adapter. You have to load it by the git url in ioBroker : https://github.com/schmupu/ioBroker.ring

New Version works more or less...
Could not get health for the Chime. (?)
Seems to restart after a few tries.

Hmm, ich habe leider keinen chime zum Testen. Ich schaue in den source Code ob der Fehler sichtbar ist

Wird chime überhaupt nicht erkannt?

So schaut es im Log aus:

ring.0
2019-03-09 15:05:56.537
info
Could not get Health for 5359415 in getHealthSummarie(id). Could not  get Health for [object Object] in getHealth(id). Error: API returned  Status Code 410

ring.0
2019-03-09 15:05:55.485
info
Starting Ring Device for Id 5359415

ring.0
2019-03-09 15:05:52.567
info
Starting Ring Device for Id 5359409

ring.0
2019-03-09 15:04:49.499
info
Could not get Health for 5359415 in getHealthSummarie(id). Could not  get Health for [object Object] in getHealth(id). Error: API returned  Status Code 410

ring.0
2019-03-09 15:04:48.426
info
Starting Ring Device for Id 5359415

ring.0
2019-03-09 15:04:45.755
info
Starting Ring Device for Id 5359409

ring.0
2019-03-09 15:04:27.569
info
Could not get Health for 5359415 in getHealthSummarie(id). Could not  get Health for [object Object] in getHealth(id). Error: API returned  Status Code 410

ring.0
2019-03-09 15:04:26.210
info
Starting Ring Device for Id 5359415

ring.0
2019-03-09 15:04:16.270
info
Starting Ring Device for Id 5359409

ring.0
2019-03-09 15:04:12.517
info
Starting Adapter ring.0 in version 1.0.3

ring.0
2019-03-09 15:04:12.236
info
starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.ring, node: v8.15.0

host.Pi-Master
2019-03-09 15:04:10.966
info
instance system.adapter.ring.0 started with pid 19459

host.Pi-Master
2019-03-09 15:04:10.922
info
object change system.adapter.ring.0

Chime (die ...15) wird erkannt und korrekt benannt etc.
Ring-Doorbell (die ...09) ebenfalls.

Bin unterwegs, schaue heute Abend. Ich hoffe du kannst mit beim Testen helfen?

Gerne.
Aber heute schaffe ich nichts mehr... ;-)

Ich habe noch ein paar Debug Meldungen eingebaut. Du musst bitte nochmals die Version des Ring Adapters unter Git installieren  https://github.com/schmupu/ioBroker.ring . Anschließend bitte unter Instanzen auf Expertenmodus gehen und dann den Ring Adapter auf "debug" Modus erstellen.
Suche im Logfile nach folgenden Wörtern:

Devices:
Chimes:
Health ID:
Health:
Health Summary ID:
Health Summary Doorbell:
Health Summary:

Ich benötige davon den Output und schicke es mir an<EMAIL_ADDRESS>. Du kannst mir aber auch gerne Dein komplettes Logfiles schicken. Lösche bitte umbedingt Dein Passwort vorher aus dem Logfile.

Du hast Mail.
Hoffe das ist alles lesbar soweit.
„Muss“ das zur Zeit alles mit dem Handy/iPhone machen. :-(

Noch ist keine Email mit  Logfiles angekommen. Werde jetzt aufs Rennrad steigen (Sonne scheint in Hamburg). Dann werde ich schauen. Ich hoffe die API unterstützt den chime anständig.

dann lieber auf deutsch :) sorry unser kleiner war krank und ich hatte keine fürs smarthome...
ich hab den neuen adapter grad instaliert, der läuft aber nicht....
`

ring.0
2019-03-11 12:35:32.322
info
Could not get all doorbell devices in getAllRingsDevices(). Could not get device instance in method getDevices(). Error: Api failed to return an authentication_token

ring.0
2019-03-11 12:34:30.278
info
Could not get all doorbell devices in getAllRingsDevices(). Could not get device instance in method getDevices(). Error: Api failed to return an authentication_token

ring.0
2019-03-11 12:33:28.869
info
Could not get all doorbell devices in getAllRingsDevices(). Could not get device instance in method getDevices(). Error: Api failed to return an authentication_token

ring.0
2019-03-11 12:33:11.923
info
Could not get all doorbell devices in getAllRingsDevices(). Could not get device instance in method getDevices(). Error: Api failed to return an authentication_token

ring.0
2019-03-11 12:33:10.324
info
Starting Adapter ring.0 in version 1.0.3

ring.0
2019-03-11 12:33:10.324
info
starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.ring, node: v8.14.0

ring.0
2019-03-11 12:33:07.144
info
Closing Adapter

ring.0
2019-03-11 12:32:54.988
info
Could not get all doorbell devices in getAllRingsDevices(). Could not get device instance in method getDevices(). Error: Api failed to return an authentication_token

ring.0
2019-03-11 12:32:38.298
info
Could not get all doorbell devices in getAllRingsDevices(). Could not get device instance in method getDevices(). Error: Api failed to return an authentication_token

ring.0
2019-03-11 12:32:36.534
info
Starting Adapter ring.0 in version 1.0.3

ring.0
2019-03-11 12:32:36.520
info
starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.ring, node: v8.14.0

ring.0
2019-03-11 12:32:33.366
info
Closing Adapter

ring.0
2019-03-11 12:32:33.359
info
Closing Adapter

ring.0
2019-03-11 12:32:31.892
info
Could not get all doorbell devices in getAllRingsDevices(). Could not get device instance in method getDevices(). Error: Api failed to return an authentication_token

ring.0
2019-03-11 12:32:15.647
info
Could not get all doorbell devices in getAllRingsDevices(). Could not get device instance in method getDevices(). Error: Api failed to return an authentication_token

ring.0
2019-03-11 12:32:13.611
info
Starting Adapter ring.0 in version 1.0.3

ring.0
2019-03-11 12:32:13.597
info
starting.

Die app sagt auch nichts über den Systemzustand von Ring (normal alles grün, jetzt nur weißer bildschirm...)

Ich gehe davon aus, meine Mail ist nicht angekommen?
Hier nochmal ein kleiner Auszug aus dem Log:

2019-03-11 12:40:09.464  - info: ring.0 Starting Ring Device for Id 5359415
2019-03-11 12:40:09.465  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"xxx","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:09.808  - debug:  ring.0 Devices:  {"doorbots":[{"id":5359409,"description":"Haustür","device_id":"e04f434d999d","time_zone":"Europe/Berlin","subscribed":true,"subscribed_motions":true,"battery_life":4100,"external_connection":false,"firmware_version":"Up  to  Date","kind":"lpd_v2","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"enable_vod":true,"motion_zones":{"enable_audio":false,"active_motion_filter":1,"sensitivity":5,"advanced_object_settings":{"human_detection_confidence":{"day":0.9,"night":0.9},"motion_zone_overlap":{"day":0.3,"night":0.5},"object_time_overlap":{"day":0.5,"night":1.5},"object_size_minimum":{"day":0.05,"night":0.09},"object_size_maximum":{"day":0.6,"night":0.6}},"zone1":{"name":"Zone   1","state":2,"vertex1":{"x":0,"y":0},"vertex2":{"x":0.36748746,"y":0},"vertex3":{"x":0.23873124,"y":0.46172106},"vertex4":{"x":0.5707414,"y":0.4913291},"vertex5":{"x":0.69699496,"y":0.6542746},"vertex6":{"x":0.91235393,"y":0.7344214},"vertex7":{"x":0.875626,"y":1},"vertex8":{"x":0,"y":1}},"zone2":{"name":"Zone   2","state":2,"vertex1":{"x":0.74144405,"y":0},"vertex2":{"x":1,"y":0},"vertex3":{"x":1,"y":0.33412462},"vertex4":{"x":1,"y":1},"vertex5":{"x":0.8194908,"y":1},"vertex6":{"x":0.88230383,"y":0.7400594},"vertex7":{"x":0.890025,"y":0.5412463},"vertex8":{"x":0.8833473,"y":0.34718102}},"zone3":{"name":"Zone   3","state":0,"vertex1":{"x":0,"y":0},"vertex2":{"x":0,"y":0},"vertex3":{"x":0,"y":0},"vertex4":{"x":0,"y":0},"vertex5":{"x":0,"y":0},"vertex6":{"x":0,"y":0},"vertex7":{"x":0,"y":0},"vertex8":{"x":0,"y":0}}},"motion_snooze_preset_profile":"low","live_view_preset_profile":"highest","live_view_presets":["low","middle","high","highest"],"motion_snooze_presets":["none","low","medium","high"],"doorbell_volume":1,"chime_settings":{"type":0,"enable":false,"duration":10},"video_settings":{"birton":"","brightness":16,"contrast":80,"saturation":48,"ae_level":32},"motion_announcement":false,"stream_setting":0,"advanced_motion_detection_enabled":false,"advanced_motion_detection_human_only_mode":false},"features":{"motions_enabled":true,"show_recordings":true,"advanced_motion_enabled":false,"people_only_enabled":false,"shadow_correction_enabled":false,"motion_message_enabled":false,"night_vision_enabled":false},"owned":true,"alerts":{"connection":"online"},"motion_snooze":null,"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"},"night_mode_status":"false"}],"authorized_doorbots":[],"chimes":[{"id":5359415,"description":"Flur","device_id":"c8fd1906ac0f","time_zone":"Europe/Berlin","firmware_version":"Up  to  Date","kind":"chime","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"volume":5,"ding_audio_user_id":"ring","ding_audio_id":"xxxfa2-a83d-e5a4-5af2-5646cb2449be","motion_audio_user_id":"ring","motion_audio_id":"xxxe86-f43b-738f-7287-5693688ec52b"},"features":{"ringtones_enabled":true},"owned":true,"alerts":{"connection":"online"},"do_not_disturb":{"seconds_left":0},"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"}}],"stickup_cams":[],"base_stations":[],"beams_bridges":[],"beams":[]}
2019-03-11 12:40:09.809  - debug:  ring.0 Doorbell:  {"id":5359409,"description":"Haustür","device_id":"e04f434d999d","time_zone":"Europe/Berlin","subscribed":true,"subscribed_motions":true,"battery_life":4100,"external_connection":false,"firmware_version":"Up  to  Date","kind":"lpd_v2","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"enable_vod":true,"motion_zones":{"enable_audio":false,"active_motion_filter":1,"sensitivity":5,"advanced_object_settings":{"human_detection_confidence":{"day":0.9,"night":0.9},"motion_zone_overlap":{"day":0.3,"night":0.5},"object_time_overlap":{"day":0.5,"night":1.5},"object_size_minimum":{"day":0.05,"night":0.09},"object_size_maximum":{"day":0.6,"night":0.6}},"zone1":{"name":"Zone   1","state":2,"vertex1":{"x":0,"y":0},"vertex2":{"x":0.36748746,"y":0},"vertex3":{"x":0.23873124,"y":0.46172106},"vertex4":{"x":0.5707414,"y":0.4913291},"vertex5":{"x":0.69699496,"y":0.6542746},"vertex6":{"x":0.91235393,"y":0.7344214},"vertex7":{"x":0.875626,"y":1},"vertex8":{"x":0,"y":1}},"zone2":{"name":"Zone   2","state":2,"vertex1":{"x":0.74144405,"y":0},"vertex2":{"x":1,"y":0},"vertex3":{"x":1,"y":0.33412462},"vertex4":{"x":1,"y":1},"vertex5":{"x":0.8194908,"y":1},"vertex6":{"x":0.88230383,"y":0.7400594},"vertex7":{"x":0.890025,"y":0.5412463},"vertex8":{"x":0.8833473,"y":0.34718102}},"zone3":{"name":"Zone   3","state":0,"vertex1":{"x":0,"y":0},"vertex2":{"x":0,"y":0},"vertex3":{"x":0,"y":0},"vertex4":{"x":0,"y":0},"vertex5":{"x":0,"y":0},"vertex6":{"x":0,"y":0},"vertex7":{"x":0,"y":0},"vertex8":{"x":0,"y":0}}},"motion_snooze_preset_profile":"low","live_view_preset_profile":"highest","live_view_presets":["low","middle","high","highest"],"motion_snooze_presets":["none","low","medium","high"],"doorbell_volume":1,"chime_settings":{"type":0,"enable":false,"duration":10},"video_settings":{"birton":"","brightness":16,"contrast":80,"saturation":48,"ae_level":32},"motion_announcement":false,"stream_setting":0,"advanced_motion_detection_enabled":false,"advanced_motion_detection_human_only_mode":false},"features":{"motions_enabled":true,"show_recordings":true,"advanced_motion_enabled":false,"people_only_enabled":false,"shadow_correction_enabled":false,"motion_message_enabled":false,"night_vision_enabled":false},"owned":true,"alerts":{"connection":"online"},"motion_snooze":null,"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"},"night_mode_status":"false"}
2019-03-11 12:40:09.809  - debug:  ring.0 Chimes:  {"id":5359415,"description":"Flur","device_id":"c8fd1906ac0f","time_zone":"Europe/Berlin","firmware_version":"Up  to  Date","kind":"chime","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"volume":5,"ding_audio_user_id":"ring","ding_audio_id":"xxxfa2-a83d-e5a4-5af2-5646cb2449be","motion_audio_user_id":"ring","motion_audio_id":"xxxe86-f43b-738f-7287-5693688ec52b"},"features":{"ringtones_enabled":true},"owned":true,"alerts":{"connection":"online"},"do_not_disturb":{"seconds_left":0},"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"}}
2019-03-11 12:40:09.809  - debug:  ring.0 Doorbell for Id: 5359415 =  {"id":5359415,"description":"Flur","device_id":"c8fd1906ac0f","time_zone":"Europe/Berlin","firmware_version":"Up  to  Date","kind":"chime","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"volume":5,"ding_audio_user_id":"ring","ding_audio_id":"xxxfa2-a83d-e5a4-5af2-5646cb2449be","motion_audio_user_id":"ring","motion_audio_id":"xxxe86-f43b-738f-7287-5693688ec52b"},"features":{"ringtones_enabled":true},"owned":true,"alerts":{"connection":"online"},"do_not_disturb":{"seconds_left":0},"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"}}
2019-03-11 12:40:09.811  - debug: ring.0 Health Summary ID: 5359415
2019-03-11 12:40:09.812  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:10.072  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:10.197  - debug:  ring.0 Devices:  {"doorbots":[{"id":5359409,"description":"Haustür","device_id":"e04f434d999d","time_zone":"Europe/Berlin","subscribed":true,"subscribed_motions":true,"battery_life":4100,"external_connection":false,"firmware_version":"Up  to  Date","kind":"lpd_v2","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"enable_vod":true,"motion_zones":{"enable_audio":false,"active_motion_filter":1,"sensitivity":5,"advanced_object_settings":{"human_detection_confidence":{"day":0.9,"night":0.9},"motion_zone_overlap":{"day":0.3,"night":0.5},"object_time_overlap":{"day":0.5,"night":1.5},"object_size_minimum":{"day":0.05,"night":0.09},"object_size_maximum":{"day":0.6,"night":0.6}},"zone1":{"name":"Zone   1","state":2,"vertex1":{"x":0,"y":0},"vertex2":{"x":0.36748746,"y":0},"vertex3":{"x":0.23873124,"y":0.46172106},"vertex4":{"x":0.5707414,"y":0.4913291},"vertex5":{"x":0.69699496,"y":0.6542746},"vertex6":{"x":0.91235393,"y":0.7344214},"vertex7":{"x":0.875626,"y":1},"vertex8":{"x":0,"y":1}},"zone2":{"name":"Zone   2","state":2,"vertex1":{"x":0.74144405,"y":0},"vertex2":{"x":1,"y":0},"vertex3":{"x":1,"y":0.33412462},"vertex4":{"x":1,"y":1},"vertex5":{"x":0.8194908,"y":1},"vertex6":{"x":0.88230383,"y":0.7400594},"vertex7":{"x":0.890025,"y":0.5412463},"vertex8":{"x":0.8833473,"y":0.34718102}},"zone3":{"name":"Zone   3","state":0,"vertex1":{"x":0,"y":0},"vertex2":{"x":0,"y":0},"vertex3":{"x":0,"y":0},"vertex4":{"x":0,"y":0},"vertex5":{"x":0,"y":0},"vertex6":{"x":0,"y":0},"vertex7":{"x":0,"y":0},"vertex8":{"x":0,"y":0}}},"motion_snooze_preset_profile":"low","live_view_preset_profile":"highest","live_view_presets":["low","middle","high","highest"],"motion_snooze_presets":["none","low","medium","high"],"doorbell_volume":1,"chime_settings":{"type":0,"enable":false,"duration":10},"video_settings":{"birton":"","brightness":16,"contrast":80,"saturation":48,"ae_level":32},"motion_announcement":false,"stream_setting":0,"advanced_motion_detection_enabled":false,"advanced_motion_detection_human_only_mode":false},"features":{"motions_enabled":true,"show_recordings":true,"advanced_motion_enabled":false,"people_only_enabled":false,"shadow_correction_enabled":false,"motion_message_enabled":false,"night_vision_enabled":false},"owned":true,"alerts":{"connection":"online"},"motion_snooze":null,"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"},"night_mode_status":"false"}],"authorized_doorbots":[],"chimes":[{"id":5359415,"description":"Flur","device_id":"c8fd1906ac0f","time_zone":"Europe/Berlin","firmware_version":"Up  to  Date","kind":"chime","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"volume":5,"ding_audio_user_id":"ring","ding_audio_id":"xxxfa2-a83d-e5a4-5af2-5646cb2449be","motion_audio_user_id":"ring","motion_audio_id":"xxxe86-f43b-738f-7287-5693688ec52b"},"features":{"ringtones_enabled":true},"owned":true,"alerts":{"connection":"online"},"do_not_disturb":{"seconds_left":0},"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"}}],"stickup_cams":[],"base_stations":[],"beams_bridges":[],"beams":[]}
2019-03-11 12:40:10.198  - debug:  ring.0 Doorbell:  {"id":5359409,"description":"Haustür","device_id":"e04f434d999d","time_zone":"Europe/Berlin","subscribed":true,"subscribed_motions":true,"battery_life":4100,"external_connection":false,"firmware_version":"Up  to  Date","kind":"lpd_v2","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"enable_vod":true,"motion_zones":{"enable_audio":false,"active_motion_filter":1,"sensitivity":5,"advanced_object_settings":{"human_detection_confidence":{"day":0.9,"night":0.9},"motion_zone_overlap":{"day":0.3,"night":0.5},"object_time_overlap":{"day":0.5,"night":1.5},"object_size_minimum":{"day":0.05,"night":0.09},"object_size_maximum":{"day":0.6,"night":0.6}},"zone1":{"name":"Zone   1","state":2,"vertex1":{"x":0,"y":0},"vertex2":{"x":0.36748746,"y":0},"vertex3":{"x":0.23873124,"y":0.46172106},"vertex4":{"x":0.5707414,"y":0.4913291},"vertex5":{"x":0.69699496,"y":0.6542746},"vertex6":{"x":0.91235393,"y":0.7344214},"vertex7":{"x":0.875626,"y":1},"vertex8":{"x":0,"y":1}},"zone2":{"name":"Zone   2","state":2,"vertex1":{"x":0.74144405,"y":0},"vertex2":{"x":1,"y":0},"vertex3":{"x":1,"y":0.33412462},"vertex4":{"x":1,"y":1},"vertex5":{"x":0.8194908,"y":1},"vertex6":{"x":0.88230383,"y":0.7400594},"vertex7":{"x":0.890025,"y":0.5412463},"vertex8":{"x":0.8833473,"y":0.34718102}},"zone3":{"name":"Zone   3","state":0,"vertex1":{"x":0,"y":0},"vertex2":{"x":0,"y":0},"vertex3":{"x":0,"y":0},"vertex4":{"x":0,"y":0},"vertex5":{"x":0,"y":0},"vertex6":{"x":0,"y":0},"vertex7":{"x":0,"y":0},"vertex8":{"x":0,"y":0}}},"motion_snooze_preset_profile":"low","live_view_preset_profile":"highest","live_view_presets":["low","middle","high","highest"],"motion_snooze_presets":["none","low","medium","high"],"doorbell_volume":1,"chime_settings":{"type":0,"enable":false,"duration":10},"video_settings":{"birton":"","brightness":16,"contrast":80,"saturation":48,"ae_level":32},"motion_announcement":false,"stream_setting":0,"advanced_motion_detection_enabled":false,"advanced_motion_detection_human_only_mode":false},"features":{"motions_enabled":true,"show_recordings":true,"advanced_motion_enabled":false,"people_only_enabled":false,"shadow_correction_enabled":false,"motion_message_enabled":false,"night_vision_enabled":false},"owned":true,"alerts":{"connection":"online"},"motion_snooze":null,"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"},"night_mode_status":"false"}
2019-03-11 12:40:10.199  - debug:  ring.0 Chimes:  {"id":5359415,"description":"Flur","device_id":"c8fd1906ac0f","time_zone":"Europe/Berlin","firmware_version":"Up  to  Date","kind":"chime","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"volume":5,"ding_audio_user_id":"ring","ding_audio_id":"xxxfa2-a83d-e5a4-5af2-5646cb2449be","motion_audio_user_id":"ring","motion_audio_id":"xxxe86-f43b-738f-7287-5693688ec52b"},"features":{"ringtones_enabled":true},"owned":true,"alerts":{"connection":"online"},"do_not_disturb":{"seconds_left":0},"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"}}
2019-03-11 12:40:10.199  - debug:  ring.0 Doorbell for Id: 5359415 =  {"id":5359415,"description":"Flur","device_id":"c8fd1906ac0f","time_zone":"Europe/Berlin","firmware_version":"Up  to  Date","kind":"chime","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"volume":5,"ding_audio_user_id":"ring","ding_audio_id":"xxxfa2-a83d-e5a4-5af2-5646cb2449be","motion_audio_user_id":"ring","motion_audio_id":"xxxe86-f43b-738f-7287-5693688ec52b"},"features":{"ringtones_enabled":true},"owned":true,"alerts":{"connection":"online"},"do_not_disturb":{"seconds_left":0},"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"}}
2019-03-11 12:40:10.199  - debug:  ring.0 Health Summary Doorbell:  {"id":5359415,"description":"Flur","device_id":"c8fd1906ac0f","time_zone":"Europe/Berlin","firmware_version":"Up  to  Date","kind":"chime","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"volume":5,"ding_audio_user_id":"ring","ding_audio_id":"xxxfa2-a83d-e5a4-5af2-5646cb2449be","motion_audio_user_id":"ring","motion_audio_id":"xxxe86-f43b-738f-7287-5693688ec52b"},"features":{"ringtones_enabled":true},"owned":true,"alerts":{"connection":"online"},"do_not_disturb":{"seconds_left":0},"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"}}
2019-03-11 12:40:10.199  - debug:  ring.0 Health ID:  {"id":5359415,"description":"Flur","device_id":"c8fd1906ac0f","time_zone":"Europe/Berlin","firmware_version":"Up  to  Date","kind":"chime","latitude":LAT026,"longitude":LON626,"address":"strasse  Str. 1b, ort, nds PLZ,  DE","settings":{"volume":5,"ding_audio_user_id":"ring","ding_audio_id":"xxxfa2-a83d-e5a4-5af2-5646cb2449be","motion_audio_user_id":"ring","motion_audio_id":"xxxe86-f43b-738f-7287-5693688ec52b"},"features":{"ringtones_enabled":true},"owned":true,"alerts":{"connection":"online"},"do_not_disturb":{"seconds_left":0},"stolen":false,"location_id":"xxx0k-4ishs-0","ring_id":null,"owner":{"id":4813372,"email":"email@prov.xx","first_name":"VORNAME","last_name":"NACHNAME"}}
2019-03-11 12:40:10.419  - info:  ring.0 Could not get Health for 5359415 in getHealthSummarie(id). Could  not get Health for [object Object] in getHealth(id). Error: API  returned Status Code 410
2019-03-11 12:40:11.293  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:12.522  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:13.758  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:15.257  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:16.497  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:17.739  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:18.983  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:20.192  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:21.416  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:22.651  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:23.874  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:25.166  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":"bvZJTZMKi9xxNvQk1GmR","api_version":11,"authenticating":false,"authQueue":[null],"quthQueue":[]}}
2019-03-11 12:40:25.422  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":null,"api_version":11,"authenticating":false,"authQueue":[]}}
2019-03-11 12:40:25.428  - info: host.Pi-Master object change system.adapter.ring.0
2019-03-11 12:40:25.429  - info: host.Pi-Master "system.adapter.ring.0" disabled
2019-03-11 12:40:25.430  - info: host.Pi-Master stopInstance system.adapter.ring.0
2019-03-11 12:40:25.430  - info: host.Pi-Master stopInstance system.adapter.ring.0 killing pid 16553
2019-03-11 12:40:25.424  - debug:  ring.0 Ring  {"eventEmitter":{"domain":null,"_events":{},"_eventsCount":0,"_maxListeners":100},"adapter":{"logList":["system.adapter.admin.0"],"adapterDir":"/opt/iobroker/node_modules/iobroker.ring","pack":{"_from":"https://github.com/schmupu/ioBroker.ring/tarball/master","_id":"iobroker.ring@1.0.3","_inBundle":false,"_integrity":"sha512-8uibFEDsWJ+TeJDE9fXs9YBfNo38Hn+4QVsyyf6/FG72dZiK0nY/WDikXkMZf4M2efK4J+5WPjJTTqA1tR+Czg==","_location":"/iobroker.ring","_phantomChildren":{"@types/node":"10.12.18"},"_requested":{"type":"remote","raw":"https://github.com/schmupu/ioBroker.ring/tarball/master","rawSpec":"https://github.com/schmupu/ioBroker.ring/tarball/master","saveSpec":"https://github.com/schmupu/ioBroker.ring/tarball/master","fetchSpec":"https://github.com/schmupu/ioBroker.ring/tarball/master"},"_requiredBy":["#USER","/"],"_resolved":"https://github.com/schmupu/ioBroker.ring/tarball/master","_shasum":"f23947995b40496f57a1622f257d5f7ace502bab","_spec":"https://github.com/schmupu/ioBroker.ring/tarball/master","_where":"/","author":{"name":"Thorsten Stueben","email":"thorsten@stueben.de"},"bugs":{"url":"https://github.com/schmupu/ioBroker.ring/issues"},"bundleDependencies":false,"contributors":[{"name":"Thorsten Stueben","email":"thorsten@stueben.de"}],"dependencies":{"@apollon/iobroker-tools":"git+https://github.com/schmupu/iobroker-tools.git","@iobroker/adapter-core":"^1.0.3","doorbot":"git+https://github.com/davglass/doorbot.git","events":"^3.0.0","node-schedule":"1.3.0","request":"^2.85.0","ring-api":"^3.0.7","semver":"^5.6.0"},"deprecated":false,"description":"Ring","devDependencies":{"chai":"^4.1.2","eslint":"^5.15.1","eslint-plugin-react":"^7.12.4","gulp":"^3.9.1","mocha":"^4.1.0"},"engines":{"node":">=8.0.0"},"homepage":"https://github.com/schmupu/ioBroker.ring","keywords":["ring","logic"],"license":"MIT","main":"ring.js","name":"iobroker.ring","repository":{"type":"git","url":"git+https://github.com/schmupu/ioBroker.ring.git"},"scripts":{"test":"node  node_modules/mocha/bin/mocha  --exit"},"version":"1.0.3"},"ioPack":{"common":{"name":"ring","version":"1.0.3","title":"Ring","news":{"1.0.3":{"en":"Changing  ring API. Old one did not work anymore","de":"Wechsel der ring.com  API"},"1.0.2":{"en":"More debug information","de":"Debug Ansicht  erweiteret"},"1.0.1":{"en":"Support of compact mode","de":"Compact mode  Unterstützung"},"1.0.0":{"en":"Add Ring Camera as new device","de":"Ring  Camera Unterstützung"},"0.1.3":{"en":"Update","de":"Anpassung  Fehlererkennung"},"0.1.2":{"en":"Update error handlinge","de":"Anpassung  Fehlererkennung"},"0.1.1":{"en":"A few updates","de":"Kleine  Änderungen"},"0.1.0":{"en":"First version","de":"Erste  Version"}},"titleLang":{"en":"Ring","de":"Ring","ru":"изобилующий  раковинами","pt":"Ring","nl":"schaalachtig","fr":"Ring","it":"Ring","es":"Ring","pl":"Ring"},"desc":{"en":"Ring  Adapter","de":"Ring Adapter","ru":"Шестигранный  адаптер","pt":"Adaptador Ring","nl":"Ring adapter","fr":"Adaptateur  Ring","it":"Adattatore Ring","es":"Adaptador Ring","pl":"Adapter  Ring"},"license":"MIT","authors":["Thorsten Stueben "],"platform":"Javascript/Node.js","mode":"daemon","messagebox":true,"stopBeforeUpdate":true,"subscribe":"messagebox","icon":"ring.png","materialize":true,"enabled":true,"compact":true,"extIcon":"https://raw.githubusercontent.com/schmupu/ioBroker.ring/master/admin/ring.png","keywords":["ring"],"readme":"https://github.com/schmupu/ioBroker.ring/blob/master/README.md","loglevel":"info","type":"hardware","restartAdapters":[]},"native":{"email":"email@test.foo","password":"password","timeout":5,"pollsec":15},"objects":[],"instanceObjects":[]},"name":"ring","namespace":"ring.0","users":[],"defaultHistory":null,"autoSubscribe":null,"inputCount":0,"outputCount":2,"FORBIDDEN_CHARS":{},"getPortRunning":null,"inited":true,"objects":{},"_namespaceRegExp":{},"_events":{},"_eventsCount":5,"connected":true,"states":{},"instance":0,"config":{"email":"email@prov.xx","password":"PASSWORT","timeout":5,"pollsec":15,"keys":[]},"host":"Pi-Master","common":{"name":"ring","version":"0.1.3","title":"Ring  Video Doorbell","news":{"0.1.3":{"en":"Update","de":"Anpassung  Fehlererkennung"},"0.1.2":{"en":"Update error handlinge","de":"Anpassung  Fehlererkennung"},"0.1.1":{"en":"A few updates","de":"Kleine  Änderungen"},"0.1.0":{"en":"First version","de":"Erste  Version"},"1.0.1":{"en":"Support of compact mode","de":"Compact mode  Unterstützung"},"1.0.0":{"en":"Add Ring Camera as new device","de":"Ring  Camera Unterstützung"}},"titleLang":{"en":"Ring Video  Doorbell","de":"Ring Video Doorbell","ru":"изобилующий  раковинами","pt":"Ring Video Doorbell","nl":"schaalachtig","fr":"Ring  Video Doorbell","it":"Ring Video Doorbell","es":"Ring Video  Doorbell","pl":"Ring Video Doorbell"},"desc":{"en":"Ring Video Doorbell  Adapter","de":"Ring Video Doorbell Adapter","ru":"Шестигранный  адаптер","pt":"Adaptador Ring Video Doorbell","nl":"Ring Video  Doorbell-adapter","fr":"Adaptateur Ring Video Doorbell","it":"Adattatore  Ring Video Doorbell","es":"Adaptador Ring Video Doorbell","pl":"Adapter  Ring Video Doorbell"},"license":"MIT","authors":["Thorsten Stueben "],"platform":"Javascript/Node.js","mode":"daemon","messagebox":true,"stopBeforeUpdate":true,"subscribe":"messagebox","icon":"ring.png","materialize":true,"enabled":true,"extIcon":"https://raw.githubusercontent.com/schmupu/ioBroker.ring/master/admin/ring.png","keywords":["ring"],"readme":"https://github.com/schmupu/ioBroker.ring/blob/master/README.md","loglevel":"debug","type":"hardware","restartAdapters":[],"installedVersion":"0.1.3","host":"Pi-Master","restartSchedule":"49  5 * *  *","compact":true},"mboxSubscribed":true,"log":{"level":"debug"},"version":"1.0.3"},"ring":{"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":null,"api_version":11,"authenticating":false,"authQueue":[]}},"kind":{},"checktime":1}
2019-03-11 12:40:25.426  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":null,"api_version":11,"authenticating":false,"authQueue":[]}}
2019-03-11 12:40:25.427  - debug:  ring.0 Ring:  {"auth":{"email":"email@prov.xx","password":"PASSWORT","retries":10,"userAgent":"My  User  Agent","api_version":11,"timeout":600000},"ring":{"username":"email@prov.xx","password":"PASSWORT","retries":10,"timeout":600000,"counter":0,"userAgent":"My  User  Agent","token":null,"api_version":11,"authenticating":false,"authQueue":[]}}
2019-03-11 12:40:25.444  - info: ring.0 Closing Adapter
2019-03-11 12:40:25.457  - info: ring.0 Closing Adapter
2019-03-11 12:40:25.514  - info: host.Pi-Master instance system.adapter.ring.0 terminated with code 0 (OK)
2019-03-11 12:40:33.012  - info: host.Pi-Master object change system.adapter.ring.0

Danke für das Logfile. Ich habe es mir angeschaut. Es scheint ein Fehler in der ring API zu sein. Ich gebe mal ein Issue auf.

@SoerenKaiser99, welche Ring Geräte hat du im Einsatz?
Ich denke bei dir zieht er in der Version 1.0.3 nicht die zugrundeliegende API von Github.
Kannst du dir 1.0.3 nochmals über Github laden. Im Logfile sollte jetzt stehen welche API der Adapter lädt

Die alte API funktioniert wieder. Ich denke ring.com hatte irgendetwas letzte Woche geändert und heute wieder zurückgedreht. Nun unterstützt der Adapter in der Version 1.0.3 beide APIs.
 Zur Auswahl stehen ring-api (default) oder doorbot
Wer möchte kann damit herumexperimentieren.
Ich schließe den Issue. Falls es weiterhin Probleme gibt, bitte melden
VG
Stübi

Hallo,
habe mir heute den Adapter installiert, und besitze ebenfalls einen Chime, Problem wie hier im Issue beschrieben.
Fehlermeldung: "Could not get Health for [object Object] in getHealth(id). Error: API returned Status Code 410"
Auszug Debug Log:

Could not get Health for 22624991 in getHealthSummarie(id). Could not get Health for [object Object] in getHealth(id). Error: API returned Status Code 410
ring.0	2019-03-18 23:13:41.987	debug	Health ID: {"id":22624991,"description":"Obergeschoss","device_id":"6cc374f0f565","time_zone":"Europe/Berlin","firmware_version":"Up to Date","kind":"chime","latitude":XX.XX,"longitude":6.88401,"add
ring.0	2019-03-18 23:13:41.987	debug	Health Summary Doorbell: {"id":22624991,"description":"Obergeschoss","device_id":"6cc374f0f565","time_zone":"Europe/Berlin","firmware_version":"Up to Date","kind":"chime","latitude":XX.XX,"longitude
ring.0	2019-03-18 23:13:41.987	debug	Doorbell for Id: 22624991 = {"id":22624991,"description":"Obergeschoss","device_id":"6cc374f0f565","time_zone":"Europe/Berlin","firmware_version":"Up to Date","kind":"chime","latitude":XX.XX,"longit
ring.0	2019-03-18 23:13:41.987	debug	Chimes: {"id":22624991,"description":"Obergeschoss","device_id":"6cc374f0f565","time_zone":"Europe/Berlin","firmware_version":"Up to Date","kind":"chime","latitude":XX.XX,"longitude":6.88401,"addres
ring.0	2019-03-18 23:13:41.987	debug	Doorbell: {"id":22624729,"description":"Haustür","device_id":"0c1c576d2d53","time_zone":"Europe/Berlin","subscribed":true,"subscribed_motions":true,"battery_life":"99","external_connection":false,"fir
ring.0	2019-03-18 23:13:41.986	debug	Devices: {"doorbots":[{"id":22624729,"description":"Haustür","device_id":"0c1c576d2d53","time_zone":"Europe/Berlin","subscribed":true,"subscribed_motions":true,"battery_life":"99","external_connection
ring.0	2019-03-18 23:13:41.667	debug	Ring: {"auth":{"email":"mail@gmail.com","password":"PWD!","retries":10,"userAgent":"My User Agent","api_version":11,"timeout":600000},"ring":{"username":"mail@gmail.com","password":"N
ring.0	2019-03-18 23:13:41.667	debug	Starting _event
ring.0	2019-03-18 23:13:41.610	debug	Ring: {"auth":{"email":"mail@gmail.com","password":"PWD!","retries":10,"userAgent":"My User Agent","api_version":11,"timeout":600000},"ring":{"username":"mail@gmail.com","password":"N
ring.0	2019-03-18 23:13:41.610	debug	Starting getDevices

Leider wird Chime nicht in der Ring API die Grundlage des Ring Adapters ist unterstützt. Da werde ich momentan nichts machen können.

https://github.com/davglass/doorbot/issues/43


[SUPPORT] Change the location of a hudi table in AWS ?

Tips before filing an issue

Have you gone through our FAQs?Yes

Describe the problem you faced
How can we change the location of a hudi table to new location. I've customer table that is saved at s3://aws-amazon-com/Customer/ which I want to change to  s3://aws-amazon-com/CustomerUpdated/ .
A clear and concise description of the problem.
How can we change the location of a hudi table to new location. I've customer table that is saved at s3://aws-amazon-com/Customer/ which I want to change to  s3://aws-amazon-com/CustomerUpdated/ .
To Reproduce
val partitionColumnName: String = "year"
    val hudiTableName: String = "Customer"
    val preCombineKey: String = "id"
    val recordKey = "id"
    val tablePath = "s3://aws-amazon-com/Customer/"
    val databaseName="consumer_bureau"

    val hudiCommonOptions: Map[String, String] = Map(
        "hoodie.table.name" -> hudiTableName,
        "hoodie.datasource.write.keygenerator.class" -> "org.apache.hudi.keygen.ComplexKeyGenerator",
        "hoodie.datasource.write.precombine.field" -> preCombineKey,
        "hoodie.datasource.write.recordkey.field" -> recordKey,
        "hoodie.datasource.write.operation" -> "bulk_insert",
        //"hoodie.datasource.write.operation" -> "upsert",
        "hoodie.datasource.write.row.writer.enable" -> "true",
        "hoodie.datasource.write.reconcile.schema" -> "true",
        "hoodie.datasource.write.partitionpath.field" -> partitionColumnName,
        "hoodie.datasource.write.hive_style_partitioning" -> "true",
        // "hoodie.bulkinsert.shuffle.parallelism" -> "2000",
        //  "hoodie.upsert.shuffle.parallelism" -> "400",
        "hoodie.datasource.hive_sync.enable" -> "true",
        "hoodie.datasource.hive_sync.table" -> hudiTableName,
        "hoodie.datasource.hive_sync.database" -> databaseName,
        "hoodie.datasource.hive_sync.partition_fields" -> partitionColumnName,
        "hoodie.datasource.hive_sync.partition_extractor_class" -> "org.apache.hudi.hive.MultiPartKeysValueExtractor",
        "hoodie.datasource.hive_sync.use_jdbc" -> "false",
        "hoodie.combine.before.upsert" -> "true",
        "hoodie.index.type" -> "BLOOM",
        "spark.hadoop.parquet.avro.write-old-list-structure" -> "false",
        DataSourceWriteOptions.TABLE_TYPE.key() -> "COPY_ON_WRITE"
      )

      val df=Seq((1,"Mark",1990),(2,"Martin",2009)).toDF("id","name","year")

         df.write.format("org.apache.hudi")
        .options(hudiCommonOptions)
        .mode(SaveMode.Append)
        .save(tablelocation)

        val tablelocationUpdated="s3://eec-aws-uk-ukidcibatchanalytics-prod-hudi-replication/consumer_bureau/production/CustomerUpdated/"

        df.write.format("org.apache.hudi") //writng to new location
        .options(hudiCommonOptions)
        .mode(SaveMode.Append)
        .save(tablelocationUpdated)

I can use the following code to change the location of the table manually in aws glue.I'm reading the data from the new location and upserting it's one row to the updated location.
val dfupdated=spark.read.format("hudi").load(tablelocationUpdated).limit(1)

val hudiCommonOptions: Map[String, String] = Map(
        "hoodie.table.name" -> hudiTableName,
        "hoodie.datasource.write.keygenerator.class" -> "org.apache.hudi.keygen.ComplexKeyGenerator",
        "hoodie.datasource.write.precombine.field" -> preCombineKey,
        "hoodie.datasource.write.recordkey.field" -> recordKey,

        "hoodie.datasource.write.operation" -> "upsert",  // Chnged to upsert
        "hoodie.datasource.write.row.writer.enable" -> "true",
        "hoodie.datasource.write.reconcile.schema" -> "true",
        "hoodie.datasource.write.partitionpath.field" -> partitionColumnName,
        "hoodie.datasource.write.hive_style_partitioning" -> "true",
        // "hoodie.bulkinsert.shuffle.parallelism" -> "2000",
        //  "hoodie.upsert.shuffle.parallelism" -> "400",
        "hoodie.datasource.hive_sync.enable" -> "true",
        "hoodie.datasource.hive_sync.table" -> hudiTableName,
        "hoodie.datasource.hive_sync.database" -> databaseName,
        "hoodie.datasource.hive_sync.partition_fields" -> partitionColumnName,
        "hoodie.datasource.hive_sync.partition_extractor_class" -> "org.apache.hudi.hive.MultiPartKeysValueExtractor",
        "hoodie.datasource.hive_sync.use_jdbc" -> "false",
        "hoodie.combine.before.upsert" -> "true",
        "hoodie.index.type" -> "BLOOM",
        "spark.hadoop.parquet.avro.write-old-list-structure" -> "false",
        DataSourceWriteOptions.TABLE_TYPE.key() -> "COPY_ON_WRITE"
      )

     dfupdated.write.format("org.apache.hudi")
         .options(getHudiOptions())
         .mode(SaveMode.Append)
         .save(tablelocation)

Expected behavior
How can we change the location of a hudi table to new location . I've customer table that is saved at s3://aws-amazon-com/Customer/ which I want to change to  s3://aws-amazon-com/CustomerUpdated/ .
A clear and concise description of what you expected to happen.
Environment Description
Glue 4
hudi-spark3-bundle_2.12-0.12.1.jar
calcite-core-1.16.0.jar
libfb303-0.9.3.jar

Hudi version : 0.12

Spark version : Spark3.3

Hive version :

Hadoop version :

Storage (HDFS/S3/GCS..) : S3

Running on Docker? (yes/no) : no

Additional context
How can we change the location of a hudi table to new location. I've customer table that is saved at s3://aws-amazon-com/Customer/ which I want to change to  s3://aws-amazon-com/CustomerUpdated/ .

any updates on this would be really helpful .

@MathurCodes1 You can just manually copy folder to new location you want. In case if you are using meta sync to glue catalog, Then you can run one ALTER command to update the location.


CI to only login and push if its not a PR. CI to use github action cache

Noticed this in the output:
Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

I believe we can ignore that. The article also links to them postponing this deprecation, but still saying they'll be showing the warning. https://github.blog/changelog/2023-07-24-github-actions-update-on-save-state-and-set-output-commands/
With no new date in mind and us planning to move away from GH actions, this should be ok as-is.


Remove repeated font-family: monospace

https://github.com/necolas/normalize.css/issues?utf8=✓&q=monospace

@GaetanBt thanks.

You're welcome :)


Complete removal of boost::python.

This pull request finishes the support for running the pylambda workers in cython and removes the use boost::python from the code base.

cy_pylambda_worker.pyx now does the heavy lifting for lambda evaluation.
centralized python callback function for exception handling.
spark unity now a python script that enables cython callbacks.

jenkins pls

@esoroush Can you test this?

The travis build failure is odd -- it's compiling an old version of the file that no longer has that issue.  Commit cd2ec63 doesn't have that in there.  Is there a way to retrigger travis?

jenkins pls

@hoytak - I think this PR could also remove a fair amount of stuff override_cmake/ExternalProjectBoost.cmake too.

@ylow @emad -- are we ready to merge this?

OMG this makes me so happy to finally have this in.


Consider backing up Azure Files to Azure Backup

Sample: https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.recoveryservices/recovery-services-backup-file-share


Adding RateMyProfessor links

Don't actually merge this but I would like for the site to link to RateMyProfessor for each the instructor names. Additionally you could add "the would take again" percentage or rating overall next to profs name if you wanted. Sorry if it isn't formatted correctly, let me know what improvements need to be made.

I've been thinking about this for a while, and I'm having one big reservation about adding RateMyProfessor links to Hyperschedule.  Personally, I'm not sure how I feel about RMP ethically--I feel like it's often enough 1) inaccurate and 2) toxic that "endorsing" it, by way of incorporating it to Hyperschedule, could be problematic.  To elaborate on what I mean, anecdotally:

Several of my favorite instructors (not from the 5Cs)--especially some of those who inspired me to be excited about math, who were to various extents role models for me, who devote immense effort to improving their teaching--have astoundingly poor reviews.  Students complained about their classes being "too hard", or "too theoretical", or in other ways did not fit their expectations.  I knew, from my personal experience, that these professors did teach very challenging material--but they also gave their best to keep you engaged and guide you to discover the material with your own devices (very much what made me fall in love with math in the first place).  I could only conclude that the students who wrote those reviews were either 1) looking for an easy class, or 2) unwilling to put in the effort to make their experiences worthwhile, or 3) expected a simply different style and focus of teaching.
Ratings are very inconsistent across different institutions.  Mudd (and maybe 5C in general) students tend to love their professors, because we have close relationships with them, because that is part of our culture.  Mudd students are also, by and large, far more competent, eager to take on challenges, hardworking, and excited about learning than other colleges, on average.  Consequently, Mudd professors across the board tend to get pretty solid ratings on RMP (I looked up a handful of "random" profs that came to my mind; nearly all were in the 4-5 range, only a few were in the 3-4 range, and none were below).  Meanwhile, professors who haven't spent a long time at Mudd (visiting profs, or newly-hired) tend to have notably worse ratings--not because they're actually bad, but because they were judged in a different context, by a different kind of student that tends to be far less appreciative of their professors than we are.  Not only is this disparity uninformative/misleading, I think it's unfair to these professors, excited to be teaching excited students at a new school, to be judged immediately even before they are given a chance.  Also from personal experience, I took some Core classes with newcomer profs who had outstandingly poor RMP ratings but whom I loved and would absolutely love to take more classes with (and, mind you, I'm saying this about Core, which is already a difficult thing to enjoy).

Even among the reviews that are not toxic and "fair", I would maintain that every student has their own learning style, every professor has their own teaching style, and picking a professor is more a question of "do the student's and teacher's styles fit?" rather than "is the teacher's style good?"  After all, different things work well for different people, and assigning a single 1-5 score, Amazon product-review-style, feels like it's 1) an oversimplification of what good teaching means, 2) subjective, 3) potentially objectifying to professors, and 4) possibly misleading.
To be clear, I'm not saying that all of RMP is bad and can never be useful, but rather that some of it can be quite mean and unfair to our profs, and to add RMP support in general to Hyperschedule is, in a way, to endorse all of RMP, even the bad stuff.  That, together with the reasons above, is why I'm now hesitant to add RMP to Hyperschedule.  Nevertheless, I'd like to hear what you think of these reasons and whether you think RMP could still be a good idea.  I'm open to considering it still!

Ok makes sense. Yeah it is not always accurate.


Use diff instead of cmp

We're seeing some flakiness in this test, but aren't sure what it's complaining about. cmp only says where the difference was, but doesn't print what was different. diff prints what was difference so we have a chance to figure out what happened.
Cherry-picking: https://github.com/apple/swift/pull/65364

@swift-ci please test


Refactors auth to live in common

I was doing some debugging and forgot to change it back.  I'll do that when
I get in
On Wed, May 9, 2018, 8:21 AM Alex Silva<EMAIL_ADDRESS>wrote:

@roarking commented on this pull request.
In avro/src/test/scala/hydra/avro/ISODateConverterSpec.scala
https://github.com/pluralsight/hydra/pull/83#discussion_r187056400:

@@ -26,7 +26,7 @@ class ISODateConverterSpec extends Matchers with FlatSpecLike {

it should "return the epoch on bad formed dates" in {
val c = new ISODateConverter()

c.fromCharSequence("2015-07-281",

c.fromCharSequence("2015-07-28",

Why did you change this here? This is meant to test the behavior on bad
dates
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pluralsight/hydra/pull/83#pullrequestreview-118758233,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJwR_DNEhTmxMewCRBZGYqz_1DnPtaUBks5twvtQgaJpZM4T3Yj_
.

Codecov Report

Merging #83 into master will increase coverage by 0.09%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #83      +/-   ##
==========================================
+ Coverage   92.49%   92.58%   +0.09%
==========================================
  Files         127      129       +2
  Lines        1985     1956      -29
  Branches      119      108      -11
==========================================
- Hits         1836     1811      -25
+ Misses        149      145       -4

Impacted Files
Coverage Δ

.../hydra/kafka/endpoints/TopicMetadataEndpoint.scala
100% <ø> (ø)
:arrow_up:

core/src/main/scala/hydra/core/Settings.scala
100% <ø> (ø)
:arrow_up:

...a/hydra/common/auth/AuthenticationDirectives.scala
100% <100%> (ø)

common/src/main/scala/hydra/common/Settings.scala
100% <100%> (ø)

...la/hydra/common/auth/NoSecurityAuthenticator.scala
100% <100%> (ø)

...n/scala/hydra/common/auth/HydraAuthenticator.scala
100% <100%> (ø)

sql/src/main/scala/hydra/sql/PostgresDialect.scala
92.15% <0%> (-1.97%)
:arrow_down:

sql/src/main/scala/hydra/sql/JdbcUtils.scala
98.57% <0%> (-0.17%)
:arrow_down:

sql/src/main/scala/hydra/sql/DbSyntax.scala
100% <0%> (ø)
:arrow_up:

sql/src/main/scala/hydra/sql/TableCreator.scala

... and 7 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 86442a0...8e4a768. Read the comment docs.


Testing: python 3.8 test sklearnex deselections

Description
These tests are currently failing on python 3.8 with 2024.0 setup.

/intelci: run

/intelci: run

@mergify backport rls/2024.0.0-rls