[release-1.4] Update proxy sha to include mixerless telemetry fixes

This is an automated cherry-pick of #17925

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-galley-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-galley-k8s-tests_istio_release-1.4

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-galley-k8s-tests_istio_release-1.4

/test integ-security-k8s-tests_istio_release-1.4

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

e2e-simpleTests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test e2e-simpleTests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

integ-security-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-security-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-security-k8s-tests_istio_release-1.4

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

integ-pilot-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-pilot-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

pilot-e2e-envoyv2-v1alpha3_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test pilot-e2e-envoyv2-v1alpha3_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

pilot-e2e-envoyv2-v1alpha3_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test pilot-e2e-envoyv2-v1alpha3_istio_release-1.4

e2e-simpleTests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test e2e-simpleTests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

pilot-e2e-envoyv2-v1alpha3_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test pilot-e2e-envoyv2-v1alpha3_istio_release-1.4

e2e-simpleTests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test e2e-simpleTests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test e2e-simpleTests_istio_release-1.4

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test integ-mixer-k8s-tests_istio_release-1.4

unit-tests_istio_release-1.4
63fbdf43017681407a85c6eed49516db706e0db6
link
/test unit-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


fix support check authorization for view but skip check in the view

Proposed changes
pick from master #31289

run buildall

run buildall

run buildall


[ADD] DCOS-993 Install script functionality to optionally add dcos to path

Won't this overwrite their python with the virtualenv's python?

We currently ask the user to source $ENV_SETUP at the end of that script: https://github.com/mesosphere/dcos-cli/pull/265/files#diff-d91144fb7701278fd2baa5eed67ff3faR101
I think we need to clean up our messaging. @ssk2 Can you help here?
What about Windows? Is this a Linux/MacOS feature only or should we implement this for Windows too?
Also, do we need to change the DCOS documentation? The DCOS UI? @ssk2 Please follow up on this.

@mgummelt - if the path to dcos/bin is appended to their PATH then it shouldn't overwrite their system Python (since it looks in the left most location first, etc.).

@ytalashkocv - can we change this so that if the user has said yes to adding DCOS to their path it prints:
source ~/.bashrc && dcos help (or whatever their bash profile file is).
If they say no, print the current output (i.e.  echo "source $ENV_SETUP && dcos help")

@jsancio - Adding this to Windows is a good idea too. @ytalashkocv - could you add this to the Powershell script too?

@jsancio, @ytalashkocv  - is it worth checking to see if a user already has DCOS in their path and removing/replacing if so?

@jsancio - DCOS UI doesn't need updating. We will want to update the docs. I have created DOCS-90 to track this.

@ssk2 PR updated

@truskovskiyk Can you add a new line before and after the modify message (Modify your bash profile to add DCOS to your PATH? [yes/no]) please?

@ytalashkocv - this doesn't quite work as intended since we rely on DCOS_CONFIG being set which is done by the env-setup script. However, once #314 lands, this will no longer be necessary - so we should only merge this after that.

@ytalashkocv - the script doesn't appear to work on Windows 8.1 for me:
PS C:\dcos-993> wget https://raw.githubusercontent.com/mesosphere/dcos-cli/dcos-993/win_bin/install/install-dcos-cli.ps1
 -OutFile install.ps1
