Set upperbounds numpy to fix CI failure

This PR is for quickly fix the mypy test failure to unblock other PRs caused by NumPy 1.20.0 release.
This upper bound should be removed again when finishing & merging #2026

I'd merge this now to unblock other PRs.
I'm working on the support NumPy 1.20.0 at #2026 which would remove the upper bound.

Sorry I mistakenly set the title as commit name rather than PR title when merging.


Bug in element-wise power

On this line of power.py, the variable p does not appear to be defined. The surrounding code is
        if self.p_rational is not None:
            p = self.p_rational
        elif p.value is not None:    # <-- This check looks problematic and is flagged as such by my linter
            p = self.p.value
        else:
            raise ValueError("Cannot compute grad of parametrized power when "
                             "parameter value is unspecified.")

Version

OS: Any
CVXPY Version: master

Additional context
Add any other context about the problem here.

Fixed on master. Thanks for pointing this out! What is your linter?


support nginx cookie learn session sticky

/kind feature

Should support cookie learn sticky method (http://nginx.org/en/docs/http/ngx_http_upstream_module.html#sticky)
I think this may be useful

Closing. This option is available only in the commercial version of nginx

@aledbf thank you , I know


Make copycat connections own dedicated gRPC channel

Earlier, gRPC channel cache in CopycatGrpcClient was not checking channels' health status. This was causing unhealthy/revoked channels to be reused sometimes for targets that have failed over. Restarted node was not remembering existing channels' authentication Id, so no new connections could be accepted.
Rather than disposing unhealthy channels from cache during connection building, this PR makes each connection own its own gRPC channel. There are two reasons for that:

As a simplification of code base as copycat already does connection pooling. So channels will be cached implicitly by Copycat.
When cluster membership changes, each copycat server resets its connection pool, which in turn closes each outstanding connection. There is no place to receive this event from transport layer, so caching gRPC channels outside causes old channels to linger around after their target is lost.

A trade off, imposed by copycat's connection reset procedure, is that when cluster membership changes, n^2 gRPC authentication will take place among servers. (n being participating node count). This is because new connections will be given their own brand new channels. This is not expected during normal operation and could happen only during bootup/failover and explicit membership change.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4883/
Test FAILed.

Jenkins, test this please.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4888/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4889/
Test PASSed.

@calvinjia PTAL. Thanks!

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4895/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4903/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4908/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4914/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4919/
Test PASSed.

alluxio-bot, merge this please.


Allow referendums to begin out of order

Right now, referendums can only begin if they end after the latest-ended existing referendum. This basically means that fast-tracking cannot work unless there is not an existing referendum happening.
This PR relaxes that constraint.

Test added.

After looking again into the code, I'm not sure if we should change NextTally to LowestTally or whatever, but that it points to the lowest still active index.
You also need to adapt the functions active_referenda and maturing_referenda_at as they still use take_while. (These functions also would not find any referendum that is still active and has a lower index as the one returned by next_tally().)

Please check my changes (made before your comment, but possible after your review). There is no take_while in that file.

You're right about the renaming - just fixed.

After looking again into the code, I'm not sure if we should change NextTally to LowestTally or whatever, but that it points to the lowest still active index.
You also need to adapt the functions active_referenda and maturing_referenda_at as they still use take_while. (These functions also would not find any referendum that is still active and has a lower index as the one returned by next_tally().)

Please check my changes (made before your comment, but possibly after your review). There is no take_while in that file.

For some reason I have overlooked this. With the rename it is not much better/clearer.


Failed to install extension scheduler (v0.1.1). 500 INTERNAL SERVER ERROR

unfortunately I get this error when I hit install, tried also with 0.1.0 same error.
no further informations available, can you help out and point into right direction?
lnbits 0.12.4 running on citadel node

I'm not famiiar with running the citadel node but if you are running the LNBits inside of a docker container, this may not work.  It is best run on a standalone barebones setup on ubuntu.
The user that runs LNBits server MUST have crontab -e permissions in order to read/write to crontab file. So you will need to enable that. (See the README file.)

done, moved to raspibolt :D just because of this.


Redo all the sprites

[ ] Vanishing platforms
[x] Door
[ ] Checkpoints
[ ] Spider / Ghosts
[ ] Portals
[ ] Lazers
[x] trampolines -> pumpkines
[x] Add foreground / background
[x] Keys
[ ] Candy

Updated what is done so far (the list does not concern the animations).

NB*- the list does not concern the animations.


Replace AutoML test with tests for each sample which execute (not skipped)

Every code sample should have a corresponding test which is not skipped, as much as possible.
In cases where a code sample runs a long-running operation, this may mean that the cloud.google.com code sample may be extended to include a cancellation.
Alternatively, the test can cancel the operation after it has been started.
Operations which run in a reasonable amount of time should be executed, e.g. anything which takes < 1 minute to execute (as an example)

@googleapis/ml-apis


Updated sql file and added security settings for LQA

Creating this PR to help in creating LQA orgs set up.
Critical Changes
Changes
Issues Closed
New Metadata
Unpackaged Metadata
Deleted Metadata
Testing Notes

Closing this PR since it will be covered in another one.


chore: convert e2e tests to using the crawlers directly

Closes #81

I am probably a bit out of context here, but I just realized that we're currently changing e2e to basically normal actors, while originally these were testing the crawlers (public actor crawlers, i.e. cheerio, puppeteer, and web scraper), including their input. This applies to my PR too btw. Now we basically test the SDK here, and that's ok, but just double-checking whether it's something that we do intentionally as at some point we would need to upgrade the scrapers (public actors) too @B4nan
As for our discussion on Slack regarding SSL tests @vladfrangu - I tried locally and I think they work as expected, one test ignores SSL errors, and the other one doesn't. Need to adjust the numbers in assertions and it should be good.
There are web-scraper tests too, but given we are converting these to e2e SDK test - I guess we could just remove web-scraper ones for now?

Now we basically test the SDK here

Yes, e2e tests of the SDK, on the platfom, via apify-client rather than storage-local.
This repository will not contain the apify package, neither apify storage local or the actor scraper repository - those will go to another monorepo. We could have such tests for the public scrapers there, but not here, here we care about the SDK/crawlee code only.

In this case, I guess we could remove all web-scraper tests straight away (not to be distracted by them here), as it's also using puppeteer under the hood.

Yeah exactly, we already discussed that with @vladfrangu, I believe that's why the PR is marked as draft, other than that it should be ready.

Got it, cool! One more thing - Since In my draft I will basically have it now with a full actor directory (with Docker file) - wanted to see how we're going to proceed? Vlad could probably merge it and I will convert it as I did with the first test + double-check the assertions and stuff, or should just merge the PRs? Just checking what and when should I do with my part :)

Yop, we will first merge this one, and you will convert them all to the new shape.

That should be everything :D

perfect, lets wait for the green light :]


jQuery Mobile: tiles missing and locate not in the map center

Steps to reproduce:

open: http://output.jsbin.com/gekowud in Chrome, Safari, Firefox or the iOS Simulator
the lower tiles are missing
press the tab "Locate".
your position will be located but the marker is not in the map center. all tiles are being loaded. in the iOS simulator tiles are still missing.

if you resize the browser in step 2. then all missing tiles will be loaded.
Please see the screenshots attached.
Please also test with the iOS simulator in the homescreen mode (website saved to the homescreen an run from there)
The CSS class .ui-content shall not be changed as this would affect the rest of the layout of the app. So we use the DIV with CSS class .map-outer to style the map.

Use map.invalidateSize() after the map container size or visibility changed.

The map container size or visibility is not being changed dynamically here. The map is being created in the jQuery mobile event pageshow. So when should I call map.invalidateSize() then? Could you please correct the example http://output.jsbin.com/gekowud without styling .ui-content That would be great - thank you very much!

I'm not familiar with jQuery mobile — you'll have to ask for help on the Leaflet forum or figure it out yourself. This isn't a Leaflet issue if it can't be replicated without jQuery mobile.

ok - solved it here: http://jsbin.com/ruqaqo
by calling:
setTimeout(correct_view, 1);
in the jQuery Mobile "pageinit" event but don't consider it a very elegant solution though.
function correct_view() {
map.invalidateSize();
}

map.setZoomAround() doesn't seem to work here properly in http://jsbin.com/ruqaqo why is that? if you click on the tab "locate" the map center is not the found position of the user but slightly shifted.

@googol7 you should ask on the forum for help using Leaflet: https://groups.google.com/forum/#!forum/leaflet-js
This issue tracker is only for Leaflet codebase itself.


Compile fail on windows 10 + MSYS2 + ninja.exe

Good morning
I am trying to compile the "library" on the wfollowgin environment

Windows 10 64bit

$ cat /proc/version
MSYS_NT-10.0-19044 version 3.3.6-341.x86_64 (runneradmin@fv-az277-82) (gcc version 11.3.0 (GCC) ) 2022-10-24 08:25 UTC

