[FEATURE_REQUEST] Reordering layout of the sections and items within it onMouseHoldDrag

Is your feature request related to a problem? If so, please describe.
NO
Describe the solution you'd like
During the edit layout mode:

[ ] It would be nice to have drag and reorder layouts feature for reordering sections and layouts.
[ ] Also a further extension of this would be to resize sections in specific grid units using mouse drag on the border of the sections, items, and widgets.

Priority
Medium (Would be very useful)
Is this something you would be keen to implement
Yes!

Is your feature request related to a problem? If so, please describe.
NO
Describe the solution you'd like
During the edit layout mode:

[ ] It would be nice to have drag and reorder layouts feature for reordering sections and layouts.
[ ] Also a further extension of this would be to resize sections in specific grid units using mouse drag on the border of the sections, items, and widgets.

Priority
Medium (Would be very useful)
Is this something you would be keen to implement
Yes!

Please check the pinned issues, it is a known thing, it has been submitted many times, Lissy has this on her roadmap. Since some weeks Lissy has found again more time for dashy but she is very busy in her private life.

Duplicate of https://github.com/Lissy93/dashy/issues/378

Duplicate of #378

You misunderstood the request - this is not a duplicate. #378 is for copying or moving items between sections - this one is for a way to re-order sections (and items within sections). This is something I've been banging my head on this evening, trying to figure out how to do. Best I can tell, is that there is no way to re-order the sections via GUI?

this one is for a way to re-order sections (and items within sections)

Yup, this is exactly what this feature request meant.


Module 4.1 error

Testing with SampleInput / DemoData produces the following error:
Comparison is not allowed for operands of type 'nvarchar(max)' and 'datetime' in expression 'DeepStreamInput . [@timestamp] ! = CAST ( '1970-01-01T00:00:00.000Z' AS datetime )'.

Thanks for reporting, it looks like this is due to a service side change, I've modified the query to work with the new type expectations.

Please be aware that if you were working with a previous version of the repo and got caught in the middle of this change, you will need to update the DeepStreamAnalytics base module URI and the associated properties.desired as shown in this commit: https://github.com/toolboc/Intelligent-Video-Analytics-with-NVIDIA-Jetson-and-Microsoft-Azure/commit/f4015cd80827da5e3312c94dd4c3d910975bf713


multi: update to lnd with MuSig2

Takeover of: https://github.com/lightninglabs/lndclient/pull/97

Updated to latest musig2 API.

One addition over the original PR is that I added MuSig2TaprootTweakOpt too.


Make it easier to integrate with prezto by not forcing a directory name

This will let antigen remove a number of hacks they're using to load prezto and make it possible to place this in any directory and source it. The existing location will still work.


apps: Fix linking to SSO versions of desktop app.

