JDBC 'ROLLBACK' throws exception for rejected txns

I fixed OLTP-Bench so that it doesn't try to rollback a txn twice in TPC-C when there is a UserAbortException. The problem is that we don't seem to support JDBC rollback at all:
This line here:
https://github.com/oltpbenchmark/oltpbench/blob/master/src/com/oltpbenchmark/api/Worker.java#L427
Throws this exception:
java.lang.RuntimeException: Unexpected fatal, error in 'WORKER<TPCC>010' when executing 'Payment/02' [PELOTON]
        at com.oltpbenchmark.api.Worker.doWork(Worker.java:524)
        at com.oltpbenchmark.api.Worker.run(Worker.java:296)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.postgresql.util.PSQLException:
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2310)
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2023)
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:217)
        at org.postgresql.jdbc.PgConnection.executeTransactionCommand(PgConnection.java:778)
        at org.postgresql.jdbc.PgConnection.rollback(PgConnection.java:811)
        at com.oltpbenchmark.api.Worker.doWork(Worker.java:427)
        ... 2 more

This occurs when a Payment txn tries to update the WAREHOUSE table with this query:
https://github.com/oltpbenchmark/oltpbench/blob/master/src/com/oltpbenchmark/benchmarks/tpcc/procedures/Payment.java#L39
Here is the original exception that causes us to try to rollback the txn:
13:19:21,703 (Worker.java:417) WARN  - PSQLException thrown when executing 'Payment/02' on 'WORKER<TPCC>018' [Message='', ErrorCode='0', SQLState='40001']
org.postgresql.util.PSQLException:
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2310)
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2023)
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:217)
        at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:421)
        at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:166)
        at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:137)
        at com.oltpbenchmark.benchmarks.tpcc.procedures.Payment.run(Payment.java:182)
        at com.oltpbenchmark.benchmarks.tpcc.TPCCWorker.executeWork(TPCCWorker.java:74)
        at com.oltpbenchmark.api.Worker.doWork(Worker.java:386)
        at com.oltpbenchmark.api.Worker.run(Worker.java:296)
        at java.lang.Thread.run(Thread.java:745)

To reproduce this, run the latest version of OLTP-Bench with an updated version of @jessesleeping's testing scripts:
https://github.com/apavlo/peloton/blob/master/script/oltpbenchmark/testbed/measure-performance-tpcc.py
$ python measure-performance-tpcc.py hostname 15721 --client-threads=20

I can look into this and #435

@sid1607 Great. I realize that you're traveling this week, so just let me know if you can't get to it so that we can have somebody still around look at it.

At a high level, I think this bug is because -

I call TrafficCop::AbortQueryHelper() when 'ROLLBACK' is issued by the client
AbortQueryHelper() is designed to always send an ErrorResponse as it assumes Query abortion is never supposed to happen

Since AbortTransaction is the required action from 'ROLLBACK', I think the fix is to not send an error response when 'ROLLBACK' is sent. This should be a quick fix.

@sid1607 This fix works! The # of rejected has gone down. Trying it now with higher client thread counts

Yes, I was just testing it too on MemSQL machines and it seems to be fine. Histograms show many unexpected errors, which I think are because of - https://github.com/oltpbenchmark/oltpbench/blob/master/src/com/oltpbenchmark/api/Worker.java#L422
I don't think these failures should be recorded under txnErrors?

Also, I will issue a PR for this now

@sid1607 I need to think about this. I think our logic is still incorrect. We don't have this problem with postgres.
I will take care of this. Have a safe flight. Thanks for everything.

Thanks! I'll try pitching in if issues are still open, once I reach


Does Hudi will be supported ?

We are recently building lakehouse platform with Hudi, and I am just wonder that does openmetadata will support Hudi plugin in the future?

@ShepardZhao would you be interested to contribute the connector? We have great documentation to guide you https://docs.open-metadata.org/v1.4.x/developers/contribute/developing-a-new-connector


Title is missing ; Results not matching with Web Service and Web Application

Hi, I tried to convert PDF to Full Text Document.
The title of the document is missing in the extracted xml document.
Here are my trails.
Trail 1:
In Webapp , the title statement is missing.
<titleStmt>
              <title level="a" type="main"></title>
  </titleStmt>

In Webapp, with Consolidate header option enabled,
<titleStmt>
                <title level="a" type="main">  Document Title    </title>
    </titleStmt>

Trail 2:
From CURL Command,

curl -v  --form<EMAIL_ADDRESS>http://<IP_ADDRESS>:8900/api/processFulltextDocument

curl -v  --form<EMAIL_ADDRESS>consolidateHeader=1 http://localhost:8900/api/processFulltextDocument

curl -v  --form<EMAIL_ADDRESS>--form consolidateHeader=1 http://localhost:8900/api/processFulltextDocument

For all three, I got
 <titleStmt>
                <title level="a" type="main"></title>
    </titleStmt>

Title is missing.
Please guide/suggest me steps to improve/get title fileld in results.
Batch mode is also fine.

Hello @rajeshkumargp !
Thanks for reporting the problem, could you add the PDF (or send it to me by email if it is not public) so that we can reproduce the error?

Let me check and update you.

Reading order issue, the title comes at the end of the page in the PDF stream and for some obscure reasons it vanishes in the limbos.


Loss and Gradients not correct when last batch has different size

Thank you for providing the gradient accumulation feature. It has helped me a lot in in developing a custom optimizer that needs accumulated gradients.
However, when looking through the code, especially the normalization line, I'm having questions about the correct implementation: https://github.com/keras-team/keras/blob/efec34132d70d392474665edb585755f57247599/keras/src/optimizers/base_optimizer.py#L394
This assumes that all batches are of equal size because they contribute equally to the gradients. Typically, the last batch in an epoch is of unequal size (the remainder). By normalizing over the full number of batches, the gradients of the last batch get more weight than the others before. This might become negligible for very large datasets with many batches and a last batch of roughly the same size. However, the mean loss/gradients are not correct.
This is also true for the loss computation; the loss of the last batch has a relatively higher impact.
Here is a notebook showing this behavior:
https://colab.research.google.com/drive/1_Ih_xNjW4Ofv-vQr3v6xRZ0PuVGwxvS0?usp=sharing

This is true for the non-accumulated case as well: each step of gradient update is weighted the same independently of the size of the batch.
It's not clear to me whether this should be changed -- this is the expected behavior when doing gradient descent, I would think.
If you want to change that for a custom training loop, I think the best way to achieve it would be to keep track of the batch size and multiply the gradients of each batch by the batch size (divided by some constant factor probably equal to the average batch size, to avoid having to change the learning rate by a lot). This can be done in a custom train_step().
Another alternative, which would be preferred most of the time, is to by-pass the issue by always having the same batch size. This can be achieved easily in tf.data, for instance by using drop_remainder when batch data, or using repeat() to make the dataset infinitely repeating.

Thank you for your answer. Dropping the remainder seems the best solution, however, when dealing with large batches this is not ideal.


start: less content in sub-index pages

The only issue with adding this middle click-level is that it's possible to "get lost" in the navigation. Example: I click Get Started and read the general index. Then I only open the Data Management element in the nav (click the little arrow) *without opening its index page* and see that there's pages inside. I then assume the content starts in the first sub-page (Accessing Data) and click on that. I have now missed all of the basic info on data mgmt. Cc @shcheklein

Originally posted by @jorgeorpinel in https://github.com/iterative/dvc.org/pull/3455#discussion_r859150197
Also brought up recently in https://github.com/iterative/dvc.org/issues/3676

@iesahin could you still look into this?


Mobile compatibility

Add mobile compatibility for different device types, including phones/tablets in landscape and portrait mode. See here: https://responsivedesign.is/develop/browser-feature-support/media-queries-for-common-device-breakpoints

Full mobile functionality as of 11f39d3c1a5f5583ce48540c872d8650efe95d3e. Adding device-specific CSS is the only remaining task here.

Tablet Landscape full functionality.
Tablet Portrait single-column view.
Phone Landscape no footer, single-column view.
Phone Portrait no header, text-only footer, single column view.

Satisfactory as of bfcd29dfe90c18a97df12d2e863a54f880944be0.

Samsung Galaxy Note5 : Chrome 51.0.2704.81

Verified working on Shawn's phone as of 1f50039161bfd48a9d9974be6d3dfb9b7e79c35b. Not a Galaxy, though, so this could potentially be a Samsung-specific issue.
Also, I contacted a cross-browser compatibility provider about getting a free license because all of our code is publicly available.

Fixed as of f0dea657c755b0298232e83de1d11e5f28242308.


Release process and versioning

I would like to clarify the release process and versioning of this amazing bundle. Unfortunately, the configuration changed in a non backwards compatible way from version 0.9.10 to the latest stable version 0.9.21, the option json_api does not exist anymore. I would assume that such a change should require a new major version, definitely not just an increase of the patch number. At the moment, on my project, I added ~0.9, and this caused things to break badly. What are the intents for the future? Should I lock on composer the version?

@titolendable Totally right, my bad. I've been rushing last week and might have made more than one hideous errors like that.
@acmenna, can you add some tags for this?

@acmenna, where you able to check this out?

@titolendable: Unfortunately, we cannot amend it because we could affect other users. Please, lock the version in your composer.json unless you were able to upgrade. In addition, we've created 0.10.0 that will reflect the latest development changes.
Sorry for any inconvenience.

@acmenna that's exactly what I did, it solved my problem, hopefully this problem will not happen again in the future, keep up the good work.

Thanks, @acmenna! And thanks, @titolendable!
We'll try to be smarter about versioning next time. It was definitely a n00b mistake :smile_cat:


build: Add article-template to Travis-CI

Just mainly followed https://code.visualstudio.com/docs/extensions/testing-extensions with some changes for the mono-repo setup here.
Not sure if the stages part makes sense in this case, mostly done to spearate out the plug-ins. This means they don't parallelize though.

Hi @nschonni , thanks for the contribution.  Reviewing PR now.