$ pacman -Qe
base 2022.06-1
base-devel 2022.01-2
filesystem 2022.01-5
git 2.38.1-1
mingw-w64-clang-x86_64-github-cli 2.18.0-1
mingw-w64-cross-zlib 1.2.11-1
mingw-w64-i686-zlib 1.2.13-1
mingw-w64-ucrt-x86_64-zlib 1.2.13-1
mingw-w64-x86_64-binutils 2.39-2
mingw-w64-x86_64-cmake 3.24.2-4
mingw-w64-x86_64-crt-git 10.0.0.r113.g57fd0b77a-1
mingw-w64-x86_64-gcc 12.2.0-4
mingw-w64-x86_64-gcc-ada 12.2.0-4
mingw-w64-x86_64-gcc-fortran 12.2.0-4
mingw-w64-x86_64-gcc-libgfortran 12.2.0-4
mingw-w64-x86_64-gcc-libs 12.2.0-4
mingw-w64-x86_64-gcc-objc 12.2.0-4
mingw-w64-x86_64-gdb 12.1-4
mingw-w64-x86_64-gdb-multiarch 12.1-4
mingw-w64-x86_64-headers-git 10.0.0.r113.g57fd0b77a-1
mingw-w64-x86_64-libgccjit 12.2.0-4
mingw-w64-x86_64-libmangle-git 10.0.0.r113.g57fd0b77a-1
mingw-w64-x86_64-libwinpthread-git 10.0.0.r113.g57fd0b77a-1
mingw-w64-x86_64-make 4.3-1
mingw-w64-x86_64-pkgconf 1~1.8.0-2
mingw-w64-x86_64-qt6-base 6.4.0-3
mingw-w64-x86_64-tools-git 10.0.0.r113.g57fd0b77a-1
mingw-w64-x86_64-winpthreads-git 10.0.0.r113.g57fd0b77a-1
mingw-w64-x86_64-winstorecompat-git 10.0.0.r113.g57fd0b77a-1
mingw-w64-x86_64-wxwidgets3.2-msw 3.2.1-1
msys2-runtime 3.3.6-3

I have updated the repository as of today
$ git rev-parse HEAD
7c66c88d4b075ef2c01388889ea0f9658e8cbb38

damiano.bolla@P2-DAMIANOB MSYS /c/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz
$ git status
On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   CMakeLists.txt

there is one line added to CMakeList.txt
SET(wxWidgets_ROOT_DIR "c:/msys64/mingw64")
The error that appears is
$ ninja.exe
[36/67] Building CXX object CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj
FAILED: CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj
C:\msys64\mingw64\bin\c++.exe -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXMSW__ -isystem C:/msys64/mingw64/lib/wx/include/msw-unicode-3.2 -isystem C:/msys64/mingw64/include/w
x-3.2 -g -std=gnu++17 -MD -MT CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj -MF CMakeFiles\Wisteria.dir\src\ui\app.cpp.obj.d -o CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj -c C
:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp: In constructor 'Wisteria::UI::BaseApp::BaseApp()':
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp:21:5: error: 'wxHandleFatalExceptions' was not declared in this scope; did you mean 'OnFatal
Exception'?
   21 |     wxHandleFatalExceptions();
      |     ^~~~~~~~~~~~~~~~~~~~~~~
      |     OnFatalException
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp: In member function 'void Wisteria::UI::BaseApp::GenerateReport(wxDebugReport::Context)':
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp:279:84: error: cannot convert 'wxString' to 'LPCWSTR' {aka 'const wchar_t*'}
  279 |             ShellExecute(NULL, _DT(L"open"), wxStandardPaths::Get().GetDocumentsDir(),
      |                                              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
      |                                                                                |
      |                                                                                wxString
In file included from C:/msys64/mingw64/include/windows.h:89,
                 from C:/msys64/mingw64/include/winsock2.h:23,
                 from C:/msys64/mingw64/include/wx-3.2/wx/msw/wrapwin.h:46,
                 from C:/msys64/mingw64/include/wx-3.2/wx/msw/init.h:27,
                 from C:/msys64/mingw64/include/wx-3.2/wx/init.h:58,
                 from C:/msys64/mingw64/include/wx-3.2/wx/app.h:23,
                 from C:/msys64/mingw64/include/wx-3.2/wx/wx.h:25,
                 from C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.h:15,
                 from C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp:9:
C:/msys64/mingw64/include/shellapi.h:76:79: note:   initializing argument 3 of 'HINSTANCE__* ShellExecuteW(HWND, LPCWSTR, LPCWSTR, LPCWSTR, LPCWSTR, INT)'
   76 |   SHSTDAPI_(HINSTANCE) ShellExecuteW (HWND hwnd, LPCWSTR lpOperation, LPCWSTR lpFile, LPCWSTR lpParameters, LPCWSTR lpDirectory, INT nShowCmd);
      |                                                                       ~~~~~~~~^~~~~~
[41/67] Building CXX object CMakeFiles/Wisteria.dir/src/ui/controls/searchpanel.cpp.obj
ninja: build stopped: subcommand failed.

Thank you for any possible hint

Can you please try this:

Open "Wisteria-Dataviz/src/ui/app.cpp"
Change line 279 to this:
 ShellExecute(NULL, _DT(L"open"), wxStandardPaths::Get().GetDocumentsDir().wc_str(),

Basically, adding .wc_str() to the end of wxStandardPaths::Get().GetDocumentsDir().
Then try to compile again.  wxString has an implicit conversion to wchar_t*, but that appears to not be happening here.

I just checked in a possible fix. Please let me know if there's still an error.

Better, there is a different, shorter, error
I did delete the build directory and run again cmake ../ and ninja
$ ninja.exe
[37/70] Building CXX object CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj
FAILED: CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj
C:\msys64\mingw64\bin\c++.exe -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXMSW__ -isystem C:/msys64/mingw64/lib/wx/include/msw-unicode-3.2 -isystem C:/msys64/mingw64/include/w
x-3.2 -g -std=gnu++17 -MD -MT CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj -MF CMakeFiles\Wisteria.dir\src\ui\app.cpp.obj.d -o CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj -c C
:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp: In constructor 'Wisteria::UI::BaseApp::BaseApp()':
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp:21:5: error: 'wxHandleFatalExceptions' was not declared in this scope; did you mean 'OnFatal
Exception'?
   21 |     wxHandleFatalExceptions();
      |     ^~~~~~~~~~~~~~~~~~~~~~~
      |     OnFatalException
[42/70] Building CXX object CMakeFiles/Wisteria.dir/src/ui/controls/codeeditor.cpp.obj
ninja: build stopped: subcommand failed.

Thanks !

I just pushed a fix for the wxHandleFatalExceptions compile error. Thanks!

Not easy to squash this bug
$ ninja.exe
[37/70] Building CXX object CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj
FAILED: CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj
C:\msys64\mingw64\bin\c++.exe -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXMSW__ -isystem C:/msys64/mingw64/lib/wx/include/msw-unicode-3.2 -isystem C:/msys64/mingw64/
include/wx-3.2 -g -std=gnu++17 -MD -MT CMakeFiles/Wisteria.dir/src/ui/app.cpp.obj -MF CMakeFiles\Wisteria.dir\src\ui\app.cpp.obj.d -o CMakeFiles/Wisteria.dir/src/u
i/app.cpp.obj -c C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp: In constructor 'Wisteria::UI::BaseApp::BaseApp()':
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp:22:5: error: 'wxHandleFatalExceptions' was not declared in this scope; did you mean
 'OnFatalException'?
   22 |     wxHandleFatalExceptions();
      |     ^~~~~~~~~~~~~~~~~~~~~~~
      |     OnFatalException
[42/70] Building CXX object CMakeFiles/Wisteria.dir/src/ui/controls/codeeditor.cpp.obj
ninja: build stopped: subcommand failed.

I also have attached the current config files
Thanks for your help
build.ninja.txt
CMakeCache.txt

I've explicitly added an include for the header that wxHandleFatalExceptions() is in; hopefully that will fix it.

I have done some digging up the dead, if I am not mistaken the "method" wxHandleFatalExceptions is available only when using a Microsoft compiler and since I am using gcc .... it is not available.

there are a few ways to "fix" this, it is up to you which one to choose.
I did comment line 22 of app.cpp and the compile continued, but eventually failed with the attached message
log.txt

Just added explicit checks for MSVC and also the ERROR_CLOUD_FILE_* constants, so MinGW should skip over those now.  I did a scan for any other Win32 specific code and didn't see any, so hopefully this should be it...

Would it be easier if there is a CI build for mingw environment? I can try to add that. Any build instructions would be helpful.

better !
there are issues at linking level
the ninja.exe report is attached to this comment
I fail to see how a specific build for mingw would help to make things simpler, this just means that I am happy with current inteructions, the issues at hand are peculiar to the
log.txt
usual crap windows (I have to use it here, unfortunately)

Do you have the file "src/wxSimpleJSON/src/wxSimpleJSON.cpp" in your set of Wisteria files?  It seems like that file is entirely missing or at least not being included in your build.
If you are using the CMake file (it looks like you are), then it should be getting the list of all files to include from "tools/files.cmake".  In that "files.cmake" file, it should mention "src/wxSimpleJSON/src/wxSimpleJSON.cpp"...do you see that?
Did you download the submoduldes when you did a git pull initially?  If not, git submodule update --init should download them.

Yes, the source tree is updated, even the submodules
What I am doing is:
mkdir build
cd build
cmake ..
ninja.exe
I have captured the output of ninja
ninja.log

I updated one of the submodules, wxSimpleJSON, to fix this. It appears that WXUSINGDLL is defined somehow in the build workflow with MinGW and that was messing up this submodule's linking. So I made it use its own define (instead of WXUSINGDLL) and that should get rid of the dllimport linking errors.

Better, after having updated submodules, ninja almost arrives to the end
$ ninja.exe
[70/70] Linking CXX executable WisteriaDemo.exe
FAILED: WisteriaDemo.exe
cmd.exe /C "cd . && C:\msys64\mingw64\bin\c++.exe -g -mwindows CMakeFiles/WisteriaDemo.dir/demo/demo.cpp.obj CMakeFiles/WisteriaDemo.dir/C_/msys64/mingw64/include/wx/ms
w/wx.rc.obj -o WisteriaDemo.exe -Wl,--out-implib,libWisteriaDemo.dll.a -Wl,--major-image-version,0,--minor-image-version,0  libWisteria.a  -LC:/msys64/mingw64/lib  -pip
e  -Wl,--subsystem,windows  -mwindows  -lwx_mswu_core-3.2  -lwx_baseu-3.2  -lwx_mswu_html-3.2  -lwx_mswu_ribbon-3.2  -lwx_baseu_xml-3.2  -lwx_mswu_xrc-3.2  -lwx_mswu_qa
-3.2  -lwx_mswu_propgrid-3.2  -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 && cmd.exe /C "cd /D C:\Users\damiano.bol
la\Documents\eclipse-python\Wisteria-Dataviz\build && mt.exe -manifest "C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/demo/wx_dpi_aware.manifest" -ou
tputresource:"C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/build/WisteriaDemo.exe";#1 && cd /D C:\Users\damiano.bolla\Documents\eclipse-python\Wiste
ria-Dataviz\build && C:\msys64\mingw64\bin\cmake.exe -E copy_directory C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/demo/res C:/Users/damiano.bolla/
Documents/eclipse-python/Wisteria-Dataviz/build/res && cd /D C:\Users\damiano.bolla\Documents\eclipse-python\Wisteria-Dataviz\build && C:\msys64\mingw64\bin\cmake.exe -
E copy_directory C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/datasets C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/build/datase
ts""
'mt.exe' is not recognized as an internal or external command,
operable program or batch file.
ninja: build stopped: subcommand failed.

You are doing an impressive job, it is just that you are fighting against a horde of mindless greedy zombies
Thanks

I removed the call to MT.exe, that will fix that final message.  I also added flags for MSYS2, so that should be the last of any Visual Studio dependency.
I think my main fight is with dashboarding software.  Dashboards make me sad; I hope to provide a more artistic alternative with this program.

The movie is not done, yet
$ ninja.exe
[39/70] Building CXX object CMakeFiles/WisteriaLib.dir/src/ui/app.cpp.obj
FAILED: CMakeFiles/WisteriaLib.dir/src/ui/app.cpp.obj
C:\msys64\mingw64\bin\c++.exe -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXDEBUG__ -D__WXMSW__ -DwxDEBUG_LEVEL=2 -isystem C:/msys64/mingw64/lib/wx/include/msw-unicode-3.2
-isystem C:/msys64/mingw64/include/wx-3.2 -g -Wall -Wextra -Wpedantic -Og -std=gnu++17 -MD -MT CMakeFiles/WisteriaLib.dir/src/ui/app.cpp.obj -MF CMakeFiles\WisteriaLib.
dir\src\ui\app.cpp.obj.d -o CMakeFiles/WisteriaLib.dir/src/ui/app.cpp.obj -c C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp: In member function 'virtual int Wisteria::UI::BaseApp::OnExit()':
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp:145:31: error: cannot convert 'const wxString' to 'LPCWSTR' {aka 'const wchar_t*'}
  145 |             OutputDebugString(memMsg);
      |                               ^~~~~~
      |                               |
      |                               const wxString
In file included from C:/msys64/mingw64/include/winbase.h:15,
                 from C:/msys64/mingw64/include/windows.h:70,
                 from C:/msys64/mingw64/include/winsock2.h:23,
                 from C:/msys64/mingw64/include/wx-3.2/wx/msw/wrapwin.h:46,
                 from C:/msys64/mingw64/include/wx-3.2/wx/msw/init.h:27,
                 from C:/msys64/mingw64/include/wx-3.2/wx/init.h:58,
                 from C:/msys64/mingw64/include/wx-3.2/wx/app.h:23,
                 from C:/msys64/mingw64/include/wx-3.2/wx/wx.h:25,
                 from C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.h:15,
                 from C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/ui/app.cpp:9:
C:/msys64/mingw64/include/debugapi.h:21:54: note:   initializing argument 1 of 'void OutputDebugStringW(LPCWSTR)'
   21 |   WINBASEAPI VOID WINAPI OutputDebugStringW (LPCWSTR lpOutputString);
      |                                              ~~~~~~~~^~~~~~~~~~~~~~
[44/70] Building CXX object CMakeFiles/WisteriaLib.dir/src/ui/controls/searchpanel.cpp.obj
ninja: build stopped: subcommand failed.

Let's look it in a positive way, better to discover rats earlier than later
Thanks

...and that string casting issue is fixed now.

YESSS !!!
Thank you ! It works !
There is one minor issue, if you wish to handle it
I am closing the ticket, thanks for your help
$ ninja.exe
[60/70] Building CXX object CMakeFiles/WisteriaLib.dir/src/util/memorymappedfile.cpp.obj
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/util/memorymappedfile.cpp: In member function 'bool MemoryMappedFile::MapFile(const wxString&, bool
, bool)':
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/util/memorymappedfile.cpp:88:12: warning: catching polymorphic type 'class MemoryMappedInvalidFileS
ize' by value [-Wcatch-value=]
   88 |     catch (MemoryMappedInvalidFileSize)
      |            ^~~~~~~~~~~~~~~~~~~~~~~~~~~
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/util/memorymappedfile.cpp: In instantiation of 'MemoryMappedFile::MapFile(const wxString&, bool, bo
ol)::<lambda(auto:1)> [with auto:1 = long unsigned int]':
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/util/memorymappedfile.cpp:145:29:   required from here
C:/Users/damiano.bolla/Documents/eclipse-python/Wisteria-Dataviz/src/util/memorymappedfile.cpp:121:53: warning: unused parameter 'errorCode' [-Wunused-parameter]
  121 |         const auto isCloudFileError = [](const auto errorCode) noexcept
      |                                          ~~~~~~~~~~~^~~~~~~~~
