ob init doesn't fetch from git properly

When running "ob init" on fresh nix install (after following other steps from the readme), ob init produces the following result:
ob init -v
Starting Obelisk </nix/store/ac6gbgq4awr8f4zvj7idapn7hnjsr8vl-obelisk-command-0.1/bin/ob> args=Args {_args_noHandOffPassed = False, _args_verbose = True, _args_command = ObCommand_Init InitSource_Default} noSpinner=False logging-level=Debug
./.obelisk/impl: command not cached, building ...
Creating process: CreateProcess {cmdspec = RawCommand "nix-build" ["./.obelisk/impl","-A","command","--out-link","./.obelisk/impl/.attr-cache/command.out"], cwd = Nothing, env = Nothing, std_in = Inherit, std_out = CreatePipe, std_err = CreatePipe, close_fds = False, create_group = False, delegate_ctlc = False, detach_console = False, create_new_console = False, new_session = False, child_group = Nothing, child_user = Nothing}
building '/nix/store/qrq60v9il0qp8zcqrczrnwicaify2zip-source.drv'...

trying https://github.com/obsidiansystems/obelisk/archive/ca6c8c0cb0ab9720181cc48119e57250cee78b3c.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
error: cannot download source from any mirror
builder for '/nix/store/qrq60v9il0qp8zcqrczrnwicaify2zip-source.drv' failed with exit code 1
error: build of '/nix/store/qrq60v9il0qp8zcqrczrnwicaify2zip-source.drv' failed
RawCommand "nix-build" ["./.obelisk/impl","-A","command","--out-link","./.obelisk/impl/.attr-cache/command.out"] failed with exit code: 1
✖ Running nix-build on ./.obelisk/impl [command]

Apparently, it doesn't see NIX_GITHUB_* env variables. I could workaround that by setting "private": false" in .obelisk/impl/github.json, but not sure whether this is the right thing to do.

That is the right thing to do. This looks like a bug: we need to make it
not be marked as private. @luigy?
On Fri, May 25, 2018, 20:54 Ivan Frolov<EMAIL_ADDRESS>wrote:

When running "ob init" on fresh nix install (after following other steps
from the readme), ob init produces the following result:
ob init -v
Starting Obelisk </nix/store/ac6gbgq4awr8f4zvj7idapn7hnjsr8vl-obelisk-command-0.1/bin/ob> args=Args {_args_noHandOffPassed = False, _args_verbose = True, _args_command = ObCommand_Init InitSource_Default} noSpinner=False logging-level=Debug
./.obelisk/impl: command not cached, building ...
Creating process: CreateProcess {cmdspec = RawCommand "nix-build" ["./.obelisk/impl","-A","command","--out-link","./.obelisk/impl/.attr-cache/command.out"], cwd = Nothing, env = Nothing, std_in = Inherit, std_out = CreatePipe, std_err = CreatePipe, close_fds = False, create_group = False, delegate_ctlc = False, detach_console = False, create_new_console = False, new_session = False, child_group = Nothing, child_user = Nothing}
building '/nix/store/qrq60v9il0qp8zcqrczrnwicaify2zip-source.drv'...
trying https://github.com/obsidiansystems/obelisk/archive/ca6c8c0cb0ab9720181cc48119e57250cee78b3c.tar.gz
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
error: cannot download source from any mirror
builder for '/nix/store/qrq60v9il0qp8zcqrczrnwicaify2zip-source.drv' failed with exit code 1
error: build of '/nix/store/qrq60v9il0qp8zcqrczrnwicaify2zip-source.drv' failed
RawCommand "nix-build" ["./.obelisk/impl","-A","command","--out-link","./.obelisk/impl/.attr-cache/command.out"] failed with exit code: 1
✖ Running nix-build on ./.obelisk/impl [command]
Apparently, it doesn't see NIX_GITHUB_* env variables. I could workaround
that by setting "private": false" in .obelist/impl/github.json, but not
sure whether this is the right thing to do.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/obsidiansystems/obelisk/issues/26, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGlYOpy6S0Qdw3ooIaFu2G0AGe9scB_ks5t2NHhgaJpZM4UOxHo
.

@ryantrinkle hmm that seems like something that should have been taken care of by 5231017a73da7e93e84b83d5142c108c827c489b, but perhaps an older version was in use. It would be helpful to have -v log the commit/version of ob

Yeah, logging the version of ob (both pre and post handoff) sounds good
On Fri, May 25, 2018, 21:14 Luigy Leon<EMAIL_ADDRESS>wrote:

@ryantrinkle https://github.com/ryantrinkle hmm that seems like
something that should have been taken care of by 5231017
https://github.com/obsidiansystems/obelisk/commit/5231017a73da7e93e84b83d5142c108c827c489b,
but perhaps an older version was in use. It would be helpful to have -v
log the commit/version of ob
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/obsidiansystems/obelisk/issues/26#issuecomment-392235119,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGlYBCl-f8KOD1IQPY3KLNq676Wvvxlks5t2NaWgaJpZM4UOxHo
.

After pulling from master and rebuilding ob it's now working fine. Thanks!

Glad to hear it :)
On Fri, May 25, 2018, 23:05 Ivan Frolov<EMAIL_ADDRESS>wrote:

Closed #26 https://github.com/obsidiansystems/obelisk/issues/26.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/obsidiansystems/obelisk/issues/26#event-1647766232,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGlYNwhp2i3EWd8TGuQ4IUUG7UlTIjsks5t2PCjgaJpZM4UOxHo
.


sbt mutation testing

Add un-configured sbt mutationTest task. Adds a quality metric to unit tests by injecting
mutations (bugs) and validating how many are killed.
To test:
$ sbt mutationTest and a report can be found in the target folder.
This is open for discussion more than a well thought out PR. I've seen improved tests from introducing this in the past, and it can make testing fun (think space invaders for tests!). The report says none of the mutations were killed, which I find hard to believe, but then I haven't configured the plugin; it may not be running against the correct source sets (unit/integ). We may also wish to fine tune the mutations we want to introduce, along with adding some exclusions i.e. don't test controllers (assuming the logic has been extracted).
  The 1 line of code change wasn't taxing, so I'm happy if we choose not to progress (with a valid reason ofc ;-) ).

I did some digging an it looks like the plugin is still early development; https://github.com/sugakandrey/scalamu/issues/1
I forgot that I had also used an older version of the plugin as the latest failed, but that could be down to the rubbish wifi in my airbnb. I will try again with the latest and report back

Ok, so the latest version they recommend in the README (0.1.2) doesn't resolve, but I was able to bump 0.1.0 -> 0.1.1. The effect is that 5 mutations get killed now, including the one we discussed today @nigelhp , so that looks a little better.  I guess the question now becomes; is it useful in its current state? It's clearly not massively stable, but may be adding value.
The configuration could still be optimised to exclude generated code.

This is of interest, and I guess ultimately, it cannot really harm to add this to the build.
In its current state however, I'm still not really sure what the output is telling us.  Some of the issues flagged with the new code that I would consider to be the most serious, are issues that I cannot replicate myself.  i.e. if I change the code in the way that the mutation description suggests it has, the tests correctly fail.  It therefore feels as if "buy in" to further manual investigation is going to be required.
Another point to note, and one I have mentioned a couple of times, is that the team has no build monitors / dashboards.  I think this needs to be considered, as I don't see developers consistently running all of the various plugin reports such as checkstyle / mutation testing locally.  And if they are just being run on the build servers, and no one is actually looking at the output, then ultimately we're just fooling ourselves.  Without a simple "trend dashboard" that is blatantly visible to everyone and ultimately encourages someone to jump in and try to pick off some issues, my experience is that the reports will ultimately be ignored.
If we cannot get some build monitors, perhaps we need a "post standup" session on a regular basis, where we use the TV to go through some of the reports.  This is definitely not the preferred approach however...
If we do proceed with this, we should exclude the Play auto-generated code.

Good points, and I agree. I posted a page on Confluence about how to enable pre-commit hooks. I think that would enforce checks before a push - but, it's an opt-in option, developers have to want to enable it.
I think some of the things you raise would be good topics for the retro.
Lets keep this PR open for now and keep rebasing. It will be useful to see if it adds value over time. In the meantime I will tune the config to make it more bearable.


Organization user (not admin) should have the possibility to upgrade when there are not geocoding credits left

STR

Take a user belonging to an organization, not the admin.
Use all your geocoding credits wherever you want, or set your geocoding quota to 0.
Go to a dataset and open the geocoding dialog.
Select the "Street address" tab.
Check that the user has the chance to upgrade his/her account, something that is not possible.

I'd show a something like: "Contact your administrator and ask for more resources".

And remove the stuff related to billing cycle.
cc @josecruz

These texts/behavior was defined when we worked on the new georeference, how should this "upgrade" workflow look then? cc @saleiva

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


matplotlib conflict when importing sif_parser is breaking pyplot.plot

Unbuntu 22.04
Python 3.10.6
Minimal virtual environment
I'm getting this error...
Exception has occurred: UnicodeDecodeError
'utf-8' codec can't decode byte 0x89 in position 0: invalid start byte
This doesn't work....
import sif_parser as sif
import matplotlib.pyplot as plt
plt.plot([1,2,3,4],[1,2,1,2])
plt.show()
This does work...
#import sif_parser as sif
import matplotlib.pyplot as plt
plt.plot([1,2,3,4],[1,2,1,2])
plt.show()
Digging down a little if I comment out line 23 in the 'plugin' module of sif_parser:
#Image.register_open("SIF", SifImageFile)
then this works again