How about to enable tslint check in CI?

Closing this out since it hasn't gotten any traction. Might still be good to setup Azure Pipelines or something


fix: prevent multiple submits

This PR solves a problem I have often encountered - when clicking a button instead of waiting, someone was able to send several of the same appeals. When submitting the form, the button is disabled and the user is informed that the form is being submitted.

Thank you for the fix!


How to set custom background with transparency?

When i call setItemBackground(someDrawable) - this drawable is set over default white rectangle, but not replacing it. For example you can not set the background with rounded top corners. How can i reach this?

There's no way to do this, since the item background is drawn on top of the bottom sheet background. The item background setter is meant to change the background color or ripple, not to add custom borders or shapes.


Move DNS related alerts to cabbage

during our alerts session we have identified alerts that probably should land on cabbage plate - ping in channel if discussion is needed

@mcharriere updated


Update artemis-jms-client-all to 2.26.0

Updates org.apache.activemq:artemis-jms-client-all from 2.19.1 to 2.26.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.activemq", artifactId = "artemis-jms-client-all" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.apache.activemq", artifactId = "artemis-jms-client-all" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #344.


Part of the software switch will originally control the content

Pock does a good job, but I want to see the original way when I use some other software，Like JetBrains or Safari, sometimes their feature bars are really handy

You can double press ^Control key to toggle between Pock and default Touch Bar.


Add a has_composer_package function to php images

Credits to @sroze for creating it in #329

just seen it's use-case uses "true" but I want to convert to return values for simple if has_package "package" bash evaluation

this doesn't currently check packages-dev, which would be a good idea also

Great work tho 👍


Day 403

Good morning! Here's your coding interview problem for today.
This problem was asked by Two Sigma.
Using a function rand5() that returns an integer from 1 to 5 (inclusive) with uniform probability, implement a function rand7() that returns an integer from 1 to 7 (inclusive).

Identical to Day 45 https://github.com/vaskoz/dailycodingproblem-go/issues/101


[msal-node] Export request types

Coverage remained the same at 82.733% when pulling 8644c725adfc901ad3280c3a73c0c7292b54f796 on msal-node-export-request-types into d835e669489757e483fbda73fa487c1e877c741f on dev.


docs: update the ROOT documentation and error messages

The documentation now reflects what happens in the
setting/repository.go::newRepository function:
filepath.Join(AppWorkPath, RepoRootPath) was missing.

The error message displayed when RepoRootPath is not found now
displays the value of RepoRootPath. Given the complexity of the
construction of this value, only referring to it in the abstract
is likely to be misleading to the Gitea admin trying to interpret
the message.

Codecov Report

Merging #19832 (176edd5) into main (65e0688) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main   #19832   +/-   ##
=======================================
  Coverage   47.28%   47.29%
=======================================
  Files         957      957
  Lines      133346   133346
=======================================
+ Hits        63055    63066   +11
+ Misses      62628    62619    -9
+ Partials     7663     7661    -2

Impacted Files
Coverage Δ

cmd/serv.go
2.33% <0.00%> (ø)

modules/queue/queue_bytefifo.go
47.29% <0.00%> (-2.89%)
:arrow_down:

modules/queue/workerpool.go
53.62% <0.00%> (-1.04%)
:arrow_down:

routers/api/v1/repo/pull.go
47.17% <0.00%> (+0.17%)
:arrow_up:

models/issue_comment.go
52.23% <0.00%> (+0.33%)
:arrow_up:

models/repo_list.go
83.37% <0.00%> (+0.44%)
:arrow_up:

routers/web/repo/view.go
40.48% <0.00%> (+0.48%)
:arrow_up:

services/pull/check.go
29.13% <0.00%> (+1.18%)
:arrow_up:

modules/queue/queue_disk_channel.go
62.08% <0.00%> (+1.25%)
:arrow_up:

models/unit/unit.go
48.71% <0.00%> (+1.70%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

@delvh @techknowlogick what about logging the error with the path and adding a reminder to the error message that the path can be found in the log? Would that help with debugging while not compromising security?


GetExchangeRequest has a required party field.

GetExchangeRequest currently has a required oneof field named party.
From AIP-131:

The request message must not contain any other required fields, and should not contain other optional fields except those described in another AIP.

The implementation checks whether the authenticated user matches this field, and furthermore uses the value in the underlying query. Instead, the implementation should read the Exchange and then check whether it matches the caller.

Obsoleted by #143


Add linked list implementations

Add implementations for the following in C:

Memory efficient double linked list (XOR linked list)
Circular linked list.
Unrolled linked list.

Create a folder named < github-handle >. For example mine would be sharanyakamath.
In that folder add a files named xor.c , circular.c and unrolled.c

Add Appropriate labels to the same!

I claim

Issue closed, end of Hacktoberfest!


Mere mention of PointSize BuiltIn does not require Shader capability

Fixes https://github.com/KhronosGroup/SPIRV-Tools/issues/365 which
was reopened for this.

+2 LGTM.

Rebased


Csi driver

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

@scetuch What is the objective of this PR?  Please check out from development branch and submit PR to development branch, not the master branch.  Thanks.

Close this PR. The new one on #887

Please close this PR. The new on #887.


Vendor library name tracking issue

There's currently a bit of a mix of vendor library names:

semi-diode-Vendor and semi-trans-Vendor for diodes/transistors
Vendor for generic parts

In addition, there are libraries for vendors that are now owned by others (for example Atmel, now acquired by Microchip).
I'm not sure of my original decision to split off semi-diode-* and semi-trans-*; maybe these should just be in the main vendor library. Filtering can be done by the component selector.
I think I want to keep separate vendors that are more recognized by an old name - for instance, keep Atmel parts under Atmel. Open to comments on that.

I agree, it is best to keep "historical vendors" separate if they are still recognizable. Huge brands like LT(ADI) or Atmel (MCHP), but perhaps not Supertex (MCHP) or other tiny chip companies that got eaten by the big players. I would ditch the separation of semi-diode, semi-trans, etc and just name every non-generic library with a vendor/brand name with a standardized capitalization.


Increase CI test coverage

We have set up CI with GitHub Actions which runs on every open PR, however our code coverage is extremely low and should be increased in the future to ensure robustness with new code and updates.

Regression tests would be the most important ones I think. Those kind of test make sure that the results from running the full analysis are the same like in a previously run analysis that we confirmed to be true.
@hrwakeford it seems to me like it would be fairly easy to write some simple regression tests, as we would just be comparing numbers to numbers, e.g. the results for the marginalised parameters. I could start writing this for W17 in the case of fit_time. Does that make sense to you or would you prefer I choose a different case as our benchmark?

I think that fit_time is the perfect thing to test it on as that will be used most often. The most comprehensive would be fit_all but that would not be needed in this simple "does it work" test.

@ivalaginja Can we close this issue now?

yes this can now be closed


Add capability for projected climate info (enables stage transitions)

Haven't finished handling both historic and projected climate drivers yet. Since it is possible to run the eq stage with just the historic data, things are hardcoded to use historic right now (See Cohort constructor).
Solving this issue will involve making some decisions about how/when to read in historic vs projected data and also how to decide which to use (maybe somewhere in the vicinity of the BOOST_LOG_NAMED_SCOPEs for selecting stages in TEM.cpp

I think this is finished now?

This seems to be resolved by PR #157


Questionable usage of constexpr in type_info.hpp

Several member functions in type_info.hpp are marked constexpr despite relying on functions or values that are themselves not constexpr. For example, type_info has a constexpr constructor which calls type_index::value(), type_hash::value(), and type_name::value():
    template<typename Type>
    constexpr type_info(std::in_place_type_t<Type>) noexcept
        : seq{type_index<std::remove_cv_t<std::remove_reference_t<Type>>>::value()},
          identifier{type_hash<std::remove_cv_t<std::remove_reference_t<Type>>>::value()},
          alias{type_name<std::remove_cv_t<std::remove_reference_t<Type>>>::value()} {}

Of these three calls, only type_name::value() is static constexpr, while the others are static only. For brevity, I will only show the definition of type_index:
template<typename Type, typename = void>
struct ENTT_API type_index final {
    [[nodiscard]] static id_type value() noexcept {
        static const id_type value = internal::type_index::next();
        return value;
    }

    [[nodiscard]] constexpr operator id_type() const noexcept {
        return value();
    }
};

Trying to initialize a constexpr variable with these constexpr functions does not compile and may confuse users (as these functions are clearly marked constexpr). This can be demonstrated easily: https://godbolt.org/z/WoxzaMMvs
I suggest removing constexpr from these functions where it offers no benefit.
I ran into this issue while researching ways to make a constexpr counter for type IDs. While EnTT may not need it, I was shown a possible solution to the problem (which, admittedly, has questionable legality): https://mc-deltat.github.io/articles/stateful-metaprogramming-cpp20

That's questionable either way actually.
The fact is that all type_* tools are fully customizable and nothing prevents you from defining a constexpr version of them.
If it happened, it could be an issue not to have i.e. the type_info constructor as constexpr.
So, let's say, among the choices to make, I made the most flexible one in case of customizations and not the most correct one given the default version. 🤷♂
That said, both hash and name are constexpr. The only one left out is index at the moment. Am I missing something?

Closing as starving as well as invalid/won't fix.


Tortoise orm support

So I run into an import error for the testclient when I try and run the tests but in theory everything works for the test implementation and I tested it by hand and it should behave the same way as the others!

Awesome! I will take a closer look in the morning :)

Awesome! I will take a closer look in the morning :)

Sorry got caught up in school. I'm new to open source contributing. I see you have changes requested but I can't find them. What do I need to do? 😛

Sorry got caught up in school. I'm new to open source contributing. I see you have changes requested but I can't find them. What do I need to do? 😛

Sorry got caught up in school. I'm new to open source contributing. I see you have changes requested but I can't find them. What do I need to do? 😛

I've set it all up with pytest, All that's left is to setup tortoise correctly in tests/implementations/tortoise.py so the tests pass. Currently the models never registered with tortoise. Once the tests pass we should be good to go😃