[70/70] Linking CXX executable demo\WisteriaDemo.exe

Awesome! And thanks for all your help and patience!
(I just fixed those warnings also.)


ADComputer: Add example to create cluster computer account

Pull Request (PR) description

Changes to ActiveDirectoryDsc

Fix examples that had duplicate guid that would have prevented them
to be published.

Changes to ADComputer

Add example showing how to create cluster computer account (issue #401).

This Pull Request (PR) fixes the following issues

Fixes #401

Task list

[x] Added an entry under the Unreleased section in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in resource directory README.md.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[x] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #461 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##            dev   #461   +/-   ##
===================================
  Coverage    98%    98%
===================================
  Files        20     20
  Lines      2809   2809
  Branches     10     10
===================================
  Hits       2761   2761
  Misses       38     38
  Partials     10     10


Refined type annotations

to pass mypy with --disallow-untyped-defs --disallow-any-generics

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
63

Relevant Lines:
63

💛  - Coveralls


Question about repo

I'd like to clarify, does this repo convert GoPro video and synchronized IMU data into EuRoC formats so that it can be used by VIO systems?

Yes that is correct.


Add support for transpiled modules

Don't merge yet
This PR tracks how best to handle CommonJS modules that have already been transpiled by Babel, TypeScript or something similar. These CommonJS modules define a __esModule property on their exports object, and export their default export as a default property.
We should:

remove the __esModule property
use the default property for the default export instead of the module.exports object

Fixes #10

Would it be appropriate to warn users in this situation? It may be that we're dealing with external packages, in which case the user may have limited control, but it might help people understand that their Babel config is messed up etc

messed up? does this mean it’s somehow not working as intended? why?

@flying-sheep Messed up as in Babel is being used to convert ES6 modules to CommonJS modules, which means Rollup has to convert them back to ES6 modules so that it can bundle them (quite possibly in order to generate a CommonJS bundle). Keeping everything as ES6 until you need to run it is the name of the game.

ok, but how? jsnext:main should point to a “distributable” package, not a ES2015 package… should we really introduce another field and copy of the lib for an ES2015 version?
i’ll comment in rollup/rollup#337 about it.
for this issue and plugin, i think we should simply detect the most common ways stuff is distributed and be practical instead of idealistic. this is a practical plugin, written for a world of commonjs modules. it should “get” as many of them as possible.

Should have been more specific – I meant keeping everything as ES6 modules is the goal, since that's the only thing that's getting translated back and forth otherwise.

makes sense. this is a frequent language confusion in the discussions here.
but still: both should be supported as we can’t hope to convince everyone and therefore be practical.

let’s help redux with fixing their use of jsnext:main
let’s finish and pull this PR

then we can actually work productively with rollup as node_modules bundler

Looks good to me. :+1:

Have released this as 2.0.0 (since it's technically a breaking change) – it doesn't include warnings about already-transpiled modules, but we could revisit that in future if we choose

Sorry, I think this change is indeed breaking support of rollup modules in browserify/babel. If you export default but not __esModule, browserify/babel won't pick that up. I had left a comment here too: https://github.com/rollup/rollup/issues/496#issuecomment-198746673


Question: Notes on upgrading to razzle@next

Hi,
We've bene using Razzle from about the December 2017. Things have moved on and we'd love to make use of the latest features (such as WebPack 4). We've had to expand quite extensively on razzle.config.js, so my question is this: What do we need to look out for or change in our razzle.config.js in order to upgrade to razzle@next?
Any tips or ideas appreciated.

probably majority of your challenges will be with webpack plugins (if you use any, outside of razzle).
For example:
//No supporting webpack 4
//const ExtractTextPlugin = require('extract-text-webpack-plugin');
//replaced with
const MiniCssExtractPlugin = require("mini-css-extract-plugin");

//Does not work with webpack 4
//const InlineChunkManifestHtmlWebpackPlugin = require('inline-chunk-manifest-html-webpack-plugin');

A good chunk of razzle's internal things are based off Create React App.
Create React App is in early stages of migrating to webpack 4.
Eventually Razzle, could take advantages of the changes they are making in CRA.
In a way, razzle is a bit ahead of CRA in this respect (as CRA official releases are still on web pack 3)

Yeah, we do. We use things like SASS, SWPrecache and CodeSplitting.
We'd love to know when Razzle starts implementing these so we don't have to. 🥇
Should we then look to see which of these features (such as SWPrecache) is implemented in CRA?
You're quite correct in porting the ones we have to WP4, will be a challenge.


Hide ViewMore Link if no expanded documentation

Bug/issue #, if applicable: rdar://106860554
Summary
Hide the view more link if there is no expanded documentation based on the metadata
Dependencies
https://github.com/apple/swift-docc/pull/510
Testing
Steps:

Manually add metadata.hasNoExpandedDocumentation to a render json
Verify its ViewMore link doesn't show.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran npm test, and it succeeded
[ ] Updated documentation if necessary - NA

@swift-ci test

@swift-ci test


FRONTEND WITH FRAMEWORK: VueJS-5.2 => Emitting events

Description
Contributors are required to explain about Emitting events in VueJs, which should cover questions like:-
What is the meaning of Emitting events in Vue.js?
How does this work?
Why there is a need for this?
What are the advantages to use it and when to use it?
How to implement this with code (also give theory explanation of code)?
You can take 2-3 examples with codes of different types to explain this.
etc....
Note:
Plagiarism is strictly prohibited.
Changes should be made inside the Frontend_Web_Development_React_Angular_Vue/ dir inside Frontend_Web_Development_React_Angular_Vue branch.
Files need to be added into the Week5 folder only.
Domain
Frontend Dev React/Angular/Vue
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

@YASHMAROO, any updates?

@SourabhSaraswat-191939 I have made the PR. Please review it. Sorry for late submission.


Problem using zoom in the page

When I have the 150% zoom in the page and I open up this hidden list which contains "about", "documentation", etc. When I select one of them I can't get in

@Fede5432 thank you for reporting this issue! I have opened #1917 to fix this, and deployed it to https://dscho.github.io/git-scm.com/. Could you please verify that it works for you there?


Updated touchable components and added new Expo example with newer React Native version

I had problems in a project, where I updated the React Native version. The fix is mentioned here: https://github.com/sohobloo/react-native-modal-dropdown/issues/251#issuecomment-673422043
There should not be two touchable components nested.
So I wanted to update the example in this repository. Problem was, that the update of React Native from 0.53.0 made problems. I decided to setup a new example with using Expo (latest SDK 38), which uses React Native 0.62.2.
After that I decided to resolve some open issues. I wanted to make the used touchable component less hard coded. So I created new props to pass components and props for the rendered rows of the dropdown and the main button.
Resolves #7
I encountered problems with using TouchableNativeFeedback on Android. I wanted this as default, but the onPress is not triggered for some weird reason. One can read about problems with that component in the web and also on the official documentation: https://reactnative.dev/docs/touchablenativefeedback

At the moment it only supports having a single View instance as a child node...

Maybe there is a way to fix that, but I did not find out.
With doing that, it was a small addition to add also new props to be passed for the Text, which is rendered when not passing renderRow.
Resolves #5

@siemiatj is there a way to assist you with managing pull requests? It would be nice to go on here and grab further issues.


Project pipeline is failing

See here.

It looks like this is now biting the buildpack too, see here
Notably:
Your CF API version (2.125.0) is no longer supported. Upgrade to a newer version of the API (minimum version 2.128.0). Please refer to https://github.com/cloudfoundry/cli/wiki/Versioning-Policy#cf-cli-minimum-supported-version


Fix typos in cel.md

@fenggw-fnst Thanks for identifying and applying the fixes
/lgtm
Deploy Preview: deploy-preview-40015

/approve


Bind path rewriting

We need to replace Windows paths to their WSL equivalents when creating a container so mounting works properly in WSL.

See https://github.com/docker/for-win/issues/6628#issuecomment-635906394 for path formats that we need to handle.


refactor assert_satisfied_full

uses MockProver utils inside assert_satisfied_full which enables additional missing checks for things like assert zero expressions.
removes duplicate code to check of multiplicity
enables MockProver to check for multiplicity of all instances (previously only instance 0 was considered)

@matthiasgoergens Thanks for review and suggestion PR!

Can't we change that? let lk_mlt = if std::env::var("MOCK_PROVING").is_ok() {

That part of the code executes before the mock prover is triggered in the e2e test. Since by the time we are in mock prover, the lk_mlt data is deleted. Unless we add a similar condition before data is deleted, it's difficult to recover the data.


⚠ Bofrost.lu has degraded performance

In c38c707, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1928 ms

Resolved: Bofrost.lu performance has improved in f4f7ce5 after 20 minutes.


Can't navigate from header

1.0.0-beta.9
No error messages, no warnings...
Clicking the button fires goToNewEvent but doesn't navigate to the route.
...
events: {
	screen: StackNavigator({
		events: { screen: HomeScreen },
		newEvent: { screen: NewEventScreen }
	})
}
...

class NewIcon extends Component {
	goToNewEvent = () => {
       		this.props.navigation.navigate({
        		routeName: 'newEvent'
    		});
    	};
  	render() {
	    return (
	      	<TouchableOpacity onPress={() => this.goToNewEvent()}>
			<Icon name='new-message' color='black' size={25} />
		</TouchableOpacity>
	    );
  	}
}

class HomeScreen extends Component {
	static navigationOptions = ({navigation}) => ({
		tabBarIcon: ({focused}) => (focused ? HomeIcon : HomeIconWhite),
		headerRight: <NewIcon navigation={navigation} />,
		title: <Text style={{color: 'black'}}>Events</Text>,
		headerStyle: {
			backgroundColor: 'white'
		}
	})

	constructor(props) {
	    super(props);
	}

	render() {
		return (
			<View style={{flex: 1}}>
			</View>
		);
	}
}

You should call navigate('newEvent') instead. The format with { routeName: 'newEvent' } is used for the NavigationActions.navigate method.

Generates this error when I try to navigate:
"Invalid data message - all must be length: 36"

import React, { Component } from 'react';
import {
	View,
	Text
} from 'react-native';

class NewEventScreen extends Component {

	constructor(props) {
	    super(props);
	}

	render() {
		return (
			<View style={{flex: 1}}>
			</View>
		);
	}
}

export default NewEventScreen;

Also, this error logs with the previous one:
Converting circular structure to JSON

getting the same message

Ok I found the issue. Changing the title in my navigationOptions to a generic string instead of a <Text> component resolves the error. Seems like either this is no longer accepting anything but generic strings, or this is a bug. Im uncertain since its hard to tell where in the react-native code this error is being thrown.

To use a custom component for the title in the header, you have to use the headerTitle option.
static navigationOptions = ({navigation}) => ({
  // ...
  headerTitle: <Text style={{color: 'black'}}>Events</Text>,
  headerStyle: {
    backgroundColor: 'white'
  }
})

headerTitle will also have precedence over title

But if the only customisation you want to do is concerning style, then you can simply set the headerTitleStyle option.

Right but ideally some where this should be caught and a warning or error should be thrown with a message.

Everything is good now I guess.


admin way to dump leveldb

addition of a /healthz for Kubernetes liveness and readiness probe. An admin handler that, if enabled via command line, allows one to dump out the leveldb and save it off just in case LevelDB should get corrupted. Like in a Kubernetes migration or some such silliness. Assumptions are made that the running Go is protected via Underpants or some other mechanism. Also a command line tool to load it back should need be.

Sorry for the delay on this. Updated are per previous comments with iterator Release and check for Error from iterator.


Enabled and auto generated forget() method for UsbDevice

This will allow the user to forget a device which has been "trusted" or "remembered" by the browser.
As defined here: https://developer.mozilla.org/en-US/docs/Web/API/USBDevice/forget
Apologies for my earlier erroneous pull request.

I added something, is that sufficient?

Thank you!


add accessors for remaining org.freedesktop.Secret.Item properties

https://specifications.freedesktop.org/secret-service/re03.html
Adds methods to item: Created(), Modified(), Attributes()

ping

If you'd like, you can open a PR on my fork. I am attempting to keep this project maintained.

@ciehanski Awesome! thanks for keeping it alive. I forgot why I even added these now but hope to remember soon ;)  -- https://github.com/ciehanski/go-libsecret/pull/3


wrong book input?

Continuation from https://github.com/Disservin/fast-chess/pull/556#issuecomment-2227093885
For a game (at fixed depth) with different result between cutechess and fast-chess, the origin seems to be in parsing the book. The initial FEN in the corresponding match pgn is:
fast-chess:
[FEN "rnbqkbnr/ppp2ppp/8/3Pp3/8/8/PPPP1PPP/RNBQKBNR w KQkq - 0 1"]
leading to
1. Nc3 {+1.00/10, 0.006s} Nf6 {-0.98/12, 0.026s} 2. Nf3 {+0.92/10, 0.007s}
Bd6 {-0.75/12, 0.019s} 3. d4 {+0.62/10, 0.015s} e4 {-0.67/12, 0.010s}

cute-chess:
[FEN "rnbqkbnr/ppp2ppp/8/3Pp3/8/8/PPPP1PPP/RNBQKBNR w KQkq e6 0 1"]
1. dxe6 {+1.34/10 0.003s} Bxe6 {-1.24/12 0.019s} 2. Nf3 {+1.43/10 0.003s}
Nf6 {-1.24/12 0.004s} 3. Nc3 {+1.19/10 0.022s} Nc6 {-1.25/12 0.012s}

The book fen is
rnbqkbnr/ppp2ppp/8/3Pp3/8/8/PPPP1PPP/RNBQKBNR w KQkq e6

Reproducible with:
$ cat minibook.epd
rnbqkbnr/ppp2ppp/8/3Pp3/8/8/PPPP1PPP/RNBQKBNR w KQkq e6

and
$ cat do_match_fastchess.sh
for binary in ./cutechess-cli ./fast-chess
do

echo " ============= $binary ============== "

(

$binary         -recover -repeat -games 2 -rounds 1 -tournament gauntlet\
                -pgnout $binary-out.pgn\
                -srand $RANDOM  -resign movecount=3 score=600 -draw movenumber=34 movecount=8 score=20\
                -variant standard -concurrency 1 -openings file=minibook.epd format=epd order=sequential \
                -engine name=sf_1 tc=100+0.1 depth=10 cmd=./sf_1 dir=.\
                -engine name=sf_2 tc=100+0.1 depth=12 cmd=./sf_2 dir=.\
                -each proto=uci option.Threads=1

) | grep "Finished game" | sort -n -k 3 > $binary-out.finished

done

diff ./cutechess-cli-out.finished ./fast-chess-out.finished

hmm possibly because of the removed movecounter?

epd has no move counter?

apparently this is a bug in the setFen where the en peassant square doesnt get parsed when the FEN has no movecounter

good catch, ill fix


Support Azure DevOps specific tags

Basic Markdown

[x] Headers
[x] Paragraphs and line breaks
[x] Blockquotes
[x] Horizontal rules
[x] Emphasis (bold, italics, strikethrough)
[x] Code highlighting
[x] Tables
[x] Lists
[x] Links
[x] Images
[x] Checklist or task list
[x] Emoji
[x] Ignore or escape Markdown syntax to enter specific or literal characters
[x] Attachments (does not make sense)
[x] Mathematical notation and characters, #67

https://docs.microsoft.com/en-us/azure/devops/project/wiki/markdown-guidance?view=azure-devops
Wiki Markdown

[x] Table of contents (TOC) for Wiki pages
[x] Add Mermaid diagrams to a Wiki page
[x] Embed videos in a Wiki page
[x] YAML tags
[x] Embed Azure Boards query results in Wiki
[ ] @mention users and groups
[x] Link to work items from a Wiki page
[x] HTML tag support in wiki pages

https://docs.microsoft.com/en-us/azure/devops/project/wiki/wiki-markdown-guidance?view=azure-devops

For me the checklist or task list already works. (rendered with the devopswikistyle.css)
Screenshot from my PDF:

used markdown
**Result:**

- [ ] A
- [ ] B
- [ ] C
- [x] A
- [x] B
- [x] C

> A checklist within a table cell isn't supported.

For me the checklist or task list already works. (rendered with the devopswikistyle.css)
Screenshot from my PDF:

used markdown

**Result:**

- [ ] A

- [ ] B

- [ ] C

- [x] A

- [x] B

- [x] C

> A checklist within a table cell isn't supported.

Thanks, checked above.

updated because of #75

updated because of #87

@MaxMelcher There is also an Azure DevOps-specific TOC tag that includes child pages: [[TOSP]]


Network (WfFi) Status

Is there an API for the network (WiFi) connection for the car?  I looked around a bit but couldn't find anything relevant.

As far as I know, state is 'asleep' in case of wifi, 'offline' otherwise.
But 'online' is used in both cases when car is awake.

Hmmm.... I was wanting to be able to view, and maybe control, the WiFi connection.  Name, signal strength, MAC address, etc.  But it looks like those things might not be available to the API.

Nope, those aren't on the API.


runtime.Value should log on value update

cc @cw9
Would make debugging etcd issues easier.

https://github.com/m3db/m3cluster/pull/176 should address this


[Feature] add EDU images as an external source

Problem
The goal is to add a good number of external sources to give users a variety of results from different sources.
Description
EDU images ia a free library of photos celebrating students—and the educators who teach them—in seven schools across the United States,  licensed under Creative Commons Attribution-NonCommercial 4.0 International..Gotten from the additional sources list of Openverse available in the file get-additional-sources.ts mentioned in https://github.com/creativecommons/search/issues/48
Adding EDU images as an external source to CC search will be a good addition and will benefit our users.
Alternatives

Additional context

Implementation

[x] I would be interested in implementing this feature.

@possumbilities please triage this issue

Hi @possumbilities I want to wo

@dikehprosper Thankyou for the contribution of making this Issue. You've made several contributions already or are working through them, so I'd suggest you leave this one for someone else who hasn't gotten a chance to contribute to do so.

I want to work on this. Can you assign to me please

@possumbilities alright ma’am as you wish 😊

Please verify and affirm that adding this engine is inline with our new listed criteria here in the Engines Guide, before we proceed with making this status: ready for work

@dikehprosper this engine your proposing though of CC license doesn't return much valuable data nor is the search results numerous... Thus I don't think it'll be best to include it.... You can keep searching for ways to better it and enlighten us...
@possumbilities will have the final say....

Having conducted proper research…I discovered the site does have the CC license registration and the search results are specific to images of students and their tutors in schools across the United States…It does have its own unique content and still display results to searches related to what it offers


Expression evaluation returns true (instead of an error) for "a is X" when X is an unresolved identifier (in Flutter?)

I'm not sure if this is a Dart or Flutter issue - I seem to only be able to reproduce in Flutter, but I assume expression evaluation is done here (@bkonyi you might be more familiar with this - if you think I should move to flutter/flutter, let me know!)
@FMorschel reported to me conditional breakpoints not working as expected, and we tracked it back to expression evaluation returning true for conditions that we didn't expect. We managed to reproduce it with just simple expression eval:

The error messages shown here only show up because I'm running in -verbose mode, otherwise you'd only see the true responses. When doing x is A where A is some class that's apparently not in scope, the result is just true. For non-Flutter dart, you get a reasonable error:

The VM traffic is below. The flutter run stdout output shows the error in verbose mode, but the VM Service response to evaluateInFrame returns a valid boolean of true with no indication that the request failed.
==> [VM] {
	"jsonrpc": "2.0",
	"id": "741",
	"method": "evaluateInFrame",
	"params": {
		"isolateId": "isolates/3676968675006663",
		"frameIndex": 0,
		"expression": "a is FutureOr<int>",
		"disableBreakpoints": true
	}
}
<== [Flutter] [+44567 ms] org-dartlang-debug:synthetic_debug_expression:1:6: Error: 'FutureOr' isn't a type.
<== [Flutter] [        ] a is FutureOr<int>
<== [Flutter] [        ]      ^^^^^^^^
<== [VM] {
	"jsonrpc": "2.0",
	"result": {
		"type": "@Instance",
		"_vmType": "Bool",
		"class": {
			"type": "@Class",
			"fixedId": true,
			"id": "classes/62",
			"name": "bool",
			"location": {
				"type": "SourceLocation",
				"script": {
					"type": "@Script",
					"fixedId": true,
					"id"<EMAIL_ADDRESS>					"uri": "dart:core/bool.dart",
					"_kind": "kernel"
				},
				"tokenPos": 508,
				"endTokenPos": 9302,
				"line": 15,
				"column": 1
			},
			"library": {
				"type": "@Library",
				"fixedId": true,
				"id": "libraries/@0150898",
				"name": "dart.core",
				"uri": "dart:core"
			}
		},
		"identityHashCode": 0,
		"kind": "Bool",
		"fixedId": true,
		"id": "objects/bool-true",
		"valueAsString": "true"
	},
	"id": "741"
}

This appears to be a Flutter issue, possibly the Flutter tools code that interacts with the frontend is not checking for the return code correctly.

//cc @andrewkolos

I'm unassigning myself as it is concluded above that this is not a CFE/expression compilation issue.

@DanTup sorry for the delay, this should probably be moved to the Flutter repo since it's probably an implementation issue with Flutter's expression evaluation.

np - I've moved this to https://github.com/flutter/flutter/issues/157922


Cannot replicate one of the screenshots

Bug Description
I have tried searching everywhere, and I copied you settings in the readme file but I cannot replicate the screenshot shown in this issue. Please tell me or include in the readme file how to make the right side big.
Your one:

My one:

To Reproduce
No response
Extensions log
No response
Screenshots

I apologize for the late reply. You need to install this extension, enable this theme in its settings afterwards, restart and then increase the Grid View details width in Playnite settings under layout.
https://playnite.link/addons.html#ThemesDetailsViewToGridViewConverter_ef8a7226-eedc-478d-a506-92ee6c088aa3


Hint for form fields is now a help cursor instead of underline (which implies link)

Which issue is fixed by this PR? If not related to an existing issue, what does this PR do?
In Traffic Portal forms, when a help popover is available the UI indicates this by underlining the field label. This PR changes the hint to instead make the cursor appear as the system's default "help" cursor, indicating help on the topic available. The underline makes it seem like the text is a link, and clicking on it may navigate me away from the form.
Which TC components are affected by this PR?

[ ] Documentation
[ ] Grove
[ ] Traffic Analytics
[ ] Traffic Monitor
[ ] Traffic Ops
[ ] Traffic Ops ORT
[x] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] Other _________

