Updating tile configuration with SSL certificate causes deployment error

Harbor tile version: v0.0.48
Steps to reproduce -
Deploy tile
Update Certificate- used SSL
Click apply
Result:
Expected - Harbor should be updated/redeployed with new changes
Actual - Deployment errors out
Note: This error only happened when SSL certificate was used and reconfigure tile,  in case of new External/Ops manager certificate change it worked fine.
Logs:
harbor-app-3e502db1fc97.zip
harbor-app-d61fa1449922.zip

Hi @singhshwetaQE , could you please check #3774 which might be the same issue as yours ?

I think we can close this. I was testing with a certificate with a common name that was not the hostname. This was causing the issue in updating the deployment since the certificate was invalid.
Repeating the process with an autogenerated cert or with a custom certificate with a valid common name and subject alternative name allowed the tile to get installed successfully.

@singhshwetaQE Your harbor version is outdated, please try to use the latest one to do testing.
The version should be 1.3.0-*.pivotal
Here is the latest build of harbor tile: https://storage.googleapis.com/harbor-ci-pipeline-store/tile-releases/harbor-1.3.0-rc.21.pivotal

@singhshwetaQE any update?

Still having same issue with build harbor-container-registry-1.3.0-build.37.pivotal
Deploy tile
Update Certificate- used SSL
Click apply
Deployment errors out, attaching new logs
harbor-app-a62c623ef443.zip

@singhshwetaQE how do you "Update Certificate- used SSL" ?  Is your issue the same as #3823 ?

