Warning when running the forget-me tool when the databases are pointed to Oracle

Get a warning as below when the databases are pointed to Oracle. The driver is copied to <IS_HOME>/repository/components/tools/forget-me/lib directory. What could be the reason?
2018-03-08 14:01:48 INFO  ForgetMeTool:168 - Generating pseudonym as pseudo name is not provided : bd4862e8-efe9-4373-bfd3-bd07111cfe6e
2018-03-08 14:01:48 INFO  HikariDataSource:72 - HikariPool-0 - is starting.
2018-03-08 14:01:48 WARN  DriverDataSource:68 - Registered driver with driverClassName=oracle.jdbc.driver.OracleDriver was not found, trying direct instantiation.
2018-03-08 14:01:49 INFO  HikariDataSource:72 - HikariPool-1 - is starting.
2018-03-08 14:01:49 WARN  DriverDataSource:68 - Registered driver with driverClassName=oracle.jdbc.driver.OracleDriver was not found, trying direct instantiation.
2018-03-08 14:01:49 INFO  HikariDataSource:72 - HikariPool-2 - is starting.
2018-03-08 14:01:49 WARN  DriverDataSource:68 - Registered driver with driverClassName=oracle.jdbc.driver.OracleDriver was not found, trying direct instantiation.
2018-03-08 14:01:49 INFO  RdbmsForgetMeInstruction:77 - Processing SQL in directory org.wso2.carbon.privacy.forgetme.sql.sql.SQLFileReader@763fcdc0
2018-03-08 14:01:49 INFO  ForgetMeExecutionEngine:219 - Processor execution completed. Processor : log-file
2018-03-08 14:01:49 INFO  RdbmsForgetMeInstruction:146 - Completed all SQLa in directory /home/dilinig/wso2_products/is_releases/wso2is-5.5.0-beta/repository/components/tools/forget-me/conf/sql/identity.
2018-03-08 14:01:49 INFO  ForgetMeExecutionEngine:219 - Processor execution completed. Processor : rdbms
2018-03-08 14:01:49 INFO  ForgetMeExecutionEngine:115 - All processors have been properly shut-down

What is the driver jar used? from where it was taken?

driver - ojdbc7.jar
download link - http://www.oracle.com/technetwork/database/features/jdbc/jdbc-drivers-12c-download-1958347.html

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


prepare changelog for 0.21.0 release

Problem
The changelog requires updating in advance of 0.21.0
Solution
This updates the changelog.

Note: All schema changes require discussion. Please link the issue for context.

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).
Checklist

[x] You've signed-off your work
[x] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[x] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] Your comment includes a one-liner for the changelog about the specific purpose of the change (if necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project

Codecov Report

Merging #1679 (8f2abd4) into main (863b42e) will decrease coverage by 5.69%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main    #1679      +/-   ##
============================================
- Coverage     83.34%   77.66%   -5.69%
============================================
  Files            89       64      -25
  Lines          4006     3502     -504
  Branches         29        0      -29
============================================
- Hits           3339     2720     -619
- Misses          635      782     +147
+ Partials         32        0      -32

Impacted Files
Coverage Δ

...ntegration/airflow/openlineage/airflow/listener.py
0.00% <0.00%> (-71.14%)
:arrow_down:

...ow/openlineage/airflow/extractors/ftp_extractor.py
33.33% <0.00%> (-56.42%)
:arrow_down:

...eage/airflow/extractors/redshift_data_extractor.py
39.47% <0.00%> (-50.00%)
:arrow_down:

...lineage/airflow/extractors/sagemaker_extractors.py
26.26% <0.00%> (-47.48%)
:arrow_down:

integration/airflow/openlineage/airflow/plugin.py
62.50% <0.00%> (-37.50%)
:arrow_down:

integration/airflow/openlineage/airflow/adapter.py
50.57% <0.00%> (-33.34%)
:arrow_down:

.../openlineage/airflow/extractors/trino_extractor.py
64.00% <0.00%> (-28.00%)
:arrow_down:

integration/airflow/openlineage/airflow/utils.py
71.01% <0.00%> (-9.79%)
:arrow_down:

...w/openlineage/airflow/extractors/sftp_extractor.py
84.61% <0.00%> (-9.62%)
:arrow_down:

integration/airflow/openlineage/airflow/facets.py
85.10% <0.00%> (-8.52%)
:arrow_down:

... and 27 more

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


detached kb/mouse focus modes and pass bind behaviour

Steps to reproduce

enable follow_mouse={2,3}
enable a bind with the pass dispatcher ( in my example with mouse:276 to .*discord.* )
focus the relevant window ( in my case discord )
move the mouse off the window

Expected outcome
for the bind of the button to continue to be passed to the relevant window
as it is when focus is on a different window or focus is on the relevant window and the cursor is above it
Noted outcome
the bind is entirely ignored by the relevant window

I'm using the NixOS version of hyprland as explained in the wiki, sorry bout it :trollface:
Hyprland, built from branch  at commit 606cb2832aff2c7305da1f880ce732f7eb464d04 ().
flags: (if any)
debug

also not entirely sure if a bug, tho if this is intended.. why?

prolly bug


Add enzyme oracle

Adds enzyme oracle for https://github.com/gnosis/safe-transaction-service/issues/384

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 91.34%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
2658

Relevant Lines:
2910

💛  - Coveralls


Output pin for PWM not being set

I'm using a RaspberryPi Zero and I was getting the following error:
remi.server      INFO     Started httpserver http://<IP_ADDRESS>:8081/
remi.server.http DEBUG    get: /
Initiated Heater PWM.
wiringPiSetup: You must only call this once per program run. This is a fatal error. Please fix your code.*
It seems that wp.wiringPiSetup() is being called in the the HeaterPWM.py module after its already called in the max31855.py module. As a result, the next line,  wp.pinMode(pin, 1), is never executed and the PWM pin doesn't get set to OUTPUT mode.
Removing the wiringPiSetup() line in the HeaterPWM.py module fixed the problem.
Thanks for creating this PID Controller. It's super easy to use and is doing a great job on my Gaggia.

Oops! I wasn't getting that error with the Odroid modified version of WiringPi.
Should be fixed. And it's good to hear that this works on a Zero.


Remove unused imports

I noticed that there were some imports in Heroku.hs that may have been left over from some refactoring. These imports are not being used in the file and compiling with -Wall produces warnings about them.

thanks!


Creating similarity matrix and adjacency matrix

Can you help me? When I run the code to create matrix the csv file was created but there's no data

Could you provide some details as to how it fails?


Migrate the lib to TypeScript

Is your feature request related to a problem? Please describe.
No my feature request does not come from a problem
Describe the solution you'd like
Switching the lib to TypeScript
Describe alternatives you've considered
I don't really have an alternative. My goal is to make the lib nullsafe to add other functionality later
Additional context
To be honest, I'm not really asking for a job from you. My goal is to know if it is useful for me to take the time to offer you a PR allowing you to migrate to TypeSafe. As well as adding the definition of the 5 gateways that I have already been asked for on my side.
And in a more or less near future, I thought that I could have a system for updating internal values with events
The real job I would ask is proofreading, because unfortunately I'm not perfect yet and I still have to learn about languages and their possibilities.
 Thank you Google Translate

Hi,
I will be happy about a PR that convets the code base to Typescript. As I started the project it was way to experimental and typescript would have hindered me in trying stuff out with the communizty (because I myself do not have such a device at all). But yes it is the next logical step :-)
I would like to keep the generated JS version compatible to the current one if possible.
I do not know if we ever get it typesafe and nullsafe because in fact we just "reverse engineer" an external API which is not documented and not published and so Daikin can change anything anytime ... So any types are just correct unless Daikin changes something, so we also should consider this! SO maybe use partials or such, because else we need to get infos on any little change and need to update the typings for users to use it. I know this from several other projects ... So do not expect 100% accuracy for the future and please design the types in that way!
Also adding the currently known 5 gateways is a great idea. Cool - then you have more insights then I have :-) In which projects you plan to use the library (just for my personal interst :-) )
I also have just basic TS knowledge and have some TS "pro's" in my back hand ... so we will get professional feedback if you like :-)
Ingo

Hello, Thank you for your answer, I was just thinking of making a definition file allowing an app using ts to be able to understand it. I didn't think I would touch the current database with all the useful information.
I also tell you that I am currently in contact with Daikin to see if there is a way to have a real API that we could use in the lib.
Ps: Thank you for the help, as a student it will allow me to improve
Cordially
Thibaut