What is the best way to verify this PR? Please include manual steps or automated tests.
Build and start Traffic Portal and check that the field label text is no longer underlined on hover, but instead transforms the cursor into your system's "help" cursor (usually a question mark of some kind).
Check all that apply

[ ] This PR includes tests
[ ] This PR includes documentation updates
[ ] This PR includes an update to CHANGELOG.md
[ ] This PR includes all required license headers
[ ] This PR includes a database migration (ensure that migration sequence is correct)
[ ] This PR fixes a serious security flaw. Read more: www.apache.org/security

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3215/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3229/
Test PASSed.

Update: now uses a dotted underline to indicate hovering the text will show a popover. This is how most (read: "all of which I'm aware")  user agents handle e.g. <abbr> tags with title attributes.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3231/
Test PASSed.


New Maven build?

Last update was 2015-11-12 lot of useful new features have been pushed since then so time for update?

That's right! Time for an update. I will be preparing a new build in the next days. I will close this.


Quality-of-life improvements for lumen compile

Changelog
Enhancements

Remove -l flags no longer needed in integration tests.  The removed -l flags were added as defaults for the respective targets previously.
Create all parent directories before emitting a file.  This ensures that the --output-dir exists before any file is written to it.
Create all parent directories of --output
Support multiple input paths to lumen compile.
Makes it easier to test using the native_implemented/otp/tests/shared/src files.  No need to symlink into each test's src directory.