Looks similar issue to me
From: Jesse Hu<EMAIL_ADDRESS>Sent: Wednesday, December 20, 2017 2:08 AM
To: vmware/harbor<EMAIL_ADDRESS>Cc: Shweta Singh<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [vmware/harbor] Updating tile configuration with SSL certificate causes deployment error (#3779)
@singhshwetaQEhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_singhshwetaqe&d=DwMCaQ&c=uilaK90D4TOVoH58JNXRgQ&r=69KLxzYiiLa4y4Mu0KNTvaRuG9xl54B6kfep9q-kgW4&m=ml_rIN5lS5KA1AZCUIAM2K3fsOZDzfdnjB3iovGMABY&s=lw60ihq7oV4K5D7IfH89PAZuFxt16Hv8Q3d4ud048Zc&e= how do you "Update Certificate- used SSL" ? Is your issue the same as #3823https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_vmware_harbor_issues_3823&d=DwMCaQ&c=uilaK90D4TOVoH58JNXRgQ&r=69KLxzYiiLa4y4Mu0KNTvaRuG9xl54B6kfep9q-kgW4&m=ml_rIN5lS5KA1AZCUIAM2K3fsOZDzfdnjB3iovGMABY&s=J5FgHvP-hkYx3EEXeHAzc9_4t2h_g7W8goOytt0HHyo&e= ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_vmware_harbor_issues_3779-23issuecomment-2D352993448&d=DwMCaQ&c=uilaK90D4TOVoH58JNXRgQ&r=69KLxzYiiLa4y4Mu0KNTvaRuG9xl54B6kfep9q-kgW4&m=ml_rIN5lS5KA1AZCUIAM2K3fsOZDzfdnjB3iovGMABY&s=dY41VKDKensVRRBVzkfaaWT1swNfALO2E3wKZ24x_hI&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AbuXyInk7GxLkYKIXswlUTyAzqt92RuQks5tCMBSgaJpZM4Q-5FwL3&d=DwMCaQ&c=uilaK90D4TOVoH58JNXRgQ&r=69KLxzYiiLa4y4Mu0KNTvaRuG9xl54B6kfep9q-kgW4&m=ml_rIN5lS5KA1AZCUIAM2K3fsOZDzfdnjB3iovGMABY&s=KyWfNe4NvXtVhu6rs-7DFaUl78Z_0gGRBMf-8Hq7SqE&e=.

Closing as #3823 is fixed, the change is contained in master branch not 0.8


Root instance not found when using with Vue 2.7

Error in setup: "Error: Instance $root not found"

Most likely cause by the following:
https://github.com/vuejs/apollo/blob/757e45cac05e860c0a0cc6d1c513545df4009c72/packages/vue-apollo-composable/src/util/loadingTracking.ts#L15
It should be  const vm = getCurrentInstance().proxy;

I'm facing the same problem.

Also running into this issue and preventing a project I'm working on to upgrading to vue 2.7. I tested out the change @chanlito has mentioned and can confirm that fixed the issue for me.

Any update on this being updated in an official release? I also have a project that requires Vue 2.7, as the recent Nuxt composition API update depends on it, and usage of the @nuxtjs/apollo module is required, which utilizes vue/apollo-composable in order to function in the composition API.


Nucleo STM32L011 Unknown Chip ID: 0x10086457

NOTICE: The issue may be closed without notice when not enough information is provided!

[ X]  Stlink/v2-onboard
[ ] Programmer firmware version: e.g STSW-LINK007 2.27.15
[ X] Operating system: Windows 10
[ X] Stlink tools version v1.3.0
[ X] st-util
[ X] Target chip (and optional board): STM32L011K4T6 (STM32L011 Nucleo-32)

Board firmware: V2.J28.M18 STM32 Debug+Mass storage
Output:
C:\tools\stlink-1.3.0-win64\bin>st-util
st-util 1.3.0
2017-05-29T14:24:15 INFO C:\Users\Jerry\Desktop\stlink-master\src\common.c: Loading device parameters....
2017-05-29T14:24:15 WARN C:\Users\Jerry\Desktop\stlink-master\src\common.c: unknown chip id! 0x10086457

C:\tools\stlink-1.3.0-win64\bin>st-info --chipid
libusb: warning [init_device] could not get node connection information for device '\\.\USB#VID_045E&PID_0745&MI_02#8&12437C26&0&0002': [87] The parameter is incorrect.

Expected/description:
I expect to see a connection like this, from my working STM32L031 Nucleo-32 (STM32L031K6T6)
C:\tools\stlink-1.3.0-win64\bin>st-util
st-util 1.3.0
2017-05-29T14:29:19 INFO C:\Users\Jerry\Desktop\stlink-master\src\common.c: Loading device parameters....
2017-05-29T14:29:19 INFO C:\Users\Jerry\Desktop\stlink-master\src\common.c: Device connected is: L0x Category 2 device, id 0x20186425
2017-05-29T14:29:19 INFO C:\Users\Jerry\Desktop\stlink-master\src\common.c: SRAM size: 0x2000 bytes (8 KiB), Flash: 0x8000 bytes (32 KiB) in pages of 128 bytes
2017-05-29T14:29:19 INFO C:\Users\Jerry\Desktop\stlink-master\src\gdbserver\gdb-server.c: Chip ID is 00000425, Core ID is  0bc11477.
2017-05-29T14:29:19 INFO C:\Users\Jerry\Desktop\stlink-master\src\gdbserver\gdb-server.c: Listening at *:4242...

Already supported in v1.3.1 or higher, but no build for windows is available (yet). See https://github.com/texane/stlink/blob/master/ChangeLog.md#v131.

This explains why I could see no problem in the current source.


remove future imports

Description
Remove all unused future imports

This is my favourite pull request

Was very satisfying

I don't know, it's also a bit slower using 3.5 than 3.6

Also some of the solvers fail to converge with 3.5 (but work fine on 3.6) - https://travis-ci.org/pybamm-team/PyBaMM/jobs/531078575#L3079
Can be fixed by using fewer grid points or stopping at an earlier time, but it's a bit annoying


Fix sidebar indenting CSS

Replaces https://github.com/cfpb/design-system/pull/368
Changes

Change margin and padding on sidebar CSS so that multi-line items are indented correctly.

Testing

Pull branch, run local docs, see that sidebar is indented versus live version.

Screenshots
Before:

After:

Bravo 🎉 and thanks for updating snyk!


[CBR-285] Wire submission layer to the wallet

Description
This PR capitalises on CBR-245 by actually threading the submission layer as part of the new wallet.
It also adds a new acid-state update called evictPending, which is called whenever we need to evict
transactions from the wallet's pending set.
Linked issue
https://iohk.myjetbrains.com/youtrack/issue/CBR-285
Type of change

[~] 🐞 Bug fix (non-breaking change which fixes an issue)
[X] 🛠 New feature (non-breaking change which adds functionality)
[~] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[X] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[~] 🔨 New or improved tests for existing code
[~] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[~] I have read the style guide document, and my code follows the code style of this project.
[~] If my code deals with exceptions, it follows the guidelines.
[~] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

[~] I have added tests to cover my changes.
[~] All new and existing tests passed.

QA Steps

Screenshots (if available)

@edsko I have completed the refactorings (I eventually opted to go with 3 distinct commits for ease of review). I think we should be in business now.


Update ss-linux-cluster-availability-group-create-prereq.md

update AlwaysOn XE with new docs link.

Hi @MikeRayMSFT - I can't find an author attribute for this include file. You've updated it several times--could you review the PR? Thanks.

If the update is approved, the PR review team can remove the locale (en-us) from the link that's added.

Hi @MikeRayMSFT - Could you take a look at this PR? Thanks.

@suresh-kandoth Thanks for the suggested fix. @MikeRayMSFT I think we need to make this a relative link. To make sure we do it right, can you make the change in a separate PR to make sure we put a valid relative link in there. Then we can close this without merging as fixed. Thanks!

I had a problem with the link and am fixing it now.


Shader files not loading in 1.7

Environment
Windows build number: 10.0.19042.0
Windows Terminal version: 1.7.572.0

Steps to reproduce

Build/Install Windows Terminal 1.7.572.0
Set experimental.pixelShaderPath on a profile (or globally) such that it points to an appropriately structured HLSL file (such as Invert.hlsl from the samples folder)
Run the terminal (with the appropriate profile if necessary)

Expected behavior
The pixel shader is loaded and executed.
Actual behavior
The pixel shader is not loaded.
Comments
I have not been able to load any shader files at all in 1.7 from the official release, nor when I build it from source. Poking around in the debugger, I can see that the shader file path is definitely there when the JSON is read in:

However it seems to disappear at some point between being read and sent to SetPixelShaderPath(). I'm not sure if it's being deserialized correctly because I don't really understand how I'm supposed to inspect the settings object; it doesn't behave the way I'd expect it to (just C++ things, I assume).
release-1.7

release-1.6

I've tried this on other machines that have never had any version of the Terminal installed and they all exhibit the same issue.

Well that's batty. Maybe that's what's causing #9338?
I'm gonna real quick @DHowett because he was helping investigate another bug where the shader path would get absolutely mangled before making it into the DxRenderer.

Well that's batty. Maybe that's what's causing #9338?

I did see that issue, but I decided to post a separate one because they're using 1.6, which has no problems for me, and they're also experiencing an error message, which I'm not getting even if use a non-existent path (because it just becomes an empty string, I guess). Could still be related though? ¯_(ツ)_/¯

Yea, after re-reading #9338, they do definitely seem different. The warning dialog in that one's really throwing me for a loop.  They're both crazy, just, each their own unique kind of crazy 😄

@PankajBhojwani Check this out!
TerminalSettings.h:117
        GETSET_PROPERTY(hstring, PixelShaderPath);

But look at all the other settings ...
        GETSET_SETTING(TerminalApp::TerminalSettings, bool, RetroTerminalEffect, false);
        GETSET_SETTING(TerminalApp::TerminalSettings, bool, ForceFullRepaintRendering, false);
        GETSET_SETTING(TerminalApp::TerminalSettings, bool, SoftwareRendering, false);
        GETSET_SETTING(TerminalApp::TerminalSettings, bool, ForceVTInput, false);

When we create a new TerminalSettings leaf object, it has no PixelShaderPath because it is not an inheritable setting.
The danger of macros with a bunch of identical names.

Maybe we should GET rid of the GETSET_ prefix, because that's not really relevant anymore.


Trimless stopped working?

It seems like Trimless stopped working with one of the recent updates of GMail or Chrome. Right? Is it still working for others?

Works on my machine ¯\_(ツ)_/¯

Thank you for the super fast reply!
I'm on Mac OS 10.14.4, Chrome 76.0.3809.100.
Does it work for you such that you never see those 3 dots in Gmail?

Not sure about "never", since I'm not using this extension in my day-to-day, but I've given it a quick go through several emails and haven't noticed any issues. Are you sure it's enabled? Chrome may sometimes have a mind of its own. Have you tried restarting your browser? Have your tried hard-refreshing Gmail? Have you tried enabling Trimless in incognito and testing it there? Have you tried reinstalling the extension?

Following up on this with some delay.

Yes, it's enabled.
Yes, I've restarted my browser.
Hard-refreshing: Gmail: How does that work?
Incognito: When I'm in incognito mode all my browser extensions don't show up. How can this be done?
Yes, I tried reinstalling the extension.

Thanks a lot!!

Re: Incognito:

Open top-right menu > More tools > Extensions.
Press "Details" under Trimless.
Enable "Allow in Incognito".
Open an Incognito tab, log into Gmail and open a few emails, see if it's still broken.
Disable "Allow in Incognito", as to keep it clean.


Fix icon in README

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://github.com/snowplow/snowplow/wiki/CLA to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

Confirmed! @l4u has signed the Individual Contributor License Agreement. Thanks so much

Closing in favor of https://github.com/snowplow/snowplow-javascript-tracker/issues/596. Thanks!


How uninstall distro or reinstalled

Hi guys
Im using Windows Server 2019

I was learning about Linux subsystem and I want to know if is posible to uninstall a distro a remove the folder or reinstall a distro.
Currently I'm getting this because Im was trying to install 0h-my-zsh on the linux subsystem but then I can't enter to linux so unregister the distro and trying to delete all the folder to reinstall linux distro.
But it said to my I don't have permissions to delete and this message went I try to execute.

If anyone can't give some guide it will be great how to uninstall de distro. Thanks

never mind...
wslconfig /unregister
and then delete the files...
sorry for the inconvenience

just for knowledge I can't delete this file:


Change type annotation from list to Sequence

Change type annotation from list to Sequence in send_batch and send_sub_entry methods to make variable covariant https://mypy.readthedocs.io/en/stable/generics.html#variance-of-generic-types

@nesb1 it is fair, this shouldn't introduce any breaking change I suppose?

@DanielePalaia  yes, it is not breaking change because list is subclass of Sequence

@nesb1 thank you!


Courts: collateral and reputation

Regarding the example of the responsibilities of the code of conduct, I can't understand why there is a difference between responsibility 1 and 3:

In the event that either party of the dispute attempts to bribe the court, the juror agrees to flag the case for review.

In the event that a single party attempts to bribe the court, the juror agrees to rule in favor of the party which did not attempt to bribe the court.

As I understand it either means a single party so in this case does the juror flag the case for review or rule?
(From @mariapao)

+1, have the same question after reading


Build error: Version 0.10.3 (2015-3-25)

msgpack-nim fails compilation with the following print out. I have no idea what happened but closure seems to be in trouble.
gcc -c  -w  -I/home/akira/.nimvm/versions/devel/lib -o /home/akira/msgpack-nim/nimcache/msgpack_msgpack.o /home/akira/msgpack-nim/nimcache/msgpack_msgpack.c
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c: In function 'appendarray_103351':
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2694:5: error: too few arguments to function 'pack_103344'
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:472:1: note: declared here
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c: In function 'appendmap_103402':
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2731:5: error: too few arguments to function 'pack_103344'
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:472:1: note: declared here
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2733:5: error: too few arguments to function 'pack_103344'
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:472:1: note: declared here
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c: In function 'pack_103344':
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2768:21: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2768:47: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2768:100: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2768:136: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2785:21: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2785:47: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2785:99: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2785:135: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2802:21: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2802:47: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2802:99: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2802:135: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2820:19: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2820:43: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2820:92: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2820:126: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2837:19: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2837:43: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2837:91: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2837:125: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2854:19: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2854:43: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2854:91: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:2854:125: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c: In function 'pack_105277':
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:4137:13: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:4137:32: error: request for member 'ClPrc' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:4137:59: error: request for member 'ClEnv' in something not a structure or union
/home/akira/msgpack-nim/nimcache/msgpack_msgpack.c:4137:88: error: request for member 'ClPrc' in something not a structure or union
Error: execution of an external program failed

Resolved with devel
Related issue:
https://github.com/Araq/Nim/issues/2404


Unreadable characters in the name of the project or database

Description
When working with с Dbeaver 23.0.4  - Unreadable characters in the name of the project or database . A copy of the enclosed screen.  **Please help me fix it !!!!!

DBeaver Version
<IP_ADDRESS>305071722
Operating System
Microsoft Windows 10.0.19044
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Unfortunately, the quality of your screenshot is poor, so we can't see what's the issue and where is "unreadable characters". Could you send the screenshot here directly by doing Ctrl+V to the text area for the comment (without pasting to Microsoft Word)?

window or bookmark projects or database => Unreadable characters
Help !

Oh, I see. Could you try changing Main font in preferences?

Thanks a lot ! I'll try to change the settings within an hour . I’ll write about the results right away

Your recommendations led to a positive result . Thank you very much . I admire your professionalism

good luck and have a nice day

Thank you for update.


Add support for RSASSA-PSS Signature algorithm

Currently, the library does not support any of the algorithms added by JDK-8146293, i.e.:

SHA512/224withRSA (1.2.840.1135<IP_ADDRESS>)
SHA512/256withRSA (1.2.840.1135<IP_ADDRESS>)
RSA-PSS (1.2.840.1135<IP_ADDRESS>)
SHA1withRSAandMGF1
SHA224withRSAandMGF1
SHA256withRSAandMGF1
SHA384withRSAandMGF1
SHA512withRSAandMGF1
SHA512/224withRSAandMGF1
SHA512/256withRSAandMGF1

(see also JDK-82334183])
The changes probably only need to be applied to the enum Algorithm.
Ii am not sure which naming pattern to apply to the enum names as well as portable name and jmvName attributes. Any suggestions?