It is wired... I can't reproduce this in my environment.
Colabo also works fine
https://colab.research.google.com/drive/1BoezvuKMFCJJDg-3smFQjDgkmpEp2hff?usp=share_link
Which environment do you use?
Pillow is imported by chance?
We have a problem with Pillow. see #14.

@fujiisoup Could you implement a fix using this method?

I will, but probably this weekend.  Sorry for my late response.

Thanks a lot!


Updated the SDL documentation

Updated the SDL version number in the docs for Visual Studio.
Also, added a bulleted list - on a quick read it was not immediately obvious there are two libraries to get.

I think we should be consistent about the SDL versions we're recommending/automagically installing... WSL/MinGW docs also specify 2.0.10 and the various CI scripts install that.
Auto-install in vs/sdl/sdl2-config.cmake is doing 2.0.12 though... err...

I can update the other references as well and add them to this PR.

Changed every place to be the same version 2.0.14, docs, scripts, everything :)

Thanks for giving the docs a shakeup and trying to get the SDL setup consistent. It's appreciated!
Judging by the test failures on MinGW I think you also need to update -  https://github.com/pimoroni/32blit-beta/blob/master/ci/install_sdl_mingw.sh

I actually did update that file, and now I am trying to figure out the error logs, why it failed here on Github? Strange.

There is something nasty going on with SDL's CMake config in the MinGW build... The library path is very wrong...
Partly caused by this: https://github.com/pimoroni/32blit-beta/blob/master/mingw.toolchain#L4-L5 (library name ends up SDL2). But still wrong without that (libSDL2.dll, should be libSDL2.dll.a)

Okay at least some of it is bugs in SDL's CMake config... (not setting IMPORTED_IMPLIB for Windows, I should probably go open a bug about that...)
Even fixing that and some stuff on the blit side, it still fails because -lmingw32 is getting linked in the wrong place...

I think this needs rebased to see if it builds with the latest fixes?

Looks like SDL has fixed the MinGW problem: https://github.com/libsdl-org/SDL/commit/501fe465977a13e3cb5239e965e949b7e5405582...

Yep, 2.0.16 works: https://github.com/32blit/32blit-sdk/compare/master...Daft-Freak:lenardg/docs/sdl

Replaced by #783 - thank you all!


Support for remote files via plex-mpv-shim or jellyfin-mpv-shim

I get the error "Unable to Scrobble" for media hosted on Plex or Jellyfin, both tv shows and movies:

The script works fine for local files, but more of my media is stored remotely than ever before in places like Plex and Jellyfin servers and I wish I can scrobble files on there to trakt using this script. When I use it with plex-mpv-shim, the log shows:
2021-03-20 12:07:45,182 [   ERROR] mpv: trakt_mpv: Traceback (most recent call last):
2021-03-20 12:07:45,182 [   ERROR] mpv: trakt_mpv: File "/home/aziz/.config/mpv/scripts/trakt-mpv/main.py", line 332, in <module>
2021-03-20 12:07:45,182 [   ERROR] mpv: trakt_mpv: main()
2021-03-20 12:07:45,182 [   ERROR] mpv: trakt_mpv: File "/home/aziz/.config/mpv/scripts/trakt-mpv/main.py", line 326, in main
2021-03-20 12:07:45,182 [   ERROR] mpv: trakt_mpv: switch[sys.argv[1]](sys.argv, data)
2021-03-20 12:07:45,183 [   ERROR] mpv: trakt_mpv: File "/home/aziz/.config/mpv/scripts/trakt-mpv/main.py", line 122, in query
2021-03-20 12:07:45,183 [   ERROR] mpv: trakt_mpv: __query_movie(infos.group(1), infos.group(2), configs)
2021-03-20 12:07:45,183 [   ERROR] mpv: trakt_mpv: File "/home/aziz/.config/mpv/scripts/trakt-mpv/main.py", line 177, in __query_movie
2021-03-20 12:07:45,183 [   ERROR] mpv: trakt_mpv: show_title = res.json()[0]['movie']['title']
2021-03-20 12:07:45,183 [   ERROR] mpv: trakt_mpv: IndexError: list index out of range

Maybe trakt-mpv cannot get the media info because the media is coming via Plex via plex-mpv-shim to mpv instead of being stored on a local disk. However, you can see that mpv knows the media info when its shown at the bottom left of the screenshots, above the progress bar

Uhm I see. I've never used Plex or Jellyfin so I've never experienced that issue.
I'm a bit busy this week so I'm likely not going to be able to fix it this week, but when I get some free time will try to set up a server and replicate the issue.
Thanks for posting it, if anyone else has time to fix it feel free, otherwise I'll try to check it out when I can 🙂

I can invite you to that Plex server where it's already happening for debugging if you want. Share the Plex username  or email address you'd like to use, it can be a temporary account for testing purposes

I changed mp.get_property('filename') on line 75 in trakt-mpv.lua to be mp.get_property('media-title') and now I can scrobble plex/jellyfin hosted files playing in mpv onto trakt.
The problem was that files served from plex/jellyfin give mangled filenames like file.mkv?X-Plex-Token=transient-&X-Plex-Version=2_ (checked info by pressing i key inside mpv) and since the script relies on the filename to do lookups, it would fail

I noticed the title passed to mpv from plex/jellyfin is usually correct, and tried to make use of it for the lookup using media-title. It seems to work okay enough as long as what's passed can be looked up by the script on trakt
I haven't noticed any problems with scrobbling local files with this change yet either


🐛 Quotes card slider alignment issue

Description
Quotes card slider alignment issue
I'm a GSSoC'23 contributor please assign me this issue under gssoc label and level.
Screenshots

Any additional information?
No response
What browser are you seeing the problem on?
Microsoft Edge
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

Go Ahead @biplavmz ☺


Stabilize Beta features

Description
Stabilize Beta features introduced in Kotools Types v3.2.0.
Dependencies

[ ] #59

Checklist

[ ] Implement.
[ ] Test.
[ ] Refactor.
[ ] Update Work in progress section in changelog.

We will release a stable version instead.


Feature/tfsec

fixes #13

I think we should have a tfsec recipe in the makefile so we can run it locally

I think we should have a tfsec recipe in the makefile so we can run it locally

@phillebaba done!


Use multi-stage docker to shrink final image size

Tidy up the Dockerfile and move building the tesla go apps in a stage so go does not have to be installed in final image.
$ docker images
ghcr.io/jesserockz/tesla-http-proxy-docker:multi-stage	d34dc71a8677  3 minutes ago  100MB
ghcr.io/jesserockz/tesla-http-proxy-docker:latest       2ac1f534c956  47 hours ago   613MB

Tidy I didn't you know do that!


Add scenario for IsManagedAccount

Learn Build status updates of commit d9acd7a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

support/sql/admin/error-1069-service-cannot-start.md
:warning:Warning

Details

support/sql/admin/error-1069-service-cannot-start.md

Line 194, Column 64: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/gmsa-troubleshooting#check-the-gmsa-account' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 40, Column 5: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'hr' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 84, Column 5: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'hr' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 194, Column 64: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/gmsa-troubleshooting#check-the-gmsa-account' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit a0f819d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

support/sql/admin/error-1069-service-cannot-start.md
:warning:Warning

Details

support/sql/admin/error-1069-service-cannot-start.md

Line 194, Column 64: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/gmsa-troubleshooting#check-the-gmsa-account' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 194, Column 64: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/gmsa-troubleshooting#check-the-gmsa-account' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit ab6df66:
:warning: Validation status: warnings

File
Status
Preview URL
Details

support/sql/admin/error-1069-service-cannot-start.md
:warning:Warning

Details

support/sql/admin/error-1069-service-cannot-start.md

Line 194, Column 64: [Warning: file-not-found - See documentation] Invalid file link: '../../virtualization/windowscontainers/manage-containers/gmsa-troubleshooting.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 0e75717:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

support/sql/admin/error-1069-service-cannot-start.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

I added some spacing and header lines in the doc as visually it is hard to find what section you are looking for, in my opinion. If this does not follow the template feel free to update and add more universally accepted formatting. However if we can space things out a bit, I think that would be extremely helpful for users.

Lab info
Reproed – changed registry value - HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\MSSQL$SQL19STAND3\ServiceAccountManaged
After restarting OS, observe error below through services.msc
SQL config manager:
System event log error 7038  -
Log Name:      System
Source:        Service Control Manager
Date:          12/9/2022 11:03:08 AM
Event ID:      7038
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      VMREPL1.contoso.lab
Description:
The MSSQL$SQL19STAND3 service was unable to log on as CONTOSO\SQL_GMSA$ with the currently configured password due to the following error:
The user name or password is incorrect.
Command to check registry value: sc qmanagedaccount MSSQL$SQL19STAND3
Running the command qmanagedaccount doesn’t change it as below.
True command that changes; sc managedaccount MSSQL$SQL19STAND3 TRUE

Learn Build status updates of commit 138249c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

support/sql/admin/error-1069-service-cannot-start.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 7f49cb2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

support/sql/admin/error-1069-service-cannot-start.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Unable to use set function