Contact to Daikin? Cool ... I tried that several times in the last years and never got any response :-(
But be careful ... It is easy for them to shut us down!

I did not indicate the direct git but the Home Assistant and Jeedom forum posts.
To contact them, I have the chance to have an acquaintance working at the French head office (Commercial)
I would also find it a pity that it limits the possibilities. Because it would make them lose market share.
Feedback that I have had is that for them it was complicated today because it would take an intermediate server. Which I'm not for.
Cordially
Thibaut

@Apollon77 this one can be closed now.


disableInitialSync feature flag

What issue type does this pull request address? (keep at least one, remove the others)
/kind enhancement
/kind feature
What does this pull request do? Which issues does it resolve? (use resolves #<issue_number> if possible)
Partially resolves #1218 adding support to disable completely the initial sync
Please provide a short message that should be published in the DevSpace release notes
Enhance the configuration capabilities of DevSpace to enable the possibility of disabling the initial sync, similar to how you can currently disable the upload or download.
What else do we need to know?
There are use cases where syncing is required only for files changed after the development or sync process has been initiated, rather than fully synchronizing the remote or local repository.

@lizardruss changed and added e2e.
dev:app-meta sync  Start syncing dev:app-meta sync  Sync started on: ./ <-> /code/ dev:app-meta sync  Waiting for initial sync to complete dev:app-meta sync  Downstream - Initial sync disabled dev:app-meta sync  Upstream - Initial sync disabled dev:app-meta sync  Initial sync completed dev:app-meta ssh   Port forwarding started on: 9042 -> 8022


Provide support for Debug protocol

see https://github.com/Microsoft/vscode/issues/19636 and https://github.com/Microsoft/vscode-debugadapter-node https://bugs.eclipse.org/bugs/show_bug.cgi?id=508470

2 possibilities:

have the server pulling via JMX the information
have the server registering an interceptor so that when a breakpoint is hit, the interceptor is notifying the debug adapter which will in return notify the Client IDE.

In Fuse Tooling, the pull mode is used currently for the Graphical debug. It has some latencies due to this architecture; the pull cannot be done every milliseconds otherwise there was some issues with the results given and Camel was overloaded based on comments in the code. But might be easier to implement.


$ionicLoading freezes user interaction for a while on iOS

On iOS, after using $ionicLoading.hide() user interaction is disabled for a few seconds to up to a minute.
Which Ionic Version? 1.x or 2.x
ionic 1.3.1
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.2.0
Gulp version:  CLI version 1.2.2
Gulp local:
Ionic CLI Version: 1.7.15
Ionic App Lib Version: 0.7.2
ios-deploy version: 1.8.6
ios-sim version: Not installed
OS: Mac OS X El Capitan
Node Version: v4.4.5
Xcode version: Xcode 7.3.1 Build version 7D1014

Note that the interface seems freezed but I can programatically do whatever I want. It's just user interaction (touch, swipe...) that does not have any effect. Like if it would have been a layer on top or a pointer-events:none (but I found none of these using Safari remote debugger)

This issue was moved to driftyco/ionic-v1#68


Tweaks to YT Description script

Added property playlistId for main tracks to work with yt-desc script (see https://github.com/CodingTrain/thecodingtrain.com/issues/205#issuecomment-1159516945)
Changes to script to use the playlistId for Previous Video / Next Video / All Videos
Minor tweak to emoji selection for reference links
Removed 404 amazon influencer store link from description (let me know if this needs to be kept)

Thank you for working on this more @dipamsen!!

Removed 404 amazon influencer store link from description (let me know if this needs to be kept)

Yes, I no longer have an amazon affliate account. I'd like to create a https://bookshop.org list but I haven't had the time yet.


repos name should be changed to reflect 'github.com/monstorak/monstorak'

Go files should be packaged currectly, according to the github repo.
So importing packages may look like,
'github.com/monstorak/monstorak/<module_name>'

Closing the issue side, as it is fixed with the above changes


Typo

A typo on point 12. "Duration before reacceptance requires (days)"
"requires" should be "required".
This typo is repeated again a few lines further on.
Also the setting in the GUI is hyphenated : "re-acceptance".
This made the page harder to find with a search.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 618ca851-56c8-5ba1-35de-a7b8e7af8aa2
Version Independent ID: 5facc663-2e29-65ad-f208-982150351b22
Content: Terms of use - Azure Active Directory
Content Source: articles/active-directory/conditional-access/terms-of-use.md
Service: active-directory
Sub-service: compliance
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@alicain Thank you for your feedback . We will investigate and update the thead.

I guess I will assign this to me to do. #reassign@MicrosoftGuyJFlo


qovery-cli: 0.91.3 -> 0.92.2

Diff: https://github.com/Qovery/qovery-cli/compare/refs/tags/v0.91.3...v0.92.2
Changelog: https://github.com/Qovery/qovery-cli/releases/tag/v0.92.2
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package built:

qovery-cli


About css

I've already tried the gitter channel, but since I'm not receiving any answer, I'm just writing right here. Copy-paste:
Hi, I'm deciding to switch from flexslider to slick. First thing first: are its styles fully customisable? Are they mandatory? Can I fully override them if needed? I mean, without too much hassle: flexslider lets you not to load its css and setup basic functionality with really few lines of css (again, I mean to have the basic masking/changing images, and then one starts styling anything else). I thing that's mainly because in flexslider the really relevant styles are inline-written via javascript. Is Slick the same?

Why don't you just test it?

Thanks for trying the gitter channel first. We've broken the slick styles into "base" and "theme". Obviously with code you can change everything/anything you want, and so in that sense they are customizable, but the base styles will give you the base functionality. Theme has button placement, arrow styles etc. Hope that helps. Give it a spin--there's a jsfiddle you can play with in the contributions.md


Use the Swift runtime's (faster) class check in the stdlib instead of shimming object_getClass()

Cherry-picking this speedup to 5.1

@swift-ci please test

Original PR: https://github.com/apple/swift/pull/24647


An AsyncAPI perspective

Even though background lays the foundation for an AsyncAPI perspective, for the sake of clarity I am going to bring it to light here and try to map the proposals to the requirements and whether they solve the problems we are facing.
The alternative approach we are looking at is making a superset of the JSON Reference standard and restrictively defining the missing behaviors that work for our case (something along the lines of this PR).
The referencing standard is only part one of solving the referencing discrepancies as tooling is the second part that should be able to work with any JSON format which uses some form of referencing standard. See more in this discussion: https://github.com/orgs/asyncapi/discussions/485
The main use-case for us and the reason we want to change the referencing standard is to allow a message to define its payload with something different than JSON formats, which includes but is not limited to Protobuf and XSD formats.
The requirements we are looking at are the following (this primarily comes from questions raised when trying to build a referring tool and where the specs did not provide an answer):

Should always produce a valid JSON document (resolving referenced resource should always be compatible with JSON)
Should define the behavior for referencing non-JSON resources in a JSON document (this can be as simple as resolving the content into a string value)
Should define the behavior for referencing JSON data
Should define the behavior for referencing JSON data that also have reference behavior, and how they interconnect / or not (say two standards both use $ref the new standard should define a clear separation between the two and how referencing tools should interpret it)
Should define the behavior of nested schemas within the same file (so there is no difference between what the spec allows and what tooling enables)

If you have any questions/concerns feel free to raise them below! I am gonna block out some time to map the proposals to the requirements we have at some point, if you are bored, feel free to jump-start the process 😄!

Thanks for writing this up! I'd be happy to write up how the JRef proposal addresses these requirements, but I'd like to ask a couple clarifying questions first.

Should always produce a valid JSON document (resolving referenced resource should always be compatible with JSON)

It isn't possible to resolve and inline recursive references into a JSON document.
For example.
{
  "foo": 42,
  "bar": { "$ref": "#" }
}

If you try to resolve and inline this schema, you'll end up with an infinitely sized document.
{
  "foo": 42,
  "bar": {
    "foo": 42,
    "bar": {
      "foo": 42,
      "bar": { ... recursing forever ... }
    }
  }
}

However, it is possible to resolve recursive references into an in-memory data structure in such a way that you can work with it as JSON compatible data without having to think about references. It would be like working with a structure like this,
const value = { foo: 42 };
value.bar = value;

console.log(value.bar.bar.bar.bar.bar.bar.foo); // Result => 42

So, since it isn't possible to fulfill this requirement as written, is there another variation of the requirement that also satisfies whatever use case prompted this requirement?

Should define the behavior of nested schemas within the same file (so there is no difference between what the spec allows and what tooling enables)

I'm not sure I understand what you mean here. I think this is saying something about embedded schemas (bundling), but I'm not sure what. Could you elaborate on what you're looking for here?

I'd be happy to write up how the JRef proposal addresses these requirements

That would be awesome 🔥

So, since it isn't possible to fulfill this requirement as written, is there another variation of the requirement that also satisfies whatever use case prompted this requirement?

That is a very good point. The requirement was mainly focused towards the non-JSON resources as reference tooling has to provide a way to interact with the referenced resource in some way or form. For example, if you reference a protobuf file how can tooling interact with it? This can be decided in the spec, or it is left to the context specification (as defined in JRI) or even to tooling. I don't think we really have an ultimatum here, just as long as it's well-defined it would clear it.
As you outline there is the in-memory example, which definitely would satisfy it. It's however also possible to convert the in-memory data structure into and from JSON while still supporting circular references, it just requires some customization. We actually have this as a "feature" for our AsyncAPI parser, because we have UI cases where we need to serialize the recursive structure. But that probably deserves it's own issue to discuss it and possible solutions 😄

I'm not sure I understand what you mean here. I think this is saying something about embedded schemas (bundling), but I'm not sure what. Could you elaborate on what you're looking for here?

Definitely, and you are spot on, that's definitely one of the drivers.
In AsyncAPI and OpenAPI we have components that we store the reusable components and JSON Schema $def, the standard must clearly define the behavior for how references work depending on the context specification.
I know for JSON Schema the automapping between $id and components in $def (compound schemas) is a great hit, but it's definitely not something we see with great positivity from an AsyncAPI perspective at the moment 😄 But let's not focus on this here, this is just to map the specs to AsyncAPI and what it enables and restricts, then we can always bring it up later 🙂

Ok. I think I understand. Let me know if I have this right.
For (1), my understanding is that tooling needs to be able to abstract references and non-JSON data so that there's a consistent and well defined way to work with the document as only JSON-compatible types and data structures. It's not necessarily about converting it to a JSON document.
For (5), my understanding is that you're talking about where references are allowed and what is allowed to be referenced. If { "$ref": "#/foo" } appears somewhere in an AsyncAPI document where a reference isn't allowed, tooling should treat it as an object (or an error) rather than as a reference.

Here's how I see that JRef applies to your requirements for AsyncAPI. I hope it's helpful.

Should always produce a valid JSON document (resolving referenced resource should always be compatible with JSON)

In JRef, references are always transparent. Developers are always working only with the standard JSON types. When you get a value from a JRef document, the JRef tooling follows the reference automatically and gives you the referenced value as if the referenced value was always there.
Example
const doc = JRef.load({
  "foo": { "$href": "#/bar" },
  "bar": "42"
});

const foo = JRef.get("/foo", doc); // => 42
const bar = JRef.get("/bar", doc); // => 42

Should define the behavior for referencing non-JSON resources in a JSON document (this can be as simple as resolving the content into a string value)

JRef allows implementations to define how they want non-JSON values to be represented. Everything is based on media types. You can have XML converted into a JRef compatible document, or just return it as a string. You would write a plugin for the JRef tooling describing the behavior you expect for each media type.
Example:
const doc = JRef.load({
  "schema": { "$href": "./my-xml-schema.xml" }
});

const xmlSchema = JRef.get("/schema", doc); // => Some representation of an XML document
const value = XML.get(someXPathExpression, xmlSchema); // => The value of applying the XPath expression to the XML document

Should define the behavior for referencing JSON data

The JRef proposal covers the behavior of references in JRef documents. Although JRef is syntactically compatible with JSON, it's considered a different media type and must be configured as a plugin the same way you would for XML.
Example
const doc = JRef.load({
  "foo": { "$href": "./my-json-document.json" }
});

// ./my-json-document.json
// {
//    "aaa": { "$href": "#/bbb" },
//    "bbb": 42
// }

const foo = JRef.get("/foo", doc);
const aaa = foo.aaa; // => { "$href": "#/bbb" } # A value that looks like a JRef reference, but is actually just a plain JSON object with no special meaning
const bar = foo.bbb; // => 42

Should define the behavior for referencing JSON data that also have reference behavior, and how they interconnect / or not (say two standards both use $ref the new standard should define a clear separation between the two and how referencing tools should interpret it)

Every document has a media type and each media type has it's own rules for referencing. If you reference a JSON Schema from a JRef document, once you follow that reference, then only the rules for JSON Schema apply. Because it's document based, there are some consequences to be aware of. If your AsyncAPI document identifies as a JRef media type, you can't embed a JSON Schema in that document because it's a different media type. You can only reference to a JSON Schema. That shouldn't be a big deal because it's what you already have to do for non-JSON compatible types already.
One way around that is to define AsyncAPI as a separate media type that defines that certain locations are to be interpreted as JSON Schemas. Then it can be a reference or inline. But, that would require extra work to extend the standard JRef tooling.
Another way around that is to introduce some syntax for embedding external documents in a JRef document. I've explained why an embedding/bundling feature is not included in https://github.com/json-schema-org/referencing/issues/7, but I'm open to discussion if there's demand for it.
If both AsyncAPI and JSON Schema decide to adopt JRef, this problem goes away, but I don't think that's likely from the JSON Schema side.

Should define the behavior of nested schemas within the same file (so there is no difference between what the spec allows and what tooling enables)

JRef doesn't restrict where a reference can be or what can be referenced. Because the tooling abstracts away references, there should be no developer burden and AsyncAPI document authors are empowered to use references however fits their needs. If AsyncAPI does want to make restrictions like this, they would need to define their own media type and would have to extend the standard tooling.

@jdesrosiers thanks for the quick feedback! Do you mind starting a new issue just for the JRef perspective? Then we can discuss it there instead of mixing it together with jri 🙂 Then I will start another one just for jre.

Added the JRI perspective here where I answered the simple questions above: https://github.com/json-schema-org/referencing/issues/17
I do not go into depth here, but it seems like it clarifies the questions.

Going forward the discussion around this subject will slowly progress for AsyncAPI, so don't expect anything like a 🚤, as the proposal is not aimed at the upcoming spec 3.0 but a feature likely end of this year at some point - https://github.com/asyncapi/spec/issues/881
Unless someone else champions the change through earlier then what I can 😄

Unless someone else champions the change through earlier then what I can

Do you mean on the AsyncAPI side or also speeding things up on this side?

Do you mean on the AsyncAPI side or also speeding things up on this side?

On the AsyncAPI side we don't "need" to take any decisions on our end before the end of this year probably, that is unless someone else champions the issue through instead of me 😄


Refactor temporal_superposition in _BaseSolver to use numpy.einsum

The temporal superposition process in the calculation of the g-function becomes time demanding as the number of boreholes grow.
Currently, for a square field of 20 by 20 boreholes (400 boreholes in total) and Nt=50 time steps :
Identifying similarities ... 0.406 sec
------------------------------------------------------------
   Calculating g-function for boundary condition : 'UBWT'
------------------------------------------------------------
Calculating segment to segment response factors ... 13.370 sec
Building and solving the system of equations ... 379.955 sec
Total time for g-function evaluation: 393.616 sec
------------------------------------------------------------

Using the profiler, we find that the total time in _BaseSolver.temporal_superposition() is 289 sec. This is largely due to the inefficient for loop :
https://github.com/MassimoCimmino/pygfunction/blob/66d8b4ce8ee12f14fb74e48d5283284a7a6cc121/pygfunction/gfunction.py#L1417-L1428
This can be refactored to use numpy.einsum :
# Number of heat sources
nSources = Q_reconstructed.shape[0]
# Number of time steps
nt = Q_reconstructed.shape[1]
# Borehole wall temperature
Tb_0 = np.zeros(nSources)
# Spatial and temporal superpositions
dQ = np.concatenate(
    (Q_reconstructed[:,0:1],
      Q_reconstructed[:,1:]-Q_reconstructed[:,0:-1]), axis=1)[:,::-1]
Tb_0 = np.einsum('ijk,jk', h_ij[:,:,:nt], dQ)

We get :
Identifying similarities ... 0.401 sec
------------------------------------------------------------
   Calculating g-function for boundary condition : 'UBWT'
------------------------------------------------------------
Calculating segment to segment response factors ... 13.423 sec
Building and solving the system of equations ... 127.854 sec
Total time for g-function evaluation: 141.546 sec
------------------------------------------------------------

The profiler shows that the total time in _BaseSolver.temporal_superposition() is reduced to 40.74 sec. The largest time is due to the solution of the system of equations using numpy.solve, which takes 51.47 sec.

Same test cases as in #78.

Case 1 : Rectangular fields up to 12 by 12

Case 2 : Number of segments for a 5 by 5 bore field

Case 3 : Field of 100 boreholes with 2 different lengths


Fix spelling and include RangeAttribute in validation

I received feedback about a spelling error in EntryValidation and the idea, to make the value more flexible and also include range validation values.

The renaming must also be fixed within the maintenance web.

I checked and the MaintenanceWeb does currently not include validation AFAIK.

The renaming must also be fixed within the maintenance web.

I checked and the MaintenanceWeb does currently not include validation AFAIK.

I think you missed the deserialization: https://github.com/PHOENIXCONTACT/MORYX-MaintenanceWeb/blob/dev/src/Moryx.Runtime.Maintenance.Web.UI/src/modules/models/EntryValidation.ts

Yes I did :-)


Support custom completion block.

Added a completion block to support additional animations when the transition is finished.
Here's an example in Swift:
func animationBlockForZoomTransition() -> ZoomAnimationBlock! {
    return { (animatedSnapshot: UIImageView!, sourceView: UIView!, destinationView: UIView!) -> Void in
        animatedSnapshot.transform = CGAffineTransformMakeScale(1.02, 1.02)
    }
}

func completionBlockForZoomTransition() -> ZoomCompletionBlock! {
    return { (animatedSnapshot: UIImageView!, sourceView: UIView!, destinationView: UIView!, completion: (() -> Void)?) -> Void in
        UIView.animateWithDuration(0.2, animations: { () -> Void in
            animatedSnapshot.transform = CGAffineTransformIdentity
            }, completion: { (Bool) -> Void in
                if let completion = completion {
                    completion()
                }
        })
    }
}

Hello, fixed 2 problems.

Frame rate drops obviously if fromView/toView are complicated (it even drops on my 6s Plus!).
Improved that by using another background view to animate instead of changing alpha value of the original views. And also reduced some unnecessary calculations.
Edge pan gestures shouldn't be added if it's going backward, just added a detection to avoid that.

Hey!
I've released 0.4.0 version with those changes, thank you very much!
I've also granted you push access, just in case you might need something else :beers:

Thank you very much! 😊


Next release

Since there are some pretty useful changed recently, I'd like to kindly ask if it would be possible to make a release some time soon?

Done :)

Same story now, not opening a new bug yet.


Neither Package Manager command works

Neither
_https://github.com/acoppes/unity-history-window.git#1.0.6_
nor
_https://github.com/acoppes/unity-history-window.git#1.0.4_
works in 2021.1.7. Error:
[Package Manager Window] Cannot perform upm operation: Unable to add package [https://github.com/acoppes/unity-history-window.git#1.0.6]:
Could not clone [https://github.com/acoppes/unity-history-window.git]. Revision [1.0.6] could not be found. [NotFound].
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()
Am I doing something wrong? Tried different ways, git and https syntax, no specific version. :(

Just tested it using https://github.com/acoppes/unity-history-window.git#1.0.6 and Unity 2020.3.5f1, have to test it again in 2021, maybe something changed in specifying package dependencies with https or git url.

It works with 2021.2.0a10 too, maybe you are doing something wrong?


Dark Mode - Accordion

This issue depends on #788 being completed
Implement the root variables in the Accordion and Card components. Component-specific colors should be scoped to their own stylesheets.
The components should switch their theme depending on a global site variable, and be able to be overridden by a data attribute data-mwc-theme or data-modus-theme

Moved Card to #797

components changed and merged with dev/msankaran/dark-mode-main


[Android11] FileSystemException is happened at Isar.open

Steps to Reproduce
execute Isar.open, directory is below.
Errors
Unhandled Exception: FileSystemException: Creation failed, path = 'some' (OS Error: Read-only file system, errno = 30)
E/flutter (11085): #0      _Directory.create.<anonymous closure> (dart:io/directory_impl.dart:117:11)
E/flutter (11085): #1      _rootRunUnary (dart:async/zone.dart:1362:47)
E/flutter (11085): #2      _CustomZone.runUnary (dart:async/zone.dart:1265:19)
E/flutter (11085): <asynchronous suspension>
E/flutter (11085): #3      openIsarNative (package:isar/src/native/open.dart:25:3)

Code sample
    final isar = await Isar.open(
      schemas: [DataSchema],
      directory: 'some/directory',
    );

Version

Platform: Android
Flutter version: 2.2.3
Isar version: 1.0.0+1

help me...

You need to provide a valid directory on the platform you are running on. I recommend using path_provider

It would help noobs like me if this were the way it is implemented in the docs - or mentioned there

Added it here: https://github.com/isar/isar#3-open-an-instance 🙂

I am now a happy noob 😄


⚠ Bofrost.at has degraded performance

In c6d717f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2626 ms

Resolved: Bofrost.at performance has improved in 17e72e1 after 20 minutes.


kivy/lib/mtdev.py: ctypes "POINTER" should be "pointer"

Line 155 in kivy/lib/mtdev.py
        mtdev_close(POINTER(self._device))

should be
        mtdev_close(pointer(self._device))

the former creates a pointer type, the latter creates an actual pointer instance. this solves a crash.

Thanks for reporting the issue. If you can, please open a pull request with the change, so that you get the credits for it. Also, if you can, please provide the crash log to this issue. :)

np. i'm in no need of credits. there has been a proposed fix for this by someone else, coupled with an actual commit, but i don't know why it never made it to the trunk?

Aaaah, I think it's #5206. I'm not sure either, but from the discussion I believe even the CPU issues were figured out. Let's merge it to master and wait if something weird pops out. Doesn't look like it though.

Closed by #5206


pkgsLinux: set crossSystem instead of localSystem

Description of changes
As the doc implies, we should be using crossSystem to build for the Linux platform. Using localSystem just happens to occasionally hit cached builds. See also https://github.com/NixOS/nixpkgs/pull/316659#issuecomment-2149539101 and https://github.com/NixOS/nixpkgs/runs/25855763929
See also #282401
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

The latest commit would likely cause a lot of rebuilds since it’s systemd dependency. I’ll rebase to the staging branch later.

OK, apparently some Linux-specific packages are still getting pulled from hostPkgs (mostly for full systemd, for some reason, e.g. bpftool). Marking the PR as ready for review so we’d at least get an evaluation failure instead of confusing build failure for now.

Ah, I see #293573. That’s still seems like a really weird and niche use case to me — I mean, if it requires linux builder, so why not run tests there? Instead, I think we should be able to cross-compile NixOS from macOS with some effort.

I'd previously asked the infra team to provide a Linux builder, but they were concerned about a deadlock issue. I've now opened an issue with alternatives that avoid the problem (and it's also actually properly visible, unlike chat in Matrix).

https://github.com/NixOS/infra/issues/439


Model Populated by a Schema Default via Reference vs Copy

I am building out a custom model binding and am comparing objects to scope.schemaForm.schema object.  I noticed when the model is initialized with defaults from the schema defaults, it's added to the model as a reference to the schema default object/array rather than copied.  The result being, when a new object is being added to an array on the model and that array was created from the schema default, the schema object's default property will also include the new object.
Frankly I haven't dived into any of the validation code, but if it's basing any validation on the schema object that seems like an issue.  Perhaps not, since I can't really see a reason to care about defaults when validating, but for my purpose, I'm comparing the object to the defaults to determine if I should consider the object for removal from the model (when the contained target property from the field input is empty string/null and the containing object is empty and not contained in the default).
I first thought I could just do a copy on the schema default from the builder, but seems like that object copy should happen when passsing the schema default value to sfSelect in the schemaForm directive (the line specifically: sfSelect(path, scope.model, prop['default']);).  Otherwise, if I have nested objects in my schema each with a default of it's own, I end up with a schema default object with properties not originally defined in the schema.

@kyse I believe this is already known via #407
Can you confirm if that is the case or not and close this or comment further accordingly please?

was this fixed? I am still having the same problem.

I never saw any end in sight to all these updates needed.  Doesn't appear they do very many publishes either.  So I just work on a manually modified version of the library to address this myself and prevent bower from updating the library unless I do so manually to readdress my modifications.

Line 2667: sfSelect(path, scope.model, angular.copy(prop['default']));
My other modification is to prevent killing the titleMap but parse properties to see what needs updating on line 2393 to 2399.


Update for SE-0025 ('private' and 'fileprivate')

SE-0025 makes private restrict access to a lexical scope; the Swift 2 behavior is now named fileprivate. At the time of this pull request, the compiler treats both private and fileprivate as having fileprivate semantics, but that will soon change.
Supersedes #124; the latest amendment to SE-0025 permits some accesses that the original model (or at least our interpretation of it) would have forbidden.

cc @mike-ferris-apple, @modocache

Looks reasonable to me...

Looks good to me -- thanks @jrose-apple!


Improve get_push_notification_receipts

This PR contains #62

There is a compilation error in lib.rs, but it might be fixed by other Pull Requests #63

Why don't you use a builder to construct a request body for /--/api/v2/push/getReceipts?


Add syntax highlighting for let and other alpha-release builtin keywords

Syntax highlighting is missing for (let [...] ...). Can you add syntax highlighting for other similar macros covered under alpha release?

Should be fixed with https://github.com/hylang/vim-hy/commit/813ff051dfc73ed225ef71495c2b235f84fbaa1e, thanks for opening an issue!
Let me know if there are any keywords I missed.


Update Java to version 1.5.0

This is for the Java release of 1.5.0, it updates the version used in the examples.

Waiting for Maven to get iopipe 1.5.0, so do not merge until that happens.


Updated IaaS reference

Corrected IaaS reference from "Information as a Server" to "Infrastructure as a Service".

Hi @marcusclayton, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@marcusclayton : Thanks for your contribution to the Azure documentation! The author, @PVRK, has been notified to review your proposed change.

#sign-off


App obstruct macOS window server

After a few minutes the whole Finder get continuously blocked.

The problem is provoked probably because each time draw is called a new layer with new paths are created. All this graphic objects pile up continuously minute by minute, making WindowServer process to get jammed.


[red-knot] Add symbols for for loop variables

Summary
This PR adds symbols introduced by for loops to red-knot:

x in for x in range(10): pass
x and y in for x, y in d.items(): pass
a, b, c and d in for [((a,), b), (c, d)] in foo: pass

This is the first one of these PRs that I've done, so I hope I haven't missed anything!
Test Plan
Several tests added, and the assertion in the benchmarks has been updated.

Thanks @dhruvmanila and @carljm! Pushed some changes. Lmk if it's still not quite right.


Only suggest adding livecheck it auto-detection fails.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Fix audit failures for working livechecks.

Review period skipped due to critical label.


De-fake the cloud generator

Remove all GCP specific settings and references. Missing annotations can be provided using the configuration file.

I can see restoring the prior credentials file, and considering it something that belongs at the package level. And the scopes would be a combination of all services defined at that package, e.g. google.cloud.speech.v1. Do we want to make that change in this PR, or a separate PR?

Per @landrito's offline request, I have removed the expected output for all four configured services from the cloud generator tests, and the change to the showcase test to use the cloud generator. PTAL.

All issues have been created.


Enhancement print

Configured print to only print the active section + contact information.
Improved styles across all sections for print.
Fixes #323

Detected a Chrome bug which does not like hiding sections on page which crashes print dialog. Can only reproduce on my Chrome v60.0.3112.113. Prints fine in other browsers, hoping it's a one-off on my machine.


move datapackage dependency to tox.ini

fixes #11

Thanks @wardi! Great to hear that datapackage support is being improved in ckanapi!


h

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 28284335-e258-1c98-9017-65c35b8fcb48
Version Independent ID: 9e40fdb4-7a18-26cb-2923-567f273686d8
Content: service-oriented architecture (SOA) - Microsoft Style Guide
Content Source: styleguide/a-z-word-list-term-collections/s/service-oriented-architecture-soa.md
Product: non-product-specific
GitHub Login: @pallep
Microsoft Alias: pallep

Hi @zeinabkamel could you elaborate on your issue? Thanks!


2.3.0 Release Checklist

Ok, I think we should do a 2.3.0 release at the end of this month. What do we want to have included?

CDN Endpoints support
https://developers.digitalocean.com/documentation/v2/#cdn-endpoints


Flyin Donut: Text entry special icons are TINY

When entering your name for a high score, the caps, tab, shift, and backspace icons are very small, and were probably never resized from tom_thumb to ibm_vga8

Hmm, that's fair.  But, perhaps next year.  Actually, next year I might part-out the keyboard so it can be used elsewhere.

I thought you had already parted it out this year? Looks like it's self-contained in its own c and h files, as far as I can tell from a glance


1.4.1 Texfield multiline jest snapshot tests broken

When upgrading to 1.4.1 all our snapshot tests including a <TextField multiline /> are broken due to Error: Uncaught [TypeError: Cannot read property 'scrollHeight' of null].
We had similar issues in the past which were related to refs + react-test-renderer, but I couldn't spot any change in 1.4.1 yet which changed the ref logic.

related #5531

[x] This is a v1.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
minor version jump shouldn't break testing setup
Current Behavior
testing setup is broken
Steps to Reproduce
Snapshot <TextField multiline {...props} /> via jest.
Context
We render snapshots of all our pages to spot changes on component updates.
Your Environment

Tech
Version

Material-UI
v1.4.1

React
latest

@sakulstra I have removed some defensive checks that looks very much like dead code to me in #12238. I doubt the root of the issue is on Material-UI. The component can be mounted just fine on a browser environment.

I am having this issue as well. The issue is caused by the syncHeightWithShadow function inside of the Textarea component because it is attempting to access it's refs without ensuring that they are actually mounted.
https://github.com/mui-org/material-ui/blob/4eb6628e5be27a6c140c774069ea794d091c48c3/packages/material-ui/src/Input/Textarea.js#L121-L130
Our snapshot tests use Jest/Enzyme to do shallow rendering, which means child components are not mounted so the refs are null. There is currently no way for us to fix tests affected by this issue, save for just mocking the TextArea component, but that would cause the quality of the test to suffer.

Are you OK closing the issue for https://github.com/airbnb/enzyme/issues/1411?

@oliviertassinari I thought about disabling lifecycle methods. The problem I'm facing with that is we depend on the lifecycle methods to perform functional testing on a few of our components. Because we use storybook and the storyshots addon to perform snapshot testing, if I disable lifecycle methods, I will have to disable them for the entire project. I haven't figured out how to disable them on a per component basis yet, not sure it's possible.

@kanzelm3 With the information I have at hand, I deeply think it's an enzyme issue, but let's make the life easier for everybody. I think that we should be adding the defensive branch logic back 😢.


Group Issues from Original Repository

I added the issues from the original repository to a list and roughly grouped them into the categories

Crashes
Errors + Incorrect Parsing
Format issues
Feature requests
Misc

@andipabst, sorry for a slow response (I failed to set up proper notifications and haven't looked at the repo). If you are still interested, it'd be great to have you onboard in the project. Let me know what you prefer.


JavaScript autocomplete in script tag broken.

Hello, thanks for the nice plugin!
Looks like I might have the same problem as https://github.com/emmetio/emmet-atom/issues/587
Basically, inside of a <script> tag, I expect for JavaScript completion to work, but when I type something like
document.queryS

and hit tab then it unexpectedly becomes
<document className="queryS"></document>

As a workaround I can press enter instead of tab, but my muscel memory keeps accidentally hitting tab like I normally do in non-html files.
It'd be awesome if this could be fixed.

This plugin is outdated, try new one: https://github.com/emmetio/atom-plugin


Change field in math benchmarks to Stark field

TITLE
Description
Description of the pull request changes and motivation.
Type of change
Please delete options that are not relevant.

[ ] New feature
[ ] Bug fix
[ ] Optimization

Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

[ ] This change is an Optimization

[ ] Benchmarks added/run

Codecov Report

Merging #383 (b3c3f05) into main (61b26ab) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #383   +/-   ##
=======================================
  Coverage   93.60%   93.60%
=======================================
  Files          61       61
  Lines        7433     7433
=======================================
  Hits         6958     6958
  Misses        475      475

Impacted Files
Coverage Δ

math/src/unsigned_integer/element.rs
98.13% <100.00%> (ø)

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


DataPoints concept

In integration branch.
In order to reduce the "frictions" for the Python user, introduce the DataPoints notion that contains the result of dataNode execution

Not needed anymore, since Taipy integration.


0.8.19+ - Object doesn't support property or method 'isFrozen'

Browser: IE 11.2068.14393.0 Update Version 11.0.51
zone.js: 0.8.20
Last working zone.js version: 0.8.18
Since updating I've had the following error:

Object doesn't support property or method 'isFrozen'

function rewriteDescriptor(obj, prop, desc) {
    // issue-927, if the desc is frozen, don't try to change the desc
    if (!Object.isFrozen(desc)) { // <<<<<<<<<
        desc.configurable = true;
    }
    // ...
}

So the issue is related to the fix of #927
This is odd, seeing how isFrozen is natively supported in IE11.
Purely informational, I also have the following polyfills:
/** IE9, IE10 and IE11 requires all of the following polyfills. **/
import "core-js/es6/symbol";
import "core-js/es6/object";
import "core-js/es6/function";
import "core-js/es6/parse-int";
import "core-js/es6/parse-float";
import "core-js/es6/number";
import "core-js/es6/math";
import "core-js/es6/string";
import "core-js/es6/date";
import "core-js/es6/array";
import "core-js/es6/regexp";
import "core-js/es6/map";
import "core-js/es6/weak-map";
import "core-js/es6/set";

/** IE10 and IE11 requires the following for NgClass support on SVG elements */
import "classlist.js";  // Run `npm install --save classlist.js`.

/** IE10 and IE11 requires the following for the Reflect API. */
import "core-js/es6/reflect";

/**
 * Required to support Web Animations `@angular/platform-browser/animations`.
 * Needed for: All but Chrome, Firefox and Opera. http://caniuse.com/#feat=web-animation
 **/
import "web-animations-js" // Run `npm install --save web-animations-js`.

@Mysame , you need to import "core-js/es6/object".

@JiaLiPassion It's in there. 2nd line in the imports.

@Mysame, sorry I didn't see it, if you import object, isFrozen should be there. Could you post a reproduce repo?

I've got a suspicion it's Webpack-related.
It executes that piece of code a couple of times, until suddenly it can't.
The object 'desc' it's trying to execute it on is pretty interesting (see attachment

.

@Mysame , I think I still need a reproduce repo, could you just try to print Object.isFrozen or other polyfills which loaded by core-js.

I just had this problem in an aspnet core angular build where i import polyfills in bootbrowser.ts.
For me, it was solved by importing the polyfills before zone.js
import './polyfills';
import 'zone.js';

I can confirm this works.
I wouldn't call it a fix, though.

We have the same issue, when we split the polyfills for IE and for other browser like angular.io is doing

Has this issue been resolve? We are having the same issue except it only happens when my coworker compiles the project. The "if (!Object.isFrozen(desc)) ..." appear in his polyfill but when I compile the code it doesn't. We compared the package.json file and they were the same. How does polyfills.bundle.js file gets generated?

@davcyr , please post reproduce repo, thanks.

I am using angular 5 and has the same error. i have imported all mentioned by uncommenting. Also I have no bootbrowser.ts file. Kindly help!

@piyushkashyap14, please provide a reproduce repo.

will close it for now.


mention breaking changes in readme file

A lot of people don't use HtmlBars yet  and its causes confusion as to why the addon is throwing errors. I think it should clearly be mentioned on the readme file that if you are not on the latest ember you must pull in the '0.0.4' version of the addon. I was about to uninstall the addon but i was lucky to take a look at changelog at the very last minute.

It is already mentioned in the install section of the readme: https://github.com/cibernox/ember-cli-accounting#installation
In any case, if you had trouble to see it, anyone else might have too. I'll make it more visible.


Proposed icon

Here's a mockup/idea I came up with, perhaps inspired by a certain other icon but not a copy or derivative of it. Consider all work posted by me in this thread to be public domain.
<removed - see below>
Had to zip the SVG due to Github limitations.
<removed - see below>

And an alternative although perhaps a bit too close to another well known app's icon? Does allow him to be even hornier though (erm, see previous explanation).

Wtih zipped SVG.
MyYakYak2.zip

The second one looks mysteriously like Homestar Runner...

Haha I knew I recognised the shape! It was just a chat bubble rotated with an extra line.

Omnomnom. "I'm chewing grass to stop people confusing me with Homestar Runner."

Woke up with a couple more ideas.

Zipped SVG: MyYakYak5.zip

Procrastinating on something else, played about and made a .ico file, trying to make the lo-res ones look less like smudges.
MyYakYak-ico-xcf.zip

submitted in #21 closing issue
ps. looks really nice :)


Stackable items inside an item.

Hello everyone,
First of all, thanks for this awesome repo. I have some difficulties to handle my case with react-calentar-timeline. Well, let me explain my use case. I have to display an item which have multiple items inside (something like a background item of a group of items). The group of items inside of the background item should be stacked like the picture below.

I tried to set the startTime/endTime of the backgroundItem with a native date to exclude it from the stackItems props effect (this allow to put it in the background). And then, i set a boolean to true in my item data if it is a background item to handle the two styles cases (zIndex, backgroundColor, etc).
The problem is that i have a lot of sides effect like when I trigger a drag and drop or a resize event, the background item become stackable 😆.

P.S. I need this background item to be a real item (Clickable, draggable, resizable) not an unavailable layer like a saw in some examples.
Do you guys now how can I handle this case please ? Is it the right way to do this ?

Thanks for your reactivity ! 🤣

@HichamELBSI how is it possible to work with a 'background item'? I'm trying to implement one without any need to be clickable, draggable, etc, but I can't set if an individual item can be 'stackable' or not. So either I have something like your second print or all items at the same height, overlapping each other.


Add Access organization

Adds the Access organization resource: https://api.cloudflare.com/#zero-trust-organization-properties
Closes #1382

don't forgot to run make docs locally as well so it generates the registry documentation for you too.

acceptance tests look good
=== RUN   TestAccCloudflareAccessOrganization
--- PASS: TestAccCloudflareAccessOrganization (5.17s)
PASS
ok      github.com/cloudflare/terraform-provider-cloudflare/internal/provider   5.842s


Use Git instead of tarball for GTag extension

@SkizNet - I hope tagging you here will notify you. As the author of the GTag extension, do you have any thoughts on using the latest version of the code from GitHub, as opposed to using the downloadable .tar.gz file (which until now has been included directly in Canasta)?

@SkizNet hasn't responded here, but I asked him via email and he said that the Git version of GTag is fine, and that's what most people use. Can anyone please approve this PR?


Android 13 targeting investigation + disable AAID at GMS level

User Story
As a Product Owner,
I want to create a Curious Reader production build that targets Android 13 (API level 33) that disables Android Ad ID collection at the GMS level (see note from Google Play below for more),
So that we can QA test Curious Reader compatibility with Android 13 and fill out the additional compliance declarations on Google Play associated with Android 13 and have it checked for compliance by the Google Play Store.
From Google Play:
If your app is updated to target API level 33 (Android 13), ensure that your app or a library included in your app does not declare the new AAID permission, or that AAID is disabled. For more information on this permission and how to include or disable AAID, see this article. By updating to target API level 33 and not including the permission, AAID will automatically be disabled (set to a string of zeros).
Acceptance Criteria
Given that I have made a build of the Curious Reader container app that targets Android 13 (API level 33),
When I play it on a physical or virtual device that uses Android 13,
Then the app should behave as it did on previous versions of Android.

@burrage As the current prod app is working as expected and also is approved by play store, please let us know if we still need to proceed with this task?

@divyahariharan2103 We can indeed move this to DONE! The

line in the Android Manifest took care of the compliance stuff in conjunction with the new OS targeting :-)
Thankfully much easier than expected and less effort than we were anticipating with the 3! (hopefully!)

ok thanks Ben !!


KeyError in quickstart example

Hi @matthewwardrop , I'm running this repo from the quickstart with latest pypi version, and I got a ds key error:
import os
from mensor.measures.registry import MeasureRegistry
from mensor.backends.pandas import PandasMeasureProvider

registry = MeasureRegistry()

data_dir = "<path to checked out Mensor repository>/tests/data"

people = (
    PandasMeasureProvider(
        name='people',
        data=os.path.join(data_dir, 'people.csv')
    )
    .add_identifier('person', expr='id', role='primary')
    .add_dimension('name')
    .add_measure('age')
    .add_partition('ds')
)
registry.register(people)

people2 = (
    PandasMeasureProvider(
        name='people2',
        data=os.path.join(data_dir, 'people.csv')
    )
    .add_identifier('person', expr='id', role='unique')
    .add_identifier('geography', expr='id_geography', role='foreign')
    .add_partition('ds')
)
registry.register(people2)

geographies = (
    PandasMeasureProvider(
        name='geographies',
        data=os.path.join(data_dir, 'geographies.csv')
    )
    .add_identifier('geography', expr='id_geography', role='primary')
    .add_dimension('name')
    .add_measure('population')
    .add_partition('ds')

)
registry.register(geographies)

transactions = (
    PandasMeasureProvider(
        name='transactions',
        data=os.path.join(data_dir, 'transactions.csv')
    )
    .add_identifier('transaction', expr='id', role='primary')
    .add_identifier('person:buyer', expr='id_buyer', role='foreign')
    .add_identifier('person:seller', expr='id_seller', role='foreign')
    .add_measure('value')
    .add_partition('ds', requires_constraint=True)
)
registry.register(transactions)

transactions.evaluate(
    unit_type='transaction',
    measures=['value'],
    segment_by=['person:seller'],
    where={'ds': '2018-01-01'}
)

and KeyError:
Traceback (most recent call last):
  File "/home/guokr/.local/lib/python3.6/site-packages/pandas/core/indexes/base.py", line 2657, in get_loc
    return self._engine.get_loc(key)
 File "pandas/_libs/index.pyx", line 108, in pandas._libs.index.IndexEngine.get_loc
 File "pandas/_libs/index.pyx", line 132, in pandas._libs.index.IndexEngine.get_loc
 File "pandas/_libs/hashtable_class_helper.pxi", line 1601, in pandas._libs.hashtable.PyObjectHashTable.get_item
  File "pandas/_libs/hashtable_class_helper.pxi", line 1608, in pandas._libs.hashtable.PyObjectHashTable.get_item
KeyError: 'ds'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "demo.py", line 66, in <module>
    where={'ds': '2018-01-01'}
  File "/home/guokr/mensor/mensor/measures/providers/mutable.py", line 254, in wrapped
    return f(self, unit_type, measures=measures, segment_by=segment_by, where=where, joins=joins, stats_registry=stats_registry, stats=stats, covariates=covariates, context=context, **opts)
  File "/home/guokr/mensor/mensor/measures/providers/mutable.py", line 329, in evaluate
    **opts
  File "/home/guokr/mensor/mensor/backends/pandas.py", line 69, in _evaluate
    stats_registry=stats_registry, stats=stats, rebase_agg=rebase_agg
  File "/home/guokr/mensor/mensor/backends/pandas.py", line 107, in _finalise_dataframe
    df = cls._apply_where_to_df(df, where)
  File "/home/guokr/mensor/mensor/backends/pandas.py", line 209, in _apply_where_to_df
    return df[cls._get_constraint_for_df(df, where)]
  File "/home/guokr/mensor/mensor/backends/pandas.py", line 214, in _get_constraint_for_df
    return cls._get_constraint_maps()[constraint.kind](df, constraint)
  File "/home/guokr/mensor/mensor/backends/pandas.py", line 230, in <lambda>
    CONSTRAINTS.EQUALITY: lambda df, c: eq(df[c.field], c.value),
  File "/home/guokr/.local/lib/python3.6/site-packages/pandas/core/frame.py", line 2927, in __getitem__
    indexer = self.columns.get_loc(key)
  File "/home/guokr/.local/lib/python3.6/site-packages/pandas/core/indexes/base.py", line 2659, in get_loc
    return self._engine.get_loc(self._maybe_cast_indexer(key))
  File "pandas/_libs/index.pyx", line 108, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/index.pyx", line 132, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/hashtable_class_helper.pxi", line 1601, in pandas._libs.hashtable.PyObjectHashTable.get_item
  File "pandas/_libs/hashtable_class_helper.pxi", line 1608, in pandas._libs.hashtable.PyObjectHashTable.get_item
KeyError: 'ds'

Hi @ailurus1991! Thanks for trying out mensor! Mensor is not yet super stable, and I'm still mulling over certain aspects of its API. With that said, what works works pretty well.
Unfortunately, a limitation of the current MeasureProvider backend implementations is that they don't request from the data source columns that are only present in the where clause (this is not a limitation of mensor, only its concrete data source implementations). A fix for that will be "coming soon", after I am happy with the rest of the API.
As a work around, you can do:
transactions.evaluate(
    unit_type='transaction',
    measures=['value'],
    segment_by=['ds', 'person:seller'],
    where={'ds': '2018-01-01'}
)

many thanks for the super fast reply!
I tried:
transactions.evaluate(
    unit_type='transaction',
    measures=['value'],
    segment_by=['ds', 'person:seller'],
    where={'ds': '2018-01-01'}
)

and I got:
  File "demo.py", line 66, in <module>
    where={'ds': '2018-01-01'}
  File "/home/guokr/mensor/mensor/measures/providers/mutable.py", line 255, in wrapped
    return f(self, unit_type, measures=measures, segment_by=segment_by, where=where, joins=joins, stats_registry=stats_registry, stats=stats, covariates=covariates, context=context, **opts)
  File "/home/guokr/mensor/mensor/measures/providers/mutable.py", line 329, in evaluate
    **opts
  File "/home/guokr/mensor/mensor/backends/pandas.py", line 59, in _evaluate
    dimension.fieldname(role='dimension', unit_type=unit_type if not rebase_agg else None): raw_data.eval(dimension.expr) for dimension in segment_by
  File "/home/guokr/mensor/mensor/backends/pandas.py", line 59, in <dictcomp>
    dimension.fieldname(role='dimension', unit_type=unit_type if not rebase_agg else None): raw_data.eval(dimension.expr) for dimension in segment_by
  File "/home/guokr/.local/lib/python3.6/site-packages/pandas/core/frame.py", line 3203, in eval
    return _eval(expr, inplace=inplace, **kwargs)
  File "/home/guokr/.local/lib/python3.6/site-packages/pandas/core/computation/eval.py", line 299, in eval
    ret = eng_inst.evaluate()
  File "/home/guokr/.local/lib/python3.6/site-packages/pandas/core/computation/engines.py", line 76, in evaluate
    res = self._evaluate()
  File "/home/guokr/.local/lib/python3.6/site-packages/pandas/core/computation/engines.py", line 123, in _evaluate
    return ne.evaluate(s, local_dict=scope, truediv=truediv)
  File "/home/guokr/.local/lib/python3.6/site-packages/numexpr/necompiler.py", line 822, in evaluate
    zip(names, arguments)]
  File "/home/guokr/.local/lib/python3.6/site-packages/numexpr/necompiler.py", line 821, in <listcomp>
    signature = [(name, getType(arg)) for (name, arg) in
  File "/home/guokr/.local/lib/python3.6/site-packages/numexpr/necompiler.py", line 703, in getType
    raise ValueError("unknown type %s" % a.dtype.name)
ValueError: unknown type object

did I miss something or should I install Mensor from master branch?

Hmmm.... That doesn't look good; but also is not surprising. Since v0.3.1, I've torn apart a lot of the API and refactored a whole bunch more; and am still nailing the pieces back together. When v0.4 is released (hopefully later this year), things will be in much better shape. For the time being, I'd use v0.3.1 (which also has limitations), or wait. In its current form, I don't think mensor is ready for production use cases.

emmm, after I viewed Mensor's doc, I think I really need this in my data science project flow to save time. If I wanna join, could you show me a simple guide line? cuz I've check Mensor's source code for several hours and I found it's not that easy to understand the class/func design right now..

Hi @ailurus1991 ; I'm thrilled that you are excited by what mensor will offer; but it's just not yet ready to be used anywhere where frequent bugs and errors are not okay. It is still my pet research project, and is in alpha status. With the next release (0.4) where I am targetting API completeness, things will be different, but I have no fixed timeline for this release, and lots of things need to be changed before then (but I'd love to see it released sooner rather than later). I'm sorry that this doesn't line up with the timelines for your project :'(.

I found this sample data's ds column dtype lead to this KeyError.
in (build Provider's own df)[https://github.com/airbnb/mensor/blob/master/mensor/backends/pandas.py#L59]. I tried print(raw_data.eval('ds'))and I got the same error. I think the reason is Pandas's DF cant support eval operation on str dtype column(ds column in the test dataset)

Thanks to @danfrankj , looks like the master branch should work for you now @ailurus1991 . Thanks again for your interest :). I'm hoping to finish up the refactoring work ASAP, after which mensor should become much more stable!


Update Broadlink controller

Broadlink devices are now configured via config flow and broadlink.send is deprecated in favor of remote.send_command.
This update is necessary to keep things working after these changes.

Any idea when a RC will be available to test this out

It is already merged into the dev branch. It may take a while to be released, as the master branch is 511 commits behind dev and these updates will be merged gradually. This is the master branch of the Broadlink integration. You can look into it to check if the updates from dev are already merged.

It is already merged into the dev branch. It may take a while to be released, as the master branch is 511 commits behind dev and these updates will be merged gradually. This is the master branch of the Broadlink integration. You can look into it to check if the updates from dev are already merged.

but the smartir component needs to be updated to use it

You can pull this update from my fork. But you have to wait for the configuration flow update to be released in Home Assistant, or you can pull it from the dev branch to be the first to test.

Hi, just to mention that I tried this PR together with https://github.com/home-assistant/core/commit/a2c1f08c8ca01bed2dbdc0080fbe0287150d4c51 applied to home-assistant 0.114.4 and
https://github.com/mjg59/python-broadlink/pull/407, https://github.com/mjg59/python-broadlink/pull/410 and https://github.com/mjg59/python-broadlink/pull/412 applied to python-broadlink with a RM4 mini (0x62bc) and it works great (it didn't work before).

Thanks for you hard work testing this update. I'm happy to know that it works for the RM4 series.


Document production jobs on fifewiki

Document here:
https://fifewiki.fnal.gov/wiki/Getting_started_with_jobsub_lite
Give an idea of managed tokens, with tentative link to managed tokens on FIFE wiki.

I put a draft up on the wiki page.  It could probably use a review and some touch-up.

Cool - thanks Marc!

Made a couple of revisions.  Does this look good to you, Marc?

Yes, thanks!

Made one final edit.  I'm good with calling this done.


cmd/atlas/internal/cmdapi: introduce transaction mode for migration execution

This PR introduces the --tx-mode flag to specify the transaction strategy when applying pending migration files:

all: All pending migration files will be wrapped into one transaction. In case of an error, all files will be rolled back.
file: Each pending migration file will be wrapped in its own transaction. In case of an error, only the currently executed file gets rolled back.
none: No transaction. No rollbacks.

In addition, this PR changes the previous (buggy) behavior, where a rolled back migration was not reflected by the revision table. Now all rolled back revisions will get the Applied field set to zero. The previous PR already altered the logic to compute pending files to take this into account.
Postgres testscript has all of the above tested. Handling of special cases like MySQL implicit commits has to be discussed.

Postgres testscript has all of the above tested. Handling of special cases like MySQL implicit commits has to be discussed.

Can you please add test cases for SQLite and MySQL as well? This feels to me like one the most critical part in versioned migration.
Also, what are the open questions about implicit commit and MySQL?


PowerShell module for connections

Can this module only be executed by installing WAC in Gateway mode?

Detalhes do documento
⚠ Não edite esta seção. É necessário para a vinculação do problema do docs.microsoft.com ➟ GitHub.

ID: 239ce76b-e4b8-77d0-8e89-f35d85580e23
Version Independent ID: 4c8f067e-2a3d-2058-6a77-8028e3889843
Content: Get started with Windows Admin Center
Content Source: WindowsServerDocs/manage/windows-admin-center/use/get-started.md
Product: windows-server-threshold
Technology: manage
GitHub Login: @nwashburn-ms
Microsoft Alias: niwashbu

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Evaluation time is exponential w.r.t. the depth of the dependency graph

In particular the size of the nickel-res.json derivation. This gist contains code for the following dependency graph with variable depth, both created with native nix and organist. Evaluation of former seems to have the expected linear complexity, while for the one created with organist, it has exponential complexity.
This seems inevitable when we're passing the dependency graph from nickel to nix by serializing it to a tree with nickel export.

That's indeed a limiting factor for scalability. There's some work on the Nickel side to add some experimental support for directly calling Nix from Nickel (though it's not good-enough for our use-case yet), that plus RFC 92 could hopefully sidestep this problem altogether eventually


added a link in README to a post

Added a link in README.md section "Getting the blog up and running" to a post on medium explaining how the get the blog up and running on your system.

Instead of just linking to medium, why don't you try your hand at creating a blog post in our environment. That way people don't have to come to our github page they can just read the post on the community site.

I am nervous about writing an 'official' post. lol

Lol... Don't worry about it yet, maybe play with it on your local install and get use to using markdown language. I'll merge this into master.

Solid! :) :+1:

Love the idea of having it be a native post on the blog too!

I think what I'm going to do is make a video of the process that people can follow and then also add text of the process. @chaudhary27 did a lot of the ground work for me with his write up which is awesome!


Url pattern detection for direct redirects is not optimal

I had issues using chevron as I usually open links to ip addresses or localhost, etc. This is not possible with the current Regex that is used for URL detection.
I added a better one and wanted to make  it available for everyone.

See #16


Progress bars don't show after v1.39 update

Same exact config: with 1.39 or later progress bars don't show. 1.38 is the latest rclone version that makes rcloneBrowser show bars.
Checking "verbose output" doesn't seem to make a difference.

+1 to this, though for me size, bandwidth, elapsed time, transferred, errors & checks don't populate at all.

+1 to this, only progress bars of Elapsed time and Errors shows When I update my rclone to the lastest rclone v1.44.

Is it related to #117?
Upload progress blank? #117
Try using rclone from the command line and you'll note that there is no progress at all without the -P option.
       Note: Use the -P/--progress flag to view real-time transfer statistics
              rclone copy source:path dest:path [flags]

I'm building from these repos and the dialogs work okay for my use case:
nce/rclone
JanHellwig/RcloneBrowser

@noabody Your are so great , and I hope your can release your build or pull requests so I can use it since I don't have CMAKE environment in my Windows system.
On the other hands , Is it a good idea to get rclone version by using rcloneGetVersion() (https://github.com/mmozeiko/RcloneBrowser/blob/710663876d385b0d263b967495b2a2de07e7eb4a/src/main_window.h#L18) and then make different regexp?

https://github.com/DinCahill/RcloneBrowser/releases ?

As this repo is dead for so long I did some DIY combining various enhancements and fixes together and released binaries for macOS, Win64 and Linux64. If anybody is interested give it a try - https://github.com/kapitainsky/RcloneBrowser/releases


Install gtctl from Homebrew Tap

Reference: How-to-Create-and-Maintain-a-Tap.

The tap is ready: https://github.com/GreptimeTeam/homebrew-greptime.


sink/mq(ticdc): split json.go and add callback

What problem does this PR solve?

Issue Number: ref https://github.com/pingcap/tiflow/issues/5928
What is changed and how it works?

split json.go (rename some funcs)
add callback to encoder

Check List
Tests

Unit test

Questions
Will it cause performance regression or break compatibility?
No
Do you need to update user documentation, design documentation or monitoring documentation?
No
Release note
None

/run-all-tests

/run-all-tests

/run-all-tests

Codecov Report

Merging #6176 (9e9d80a) into master (ef587e6) will decrease coverage by 0.5657%.
The diff coverage is 67.6664%.

Flag
Coverage Δ

cdc
63.4255% <66.9955%> (-1.2591%)
:arrow_down:

dm
51.9092% <64.1509%> (+0.0201%)
:arrow_up:

engine
62.5993% <72.3618%> (+0.0654%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #6176        +/-   ##
================================================
- Coverage   58.4193%   57.8536%   -0.5658%
================================================
  Files           711        704         -7
  Lines         84205      83153      -1052
================================================
- Hits          49192      48107      -1085
- Misses        30540      30679       +139
+ Partials       4473       4367       -106

/run-all-tests


RFC: Tracing

I propose to introduce a mechanism to trace the GC and scheduler operations as they happen, when they happen and what they did, sometimes even measuring how long the operation took (e.g. GC.malloc).
This has proven invaluable at understanding multi-threaded synchronization issues, that would have been impossible to reproduce using a debugger (you can't step manually and hope to reach a race condition: you need brute force and then analysis). In addition tracing the GC can lead to interesting stats about how much time is spent on GC (malloc, collect, ...), or find out how many allocations happened and when they happen. Tracing both the GC and scheduler, we can cross analyze the lifetime of a program.
The tracing itself is relatively simple: each trace is a line with its section (gc, sched), the operation (malloc, enqueue, ...) then context metadata (thread, fiber, time, duration) and eventually metadata about the operation itself. The trace is meant to be easy to parse and read, to be grepped, searched, copy pasted, you name it.
I propose to have the tracing enabled with a compile time flag (-Dtracing) and to have the feature directly built right into the stdlib. It could be implemented into the perf-tools shard, but it would be harder to patch itself in (especially into the GC collection) and harder to maintain when the stdlib changes. It would also be harder to use, as you would have to add the shard & require it before you can start using it.
Once compiled with tracing enabled, each section should be enabled manually (by default they're all disabled) using the CRYSTAL_TRACE environment variable, which is a list of section names separated by a comma (,). For example CRYSTAL_TRACE=gc,sched would log everything, while CRYSTAL_TRACE=gc would only log the GC.
Evolutions
We could augment the tracing to report more/less data about the program, for example only output GC collection stats (with more before/after details). We could also listen to a signal (and/or a keyboard shortcut) to stop the world and print details about the threads and schedulers (that one would fit nicely into perf-tools for starters).
Technical notes
See #14599 for a proposed implementation and technical discussions.

To clarify/for the record: This is about logging for basic components of the Crystal runtime. We cannot use the sophisticated Log API because that itself builds on top of these runtime features. This has to be very low level.

The trace is meant to be easy to parse and read, to be grepped, searched, copy pasted, you name it.

Single-line log messages is great. But I'd suggest to use a standardized format instead of a kind of custom key=value sequence. JSON could be a good choice. It's maybe not as great in terms of human readability, but still quite okay. It's umabiguous and efficient to generate and parse. And it's super easy to pipe into all kinds of log analytics engines.
Dumping the trace unconditionally to stderr could mix up with application output going to the same file descriptor. We need to be able to isolate these different purposes from each other, i.e. write traces to a different location.
It might be fine to use stderr by default, but allow configuration of a specific file descriptor or a path to a file, via an environment variable. Tooling such as crystal tool trace could set that up automatically.

This is about logging for basic components of the Crystal runtime.

It's also meant to have the least impact on the program execution, so edge cases and race conditions can still be reproduced (not every time, it will still have some impact).

I'd suggest to use a standardized format instead of a custom sequence.

Good point for a standard format that could be easily ingested by external tools and databases (nice)! I hope I can find a better format than JSON that would hurt human reading (my main use case).

Dumping the trace unconditionally to stderr could mix up with application output going to the same file descriptor

Being able to trace to a file instead of stderr would be :heart:. I'm just afraid to lose the atomic write guarantee of pipes (up to PIPE_BUF bytes) that would lead to smashed traces when multiple threads are tracing.

This is great to have and will reduce the need to do manual printf when debugging. It is probably not needed at the first implementation, but at some point it would eventually be nice if the handling of the events would be pluggable with a pretty locked down interface (ie, no strings except for things like fiber names, just records with enums and measurements in the recording steps) - I'm thinking of shards providing support for something like https://github.com/mikesart/gpuvis/wiki , or pushing the values into hdrhistogram to be processed later or whatever, without having to monkeypatch anything.
That also changes the perspective a bit, as it immediately changes the discussion to be about generation and processing/presenting, as separate activities where the latter is up to the user.

Researching formats:

the key=value notation is very popular in line protocols (Syslog, OpenTSDB, InfluxDB);
traces add up quickly. For example the crystal compiler compiling itself leads to roughly 60 million events. The more complex the message, the more impact it has (speed, log size).

I'd thus like to have a couple formats. By default a format that is both & readable as possible. I propose to follow OpenTSDB line protocol:
<section>.<operation> <timestamp> thread=<0x1234>:<name> fiber=<0x9876>:<name> [key=value]

Then have a CRYSTAL_TRACE_FORMAT=json to output a bloated JSON string of the form (pretty printed for the sake of the format description, the trace will be on one line):
{
  "event": "<section.operation>",
  "timestamp": <timestamp>,
  "thread_id": "0x1234",
  "thread_name": "<name>",
  "fiber_id": "0x5678",
  "fiber.name": "<name>",
  "key": "value"
}

Notes:

The duration becomes a simple metadata attribute;
Strings should be enclosed within double quotes (especially for JSON), which means we must add support for escaping a character to Crystal::System.printf.

Single-line log messages is great. But I'd suggest to use a standardized format instead

Did you consider the OpenTelemetry Protocol (OTLP)? OTLP/HTTP maybe?
That could be fed into the Jaeger tracing platform, for example.
You can log time spans and log messages that way.
Ruby:
https://opentelemetry.io/docs/languages/ruby/
https://github.com/open-telemetry/opentelemetry-ruby
Line-based output would still be helpful for quick debugging, as OTLP can be slightly tricky to set up.
Maybe one of the OpenTelemetry exporters can do that.

the key=value notation is very popular in line protocols (Syslog, OpenTSDB, InfluxDB);

Yes, that's "logfmt".
https://grafana.com/docs/loki/latest/send-data/promtail/stages/logfmt/
https://brandur.org/logfmt
imho that's good for log messages, not so much for nested time spans though.

Reading the OTLP spec, it looks far too complex for the bare metal level we want here. It's not about tracing an application, but tracing the core runtime, down to each GC malloc for example.


[Bug]: T8213 unable to stream, seeing motion, ring is detected

I am not certain when functionality ceased but it might coincide with the last plug in update. I am now getting this message in the logs:
[17/02/2024, 08:41:13] [homebridge-eufy-security] This plugin slows down Homebridge. The write handler for the characteristic 'Selected RTP Stream Configuration' on the accessory 'DVH - Front Doorbell E5AC' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.
Also:
[02/17/2024, 08:29:57]  [EufySecurity]  ERROR   DVH - Front Doorbell Local livestream didn't start in time. Abort livestream request.
[02/17/2024, 08:29:57]  [EufySecurity]  WARN    DVH - Front Doorbell Could not get snapshot from livestream!
[02/17/2024, 08:29:57]  [EufySecurity]  WARN    DVH - Front Doorbell No camera source detected.
Device Type
Doorbell (Supported) T8213
Plugin Version
v2.0.x (Supported) v2.2.21
HomeBridge Version
v1.6.x (Supported) v1.7.0
NodeJS Version
other (UnSupported) v20.11.1
Operating System
Raspbian 10+ (Supported) v12-Bookworm
Relevant log output
[17/02/2024, 08:13:10] [homebridge-eufy-security] Restarting Process...
[17/02/2024, 08:13:12] [homebridge-eufy-security] Launched child bridge with PID 154472
[17/02/2024, 08:13:15] Registering platform 'homebridge-eufy-security.EufySecurity'
[17/02/2024, 08:13:15] [homebridge-eufy-security] Loaded homebridge-eufy-security v2.2.21 child bridge successfully
[17/02/2024, 08:13:15] Loaded 4 cached accessories from cachedAccessories.0EE1D1A47356.
[02/17/2024, 08:13:15]  [EufySecurity]  WARN    warning: planned changes, see https://github.com/homebridge-eufy-security/plugin/issues/1
[02/17/2024, 08:13:15]  [EufySecurity]  INFO    Country set: US
[02/17/2024, 08:13:15]  [EufySecurity]  INFO    Finished initializing!
[17/02/2024, 08:13:15] Homebridge v1.7.0 (HAP v0.11.1) (homebridge-eufy-security) is running on port 46279.
[02/17/2024, 08:13:26]  [EufySecurity]  INFO    Updating existing accessory: DVH - eufy HomeBase2
[02/17/2024, 08:13:29]  [EufySecurity]  INFO    Updating existing accessory: DVH - Back Door
[02/17/2024, 08:13:29]  [EufySecurity]  INFO    Updating existing accessory: DVH - Upstairs Door
[02/17/2024, 08:13:29]  [EufySecurity]  INFO    Updating existing accessory: DVH - Front Door
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    DVH - Front Doorbell Setting up automatic snapshot refresh every 60 minutes. This may decrease battery life dramatically. The refresh process for DVH - Front Doorbell should begin in 1 minutes.
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    DVH - Front Doorbell is set to handle snapshots with cloud images. Snapshots might be older than they appear.
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    DVH - Front Doorbell Empty snapshot will be sent on ring events immediately to speed up homekit notifications.
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    Publishing unbridged accessory externally: DVH - Front Doorbell
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    DVH - Upstairs Doorbell Setting up automatic snapshot refresh every 60 minutes. This may decrease battery life dramatically. The refresh process for DVH - Upstairs Doorbell should begin in 2 minutes.
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    DVH - Upstairs Doorbell is set to handle snapshots with cloud images. Snapshots might be older than they appear.
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    DVH - Upstairs Doorbell Empty snapshot will be sent on ring events immediately to speed up homekit notifications.
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    Publishing unbridged accessory externally: DVH - Upstairs Doorbell
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    DVH - Back Doorbell Setting up automatic snapshot refresh every 60 minutes. This may decrease battery life dramatically. The refresh process for DVH - Back Doorbell should begin in 3 minutes.
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    DVH - Back Doorbell is set to handle snapshots with cloud images. Snapshots might be older than they appear.
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    DVH - Back Doorbell Empty snapshot will be sent on ring events immediately to speed up homekit notifications.
[02/17/2024, 08:13:30]  [EufySecurity]  INFO    Publishing unbridged accessory externally: DVH - Back Doorbell
[17/02/2024, 08:13:30] DVH - Front Doorbell E5AC is running on port 34577.
[17/02/2024, 08:13:30] Please add [DVH - Front Doorbell E5AC] manually in Home app. Setup Code: 147-83-994
[17/02/2024, 08:13:31] DVH - Upstairs Doorbell 2835 is running on port 36839.
[17/02/2024, 08:13:31] Please add [DVH - Upstairs Doorbell 2835] manually in Home app. Setup Code: 147-83-994
[17/02/2024, 08:13:31] DVH - Back Doorbell F906 is running on port 39797.
[17/02/2024, 08:13:31] Please add [DVH - Back Doorbell F906] manually in Home app. Setup Code: 147-83-994
[02/17/2024, 08:14:01]  [EufySecurity]  INFO    Looking for old cached accessories that seem to be outdated...
[02/17/2024, 08:14:01]  [EufySecurity]  INFO    No outdated cached accessories found.
[02/17/2024, 08:14:40]  [EufySecurity]  ERROR   DVH - Front Doorbell Local livestream didn't start in time. Abort livestream request.
[02/17/2024, 08:14:40]  [EufySecurity]  WARN    DVH - Front Doorbell Could not get snapshot from livestream!
[02/17/2024, 08:14:40]  [EufySecurity]  WARN    DVH - Front Doorbell No camera source detected.
[02/17/2024, 08:15:40]  [EufySecurity]  ERROR   DVH - Upstairs Doorbell Local livestream didn't start in time. Abort livestream request.
[02/17/2024, 08:15:40]  [EufySecurity]  WARN    DVH - Upstairs Doorbell Could not get snapshot from livestream!
[02/17/2024, 08:15:40]  [EufySecurity]  WARN    DVH - Upstairs Doorbell No camera source detected.
[02/17/2024, 08:16:40]  [EufySecurity]  ERROR   DVH - Back Doorbell Local livestream didn't start in time.  The write handler for the characteristic 'Selected RTP Stream Configuration' on the accessory 'DVH - Front Doorbell E5AC' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.
[02/17/2024, 08:41:14]  [EufySecurity]  ERROR   DVH - Front Doorbell Local livestream didn't start in time. Abort livestream request.
[02/17/2024, 08:41:14]  [EufySecurity]  ERROR   DVH - Front Doorbell Unable to start the livestream: no started livestream found

config
{
    "enableDetailedLogging": false,
    "CameraMaxLivestreamDuration": 30,
    "pollingIntervalMinutes": 10,
    "hkHome": 1,
    "hkAway": 0,
    "hkNight": 3,
    "hkOff": 63,
    "ignoreStations": [],
    "ignoreDevices": [
        "T8113N1319472ED7",
        "T8113N131949795F",
        "T8113N1320100B85"
    ],
    "country": "US",
    "cameras": [
        {
            "serialNumber": "T8213P11215106B3",
            "rtsp": false,
            "enableCamera": true,
            "enableButton": false,
            "motionButton": false,
            "indoorChimeButton": false,
            "immediateRingNotificationWithoutSnapshot": true,
            "refreshSnapshotIntervalMinutes": 60,
            "snapshotHandlingMethod": 3
        },
        {
            "serialNumber": "T8213P11220501E0",
            "rtsp": false,
            "enableCamera": true,
            "enableButton": false,
            "motionButton": false,
            "indoorChimeButton": false,
            "immediateRingNotificationWithoutSnapshot": true,
            "refreshSnapshotIntervalMinutes": 60
        },
        {
            "serialNumber": "T8213P1122050C83",
            "rtsp": false,
            "enableCamera": true,
            "enableButton": false,
            "motionButton": false,
            "indoorChimeButton": false,
            "immediateRingNotificationWithoutSnapshot": true,
            "refreshSnapshotIntervalMinutes": 60
        }
    ],
    "cleanCache": true,
    "unbridge": true,
    "username": "EMAIL",
    "password": "PASSWORD",
    "deviceName": "",
    "platform": "EufySecurity",
    "_bridge": {
        "username": "0E:E1:D1:A4:73:56",
        "port": 46279
    },
    "stations": [
        {
            "hkHome": 1,
            "hkAway": 0,
            "serialNumber": "T8010P1321492A0A",
            "hkNight": 3,
            "hkOff": 63
        }
    ]
}

This has been reviewed - The connection to Eufy appears to be working as I am getting push notifications for doorbell rings and contact switches are functioning.

I was getting the 'livestream didn't start in time' error on my Eufy S220 doorbell. I tried everything I could think of this weekend to troubleshoot. What finally fixed it for me was rolling back from node.js version 20.11.1, back to 18.15.0 (the minimum for Homebridge 1.7.0. Once I did this I could start livestreaming video from my doorbell again.

I considered this as well. Thanks for posting! I will try this as well. Perhaps incrementally back versioning node.js

node.js 20.11.1 - issue encountered
node.js 20.11.0 - issue not encountered
Well, @JayRKay  is a genius! 👍🏻
My apologies to the developers. It was not the app upgrade, it was the node.js update.
For now, issue resolved for me.