I would also need this feature. Could you please tell me if you intend to implement it? Thank you!

I've raised PR #32  for RSASSA-PSS

Can you check #32 and #38? Does it cover your needs?

@sebastien-rosset looks perfect to me! thanks so much for your effort!


Unify tokenize and findContentBreak logic

One is manually searching for whitespace and the other is using a regex to split. The logic that analyzes tokens should be the same in both the split and merge cases. I think what is supposed to happen is that we tokenize in the split checks and then refactor findContentBreak to operate on the tokens.

unified in the single line case, but not in the block case

Somewhere during today's and yesterday's series of misc. commits the split function was revised and no longer uses findContentBreak and uses the same tokenize function as split. The original findContentBreak has been deprecated entirely. There is a new similarly named helper function in split that does something similar but it now does so on the basis of the tokenized word boundaries instead of hacky whitespace pattern matching.

Somewhere during today's and yesterday's series of misc. commits the split function was revised and no longer uses findContentBreak and uses the same tokenize function as split. The original findContentBreak has been deprecated entirely. There is a new similarly named helper function in split that does something similar but it now does so on the basis of the tokenized word boundaries instead of hacky whitespace pattern matching.


Test case /v1/regard-application::Forwardings triggered? / NewApplicationCausesRequestForTopologyChangeInformation:: Expected ExecutionAndTraceLog/v1/list-records-of-flow::

