ColorPickerActionButtons: dialogActionButtons are not showing up in the bottom

Hello,
i have the following code and want to display the dialogActionButtons in the bottom of the dialog. Unfortunately, they will not appear.

showDialog(
        context: context,
        builder: (BuildContext context) {
          return SizedBox(
              width: double.infinity,
              child: LayoutBuilder(builder: (context, constraint) {
                return Padding(
                    padding: const EdgeInsets.all(5.0),
                    child: SingleChildScrollView(
                      child: Card(
                        elevation: 2,
                        child: ColorPicker(
                          color: primaryColor!,
                          onColorChanged: (Color color) {
                             setState(() {
                                    primaryColor = color;
                                  })
                          },
                          width: constraint.smallest.shortestSide * 0.1,
                          height: constraint.smallest.shortestSide * 0.1,
                          actionButtons: const ColorPickerActionButtons(
                            okButton: false,
                            closeButton: false,
                            dialogActionButtons: true,
                          ),
                          pickersEnabled: <ColorPickerType, bool>{
                            ColorPickerType.both: true,
                            ColorPickerType.accent: false,
                            ColorPickerType.primary: false,
                          },
                        ),
                      ),
                    );
              )}));
        }
);

Hi @bettyballin, without seeing a bit more of the use case it is difficult the say for 100% sure what the issue is. However, based on the included code, it looks to me like you are using the ColorPicker Widget in your own custom dialog.
It is of course a perfectly fine use case, to use your own custom dialog design. However, FlexColorPicker and its properties cannot control or show bottom buttons in a dialog (AlertDialog) that is not a dialog it creates and controls itself.
If you want to use your own dialog you will have to make your own dialog buttons and correct actions on them as a part of your own custom dialog.
In the FlexColorPicker config class ColorPickerActionButtons the okButton and closeButton are indeed controlling a part of the ColorPicker Widget's title content. So they will actually show up in a custom dialog too, although I have not actually tested how/if they work when used with a custom dialog, but to be honest they were not intended to be used in custom dialog design either. The reason being that if you are making your own dialog design, your probably want to make your own title and any top actions buttons as well.
In the config class ColorPickerActionButtons , the dialogActionButtons is controlling the visibility of action buttons when you use the ColorPicker:s built-in dialog. Thus this setting will not have any impact at all in your custom dialog, since you are not using the part of FlexColorPicker package at all where it is used and has an impact.
For more info on the built-in ways of using the ColorPicker with its pre-made dialogs, please see the tutorial here:
https://pub.dev/packages/flex_color_picker#dialog-colorpicker-method or here https://pub.dev/packages/flex_color_picker#dialog-colorpicker-function
If you just want to quickly select and pick a color, the latter one is easier to use. If you also want to interactively change colors (like theme colors etc) in the running app, while the dialog is open and operated, then you need to use the first a bit more complex variant.
As mentioned though, you can totally make and build your own dialog, you just can't use features related to built-in dialogs when doing so. Of course nothing prevents you from re-using some of the properties in FlexColorPicker and its config classes, to control availability and visibility of same features in your own custom dialog(s), but you will have to code in that behavior then.
The built-in dialog in FlexColorPicker does offer quite a lot of configuration options, so in most/many cases you might not need to make a custom dialog. In case you did not try that already, you might want to test it too.
In addition to the tutorial the live web demo and its package bundled code also offers more insights into usage and configuration options of the ColorPicker.
Hope this explanation helps! 😃

Closing this question since there has not been any follow-up question or activity since the above answer. If you feel that answer is not sufficient, fell free to open a new follow-up question.


App seems to crash when Template Deleted

Following steps to reproduce:

Create Trip and add template
Delete Template
Try to edit the pack, it seems to be gone.

Or at least I think so, hard to tell. This makes the need for the logs in #59 so much more important

This seems to be an iOS 14 bug

Ok this bug was NOTHING like I thought it was.
The onDisappear for EditCategory was going crazy, firing constantly, driving memory and CPU usage up, and causing a crash. I moved the onDisappear next to the onAppear, so hopefully that will fix it.


DSA

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: beef9999:x: hhb584520You have signed the CLA already but the status is still pending? Let us recheck it.


Local Npm module "less-plugin-autoprefix" not found. Is it installed?

I always get this error.
I've installed using: npm install less-plugin-autoprefix --save-dev
Any suggestions?

sorry, looks to me like npm didn't install or something went wrong..
what gives the local Npm module not found message?

Found that removing the grunt.loadNpmTasks('less-plugin-autoprefix'); resolved this issue.


Add service supervisord start somewhere in production install process

Apparently on at least some systems this isn't started automatically when installed via apt.

We fixed this a while ago.


Types for getQueryData is unknown

Describe the bug
I got unknown type when type in known
  const {} = useQuery({
    queryKey: ["cart_quantity"],
    queryFn: async () => {
      if (user) {
        const cart_quantity = await supabaseClient
          .from("users_cart")
          .select("cart_quantity")
          .eq("id", user?.id)
        return cart_quantity as ICartQuantityResponse
      }
      return null
    },
  })

I know that type here is ICartQuantityResponse
When I want to get queryData I got unknown type

Your minimal, reproducible example
codesandbox doesn't work (no way to open in vs code - infinity loading - no way to delete some file - it do nothing)
Steps to reproduce

make query request
getQueryData
got unknown type of query data

Expected behavior
I wait that I give me type for query data but I got unknown
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
"next": "13.5.3",
"@tanstack/react-query": "^5.0.0",
"@tanstack/react-query-devtools": "^5.0.1",
Tanstack Query adapter
react-query
TanStack Query version
^5.0.0
TypeScript version
5.2.2
Additional context
No response

this has always been the expected behaviour. React Query cannot know what lives under a certain queryKey in the cache, because there is no up-front definition. Instead, queries are defined ad-hoc.

codesandbox doesn't work (no way to open in vs code - infinity loading - no way to delete some file - it do nothing)

next time, use typescript playground.
what you can do is pass a generic to queryClient.getQueryData, as shown in this typescript playground

what's new in v5 is that you can define your query object with the queryOptions helper, and re-use the key from that. Those keys are "tagged" with the return type from the queryFn, so we can actually know the expected type. Have a look at this playground.

all of this is documented here:

https://tanstack.com/query/v5/docs/react/typescript#typing-query-options

because there is no up-front definition
What do you mean by 'up-front definition'?

A I got you what you mean - I mean this

I want press ctrl+alt+enter and got TypeScript intellisense of all my queries - also you may store info in provider (its something I wrap all my project in layout.tsx)
(for exampe under node_modules generate types for intellisense)
In supabase I know exist that thing (but you need to do it manually because its server related - no way to refresh it when DB changes)
So I don't want to continue this conversation - please ignore this (if you want - you can improve this)

What do you mean by 'up-front definition'?

