Has the ability to create a TFS Branch been removed?

I can't seem to figure out how to create a new TFS branch with the TeamFoundation libraries.  These samples show how to do it with the git but not TFS.
Microsoft.TeamFoundationServer.ExtendedClient version 14.83.0 has VersionControlServer.CreateBranch and you get the VersionControlServer from the TfsTeamProjectCollection.  These are gone in the current 16.143.2 version.  In fact, they seem to be gone as early as 14.83.1.  Strange that it's removed in such a minor version and it's not in the release notes.
Can I programmatically create a branch?

I think they just moved it to another assembly. It's in Microsoft.TeamFoundation.VersionControl.Client for the nuget package version 15.131.1.

@chambersDon my team did pretty in depth research about the branch creation of a TFS branch and we were unable to do so.
There might be a possibility loading that DLL in a powershell script and running that but that still uses the CreateBranch method in the older DLL.

Microsoft removed this option in the new Rest API model :/
You can do it only with the old dll.


Revoke active access token when unsharing a shared app

Purpose
When unsharing a shared app, the access token associated with the shared app will be revoked with this effort.

 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.4 out of 5 committers have signed the CLA.:white_check_mark: ChanikaRuchini:white_check_mark: ShanChathusanda93:white_check_mark: mpmadhavig:white_check_mark: dewniMW:x: wso2-jenkins-botYou have signed the CLA already but the status is still pending? Let us recheck it.

Tracked with https://github.com/wso2/product-is/issues/19280


to_proc and unary & for symbols

Symbol#to_proc and &:symbol to create a Proc that takes a single argument and calls the named method on it.

Closed by 2539e9246cf8824e59f6a35aa2c4d3b5bd54890f


Some Scripts we are Using as GPO-Replacement

Instead using GPOs want to make it possible to do all with RTMM....

Thanks for the contributions!


Upgrade WW to 0.4.1

Fixes #2327.
This PR mostly consists of fixing unit tests and functionality where we deal with WW logical types since they are now instantiated instead of returning the class.
Perf tests look good with no changes in model performance and somelittle change in init time and fit time but all within a couple percentage points. Ran with 50 iterations and 3 trials.
ww_upgrade_perf_results.zip