Problem Description:
Test case /v1/regard-application::Forwardings triggered? / NewApplicationCausesRequestForTopologyChangeInformation:: Expected ExecutionAndTraceLog/v1/list-records-of-flow is failing with assertion error expected 200 to equal 204
Root Cause :
The forwarding triggered /v1/redirect-topology-change-information returns response-code 200 which is as expected but test suite is expecting it to 204.
Solution:
Test-suite should expect the code to be 200 but not 204.

Assertion Failure details :
/v1/regard-application::Forwardings triggered? / NewApplicationCausesRequestForTopologyChangeInformation:: Expected ExecutionAndTraceLog/v1/list-records-of-flow


Expose more of the libvore API in libvorejs

Currently there is only the "voreSearch" function which will compile and run the regex on every call.
We should be able to expose the Compile and Run functions from the Vore type to make it so the user can compile the regex once and run it against many different search texts

Started adding a voreCompile function that just returns the bytecode so that the js can call voreSearch with the bytecode object and it will skip the compile step.

Maybe having a custom byte encoding would actually be easier to serialize and deserialize


Add GlusterFS to k8s

Added k8s to the gluster role.
Tested and forms the same k8s cluster visible to all workers.

[ ] Installs cleanly on a fresh build of most recent master branch
[ ] Upgrades cleanly from the most recent release
[ ] Updates documentation relevant to the changes

@sehqlr: could the new folks help with testing this?

@andreimc Sorry for the delay, we're still working on testing this. I believe @sehqlr will be helping @nigerianlegend with that today, so I'm going to assign this PR to them.

Cool I tested this on AWS

Works for me:
[centos@mantl-kubeworker-002 ~]$ sudo touch /mnt/container-volumes/TEST2
[centos@mantl-kubeworker-002 ~]$ exit
logout
Connection to <IP_ADDRESS> closed.
code/mantl2 > mantl_ssh control
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
Last login: Fri Jul 29 11:25:44 2016 from fs.svanette.ch
[centos@mantl-control-03 ~]$ ls /mnt/container-volumes/
TEST  TEST2

I went ahead and cherry picked your commit to master rather than merging the PR, just to keep our git history a little cleaner. You can see it in master here: https://github.com/CiscoCloud/mantl/commit/fe2d5bb8a81ab473ea93945a16991a45820f5a70

👍


Fix switching components not actually switching sometimes

remove shouldComponentUpdate from UserComponentContainer (previously called NoUpdate)

It was because we were rending the user component on mount to a div that the NoUpdate component was mounted. We still do that but not rerender on component update, which seems to work fine.


merge package from arlac77/npm-package-template

package.json

chore(devDependencies): add rollup-plugin-babel:^3.0.4 from template
chore(devDependencies): add babel-preset-env:^1.6.1 from template
chore(devDependencies): update semantic-release:^15.2.0 from template

:tada: This PR is included in version 1.0.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


creole markup rendering on github is broken, leaving 404 urls

Some links like the one in Readme.creole:
Metatrader using OTMql4Py (https://github.com/OpenTrading/OTMql4Py).

Leave the closing ) as part of the url.  Then the url
https://github.com/OpenTrading/OTMql4Py)

Is 404,
Could we switch to an alternate creole url syntax or leave a space after url end to mitigate the broken url issue?

Maybe you might write an issue here https://github.com/github/markup/issues

Github's creole is really broken: the rendering of creole in the wiki is different from the rendering of the top-level README.creole. I have some work arounds for the README that I've done another pass on, so it should be better now, but it really needs fixing at their end.
Thanks femtotrader for the link - I was looking for the repository for the creole rendering so I could take a look at the code. I'll look again for it or if you find it please add it here. The problem is, I can't see why the rendering is different (better) in the wiki than the top-level!

A trailing space after the link works around it - they all should be OK now. The page won't change much now.
The README.creole file is a copy of FrontPage.creole in the wiki, with a sed script to try to work around the brokeness. In the wiki, things work OK, even though their implementation is lame.
Thank you for your help catching these details as it makes the project look bad with broken URLs.

I think these are all fixed, but I'll leave the issue open to remind me to track down a simple case to submit a bug report to github.


5.2 backwards compatability