Please avoid using the issue tracker for questions or help. Submitting issues to this repository are usually reserved for bugs, feature requests, or changes to the source code. We have a help channel at https://gitter.im/kreait/firebase-php (you can sign in with your GitHub account). If nobody can answer your question, tag @jeromegamez in your question.
Also see past issues and https://firebase-php.readthedocs.io/en/latest/troubleshooting.html to check if your problem has already been covered.
Please chose a descriptive title for your issue and delete everything before and including this line before submitting the issue.
The problem
Unable to use set during query
Environment

PHP Version (php -v):
PHP 7.0.32 (cli) (built: Sep 17 2018 14:40:36) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
with the ionCube PHP Loader (enabled) + Intrusion Protection from ioncube24.com (unconfigured) v10.0.3, Copyright (c) 2002-2017, by ionCube Ltd.
with Zend OPcache v7.0.32, Copyright (c) 1999-2017, by Zend Technologies

Firebase PHP SDK version (composer show | grep kreait):
kreait/firebase-php                  dev-master bd11f8f Firebase Admin SDK
kreait/firebase-tokens               1.7.1
kreait/gcp-metadata                  1.0.1

Details
Why is set not found???
Full ERROR:
Fatal error: Uncaught Error: Call to undefined method Kreait\Firebase\Database\Snapshot::set() in /home/public_html/authTokenUpdate.php:62 Stack trace: #0 /home/public_html/authTokenUpdate.php(97): FIREBASEauthTokenUpdate->updateToken(Array, 'testemail') #1 {main} thrown in /home/public_html/authTokenUpdate.php on line 62
Code to reproduce issue
	public function updateToken(array $Token, string $Email)
	{
		if (empty($Token) || empty($Email) || !isset($Token)|| !isset($Email)) { return false; }
		if ($this->database->getReference($this->dbname)->getSnapshot()->hasChild($Email))
		{
			foreach ($Token as $key => $value)
			{
				$reference = $this->database->getReference($this->dbname)->getSnapshot()->getChild($Email)->getChild($key);
				$attempt = $reference->set($value);
				$attempt;
			}
			return true;
			//email not in database
		} else { echo "Email not in database"; }
	}

Please remember that with sample code it's easier to reproduce the bug and it's much faster to fix it.

A Snapshot is a read-only snapshot of the reference you are creating it from. If you want to change the value of a child, you have to get a new reference of that child, so for example:
if ($snapshot->hasChild('foo')) {
    $snapshot->getChild('foo')
        ->getReference()
        ->set('new value');
}

PS: Please make the issue description useful in the sense that you don't keep the template in it - if you look at your post, you will certainly agree that it is super hard to read and see the actual information.


Require just used functions & use natives

Hi,
I made this because after a few requests using this module, lodash was causing some memory allocation problems, the full file is very big and it was causing me problems.
I don't quite understand why, but make just these changes, requiring just the used functions and using a few native functions, my application decrease the memory allocation from 500mb to 220mb.

Thanks @luanmuniz !
That is an important finding I would like to understand better so that future versions don't reintroduce this issue. Can you say something about the following questions?

The code pieces you replaced with native functions are only executed once when you require the module. I expect if you revert them to using lodash functions you still won't have the memory issue. Could you try this out?
Apart from the native functions you did (1) require individual lodash functions and (2) update lodash from 3.6.x to ^3.6.0. First of all, which lodash version do you use? Please have a look at /node_modules/request-promise/node_modules/lodash/package.json. This may answer whether (1) or (2) resolved the issue.

Yes. When the native is replaced for the lodash version the memory issues its not there. The problem is in calling the entire module for just a few functions. (Full lodash has almost 500kb)
The 1 is the one that solve the issue. request-promise is using 3.6 right now. I meant to update to 3.10 just to update, not to solve the problem (My mistake pushing just a different call for the same version)
2.1 Update to 3.10 is a good thing because there are a lot of modules using lodash and most of then use the last version and when you have 2 or more versions at the same application (different dependences using different versions) node.js need to cache all the versions instead of just one.

Do you want me to update the PR in any way?

Thanks for the info @luanmuniz ! I can take it from here. You don't need to update the PR.

I just published version 0.4.3 on NPM which contains your changes. Thanks for your contribution!

Thank you very much! :D

Just by curiosity, is there a reason not to use the native Object.keys, Array.forEach and the isUndefined?

I don't know. I leave the expertise on subtle differences between platforms to lodash. ;)


(Request) Player name/attribute substitution

Thank you very much for making this mod! It's critical to my server's setup for so many things! 🙂 But, one addition would make it significantly more powerful for some use cases I've encountered:
There are many commands (notably LuckPerms "user" commands) that require the target player's name to be passed in as an argument. Vanilla selectors like @s have no way to fill this role.
The ability to substitute aspects of the command user into the executed actions would be a huge help.
The only Fabric mod I've found with something like this so far is Player Events, where "custom_commands" can substitute things like "${player.name}" or even "${killedEntity.x}" on a "kill_entity" event. Sadly, this mod is not updated to 1.21 as of this writing and it misses some of the convenient and useful features that your mod provides, most notably permissions restrictions on commands.
So, if you find any time to implement such a thing, I'd be very grateful! 🙂

Maybe it would be possible to make it so one could use placeholders in the commands. This way you could access not only player attributes but also for the server or even other mods.


Support for List's default behaviour (swipe across/Multi row delete)

WIll you implement, or is it possible to implement, the two enhancements to ForEach OnDelete, like swiping across to perform a default (destructive) action, as well as swipe down to delete multiple rows?  Users are used to these actions on lists,  and we just want to make sure it's possible to implement these as well.

Hi, thank you for your feedback.
I just released v1.2.0 (Purrfectized Button, NavigationLink, ... in Swipy view), please update your package. 😇
I didn't understand what you mean; could you explain more? If one of what you mean is swiping harder to perform the rightest-placed action, I'm planning to implement that feature.


Generate PInvoke transitions in the JIT

The JIT needs to generate the following code around PInvoke calls, the existing logic to check for PInvoke calls is in Compiler::impCheckForPInvokeCall should work:
	PInvokeTransitionFrame frame; // opaque local - the size is returned via JIT-EE interface

…
	lea arg0, &frame
	call JIT_PINVOKE_BEGIN // new JIT helper – needs to be added to corinfo.h
	// no managed references can be in registers between BEGIN/END callouts
	<argument setup>
	call target
	<store return value>
	lea arg0, &frame
	call JIT_PINVOKE_END // new JIT helper
…

There is some of this in the RyuJIT already – the difference between the above and what’s there today are:

JIT_PINVOKE_BEGIN callback does not exist, instead the JIT has knowledge of the CoreCLR-specific EE datastructures and conventions involved and inlines the required checks into the code
JIT_PINVOKE_END callback sort of exists (it is called CORINFO_HELP_STOP_FOR_GC), but the hot part of it is again inlined into the code

The sequence proposed above avoids the tight coupling between codegen and runtime at the cost of two calls. If this overhead will prove to be a problem, we will worry about optimizing it later.

@jkotas
// no managed references can be in registers between BEGIN/END callouts

Would it be more precise to say "no managed references may be live only in registers?" I assume that this is due to the GC transition that JIT_PINVOKE_BEGIN will perform.
<argument setup>
call target
<store return value>

Similarly, I assume that argument setup and the return value store don't need to be tightly positioned around the call to the target so long as they respect the condition above.

Would it be more precise to say "no managed references may be live only in registers?"

Yes.

I assume that argument setup and the return value store don't need to be tightly positioned around the call to the target so long as they respect the condition above.

This depends on the calling convention of these JIT helpers. If they are going to have regular calling convention, then the argument setup has to be after the call to the helper. We can explore a custom calling convention if it would be too hard to use the regular calling convention for these in the JIT.

This depends on the calling convention of these JIT helpers. If they are going to have regular calling convention, then the argument setup has to be after the call to the helper.

Ah, right.

We can explore a custom calling convention if it would be too hard to use the regular calling convention for these in the JIT.

Sure. I'm thinking of LLVM in particular (via LLIILC), which currently performs GC transitions immediately before and after the unmanaged call instruction in order to ensure that the preemptive mode invariants are respected.

Work in progress: https://github.com/pgavlin/corert/tree/PInvokeHelpers

This is done.


start kited at startup

Autostart kited at startup of the plugin.

if necessary add a new setting to disable the automatic startup, default to false, i.e. to an automatic start of kited
if setting "start kited at startup" is enabled:

detect if kited is running at startup

if not running: detect if kited is installed

if installed: launch kited

Locating and launching kite:
https://kite.quip.com/rVcJA1bIqZny/Kite-Status-Spec#QcWACAD7xTp

Done in #144.


Allow creating a HttpClient from a Builder

This PR adds a new method HttpClient::from_builder. This allows specifying a Hyper Builder and Connector, which provides for greater control over how a HttpClient makes connections.

👍 thanks!


Vickel: Watch babawalewiseman01(?:@gmail.com)?

Vickel requests the watch of the watch_keyword babawalewiseman01(?:@gmail\.com)?. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

babawalewiseman01(?:@gmail\.com)? has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Nick in Charcoal HQ


Port backend primitives v2

Summary
Port BackendEstimatorV2 and BackendSamplerV2 from Qiskit, since they are needed for local testing mode before Qiskit 1.1 release.
Details and comments
Fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