PS C:\dcos-993> .\install.ps1 . http://dcos.com
At C:\dcos-993\install.ps1:109 char:23
+     $NewPath = $OldPath + â?T;â?T + $AddedLocation
+                          ~
You must provide a value expression following the '+' operator.
At C:\dcos-993\install.ps1:109 char:24
+     $NewPath = $OldPath + â?T;â?T + $AddedLocation
+                           ~~~
Unexpected token 'â?T' in expression or statement.
At C:\dcos-993\install.ps1:116 char:73
+     $yes = New-Object System.Management.Automation.Host.ChoiceDescription "&Yes", `
+                                                                            ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double
quotation marks ("&") to pass it as part of a string.
At C:\dcos-993\install.ps1:118 char:72
+     $no = New-Object System.Management.Automation.Host.ChoiceDescription "&No", `
+                                                                           ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double
quotation marks ("&") to pass it as part of a string.
At C:\dcos-993\install.ps1:119 char:14
+         "No, don't add DCOS to PATH."
+                 ~~~~~~~~~~~~~~~~~~~~~
The string is missing the terminator: '.
At C:\dcos-993\install.ps1:106 char:1
+ {
+ ~
Missing closing '}' in statement block.
    + CategoryInfo          : ParserError: (:) [], ParseException
    + FullyQualifiedErrorId : ExpectedValueExpression

Could we add support for zsh too? You can add the same line to the ~/.zshrc file.

@ssk2 PR Updated. Please re-review.

@ssk2 please review

@ssk2 Can we merge this?

@jsancio nope, I'd like to test it.

@ytalashkocv - this change is better but I'd like to avoid adding the line multiple times to the users' path. When I installed it twice, my .bashrc had:
# path to the DCOS CLI binary
if [[ "$PATH" != *"/home/vagrant/dcos/bin"* ]];
  then export PATH=$PATH:/home/vagrant/dcos/bin;
fi

# path to the DCOS CLI binary
if [[ "$PATH" != *"/home/vagrant/dcos/bin"* ]];
  then export PATH=$PATH:/home/vagrant/dcos/bin;
fi

Is there a way to avoid having this twice in the users' .bashrc? Our recommended upgrade procedure is to run this script everytime the user wants to upgrade to a new version of the CLI.

@ytalashkocv - actually you can remove .zshrc support. I think this will add too much complexity.

@ytalashkocv - I'm still seeing errors on Windows. Is there something extra I need to do?
At C:\dcos\install.ps1:116 char:73
+     $yes = New-Object System.Management.Automation.Host.ChoiceDescription "&Yes", `
+                                                                            ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double
quotation marks ("&") to pass it as part of a string.
At C:\dcos\install.ps1:118 char:72
+     $no = New-Object System.Management.Automation.Host.ChoiceDescription "&No", `
+                                                                           ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double
quotation marks ("&") to pass it as part of a string.
At C:\dcos\install.ps1:119 char:14
+         "No, don't add DCOS to PATH."
+                 ~~~~~~~~~~~~~~~~~~~~~
The string is missing the terminator: '.
At C:\dcos\install.ps1:105 char:1
+ {
+ ~
Missing closing '}' in statement block.
    + CategoryInfo          : ParserError: (:) [], ParseException
    + FullyQualifiedErrorId : AmpersandNotAllowed

PS C:\dcos>```

@ssk2 About this comment https://github.com/mesosphere/dcos-cli/pull/265#issuecomment-137886910 I can mach this lines in .bashrc and replace them, but this lines too common and user can also made some changes in his/her .bashrc. Also remove .zshrc support and fix windows install script.

@ytalashkocv - that's a valid point. Let's leave as is for the moment and we'll update the documentation accordingly.


Move documentation to read the docs

On the current Github pages we only have the latest documentation, RTD could automatically keep a version live for each PowerSensor release.

Done in #171


Unable to ignoreQueryParams per request basis

The current implementation doesn't support setting ignoreQueryParams on a per-request basis due to its reliance on the global mockAddonConfigs.
A workaround to add this feature in the Story not requests involves providing a default value for globalMockData in the Story parameters when not using the global config. However, this approach can be inconvenient if a global config is already defined.
If you have not specified globalMockData but only ignoreQueryParams it would fail on the spread operator.
This limitation was noted in the latest release, as seen in the merge request.

1


Update Composer dependencies (2024-06-22-00-17)

Visual regression test passed!
View the visual regression test report


Client-side Dynamic Routing bug in combination with Static Export

Bug report
Describe the bug
I have a single page, pages/index.js, that hides/shows 4 modals in response to the activeSection query param, with routes aliased like this:
// next.config.js.exportPathMap
      '/': { page: '/' },
      '/about': {
        page: '/',
        query: { activeSection: 'about' },
      },
      // ...

// server.js
server.get('/about', (req, res) => {
    const actualPage = '/';
    const queryParams = { activeSection: 'about' };
    app.render(req, res, actualPage, queryParams);
  });

// pages/index.js
<Link href="/?activeSection=about" as="/about">
      About
</Link>

In development (the context in which this bug occurs), I'm using an Express server, but for production, I have the project configured to statically export a page for each active section (/about/index.html, /store/index.html, etc) so I can serve it on S3 and have SEO for each page.
When I click on a Link to a dynamic route, the page doesn't re-render and my UI doesn't update.  If I remove the exportPathMap key from my next.config.js, dynamic routes do work.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Check out my sample project
git clone https://github.com/wkentdag/next-bug
3.cd next-bug && npm i && npm start
Navigate to localhost:3000, click on nav links, observe that nothing happens
Quit server, comment out exportPathMap key from next.config.js, restart server
Note that routes update as expected when clicked
uncomment exportPathMap and run npm run export && npm run serve, note that dynamic routing works in this context

Expected behavior
I expect the route to update and UI to re-render when links are clicked in any context (server-side, static, or client-side)
System information

OS: macOS
Browser: chrome
Version of Next.js: 6.0.3

Additional context

Once I export the project as static, dynamic links do work as expected
If you directly link to a dynamic route, e.g. localhost:3000/about, the page will display correctly, and it will also update whenever you click on a link on the page 🤔
I thought I had the same problem described in https://github.com/zeit/next.js/issues/3257 but as you can see I already am using getInitialProps and have isolated my issue to the static export thing.

This appears to be working fine in the latest version of Next.js so I am going to close this issue. If you are still having trouble with this feel free to comment.


a11y: focus lost after pressing ESC

You do seem to put the focus back on the element that triggered the lightbox when the user clicks the Close button. But when the user presses ESC, the focus jumps to the body element.

I cannot reproduce this. Can you give some more informations? Lity version, Browser etc.

I simply checked on your demo page: http://sorgalla.com/lity/ It happened on Chrome 56.
Steps to reproduce:

click the Image button/link
wait for image load
press ESC

The focus is not back on the  Image button/link as it should be.
However, if you do:

click the Image button/link
wait for image load
click the cross

the Focus is back where it was before the lightbox opened.

Ah yes, the site used an older version of Lity. I've updated the site, check again ;)

That's better!


[Storage] Deprecate str and dict[str, str] as types for crednetials

Currently the credential arguments of all Storage clients/functions except many types including str and dict[str, str] where str is meant to be the account key and dict[str, str] is meant to be the account name and key in dictionary form.
Now that we support AzureNamedKeyCredential to specify an account name/key, we should deprecate both str and dict[str, str] in favor of this as this would be the preferred/recommended way to supply an account key. Additionally, this should help to address confusion around needing to specify the account name when using a non-standard account URL as AzureNamedKeyCredential always requires the account name.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Storage:0.5315591,Azure.Identity:0.32559848,KeyVault:0.02075138'


does codis-proxy support HA ? haproxy is so bad , becauseof Network bottleneck .

assume  codis-proxy1 and codis-proxy2 are alive ,
client connect to both proxy , if codis-proxy1 down ,will  cient visit  codis-proxy1 ?

sorry ! after few seconds , I found jodis has resolved my question , jodis can detect dead proxy . https://github.com/wandoulabs/codis/tree/master/extern/jodis


Redis handler fix

Codecov Report

Merging #29 into master will increase coverage by 5.42%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #29      +/-   ##
==========================================
+ Coverage   52.89%   58.31%   +5.42%
==========================================
  Files           8        8
  Lines         484      475       -9
==========================================
+ Hits          256      277      +21
+ Misses        228      198      -30

Impacted Files
Coverage Δ

pipert/core/message_handlers.py
86.79% <100%> (+46.46%)
:arrow_up:

Continue to review full report at Codecov.

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


update the uploader on bignum

This issue was originally filed by @financeCoding

The uploader email address is no longer valid, can someone update it to<EMAIL_ADDRESS>http://pub.dartlang.org/packages/bignum
Thanks!

This issue has been moved to dart-lang/pub#444.


FXChain API platform compatibility fixes and master track support

More bugfixes and feature improvement for CF_GetFocusedFXChain, CF_GetTrackFXChain and CF_EnumSelectedFX.

:x: Build sws 318-master failed (commit https://github.com/reaper-oss/sws/commit/eb12b81d49 by @cfillion)

:white_check_mark: Build sws 318-master completed (commit https://github.com/reaper-oss/sws/commit/eb12b81d49 by @cfillion)

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=armv7l

build/sws-<IP_ADDRESS>-Linux-armv7l-getfocusedfxchain-v2.12.1-eb12b81d.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=aarch64

build/sws-<IP_ADDRESS>-Linux-aarch64-getfocusedfxchain-v2.12.1-eb12b81d.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x64

build/sws-<IP_ADDRESS>-Windows-x64-getfocusedfxchain-v2.12.1-eb12b81d.exe
build/reaper_sws-x64.pdb
build/BuildUtils/whatsnew.html
build/BuildUtils/SWS_Template.ReaperLangPack

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Visual Studio 2019, ARCH=x86

build/sws-<IP_ADDRESS>-Windows-x86-getfocusedfxchain-v2.12.1-eb12b81d.exe
build/reaper_sws-x86.pdb
build/BuildUtils/whatsnew.html
build/BuildUtils/SWS_Template.ReaperLangPack

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=i686

build/sws-<IP_ADDRESS>-Linux-i686-getfocusedfxchain-v2.12.1-eb12b81d.tar.xz

Environment: APPVEYOR_BUILD_WORKER_IMAGE=Ubuntu1804, ARCH=x86_64

build/sws-<IP_ADDRESS>-Linux-x86_64-getfocusedfxchain-v2.12.1-eb12b81d.tar.xz


abstract model names <Noun> -> Model

updated

@contra updated, it now gets the current directory and uppercases the first letter

Might be over-engineered, I don't think its a big deal to write the model name

updated


Memory leak when running test49 introduced by patch 8.2.0823

Running test49.out with the leak sanitizer shows memory leaks in vim-8.2.0877 and older:
$ git diff
diff --git a/src/Makefile b/src/Makefile
index 520ef0b93..9521379e4 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -702,6 +702,7 @@ LINT_OPTIONS = -beprxzF
 # When running tests output can be found in testdir/asan.*
 #SANITIZER_CFLAGS = -g -O0 -fsanitize=address -fno-omit-frame-pointer
 #SANITIZER_CFLAGS = -g -O0 -fsanitize=undefined -fno-omit-frame-pointer
+SANITIZER_CFLAGS = -g -O0 -fsanitize=leak -fno-omit-frame-pointer
 SANITIZER_LIBS = $(SANITIZER_CFLAGS)

 # MEMORY LEAK DETECTION
@@ -709,7 +710,7 @@ SANITIZER_LIBS = $(SANITIZER_CFLAGS)
 # Configuration is in the .ccmalloc or ~/.ccmalloc file.
 # Doesn't work very well, since memory linked to from global variables
 # (in libraries) is also marked as leaked memory.
-#LEAK_CFLAGS = -DEXITFREE
+LEAK_CFLAGS = -DEXITFREE
 #LEAK_LIBS = -lccmalloc

 # Uncomment this line to have Vim call abort() when an internal error is

$ export ASAN_OPTIONS="abort_on_error=0:detect_leaks=1"
$ ./configure --with-features=huge --enable-gui=none
$ make -j8
$ cd src/testdir
$ make test49.out
...snip...
Press ENTER or type command to continue

=================================================================
==32397==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 16 byte(s) in 1 object(s) allocated from:
    #0 0x7f289506417d in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/liblsan.so.0+0xf17d)
    #1 0x560ef5c105f7 in lalloc /home/pel/sb/vim/src/misc2.c:925
    #2 0x560ef5c104a2 in alloc /home/pel/sb/vim/src/misc2.c:828
    #3 0x560ef5c10b2f in vim_strsave /home/pel/sb/vim/src/misc2.c:1281
    #4 0x560ef5ca5679 in estack_sfile /home/pel/sb/vim/src/scriptfile.c:129
    #5 0x560ef5b9a8ed in cause_errthrow /home/pel/sb/vim/src/ex_eval.c:293
    #6 0x560ef5d9821d in emsg_core /home/pel/sb/vim/src/message.c:650
    #7 0x560ef5d9847e in emsg /home/pel/sb/vim/src/message.c:748
    #8 0x560ef5b7616d in ex_unletlock /home/pel/sb/vim/src/evalvars.c:1445
    #9 0x560ef5b75ea2 in ex_unlet /home/pel/sb/vim/src/evalvars.c:1373
    #10 0x560ef5b8f353 in do_one_cmd /home/pel/sb/vim/src/ex_docmd.c:2511
    #11 0x560ef5b8c5f5 in do_cmdline /home/pel/sb/vim/src/ex_docmd.c:979
    #12 0x560ef5ca8036 in do_source /home/pel/sb/vim/src/scriptfile.c:1401
    #13 0x560ef5ca7381 in cmd_source /home/pel/sb/vim/src/scriptfile.c:950
    #14 0x560ef5ca73cd in ex_source /home/pel/sb/vim/src/scriptfile.c:976
    #15 0x560ef5b8f353 in do_one_cmd /home/pel/sb/vim/src/ex_docmd.c:2511
    #16 0x560ef5b8c5f5 in do_cmdline /home/pel/sb/vim/src/ex_docmd.c:979
    #17 0x560ef5b8bb72 in do_cmdline_cmd /home/pel/sb/vim/src/ex_docmd.c:590
    #18 0x560ef5d941d8 in exe_commands /home/pel/sb/vim/src/main.c:3144
    #19 0x560ef5d90d2a in vim_main2 /home/pel/sb/vim/src/main.c:789
    #20 0x560ef5d906a0 in main /home/pel/sb/vim/src/main.c:438
    #21 0x7f28932adb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96)

SUMMARY: LeakSanitizer: 16 byte(s) leaked in 1 allocation(s).

shell returned 23
...snip...
Press ENTER or type command to continue

=================================================================
==322==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 27 byte(s) in 1 object(s) allocated from:
    #0 0x7f846e8f017d in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/liblsan.so.0+0xf17d)
    #1 0x56126a4425f7 in lalloc /home/pel/sb/vim/src/misc2.c:925
    #2 0x56126a4424a2 in alloc /home/pel/sb/vim/src/misc2.c:828
    #3 0x56126a4d7716 in estack_sfile /home/pel/sb/vim/src/scriptfile.c:146
    #4 0x56126a3cc8ed in cause_errthrow /home/pel/sb/vim/src/ex_eval.c:293
    #5 0x56126a5ca21d in emsg_core /home/pel/sb/vim/src/message.c:650
    #6 0x56126a5ca576 in semsg /home/pel/sb/vim/src/message.c:776
    #7 0x56126a55a5cd in emsg_funcname /home/pel/sb/vim/src/userfunc.c:543
    #8 0x56126a55a8af in get_func_tv /home/pel/sb/vim/src/userfunc.c:615
    #9 0x56126a5625d8 in ex_call /home/pel/sb/vim/src/userfunc.c:3810
    #10 0x56126a3c1353 in do_one_cmd /home/pel/sb/vim/src/ex_docmd.c:2511
    #11 0x56126a3be5f5 in do_cmdline /home/pel/sb/vim/src/ex_docmd.c:979
    #12 0x56126a55c517 in call_user_func /home/pel/sb/vim/src/userfunc.c:1376
    #13 0x56126a55cb73 in call_user_func_check /home/pel/sb/vim/src/userfunc.c:1517
    #14 0x56126a55da3b in call_func /home/pel/sb/vim/src/userfunc.c:1964
    #15 0x56126a55a855 in get_func_tv /home/pel/sb/vim/src/userfunc.c:606
    #16 0x56126a5625d8 in ex_call /home/pel/sb/vim/src/userfunc.c:3810
    #17 0x56126a3c1353 in do_one_cmd /home/pel/sb/vim/src/ex_docmd.c:2511
    #18 0x56126a3be5f5 in do_cmdline /home/pel/sb/vim/src/ex_docmd.c:979
    #19 0x56126a55c517 in call_user_func /home/pel/sb/vim/src/userfunc.c:1376
    #20 0x56126a55cb73 in call_user_func_check /home/pel/sb/vim/src/userfunc.c:1517
    #21 0x56126a55da3b in call_func /home/pel/sb/vim/src/userfunc.c:1964
    #22 0x56126a55a855 in get_func_tv /home/pel/sb/vim/src/userfunc.c:606
    #23 0x56126a5625d8 in ex_call /home/pel/sb/vim/src/userfunc.c:3810
    #24 0x56126a3c1353 in do_one_cmd /home/pel/sb/vim/src/ex_docmd.c:2511
    #25 0x56126a3be5f5 in do_cmdline /home/pel/sb/vim/src/ex_docmd.c:979
    #26 0x56126a4da036 in do_source /home/pel/sb/vim/src/scriptfile.c:1401
    #27 0x56126a4d9381 in cmd_source /home/pel/sb/vim/src/scriptfile.c:950
    #28 0x56126a4d93cd in ex_source /home/pel/sb/vim/src/scriptfile.c:976
    #29 0x56126a3c1353 in do_one_cmd /home/pel/sb/vim/src/ex_docmd.c:2511

SUMMARY: LeakSanitizer: 27 byte(s) leaked in 1 allocation(s).

shell returned 23

Press ENTER or type command to continue
...snip...
Press ENTER or type command to continue
-----------------------------------------------------
Suppressions used:
  count      bytes template
      7        652 libXt.so.6
-----------------------------------------------------

# For flaky tests retry one time.  No tests at the moment.
#@/bin/sh -c "if test -f test.out -a test49 = test61; then \
#	  if diff test.out test49.ok; \
#	  then echo flaky test ok first time; \
#	  else rm -rf test49.failed test.out X* viminfo; \
#		VIMRUNTIME=../../runtime  ../vim -f  -u unix.vim -U NONE --noplugin --not-a-term -s dotest.in test49.in; \
#	  fi \
#	fi"
# Check if the test.out file matches test.ok.
rm -rf X* test.ok viminfo

The test passes despite detecting leaks.
Doing a git bisection, I see that there is no leak in
vim-8.2.0822 and the leak starts in vim-8.2.0823. So this
change introduced the leak:
commit 25e0f5863e9010a75a1ff0d04e8f886403968755
Author: Bram Moolenaar<EMAIL_ADDRESS>Date:   Mon May 25 22:36:50 2020 +0200

    patch 8.2.0823: Vim9: script reload test is disabled

    Problem:    Vim9: script reload test is disabled.
    Solution:   Compile a function in the context of the script where it was
                defined.  Set execution stack for compiled function.  Add a test
                that an error is reported for the right file/function.

Dominique wrote:

Running test49.out with the leak sanitizer shows memory leaks in vim-8.2.0877 and older:
$ git diff
diff --git a/src/Makefile b/src/Makefile
index 520ef0b93..9521379e4 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -702,6 +702,7 @@ LINT_OPTIONS = -beprxzF
 # When running tests output can be found in testdir/asan.*
 #SANITIZER_CFLAGS = -g -O0 -fsanitize=address -fno-omit-frame-pointer
 #SANITIZER_CFLAGS = -g -O0 -fsanitize=undefined -fno-omit-frame-pointer
+SANITIZER_CFLAGS = -g -O0 -fsanitize=leak -fno-omit-frame-pointer
 SANITIZER_LIBS = $(SANITIZER_CFLAGS)

 # MEMORY LEAK DETECTION
@@ -709,7 +710,7 @@ SANITIZER_LIBS = $(SANITIZER_CFLAGS)
 # Configuration is in the .ccmalloc or ~/.ccmalloc file.
 # Doesn't work very well, since memory linked to from global variables
 # (in libraries) is also marked as leaked memory.
-#LEAK_CFLAGS = -DEXITFREE
+LEAK_CFLAGS = -DEXITFREE
 #LEAK_LIBS = -lccmalloc

 # Uncomment this line to have Vim call abort() when an internal error is

$ export ASAN_OPTIONS="abort_on_error=0:detect_leaks=1"
$ ./configure --with-features=huge --enable-gui=none
$ make -j8
$ cd src/testdir
$ make test49.out
...snip...
Press ENTER or type command to continue

=================================================================
==32397==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 16 byte(s) in 1 object(s) allocated from:
    #0 0x7f289506417d in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/liblsan.so.0+0xf17d)
    #1 0x560ef5c105f7 in lalloc /home/pel/sb/vim/src/misc2.c:925
    #2 0x560ef5c104a2 in alloc /home/pel/sb/vim/src/misc2.c:828
    #3 0x560ef5c10b2f in vim_strsave /home/pel/sb/vim/src/misc2.c:1281
    #4 0x560ef5ca5679 in estack_sfile /home/pel/sb/vim/src/scriptfile.c:129
    #5 0x560ef5b9a8ed in cause_errthrow /home/pel/sb/vim/src/ex_eval.c:293
    #6 0x560ef5d9821d in emsg_core /home/pel/sb/vim/src/message.c:650
    #7 0x560ef5d9847e in emsg /home/pel/sb/vim/src/message.c:748
    #8 0x560ef5b7616d in ex_unletlock /home/pel/sb/vim/src/evalvars.c:1445
    #9 0x560ef5b75ea2 in ex_unlet /home/pel/sb/vim/src/evalvars.c:1373

[...]
Took some debugging and bisecting to find where this happens.  It's an
:unlet command that throws to errors, and the script file name in the
second wasn't freed.  Patch 8.2.0883 should fix it, please check.
--
hundred-and-one symptoms of being an internet addict:
250.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

This issue was fixed in patch 8.2.0883. Closing.


Rake instrumentation adapter

Convert Datadog instrumentation for Rake to OpenTelemetry.
See

Datadog porting guide
Semantic Conventions
Datadog implementation

Can I take this one? We already have a kind of patch for this. It's going to be a very simple instrumentation.
Or should I wait until the "semantic convention" to reach a conclusion?

@yoheyk definitely make a PR! Thanks!


Expose Scroll events for Pagination

Is your feature request related to a problem? Please describe.
To implement features like  pagination on the client side we should expose scroll events of the suggestion
Describe the solution you'd like
A scroll event callback should be fired when the suggestions are scrolled with two parameters offset and maxOffset.

Released in v0.9.7
See: Pagination example


About "condition_on_previous_text"

"condition_on_previous_text" is a parameter used in natural language processing models, indicating whether the model should consider the previous text content when generating new text. When set to True, the model will base the generation of the next text on the preceding text content, which can help the model better understand the context and produce more coherent text. This is particularly useful in dialogue systems or continuous text generation tasks, as the model can respond or continue generating text based on the preceding conversation or text content.
So,How can I use "condition_on_previous_text" this param to increase the accuracy of recognition in python's api?
Thank you!

If you use the huggingface implementaton there is some overlap between chunks, but the condition_on_previous is not implemented per se. Actually it makes the model work worse in many case, see:
https://github.com/huggingface/transformers/issues/21467
To get back to the topic, I would actually like to see the implementation of the hyperparameter as well, just for the opposite reason of OP. I want to disable condition_on_previous and this is not possible in the hugginface transformer pipeline as shown in the link above.

If you use the huggingface implementaton there is some overlap between chunks, but the condition_on_previous is not implemented per se. Actually it makes the model work worse in many case, see:
huggingface/transformers#21467
To get back to the topic, I would actually like to see the implementation of the hyperparameter as well, just for the opposite reason of OP. I want to disable condition_on_previous and this is not possible in the huggingface transformer pipeline as shown in the link above.
My benchmarks have consistently shown that whisper models of the transformer pipeline have been outperformed in terms of scoring in comparison to for example faster whisper. This has been due to this parameter which can decrease model performance.

oh,thanks


Owls 93146 - fix infinite introspector retries

Correct integration job failure-count functionality.
Includes substantial refactoring of JobHelper.
Integration test run
Note: this run has two failures:

ItLivenessProbeCustomization.testCustomLivenessProbeFailureThresholdSuccessThreshold, which passes when run again, and
ItProductionSecureMode.testVerifyProductionSecureMode, which fails in main.

Does this include a merge that it shouldn't? For example, there are doc changes that look related to unrelated work.

Does this include a merge that it shouldn't? For example, there are doc changes that look related to unrelated work.

I don't think so. I had to do a couple of merges from main, where there were doc changes, but that's it. Are there specific changes you're wondering about?

Does this include a merge that it shouldn't? For example, there are doc changes that look related to unrelated work.

I don't think so. I had to do a couple of merges from main, where there were doc changes, but that's it. Are there specific changes you're wondering about?

We have a few files, such as the documentation/domains directory and the CRD, that are generated during the build. We likely shouldn't be doing this, but Russ doesn't have to fix that as part of this PR. If you can merge the latest from main the I believe that we can merge this PR.

@russgold, any idea how to resolve this conflict in JobHelperTest?

@russgold, any idea how to resolve this conflict in JobHelperTest?

Yes, it's done. Somebody else added tests.


Code snippets that actually work?

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.

Hi @PaulPetersenAtTheAA ,
Which snippet didn't work for you? Could you share an example?

PS C:\Windows\system32> Import-Module Microsoft.Graph.Users
A UPN can also be used as -UserId.
Get-MgUserPhotoContent -UserId $userId -OutFile $outFileId
Get-MgUserPhotoContent : Cannot bind argument to parameter 'UserId' because it is an empty string.
At line:4 char:32

Get-MgUserPhotoContent -UserId $userId -OutFile $outFileId

                           ~~~~~~~

CategoryInfo          : InvalidData: (:) [Get-MgUserPhotoContent], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Get-MgUserPhotoContent

PS C:\Windows\system32>

Hi @PaulPetersenAtTheAA it seems like the $userId parameter you are trying to use is empty.
The userId can be replaced with a valid id or upn directly in the command, for example
Get-MgUserPhotoContent -UserId<EMAIL_ADDRESS>-OutFile "outputFile.jpg"

Or even populating the userId and outFileId parameters before calling the command in your script, like:
$userId =<EMAIL_ADDRESS>$outFileId = " C:\Users\user\photo.jpg"
Get-MgUserPhotoContent -UserId $userId -OutFile $outFileId


[Control Service] Come up with a safer approach to job image configuration in helm chart

What is the feature request? What problem does it solve?
With the introduction of the deploymentSupportedPythonVersions configuration, the fqdn of the image registry became part of the configuration map, instead of the previously used composite configuration approach.
This causes a situation, where the registry and its associated credentials need to be set in a separate configuration, thus leading to the possibility of unexpected errors, as mentioned in https://github.com/vmware/versatile-data-kit/pull/2075#discussion_r1197522079
We need to figure out a way to validate that the registries in the deploymentSupportedPythonVersions configuration are the same as the ones used for setting up the secrets.
Suggested solution
TBD
Additional context
Add any other context or screenshots about the feature request here.

Triaged. Closed as stale.


Spelling error in the description of iOS app

The second line of the english description of the App in the App Store says "Completely voulantary".

@Whalewhalewell thank you for your information. We will look at it together with FHI

I have fixed the typo in App Store Connect, the change is expected to take place with next release.

I have fixed the typo in App Store Connect, the change is expected to take place with next release.

Actually, the text has already been updated by Apple.

Closing the issue :)

Actually, the text has already been updated by Apple.

Closing the issue :)


Changing a Modified Color Token's Reference Changes In Both Variable Modes

Describe the bug
This issue is similar to #2278, but this bug emerged only after the latest 1.38.6 release. Changing modified color-tokens and creating/syncing variables now changes the value in both modes.

The first issue in video presented is when changing the value of token updates the same value across both modes
The second issue presented is that the mode's values are only corrected upon clicking sync variables.

To Reproduce
Steps to reproduce the behavior:

Create Variables
Change value of token - jf.container.color.regular.bg.surface-main.enabled - can be found in set Patterns/Backgrounds
See error

Expected behavior
It should work as it did previously:

Variables should be created respecting each mode's values
Changing a token's value should only update in one mode and not both

Screenshots or Screencasts
https://github.com/tokens-studio/figma-plugin/assets/93133012/1e6958d9-87e8-488d-9c6f-6f49044a856b
Figma file (optional)
Test section

Will be fixed in 2.0


Add ReadMe plugin

Hi folks, big 1Password fans over here at ReadMe! Looking forward to being a part of this exciting new ecosystem 💙
~I still have a few small outstanding TODOs in this PR (that I'll address before officially marking this as ready for review), but the main outstanding issue is that I'm running into is that the env variable RDME_API_KEY isn't properly being provisioned in my testing 😕 see #107 for more information!~
EDIT: fixed, thanks for your help @SimonBarendse @florisvdg!
Closes #108

(oops, didn't mean to remove the review request for @DCKcode, sorry!)

This looks great - thanks for your contribution!

(sorry folks, just fixing up a linting error!)

So sorry y'all, I was playing around locally and realized that it doesn't make sense for us to include whoami in our list of commands. This is officially ready to be merged! 😅


adding extensions page

closes https://github.com/bids-standard/bids-specification/issues/96
This is an attempt at splitting off the "contributing to BIDS / extensions" page into its own separate page so that the content is a bit more discoverable (originally mentioned in https://github.com/bids-standard/bids-specification/issues/96). @emdupre and @chrisfilo what do you think?

Thanks for doing this. LGTM.

good call @emdupre - how's the latest push look?

LGTM, thanks ! :+1:

All that's left is to fix some linter errors: https://travis-ci.com/bids-standard/bids-specification/builds/92754960#L490

fixed!


pub update - socket error on windows

This issue was originally filed by @bp74

What steps will reproduce the problem?
Calling "pub update" from the Dart Editor gives this output:
--- 25.04.2013 19:33:20 Running pub update ... ---
Pub update failed, [1] Resolving dependencies...
Got socket error trying to find package "browser" at https://pub.dartlang.org.
OS Error: errno = -8179
What is the expected output? What do you see instead?
Pub should update the packages :)
Downloading packages with a browser from pub.dartlang.org works fine.
What version of the product are you using? On what operating system?
Dart Editor version 0.1.2_r22037
Dart SDK version <IP_ADDRESS>_r22037
Windows 7, 64 bit
Please provide any additional information below.

This issue has been moved to dart-lang/pub#526.


Resume saved state on exit not working on Duckstation

On the legacy version on Duckstation I could automatically load, as soon as the game started, the state that gets saved the last time I exited the game if I changed the value of resumeState to 1 on the am start arguments, like this:
com.github.stenzek.duckstation/.EmulationActivity
-e bootPath {file.path}
--ez resumeState 1
--activity-clear-task --activity-clear-top
First of all, I never understood why the value was set to 0 as a default. But what makes me open this issue is that this no longer works with Duckstation ever since it started using scoped storage. I gave both Daijisho and Duckstation access to the ROMs folder, and it seems like the state gets saved when the game is launched via Daijisho, because if I open the game directly through Duckstation I get a prompt to load the state that got saved when I exited the game after starting it through Daijisho
Can this be fixed?

If you updated Duckstation, the resumeState command no longer works when launched externally (from an ADB session or frontend). I believe it was either quietly removed when Duckstation updated to align with Google's scoped storage rules or was changed (which we can't check as the Android version is closed source the last I checked)
Sten did leave up the Legacy Build downloadable here

Closing issue as this is more of a Duckstation question as it involves what Duckstation allows when loaded from a command


{App Service} az webapp create, az functionapp create, az webapp vnet-integration add Move route all to use site property

Related command
az webapp create
az functionapp create
az webapp vnet-integration add
Description
To meet Vanguard security requirements and enforce Azure Policy compliance we need to move certain site config properties to site properties. Customers should not be affected by this change and behavior should not change.
Testing Guide

History Notes

{App Service} az webapp create Move route all to use site property
{App Service} az functionapp create Move route all to use site property
{App Service} az webapp vnet-integration add Move route all to use site property

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

App Service


Build 2020 Feedback Thread - Fluent UI Android

Welcome Build 2020 participants! Did you get a chance to try out the Fluent UI Android library
or watch our Build 2020 talk? If so, we want to hear your feedback! Let us know how we can make this even more useful to you moving forward.
Feel free to leave feedback on any of the following (and please keep feedback constructive and respectful):

Likes
Dislikes
Bugs
Areas for improvement

Thank you,
The Fluent UI Android team

I'm curious about the plan of Fluent UI.
I found the catalog page for Fluent UI.
https://developer.microsoft.com/en-us/fluentui#/controls/android
More components are provided on the web platform.
Are you planning to add more components to Android?
(like Toggle, TextField, Slider, Shimmer, Dialog, Card)
If so, it would be more nice to have a guide in a form that developers can contribute to. :)

Closing this for 2020


cloud ml metric tools

Added two scripts to compute metrics that will be used in the cloud-ml project.
scoring.py contains functions to compute different scores
utils.py contains functions to make biases plots and color palettes
Note: This is a copy from the create-cloud-ml-project branch
Coverage reports (updated automatically):

test_unit: 83%

@nbren12 the previous PR wasn't pushed to master. @brianhenn and I thought it was better to send another PR to document this new change.

Yah we noticed (after hitting merge, woops) that the old PR was not set to merge into master but into create-cloud-ml-project.


ROX-18375: [Helm] Set core_bpf a default collection method

Description
Make core_bpf a default one for Helm charts. Part of https://github.com/stackrox/collector/issues/1470
Checklist

[ ] Investigated and inspected CI test results
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

No need for unit or regression tests.
Testing Performed

/retest

lgtm. Just an idea: we could add a quick helmtest test for checking the default value (and that it can be overwritten)? Something along these lines:
values:
  imagePullSecrets:
    allowNone: true
tests:
- name: "test default collection method is CORE_BPF"
  expect: |
   envVars(.daemonsets.collector; "collector")["COLLECTION_METHOD"] | assertThat(. == "CORE_BPF")

in a new file pkg/helm/charts/tests/securedclusterservices/testdata/helmtest/collector-collection-method.test.yaml

Thanks! Added it in a separate PR: https://github.com/stackrox/stackrox/pull/9253


Add handle "knobs" to resize bars

This will make it more obvious that the user can resize the panes.

Implemented; closing.


adding footer to partials [skip ci]

font awesome not showing up but will open ticket

Please pay careful attention to spelling, use a spell check on all text e.g. Realeases should be Releases

Overview
-fixed conflict with upstream
-adding svg for footer icons instead of font awesome
-worked on menu


Add a way to hear sound through portals

if this is possible, please make it so you can hear sound through portals. It's a bit weird just the noise instantly changing after going through the portal.

Fixed https://github.com/qouteall/ImmersivePortalsMod/releases/tag/v0.67-1.16

Fixed https://github.com/qouteall/ImmersivePortalsMod/releases/tag/v0.67-1.16


update to go1.23.4 / go1.22.10

go1.23.4 (released 2024-12-03) includes fixes to the compiler, the runtime, the trace command, and the syscall package. See the Go 1.23.4 milestone on our issue tracker for details.
https://github.com/golang/go/issues?q=milestone%3AGo1.23.4+label%3ACherryPickApproved

go1.22.10 (released 2024-12-03) includes fixes to the runtime and the syscall package. See the Go 1.22.10 milestone on our issue tracker for details.
https://github.com/golang/go/issues?q=milestone%3AGo1.22.10+label%3ACherryPickApproved

/cherry-pick release/2.0

/cherry-pick release/1.7


Retry failed HTTP requests when exporting to FireCloud

Currently when exporting to FireCloud (via the bagit_to_firecloud Lambda, the HTTP requests are only tried once, and if it fails, the export fails.
There are many cases in an HTTP request can fail and a subsequent retry will succeed, and to have a reliable/robust system, retry is essential.
There are a variety of ways to implement retrying operations.
It looks like the requests package does provide retry support, so that may be a good option.
Another option to consider is the @retry decorated developed by the HCA data-store team, here: https://github.com/HumanCellAtlas/data-store/blob/master/dss/util/retry.py

Note that the error seen in a demo was not in exporting; it was seen in bringing up the dialog where the user specifies the inputs for the export. To bring up the dialog, the UI makes 2 API calls to FireCloud to get the user's workspaces and billing projects, and either of those APIs would sometimes fail. Retrying those calls seems to get around the failure.
This has been addressed in https://github.com/DataBiosphere/boardwalk/commit/d7694831656b3c76bfc12226d8cd3cff367dd68d -- we are now doing up to 5 retries from the browser.
For the actual export to FireCloud, which makes API calls to optionally create the workspace and export the data, the need for those changes is covered by DataBiosphere/bagit-firecloud-lambda#9


Bump to xamarin/monodroid/main@e68da1e8

Changes: https://github.com/xamarin/monodroid/compare/d1d43ab1...e68da1e8

Bump external/xamarin-android from 35f41dc to cb23f7e
[s360] Ignore irrelevant lz4 warnings
Bump to dotnet/android@c157aed
Bump to xamarin/android-sdk-installer@05e4d62
[tools/msbuild] fix  creation of subdirectories

Addressing the LLVM failure: PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ in #9169, so we can ignore that one.


Implementation Plan of SYCL Image

Many GPUs contain special optimizations for texture memory, originally meant for 3D graphics. This usually involves storing 2D or 3D data in a device-specific tiled format to increase its data locality. On some older GPUs, there also exists a separate texture cache (although this difference has been largely eliminated in newer GPUs). Also, one may also access some features specific to image processing.  In OpenCL and SYCL, texture memory can be used via an Image object.
According to SYCL 2020,

Memory objects in SYCL fall into one of two categories: buffer objects and image objects. A buffer object stores a one-, two- or three-dimensional collection of elements that are stored linearly directly back to back in the same way C or C++ stores arrays. An image object is used to store a one-, two- or three-dimensional texture, frame-buffer or image data that may be stored in an optimized and device-specific format in memory and must be accessed through specialized operations.

Currently, Image is not implemented in AdaptiveCpp. Is there any plan on the roadmap for implementing that in the future?

Currently, Image is not implemented in AdaptiveCpp. Is there any plan on the roadmap for implementing that in the future?

To my knowledge, there is no SYCL implementation that wants to implement SYCL 2020 images as a priority. This is because it is widely believed that the API is in need of major changes to be more similar to e.g. CUDA bindless textures.
Given that

SYCL 2020 images are an optional feature
The API has an uncertain future and might need a complete reimplementation in the future anyway to allow bindless semantics
A large section (but not the entirety) of apps have no need for images
images are very, very complex and implementation would tie up a large amount of development resources

it seems very unattractive to put much effort into implementing the SYCL 2020 image API. It is thus a very low-priority item for me at the moment. Once the successor API is there, it might be appropriate to reconsider.

To my knowledge, there is no SYCL implementation that wants to implement SYCL 2020 images as a priority. This is because it is widely believed that the API is in need of major changes to be more similar to e.g. CUDA bindless textures.

Thanks for the answer.


nixos/public-inbox: fix incorrectly restrictive option type

The freeformType of settings.publicinbox in this module prevented users from setting settings on the publicinbox section itself (which is necessary for making e.g. IMAP work correctly), and only allowed configuration of nested per-inbox sections.
In general I believe that these overly specific types which are traditional in NixOS, and this kind of config generation, are a huge footgun. This commit is the least invasive change that makes the module work correctly.

@tazjin, thank you for spotting this, just a nitpick: would you agree to simplify the comment by just listing examples of supported options, I think that would be easier to understand.
Something like:
# Support both global options like `services.public-inbox.settings.publicinbox.imapserver`
# and inbox specific options like `services.public-inbox.settings.publicinbox.foo.address`.

We should also add explicit types/description for the current options (eg. imapserver), but this is obviously not a blocker for merging the fix in this PR.
Side note, as you can see services.public-inbox.settings.publicinbox.foo.address is normally set through services.public-inbox.inboxes.foo.address. The existence of services.public-inbox.inboxes is mostly historical, it just deviates from public-inbox's expected config by introducing a description option. I guess it would be cleaner to alias it to services.public-inbox.settings.publicinbox, but it's low priority for me.

Oh, that's a quick merge. I'll rebase and apply the comment change in https://github.com/NixOS/nixpkgs/pull/207879


VOT Short term tracking

I looked into your repo but couldn't gather what all arguments to change in config.py file so as to train with 2nd Algorithm which was presented in the paper (i.e. for VOT short term tracking). It would be very helpful if you could tell me what all changes I have to make to train my model based on 2nd algorithm.
Thanks

Hi,
the short-term tracking algorithm is only a variant of the tracking algorithm used at test time. The training step does not change.

yes right! my bad.
So how do I do the tracking using 2nd algorithm?
If I use the main_vot18 function to do tracking on VOT2018 dataset, will it use 2nd algorithm to do the tracking?
Thanks

We didn't publish the code of the short-term tracking algorithm in this repository, because it is not really part of the normal method.
I can share the code with you, if you write me an email or share your email address.

That would be very helpful sir.
This is my college email address<EMAIL_ADDRESS>Thanks


Contribution guidelines

Could you please add contribution guidelines ? thank you

Please use the issue template to describe your issue > https://github.com/syoyo/tinygltf/issues/new/choose


Icons not rendering in a dynamic  Array creation

UnoCSS version
latest
Describe the bug
I tried creating flag icons based on the country name using unocss icons

interface Country {
  name: string
  code: string
  icon: Element
}

const countryfy = (countryArr: CountryData[]): Country[] =>
  countryArr.map((c) => ({
    name: c.countryNameEn,
    icon: (

    ),
    code: c.countryCallingCode,
  }))

What would be the better approach for this scenario ? Defining country flag icons one-by-one ?
Reproduction
Vite Solid-ts
System Info
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

https://unocss.dev/guide/extracting#safelist


endpoint for training_set details

Short description
An endpoint was added to get details of a training-set by providing the training-set id
Proposed changes
Added "training_set_details" endpoint
Added training-set-by-id viewset

Oh, and one question: This also "leaks" training sets of individual disciplines which would otherwise just be retrievable with a valid API key. I'm not sure whether this is an issue since we decided API-keys aren't "real secrets", but do you think there is still a difference between "not a real secret" and "completely public"?

You are right, I added the check

Awesome, thanks a lot! rocket Now, could you squash your commits into one?

Done.


Add field for organizations - Twitter handle

For example Riigikantselei @EstonianGovt

@keeganmcbride - So there is a field now? How I should contrib with content? Should I create csv what You can use for updating?

This is done, adding organizations twitter handles is a seperate issue, but the field now exists.


Allow loadbalancerIP for frontend service

What was changed:

Why?

It allows static IP from a load balancer
Checklist

How was this tested:

deploy the helm with the values set, OK

documentation in readme or comment in values file would be helpful for usage here

closing this after conversations about how we will handle these resources going forward. see: https://github.com/temporalio/proposals/issues/42 for more details.


Custom CSS class namespace option?

First of all: very nice plugin, I love that it's lightweight and has lots of options.
Question: would you consider an option for custom class names when instantiating the menu?
iw- is fine for most users, but one might need a custom namespace, in order to have the generated menu classes synced with existing code/namespacing in their app.
Thanks!

Whatever, I guess this is not maintained anymore.
Closing this, I gave up on using the plugin when I went through it's code and saw how it adds HTML markup on page load for every element that it was triggered on (what if you have a page with 100 elements that you want to use the contextmenu on? you get 100 <ul>s injected when you visit the page...)

@hellocosmin Yes, I know some parts needs a rewrite for better performance.
But I am quite busy with other priorities this days. Maybe you can contribute here for those changes?


RTE dart2js when creating a Uint8Array from a MappedListIterable

The following code runs fine in DartVM, but RTE's after dart2js:
Stream get value$ => _state$.stream
.map((Iterable<Tuple6<int, int, Shape, Rotation, Color, bool>> cells) => cells.map(_cellToValue))
.map((Iterable list) => new Uint8List.fromList(list)); // this line RTE
The js debugger complains about a method '$index' not found from within an isolate
To fix this, I had to call toList on the MappedIterable first:
Stream get value$ => _state$.stream
.map((Iterable<Tuple6<int, int, Shape, Rotation, Color, bool>> cells) => cells.map(_cellToValue))
.map((Iterable list) => new Uint8List.fromList(list.toList(growable: false))); // no more RTE

My guess is that this is as intended since Uint8List.fromList is declared to expect a List. I assume that if you run the first program in checked mode, then the dartvm also produces a RTE. Correct?
It seems that the dart2js implementation of this constructor does assume that the input is a List, while the VM doesn't only relies on the APIs that are also part of Iterable, so it just happens to work there. We could change the code here to do result.addAll(list) instead, but it's likely going to be more expensive.
/cc @lrhn

I need to doublecheck but I think it works in the vm with checked true. Even the analyser strict mode doesn't complain for me.

It wouldn't give a warning because you are passing an Iterable to a function expecting a List, and Iterable is assignable to List.
It should fail at runtime in checked mode because the Iterable isn't actually a List.


Missing read line...

Where is the ConsoleRead in your example? This ex returns nothing!!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 799f3460-8d63-76ac-0f6b-8dc09840da09
Version Independent ID: 777bcccf-fc8b-5a95-114f-9a2e74e33318
Content: Command-Line Arguments - C# Programming Guide
Content Source: docs/csharp/programming-guide/main-and-command-args/command-line-arguments.md
Product: dotnet-csharp
Technology: csharp-fundamentals
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

@humdam121 Perhaps you can elaborate as to why you expected a Console.Read line? This article is demonstrating reading the command line arguments and printing them out. This means that you call the executable with an input value:
myfile.exe argument where argument is the value you pass to the executable and read through the args array.


Support for decorator @NgModule

Will the dart angular 2 version have support for the decorator @NgModule ? Or is there an alternative to this decorator, to group components, directives, services and pipes as a module?

Angular 2 Dart does not really need @NgModule,
If you want to use deferred loading, there is a nice article about it
<EMAIL_ADDRESS>

Yep, this isn't planned at this time.
Please re-open if there are specific features you feel you need.


Invalid argument: 'C:\...\PycharmProjects\libraries\

System information

OS Platform and Distribution : Windows 10 Professional x64 Build 1909
Modin version : 0.8.0
Python version : 3.8.1
Code we can use to reproduce :

import os
os.environ["MODIN_ENGINE"] = "dask"
import modin.pandas as pd
Describe the problem
I have installed Modin using pip install modin[dask] on my virtual environment after having uninstalled Modin and Ray recently (I had installed modin[ray] unaware of incompatibility with Windows environment)
Now when I try to import the module, it throws an infinite error with the traceback
I had to put space around input, else the HTML format rendered it invisible, the spaces are non-existent in execution

OSError: [Errno 22] Invalid argument: 'C:\Users\user\PycharmProjects\libraries\ < input >

Source code / logs
UserWarning: The Dask Engine for Modin is experimental.
Traceback (most recent call last):
File "", line 1, in
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 116, in spawn_main
exitcode = _main(fd, parent_sentinel)
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 125, in _main
Traceback (most recent call last):
File "", line 1, in
prepare(preparation_data)
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 236, in prepare
_fixup_main_from_path(data['init_main_from_path'])
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 287, in _fixup_main_from_path
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 116, in spawn_main
main_content = runpy.run_path(main_path,
File "C:\Program Files\Python38\lib\runpy.py", line 262, in run_path
exitcode = _main(fd, parent_sentinel)
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 125, in _main
code, fname = _get_code_from_file(run_name, path_name)
File "C:\Program Files\Python38\lib\runpy.py", line 232, in _get_code_from_file
prepare(preparation_data)
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 236, in prepare
with io.open_code(fname) as f:
_fixup_main_from_path(data['init_main_from_path'])OSError: [Errno 22] Invalid argument: 'C:\Users\user\PycharmProjects\libraries\'
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 287, in _fixup_main_from_path
main_content = runpy.run_path(main_path,
File "C:\Program Files\Python38\lib\runpy.py", line 262, in run_path
code, fname = _get_code_from_file(run_name, path_name)
File "C:\Program Files\Python38\lib\runpy.py", line 232, in _get_code_from_file
with io.open_code(fname) as f:
OSError: [Errno 22] Invalid argument: 'C:\Users\user\PycharmProjects\libraries\ < input > '
Traceback (most recent call last):
File "", line 1, in
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 116, in spawn_main
exitcode = _main(fd, parent_sentinel)
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 125, in _main
prepare(preparation_data)
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 236, in prepare
_fixup_main_from_path(data['init_main_from_path'])
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 287, in _fixup_main_from_path
main_content = runpy.run_path(main_path,
File "C:\Program Files\Python38\lib\runpy.py", line 262, in run_path
code, fname = _get_code_from_file(run_name, path_name)
File "C:\Program Files\Python38\lib\runpy.py", line 232, in _get_code_from_file
Traceback (most recent call last):
File "", line 1, in
with io.open_code(fname) as f:
OSError: [Errno 22] Invalid argument: 'C:\Users\user\PycharmProjects\libraries\ < input > '
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 116, in spawn_main
Traceback (most recent call last):
File "", line 1, in
exitcode = _main(fd, parent_sentinel)
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 125, in _main
prepare(preparation_data)
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 236, in prepare
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 116, in spawn_main
_fixup_main_from_path(data['init_main_from_path'])
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 287, in _fixup_main_from_path
exitcode = _main(fd, parent_sentinel)
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 125, in _main
main_content = runpy.run_path(main_path,
File "C:\Program Files\Python38\lib\runpy.py", line 262, in run_path
prepare(preparation_data)
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 236, in prepare
code, fname = _get_code_from_file(run_name, path_name)
File "C:\Program Files\Python38\lib\runpy.py", line 232, in _get_code_from_file
_fixup_main_from_path(data['init_main_from_path'])
File "C:\Program Files\Python38\lib\multiprocessing\spawn.py", line 287, in _fixup_main_from_path
main_content = runpy.run_path(main_path,
File "C:\Program Files\Python38\lib\runpy.py", line 262, in run_path
code, fname = _get_code_from_file(run_name, path_name)
File "C:\Program Files\Python38\lib\runpy.py", line 232, in _get_code_from_file
Traceback (most recent call last):
File "", line 1, in
with io.open_code(fname) as f:
OSError: [Errno 22] Invalid argument: 'C:\Users\user\PycharmProjects\libraries\ < input > '

Hi @hazeyblu thanks for posting!
This appears to be related to #843 with Dask. Ray does have windows support now, though it is experimental. Would it be possible to try with Ray? Ray doesn't have the same multiprocessing error issue that Dask has.

Hi @hazeyblu are you still facing this issue? I'm going to go ahead and close this issue since the thread has gone stale.


RajendarR0001 - Added HelloWorld Program to Rajendar.java

Adding the Hello world program in the Rajendar.java

Added Utility function to check divisibility by 2


"bugreport" enhancement request

Would it be possible to add the following "dynamic" information to the output of the "bugreport" Addon macro which is available at https://www.motoslave.net/sugarcube/download.php/2/modules/bugreport-macro-for-sugarcube-v2.zip?
(It's in twee code below, copied directly from one of my story files.)
''Story Name:'' <<= $('tw-storydata').attr('name')>>
''Story IFID:'' <<= $('tw-storydata').attr('ifid')>>
''Story Format:'' <<= $('tw-storydata').attr('format') + " v" + $('tw-storydata').attr('format-version')>>
''Compiler:'' <<= $('tw-storydata').attr('creator') + " v" + $('tw-storydata').attr('creator-version')>>
''Browser:'' <<= navigator.userAgent>>

Alternatively, is there a non-pre-compiled version of the Addon's javascript available so I could try to add it myself? Unfortunately, I find the javascript as provided in the zip download to be, well, opaque.
Thanks!

Sorry for the delayed response.
Allowing users to specify a prolog for reports is reasonable.  I'll see if I can't get something worked up soonish.

Sorry for the delayed response.
Allowing users to specify a prolog for reports is reasonable.  I'll see if I can't get something worked up soonish.


Docs: known issue for 188

See also updated issue description

After approval of this PR we'll change milestone of #188 to 0.8.1


Improving Region Availability

This PR fixes
Improving Region Availability for DMA by including the list of regions where ZRS is available. Also removed unnecessary dependency based on linting rules.

Preview Link


How do you use Arrow with Moya+RxSwift

I'm using Moya + RxSwift and would like to use Arrow to do the parsing. Has anyone ever tried this?
Thanks.

@zkon I've never used Moya but I'm going to try it this afternoon and will report back :)

@zkon Ok I've been checking out the Moya repo and here is how I plugged Arrow based on their example project.
Create a strongly typed Repository
struct Repository {
    var name = ""
}

Add JSON Mapping
extension Repository: ArrowParsable {
    mutating func deserialize(_ json: JSON) {
        name <-- json["name"]
    }
}

In the downloadRepositories function, use this code instead
let response = try result.dematerialize()
let value = try response.mapJSON()

let json = JSON(value)
let repositories = json?.collection?.map { json -> Repository in
    var repo = Repository()
    repo.deserialize(json)
    return repo
}
self.repos = repositories ?? [Repository]()
self.tableView.reloadData()

Hope this helps :)
PS: If you use Arrow and Alamofire, then you might like ws


Rust bindings implementation

This MR makes it possible to use go-enry from Rust via FFI. Almost all exposed functions (which make sense to use) through CGo shared library were covered.

Thanks for review and little adjustments! I prefer to add Github Action CI in this PR and I'll do it later.


Problems importing project

I use IntelliJ IDEA 2017.1.2
When importing the project, I get errors:
Error:Error while importing SBT project:
...

[error]     wrong checksum: /Users/rouquett/.coursier/cache/v1/https/repo1.maven.org/maven2/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error] (nlp/*:coursierSbtClassifiersResolution) coursier.ResolutionException: Encountered 1 error(s) in dependency resolution:
[error]   org.jboss.interceptor:jboss-interceptor-api:1.1:
[error]     not found:
[error]       https://repo.typesafe.com/typesafe/ivy-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       /Users/rouquett/.ivy2/local/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       http://repo.typesafe.com/typesafe/releases/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error]       https://dl.bintray.com/heroku/sbt-plugins/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]     wrong checksum: /Users/rouquett/.coursier/cache/v1/https/repo1.maven.org/maven2/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error] (deepwalk/*:coursierSbtClassifiersResolution) coursier.ResolutionException: Encountered 1 error(s) in dependency resolution:
[error]   org.jboss.interceptor:jboss-interceptor-api:1.1:
[error]     not found:
[error]       https://repo.typesafe.com/typesafe/ivy-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       /Users/rouquett/.ivy2/local/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       http://repo.typesafe.com/typesafe/releases/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error]       https://dl.bintray.com/heroku/sbt-plugins/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]     wrong checksum: /Users/rouquett/.coursier/cache/v1/https/repo1.maven.org/maven2/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error] Total time: 25 s, completed Apr 15, 2017 9:25:36 AM

See complete log in file:/Users/rouquett/Library/Logs/IntelliJIdea2017.1/sbt.last.log

It seems that the project is missing a resolver for Maven Central to find the dependency:
http://search.maven.org/#artifactdetails|org.jboss.interceptor|jboss-interceptor-api|1.1|jar

I get such errors randomly when I try to use Coursier (currently I am getting none), and don't know enough to fix them. A work-around is to comment out the coursier plugin in plugins.sbt.

I have removed some dependencies no longer used and updated plugin versions. Could you try again?

Thanks @siddhartha-gadgil for looking into this.
After updating, IntellijIDEA 2017.1.2 can properly import the project with build.sbt modified like this:
lazy val commonSettings = baseSettings ++ Seq(
    resolvers += "Typesafe Repository" at "http://repo.typesafe.com/typesafe/releases/",

    // Coursier fails to verify the checksum of
    // https://repo1.maven.org/maven2/org/jboss/interceptor/jboss-interceptor-api/1.1/
    coursierChecksums := Seq(None),

    // needed to resolve org.jboss.interceptor:jboss-interceptor-api:1.1
    externalResolvers in updateSbtClassifiers += "Maven Central" at "https://repo1.maven.org/maven2/",

It's unfortunate that checksum verification had to be disabled.

Seems to be an issue addressed in:
http://stackoverflow.com/questions/41966066/jboss-interceptor-api-1-1-not-found-when-added-as-sbt-dependency
There is disagreement there as to what is the best way to solve this - whether or not I should add a resolver.

@NicolasRouquette
For some reason this doesn't work for me.
Both in stable IntelliJ IDEA 2017.1 (Build #IU-171.3780.107) and early-access IntelliJ IDEA 2017.1.2 EAP (Build #IU-171.4249.4) with your changes I have
Error:Error while importing SBT project:
...

[error]       /home/dmitin/.activator/repository/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       /home/dmitin/activator-dist-1.3.10/repository/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       http://repo.typesafe.com/typesafe/releases/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error]       http://repo.typesafe.com/typesafe/ivy-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       http://repo.typesafe.com/typesafe/releases/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error]       https://dl.bintray.com/heroku/sbt-plugins/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]     wrong checksum: /home/dmitin/.coursier/cache/v1/https/repo1.maven.org/maven2/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error]   org.jboss.interceptor:jboss-interceptor-api:1.1:
[error]     not found:
[error]       https://repo.typesafe.com/typesafe/ivy-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       /home/dmitin/.ivy2/local/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       /home/dmitin/.activator/repository/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       /home/dmitin/activator-dist-1.3.10/repository/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       http://repo.typesafe.com/typesafe/releases/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error]       http://repo.typesafe.com/typesafe/ivy-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       http://repo.typesafe.com/typesafe/releases/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error]       https://dl.bintray.com/heroku/sbt-plugins/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]     wrong checksum: /home/dmitin/.coursier/cache/v1/https/repo1.maven.org/maven2/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error] Total time: 42 s, completed 17.04.2017 12:57:33

See complete log in file:/home/dmitin/.IntelliJIdea2017.1/system/log/sbt.last.log

I commented Coursier in plugins.sbt and coursierChecksums in build.sbt. Then I have
Error:Error while importing SBT project:
...

[error] (functionfinder/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (normalform/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (mantle/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (mantle/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (client/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (coreJVM/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (realfunctions/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (realfunctions/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mizar/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (mizar/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (coreJS/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (exploring/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (exploring/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (provingground/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (server/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (nlp/*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] (realfunctions/*:update) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mizar/*:update) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mantle/*:update) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] Total time: 777 s, completed 17.04.2017 13:18:41

See complete log in file:/home/dmitin/.IntelliJIdea2017.1/system/log/sbt.last.log

@siddhartha-gadgil
In 2017.1.2 after I addded JBoss to global.sbt I have
Error:Error while importing SBT project:
...

[warn] 	Note: Unresolved dependencies path:
[warn] 		org.scalanlp:breeze_2.12:0.13.+ (/home/dmitin/Projects/ProvingGround_3/ProvingGround/build.sbt#L59)
[warn] 		  +- in.ernet.iisc.math:provingground-mantle_2.12:0.1
[trace] Stack trace suppressed: run 'last andrewscurtis/*:ssExtractProject' for the full output.
[trace] Stack trace suppressed: run 'last mantle/*:ssExtractProject' for the full output.
[trace] Stack trace suppressed: run 'last realfunctions/*:ssExtractProject' for the full output.
[trace] Stack trace suppressed: run 'last mizar/*:ssExtractProject' for the full output.
[trace] Stack trace suppressed: run 'last exploring/*:ssExtractProject' for the full output.
[trace] Stack trace suppressed: run 'last realfunctions/*:update' for the full output.
[trace] Stack trace suppressed: run 'last mizar/*:update' for the full output.
[trace] Stack trace suppressed: run 'last mantle/*:update' for the full output.
[error] (andrewscurtis/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mantle/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (realfunctions/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mizar/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (exploring/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (realfunctions/*:update) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mizar/*:update) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mantle/*:update) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] Total time: 389 s, completed 17.04.2017 13:44:43

See complete log in file:/home/dmitin/.IntelliJIdea2017.1/system/log/sbt.last.log

Then I uncheck "Download SBT sources" and have
Error:Error while importing SBT project:
...

[warn] 	Note: Unresolved dependencies path:
[warn] 		org.scalanlp:breeze_2.12:0.13.+ (/home/dmitin/Projects/ProvingGround_3/ProvingGround/build.sbt#L59)
[warn] 		  +- in.ernet.iisc.math:provingground-mantle_2.12:0.1
[trace] Stack trace suppressed: run 'last andrewscurtis/*:ssExtractProject' for the full output.
[trace] Stack trace suppressed: run 'last mantle/*:ssExtractProject' for the full output.
[trace] Stack trace suppressed: run 'last realfunctions/*:ssExtractProject' for the full output.
[trace] Stack trace suppressed: run 'last mizar/*:ssExtractProject' for the full output.
[trace] Stack trace suppressed: run 'last exploring/*:ssExtractProject' for the full output.
[trace] Stack trace suppressed: run 'last realfunctions/*:update' for the full output.
[trace] Stack trace suppressed: run 'last mizar/*:update' for the full output.
[trace] Stack trace suppressed: run 'last mantle/*:update' for the full output.
[error] (andrewscurtis/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mantle/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (realfunctions/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mizar/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (exploring/*:ssExtractProject) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (realfunctions/*:update) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mizar/*:update) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] (mantle/*:update) sbt.ResolveException: unresolved dependency: org.scalanlp#breeze_2.12;0.13.+: not found
[error] Total time: 39 s, completed 17.04.2017 13:51:43

See complete log in file:/home/dmitin/.IntelliJIdea2017.1/system/log/sbt.last.log

The maven central seems to have the same artifacts as those published on the jboss repo.
Both have invalid checksums; which I reported here: https://issues.jboss.org/browse/JBINTER-21
Until that is fixed, it is necessary to disable coursier's checksums.
Try deleting the the Coursier cache folder: ~/.coursier/cache
lazy val commonSettings = baseSettings ++ Seq(
    resolvers += "Typesafe Repository" at "http://repo.typesafe.com/typesafe/releases/",

    // Coursier fails to verify the checksum of
    // https://repo1.maven.org/maven2/org/jboss/interceptor/jboss-interceptor-api/1.1/
    coursierChecksums := Seq(None),

    // needed to resolve org.jboss.interceptor:jboss-interceptor-api:1.1
    externalResolvers in updateSbtClassifiers += "JBoss" at "https://repository.jboss.org/",

With this, I can properly import the project with intellij 2017.1.2 and with sbt.
IntelliJ import behavior is equivalent to sbt update at the command line.
Both should yield equivalent results.

@NicolasRouquette Thanks
@DmytroMitin I don't use IntelliJ and have limited experience with builds, so do not have any idea about these issues.

@siddhartha-gadgil Thank you. Do you use any IDE / text editor while working on ProvingGround?
@NicolasRouquette Many thanks. After deleting Coursier cache and with this build.sbt I successfully imported project too (if I uncheck "Download SBT sources") both in 2017.1.2 and 2017.1.
Can you run your code from Idea?
I added to build.sbt
lazy val myproject = (project in file("myproject"))
  .settings(commonSettings: _*)
  .settings(jvmSettings: _*)
  .dependsOn(coreJVM)
  .dependsOn(functionfinder)
  .dependsOn(mantle)

and then created a file ProvingGround/myproject/src/main/scala/App.scala
import provingground._
import HoTT._
import TLImplicits._
import shapeless._
import ammonite.ops._
import FansiShow._

object App {
  def main(args: Array[String]): Unit = {
    val A = "A" :: Type
    println(A)
    val a = "a" :: A
    println(a)
  }
}

but have an error
Error:scala: Multiple 'scala-library*.jar' files (scala-library-2.12.0.jar, scala-library-2.12.1.jar) in Scala compiler classpath in Scala SDK SBT: org.typelevel:scala-library:2.12.1:jar
It's because both org.scala-lang:scala-library:2.12.1:jar and org.typelevel:scala-library:2.12.1:jar are in classpath. Do you know how to fix this? I guess it should be something easy like
 .settings(libraryDependencies += "???" % "???" % "???" exclude("org.scala-lang", "scala-library"))
in proper place. Thank you.

@DmytroMitin I use Atom with Ensime, though have used scala-ide in the past.

@DmytroMitin I tried your example; however, the checksum errors came back.
I tried to disable coursier; however, SBT takes a really long time to refresh.
I'm stumped; sadly, I haven't been able to use this project.
About excluding org.scala-lang dependencies, yes you're correct.
This is basically what is explained here: http://www.scala-sbt.org/0.13/docs/Library-Management.html#Exclude+Transitive+Dependencies
I found it very useful to use the sbt dependency graph plugin to inspect the dependency tree and selectively exclude selected dependencies at the right place.

@NicolasRouquette
Thank you.
sbt "whatDependsOn org.typelevel scala-library 2.12.1" shows that typelevel's scala-library is used in  many places.
sbt "whatDependsOn org.scala-lang scala-library 2.12.1" shows that scala-lang's scala-library isn't used anywhere. I guess Idea adds scala-lang's scala-library at some moment (I'm not sure when and how to switch this off, if I exclude it in "Project Structure" manually anyway I have the same error).
But there is a workaround.
We can import not the whole project ProvingGround with all subprojects but just project ProvingGround/core with the following ProvingGround/core/build.sbt
name := "provingground-core"

version := "0.1"

scalaVersion := "2.12.1"

organization := "in.ernet.iisc.math"

resolvers += Resolver.sonatypeRepo("releases")

resolvers += "Typesafe Repository" at "http://repo.typesafe.com/typesafe/releases/"

externalResolvers in updateSbtClassifiers += "JBoss" at "https://repository.jboss.org/"

libraryDependencies ++= Seq(
      "org.scala-lang.modules" %% "scala-parser-combinators" % "1.0.5",
      "org.spire-math" %% "spire"     % "0.13.0",
      "com.lihaoyi"    %% "fansi"     % "0.2.3",
      "com.lihaoyi"    %% "upickle"   % "0.4.4",
      "com.chuusai"    %% "shapeless" % "2.3.2",
      "org.typelevel"  %% "cats"      % "0.9.0",
      "com.lihaoyi"    % "ammonite"   % "0.8.1" cross CrossVersion.full
    )

scalacOptions ++= Seq("-unchecked",
                          "-deprecation",
                          "-feature",
                          "-language:existentials")

Then this small project is imported to Intellij Idea successfully and code runs.
You can check for example the following code:
ProvingGround/core/src/main/scala/mypackage/App.scala
package mypackage

import provingground._
import HoTT._
import TLImplicits._
import shapeless._
import ammonite.ops._
import FansiShow._

object App {
  def main(args: Array[String]): Unit = {
    val A = "A" :: Type
    println(A)
    val a = "a" :: A
    println(a)

    val a1 = "a1" :: A
    val a2 = "a2" :: A
    val a3 = "a3" :: A
    val a4 = "a4" :: A

    val Nat = "Nat" :: Type
    val NatInd = ("0" ::: Nat) |: ("succ" ::: Nat -->>: Nat) =: Nat
    val zero :: succ :: HNil = NatInd.intros

    val one = succ(zero)
    val two = succ(one)
    val three = succ(two)
    val four = succ(three)
    val five = succ(four)

    val n = "n" :: Nat
    val m = "m" :: Nat

    val recNNN = NatInd.rec(Nat ->: Nat)
    val addn ="add(n)" :: Nat ->: Nat
    val add = recNNN(m :-> m)(n :-> (addn :-> (m :-> succ(addn(m)) )))

    val Vec = "Vec" :: Nat ->: Type
    val VecInd = ("nil" ::: (Vec -> Vec(zero))) |: { "cons" ::: n ~>>: (A ->>: (Vec :> Vec(n)) -->>: (Vec -> Vec(succ(n))))} =:: Vec
    val vnil :: vcons :: HNil = VecInd.intros

    val vn = "v_n" :: Vec(n)
    val vm = "v_m" :: Vec(m)

    val indVVV = VecInd.induc(n :~> (vn :-> (m ~>: (Vec(m) ->: Vec(add(n)(m)) ))))
    val concatVn = "concat(v_n)" :: (m ~>: (Vec(m) ->: Vec(add(n)(m)) ))
    val vconcat = indVVV(m :~> (vm :-> vm))(n :~> (a :-> (vn :-> (concatVn :-> (m :~> (vm :-> vcons(add(n)(m))(a)(concatVn(m)(vm)) ))))))

    val vect = vcons(one)(a)(vcons(zero)(a1)(vnil))
    val vect1 = vcons(two)(a2)(vcons(one)(a3)(vcons(zero)(a4)(vnil)))
    val vect2 = vconcat(two)(vect)(three)(vect1)
    val vect3 = vcons(four)(a)(vcons(three)(a1)(vcons(two)(a2)(vcons(one)(a3)(vcons(zero)(a4)(vnil)))))

    println(vect2)
    println(vect2.fansi)
    println(vect2 == vect3)
    println(vect2.typ)
    println(vect2.typ.fansi)
    vect2 !: Vec(five)

  }
}

I have done fresh clean install with latest everything and all seem work well now.
No tweak needed for IntelliJ. Everything working from scratch with ProvingGround HEAD.
This issue could probably be closed.

Thanks @newca12


feat(web): add resort header

Can you comment with a screenshot of what it looks like please

@heybereket dont merge until @f1shy-dev approves

Yes @HenryLeC , here you go -

I will review right now once I get the environment setup

Yep looks great, if you don't mind can you gitignore the custom css file that you made for vsc

I can do all the data loading rn

sure, could you do that? i mean we already have the data there, just needs to be passed into the header.

also @HenryLeC the .vscode thing is meant to not be ignored, it basically tells vscode that @<whatever> is an actual directive as tailwind directives give errors in vscode syntax highlighting.

Ok cool makes sense

sure, could you do that? i mean we already have the data there, just needs to be passed into the header.

Yep okay I'm merging

@akashrajum7 we can add the vscode config as well as some other editor config in a new pr, if you could open it thatd be great

should we merge then push the data loading after?

ok that works

Oops, I removed the custom config :sweat: , should I add it back? Also @f1shy-dev I'd be happy to work on the data part as well, sure.

Oops, I removed the custom config :sweat: , should I add it back? Also @f1shy-dev I'd be happy to work on the data part as well, sure.

I merged just make a new pr with the config and I will handle the data stuff

@akashrajum7 we can add the vscode config as well as some other editor config in a new pr, if you could open it thatd be great

Sure, doing it.

Pretty sure @HenryLeC said he is going to be working on the data part.

Oops, I removed the custom config 😓 , should I add it back? Also @f1shy-dev I'd be happy to work on the data part as well, sure.

I merged just make a new pr with the config and I will handle the data stuff

replied to wrong one*

Okay sure, I will open a PR for the config.

ok lets stop commenting here, and move to the other config pr while henry does config. Settled


$raw - support SQL auto completion based on introspection

Our $raw command should provide awesome auto-completion as in https://github.com/segmentio/ts-mysql-plugin.

Is that limited to MySQL or is there also Postgres and SQLite by any chance?

The segment package only supports mysql, but this package supports both mysql, postgres and sqlite: https://github.com/joe-re/sql-language-server.

Hi, I created an extension that solves this! Please try it out!
This extension supports Postgres, MySQL, SQLite3 and more.
https://github.com/senkenn/sqlsurge


Error during Grafana-deployment

We are on version 0.20.2.
Same issue on tenant-root and sub tenant.
Failed pod is stuck in initialization phase
Init container 'load-vm-ds-plugin' is in BackOff state
Pod events show continuous container restarts
Init container script reveals unauthenticated GitHub API calls
here is the logs
[ 2024-12-27T13:58:13.693 ]: tar: invalid tar magic
[ 2024-12-27T13:58:13.691 ]: + tar -xf /var/lib/grafana/plugins/vl-plugin.tar.gz -C /var/lib/grafana/plugins/
[ 2024-12-27T13:58:13.684 ]:
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100     9  100     9    0     0     33      0 --:--:-- --:--:-- --:--:--    33
100     9  100     9    0     0     33      0 --:--:-- --:--:-- --:--:--    33
[ 2024-12-27T13:58:13.418 ]:                                  Dload  Upload   Total   Spent    Left  Speed
[ 2024-12-27T13:58:13.418 ]:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
[ 2024-12-27T13:58:13.41 ]: + curl -L https://github.com/VictoriaMetrics/victorialogs-datasource/releases/download/v0.13.2/victorialogs-datasource-v0.13.2.tar.gz -o /var/lib/grafana/plugins/vl-plugin.tar.gz
[ 2024-12-27T13:58:13.41 ]: + ver=v0.13.2
[ 2024-12-27T13:58:13.107 ]: + head -1
[ 2024-12-27T13:58:13.106 ]: + grep -oE 'v[0-9]+\.[0-9]+\.[0-9]+'
[ 2024-12-27T13:58:13.106 ]: + curl -s https://api.github.com/repos/VictoriaMetrics/victorialogs-datasource/releases/latest
[ 2024-12-27T13:58:13.102 ]: + mkdir -p /var/lib/grafana/plugins/

Hey @matthieu-robin this issue is fixed by https://github.com/aenix-io/cozystack/pull/538 and released in v0.21.0
Do you need to preform patch relese for v0.20 or you going to update v0.21?

We will upgrade :)
Thanks a lot
On Dec 30, 2024 at 11:26 AM +0100, Andrei Kvapil @.***>, wrote:

Hey @matthieu-robin this issue is fixed by #538 and released in v0.21.0
Do you need to preform patch relese for v0.20 or you going to update v0.21?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Implementing Accessibility

Here we suppose to implement accessibility to our WebSite.
We work and commit to each of our projects together.

Hi @Nidala,
Good job so far!
There are some issues that you still need to work on to go to the next project but you are almost there!
Required Changes ♻
Check the comments under the review.

[ ]  When I see the basic structure of the page I found two elements/tags in the wrong place. The heading ##  MY RECENT WORK  is detached from the work-section elements completely. It is a heading for the work-section elements and it should be under the same parent element with the work-section elements.
[ ]  The other is you put main tag inside background-bottom - div element. That violates the correct page structure. main tag represents part of the page between the header and footer sections.
[ ]  You need to have a report summary of the evaluation you have made on your PR. Each summary list should also be linked to the code snippet where file changes are made in the GitHub files.  Please carefully read the project's requirements, make the necessary changes before you request another review.

Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
As described in the Code reviews limits policy you have only 3 code reviews per project. If you think that the code review was not fair, you can request a second opinion using this form.

@henatan99 Sorry who is Nidala? are you sure are you reviewing the correct repo?