This fixes backwards compatability with api-version 13 (appliance version 5.2). Api-version 13 does not have support for dev-keyring, so preparing an upgrade image on appliance version 5.2 would fail because of this.. This fixes it by:

only setting the dev-keyring value for the prepare request if it is true
Checking the api-version in the prepare command and setting dev-keyring to false if it v13 or below.

E2E: https://got-testrail.agi.appgate.com/index.php?/plans/view/1027353


Change DB structure, modify DM methods, Adjust all functionality and tests

Coverage decreased (-7.3%) to 66.541% when pulling b41d73655a48a0f1947a6181e784914f4f179178 on changedb into ce48264940c89adc529e884be421d2b49c423a69 on master.


Resourcegraph

Pull Request Description
What issue does this change request address?
#163
What are the significant changes in functionality due to this change request?
This PR implements the ability to create a resource graph png during a debug mode run

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass.
[x] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large tes.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added, the the analytic documentation must be updated/added.
[x] 9. If any test used as a basis for documentation examples have been changed, the associated documentation must be reviewed and assured the text matches the example.

Here is what the plots look like:

@dgarrett622 are you available to finish the review of this PR?

Everything looks good to go. I'll get this merged in momentarily. Thanks @j-bryan and @dylanjm!


Provide initial manifest.yaml

Description
This is the result of the conversion of our composition into a k8s manifest.
It was created live in yesterdays k8s session with some @GeeksCAT/arch-ci folks :)
Considerations
Understand this as an initial manifest that just describes our composition.

current entrypoint is the same than in our composition, in short-term should be moved to a uwsgi server
base env definition has been integrated with the .env.dev.sample values. It can be patched without effort
SSL layer has not been defined (k8s cert-manager is not yet ready) //WIP
no persistence has been applied to the DB (see proposal of discussion below)

Some further discussions should be placed regarding:

How to deal with the DB (so far integrated as an embeded service inside the namespace)
Integrate our fronted (frontoffice and backoffice) or wait for some functionality

Fix #29
How to deploy it
export NAMESPACE=apf-dev
kubectl create namespace $NAMESPACE
kubectl apply -n $NAMESPACE -f manifest.yaml

Code formating
done

Many thanks for the review @jbagot, I agree in all suggestions. For me this is just an starting draft that should be improved. All this points from my perspective doesn't block us, right?
If you want feel free to push to this branch, if not I will work on it tomorrow night or monday morning.
What about the discussions that I propose?
Maybe we should start the conversations about the DB, this is an stopper decision that should be placed ASAP.

Proposed changes has been amended

[x] manifest.yaml has been splitted into small chunks grouped by functional scope
[x] credentials are deployed as a Secret

Additionally,

[x] ingress is k8s 1.18+ compatible
[x] ingress uses SSL/TLS layer

Start script used in the entrypoint has not been changed, I think that is better to modify it in another PR
I think that this could be a good starting point to go forward with the Helm Chart definition


Unable to create LXC: 403 Forbidden