The SSO build of the desktop app is intended only for those users who
who have settings.SSO_ONLY set, i.e. the only way to login is via the
site's SSO REMOTE_USER authentication.  We were incorrectly linking to
it on all production installations :(.

Automated message from Dropbox CLA bot
@timabbott, it looks like you've already signed the Dropbox CLA. Thanks!

@lfranchi I think that this fixes the issue we've been having with people downloading the wrong build.
Long term we probably will want to get rid of this build entirely but for now I'm trying to avoid breaking things.

lgtm, fftp

Merged, thanks @lfranchi for the review!


[Feature pull request]Click on status bar branch to open beanches menu

Hello, i created this little snipper in my init.coffee
editorEl = document.querySelector('atom-text-editor')
gitBranchEl = atom.views.getView document.querySelector('.git-branch')
gitBranchEl.addEventListener 'click', ->
  atom.commands.dispatch(editorEl,'git-plus:checkout')
gitBranchEl.style.cursor = 'pointer'

I'm not sure where to put this for make a pull request

the activate method in lib/git-plus.coffee might be the place for it.
The 5.5.0 branch is what I'm working on for the next release so can you make a clone of that branch and work with that instead?

this is now in the latest release


Winget installation fails: hash does not match

Lapce Version
0.2.7
System information
W11
Describe the bug
Winget installation fails because of hash mismatch.
Also, shouldn't Winget point to 0.2.8?
I think the issue is that the link points at 0.2.8 while some Winget metadata may still refer to 0.2.7.
Additional information
PS C:\Users\dell> winget install lapce
Found Lapce [Lapce.Lapce] Version 0.2.7
This application is licensed by the owner.
Microsoft is not responsible for or grants any license to any third party packages.
Downloading https://github.com/lapce/lapce/releases/latest/download/Lapce-windows.msi

██████████████████████████████ 17.9 MB / 17.9 MB

The installer hash does not match.

It's a problem with winget, not lapce. You should open issue in https://github.com/microsoft/winget-pkgs

Committing a new manifest should solve the issue:
https://github.com/microsoft/winget-pkgs/tree/master/manifests/l/Lapce/Lapce
0.2.7 is the last one and is pointing to latest.
It was not clear to me that it was manual effort to update the manifest, so I do apologize for opening the issue in the wrong place.

Seems that https://github.com/microsoft/winget-pkgs/pull/112921 fixed it


genome-workbench 2.11.10 (new formula)

NCBI Genome Workbench is an integrated application for
viewing and analyzing sequence data.
If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[ ] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Thanks for merging, Tin!


Add BuildInfo metric End Point.

Looks like it is good practice to have a build_info end point as well for the metrics.
We will need to build out the Observer Interface to include a way to pass in a BuildInfo struct.
Need to build out a BuildInfo struct that will contain the following information:

version of Tegola.
git version
which build tags have been enabled
values of important ENV's like TEGOLA_OPTIONS and CGO_ENABLED  (Should we expose TEGOLA_SQL_DEBUG and/or TEGOLA_HTTP_PPROF_BIND)
start time

Added by #765


Improve parsing of dates for recurring events

See https://github.com/OfficeDev/ews-java-api/pull/165 and https://github.com/OfficeDev/ews-java-api/issues/169 for discussion.

Hi @ahaarrestad, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@serious6 @evpaassen new PR created.

Updated as commented.

merge-time?

Improved solution in https://github.com/OfficeDev/ews-java-api/pull/176


Remove critical-pod annotation from Concierge and add priorityClassName: system-cluster-critical instead

Is your feature request related to a problem? Please describe.
Concierge deployments cause this warning: Warning: spec.template.metadata.annotations[scheduler.alpha.kubernetes.io/critical-pod]: non-functional in v1.16+; use the "priorityClassName" field instead.
Describe the solution you'd like
Remove critical-pod annotation from Concierge and add priorityClassName: system-cluster-critical instead. See this old TODO in the code: https://github.com/vmware-tanzu/pinniped/blob/0651b9a91220bceec8e69c834e506b357dd750fb/deploy/concierge/deployment.yaml#L228-L230
Describe alternatives you've considered
None.
Additional context
Would this prevent deploys on Kube 1.16 and earlier? Would we be okay with that? We don't test against those old unsupported versions, so we're not sure if the Concierge deploys and works on those old versions anyway.

I think this was effectively done in #1693


Add IndexedQubit class in the same vein as NamedQubit

Qubit represented by integer/index rather than name or co-ordinates.
Used in pytket, can merge in if useful generally?
Implemented at https://github.com/ss2165/Cirq/commit/cd83e620ca6519efdd8dd9cbffda32a1b54bd55e

Thanks for the suggestion. We actually already have this; we just call it LineQubit instead of IndexedQubit.
In the future, feel free to make a pull request from your forked repo's branch into this repository instead-of / in-addition-to opening an issue. Maintainers love it when you state your feature request in the form of a pull request.
Since we have a similar class, I will tentatively close this issue.

I was aware of LineQubit but thought of it in the same local sense as GridQubit (i.e. the identifier corresponds to a location) and wanted something more abstract like NamedQubit. But they do the same job, so I'll switch my implementation to use LineQubit.


dnx 1.0.0-beta7-12331, dnu restore issue

After installing the nightly build I am trying to do a dnu restore.

These weird issues are caused by the fact various ASP.NET 5 packages reference CoreCLR packages that are not on MyGet/NuGet yet (23210 > 23207).
@davidfowl curious: shouldn't DNU automatically use the latest available version when it cannot find the specific build referenced in a package?

Not if the dependency constraint is violated. If you depend on 4.0.20 and only 4.0.10 is there, it will fail.

Well, it's a bit more subtle: when we specify 4.0.1-beta-* in project.json, it's automatically converted to 4.0.1-beta-[build available when the package is created] in .nuspec (for instance, 4.0.1-beta-23210).
But since we used a wildcard in project.json (4.0.1-beta-*) to indicate we wanted to reference the latest build, 4.0.1-beta-23207 (the latest version found) should be considered as a valid version.

But since we used a wildcard in project.json (4.0.1-beta-*) to indicate we wanted to reference the latest build, 4.0.1-beta-23207 (the latest version found) should be considered as a valid version.

That does work but the above project.json would need to specify all of the transitive dependencies as * which kinda defeats the purpose.

@causer FYI, the missing packages are now on MyGet! :smile:

@PinpointTownes Thank you, now 'dnu restore' reports "Done, without errors, Restore complete". I should close this issue?


Fixes remotes_test.go on 32 bit platforms

Using MaxInt32 instead of MaxInt64 in TestRemotesLargeRanges. Stops an
overflow on 32 bit systems. Closes #1384
Signed-off-by: Drew Erny<EMAIL_ADDRESS>

LGTM

NB I don't actually have a 32 bit platform to test compile this on.

Rebasing should deal with the test failure.

LGTM

LGTM

LGTM


update image tags to v0.5.0-beta.0

Signed-off-by: Iceber Gu<EMAIL_ADDRESS>What type of PR is this?

/kind cleanup
What this PR does / why we need it:
Release 0.5.0 beta version, after a week of testing release 0.5.0 version
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

Ignore the error, the image of 0.5.0-beta.0 was not found, I will add the  after this pr merge
@calvin0327 Do you think there is a better way to deal with this problem?


FLAPPY SPACE SHUTTLE 🚀

FLAPPY SPACE SHUTTLE 🚀 does not work in mobile. It works fine in desktop (using Space Bar) but it does not detect mobile taps. So make it mobile friendly.

i want to work on it

@prajwal2431 ok sir


Support for Linux aarch64

Description
Would it be possible for create a release version that would work on Linux aarch64 devices?
Acceptance Criteria
additional release that includes *.tar.gz or *.AppImage file for aarch64 arcitecture (Such as Raspberry Pi's etc)

I personally have not done this before but here are some steps I found:
To support aarch64 architecture, you need to build your application for the aarch64 target. Here is a step-by-step guide to cross-compile your application for aarch64 on an Intel PC and package it into an AppImage.
Steps to Cross-Compile for aarch64 and Create an AppImage:

Install Cross-Compilation Tools: Install the necessary tools for cross-compiling to aarch64.  sudo apt update sudo apt install gcc-aarch64-linux-gnu g++-aarch64-linux-gnu
Set Up Cross-Compilation Environment: Configure your build system (e.g., CMake, Makefile) to use the aarch64 cross-compiler.  For CMake, you can create a toolchain file aarch64-toolchain.cmake:  # aarch64-toolchain.cmake set(CMAKE_SYSTEM_NAME Linux) set(CMAKE_SYSTEM_PROCESSOR aarch64) set(CMAKE_C_COMPILER aarch64-linux-gnu-gcc) set(CMAKE_CXX_COMPILER aarch64-linux-gnu-g++)
Build the Application: Use the toolchain file to build your application for aarch64.  mkdir build-aarch64 cd build-aarch64 cmake -DCMAKE_TOOLCHAIN_FILE=../aarch64-toolchain.cmake .. make
Create the AppImage: Use linuxdeploy and linuxdeploy-plugin-appimage to create the AppImage.wget https://github.com/linuxdeploy/linuxdeploy/releases/download/continuous/linuxdeploy-x86_64.AppImage wget https://github.com/linuxdeploy/linuxdeploy-plugin-appimage/releases/download/continuous/linuxdeploy-plugin-appimage-x86_64.AppImage chmod +x linuxdeploy*.AppImage ./linuxdeploy-x86_64.AppImage --appdir AppDir --executable path/to/your/aarch64/executable ./linuxdeploy-plugin-appimage-x86_64.AppImage --appdir AppDir

Thanks, I will try to support this arch on the next release 👍


Allow wildcards in [bumpversion:file:...]

Can I specify folders in .bumpversion.cfg?,
I'm trying to use this to update all the @version x.x.x php doc block tags in specific folders in my project.

You mean as in
[bumpversion:file:path/to/source/**.php]

would then expand and match
path/to/source/a_file.php
path/to/source/a_second_file.php
path/to/source/another_file.php
path/to/source/file_that_does_not_start_with_a.php

?
No, it doesn't work that way at the moment, you'd have to specify all the files individually in the configuration.
I like the idea though, pull requests welcome :)

Yes, thats what I need.
I have the config working on all the unique files but it'll be back to the old find and replace on folders for now then :)
Thanks for the quick reply.

@louisl

back to the old find and replace on folders for now then

You have folders that have version numbers in their names or am I misunderstanding this ?

No not in the folders names, this for a website so the version is in the header doc blocks of each php and js file and in a constants file as a variable. Also it's in bower.json, composer.json, package.json. So on a version bump I need to update a lot of places.

I'm currently working on this, by first trying the builtin glob library, and if that fails (because glob doesn't expand everything that a shell can, eg curly brackets) then calls the shell via subprocess.check_output. What I have seems to be working. Currently reading through the unit tests and adding some tests for multiple files via globs. I should have a PR ready within a couple of days or so.

Incidentally, do you mind if I refactor the 1864 line tests/test_cli.py module into some separate modules containing related tests?
Also, do you mind if I cleanup tmpdir after each test that uses it (so I don't have to worry about what files already exist)?

@jackmaney you ever get a PR for this? Or is your work available in a fork/branch?


Change options at breakpoints

Hi David
could you help me with some example to change options at breakpoints, i need to change the draggable to false, in min-width 1024px
I'm looking for an example and haven't found it, I'm using vanilla js
thank you so much

Hi @lorenzecode,
Thank you for your question. Try something along these lines:
const BREAKPOINT = 1024

embla.on('resize', () => {
  const draggable = window.innerWidth < BREAKPOINT
  embla.reInit({ draggable })
})

Let me know if it helps.
Best,
David

Thanks for answering
it worked, but when I start at the breach point 1024, the draggable is active and only changes if I resize

That's because you need to run the same function upon init:
const BREAKPOINT = 1024

// Check for the window size when you initialize your carousel too
const options = { draggable: window.innerWidth < BREAKPOINT }
const embla = EmblaCarousel(emblaNode, options)

embla.on('resize', () => {
  const draggable = window.innerWidth < BREAKPOINT
  embla.reInit({ draggable })
})

Kindly,
David

Wow,
It Works Very Well, Thank You!
For the other options would it be the same?
Ex: Align: Start for the Center

For the other options would it be the same?

Yes, the same approach will work for other options as well.
Enjoy,
David

@lorenzecode it’s now possible to change options at breakpoints using this approach.
Best,
David


Docs.MS CI Updates for Microsoft.OpenTelemetry.Exporter.AzureMonitor

CI Update for release of Microsoft.OpenTelemetry.Exporter.AzureMonitor

Docs Build status updates of commit 2d3e4c3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

bundlepackages/azure-dotnet-preview.csv
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 79c8673:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

bundlepackages/azure-dotnet-preview.csv
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


"npm start" failing with "JSX syntax extension is not currently enabled"

Am following https://github.com/jeffeb3/sandify#running-from-source-locally
"npm start" failing with "JSX syntax extension is not currently enabled.
Error message seems to include info on how to fix.  Am new to vite, so figured on filing this issue for clarity...
"The esbuild loader for this file is currently set to "js" but it must be set to "jsx" to be able to parse JSX syntax. You can use "loader: { '.js': 'jsx' }" to do that."

Hmm, maybe those messages are ignorable?  Despite the scary errors during startup am still able to access the localhost:3000 app 🤷♂ ?

Yes, we have configuration settings in vite.config.js to handle that error, so not sure why are you seeing it.
What version of node are you using? We are at 20.6.1.
Are you using nvm for node versioning? If not, I recommend installing it, installing 20.6.1 if you don't have it, and then running "nvm use" from the project directory. Likely unrelated, but I see no warnings when running "npm start".

Am on Node 18 still.  Site still seems to work, will update to 20 if I run into a blocking issue, and/or when Node 20 reaches long term support https://nodejs.org/en/blog/announcements/v20-release-announce .   Cheers for the info/guidance!

I use the docker compose. There important commands are in the docker compose file. So that should always have a working version of node and npm.


Add registry oyster to README

Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

cc @ahmetalpbalkan

:shipit:

LGTM!

Nice. LGTM.


HBASE-24250 CatalogJanitor resubmits GCMultipleMergedRegionsProcedure…

… for the same region

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 22s
the patch passed

+1 :green_heart:
compile
1m 25s
the patch passed

+1 :green_heart:
javac
1m 25s
the patch passed

+1 :green_heart:
shadedjars
7m  9s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 52s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 20s
the patch passed

+1 :green_heart:
compile
1m 10s
the patch passed

+1 :green_heart:
javac
1m 10s
the patch passed

+1 :green_heart:
shadedjars
5m 41s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 39s
hbase-server in the patch failed.

Looks good, It actually addressed the issue for HBASE-24316. Let me put up an unitest as I planned to do for HBASE-24316. Mind put the following code in as well? (Please review first, :))
{code}
diff --git a/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java b/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
index ac79e8aaff..e345483351 100644
--- a/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
+++ b/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
@@ -1904,6 +1904,16 @@ public class MetaTableAccessor {
qualifiers.add(qualifier);
delete.addColumns(getCatalogFamily(), qualifier, HConstants.LATEST_TIMESTAMP);
}
+

// There will be race condition that a GCMultipleMergedRegionsProcedure is scheduled while
// the previous GCMultipleMergedRegionsProcedure is still going on, in this case, the second
// GCMultipleMergedRegionsProcedure could delete the merged region by accident!
if (qualifiers.isEmpty()) {

 LOG.info("No merged qualifiers for region " + mergeRegion.getRegionNameAsString() +

   " in meta table, they are cleaned up already, Skip.");

 return;

}

{code}

@huaxiangsun, thanks for review .
Yes,I think you can submit another PR for  HBASE-24316

Looks good, It actually addressed the issue for HBASE-24316. Let me put up an unitest as I planned to do for HBASE-24316. Mind put the following code in as well? (Please review first, :))
diff --git a/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java b/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
index ac79e8aaff..e345483351 100644
--- a/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
+++ b/hbase-client/src/main/java/org/apache/hadoop/hbase/MetaTableAccessor.java
@@ -1904,6 +1904,16 @@ public class MetaTableAccessor {
       qualifiers.add(qualifier);
       delete.addColumns(getCatalogFamily(), qualifier, HConstants.LATEST_TIMESTAMP);
     }
+
+    // There will be race condition that a GCMultipleMergedRegionsProcedure is scheduled while
+    // the previous GCMultipleMergedRegionsProcedure is still going on, in this case, the second
+    // GCMultipleMergedRegionsProcedure could delete the merged region by accident!
+    if (qualifiers.isEmpty()) {
+      LOG.info("No merged qualifiers for region " + mergeRegion.getRegionNameAsString() +
+        " in meta table, they are cleaned up already, Skip.");
+      return;
+    }
+

Yes, looks good.

@saintstack could you help review this one ?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 58s
the patch passed

+1 :green_heart:
compile
1m  4s
the patch passed

+1 :green_heart:
javac
1m  4s
the patch passed

+1 :green_heart:
shadedjars
5m  9s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 39s
hbase-server in the patch failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 57s
the patch passed

+1 :green_heart:
compile
1m 19s
the patch passed

+1 :green_heart:
javac
1m 19s
the patch passed

+1 :green_heart:
shadedjars
6m 29s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 46s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
214m 54s
hbase-server in the patch passed.

245m 43s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1629/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1629

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 57814e45deed 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a9a1b9524d

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1629/4/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1629/4/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1629/4/testReport/

Max. process+thread count
3167 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1629/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

@nyl3532016 I merged the patch. Can you back port it to branch-2 and branch-2.3? Thanks


Add notes and slides from the different ICAT schema discussion meetings

Add the slides and notes from the discussions around the ICAT schema changes, linking to the relevant issues in the icat.server component.

cc @stuartpullinger @RKrahl - it would be great to upload the slides from the discussions to the website
+

Sure! Where shall I put the slides?

I suggest creating a specific folder under: https://github.com/icatproject/icatproject.github.io/tree/gatsbyjs/content/collaboration/communication
and having sub-folders for each of the meetings.
We need to include the slides + move all the content from the google docs to the website


The result is inconsistent after swapping the sequence of the "Create Empty Blob" and "Upload Folder" actions

OS: All
Build Version: 20210420.1
Repro Steps:

Create a Blob Container -> Create an empty blob with name "test" -> Upload a folder with the same name "test" to the Blob Container -> Click "Yes to all" when asking to overwrite -> Check the result.
Create a new Blob Container -> Upload a folder with name "test" to the Blob Container -> Create an empty blob with the same name "test" -> Check the result.
Check whether the result is consistent between the step 1 and step 2.

Expect:
The result is consistent between the step 1 and step 2.
Actual:
The result is inconsistent between the step 1 and step 2.

Step 1: Succeed to upload the folder "test" without any error, the blob "test" and folder "test" exist at the same time.

Step 2: Fail to create a blob "test" with an error.

More Info:

There is an error when deleting the blob/folder "test" from step 1 on Windows.

This issue also reproduces for the attached storage account and Local Emulator.

:slightly_frowning_face: In the last 60 days, this issue has received less than 5 community upvotes and we closed it. Still a big Thank You to you for taking the time to create it! To learn more about how we handle issues, please see our documentation.
Happy Coding!


feat: Pass ReactApplicationContext along to Plugin Initializer

What
Passes the ReactApplicationContext along to the Frame Processor Plugin Initializer function.
Before:
FrameProcessorPluginRegistry.addFrameProcessorPlugin("example_plugin", options -> {
  return new ExampleFrameProcessorPlugin(options)
});

After:
FrameProcessorPluginRegistry.addFrameProcessorPlugin("example_plugin", (context, options) -> {
  return new ExampleFrameProcessorPlugin(options)
});

This is considered a breaking change since the new parameter has to be added to all FP Plugins

Changes

Tested on

Related issues

@xulihang is that something you need?

It turns out that it is not neccessary as I can use static methods to access the context and do my job.

Awesome!


[WIP] Update pydata theme

This updates the theme dependency to use the newest pydata theme, it'll also bring in a few more styles and configuration options. Most notably it will add support for a dark theme. This PR will track the needed updates for this:

[ ] Theme re-builds with no errors or visual problems
[ ] Dark/light mode support
[ ] Update announcement support
[ ] Remove CSS improvements in upstream theme that are no longer needed in this theme

Closes #575

Closing this one in favor of the updated PR from @AakashGfude here:

https://github.com/executablebooks/sphinx-book-theme/pull/597


Add new stable API-version 2023-05-01 in Microsoft.Dataprotection

ARM API Information (Control Plane)
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Note that this doesn't apply if you are trying to merge a PR that was previously in the private repository.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

"UserAssignedIdentityDetails": {

See https://github.com/Azure/azure-rest-api-specs/blob/main/specification/common-types/resource-management/v5/managedidentity.json.

Refers to: specification/dataprotection/resource-manager/Microsoft.DataProtection/stable/2023-05-01/dataprotection.json:5500 in 26675d4. [](commit_id = 26675d46603b8561db2ba67ed5514e406f5759f5, deletion_comment = False)

"NamespacedNameResource": {

Resource Name seems a bit confusing.

Refers to: specification/dataprotection/resource-manager/Microsoft.DataProtection/stable/2023-05-01/dataprotection.json:6372 in 26675d4. [](commit_id = 26675d46603b8561db2ba67ed5514e406f5759f5, deletion_comment = False)

6372

Hi @visingla-ms, NamespacedNameResource is defined in common contract and it defines those resources which are identified by both namespace and its name.

Here in one of the required checks: Swagger ModelValidation.. I can see failure's
Basically we have added one field in Backup Vault Property and its a read-only property.. however there is a requirement that whatever response we get as part of GET, should work as part of PUT as well.. therefore we have kept the field as part of PUT request as well. Current Behaviour is set in a way that it would ignore that field.
Customer can send this sometimes and instead of failing the call we would just ignore it..
Before finalizing this we posted this on stack overflow and this was one of the recommended way of handling such properties.
https://stackoverflow.microsoft.com/questions/347097

@scbedd please review the ModelValidation error

@ankur741999 please fix the API Readiness Check error

Basically we have added one field in Backup Vault Property and its a read-only property.. however there is a requirement that whatever response we get as part of GET, should work as part of PUT as well.. therefore we have kept the field as part of PUT request as well. Current Behaviour is set in a way that it would ignore that field.

I'm looking at this model validation failure...and the failure makes sense. If that property is marked readOnly, it can't be set from client side.
I will allocate a couple hours on Monday morning first-thing to see if I can understand your use-case.

"IdentityDetails": {

Instead of defining it here, use "ManagedServiceIdentity" from common-types: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/common-types/resource-management/v5/managedidentity.json.
Refers to: specification/dataprotection/resource-manager/Microsoft.DataProtection/stable/2023-05-01/dataprotection.json:4321 in 26675d4. [](commit_id = 26675d4, deletion_comment = False)

While we can use common contract for tracked resource, this contract is used in proxy resource and hence we want a specific contract. Proxy resource can use subset of identities from tracked resource. Also we may want more custom fields for proxy resource in the future like default identity.

Basically we have added one field in Backup Vault Property and its a read-only property.. however there is a requirement that whatever response we get as part of GET, should work as part of PUT as well.. therefore we have kept the field as part of PUT request as well. Current Behaviour is set in a way that it would ignore that field.

I'm looking at this model validation failure...and the failure makes sense. If that property is marked readOnly, it can't be set from client side.
I will allocate a couple hours on Monday morning first-thing to see if I can understand your use-case and come up with a workaround.

@scbedd , many users do a Get-Resource API and use the response of the same to do update vault by modifying 1-2 properties' values. Hence, to avoid failures for those users, we have the example with readonly property allowed in request

@keryul Does suppressing this error follow with your experience? Do you happen to know who would be the swagger SME that I talk to about changes that I make to oav? Or is this a case of actual error that we just ignore.

Basically we have added one field in Backup Vault Property and its a read-only property.. however there is a requirement that whatever response we get as part of GET, should work as part of PUT as well.. therefore we have kept the field as part of PUT request as well. Current Behaviour is set in a way that it would ignore that field.

I'm looking at this model validation failure...and the failure makes sense. If that property is marked readOnly, it can't be set from client side.
I will allocate a couple hours on Monday morning first-thing to see if I can understand your use-case and come up with a workaround.

@scbedd , many users do a Get-Resource API and use the response of the same to do update resource (via PUT) by modifying 1-2 properties' values. Hence, to avoid failures for those users, we have the example with readonly property allowed in request. Let me know if it makes sense. This change was approved as part of our changes in preview API version.
PR link for preview version - #23391

@amchandn can you tag the example with readonly property allowed in request? Let's find if there's a exclusion for this situation.

@keryul Does suppressing this error follow with your experience? Do you happen to know who would be the swagger SME that I talk to about changes that I make to oav to support this scenario? Or is this a case of actual error that we just ignore.

I haven't see any exclusion about error READONLY_PROPERTY_NOT_ALLOWED_IN_REQUEST.
Let's see if there's any exclusion in https://github.com/Azure/azure-rest-api-specs/pull/23391.

@keryul Does suppressing this error follow with your experience? Do you happen to know who would be the swagger SME that I talk to about changes that I make to oav to support this scenario? Or is this a case of actual error that we just ignore.

I haven't see any exclusion about error READONLY_PROPERTY_NOT_ALLOWED_IN_REQUEST. Let's see if there's any exclusion in #23391.

I don't understand what you mean by

let's see if there's any exclusion in #23391

Do you mean there is no prior art of a suppression on this type of error? Or that the other PR has an exclusion within it that we can copy?

Basically we have added one field in Backup Vault Property and its a read-only property.. however there is a requirement that whatever response we get as part of GET, should work as part of PUT as well.. therefore we have kept the field as part of PUT request as well. Current Behaviour is set in a way that it would ignore that field.

I'm looking at this model validation failure...and the failure makes sense. If that property is marked readOnly, it can't be set from client side.
I will allocate a couple hours on Monday morning first-thing to see if I can understand your use-case and come up with a workaround.

@scbedd , many users do a Get-Resource API and use the response of the same to do update resource (via PUT) by modifying 1-2 properties' values. Hence, to avoid failures for those users, we have the example with readonly property allowed in request. Let me know if it makes sense. This change was approved as part of our changes in preview API version.
PR link for preview version - #23391

@amchandn can you tag the example with readonly property allowed in request? Let's find if there's a exclusion for this situation.

Hi @keryul , @scbedd , looks like a force push by the PR author undoe'd the concerned change. We're making that change again and will update the conversation in this PR.
Thanks for your patience.

@keryul Does suppressing this error follow with your experience? Do you happen to know who would be the swagger SME that I talk to about changes that I make to oav to support this scenario? Or is this a case of actual error that we just ignore.

I haven't see any exclusion about error READONLY_PROPERTY_NOT_ALLOWED_IN_REQUEST. Let's see if there's any exclusion in #23391.

I don't understand what you mean by

let's see if there's any exclusion in #23391

Do you mean there is no prior art of a suppression on this type of error? Or that the other PR has an exclusion within it that we can copy?

I want to know if that PR has an exclusion within it that we can copy cause I haven't found any readOnly property in request in that PR.

@keryul Does suppressing this error follow with your experience? Do you happen to know who would be the swagger SME that I talk to about changes that I make to oav to support this scenario? Or is this a case of actual error that we just ignore.

I haven't see any exclusion about error READONLY_PROPERTY_NOT_ALLOWED_IN_REQUEST. Let's see if there's any exclusion in #23391.

I don't understand what you mean by

let's see if there's any exclusion in #23391

Do you mean there is no prior art of a suppression on this type of error? Or that the other PR has an exclusion within it that we can copy?

I want to know if that PR has an exclusion within it that we can copy cause I haven't found any readOnly property in request in that PR.

@keryul , @scbedd , here is the failing example and readonly property that is failing check during ModelValidation with examples
`

READONLY_PROPERTY_NOT_ALLOWED_IN_REQUEST
ReadOnly property "secureScore" cannot be sent in the requestUrl: Microsoft.DataProtection/stable/2023-05-01/dataprotection.json#L4835:24ExampleUrl: 2023-05-01/examples/VaultCRUD/PutBackupVault.json#L7:19

Failing validation link
`

Let me know if it makes sense. This change was approved as part of our changes in preview API version.

@amchandn  Did I misunderstand the phrase? If this change was approved in preview PR, we will try to approved it in this PR. Or if not, we still think you should fix the MV error.

Let me know if it makes sense. This change was approved as part of our changes in preview API version.

@amchandn Did I misunderstand the phrase? If this change was approved in preview PR, we will try to approved it in this PR. Or if not, we still think you should fix the MV error.

Yes, this change was approved as part of preview API version's PR, so requesting you to approve in this PR as well

I haven't found this change in preview PR, can you tag it here?

Hi @keryul , I recheckede and realised that as part of that PR we did not add this property in request. So this seems to be a new change in example only. Sorry for the confusion.

Let me know if it makes sense. This change was approved as part of our changes in preview API version.

@amchandn Did I misunderstand the phrase? If this change was approved in preview PR, we will try to approved it in this PR. Or if not, we still think you should fix the MV error.

Yes, this change was approved as part of preview API version's PR, so requesting you to approve in this PR as well

I haven't found this change in preview PR, can you tag it here?

Hi @keryul , I recheckede and realised that as part of that PR we did not add this property in request. So this seems to be a new change in example only. Sorry for the confusion.

We have removed the readonly property from request example and all required checks are passing now.

@qiaozha please review the JS breaking change

Hi @keryul, ARM review has been completed. Can we merge this PR if we have no more issues?

@qiaozha please review the JS breaking change

this js sdk breaking should be a non-breaking


chore: update changelog

Checklist

[ ] npm test passes
[ ] tests and/or benchmarks are included
[ ] commit message follows commit guidelines

Description of change

Pull Request Test Coverage Report for Build 393895365

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 93.389%

Totals

Change from base Build 393856494:
0.06%

Covered Lines:
10669

Relevant Lines:
11077

💛  - Coveralls


DBZ-5770: Update documentation regarding the Binary Data Converter

Updated all references from ByteBufferConverter to BinaryDataConverter.
Also added special note about changing the settings before upgrading when running in Kafka Connect (otherwise Kakfa Connect will fail to start).

@enzo-cappa Applied, thanks a lot!


Add explicit flags for volume cp/no-cp

- What I did
This allows a user to specify explicitly to enable
automatic copying of data from the container path to the volume path.
This does not change the default behavior of automatically copying, but
does allow a user to disable it at runtime.
- How I did it
Add option flags for volume specs for nocopy and copy
- How to verify it
docker run -v foo:/bar:nocopy
docker run -v /foo:/bar:copy
- A picture of a cute animal (not mandatory but encouraged)

Signed-off-by: Brian Goff<EMAIL_ADDRESS>

win2lin is failing for unknown reasons.

do we need the copy option? I cannot think of any case where we might need to be very explicit in that. Do you have any examples?

@calavera see the second example, I.e. Also copy to a bind-mounted location

Yep, what @thaJeztah said.
There's also a nice error when you have copy explicitly enabled but a copy doesn't happen due to the volume not being empty.

LGTM

So let's just remove the :copy option on bindmounts since that doesn't make much sense and has no real usecase.

if copy is the default, and not supported for bind-mounts, perhaps we should drop it as a whole for now?

@thaJeztah ah, it is dropped, I missed the opt in the doc.

Updated

OMG PANDA :panda_face:

LGTM

is this related:
18:08:14 ----------------------------------------------------------------------
18:08:14 FAIL: docker_cli_run_test.go:4223: DockerSuite.TestRunAttachFailedNoLeak
18:08:14
18:08:14 docker_cli_run_test.go:4233:
18:08:14     c.Assert(err, checker.NotNil)
18:08:14 ... value = nil
18:08:14
18:08:35
18:08:35 ----------------------------------------------------------------------

That test is flaky; there was a fix, but apparently not sufficient. I'll reopen https://github.com/docker/docker/issues/21247

sigh, and now it ended on a Windows node with networking issues

all green, and two LGTM's, so moving to docs review

@cpuguy83 can you add the new options to;

https://github.com/docker/docker/blob/master/docs/reference/commandline/run.md
https://github.com/docker/docker/blob/master/docs/reference/commandline/create.md
https://github.com/docker/docker/blob/master/man/docker-run.1.md
https://github.com/docker/docker/blob/master/man/docker-create.1.md

also ping @albers @sdurrheimer to check if there's changes needed for the completion scripts :heart:

Looks like we would not be able to merge this PR because of merge conflicts. Please rebase, fix conflicts, and force push to your branch.

@thaJeztah done.

Awesome! LGTM

ping @vdemeester ptal, this is for 1.11 :innocent:

LGTM 🐼

the failures are unrelated, merging.


Deconflict version command (version -> ver)

Context and purpose of the change
version --long no longer displays package information important for debugging chain issues
Brief Changelog
Renamed "version" command to "ver" to allow the existing "version --long" command to work
Author's Checklist
I have...

[ ] Run and PASSED locally all GAIA integration tests
[ ] If the change is contentful, I either:

[ ] Added a new unit test OR
[ ] Added test cases to existing unit tests

[X] OR this change is a trivial rework / code cleanup without any test coverage

If skipped any of the tests above, explain.
works in stride v10.0.0
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] manually tested (if applicable)
[ ] confirmed the author wrote unit tests for new logic
[ ] reviewed documentation exists and is accurate

Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md?
[ ] This pull request updates existing proto field values (and require a backend and frontend migration)?
[ ] Does this pull request change existing proto field names (and require a frontend migration)?
How is the feature or change documented?

[ ] not applicable
[ ] jira ticket XXX
[ ] specification (x/<module>/spec/)
[ ] README.md
[ ] not documented

We'd prefer to not modify this version command, but I opened #831  to address this. Please let me know if that works for you!

Closing in favor of #831


Sustainment Reporting Feature service used by GeoEvent Services

The Sustainement Reporting Feature Service is used by GeoEvent Services that are going to be released. This service needs to be released or the GeoEvent Input/Outputs need to be removed.
As a reminder the nsecgee is not a development machine, it is for ready to release GeoEvent content.
Service Item id:998c767c6af34ff197e73b25b77c80fa
The name of this service is "Map" that is not a good name for the service and the service name should be changed before release.

#1212 depends on this issue.

This was resovled by @pHill5136


can you do a handshake and push to client protocol

What is the business background? Please provide a description.
Who are the users? How do they utilize this feature? What problem does this feature address?
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

!!! Before submitting a new feature request, please ensure you have searched for any existing features and utilized
the Ask AI feature at https://ossrs.io or https://ossrs.net (for users in China). Duplicate issues or
questions that are overly simple or already addressed in the documentation will be removed without any
response.


Expectations if a gateway peer is restarted for submit transactions

A client does not have to recreate a grpc connection or gateway to cater for a gateway peer terminating and restarting (note this does not take into account talking to a peer through an ALB which may create a different connectivity behaviour), nor should a well designed client applicaton require restarting however the client application should expect certain errors when the peer goes down.
In our testing we see
"Failed","message":"14 UNAVAILABLE: Connection dropped"

and
"Failed","message":"1 CANCELLED: Call cancelled"}

occuring when the gateway peer terminates
When the gateway peer is restarted, even though it will accept requests to endorse you could see the following error
"14 UNAVAILABLE: no combination of peers can be derived which satisfy the endorsement policy: no peer combination can satisfy the endorsement policy"

These stop after about 1 second in our tests as the gateway peer rediscovers the available peers. This implies that a gateway peer isn't instantly available to process requests even though it accepts requests (potential for enhancement ????)
This doesn't happen all the time due to delays in the client polling for a ready connection and possibly how fast the peer creates it's knowledge of endorsing peers
We could recommend a client make use of the waitForReady api in their grpc connection. This provides a simple api to determine if there is an actual connection to the gateway peer and can be used in a polling fashion to wait until the gateway peer has started and the connection is restored. This of course is no indication that the peer is ready to accept requests and if you don't do this then you will get an error trying to submit the request (as expected as the peer is down). In our testing this proved to be a nice way to wait before sending submit requests but of course doesn't help with the gateway peer not being ready to process the request due to discovering the network

If some service is temporarily down — either the Gateway peer or another Node it’s trying to reach — then a gRPC UNAVAILABLE seems like exactly the right behaviour, and the client can retry, perhaps with some backoff. I don’t see anything obvious to improve on.
The use of wait-for-ready at the client end just means the client should wait for the gRPC connection to the Gateway to re-establish if it’s currently in a failed state rather than failing fast. Other than just modifying that one aspect of behaviour, I don’t see how it addresses the overall scenario that some service in the network is not currently available.
I guess the use of wait-for-ready for Gateway peer connections to other nodes might slightly change the client-observable behaviour. Whether any behavioural change is desirable, I'm not sure. gRPC defaults to fail-fast by design.


Support Delayed Authorizations (aka. Pre-Orders)

A couple of sites have asked for the ability to support a flow where:

No authorization is performed at checkout, just a confirmed order reference.
The order is created in the Magento admin with a "pending" status.
The merchant is able to generate an invoice that creates a new authorize and capture on the confirmed order reference associated with the order.
** In the event the authorize and capture fails, the merchant should see an error message and be able to collect payment via another form.

Thinking this could function as a new payment action config:

authorize only
authorize & capture (default)
token only

Token only would create the billing agreement, and create a new Magento order with "processing" status.
Later, the merchant can to the order page, select invoice.  There is process Offline / Online options currently.  If a token exists, would add a "Process via Token" option on the invoice, that would process the auth & capture payment via Amazon Payments and complete the order.

Setting only at global level, will defer item-level config.

New global config option under Enable Tokenized Payments: Allow Pre-Orders
Magento order status defaults to "New Order Status" config
Invoice creation authorizes and captures (automatically detects if pre-order or not. Order comment also indicates pre-order)


Improve batch progress state

Now show a meaningful message instead of numbers to indicate the
progress of the batch
Signed-off-by: Saeid Askari<EMAIL_ADDRESS>

Does it need more tests? The field in the status that was changed is already in 6 integration tests that check Completed and InProgress states. NotStarted state is not really used and can't be observed because it immediately changes to InProgress.

Does it need more tests? The field in the status that was changed is already in 6 integration tests that check Completed and InProgress states. NotStarted state is not really used and can't be observed because it immediately changes to InProgress.

Fine then, I wasn't aware of the integration test checks

/retest


[CT-2229] [Bug] Tarball Dependencies expose URL credentials when running dbt deps

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
When I use the new Tarball dependencies feature, I specify username and password (using env_var function) in the packages.yml .
When I run dbt deps, it prints out the tarball package URL, including the credential
Expected Behavior
I expect that if there is a credential in the URL, it should be masked
Steps To Reproduce
In my example I am using an internal https repository, however it is simply reproduced using http.server:

Create a packages.yml file as so

packages:
  - tarball: "http://secret_user:secret_password@localhost:8080/dbt_package.tar.gz"
    name: package_name

Obtain a valid dbt package file, and from the directory where it is stored, run python3 -m http.server 8080
run dbt deps

You should see output similar to:
13:44:29  Running with dbt=1.4.1
13:44:29  Installing package_name
13:44:29    Installed from tarball (url: http://secret_user:secret_password@localhost:8080/dbt_package.tar.gz)

what I would prefer to see is
13:44:29    Installed from tarball (url: http://***@localhost:8080/dbt_package.tar.gz)

Or something similar
Relevant log output
No response
Environment
- OS: Linux
- Python: 3.10.6
- dbt: 1.4.1

Which database adapter are you using with dbt?
other (mention it in "Additional Context")
Additional Context
(using dbt-athena-community adapter)

oh yes, of course I had forgotten about that - sorry!!
on the upside, I now know my way around the dbt-core codebase and test suites :joy:
silently deletes unnecessary fully formed fork
Thanks @jtcohen6 !


fix: dependabot

Status
READY
Description

Source: dependabot package-ecosystem
The correct yaml-value for Yarn in combination with dependabot is npm. This has been fixed. Now it should work.
In addition, the GitHub actions are now also kept up to date.

When I submitted the original we were having trouble getting it working. I use dependabot on all my projects but for some reason for this one its not picking it up and I wasn't sure if it was the way this GH project was set up.  Hopefully this does work though!

You also have to activate the Depedabot additionally in the repository settings.
@anymaniax @melloware Can you check this?


Document Tanzu cli install without the shell script

Description
Can we please document the manual steps to install the Tanzu CLI. While the shell scripts are nice sometimes they do things a user might not want (for example putting the tanzu binary in /usr/local/bin). It would be good if we could document

Download the binary
Run the initialization scripts
Any other tasks that should follow

@thesteve0
are you referring to the method shown here in the contributing guide?
https://tanzucommunityedition.io/docs/latest/contribute/contributing/#fetch-the-source

FWIW, I don't think it's a good idea to give users instructions on how to do their own custom install. We have a recommended location for the binary, and need other files in the correct place, so adding instructions and giving the impression that it's OK to move things wherever you like isn't a safe thing to do.
For those technically savvy enough, they can just take a look at the install.sh file to see what we are doing and try making changes. But then it's explicitly on them that they are deviating from the norm.

Hey Folks:
I see the Sean has some pretty strong complaints and I am sympathetic to them. Before Kay goes and tries to doc this perhaps we should discuss it a bit before she moves forward.
I think my main objection now is that

Without prompting the user, tt automatically removes a tanzu binary if it finds one in place
If there is a home bin directory it installs there by default but if not it tries to elevate privs and then put in /usr/local/bin

I see all the work the script is going but the TKG install is just
https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/1.5/vmware-tanzu-kubernetes-grid-15/GUID-install-cli.html#install-the-tanzu-cli-2
And would actually give the user more control over what happens.
Basically it comes down to, because of all the automagic, there is a potential to really mess things up for a user when running install.sh if they already have a tanzu cli version installed.

FWIW, I don't think it's a good idea to give users instructions on how to do their own custom install. We have a recommended location for the binary, and need other files in the correct place, so adding instructions and giving the impression that it's OK to move things wherever you like isn't a safe thing to do.

This right here. The other HUGE problem is that how you install everything changes between each and every release (if you look at the install script there is already commented out forward-looking code to handle Tanzu Framework 0.17.0). Most of the time it takes me like 2-4 days just to understand where the heck stuff needs to go in order for everything to install correctly. I would have a strong position that if the install isn't done by how it's prescribed by the install script, the configuration isn't supported.
@thesteve0 for your points:

Without prompting the user, tt automatically removes a tanzu binary if it finds one in place

The reason why it's like this is for the upgrade scenario. Since the binary is in the path, it's pretty much assumed that's the tanzu cli that you would use to runs commands with. Running the install scripts where a previous installation exists will upgrade (or in the very least "reset") the installation to that prescribed configuration. Please see https://github.com/vmware-tanzu/community-edition/issues/3597
To your point, we could warn the user saying "hey, we detected a previous install, do you want to install this version?" and also have a silent install for automation, scripting, etc. I plan on doing that in a PR to help address https://github.com/vmware-tanzu/community-edition/issues/3597

If there is a home bin directory it installs there by default but if not it tries to elevate privs and then put in /usr/local/bin

The $home/bin is a safe not global space to install the CLI. Otherwise, the prescribed location according to TKG is /usr/local/bin. We are just following TKG's prescribed way of install.

Basically it comes down to, because of all the automagic, there is a potential to really mess things up for a user when running install.sh if they already have a tanzu cli version installed.

The automatic is a good thing when has it not been? Most people don't care how it gets installed, they just want it installed correctly. I feel the install script does exactly what it needs to do (with some needed warnings perhaps - again will have a PR for that shortly). If the install script doesn't do exactly what it's supposed to do, that's a bug. I would be infinitely more concerned with users attempting to roll their own "new" installation method each and every release.

PTAL https://github.com/vmware-tanzu/community-edition/pull/4211


feat(plasma-manager): add support for konsole

Adds plasma manager modules support and Konsole support in plasma-manager module
Related: #215

Didn't found a good solution for it, so I will close it for now.


fix/support async retry config

fix(triggers): bulck create trigger delete old bug
fix(scf): support async retry config

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


resend email confirmation

Is there a way to resend the email confirmation link? It'd be nice if this was just a known endpoint already.

No there actually isn't. This would be a good place for a pull request :)
https://github.com/volatiletech/authboss/blob/master/confirm/confirm.go#L83
You can see that the confirm module only has one endpoint and that's to actually confirm the tokens it creates.

You should be able to do this now by calling this method:
https://github.com/volatiletech/authboss/blob/9ef2a06dcb6a99b2a33817131e506ee3fd695988/confirm/confirm.go#L110
Is this sufficient? It requires that you have an authboss instance, and use that to create a Confirm instance before you can call the method (since config etc. is given in that way), but I think that's pretty reasonable. Thoughts?

The above should work. Let me know if there's any problems with the approach.

For posterity, here's what I had to do:
 ab := authboss.New()
/* set up authboss */
confirmer := confirm.Confirm{Authboss: auth}
router.HandleFunc("/resend-confirmation", func(w http.ResponseWriter, r *http.Request) {
    user, err := auth.CurrentUser(r)
    if err != nil {
        handleNotAuthorized(w, r)
        return
    }
    confirmer.StartConfirmation(r.Context(), user.(authboss.ConfirmableUser), true)
    getDataAndSendTemplate(w, r, db, "auth/resend-confirmation.html")
})


Image Alt Text not added to PDF in DITA-OT 3.3.3 with Apache FOP formatter

Expected Behavior
Expect <image><alt>string</alt></image> to display alt text in PDF output using Apache FOP formatter. In Acrobat reader I would expect popup showing string and the audio screen reader to read the alternate text just as if I were to edit it in manually on an image using Microsoft Word or another PDF editor.
Actual Behavior
Used Apache FOP formatter with following command line: dita -i filename.ditamap -f pdf2
I checked code in topic_fop.xsl
<xsl:template match="*|@alt" mode="graphicAlternateText">
       <xsl:attribute name="fox:alt-text">
            <xsl:apply-templates select="." mode="text-only"/>
       </xsl:attribute>
 </xsl:template>

I checked the XSLT. It is running through the code and resolving the select statement as expected. But doesn't exhibit as alt text in the PDF output.
Actual Solution
Sorry, retract this. Not a bug. To answer my own question, the <accessibility> setting has to be added or configured as true in the fop.xconf file:
<fop version="1.0">
  <accessibility>true</accessibility>
  ...****

As described at the following link: Apache™ FOP: Accessibility
This solved the problem.
Steps to Reproduce

Using following command line:
dita -i:filename.ditamap -f pdf2

where dita files contained text string
Copy of the error message, log file or stack trace
No error messages, completed normally producing PDF file as expected.
Environment

DITA-OT version: DITA-OT 3.3.3

Operating system and version: Window 10
(Linux, macOS, Windows)

How did you run DITA-OT? startcmd, dita command, and in oXygen 21.1

Transformation type:
PDF2, in oxygen PDF FO and PDF CSS

Maybe you need to run the Apache FOP with the "-a" flag:
https://xmlgraphics.apache.org/fop/2.2/accessibility.html
or add:
 <accessibility>true</accessibility>

in the fop.xconf

Marking closed - based on the updated text in the description, this was resolved by updating the FOP configuration as Radu suggested.

If a question arises as to why the DITA OT does not enable accessibility by default in the PDFs, I think there are two problems:

PDF increases in size.
The Apache FOP processor has had in the past and may still have various bugs related to enabling this flag: https://github.com/dita-ot/docs/issues/64


RuleContext can return matched lexemes

This is needed to satisfy an order of setting something to model part edited with Hybrid Sync. See SimpleHybridSync which needs HybridProperty. To set into such a model, you need not parsed wrapper but list of tokens instead.

You need only tokens (lexeme.getValue()). Why can't you use myRuleContext.myValues through get(index) and getValueCount() in RuleContext? Isn't it the same thing you trying to expose?

Decided to introduce getLexemesValues() instead. This will reduce the boilerplate in the client code.


pre-commit: 3.3.1 -> 3.3.2

Diff: https://github.com/pre-commit/pre-commit/compare/v3.3.1...v3.3.2
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 232698 run on x86_64-linux 1

4 packages built:

commitizen
commitizen.dist
pre-commit
pre-commit.dist


Example ?

Any good example how to implement this library ?

It's depend on your usage but I think if you read README file it's easy to start your work with.

I will be create a simple example ASAP.

if downloading is interrupted because the user or system force to stop the app, it is possible to continue downloading in next app running?

No.
In this situation lib can't set download task state correctly because of that lib state machine can't start task.

why does downloading stops without any reason and onConnectionLost does not restart? how can l resolve this?
please help

@lekeCoder It's depends. In some cases because of server response time limitation this situation occur.

@majidgolshadi Thanks for your reply. I took a look at the code and adjusted among other things the thread portion that determines inactivity.
The issue now is it cannot download from https links. The last time l tried certificate issues came up. What can l do?


error "Killed"

Hello everyone, I'm encountering an issue with the Gradio application. After running the command "python3 -m demo.gradio_animate" and launching the Gradio application on port "http://<IP_ADDRESS>:7860/", I'm facing a problem. When I upload a video and image, after a few seconds, it displays the message "Killed" in the terminal, and the application shows a "Connection errored out" message. Can anyone provide assistance or guidance on resolving this issue?

I had the same issue running on Linux WSL. I had to reinstall CUDA for Linux.

i have the same problem. i think it is because of low vram when torch cat the image and video into grid. try a short densepose video

i have the same problem. i think it is because of low vram when torch cat the image and video into grid. try a short densepose video

when i have such problem it gives out of vram error. OOM

i guess it because RAM not enough(not VRAM). it seems the last merging step requires much RAM(based on your motion sequence).
maybe u can try cleaning cpu memory usage, lower motion mp4 fps or just cut your video into smaller part


Fixed a typo in the docs

Might seem small but caused me a bit of grief as resulted in getting back an empty list each time rather than any error as it used a different action method :).  Cheers for a useful project.

Actually, this isn't a typo. You'll notice that the action object in actstream/__init__.py is just the imported version from actstream.signals.py and that the action object in actstream/actions.py is also the same object. It's probably better to use the one that is in actstream/__init__.py as that is consistent, and imported specifically for your use.


upgrade spec package and simplify code

Describe the PR
upgrade spec package to 0.19.12 and simplify code
Relation issue
#806

Upgrading spec breaks tests since it changes the output slightly, see #835


How to disable eager mode?

Click to expand!
Issue Type
Support
Source
binary
Tensorflow Version
2.8
Custom Code
No
OS Platform and Distribution
Linux Ubuntu 20.04 in WSL2
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Is there a way to disable the eager mode globally in TensorFLow 2? I do not want to use the following command:
"tf.compat.v1.disable_eager_execution()"

as my trained keras model is kind of corrupted after reload from cache in Streamlit (see #57645 report)
Standalone code to reproduce the issue
import numpy as np
import matplotlib.pyplot as plt

import tensorflow as tf
from tensorflow.keras.models import Sequential
from tensorflow.keras.layers import Dense
from tensorflow.keras import Input
from tensorflow.keras.initializers import RandomNormal
from tensorflow.keras.optimizers import Adam

from datetime import datetime

import streamlit as st

# Do not use GPU
tf.config.set_visible_devices([], "GPU")
tf.compat.v1.disable_eager_execution()  # adding this line make keras training much slower

# Generate data
def f(x):
    return (x + 1) * np.sin(5 * x)

x_plot = np.arange(-1, 1 + 0.001, 0.001)
y_plot = f(x_plot)

x_train = np.arange(-1 + 0.05, 1, 0.2)
y_train = f(x_train)

x_val = np.arange(-1 + 0.15, 1, 0.2)
y_val = f(x_val)

# Plot the problem
plt.figure()
plt.plot(x_plot, y_plot, "-", label="Orgininal function")
plt.plot(x_train, y_train, "o", label="Training points")
plt.plot(x_val, y_val, "s", label="Validation points")
plt.xlim(-1, 1)
plt.ylim(-2, 2)
plt.xlabel("x")
plt.ylabel("f")
plt.grid()
plt.legend()
plt.show(block=False)

# Reshape
X_train = x_train.reshape(x_train.shape[0], 1)
Y_train = y_train.reshape(x_train.shape[0], 1)

X_val = x_val.reshape(x_val.shape[0], 1)
Y_val = y_val.reshape(x_val.shape[0], 1)

# Simple model
start_time = datetime.now()

@st.experimental_singleton
def train():
    tf.keras.utils.set_random_seed(1)
    model = Sequential()
    model.add(Input(shape=(1,)))  # Input layer
    model.add(
        Dense(
            4,
            activation="sigmoid",
            kernel_initializer=RandomNormal(mean=0.0, stddev=1.0, seed=1),
        )
    )
    model.add(Dense(1))

    model.compile(
        loss="mean_squared_error", optimizer=Adam(learning_rate=3e-1), run_eagerly=False
    )
    history = model.fit(
        X_train,
        Y_train,
        validation_split=0.0,
        validation_data=(X_val, Y_val),
        validation_freq=1,
        batch_size=X_train.shape[0],
        epochs=2000,
        verbose=0,
    )
    return model

run_time = datetime.now() - start_time

model2 = train()

print("Training time : {:.4f} s".format(run_time.total_seconds()))

st.write("Please rerun the app to see the error")

model2.predict(X_val)

Relevant log output
No response

Ok, So, you wants to disable the eager mode and meanwhile you don't wants to use "tf.compat.v1.disable_eager_execution()" this command. So, I think there is also another way to do so, because I researched a lot and found this answer( https://stackoverflow.com/questions/53429896/how-do-i-disable-tensorflows-eager-execution ). And I think this method will help you a lot as I found it on StackOverflow and Also in tried to implement it and this works for me perfectly. I think this is the correct answer for your issue

Thank you @sandy088, the line do the job disable the eager mode. But at last, my trained keras model is still corrupted after reload from cache in Streamlit. It seems like there is no problem with "tf.compat.v1.disable_eager_execution()" but something really changes inside Keras whether the eager mode is activated or not, which makes keras model not cacheable.


Fixing test builds for devices with softdevices.

Previously, .hex files were not copied when building source as a library.
This prevents builds that pre-compile source as a library and then includes the build directory as the only source (because there is no softdevice present). This PR adds an option to copy hex files when compiling source as a library. This is currently being used when compiling tests within test.py
Please review @0xc0170 and @screamerbg
FYI @pan-

What about static libraries, like there are bootloaders as static libs or just another software that can't be open sourced , but has to be included in the build?

Can we copy hex files by default?

Can we copy hex files by default and drop the parameter? This is for library builds afterall.

Can we copy hex files by default and drop the parameter? This is for library builds after all and do not affect application build.

I was hesitant to do this because I wasn't sure if the build_library function was used throughout the tools or just in this case. If you're confident this won't cause issues then I'm fine with making it the default behavior.

@bridadan see comments above. Dont modify build lib. its legacy

@mbed-bot: TEST
HOST_OSES=windows
BUILD_TOOLCHAINS=GCC_ARM,ARM
TARGETS=NRF51822,NRF51_DK

The build bot didn't try and build the tests locally, but I just tried. I'm getting the following linker error when building for the NRF51822 with GCC_ARM for many of the tests:
* NRF51822::GCC_ARM::RTOS_1
        Building project basic (NRF51822, GCC_ARM)
        Link: basic
        C:/Users/bridan01/Documents/dev/mbed/build/mbed/TARGET_NRF51822/TOOLCHAIN_GCC_ARM/NRF51822.ld:133 cannot move location counter backwards (from
 20004330 to 20003800)

@c1728p9 Do you know if this is because the tests are too big to fit in the ROM? I'm not familiar with this error

@bridadan To makes mbed BLE works with the RTOS work, the main stack size has been changed.
Apparently there is not enough memory left for the NRF51822, when this test is build.
Let me have a look, maybe it is possible to gain memory from elsewhere.

Thanks!! 👍

This is still not propagated to Nordic's repository and they cannot use it.
@sg- @pan- @bridadan

@screamerbg Do we need to resolve this? Or maybe @pan- can help them rebase/update their fork?

@bridadan You don't need do it, I will just cherry-pick your commit.


github-util: Update FROM version

Update underlying docker images.
Issue number: #1

@docktermj take a look at:  https://github.com/Senzing/docker-base-image-debian/issues/60


Fix branch encoding in upstream option (11.2)

https://github.com/axonivy/process-editor-client/pull/422


Logging and Metrics

I need to create much better logging. The program currently has pretty good logging but this is only true when watching the terminal in real time. I need to create actual txt logs so I can refer back to a file to see issues that happened in the past.
I also need to separate my logging form production, debugging, etc so I can turn certain logging on or off based on what stage the program is running in.

server metrics

resource usage
database size

collection sizes on a pie chart

accepted events per hour minute day average
average size of accepted event
uptime


Settings improvements

🚀 Feature

I would like to request few upgrades to the new settings feature

Use version information in the path to the settings file.
Why: napari dynamically updated the inner structure. There are also plans to store more things in settings. Then working on stable and development settings may often corrupt the settings file. Maybe also stable and development version of napari should be separated. Maybe use:
Path(user_config_dir(self._APPNAME, self._APPAUTHOR)) / packaging.version.parse(__version__).base_version

instead of Path(user_config_dir(self._APPNAME, self._APPAUTHOR))
But this also needs a mechanism of settings migration from the older version.

Does not use global settings object.
Why: When using napari from notebook user may open more than one napari Viewer instance. They should not share state so should not share settings object. Open multiple Viewer may be useful when preparing to meet and like to prepare few different views (without a wait for calculations on meeting).

Allow to simply provide a path to the directory where settings should be stored.
Why: I embed napari in my own application This application provides its own set of plugins etc. To avoid settings collision (especially when store plugins-related things in napari) I would like to store settings for the embedded instance application-specific directory. I think that it also will be useful for other persons who develop rich plugins.
This may be much easier with local settings object

Settings as EventedModel?
If I good understand now settings object is manually synchronized. It should rather be automatically two-way synchronized.

Question: Maybe I wrong read, but I do not see how safe_load from yaml will handle refactors which will take change name of a class or change of module in which it is implemented (I wrote about class serialization)?

Hi @Czaki thanks for bringing this up and starting this discussion.

Use version information in the path to the settings file.
Why: napari dynamically updated the inner structure. There are also plans to store more things in settings. Then working on stable and development settings may often corrupt the settings file. Maybe also stable and development version of napari should be separated. Maybe use:

Great point. Indeed, for dev versions we should probably use a different name. Noted!

But this also needs a mechanism of settings migration from the older version.

Migration is coming with the future work, thanks for brin gin this up!

Does not use global settings object.
Why: When using napari from notebook user may open more than one napari Viewer instance. They should not share state so should not share settings object. Open multiple Viewer may be useful when preparing to meet and like to prepare few different views (without a wait for calculations on meeting).

We are iterating on settings and having the global object was the initial use case, but the plan is to move from a global to more specific settings per viewer, but that requires making some changes to the Viewer interface and how some of these options are propagated, so definitely something we are working on. We will keep iterating :)

Allow to simply provide a path to the directory where settings should be stored.
Why: I embed napari in my own application This application provides its own set of plugins etc. To avoid settings collision (especially when store plugins-related things in napari) I would like to store settings for the embedded instance application-specific directory. I think that it also will be useful for other persons who develop rich plugins.
This may be much easier with local settings object

Absolutely! I completely agree with this. We will work on this. Might need to sync uop with you to get things going smoothly.

Settings as EventedModel?
If I good understand now settings object is manually synchronized. It should rather be automatically two-way synchronized.

Settings IS an evented model. We need a mapping from settings and the actual models in the viewers and layer so that the two way sync can be specified more automatically.

Question: Maybe I wrong read, but I do not see how safe_load from yaml will handle refactors which will take change name of a class or change of module in which it is implemented (I wrote about class serialization)?

This will be part of the version handling and update, not yet implemented but on the pipeline.

Thanks for bringing these points @Czaki, all very important and something we have considered. Sorry for the breakages!

Sometimes, even when taka patience sometimes my settings files got corrupted (migration fails). So I decide to split state persistence into multiple files (and got corruption only a part of the data). Maybe it could be a good approach for napari when increase amount of stored data?

Sometimes, even when taka patience sometimes my settings files got corrupted (migration fails). So I decide to split state persistence into multiple files (and got corruption only a part of the data). Maybe it could be a good approach for napari when increase amount of stored data?

It is something we have discussed, might be something that changes moving forward. Thanks for bringing this up!

With https://github.com/napari/napari/pull/5333 settings are per-environment.
But I dont think there is an easy way for someone to relocate the settings?
@Czaki maybe you can update OP with checkboxes for what still needs to be done? or is this closable +/- a new issue?


Flow infers wrong type for disjoint union sentinels.

Flow seems to infer the wrong type for a disjoint union discriminator. TryFlow example
type Action = { type: 'FOO', foo: number } | { type: 'BAR', bar: bool };

For any act: Action, it should infer act.type as the union of the sentinel values 'FOO' | 'BAR'. However it seems to infer some other type, causing wrong behavior.
This function compare should generate a Flow error:
const compare = (act: Action): void => {
  if (act.type === 'BAZ') {  // should error! BAZ ∉ Action.type
    console.log('found a BAZ');
  }
};

Specifically, it should generate the same error as if we'd explicitly defined the sentinel type:
type ActionType = 'FOO' | 'BAR';
const compare = (atype: ActionType): void => {
  if (atype === 'BAZ') {
    console.log('found a BAZ');
  }
};

// 3:   if (atype === 'BAZ') {
//                    ^ string literal `BAZ`. This type is incompatible with
// 2: const compare = (atype: ActionType): void => {
//                            ^ string enum

This is the root issue behind #4893, #5083, and likely others.
Workaround
We can force correct type checking for disjoint unions by using $PropertyType<Action, "type">. The code and the resulting error are much more verbose, and we have to remember to use it every time, but hey it works ¯\(ツ)/¯
const compare = (act: Action): void => {
  const actType: $PropertyType<Action, "type"> = act.type;
  if (actType === 'BAZ') {
    console.log('found a BAZ');
  }
};

// 3:   if (actType === 'BAZ') {
//                      ^ string literal `BAZ`. This type is incompatible with
// 2:   const actType: $PropertyType<Action, "type"> = act.type;
//                     ^ union: property type(s)
// Member 1:
// 2:   const actType: $PropertyType<Action, "type"> = act.type;
//                     ^ property typeError:
// 3:   if (actType === 'BAZ') {
//                      ^ string literal `BAZ`. This === check always fails because `BAZ` is not the same string as `FOO`
// 2:   const actType: $PropertyType<Action, "type"> = act.type;
//                     ^ string literal `FOO`
// Member 2:
// 2:   const actType: $PropertyType<Action, "type"> = act.type;
//                     ^ property typeError:
// 3:   if (actType === 'BAZ') {
//                      ^ string literal `BAZ`. This === check always fails because `BAZ` is not the same string as `BAR`
// 2:   const actType: $PropertyType<Action, "type"> = act.type;
//                     ^ string literal `BAR`

This problem also seem to affect switch cases.
export type Msg =
    | {type: 'NoOp', data: void}
    | {type: 'SetText', data: string}

const update = (mdl: Model, msg: Msg): Model => {
    const msgType: $PropertyType<Msg, "type"> = msg.type;

    switch(msgType) {

        case 'NoOp':
            return mdl;

        case 'SetText':
            const newModel = merge(mdl, {text: msg.data});
            return newModel;

        //Should throw error or at least a warning?
        case 'Uggachaka':
            return mdl;

        default:
            throw 'error';
}

Worth noting though that
const update = (mdl: Model, msg: Msg): Model => {
    const msgType: $PropertyType<Msg, "type"> = msg.type;

    switch(msgType) {

        case 'NoOp':
            return mdl;

        //With this order throws an error
        case 'Uggachaka':
            return mdl;

        case 'SetText':
            const newModel = merge(mdl, {text: msg.data});
            return newModel;

        default:
            throw 'error';
}

Throws an error. So that's good at least.
I also found that the flow doesn't throw any errors with tuples so if you have:
type Msg =
    | ['NoOp', void]
    | ['SetText', string]

const update = (mdl: Model, msg: Msg): Model => {
    switch(msg[0]) {

        case 'NoOp':
            return mdl;

        //Should throw error but doesn't
        case 'Uggachaka':
            messupeverything();
            return mdl;

        case 'SetText':
            const newModel = merge(mdl, {text: msg[1]});
            return newModel;

        default:
            throw 'error';
}

we have the same problem as well.

Fixed by Flow 0.58! 🎉🎉🎉


[GLUTEN-4615][CH] Cover more cases in RewriteDateTimestampComparisonRule

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
Fixes: #4615
How was this patch tested?
(Please explain how this patch was tested.


Object 'this' properties

I got the following dynamic object:
PERSON_NAME
DEPARTMENT_NAME

With the classes:
class Person
{
public string Name {get;set;}
public Department Department {get;set;
}

class Department
{
public string Name {get;set;}
}

When using the Automapper the Department object is created and the name is filled. Due the PERSON_ prefix for this object the Person.Name is not filled. Is there any way to achieve this without editing the raw dynamic data?

HI @xzaz
Are you using the last version of Slapper? 1.0.7. If true: can you create test for this error?
Thanks...

https://github.com/xzaz/Slapper.AutoMapper/commit/79c39887c0f2d89849e138481ab4daaa676e0d53

Hi @xzaz
In your ExpandoObject Person, person.PERSON_NAME is incorrect. In your object person, the property is called Name
This test pass!
[Test]
public void Can_Populate_Self_Object_Properties()
{
	dynamic person = new ExpandoObject();
	person.NAME = "Clark"; // Changed PERSON_NAME by NAME
	person.DEPARTMENT_NAME = "IT";

	var list = new List<dynamic> { person };

	var pPerson = Slapper.AutoMapper.MapDynamic<Person>(list).FirstOrDefault();

	Assert.NotNull(pPerson);
	Assert.NotNull(pPerson.Name);
	Assert.NotNull(pPerson.Department.Name);
}

if you can't edit or change the raw dynamic data, then the property Name in class Person, must be called Person_Name.
public class Person
{
       public string Person_Name { get; set; }
       public Department Department { get; set; }
}

So yes, that is the 'problem' I want to map the PERSON_ to the this object. Or is this against the rules?

https://github.com/xzaz/Slapper.AutoMapper/commit/3f4c551d8c26fc7efceb9074a4c2c56d0e8fab38
This does it for me, everything checks out. Meh.

Sorry @xzaz
This is against the rules... you can change class Person if can't edit or change the raw dynamic data.


点击群组里面的小视频后一直循环播放，无法关闭小视频

Description
First of all, thanks for your attention to open an issue for this project.
Please notice that if you are requesting a feature, then you should give a brief description of your request.
If you are reporting a bug, please follow the template below.
A bug report without detailed information required will have a very low priority and even be ignored (closed directly)!
Specifications

Version of Electron (run $ electron --version): v2.0.0
OS: <Linux voiue-pc 3.13.0-117-generic #164~precise1-Ubuntu SMP Mon Apr 10 16:16:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux>
Stack trace from the error message (if any)

<点击群组里面的小视频后一直循环播放，无法关闭小视频只能强行退出应用>

个人做法：把框拉大，然后点击视频外的空白，就能自动关闭

我也遇到这个问题,试试楼上的方法

亲测有效。On Feb 14, 2018 21:07, autowander<EMAIL_ADDRESS>wrote:我也遇到这个问题,试试楼上的方法
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.


iOS angle render bug

G2 Version: 4.0.6
Platform: iOS Mobile
Mini Showcase(like screenshots):

Expected:

Result:

CodePen Link: https://codepen.io/matheuslbenachio/pen/RwWrVvO

In Iphone in some cases the start angle and end angle bug out, and a little 'spike' appears in the start of the angle.
This only happen if you specify 'startAngle' and 'endAngle', if the chart is a full circle this doesn't happen.
It only happens in chrome and safari iOS, not android.

fixed.


squid4: 4.6 -> 4.7

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/squid/versions.
meta.description for squid4 is: '"A caching proxy for the Web supporting HTTP, HTTPS, FTP, and more"'.
meta.homepage for squid4 is: '"http://www.squid-cache.org"

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 4.7 with grep in /nix/store/hh1sgscfangpma9z3rp5fgh2976dd7fz-squid-4.7
directory tree listing: https://gist.github.com/f58581ef6bd07fab36bb73fbd485b3ba
du listing: https://gist.github.com/bf301d014b590b2194df13448a940f1a

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

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
squid4

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hh1sgscfangpma9z3rp5fgh2976dd7fz-squid-4.7 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A squid4 https://github.com/r-ryantm/nixpkgs/archive/48178d947f70ba21a47cccb30de422c771e4b052.tar.gz

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

cc @fpletz @7c6f434c for testing.

Changelog seems fine


updating name of last alarm

Updating alarm name of last alarm with "default" name

Should this be linked to a Jira issue?

Should this be linked to a Jira issue?

Yes, but it so minor change that I do not create a task for it.


Results on PATTERN

Hi,
Thank you for your impressive work. I try to reproduce the results of SAN and GatedGCN on PATTERN using GraphGPS framework. The results are all around 89.9 test accuracy, which are significantly higher than the results reported in the paper (~85.6 test accuracy).
I understand that you report the results from benchmarking gnn. May I ask if you have encountered same issue during the experiments?
The config file I use is in config.zip
Thank you!
Yiming

Hi @MatthewCYM,
Thank you for bringing this up and sorry for the delay. I found that there was a mistake in GraphGPS evaluation, I used plain accuracy as the evaluation metric, and not the weighted accuracy. I have now fixed the code and redone the GPS experiments, please see #12 .
Best,
Ladislav


BlobCacheSettings Issue when trying to declare same URL with different zone;

Details of the scenario you try and problem that is occurring:
Imagine the case where you have a DSC configuration that declares two different BlobCacheSettings, for the same Web Application, but for a different Zone. Trying to compile such a resource gives an error similar to the following:
Test-ConflictingResources : A conflict was detected between resources
'[SPBlobCacheSettings]5daeca26-879d-4f5b-be9f-7270aa6551d1 (C:\temp\SP-Farm.DSC.ps1::584::9::SPBlobCacheSettings)' and '[SPBlobCacheSettings]ef14ea31-4cd6-41ad-8920-f7fd9de1aee4 (C:\temp\SP-Farm.DSC.ps1::595::9::SPBlobCacheSettings)' in node 'MVA-APP'. Resources have identical key properties but there are differences in the following non-key properties:
'Zone'. Values 'Default' don't match values 'Intranet'. Please update these property values so that they are identical in both cases.
when looking at the *.schema.mof file, I off course see that while the Zone parameter is marked as required, that only the WebAppUrl parameter is identified as a Key. Can't we also make the Zone a Key parameter to solve this issue?
The DSC configuration that is using the resource:
[...]
SPBlobCacheSettings 5daeca26-879d-4f5b-be9f-7270aa6551d1
{
MaxSizeInGB = 10;
PsDscRunAsCredential = $Credssp_farm;
FileTypes = ".(gif|jpg|jpeg|jpe|jfif|bmp|dib|tif|tiff|themedbmp|themedcss|themedgif|themedjpg|themedpng|ico|png|wdp|hdp|css|js|asf|avi|flv|m4v|mov|mp3|mp4|mpeg|mpg|rm|rmvb|wma|wmv|ogg|ogv|oga|webm|xap)$";
EnableCache = $False;
Location = "C:\BlobCache\14";
MaxAgeInSeconds = 0;
Zone = "Default";
WebAppUrl = "http://mva-wfe/";
}
SPBlobCacheSettings ef14ea31-4cd6-41ad-8920-f7fd9de1aee4
{
MaxSizeInGB = 10;
PsDscRunAsCredential = $Credssp_farm;
FileTypes = ".(gif|jpg|jpeg|jpe|jfif|bmp|dib|tif|tiff|themedbmp|themedcss|themedgif|themedjpg|themedpng|ico|png|wdp|hdp|css|js|asf|avi|flv|m4v|mov|mp3|mp4|mpeg|mpg|rm|rmvb|wma|wmv|ogg|ogv|oga|webm|xap)$";
EnableCache = $False;
Location = "C:\BlobCache\14";
MaxAgeInSeconds = 0;
Zone = "Intranet";
WebAppUrl = "http://mva-wfe/";
}
[...]
Version of the Operating System and PowerShell the DSC Target Node is running:
Win Server 2016/WMF 5.1
Version of the DSC module you're using:
<IP_ADDRESS>

Agree that zone should be a key as well, adding to the backlog

Will be changed in my next Rollup PR

This has been rolled in to dev and will be included in our next release. Closing this issue.


$psStyle.FormatHyperlink should passthru in build environments

Summary of the new feature / enhancement
As the author of many formatting files, I want to make hyperlinked formatters.
Unfortunately, within certain environments, like GitHub Workflows, hyperlinks will not render.
Rather than show nothing, $psStyle.FormatHyperlink should ideally be intelligent enough to pass thru under certain conditions.
Proposed technical implementation details (optional)
As loathe as I am to introduce anything like strong coupling, I see the easiest path between two points here to be:

Make a list of environment variables that do hint hyperlink formatting is not present
If any of these are present, $psStyle.FormatHyperlink should return the text (without the hyperlink)

To start off that list:

$env:GITHUB_WORKSPACE indicates you are within a GitHub workflow.

Could you show some example? It's not entirely clear what you are proposing.
psStyle.FormatHyperlink() is a method where you format a hyperlink and get the desired result.

@237dmitry if you run that method within a GitHub workflow, you'll get
"The is a [LITERAL BLANK] hyperlink"
The syntax sugar works, it just does not gracefully degrade in contexts that do not support it.
Make sense?