Sorry got caught up in school. I'm new to open source contributing. I see you have changes requested but I can't find them. What do I need to do? 😛

I've set it all up with pytest, All that's left is to setup tortoise correctly in tests/implementations/tortoise.py so the tests pass. Currently the models never registered with tortoise. Once the tests pass we should be good to go😃

Awesome work @timwford . Thanks for all the help 🥇


plan should override storage_policy requirement in cloudapps instance creation

Hi,
Please see https://github.com/Commvault/cvpysdk/blob/dev/cvpysdk/instance.py#L1120-L1131
The logic here demands storage policy to be set, but it is optional if plan is provided, or at least should be.
The code logic needs a refactor to allow the part below at https://github.com/Commvault/cvpysdk/blob/dev/cvpysdk/instance.py#L1150-L1153
to override storage policy.

Hi, Can you please confirm in which SP you are trying this?

Hi @tejaKing123,
We are working with 11.30 (2023) currently.

Hello @tejaKing123, I do not understand the question as it should be generic for any cloud storage instance type as in Command Center there is no concept of storage policies only plans.
That said we are using it for Amazon RDS currently.

Hello @tejaKing123, can you share an update?

@tejaKing123 the update looks good, thanks for picking this up!


Update go.mod

go get was failing with:
•6% ➜ go get github.com/m110/watermill-amazonsqs
go: github.com/m110/watermill-amazonsqs upgrade => v0.0.0-20200625163019-8d5def4d7c67
go get<EMAIL_ADDRESS>parsing go.mod:
	module declares its path as: github.com/ThreeDotsLabs/watermill-amazonsqs
	        but was required as: github.com/m110/watermill-amazonsqs

I believe this fixes it

@p4tin @m110 can we get this reviewed and merged ?

I'm sorry folks, I totally missed this PR for some reason. 😞

Thanks!


Add AERONET cmorizer

Description

Closes #3067
Link to documentation:

Before you get started

[ ] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[ ] 🛠 This pull request has a descriptive title
[ ] 🛠 Code is written according to the code quality guidelines
[ ] 🛠 Documentation is available
[ ] 🛠 Tests run successfully
[ ] 🛠 The list of authors is up to date
[ ] 🛠 Any changed dependencies have been added or removed correctly
[ ] 🛠 All checks below this pull request were successful

New or updated recipe/diagnostic

[ ] 🧪 Recipe runs successfully
[ ] 🧪 Recipe is well documented
[ ] 🧪 Figure(s) and data look as expected from literature
[ ] 🛠 Provenance information has been added

New or updated data reformatting script

[ ] 🛠 Documentation is available
[ ] 🛠 The dataset has been added to the CMOR check recipe
[ ] 🧪 Numbers and units of the data look physically meaningful

To help with the number of pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

The latest changes add num_days and num_points as ancillary variables for the purpose of quality control.
@catherinehardacre, with the files cmorized by the latest version here, you should then be able to do something like
c = iris.load_cube("od440.nc")  # use correct filename and path, of course
num_days = c.ancillary_variable("Number of days")
num_points = c.ancillary_variable("Number of points")

c.shape == num_days.shape
c.shape == num_points.shape

and use that information to perform the filtering.

Hi @alistairsellar. I believe it's ready for review. I used the branch when working on #3048 with @catherinehardacre last year, and don't remember having any issues. Have you run into any issue @catherinehardacre?

@alistairsellar @ljoakim I spent some time testing the aeronet-cmorizer branch last week and it is working perfectly. So all ready to go!

Thanks @ljoakim and @catherinehardacre, in that case I've moved it from draft to ready-for-review. I also resolved a trivial conflict with a parallel change on main (new AGCD cmoriser) to bring this up to date with main.
This PR currently doesn't have an assignee - @ljoakim is it OK if I assign to you?
I could do the science review. @ESMValGroup/tech-reviewers can anyone suggest a technical reviewer?

This PR currently doesn't have an assignee - @ljoakim is it OK if I assign to you?

@alistairsellar Yes, it is ok! I need to get up to speed a bit, and might not have much time the next couple of weeks, but I'll do what I can to help out.

This PR currently doesn't have an assignee - @ljoakim is it OK if I assign to you?

@alistairsellar Yes, it is ok! I need to get up to speed a bit, and might not have much time the next couple of weeks, but I'll do what I can to help out.

Great, thanks! Caveats all totally understood.

@hb326 Thank you for testing the downloader and formatter! Since @zklaus has moved on from ESMValTool, I have added some text in the PR description above and I will expand this to make it clear that the additional packages are required at the moment.
In the description I have explained about the weirdness of the NetCDF file structure... I know it looks a little odd, but I think it is the best approach for point source data sets. I'm happy to discuss further though :). NetCDF does support non-contiguous lat/lon and it means that Iris cube-type operations can be performed on the whole (AOD) data set. The hugely sped up the loading and certain processing operations in the diagnostic (thanks @ljoakim!), which would otherwise have involved looping over individual stations.

I'm sorry @ljoakim - this is also beyond my knowledge! I did originally have trouble with the pys2index package due to some issues with conda. However, I'm sure that Klaus did manage to fix that because in my most recent testing with a clean branch, I did not run into those problems. Hopefully @valeriupredoi can shed some light on this?

Shall have a look in a wee while later today, folks! Cheers for raising the issue 🍺

OK folks here's the spiel about that issue with pys2index - it's got issues building the wheel when it gets installed from PyPI - we always install everything from conda-forge via the environment file, but the Circle test runs via a container that loads a pre-built environment that doesn't contain pys2index since it was added only in this PR, so the install sitches to installing it from PyPI instead, falling over due to the pkg having wheel building issues (this is one of the reasons why we tray to get our dependencies 100% from conda-forge). Solution for now is to have it removed from setup.py so we don't fall into this hole again; installation from conda-forge works very well, see GA tests

Thanks for looking into it @valeriupredoi! Good to hear installation works from conda-forge.
In the Circle run_tests there is another error (ModuleNotFoundError), due to the missing package: https://app.circleci.com/pipelines/github/ESMValGroup/ESMValTool/11601/workflows/d59e5c22-0972-4bc7-8c0b-89e407145a28/jobs/73241/steps?invite=true#step-107-12603_149. I'm guessing this is also because that step runs in the environment of the pre-built image? Should we ignore this error? Is the image rebuilt when releasing a new version of ESMValTool?

there are quite a few assertion calls, those would be very nice if they got converted to exceptions, and be raised in a user-friendly way (I imagine Klaus put those in there before finding time to convert them to runtime exceptions)

when building the iris Cube, it'd be very good if all data members (ie data, and coordinates/dimensions) were lazy ie built with Dask - I've seen most of them are but I also saw a few are still numpy arrays - this is not crucial when data is loaded from disk, but it'd be good to have it when the user is running the CMORization on the fly

I'll look into it. I'll open a new PR for pys2index as well, to get the tests to pass.

@valeriupredoi, @ljoakim - Thank you for your review and work to get this PR up to speed. These issues are out of my comfort zone, I'm better on the scientific analysis... If it is useful, I can test any changes :)

there are quite a few assertion calls, those would be very nice if they got converted to exceptions, and be raised in a user-friendly way (I imagine Klaus put those in there before finding time to convert them to runtime exceptions)

when building the iris Cube, it'd be very good if all data members (ie data, and coordinates/dimensions) were lazy ie built with Dask - I've seen most of them are but I also saw a few are still numpy arrays - this is not crucial when data is loaded from disk, but it'd be good to have it when the user is running the CMORization on the fly

I've removed all assertions, but couldn't change all numpy arrays to dask arrays, see example in my previous comment.

A few questions:

There needs to be a bibtex entry for the dataset in the references folder, right? Which should be referenced from the new AERONET.yml file?
Is there a list of supported datasets that should include the AERONET dataset?

* Is there a list of supported datasets that should include the AERONET dataset?

Great work @ljoakim! Sorry I'm not sure about your first question, but for the second one, please update the documentation here:
https://github.com/ESMValGroup/ESMValTool/blob/b9e67d8142053ae93995e90ce762c56b4c4d876c/doc/sphinx/source/input.rst?plain=1#L225
Separately, I've used the branch to download and cmorise the aeronet data. Worked out of the box! One question / suggestion: the raw data comes with a USAGE_INFORMATION file with various requests about how to credit Aeronet in publications. Is there any way that we can carry some of that spirit of those requests through to the cmorised files? Clearly too much information to include in a netCDF attribute verbatim, but could the netCDF file perhaps link to an online copy of the usage information file?

gents, great work! Just pls let me know when I should re-review my stale review, and will do so asap - there are solid chances this can make it into 2.11 :beer:

Hi @valeriupredoi! Yes, from a technical point of view, I think it's basically ready for a review. I will return to this PR next week (I will be unavailable for the rest of the week), but there are a few things I believe still need to be addressed:

The AERONET/AOD dataset needs to be added to the supported dataset list in the documentation
As @alistairsellar mention above: the raw data USAGE_INFORMATION should probably be dealt with:

Separately, I've used the branch to download and cmorise the aeronet data. Worked out of the box! One question / suggestion: the raw data comes with a USAGE_INFORMATION file with various requests about how to credit Aeronet in publications. Is there any way that we can carry some of that spirit of those requests through to the cmorised files? Clearly too much information to include in a netCDF attribute verbatim, but could the netCDF file perhaps link to an online copy of the usage information file?

In reference to my own question, the esmvaltool/references folder seems to contain bibtex files for all supported datasets, and a bibtex for the AERONET dataset should probably be added? (maybe @catherinehardacre can help out?)

There needs to be a bibtex entry for the dataset in the references folder, right? Which should be referenced from the new AERONET.yml file?


Add default to prior parameter

What did we want the default parameter to be?

0.5. This has been implemented.


[crypto] Safely generate P-256 secret scalars d and k from random seeds.