I'm not sure what is going on with the Linux runner as there is just no log for it.  It could either be a problem with GitHub Actions or something like a memory or space issue that it can't report properly.  The build works fine locally using the docker image, so merging.


metrics: fix potential conflict on metrics registration

In Cilium v1.13, K8s rest client metrics, such as cilium_k8s_client_api_latency_time_seconds and cilium_k8s_client_api_calls_total, are missing because of a conflict with controller-runtime on the metrics registration.
controller-runtime(sigs.k8s.io/controller-runtime/pkg/metrics) also registers the client-go rest client metrics on its registry using metrics.Register method in its init function. The metrics.Register can be called only once, and subsequent calls will be ignored.
cilium-agent doesn't use controller-runtime, but there's an indirect dependency from github.com/cilium/cilium/daemon to github.com/cilium/cilium/operator/metrics package. (operator uses controller-runtime in its Gateway API implementation) For example,
github.com/cilium/cilium/daemon/cmd
-> github.com/cilium/cilium/pkg/ipam
-> github.com/cilium/cilium/pkg/ipam/metrics
-> github.com/cilium/cilium/operator/metrics
The init function of sigs.k8s.io/controller-runtime/pkg/metrics will be called because of this indirect dependency.
The issue(missing client-go metrics) doesn't happen with v1.14 and later, but it can happen if the order of imports changes again. This commit is to prevent the issue from happning.
This commit is a forward port of　https://github.com/cilium/cilium/pull/26412/commits/e4ff641fb30fa0e711dc9a7e2fcce92dd6d510b6
fixes: #25610
Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Are you a user of Cilium? Please add yourself to the Users doc
[x] Thanks for contributing!