239 of 243 (98.35%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 82.835%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_runtime/qiskit/primitives/backend_sampler_v2.py
98
99
98.99%

qiskit_ibm_runtime/qiskit/primitives/backend_estimator_v2.py
137
140
97.86%

Totals

Change from base Build<PHONE_NUMBER>:
0.5%

Covered Lines:
6008

Relevant Lines:
7253

💛  - Coveralls


chore: re-export specific things from @envelop/core

after some thought I think we should really only export selective things from @envelop/core instead of exporting everything. This way we avoid any breaking changes downstream envelop impacting us.
closes https://github.com/dotansimha/graphql-yoga/issues/2039

@enisdenjo Everything that is not really needed because it is internal or might cause weird stuff. E.g. useMaskedErrors does not need to be re-exported as we already have it built in.


A second, dead toc in the readme?

Ah, thanks for bringing that to my attention.
The "second toc" is to list all the advanced topics that don't need to be grouped together with the more fundamental stuff.
There are definitely some broken links in there, but not all of them are broken (I removed a bunch of stuff in v0.20). Give them all a test and keep the ones that are still working.
Also thanks for the PR :smile:


Summary for search results shows wrong percentages

E.g. https://caniuse.com/#search=split
This shows 9 results. All have full support in Firefox 70, but the summary claims it has only 50 % support for all these features. According to the summary, support last increased between 60 and 63, but the data don't have such a change.
Chrome 78 has at least partial support for all (full support for 7, one prefixed, one partial), with no difference in version 79, but the summary says 42 %, while version 79 will raise to 50 %.
Current and future Safari has similar support as Chrome (except missing data for ChannelSplitterNode() constructor), but has only 8 % in the summary, which will increase to 25 %.
Data for UC Browser and KaiOS Browser are identical, but the summary has 33 % for UC Browser, and only 17 % for KaiOS.
If I ignore the results from MDN, and toss a coin for String.prototype.split (as it doesn't have a table), the summary matches the data a bit better, but still doesn't make much sense. So, something is broken with the way the percentages in the summary are calculated.

Other example: https://caniuse.com/#search=lazy
There are 2 features, Firefox supports neither, yet in summary has 40 % support. Edge will raise from 0 % to 40 % by dropping support.

Yeah, I feel the summary's currently too broken and confusing to be useful, so have disabled it for now. I'm in the middle of rewriting the front-end code so will make sure it works as expected once that's complete.


OOM for training

Hi, I try to train on my dataset, the running command is python tools/train.py -f exps/default/yolov3.py -d 4 -b 32 --fp16 -c YOLOX_outputs/yolov3_17/latest_ckpt.pth. The first 17 epochs are relatively normal. When running to the 18th epochs, loss begins to grow and report the errors in the following pictures.

I learned from issues that the latest code has fixed this problem. What is the reason for its recurrence？
Looking forward to your reply soon!  Thanks a lot!

same here. No clue why.

I'm facing a similar issue. Currently, I've found that reducing the batch size has prevented the conf loss from blowing up. I'm still not sure why this works.

I comment out the learning rate policy section in config file and this error disappeared.

Does this mean you are using an absolute learning rate now?
I've tried both increasing and decreasing base_lr_per_img but it did not work for me.
However, that seems to have worked in this other issue: #830

Does this mean you are using an absolute learning rate now? I've tried both increasing and decreasing base_lr_per_img but it did not work for me. However, that seems to have worked in this other issue: #830
yes i am using a fix number (0.01) as lr rate.  I also changed to yolox-l, (I was using yolox-x, the biggest version)


fix guice initialize TriggerManager twice bug

This bug was found in local solo server built by July 19th's master code. Our integration test tried to add trigger, which run every minutes. The strange observation is that this trigger never run. We debugged the code and found that the TriggerScannerThread was launched twice, and newly added triggers were put into the should-not-exist thread and never run. I noticed that TriggerManager did not bind to Singleton in Guice Conf. I made this change, and the thread was not launched twice. The bug disappeared.

Thanks for reviewing. Merging.


add multiple "listen" instructions in the configuration file

Hello,
for monitoring correctly our sphinx status, we would need to generate a sphinx configuration, with double "listen" instruction
listen                 = <IP_ADDRESS>:9312
listen                 = <IP_ADDRESS>:9313:mysql41
We can't find how to set-up our thinking_sphinx.yml to do so :/
It seems it isn't possible to add a "listen" instruction.
https://gist.github.com/pat/a7d73376dd657b4457092efc9e9c418a
Is it ?

This issue's been dormant for a while, so I'm going to close it just to keep things tidy - but if there's further questions around this topic, still feel free to comment here, and we can re-open if required :)


Extracting depth information from pixels using D435 realsense_camera

Hello Everyone,
I am using D435 realsense camera, I am able to display the distance from the center of the image, but what I want to know exactlly is how to display the distance or depth information of each pixel on frame ? what's is the principal part of code which do that ? and for note, currently I am analyzing the rs-mesure code ( which has the caracteristic of measuring distance between two fixed pixels ) , but I didn't find the main part that allows me to get depth information from those pixels ?
Thanks for your help

The discussion linked to below may be of use to you.   It contains code references for getting pixel depth with just SDK 2.0, or by using SDK 2.0 in combination with the OpenCV vision software.
https://communities.intel.com/message/546117#546117

Thanks Sir. MartyG-RealSense , It's work fine. : )


Nullish coalescing operator (??) will trigger "nestedTernary"

Describe the bug
Nullish coalescing operator (??) will trigger the detection of rule "rrd ~ nested Ternary"
To Reproduce
Steps to reproduce the behavior:

What is the exact code you are analyzing?

const testFunc = (arr: string[]) => arr ?? []

What is the output you are getting?

-  rrd ~ nested Ternary
   src\views\xxx.vue
   👉 Break the nested ternary into standalone ternaries, if statements, && operators, or a dedicated function. See: https://vue-mess-detector.webmania.cc/rules/rrd/nested-ternary.html
   line #25 has nested ternary 🚨

Expected behavior
Nullish coalescing operator (??) should avoid triggering the nestedTernary detection.
Used version number of vue-mess-detector: 0.57.0
Used version number of node & yarn<EMAIL_ADDRESS><EMAIL_ADDRESS>Additional context
vue-mess-detector.json:
{
  "apply": "vue-essential,vue-recommended,vue-strong,rrd,security",
  "ignore": "multiAttributeElements,ifWithoutCurlyBraces"
}

Thanks for reporting!
Failing test added in last commit for reference 🫡

By the way, using both --apply and --ignore flags should not be used at the same time 👀 https://github.com/rrd108/vue-mess-detector/issues/363
Again, thanks for reporting

This is fixed in last commit https://github.com/rrd108/vue-mess-detector/commit/04eac5405a8f2041d68d0553f2cb7d8e6f6dbb3e
You can try it out via npm i https://pkg.pr.new/rrd108/vue-mess-detector@04eac54


Consider making ChainId part of Tx interface

Shouldn't a Tx know it's own ChainId? Perhaps for some reason not. Otherwise Tx could look like:
type Tx interface {
    ChainId string
    CanonicalBytes() []byte
}

Can we can drop the chainId argument from WriteSignBytes or CanonicalBytes

I think the only argument for not knowing is redundancy. it's redundant extra information added to every tx in the chain. that said, I sympathize with the extra complexity of having to grab it from somewhere magic to validate a signature, but you'll need to do that anyways to validate that it's on the right chain. so in reality the only effect of this is to add useless data to the chain.

actually, maybe there's a use case for knowing what chain a tx should be on just by looking at the tx, rather than checking the CanonicalBytes are for a chain you know about. but maybe you can make a privacy argument against that as well

at the interface level we don't need to affect the wire format.  That said, we can take a shorter hash of the ChainIdHash, and include it in the tx on the wire, especially for situations where multiple chains run on shared nodes.
@ebuchman can you point to where Tendermint adds a "mapping-identifier", assuming the need for this from GnuClear, or please correct me if Im wrong assuming that.

As I think Ben is saying, we don't have to add the ChainId to the serialisation of a transaction, we could just grab the ChainId from somewhere suitable when you need to deserialise or create a new Tx in memory.
I'm not sure about this case, but I often like to follow the principle of including redundant information in a piece of data if it makes it more self-describing when divorced from it's context. Can be convenient when processing from another tool, when debugging, etc.

Doesn't the application have a protocol version in the transaction?
I haven't had any caffeine yet, but people shouldn't be process "loose" transactions outside of blocks unless it's crosstalk between two networks, in which case it seems reasonable to kick the identification into either the block(transaction log) and/or let the application manage it.

Doesn't the application have a protocol version in the transaction?

I don't think so neither in the concrete Tx types or the block header... What would be the bearing of this if it did?

but people shouldn't be process "loose" transactions outside

Perhaps not, my point doesn't really amount to much more than "metadata is good"
Having the ChainId on the Tx interface is convenient whether or not we include on the wire.

I see. I can see value in storing the chainID in the tx struct but not in the serialization for convenience. but no really ;)

Done


tarefa #351

coloquei no index uma barra lateral com 5 ultimas vagas de emprego e proximos 5 eventos

Coverage decreased (-0.02%) to 14.786% when pulling 0fdf232a97ea3b60bad50a7c8751ef7290e3f129 on helioborges:master into a0baf13074674b3c53d77b87d6ab4b5aabd9e50e on gorails:master.

Coverage decreased (-0.02%) to 14.786% when pulling 0fdf232a97ea3b60bad50a7c8751ef7290e3f129 on helioborges:master into a0baf13074674b3c53d77b87d6ab4b5aabd9e50e on gorails:master.

Coverage decreased (-0.02%) to 14.786% when pulling 0fdf232a97ea3b60bad50a7c8751ef7290e3f129 on helioborges:master into a0baf13074674b3c53d77b87d6ab4b5aabd9e50e on gorails:master.


Can't sign into Google Account, unsupported browser

Signing up on services like YouTube will fail with the following message:

The way I got around this is by using Ctrl + Shift + I -> Toggle device toolbar -> Select 'iPhone X' and retry.
Selecting a device from this list also changes the navigator.userAgent, although creating a custom device with a user agent of a supported browser did not work.

I have the same issue and as I understand it should be fixed with v.3.0 coming soon.


Adding Breaking change

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Articles/BreakingChanges.md
:white_check_mark:Succeeded

Articles/connectors/UserToken.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add markdown documentation support for transformer

Codecov Report

Merging #23761 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #23761   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

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 1c23507...425d7cb. Read the comment docs.


Payload extraction design

How does AppScope extract payloads?
What payloads can get get?
What's the overhead?
Options

Closing as part of clean-up at the moment
If needed, will be reopened to track the relevant work


Something went wrong: FancyZones

Microsoft PowerToys version
v0.55.2
Running as admin

[ ] Yes

Area(s) with issue?
General, FancyZones
Steps to reproduce
new log on to the system
PowerToys doesn't load and when I manually start it, I get the error (after the error, everything seems to work again
2022-02-17.txt
)
✔ Expected Behavior
Auto start from logon
Start without error if manually starting
❌ Actual Behavior
Does not auto start
Error when manually starting (works after error though)
Other Software
No response

