Sangjeedondrub patch 1

Do you want to add multiple authors?
I test your patch for the default config file. There are some ERROR.
 error calling partial: template: partials/head.html:28:32: executing "partials/head.html" at <.Params.author>: range can't iterate over xianmin

It is best able to be compatible with the default configuration.

I find two related links:

[SOLVED] Multiple Authors w/ Own Article List (site.com/authors/author-name/article.md) - support - Hugo Discussion
sethmacleod/hugo-multi-author: Simple multi-author blog for the Hugo Static Site Generator

If we want to do this well, maybe we need more work.

The links you provided help is very informative and solve my issue. Thanks.


Deciding on binary question text (yes/no? agree/disagree?)

Right now, the app handles "structured questions" (the ones where you press 1 or 2) by having only two, hard-coded options — "repair" and "remove". This is vestigial from the South Bend case.
Because it'll be a fair bit of development work to allow for customizable numbers of, and text for, structured questions, we want to select a reasonable default for where the codebase is now.
Some options:

Yes / No
Agree / Disagree

@migurski has a strong leaning towards 2, and I'm fairly agnostic.
@cyd — do you have thoughts on this?
@waltz and @rduecyg — in your South Bend reuses, did you learn a bit more about what users might like?

@jmadans I'd love your thoughts on this.

Still an open issue. For our pilots, I've decided to constrain the cities to Agree/Disagree statements.
In line with @dave's assumption, Cities don't have a clear preference for how to structure the binary question. It's dependent on the question. The fix here is to offer them a drop down menu to customize their question type.
I think we should offer three question types:

Yes/No Question
Agree/Disagree Statements
1-5 Scale question


Add ability to enable or disable the "Logo"

Add the ability to either have no logo or have a choice between a text or image logo.

Done, branch - 20220317-no_logo. Will merge into main.


#99: add credentials to all requests

This change is

Coverage remained the same at 48.485% when pulling fb78476cf1d68d0fdab0c5b92b1d41cb8628b641 on feature/liort_user_pass into 60d9afd7df8daaaecdebab8cbdb433273099dc1d on dev.


Addition of user service tests

Motivação
O serviço de users possuiam algumas funções sem testes unitários
Mudanças feitas
Adição de testes em funções do user service
Tarefa relacionada

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
19.3%

Covered Lines:
115

Relevant Lines:
149

💛  - Coveralls


Minor update to calendar history requests

This PR summarises:

The 15 minute interval parameter that can be used with the day period in calendar history.
Some of the idiosyncrasies seen in Tesla data sets generated with calendar history requests.
Links to a gist for anyone who wants to continue the work of resolving inconsistencies in these data sets.

Thanks!


How to add additional headers to journal file?

Hi,
I'd like to export my journals to HTML, but don't need a header numbering, so normally I would add a header #+OPTIONS: num:nil to the file.
How can this be done automatically for each newly created journal file? I'm not that experienced with Emacs/Elisp.

You could use the org-hournal-after-entry-create-hook and insert your text at the beginning of the buffer, for example like this:
(add-hook 'org-journal-after-entry-create-hook
            (lambda ()
              (save-excursion
                (beginning-of-buffer)
                (insert "#+OPTIONS: num:nil\n\n"))))

I use something similar to add file example #+FILETAGS to my journal files.

Another option is to modify org-journal-date-prefix, for example:
(setq org-journal-date-prefix "#+OPTIONS: num:nil\n* ")

(default is "* ")

Is there a way to get a default File template  say
#+TITLE: Daily Journal for (date-format)'

Status  yada yada (stuff)
Entries      {everthing above including this line pulled from a template}
** 00:01  starting entries
** 00:30  adding notes to journal

end

While this would be possible with just org-journal's templates, something like @martinbalfanz' solution is probably easier to maintain.

Related to #153


Layout is not visible on Release build

Shows container instead of layout,but debugging one is showing well.
Created my own layouts and also tested your Example code,but nothing is showing in release mode

Please show me flutter log. And does this happen which on Android or iOS?

@sakebook  It does not logs anything,and Ive never tried on Ios,it happens only on Android.
Debugging is working superb,the release build the widget is simply white

I'm also having the same problem, it was working normally in the debug and release, but now the widget only renders a blank space

Same problem

I added the following to my proguard-rules.pro and Ads show up in release.
`## Admob
-keep public class com.google.firebase.analytics.FirebaseAnalytics {
public *;
}
-keep public class com.google.android.gms.measurement.AppMeasurement {
public *;
}`


1 day retention support

Removed the "less than 30 days not supported" Statement as the true 1 day feature is shipped.

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@LolaJacobsen PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

I ping'd the PM to confirm.

PM confirmed.


lift merge check up to Blockchainprovider

Describe the feature
currently we use:
https://github.com/paradigmxyz/reth/blob/875cee27aca747315af1ef2a9dcdf29e058b33e7/crates/storage/provider/src/providers/database/mod.rs#L230-L234
on db provider level, when we should check this here:
https://github.com/paradigmxyz/reth/blob/875cee27aca747315af1ef2a9dcdf29e058b33e7/crates/storage/provider/src/providers/blockchain_provider.rs#L305-L306
and
https://github.com/paradigmxyz/reth/blob/875cee27aca747315af1ef2a9dcdf29e058b33e7/crates/storage/provider/src/providers/mod.rs#L197-L203
because these types should have access to the chainspec, this will allow us to get rid of the chainspec on the databaseprovider:
https://github.com/paradigmxyz/reth/blob/875cee27aca747315af1ef2a9dcdf29e058b33e7/crates/storage/provider/src/providers/database/provider.rs#L112-L113
Additional context
No response

closing for now because might not be possible rn, and maybe not useful.


Support building separate container for cython3

Affects:

[x] cythonize.sh
Also see Issue 5

Fixed in 17f0356


Add active state for star button

Currently the star icon button on :active gets colored yellow, however it is more convenient to also add an active state for the button (a new class .active) where the color of the star will be yellow. It should also have a nice transition between the inactive and active state. It shouldn't be displayed on the website, but if someone adds the class .active to the button or removes it, the transition should look nice.

Can I do it please ? I just have 1 small other pending issue

@crew-guy I really appreciate you contributing to this repository but I can't give you too many issues to work on at the same time. Once you finish at least one of them you can then get assigned to a new one. Thank you!

@shahednasser I already forked the repository but I forget to add comment here. Could you assign this to me?

sure @pontakornth but please follow the other instructions I gave you as well.

@crew-guy I really appreciate you contributing to this repository but I can't give you too many issues to work on at the same time. Once you finish at least one of them you can then get assigned to a new one. Thank you!

Yaya cool ! Guess I am taking wayy too much work to properly process and finish it all 😂✌🏻

can you assign this to me? thanks

sure @pontakornth but please follow the other instructions I gave you as well.

Done. The check is still failed and I have no idea why.

i would like to contribute


Fix for TTML alignment (non-centered) in Firefox

It was discovered that TTML alignments that is not centered (e.g. left) was shown incorrectly in Firefox. The reason I discovered was that the cue.positionAlign was not set and defaulted to "center". This caused the subtitles to be positioned on the left (when tts:textAlign=left) but with the text center aligned.
Note that for Firefox v48 or lower the implementation of cue.positionAlign did not fully follow the spec and was corrected in v49 and above.

@ismena, this looks reasonable to me, but you have more experience here.  Any objections?


Non-Rendering Chart with Extended Width & Pixelated Chart Lines

Hey all -- I'm having a responsive: true Chart width issue that is similar to all the scenarios in Issue #56 . I've attempted implementing several of the stated solutions, but have had no luck so far. Does anyone have suggestions?
Issue:

After a certain pixel width, the Chart no longer renders. For me, that break point is around and above 19,000 pixels wide.
The Chart Lines get pretty darn blurry the wider the chart.
Here's a CodePen showing my issue: https://codepen.io/tcraw/pen/bYdMrN
(I'm not actually using JQuery in my app code -- just used it because I was being lazy. Just needed a quick replication scenario.)

My Current Requirement:

Draw a Line Chart that matches up with a table of data below it (we want to scroll the table and see the correlated data plots on the line chart -- the table headers / x-axis labels are dates. This of course means matching the Chart width with the width of the table dynamically (the table may contain up to 1.5 - 2 years of dates).

Chart Configuration:

Using ChartJS version 2.7.0
The <canvas> element has a position: relative style and is in a wrapper .
The wrapper  has a width: 100% style.
The Chart Options have var lineGraphOptions  = { responsive: true, maintainAspectRatio: false, etc... } settings.
I am calling new Chart(lineCtx, { type: 'line', data: lineGraphData, options: lineGraphOptions }) in an angular $timeout function so I can grab the actual width of the table once the data lookup occurs and the table is rendered.

Environment:

Chrome (61)
Firefox (56)
Edge (40)   ---  Edge renders the chart despite a high pixel width, and also provides crisp chart lines! However, the chart is still getting cut off at a certain point.

There was at least one issue related to responsiveness that was fixed in 2.7.1. Can you update the codepen to 2.7.1 and confirm if it's still an issue?

@benmccann
Definitely -- I just updated the CodePen to the .../2.7.1/Chart.js CDN and no dice unfortunately.
Updated CodePen Link: https://codepen.io/tcraw/pen/bYdMrN
Also I should mention that I am applying the width to the chart wrapper  style:
chartWrapper.style.width = width + "px";
chartWrapper.style.height = height + "px";

If I apply styling or attribute sizing to the canvas directly, it will only fill 100% of the viewport no matter the overflow setting. (Perhaps I'm just missing some simple css rule to deal with that, but I thought it worth mentioning.)

That could possibly be related to https://github.com/chartjs/Chart.js/pull/4874?

My gut on this is that something is hitting the limits of canvas draw APIs. As far as I know, nothing we've written has a max size hardcoded anywhere.
As an aside I've seen this in various browsers with SVG before. For instance, on Safari is a horizontal line of an SVG path is longer than 4096 screen pixels (not css pixels) it fails to render past the 4096th pixel.

@benmccann Looking at #4874, I assume that there was possibly a discrepancy applying height/width styling directly to a canvas -- I did actually try both applying styling as well as trying to change the canvas width attribute and received the same results (unless I was targeting incorrectly?).

// Attribute Application
var ctx = canvas.getContext("2d");
ctx.canvas.width = width / pixelRatio;

// Styling Application
var canvas = document.getElementById("canvas");
$(canvas).attr('width', (width / pixelRatio));

@etimberg I think that may be the situation -- that the canvas draw API may be enforcing a pixel limit (though I haven't confirmed by looking at the HTML5 Canvas docs).
You can actually see the picture a bit clearer by running my Codepen in Edge: It seems to approach the rendering a bit differently than Chrome or Firefox -- rather than just not rendering if its width limit is hit, it renders only what it can up to cut-off point.

Disabling the clipping works around this limitation:
Chart.helpers.canvas.clipArea = function() {};
Chart.helpers.canvas.unclipArea = function() {};

https://codepen.io/kurkle/pen/mdOvNYN

As of 3.4.0 clip: false should be a workaround for this.


Please migrate from BlueSocket and BlueSSLService to swift-nio

Migrate from BlueSocket and BlueSSLService to definitely preferred Apple's open source swift-nio.
Currently BlueSocket and BlueSSLService block modern versions of swift-argument-parser. They depend on 'swift-argument-parser' 0.4.1..<1.0.0. It's definitely wrong when networking libraries (not their applications) depend on argument parser.

NIO has its own PG library (https://github.com/vapor/postgres-nio). Though PG access doesn't really make sense in a non-blocking context in the first place. Would be nice to keep that as a proper blocking lib.

Let's move the swift-argument-parser version constraint problem to #42.
And use this issue (#41) to explore the bigger question of moving PostgresClientKit from BlueSocket/BlueSSLService to swift-nio.

(1) I'd also like to be rid of BlueSocket/BlueSSL in favor of Network Framework, which is already baked into macOS, iOS, watchOS, and tvOS. I've moved all my API services from Swift-NIO to NW-framework and not looking back. NIO is somewhat long in the tooth and I consider it bloatware at this point. WIth no async/await and now only Vapor as its chief supporter, one has to wonder how long NIO will be maintained in its current form.
(2) Speaking of async/await... Overall performance and ease-of-use would also be improved if PostgresClientKit moved to an async/await model instead of dispatch. Dispatch is not totally dead, but it's slow-walking toward the graveyard.

I agree that removing the BlueSocket/BlueSSLService dependencies is highly desirable.  Thank you for your thoughts about SwiftNIO vs. Network Framework.  Right now, I don't know enough to have my own opinion on this.  @helje5, you have written about this.  Do you have any further guidance on selecting a framework for a non-HTTP TCP client?
I see how an async/await API would be helpful for ConnectionPool, replacing the completion handler pattern.  Do you see benefit to async APIs elsewhere?

(1) We're almost 3 hours into the change of timeout value back to 0, and the behavior has be much, much better.  I’ll know more after 24 hours or so. But for now, it looks like the correct change. I guess somewhere along the way I simply missed the part where the workaround required the timeout to be 0. Most likely I read right over that tidbit and it simply bounced off my thick skull LOL!
(2) I originally wrote all my APIs in Swift using the NIO framework as the HTTP wrapper.  NIO handles all the client-facing networking (i.e. certificates, https handshaking, etc.) and eventually hands all client request data to your API code.  At this point the API does its thing and hands the results back to NIO, which runs it back down the output pipeline to the remote client. It works, It’s reliable, and it’s also large, complex, and full of it’s own concepts and paradigms.
But that was 2018-ish and NIO was the only thing for server-side Swift.  NIO is reliable for sure, and it also has a Postgres-NIO add-on that is also reliable, but also equally difficult to implement. NIO is also thread-centric, and has its own promise/future/runloop mechanism that I could never fully grasp (thick skull syndrome again). After years of conditioning my brain to dispatch queues, the thread-centric model of NIO seemed very foreign to me. Most NIO programming for me consisted of copy/paste/pray. I can say I’ve never fully understood it.
Now, here we are in 2023 and Swift 5.7 is well down its own runtime concurrency path. This model is something completely different from NIO’s promise/future system, and has analogs back to dispatch. I suspect that async/await/actors are built on top of dispatch, or at least a framework that’s both dispatch-aware and dispatch-cooperative. That, along with the fact that this new model has once again booted explicit threads and runloops out of the programming vernacular, has really benefited my mental picture of how it’s working under the hood.  As for the HTTP wrapper part, I’m using Apple’s native Network Framework, which they have put forth as an IETF standard. In fact, NIO will run on top of Network Framework if it's running on an Apple device.  Network Framework is not tied to any particular protocol, but operates at the TCP/UDP level and should easily handle persistent TCP/IP connections. So I’ve had to implement my own HTTP server protocol on top of a Network Framework listener object.
The big benefit I see from async/await is that it’s effectively a runtime sub-thread scheduling system. No longer does the entire thread have to context switched to/from a CPU core.  In stead, a thread can stay in context on the CPU to which it is assigned, and the Swift runtime uses its internal trickery to do on-thread context switching of just the code blocks and stack segments that need switching. I’m not sure how it all works, but my API is now at least 15% faster on the same CPU.  I also suspect that async/await will allow future versions of Swift to generate more and more efficient scheduling code for ARM cores.  Since async/await is embedded in the programmer’s code, this optimization can be become very specific to the function and code block at hand.
Async/await will definitely improve overall program flow as it eliminates virtually all closures. In addition, rewriting your connection pool as a singleton Actor will eliminate virtually all the code you have tied up in dispatch queue management and avoiding race conditions.
—Barry

On Feb 15, 2023, at 12:38 PM, David Pitfield [dbp] @.***> wrote:
I agree that removing the BlueSocket/BlueSSLService dependencies is highly desirable. Thank you for your thoughts about SwiftNIO vs. Network Framework. Right now, I don't know enough to have my own opinion on this.  @helje5 https://github.com/helje5, you have written https://www.alwaysrightinstitute.com/network-framework/ about this. Do you have any further guidance on selecting a framework for a non-HTTP TCP client?
I see how an async/await API would be helpful for ConnectionPool, replacing the completion handler pattern. Do you see benefit to async APIs elsewhere?
—
Reply to this email directly, view it on GitHub https://github.com/codewinsdotcom/PostgresClientKit/issues/41#issuecomment-1431835389, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTRL5C5QRQBO6SIDCLEBJLWXUPD5ANCNFSM53YSZUAQ.
You are receiving this because you commented.

Thanks for the update.  Please see my comment over at #10.

Thanks for sharing your experience and thoughts on Swift NIO & Network Framework.  Appreciated!

Thanks, David, for your expeditious assistance. I went back and re-read the API docs. And sure enough, for socketTimeout: "The timeout for socket operations, in seconds, or 0 for no timeout." In my mind, I was mistakenly reading this as "The timeout for the socket to complete the connection."  It's much clearer to me now that this means ALL socket operations for a given connection, including wait time for the remote server to respond.
My initial 10-second value wasn't causing a problem at first. But as my API service has become more and more busy, this value was not allowing enough time between the Execute statement and when a loaded-down, remote server could finally respond.  I wasn't comfortable with a "never timeout." So I've set the production value to 300 and it seems to be humming along in splendid fashion, even in SSL mode. More CPUs in the AWS config are certainly on the docket as well.


cant create ERC20 Deposit Address

Hi i have tried create deposit address but i dont know why it not work
ETH Deposit Address working normal

TST(test token testnet) Deposit Address not work

Daemon log

Send API request to generate address.
Re-Check Blockchain configuration.
Re-Check Contract address.
Re-Check Deposit wallet and Hot wallet address, and blockchain info in wallet section (for tst).
Check Log of geth/parity to verify the RPC queries and response.

Send API request to generate address.
Re-Check Blockchain configuration.
Re-Check Contract address.
Re-Check Deposit wallet and Hot wallet address, and blockchain info in wallet section (for tst).
Check Log of geth/parity to verify the RPC queries and response.

hi adarshdubeytech
erc20 working normal
just ask

now work
forgot add deposit wallet


New loaders to inspire from.

This thread contains all the new loaders to inspire and add them in this project.

https://codepen.io/golle404/pen/JXmzaE/


Allow already initialized Sentry instances to be used in other packages

Problem Statement
Description
The current static only approach doesn’t gracefully allow other packages to rely (inject) on a Sentry instance that has already been initialized.
Such scenario can be seen in application packages (refer to the example Use case below), and also within other Sentry packages, as in package:sentry_flutter or as outlined by @uemann in a discussion. Some workarounds require to ignore the warning // ignore: invalid_use_of_internal_member,  however, ignoring internal members is discouraged and is not the best way to resolve the issue. I would like the Sentry package to support such use cases gracefully without having to work around it or ignore warnings.
Relevant discussion:

https://github.com/getsentry/sentry-dart/discussions/2073

Use case
In occasions you may have an Application Package (as defined in the Dart documentation) that depends directly on two packages: package:flutter_sentry and a Dart Package that depends on package:sentry (see illustration).

The Dart Package does not depend on Flutter. The Dart Package has classes and methods that rely on a package:sentry . These methods abstract away package:sentry  functionalities, for example captureEvent . The Dart Package wraps around them, includes additional logic and ensures that the Application Package doesn’t have a strong dependency with Sentry (meaning it can be swapped out by another Dart Package that relies on a different application performance monitoring [APM] provider easily when implementing a common interface). The illustration below shows how the application would easily swap out the Sentry dependency for another APM provider. For more information about the pattern refer to the Very Good Flutter architecture blog post.

The Dart Package does not initialize Sentry, the Application Package does. The static Sentry instance that has been initialized in the Application Package can’t be passed as an argument to the Dart Package, making the following obviously not possible:
// package:my_app
void main() {
  // ...
  await Sentry.init((options) => options.dsn = 'dsn');
  final apmClient = MySentryClient(client: Sentry)
  // ...
}

// package:my_another_apm
class MySentryClient implements MyApmClient {
  const MySentryClient({
    required this.client,
  })

  final Sentry client;

  // ...
 }

Instead, it is preferred that the Dart Package gets injected a SentryClient or a Hub so that it can access its useful methods, for example:
// package:my_app
void main() {
  // ...
  await Sentry.init((options) => options.dsn = 'dsn');
  final sentryClient = SentryClient(Sentry.currentHub.options);
  final apmClient = MySentryClient(client: sentryClient)
  // ...
}

// package:my_another_apm
class MySentryClient implements MyApmClient {
  const MySentryClient({
    required this.client,
  });

  /// The Sentry client.
  final SentryClient client;

  // ...
 }

However, the above will report an invalid_use_of_internal_member. Meaning that the above usage is “invalid” and is ultimately discouraged. According to @ueman it is currently protected so:

[…] other Sentry libraries (files, dio, etc) to read from the options since they can't be initialized during the Sentry init call.

One could pass callbacks for each Sentry static method, as such:
// package:my_app
void main() {
  // ...
  await Sentry.init((options) => options.dsn = 'dsn');
  final sentryClient = SentryClient(Sentry.currentHub.options);
  final apmClient = MySentryClient(
  captureEvent: Sentry.captureEvent,
    addBreadcrumb: Sentry.addBreadcrumb,
  );
  // ...
}

However, the above is largely inconvenient since it will require the developer to define the function signatures to be injected in MySentryClient for each method, increasing the maintenance burden for future updates compared to simply relying on the SentryClient or Hub that already provide such methods without having to specify the signatures of each method.
Solution Brainstorm
Draft proposals
Below some changes that might help solve the above inconvenience:

Define a view only (immutable) SentryOptions (similar to those found in dart:collection, for example UnmodifiableListView) so that accessing the options outside the init method can be done safely. Then make a getter so that it is publicly accessible, not protected. The same view-only approach might apply to other relevant classes for this to be plausible.
Refactor the package to stop using a static Sentry to perform operations. In essence, the current approach introduces:

A global variable (can’t be properly scoped) and developers can’t rely on their own preferred dependency injection tools to access Sentry .
It is somewhat against the Effective Dart guideline (when only considering its public API) and its matching lint rule avoid_classes_with_only_static_members.
It makes it cumbersome to benefit from the object oriented paradigm (which Dart is great at), since static methods make it purely functional.

Open to any other solutions that resolve the described inconvenience

Are you willing to submit a PR?
None

You can use the static classes of Sentry without initializing it in the package, though. If the application properly initializes Sentry, the events from the package are properly send.
So the following example
// in application code
SentryFlutter.init(...);

// in package code
Sentry.captureException(...);

works and reports the errors properly to Sentry. Sentry does all of the required things internally.
That's also how the other Sentry packages work. They simply use the static methods internally. They only need the options for configuration, not for reporting of the actual exceptions/performance traces etc. So in theory, the other Sentry packages could work without having access to the Sentry options.
Even Sentry itself uses the static methods internally: https://github.com/getsentry/sentry-dart/blob/e6b16cd4aa51b0236a52f4c6380d53b6d1a1aee9/dart/lib/src/hub_adapter.dart
If you need testability, I would recommend writing something like the HubAdapter (as mentioned above) yourself.

Hi @ueman thanks for the quick reply! The information helps! I've left some questions based on your information, hopefully you can provide some clarity on those.

You can use the static classes of Sentry without initializing it in the package

That's good to know. I've added documentation in #2093 around such behaviour (since I wasn't sure if it was purposely designed for so, or if it was a discouraged behaviour) and added some documentation around the information you shared on #2073.

If you need testability, I would recommend writing something like the HubAdapter (as mentioned above) yourself.

Is there any documentation around testing Sentry for Dart/Flutter? What is the preferred way to verify that calls to Sentry (such as, Sentry.captureEvent) get called?
I can't find testing related documentation on https://docs.sentry.io/platforms/flutter/ or https://docs.sentry.io/platforms/dart/. It seems that Node has some, https://docs.sentry.io/platforms/javascript/guides/node/best-practices/sentry-testkit/, is there any tracking effort to document and improve the testing experience for Flutter and Dart?
Testability is very important for mostly all developers, and if instead of using static members the package provided an instance it would be very simple to mock in tests. I believe there are currently ways to overcome it, but they are far from perfect and hinder the developer experience.

With the current approach, what happens when you would like to have two Sentry instances that you would like to report information to? How would you report captured events for one and not the other?

What happens if a package initialised Sentry to collect information, the application also initialises another Sentry to collect another information, and there is another package that would like to rely on the Sentry that got initialised in the application (not the one from the first package)? What would the static Sentry members (in the latter package) used on this rely on, would it work as expected?
Here's some code to exemplify the above:
// in package B
Sentry.init(...);

// in application code
SentryFlutter.init(...); // different DSN

// in package C
Sentry.captureException(...);

I'm also curious to know what is the motivation for making everything static and global rather than letting the user have an actual instance?
I'm guessing that the "static everything" approach might be a consequence of trying to make the package API surface homogeneous throughout all other languages, but other languages might offer more flexibility around static members or object and as a result this might not be even be such an issue.

I can't answer all of your questions, but here's what I can say. (I'm no Sentry employee, but I contributed a lot in the past to the SDKs, so I know a lot of the internals of it)

Is there any documentation around testing Sentry for Dart/Flutter?

Speaking from experience of using error monitoring tools, there's no point of testing it.
The reporting for global error handlers is already tested by the tool itself, and for other cases I usually used a logger and the monitoring integration with it.

With the current approach, what happens when you would like to have two Sentry instances (with different options) that you would like to report information to? How would you report captured events for one and not the other?

That's an unsupported use case. Due to how Sentry (or rather how error handling in general) works, there should only be one error monitoring tool active at a time. Especially on the native side you could end up not reporting errors at all if you initialize Sentry and another tool.

What happens if a package initialised Sentry to collect information, the application also initialises another Sentry to collect another information, and there is another package that would like to rely on the Sentry that got initialised in the application (not the one from the first package)? What would the static Sentry members (in the latter package) rely on, would it work as expected?

That's an unsupported use case. I suppose using it like that would result in some data loss, but it would report some data.

I'm also curious to know what is the motivation for making everything static and global rather than letting the user have an actual instance?

Well, errors are global and not all global error handlers support adding multiple listeners. With Flutter, this is especially tricky since it needs to work seamless across Flutter and the native platforms. So it's somewhat a result of how error handlers are working, in addition to design choices of the devs of Sentry.

Thanks @ueman for the reply! I'm going to wait for a Sentry employee to get back.
Regarding testing, I do think it is a good practice to assert that the right flow-tracking or error is being sent to Sentry, and hence the question. From the testing documentation for Sentry on Node:

Learn how to assert that the right flow-tracking or error is being sent to Sentry, but without really sending it to the Sentry server

Thanks @alestiago for the questions and @ueman for chiming in - much appreciated! I don't have a lot to add to the above - the scenarios described are unsupported use cases, and we currently don't have plans to provide tooling for 3p testing of the SDK.

Hi!
Just want to quickly add that the Sentry Testkit for JS is community driven so we don't explicitly own it at Sentry.
That might not be exactly what you're looking for but we have support for spotlight with the Flutter SDK which can help you quickly validate Sentry events.

Closing this as not planned, the Sentry team doesn't have a roadmap for improving the testing experience of sentry_flutter or `sentry.


TypeError: ImageSaver.save_files() missing 1 required positional argument: 'clip_skip'

I have a GGUF workflow that worked fine together the ImageSaver Image Save node. But since i updated the error "ImageSaver.save_files() missing 1 required positional argument: 'clip_skip' " happens at the time of saving.
The image is not saved. I do not have a clip_skip set and have not needed to set it before.

I recreated the node and now there is a cli_skip in the imagesave node and that is set to 0 and it works fine again.


Existing arguments are not being passed from $PSBoundParameters to $fakeBoundParameters during argument completion

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Using the example code from the about_Functions_Argument_Completion page, with a line added to inspect the value of the $fakeBoundParameters variable:
function MyArgumentCompleter{
    param ( $commandName,
            $parameterName,
            $wordToComplete,
            $commandAst,
            $fakeBoundParameters )

    $fakeBoundParameters | Out-String | Add-Content -Path "C:\Temp\Debug.txt" # testing

    $possibleValues = @{
        Fruits = @('Apple', 'Orange', 'Banana')
        Vegetables = @('Tomato', 'Squash', 'Corn')
    }

    if ($fakeBoundParameters.ContainsKey('Type')) {
        $possibleValues[$fakeBoundParameters.Type] | Where-Object {
            $_ -like "$wordToComplete*"
        }
    } else {
        $possibleValues.Values | ForEach-Object {$_}
    }
}

function Test-ArgumentCompleter {
[CmdletBinding()]
 param (
        [Parameter(Mandatory=$true)]
        [ValidateSet('Fruits', 'Vegetables')]
        $Type,

        [Parameter(Mandatory=$true)]
        [ArgumentCompleter({ MyArgumentCompleter @args })]
        $Value
      )
}

Then try the following:
Set-Content -Path "C:\Temp\Debug.txt" -Value $null
Test-ArgumentCompleter -Type Fruits -Value Apple,{tab}
# i.e. Test-ArgumentCompleter -Type Fruits -Value Apple,Apple
Get-Content -Path "C:\Temp\Debug.txt"

Returns the following:
Name                           Value
----                           -----
Type                           Fruits

Now try:
Set-Content -Path "C:\Temp\Debug.txt" -Value $null
Test-ArgumentCompleter -Type Fruits -Value Apple,B{tab}
# i.e. Test-ArgumentCompleter -Type Fruits -Value Apple,Banana
Get-Content -Path "C:\Temp\Debug.txt"

Returns the following:
Name                           Value
----                           -----
Type                           Fruits
Value                          {Apple, B}

Expected behavior
In the first example above, should return:

Name                           Value
----                           -----
Type                           Fruits
Value                          {Apple}

### Actual behavior

```console
In the first example above, actually returns:

Name                           Value
----                           -----
Type                           Fruits

The missing argument value makes it impossible to implement logic that sets or limits the autocomplete list based on arguments already selected.

### Error details

```console
n/a

Environment data
Name                           Value
----                           -----
PSVersion                      7.2.6
PSEdition                      Core
GitCommitId                    7.2.6
OS                             Microsoft Windows 10.0.19044
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0, 5.0, 5.1.10032.0, 6.0.0, 6.1.0, 6.2.0, 7.0.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
n/a

I think the problem lies with how fakeBoundParameters is determined
if you have -Type ("Fru" + "its")  it is evaluated and fakeBoundParameters  holds type = "Fruits" , but if it is not complete syntactically it won't evaluate.
It is possible to use commandAst to do what you want, but it is a lot more work.

Indeed, it seems that the syntactical incompleteness  of an argument such as -Value Apple, causes a Value entry to  be unexpectedly absent from the dictionary stored in $fakeBoundParameters.
While, as you state, a workaround vie $commandAst is possible, it is indeed quite cumbersome - see this Stack Overflow answer for an example.
I suggest classifying this is a bug.


Make sure —preserve-exchange-records applies to issuers, holders, and verifiers

From this comment on issue 535:

Hi regarding the --preserve-exchange-records, it retains for the holder side but not on the issuer's side. Is there a way to retain the exchange records for the issuer's side as well?

This task is to look at what is being done for all parts of the exchanges (issuers, holders and verifiers) and to make sure that the settings are applied correctly for each.

see #2352. I did some work to extend that flag to include presentation exchanges and auto_remove to override. maybe there are still gaps?

quikc update, haven't checked out all of it.
using issue credential v1 API (haven't checked v2)... issuer and holder can retain/preserve the exchanges. there is a bug on the holder side to override --preserve-exchange-records behaviour (by setting auto_remove=True on send-request), so exchanges currently are ALWAYS preserved. easy fix though.
more investigation on presentation exchanges (v1 and v2) tomorrow.


python36Packages.scipy: segmentation fault when running tests

Describe the bug
On current nixos-unstable Scipy fails to build with a segmentation fault during testing:
../cluster/tests/test_vq.py::TestKMean::test_kmeans2_init <- ../../nix/store/d00fds078va595ifakggj6srmky01jq2-python3.6-scipy-1.4.1/lib/python3.6/site-packages/scipy/cluster/tests/test_vq.py PASSED [  0%]
../cluster/tests/test_vq.py::TestKMean::test_krandinit <- ../../nix/store/d00fds078va595ifakggj6srmky01jq2-python3.6-scipy-1.4.1/lib/python3.6/site-packages/scipy/cluster/tests/test_vq.py Fatal Python error: Segmentation fault

Current thread 0x00007ffff7898f40 (most recent call first):
  File "/nix/store/d00fds078va595ifakggj6srmk/nix/store/ds7r5c4z1vzrm0jw7ay712zs59p64hf7-stdenv-linux/setup: line 1302:  9640 Segmentation fault      (core dumped) /nix/store/acwrn1di4lgiz80qxam9vk28b2mkr2py-python3-3.6.10/bin/python3.6 -c 'import scipy; scipy.test("fast", verbose=10)'
builder for '/nix/store/2sa0mm8g3rb2l4x4j4y2i7qihb2lbdpy-python3.6-scipy-1.4.1.drv' failed with exit code 139
cannot build derivation '/nix/store/0mxrinnvr4f43h17wpcfpfisc3kbqywk-python3-3.6.10-env.drv': 1 dependencies couldn't be built
error: build of '/nix/store/0mxrinnvr4f43h17wpcfpfisc3kbqywk-python3-3.6.10-env.drv' failed

To Reproduce
Steps to reproduce the behavior:

save the following as shell.nix

{
  nixpkgs ?  import (builtins.fetchGit {
    url = "https://github.com/nixos/nixpkgs-channels/";

    #
    # Commit hash for nixos-unstable
    # `git ls-remote https://github.com/nixos/nixpkgs-channels nixos-unstable`
    name = "nixos-unstable-2020-07-06";
    ref = "refs/heads/nixos-unstable";
    rev = "dc80d7bc4a244120b3d766746c41c0d9c5f81dfa";

    #
    # Commit hash for nixos-20.03
    # `git ls-remote https://github.com/nixos/nixpkgs-channels nixos-20.03`
    #name = "nixos-20.03-2020-07-06";
    #ref = "refs/heads/nixos-20.03";
    #rev = "afa9ca61924f05aacfe495a7ad0fd84709d236cc";
  }) {}
}:

with nixpkgs;

let
  python = python36;
  python-with-base-packages = python.withPackages(ps: with ps; [
    # the following packages are related to the dependencies of your python
    # project.
    # In this particular example the python modules listed in the
    # requirements.txt require the following packages to be installed locally
    # in order to compile any binary extensions they may require.
    #

    scipy
  ]);

in mkShell {

  buildInputs = [
    python-with-base-packages
    python3Packages.venvShellHook
  ];

  shellHook = ''
    # set SOURCE_DATE_EPOCH so that we can use python wheels
    SOURCE_DATE_EPOCH=$(date +%s)
    venvShellHook
  '';
}

run nix-shell

Expected behavior
Should not segfault during test.
Additional context
SciPY seems to build just fine on current 20.03 release.
Notify maintainers
cc @FRidh , @matthewbauer
Metadata

system: "x86_64-linux"
host os: Linux 5.4.46, NixOS, 20.09pre232692.7db146538e4 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.6
channels(root): "home-manager, nixos-20.09pre233323.dc80d7bc4a2, nixos-hardware, nixpkgs-20.09pre233075.6e139365424"
channels(ente): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Particular stacktrace is:
../cluster/tests/test_vq.py::TestKMean::test_kmeans2_simple <- ../../nix/store/x1vz10qv9ryk4ixiizdyq4mk6awqq168-python3.8-scipy-1.5.2/lib/python3.8/site-packages/scipy/cluster/tests/test_vq.py PASSED [  0%]
../cluster/tests/test_vq.py::TestKMean::test_kmeans2_rank1 <- ../../nix/store/x1vz10qv9ryk4ixiizdyq4mk6awqq168-python3.8-scipy-1.5.2/lib/python3.8/site-packages/scipy/cluster/tests/test_vq.py PASSED [  0%]
../cluster/tests/test_vq.py::TestKMean::test_kmeans2_rank1_2 <- ../../nix/store/x1vz10qv9ryk4ixiizdyq4mk6awqq168-python3.8-scipy-1.5.2/lib/python3.8/site-packages/scipy/cluster/tests/test_vq.py PASSED [  0%]
../cluster/tests/test_vq.py::TestKMean::test_kmeans2_high_dim <- ../../nix/store/x1vz10qv9ryk4ixiizdyq4mk6awqq168-python3.8-scipy-1.5.2/lib/python3.8/site-packages/scipy/cluster/tests/test_vq.py PASSED [  0%]
../cluster/tests/test_vq.py::TestKMean::test_kmeans2_init <- ../../nix/store/x1vz10qv9ryk4ixiizdyq4mk6awqq168-python3.8-scipy-1.5.2/lib/python3.8/site-packages/scipy/cluster/tests/test_vq.py PASSED [  0%]
../cluster/tests/test_vq.py::TestKMean::test_krandinit <- ../../nix/store/x1vz10qv9ryk4ixiizdyq4mk6awqq168-python3.8-scipy-1.5.2/lib/python3.8/site-packages/scipy/cluster/tests/test_vq.py Fatal Python error: Fatal Python error: Segmentation fault

Thread 0x00007ffff7843f40 (most recent call first):
  File "/nix/store/x1vz10qv9ryk4ixiizdyq4mkSegmentation fault

/nix/store/333six1faw9bhccsx9qw5718k6b1wiq2-stdenv-linux/setup: line 1303: 10293 Segmentation fault      (core dumped) /nix/store/wm30fgxfnn26z7z24y1iw64phb3djrq0-python3-3.8.5/bin/python3.8 -c 'import scipy; scipy.test("fast", verbose=10)'
builder for '/nix/store/2xmrj9b9zf4c2wxgknrbyhaw7h58gsry-python3.8-scipy-1.5.2.drv' failed with exit code 139
cannot build derivation '/nix/store/mfqj9l730b1wjhi8yhixj03mhb71va6k-python3-3.8.5-env.drv': 1 dependencies couldn't be built

I believe the fix is contained in:
https://github.com/xianyi/OpenBLAS/pull/2729
and upstream tracking issue is:
https://github.com/xianyi/OpenBLAS/issues/2728

I believe the fix is contained in:
xianyi/OpenBLAS#2729
and upstream tracking issue is:
xianyi/OpenBLAS#2728
and Debian issue:
bugs.debian.org/cgi-bin/bugreport.cgi?bug=966463

Opened https://github.com/NixOS/nixpkgs/pull/101780 to bump openblas to a version with that fix

#101780 fixes this for me - @Enteee @jcumming @chekoopa can you confirm?

{
  nixpkgs ?  import (builtins.fetchGit {
    url = "https://github.com/nixos/nixpkgs/";

    #
    # Commit hash for nixos-unstable
    # `git ls-remote https://github.com/nixos/nixpkgs-channels nixos-unstable`
    ref = "refs/heads/staging";
    #rev = "3b4cd4f4dacd7db4011e88d819a1ae5acc3f3aff";
    rev = "5219a3ade1939470f2965ad4d80c87f7fb33db3e";

    #
    # Commit hash for nixos-20.03
    # `git ls-remote https://github.com/nixos/nixpkgs-channels nixos-20.03`
    #name = "nixos-20.03-2020-07-06";
    #ref = "refs/heads/nixos-20.03";
    #rev = "afa9ca61924f05aacfe495a7ad0fd84709d236cc";
  }) {}
}:

with nixpkgs;

let
  python = python36;
  python-with-base-packages = python.withPackages(ps: with ps; [
    # the following packages are related to the dependencies of your python
    # project.
    # In this particular example the python modules listed in the
    # requirements.txt require the following packages to be installed locally
    # in order to compile any binary extensions they may require.
    #

    scipy
  ]);

in mkShell {

  buildInputs = [
    python-with-base-packages
    python3Packages.venvShellHook
  ];

  shellHook = ''
    # set SOURCE_DATE_EPOCH so that we can use python wheels
    SOURCE_DATE_EPOCH=$(date +%s)
    venvShellHook
  '';
}

builds for me

Works, thanks!

This still affects release-20.09. Is there a simple fix we can backports (either in nixpkgs, or here locally)?

This still affects release-20.09. Is there a simple fix we can backports (either in nixpkgs, or here locally)?

Backport openblas updates: https://github.com/NixOS/nixpkgs/commits/staging/pkgs/development/libraries/science/math/openblas/default.nix

Backport openblas updates: https://github.com/NixOS/nixpkgs/commits/staging/pkgs/development/libraries/science/math/openblas/default.nix

Thanks, I’ll try that. Would such a backport be eligible to go to release-20.09?

Thanks, I’ll try that. Would such a backport be eligible to go to release-20.09?

I don't really do backports, but since it fixes something known to be broken I assume it would be fine.

I don't really do backports, but since it fixes something known to be broken I assume it would be fine.

Pull request should target staging-20.09 not release-20.09.

Pull request should target staging-20.09 not release-20.09.


added tolerations from install

Signed-off-by: Xavier Dharmaiyan<EMAIL_ADDRESS>Issue: Issue: https://github.com/stolostron/backlog/issues/25020

/lgtm

/lgtm


deMon2k parser & DZVP-GGA basis

Implements a parser for the deMon2k format and adds the DZVP-GGA basis set.
Closes #190
Closes #189

Codecov Report

Merging #194 (bb21ca4) into master (32721c8) will decrease coverage by 1.39%.
The diff coverage is 17.97%.

@bennybp ready to merge


New-HTMLNav - Locational Awareness

I have been using New-HTMLTopNav with success for a while now. The issue that I am running into is sprawl with nested links...
One way I thought could help tremendously here is if I switched to left nav (New-HTMLNav) and that it could 'know where you are' or more simply 'open to your location'.
Looking at the pic below, if I am browsing the page at Compute > VMware > Stats > Clusters
and then want to jump to Compute > VMware > Stats > Hosts
it takes like 5 clicks :-(
If the nav opened/expanded the list to the current page it would be easier (one click) to navigate to other similar pages without having to open the menu and drill, drill, drill, drill each time.

Hope this makes sense!

You want the state of nav to be saved. I am not sure how to do that. It's a good idea, but I doubt my html/css/js skills are high enough to do this. You would probably need limit the example, and post on stackoverflow or maybe ask chatgpt and then we can try and figure it out.

I'm not sure 'saved' is needed as much as the ability to open/expand the menu to a certain link?
If we could do that, we just look at the current pageid and open to the corresponding link?

Either way,  I don't have idea on how to do it properly. Feel free to experiment.


tla+ spec for dynamodb lock

Description
Spec is model checked without pause and crash.
Adding crash and pause to the modeling requires enabling timer in the
spec (i.e. setting TIME_TICK_UNIT > 0). This will fail the model check
because lock with expiration cannot gurantee correctness without use of
fenching token.

also cc @mosyp who is the author of the dymodb lock.
The spec is probably not very readable for those who hasn't worked with TLA+ before. If you really want to read it, only read lines before \* BEGIN TRANSLATION (chksum(pcal) = "e6415912" /\ chksum(tla) = "ffc65bb2"). The rest are transpiled TLA+ code from the PlusCal algorithm code defined in the comment.

Wow, that is impressive diffs, how to run these specs?

@mosyp you will need to download tla+ toolbox and load the project to run it. See download link in the readme.

Hi,
I landed here because I was searching for TLA+ applications and thought I'll share a few things which may be helpful:

TLA+ specs can be checked from the command line, either directly or with other tools.
To make checking the spec more straightforward I would also add a cfg file, for example as in https://github.com/fpaxos/fpaxos-tlaplus.
If you can't get used to the latex syntax, it's possible to use VSCode and configure it so that it will be hidden: https://github.com/alygin/vscode-tlaplus/wiki/Fonts


Fibonacci series

Title of article
Write a Java program to print Fibonacci series.
Additional information
Input  : 10
Output : 0 1 1 2 3 5 8 13 21 34

Code of Conduct

[X] I have read and agree to the Codinasion project's Code of Conduct

Hi, I want to handle this issue, where should I put the Java file that I create and do I need to to anything else or simply make a Java file that prints Fibonacci series

Hi, I want to handle this issue, where should I put the Java file that I create and do I need to to anything else or simply make a Java file that prints Fibonacci series

Hii @agnarrarendelle
Please do follows:

create a java folder
create a programme file inside it
create a folder with 1-programme-title
add java file in the folder
create a pull request

Optional steps (if you wanna do)

create a README.md like this
create a index.md like this

Thanks 😃


Only one OutOfPlaneAngle in the RTK 3D circular projection geometry

There is only one OutOfPlaneAngle in the geometry of rtk, and the actual system will have two OutofplaneAngles, does it have no effect?

The orientation of the detector is fully described by three angles: GantryAngle, OutOfPlaneAngle and InPlaneAngle. See documentation here. Please use the mailing list, this is not a software issue.


Implement 32 bit float calculations and GTG format (Geodetic TIFF grids)

In your FAQ you say it is only integer formats and only uncompressed. Very outdated and makes it not bitperfect and thus IMHO not very usefull for XGM2019e or upcoming EGM2020.
Samples are here: https://www.agisoft.com/downloads/geoids/
And outdated geotiff samples are here https://www.agisoft.com/downloads/obsolete-geoids/
In both cases I only care about best EGM2008 1'x1' (though that is EPSG::3859, not EPSG::3855, 3855 is 2.5' EGM2008). https://epsg.org/crs_3859/EGM2008-height.html

The representation of geoid models in GeographicLib was dictated shortly after the EGM2008 model was released by the need to accommodate the 1' model in memory and the need to keep GeographicLib free of any dependant libraries.  I would probably make a different design decision today.  However, you now have alternative packages which will deal with this data and I don't expect to change GeographicLib's handling of geoids anytime soon.
With GeogrpahicLib, you do have the choice to compute geoid heights directly from the spherical harmonic gravity model (using the GravityModel class).  This allows you to avoid the possible 25mm error in geoid height you get using bilinear interpolation on the 1' EGM2008 model.

using the GravityModel class

So it is actually 32 bit float inside? And all good comoared to proj?

No, it's better than that.  The EGM2008 spherical harmonic model is stored as doubles.  The GravityModel class will then compute gravity at arbitrary points and will also compute the geoid height.  I believe that PROJ uses GravityModel to compute the geoid grids that it uses.
Be warned: calling the methods in GravityModel with EGM2008 is relatively expensive.

No, it's better than that.

Than what?

The EGM2008 spherical harmonic model is stored as doubles

1'x1' is 4 bytes per pixel, and 21601x10801 pixels.

believe that PROJ uses GravityModel to compute the geoid grids that it uses.

So it uses your code?

There's no grid or "pixel" in the EGM2008 model. The gravity potential is defined as a continuous function of position in terms of spherical harmonics.

No, it is 32 bit float whether in original NGA big or little enidian or in compressed (lossless method) in Tiff (link https://www.agisoft.com/downloads/geoids/). And it has pixels, like any tif. Of course those pixels are data really created by fortran program from some smaller data. Or you mean it is dithered (interpolated) by some "standard" method to create some more perfect smooth data? Well, that is internal deliberations.
I suppose if you are saying 32 bit is supported (and bitperfect with what ArcGIS does) then the only thing missing is geotiff + gtg where you need to wire floating code into and from.

I think we're talking at cross purposes.  The GravityModel class
implements, e.g., the NGA EMG2008 gravity model
Pavlis et al. https://doi.org/10.1029/2011JB008916
which defines gravity at arbitrary positions at (nominally) double
precision.  Starting with this model of gravity (and the corresponding
"zeta-to-N" corrections), it is possible to compute the geoid height at
an arbitrary point on the earth -- no need for a grid or interpolation.
Because computing geoid height in this way is fairly expensive, you can
elect to precompute the geoid height on a grid and interpolate into
that.  That's what the Geoid class does.

The GravityModel class
implements, e.g., the NGA EMG2008 gravity model

It cannot implement it, the file is 890 Megabyte, not bit, it will not fit and moroever no one will fit this into code, but use a binary file or compressed losslessly file with "pyramids" style (e.g. GeoTiff) with metadata (e.g. GTG metadata).

which defines gravity at arbitrary positions at (nominally) double
precision.

No, it is 32 bit, not double, i.e. 64 bit. You mean you use 64 bit precision of math processing, well, so not even arbitrary (a.k.a. infinite) precision.

it is possible to compute the geoid height at
an arbitrary point on the earth

You are oversimplifying this. What WGS 84 is in use, e.g? Is it latest G2139 of Janaury 2021? Or the base of the ensembly? What is the ellipsoid? WGS one? Or GRS 90?

Starting with this model of gravity

In fact you do not start with that, since that data was derived by the intellegence agency. Deriviation happens from undulation file or in case of XGM2019e (and upcoming EGM2020) from many data sources.

I cannot fathom much of what you say.  "It cannot implement it": but
GegoraphicLib does!  "It will not fit": but it does!  "In fact you do
not start with [the EGM2008 gravity model]": but that is precisely how
the gridded geoid values were computed in the first place.
You are right that most users will prefer to use the gridded data.
GeographicLib definitely takes shortcuts here (representing the data at
3 mm resolution).  However you should be clear that even with a float
GeoTiff there are two sources of error: (a) a minor one, representing
the heights as floats, (b) a major one, the need to interpolate into the
grid to get the geoid height at an arbitrary position.  In particular
bilinear interpolation into the 1' EGM2008 grid can lead to an error of
up to 25 mm.

but
GegoraphicLib does

The whole repository with a git clone does not weight 800 MB.

but it does!

I am not even sure gcc will allow 800 MB text files. Stack too.

but that is precisely how
the gridded geoid values were computed in the first place.

No, they were computed from https://web.archive.org/web/20161118021013/http://earth-info.nga.mil/GandG/wgs84/gravitymod/egm2008/Und_min1x1_egm2008_isw=82_WGS84_TideFree.gz

I do not include voluminous data with GeographicLib.  This is packaged
separately:
to install the gravity models for use with GeographicLib, visit
https://geographiclib.sourceforge.io/C++/doc/gravity.html#gravityinst
to install the geoids for use with GeographicLib, visit
https://geographiclib.sourceforge.io/C++/doc/geoid.html#geoidinst
It seems you are unfamiliar with the gravity models that are used to
obtain the gridded geoid models.  I recommend you read Pavlis's paper
and download the table of spherical harmonic coefficients (and
associated documentation) from
https://earth-info.nga.mil/php/download.php?file=egm-08spherical
This gives you a zip file (size 105MB), which unzips to 369M of double
precision coefficients in ASCII.  For use with GeographicLib, I
repackaged the data as binary (but uncompressed) which reduces its size
to 73MB.
The 1'x1' gridded geoid data you pointed me too can be generated by
GeographicLib from the EGM2008 gravity model using GeoidToGTX.  Note the
comparative sizes:
EGM2008 gravity model (double precision, uncompressed binary) is 73MB.
EGM2008 1'x1' grid (float tiff, compressed) is 408MB.
Besides being 5.5 times smaller than the gridded geoid, the gravity
model also lets you compute the magnitude and direction of the gravity
in three dimensions.

Your geoids (.PGM) are quantised to 16 bits. https://lists.osgeo.org/pipermail/proj/2019-December/009121.html

The major drawback of this format is that since there are only 65535 possible pixel values, the height must be quantized to 3 mm. However, the resulting quantization error (up to 1.5 mm) is typically smaller than the linear interpolation errors.

These are convedted from 16 bit data too https://github.com/OSGeo/PROJ-data/blob/master/us_nga/us_nga_egm08_25.tif which is an obvious bug.
P.S. I do not need gravity models or magnetic models. Only geoids for GNSS stuff (GPS, Galileo).

It's not clear in your previous message where the "obvious bug" is.  The
PROJ-data file us_nga_egm08_25.tif wasn't converted from 16 bit data.
Even though you might not need all the information a gravity model
provides, the geoid height can be accurately computed from a gravity
model and you can then avoid the interpolation error you would incur
using a grid representation of the geoid height.

The
PROJ-data file us_nga_egm08_25.tif wasn't converted from 16 bit data.

It was converted egm08_25.gtx (last modified at 2018/10/08) so even though tiff is 32 bit that file I think was 16 bit. Maybe you can confirm that, if you know.

The
PROJ-data file us_nga_egm08_25.tif wasn't converted from 16 bit data.

It was converted egm08_25.gtx (last modified at 2018/10/08) so even though tiff is 32 bit that file I think was 16 bit. Maybe you can confirm that, if you know. I suppose it is possible the original 135 MB data managed to be packed in tiff of 79 MB.

The data in this file was generated by the GeographicLib's example
program, GeoidToGTX using the EGM2008 gravity model (see my earlier
posting).  This computes the geoid heights in double precision and then
converts them to floats.  No 16-bit quantizations are involved.
Yes, the DEFLATE compression used in the tiff file gets you about a
factor of 2 compression.  (You can check all this stuff yourself!)

You can check all this stuff yourself!

It is not that simple, ffmpeg does not like geotiff, and it is what I usually use to decode to float or integer (YCbCr and rgb) uncompressed without header formats. There is also the fact it may not be bitperfect with original NGA 2.5' data anyway.
This got out of topic. :) 32 bit is supported in both gravity to geoid generation and in geoid use as well to get orthometric heights from WGS 84 (static, no epoch) 3D CRS variant of the WGS 84 ensembly (even if not perfectly exposed API-wise), all good then. What about Geotiff and GPG? That means GDAL integration simply...

You can read the data in the GeoTiff by using gdal_translate to convert
it to a simpler format, e.g., GTX, which is trivial to read in a
program.  And, if I were going to support geoid grids with float data, I
would probably use the GTX format for this reason.  I'm not going to
make GeographicLib depend on GDAL; this would be a huge headache for
most developers.
Understand that when I wrote the Geoid class it was to support the
massive size of the newly released EGM2008 geoid and there were
basically no other libraries that handled it (with the possible
exception of GeoTRANS, which was another headache to deal with).  The
choices I made back then turned out to be OK.  I don't see a particular
need to increase the precision I use on the geoid models.  If you need a
higher precision, then you can use GDAL or PROJ yourself.  Alternatively
you can stick with GeographicLib and use the GravityModel class and
generate your own grid (maybe finer than 1'?) to cover your area of
interest.
Finally the concern about being bit-perfect with the NGA data is
misplaced; floats offer excessive precision close to zero.  In addition
the whole Zeta-to-N business used in generating the geoid height is a
kludge (approximating the mostly unknown mass of the terrain above the
geoid by spherical harmonics).

generate your own grid (maybe finer than 1'?) to

The fact NGA did not do it suggests it is not really possible? There is only degree 2190 and order 2159?

generate your own grid (maybe finer than 1'?) to

The fact NGA did not do it suggests it is not really possible? There is only degree 2190 and order 2159?

The maximum degree and order of the gravity model just means that the
data is band limited.  You can certainly sample band-limited data at as
finer resolution as you wish.  NGA probably didn't do this because (a)
they didn't want to deal with the resulting huge datasets and (b) even
though the finer grids result in lower interpolation errors, they knew
that these were already less than the intrinsic error in the gravity
model.  (Indeed it looks like they no longer offer the 1' grid.)

Indeed it looks like they no longer offer the 1' grid.

Well, yes, even XGM2019e is 2', not 1'. That is still better than 2.5'. But! EPSG does provide 1' EGM2008!! It is actually a variant, compare:
https://epsg.org/crs_3859/EGM2008-height.html
https://epsg.org/crs_3855/EGM2008-height.html

You can certainly sample band-limited data at as
finer resolution as you wish.

You can also put 16 bit quantised values into 32 bit float container too. :)

OK, I'll let you delve into these variants.  I think we've exhausted this topic so I'm closing it as resolved.

I think we've exhausted this topic so I'm closing it as resolved.


[tests] Consider moving Azure specific component tests to Azure sdk repo

Currently, the Azure component tests don't run on CI as they need test resources in Azure to run. This issue is to decide whether to move these tests to the Azure sdk repo, and utilize the test framework there. And if so, what needs to be done to make it happen.
context: https://github.com/dotnet/aspire/issues/2689#issuecomment-2045664700
@eerhardt:
What is the medium-to-long-term vision for where the Azure Hosting code lives? If we intend to move it to [Azure/azure-sdk-for-net](https://github.com/Azure/azure-sdk-for-net/), it may make sense to wait until then to hook it up to automated tests.
On the Components side, my goal is to eventually move them to the Azure repo, so they can ship and service along with the Azure SDK packages.
cc @joperezr @mitchdenny

@tg-msft @weshaggard (and any other Azure SDK devs) - thoughts on this?


How to config celery beat task  in docker?

I have some scheduler tasks, so I need celery beat to  manage them. Like below:
Only run celery -A myproject.celeryconf beat in one worker, but run celery worker -A myproject.celeryconf -Q default -n default@%h in multiple workers.
How to write the run_celery.sh or use other strategies to accomplish it?

I asked a question in stackoverflow:
http://stackoverflow.com/questions/42455660/deploy-celery-with-beat-in-docker


luxtronik log warning

Logger: homeassistant.components.sensor
Source: components/sensor/init.py:980
Integration: Sensor (documentation, issues)
First occurred: 14:07:34 (3 occurrences)
Last logged: 14:07:34
Entity sensor.luxtronik2_overheating_target_temperature (<class 'custom_components.luxtronik2.sensor.LuxtronikSensor'>) is using native unit of measurement 'K' which is not a valid unit for the device class ('temperature') it is using; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
Entity sensor.luxtronik2_analog_out1 (<class 'custom_components.luxtronik2.sensor.LuxtronikSensor'>) is using native unit of measurement 'V' which is not a valid unit for the device class ('energy') it is using; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.
Entity sensor.luxtronik2_analog_out2 (<class 'custom_components.luxtronik2.sensor.LuxtronikSensor'>) is using native unit of measurement 'V' which is not a valid unit for the device class ('energy') it is using; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

@kotana Thanks for your issue.

using native unit of measurement 'K' which is not a valid unit for the device class ('temperature')

This is wrong in the legacy ha version (I think 2022.12). Please use a newer ha version or ignore this log message.
See the current ha source:
const > TEMPERATURE  > Unit of measurement: °C, °F, K

analog_out1 + analog_out2

I have changed this now. See the next release.


Bump container image tag to fix incompatibility between the SDK and the container.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand:

[ ] What the pull request does
[ ] Why it does it
[ ] How it does it
[ ] Why this approach

[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Run Python Dataflow ValidatesRunner

Run Python Dataflow ValidatesRunner

Ready for merge.


fix(o2k): plugin sort if inso-compat is enabled

no id is available in inso-compat mode, and a nil-ref would occur. Now the foreign keys are used to sort in deterministic order.
fixes #183

Codecov Report
Attention: Patch coverage is 89.47368% with 2 lines in your changes missing coverage. Please review.

Project coverage is 67.86%. Comparing base (95d22e8) to head (85d153b).

Files
Patch %
Lines

openapi2kong/openapi2kong.go
89.47%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #187      +/-   ##
==========================================
+ Coverage   67.77%   67.86%   +0.08%
==========================================
  Files          23       23
  Lines        2492     2505      +13
==========================================
+ Hits         1689     1700      +11
- Misses        643      644       +1
- Partials      160      161       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[bug] 1.29.4 and 1.29.3 incompatibility

Describe the bug
There appears to be an incompatibilty in the docker setup step of 1.29.4
In my package.json devDependencies I have ^1.29.3.
Locally I'm running 1.29.2
Inside my dockerfile I curlpipebash the latest version (1.29.4 at present)
when running RUN moon docker setup in my dockerfile, I get the following error:
   npm error Error: Cannot find module<EMAIL_ADDRESS>  npm error Require stack:
  npm error -<EMAIL_ADDRESS>  npm error     at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15)
  npm error     at Function.resolve (node:internal/modules/helpers:133:19)
  npm error     at Object.<anonymous> (/home/runner/_work/myrepo/myproject/node_modules/@moonrepo/cli/postinstall.js:41:38)
  npm error     at Module._compile (node:internal/modules/cjs/loader:1460:14)
  npm error     at Module._extensions..js (node:internal/modules/cjs/loader:1544:10)
  npm error     at Module.load (node:internal/modules/cjs/loader:1275:32)
  npm error     at Module._load (node:internal/modules/cjs/loader:1091:12)
  npm error     at wrapModuleLoad (node:internal/modules/cjs/loader:212:19)
  npm error     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:158:5)
  npm error     at node:internal/main/run_main_module:30:49 ***
  npm error   code: 'MODULE_NOT_FOUND',
  npm error   requireStack: [
  npm error<EMAIL_ADDRESS>  npm error   ]

Expected behavior
It could be that the docker packages move around, but I wouldn't expect a patch upgrade to break compat
Screenshots

Environment
  System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Max
    Memory: 996.50 MB / 32.00 GB
    Shell: 3.7.1 - /usr/local/bin/fish
  Binaries:
    Node: 22.3.0 - ~/.nvm/versions/node/v22.3.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v22.3.0/bin/yarn

Additional context

In fairness, I'm not sure if having devdependencies and curlpipebash at the same time is a great idea, but it's what the docs suggest

Also since updating everything to 1.29.4 I’ve been getting occasional core dumps from tokio which seems suspicious:
RUN moon docker scaffold some-module:
client-js:integration | 1.175 ▪▪▪▪ installing proto 0.42.0
client-js:integration | 8.001 ▪▪▪▪ installing node 22.3.0
client-js:integration | 1171.8
client-js:integration | 1171.8 thread 'tokio-runtime-worker' has overflowed its stack
client-js:integration | 1171.8 fatal runtime error: stack overflow
client-js:integration | 1172.7 Aborted (core dumped)

@CluEleSsUK Is the cycle the problem for the original post? If so, you can edit the post/title to mention the cycle instead and I can look into it.

No, cycle is just for the tokio stack overflow

I don't see anything in the diff that would cause this: https://github.com/moonrepo/moon/compare/7d3702984e9774e2dc0a9d42d49977fd165585e1..ac8fa57f2b35b746e16df6d756fc44e74bbd64fe
Did npm install run and succeed? The error seems like @moonrepo/cli wasn't installed into node modules correctly.


[FEATURE] Add DeitaPreferenceTask

Is your feature request related to a problem? Please describe.
The Deita paper presents different prompts to evaluate complexity and quality of responses based on EvolInstruct, we can include the ones related to rank and score.
Describe the solution you'd like
Implement those. We can use as inspiration the implementation from UltraFeedbackTask:
from distilabel.tasks import DeitaPreferenceTask

deita_complexity = DeitaPreferenceTask.for_complexity()
deita_quality = DeitaPreferenceTask.for_quality()

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Correspond to Section E2, table 14 and Section E3, table 18

@plaguss, while reading the paper it seems EvolComplexity and EvolQuality are the names for the prompt templates methods combining both generation and ranking. The templates for generation are directly intended to be used with their equivalents for scoring and ranking. Do you think it makes sense to rename them to EvolComplexityGeneration and EvolQualityGeneration, ans ...Prefrence

I thought those could work on their own, but could make sense. Even though it might duplicate code. Will read it more carefully, thanks!

I think they can work on their own but the name for the tasks described in the paper is shared among the generation and rating and are called EvolComplexity and EvolQuality I believe.

Already merged in #302


Success callback for Model.message()

Sails version:0.12.4
Node version:6.7.0
NPM version:3.10.8
Operating system:Mac OSX

Is there a way to add a success callback to the User.message(data) call?
Similar to how it is described here
http://stackoverflow.com/questions/13549734/success-callback-for-emit-method-in-socket-io
but from server to client. So on server side I do
User.message(someData)
and on the client
socket.on('user', function(){
// do something
});
When the client has received the message the server should get notified, so perhaps something like this
User.message(someData, function() {
// success callback - message has been delivered
}, function(error) {
// error callback - message has not been delivered
})
P.S. I created first the same issue also on https://github.com/balderdashy/sails-hook-sockets/issues/32, but as pubsub.js is inside the sails lib opening the ticket here

@dominiksteiner Thanks for bringing this up!  To the best of my knowledge, there is no "ack" for socket broadcasts-- at least not that can be safely relied upon in a multi-node (i.e. one-of-many-servers-behind-a-load-balancer) world.  (see http://socket.io/docs/server-api/#server#emit)
This would probably be achievable for single-recipient broadcasts (where you use a socket id, not a room name), but it would have to live on top of Socket.io.  I agree it'd be nice to have a core way of doing a delivery guarantee...  But rather than RPS, the place to tackle that would be in sails.sockets.broadcast.  I'd def be open to figuring something like that, just needs a bit more research to figure out the best way to do it first.  (And I think we should use a different method name for it-- e.g. sails.sockets.reverseRequest(someSocketId, { whatever: ['data', 'you want'] }, function (err, optionalJsonSerializableData) {  }))

Minor aside:  Just to give you a heads up:  In Sails v1 (which will be released before the end of the year), we're changing message().  So instead, you'll be able to use .publish(), which is very similar, except slightly lower level in that it doesn't mess with the format of the message you send out standardize will have the callback.  There'll be more on that in the migration guide when it comes time to upgrade-- just wanted to let you know in advance.

cc @sgress454

Thanks @mikermcneil for the quick response.
For our use case we wouldn't be able to use publish() as we want to notify all connected sockets of an another incoming server request, so the req object wouldn't be the one triggered from the sockets. So if message() is going away what would be the alternative?
broadcast() looks like a better fit, so if I use the session id as the room name it would do the same thing as message()?

@dominiksteiner Cool!  Yeah, I'd say since this API is in flux, at the moment I'd probably recommend sails.sockets.broadcast().  You can use that to address a room or an individual socket (just use the socket id as the room name).
Something that might be helpful to keep in mind: Behind the scenes, all that .publish()/.message() are really doing is wrapping sails.sockets.broadcast() (and building up a dynamic room name for each record, using the specified record id).  Similarly, .subscribe() does the same thing for sails.sockets.join().  And .unsubscribe() does it for sails.sockets.leave()

@dominiksteiner here are some recent updates I did to the RPS docs which might also be helpful: https://github.com/balderdashy/sails-docs/commit/8b53f402ec8cbbd2d621b4b4896c7011b5ee8d93?diff=unified

@mikermcneil thanks for the clarification, I will play with broadcast() and see what can be done there.


Fix the signature of D3.Transition.each

Only the first argument of D3.Transition.Transition.each is optional, while the callback parameter is mandatory. Setting both parameters optional does not produce the expected behavior. We should use overload here.
See API reference of transition.each:

transition.each([type, ]listener)
If type is specified, adds a listener for transition events, supporting "start", "end" and "interrupt" events. The listener will be invoked for each individual element in the transition.
...
If type is not specified, behaves similarly to selection.each: immediately invokes the specified function for each element in the current transition, passing in the current datum d and index i, with the this context of the current DOM element.

@gildorwang thanks mate!


Change property value while converting from XML to JSON

In a project I'm getting some data from DB using TSQL FOR XML. In all tables the minimun value for Date fields is set to 01/01/1900.
That's because null values are not permitted as an internal politic that cannot be changed
With the xml result I need to convert it to JSON and serialize it to a client.
For doing so I'm using:
string jSonString = Newtonsoft.Json.JsonConvert.SerializeXmlNode(xmlDoc, Newtonsoft.Json.Formatting.None, true);

Good; now I need to convert each 01/01/1900 date to DateTime.MinValue (01/01/0001) while converting into JSON; how can I handle this?

This isn't a bug. Ask on Stackoverflow.

Ok, thanks. Here is the question http://stackoverflow.com/q/30239402/975520, I can't find a way to handle this


feat(parser): implement middy parser middleware

Description of your changes
This PR adds parser middy middleware. We only have before part to parse event object with specific envelope or custom schema.
The PR is in draft for now and contains changes from the envelope work. I leave it as draft for early comments and suggestions. Once #1815 merged it will contain less changes.

Related issues, RFCs

Issue number: closes #1792
Checklist

[ ] My changes meet the tenets criteria
[ ] I have performed a self-review of my own code
[ ] I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my change is effective and works
[ ] The PR title follows the conventional commit semantics

Breaking change checklist
Is it a breaking change?: NO

[ ] I have documented the migration process
[ ] I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Erm, let me rebase first, something weird with git again


compile fails 2022/12/05

Compile fails on Ubuntu 22.10
Using cross-compile instructions
Here is the end of the log after the tests:
----------------------------------------------------------------------
Ran 302 tests in 3.458s

OK
make[1]: Leaving directory '/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/BaseTools/Tests'
make: Leaving directory '/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/BaseTools'
Using EDK2 in-source Basetools
WORKSPACE: /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b
EDK_TOOLS_PATH: /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/BaseTools
CONF_PATH: /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/Conf
Copying $EDK_TOOLS_PATH/Conf/build_rule.template
     to /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/Conf/build_rule.txt
Copying $EDK_TOOLS_PATH/Conf/tools_def.template
     to /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/Conf/tools_def.txt
Copying $EDK_TOOLS_PATH/Conf/target.template
     to /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/Conf/target.txt
Build environment: Linux-5.19.0-23-generic-x86_64-with-glibc2.36
Build start time: 21:37:14, Dec.05 2022

WORKSPACE        = /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b
PACKAGES_PATH    = /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2:/home/stranche/macc-uefi-build-script-main/actions/scrip                                                                             ts/e2b/edk2-platforms:/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2-non-osi
EDK_TOOLS_PATH   = /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/BaseTools
CONF_PATH        = /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/Conf
PYTHON_COMMAND   = /usr/bin/python3

Architecture(s)  = AARCH64
Build target     = RELEASE
Toolchain        = GCC5

Active Platform          = /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2-platforms/Platform/SolidRun/Armada80x0McBin/Arma                                                                             da80x0McBin.dsc

Processing meta-data ........####.... done!
Building ... /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib.inf                                                                              [AARCH64]
Building ... /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/MdePkg/Library/BaseStackCheckLib/BaseStackCheckLib.inf [AARCH6                                                                             4]
Trim --asm-file -o /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/ArmPkg/Lib                                                                             rary/CompilerIntrinsicsLib/CompilerIntrinsicsLib/OUTPUT/AArch64/Atomics.i -i /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/Bui                                                                             ld/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib/OUTPUT/inc.lst /home/stranche/macc-u                                                                             efi-build-script-main/actions/scripts/e2b/edk2/ArmPkg/Library/CompilerIntrinsicsLib/AArch64/Atomics.S
"gcc"   -g -Os -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror -Wno-array-bounds -include AutoGen.h -fno-common -ffunction-sectio                                                                             ns -fdata-sections -DSTRING_ARRAY_NAME=BaseStackCheckLibStrings -g -Os -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror -Wno-array                                                                             -bounds -include AutoGen.h -fno-common -mlittle-endian -fno-short-enums -fverbose-asm -funsigned-char -ffunction-sections -fdata-sections -Wno-                                                                             address -fno-asynchronous-unwind-tables -fno-unwind-tables -fno-pic -fno-pie -ffixed-x18 -mcmodel=small -flto -Wno-unused-but-set-variable -Wno                                                                             -unused-const-variable -D ENABLE_MD5_DEPRECATED_INTERFACES -mstrict-align -mgeneral-regs-only -c -o /home/stranche/macc-uefi-build-script-main/                                                                             actions/scripts/e2b/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/MdePkg/Library/BaseStackCheckLib/BaseStackCheckLib/OUTPUT/./BaseStackChe                                                                             ckGcc.obj -I/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/MdePkg/Library/BaseStackCheckLib -I/home/stranche/macc-uefi-bui                                                                             ld-script-main/actions/scripts/e2b/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/MdePkg/Library/BaseStackCheckLib/BaseStackCheckLib/DEBUG                                                                              -I/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/MdePkg -I/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/e                                                                             dk2/MdePkg/Include -I/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/MdePkg/Test/UnitTest/Include -I/home/stranche/macc-uef                                                                             i-build-script-main/actions/scripts/e2b/edk2/MdePkg/Include/AArch64 /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/MdePkg/                                                                             Library/BaseStackCheckLib/BaseStackCheckGcc.c
Building ... /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/ArmPkg/Library/ArmArchTimerLib/ArmArchTimerLib.inf [AARCH64]
"gcc"   -g -Os -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror -Wno-array-bounds -include AutoGen.h -fno-common -ffunction-sectio                                                                             ns -fdata-sections -DSTRING_ARRAY_NAME=ArmArchTimerLibStrings -g -Os -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror -Wno-array-b                                                                             ounds -include AutoGen.h -fno-common -mlittle-endian -fno-short-enums -fverbose-asm -funsigned-char -ffunction-sections -fdata-sections -Wno-ad                                                                             dress -fno-asynchronous-unwind-tables -fno-unwind-tables -fno-pic -fno-pie -ffixed-x18 -mcmodel=small -flto -Wno-unused-but-set-variable -Wno-u                                                                             nused-const-variable -D ENABLE_MD5_DEPRECATED_INTERFACES -mstrict-align -mgeneral-regs-only -c -o /home/stranche/macc-uefi-build-script-main/ac                                                                             tions/scripts/e2b/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/ArmPkg/Library/ArmArchTimerLib/ArmArchTimerLib/OUTPUT/./ArmArchTimerLib.ob                                                                             j -I/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/ArmPkg/Library/ArmArchTimerLib -I/home/stranche/macc-uefi-build-script-                                                                             main/actions/scripts/e2b/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/ArmPkg/Library/ArmArchTimerLib/ArmArchTimerLib/DEBUG -I/home/stranc                                                                             he/macc-uefi-build-script-main/actions/scripts/e2b/edk2/MdePkg -I/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/MdePkg/Inc                                                                             lude -I/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/MdePkg/Test/UnitTest/Include -I/home/stranche/macc-uefi-build-script                                                                             -main/actions/scripts/e2b/edk2/MdePkg/Include/AArch64 -I/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/EmbeddedPkg -I/home                                                                             /stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/EmbeddedPkg/Include -I/home/stranche/macc-uefi-build-script-main/actions/scripts                                                                             /e2b/edk2/ArmPkg -I/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/ArmPkg/Include /home/stranche/macc-uefi-build-script-mai                                                                             n/actions/scripts/e2b/edk2/ArmPkg/Library/ArmArchTimerLib/ArmArchTimerLib.c
Building ... /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf [                                                                             AARCH64]
gcc: error: unrecognized command-line option ‘-mlittle-endian’
gcc: error: unrecognized command-line option ‘-mstrict-align’; did you mean ‘-Wstrict-aliasing’?
make: *** [GNUmakefile:293: /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/A                                                                             rmPkg/Library/ArmArchTimerLib/ArmArchTimerLib/OUTPUT/ArmArchTimerLib.obj] Error 1

build.py...
 : error 7000: Failed to execute command
        make tbuild [/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/ArmPkg/L                                                                             ibrary/ArmArchTimerLib/ArmArchTimerLib]

build.py...
 : error 7000: Failed to execute command
        make tbuild [/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/MdePkg/L                                                                             ibrary/BaseStackCheckLib/BaseStackCheckLib]

build.py...
 : error 7000: Failed to execute command
        make tbuild [/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/MdePkg/L                                                                             ibrary/UefiDriverEntryPoint/UefiDriverEntryPoint]

build.py...
 : error 7000: Failed to execute command
        make tbuild [/home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/AARCH64/ArmPkg/L                                                                             ibrary/CompilerIntrinsicsLib/CompilerIntrinsicsLib]

build.py...
 : error F002: Failed to build module
        /home/stranche/macc-uefi-build-script-main/actions/scripts/e2b/edk2/ArmPkg/Library/ArmArchTimerLib/ArmArchTimerLib.inf [AARCH64, GCC5,                                                                              RELEASE]

- Failed -
Build end time: 21:37:26, Dec.05 2022
Build total time: 00:00:12

ls: cannot access 'Build/Armada80x0McBin-AARCH64/RELEASE_GCC5/FV/ARMADA_EFI.fd': No such file or directory
Traceback (most recent call last):
  File "/home/stranche/macc-uefi-build-script-main/actions/scripts/kickoff.py", line 52, in <module>
    main()
  File "/home/stranche/macc-uefi-build-script-main/actions/scripts/kickoff.py", line 48, in main
    edk2_build()
  File "/home/stranche/macc-uefi-build-script-main/actions/scripts/kickoff.py", line 33, in edk2_build
    buildProcess = subprocess.run("./build.sh", shell=True, check=True)
  File "/usr/lib/python3.10/subprocess.py", line 524, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command './build.sh' returned non-zero exit status 2.

Compilation failures are out of the scope of this project, I just provide scripts that should run the build process for you, whether it works or not isn't guaranteed.


Invalid syntax when trying to use the library

I just installed your library as documented using 'pip install orgparser'
and then tried to import 'load' and 'loads' from orgparser in a python shell.
It fails with the following syntax error message:
In [3]: from orgparse import  load, loads
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/IPython/core/interactiveshell.py", line 3296, in run_code
exec(code_obj, self.user_global_ns, self.user_ns)
File "", line 1, in
from orgparse import  load, loads
File "/usr/local/lib/python3.5/dist-packages/orgparse/init.py", line 112, in
from .node import parse_lines, OrgNode # todo basenode??
File "/usr/local/lib/python3.5/dist-packages/orgparse/node.py", line 16
chunk: List[str] = []
^
SyntaxError: invalid syntax

Hi!
Right, so the reason is that you're using python3.5, and I've recently had to drop support for python < 3.6. (just updated release notes for that, so thanks for spotting! https://github.com/karlicoss/orgparse/releases/tag/v0.2.0)
If you can't/don't want to update your python version now, you can use pip install --force-reinstall 'orgparse=0.1.4' to install the previous version which should work with python3.5. Let me know if that helps!

Many thanks !
I decided to upgrade my python version to 3.9.0 and it works well now.
I would also been interested in a capacity to serialize back the org nodes into an org file,
as you experiment with inorganic.

Glad it worked!
If guess you want to load something with orgparse, modify and then serialize back? It's not directly supported, at least yet, but:

for modifying, you can modify the internal attributes of OrgNode, e.g. set node._heading = "something"...

for serializing, you can traverse it recursively and write out:
for x in root:
    print('    ' * x.level + x.heading)

, or something like that

Yes, I see. It can help for the moment...
And why not merging orgparse with orger ?

And why not merging orgparse with orger
Mainly because they are serve pretty different purposes at the moment, so better keep it separate for simplicity. The kind of org-mode rendering orger is doing is very specific (i.e. list hierarchies), and to justify integration with orgparse it would need to be more general purpose so both libraries could somehow benefit from it


feat: add accel brake map calibrator packages

Related Issue
#1
Related Link
This PR depends on #4
Description
Add accel brake map calibrator packages from https://github.com/tier4/AutowareArchitectureProposal.iv
How to review
Check the following items
vehicle cmd gate

readme
sample launch

@taikitanaka3
Could you merge this?
https://github.com/tier4/AutowareArchitectureProposal.iv/pull/755

@tkimura4  Done at 3c9e34c


Properly encode BigDecimal values whose first digit is 10k

When serializing a numeric column, we need to take a decimal value and
convert it to a list of its digits in base 10k. The serialization code
had a bug when the first digit was exactly 10000, resulting in the
digits being [10000, ...] instead of [1, 0, ...]. This bug only
affected the integral part, as the decimal portion uses different logic
in order ot strip trailing zeroes.
Fixes #1044.

/cc @rubdos


Why why not just products : Array[Slot]?

What is the point of having a single product, then byproducts?

What is the point of having a single product, then byproducts?

It really doesn't make sense anymore, I think it's interesting to change to this idea, it would be a little simpler.
I believe it was like this because at first there was only one product and the by-products were added later.

Fixed on 0.9.3


applyAsync on a root resource should create a dependency resource onl…

…y if it is not already created and root resource always needs to be updated in this case.
@jianghaolu this is the issue we discussed last week i.e. root resource not getting updated on applyAsync call. Looks like the quick fix we discussed didn't work so fixing it in this PR. [This was blocking my extension update scenario].

Can one of the admins verify this patch?


update bitbucket-pipelines.yml filename in installation

User description
Thank you for providing such a useful tool.
I noticed that the bitbucket_pipelines.yml file mentioned in the documentation was not functioning correctly with Bitbucket Pipelines. I have corrected the filename to bitbucket-pipelines.yml, which resolves the issue.
I appreciate your ongoing efforts and look forward to the continued development of this tool.

PR Type
documentation

Description

Corrected the filename in the Bitbucket installation documentation from bitbucket_pipelines.yml to bitbucket-pipelines.yml.
This change ensures that the documentation aligns with the correct file naming convention required by Bitbucket Pipelines.

Changes walkthrough 📝
Relevant filesDocumentation

bitbucket.mdCorrect filename for Bitbucket Pipelines configuration

docs/docs/installation/bitbucket.md
Corrected the filename from bitbucket_pipelines.yml to bitbucket-pipelines.yml.  Ensures compatibility with Bitbucket Pipelines.

+1/-1

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

Thanks @nomi3 !


Make compatible with older versions and other changes

Hello! First of all, thanks for this nice plugin, it's really helpful.
I'd like you to consider merging these changes I made:

First of all and most importantly make the plugin compatible with older versions of IDEA by explicitly setting a sinceBuild. I've found the build number by running an code inspection and seeing what the lowest build was where all the APIs used in your code were available.
I've added an alternative way to check if the debugging session is for an IntelliJ Plugin. Instead of evaluating I search for the presence of the ApplicationManager class in the process classpath and if yes that means it's an IntelliJ instance. This is not just a little bit faster (actually, upto 30x faster in some cases) but, more importantly, also handles the case where Application.isInternal() returns false which is the default case for Legacy IntelliJ Plugin projects for example. I haven't deleted the original checking logic in case mine fails.
Some minor changes that IntelliJ itself suggeste: replacing deprecatedServiceManager. getService() with the new way of getting application services and replacing JList with JBList (doesn't break anything).

Thank you. Feel free to test these changes and tell me what you think about them.

Thx for the PR! Please give me some time to review it :)

I've updated the PR to make it compatible with your new changes


Fix/animated lists types

Summary
I was working on Animated.FlatList and found some types missing as below

also Animated.SectionList

So I added type definition for Animated.FlatList and Animated.SectionList copied from FlatList types located at Library/Lists/FlatList.d.ts, Library/Lists/SectionList.d.ts.

Changelog
[GENERAL] [FIXED] - add missing FlatList types for Animated FlatList
[GENERAL] [FIXED] - add missing SectionList types for Animated SectionList

Test Plan

Ran yarn test-typescript and yarn test-typescript-offline with no errors.

Can we factor this to reuse the imperative methods already defined for VirtualizedList, instead of duplicating this?

I tried to use abstract class to reuse the imperative methods.
Thank you 🙇🏻♂.

Do you think it is a good idea to make changes only on Animated.d.ts and not change Flatlist.d.ts and SectionList.d.ts? Otherwise this looks good to me.

Do you think it is a good idea to make changes only on Animated.d.ts and not change Flatlist.d.ts and SectionList.d.ts? Otherwise this looks good to me.

I made changes only on Animated.d.ts to fix Animated.FlatList type definition not supporting Animated.FlatList method types which shares with FlatList. (scrollToIndex, scrollToItem, ... etc).
So, I fixed Animated.FlatList to extends FlatList types including method types.