I'm unable to create a new LXC with v3.0.1-rc3. I get a 403 response, even though I'm using a role with every single permission (essentially Administrator - I tried it with the Administrator role, too), with username & password authentication. No OTP.
Output:
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # module.lx-container.proxmox_lxc.lx_containers["test-lxc"] will be created
  + resource "proxmox_lxc" "lx_containers" {
      + arch         = "amd64"
      + cmode        = "tty"
      + console      = true
      + cores        = 4
      + cpulimit     = 0
      + cpuunits     = 512
      + hostname     = "test-lxc"
      + id           = (known after apply)
      + memory       = 8192
      + onboot       = true
      + ostemplate   = "local:vztmpl/docker-debian-bookworm.tar.gz"
      + ostype       = "debian"
      + password     = (sensitive value)
      + protection   = false
      + start        = true
      + swap         = 0
      + tags         = (known after apply)
      + target_node  = "my-pve"
      + tty          = 2
      + unprivileged = true
      + unused       = (known after apply)
      + vmid         = (known after apply)

      + features {
          + fuse    = false
          + keyctl  = true
          + mknod   = false
          + nesting = true
            # (1 unchanged attribute hidden)
        }

      + network {
          + bridge   = "vmbr0"
          + firewall = false
          + gw       = "<IP_ADDRESS>"
          + hwaddr   = (known after apply)
          + id       = (known after apply)
          + ip       = "<IP_ADDRESS>/24"
          + name     = "eth0"
          + rate     = 0
          + tag      = (known after apply)
          + trunks   = (known after apply)
          + type     = (known after apply)
        }

      + rootfs {
          + size    = "32G"
          + storage = "local"
          + volume  = (known after apply)
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

module.lx-container.proxmox_lxc.lx_containers["test-lxc"]: Creating...
╷
│ Error: error creating LXC container: 403 Forbidden, error status: {"data":null} (params: {"arch":"amd64","cmode":"tty","console":true,"cores":4,"cpulimit":0,"cpuunits":512,"features":"nesting=1,keyctl=1","hostname":"test-lxc","memory":8192,"net0":"name=eth0,bridge=vmbr0,ip=<IP_ADDRESS>/24,gw=<IP_ADDRESS>","onboot":true,"ostemplate":"local:vztmpl/docker-debian-bookworm.tar.gz","ostype":"debian","password":"admin","pool":"","protection":false,"rootfs":"local:32","start":true,"storage":"local","swap":0,"tags":"","tty":2,"unprivileged":true,"vmid":110})
│
│   with module.lx-container.proxmox_lxc.lx_containers["test-lxc"],
│   on modules/lx-container/main.tf line 33, in resource "proxmox_lxc" "lx_containers":
│   33: resource "proxmox_lxc" "lx_containers" {
│
╵

TF Code:
resource "proxmox_lxc" "lx_containers" {
  for_each = var.lx_containers

  target_node = "my-pve"

  hostname = format("%s-lxc", each.key)

  ostemplate = "local:vztmpl/docker-debian-bookworm.tar.gz"
  ostype     = "debian"
  arch       = "amd64"

  password     = "admin"
  unprivileged = true

  cores    = each.value.cores
  cpuunits = lookup(var.cpuunits_by_priority, each.value.priority, 100)
  memory   = each.value.memory
  swap     = 0

  start  = true
  onboot = coalesce(each.value.onboot, true)

  features {
    nesting = true
    keyctl  = true
    fuse = coalesce(each.value.enable_fuse, false)
  }

  rootfs {
    storage = "local"
    size    = each.value.disk_size
  }

  network {
    name     = "eth0"
    bridge   = "vmbr0"
    ip       = format("%s/%s", each.value.ip_addr, "24")
    gw       = "<IP_ADDRESS>"
    firewall = false
    rate     = coalesce(each.value.net_rate, 0)
  }

  lifecycle {
    ignore_changes = [
      ostemplate,
    ]
  }
}

with
lx_containers = {
  "test" = {
    cores     = 4
    priority  = "medium"
    memory    = 8192
    disk_size = "32G"
    ip_addr   = "<IP_ADDRESS>"
  }
}

On that note, I'm not really a terraform expert, but can I roll back to v2 without any issues?

It's not definite, but you might consider using the root username and password instead of an API token.
https://registry.terraform.io/providers/Telmate/proxmox/latest/docs#creating-the-connection-via-username-and-password

@im6h I (think) I tried that in my desperation, and it did not work for me.

I guess you need to comment and try each block code features, network, lifecycle. In my case, I encouraged this issue with mountpoint block because it is not permitted by apis of the proxmox.


⚠ ClamAV has degraded performance

In efd131d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 65 ms

Resolved: ClamAV performance has improved in fbc344c.


Adapt new and existing package metadata as SPDX relationships

SPDX has the concept of relationships that can be applied to packages, files, or other artifacts. This issue aims to explore what existing metadata can be expressed via SPDX relationships as well as potentially add more metadata to collect via the catalogers that can be expressed as SPDX relationships.
Internal to syft there is already the concept of package-to-package relationships, what isn't clear is if this should be further expanded generally or isolated only to the SPDX presenter (which is generally a new concept, since all data typically gets expressed via the JSON model first).

I've been doing research on this since Friday afternoon and this AM. The first questions I have concerns this repository:
https://github.com/spdx/tools-golang
The library is hosted by the spdx organization and defines roughly the same model we do in presenter/packagers/model/spdx22.
If we want to express SPDX relationships for 2.2 correctly I think the first discussion should be around if we move to their model or keep our presenter model.
The tough part with this proposal is that their model is not designed as a presenter (no JSON tags).
They take a pretty interesting approach as far as marshalling/unmarshalling.
Check out their parsing code here.
@wagoodman if you have time today can we talk a bit about the complexity of juggling our JSON model against the spdx tool model and then wrapping that into a "correct" presenter?

One thing of note: I think CycloneDX also has a way of specifying dependencies using a bom-ref: https://cyclonedx.org/use-cases/#dependency-graph so we would quite possibly want this handled somehow in our own model

Added - https://github.com/anchore/syft/pull/507 as a starting point to build out the initial ROOT --> Package relationships

https://github.com/anchore/syft/pull/507/files has been updated to now populate Files and include vertices between Packages and Files in the Relationships field

Before we dig further into relationships it's probably worth tackling some of the prioritized bugs we have surrounding SPDX. I pulled in https://github.com/anchore/syft/issues/460 to make some progress in cleaning up our license section.

@luhring The next steps for making this better is starting to dive on the architecture changes we talked about on Monday.
https://github.com/anchore/syft/issues/516
We'll work on refining this issue so we have a clear path to get syfts command API in the right place.

I've broken out package relationships into https://github.com/anchore/syft/issues/572 such that package catalogers raise this information before presenters/formats can leverage them (such as SPDX).


Support any name of AvailabilitySet

Azure teams gave us different name of AvailabilitySet. Sometimes it is hard to rename it under pinning condition. Can LISAv2 support variable AvSet name?

Could you please clarify detailed requirement? you mean specify the AVset name as parameter when run LISAv2, or generate a random name in code? Or you need run tests against existed environment with a different AVset name?

Introduce a new parameter, -UseExistingAV, then it will use the same named one in the existing EG. This parameter should be dependent on -UseExistingRG.
a) If it is with -UseExistingRG,

If it is with -UseExistingAV, then it should use the existing AVSet in the specific RG.
Otherwise, it will use the existing RG but it can create the default AVSet, AvailabilitySet.
b) If it is NOT with -UseExistingRG, -UseExistingAV should be used.

It is not about "creating a new AVSet". It means, it comes out above condition a)-1), but if there is no that named AVSet, the test run-time should be terminated. a)-1) case also has AvailabilitySet exists in the RG already.

https://github.com/LIS/LISAv2/blob/master/Libraries/Azure.psm1#L860 will use existed AV in existed RG when run .\Run-LisaV2.ps1 with -UseExistingRG
https://github.com/LIS/LISAv2/blob/master/Libraries/Azure.psm1#L419 will make sure the AV is not deleted


'NoneType' object has no attribute 'Extension'

Hi,
Following for the previous issue, I made sure that time that pywin32 and virtual env are active.

And that's the picture inside the folder

And that's the error.

Yup I'm getting the same issue. Just trying to test out a few different ways to hit the solid works api through python