FYI I'll file a follow-up issue to use the new functionality added in this release:
Add option to return TableSchema instead of DataFrame from table accessor select method (#916)
Add dropping and renaming columns inplace (#920)

@freddyaboulton can you also add using concat_columns to that issue?

Taking a slight calculated risk and merging this before the docs build completes. We have a lot queued right now. I hope #2404 will help us here!


Added support for Mill 0.10.0-M5

Codecov Report

Merging #44 (bc1536e) into main (dfb1705) will decrease coverage by 48.38%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #44       +/-   ##
===========================================
- Coverage   83.87%   35.48%   -48.39%
===========================================
  Files           2        2
  Lines          31       31
  Branches        2        2
===========================================
- Hits           26       11       -15
- Misses          5       20       +15

Impacted Files
Coverage Δ

.../de/tobiasroeser/mill/vcs/version/VcsVersion.scala
0.00% <0.00%> (-83.34%)
:arrow_down:

Continue to review full report at Codecov.

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


refactor(typescript): refactor to typescript and add typescript example

Description
this is draft PR for refactoring to typescript. almost type is declared as any. If this draft PR match and good thing for @vendia/serverless-express, I will change all any type.
Best wishes.
Checklist
[x] Tests have been added and are passing
[] Documentation has been updated

Hey! This is great! I wish you had created an Issue first to discuss though as we don't plan on making any changes to V3 other than bug/security fixes. We plan on releasing V4 in January. Would you like to convert that to TS?

@brettstack
Thanks for your attention. I make an Issue for Conversion V4 to Typescript. For now, I close this PR.


bump dependencies, npm test passed

Looks like tests are failing b/c html-validator no longer contains the cli, it's been abstracted here: html-validator-cli

hmmmm ... strange, it passed the test locally, I'll take a look at it.

hmmmm ...
$ rm -rf node_modules/
$ npm install && npm test

.
.
.
.
.

      ✓ -> [object Object]
      ✓ -> [object Object]
      ✓ -> [object Object]
      ✓ -> [object Object]
    contains bootstrap
      ✓ -> 3.3.5
      ✓ -> 3.3.4
      ✓ -> 3.3.2
      ✓ -> 3.3.1
      ✓ -> 3.3.0
      ✓ -> 3.2.0
      ✓ -> 3.1.1
      ✓ -> 3.1.0
      ✓ -> 3.0.3
      ✓ -> 3.0.2
      ✓ -> 3.0.1
      ✓ -> 3.0.0
      ✓ -> 3.0.0-noicons
      ✓ -> 2.3.2
      ✓ -> 2.3.2-noicons
      ✓ -> 2.3.1
      ✓ -> 2.3.0
      ✓ -> 2.2.2
      ✓ -> 2.2.2-noresponsible
      ✓ -> 2.2.1
      ✓ -> 2.2.0
      ✓ -> 2.1.1
      ✓ -> 2.1.0
      ✓ -> 2.0.4

  548 passing (1m)

anyway, I updated the PR to add html-validator-cli and see if it pass.

npm test doesn't run the validation that's run on Travis
On Sun, Sep 27, 2015 at 14:33 Peter Dave Hello<EMAIL_ADDRESS>wrote:

hmmmm ... strange, it passed the test locally, I'll take a look at it.
—
Reply to this email directly or view it on GitHub
https://github.com/MaxCDN/bootstrap-cdn/pull/585#issuecomment-143596406.

Okay, thanks. Now it passed build :+1:

Awesome. I'll merge this later today or early tomorrow, thanks for the contribution!

Thanks @PeterDaveHello !


temp-file in own project

This issue is related to #767. The behaviour of #767 happens in files in own projects which import other files from that project. So if such a buffer is not saved, C-c C-g will produce an empty buffer and C-c C-p will produce a "unknown identifier"-error.
Steps to reproduce
(1) Create a new directory foo anywhere (outside any Lean library folder)
(2) Create a file test1.lean in foo, containing definition foo := @eq and save this buffer
(3) Create a project file via the menu bar
(4) Create a file test2.lean in foo containing
import .test1

definition bar : foo 0 0 :=
begin

end

(5) In this buffer the behaviour in #767 occurs. So if you save the buffer test2.lean then C-c C-g and C-c C-p work, but if you modify it without saving, neither command works.
(note: this happens for both .lean and .hlean files)

This happens because lean-mode creates a temporary file, usually at /tmp/xxxx, to process an unsaved buffer (here test2.lean). test2.lean is importing test1.lean which is required to be at the same directory of test2.lean but it's not the case here because we create a temp file only for test2.lean.
I think the option --dir mentioned in https://github.com/leanprover/lean/issues/788#issuecomment-130118017 can be used to solve this problem as well.

@soonhokong @leodemoura : how much effort do you think this fix would take? I've been working on the analysis library a bit, and keep running into this. There was no one-line fix I noticed scanning through the emacs folder, but I don't know quite what I'm looking at. If you think it's reasonably easy/could point me in the right direction, I'll try harder to figure it out.

@leodemoura, could you implement --dir option? It helps close two issues that we have.

@soonhokong I will try

Done it.

@leodemoura, thanks!

@rlewis1988, could you test https://github.com/soonhokong/lean/commit/b4b365239f8c7c1b2075c68bf6cc3fedc442b57a ?

That seems to fix both this issue and #788. Thanks to both of you- this makes things way smoother!

@rlewis1988, thanks for checking it up. I merged my commit to the blessed repo. Thanks @leodemoura!


[Nitpick] StretchPaused doesn't pause

Give an example of what is wrong
The problem is the GainFocusCommand: GainFocusCommand=cmd(play);
Given an example of what it should look like
If should be like this: GainFocusCommand=cmd(pause);
Its OnCommand has :pause() but it gets overwriten by the GainFocus' play()

Funnily enough, this seems to be an upstream bug, with the commands being put into the BackgroundEffects in February of 2007.
This should be fixed in the next hotfix! I'm leaving this open for now, so please re-test when the hotfix releases.

I checked and it now seems to work as intended out of the box (as well as the "no cmd in code" in both Background folders) so this can be closed now.


Revert ami changes for sles tests

What does this PR do?
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable DEPLOY_AGENT=true --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on


☂ - Improved raster cache heuristics for complex pictures

Currently flutter uses a raster cache of Pictures to speed up rendering when the same pictures are rendered frame after frame. Consider, a ScrollView of ListTiles, as you scroll each will be rendered, then raster cached, then evicted once they move off screen.
Currently the raster cache heuristics are tuned such that they work reasonably well with the Material and Cupertino libraries. These same heuristics lead to less than optimal behavior on extremely complex pictures such as SVGs, which can contain 100s or 1000s of drawing commands. These pictures may benefit from different cache heuristics and raster cache behavior, to be described in the issue list below:
Behavior

[ ] Raster cache entires are eagerly evicted if they move offscreen
[ ] Raster cache entries are only cached if they survive for 1+ frames
[ ] Raster cache has a first-come first-served limit on cache entries per frame

Documentation

[ ] Raster cache behavior is under-documented

Tooling

[ ] We lack tooling or documentation on how to use our tooling to determine whether raster cache behavior is appropriate

@flar

cc @chinmaygarde

@dnfield

The first two referenced issues point to the same github issue even though their text describes different problems.

Closing as I don't believe the raster cache is worth working on anymore


Risk and Security plugin

We consider developing a risk and security plugin for Archi. We want to use OpenFair taxonmy to work with properties(attributes in Archimate). The purpose is to feed the repository with structured information about risk and security to be able to create profiles, views, viewpoints, model etc for risk and security reports/dashboards.
If this is of general interest, we will chase funding, develop and share on GitHub.

Hi Thorbjørn, sounds interesting.
(BTW, the XSLT example you made for the ArchiMate exchange format was useful)

Thanks! I have forked and created a branch called risk and security

Can I put the requirements specification as an Archimate model in the repository to collaborate on it? If yes, where should I put it?

Would it be better to open a new git repo in this set of projects?
https://github.com/archimatetool

Best would be inside https://github.com/archi-contribs ;-)

Best would be inside https://github.com/archi-contribs ;-)

Yes, I forgot about that!

So just choose a name for your repo and I will create it and give you admin access on it.

Thanks! Sounds like a good idea. Call it Risk-Security

Done: https://github.com/archi-contribs/risk-security
You've been invited to be part of R/W group associated with this repo.

Thanks!


cmake:fix the problems of using cmake to compile custom board

Summary
1. No config found when reconfig
when reconfiguring a custom configuration, because ${BOARD_CONFIG} uses a relative path, it will cause the following error:
# config first time
cmake -B out -DBOARD_CONFIG=coustom/boards/sim/sim/sim/config/nsh
# run first build for target menucofing
cmake --build out -t menuconfig
# run second build for final build will failed
cmake --build out

2. Generate config.h error
The result of dequote is inconsistent with cfgdefine.c
// config example
CONFIG_INIT_ARGS="\"widgets\""
CONFIG_INIT_ENTRYPOINT="demo_main"

// generated wrong header file
#define CONFIG_INIT_ARGS \widgets\
#define CONFIG_INIT_ENTRYPOINT demo_main

//expected
#define CONFIG_INIT_ARGS "widgets"
#define CONFIG_INIT_ENTRYPOINT demo_main

3. board.h is not linked in the binary directory
fix board.h is not set correctly when using cmake to compile a board with a common directory
Impact
Testing
CI

the CI failure dose not caused by this patch.

the CI failure dose not caused by this patch.

yes, other patch make the break, but it fix. please update your patch to retrigger ci.


[BUG] Azure snapshot backup a file-consistent backup is created and some databases are corrupted.

HCL Product Version
HCL Domino 12.0.2FP1
Describe the bug
When doing an Azure snapshot backup a file-consistent backup is created and some databases are corrupted.
https://learn.microsoft.com/en-us/azure/backup/backup-azure-vms-introduction#snapshot-consistency
Error Message
If an error message is displayed, include details here. Quickly identifying the code causing the error will help to more quickly resolve it.
To Reproduce
Steps to reproduce the behaviour:

Run a Windows Server 2019 Azure Virtual Machine
Run an HCL Domino server on HCL Domino 12.0.2FP1
While the Domino Server is running, Run a Azure Backup by going to the Backup Instance of the VM in the Azure Portal and clicking Backup Now
You can see that backupvss is doing something in the logs but the Azure Backup is still a file-consistent backup instead of a application consistent

Expected behaviour
An Application Consistent Backup is created when performing an Azure Backup with the Domino Backupvss task running and the databases are not corrupted.
Screenshots
Crash Consistent Backups are taken when the server was offline.
Application Consistent Backups were taken when Domino was stopped or running without the backupvss task.
File Consistent Backups were taken when Domino is running
https://learn.microsoft.com/en-us/azure/backup/backup-azure-vms-introduction#snapshot-consistency

Domino Backup Database Configuration
Main Tab:

Backup Tab:

The rest of the tabs are default.
Desktop (please complete the following information):

OS: Windows Server 2019

Additional context
I was asked by HCL Software Customer Support to open a GitHub Issue after I raised a support case with HCL "CS0394460" regarding this issue.
I have tried the following using the backupvss task introduced in Domino 12.0.2:

Take a snapshot without the task running but the Domino server was running (caused an application consistent backup but log.nsf was corrupted so it was not a reliable backup)
Take a snapshot while the task was running and the Domino Server was running (caused a file consistent backup but a delta file was created for log.nsf and ddm.nsf based on the backup configuration in dominobackup.nsf)
Take a snapshot with "USEVSSCOPYBACKUP"="TRUE" set in the Windows registry and excluded log.nsf and ddm.nsf from the configuration file (caused a file consistent backup but no delta files were created)

I could not see anything in Azure, event viewer, ddm, or log.nsf that showed that the backup had any errors.
I am expecting that the backups should be application consistent as this means that all vss snapshots succeeded. https://learn.microsoft.com/en-us/azure/backup/backup-azure-vms-introduction#snapshot-consistency
Where is the VSS_VOLSNAP_ATTR_AUTORECOVER set? Is it on the virtual machine or on the application that creates the snapshot? Also, How would I be able to verify if this option is set?

If the above is not possible, would you be able to tell me what the best practice is for creating a backup of the Domino Data directory on Azure Virtual Machines, preferably using snapshot backups and storing the backups in Azure, please?

First of all the platform needs to support application consistent snapshots. Sadly we had no chance to fully test it on our own.
At the time I looked at it The platform wasn't able to handle application consistent snapshots.
The VSS back end would be responsible to call the right VSS back-ends to have Domino backupvss be trigged in the right way.
Can you enable debugging via load backupvss -d and keep the console open?
The console will write the VSS events from the VSS back-end to the console. Those logs only show on the console, because the code called in those back-ends are not Domino thread initialized (because they are back-end VSS callbacks).
I need the VSS events to see what the Azure platform uses in that way. You UI indicates you had some backup invocation, which might have triggered application aware backup. others didn't for sure.
The logs would be the first step.
Domino backup really just implements the VSS back-end we can't try all environments on our own, know know how to configure them on the platform side. Like Azure. You are the first one to try it.
We for sure want to understand this scenario, want to get it work and share it with others later!

If an application does not perform application aware snapshots, backupvss should automatically write the delta files and leverage your configuration. In this type of configuration beside the snapshot backup your file backup would be used. Only the snapshot and the delta would work together on a restore and you have to take care of backing up the delta files.
In your case you are excluding log.nsf and ddm.nsf. This will cause the databases to not write their delta logs, even their full backup is in the snapshot.
I hope this clarifies how it works?

Hi Daniel,
Ill give running load backupvss -d a go and come back to you when I have the results.
When the log.nsf and ddm.nsf were not in the list I could see the delta files being created, however, how would I be able to restore the snapshot and delta files to restore those 2 files and potentially any other files affected?
I am still a bit confused on the Application Aware snapshots, how do I know if the application, I guess in this case Azure, is application-aware or even has the auto-recovery option enabled (VSS_VOLSNAP_ATTR_AUTORECOVER).
https://help.hcltechsw.com/domino/12.0.2/admin/admn_vsssnapshots.html

what is confusing here?
the VSS auto recovery option is part of the VSS API.
the application needs to support it. when you include the database and the .delta files are not created, databases in use, are inconsistent.
the application aware snapshot offers to backupvss to mount the snapshot after the snapshot to add delta data.
so databases are consistent in the snapshot.
if a backup application does not support auto recovery snapshots, Domino backup has to create delta files.
And the restore operation needs to have access to those delta files during restore.
The restore integration needs to have access to the delta files.
This is working as intended and there is no other way.
When I took a quick look into Azure I did not see any auto recovery snapshots. That was quite a surprise, because VSS is a core Windows functionality from Microsoft.
Probably in the logs we will see that no post snapshot event occurs and Domino backup has to create the delta files as described.
You can't just exclude the files to not get delta files, to work-around that.
One of the logs from the Azure side looked like there is a auto recovery snapshot in some of the backups.
Can you raise this at Microsoft? I can't help you on the Azure side.
-- Daniel

Thanks for the logs. The output of the VSS part are only written via printf, because no Domino code can be used.
We could potentially proxy those error messages to the Domino side of backupvss and print it.
But it is just intended for troubleshooting and not used in normal cases.
The -d added the following type of log output:
DominoVSSWriter::OnPostSnapshot Post backup changes applied after 1 seconds.

And we are missing the auto recovery part! The VSS back-end does not provide the snapshot to mount it for writing.
So we cannot create an auto recovery snapshot.
You have to check with the provider to see if and how this can be enabled.
sYour screenshot contains different data than the log you send.
Side note: Can you please only send text instead of graphics in future. It would be much easier to handle.
In the screenshot case there is a delta file created and it should be also written. else you should get an error message.
In the other test there was no delta file, which was created. No database needed one.
I noticed another error in your log:
BackupVSSCompletedTimeUpdate: Error opening backup result log document: Entry not found in index

This error occurs when the backup complete time is happening earlier than expected. Normal backup snapshot applications take some time to write the snapshot data to a back-end location. In this case nothing is copied and they immediately return.
We had this with another backup provider and this issue is just failing the final update of the backup complete time into the log.
There is a SPR, which is fixed in V14 and also in 12.0.2 FP2 coming up this month.
I would need more information to understand why your one delta file was not written. in case of an error, you should see an error message.
For the auto complete snapshot you really need to speak to your vendor. I can confirm we are not receiving the volume information in the OnPostSnapshot event.
If you want to pass details to them, here is a link:
https://learn.microsoft.com/en-us/windows/win32/api/vswriter/nf-vswriter-cvsswriter-onpostsnapshot
See the section mentioning VSS_VOLSNAP_ATTR_AUTORECOVER
I hope this helps for the next steps?
Daniel

Hi Daniel,
Thank you for your reply.
I have sent the Cloud Providers the details from your previous reply and they have escalated it to Microsoft.
Regarding the BackupVSSCompletedTimeUpdate: Error opening backup result log document: Entry not found in index error, is it correct to assume that this will be fixed in HCL Domino Server 12.0.2 FP2?
Also, for these tests, I changed the Log On As for the HCL Domino Server Service to be Local System Account as the DominoSvc User Account we created to run the HCL Domino Service was failing to start the Domino Backup Writer, see logs below:
Im not sure whether this should be in a separate issue or not?
load backupvss -d

[262C:0002-2630] 14/07/2023 09:35:35   BackupVSS: Domino Backup VSS plug-in started
[262C:0004-2640] 14/07/2023 09:35:35   BackupVSS: CVssWriter::Initialize failed
[262C:0004-2640] 14/07/2023 09:35:35   BackupVSS: Domino Backup VSS plugin
BackupVSS: DominoVSSWriter::DominoVSSWriter called
BackupVSS: DominoVSSWriter::~DominoVSSWriter called
BackupVSS: DominoVSSWriter::Uninitialize called
[262C:0002-2630] 14/07/2023 09:35:38   BackupVSS: Domino Backup VSS plug-in shutdown

I suspected it was due to permissions as I could see in the Application Event Log:
Volume Shadow Copy Service error: The process that hosts the writer with name Domino Backup Writer and ID {dee12323-b0ce-4f3d-8d3a-68062f1c53cc} does not run under a user with sufficient access rights. Consider running this process under a local account which is either Local System, Administrator, Network Service, or Local Service.

Operation:
   Initializing Writer

Context:
   Writer Class Id: {dee12323-b0ce-4f3d-8d3a-68062f1c53cc}
   Writer Name: Domino Backup Writer

How could I get the DominoSvc local user account to be able to work with the backupvss task?
I have tried adding the local user account to the Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl as a DWORD and gave it permissions to the Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Diag folder.
This allowed the Domino Backup Writer to successfully run but when running the Azure Backups no logs were being generated and in the event viewer I could see the below Error:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {dee12323-b0ce-4f3d-8d3a-68062f1c53cc}
   Writer Name: Domino Backup Writer
   Writer Instance ID: {4bc61f16-390b-4832-b910-370681d15831}

I have tried the below but none have succeded:

Added the System and Network Service the registry
Added the DominoSvc account to the Backup Operators group
Added the DominoSvc account to the COM Security for "My Computer" in Component Services
Added the DominoSvc account to the Volume Shadow Copy Service, component service with local launch and activate permissions

Please let me know if there are any issues.

Ohh just checked. The issue with the update of the backup finished time  did not make it into FP2. It's planned for 12.0.2 FP3 and is addressed in Domino V14 EA2 (SPR #DNADCSBHWZ).
I don't think this is a permission problem. you really need to work with Microsoft to get this resolved. The VSS writer does not have any information about the snapshot. the event is not called. The writer can't do anything about it. It's a matter how the VSS snapshot is created.

Hi Daniel,
I am still working with Microsoft support to look into this issue, would you like me to keep you up to date with what I am communicating with Microsoft?
Also, I enabled vss debugging unsure if that is helpful but I also noticed that after running vssadmin list writers after the backup was complete I saw that the WMI Writer had timed out but the Domino Backup Writer did not error, please see files attached.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/backup-and-storage/enable-debug-tracing-features-vss
20230718 Test Azure Backup With load backupvss -d.txt
20230718 vss snapshot trace.txt
20230718 vssadmin list writers before and after.txt

Yes please keep me updated on feedback from Microsoft. But I don't think we look into traces on our own until Microsoft replies with something that needs us to research.
We need them to support auto recovery snapshots. And it does not look like they do at least in this environment.
I tried it with Hyper-V earlier and I also did not get auto recovery snapshots work.
The interesting part here is that VSS, Hyper-V and Azure are Microsoft applications, which should fully support each other...
-- Daniel

Hi Daniel,
I have attached the response from Microsoft, also are you aware of when the 12.0.2FP3 is planning on being released?
Reply from microsoft.pdf

Thanks for the info.
It does not make sense to discuss with them the details of the Domino feature.
The Domino VSS writer will use the snapshot when it is presented via the PostSnapshot event.
The caller of the VSS snapshot/backup is responsible for using the right options to make it a consistent snapshot.
This is usually the case for most applications like Veeam and others. But it looks like neither Azure nor Hyper-V use this option.
Even the very simple Windows server backup application supports application aware snapshots.
But this isn't the default. The calling applications is responsible for setting the right parameters.
The info from Microsoft is a first answer, but this isn't really fully helpful.
It's their responsibility to use the right options when creating the snapshot.
The dominovss task just consumes the calls from the VSS back-end.
And it dumps what it receives.

Hi Daniel,
I think I created a misunderstanding with them regarding the type of file extension the database is as it is a NSF rather than NFS, I will wait for their reply.
20230720 Reply from Microsoft.pdf

The snapshot is not generated in the right way. and it looks like they don't know their own VSS technology. I added all the details about it from API perspective. I don't say VSS technology or the API is easy.. But it's pretty interesting that you as a customer have to raise issues with different teams.  I hope you get this resolved. Keep us posted, but I can't do more than describing how it works and how you can look at the logs from Domino side.
The VSS API is implemented as a C++ class with call-backs.
This is all controlled by the VSS back-end.
A backup provider has to use the VSS API in the right way to get the VSS to perform the right operations, which are all handled by the VSS back-end.
-- Daniel

I am changing this from but to help wanted. This does not look like working as intended on the Domino side. We still want to help you and we are in discussion how we can provide information to help backup vendors to have their software to use the right snapshot options.
Please keep us updated what you get back from the vendor.

The beauty of the VSS application consistent snapshots (auto recovery) is that Domino can merge it's deltas directly into the snapshot and close the databases which are still in backup mode during the snapshot.
File consistent backup is not an option for Domino if the database is open. You have to use the backup API and this is what Domino backup does in the back-end for you when VSS triggers the snapshot.

VSS triggers the snapshot
backupvss gets the events and invokes the backup task which brings all databases into backup mode
once done the event continues operations and VSS generates the snaphot
with auto recovery snapshots VSS presents the snapshot to the VSS writers (this is your missing step)
Domino stops the backup mode for all databases and gets the delta data
Domino will then merge the deltas into the databases and also close databases even no delta occurred
Once done VSS makes the final snapshot available to the calling backup initiator

In your case no Auto recovery snapshot is taken and the databases need recovery on restore.
The delta files that occur can be backed up to another place and are used to recover databases later.
You have to apply the delta files and recover databases! There is no other way to make databases consistent.
Everything else isn't supported. Don't let them tell you it is a safe file consistent backup. If it would, we would not need any Domino backup ..
Restoring with delta files and a snapshot is a lot more complicated to configure. Once configured Domino restore would take care of the steps.
You would need Domino restore to look into the snapshots and get a snapshot mounted. and also needs a way to access the matching delta files.
That's the main reasons why we really want auto recovery snapshots. It dramatically simplifies backup and restore operations.
In addition the resulting NSF files in the snapshot are recoverable without Domino!
This is specially important for disaster recovery scenarios.
We are thinking about providing a C++ example how to create an auto recovery snapshot.
HCL has implemented a basic backup module for automation testing purposed and we might be able to make this available for other to look into to understand which components are missing to make a VSS snapshot auto recovery enabled.

Hi Daniel,
Thanks for confirming I have passed the details along, I have started following you on LinkedIn as I was hoping that I would be able to include you in the email trail between me and Microsoft so that you are kept up to date.

Hi Daniel,
I would like to apologise, I have spoken with one of my Managers and he has asked me to park it as I have spent too much time working on this issue. 10 days in total for looking into a backup solution, including the 4 days spent looking at this backup solution using backupvss.
Due to this, I am unable to complete the steps that you have asked me to complete. However, I have asked Microsoft if they would be able to further with you or the HCL Domino Backup team to investigate this further.
Sorry for not being able to assist further.

Sorry to hear you spend that much time. But I must say this isn't a Domino problem.
There is also nothing to work with HCL directly on this. This is basic Microsoft VSS functionality.
The Azure team has to speak with the right team at Microsoft.
VSS is a standard Windows functionality and if an own Microsoft service can't provide Auto Recovery snapshots, there is nothing we can do to help with this type of backup.
You can still use a snapshot with delta files. But this is a bit more complex to implement and we really want VSS with auto recovery snapshots to also allow longer term consistent backup.
Other vendors like Veeam support Auto Recovery snapshots automatically. And even the simple Windows backup application does support it.
I would really like to see that Microsoft supports it in Azure and also with Hyper-V where I also didn't find a way to use it earlier.
This might be the underlying reason why Azure can't support it.
With VSS Auto Recovery, the backup part of Domino could be configured in like half an hour.
Only the optional but good to have directly Notes database driven restore needs some integration.
I am sorry that I can't help in this situation.  I changed the topic of this to not show up as a bug. it isn't a bug on the Domino side from what we can tell.
Can I close the issue if you can't work on it any more?
Thanks
Daniel


The services flipping cards do not seem clickable

What happened?
The services part of the home page has a bunch of listed services that will flip and show a write up but one does not know to click it. I can improve the UI and get the buttons to bolden or change colour or something when the mouse hovers over the button. Please assign me this issue.

How can we reproduce this bug?
I saw this bug while scrolling through the home page
Desktop Information (Optional)
No response
Urgency (Optional)
Medium priority

Hey Kaashika , I would love to work on this issue as it's seem interesting on working !!

hi Cipher-08 but I opened this issue so that I may be assigned to work on it :)

issue raised before already


0.22 regression on Windows 11

Detected during manual QA from https://github.com/ipfs/ipfs-desktop/blob/main/DEVELOPER-NOTES.md#manual-testing using release candidate  .exe binary from here on Windows 11.
IPFS Desktop starts, ipfsa-webui window is displayed, but the cube spinner fades in and out until timeout for /api/v0/id is printed to the console.
There is no error, daemon seems to either take log time to start, or fails in a way that is no longer correctly handled.
Needs additional investination, this is blocking 0.22, which has Kubo 0.14.

Since I use Windows only for testing IPFS Desktop, had some updates from Microsoft queued up. Will install them and retry.
In the meantime, is someone could install  IPFS-Desktop-Setup-0.22.0-rc1.exe and comment if it works or has the same startup error, it would be highly appreciated.

False alarm, the problem was caused by Windows 11 update which was interrupted and had to finish.
After rebooting  the Windows box, IPFS Desktop works as expected.


how to remove moiré patterns?

Is this DTWAIN_SetCapValues API？how to set params?
what are these values?
DTWAIN_SOURCE | Source,
LONG | Capability,
LONG | SetType,
DTWAIN_ARRAY | CapValues

What computer language are you using?  If you are using C or C++, please see this example and others that call DTWAIN_SetCapValues.
In addition, see the help documentation.

Closing ticket.  Not able to duplicate and no follow-up.


PluginException in PyCharm 2023.2

I've been using the plugin for about six months. As soon as I upgraded to PyCharm 2023.2 I get this stack trace in every project:
com.intellij.diagnostic.PluginException: No display name is specified for configurable uk.co.ben_gibson.git.link.ui.settings.DomainRegistrySettings in xml file;
specify it using 'displayName' or 'key' attribute to avoid necessity to load the configurable class when Settings dialog is opened [Plugin: uk.co.ben-gibson.remote.repository.mapper]
	at com.intellij.openapi.options.ex.ConfigurableWrapper.getDisplayName(ConfigurableWrapper.java:156)
	at com.intellij.ide.util.gotoByName.GotoActionModel.lambda$new$0(GotoActionModel.java:81)
	at com.intellij.openapi.util.NotNullLazyValue$4.compute(NotNullLazyValue.java:120)
	at com.intellij.openapi.util.NotNullLazyValue$4.getValue(NotNullLazyValue.java:105)
	at com.intellij.ide.util.gotoByName.GotoActionModel.getConfigurablesNames(GotoActionModel.java:378)
	at com.intellij.ide.util.gotoByName.GotoActionItemProvider.processOptions(GotoActionItemProvider.java:148)
	at com.intellij.ide.util.gotoByName.GotoActionItemProvider.filterElements(GotoActionItemProvider.java:94)
	at com.intellij.ide.actions.searcheverywhere.ActionSearchEverywhereContributor.lambda$fetchWeightedElements$4(ActionSearchEverywhereContributor.java:137)
	at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$13(CoreProgressManager.java:604)
	at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:679)
	at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:635)
	at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:603)
	at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:61)
	at com.intellij.ide.actions.searcheverywhere.ActionSearchEverywhereContributor.fetchWeightedElements(ActionSearchEverywhereContributor.java:136)
	at com.intellij.ide.actions.searcheverywhere.MixedResultsSearcher$ContributorSearchTask.run(MixedResultsSearcher.java:184)
	at com.intellij.util.ConcurrencyUtil.runUnderThreadName(ConcurrencyUtil.java:218)
	at com.intellij.util.ConcurrencyUtil.lambda$underThreadNameRunnable$3(ConcurrencyUtil.java:206)
	at com.intellij.openapi.application.impl.ApplicationImpl$2.run(ApplicationImpl.java:272)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
	at java.base/java.lang.Thread.run(Thread.java:833)