/dup of #9742
Reinstalling PowerToys should fix the problem.


checking sliderLength change on componentWillReceiveProps

Hey, I am using this component in one of my projects and I had sliderLength calculated dynamically and this component were not updating positions of markers. Hence I made these changes.

Hey! Thanks for the PR. Will take a look at it tomorrow!

This is looking good! Will try it out tomorrow!


Fix links to all Tidy Tuesday repos

I just added tt- prefix to all those repos.

Get the right repo first.


Sorting in describe-variable and describe-funciton does not work

Hey. I think after recent update of emacs packages the LRU sorting in counsel-describe-variable and counsel-describe-function does not work (candidates are sorted alphabetically), while it still does work in counsel-M-x.
Here's relevant parts of my config:
(use-package ivy
  :ensure t
  :custom
  (ivy-use-selectable-prompt t)
  (ivy-on-del-error-function #'ignore)
  (ivy-enable-advanced-buffer-information t)
  (ivy-extra-directories nil)
  (ivy-use-virtual-buffers t)
  :config
  (ivy-mode t))

(use-package counsel
  :ensure t
  :config
  (counsel-mode))

(use-package prescient
  :ensure t
  :custom
  (prescient-sort-length-enable nil)
  (prescient-filter-method '(fuzzy))
  :config (prescient-persist-mode t))

(use-package ivy-prescient
  :ensure t
  :custom
  (ivy-prescient-enable-filtering nil)
  :config
  (ivy-prescient-mode t)
  (setq
   ivy-sort-functions-alist
   '((read-file-name-internal . ivy-sort-file-function-default)
     (internal-complete-buffer . nil)
     (counsel-git-grep-function . nil)
     (Man-goto-section . nil)
     (org-refile . nil)
     (t . ivy-prescient-sort-function))))

Thank you for reporting the problem. I can confirm that all functions based on completing-read are now broken. This is a critical bug. I will investigate soon and fix the problem.

I have pushed an experimental change that should fix this problem and others more permanently. Please let me know if it works, and if the change (which involves a significant change to internal functionality) breaks any important use case for you. cc @manuel-uberti

After update nothing seems to be broken, but the behavior unfortunately remains the same: I have LRU candidate order in counsel-M-x and alphabetical order in both counsel-describe-function and counsel-describe-variable.
Let me know if you need any additional information.

It seems to work fine for me. I can see everything sorted as expected, in all the commands mentioned.

@lockie two questions:

Have you made sure to enable ivy-prescient-mode after loading Counsel, which is now a requirement because of the updates to Counsel that caused this problem?
If yes, what's the value of ivy-sort-functions-alist before and after enabling ivy-prescient-mode?

Yep, here's corresponding lines in my full config: counsel on line 630, ivy-prescient on line 957.
With use-package clause for ivy-prescient being commented, ivy-sort-functions-alist is

((counsel-minor . ivy-string<)
 (counsel-colors-web . ivy-string<)
 (counsel-unicode-char . ivy-string<)
 (counsel-register . ivy-string<)
 (counsel-mark-ring . ivy-string<)
 (counsel-file-register . ivy-string<)
 (counsel-faces . ivy-string<)
 (counsel-describe-face . ivy-string<)
 (counsel-info-lookup-symbol . ivy-string<)
 (counsel-apropos . ivy-string<)
 (counsel-describe-function . ivy-string<)
 (counsel-describe-variable . ivy-string<)
 (read-file-name-internal . ivy-sort-file-function-default)
 (t . ivy-string<))

When uncommented, it becomes
((counsel-minor . ivy-string<)
 (counsel-colors-web . ivy-string<)
 (counsel-unicode-char . ivy-string<)
 (counsel-register . ivy-string<)
 (counsel-mark-ring . ivy-string<)
 (counsel-file-register . ivy-string<)
 (counsel-faces . ivy-string<)
 (counsel-describe-face . ivy-string<)
 (counsel-info-lookup-symbol . ivy-string<)
 (counsel-apropos . ivy-string<)
 (counsel-describe-function . ivy-string<)
 (counsel-describe-variable . ivy-string<)
 (read-file-name-internal . ivy-sort-file-function-default)
 (internal-complete-buffer)
 (counsel-git-grep-function)
 (Man-goto-section)
 (org-refile)
 (t . ivy-prescient-sort-function))

which is kinda weird, because I explicitly set it to a bit different value here.

This strongly suggests you are not actually loading ivy-prescient after counsel, as those modifications to ivy-sort-functions-alist are made when counsel is loaded. I would suggest doing some debugging to verify exactly what features are loaded (featurep) when your different customizations are run, and investigating the :defer/:demand options on use-package.

Oh wow, simply adding :after (counsel) to ivy-prescient's use-package clause fixed the problem. Thanks a lot for your help!


Localisation: Language dropdown menu needs to be anchored to the language change button

The dropdown menu for language select in mobile needs to be anchored to the language change button (i.e. the globe icon).
Issue:
The dropdown menu moves when user scrolls.

During analysis I found out this issue is resolved after implementing the enhancement '#1448 - Add search bar on help board with a search button',

Hey @mathigayathri2001 -- I checked the PR (#1695) that is linked to #1448, but I don't see the fix on the build URL. Could you double check please? Thank you!!

yeah #1448 aka (#1695) doesn't change that, but what it does is adding "Help Board" to that sidebar, and because of that, we moved the language switch icon to the up a bit, but it won't fix this issue for all screen sizes.

This was fixed with #1865 (act as organization) as it changes the entire drawer menu for mobile.


Refactor and update README

Try to clean up further

TODO:

clean up numpy implementation
add C++ code for the same


Explicitly pass the handler

Since the codebase is not returning the next explicitly, when you have an async interface involving this library, the Promise exit early getting the implicit undefined until now returned.

@carpasse can you have a look?

I think what @Kikobeats needs can probably be achieved by creating a wrapper around the responseTime middleware:
function responseTimeWrap(opts) {
  var _responseTime = responseTime(opts);

  return function (req, res, next) {
    return new Promise((resolve, reject) => {
      try {
        _responseTime(req, res, resolve);
      } catch (err) {
        reject(err)
      }
    })
    .catch(next)
    .then(next);
  };
}

We should probably wait until Express next Major v5 supports promises natively before implementing such a change.


[CONTINT-3889] add common container registry config for admission controller

What does this PR do?

This PR adds a config to set a common container registry to be used by admission controller webhooks.
Motivation

The APM, CWS, and agent-sidecar webhooks in the admission controller have a “container_registry” option. It defaults to “gcr.io/datadoghq” in all cases:

admission_controller.auto_instrumentation.container_registry
admission_controller.cws_instrumentation.container_registry
admission_controller.agent_sidecar.container_registry

The goal is to define an option that applies to all of them (i.e. admission_controller.container_registry) so it doesn’t need to be specified 3 times.
Additional Notes

We don't remove the existing webhook-specific container registry config options in order to preserve backward compatibility.
If a webhook wants to use a distinct container registry, it can define it is own config and use it instead of using the common container registry.

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Ensure that the following webhooks are still working even when registry is not set for each one of them:

agent sidecar
SSI
CWS instrumentation

/merge

/merge


Add ability to set the shell

What problem are you trying to solve?
In the init_hook I would like to source some scripts containing helper utilities that are written in bash.  In devbox run the shell is sh whereas devbox shell the shell is inherited from the caller's shell.
This behavior was confirmed in discord:
We designed it this way initially to make run calls more portable  and consistent. The thinking was that devbox run (especially if used in CI) would use a consistent shell and not be affected by a users specific settings, while devbox shell would use the users shell

which make sense, but if I wanted a consistent shell environment across both devbox shell and devbox run it would be nice to have a way to set that.
More discussion:

https://discord.com/channels/903306922852245526/1234953700217323541
https://discord.com/channels/903306922852245526/1251154511746039828

What solution would you like?
Ideally, the solution would be to have support for overriding the default shell for devbox shell and devbox run.  For (a contrived) example:
{
  "$schema":  "https://raw.githubusercontent.com/jetify-com/devbox/0.11.0/.schema/devbox.schema.json",
  "packages": ["bash@latest"],
  "shell": {
    "exec": {
      "shell": "/bin/bash --rcfile something.bash",
      "run": "BASH_ENV=something.bash /bin/bash -c"
    },
    "init_hook": [
      "ps -p $$",
      "source .bootstrap.sh"
    ],
    ...

Splitting out .shell.exec.shell and .shell.exec.run allows for flexibility, but if even without the split my use case is satisfied
Allowing arguments (not just a shell path) allows for flags to be passed and env vars to be set if necessary
I understand that this makes for a bit of a mess with inheriting the existing shell.  Overriding the shell with this may assume that the --pure flag is automatically set

Alternatives you've considered

Set the SHELL in the devbox.json env (no effect)
chsh in the init_hook (requires password or mucking with global filesystem)
eval bash, bash -l, and other means to starting the desired shell (creates a subshell which doesnt run the devbox run scripts)
rewriting all our helpers in sh (if I declare bash as a package, I should be able to use it in scripts)
Prefixing all script lines with bash to force the shell (verbose and problematic with the creation of subshells)

I think this is a really good suggestion, and it would help with some shell incompatibility bugs we've seen in the past.
I think I would tweak the proposal to allow the user to specify a shell package they want to install and use as well. For example (not final):
  "shell": {
    "package"<EMAIL_ADDRESS>    "exec": {
      "shell": "bash --rcfile something.bash",
      "run": "BASH_ENV=something.bash bash -c"
    },

Would install Bash 5.1 from nixpkgs and then run shell/commands/services in that shell. This way you could write zsh/bash/fish specific scripts, and have it work across systems regardless of the user's host shell.

It is counter-intuitive to devbox that the host shell is taken, given that the we expect an  isolated, reproducible development environments that runs anywhere
Bash is installed by devbox and is used when running --pure. It would be logical to use this as the default shell for all cases.
An override for the default shell would be optional.
  "shell": {
    "package"<EMAIL_ADDRESS>    "cmd": "bin/zsh -c"
 }

Allowing for separate shells for shell, init and scripts can become pretty confusing.

Allowing for separate shells for shell, init_hooks and run can become pretty confusing.

I agree, but from what I understand shell and run execute with different interactive/login settings which may require different cmd options.  For example, --rcfile vs BASH_ENV.  I could be wrong.

@scottTomaszewski After diving a litter deeper,  I suspect that the need for different configurations for run and shell
commands is the init_hook commands. These commands need to be sourced in for both the shell and run commands.
Should you be able to reference the init_hook command script in the exec specification?
  "shell": {
    "package"<EMAIL_ADDRESS>    "exec": {
      "shell": "bash --rcfile ${init_hook_commands}",
      "run": "BASH_ENV=${init_hook_commands} bash -c"
    },

I've wasted a lot of time trying to figure out why some things worked if I ran from a devbox shell but did not when using devbox run :(
Initially, I expected a completely isolated system (even with different $HOME dir), when I noticed it wasn't, the expectation was that things where running in my shell (zsh).
I tailored all the scripts to zsh, but found out that scripts run on sh and --pure shells run on bash. This has been  very frustrating journey so far.
Would it really break everything to have a setting on devbox.json that specifies the shell to be used for everything?


[beta] Consider adding additional test case for "Basic Algorithm Scripting: Finders Keepers"

Challenge finders-keepers has an issue.
function findElement(arr, func) {
  return arr.find(func);
}

findElement([1, 2, 3, 4], function(num){ return num % 2 === 0; });

Thanks to ES6, this algorithm is completely solved by the built in Array.prototype.find() method.
Maybe we should add a test case that ensures campers don't use this, but rather write their own code?

I'm on it..


Fix typo for failing task

@bkrannich there are a few references to that text in the repo (searched for "to succeed but state").

@cppforlife: Yes, sorry about that. Fixed the corresponding test with fa06f0e. The other search hits have a different context/don't contain the typo.


Upgrade jquery-rails 4.3.1

Coverage remained the same at 100.0% when pulling c55545a9a4fc8a72d26d546dc9a5a9ec118dc3b6 on upgrade/jquery-rails-4.3.1 into a053477718d2ded8942c0e1b70b2f34deca236e9 on master.


change val size

Hello, may I ask if it is possible to train the 7B model with DPO-16k data using 8-card A6000 (48GiB),


[GOBBLIN-1515]Fix hive schema not updated issue in streaming and GMIP

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1515

Description

[ ] Here are some details about my PR, including screenshots (if applicable):
There are two issues need to be fixed:

Fix the issue that Hive schema is using avro schema even for orc table: Now, since we directly use avro schema literal to calculate the column and column types for orc table, it sometimes is not correct, so we need to change avro schema to orc schema and compute column types accordingly

Change the behavior that we only evolve avro schema literal but not the hive schema when schema evolution happen: In Streaming, when we do hive registration, we compare the current schema with schema registry and when there is schema evolution, we only update avro schema literal and leave hive schema to be lag.

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@autumnust can you help take a look when you have time? Thanks!

Codecov Report

Merging #3364 (748f78b) into master (48af4c6) will decrease coverage by 3.62%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #3364      +/-   ##
============================================
- Coverage     46.54%   42.92%   -3.63%
+ Complexity    10136     1944    -8192
============================================
  Files          2051      395    -1656
  Lines         79547    16950   -62597
  Branches       8880     2089    -6791
============================================
- Hits          37027     7275   -29752
+ Misses        39091     8871   -30220
+ Partials       3429      804    -2625

Impacted Files
Coverage Δ

...org/apache/gobblin/iceberg/GobblinMCEProducer.java
48.71% <0.00%> (-1.29%)
:arrow_down:

...pache/gobblin/util/orc/AvroOrcSchemaConverter.java
0.00% <0.00%> (ø)

...a/org/apache/gobblin/util/limiter/NoopLimiter.java
40.00% <0.00%> (-20.00%)
:arrow_down:

...g/apache/gobblin/util/filters/RegexPathFilter.java
72.72% <0.00%> (-16.17%)
:arrow_down:

...lin/util/filesystem/FileSystemInstrumentation.java
92.85% <0.00%> (-7.15%)
:arrow_down:

...ore/util/DatabaseJobHistoryStoreSchemaManager.java
29.31% <0.00%> (-2.36%)
:arrow_down:

...in/java/org/apache/gobblin/cluster/SingleTask.java
76.62% <0.00%> (-2.05%)
:arrow_down:

...che/gobblin/metastore/DatabaseJobHistoryStore.java
77.77% <0.00%> (-0.49%)
:arrow_down:

.../gobblin/cluster/HelixRetriggeringJobCallable.java
60.13% <0.00%> (-0.40%)
:arrow_down:

...main/java/org/apache/gobblin/util/ConfigUtils.java
58.59% <0.00%> (-0.27%)
:arrow_down:

... and 1663 more

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 48af4c6...748f78b. Read the comment docs.

Thanks for addressing my comments. LGTM.


When will release 0.3 be officially released?

When will the release 0.3 be officially released?

Thanks for your attentions, plz refer to https://github.com/kubernetes-sigs/kueue/issues/360,  we're waiting for the v1beta1 at the moment. And if you're interest with the progress we made in v0.3.0, come to our community meeting today, we'll share something about this. See: https://docs.google.com/document/d/1XOeUN-K0aKmJJNq7H07r74n-mGgSFyiEDQ3ecwsGhec/edit#heading=h.ukbaidczvy3r


U1024 instance with values generated with noir-bignum-paramgen tool.

Description
Added parameter values for U1024 Instance, generated with the noir-bignum-paramgen tool.
Problem*
Resolves https://github.com/noir-lang/noir-bignum/issues/6
Summary*
Additional Context
PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I've run the paramgen tool myself to check and got the same constants.


Debug remote chaincode-as-a-service using a reverse proxy to localhost

Identify and document a technique for running chaincode on a remote "cloud," but connected to a process running in a local debugger.
The general idea here is to run a reverse proxy to tunnel gRPC traffic "from" a peer "to" a chaincode endpoint running locally in a debugger.  When the peer connects to chaincode, the connection will be relayed back to a port opened on the user's local workstation.

It is worth testing this pattern directly with ngrok.com as well as looking into deploying a proxy, router, and ingress/port-forward.

For reference - there is https://github.com/hyperledgendary/fabric-contract-debug-scenario
It's a draft and needs reorganizing to make it easier to read.


Actions

@TimGuiteDiamond another minor refactor.

Can we merge this? Doesn't seem like a drastic change and I think the more explicit Actions, along with separation between redux actions and "other" actions is a good thing :+1:


Add modified_on to order search response

Codecov Report

Merging #442 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #442   +/-   ##
========================================
  Coverage    95.91%   95.91%
========================================
  Files           94       94
  Lines         3084     3084
  Branches       272      272
========================================
  Hits          2958     2958
  Misses          86       86
  Partials        40       40

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 e77eba7...e24735f. Read the comment docs.


Tap action on hero card not working in web chat

Hi, I am trying to display 4 Hero Cards (Rich cards) in a plain web chat channel. I am using the classic version of the default Web Chat control with the "Preview" option enabled. I wish to have only images to my cards and clicking on the images should return me specific values.  I have added tap action to the Hero cards as given below.
CardAction plButton = new CardAction()
{
Value = dSubOption.text,
Type = "imBack",
//Type = "postBack",
Title = dSubOption.text
};
HeroCard plCard = new HeroCard()
{
Title = "",
Subtitle = "",
Images = cardImages1,
Tap = plButton
};
However I see that the Tap action on the hero card does not respond to tap. Any help is much appreciated!
Note - I am using the C# SDK, Microsoft bot builder version - 3.5.2

Works in the current build, will be deployed to channel soon, or use the current build directly via CDN or building yourself.


Docs: Document caveats with Knative split and visibility issues

Currently, the controller works with some APIs of Knative but not all.
Traffic splits are not handled at all and visibility fields are ignored. These should be explicitly documented and communicate to the users.

@hbagdi could you please clarify what "some APIs of Knative but not all" means here?

@hbagdi could you please clarify what "some APIs of Knative but not all" means here?

That's misleading description on my part. What I mean is that traffic split and visibility configuration is currently ignored by our controller and we need to explicitly document that.
We do want to add these features but they are blocked until Kong itself implements those.

That's misleading description on my part. What I mean is that traffic split and visibility configuration is currently ignored by our controller and we need to explicitly document that.
We do want to add these features but they are blocked until Kong itself implements those.

Closing as stale. We haven't seen strong interest or usage of our Knative integrations so it's not clear to us how to prioritize this at the moment: if you're reading this and have a strong need and use case please feel free to comment here and we would be happy to re-open this and re-assess.


Upgrade to pop v6

Summary
The two major API changes are to the migrator interface and how errors
are returned.
This affects

cmd/milmove/migrate.go
pkg/handlers/errors.go
pkg/migrate/Builder_test.go

I can't seem to find any detailed release notes for v6 other than https://github.com/gobuffalo/pop/releases/tag/v6.0.0
Setup to Run Your Code
make server_test

Verification Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.

Verification Steps for Reviewers
Backend

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 40313285f534c6f6de5649c73e8f8ddc41fd2f6a

This LGTM -- thanks for handling the upgrade and the fixes for the API changes! 🥇
A few small things:

I was wondering if we could go ahead and upgrade to the latest 6.0.2 version while we're at it.
In .golangci.yml, there are some gomodguard entries that talk about pop/v5 that should probably be updated.
In testdata/src/github.com/gobuffalo/pop/v6/main.go, I saw the path changed from v5 to v6, but should we change the package there from v5 to v6 as well?  I'm not familiar with this part of the code, so I'm not sure if that package name actually matters (even if it doesn't, though, we should probably sync it or use a non-versioned package name).

This LGTM -- thanks for handling the upgrade and the fixes for the API changes! 🥇
A few small things:

I was wondering if we could go ahead and upgrade to the latest 6.0.2 version while we're at it.

Yeah! I forgot to go get the latest, but I've done so now

In .golangci.yml, there are some gomodguard entries that talk about pop/v5 that should probably be updated.

Done!

In testdata/src/github.com/gobuffalo/pop/v6/main.go, I saw the path changed from v5 to v6, but should we change the package there from v5 to v6 as well?  I'm not familiar with this part of the code, so I'm not sure if that package name actually matters (even if it doesn't, though, we should probably sync it or use a non-versioned package name).

Thank you! Fixed

I deployed this to experimental and AFAICT, all seems well


Select All Checkbox

Hi @nazerulgit
It is released with version 3.9.0, thank you for your contribution!


[Layout] Layout.c is out of date

There have been bug fixes to https://github.com/facebook/react-native/blob/master/React/Layout/Layout.c since it was last updated.
For instance https://github.com/facebook/css-layout/commit/fca176109d84a7b583bc091f91109d8c359ac1fc which addresses custom measurement for  container views. The instructions for updating indicate ./import.sh which does not exist in the react-native.

@vjeux Do we want to update css-layout?

We absolutely do. There were a couple of things that broke when we updated last so need to be careful and fix them

The css-layout repo is over three months ahead of the version here and contains mostly bugfixes and new features i.e. good stuff that's ~mostly backwards-compatible.
@vjeux can a bootcamper or new team member help update css-layout and start to shape a process around keeping it up-to-date?

pingcat. can this go on the roadmap for 0.12 or 0.13?

I saw that the latest Android sync includes a new version of css-layout. Is Android using the latest css-layout, or does it match iOS's implementation? The layout engines can't diverge too much across platforms and we need a plan for keeping them in sync and up-to-date.
cc @vjeux @mkonicek

The ios diff is also in the queue. Had issue landing it because of internal unrelated breakages but it's coming

Fantastic, that's great to hear.

Closing this since css-layout was synced awhile back.


The list of teachers in the cohorts should not include developers

https://github.com/zeeguu-ecosystem/zeeguu-api/blob/7915b3e282bd96800f7355033153cce4125a3d13/zeeguu_api/api/teacher_dashboard/cohorts.py#L178
The list of teachers in each cohort returned by this endpoint includes developers. As we are shoving the teachers on the list to the teachers, developers should not be on it.

@mircealungu
It is really useful as a developer to be able to see the UI with "real" data, so removing us from the real classes is a perfect quick-fix but it is only partly a solution. ;)

I fixed it beyond your expectations even :)
now devs don't show up in any real classes;
problem is that we don't show up in our own created classes;
I can add us back manually, but let me know to which classes and whom should I add!


Workflow

Signed-off-by: Vijayan Balasubramanian<EMAIL_ADDRESS>Description
Add DOC workflow to test whether commit is signed or not.
Update snapshot to use right version.
Issues Resolved
#107
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@b5c6940). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #1   +/-   ##
=======================================
  Coverage        ?   82.48%
  Complexity      ?      474
=======================================
  Files           ?       69
  Lines           ?     1821
  Branches        ?      178
=======================================
  Hits            ?     1502
  Misses          ?      257
  Partials        ?       62

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 b5c6940...f53883c. Read the comment docs.


Run all tests

FEATURE REQUEST
Inspiration
Multi-label and mulit-tracer work is complete, all tests should be run.
Description
Update GitHub action to run all tests. Remove unused tags from testing code (optional)
Alternatives
Dependencies
Comment

ISSUE OWNER SECTION
Assumptions

List of assumptions that the code will not explicitly address/check
E.g. We will assume input is correct (explaining why there is no validation)

Requirements

[ ] 1. List of numbered conditions to be met for the feature
[ ] 2. E.g. Every column/row must display a value, i.e. cannot be empty
[ ] 3. Numbers for reference & checkboxes for progress tracking

Limitations

A list of things this work will specifically not do
E.g. This feature will only handle the most frequent use case X

Affected Components
A tentative list of anticipated repository items that will be changed, labeled
with "add", "delete", or "change".  One item per line.  (Mostly, this will be a
list of files.)

change: File path or DB table ...
add: Environment variable or server setting
delete: External executable or cron job

DESIGN
Interface Change description
Describe changes to usage. E.g. GUI/command-line changes
Code Change Description
Describe code changes planned for the feature. (Pseudocode encouraged)
Tests

[ ] 1. A description of at least one test for each requirement above.
[ ] 2. E.g. Test for req 2 that there's an exception when display value is ''
[ ] 3. Numbers for reference & checkboxes for progress tracking

I haven't yet looked at Fan's latest updates.  Did she fix the remaining broken tests?

I haven't yet looked at Fan's latest updates. Did she fix the remaining broken tests?

I'm not sure, but this can certainly wait until after the soft launch for the lab members.

Yes, this is a required priority for the Production Release, which is scheduled for early Nov.

Oh OK.  I could have sworn it was in the soft-launch milestone. Sorry about that.


bug: Upstream Quickstart CFT Inaccessible

It appears the CFT used to stamp out the NR stackset is (similarly to the rest of the experience so far) not usable either since it's inaccessible.
create: failed to create CloudFormation stack, rollback requested (ROLLBACK_COMPLETE): ["The following resource(s) failed to create: [NewRelicControlTowerEvents, NewRelicFirstLaunch]. Rollback requested by user." "Resource creation cancelled" "Received response status [FAILED] from custom resource. Message returned: An error occurred (ValidationError) when calling the CreateStackSet operation: Object referenced by https://aws-quickstart.s3.amazonaws.com/quickstart-ct-newrelic-one/templates/newrelic-stack-set.yml is not accessible.

A potential workaround has been identified which is to create the StackSet manually using the URL mentioned in the error message. The name of the StackSet with the manual deploy must be the same as the value as the StackSetName parameter name. This stack set has a few other parameters which do not have defaults which their values can be pulled from the quickstart.


odo list --path does not list devfile components in Experimental mode

/kind bug

What versions of software are you using?
Operating System:
Windows 10
Output of odo version:
1.2.0
How did you run odo exactly?
I created maven component using
odo create maven --context ~/component/dir
Actual behavior
odo list --path ~/component returns empty list
Expected behavior
odo list --path ~/component returns list with one devfile component
Any logs, error output, etc?
N/A

duplicate of https://github.com/openshift/odo/issues/2835

@dgolovin work is being done on this.

@girishramnani thanks, that would let to try it in vscode.


Appstudio update test-simple-build-ylok

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-simple-build-ylok-on-pull-request has failed.

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
17 seconds
clone-repository

🏃 Running
---
build-container


Big-ish emote handling refactor

Don't merge yet, bingo is still missing + i need to test some more changes
TODO

[x] Potentially make Emote and EmoteInstance classes
[x] Test emotes on screen module
[x] Test showemote module
[x] Test CLR behaviour of:

[x] 1x-only emote (-> TriEasy)
[x] 2x-only emote (-> Hahaa)
[x] 3x-only emotes

[ ] Test emote quest module
[x] Add unit test for fill_in_url_scheme
[x] Add unit test for iterate_split_with_index
[x] Test that regular refresh (every 1 hour) works correctly
[x] Reimplement bingo
[x] Should etmrecord/epmrecord be re-added? There was only a getter, not a setter for it

Caveats so far: $(tb:etmrecord) is gone for now, can be readded if needed

etmrecord was never implemented, so removing it is fair

It's possible to do etmrecord, I saw some redis eval functions (lua code you run in redis) that's basically ZADD but only if the new value is greater.

probably worth exploring, possibly as a separate PR?
if you feel like it's something you might get to, you could probably just leave the etmrecord replacements in

Good commands to run after this update:
!add command epmrecord @$(source:username_raw), $(1) per minute record is $(epmrecord;1).
!edit command epm @$(source:username_raw), $(1) is currently being used $(epm;1) times per minute.


Example of building a docker image and pushing to a registry

Expanding on #4, it would be good to have an example of how you set up an agent pod to build docker images, and push them to some registry. This is generally more a function of how you want to perform this task in kubernetes as opposed to anything too Jenkins specific, but it's a common use-case.

@alathon

@alathon


feat: support backfill_rate_limit for source backfill

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
fix #19297
This is a missing feature. We support source_rate_limit for shared source executor, but cannot rate limit source backfill before this PR.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#19445  👈 (View in Graphite)
#19443
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

https://github.com/risingwavelabs/risingwave-docs-new/pull/62

Merge activity

Nov 20, 3:57 PM GMT+8: A user started a stack merge that includes this pull request via Graphite.


added sessiontype property for dsc config

This change is

 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.:x: sthayduk sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I've added the option to add the session type to the dsc config. For some scenarios it is required to be different than the hardcoded RestrictedRemoteServer SessionType


Fix: account form reactive according to gmail or retailer

Issues Addressed
Closes #204
Additional Information
Added a verification for the type account to manipulate the form and the select to Gmail or Retailer

Just saw the stories comments after the PR


[bugfix] Force rsync for shared folders

What
To prevent it prompting to use SMB with Vagrant 2.0.2 on High Sierra:
 dcarley@Dans-Air  ~/p/p/paas-bootstrap   master  make dev deployer-concourse bootstrap
vagrant/deploy.sh
Bringing machine 'default' up with 'aws' provider...
==> default: Preparing SMB shared folders...
default: You will be asked for the username and password to use for the SMB
default: folders shortly. Please use the proper username/password of your
default: account.
default:
default: Username:

Since we're restricting it to rsync only, which is functional on Mac and
Linux, we no longer need to tell it not to use NFS.
How to review
Check that make dev deployer-concourse bootstrap still produces you a working Bootstrap Concourse.
Who can review
Anyone. Though it might be good for someone on Linux and someone on a version of Mac older than High Sierra to test this.

I tried this on an older version of macOS and it worked fine.

@camelpunch @keymon could one of you test on Linux?

So my initial go produced this:
$ ruby -v
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-linux]

$ make dev deployer-concourse bootstrap
vagrant/deploy.sh
Bringing machine 'default' up with 'aws' provider...
==> default: Warning! The AWS provider doesn't support any of the Vagrant
==> default: high-level network configurations (`config.vm.network`). They
==> default: will be silently ignored.
==> default: Warning! You're launching this instance into a VPC without an
==> default: elastic IP. Please verify you're properly connected to a VPN so
==> default: you can access this machine, otherwise Vagrant will not be able
==> default: to SSH into it.
==> default: Launching an instance with the following settings...
==> default:  -- Type: m4.large
==> default:  -- AMI: ami-98ecb7fe
==> default:  -- Region: eu-west-1
==> default:  -- Keypair: andrew-vagrant-bootstrap-concourse
==> default:  -- Subnet ID: subnet-56a69a33
==> default:  -- IAM Instance Profile Name: concourse-lite
==> default:  -- Security Groups: ["sg-63323c05"]
==> default:  -- Block Device Mapping: [{"DeviceName"=>"/dev/sda1", "Ebs.VolumeSize"=>50}]
==> default:  -- Terminate On Shutdown: false
==> default:  -- Monitoring: false
==> default:  -- EBS optimized: false
==> default:  -- Source Destination check:
==> default:  -- Assigning a public IP address in a VPC: true
==> default:  -- VPC tenancy specification: default
/home/andrew/.vagrant.d/gems/2.3.4/gems/nokogiri-1.8.1/lib/nokogiri/xml/sax/push_parser.rb:47:in `native_write': 6577:29: FATAL: Couldn't find end of Start Tag ipRange (Nokogiri::XML::SyntaxError) (Excon::Error::Socket)
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/nokogiri-1.8.1/lib/nokogiri/xml/sax/push_parser.rb:47:in `write'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/fog-xml-0.1.3/lib/fog/xml/sax_parser_connection.rb:31:in `block in request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/response.rb:119:in `parse'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/middlewares/response_parser.rb:7:in `response_call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/connection.rb:389:in `response'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/connection.rb:253:in `request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/middlewares/idempotent.rb:30:in `error_call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/middlewares/base.rb:11:in `error_call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/middlewares/base.rb:11:in `error_call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/connection.rb:273:in `rescue in request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/connection.rb:216:in `request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/middlewares/idempotent.rb:30:in `error_call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/middlewares/base.rb:11:in `error_call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/middlewares/base.rb:11:in `error_call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/connection.rb:273:in `rescue in request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/connection.rb:216:in `request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/middlewares/idempotent.rb:30:in `error_call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/middlewares/base.rb:11:in `error_call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/middlewares/base.rb:11:in `error_call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/connection.rb:273:in `rescue in request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/excon-0.59.0/lib/excon/connection.rb:216:in `request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/fog-xml-0.1.3/lib/fog/xml/sax_parser_connection.rb:35:in `request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/fog-xml-0.1.3/lib/fog/xml/connection.rb:7:in `request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/fog-aws-1.4.1/lib/fog/aws/compute.rb:547:in `_request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/fog-aws-1.4.1/lib/fog/aws/compute.rb:538:in `request'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/fog-aws-1.4.1/lib/fog/aws/requests/compute/describe_security_groups.rb:38:in `describe_security_groups'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/fog-aws-1.4.1/lib/fog/aws/models/compute/security_groups.rb:63:in `all'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:229:in `block in allows_ssh_port?'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:228:in `map'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:228:in `allows_ssh_port?'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:106:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/elb_register_instance.rb:16:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/warn_networks.rb:14:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/builtin/provision.rb:80:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/builtin/call.rb:53:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /home/andrew/.vagrant.d/gems/2.3.4/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/connect_aws.rb:43:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/builtin/box_check_outdated.rb:36:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/machine.rb:227:in `action_raw'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/machine.rb:202:in `block in action'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/environment.rb:631:in `lock'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/machine.rb:188:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/machine.rb:188:in `action'
	from /opt/vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
Makefile:151: recipe for target 'bootstrap' failed
make: *** [bootstrap] Error 1

I'll start fiddling around.

It worked fine for me.

Worked fine second time around. Ship it.


Add fastlane metadata for F-Droid

Addresses #1397

This seems great, I'm just going to move it into the clients/android/fastlane directory

move it into the clients/android/fastlane directory

But as per the F-Droid doc, it has to be in root directory.
@linsui Request to check if its okay to use clients/android/fastlane directory for F-Droid.

It must be in the root directory currently.

@samuelclay v13.0.0 available on F-Droid but still we're missing metadata because they're in the wrong place 😔


fix issue on paste table with th elements in first row

Hi!
When I paste copied table i get nothing. But expected result is data table.
Example of table:
`

1

2

3

a

s

d

`

Thanks


Header

[ ] Allianz logo with link
[ ] top level menu
[ ] 2nd level menu items
[ ] Contact button
[ ] link to https://reseau-allianz.ma/ (different site not in scope)

could split into different issues if needed


First wave of refactoring

The app is now aware of the parameters (range & #POI)
Now using a library to connect to the Internet
Now using Singleton pattern to hold some variables
Cleaned code, updated deprecated code

Woops, wrong branch


Integrate Jupyter notebooks into automated tests & Travis CI

Currently we have no process for ensuring that our notebooks remain valid as the underlying codebase changes.  In most cases this isn't a huge issue -- many of them are really scratch paper -- but it would be useful to make sure a few of them continue functioning:

Notebooks we use in the integration of new data as it is released periodically
At least one introductory / documentation notebook for new PUDL users/contributors
Notebooks used to perform example analyses and data visualizations the PUDL data and analyses.

It looks like there are several plugins to PyTest that may be able to help achieve this goal, and get the test system to run specified collections of notebooks. nbval is the best looking option I've come across. Documentation here

The nbval tox environment does most of this -- closing and replacing w/ a re-org of notebooks into travis / non-travis tested ones...