Use this code :
`import sys
import time
import asyncio
import pythoncom
import win32com.client
Solidworks Version (write the year):
SWV = 2023
API Version
SWAV = SWV - 1992
Elapsed time
elapsed = 0
async def main():
# Attempt to connect to SolidWorks
try:
sw = win32com.client.GetActiveObject("SldWorks.Application")
except:
print("Failed to connect. Launching a new instance.")
sw = win32com.client.Dispatch("SldWorks.Application")
sw.Visible = True
if not sw:
    print("Failed to connect or launch SolidWorks")
    return

print(f"Solidworks API Version: {SWAV}", "\n", f"Solidworks Version: {SWV}")

Model = sw.ActiveDoc

if Model is None:
    print("No active document found. Creating a new document...")
    # Create a new part document (you can change the document type)
    partTemplate = "C:\\ProgramData\\SOLIDWORKS\\SOLIDWORKS " + str(SWV) + "\\templates\\Part.prtdot"
    Model = sw.NewDocument(partTemplate, 0, 0, 0) # You can adjust the last three parameters as needed

ARG_NULL = win32com.client.VARIANT(pythoncom.VT_DISPATCH, None)
ck = Model.Extension.SelectByID2("Front", "PLANE", 0, 0, 0, False, 0, ARG_NULL, 0)
Model.SketchManager.InsertSketch(True)
Model.ClearSelection2(True)

mySketchText = Model.InsertSketchText(
    0, 0, 0, "Hello Python World!", 0, 0, 0, 100, 100
)
myFeature = Model.FeatureManager.FeatureExtrusion2(
    True,
    False,
    False,
    0,
    0,
    0.001,
    0.001,
    False,
    False,
    False,
    False,
    0,
    0,
    False,
    False,
    False,
    False,
    True,
    True,
    True,
    0,
    0,
    False,
)

Model.SelectionManager.EnableContourSelection = False
Model.ClearSelection2(True)
s = time.perf_counter()
elapsed = time.perf_counter() - s
print(f"{__file__} executed in {elapsed:0.2f} seconds until while-loop")
time.sleep(2)
while True:
    Model.ViewRotateplusy()
    time.sleep(0.1)

If running as a script, execute the main function
try:
if name == "main":
asyncio.run(main())
except KeyboardInterrupt:
sys.exit()
`
If Solidworks is not open it open it
If there is no open part open it create a new part
Then it write Hello Python
If you are not using Solidworks 2023 change the year at the beginning of the code


Shipping label not generated when changing carrier in shipment method card

Current behavior
When changing the carrier in the Shipment Method card from the order details page, the shipping label does not get generated if the shipment method remains the same. This issue affects the workflow by preventing the generation of the correct shipping label after a carrier change.
Expected behavior
The shipping label should be generated correctly when the carrier is changed in the Shipment Method card, regardless of whether the shipment method is the same
Steps to reproduce the issue

Navigate to the order details page.
Change the carrier in the Shipment Method card.
Attempt to generate the shipping label.
Observe that the shipping label is not generated.

Can you handle fixing this bug by yourself?

[ ] YES
[x] NO

Environment details

Browser: Chrome
OS: IOS, Version 14.4.1
Code Version: Dev version of the App.

Additional information
Jam: https://jam.dev/c/15249429-3142-403f-8176-7f12fd5ff9bf

Verified and working fine in release v2.7.2. Hence, closing it.


Allow connecting to more than one chat simultaneously

Currently you can have only one chat per websocket connection.
This is limited in internal/agent/agent.go where Agent struct holds single Chat.
On client, this currently works by connecting to new chat and disconnecting from previous one each time a different chat is clicked. But this prevents getting messages from other chats, although you can still show number of unread messages by invoking the unread count endpoint.

https://nats-io.github.io/docs/developer/concepts/seq_num.html
At the bottom it mentions a nice pattern.
So you can have many chats this way with the one connection i think.


Upgrade ESLint to v9

Clear and concise description of the problem
Upgrade ESLint to v9
Suggested solution
https://eslint.org/docs/latest/use/migrate-to-9.0.0
Alternative
No response
Additional context
No response
Validations

[X] Follow the Code of Conduct.
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

wip


Consider merging with an existing list

It looks like @KevinColemanInc's list (https://github.com/KevinColemanInc/awesome-privacy) exists longer. Why not contribute to that?
See also https://github.com/pluja/awesome-privacy/issues/24

Most privacy lists I found on GitHub were rather limited (few categories), so that's why I decided to create a broader and more diverse list with software of all horizons (graphic design, video editing, web development, mobile security…).
But why not merge with other lists in the future if they're interested.


Origin/dockerfile improvements

Adding packages to dev and prod containers to support large-scale training on less inodes.

@cssprad1 skipping review for this commit since its only artifacts to the dev and prod containers. Merging from feature branch to develop.


docs.pachyderm.io redirecting incorrectly

docs.pachyderm.io is redirecting to a 404

should be fixed now.


.env file for secrets

Is your feature request related to a problem?
No.
Which solution do you suggest?
Store secrets in .env file.
Which alternative solutions exist?
or some yaml file.
Additional context

/kind feature

Have you tried variables in devspace.yaml yet? https://devspace.sh/cli/docs/configuration/variables/basics
They are either read from environment variables or from user input. In case of user input, they are actually stored in .devspace/generated.yaml. You can also set them before deployment using this command: devspace set var https://devspace.sh/cli/docs/commands/devspace_set_var
Let me know if that helps you to do what you're trying to achieve.

@0x77dev Were you able to solve this using config variables?

Closing this for now. Feel free to reopen if there are any unresolved issues.


GH-2044 store cardinality in query model node

Related GitHub issue: #2044
Briefly describe the changes proposed in this PR:

introduce getter and setter for cardinality in QueryModelNode
default implementation in AbstractQueryModelNode
include cardinality in signature for StatementPattern

prints StatementPattern ( cost=1 ) instead of just StatementPattern