It's clear to me now that you don't understand how react-query works and why we can't have "autocomplete" on queryClient.getQueryData.
In things like supabase or graphql, you have one big definition (the database or the graph): one place where everything is defined. That's where auto-complete comes from.
In react-query, no such thing exists. I can have a button that does:
<button onClick={() => queryClient.setQueryData(['foo'], 'bar)

after I click the button ['foo'] is a query in the cache.
before that, it isn't.
So when you do queryClient.getQueryData(I WANT AUTO COMPLETE HERE), there is no way that we can show you ['foo']`.
tools like trpc or zodios that build on top of react query can do this because again, they have an "up front" definition: one place that exists at compile time, before your code runs, where every possible key is defined (in trpc, its the router), that typescript can look at and infer types from.

also you may store info in provider

for that to work, you would need to provide information about all queries to the QueryClient at the point where you define the QueryClient, not only about what the possible keys are, but also about what the types are.


Add more stats to statsd

This should be split up into two PRs: adding the new metric type and the new logging.

We should probably move dongle id from a tag to a field.  Then it doesn't contribute to series cardinality and I expect using it as a secondary filter will still be fast.  The trade-off is poor performance grouping by it at the top level, which I am inclined to say is not useful.

We should probably move dongle id from a tag to a field. Then it doesn't contribute to series cardinality and I expect using it as a secondary filter will still be fast. The trade-off is poor performance grouping by it at the top level, which I am inclined to say is not useful.

Sounds reasonable, will make a PR


CAMEL-21098: prevent incorrectly trying to reuse the same NamespacedHierarchicalStore

/component-test ftp sftp

/component-test camel-ftp

Our GH actions are down ...
But I tested this .... I promise. Let's merge. 🤞


Handle silverlight framework identifiers comparison

simpler approach than https://github.com/fsprojects/Paket/pull/1127

Deleting the branch as the module has been rewritten in the mean time


Updated README

Description
I have:

updated the README file with a few useful links
added Code Style section to CONTRIBUTING file
bumped some dependencies to their newest possible versions.
removed selfish information about how I started this project from the README file :)

Fixes #19
Flutter Channel:

[x] I have used the Flutter Beta channel on my local machine

Type of Change:

Code
Documentation

How Has This Been Tested?
Ran locally on my Android emulator (Pixel 3a API 29). Everything works fine.
Checklist:

[x] My PR follows the style guidelines of this project
[x] I have performed a self-review of my own code or materials
[ ] I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Code/Quality Assurance Only

[x] My changes generate no new warnings

Looks like this can fix #19 , can you do the changes mentioned there too? So that we can close it too

@Techno-Disaster sure, will check this soon. I just copied them from some other PR so that's probably why they're broken.

🤦♂


Cant specify system prompt

Like the prompt format but submitted once at the beginning of the conversation

Hi. You can read about system prompt here.


Update object-roles.md: removed a repeated word

Word "listed" was repeated twice by mistake

@Tanya-Solyanik : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Why are there not dbn and rbm in tensorflow model zoo?

Can anyone add them to tensorflow to make it better?

@jmchen-g @nealwu for model zoo. Model zoos tend to be applied examples, for instance image recognition network training on a corpus such as MNIST, rather than a network building block, like an RNN cell.
RBMs can be implemented in contrib. Effectively we have DBNs if you care to stack layers.

If there are models you would like to see in https://github.com/tensorflow/models, feel free to submit a pull request for them.


How to cancel a task in AFURLSessionManager

I download a file by downloadTaskWithRequest，and I want to cancel it.
How can I do?

@shuijinliuxi If you use AFURLSessionManager, method should be "downloadTaskWithRequest" return NSURLSessionDownloadTask, please read Apple documentation about this class. That can be cancel, resume, suspend :)


Investigate DAG idempotency

Context

In a recent conversation about unplanned EC2 instance restarts and how they might affect our infrastructure, we began discussing how our current DAGs might handle a random dropout. Here's that conversation for posterity:
From @sarayourfriend:

The main one that comes to mind is Airflow. The big question (from Sara) is what the risks of an Airflow instance fully shutting down at a random time are. For example, what happens if a data refresh is shut down in the middle. Does the data refresh DAG tracking the progress and state of the indexer workers/ingestion server in such a way that it can pick it back up if it's restarted in the middle? What about the staging database refresh? That DAG mostly uses AWS operators to implement the full cycle. Is it safe if interrupted? How about other DAGs that interact with infrastructure pieces like the catalog DB snapshot DAG. Does the batched update DAG, if cancelled in the middle of an update task, track that fact and able to recover? Maybe we need to make sure that batched update update queries are written in an idempotent way. Existing ones may be (we should audit and confirm to be certain), but if it could be an issue then we should add some kind of safeguard to ensure it (e.g., transaction handling if we're not already doing that, some kind of ability for the DAG to know exactly what part of the update task it failed at, where it's safe to automatically recover and where might need manual intervention, etc). Multiply this line of questioning by all critical DAGs. Most should be okay, by the nature of how Airflow is designed to work, but any long-running individual tasks may be problematic if they do not persist state outside of RAM.

From @aetherunbound:

Does the data refresh DAG tracking the progress and state of the indexer workers/ingestion server in such a way that it can pick it back up if it's restarted in the middle?

Currently, no. Usually the easiest way to address this is just to start the refresh process over again. This will certainly change once the ingestion server removal project is complete. With that, we should be able to restart an individual step that failed, rather than the entire refresh.

What about the staging database refresh?

You're right that most of this DAG uses AWS Operators to perform the steps required. The DAG is supposed to be able to recover on failure, but that recovery can't happen if the orchestrator itself is down! That said, in this case what would likely happen is that the Task in Airflow would "fail" while the actual operation would succeed. Example: Airflow issues a command to spin up a new database based on a snapshot, and is currently waiting for that snapshot to be live. The EC2 instance is replaced which kills this task. The database still comes up because AWS is still processing the command, the task just failed to finish waiting. In this case we'd want to verify the operation itself had actually completed, then just manually mark the task as succeeded so the rest of the DAG could continue.

Does the batched update DAG, if cancelled in the middle of an update task, track that fact and able to recover?

I believe this exact case has already happened actually, and it should be trivial to restart the DAG from that point in updating the tables.
The Postgres operations may be exactly similar to the AWS ones described above -- with the command issued already, it might complete just fine but the Airflow task itself will show as failed. This one might need some experimentation, but ideally those operations would be idempotent, too, (as you mention) so that we could simply restart them in the case where Airflow goes down.

Description
We should audit our current set of DAGs to make sure their behavior is consistent with what's described above, and that all DAGs (critical or not) would be able to be restarted easily if the worker is terminated during the course of the run.

To clarify, "the worker" (in the final paragraph) means anywhere that is executing DAG-managed tasks, right? So that would include:

the local task executor (i.e., the Airflow server)
Postgres create, update, delete queries. i.e., the query and method of execution of the query (e.g., transations, atomic, etc) for batched update, insertions of new media, etc.

That's about our queries, not whether Postgres does what we tell it to do, but whether what we tell it to do is atomic, idempotent, fail-safe, and so forth

the indexer worker logic

(ignoring the ingestion server given it's pending removal)
Is that correct, @AetherUnbound? Is there anywhere that executes custom logic for tasks that I'm missing?
Is the outcome for this issue a comment in this issue followed by issues to address changes needed in certain areas or do further investigation/mini-implementation plans for things of greater complexity that the auditor cannot give a concrete solution for right away?

I have seen this and will respond to this discussion when I have time!


Fix code scanning alert - Inefficient regular expression

Tracking issue for:

[x] https://github.com/RicardoGEsteves/Storyscape/security/code-scanning/3

fixed


swapExactETHForTokens transaction

How can I convert the following transaction to work in a multicall?
var contract = new web3.eth.Contract(routerAbi, routerAddress);
var swapETHforTokens = contract.methods.swapExactETHForTokens(0, [WBNB, tokenAddress], WalletAddress, timeStamp);
var encodedABI = swapETHforTokens.encodeABI();
var swapETHforTokensTX = {
from: WalletAddress,
to: routerAddress,
gas: 176024,
data: encodedABI,
value: web3.utils.toWei(ETHtoSell, 'ether'),
};
No problem calling it with eth.call:
await web3.eth
.call(swapETHforTokenstx, 'pending')
.then((result) => {
console.log(web3.eth.abi.decodeLog([{ 'internalType': 'uint256[]', 'name': 'amounts', 'type': 'uint256[]' }], result).amounts[1]);
})
.catch((revertReason) => console.log(revertReason));

The problem is in the contract, which does not make it possible to do what is requested. To make this type of request it is necessary to modify the contract:
function aggregate(Call[] memory calls) public returns (uint256 blockNumber, bytes[] memory returnData) {
        blockNumber = block.number;
        returnData = new bytes[](calls.length);
        bytes memory ris = hex"00";
        for(uint256 i = 0; i < calls.length; i++) {
            (bool success, bytes memory ret) = calls[i].target.call{value: calls[i].ethtosell, gas: calls[i].gastouse}(calls[i].callData);
            if (!success){
                ret = ris;
            }
            returnData[i] = ret;
        }
    }

It is also necessary to add some features to the contract, namely the ability to receive BNB (to pay the fees).
receive() external payable{}
Now it is possible to fulfill the request:
import Web3 from 'web3';
var web3 = new Web3('speedy node...');

const routerAbi = [];
const multicallAbi = [];
var MAINTOKEN = 'main token address (WETH, WBNB ...)';
var tokenAddress = '...';
var multicallAddress = '...';
var timeStamp = web3.utils.toHex(Math.round(Date.now() / 1000) + 60 * 20);
var maxgas = 2000000;

var routerContract = new web3.eth.Contract(routerAbi, routerAddress);
var multicallContract = new web3.eth.Contract(multicallAbi, multicallAddress);

var swapETHforTokens = routerContract.methods.swapExactETHForTokens(0, [MAINTOKEN, tokenAddress], multicallAddress, timeStamp);
var encodedABI = swapETHforTokens.encodeABI();

var MAINTOKENtoSell =<PHONE_NUMBER>00000;
var result = await multicallContract.methods
   .aggregate([{ target: routerAddress, callData: encodedABI, ethtosell: MAINTOKENtoSell, gastouse: maxgas }])
   .call()
   .catch((err) => console.log(err));
console.log(result);

@malvaphe - is it possible to use multicall to call swapExactETHForTokens without actually paying gas and swapping the tokens?
I'm looking to use multicall to test on chain whether I can swapExactETHForTokens successfully and swap it back before actually submitting the transactions.
I know websites like https://honeypot.is/ do this on chain, however, I'm wondering if they're using technique such as a multicall.


How to Disable the Scanning Window During Image Acquisition?

I want to disable this UI during the scanning process, but I couldn't find any relevant information in the documentation.
Is there a way to hide this UI?

There is no guarantee this will work, since this is highly dependent on the TWAIN data source, but you can try DTWAIN_EnableIndicator

Thanks for your help, it worked


az login fails

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
az login -t $tenant -u $username -p $password_raw
Get Token request returned http error: 400 and server response: {"error":"invalid_grant","error_description":"AADSTS50126: Error validating credentials due to invalid username or password.\r\nTrace ID: a287413d-c526-4d4a-a6eb-ac9108b03000\r\nCorrelation ID: 7f85270a-1b07-401e-b684-a19533c1b5ea\r\nTimestamp: 2021-06-25 13:16:19Z","error_codes":[50126],"timestamp":"2021-06-25 13:16:19Z","trace_id":"a287413d-c526-4d4a-a6eb-ac9108b03000","correlation_id":"7f85270a-1b07-401e-b684-a19533c1b5ea","error_uri":"https://login.microsoftonline.com/error?code=50126"}
To Reproduce
The username and password is correct. I am not sure why az login complains that it is wrong.
Expected behavior
Able to login
Environment summary
azure-cli                         2.10.0

@jiasli for awareness

@smithago When you provide -u $username this is the Service Principal right? See: az login reference

AADSTS50126: Error validating credentials due to invalid username or password. is returned by AAD service indicating the credential is not correct.

If you are using a user credential, make sure the tenant/username/password combination is correct.
If you are using a service principal, make sure --service-principal is provided.


[stable/minio] Indentation fix for pod label capability

Signed-off-by: Sherief Shahin<EMAIL_ADDRESS>
What this PR does / why we need it:
Fixes the previous pod capability added, by removing extra indentation
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:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @wlan0

/assign @wlan0

/ok-to-test

@nitisht Is it okay to merge now for use in our project? It has been an impediment for us as well as the next commit I am planned to push today after a successful trial of the pod label capability in our project

If possible, I checked the list of helm members and I found that @prydonius can approve my merge as well. We are truly blocked by not having pod label capabilities

Looks good @sshahinco we can merge

/lgtm


ui fixed. dots work.

Hello @evilcloud! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file core.py:

Line 47:5: E731 do not assign a lambda expression, use a def
Line 63:80: E501 line too long (86 > 79 characters)
Line 86:80: E501 line too long (86 > 79 characters)
Line 93:80: E501 line too long (83 > 79 characters)
Line 99:80: E501 line too long (81 > 79 characters)


Undo sets the cursor to the beginning of the document

https://user-images.githubusercontent.com/44893228/210773697-c867e1ed-88b4-4a3d-892d-1698a1526fcc.mp4

The first undo record is pushed in the CodeHistoryController constructor. It has the selection collapsed at -1. When changed and undone, that first undo record is applied, and the selection of -1 is somehow converted to 0 which is the beginning of the document.
The quick fix
Find and fix that -1 -> 0 conversion. This would also need a test.
The proper fix
Keep the selection at the edit point when the first edit is undone. Some ideas for this:

When creating an undo record, check if the only record below is the initial one. If so, replace it with another one with the selection as it was before the edit.
When selection changes, always create an undo record. Replace the older top record if it is different from the pre-top only in the selection.

Tests for this:

Go to location A, edit, undo. Expect being at A.


POC on VS Code w remote containers

What: Remote containers allow us to streamline our dev environments and performance
Why: Because it might be easier and cheaper then buying new machines all the time

[ ] View & discuss @ https://docker.events.cube365.net/dockercon-live/2021/content/Videos/f9kJRuGDj8w6ayTh7
[ ] Test & demo

Its hard for us to get new hardware, maybe its cheaper to use remote containers on cloud computers?

No active plans for pursuing, will create new issue once relevant again.


Gradient fill

Does the LineChart component support gradient fill color via config? Thanks.

Not supported yet. PR's are welcome though :)

Would love this feature as well!

I'm willing to take a stab at this, but I am very new to React and React Native.  Can you point me in the right direction in terms of resources, etc?

Hey @Jpadilla1 !
Very nice lib thank you very much. I'm joining the others to say that a support for Gradient fill LineChart would be awesome.
I am also new to React Native. Would love to help but I'm not sure how ...


Argument List Too Long - RISC-V AR

When building the Cordio library for the RISC-V on MAX32690, the AR command fails with an "Argument List too Long" error.  It looks like this was resolved in gcc.mk by using an ar_args.txt for the arguments.  This should be ported over to the RISC-V makefile as well.

Thanks @BrentK-ADI, looks like I fixed this issue when I synced up this GCC makefiles with each other in https://github.com/Analog-Devices-MSDK/msdk/pull/653
The release SDK doesn't have these changes yet, the development repo should fix this issue.  I'll close this out when we push the release in case anyone else hits it.

Closing alongside the Oct 2023 release:  https://github.com/Analog-Devices-MSDK/msdk/releases/tag/v2023_10


Consider making builds generated by :init use same versions as embedded for Groovy and Kotlin dependencies

for consistency.
Expected Behavior
gradle init --type=groovy-application

would generate a build that depends on Groovy using the same version as the embedded Groovy version.
In the same way,
gradle init --type=kotlin-application

would generate a build that depends on Kotlin using the same version as the embedded Kotlin version.
Current Behavior
The Groovy and Kotlin versions used by :init are set to "latest available on release branching according to a range" configured in
https://github.com/gradle/gradle/blob/0fa0d95ff7b8510349669c4ecc94572ed16bce32/subprojects/build-init/build-init.gradle.kts#L62-L72
which might be different than the embedded versions.
Context
#7793, #7795 and #7796

What is the reason that we want to use the embedded versions as default for building an application with Groovy/Kotlin? I don't see why someone should bind the version of Groovy/Kotlin in their project to whatever Gradle uses currently.

In the Kotlin case, the currently embedded version happens to be the latest stable Kotlin version so it makes sense.

@wolfs the version we use in :init generated builds isn't the single supported version. One can change the version in their build according to any compatibility issues. This issue isn't suggesting to change that but to change what particular version :init uses when generating the builds and use the same version as embedded Groovy/Kotlin, for consistency and least astonishment. I think it would also makes things simpler for us and prevent situations like #7793.

I don't think we should recommend people use this pattern for anything that isn't intended to run on Gradle itself (plugins and build logic libraries). If the software is not intended to run on Gradle, then by using the local Kotlin or Groovy version people are unnecessarily coupling the version of the language they use in production with the version of the build tool that they use. This is not a good situation for people to be in.
I'm going to close this.


failover fails with "failover cluster has not recovered from last placement action"

configuration:

hub: hub
dr-clusters: cluster1, hub

scenario:

busybox-sample application initially deployed to cluster1 successfully
busybox-sample application failed over to hub unsuccessfully

test "$(kubectl --context hub -n busybox-sample get subscriptions/busybox-sub-local -ojsonpath={.status.phase})" = Subscribed
Error from server (NotFound): subscriptions.apps.open-cluster-management.io "busybox-sub-local" not found

logs:
ramen-hub-log.txt
ramen-dr-cluster-hub-log.txt
ramen-dr-cluster-cluster1-log.txt
resources:
busybox-placement.txt
busybox-drpc.txt
busybox-vrg-hub.txt
busybox-vrg-cluster1.txt

So I looked at it and I see that something is not ligned up right.  It is possible that at some point, there were two instances of the DRPC.  I can't explain how that could have have happened, but the logs agree with what I said:
2021-09-28T22:31:48.976Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol_controller.go:541    VRGs location   {"VRGs": {"cluster1":....
2021-09-28T22:31:48.977Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol.go:57    Process DRPC Placement  {"DRAction": ""}
2021-09-28T22:31:48.977Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol.go:89    Running initial deployment
2021-09-28T22:31:48.977Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol.go:89    Using homeCluster cluster1 for initial deployment, uPlRule Decision [{cluster1 cluster1}]
2021-09-28T22:31:48.977Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol.go:155   isAlreadyDeployedAndProtected? - map[cluster1:0xc0004dc200]
2021-09-28T22:31:48.977Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol.go:113   Already deployed on homeCluster cluster1. Last state: Deployed
2021-09-28T22:31:48.977Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol_controller.go:561    Completed processing placement  {"requeue": false}
2021-09-28T22:31:48.978Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol_controller.go:554    Finished processing {"Requeue?": false}
2021-09-28T22:31:48.978Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol_controller.go:554    Done reconciling
2021-09-28T22:31:48.978Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol_controller.go:554    Requeue time    {"duration": "9m47.021779343s"}
2021-09-28T22:31:48.978Z    INFO    controllers.DRPlacementControl  controller/controller.go:298    Exiting reconcile loop  {"DRPC": "busybox-sample/busybox-drpc"}
2021-09-28T22:32:02.437Z    INFO    MCV predicate/predicate.go:87   Update event for MCV busybox-drpc-busybox-sample-vrg-mcv/hub
2021-09-28T22:32:02.437Z    INFO    controllers/drplacementcontrol_controller.go:439    Filtering MCV (busybox-drpc-busybox-sample-vrg-mcv/hub)
2021-09-28T22:32:02.437Z    INFO    controllers/drplacementcontrol_controller.go:439    Filtering MCV (busybox-drpc-busybox-sample-vrg-mcv/hub)
2021-09-28T22:32:02.437Z    INFO    controllers.DRPlacementControl  controller/controller.go:298    Entering reconcile loop {"DRPC": "busybox-sample/busybox-drpc"}
2021-09-28T22:32:02.449Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol_controller.go:507    Validating schedule from DRPolicy
2021-09-28T22:32:02.449Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol_controller.go:715    Getting User PlacementRule  {"placement": {"kind":"PlacementRule","name":"busybox-placement"}}
2021-09-28T22:32:02.449Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol_controller.go:527    Preferred cluster is configured. Dynamic selection is disabled  {"PreferredCluster": "cluster1"}
2021-09-28T22:32:02.449Z    INFO    MCV controllers/drplacementcontrol_controller.go:208    MCV condtions: [{Processing True 0 2021-09-28 22:31:49 +0000 UTC GetResourceProcessing Watching resources successfully}]    {"resouceName": "busybox-drpc"}
2021-09-28T22:32:02.450Z    INFO    MCV controllers/drplacementcontrol_controller.go:208    MCV condtions: [{Processing True 0 2021-09-28 22:32:02 +0000 UTC GetResourceProcessing Watching resources successfully}]    {"resouceName": "busybox-drpc"}
2021-09-28T22:32:02.450Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol_controller.go:541    VRGs location   {"VRGs": {"cluster1":.... "hub":....
2021-09-28T22:32:02.450Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol_controller.go:561    Starting to process placement
2021-09-28T22:32:02.450Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol.go:57    Process DRPC Placement  {"DRAction": ""}
2021-09-28T22:32:02.450Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol.go:89    Running initial deployment
2021-09-28T22:32:02.450Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol.go:89    Using homeCluster cluster1 for initial deployment, uPlRule Decision [{cluster1 cluster1}]
2021-09-28T22:32:02.450Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol.go:155   isAlreadyDeployedAndProtected? - map[cluster1:0xc0008f8000 hub:0xc0008f8200]
2021-09-28T22:32:02.451Z    INFO    controllers.DRPlacementControl  controllers/drplacementcontrol.go:113   Already deployed on homeCluster cluster1. Last state: Deployed

I edited the log to remove the noise, but as clearly shows, the first time we queried for all VRGs, only the one in cluster1 showed up.  Then nothing really happened, and then we queried again, and we got two VRGs {cluster1 and hub}.
Talked to @hatfieldbrian and he thinks the theory might hold some truthfulness.  He will try to reproduce it while keeping an eye and see if everything has been cleaned up before redeploying.

Again I confirmed the ramen-system and busybox-sample namespaces were absent before deploying ramen and busybox sample application.  Shortly after busybox sample application was initially deployed successfully to cluster1, I noticed two vrgs that were created in the same second:
$ kubectl --context cluster1 -nbusybox-sample get vrg/busybox-drpc -ojsonpath='{.metadata.creationTimestamp}'
2021-09-30T21:56:40Z
$ kubectl --context hub -nbusybox-sample get vrg/busybox-drpc -ojsonpath='{.metadata.creationTimestamp}'
2021-09-30T21:56:40Z

But the manifestworks that cause their creation have very different ages:
$ kubectl --context hub -ncluster1 get manifestworks/busybox-drpc-busybox-sample-vrg-mw -ojsonpath='{.metadata.creationTimestamp}'
2021-09-30T21:56:40Z
$ kubectl --context hub -nhub get manifestworks/busybox-drpc-busybox-sample-vrg-mw -ojsonpath='{.metadata.creationTimestamp}'
2021-09-29T22:44:42Z

Somehow the hub's vrg manifestwork was not deleted...  About the same time as that manifestwork was created, a failover from cluster1 to hub was performed as documented in issue #302

Here is the stale manifestwork:
$ kubectl --context hub -nhub get manifestworks busybox-drpc-busybox-sample-vrg-mw -oyaml
apiVersion: work.open-cluster-management.io/v1
kind: ManifestWork
metadata:
  annotations:
    drplacementcontrol.ramendr.openshift.io/drpc-name: busybox-drpc
    drplacementcontrol.ramendr.openshift.io/drpc-namespace: busybox-sample
  creationTimestamp: "2021-09-29T22:44:42Z"
  finalizers:
  - cluster.open-cluster-management.io/manifest-work-cleanup
  generation: 2
  labels:
    app: VRG
  name: busybox-drpc-busybox-sample-vrg-mw
  namespace: hub
  resourceVersion: "7166124"
  uid: 5a168e24-3ae8-46b0-84cb-d5b469ea3604
spec:
  workload:
    manifests:
    - apiVersion: ramendr.openshift.io/v1alpha1
      kind: VolumeReplicationGroup
      metadata:
        name: busybox-drpc
        namespace: busybox-sample
      spec:
        pvcSelector:
          matchLabels:
            appname: busybox
        replicationClassSelector: {}
        replicationState: secondary
        s3ProfileName:
        - minio-on-cluster1
        schedulingInterval: 1m
      status:
        lastUpdateTime: null
status:
  conditions:
  - lastTransitionTime: "2021-09-30T21:56:40Z"
    message: Apply manifest work complete
    observedGeneration: 2
    reason: AppliedManifestWorkComplete
    status: "True"
    type: Applied
  - lastTransitionTime: "2021-09-30T21:56:40Z"
    message: All resources are available
    observedGeneration: 2
    reason: ResourcesAvailable
    status: "True"
    type: Available
  resourceStatus:
    manifests:
    - conditions:
      - lastTransitionTime: "2021-09-30T21:56:40Z"
        message: Apply manifest complete
        reason: AppliedManifestComplete
        status: "True"
        type: Applied
      - lastTransitionTime: "2021-09-30T21:56:40Z"
        message: Resource is available
        reason: ResourceAvailable
        status: "True"
        type: Available
      resourceMeta:
        group: ramendr.openshift.io
        kind: VolumeReplicationGroup
        name: busybox-drpc
        namespace: busybox-sample
        ordinal: 0
        resource: volumereplicationgroups
        version: v1alpha1

Yes, that will do it.  And in theory, that's exactly what should have happened. IOW, if the MW stayed around in the hub, then you will end up with 2 VRGs, one going to the preferredCluster (cluster1) and another one going to the hub cluster because the hub's MW is still alive.  Because of that, the MW will keep trying to recreate the VRG until it succeeds or is deleted.
You might ask the question; why is the creation time for the two VRGs the same?  Well, it is a perfect coincidence. The two MWs are completely independent of each other. The perfect creation time for the two VRGs was helped by the creation of the busyboxy-samples namespace. The MW on the hub has been trying to recreate the VRG since the namespace was deleted, but kept failing and failing until the namespace was recreated. How do I know that; well, that's the behavior of a MW.
So, that worked as expected, but the question now is; why didn't the MW in the hub get deleted when the DRPC was deleted?  The answer to that question will be found in the DRPC log if you have it.

Closing since failover is working reliably now.


added fibonacci search #issue 4317

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # <4317>

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[X] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[X] DSA
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[X] I follow Contributing Guidelines & Code of conduct of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@aisharay Closing the PR since your format is incorrect. If you wish to still work on this issue, feel free to create a new corrected PR before 30 Nov, which points to GWOC DSA Branch from your fork's DSA branch.


401 on every attempt

Unfortunately I can't get this to work. I tried with various API keys and domains but none seem to work. Any ideas?

Do you have the correct region? This problem can occur if your Mailgun is set to the EU zone but your API isn't.

I'm not sure, because I didn't really know what to set the region to. Is there any documentation that you can point me to perhaps?

Yes, that fixed it!  Perhaps you could put your snippet in the readme of the repo instead of the current YOUR_REGION? To me that was unclear anyway. I can make a PR if you want

I've updated the README.md :)


xFirewall Can't Detect Rules Created via the GUI (Windows 2012/WMF4)

I'm running Windows 2012 (non R2) with WMF4. We have manually created some firewall rules using the GUI, and are now trying to detect and monitor these rules using DSC. When created with the GUI, the resources get a Name that is a GUID, and a DisplayName of whatever you intended the name to be. All the -NetFirewallRule checks in the xFirewall resource use -Name, so it is unable to detect the rule properly. A possible fix would be to have -NetFirewallRule check for either Name or DisplayName matches.
Output:
Here's what happens when I try to Test-TargetResource:
PS C:\Program Files\WindowsPowerShell\Modules\xNetworking\DSCResources\MSFT_xFirewall> $parms
Name                           Value

Action                         Allow
Ensure                         Present
Profile                        Domain
Description                    Allow Trend for Exchange2013
LocalPort                      {80, 443, 5168, 16372...}
Name                           TrendFirewallPortsforExchange2013 (TCP-IN)
Direction                      Inbound
Protocol                       Tcp
DisplayName                    TrendFirewallPortsforExchange2013 (TCP-IN)
PS C:\Program Files\WindowsPowerShell\Modules\xNetworking\DSCResources\MSFT_xFirewall> Import-Module .\MSFT_xFirewall.psm1
PS C:\Program Files\WindowsPowerShell\Modules\xNetworking\DSCResources\MSFT_xFirewall> Test-TargetResource @parms -Verbose
VERBOSE: Test-TargetResource: Checking settings for firewall rule with Name 'TrendFirewallPortsforExchange2013 (TCP-IN)'.
VERBOSE: Test-TargetResource: Find firewall rule with Name 'TrendFirewallPortsforExchange2013 (TCP-IN)'.
VERBOSE: Get-FirewallRule: No Firewall Rule found with Name 'TrendFirewallPortsforExchange2013 (TCP-IN)'.
VERBOSE: Test-TargetResource: Firewall rule with Name 'TrendFirewallPortsforExchange2013 (TCP-IN)' does not exist.
VERBOSE: Test-TargetResource: Check Firewall rule with Name 'TrendFirewallPortsforExchange2013 (TCP-IN)' returning False.
False
Here's the resource props:
[DBG]: PS C:\Program Files\WindowsPowerShell\Modules\xNetworking\DSCResources\MSFT_xFirewall>> Get-NetFirewallRule | where {$_.DisplayName -like "Trend"} | fl
Name                  : {615DCE6C-32DD-49B0-B81E-808BA37473DC}
DisplayName           : TrendFirewallPortsforExchange2013 (TCP-IN)
Description           : Allow Trend for Exchange2013
DisplayGroup          :
Group                 :
Enabled               : True
Profile               : Domain
Platform              : {}
Direction             : Inbound
Action                : Allow
EdgeTraversalPolicy   : Block
LooseSourceMapping    : False
LocalOnlyMapping      : False
Owner                 :
PrimaryStatus         : OK
Status                : The rule was parsed successfully from the store. (65536)
EnforcementStatus     : NotApplicable
PolicyStoreSource     : PersistentStore
PolicyStoreSourceType : Local
Here's a pic of the GUI:

I think this issue is the same as this recently closed (but not resolved) issue: https://github.com/PowerShell/xNetworking/issues/75
I did post a possible way we could work around this (in #75), but we never actually implemented it.
@tysonjhayes - any thoughts on this?


fixes #4070

We do not want the slice B to be updated two times per action.
See https://github.com/reduxjs/redux/issues/4070
Thanks for the PR!
To better assist you, please select the type of PR you want to create.
Click the "Preview" tab above, and click on the link for the PR type:

:memo: Documentation Fix

Will follow the proper template to create this PR.


Inline datepicker

It would be nice to have the possibility to display just the calendar inline, without a previous input.

Yes,
I'm working on it.

Is the datepicker editable? when I add date with keyboard is not working. please help me

+1 I also need to show a date picker without an input box. Is it possible to do it with the current version?


the transaction that copy from another one can't be updated its Own account

the transactions that copy from another one can't be updated its Own account

After saving, the editing transactions that were supposed to alter my own account did not take effect. I'm uncertain if the issue lies with my actions.

I am unable to replicate my issue at https://demo.firefly-iii.org/login; however, I have discovered additional matters. The temporal aspect of transactions appears to undergo alterations, and transactions vanish upon preservation. I surmise that these occurrences bear a connection to my predicament. Are these phenomena considered ordinary?
https://github.com/dreautall/waterfly-iii/assets/72897835/4517b965-9397-44f1-bc6e-6de34c603721


🧹api test refactoring

[x] replace ClassFixture with CollectionFixture for TestApp
[ ] fix error messages when docker build

Task two will be fixed in a new PR


Front Admin - other language

Context :
currently the administration application is set in english, we might want to use other language, like french.
To Analyze :
how to create a language switch so where to save translations data

duplicated ticket : #1346


Hovering over anything doesn't show the hud utility

When you spawn a gate, for an exemple then you put your crosshair over it you get a small window saying what that gate is, what its operation looks like or for e2 it might be the OPS and if its running or not, this changes based on what you are looking at.
CONTEXT ;
This is what it would look like normally ;
https://preview.redd.it/2aovccsowjx41.png?width=393&format=png&auto=webp&s=5295ce3c5a8b2374e2e7bf7d8fa74d673ad9e043
I could only find what it normally looks like online
OS Info ;

Gmod info ;
Branch is x64_86 chromium
Launch options are "-vulkan -mat_softwaretl -gl_enablesamplerobjects -swapcores -threads 4 -console -x 2080 -y 0 -command fps_max 90"
I used cefcodecfix
I tested this both with and without any addons
To remake it ;
-Simply place down a gate or an e2 a lever, ect...
-Look at it
If all conditions are met the bug looks like this ;

I forgot to detail the compability option for gmod info which is Steam Linux Runtime has im not sure if it does the same on proton!

Is cl_drawworldtooltips convar set to 1?

it wasn't thanks for finding the command!


LocalFileDetector - PhantomJs 2.0 GhostDriver Windows8

PHP CALL
 $file_input = $this->driver->findElement(WebDriverBy::xpath(".//*[@id='uploader']/form/input[3]"));
    $file_input->setFileDetector(new LocalFileDetector);
    $file_input->sendKeys($image);

ERROR
PHP Fatal error:  Uncaught exception 'WebDriverException' with message 'JSON decoding of remote response failed.
Error code: 4
The response: 'Error - incompatible type of argument(s) in call to _uploadFile(); candidates were
_uploadFile(QString,QStringList)'
' in /var/www/craiglist/php/v3/lib/remote/HttpCommandExecutor.php:241
Stack trace:
#0 /var/www/craiglist/php/v3/lib/remote/RemoteWebDriver.php(491): HttpCommandExecutor->execute(Object(WebDriverCommand))
#1 /var/www/craiglist/php/v3/lib/remote/RemoteExecuteMethod.php(36): RemoteWebDriver->execute('uploadFile', Array)
#2 /var/www/craiglist/php/v3/lib/remote/RemoteWebElement.php(338): RemoteExecuteMethod->execute('uploadFile', Array)
#3 /var/www/craiglist/php/v3/lib/remote/RemoteWebElement.php(299): RemoteWebElement->upload('/var/www/craigl...')
#4 /var/www/craiglist/php/v3/includes/classes/clposter_basic.class.php(478): RemoteWebElement->sendKeys('/var/www/craigl...')
#5 /var/www/craiglist/php/v3/includes/classes/clposter_basic.class.php(487): clposter_basic->uploadImag in /var/www/craiglist/php/v3/lib/remote/HttpCommandExecutor.php on line 241

I get the same error when trying to attach file using the Codeception framework (with PhantomJS running as GhostDriver).
Anyone have idea how to work around this?

You need to remove 'multiple' from input tag to make it work
e.g
<input type="file" name="img" multiple>
Following is how i manage to remove using php
$this->driver->executeScript("document.getElementsByName('file')[0].removeAttribute('multiple')", array());

<input name="MultipleUploadForm[file]" id="MultipleUploadForm_file" type="file">
There's no "multiple" in the input tag of the upload field I'm struggling with. Having said that, it does accept multiple files to be uploaded when doing it manually. I suppose it's still the same issue, yet I can't bypass it by removing the 'multiple' from the input tag.
Any ideas?

same for me, Codecpetion 2.1.2, PhantomJS 2.0.0

I looked into this a fair bit.
Short: Use the UselessFileDetector. Make sure your files are available on the machine where PhantomJS is running.
Longer: As mentioned on SO, this does not happen when running with the PhantomJS driver directly. That's because Ghost Driver PR#324 implemented the uploadFile command incorrectly. Instead of taking a zipped file in the  file parameter as the Selenium server does, it's expecting two parameters: selector and filepath.
What does uploadFile do? The Remote WebDriver must assume that PhantomJS is on another machine. Therefore, it needs not only to send the path of the file to the browser (PhantomJS), but also the file itself. The latter is what uploadFile does.
The workaround is to not try to upload the file in the first place, but just send the path.
For Python this means setting the _is_remote attribute:
is_remote = webdriver._is_remote
webdriver._is_remote = False
webdriver.find_element_by_css_selector('input').send_keys(filepath)
webdriver._is_remote = is_remote

Looking at Facebooks PHP version of the remote driver, the decision of whether or not to use uploadFile hinges on the $this->fileDetector. This means for the duration of sendKeys you need to switch to the UselessFileDetector, which is the default. To be sure:
$file_input = $this->driver->findElement(WebDriverBy::xpath(".//*[@id='uploader']/form/input[3]"));
$file_input->setFileDetector(new UselessFileDetector);
$file_input->sendKeys($image);

If your PhantomJS actually runs on a different machine, regardless of which remote driver you use you need to make sure that the files are actually available on the remote server on the path that you are sending.


Add ability to generate Cargo.lock with minimal versions

It seems that this is currently not possible. That would be useful for debugging things like that: https://github.com/rust-lang/cargo/issues/11765

I think it is okay to provide the ability to preserve the generated lock file, but as said in #18, providing the ability to just generate a lock file is problematic.

BTW, if there is no existing Cargo.lock, the cargo-minimal-versions already works that way.


pandas pyarrow-backed strings display differently to other strings

Prework

[x] Read and agree to the code of conduct and contributing guidelines.
[x] If there is already a relevant issue, whether open or closed, comment on the existing thread instead of posting a new issue.

Description
if I run
from great_tables import GT
import pandas as pd

df = pd.DataFrame(
    {
        "example": ["Row " + str(x) for x in range(1, 5)],
        "numbers": [
            "20 23 6 7 37 23 21 4 7 16",
            "2.3 6.8 9.2 2.42 3.5 12.1 5.3 3.6 7.2 3.74",
            "-12 -5 6 3.7 0 8 -7.4",
            "2 0 15 7 8 10 1 24 17 13 6",i
        ],
    }
)
GT(df)

and then
GT(df.convert_dtypes(dtype_backend='pyarrow'))

then they display differently

For Polars, the alignment is different still?

Reproducible example

[ ] Post a minimal reproducible example (MRE) so the maintainer can troubleshoot the problems you identify. A reproducible example is:

[ ] Runnable: post enough code and data so any onlooker can create the error on their own computer.
[ ] Minimal: reduce runtime wherever possible and remove complicated details that are irrelevant to the issue at hand.
[ ] Readable: format your code according to the Style Guide for Python Code.

Expected result
I think they should look the same?
Development environment

Operating System: linux
great_tables Version: 0.11.0

Additional context
Add any other context about the problem here.

Shoot -- this issue comes from our very old and rough code for handling alignment:
https://github.com/posit-dev/great-tables/blob/079dc836f7e198b6879a0f99a624ea5da271fdfa/great_tables/_gt_data.py#L308
Currently, it uses the string names of dtypes, which is a bit brittle (def an area where narwhals can help ;). We should move this code into out DataFrame backend layer, _tbl_data.py, and clean up the detection of dtypes.


iOS 15.2 has broken safe area insets under some conditions

See https://twitter.com/LeoNatan/status/1458388991666016257
This is an Apple bug, and FB9750551 has been opened:

iOS 15.2: SwiftUI.PlatformViewHost incorrectly calculates safe area insets for itself and its view hierarchy
Please provide a descriptive title for your feedback:
iOS 15.2: SwiftUI.PlatformViewHost incorrectly calculates safe area insets for itself and its view hierarchy
Which area are you seeing an issue with?
SwiftUI Framework
What type of feedback are you reporting?
Incorrect/Unexpected Behavior
Please describe the issue and what steps we can take to reproduce it:
On iOS 15.2, SwiftUI.PlatformViewHost incorrectly calculates safe area insets for itself and its view hierarchy.
I have attached an example project which reproduces the issue. In the example project, I add a UIHostingController, which has additionalSafeAreaInsets set to non-zero value. Further down the hierarchy, I have a UIViewRepresentable, which gets wrapped in a PlatformViewHost. The result is that the view in UIViewRepresentable gets an incorrect safeAreaInsets value.
This is a regression in iOS 15.2.
See screenshots from iOS 15.0 and iOS 15.2, where the issue is clear.

Fixed in beta 3.


[tryceratops]: Too Many Try Statements

Merge after #3109 because this closes: #2056

I'm conflicted on this one. I see the intent of what the rule is trying to do, but even in the example, I'm not certain the fixed version is better:
def main_function():
    try:
        receipt_note = receipt_service.create(order_id)
        broker.emit_receipt_note(receipt_note)
    except ReceiptNoteCreationFailed:
        logger.exception("log")
        raise
    except NoteEmissionFailed:
        logger.exception("another log")
        raise

Since it's now unclear which statement is expected to throw which exception. I ran this over Zulip too and it hit some cases where it wouldn't make sense to refactor in this way (e.g., a function with a for loop that handles an exception in body, followed by another exception handler way down after the loop). In general, I actually think handling exceptions in the narrowest scope possible is good.
What do you think?

I think the bigger issue is if we have two separate blocks catching a ValueError.

Im gonna go ahead and close this.

I have a strong preference for the opposite of what TRY101 promotes -- specifically addressed by Pylint W0717 (unfortunately using the same name as this proposed rule 🙃).  Is there any ongoing work to implement Pylint W0717 in ruff?  If not I may take a stab at it

Seems like we could rename the pylint check to too-many-statements-inside-try to differentiate the two.


ARM support for Reachability

Reachability.swift - Will it support ARM processor architecture?

It's an iOS framework... It's all ARM.


Add Bootlint 0.16.6. and update deps

Needs the files on the origin, including the /latest/ endpoint.

@jmervine it seems the files aren't uploaded yet? Don't forget the /latest/ endpoint too.

@XhmikosR Uploaded. Restarting CI now. Might need to clear the cache for latest to succeed.


Adds more methods

Adds angle to Point.
Example: MG::Point.new(5,5).angle
Adds start_location to TouchEvent
Example on_touch_end { |event| puts event.start_location, event.location.
event.start_location contains the coordinate where the touch startet.
event.location contains the coordinate where the touch ended.
Can be used for SwipeGesture.

Thanks


an index.html file

just trying this out lol

@all-contributors please add ruth-chirwa for code, content

i didnt see this sooner, thanks for the add


Add remediations page

OAMG-9902
Added page for remediations.
Table with available remediation with some metadata and link to them, introduced in this PR.
Additional filtering for leapp remediations playbooks will be needed (another task).

[x] PR has a short description
[x] Tests for the changes have been added

Codecov Report
Attention: 13 lines in your changes are missing coverage. Please review.

Comparison is base (09407bf) 63.70% compared to head (36e7a80) 65.18%.

Files
Patch %
Lines

.../Components/RemediationsPage/RemediationsTable.tsx
76.19%
10 Missing :warning:

...c/Components/RemediationsPage/RemediationsPage.tsx
75.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #183      +/-   ##
==========================================
+ Coverage   63.70%   65.18%   +1.47%
==========================================
  Files          14       16       +2
  Lines         416      471      +55
  Branches      102      111       +9
==========================================
+ Hits          265      307      +42
- Misses        150      163      +13
  Partials        1        1

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


QF-247-Update .Net 6 and Acceptance Test

Closing this pull request for now. There looks to be a bigger problem here between the NServiceBus unit of work and SQL plus Entity framework.
It seems the upgrade to .Net 6 plus Entity Framework packages conflicts with the transactional nature of the unit of work and so nothing can be saved or retrieved from the database. Testing the release in AT in a stand alone nature seems to respond to API calls correctly. However during the regression ran it seems to cause issues.
https://sfa-gov-uk.visualstudio.com/Digital Apprenticeship Service/_releaseProgress?_a=release-environment-extension&releaseId=82813&environmentId=399535&extensionId=ms.vss-test-web.test-result-in-release-environment-editor-tab&runId=3040582&resultId=100009&paneView=debug
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.ValidateConnectionForExecute(SqlCommand command)    at Microsoft.Data.SqlClient.SqlInternalTransaction.Rollback()    at Microsoft.Data.SqlClient.SqlTransaction.Dispose(Boolean disposing)    at SFA.DAS.NServiceBus.SqlServer.Features.ClientOutbox.Data.SqlClientOutboxTransaction.Dispose()    at SFA.DAS.UnitOfWork.NServiceBus.Features.ClientOutbox.Managers.UnitOfWorkManager.EndAsync(Exception ex)    at SFA.DAS.ApprenticeCommitments.Infrastructure.Mediator.UnitOfWorkPipelineBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) in /azp/agent/_work/1/s/src/SFA.DAS.ApprenticeCommitments/Infrastructure/Mediator/UnitOfWorkPipelineBehavior.cs:line 38    at SFA.DAS.ApprenticeCommitments.Infrastructure.Mediator.LoggingPipelineBehavior2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate1 next) in /azp/agent/_work/1/s/src/SFA.DAS.ApprenticeCommitments/Infrastructure/Me


scp file copy problem

Hi,
When i try remote-sync file is uploaded, but files is empty on destination location.  Please help.
[ansible@server Direct]$ ls -l total 0 -rw-rw-r--. 1 ansible ansible 0 May 28 09:54 info
[ansible@server Direct]$ cat info

{

"logger": {
"title": "Remote Sync"
},
"uploadOnSave": true,
"useAtomicWrites": false,
"deleteLocal": false,
"hostname": "<IP_ADDRESS>",
"port": "22",
"target": "/home/ansible",
"ignore": [
".remote-sync.json",
".git/**"
],
"username": "ansible",
"password": "ansible",
"watch": [],
"transport": "scp"
}
Thank you.

Sorry.  Package work good.
I need first save all changes in Atom.


Add env var for 2D memcpy through SDMA

Default path uses 2D Memcpy kernel

Closing this since https://github.com/ROCm-Developer-Tools/HIP/pull/947 should help when SDMA path doesn't work.


Added opening multiple instances, and reopening if crashes

Added opening multiple instances because Helium doesn't have a tab system, reopening because you're screwed if an app crashes inside of Lockdown.

Great, thanks!


Encrypt endpoint not found

Describe the bug
Trying to publish data from the publisher I'm getting this error using the new node
GatewayError: Gateway error: Error: Http error with code 404: Request POST https://node.mumbai.public.nevermined.network/api/v1/gateway/services/encrypt fail - {"statusCode":404,"message":"Cannot POST /api/v1/gateway/services/encrypt","error":"Not Found"}
Was working before in the previous gateway address https://gateway.mumbai.public.nevermined.network
To Reproduce
Steps to reproduce the behavior:
1.
2.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

It's now working, maybe the node was down.


[INSTALL]: install ESMF 8.6.1 and MAPL 2.46.2 in spack-stack 1.6.0

Package name
ESMF and MAPL
Package version/tag
ESMF/8.6.1 and MAPL/2.46.2
Build options
Current
Installation timeframe
The two libraries will be installed under current spack-stack 1.6.0.
Other information
No response
WCOSS2

[X] Check this box if and only if your package should be installed on WCOSS2 Cactus and Dogwood (all spack-stack packages will be installed on Acorn). If not, you may disregard the rest of the items below and submit this request.

WCOSS2: General questions
No response
WCOSS2: Installation and testing
No response
WCOSS2: Technical & security review list

[ ] The code is mature, stable, and production ready
[ ] The code is does not and cannot use the internet, and does not contain URLs (http, https, ftp, etc.) except in comments
[ ] The package does not contain prebuilt binary files that have not been approved by NCO security review
[ ] The code has no publicly disclosed cybersecurity vulnerabilities and exposures (search https://cve.mitre.org/cve/)
[ ] The code is not prohibited by DHS, DOC, NOAA, or NWS
[ ] The code comes from a trusted source. Trusted sources include other NWS, NOAA, or DOC, agencies, or other Federal agencies that operate at a FISMA high or equivalent level. Additionally, trusted sources could be third-party agencies through which there is an existing SLA on file (such as RedHat).
[ ] The code is actively maintained and supported (it continues to get updates, patches, etc.)
[ ] The code is not maintained by a private entity operating in a foreign country (if it is, make a note below)
[ ] There is sufficient documentation to support maintenance
[ ] There are no known security vulnerabilities or weaknesses
[ ] Installing and running the code does not require privileged processes/users
[ ] There are no software dependencies that are unapproved or have security concerns (if there are, make a note below)
[ ] There are no concerns related to SA, SI, and SC NIST control families

WCOSS2: Additional comments
No response

We need to do https://github.com/JCSDA/spack-stack/issues/1157 first, then this.

#1157 was merged, so we can go ahead with this. Unlikely it will happen before the 4th of July weekend. Many people will be on leave.

Below are the instructions and a list of platforms / assigned spack-stack installers:
Instructions

Go to spack-stack-1.6.0 installation and run the basic steps for building spack-stack environments on this system (see https://spack-stack.readthedocs.io/en/1.6.0/PreConfiguredSites.html)

Make sure git remotes are configured correctly to point to JCSDA for both spack-stack and spack, do a git remote update, git check out jcsda/release/1.6.0 (replace jcsda with origin or however the remote is named); a subsequent git status should show

-bash-4.2$ git status

# On branch release/1.6.0
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#   (commit or discard the untracked or modified content in submodules)
#
#       modified:   spack (new commits, modified content)

git submodule update should check out the correct hash for the spack submodule; if not, go to spack, do a git remote update && git checkout jcsda/release/1.6.0.

Back to the spack-stack top-level directory: source setup.sh

For each unified environment in envs, do (please use a name that works for your setup, may include compiler suffix etc):

spack stack create env --name=ue-esmf-8.6.1-mapl-2.46.2 --site=s4 --template=unified-dev \
    --upstream=/data/prod/jedi/spack-stack/spack-stack-1.6.0/envs/unified-env/install \
    2>&1 | tee log.create.ue-esmf-8.6.1-mapl-<IP_ADDRESS>

Update envs/ue-esmf-8.6.1-mapl-2.46.2/spack.yaml and set the correct compiler in the compiler matrix line (match upstream!) and set correct esmf/mapl versions:

sed -i "s/'%aocc', '%apple-clang', '%gcc', '%intel'/'%intel'/g" envs/ue-esmf-8.6.1-mapl-2.46.2/spack.yaml
sed -i<EMAIL_ADDRESS>^esmf<EMAIL_ADDRESS><EMAIL_ADDRESS>envs/ue-esmf-8.6.1-mapl-2.46.2/spack.yaml
sed -i "s/-<EMAIL_ADDRESS><EMAIL_ADDRESS>envs/ue-esmf-8.6.1-mapl-2.46.2/spack.yaml
spack env activate -p envs/ue-esmf-8.6.1-mapl-2.46.2

Concretize: spack concretize 2>&1 | tee log.concretize.ue-esmf-8.6.1-mapl-<IP_ADDRESS>, check output:

$ cat log.concretize.ue-esmf-8.6.1-mapl-<IP_ADDRESS> | grep -vE '\[+\]|\[e\]|\[\^\]'
==> Concretized<EMAIL_ADDRESS>
==> Concretized<EMAIL_ADDRESS>
==> Concretized ewok-env%intel+cylc+ecflow

==> Concretized fms@release-jcsda%intel

==> Concretized<EMAIL_ADDRESS>
==> Concretized global-workflow-env%intel
 -   lumhmam  global-workflow-env<EMAIL_ADDRESS>build_system=bundle arch=linux-centos7-skylake_avx512
 -   lyeuaa6      ^esmf<EMAIL_ADDRESS>cxxflags="-fp-model precise" fflags="-fp-model precise" ~debug~external-lapack+external-parallelio+mpi+netcdf~pnetcdf~shared~xerces build_system=makefile esmf_comm=auto esmf_os=auto esmf_pio=auto patches=f63d405 snapshot=none arch=linux-centos7-skylake_avx512

==> Concretized gmao-swell-env%intel

==> Concretized gsi-env%intel

==> Concretized jedi-fv3-env%intel

==> Concretized jedi-mpas-env%intel

==> Concretized jedi-neptune-env%intel
 -   dwzunza  jedi-neptune-env<EMAIL_ADDRESS>build_system=bundle arch=linux-centos7-skylake_avx512
 -   lyeuaa6      ^esmf<EMAIL_ADDRESS>cxxflags="-fp-model precise" fflags="-fp-model precise" ~debug~external-lapack+external-parallelio+mpi+netcdf~pnetcdf~shared~xerces build_system=makefile esmf_comm=auto esmf_os=auto esmf_pio=auto patches=f63d405 snapshot=none arch=linux-centos7-skylake_avx512

==> Concretized jedi-ufs-env%intel<EMAIL_ADDRESS><EMAIL_ADDRESS> -   fikj3on  jedi-ufs-env<EMAIL_ADDRESS>build_system=bundle arch=linux-centos7-skylake_avx512
 -   lyeuaa6      ^esmf<EMAIL_ADDRESS>cxxflags="-fp-model precise" fflags="-fp-model precise" ~debug~external-lapack+external-parallelio+mpi+netcdf~pnetcdf~shared~xerces build_system=makefile esmf_comm=auto esmf_os=auto esmf_pio=auto patches=f63d405 snapshot=none arch=linux-centos7-skylake_avx512
 -   7okttfo      ^mapl<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   r2lhznx          ^fargparse<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   gf6rzli          ^gftl<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   h7wqbpx          ^gftl-shared<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512

==> Concretized jedi-um-env%intel

==> Concretized<EMAIL_ADDRESS>
==> Concretized<EMAIL_ADDRESS><EMAIL_ADDRESS> -   7okttfo  mapl<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   lyeuaa6      ^esmf<EMAIL_ADDRESS>cxxflags="-fp-model precise" fflags="-fp-model precise" ~debug~external-lapack+external-parallelio+mpi+netcdf~pnetcdf~shared~xerces build_system=makefile esmf_comm=auto esmf_os=auto esmf_pio=auto patches=f63d405 snapshot=none arch=linux-centos7-skylake_avx512
 -   r2lhznx      ^fargparse<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   gf6rzli      ^gftl<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   h7wqbpx      ^gftl-shared<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512

==> Concretized soca-env%intel

==> Concretized ufs-srw-app-env%intel<EMAIL_ADDRESS><EMAIL_ADDRESS> -   v4cb5fx  ufs-srw-app-env<EMAIL_ADDRESS>build_system=bundle arch=linux-centos7-skylake_avx512
 -   lyeuaa6      ^esmf<EMAIL_ADDRESS>cxxflags="-fp-model precise" fflags="-fp-model precise" ~debug~external-lapack+external-parallelio+mpi+netcdf~pnetcdf~shared~xerces build_system=makefile esmf_comm=auto esmf_os=auto esmf_pio=auto patches=f63d405 snapshot=none arch=linux-centos7-skylake_avx512
 -   7okttfo      ^mapl<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   r2lhznx          ^fargparse<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   gf6rzli          ^gftl<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   h7wqbpx          ^gftl-shared<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512

==> Concretized ufs-weather-model-env%intel<EMAIL_ADDRESS><EMAIL_ADDRESS> -   6wx4cyl  ufs-weather-model-env<EMAIL_ADDRESS>build_system=bundle arch=linux-centos7-skylake_avx512
 -   lyeuaa6      ^esmf<EMAIL_ADDRESS>cxxflags="-fp-model precise" fflags="-fp-model precise" ~debug~external-lapack+external-parallelio+mpi+netcdf~pnetcdf~shared~xerces build_system=makefile esmf_comm=auto esmf_os=auto esmf_pio=auto patches=f63d405 snapshot=none arch=linux-centos7-skylake_avx512
 -   7okttfo      ^mapl<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   r2lhznx          ^fargparse<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   gf6rzli          ^gftl<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512
 -   h7wqbpx          ^gftl-shared<EMAIL_ADDRESS>build_system=cmake build_type=Release generator=make arch=linux-centos7-skylake_avx512

Install via spack install --verbose 2>&1 | tee log.install.ue-esmf-8.6.1-mapl-<IP_ADDRESS>, then spack module lmod refresh --upstream-modules (use tcl instead of lmod where necessary), then spack stack setup-meta-modules

List of platforms / installers

[ ] MSU Orion (EPIC/EMC)
[ ] MSU Hercules (EPIC/EMC)
[ ] NASA Discover SCU16 (@srherbener)
[ ] NASA Discover SCU17 (@srherbener)
[ ] NAVY HPCMP Narwhal (@climbfuji)
[ ] NAVY HPCMP Nautilus (@climbfuji)
[ ] NCAR-Wyoming Derecho (EPIC)
[ ] NOAA Acorn (WCOSS2 test system; @AlexanderRichert-NOAA)
[ ] NOAA Parallel Works EPIC (AWS, Azure, Gcloud) (@natalie-perlin)
[ ] NOAA Parallel Works JCSDA (Gcloud) (@fmahebert)
[ ] NOAA RDHPCS Gaea (EPIC/EMC)
[ ] NOAA RDHPCS Hera (EPIC/EMC)
[ ] NOAA RDHPCS Jet (EPIC/EMC)
[x] UW (Univ. of Wisconsin) S4 (@climbfuji)
[ ] Amazon Web Services Parallelcluster Ubuntu 22.04 (JCSDA)
[ ] Ubuntu CI runner for skylab, simobs, ... (@climbfuji)
[ ] Amazon Web Services Red Hat 8 @srherbener Do you want to do that? May not be necessary to unpack the released AMI for this. Up to you.

@climbfuji @AlexanderRichert-NOAA @jkbk2004 @junwang-noaa i installed a chained env based on 1.6.0 but with esmf/8.6.1 and mapl/2.46.2 here /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/ue-esmf-8.6.1-mapl-2.46.2/install/modulefiles/Core. it is intel only for now. please give a try and let us know how it works with the ufs-wm.

@climbfuji @AlexanderRichert-NOAA @jkbk2004 @junwang-noaa i installed a chained env based on 1.6.0 but with esmf/8.6.1 and mapl/2.46.2 here /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/ue-esmf-8.6.1-mapl-2.46.2/install/modulefiles/Core. it is intel only for now. please give a try and let us know how it works with the ufs-wm.

I am doing the gcc part now. I had to comment out jedi-tools-env in the chained environment, but that doesn't matter. Fortunately, 1.6.0 as the last release that had more than one compiler in one environment - this just causes trouble. Unfortunately, though, we always need to go back and make updates to 1.6.0!

@mathomp4 mapl 2.46.2 refuses to build on Hercules with gcc, because the 1.6.0 stack uses mvapich2:
==> Ran patch() for mapl
==> mapl: Executing phase: 'cmake'
==> Error: InstallError: Unsupported MPI stack

/work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/spack/var/spack/repos/builtin/packages/mapl/package.py:363, in cmake_args:
        360        elif self.spec.satisfies("^cray-mpich"):
        361            args.append(self.define("MPI_STACK", "mpich"))
        362        else:
  >>    363            raise InstallError("Unsupported MPI stack")
        364
        365        return args

See build log for details:

Any quick fix for this (locally if needed - we've moved away from mvapich2 since spack-stack-1.7.0)?

@mathomp4 mapl 2.46.2 refuses to build on Hercules with gcc, because the 1.6.0 stack uses mvapich2:
==> Ran patch() for mapl
==> mapl: Executing phase: 'cmake'
==> Error: InstallError: Unsupported MPI stack

/work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/spack/var/spack/repos/builtin/packages/mapl/package.py:363, in cmake_args:
        360        elif self.spec.satisfies("^cray-mpich"):
        361            args.append(self.define("MPI_STACK", "mpich"))
        362        else:
  >>    363            raise InstallError("Unsupported MPI stack")
        364
        365        return args

See build log for details:

Any quick fix for this (locally if needed - we've moved away from mvapich2 since spack-stack-1.7.0)?

https://github.com/JCSDA/spack/pull/449 and https://github.com/JCSDA/spack-stack/pull/1189 fix this for release/1.6.0, https://github.com/spack/spack/pull/45164 for spack develop (it will come back to spack-stack-dev with the next pull).
https://github.com/JCSDA/spack-stack/pull/1189 also fixes the missing grib-utils module file change for wgrib.

@climbfuji thanks for taking on the hercules gcc issue. it looks to me like you did the gcc install in /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/ue-esmf-8.6.1-mapl-2.46.2/install; am i correct? if so, i can let the ufs-wm devs know.

@climbfuji thanks for taking on the hercules gcc issue. it looks to me like you did the gcc install in /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/ue-esmf-8.6.1-mapl-2.46.2/install; am i correct? if so, i can let the ufs-wm devs know.

Correct.

It looks like that the platforms missing are all EMC and EPIC systems - everything else is either done or not needed.

In case it has not been reported here yet, I wanted to make aware this issue seen on Hercules when testing with the esmf/8.6.1 spack-stack 1.6.0 installation. @jkbk2004 @BrianCurtis-NOAA @FernandoAndrade-NOAA
CMake Error at /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/ue-esmf-8.6.1-mapl-2.46.2/install/intel/2021.9.0/mapl-2.46.2-uiwt3at/lib64/cmake/MAPL/MAPL-targets.cmake:73 (set_target_properties):
The link interface of target "MAPL_cfio_r4" contains:
ESMF::ESMF

but the target was not found.  Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.

That is so odd. I mean, ESMF 8.6.1 and MAPL 2.46 were essentially created to allow for the ESMF::ESMF target.
Hmm. My only next thought is that a FindESMF.cmake file is out of date? The one we have in MAPL and the one we have in ESMA_cmake are identical to the one in ESMF.
Could you some how be picking up another one? It was noted by @danrosen25 in the ESMF PR, that, at the time these CMake files were out-of-date:

NOAA-EMC/AQM-utils cmake/FindESMF.cmake
ufs-community/UFS_UTILS cmake/FindESMF.cmake
noaa-oar-arl/NEXUS cmake/FindESMF.cmake

And a look at them shows them still quite old.
Perhaps some package is still referring to an old FindESMF.cmake in some way?

That is so odd. I mean, ESMF 8.6.1 and MAPL 2.46 were essentially created to allow for the ESMF::ESMF target.
Hmm. My only next thought is that a FindESMF.cmake file is out of date? The one we have in MAPL and the one we have in ESMA_cmake are identical to the one in ESMF.
Could you some how be picking up another one? It was noted by @danrosen25 in the ESMF PR, that, at the time these CMake files were out-of-date:

NOAA-EMC/AQM-utils cmake/FindESMF.cmake
ufs-community/UFS_UTILS cmake/FindESMF.cmake
noaa-oar-arl/NEXUS cmake/FindESMF.cmake

And a look at them shows them still quite old.
Perhaps some package is still referring to an old FindESMF.cmake in some way?

I'm running with the MAPL FindESMF.cmake on WCOSS2 right now, but if this is the case, we should look into coordinating a place for one FindESMF.cmake to exist and other groups pull from that location.

There's already an issue in the cmakemodules repo that talks about using ESMF's own findESMF.cmake: https://github.com/NOAA-EMC/CMakeModules/issues/70 - there are also issues in fv3-jedi and spack for this if I remember correctly.

@climbfuji is the findESMF.cmake issue caused by the new ESMF 8.6.1? I am curious why it is not an issue in previous ESMF 8.6.0.

@climbfuji @junwang-noaa
See this pull request, which was merged into 8.6.1
https://github.com/esmf-org/esmf/pull/226
When I tests this change in UFS I had trouble IF I updated the UFS FindESMF.cmake files. If I left them alone then the UFS system built.

https://github.com/NOAA-EMC/AQM-utils cmake/FindESMF.cmake
https://github.com/ufs-community/UFS_UTILS cmake/FindESMF.cmake
https://github.com/noaa-oar-arl/NEXUS cmake/FindESMF.cmake

@danrosen25 Thanks for looking into this issue. My question is how to resolve the build issue when updating the ESMF8.6.1 and MAPL 2.46.2 in UFS weather model. I don't remember that ufs weather model has these three submodules.
@BrianCurtis-NOAA @bbakernoaa @GeorgeGayno-NOAA FYI. The FindESMF,cmake in the repository Dan listed may need updates for ESMF 8.6.1.

I'll try to find the log, but I updated all FindESMF.cmake in UFSWM and its sub-components to the one in the ESMF repo and CDEPS doesn't like the use ESMF in share/shr_abort_mod.F90 on line 11 with error #7002: Error in opening the compiled module file. Check INCLUDE paths. [ESMF]

Note, I am on PTO until beginning of August - not sure how much I can help with this issue. @AlexanderRichert-NOAA also had experience these xxxxx ESMF vs esmf issues.

@BrianCurtis-NOAA
I looked through the code: CDEPS overwrites ESMF_F90COMPILEPATHS then uses the variable directly.
The FindESMF.cmake file included with ESMF creates a new variable ESMF_INCLUDE_DIRECTORIES. Or one can use cmake targets ESMF or ESMF::ESMF. This was true before the 8.6.1 release too.
So basically, CDEPS needs to run the current version of FindESMF.cmake included with CDEPS in order for the current code to work OR share/CMakeLists.txt needs to be modified. And CDEPS will not run the FindESMF.cmake version if a target 'esmf' (case sensitive already exists.
I've been making the case for independent component build steps, such as done when using the build infrastructure in ESMX. Setting all CMake variables in one place and letting global CMAKE variables affect builds for all components is hard to manage.

@danrosen25 may I ask if you have the code updates for CDEPS so that we can move to ESMF 8.6.1? Thanks for looking into this issue.

Does it not work with the existing version of FindESMF.cmake in CDEPS?
https://github.com/NOAA-EMC/CDEPS/blob/develop/cmake/FindESMF.cmake
But I think you need to change this line from APPEND to PREPEND to use the correct module.
https://github.com/NOAA-EMC/CDEPS/blob/develop/CMakeLists.txt#L31
Either that or change the CMakeLists.txt to
https://github.com/NOAA-EMC/CDEPS/blob/develop/share/CMakeLists.txt#L23
to remove ESMF_F90COMPILEPATHS and add target_link_libraries(cdeps_share ESMF::ESMF) along with changing the rest of the CmakeLists.txt files and the FindESMF.cmake file in CDEPS to match the updated version.

It may be confusing that some cmake in CDEPS is for a "standalone" setup. I believe these are the relevant ones for UFS:
https://github.com/ufs-community/ufs-weather-model/blob/develop/CDEPS-interface/CMakeLists.txt
https://github.com/ufs-community/ufs-weather-model/blob/develop/CDEPS-interface/cdeps_files.cmake
and then within each data component CDEPS/dxxx/CMakeLists.txt

Since that's the CMakeLists.txt file being used it's probably a case sensitivity issue. The target for ESMF is ESMF::ESMF and the alias is ESMF. What I'm seeing here is esmf. I'm looking at the current FindESMF file in CMakeModules (note that this is not the one distributed by ESMF) it is lowercase esmf (we've never provided a FindESMF module with lowercase esmf.
https://github.com/NOAA-EMC/CMakeModules/blob/cabd7753ae17f7bfcc6dad56daf10868aa51c3f4/Modules/FindESMF.cmake

Note: GEOS is still has a few esmf target refs due to olden days when we were linking to libesmf.a and, well, in CMake-land that is esmf. But of course now we have a real FindESMF.cmake and we should follow that.
But until I can fix up all of GEOS, we have:
    if (NOT TARGET esmf)
      add_library(esmf ALIAS ESMF::ESMF)
    endif ()

in our code to still support the old style. I hope to remove it soon.

Similar code can be added to UFS after this line:
https://github.com/ufs-community/ufs-weather-model/blob/develop/CMakeLists.txt#L150

Where are we with this issue? Have<EMAIL_ADDRESS>and<EMAIL_ADDRESS>been installed on all NOAA RDHPCS systems in spack-stack-1.6.0? Or is this moot given that spack-stack-1.8.0 has<EMAIL_ADDRESS>with<EMAIL_ADDRESS>

MAPL 2.46.2 has a bug, we have to move to esmf 8.6.1 and mapl 2.46.3 to debug the issue. We suggest having a test version of spack-stack 1.6.0 with esmf 8.6.1 and mapl 2.46.3 to continue the debugging work, while you can move forward with spack-stack 1.8.0 release with esmf 8.6.1 and mapl 2.46.3

@RatkoVasic-NOAA FYI

@mathomp4 we can continue to test on orion and hercules for the new versions of mapl and esmf. we can follow up at https://github.com/ufs-community/ufs-weather-model/issues/2346.

MAPL 2.46.2 has a bug, we have to move to esmf 8.6.1 and mapl 2.46.3 to debug the issue. We suggest having a test version of spack-stack 1.6.0 with esmf 8.6.1 and mapl 2.46.3 to continue the debugging work, while you can move forward with spack-stack 1.8.0 release with esmf 8.6.1 and mapl 2.46.3

@RatkoVasic-NOAA FYI

@climbfuji @junwang-noaa:
@RatkoVasic-NOAA installed a test env on orion/hercules w/<EMAIL_ADDRESS>and<EMAIL_ADDRESS>in the following locations:
Hercules: /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/ue-esmf-8.6.1-mapl-2.46.3/install/modulefiles/Core
Orion: /work/noaa/epic/role-epic/spack-stack/orion/spack-stack-1.6.0/envs/ue-esmf-8.6.1-mapl-2.46.3/install/modulefiles/Core

thank you @RatkoVasic-NOAA!!!

Per a telecon today between the MAPL team (cc @tclune) and UFS team (e.g., @junwang-noaa and others), there was a request to create a MAPL tag that was based on MAPL v2.40.3 (which was the last "working" version) but with support for ESMF 8.6.1 as that version was needed. This could then be installed on Hercules for testing.
I've created a "preliminary" tag, v<IP_ADDRESS> where the changes compared to v2.40.3 are:

All esmf target references in CMake are now ESMF::ESMF
Update FindESMF.cmake to the ESMF 8.6.1 version

The tag is on MAPL now, though no release as I'm not sure yet if all the needed CMake, etc. changes have been brought over (MAPL 2.40 was a while ago).
Now, MAPL <IP_ADDRESS> is not in the spack package.py for MAPL, so I'm guessing it'll need to be installed as:
spack install<EMAIL_ADDRESS>
My laptop seems to be able to resolve that. That said, we might need to iterate on this a few times if I missed something. There have been further "fixes for Spack/UFS" on later tags and perhaps those might need backporting. If so, I can update and push the tag.

Hi @mathomp4
The 8.6.1 compliant version should fix the the method for looping over ESMF_Config tables. It's erroneous to call ESMF_ConfigNextLine when you're at the end of the table because there aren't more items. Previously you could call ESMF_ConfigNextLine at the end of the table and it would return the end of table marker ::. Here's my exchange with Ben.
reproducer_490.tgz

I removed a statically sized string buffer that held data for the "current line" of a configuration file. This work was done to eliminate the fixed maximum line length of 1024. Paired with the work and out of necessity, I also cleaned up all the calls that returned the next line. I'm not sure why the code above doesn't use tableEnd in the call to ESMF_ConfigNextLine?
https://earthsystemmodeling.org/docs/release/latest/ESMF_refdoc/node6.html#SECTION060931800000000000000
Alternatively the code could use ESMF_ConfigGetDim to get the line count of a table and use this in a do loop.
https://earthsystemmodeling.org/docs/release/latest/ESMF_refdoc/node6.html#SECTION060931300000000000000
Technically "::" isn't the next line, similar to how the label itself is not the next line. I can discuss this further with the ESMF Core team if this needs to be added back but my recommendation is to use the tableEnd argument in ESMF_ConfigNextLine.
I've attached a reproducer of this issue that includes the two working examples mentioned above.

@danrosen25 Ohhhh. Okay. Let me consult with @bena-nasa on that. I might need to push the tag...

@mathomp4 We will test ESMF 8.6.1 with this MAPL <IP_ADDRESS> in ufs-weather model then.
@AlexanderRichert-NOAA would you please install spack-stack with these new libraries on Hercules. The current Hercules module file is at: https://github.com/ufs-community/ufs-weather-model/blob/develop/modulefiles/ufs_hercules.intel.lua. Thanks

@mathomp4 the <IP_ADDRESS> build on hercules is failing because c_ptr is undefined in geom/FieldPointerUtilities.F90. Adding use iso_c_binding at the top of the file fixes it, in which case it builds okay.

@junwang-noaa if/when @mathomp4 updates the tag to fix the issue in my previous comment, I'll reinstall, but if you want to go ahead and test: /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/mapl-<IP_ADDRESS>-intel-2021.9.0/install/modulefiles/Core

@mathomp4 the <IP_ADDRESS> build on hercules is failing because c_ptr & c_loc are undefined in geom/FieldPointerUtilities.F90. Adding use iso_c_binding at the top of the file fixes it, in which case it builds okay.

Ahhh. Yeah. That was a file where we could compile it because the iso_c_binding was bleeding in via ESMF, but they fixed that on their end.
I've pushed the v<IP_ADDRESS> tag.

Thanks @mathomp4. I just reinstalled using the updated tag.

@AlexanderRichert-NOAA may I ask if you can install ESMF beta snapshot 8.8.0b04(https://github.com/esmf-org/esmf/releases/tag/v8.8.0b04) with MAPL <IP_ADDRESS> on Hercules for people to test the grid imprint issue in UFS coupled test? Thanks

Yes, will do

/work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/esmf-8.8.0b04-intel-2021.9.0/install/modulefiles/Core

@AlexanderRichert-NOAA et al, I've released a formal MAPL v<IP_ADDRESS> release[^1]:
https://github.com/GEOS-ESM/MAPL/releases/tag/v<IP_ADDRESS>
and I've made a PR to spack mainline for it:
https://github.com/spack/spack/pull/47627
If any changes are needed now, we'll up the tweak number to 2.
[^1]: The release doesn't have a Zenodo badge yet because, well, it doesn't seem to be appearing on Zenodo. Not sure why 🤷🏼. I'll keep monitoring.

@AlexanderRichert-NOAA would you please install ESMF beta snapshot 8.8.0b06(https://github.com/esmf-org/esmf/tree/v8.8.0b06) with MAPL <IP_ADDRESS> on Hercules for us to test the HR4 hanging issue? Thank you very much!

Yes will do

Done. /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/esmf-8.8.0b06-intel-2021.9.0/install/modulefiles/Core

@AlexanderRichert-NOAA with an one line change to use the new module:
-- prepend_path("MODULEPATH", "/work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/fms-2024.01/install/modulefiles/Core")
prepend_path("MODULEPATH", "/work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/esmf-8.8.0b06-intel-2021.9.0/install/modulefiles/Core")

Now we got error message:
$ module load ufs_hercules.intel
Lmod has detected the following error:  These module(s) or extension(s) exist but cannot be loaded as requested: "jasper/2.0.32", "python/3.10.13", "netcdf-fortran/4.6.1",
"cmake/3.23.1", "hdf5/1.14.0"
   Try: "module spider jasper/2.0.32 python/3.10.13 netcdf-fortran/4.6.1 cmake/3.23.1 hdf5/1.14.0" to see how to load the module(s).

Did we miss anything?

@AlexanderRichert-NOAA ESMF released a new beta snapshot 8.8.0b09 for us to testing ESMF managed thread. Would you please install it with current compiler version and MAPL <IP_ADDRESS> in spack-stack 1.6.0?
Just to clarify, this does not require any Intel compiler version change. It is a separate request from the Intel version 2021.12 for MAPL/GOCART testing. Thank you!

/work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.6.0/envs/esmf-8.8.0b09-intel-2021.9.0/install/modulefiles/Core


Cody icon not appearing in Activity Sidebar

Type: Bug
Extension Information

Cody Version: 1.41.1730474489
VS Code Version: 1.94.2
Extension Host: desktop

Steps to Reproduce

Installing Cody AI from Extensions

Expected Behaviour

The Docs say the Cody icon should automatically appear in my sidebar, it does not. The Sidebar is working for other icons. There is no option to include Cody in the sidebar settings either.
Logs

Extension version: 1.41.1730474489
VS Code version: Code 1.94.2 (Universal) (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Darwin arm64 21.3.0
Modes:

System Info

Item
Value

CPUs
Apple M1 (8 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
4, 6, 6

Memory (System)
16.00GB (0.07GB free)

Process Argv
. --crash-reporter-id d2675dc8-bb34-4814-bdff-45de61140c59

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
jg8ic977:31013176
dvdeprecation:31068756
dwnewjupyter:31046869
impr_priority:31102340
nativerepl2:31139839
refactort:31108082
pythonrstrctxt:31112756
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013

Not sure what is happening here but I was able to drag and drop the Cody icon over once loading it from the command pallete.

Based on your update, I am marking this issue as resolved/closed.If you still need help, please re-open a report and let us know 🙂 Thanks!


fixed doubly-linked-list reverse method omit change node's previous

#253

Thank you for the fix @jadestrong


Added DevC Yaounde's github profile link to the DevCGlobalDirectory.md

What does this PR do?
Hi, Updated DevC Yaounde's info with github profile link in DevCGlobalDirectory.md
Any relevant issues this PR addresses? (optional)
#
Any background context you want to add?

Thanks!


Add jekyll build and remove old dco check

Signed-off-by: Peter Zhu<EMAIL_ADDRESS>Description
The old dco check for the PR is not needed any more as it is replace by the DCO app.

We can also add proper jekyll testing.
At start we can just add a jekyll build run to ensure at least everything can be built before failing the staging pipeline.

Average runtime: 2min first run 30 secs right after due to caching.
Issues Resolved
https://github.com/opensearch-project/project-website/issues/1094
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

@krisfreedain could you take a look at this?
Thanks.

@krisfreedain could you take a look at this? Thanks.

Thanks @peterzhuamazon - this one looks really interesting - I want to understand any changes we'll need to make in pushing commits, and instructing external authors as well. - I'll book some time with you to have a quick chat


Make ResourceID available in dayPropGetter

Clear and concise description of the problem
I am using employees (resources) for the calendar and for days where the employee is not working, i would like to be able to have them remain in the calendar View, however their class="rbc-events-container" Column be shaded slightly darker so that the user knows that this employee is actually not working.
having the resourceID available would allow me to style each column individually depending on conditions.
Suggested solution
having the resourceID available would allow me to style each column individually depending on conditions.
Alternative
No response
Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Would you like to open a PR for this feature?

[ ] I'm willing to open a PR

Done. New documentation available