Follow-up from #15332
Previously, the secret scalar k was simply fetched from RND, but when reduced modulo the curve order the value will be biased. For this reason, the FIPS spec requires generating the secret scalar from a larger (320-bit) seed, and additionally ensuring it is nonzero. Generation of the secret key from a random seed is very similar.
Note that these implementations are only safe for random seeds (i.e. not keymgr-derived seeds), because they handle the secret in unmasked form and this would be unsafe if the code could be repeatedly executed with the same seed.

thx. nice. I understand this is to avoid bias and achieve FIPS compliance.
We should probably talk about SCA security a bit more. Mainly we should estimate a potential issue from leakage of ephemeral secret scalar k handling in plain. yes this is one-time. leaking a few bits of k in many sigs can be catastrophic though. let's discuss more offline and get back to here with a consolidated view :)

The CI failure is actually a bug in the implementation caused by mishandling the second share in mod_inv. This is what I get for not updating the tests first: https://github.com/lowRISC/opentitan/issues/15409
I'll fix the bug in a separate PR and return to this.

See https://github.com/lowRISC/opentitan/issues/15507 -- after some offline discussions Johann has convinced me that handling k in this way is totally safe because even tiny leakage from single traces can compromise the key. However, I'd still like to merge this for now since it's an improvement over the previous version, and can be more easily built on for further hardening.

Bug has now been fixed; are there any objections to me merging the PR even though it doesn't provide a perfect defense as recorded in #15507? If I don't hear anything I'll assume it's OK to merge.


Cythonize part of code for win32

Pull Request Test Coverage Report for Build 599

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.522%

Totals

Change from base Build 593:
0.0%

Covered Lines:
600

Relevant Lines:
609

💛  - Coveralls


ioc-scan: 1.5.0 -> 1.5.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for ioc-scan is: Tool to search a filesystem for indicators of compromise (IoC)
meta.homepage for ioc-scan is: https://github.com/cisagov/ioc-scanner
meta.changelog for ioc-scan is: https://github.com/cisagov/ioc-scanner/releases/tag/v1.5.4
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.4 with grep in /nix/store/gjiiynlj7isay9w6d1irj4mw1mwda418-ioc-scan-1.5.4
found 1.5.4 in filename of file in /nix/store/gjiiynlj7isay9w6d1irj4mw1mwda418-ioc-scan-1.5.4

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ioc-scan

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gjiiynlj7isay9w6d1irj4mw1mwda418-ioc-scan-1.5.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ioc-scan https://github.com/r-ryantm/nixpkgs/archive/86523871bb1953d15c0357c6aa82791d5847021e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/86523871bb1953d15c0357c6aa82791d5847021e#ioc-scan

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gjiiynlj7isay9w6d1irj4mw1mwda418-ioc-scan-1.5.4
ls -la /nix/store/gjiiynlj7isay9w6d1irj4mw1mwda418-ioc-scan-1.5.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ioc-scan

Maintainer pings
cc @fabaff for testing.

Result of nixpkgs-review pr 281760 run on aarch64-darwin 1

2 packages built:

ioc-scan
ioc-scan.dist


MINOR: Get rid of generic from FetchResponse

Except for LazyDownConversionRecords, we don't use the generic. We should handle the specify case directly instead of making generic in whole project.
In short, this patch is a kind of cleanup.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

It's a bit hard to know when the Lazy version can be used though, right?

It's a bit hard to know when the Lazy version can be used though, right?

You are right :(
Will go back when I have a better idea.

superseded by #9758


Documentation: Update ADSL source in "Creating and Using New Anti-Cancer Start Date" vignette

Please select a category the issue is focused on?
User Guides
Let us know where something needs a refresh or put your idea here!
ADSL should be read from pharmaverseadam instead of admiral.

@vinhn23 , pharmaverseadam is not going to be released in Q3 but in Q4. Thus I have moved this issue to the next release.


CollectionView in VerticalStackLayout doesn't scroll

Update the CollectionView docs to specify that a CollectionView is in a VerticalStackLayout takes up all the space, which stops the CollectionView scrolling. Instead, users should use a Grid.
https://github.com/dotnet/maui/issues/15402

Associated WorkItem - 98883

this is good know however at least the samples show to use Stack Layout maybe the documentation as well.


Read/write region copy

A re-hashing of #730, including original read_memory changes, similar changes in write_memory, and optimized vec creation.
Credits to @slave5vw, who originally pushed #730.

Thank you for working on this implementation, which shows the feasibility of this improvement and measures its impact. This is valuable insights.
After careful consideration we decided this should really be implemented in Wasmer, not here. I opened https://github.com/wasmerio/wasmer/issues/2035. The reason is that if we put so much effort into reasoning whether or not this is a safe operation, it should be available to all users of Wasmer, not just us. In the unlikely case that the feature request is rejected by Wasmer, we'll come back to it here.

Thank you for working on this implementation, which shows the feasibility of this improvement and measures its impact. This is valuable insights.
After careful consideration we decided this should really be implemented in Wasmer, not here. I opened https://github.com/wasmerio/wasmer/issues/2035. The reason is that if we put so much effort into reasoning whether or not this is a safe operation, it should be available to all users of Wasmer, not just us. In the unlikely case that the feature request is rejected by Wasmer, we'll come back to it here.


Add option to customize the default network and netmask

Nowadays, the script uses <IP_ADDRESS> network and <IP_ADDRESS> netmask for default, but it would be really nice if it had an option to customize this

I had the same thing in my mind and yesterday I just used editor and replaced by search and replace all 10.8. By 10.88.
Installation went well and all works :)

I deployed the openvpn on one host and its working as expected, later I installed openvon on another host and that is also working fine but the problem is I can nit use both openvpns simultaneously and seems like as they are using same private network settings which is conflicting with other setup.
Is it possible the support custom private network during the setup so we can deploy multiple openvpn with unique private network?

I had the same thing in my mind and yesterday I just used editor and replaced by search and replace all 10.8. By 10.88. Installation went well and all works :)

Yeah, I understand that's a "simple" thing to do, but, as there are other customized options (that may be used less than a custom IP range), I believe that would a nice improvement to the script

I deployed the openvpn on one host and its working as expected, later I installed openvon on another host and that is also working fine but the problem is I can nit use both openvpns simultaneously and seems like as they are using same private network settings which is conflicting with other setup.
Is it possible the support custom private network during the setup so we can deploy multiple openvpn with unique private network?

@azfarhashmi do you mean to have multiple openvpns in the same machine for multiples virtual networks? If so, I believe that would me more complex than this, as there may be many other things to consider in this use case


Unsupervised Domain Adaptation

Can this method be used for unsupervised domain adaptation?

In what sense of domain adaptation on you which to apply DiffAE, mind providing more specific details?
One thing I can say though. DiffAE might have some hope on unsupervised image translation problem, e.g. transforming male to female or a cat to a dog and etc. To what extent DiffAE is applicable is a bit underexplored in that regard.

Yes, I was asking about the unsupervised image-to-image translation. To be more specific, translating ceT1 modality to hrT2 modality. These modalities are unpaired. So, can DiffAE be used for an unpaired image-to-image translation?

They seem to be medical images, e.g. from https://www.researchgate.net/publication/359141212_Automated_Koos_Classification_of_Vestibular_Schwannoma/figures?lo=1.

We have even less clue on medical images. Do both modalities share mostly the same structure? Like cropped the same way? Are the differences between domains are spatially located on the same correspoding regions?
My feeling tells me that you have a good chance on this task. Good luck!
If you have any success, mind you keep we keep in touch? I'm curious how well could in work on medical image domains.
You can mail me directly at konpatp (at) gmail.com

Yes, sir, the two modalities share an almost identical structure.
I am going through your paper and the methodology used in your code to check whether domain translation on medical images can be possible with diffae.
Sure, I will be in touch with you :)

well, I am interested in same object

I try to
T1w mri image (2nd column) to T2w mri image (1st column) image translation
all model trained mixed T1w and T2w mri image .
and given xT = T1w, cond = T2w slice (similar slice)
but prediction is not good... any advice?

This is my best, honestly, This is cherry-picking...

Without the domain (medical) knowledge, I am not sure what's the problem with the prediction you have?


Change mall price updates to use Java 9 HttpClient

More HttpClient to prep for https://kolmafia.us/threads/migration-from-http-1-1-to-http-2-0.27303/, again unnecessary (although it does unblock a potential move to HTTP/2 later) as https://kolmafia.us/scripts/updateprices.php doesn't use HTTP/2.
Could do with somebody with access to https://kolmafia.us/scripts/updateprices.php confirming that the calls work completely correctly. I've tested it on a fake server, and it seems to send and receive the right data, but without access to the real server I can't be sure. I have sent some data to the real thing, and got successful responses back.
One more difference found: HttpClient doesn't read http.agent for the user agent; it has to be set manually.
On the plus side, the code is slightly neater, and we can choose to read the whole body in case of error, instead of just the first line, more easily.

Thanks! I will get this in, then look at creating a test for getPostData as a follow-up.


Added entry for turning emails on or off

Change screenshots to 1200px x 800px (the height can flex if you need).

I've made the changes which @adamsilver requested.


Reply with the HTTP 400 Bad Request status code and the appropriate response body in case of malformed requests.

Adding HTTP response status codes.
Replying with the HTTP 400 Bad Request status code and the appropriate response body when a malformed request is came in.
Placing the debug logging enabler into the initial state of the request handler to retrieving it later on.
Retrieving the debug logging enabler from the initial state of the request handler and logging events conditionally.
Bumping version number to 0.1.10.

She looks confident ! :+1: — Approved. :blue_heart:


Add examples for API endpoints - Rosetta, smart contracts.

Relates to https://github.com/hirosystems/docs/issues/101.

Addressed in https://github.com/hirosystems/stacks-blockchain-api/pull/1288.


Add component ID for lock frameworks

Currently, I'm preparing to add lock-related plugin support in the go agent. Since it can be used in multiple languages, we have set it up for various languages.

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

Please fix conflicts and merge.