Eg:
Projection
   ProjectionElemList
      ProjectionElem "name"
      ProjectionElem "mbox"
   Filter
      Regex
         Str
            Var (name=mbox)
         Var (name=pattern)
         Var (name=flags)
      Join
         StatementPattern ( cost=1 )
            Var (name=y)
            Var (name=_const_2c03e873_uri, value=http://example.org/ns#pattern, anonymous)
            Var (name=pattern)
         Join
            StatementPattern ( cost=1 )
               Var (name=y)
               Var (name=_const_144ac82a_uri, value=http://example.org/ns#flags, anonymous)
               Var (name=flags)
            Join
               StatementPattern ( cost=3 )
                  Var (name=x)
                  Var (name=_const_23b7c3b6_uri, value=http://xmlns.com/foaf/0.1/name, anonymous)
                  Var (name=name)
               StatementPattern ( cost=3 )
                  Var (name=x)
                  Var (name=_const_23b75369_uri, value=http://xmlns.com/foaf/0.1/mbox, anonymous)
                  Var (name=mbox)

It seems that we never explicitly generate a cardinality for the join operations.

Going to fix the tests if you agree with this PR in general @jeenbroekstra .

I'm not really sure I do, to be honest. Why would you want to make the cost estimation part of the algebra model itself?

Also: I hate to have to keep bringing this up, but could you please fix your branch name? No issue/ prefix, and use dashes instead of underscores (at least for the first one after the issue number, otherwise github doesn't recognize/hotlink it in the UI).

I still have trouble with this - the fact that it is not fully backward compatible doesn't sit well with me. I'm also not sure how useful this information really is to end users. The point of the cardinality is really to have an internal mechanism to make some sort of 'best guess' ordering of the expression tree. In and of themselves the numbers don't have any meaning, and the result of the numbers (that is, the ordering) can already be seen just by looking at the difference between the original tree and the optimized tree.
So the question is: what problem is this solving?

Pretty much every other query plan out there that I have seen exposes the cost model. It’s a natural thing for an advanced user to look at when trying to optimize a query.
Consider it an annotation. It’s a lot simpler and smoother adding an annotation inside the java object rather than having a hashmap or something else to store the annotation externally.

Pretty much every other query plan out there that I have seen exposes the cost model. It’s a natural thing for an advanced user to look at when trying to optimize a query.

It does mean we'll need to do some documentation to explain this. As I said: the numbers in themselves are meaningless. We'll need to provide guidance on how to interpret them.

Consider it an annotation. It’s a lot simpler and smoother adding an annotation inside the java object rather than having a hashmap or something else to store the annotation externally.

I fully agree it's easier. But that doesn't make it any less backward incompatible, unfortunately.
Note that this is not insurmountable obstacle - if this is the best way to do it, then let's do it this way. I'm starting to come around to the idea that this is a useful thing to further develop (I'm getting to the age where everything new is initially just "obviously wrong" - it sometimes takes me a while to get over that ;)).  It just means we'll need to schedule it for 4.0 instead of 3.2.

(I'm getting to the age where everything new is initially just "obviously wrong" - it sometimes takes me a while to get over that ;)). It just means we'll need to schedule it for 4.0 instead of 3.2.

Could say the same for myself and branch naming :P
If I give the interface methods a default implementation it should be backwards compatible since for anyone else implementing them it would be optional to implement those two methods.
Maybe we should go all in though and implement support for something along the lines of what PostgreSQL does.
Example from PostgreSQL
Seq Scan on tenk1  (cost=0.00..458.00 rows=10000 width=244)

0.00: Estimated start-up cost. This is the time expended before the output phase can begin, e.g., time to do the sorting in a sort node.
458.00: Estimated total cost. This is stated on the assumption that the plan node is run to completion, i.e., all available rows are retrieved. In practice a node's parent node might stop short of reading all available rows
10000: Estimated number of rows output by this plan node. Again, the node is assumed to be run to completion.
244: Estimated average width of rows output by this plan node (in bytes).

The costs are measured in arbitrary units determined by the planner's cost parameters.
Copied from the PostgreSQL documentation: https://www.postgresql.org/docs/10/using-explain.html#USING-EXPLAIN-BASICS

If I give the interface methods a default implementation it should be backwards compatible since for anyone else implementing them it would be optional to implement those two methods.

If that were possible it'd be great, but one of your methods is a setter. Bar throwing a NotImplementedException there's not really any way to provide a default for it.

ObNag: Don't forget to use squash and merge when you're merging this PR :)

I linked this PR with the corresponding issue but then I realized that there is no corresponding issue for this PR - it is related to #2044 but doesn't solve the full issue. So took the link off again.


Upgrade to Gradle 5.2.1

Adjust to new names and locations of TaskExecutionPlan and TaskInfo
which are ExecutionPlan and TaskNode in Gradle 5.2.1.
https://github.com/mmalohlava/gradle-visteg/issues/12

@hugares Thank you for contribution!

Thanks for getting my change in.
Would it be possible to do a release?

is there a release ?

not yet.
@mmalohlava can you do a release please


The standalone program pfio_MAPL_demo.F90 write several time record…

…s of 2D and 3D arrays.
PFIO utility methods are used to:

Define dimensions
Create variables and set variable attributes
Set global attributes
Write out data in netCDF files (same collection).

The program has an initialization section and a time stepping section to mimic
the steps needed in a real application.

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Trivial change (affects only documentation or cleanup)

Checklist:

[ ] I have tested this change with a run of GEOSgcm (if non-trivial)
[ ] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[ ] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

@JulesKouatchou First, I rebased this PR as it should be against develop not against main as we usually only take hotfixes to the library against main (changes to tests usually aren't considered hotfixes).
Second, it looks like pfio_MAPL_demo.F90 was changed recently due to changes in MAPL (how we handle command line options) since you made your branch. I've tried to make right edits and merge develop into your branch  to fix the conflict. Can you please check to see if the code is still good.

The file is not new.  I changed it after we changed the FlapCapOption to FlapCLI. That is why there is conflict.

@mathomp4 Do you still want me to check the file? I know that it is a little different than the original one created by @weiyuan-jiang but it does the same thing.

@mathomp4 Do you still want me to check the file? I know that it is a little different than the original one created by @weiyuan-jiang but it does the same thing.

If you don't see anything big, probably no need, but could you add an entry to the CHANGELOG.md about this? Most MAPL PRs require changing the CHANGELOG to be accepted (if non-trivial)

I have tested it and it is good to merge.  I am wondering why I cannot approve this PR. @mathomp4