context: https://github.com/cilium/cilium/pull/26412#pullrequestreview-1512518470

/test

/test

ginkgo build cache seems broken
https://github.com/cilium/cilium/actions/runs/5706051069/job/15462054023

/test

/test

@tommyp1ckles Do you have any other feedback or question?

@tommyp1ckles do we need backport labels?

@borkmann 👍 This fixues a bug in 1.13, but this sounds like it may prevent future issues in 1.14 as well.


Fix: Empty States for Common Items and Settings

PR Type:
Enhancement
PR Description:
This PR introduces empty states for the common item catalog and the common item settings. When there are no items in the catalog or settings, a message is displayed to the user.
PR Main Files Walkthrough:
src/components/dialogs/commonItemsDialog.tsx: Imported the NoCommonItems component and used it to display a message when the commonItemsCatalog is empty.
src/components/settings/commonItemsSettings.tsx: Imported the NoManagedCommonItem component and used it to display a message when the commonItemsCatalog is empty.
src/components/utils/commonitems/noCommonItems.tsx: Created a new component, NoCommonItems, which displays a message when there are no common items.
src/components/utils/commonitems/noManagedCommonItems.tsx: Created a new component, NoManagedCommonItem, which displays a message when there are no managed common items.

@CodiumAI-Agent /review

PR Analysis

🎯 Main theme: Adding an empty state for common items in the application.
📝 PR summary: This PR introduces a new component to display an empty state for common items in the application. It also includes some debugging and fixes in the Github workflow file.
📌 Type of PR: Enhancement
🧪 Relevant tests added: No
🔒 Security concerns: Yes. The PR includes code that prints secrets in the Github workflow file. This is a potential security risk as it could expose sensitive information.

PR Feedback

💡 General suggestions: The PR seems to be well-structured and the changes are clear. However, it would be better to separate the debugging and the enhancement into different PRs. Also, it's recommended to avoid printing secrets in the workflow file for security reasons.

 🤖 Code feedback:

relevant file: src/components/utils/commonitems/noCommonItems.tsx
suggestion: Consider adding a button or a link to direct the user to the settings or the page where they can add a new item. This would improve the user experience by providing a quick and easy way to resolve the empty state. [important]
relevant line: No Common Items found, add one in the settings, or quickly add one from an existing item.

relevant file: .github/workflows/pr_agent.yml
suggestion: It's not a good practice to print secrets in the workflow file. Even if it's for debugging purposes, it's a potential security risk. Consider removing these lines. [important]
relevant line: run: echo " ${{ secrets.OPENAI_KEY }} "

How to use

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.

/describe

@CodiumAI-Agent /describe -i

Title
Implementing Empty State for Common Items and Updating PR Agent Permissions

PR Type:
Enhancement

PR Description:
This PR introduces an empty state for the common items catalog and settings, providing a more user-friendly interface when no common items are found. It also updates the permissions for the PR Agent in the GitHub workflows, granting write access to issues, pull-requests, and contents.

PR Main Files Walkthrough:
src/components/utils/commonitems/noCommonItems.tsx: A new component 'NoCommonItems' has been added. This component displays a message when no common items are found, instructing the user to add one in the settings or from an existing item.
.github/workflows/pr_agent.yml: The permissions for the PR Agent job have been updated to include write access to issues, pull-requests, and contents.

@CodiumAI-Agent describe

@CodiumAI-Agent /review_and_review

Title
Implementing Empty States for Common Items and Settings

PR Type:
Enhancement

PR Description:
This PR introduces empty states for the common item catalog and the common item settings. When there are no items in the catalog or settings, a message is displayed to the user. Additionally, permissions have been added to the GitHub PR agent workflow.

PR Main Files Walkthrough:
src/components/dialogs/commonItemsDialog.tsx: Imported the NoCommonItems component and used it to display a message when the commonItemsCatalog is empty.
src/components/settings/commonItemsSettings.tsx: Imported the NoManagedCommonItem component and used it to display a message when the commonItemsCatalog is empty.
src/components/utils/commonitems/noCommonItems.tsx: Created a new component, NoCommonItems, which displays a message when there are no common items.
src/components/utils/commonitems/noManagedCommonItems.tsx: Created a new component, NoManagedCommonItem, which displays a message when there are no managed common items.
.github/workflows/pr_agent.yml: Added permissions for issues, pull-requests, and contents to the PR agent workflow.

@CodiumAI-Agent /reflect_and_review

PR Analysis

🎯 Main theme: Adding empty state UI for common items and settings
📝 PR summary: This PR introduces empty states for the common item catalog and the common item settings. When there are no common items to display, a message is shown to the user. The PR also includes some debugging and permissions adjustments.
📌 Type of PR: Enhancement
🧪 Relevant tests added: No
🔒 Security concerns: No

PR Feedback

💡 General suggestions: The PR is well-structured and the changes are clear. It's good to see that you're considering the user experience when there are no items to display. However, it would be beneficial to add tests to verify the new functionality. Also, ensure that debugging code and secrets are not committed to the repository.

 🤖 Code feedback:

relevant file: src/components/dialogs/commonItemsDialog.tsx
suggestion: Consider extracting the conditional rendering logic into a separate function for better readability and maintainability. [medium]
relevant line: {commonItemsCatalog.length > 0 ? (

relevant file: src/components/settings/commonItemsSettings.tsx
suggestion: Similar to the previous suggestion, consider extracting the conditional rendering logic into a separate function. [medium]
relevant line: {commonItemsCatalog.length > 0 ? commonItemsToRender : }

relevant file: .github/workflows/pr_agent.yml
suggestion: Ensure that the permissions granted are the least required for the operation. Granting write access to issues, pull-requests, and contents might be more than necessary. [important]
relevant line: permissions:

How to use

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.

@CodiumAI-Agent /review -i

Incremental PR Review

⏮ Review for commits since previous PR-Agent review: Starting from commit https://github.com/DMC09/grocer-app-ui/pull/10/commits/06dbe66c576f77055c486da0325f2c88c5576140

PR Analysis

🎯 Main theme: The PR introduces empty states for the common item catalog and the common item settings.
📝 PR summary: This PR adds empty states for the common item catalog and the common item settings. When there are no items in the catalog or settings, a message is displayed to the user. Two new components, NoCommonItems and NoManagedCommonItem, have been created for this purpose.
📌 Type of PR: Enhancement
🧪 Relevant tests added: No
🔒 Security concerns: No

PR Feedback

💡 General suggestions: The PR seems to be well-structured and the changes are in line with the PR description. However, it would be beneficial to add tests to ensure the new components work as expected. Also, the commit messages could be more descriptive about the changes made.

 🤖 Code feedback:

relevant file: .github/workflows/pr_agent.yml
suggestion: It's generally a good practice to limit the permissions of GitHub actions to only what they need to function. Removing these permissions might cause the action to fail if it requires these permissions. Please ensure that the action can run successfully with the reduced permissions. [important]
relevant line: -    permissions:

How to use

Tag me in a comment '@CodiumAI-Agent' and add one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.


Fix HIE errors (add components to hie.yaml)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This is a duplicate of #364. I don’t want to merge this until we have multi component support in ghcide itself.

@cocreature Yes, I just found #364. I'm closing this.


Need new ApplicationTokenProvider API to support authenticate by Subject Name and Issuer of cert

When using Azure DNS client,
var clientCreds = await ApplicationTokenProvider.LoginSilentWithCertificateAsync(domain, new ClientAssertionCertificate(clientId, cert)).ConfigureAwait(false);
var dnsClient = new DnsManagementClient(clientCreds);

To support authenticate by Subject Name and Issuer of cert, we need a new API like:
ApplicationTokenProvider.LoginSilentWithCertificateAsync(string domain, IClientAssertionCertificate certificate, bool sendX5c);
Thereinto, LoginSilentWithCertificateAsync will forward argument sendX5c to AcquireTokenAsync.
AuthenticationContext.AcquireTokenAsync(string resource, IClientAssertionCertificate clientCertificate, bool sendX5c)
For more detail, please ref to https://aadwiki.windows-int.net/index.php?title=Subject_Name_and_Issuer_Authentication_-_Advanced_Administrator_Guidance

We're also blocked by this. Is there an ETA?

Given the age of this issue, the linked guidance for MSAL use, and the new approach to identity in the current generation of libraries, I'm going to close this out.   If there is still a need for this feature with Azure.Identity, please open a new issue for discussion.


[BUG] - The button's event did not bubble up

NextUI Version
2.4.6
Describe the bug
Why didn't the mousedown event bubble up when clicking a button?
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Look at the screenshot.
Expected behavior
Expect the mousedown event to bubble up.
Screenshots or Videos

Operating System Version
macOS
Browser
Chrome

seems the logic from RA's onPress preventing it

closing - see https://github.com/nextui-org/nextui/issues/4059


Proposal to change an existing code

💥 Proposal to change an existing code
C-Plus-Plus/stack/Check_for_balanced_parenthesis.cpp
This program checks the brackets balancing for only the round ( ) parenthesis I want to make some minor changes and  improve this code to give the desired output for:-

square [ ] and curly { } parenthesis too.
[   (   ]  ) This is invalid parenthesis whereas [  (  )  ] this is balanced and valid parenthesis.

Please check if this issue can be assigned to me or not. Thank you!
Have you read the Contributing Guidelines on Pull Requests?
Yes

@Mohim-Singla Awesome that you want to update some existing code. I assigned you. Happy Coding!😊

@ankitaggarwal23 yes, I'm participant of GSSoC 21

Great! @Mohim-Singla Hi, I assigned you. Happy Coding!😊

@ankitaggarwal23  Please review this pull request.


Hover underline colour is dark when on a dark background

What
Where page sections have a dark background, the text colour is white, but the link underline that appears on hover is still dark. Suggest making it the same colour as the text? Ping @j-jaworski
Where
https://wellcomecollection.org/collections

Ping @dana-saur @kasiabbb for decision on this one (very backlog non-urgent). Will add "Needs: design" label.

Done in #11272


search endpoint seems to still run out of memory if the offset is over a certain threshold

Please explain the bug.
Searching over a certain offset throws error 500.
How can I reproduce it?
this works (at the time of reporting)
curl -X 'POST'
'https://api.saebasol.org/api/hitomi/search'
-H 'accept: /'
-H 'Content-Type: application/json'
-d '{
"offset": 7800,
"query": [
"female:loli"
]
}'
but this throws error 500  (at the time of reporting)
curl -X 'POST'
'https://api.saebasol.org/api/hitomi/search'
-H 'accept: /'
-H 'Content-Type: application/json'
-d '{
"offset": 7810,
"query": [
"female:loli"
]
}'
Logs/tracebacks
No response
Heliotrope version or Docker image version
6.3.6 at https://api.saebasol.org/docs

Python Version
No response
OS
No response
Additional Description
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Ok let's use the allowdiskuse option

Related #259


Cannot find the AspNetCore Nuget packages for 3.0 (specifically routing)

While developing a large number of microservices, I would like to standardize the heath check middleware calls into a package for reuse.
But I cannot find a nuget package for this .net standard 2.1 project to use that will allow me access to IEndpointRouteBuilder. (Microsoft.AspNetCore.Routing.dll)
The version i need appears to be embedded in Microsoft.AspNetCore.App but not available by itself as a nuget package (at least not on nuget.org). Other 3.0 assemblies are needed as standalone nuget packages as well.
Is my answer to create and host my own 3.0 nuget package for Microsoft.AspNetCore.Routing?
Any help is appriciated.

@redshiftz the package was removed as part of the 3.0 release. See https://github.com/aspnet/Announcements/issues/325. To reference the feature, you'll need to add a framework reference to Microsoft.AspNetCore.App. Our migration guide - https://docs.microsoft.com/en-us/aspnet/core/migration/22-to-30?view=aspnetcore-3.0&tabs=visual-studio - has details about adding a framework reference as also cross-compiling your library in case you need to support ASP.NET Core 2.x and earlier as well as ASP.NET Core 3.0 in your library.

I tried the migration by adding

to my extension project which is netstandard2.1
It throws the error NETSDK1 "The FrameworkReference 'Microsoft.AspNetCore.App' was not recognized."

@redshiftz you'll need a 3.0 compatible SDK (https://dotnet.microsoft.com/download). In addition, you have to target netcoreapp3.0 or later. Please follow the migration guide I linked earlier.


Update coffeescript package to latest and fix test command

The coffee-script package has been deprecated for a while and moved to coffeescript. This updates to the latest version of coffeescript.
The test script was also broken, but should work now.
QA

[ ] Checkout master and try to run the tests with npm test
[ ] Verify it fails with a message about the --compilers flag being deprecated for mocha
[ ] Checkout this branch
[ ] Run tests and verify they pass

@Zajn I needed to make some small changes to hubot-plusplus, so I cloned this repo and included your PR in it: https://github.com/treaz/hubot-mega-plusplus

@Zajn I needed to make some small changes to hubot-plusplus, so I cloned this repo and included your PR in it: https://github.com/treaz/hubot-mega-plusplus


jquery-pjax and browserify?

I had this working outside of a modular environment, but now inside browserify this just doesn't appear to be making the correct bindings. I'm not sure why - all my code is running inside a domready callback, so the HTML is ready and waiting, and when I do checks on the elements I need to make pjax work, they all return the appropriate dom elements.
Has anyone had any luck getting this working in a modular fashion and/or know of any gotchas that prevent it from working?

What is the actual issue you're having?

It's okay, figured it out in the end. The "document" object wasn't available so wasn't able to bind inside a browserify module. had to bind to "body" as the basis for the setup.


Don't automatically throw when a vector isn't the expected size

Resolves https://github.com/SheetJS/js-xlsx/issues/759

Looks good, but could you change the git commit message (git commit --amend) to say:
Don't throw when vt:vector isn't the expected size

Fixes #759

(keep the first line within 50 characters and reference the issue number within the commit message)

Done :)

Thanks a lot! Aiming for next release tomorrow.


ARROW-6983: [C++] Fix ThreadedTaskGroup lifetime issue

Together with a test.

@bkietz

Travis-Ci: https://travis-ci.org/pitrou/arrow/builds/602350769
AppVeyor: https://ci.appveyor.com/project/pitrou/arrow/builds/28352718

It's quite elegant solution here to creating a race condition on demand, may be useful in the future when such issues present themselves.


Added the solution to Reverse Alternate k nodes in a linked list in Java

Have you read the Contributing Guidelines on Pull Requests?
Yes.
Description
This contains the solution to reverse alternate k nodes in a singly linked list in Java.
Checklist

[✅ ] I've read the contribution guidelines.
[✅ ] I've checked the issue list before deciding what to submit.
[✅ ] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixes #2538