Dev

Summary :memo:
Write an overview about it.
Details
Describe more what you did on changes.

(...)
(...)

Bugfixes :bug: (delete if dind't have any)

Checks

[ ] Closed #798
[ ] Tested Changes
[ ] Stakeholder Approval

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Move gulp build script to a ui5 CLI module

All settings used in package.json should be usable as CLI params, too.
Furthermore, the user should be able to decide, wether or not to use CLI params, package.json or a .ui5rc file.

I have viewed your project. OpenUser5 library you https://openui5.hana.ondemand.com/downloads/openui5-sdk-1.50.8.zip. This project has disadvantages if offline, do not use the library You can add the bundl library feature to openui5 for faster web applications. thank you!. If you do not bundle the openui5 library, the number of requests will greatly slow down the web app.thank you!

Hi vvthinh,
as mentioned in the README, you can define any UI5 library as source, a self build bundle, a CDN link (as configured at the time) or a custom build of UI5. Please see part Configuration in the README.
Hope this information is helping you.
Kind regards,
Jascha
Jascha A. Quintern
Hackerstolz e.V. – Co-Founder & Board Member
startregion e.V. – Co-Founder & Board Member
PulseShift GmbH – Co-Founder & CXO
Mobile: +49 1577 3819880
Twitter: @fuchsvomwalde
Instagram: fuchsvomwalde
Mailto<EMAIL_ADDRESS>Homepage: www.jascha-quintern.de
Find me on Facebook, XING & LinkedIn

Am 26.03.2018 um 19:07 schrieb vvthinh<EMAIL_ADDRESS>You can add the bundle library openui5.I hope to get help from your team..thank you!
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/pulseshift/openui5-gulp-starter-kit/issues/20#issuecomment-376239937, or mute the thread https://github.com/notifications/unsubscribe-auth/AITaU4LhEh9LnsUdMMW0ERHLwwIgu4t7ks5tiSBbgaJpZM4SbelW.

Hi.
I implemented your project successfully using the CDN = https://openui5.hana.ondemand.com/1.54.5/resources/sap-ui-core.js
When I copy the same version to a local directory (projectRoot->ui5->1.54.5->resources) and changing the package.json to use "local" with:
"local": {
"url": "ui5/{{version}}/resources/sap-ui-core.js",
"version": "1.54.5",
"isPrebuild": true,
"isArchive": false
}
It all fails to start the application:
Uncaught Error: ui5loader-autoconfig.js: could not determine base URL. No known script tag and no configuration found!
at ui5loader-autoconfig-dbg.js:83
at ui5loader-autoconfig-dbg.js:395
index.html:61 Uncaught TypeError: sap.ui.getCore is not a function
at index.html:61

Hi Jean,
thanks for your message. Unfortunately I’m not able to reproduce your issue. Here is what I did:

download runtime (copied URL from here https://openui5.org/download.html) with the following setup:

But this step can also be done manually. What download URL have you used?

after successful download, I switched the ui5 src to the local folder (as you did):

But after starting the app with yarn start I had no console errors or any 404s.
At the time I have only two assumptions: We used different download links for the UI5 runtime, or your project is missing corrections from the master branch. You may could try to clone the project again from master to ensure the code and related dependencies are up to date.
Hope this information was helpful for you at that time.
Kind regards,
Jascha

Am 30.05.2018 um 07:15 schrieb jean-vox<EMAIL_ADDRESS>Hi.
I implemented your project successfully using the CDN = https://openui5.hana.ondemand.com/1.54.5/resources/sap-ui-core.js https://openui5.hana.ondemand.com/1.54.5/resources/sap-ui-core.js
When I copy the same version to a local directory (projectRoot->ui5->1.54.5->resources) and changing the package.json to use "local" with:
"local": {
"url": "ui5/{{version}}/resources/sap-ui-core.js",
"version": "1.54.5",
"isPrebuild": true,
"isArchive": false
}
It all fails to start the application:
Uncaught Error: ui5loader-autoconfig.js: could not determine base URL. No known script tag and no configuration found!
at ui5loader-autoconfig-dbg.js:83
at ui5loader-autoconfig-dbg.js:395
index.html:61 Uncaught TypeError: sap.ui.getCore is not a function
at index.html:61
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/pulseshift/openui5-gulp-starter-kit/issues/20#issuecomment-393033032, or mute the thread https://github.com/notifications/unsubscribe-auth/AITaU51L3lUxv7ofaqtEyCOz3qqg9lWFks5t3ir6gaJpZM4SbelW.

Hi Jascha.
Finally got to the source of the issue: Windows.
Running the build on windows replaces the / slash with \ slash causing relative paths to fail.

Ah, that's very disadvantageous, of course. I created a GitHub issue to track when relative paths in the ui5 configuration are also compatible on Windows.https://github.com/pulseshift/openui5-gulp-starter-kit/issues/27 https://github.com/pulseshift/openui5-gulp-starter-kit/issues/27

Am 12.06.2018 um 08:11 schrieb jean-vox<EMAIL_ADDRESS>Running the build on windows replaces the / slash with \ slash causing relative paths to fail.

Just ran into the same issue :-)

The solution will be to use path.normalize(sAnyRelativeOrAbsolutePath) anywhere in gulfile.babel.js where paths are used for execution, e.g. "readFile()".
It will convert any path into the correct representation matching the respective OS the node script is running on.


Handle channelName

Adds backend support for channelName
Fixes #170
Fixes OPRUN-2917

I am a bit concerned about item 6 in #163:

Edit the Operator object and change the channel to strimzi-0.33.x

This channel name doesn't match what was merged in #171, so I might need to update the regex.

I am a bit concerned about item 6 in #163:

Edit the Operator object and change the channel to strimzi-0.33.x

This channel name doesn't match what was merged in #171, so I might need to update the regex.

It looks like opm would have an issue with the regex w.r.t. semver catalog template generating minor version channels: https://olm.operatorframework.io/docs/reference/catalog-templates/#example-1 (actually, the last output block).

The channel name regex is now this:
^[a-z0-9]+([\.-][a-z0-9]+)*$

Which out to allow for the channel names, but might be too flexible?

@tmshort maybe wait on @joelanford or @grokspawn to sign off before merging? Just in case I've missed something =S

@joelanford @grokspawn you good with this?
I grabbed the demo script from @perdasilva and modified it to work with channel names per #163


merge desired sia/wallet changes into rivine/modules/wallet/*

To be done prior to focussing on #307.

Previously as part of #85, but now as a separate issue, as there is no (real) need to mix it with the others.

Make sure to check if this solves https://github.com/rivine/rivine/issues/2


Redundant scheduler

Hi!
It would be great to see this (back? i think it once had such mode) in glorytun, maybe as option to choose scheduler?
I use MPTCP for TCP aggregation, almost all high bandwidth transfer go via TCP.
For UDP, almost all data here is time sensitive and for realtime traffic. Since UDP is so little total bandwidth consumption when just using glorytun udp only for udp traffic, a redundant mode make sense. It would give realtime apps 99.99% uptime when dealing with bad links.

Hi,
Before the new scheduler, glorytun was designed to minimize jitter (mostly VoIP).
To fix your problem I plan to implement something like RaptorQ (rfc6330) with the new multipath scheduler. You'll have the best of both worlds.

Sounds great! Looking forward to all the future improvements!

Some people use https://github.com/wangyu-/UDPspeeder to solve this problem.
I like the idea to have a separate program to do this. I'll reopen if necessary.


Optional brackets around expressions in statements

Hi! I'm interested in how easy is to allow optional brackets around expressions in statements. Basically:
if n < 0 {
for i in 0...5 {
while n > 0 {

I've actually tried modifying the ifStatement parsing code, but it seems you cannot simply ignore brackets. They are used somewhere down the line.
I think optional brackets should work just fine, as long as we have { on the same line. So this can be done in a backward-compatible way. It would make the code a bit cleaner.
I'm not saying it should be added to the language itself, it's not an RFC. But I would be interested in adding this to my own fork.

Doing this would interact poorly with block arguments. Consider:
if foo { code... }

Is that an if statement whose condition is foo and whose body is the block, or is it an if statement whose condition expression is foo { code... }? The parser can't tell until it has completely finished parsing that block and can see if there's another block afterwards. That kind of arbitrary lookahead doesn't play nice with a single-pass compiler like Wren uses.
I understand the desire to eliminate unnecessary punctuation, but I think the grammar is a lot simpler and more regular if we just require parentheses for if and for expressions.

Thanks! I have not considered block arguments.


Notifications now longer show in Notification Area List

A few weeks ago everything worked great.  My notifications would pop open.  I would hear a ding and the notifications would go into a list in the action center.  I believe this worked for Edge, Chrome and Firefox.  Now the only time I get the notification to list in the action center is with Edge.  I don't hear the ding either.  Has anything changed?
My configuration:
						Push.create('Important Notifications', { 							body: App.Utils.removeHtml(portalListData[0].text), 							icon: 'resources/images/grey-circle-hbi-125.png', 							requireInteraction: false, 							timeout: ONE_MINUTE * 0.3, 							silent: false 						});
Thanks in advance.

Could you please mention your OS/Browser with their versions.
AFAIK, Chrome has only recently shifted to native notifications that go into the Notification center for Window 10. Twitter Thread for the same

I'm on Windows 10.  I've been testing with Chrome, Canary, Chromium, Edge and FireFox.  Edge is the only one which will send the notifications to the action center.  Chrome used to up until a week or so ago.  I'll see if changing requireInteraction back to true changes anything.

I find it odd that Chrome used to do that before since the integration with Action Center has been only recently rolled out. Since March 2018, a flag was made available to manually enable the support. And in Aug 2018, the chrome guys started rolling out the update that makes it default with Chrome 68. Further updates to Chrome will have the windows native notifications instead of Chrome's version of notifications.
AFAIK, requireInteraction should not hold any effect. Could you please check the value of 'enable-native-notifications' flag in your Chrome and see if that is somehow set to the wrong value.

There's a pretty good chance I'm screwing something up!  I checked the "chrome://flags/#enable-native-notifications".  It was set to default.  I enabled it, but it didn't change anything.  My notifications appear, but not in the Action Center.  Thanks.

@betsonserviceportal Are you seeing the old-style notifications with white background or the new ones which have a shade of black as the background and image on top rather at the bottom ?

Old-style with white background.


Accoil Analytics destination action documentation

Proposed changes
This is documentation for the new Accoil Analytics Segment Destination Action which is currently privately available for installation and soon to have its first test customer.
Merge timing
Happy for this to merge whenever ready as a beta doc and can raise a separate PR later to remove that.
Related issues (optional)
Action merged on https://github.com/segmentio/action-destinations/pull/2421

Thanks for your review @forstisabella . I've applied your suggested changes.

Thanks again @forstisabella . I've applied that last suggestion 👍 Let me know if there's anything I need to do on my end to progress forward.

hi @accoilmj - we're waiting on approval from @tcgilbert on this PR before we merge. Thanks for being on top of this!

Thanks @tcgilbert ! I've applied those suggested changes now.


Compile error when using gcc 5.4.0 with the portable layer in C99 mode

Hello,
Using gcc 5.4.0 in C99 mode does not work.
Here is is the compile issue:

             from /usr/home/user/git/src/test/test.c:2:

/usr/include/flatcc/portable/paligned_alloc.h:81:23: fatal error: mm_malloc.h: No such file or directory
compilation terminated.
*** Error code 1

I guess you include this file in order to make sure that posix_memalign is defined?
The problem is there is no more mm_malloc.h file shipped with gcc5.
Regards,

This patch fixes the issue:
--- ./include/flatcc/portable/paligned_alloc.h.orig	2017-01-21 09:52:50.000000000 +0100
+++ ./include/flatcc/portable/paligned_alloc.h	2017-03-29 19:00:59.724040000 +0200
@@ -77,7 +77,7 @@
#elif PORTABLE_POSIX_MEMALIGN
-#ifdef GNUC
+#if GNUC < 5
#include "mm_malloc.h"
#endif

Does this mean posix_memalign is available without including mm_malloc.h?

The change has been committed. Travis is chewing along on older gcc's now in ci-more branch and seems happy so far, but that is without C99.
https://travis-ci.org/dvidelabs/flatcc/builds/216462272

I'm closing this, but feel free to reopen if something is still broken.

It works fine, thanks for your support!

Note: I justed update paligned_alloc.h again to handle C++, but it should not have any impact on C.


jobsub_version in templates should use the version variable

Instead it's forever pinned to 1.0.
https://github.com/marcmengel/jobsub_lite/blob/eeb7477b10cfb3072f86d1c3f634a5a4a251e879/lib/utils.py#L119

And just a reminder (we probably need a comment too), that the version NEEDS to start with "lite" for jobview to work. It doesn't look at the version number, but I could see that being used in the future if we need to change something about how the logs are handled. So we probably want to lock down a format for that attribute.
Oh and the title isn't quite right (or at least misleading), since we've got an underscore in jobsub_version while __version__ has a dot. But there's no reason we couldn't stick a dot in jobsub_version that I can think of. Heck we could even put a space in it: lite v1.0.

Noted.

Just to record what @shreyb and I discussed, we think {__title__}-{__version__} is the way to go to get the constants out of the code. I'll change jobview to check if the version string contains "lite" instead of a prefix match, hopefully that's pretty future-proof.

Code written, but I want to run a couple of quick tests before opening a PR.

Ran the following tests:

$ ~/jobsub_lite/bin/jobsub_submit --version
jobsub_lite version 1.1.1
$ ~/jobsub_lite/bin/jobsub_submit --support-email
Email<EMAIL_ADDRESS>for help.
$ ~/jobsub_lite/bin/jobsub_q --version
jobsub_lite version 1.1.1
$ ~/jobsub_lite/bin/jobsub_q --support-email
Email<EMAIL_ADDRESS>for help.
$ ~/jobsub_lite/bin/jobsub_fetchlog --version
jobsub_lite version 1.1.1
$ ~/jobsub_lite/bin/jobsub_fetchlog --support-email
Email<EMAIL_ADDRESS>for help.
jobsub_submit, but don't actually submit job.  Inspect .cmd file to make sure we get the right version:
~/jobsub_lite/bin/jobsub_submit -G fermilab -n file:///usr/bin/sleep 300

In .cmd file:
+JobsubServerVersion="jobsub_lite-v1.1.1"
+JobsubClientVersion="jobsub_lite-v1.1.1"

PASS


Create pull_request_template.md

Codecov Report

Merging #60 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #60   +/-   ##
=======================================
  Coverage   96.15%   96.15%
=======================================
  Files           8        8
  Lines         519      519
=======================================
  Hits          499      499
  Misses         20       20

Flag
Coverage Δ

#unittests
96.15% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Forcing jax float64 mode

This is not really good practice, users can have legitimate reasons for not using float64 and if they import s2fft first, it will force the type without leaving them a choice:
https://github.com/astro-informatics/s2fft/blob/e9e6f78c685d2dd54f6344e29a35de65c09fb350/s2fft/transforms/spherical.py#L3
If you think float64 is really important for this library, you could instead send a warning back if the users have not enabled it.

The problem really starts to become apparent inside the recursions. With 64bit precision, at high L the error can grow from 1e-16 to around 1e-13 or so. With 32bit precision, without accounting for any other factors, this should correspond to an error from around 1e-6 to 1e-3 to even 1e-2, which isn't great.
I think a warning would be a good option around this though, but we will have to be clear that 64bit can be really quite important in this case. This hard coding of 64bit precision comes up throughout several functions, perhaps we should just include a warning at the high-level?

Yep, I'm proposing a solution in #145 Maybe the warning can be evn more ominous ^^

Closing as this was addressed in #145


Fix security vulnerabilities

KissMyResume needs manual update of some libraries, see https://github.com/karlitos/KissMyResume/network/alert/package-lock.json/minimist/open
and
https://github.com/karlitos/KissMyResume/network/alert/package-lock.json/lodash.merge/open

Fixed in 78f584e


Please default the config of the credential locations for Runtime Config to the generic config location

If i specify spring.cloud.gcp.config.credentials.location=${spring.cloud.gcp.credentials.location} in my bootstrap.properties then it works correctly. for most (all?) of the other services the autoconfig draws the config location from the generic credentials location.

Do you mean that Runtime Config doesn't work for you unless you set spring.cloud.gcp.config.credentials.location in bootstrap.properties?

I think I see the error. The autoconfig for Runtime Config is basically all in GoogleConfigPropertySourceLocator.
The constructor for that class expects a credential provider that if , but in our implementation right now in GcpConfigBootstrapConfiguration the constructor for GoogleConfigPropertySourceLocator is given a new DefaultCredentialsProvider(configProperties) instead.
Then these lines in the constructor
			this.credentials = gcpConfigProperties.getCredentials().hasKey()
					? new DefaultCredentialsProvider(gcpConfigProperties).getCredentials()
					: credentialsProvider.getCredentials();

are choosing from the same 2 options, which is causing the problem.

See https://github.com/spring-cloud/spring-cloud-gcp/pull/368#issue-166207389 for a discussion of the differences between bootstrap context an autoconfigure and why they should not be mixed.
It might be OK to add @EnableConfigurationProperties(GcpProperties.class) to GcpConfigBootstrapConfiguration and resolve this issue that way, but I'm not sure if it will mix properly with the regular autoconfigure context.

Works as intended.


Project structure changed but refresh shows old structure

VSCode Version: 1.5.2
OS Version: Windows 7 (build 7601: sp1)

Steps to Reproduce:

Used Angular CLI to generate new component but did it in subfolder.
VSCode shows the new folder automatically.
From explorer deleted new folder and all generated files.
Generated new component again this time in correct folder
VSCode still shows old file structure. Click refresh does not reload new structure. Click files will prompt file does not exist, would you like to create it.

I think the file changes on disk should be updated when clicking refresh button in VSCode.

@Lythix are you seeing a warning about .NET 4.5. being required for file watching? I suspect the file watcher is not running.

No, not seeing any warnings like that.
I did notice later that I was running Ng serve so it's possible the files were locked?

Please see if you can find any logged output that could help us find the source of the issue:

run code --verbose from the command line and attach the output
in Code select Help | Toggle Developer Tools and select the Console
attach any output you see in the Console you can find

Thanks!

A number of days has past without answer on the questions asked. I am thereby going to close this issue to clean up our backlog of issues. Once you can answer on the questions, the issue can be reopened again. Thanks for understanding this process!


Cluster Template Creation

Admin creates the template using almost the same UI as “Add Cluster”.
After filling out all the details/settings, he sees an option to save the current cluster as a template.
UI Vs YAML
We are talking about 100+ settings. We cannot offer these as UI options. Probably YAML will be a better way to present these options to the users (we ship default YAML so that the users don’t have to create one from scratch)

Tested with master build.
Cluster template and template creation through API is functional.
Basic use case cases for template revision creation by providing different cluster config parameters through API were successful.

Tested using master-head build from July 9th.
Created a cluster template and template revision using UI successfully


How to Manually invoke the DSDL compiler ?

Manually invoke the DSDL compiler and add the output directory to the project includes

See https://uavcan.org/Implementations/Libuavcan/Tutorials/8._Custom_data_types and https://github.com/UAVCAN/libuavcan/blob/master/libuavcan/dsdl_compiler/libuavcan_dsdlc. Run libuavcan_dsdlc with --help to get the usage info.

i will try, thx :)


Reduce STM_domain retries

While commenting on #129 I realized the STM_domain retries count is relatively high at 15.
When combined with a rep_count:25 for Util.repeat it means we end up repeating a property 15*25=375 times during shrinking for each shrinking candidate that fails!
In comparison Lin_domain uses retries:3 and rep_count:50 meaning it repeats a property 150 times during shrinking.
This PR therefore reduces retries to 10, thus lowering shrink repetitions to 250 to avoid burning needless CPU cycles.
I have checked locally that all existing negative STM tests still fail with a nice and short counterexample.
For, e.g., the bytecode CI target I'm expecting/hoping this will reduce the runtime a bit.

Counterexamples are still minimal (with occasional outliers as previously), so I'll merge.


Agregué palabras "de Javascript" y comillas dobles

Agregué las palabras "de Javascript" al inicio de la introducción  y la palabra "approchable" entre comillas ya que es una palabra en inglés.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


Action styles for confirm/settings and cancel are flipped

It looks like the action styles for the confirm and settings actions are flipped with the cancel action based on Apple's convention. Making a minor PR that fixes this.

Relevant: http://www.openradar.me/radar?id=5490788398006272

@delba Is it possible to merge the fix to this at #83 soon? 😄

Fixed by #83

Hey @delba, is it possible to increment the release number to v2.0.2 so that these changes are incorporated for Carthage?

Hey @jakerockland, I just released v2.0.2 .
Thanks for reminding me ;)

No prob, thank you @delba ! 😄


[Snyk] Upgrade graphql-request from 4.2.0 to 4.3.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade graphql-request from 4.2.0 to 4.3.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 3 versions ahead of your current version.
The recommended version was released a year ago, on 2022-05-30.

Release notes

Package name: graphql-request

4.3.0 - 2022-05-30

4.3.0-next.2 - 2022-05-26

4.3.0-next.1 - 2022-04-25

4.2.0 - 2022-03-23

    from graphql-request GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

👷 Deploy Preview for enchanting-melba-222e50 processing.

Name
Link

🔨 Latest commit
ffbf18d62facd00284fd7da6a469dc37684f52a7

🔍 Latest deploy log
https://app.netlify.com/sites/enchanting-melba-222e50/deploys/655ff0ac2a8ad500085906c3


How to select subsets of indoor and outdoor in subpopulation experiment

Hi,
Thanks for contributing the great project!
I have a question regarding how you selected the subsets belonging to indoor and outdoor.  While we can find corresponding subset name specified by attributes like "dog(white)" in attributes-candidate-subsets.pkl, it looks like you specified the indoor and outdoor manually in this file.
I was wondering how you generate train_set_scheme and test_set_scheme. What if we want to select cat & dog with other contexts in GENERAL_CONTEXT_ONTOLOGY, e.g., cat(bedroom)? I also noticed there is a file obj2attribute.json. Could you please provide some instructions on how to utilize it?
Thanks,
Ting

Hi, thank you for your interest in our work.
As mentioned in the paper, the subsets are selected based on the node community detection results on the meta-graph.

Section 4.1: Evaluating domain generalization
To make our evaluation settings more challenging, we merge similar subsets by running Louvain community detection algorithm (Blondel et al., 2008) on each meta-graph. Node color in Figure 2 indicates the community detection result.

In the code, the print_communities function provides the node community detection results. In practice, the community detection results tend to capture fine-grained communities. For example, although both cat(computer) and cat(sink) are indoor, they are assigned to two different communities as indicated by their node color. Therefore, for contexts that are more abstract (e.g., indoor or outdoor), you may need to manually group multiple communities together.


feat: modules communicate at runtime via hooks

Until https://github.com/customerio/customerio-android/pull/67 is merged, this will give you the changes only in this PR.
Highlights of PR

Create new module common-test that contains code that all modules use in their test code. I created this module because I created tests for messagingpush module and there were some utilities in the tracking module I wanted to use.
Refactored the dependency injection graph so that there is now 1 graph instance per site-id (to keep dependencies/resources sandboxed) and make each site-id graph a singleton so they stay in memory after CustomerIO instance may be garbage collected in the app.
Implement "hooks" so that SDK modules can talk to each other at runtime. Example: The messagingpush module can directly call tracking module code because it has the tracking module as a dependency. To avoid circular dependencies and allow customers to choose to not install the messagingpush module if they choose not to, the tracking module cannot list the messagingpush as a dependency. "hooks" is a way to allow the various SDK modules to communicate at runtime and avoid these issues.
Create doc on hooks. Hope it can help you while reviewing this PR to understand it better.
Modified the constructor of CustomerIO class to allow customers to use a non-singleton API of the SDK. This was an effort of mine to begin making progress towards this ticket and also because I had to make a refactor to the CustomerIOComponent dependency injection graph to not garbage collect the graph when there is a possibility of background queue tasks running.
Created a doc to help teach new developers of the project about the various modules of the project as the number of modules continues to grow.

Complete each step to get your pull request merged in. Learn more about the workflow this project uses.

[ ] merge https://github.com/customerio/customerio-android/pull/67
[x] Assign members of your team to review the pull request.
[x] Wait for pull request status checks to complete. If there are problems, fix them until you see that all status checks are passing.
[ ] Wait until the pull request has been reviewed and approved by a teammate
[ ] After pull request is approved, and you determine it's ready add the label "Ready to merge" to the pull request and it will automatically be merged.

Pull request title looks good 👍. If this pull request gets merged, it will cause a new release of the software.
Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.1.0.
To merge this pull request, add the label Ready to merge to this pull request and I'll merge it for you.

PR is blocked until I make some refactors to remove "Modified the constructor of CustomerIO class to allow customers to use a non-singleton API of the SDK. This was an effort of mine to begin making progress towards this ticket

PR no longer blocked. It's ready for review.


[kong] optionally expose prometheus metrics

What this PR does / why we need it:
Allows the metrics endpoint to be optionally exposed as a Kubernetes service.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the next branch and targets next, not master
[x] New or modified sections of values.yaml are documented in the README.md
[x] Title of the PR and commit headers start with chart name (e.g. [kong])

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

ping @yasn77 as this is relevant to your interests.

Awesome, thanks @glitchcrab
@hbagdi @rainest Would be great if we can get this merged...
Many thanks guys!

Can someone explain the motivation for this addition?

Yeah, we've realised that this won't work as we wanted it to - we'll just use podAnnotations to apply Prometheus annotations directly at a pod level. I'll close this off.


Refactored default.qubit for more speed

Description of the Change: Removed expand method from default.qubit. Both gate applications and expectations now use tensordot under the hood
Benefits: apparent 25x speed-up over current code
Possible Drawbacks:
Related GitHub Issues:

didn't add to the autosummary since it's an internal method anyway


Mail being marked open even on viewing sent mail

What operating system are you using?
MacOS Sierra
What version of Nylas Mail are you using?
1.0.29
Bug?
Is the issue related to a specific email provider (Gmail, Exchange, etc.)?
Not sure, as I use only Gmail
Mails being marked opened (under the name of recipient), even when I open the sent mail.

Thanks for the report! We're looking into it


Check observers for filtering null and undefined

It has to be checked, if every observer of repo-specific observables the underlying datastore (for example getViewModelObservable, getViewModelListObservable, getViewModelListBehaviorSubject, ...) filters incoming values, if they are not null and not undefined.
If values, which are null or undefined, will be filtered by the observers, the functions in the base-repository can be adjusted to do so.

Some thoughts:

There should never be undefined in the observables. You might get undefined, when subscribing to an observable which does not yet has valid data. IMO this cannot be prevented.
null can be published, meaning that this model was deleted. This behavior can be suppressed if the message of this object being deleted is not relevant.

Regarding deleted objects: I think currently everywhere where a single model is requested , the deleted-event is not needed. What would be nice is to inform the user about a deletion. E.g. the user is on the topic detail page and the topic gets deleted. Force-navigation is bad, but there could be a generic message, that this topic was deleted.

@luisa-beerboom do we need this cleanup? Are there any open ToDos regarding observables after Gabriels rework?
If not, feel free to close this issue.

I don't know how relevant the original description is, but Finns point regarding deleted objects does still hold up I think. We should probably keep this issue around for now


pip install minedojo to conda environment fails

We run multi-user Ubuntu 20.04 systems. Downgrading openjdk on the entire system seems imprudent, and docker has security issues, so this leaves setting up a Conda environment.  So I created a bare miniconda environment with python 3.12.2, and tried running pip install minedojo.
(base) root@finglas:~# conda activate minedojo
(minedojo) root@finglas:~# python --version
Python 3.12.2
(minedojo) root@finglas:~# pip install minedojo
Collecting minedojo
  Downloading minedojo-0.1-py3-none-any.whl.metadata (17 kB)
Collecting pyyaml (from minedojo)
  Downloading PyYAML-6.0.1-cp312-cp312-manylinux_2_17_x86_64.                    manylinux2014_x86_64.whl.metadata (2.1 kB)
Collecting jinja2 (from minedojo)
  Downloading Jinja2-3.1.3-py3-none-any.whl.metadata (3.3 kB)
Collecting gym==0.21.0 (from minedojo)
  Downloading gym-0.21.0.tar.gz (1.5 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.5/1.5 MB 34.3 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [1 lines of output]
      error in gym setup command: 'extras_require' must be a dictionary whose    values are strings or lists of strings containing valid project/version requirement  specifiers.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem     with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Solution for Issue #3176
To resolve the issue, run the following command:
pip install setuptools==65.5.0 "wheel<0.40.0"

This installation strategy addresses the compatibility issues discussed in GitHub Issue #3176 and aligns with the insights provided on Stack Overflow.

Unfortunately, that didn't work either.  I'm building the conda environment with python 3.12.2 -- maybe I need to use an older version of python?  In any case, after running pip install setuptools==65.5.0 "wheel<0.40.0":
(minedojo) root@finglas:~# pip install minedojo
Collecting minedojo
  Using cached minedojo-0.1-py3-none-any.whl.metadata (17 kB)
Collecting pyyaml (from minedojo)
  Using cached PyYAML-6.0.1-cp312-cp312-manylinux_2_17_x86_64.                   manylinux2014_x86_64.whl.metadata (2.1 kB)
Collecting jinja2 (from minedojo)
  Using cached Jinja2-3.1.3-py3-none-any.whl.metadata (3.3 kB)
Collecting gym==0.21.0 (from minedojo)
  Using cached gym-0.21.0.tar.gz (1.5 MB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [11 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 14, in <module>
        File "/lusr/opt/miniconda/envs/minedojo/lib/python3.12/site-packages/    setuptools/__init__.py", line 16, in <module>
          import setuptools.version
        File "/lusr/opt/miniconda/envs/minedojo/lib/python3.12/site-packages/    setuptools/version.py", line 1, in <module>
          import pkg_resources
        File "/lusr/opt/miniconda/envs/minedojo/lib/python3.12/site-packages/    pkg_resources/__init__.py", line 2191, in <module>
          register_finder(pkgutil.ImpImporter, find_on_path)
                          ^^^^^^^^^^^^^^^^^^^
      AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you   mean: 'zipimporter'?
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem     with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Yeah I would recommend that you use python 3.9.x, THEN try the
pip install setuptools==65.5.0 "wheel<0.40.0"
Let me know if the issue still persists, I haven't tried it using python 3.12

Woohoo! That worked.  Python=3.9.19.  Thanks for your help with this.


[Request] automatically create and updated logs as the script run

create and updated a text file logs while the script is running (in case of something unexpected happened especially in GDPR mode) the user can continued where they left off (maybe max last 100 entries or something user can specific)

duplicate of #49


Updated CI provider names in the Readme

Improved capitalisation and added links - hope this one is OK too!

Perfect, thanks @keithpitt :+1:


Update the How to Use section in the README file based on the latest version

Thanks, Sajad for your commit


An application that interacts between bmcweb and bios manager

This application takes care of hypervisor network configuration
by communicating with the bios-settings-mgr in the backend.
It hosts xyz.openbmc_project.Network.Hypervisor.service similar
to that of network service and implements system config, ethernet
and ip interfaces whose properties are mapped to the appropriate
properties in the base bios table.
The flow will be like:

User fires the redfish command to update hypervisor
network configuration properties
BMCWeb updates the properties in the dbus object
hosted by this application
This application would update these new values in
the base bios table

upstream for this https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-networkd/+/43173


pasing the oidc_authorization_uri to the front end

Phil, if this change does not interfere with your work, please merge it.


KOGITO-4282 DMN codegen dead code elimination

Ref: https://issues.redhat.com/browse/KOGITO-4282
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

Thanks for the PR, I forgot to remove that class 👍

Thanks for the PR, I forgot to remove that class 👍

@danielezonca * interface =P

@danielezonca * interface =P


method-update returns badly formatted keys

I've been experimenting with simpl-schema + autoform v.6 and a form with method-update will return keys with the question mark formatting from the schema in place.
This didn't use to be the case. Is this a bug or do I need to change something in my code?
{
  "_id": "wa25aF7P5xMuibu3C",
  "modifier": {
    "$set": {
      "companyPrefs.$.companyName": "abcdefg",
      "companyPrefs.$.emailBaseFQDN": [
        "abcdefg"
      ]
    }
  }
} undefined

Here's the corresponding schema
const prefs = new simplschema({
    "companyPrefs": Object,
    "companyPrefs.$.companyName": String,
    "companyPrefs.$.emailBaseFQDN": Array,
    "companyPrefs.$.emailBaseFQDN.$": String,
})

As far as a can see in the docs your schema should be:
const prefs = new simplschema({
    companyPrefs: Object,
    "companyPrefs.companyName": String,
    "companyPrefs.emailBaseFQDN": Array,
    "companyPrefs.emailBaseFQDN.$": String,
})

Thanks, that helps!
Now I'm getting Match error: Unknown key in field $set
Previously the autoform-method returned an object (that passed check() and clean()) like this:
 { '$set':
    {
      'companyPrefs.companyName': 'abc',
      'companyPrefs.emailBaseFQDN': [ 'xyz.com' ],
      'apiKeys.googleMapsAPI': '123456',
     }
 }

With autoform v.6 and the new node simpl-schema it it comes with extra _id and 'modifier' keys
{ _id: '3SRKjSxmnnkJ6wMsp',
  modifier:
   { '$set':
      { 'companyPrefs.companyName': 'abc',
        'companyPrefs.emailBaseFQDN': [ 'xyz.com' ],
        'apiKeys.googleMapsAPI': '123456',
        }
} }

So in my method I've tried running checkand clean on doc.modifier:
            let mod = doc.modifier
            check(mod, schemas.prefs)
            schemas.prefs.clean(mod, {
                extendAutoValueContext: {
                    isInsert: false,
                    isUpdate: true,
                    isUpsert: false,
                    isFromTrustedCode: false
                }
            })

but it baulks at Unknown key in field $set

Yeah, I think I changed it to pass as a single object by default in order to work with mdg:validated-method. The default used to be two separate args. But you should only have to use doc.modifier

It would be nice to have in the Note about version 6 that the parameter of the method have change.
before it was methodName: function (modifier, _id) {} now it's a single object methodName: function ({ modifier: _id }){}.
for the error, I'm not sure but I think that node-simple-schema is didn't work with check function like before :/


[TASK]: Add code user blocks to the code to model operator

Describe the task
Per design a user is able to add one or more code block to the code to model operator. Those code blocks will now be used to help create a new model. But the user created code blocks are not part of the Code asset used as input of the operator.
To enable this features, one solution needs to be selected to move forward:

When a user add a new code block to the operator state, the Code asset used as input is updated with a new file named code_to_model-[Timestamp].[language file extension] and containing the code block code. This means the code block needs to be selected as an ouput of the Code asset operator. But needs to be unchecked (as in include in process checkbox) for other outputs state by default.
Update the code_to_amr operations of the knowledge-middleware worker to stop using the data-service itself and receive code information directly.

Task Items

[ ] Decide which path to go forward: Edit Code asset used as input, or update knowledge-middleware.
[ ] Add the functionality to add user created code block to the operator state.

create model from code is currently deprecated


Add locked FH TA class

I needed TA in this app for my solo scenario, so I figured I may as well push upstream.
I only needed the ability cards, but I poked around in the webui and nothing seems broken.
If you need me to fix something, just comment and I'll fix it.

Thanks a lot for your PR !
Merging this asap. Will release it on the master branch soon :)


[BUG] upgrade hung on apply-manifests

Describe the bug

When upgrading from v1.1.2 -> v1.1.3-rc1 -> v1.2.1 the upgrade hangs on hvst-upgrade-qn7lt-apply-manifests forever and it doesn't time out. This was on the second part of the upgrade, v1.1.3-rc1 -> v1.2.1.
To Reproduce
Steps to reproduce the behavior:

Deploy 2 node v1.1.2 cluster
Do pre-upgrade tasks
upgrade to v1.1.3-rc1
Add new node to cluster
Upgrade to v1.2.1

Expected behavior

The upgrade should complete
Support bundle

support_bundle_apply_manfiests.zip
Environment

Harvester ISO version: v1.1.2 -> v1.1.3-rc1 -> v1.2.1
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): 3 node DL160 bare metal

Additional context
Add any other context about the problem here.
Longhorn volumes all look good.
On further inspection it looks like it thinks it's hung on deleting the cattle-monitoring-system logs.
[hvst-upgrade-qn7lt-apply-manifests-jl2sv] there are still 9 pods in cattle-monitoring-system to be deleted
However we deleted all of those logs in Rancher and it still was hung although the number of pods changed in the logs so it does look like it updated. Also the cordoned node is still labeled as schedulable. It looks like the apply-manifests job is hung.
You'll see two in the list, but the other one is from the previous upgrade.
hvst-upgrade-qn7lt-upgradelog-archive-2023-12-08T19-15-47Z.zip

kubectl get jobs -n harvester-system -l harvesterhci.io/upgradeComponent=manifest
NAME                                 COMPLETIONS   DURATION   AGE
hvst-upgrade-ndd42-apply-manifests   1/1           7m58s      44h
hvst-upgrade-qn7lt-apply-manifests   0/1           18h        18h

@w13915984028 Can you take a look, seems related: https://docs.harvesterhci.io/v1.2/upgrade/v1-1-2-to-v1-2-0#6-an-upgrade-is-stuck-in-the-upgrading-system-service-state

Sometimes, forcely deleting the POD may still not fix this issue, instead, we need to remove their parent objects:

POD  <- StatefulSet/Deployment/Daemonset <- Customized Prometheus/Alertmanager
<- ... finally ManagedChart

unfortunately, ManagedChart is removed but the final PODs are left, and those in-between object may also exist, if they are, deleting the POD has no effect, as they will be re-deployed.
root resources in cattle-monitoring-system

Customized CRD: Prometheus  object: rancher-monitoring-prometheus
   sub-object: statefulset.apps/prometheus-rancher-monitoring-prometheus

Customized  CRD: Alertmanager object:  rancher-monitoring-alertmanager
  Sub-object:  statefulset.apps/alertmanager-rancher-monitoring-alertmanager

Deployment:
rancher-monitoring-grafana
rancher-monitoring-kube-state-metrics
rancher-monitoring-operator
rancher-monitoring-prometheus-adapter

Daemonset:
rancher-monitoring-prometheus-node-exporter

use below commands to delete them:

kubectl delete prometheus rancher-monitoring-prometheus -n cattle-monitoring-system
kubectl delete alertmanager rancher-monitoring-alertmanager -n cattle-monitoring-system

kubectl delete deployment rancher-monitoring-grafana -n cattle-monitoring-system
kubectl delete deployment rancher-monitoring-kube-state-metrics -n cattle-monitoring-system
kubectl delete deployment rancher-monitoring-operator -n cattle-monitoring-system
kubectl delete deployment rancher-monitoring-prometheus-adapter -n cattle-monitoring-system

kubectl delete daemonset rancher-monitoring-prometheus-node-exporter -n cattle-monitoring-system

The workaroud in the document will also be updated.

@noahgildersleeve Would you mind close this ticket? The document was updated.

Closing as fixed since there was the doc update.