The plugin still works, but I have a flashing exclamation point in the lower right and I had to rebind my keyboard shortcut (which I will remind people you can do by searching the keymap for ben_gibson).

What version of the plugin are you using? That exception should have been fixed in v4.3.4

Sorry to bother you! I looked right at the changelog of "Fix project configurable display name error in 2023.2 EAP" and didn't realize it was for me, and had never updated a plugin before. Fixed.

Actually I think what happened is I saw "Unreleased" at the top of the changelog and thought it meant the changes were unreleased. If the changelog is created by hand, a "None" entry under Unreleased might clarify.


use performance profiler on core use cases of HARK and look for speed improvements

We talk a lot about computational performance but I don't think we have been very systematic about testing for it.
Especially for computationally expensive actions like computing market equilibria, this could lead to some big performance gains.
https://docs.python.org/3/library/profile.html

Setting up cProfile for core econ-ark functionality would be a good move @nicksawhney

cc @alanlujan91


Fix issues noticed by Bobby

I also prefer viewing diffs on GitHub so let’s just include it in the app (made it more robust).
Also use remote branches for merge base.

It looks like starting from 9 days ago the GNOME GitHub mirror is not working :thinking:

I have reported it in https://matrix.to/#/#sysadmin:gnome.org and Andrea fixed it. It might take a while to sync all the repos, though.


SimpleMDE Editor crashing

Describe the bug
DevHub has been crashing or consistently reloading.
According to profiler, the majority of time is spent in the new simpleMDE editor. This is due to the legacy editing implementation that renders the editors upfront, and just makes it visible/hidden when user clicks on Reply -> Comment.
Additional context
The SimpleMDE commit has been reverted. A fix has been underway

I've reopened a pull request #255 to merge SimpleMDE editor. It replaces the legacy editing implementation and accordion with component state.
Aside from the SimpleMDE editor being added, DevHub now loads much faster.


add LICENSE file (fixes #1)

per recommendations in http://choosealicense.com/licenses/isc/ (see "How to apply this license" in the sidebar)

@mudroljub I'm assuming you closed this due to the git conflicts. I've resolved them and updated the branch, so please reconsider.

Hmmm. Looks like GitHub doesn't update the branch references in the upstream repo once a PR is closed. I opened #4 instead, with the same changes.

@waldyrious Thanks a lot, I appreciate your effort.