@HarshCasper @bhav09 Kindly review.

@ankitaggarwal23 Due to a death in my family, I was inactive. I can now dedicate the required time to this.
So I request you to kindly re-open this issue as I have my code prepared with the changes requested.

Don't Worry just opened the new

Thanks a lot @ankitaggarwal23 .
I have updated the code with required changes. Kindly review.


Can anyone reproduce this result or is it just me?

Hi, I've been playing around with the loss function code to get a better understanding of the equations and I have encountered results that does not make sense to me.
Assume that two images A and B give similar embeddings. From my understanding, if A and B have different labels, the loss function should penalize more than when they have the same labels.
crit = SupConLoss()
batch_size = 16
embed_dim = 768
features = torch.ones(batch_size, 1, embed_dim) # All embeddings are same and no augmentation
features = nn.functional.normalize(features, dim=2)
Case 1: Same embeddings and same labels
labels = torch.ones(batch_size) # Try when the labels are all same
print(crit(features, labels)/batch_size) # Gives 0.1693
Case 2: Same embeddings and different labels
labels[:(batch_size//2)] = 0 # Now half of them have different labels
print(crit(features, labels)/batch_size) # Also gives 0.1693
I get same loss values for both cases and I was not able to figure out why.
Thanks in advance

Hi, have you figured it out?


Deploy bot to azure always complains "Operation failed. Only one free account is allowed for account type 'LUIS.Authoring'

Version
master
Describe the bug
Go to publish page and click "create azure resource", we got following error:

I create the bot without any recognizer, first time I can deploy to azure successfully.
Then I edit the bot with recognizer and redeploy again, I got above error.
then I remove the resource in azure which created in step1, redeploy can be proceed.

So two things need to check :

If only one luis resource could be created with Authoring key, what is the appropriate behavior if user hit this?
we should not create the luis resource every time in deployment and check if it has been created before as only 1 could be used for free account . @benbrown @zidaneymar

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Give a clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

@cwhitten @yochay, @hibrenda  , do you think we need to do the step2 in R7? To me, this is not a high priority. Because, after clarifying with Luis team, the Authoring Resource limitation is 10, we are not so clear how to select one authoring key from the 10 available Luis Authoring Account, and all those 10 are from different resource group, add a lock is not an elegant approach, user don't even know what is happening, it will bring complexity to the user. I think our current solution step1+step3 should be enough to the user.
We can sync up with Luis team on how to get the Starter_Key which is by default created in the Luis Portal, and it is more natural to use that as the default Authoring key.

Addressed in https://github.com/microsoft/BotFramework-Composer/pull/1423, https://github.com/microsoft/BotFramework-Composer/pull/1449


README: telnet: fix English syntax

Fix two typos and make it clear that e is the returned expecter.
Signed-off-by: Dan Kenigsberg<EMAIL_ADDRESS>

Thx. a lot!


Should installed distributions use canonical or specified path?

Right now, if you create a symlink, and uv pip install the symlink, then uv pip freeze, we list the canonical path (with symlinks resolved). Is this preferred? Or should we use the user-provided path? The latter is more complex as we still need to normalize it.

Perhaps use the canonical path for now, and then in the future the behaviour could be configurable.

Yeah, let's leave it as-is for now. Issue will continue to exist for users to find if it comes up in practice.


Add abbility to override secret name

secret with token should be uniform across clusters
forcing it to have same name as cluster in current
setup is a bit of a hurdle when propagating secrets to cluster
via some other automations. Adding ability to override secret name
Description
Please include the following:

a summary of the change
which issue is fixed (if there is one)
relevant motivation and context

How can this be tested?
Please include some guiding steps on how to test this change during a review.

What environment is necessary for the change to be noticeable ?
What needs to be enabled/applied for the change to be noticeable ?

Checklist

[ ] Unit tests have been updated/added
[ ] PR is labeled accordingly

The release-0.5 branch is the incorrect target.
You can already change the name of the secret by changing the name of the dynakube


Investigate parallelizing upload from file and download to file

This additionally applies to the upload method that is agnostic to stream size.


[sleepy-discord] Auto Complete Slash commands update

Updates the library to add new Discord slash commands features like auto-compete options, and min-max integers.

All features are tested successfully in the following triplet:

x86-windows
x64-windows
x64-windows-static

Thanks for the PR!


Allow external event loop to drive masonry and xilem

These changes allow you to create a masonry or xilem app that is driven by an external event loop.
Masonry
Existing method for creating masonry app:
    masonry::event_loop_runner::run(
        masonry::event_loop_runner::EventLoop::with_user_event(),
        window_attributes,
        root_widget,
        app_driver,
    )
    .unwrap();

Instead you can now do this:
    let masonry_state = MasonryState::new(window_attributes, &event_loop, root_widget);

    let mut app = AppInterface {
        masonry_state,
        app_driver: Box::new(driver),
    };
    event_loop.run_app(&mut app)

Where AppInterface implements the winit ApplicationHandler<accesskit_winit::Event> trait.
Xilem
Existing method:
    let app = Xilem::new(state, app_logic);
    app.run_windowed(EventLoop::with_user_event(), title)?;

Now:
    let xilem = Xilem::new(0, app_logic);
    let (root_widget, app_driver) = xilem.split();
    let parts = xilem.split();
    let (root_widget, app_driver) = (parts.root_widget, parts.driver)

   // and then create masonry app just like above using root_widget and app_driver

Also adds example/external_event_loop.rs which duplicates example/flex.rs but with an external event loop.

Added fix for clippy. xilem.split() now returns struct rather than tuple.

Converting to draft in order to resolve merge conflicts.

Resolved merge conflicts.


clusterDeployer: Update /etc/hosts after the AI cluster is up.

AI doesn't return a valid API VIP until at least one cluster node is up. The safest bet right now is to wait until wait_cluster() returns.  At that point nodes are up.
Fixes: b1d66d3a84e7 ("clusterDeployer: Always update /etc/hosts with the current api_ip.")

CC: @chaudron it would be great if you could test this out too, thanks!

Thanks @dceara you patch seems to solve the problem.

OK, thanks for checking!

I have one observation, and that is that for some reason I see two host.Result objects being dumped to the console. Maybe this is a leftover from some debugging in a previous patch?
...
2023-10-25 14:13:20 INFO: Finished starting VM sno-master without any errors
2023-10-25 14:27:23 INFO: updating /etc/hosts
2023-10-25 14:27:23 INFO: Only running local VMs (virbr0 not connected to externally)
2023-10-25 14:27:23 INFO: waiting for '<IP_ADDRESS>' to respond to ping
2023-10-25 14:27:23 INFO: <IP_ADDRESS> up, connecting with core
<host.Result object at 0x7fda1111cd90>
<host.Result object at 0x7fda1111cb50>
2023-10-25 14:27:23 INFO: Logging in into <IP_ADDRESS> with /root/.ssh/id_ed25519
2023-10-25 14:27:24 INFO: Skipping worker creation.

No idea why those are logged but they're definitely not because of the /etc/hosts update.  Those are hosts.py.Result instances and are CDA internals.  Nothing to do with the python_hosts library.  Maybe @bn222 knows more.

This is from an old debug that was left behind, I'll remove this
https://github.com/bn222/cluster-deployment-automation/blob/main/host.py#L70

@bn222 Do you think there's any other change needed or can this PR be merged?  Thanks!


Search API issue

Do search for projects with ordinary user account whom has no right to the project search result, found error as below.

Fixed by #1630 .


fix(snack-bar): add explicit box-sizing

Fixes the snack bar not being readable in the cases where box-sizing: border-box is applied globally.
Fixes #1412.
Note: this can also be fixed by removing the explicit height, however I wasn't sure whether it wasn't there on purpose (e.g. to prevent line wraps).

Removing explicit height messes up alignment. But honestly, box-sizing: border-box should be explicitly set for all of the components and they should be styled with that in mind. Rather than having different box sizing for each component.

Hopefully this wouldn't be too much of a problem. In Material 1, there's only 2-3 cases total where the box sizing needs to be reset, I don't expect it to be much more for Material 2. This can also be fixed by removing the padding, but then the vertical alignment is a little trickier since it'd have to use line-height which isn't very consistent across browsers.

LGTM


Update Hunt: Showdown

Game Title
Hunt: Showdown
Status of the Anti-Cheat
⭐ Supported
Tinkering Steps
No response
Proof of Mention
No proof

I've bought Hunt, when they enabled linux support and have been playing it on and of since then.
I found it confusing, that it's listed as needs tinkering, because it doesn't. So it should be moved over to supported, even if there is no proof.


[FLINK-6008] collection of BlobServer improvements

This PR is a light-weight version of #3512 that only includes the improvements and can serve as a base for FLIP-19. It improves the following things around the BlobServer/BlobCache:

replace config options in config.md with non-deprecated ones, e.g. high-availability.cluster-id and high-availability.storageDir
do not fail the BlobServer when a delete operation fails
add more unit tests
general code style and docs improvements, like using Preconditions.checkArgument

please note that there are four unrelated test failures:

2x Kafka010ITCase
2x YARNSessionCapacitySchedulerITCase

merging,


Update factorial.rb

added factorial program

@munishyadav08
If you've added the update to the factorial code.
Then remove the previous code.

@munishyadav08
Excellent.
You can follow me and star this repository for further updates.
Have fun  🙌🏼