feat: fastify support

What is it?

[X] Feature / enhancement
[ ] Bug
[ ] Docs / tests

Description
closes #2240

feat: support for fastify server;
chore: corrected most of "nodejs" mispell with the correct one "Node.js";
breaking: the qwik-city adapter called express has been renamed to a more generic node-server.

Use cases and why

Use fastify as server

Increase performances

Checklist:

[X] My code follows the developer guidelines of this project
[X] I have performed a self-review of my own code
[X] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Thank you very much @ilteoood 🙏 waiting for a approval of the core team 🎉

Hi! thanks for the PR! unfortunately, we cant merge this because of the breaking change, specially since it could be easily prevented with some deprecated APIs.
We should add back to the exports in the package.json the exports for the express, so previous code still works. Also the renamed methods should stay with a deprecated annotation

Hi @manucorporat, thank you so much for your review.
To be honest, I don't agree with what you said, because the qwik API is not yet stable, since the project is still in version 0, and this is the right time to introduce breaking changes.
I personally don't like to have deprecated code while the API is unstable, because it will be much harder in the future to remove all the deprecated code before the stable release.
By the way, I think I'll recreate the PR from scratch in order to have the minimum amount of conflict. Please be patient 🙏

Ping @manucorporat

Dealing with broken code when it can be easily avoided is day saver for us. I agree we can break now, but if we can easily avoid, i would prefer. Let's give developers a way to know what deprecated so, they know how to update, vs suddenly not working.

This is an amazing PR btw! let's ship it!

In other to show fastify in the next release we need to add a e2e test here:
https://github.com/BuilderIO/qwik-city-e2e

basically, it's deploying the exact app in fastify and run all the tests we already have!

Are we using fastify as default now or we need to activate it somewhere?


[MM-25835] - Add Icon Button common component

WIP since this is a part of a larger feature, will be tested by PM and QA when we have linked it all together.
Summary
As part of our new Menu component, and preparation for the Compass design system, this PR adds one of the subelements of the Menu, the Icon Button Common component. It renders the Icon Common component (to be added). Structure is:

iconGlyph: the name of the desired icon glyph, using constants (eg. Icon.EMOTICON_HAPPY_OUTLINE)

size: this desired size of the icon (xsmall, small, standard, large, xlarge), using constants (eg. Icon.SMALL)

label: text to use for accessibility as needed, uses aria-label

disabled: a boolean indicating whether the IconButton should be disabled or not

Snapshots should run when we have the main element created.
Ticket Link
https://mattermost.atlassian.net/browse/MM-25835
Related PR's
https://github.com/mattermost/mattermost-webapp/pull/5728
https://github.com/mattermost/mattermost-webapp/pull/5732

Looks good, but I have a bunch of things I wanted to ask about as usual.
In addition to those, is components/main_menu/elements the right place to be putting these? This seems like it would be used outside of new main menu stuff.

Yesss that's my mistake. Will move to 'components/compass/menu' :)

Do these need to be in menu though? I would've thought they could just live somewhere like components/compass/icon_button

Closing as we are restarting this effort with a slightly different approach


LINK-85 | Recurring events

Description
Modal component
Modal to enter recurring event settings
Collapsible component
List of recurring events and possibility to delete them
Closes
LINK-85
#Screenshots

I get this error

I get this error

Fixed that. Changed it also so that Timepicker replaces : with . when onBlur is called

should this one have some top and bottom margin? :)


nodejs.org GPG release keys changed

https://github.com/bucharest-gold/origin-s2i-nodejs/blob/master/Dockerfile#L34-L41 no longer matches https://github.com/nodejs/node#release-team

Thanks for reporting the issue.
landed here:
https://github.com/bucharest-gold/origin-s2i-nodejs/commit/0f8eb5baaf76dd53894a1578511c4acf4c7fc142


docs: guideline: Add mandatory guidelines

These two guidelines are mandatory rules in MISRA-C standard and address several undefined behaviors in the C99 standard.

This looks fine in terms of adding to the rules. For v2.7.0 we would like to have MISRA compliance "in kernel/* and base os code". I am interpreting "base os" as being anything under "lib/os", and if that's correct I believe we do not use malloc in the kernel or base os.
However, if we ever would like to extend that coverage at any point, our malloc will need to verify if a pointer is valid, which it currently does not. It's able to detect double-frees, but there is no pointer validation currently. In the current implementation, that is a O(n) operation.

@pfalcon  didnt we drop those in the initial review of the rules? why are we adding them now?

@nashif  I think we had overlooked them because they are not impacting Zephyr and because they are more related with the standard C library. Just sent them now because they address undefined behaviors.


Make ID an attribute

If not provided, use the old behaviour and create a new GUID.

It seems more idiomatic to me to replace Id with an ElementRef. That way, Blazor will handle the element lifetime, and if you do need to access it from JS, you can pass the ElementRef to interop.

I am in agreement with @chucker .
Since this is a Blazor component, it would be preferable to allow the runtime to handle the elements lifetime and thus handle the Id.


[1.14.3] Loading clientside code on dedicated server- Server Crash. Sidedness issue.

Relevant log stacktrace -
https://gist.github.com/ProsperCraft/cb97406ec85cc4288ca34e319e189321
Crash report-
https://gist.github.com/ProsperCraft/b5632b9ee331a92a0b25eb387e376398
Full debug log-
https://gist.github.com/ProsperCraft/ddfdd0f96cff0f4acfe3685988a20105
Modpack-
https://www.curseforge.com/minecraft/modpacks/ocean-islands-adventure/

Closed in latest version


Connect Account - Coinbase Wallet Connection Unsuccessful (Android)

Connect Account - Coinbase Wallet Connection Unsuccessful (Android)
Description: There is an issue connecting accounts with Coinbase Wallet (CBW), resulting in continuous loading after the first signature.
Expected Behavior: The account should connect successfully without continuous loading after the first signature.
Actual Behavior:
• The first signature is completed successfully on both CBW and Converse.
• Once the Converse signature is selected, the Converse app continuously shows loading and does not complete the connection process.
Steps to Recreate:

Attempt to connect an account using Coinbase Wallet.
Complete the first signature on both CBW and Converse.
Select the Converse signature.
Observe the continuous loading issue on the Converse app.

Slack Message

@CarolineMMcGuire Is this still happening in 233?

@saulmc This is resolved in 233! I was able to connect to Coinbase with no issues on Android!

Thanks @CarolineMMcGuire ! Could you do a quick scan of the issues list for any others that you feel confident closing as of 233?


Any plans to support videos?

Just curious if there are any plans to support videos. Even just for caching purposes via CloudFlare. Well, I guess I could just register my own CloudFlare account for that purpose, but it has always confused me how much bandwidth can be cached without hitting some limits on their service.
Thanks!

Support for videos is not on our roadmap unfortunately. It would simply cost too much processing power & bandwidth, and there are many great hosts for those already (this is also true for animated images). I'm also not entirely sure of the benefit of resizing/downsampling video-streams/animations on our end.
If I may suggest some (lesser-known) alternatives for video-hosting: Vimeo, Wistia, vzaar, Brightcove, SproutVideo.

In regard to this, have you thought about supporting the range header for videos? It would not need to download the whole video, if I understand correctly.
See https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests.


bug: TodoFzfLua with cwd= does not work

Did you check docs and existing issues?

[X] I have read all the todo-comments.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of todo-comments.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.2
Operating system/version
arch
Describe the bug
TodoFzfLua cwd="xxxx" does not work
Steps To Reproduce
run TodoFzfLua cwd="xxxx"
Expected Behavior
should only show todos under cwd="xxxx", but now it shows all
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "folke/todo-comments.nvim", opts = {} },
    -- add any other plugins here
  },
})

TodoTelescope cwd= works well, I try to fix it but I can not find any code transfer args to opts...

https://github.com/onns/todo-comments.nvim fix it?


New gallery performance improvements

Use https://github.com/flutter/flutter/pull/17167/files?&w=1 to ignore whitespaces.

Sure. Debugged with either debugRepaintRainbowEnabled or with debugProfileBuildsEnabled and debugProfileRepaintsEnabled and looking at the timeline.
Fixes redundant repainting of static render object subtrees during the crossfade animation and during the show options toggle.
Should improve average_frame_build_time_millis for flutter_gallery_ios__transition_perf and flutter_gallery__transition_perf


Various fixes after porting to recent dnslib & dnspythonversions

This is mainly maintenance, it ports the script to recent dnslib & dnspython versions.

Thanks!


CustomResource Controllers stop receiving updates after watch reconnect

Sometimes our controllers stop receiving updates about their custom resources. We've seen that sometimes a watch will become disconnected, and the custom resource event source will try to reconnect but fail to do so. We think that this reconnect failure is causing this problem.
I've traced the reconnection and exceptions to here : https://github.com/java-operator-sdk/java-operator-sdk/blob/master/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/event/internal/CustomResourceEventSource.java#L157 . I believe that the registerWatch method is throwing an exception which isn't caught by the SDK. because the exception is not caught by the SDK the watch stays dead and the event source no longer sends events. See my logs here where I've isolated the failure I'm describing : https://gist.github.com/secondsun/8e31d2680ff689750c62ad6ce9f419c0
To work around this for now I am trying to use reflection and CDI schedulers to get a reference to the customresourceeventsource and call "onClose" with a subclassed watchexception (https://github.com/secondsun/app-services-operator/commit/a25c4bd48fb6ad434cbf0ee4213fa3c1b070a61b#diff-7a83aac91ab02c7b354a2f40496c5d38ca1c88d3f72a391e83b8e265eb341454R69).
Clearly this is not an ideal solution, and I'm looking for workarounds or what the best fix at the SDK level could be.

After thinking I have thought of two "easy" solutions that would work for my use case.

if registerWatch in the onClose(WatchException) method throws an exception, call System.exit(1). This will restart the pod which will reestablish all connections.
Alternatively, retry registerWatch with a exponential backoff.

Harder solutions would include adding events that are fired if a resource's watch dies and allow controllers for those resources to be alterted, or have some way to expose/access the state of the event sources from the application.

@secondsun done some reading on why connection issue might happen:

cluster is unhealthy
cluster is overloaded
networking issues between nodes

Reason we seen this is because we got this OpenStack QA clusters that sometimes might get some bugs.
If we keep restarting pod on overloaded clusters we might contribute to the problem, however in this case kubernetes would do hard work on crash loop backoff
Approach nr2 with our own backoff could be problematic as there will be no way to monitor this properly and dropping connections could be one time freak accident that can lead to some CRs not being processed while . Obviously checking operator logs would give us this info.
Knowing pros and cons I think going with approach nr1 as other one would require some better monitoring.


chore: sync main with the latest develop changes

☁ Nx Cloud Report
CI is running/has finished running commands for commit e849e2aef037a315980af637b468920ea7d60cba.  Click to see the status, the terminal output, and the build insights.
📂 See all runs for this branch

✅ Successfully ran 2 targets

nx run-many --target=build --exclude=workspace --output-style=stream-without-prefixes
nx affected --target=test --exclude=workspace --output-style=stream-without-prefixes -- --ci --code-coverage --runInBand

Sent with 💌 from NxCloud.


SPOI-11614 Converter for String to byte array

@yogidevendra Please review and merge

@PramodSSImmaneni  I am getting message saying "Only those with write access to this repository can merge pull requests."


Create doxyfile

I'm sure that if you ask, @marekmaskarinec will send you a collaboration invite :D


docs: punctuation fixes

This is for you, @jonboulle.

ok

Just "ok"?

Yes
On Fri, Jun 5, 2015 at 4:19 PM, Alex Crawford<EMAIL_ADDRESS>wrote:

Just "ok"?
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/docs/pull/504#issuecomment-109479396.

Fine.


fix. Parser allow other extension

Description

Fix bug from #2086. reference CodeIgniter/View/View::render

Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPdocs
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

The User Guide will need to be updated as well:
"These scripts have a .php extension, but can not contain any PHP." (https://codeigniter4.github.io/CodeIgniter4/outgoing/view_parser.html#what-it-does)
[user_guide_src/source/outgoing/view_parser.rst]

In fact, I just saw that this problem needs to be decided in 4.0.0-rc.2, I don't know what is the reason for fixing this problem. Compatible with CI3? Or is it allowed for any extension? Is this part of the CI4 program?(translate from Google)
@jim-parry

It's a defect that makes sense to fix now before the next RC, that's all.
We fix what we can, and defer what we must.

The view parser was supposed to allow other extensions, and not doing so is an oversight.
I hope to pull together rc.2 on thursday, and hope this can be part of it.

I tried windows / linux / vagrant and there is no way to generate a user guide. Sorry I can't modify the content in the user guide. In fact, English is not my native language, and I don't think I can accurately modify the user guide.(translate from Google)

You don't have to actually generate the user guide - that is done as part of release building.
The more important thing is to update the appropriate .rst pages.
It is apparent that we need a better process for managing the user guide workflow, but that is something I plan to address in October.

Thank you :)


Don’t we need a checksum property for the Order Payload?

Checksum is only available for order post back payloads. For order payloads your request is already authenticated with access_token which is generated with a similar checksum when you login.
And all the requests to KiteConnect is via HTTPS, so they are end to end encrypted and can't be tampered.

Got it. Thanks!


Feature: add reminders to submissions

Fix #1491
Added ability to create reminders from the submission page, currently added only one and default action Remind reviewers to Review and default medium which is Email as way of communication.

Reminders are shown in the sidebar and grouped by action with delete functionality.

I have created a command for cron jobs to send reminders: https://github.com/OpenTechFund/hypha/blob/feature/add-reminders-to-submissions/hypha/apply/funds/management/commands/send_reminders.py
Most of the feature is done except Edit Reminder and List upcoming reminders on users Dashboard.

I did a rebase to get in the fix I committed for the date time widget placeholder formatting.

Thanks! Will test this now. I rebuilt the history of the branch. Please do not merge it in to your local branch, that makes the history less clean.
If you have no changes to your local branch this is a quick way to update it.
$ git fetch origin
$ git  checkout feature/add-reminders-to-submissions
$ git reset origin/feature/add-reminders-to-submissions --hard

If you have new local changes I believe a pull rebase should work.
$ git pull --rebase

I have configured git to always use rebase on pull with.
# Force all new branches to automatically use rebase
$ git config branch.autosetuprebase always

# Force existing branches to use rebase.
$ git config branch.*branch-name*.rebase true

Thanks for teaching me about "datetime-local", I hope Safari and Firefox will support it soon.

Reminder to self: Add scheduler to run "send_reminder" command every hour.


Add server/client version check

As my mod is both a client/server mod, I get so many issues from people reporting the mod doesn't work. I was thinking of making a client/server check in both directions for my mod but adding it to Wetstone seems better.
So this should probably be configurable, but basically on load, send a message from client to server with your version and mod name, then the server replies with it's version/name. If nothing is received within x time, write in chat that your mod was not found on the server. If the versions don't match, write that.
Some form of that, if that makes sense.

Could do the same with Wetstone for a version check. Like if my mod requires version 1.1.0, but only 1.0.0 is installed, it would also show this error, etc.

Yes, some form of semver version communication would be nice/desirable to have.


Blackscreen not solved by current alternatives.

Hi!
Debian 11 with xrdp 0.9.12 from pre compiled packages (apt install xrdp xorgxrdp)
I was connecting to the XRDP server very well, only trying to make USB redirection work for me, but just modifying the "FuseMountName=..." line in sesman.ini and various other parameters in the RDP clients, after one of the several service restarts I could not log anymore just that black screen after the default XRDP login screen.
Tried several suggestions that I find over the web and here in the project but none work, as:

Tried to log with an account different from root and not already logged in the system, give me the black screen. (reboot/restart service)

Tried to uninstall dbus-user-session and install dbus-x11, rebooting, and still with the black screen issue (reverting back to dbus-user-session and remove dbus-x11 and reboot/restart service)

After adding the folowing lines to /etc/xrdp/startwm.sh

unset DBUS_SESSION_BUS_ADDRESS
unset XDG_RUNTIME_DIR

Just before the "test -x /etc/X11/Xsession && exec /etc/X11/Xsession" line.
Still black screen, after that I revert back the file and reboot/restart service.

Modified /etc/X11/Xwrapper.config
from
allowed_users=console
to
allowed_users=anybody
Still black screen, then I revert back the file and reboot/restart service.

Tried to log with xfreerdp, rdesktop, mstsc, and from different hosts, always black screen after the XRDP login screen.
Any clue on how can I get to the session?
These are my logs and configuration files (clients and server in the same VLAN), now, without caring with usb redirection:
/var/log/xrdp.log
[20220610-14:50:21] [INFO ] starting xrdp with pid 1614435
[20220610-14:50:21] [INFO ] address [<IP_ADDRESS>] port [32000] mode 4
[20220610-14:50:21] [INFO ] listening to port 32000 on <IP_ADDRESS>
[20220610-14:50:21] [INFO ] xrdp_listen_pp done
[20220610-14:50:25] [INFO ] Socket 12: AF_INET connection received from <IP_ADDRESS> port 37066
[20220610-14:50:25] [DEBUG] Closed socket 12 (AF_INET <IP_ADDRESS>:32000)
[20220610-14:50:25] [DEBUG] Closed socket 11 (AF_INET <IP_ADDRESS>:32000)
[20220610-14:50:25] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20220610-14:50:25] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20220610-14:50:25] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[20220610-14:50:25] [DEBUG] TLSv1.3 enabled
[20220610-14:50:25] [DEBUG] TLSv1.2 enabled
[20220610-14:50:25] [DEBUG] Info - All channels are disabled
[20220610-14:50:25] [DEBUG] Security layer: requested 3, selected 0
[20220610-14:50:25] [INFO ] connected client computer name: computer
[20220610-14:50:25] [INFO ] all channels are disabled by configuration
[20220610-14:50:25] [INFO ] Non-TLS connection established from <IP_ADDRESS> port 37066: encrypted with standard RDP security
[20220610-14:50:25] [DEBUG] MCS_CJRQ - channel join request received
[20220610-14:50:25] [DEBUG] MCS_CJRQ - channel join request received
[20220610-14:50:25] [DEBUG] MCS_CJRQ - channel join request received
[20220610-14:50:25] [DEBUG] MCS_CJRQ - channel join request received
[20220610-14:50:25] [DEBUG] MCS_CJRQ - channel join request received
[20220610-14:50:25] [DEBUG] xrdp_0018dfcc_wm_login_mode_event_00000001
[20220610-14:50:25] [INFO ] Loading keymap file /etc/xrdp/km-00000416.ini
[20220610-14:50:25] [WARN ] local keymap file for 0x00000416 found and doesn't match built in keymap, using local keymap file
[20220610-14:50:30] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip <IP_ADDRESS> port 3350
[20220610-14:50:30] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20220610-14:50:31] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20220610-14:50:31] [DEBUG] return value from xrdp_mm_connect 0
[20220610-14:50:33] [INFO ] xrdp_wm_log_msg: login successful for display 11
[20220610-14:50:33] [DEBUG] xrdp_wm_log_msg: started connecting
[20220610-14:50:37] [DEBUG] Closed socket 17 (AF_UNIX)
[20220610-14:50:37] [INFO ] lib_mod_log_peer: xrdp_pid=1630156 connected to X11rdp_pid=1660273 X11rdp_uid=72226 X11rdp_gid=513 client_ip=<IP_ADDRESS> client_port=37066
[20220610-14:50:37] [DEBUG] xrdp_wm_log_msg: connected ok
[20220610-14:50:37] [DEBUG] xrdp_mm_connect_chansrv: skip connecting to chansrv because all channels are disabled
[20220610-14:50:37] [DEBUG] Closed socket 16 (AF_INET6 ::ffff:<IP_ADDRESS> port 54182)

/var/log/xrdp-sesman.log
[20220610-14:50:30] [INFO ] A connection received from ::ffff:<IP_ADDRESS> port 54182
[20220610-14:50:33] [INFO ] ++ created session (access granted): username username, ip <IP_ADDRESS>:37066 - socket: 12
[20220610-14:50:33] [INFO ] starting Xorg session...
[20220610-14:50:33] [DEBUG] Closed socket 10 (AF_INET6 :: port 5911)
[20220610-14:50:33] [DEBUG] Closed socket 10 (AF_INET6 :: port 6011)
[20220610-14:50:33] [DEBUG] Closed socket 10 (AF_INET6 :: port 6211)
[20220610-14:50:33] [DEBUG] Closed socket 9 (AF_INET6 ::ffff:<IP_ADDRESS> port 3350)
[20220610-14:50:33] [INFO ] calling auth_start_session from pid 1651813
[20220610-14:50:36] [DEBUG] Closed socket 8 (AF_INET6 ::ffff:<IP_ADDRESS> port 3350)
[20220610-14:50:36] [DEBUG] Closed socket 9 (AF_INET6 ::ffff:<IP_ADDRESS> port 3350)
[20220610-14:50:36] [INFO ] /usr/lib/xorg/Xorg :11 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[20220610-14:50:37] [CORE ] waiting for window manager (pid 1660272) to exit

/home/username/.xorgxrdp.10.log
[  3493.847]
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[  3493.847] Build Operating System: linux Debian
[  3493.847] Current Operating System: Linux xrdp-server 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64
[  3493.847] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-amd64 root=UUID=40cb84ab-34c4-4a10-8bc8-f38c331abaff ro quiet splash
[  3493.847] Build Date: 16 December 2021  05:08:23PM
[  3493.847] xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support)
[  3493.847] Current version of pixman: 0.40.0
[  3493.847] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  3493.847] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  3493.847] (++) Log file: ".xorgxrdp.10.log", Time: Fri Jun 10 14:48:49 2022
[  3493.847] (++) Using config file: "/etc/X11/xrdp/xorg.conf"
[  3493.847] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  3493.848] (==) ServerLayout "X11 Server"
[  3493.848] (**) |-->Screen "Screen (xrdpdev)" (0)
[  3493.848] (**) |   |-->Monitor "Monitor"
[  3493.848] (**) |   |-->Device "Video Card (xrdpdev)"
[  3493.848] (**) |-->Input Device "xrdpMouse"
[  3493.848] (**) |-->Input Device "xrdpKeyboard"
[  3493.848] (**) Option "DontVTSwitch" "on"
[  3493.848] (**) Option "AutoAddDevices" "off"
[  3493.848] (**) Not automatically adding devices
[  3493.848] (==) Automatically enabling devices
[  3493.848] (==) Automatically adding GPU devices
[  3493.848] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  3493.848] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  3493.848] 	Entry deleted from font path.
[  3493.848] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[  3493.848] (==) ModulePath set to "/usr/lib/xorg/modules"
[  3493.848] (II) Loader magic: 0x55b908482e40
[  3493.848] (II) Module ABI versions:
[  3493.848] 	X.Org ANSI C Emulation: 0.4
[  3493.848] 	X.Org Video Driver: 24.1
[  3493.848] 	X.Org XInput driver : 24.1
[  3493.848] 	X.Org Server Extension : 10.0
[  3493.849] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c8
[  3493.850] (II) xfree86: Adding drm device (/dev/dri/card0)
[  3493.850] (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted
[  3493.852] (--) PCI:*(6@0:0:0) 1002:15d8:1002:15d8 rev 217, Mem @ 0xe0000000/268435456, 0xf0000000/2097152, 0xfcc00000/524288, I/O @ 0x0000e000/256
[  3493.852] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[  3493.852] (II) LoadModule: "dbe"
[  3493.852] (II) Module "dbe" already built-in
[  3493.852] (II) LoadModule: "ddc"
[  3493.852] (II) Module "ddc" already built-in
[  3493.852] (II) LoadModule: "extmod"
[  3493.852] (II) Module "extmod" already built-in
[  3493.853] (II) LoadModule: "glx"
[  3493.853] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  3493.853] (II) Module glx: vendor="X.Org Foundation"
[  3493.853] 	compiled for 1.20.11, module version = 1.0.0
[  3493.853] 	ABI class: X.Org Server Extension, version 10.0
[  3493.853] (II) LoadModule: "int10"
[  3493.853] (II) Loading /usr/lib/xorg/modules/libint10.so
[  3493.853] (II) Module int10: vendor="X.Org Foundation"
[  3493.853] 	compiled for 1.20.11, module version = 1.0.0
[  3493.853] 	ABI class: X.Org Video Driver, version 24.1
[  3493.853] (II) LoadModule: "record"
[  3493.853] (II) Module "record" already built-in
[  3493.853] (II) LoadModule: "vbe"
[  3493.853] (II) Loading /usr/lib/xorg/modules/libvbe.so
[  3493.853] (II) Module vbe: vendor="X.Org Foundation"
[  3493.853] 	compiled for 1.20.11, module version = 1.1.0
[  3493.853] 	ABI class: X.Org Video Driver, version 24.1
[  3493.853] (II) LoadModule: "glamoregl"
[  3493.853] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[  3493.855] (II) Module glamoregl: vendor="X.Org Foundation"
[  3493.855] 	compiled for 1.20.11, module version = 1.0.1
[  3493.855] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  3493.855] (II) LoadModule: "xorgxrdp"
[  3493.855] (II) Loading /usr/lib/xorg/modules/libxorgxrdp.so
[  3493.856] (II) Module XORGXRDP: vendor="X.Org Foundation"
[  3493.856] 	compiled for 1.20.6, module version = 0.2.12
[  3493.856] 	ABI class: X.Org Video Driver, version 24.0
[  3493.856] xorgxrdpSetup:
[  3493.856] (II) LoadModule: "fb"
[  3493.856] (II) Loading /usr/lib/xorg/modules/libfb.so
[  3493.856] (II) Module fb: vendor="X.Org Foundation"
[  3493.856] 	compiled for 1.20.11, module version = 1.0.0
[  3493.856] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  3493.856] (II) LoadModule: "xrdpdev"
[  3493.856] (II) Loading /usr/lib/xorg/modules/drivers/xrdpdev_drv.so
[  3493.856] (II) Module XRDPDEV: vendor="X.Org Foundation"
[  3493.856] 	compiled for 1.20.6, module version = 0.2.12
[  3493.856] 	ABI class: X.Org Video Driver, version 24.0
[  3493.856] xrdpdevSetup:
[  3493.856] (II) LoadModule: "xrdpmouse"
[  3493.856] (II) Loading /usr/lib/xorg/modules/input/xrdpmouse_drv.so
[  3493.856] (II) Module XRDPMOUSE: vendor="X.Org Foundation"
[  3493.856] 	compiled for 1.20.6, module version = 0.2.12
[  3493.856] 	Module class: X.Org XInput Driver
[  3493.856] 	ABI class: X.Org XInput driver, version 24.1
[  3493.856] rdpmousePlug:
[  3493.856] (II) LoadModule: "xrdpkeyb"
[  3493.856] (II) Loading /usr/lib/xorg/modules/input/xrdpkeyb_drv.so
[  3493.856] (II) Module XRDPKEYB: vendor="X.Org Foundation"
[  3493.856] 	compiled for 1.20.6, module version = 0.2.12
[  3493.856] 	Module class: X.Org XInput Driver
[  3493.856] 	ABI class: X.Org XInput driver, version 24.1
[  3493.856] rdpkeybPlug:
[  3493.856] rdpIdentify:
[  3493.856] (II) XRDPDEV: driver for xrdp: XRDPDEV
[  3493.856] rdpDriverFunc: op 10
[  3493.856] (WW) Falling back to old probe method for XRDPDEV
[  3493.856] rdpProbe:
[  3493.856] (II) Loading sub module "fb"
[  3493.856] (II) LoadModule: "fb"
[  3493.856] (II) Loading /usr/lib/xorg/modules/libfb.so
[  3493.856] (II) Module fb: vendor="X.Org Foundation"
[  3493.856] 	compiled for 1.20.11, module version = 1.0.0
[  3493.856] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  3493.856] rdpProbe: found DRMDevice xorg.conf value [/dev/dri/renderD128]
[  3493.856] rdpProbe: found DRI3 xorg.conf value [1]
[  3493.856] (II) XRDPDEV(0): using default device
[  3493.856] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  3493.856] rdpPreInit:
[  3493.856] rdpPreInit: /dev/dri/renderD128 open failed
[  3493.856] (**) XRDPDEV(0): Depth 24, (--) framebuffer bpp 32
[  3493.856] (==) XRDPDEV(0): RGB weight 888
[  3493.856] (==) XRDPDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[  3493.856] (==) XRDPDEV(0): Default visual is TrueColor
[  3493.856] (==) XRDPDEV(0): DPI set to (96, 96)
[  3493.856] (II) XRDPDEV(0): 	mode "640x480" ok
[  3493.856] (II) XRDPDEV(0): 	mode "800x600" ok
[  3493.856] (II) XRDPDEV(0): Virtual size is 800x600 (pitch 800)
[  3493.856] (**) XRDPDEV(0):  Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[  3493.856] (II) XRDPDEV(0): Modeline "800x600"x0.0   36.00  800<PHONE_NUMBER>  600 601 603 625 +hsync +vsync (35.2 kHz d)
[  3493.856] rdpScreenInit: virtualX 800 virtualY 600 rgbBits 8 depth 24
[  3493.856] rdpScreenInit: pfbMemory bytes 1920000
[  3493.856] rdpScreenInit: pfbMemory 0x7fe9734a3010
[  3493.856] rdpSimdInit: assigning yuv functions
[  3493.856] rdpSimdInit: cpuid ax 1 cx 0 return ax 0x00810f81 bx 0x02040800 cx 0x7ed8320b dx 0x178bfbff
[  3493.856] rdpSimdInit: sse2 amd64 yuv functions assigned
[  3493.856] (==) XRDPDEV(0): Backing store enabled
[  3493.856] rdpClientConInit: disconnect idle session after [14400] sec
[  3493.856] rdpClientConInit: kill disconnected [1] timeout [60] sec
[  3493.856] rdpXvInit: depth 24
[  3493.856] rdpScreenInit: out
[  3493.856] (II) Initializing extension Generic Event Extension
[  3493.856] (II) Initializing extension SHAPE
[  3493.857] (II) Initializing extension MIT-SHM
[  3493.857] (II) Initializing extension XInputExtension
[  3493.857] (II) Initializing extension XTEST
[  3493.857] (II) Initializing extension BIG-REQUESTS
[  3493.857] (II) Initializing extension SYNC
[  3493.857] (II) Initializing extension XKEYBOARD
[  3493.857] (II) Initializing extension XC-MISC
[  3493.857] (II) Initializing extension SECURITY
[  3493.857] (II) Initializing extension XFIXES
[  3493.857] (II) Initializing extension RENDER
[  3493.857] (II) Initializing extension RANDR
[  3493.857] (II) Initializing extension COMPOSITE
[  3493.857] (II) Initializing extension DAMAGE
[  3493.857] (II) Initializing extension MIT-SCREEN-SAVER
[  3493.858] (II) Initializing extension DOUBLE-BUFFER
[  3493.858] (II) Initializing extension RECORD
[  3493.858] (II) Initializing extension DPMS
[  3493.858] (II) Initializing extension Present
[  3493.858] (II) Initializing extension DRI3
[  3493.858] (II) Initializing extension X-Resource
[  3493.858] (II) Initializing extension XVideo
[  3493.858] (II) Initializing extension XVideo-MotionCompensation
[  3493.858] (II) Initializing extension SELinux
[  3493.858] (II) SELinux: Disabled on system
[  3493.858] (II) Initializing extension GLX
[  3493.858] (II) AIGLX: Screen 0 is not DRI2 capable
[  3493.882] (II) IGLX: Loaded and initialized swrast
[  3493.882] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  3493.882] (II) Initializing extension XFree86-VidModeExtension
[  3493.882] (II) Initializing extension XFree86-DGA
[  3493.882] (II) Initializing extension XFree86-DRI
[  3493.882] (II) Initializing extension DRI2
[  3493.882] rdpCreateScreenResources:
[  3493.903] (II) Using input driver 'XRDPMOUSE' for 'xrdpMouse'
[  3493.903] (**) Option "CorePointer"
[  3493.903] (**) xrdpMouse: always reports core events
[  3493.903] rdpmousePreInit: drv 0x55b908e83a00 info 0x55b9090bfb70, flags 0x0
[  3493.903] (II) XINPUT: Adding extended input device "xrdpMouse" (type: Mouse, id 6)
[  3493.903] rdpmouseControl: what 0
[  3493.903] rdpmouseDeviceInit:
[  3493.903] rdpmouseCtrl:
[  3493.903] rdpRegisterInputCallback: type 1 proc 0x7fe973b80380
[  3493.903] (**) xrdpMouse: (accel) keeping acceleration scheme 1
[  3493.903] (**) xrdpMouse: (accel) acceleration profile 0
[  3493.904] (**) xrdpMouse: (accel) acceleration factor: 2.000
[  3493.904] (**) xrdpMouse: (accel) acceleration threshold: 4
[  3493.904] rdpmouseControl: what 1
[  3493.904] rdpmouseDeviceOn:
[  3493.904] (II) Using input driver 'XRDPKEYB' for 'xrdpKeyboard'
[  3493.904] (**) Option "CoreKeyboard"
[  3493.904] (**) xrdpKeyboard: always reports core events
[  3493.904] rdpkeybPreInit: drv 0x55b908e83970 info 0x55b90922f6e0, flags 0x0
[  3493.904] (II) XINPUT: Adding extended input device "xrdpKeyboard" (type: Keyboard, id 7)
[  3493.904] rdpkeybControl: what 0
[  3493.904] rdpkeybDeviceInit:
[  3493.918] rdpkeybChangeKeyboardControl:
[  3493.918] rdpkeybChangeKeyboardControl: autoRepeat on
[  3493.918] rdpRegisterInputCallback: type 0 proc 0x7fe973b7b7e0
[  3493.918] rdpkeybControl: what 1
[  3493.918] rdpkeybDeviceOn:
[  3493.923] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[  3493.923] (II) AutoAddDevices is off - not adding device.
[  3493.923] (II) config/udev: Adding input device Video Bus (/dev/input/event0)
[  3493.923] (II) AutoAddDevices is off - not adding device.
[  3493.924] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[  3493.924] (II) AutoAddDevices is off - not adding device.
[  3493.924] (II) config/udev: Adding drm device (/dev/dri/card0)
[  3493.924] (II) xfree86: Adding drm device (/dev/dri/card0)
[  3493.924] (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted
[  3493.924] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=3 (/dev/input/event4)
[  3493.924] (II) AutoAddDevices is off - not adding device.
[  3493.925] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=7 (/dev/input/event5)
[  3493.925] (II) AutoAddDevices is off - not adding device.
[  3493.925] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=8 (/dev/input/event6)
[  3493.925] (II) AutoAddDevices is off - not adding device.
[  3493.925] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[  3493.925] (II) AutoAddDevices is off - not adding device.
[  3493.929] rdpDeferredRandR:
[  3493.929] rdpResizeSession: width 1024 height 768
[  3493.929]   calling RRScreenSizeSet
[  3493.929] rdpRRScreenSetSize: width 1024 height 768 mmWidth 271 mmHeight 203
[  3493.929] rdpRRGetInfo:
[  3493.929]   screen resized to 1024x768
[  3493.929]   RRScreenSizeSet ok 1
[  3493.929] rdpResizeSession: width 1024 height 768
[  3494.019] rdpInDeferredRepeatCallback:
[  3494.019] rdpkeybChangeKeyboardControl:
[  3494.019] rdpkeybChangeKeyboardControl: autoRepeat off
[  3494.259] rdpClientConGotConnection:
[  3494.259] rdpClientConGotConnection: g_sck_accept ok new_sck 94
[  3494.259] rdpClientConGetConnection: engaging idle timer, timeout [14400] sec
[  3494.259] rdpAddClientConToDev: adding first clientCon 0x55b90939c6f0
[  3494.296] rdpClientConProcessMsgVersion: version 0 0 0 1
[  3494.297] rdpClientConProcessScreenSizeMsg: set width 1024 height 768 bpp 8
[  3494.297] rdpClientConProcessScreenSizeMsg: shmemid 8 shmemptr 0x7fe9735b8000
[  3494.308] rdpClientConProcessMsgClientInput: invalidate x 0 y 0 cx 1024 cy 768
[  3494.350] rdpClientConProcessMsgClientInfo:
[  3494.350]   got client info bytes 5752
[  3494.350]   jpeg support 0
[  3494.350]   offscreen support 0
[  3494.350]   offscreen size 0
[  3494.350]   offscreen entries 0
[  3494.350]   client supports glyph cache but server disabled
[  3494.350]   client can not do offscreen to offscreen blits
[  3494.350]   client can not do new(color) cursor
[  3494.350]   client can not do multimon
[  3494.350] rdpRRSetRdpOutputs: numCrtcs 0 numOutputs 0 monitorCount 0
[  3494.350] rdpRRSetRdpOutputs: add output 0 left 0 top 0 width 1024 height 768
[  3494.350] rdpLoadLayout: keylayout 0x00000416 variant  display 10
[  3494.361] rdpkeybChangeKeyboardControl:
[  3494.361] rdpkeybChangeKeyboardControl: autoRepeat on
[  3494.362] rdpkeybChangeKeyboardControl:
[  3494.362] rdpkeybChangeKeyboardControl: autoRepeat on
[  3494.471] rdpInDeferredRepeatCallback:
[  3494.471] rdpkeybChangeKeyboardControl:
[  3494.471] rdpkeybChangeKeyboardControl: autoRepeat off
[  3494.471] rdpInDeferredRepeatCallback:
[  3494.471] rdpkeybChangeKeyboardControl:
[  3494.471] rdpkeybChangeKeyboardControl: autoRepeat off
[  3548.823] rdpClientConRecv: g_sck_recv failed(returned 0)
[  3548.823] rdpClientConRecvMsg: error
[  3548.823] rdpClientConCheck: rdpClientConGotData failed
[  3548.823] rdpClientConDisconnect:
[  3548.823] rdpClientConDisconnect: disconnected, idle timer disengaged
[  3548.823] rdpClientConDisconnect: engaging disconnect timer, exit after 60 seconds
[  3548.823] rdpRemoveClientConFromDev: removing clientCon 0x55b90939c6f0
[  3608.859] rdpDeferredDisconnectCallback: disconnect timeout exceeded, exiting
[  3608.875] rdpmouseControl: what 2
[  3608.875] rdpmouseDeviceOff:
[  3608.875] rdpkeybControl: what 2
[  3608.875] rdpkeybDeviceOff:
[  3608.875] rdpkeybControl: what 3
[  3608.875] rdpkeybUnInit: drv 0x55b908e83970 info 0x55b90922f6e0, flags 0x0
[  3608.875] rdpUnregisterInputCallback: proc 0x7fe973b7b7e0
[  3608.875] rdpmouseControl: what 3
[  3608.875] rdpmouseUnInit: drv 0x55b908e83a00 info 0x55b9090bfb70, flags 0x0
[  3608.875] rdpUnregisterInputCallback: proc 0x7fe973b80380
[  3608.876] rdpCloseScreen:
[  3608.876] xorgxrdpDownDown:
[  3608.876] xorgxrdpDownDown: 1
[  3608.876] rdpClientConDeinit:
[  3608.876] rdpClientConDeinit: deleting file /run/xrdp/sockdir/xrdp_display_10
[  3608.876] rdpClientConDeinit: deleting file /run/xrdp/sockdir/xrdp_disconnect_display_10
[  3608.878] (II) Server terminated successfully (0). Closing log file.

cat /etc/xrdp/xrdp.ini #Comments removed for brevity
[Globals]
ini_version=1
fork=true
port=tcp://:32000
use_vsock=false
tcp_nodelay=true
tcp_keepalive=true
security_layer=negotiate
crypt_level=medium
certificate=
key_file=
ssl_protocols=TLSv1.2, TLSv1.3
tls_ciphers=HIGH
autorun=
allow_channels=false
allow_multimon=true
bitmap_cache=true
bitmap_compression=true
bulk_compression=true
max_bpp=8
new_cursors=false
use_fastpath=both
blue=474740
dark_blue=08246b
ls_top_window_bg_color=3671ad
ls_width=322
ls_height=220
ls_bg_color=E8E8E8
ls_logo_filename=/usr/share/xrdp/ad256.bmp
ls_logo_x_pos=0
ls_logo_y_pos=25
ls_label_x_pos=25
ls_label_width=70
ls_input_x_pos=110
ls_input_width=200
ls_input_y_pos=110
ls_btn_ok_x_pos=185
ls_btn_ok_y_pos=190
ls_btn_ok_width=65
ls_btn_ok_height=24
ls_btn_cancel_x_pos=110
ls_btn_cancel_y_pos=190
ls_btn_cancel_width=65
ls_btn_cancel_height=24

[Logging]
LogFile=xrdp.log
LogLevel=DEBUG
EnableSyslog=true
SyslogLevel=DEBUG
ConsoleLevel=DEBUG

[Channels]
rdpdr=true
rdpsnd=false
drdynvc=true
cliprdr=true
rail=false
xrdpvr=false
tcutils=true

[Xorg]
name=Remote
lib=libxup.so
username=ask
password=ask
ip=<IP_ADDRESS>
port=-1
code=20

cat /etc/xrdp/sesman.ini #Comments removed for brevity
[Globals]
ListenAddress=<IP_ADDRESS>
ListenPort=3350
EnableUserWindowManager=true
UserWindowManager=startwm.sh
DefaultWindowManager=startwm.sh
ReconnectScript=reconnectwm.sh

[Security]
AllowRootLogin=false
MaxLoginRetry=5
TerminalServerUsers=tsusers
TerminalServerAdmins=tsadmins
AlwaysGroupCheck=false
RestrictOutboundClipboard=false

[Sessions]
X11DisplayOffset=10
MaxSessions=50
KillDisconnected=true
DisconnectedTimeLimit=60
IdleTimeLimit=14400
Policy=Default

[Logging]
LogFile=xrdp-sesman.log
LogLevel=DEBUG
EnableSyslog=1
SyslogLevel=DEBUG
ConsoleLevel=DEBUG

[Xorg]
param=/usr/lib/xorg/Xorg
param=-config
param=xrdp/xorg.conf
param=-noreset
param=-nolisten
param=tcp
param=-logfile
param=.xorgxrdp.%s.log

[Chansrv]
FuseMountName=/run/user/%u/gvfs
FileUmask=077

[SessionVariables]

hundreds of these processes spawn while in blackscreen:
username  149955  0.0  0.0   2420    84 ?        S    13:56   0:00 /bin/sh /etc/X11/Xsession
username  149956  0.0  0.0   5304   504 ?        S    13:56   0:00 sleep 3
username  149961  0.0  0.0   2420    80 ?        S    13:56   0:00 /bin/sh /etc/X11/Xsession
username  149962  0.0  0.0   5304   504 ?        S    13:56   0:00 sleep 3
...
username  150146  0.0  0.0   2420    84 ?        S    13:56   0:00 /bin/sh /etc/X11/Xsession
username  150147  0.0  0.0   5304   564 ?        S    13:56   0:00 sleep 3
username  150152  0.0  0.0   2420    80 ?        S    13:56   0:00 /bin/sh /etc/X11/Xsession
username  150153  0.0  0.0   5304   572 ?        S    13:56   0:00 sleep 3

It looks like /etc/X11/Xsession is failing to start a session for some reason, and retrying something.
I can't find any sleep commands in my session startup scripts.
Can you post the output of this command?
DISPLAY= /bin/sh -x /etc/X11/Xsession

Don't miss out the space after DISPLAY=
If that command ends with lines something like this:-
+ ERRFILE=/home/username/.xsession-errors
+ [ -w /home/username/.xsession-errors ]
+ [ ! -L /home/username/.xsession-errors ]
+ chmod 600 /home/username/.xsession-errors
+ stat -c%s /home/username/.xsession-errors
+ [ 388129 -gt 500000 ]
+ exec

you'll find more information in ~/.xsession-errors. That would be useful to see too.

Well, it had the interesting side-effect of giving us something unusual to think about!
I'm very sure you're not dumb - we all fat-finger stuff from time-to-time.
Thanks for getting back to us.


[release/3.0-preview6] Unpin EF dependencies then grab the latest

#10050
includes new preview 6 packages from Blazor, Extensions, EntityFrameWorkCore, and AspNetCore-Tooling
update coherent parent chain to use EF Core instead of AspNetCore-Tooling again
partially reverts 58c67727dfb3

Tagging to see status here.

Retried the PR validation build. First attempt failed 6 tests on Ubuntu which is strange…

@aspnet-hello triage  https://dev.azure.com/dnceng/public/_build/results?buildId=210185&view=logs

This comment was made automatically. If there is a problem contact<EMAIL_ADDRESS>I've triaged the above build. I've created/commented on the following issue(s)
https://github.com/aspnet/AspNetCore-Internal/issues/2303

@Pilchie @natemcmaster and I looked at the test failures in the 1st attempt and couldn't find anything of concern. 2nd attempt already succeeded and is working on notifying GitHub. Anything I should wait on before merging this PR e.g. https://devdiv.visualstudio.com/DevDiv/_workitems/edit/904672 ?

Let's merge and get a build queued up. I would be shocked if this change wasn't approved by QB since this is just a dependency update.

Thanks everyone.  Merging was the right call.


Update groupId and version of flink-training-exercises dependency

flink-training-exercises's groupId was updated from com.dataartisans to com.data-artisans (in this commit https://github.com/dataArtisans/flink-training-exercises/commit/1c3fa1ad8c85b117eee29cb553baa59b1c1bb394).
This pull request is to update the pom dependency instruction tutorial accordingly (as well as the version).

Thank you for opening a pull request for this. I'll merge it.


How to resume from a checkpint file?

My training with  senet on ImageNet was unexpectedly interruped. How to resume the training from a checkpoint with distributed setting?

Trainer has resume(self, path). If you use my code, I think that just specifying the path to the saved weight is enough.

I have resume the training successfully, but when I add "-distributed" flag， the training process broke down

OK, I'll check that problem.

I think now the resume works as expected.


DBZ-7015 Enable replication slot advance check

Reverts debezium/debezium#4456
The change in https://github.com/debezium/debezium/pull/4502 should address the underlying issue.

@jpechane We have been running with this patch for a few months and did not see any issue. The retries in the referred PR definitely solved the issue for us where it complained about the slot is in use.
From Postgres docs:
confirmed_flush_lsn pg_lsn

The address (LSN) up to which the logical slot's consumer has confirmed receiving data. Data corresponding to the transactions committed before this LSN is not available anymore. NULL for physical slots.

I'm able to consistently use pg_replication_slot_advance to advance to the confirmed_flush_lsn. We should at least keep this feature as experimental behind a separate config. Without this feature there can be silent data loss (when slot is dropped for some reason), which is bad for production workloads.

This user claims that he stil experiences the warnings https://debezium.zulipchat.com/#narrow/stream/348249-community-postgresql/topic/https.3A.2F.2Fissues.2Eredhat.2Ecom.2Fbrowse.2FDBZ-6087
I am fine with intorudction of internal (undocumented) see io.debezium.config.Field.createInternal(String) config option that would enable this behaviour as opt-in

@jpechane I've updated the PR with a config for opt-in.

@prburgu Applied, thanks


Module not found: Can't resolve '@readme/variable'

I installed the package on my nextjs 12, typescript 4.7.4 and tailwind 3.1.4 project. On initialising using the package, I get this error

error - ./node_modules/@readme/markdown/dist/main.js:3:0
Module not found: Can't resolve '@readme/variable'

Here is my code snippet

there's a red highlight on the code blocks but it shouldn't affect whether my code runs or not.
Please help,otherwise, I will have to look for some other way to present code blocks in tabs

👋 Which version of NPM are you using? @readme/variable is listed as a peer dependency of this package and NPM versions less than 6 don't install them by default.

Hi @erunion! same @brianwachira 's package intstalled in my project and same error. My npm version is 8.5.5

@brianwachira you can fix it by installing it on your end.

wave Which version of NPM are you using? @readme/variable is listed as a peer dependency of this package and NPM versions less than 6 don't install them by default.

I am using npm v 8.3.2

This issue was resolved!
🚀 Changes included in v6.47.0


Added test case for editing LB and adding port rules multiple times

@cjellick , can you please review this test case?

@alena1108  , can you please review this test case?


OAK-10267: make elastic indexes more lenient when fields cannot be converted

Isn't his already handled on oak side? Any specific reason this is again done on ES level?
Reference:
https://github.com/apache/jackrabbit-oak/blob/846fcb4e89055504cb5b340462b1a961bfb0019d/oak-search-elastic/src/main/java/org/apache/jackrabbit/oak/plugins/index/elastic/index/ElasticDocumentMaker.java#L166

@tihom88 you are right but we discovered that the segment store does not respect the contract when a String field is converted to a Date. As per Javadoc, when the value cannot be converted. it does fail in the memory and document stores but not in the segment store. This PR is a sort of workaround that adds an extra layer of security in such cases.

Date

But how this behaviour effecting ES indexing. Even if we store malformed data in segment store, the check in ElasticDocumentmaker won't add this malformed date in elastic doc, right?


[ansible] Support Lifecycle Management

Currently, the contrib/ansible project does a good job of performing an initial deployment of a Kubernetes cluster. After the cluster is initially deployed, operators have a multitude of tasks that must be performed to manage the lifecycle of the cluster. For example:

Add a master or node to the cluster
Upgrade the version of Kubernetes
etc..

Ansible playbooks should be created, tested, documented, supported, etc. to support common lifecycle management tasks. Additionally, the overall design of the project should be addressed to support multiple playbooks.

/cc: @stephenrlouie @adamschaub @rutsky

From my perspective there is currently especially one thing that keeps us from having a better lifecycle management for clusters with Ansible:
The certificate generation. This can be added/fixed by altering the scripts to check with openssl what names are in the current certificate and generating a new one for newly added services (/servers) (that require a certificate "change".
Another point to mention is that it would be better to use notify instead of the *_modified variables to restart the services (something I have been working on a bit already, if it is wanted).

What's the best way to Upgrade kubernetes on CentOS 7?

@smenon78 Have you just trying to re-run the deployment? That's the way I updated my clusters as already mentioned.
See https://github.com/kubernetes/contrib/blob/master/ansible/roles/master/tasks/pkgMgrInstallers/centos-install.yml#L5 as the latest version of Kubernetes master and nodes will be always installed by running the playbook(s).

Latest package available for me via packageinstall is 1.5.2. I would like to upgrade to 1.6.1
yum --showduplicates list kubernetes
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile

base: ftp.usf.edu
epel: mirror.compevo.com
extras: repos-va.psychz.net
updates: ftp.osuosl.org
Available Packages
kubernetes.x86_64                                                                                1.3.0-0.3.git86dc49a.el7                                                                                extras
kubernetes.x86_64                                                                                1.4.0-0.1.git87d9d8d.el7                                                                                extras
kubernetes.x86_64                                                                                1.5.2-0.2.gitc55cf2b.el7                                                                                extras
kubernetes.x86_64                                                                                1.5.2-0.5.gita552679.el7

Then there are three posibilites to do it with the Ansible deployment:
a) Use github-release as kube_source_type  value.
b) Use distribution-rpm as kube_source_type value.
c) Use local build binaries (localBuild).

I tried distribution-rpm, with kubernetes 1.5.6, api server had problem starting. with kubernetes 1.6.1, dns never worked. I am troubleshooting now.

@smenon78 Upgrading to 1.6.x and higher is currently not supported by the addons (dns, etc.) as the service accounts rbac stuff is missing.

Oh, thank you so much...For 1.5.6, api server has this in the log
Failed to start Kubernetes API Server.
May 16 21:47:19 devtricorder01-master-01 systemd[1]: kube-apiserver.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2297]: panic: parse <IP_ADDRESS>:8080: first path segment in URL cannot contain colon
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2297]: E0516 21:47:19.554347    2297 server.go:254] Failed to create clientset: parse <IP_ADDRESS>:8080: first path segment in URL cannot contain colon
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2297]: I0516 21:47:19.553430    2297 config.go:527] Will report <IP_ADDRESS> as public IP address.
May 16 21:47:19 devtricorder01-master-01 systemd[1]: Starting Kubernetes API Server...
May 16 21:47:19 devtricorder01-master-01 systemd[1]: kube-apiserver.service holdoff time over, scheduling restart.
May 16 21:47:19 devtricorder01-master-01 systemd[1]: kube-apiserver.service failed.
May 16 21:47:19 devtricorder01-master-01 systemd[1]: Unit kube-apiserver.service entered failed state.
May 16 21:47:19 devtricorder01-master-01 systemd[1]: Failed to start Kubernetes API Server.
May 16 21:47:19 devtricorder01-master-01 systemd[1]: kube-apiserver.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: panic: runtime error: invalid memory address or nil pointer dereference [recovered]
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /usr/lib/golang/src/runtime/asm_amd64.s:2197
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /builddir/build/BUILD/kubernetes-114f8911f9597be669a747ab72787e0bd74c9359/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/util/wait/wait.go:52
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /builddir/build/BUILD/kubernetes-114f8911f9597be669a747ab72787e0bd74c9359/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/util/wait/wait.go:97
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /builddir/build/BUILD/kubernetes-114f8911f9597be669a747ab72787e0bd74c9359/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/util/wait/wait.go:96
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /builddir/build/BUILD/kubernetes-114f8911f9597be669a747ab72787e0bd74c9359/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/client/cache/reflector.go:198
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /builddir/build/BUILD/kubernetes-114f8911f9597be669a747ab72787e0bd74c9359/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/client/cache/reflector.go:243
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /builddir/build/BUILD/kubernetes-114f8911f9597be669a747ab72787e0bd74c9359/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/client/cache/listwatch.go:90
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /builddir/build/BUILD/kubernetes-114f8911f9597be669a747ab72787e0bd74c9359/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/plugin/pkg/admission/serviceaccount/admission.go:95
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /usr/lib/golang/src/runtime/signal_unix.go:290
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /usr/lib/golang/src/runtime/panic.go:63
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /usr/lib/golang/src/runtime/panic.go:489
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /usr/lib/golang/src/runtime/asm_amd64.s:514
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /builddir/build/BUILD/kubernetes-114f8911f9597be669a747ab72787e0bd74c9359/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/util/runtime/runtime.go:51
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /builddir/build/BUILD/kubernetes-114f8911f9597be669a747ab72787e0bd74c9359/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/util/runtime/runtime.go:65
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: /builddir/build/BUILD/kubernetes-114f8911f9597be669a747ab72787e0bd74c9359/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/util/runtime/runtime.go:72
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: E0516 21:47:19.316373    2276 runtime.go:66] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: E0516 21:47:19.315795    2276 server.go:254] Failed to create clientset: parse <IP_ADDRESS>:8080: first path segment in URL cannot contain colon
May 16 21:47:19 devtricorder01-master-01 kube-apiserver[2276]: I0516 21:47:19.314883    2276 config.go:527] Will report <IP_ADDRESS> as public IP address.
May 16 21:47:19 devtricorder01-master-01 systemd[1]: Starting Kubernetes API Server...
May 16 21:47:19 devtricorder01-master-01 systemd[1]: kube-apiserver.service holdoff time over, scheduling restart.
May 16 21:47:18 devtricorder01-master-01 systemd[1]: kube-apiserver.service failed.
May 16 21:47:18 devtricorder01-master-01 systemd[1]: Unit kube-apiserver.service entered failed state.

@smenon78 Can you post your /etc/kubernetes/apiserver and /etc/kubernetes/config file, seems like the addresse for the local bind of the apiserver is missing http:// for some reason.


⚠ Jenkins Plugins Artifactory has degraded performance

In 5e0330f, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1282 ms

Resolved: Jenkins Plugins Artifactory performance has improved in bedc9e0 after 12 minutes.


Tensorflow lite aborts due to "pure virtual method called" on Raspberry Pi

Hello.
I compiled the library as described in
https://www.tensorflow.org/lite/rpi
When running
./benchmark_model --graph=mobilenet_v1_1.0_224.tflite
or
./minimal mobilenet_v1_1.0_224.tflite
it crashes with the following output:

STARTING!
Num runs: [50]
Inter-run delay (seconds): [-1]
Num threads: [1]
Benchmark name: []
Output prefix: []
Warmup runs: [1]
Graph: [mobilenet_v1_1.0_224.tflite]
Input layers: []
Input shapes: []
Use nnapi : [0]
Loaded model mobilenet_v1_1.0_224.tflite
resolved reporter
pure virtual method called
terminate called without an active exception

I tried to debug the problem myself: it occurs in a secondary thread.
Some function that is called from
EigenForTFLite::NonBlockingThreadPoolTempl<EigenForTFLite::StlThreadEnvironment>::WorkerLoop(int)
gets the this parameter equal to NULL.
The host is a raspberry pi 3B+, with raspbian.
I tried both to cross-compile the code and to compile natively.
I tried more versions: one is r1.11
Gcc version: 4.9.2
Does anyone else have the same problem or is it just me?
Thank you.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce
Mobile device

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.

Hello. Here is the form:

Have I written custom code
No
OS Platform and Distribution
Raspbian 8 Jessie
TensorFlow installed from
Source
TensorFlow version
r1.11
Bazel version
No
CUDA/cuDNN version
No
GPU model and memory
No
Exact command to reproduce
./benchmark_model --graph=mobilenet_v1_1.0_224.tflite
Mobile device
Raspberry Pi 3B+

@vvigilante It appears that you are using cmake which is deprecated. Could you try using Bazel?

I did not use cmake. I used the steps described in https://www.tensorflow.org/lite/rpi

I got it running. Compile flag -march=armv7-a seems to break things.
Just removing that flag worked for me.
I don't know if it is related to gcc version (mine is 4.9.2). I'm doing other tests.


[Bug]: openai adapter does not work

Current Behavior
The example in the readme produces the error APIRemovedInV1

Steps To Reproduce
!pip install openai gptcache

# example in the readme
from gptcache import cache
from gptcache.adapter import openai

cache.init()
cache.set_openai_key()

question = 'what is github'
answer = openai.ChatCompletion.create(
      model='gpt-3.5-turbo',
      messages=[
        {
            'role': 'user',
            'content': question
        }
      ],
    )
print(answer)

try at: https://colab.research.google.com/drive/1TjA2plt9ZXLHIQVvZ763Nj6fzshYGSoN?usp=sharing
Environment
Google colab
python 3.10.12
openai 1.3.5
gptcache 0.1.42

Anything else?
likely related to https://github.com/zilliztech/GPTCache/issues/570

yes, as you can see from the issue, it is due to the incompatibility of the openai upgrade interface. Before being compatible with openai 1.x, you can try to use the get and put methods of gptcache to implement cache

yes, as you can see from the issue, it is due to the incompatibility of the openai upgrade interface. Before being compatible with openai 1.x, you can try to use the get and put methods of gptcache to implement cache

@SimFG How can we in a Python program create and then interact with a cache without involving any LLM model? Asking because I want to benchmark some cache settings in a Python code without worrying about setting up an LLM model to interact with. I tried calling cache.put("Hi", "Hi back") but got the error AttributeError: 'Cache' object has no attribute 'put'. Is there a way to use cache just using get and put in Python code (i.e., after creating and initializing cache with some settings like distance thresahold, etc. in the Python code rather than starting cache as a server) without involving any LLM? Any help on this is appreciated.

@SimFG Also, after I stop a running gptcache server to change some settings in the config yaml file (such as distance/similarity threshold) and restart the server using the cmd "gptcache_server -s <IP_ADDRESS> -p 8000 -f gptcache_server_config.yaml", I get the following error:
start to install package: ruamel-yaml
successfully installed package: ruamel-yaml
Traceback (most recent call last):
File "/mnt/nfshome/judah.kshitij/.conda/envs/alpaca-lora_env/bin/gptcache_server", line 8, in
sys.exit(main())
File "/mnt/nfshome/judah.kshitij/.conda/envs/alpaca-lora_env/lib/python3.8/site-packages/gptcache_server/server.py", line 178, in main
init_conf = init_similar_cache_from_config(config_dir=args.cache_config_file)
File "/mnt/nfshome/judah.kshitij/.conda/envs/alpaca-lora_env/lib/python3.8/site-packages/gptcache/adapter/api.py", line 221, in init_similar_cache_from_config
data_manager = manager_factory(**storage_config)
File "/mnt/nfshome/judah.kshitij/.conda/envs/alpaca-lora_env/lib/python3.8/site-packages/gptcache/manager/factory.py", line 125, in manager_factory
return get_data_manager(s, v, o, e)
File "/mnt/nfshome/judah.kshitij/.conda/envs/alpaca-lora_env/lib/python3.8/site-packages/gptcache/manager/factory.py", line 200, in get_data_manager
return SSDataManager(cache_base, vector_base, object_base, eviction_base, max_size, clean_size, eviction)
File "/mnt/nfshome/judah.kshitij/.conda/envs/alpaca-lora_env/lib/python3.8/site-packages/gptcache/manager/data_manager.py", line 247, in init
self.eviction_base.put(self.s.get_ids(deleted=False))
File "/mnt/nfshome/judah.kshitij/.conda/envs/alpaca-lora_env/lib/python3.8/site-packages/gptcache/manager/eviction/memory_cache.py", line 59, in put
self._cache[obj] = True
File "/mnt/nfshome/judah.kshitij/.conda/envs/alpaca-lora_env/lib/python3.8/site-packages/cachetools/init.py", line 217, in setitem
cache_setitem(self, key, value)
File "/mnt/nfshome/judah.kshitij/.conda/envs/alpaca-lora_env/lib/python3.8/site-packages/cachetools/init.py", line 79, in setitem
self.popitem()
File "/mnt/nfshome/judah.kshitij/.conda/envs/alpaca-lora_env/lib/python3.8/site-packages/gptcache/manager/eviction/memory_cache.py", line 15, in wrapper
wrapper_func(keys)
TypeError: 'NoneType' object is not callable
Only way the server starts is when I also change the cache dir of the cache in the yaml config file. How can I fix this issue? I am not sure why just changing the simi threshold in yaml config and restarting the same server would give above error. Any insights for resolving above issue is appreciated.

yes, as you can see from the issue, it is due to the incompatibility of the openai upgrade interface. Before being compatible with openai 1.x, you can try to use the get and put methods of gptcache to implement cache

@SimFG Are you suggesting here that until openai adapter becomes compatible with openai 1.x, we use cache by starting the gptcache server and access it using get and put methods? Any help on providing more details on this is appreciated.

@judahkshitij a example case: https://github.com/zilliztech/GPTCache/blob/main/examples/adapter/api.py
about the gptcache server, you can see: https://github.com/zilliztech/GPTCache/blob/main/examples/README.md#How-to-use-GPTCache-server


LONG Type queries have no results

LONG Type queries have no results

I make a commit that solve the problem
please test and give feedback

that solve the problem

think you


Option to use the --unknown-slide parameter in spaceranger count

Description of feature
Hi!
Thanks for the work on the pipeline!
I wonder if you ever considered adding the possibility to add the --unknown-slide parameter to the spaceranger count in the spatialvi pipeline?
Current design doesn't allow for it, and expects the slide and area parameters to be always present, not allowing to work with visium-1/2/2-large data.
https://github.com/nf-core/spatialvi/blob/f846f0031f3b0e4fd344324cf4ef4d1404583683/modules/nf-core/spaceranger/count/main.nf#L34-L50
Best!

Hi, @pstorozenko!
Sorry for the late reply, I've been on vacation. This is an issue with the spaceranger/count module itself, and not the spatialvi pipeline. I would recommend you to open an issue at the nf-core modules repository instead: https://github.com/nf-core/modules/issues. If the module is updated we can update the pipeline as well.


[IOTS-524] No data in the analytics view for fire alarm and connected cup samples

When running fire alarm and connected cup examples I notice that analytics view behaves very strange, i.e. usually it doesn't show any data, or on some occasions it shows the data, but then when trying to refresh the view it looses them. In the meanwhile, real time data are shown correctly, except that fire alarm data published with the period of 1 second can't be displayed in real time (multiple temperature values are shown for the same time value, resulting in orthogonal lines on the graph)Reference: https://wso2.org/jira/browse/IOTS-524

The issue doesn't exists anymore.


Documentation?

I am interested in using this library in one of my projects, but I was not able to find any sort of documentation. Can someone point me in the right direction?

Hi,
Sorry for taking so much time to respond, I was in a cryosleep during last year and didn't check github.
Unfortunately I'm no longer maintaining this project - I've left the company that was sponsoring it, and since then they've been developing this library internally. It diverged a lot from what's currently hosted here and nobody has the time to merge these changes back.
I recommend to use https://github.com/bkaradzic/bgfx instead - it's stable, reliable and has excellent documentation.
I am really sorry for taking a year to reply to your request, hope that this didn't cause any problems.


fix(v2): Ensure that theme classic require webpack provided by @docusaurus/core

Motivation
This diff continues the progress of making docusaurus v2 work under yarn v2's pnp mode.
The Problem
There is a tricky require inside @docusaurus/theme-classic:
const ContextReplacementPlugin = require('webpack/lib/ContextReplacementPlugin');

@docusaurus/theme-classic also declares webpack as a peer dependency. Currently at runtime, webpack is likely to be provided by @docusaurus/core, which declares it as a direct dependency. However, this setup is theoretically not guaranteed to work, and it will certainly break in Yarn v2 pnp's strict mode. To understand why it's the issue, let me draw an layout of the node_modules.
In a package manager doesn't implement any hoisting optimization, the layout will be like
- node_modules
  - @docusaurus/core
    - node_modules
      - webpack
  - @docusaurus/theme-classic
    - index.js (that requires `webpack`)

Therefore, when index.js require webpack it will fail, because it doesn't exist in these paths:

project-root/@docusaurus/theme-classic/node_modules
project-root/@docusaurus/node_modules
project-root/node_modules

The current setup happens to work because popular package managers implement hoisting optimization, which results in a layout like
- node_modules
  - webpack
  - @docusaurus/core
  - @docusaurus/theme-classic
    - index.js (that requires `webpack`)

Under yarn's pnp mode, things will break. Although Yarn knows that @docusaurus/theme-classic declares webpack as a peer dependency, it still doesn't know where to find it.
The Fix
I think the code author's intention is to use the webpack provided by @docusaurus/core. Therefore, I decide to make this more explicit by using Module.createRequire, which can be understood by Yarn's pnp runtime. I discussed how createRequire works in #2789.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Everything can still be properly loaded, and the preview site still works.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

@SamChou19815 I'd like to complete most of the Yarn v2 pnp compatibility before we launch the next alpha version. Do you know what else is needed?

@SamChou19815 I'd like to have most of the Yarn v2 pnp compatibility completed before we launch the next alpha version. Do you know what else is needed?

All the changes that need to happen in docusaurus core is done. There is one remaining piece: webpack module resolution. Webpack v4 doesn't support pnp natively, but can be made to support it via a plugin. (See https://yarnpkg.com/features/pnp#support-via-plugins).
Fortunately, this can be already done in the user land via docusaurus plugins, like I did for my personal repo: https://github.com/SamChou19815/website/pull/528/files.
@yangshun I wonder what's your opinion on this? There are two good options available:

Add the plugin in @docusaurus/core, just like what CRA did: https://github.com/facebook/create-react-app/blob/f5c3bdb65480f93b2d4a4c2f3214fc50753de434/packages/react-scripts/config/webpack.config.js#L326-L344 . Since CRA can add this without any flags, it should automatically work even if user is not using pnp.
Create another official plugin for this, and tell user to use it if they want their docusaurus to run with pnp.

Thanks for the explanation! I'd go for adding to @docusaurus/core if there are negligible costs to non-pnp users in doing so. What do you recommend?

Thanks for the explanation! I'd go for adding to @docusaurus/core if there are negligible costs to non-pnp users in doing so. What do you recommend?

I recommend adding it to core. The size of pnp-webpack-plugin is very small.


U+0058 'X' X is not a known ActionOrigin

When executing a command like the following:
Edit X/.*/ ,s,old,new,g

The following error is thrown:
U+0058 'X' X is not a known ActionOrigin

'
This is a test'

'this is a test'


Print each output line with one command in test runners

When running multiple test suites in parallel -- e.g., as it
happens on the CI --, the names of the executed commands and the
results of the executions can/do get printed far from each other,
interrupted by other prints. This can make the reading of the
output hard. This patch prints each line with one echo command,
which makes the interruption of the line less likely.
JerryScript-DCO-1.0-Signed-off-by: Akos Kiss<EMAIL_ADDRESS>

Ok. LGTM

LGTM


Deleting Scheduler

After creating a schedule, I hover on it with the mouse, but I can't see a field to delete. The program can be created but not delete. What should I do to delete it like in the demo?

https://github.com/remotelock/react-week-scheduler/issues/28#issuecomment-679896259
Please have a look at the existing issues before creating a new one

https://github.com/remotelock/react-week-scheduler/issues/28#issuecomment-679896259
Please have a look at the existing issues before creating a new one

thanks a lot.

thanks a lot.

thanks a lot.

Hi, did you find a way to do it?


Add Maven 3.3.3 recipe

test with:
conda install -c memex maven

I'm going to test this on Linux.

Looks good.


Cannot get dotnet-isolated project running in Azure ( works locally)

I have tried many different ways to get my C# .NET 5 (dotnet-isolated) project working in Azure, but have not had any success whatsoever. The function runs perfectly on my local machine. I've tried swapping from consumption to app plan, I've tried to build locally and then published directly from my machine to skip around the build and release steps. Still no luck. I'm out of ideas and I don't really want to rollback to .NET Core 3.1.
I'm getting constant RPCExceptions that do not occur locally. I am having no problems with dependency injection with my local machine.
Exception while executing function: Functions.HBA1C Result: Failure Exception: System.InvalidOperationException: Unable to resolve service for type 'MediatR.IMediator' while attempting to activate 'CareInnovations.IHiS.HBA1C.Web.HbA1c'.    at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.ConstructorMatcher.CreateInstance(IServiceProvider provider)    at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.CreateInstance(IServiceProvider provider, Type instanceType, Object[] parameters)    at Microsoft.Azure.Functions.Worker.DefaultFunctionActivator.CreateInstance(Type instanceType, FunctionContext context) in D:\a\1\s\src\DotNetWorker.Core\Invocation\DefaultFunctionActivator.cs:line 23    at Microsoft.Azure.Functions.Worker.Invocation.DefaultFunctionInvoker2.CreateInstance(FunctionContext context) in D:\a\1\s\src\DotNetWorker.Core\Invocation\DefaultFunctionInvoker.cs:line 26    at Microsoft.Azure.Functions.Worker.Invocation.DefaultFunctionExecutor.ExecuteAsync(FunctionContext context) in D:\a\1\s\src\DotNetWorker.Core\Invocation\DefaultFunctionExecutor.cs:line 27    at Microsoft.Azure.Functions.Worker.OutputBindings.OutputBindingsMiddleware.Invoke(FunctionContext context, FunctionExecutionDelegate next) in D:\a\1\s\src\DotNetWorker.Core\OutputBindings\OutputBindingsMiddleware.cs:line 13    at Microsoft.Azure.Functions.Worker.GrpcWorker.InvocationRequestHandlerAsync(InvocationRequest request, IFunctionsApplication application, IInvocationFeaturesFactory invocationFeaturesFactory, ObjectSerializer serializer, IOutputBindingsInfoProvider outputBindingsInfoProvider) in D:\a\1\s\src\DotNetWorker.Grpc\GrpcWorker.cs:line 166 Stack:    at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.ConstructorMatcher.CreateInstance(IServiceProvider provider)    at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.CreateInstance(IServiceProvider provider, Type instanceType, Object[] parameters)    at Microsoft.Azure.Functions.Worker.DefaultFunctionActivator.CreateInstance(Type instanceType, FunctionContext context) in D:\a\1\s\src\DotNetWorker.Core\Invocation\DefaultFunctionActivator.cs:line 23    at Microsoft.Azure.Functions.Worker.Invocation.DefaultFunctionInvoker2.CreateInstance(FunctionContext context) in D:\a\1\s\src\DotNetWorker.Core\Invocation\DefaultFunctionInvoker.cs:line 26    at Microsoft.Azure.Functions.Worker.Invocation.DefaultFunctionExecutor.ExecuteAsync(FunctionContext context) in D:\a\1\s\src\DotNetWorker.Core\Invocation\DefaultFunctionExecutor.cs:line 27    at Microsoft.Azure.Functions.Worker.OutputBindings.OutputBindingsMiddleware.Invoke(FunctionContext context, FunctionExecutionDelegate next) in D:\a\1\s\src\DotNetWorker.Core\OutputBindings\OutputBindingsMiddleware.cs:line 13    at Microsoft.Azure.Functions.Worker.GrpcWorker.InvocationRequestHandlerAsync(InvocationRequest request, IFunctionsApplication application, IInvocationFeaturesFactory invocationFeaturesFactory, ObjectSerializer serializer, IOutputBindingsInfoProvider outputBindingsInfoProvider) in D:\a\1\s\src\DotNetWorker.Grpc\GrpcWorker.cs:line 166
Here's my config in Azure after a publish
[   {     "name": "APPINSIGHTS_INSTRUMENTATIONKEY",     "value": "REMOVED",     "slotSetting": false   },   {     "name": "APPLICATIONINSIGHTS_CONNECTION_STRING",     "value": "REMOVED",     "slotSetting": false   },   {     "name": "AzureWebJobsStorage",     "value": "REMOVED",     "slotSetting": false   },   {     "name": "FUNCTIONS_EXTENSION_VERSION",     "value": "~3",     "slotSetting": false   },   {     "name": "FUNCTIONS_WORKER_RUNTIME",     "value": "dotnet-isolated",     "slotSetting": false   },   {     "name": "WEBSITE_RUN_FROM_PACKAGE",     "value": "1",     "slotSetting": false   } ]
The app appears to be running, but any attempts to call the function fail. This is a Windows function.
Edit: Also Mediatr is on the server

I, too, am having issues though I'm able to run locallly. When I set up the Function App for Deployment from External Git (a GH repo) the deployment says it's succeeded

but no Functions ever load (and no errors are shown in portal).

When I log into Kudu for the function app I can eventually get to logs which show:
[07/26/2021 19:43:45 > 099c13: SYS INFO] Run script 'Consumer.net5.exe' with script host - 'WindowsScriptHost'
[07/26/2021 19:43:45 > 099c13: SYS INFO] Status changed to Running
[07/26/2021 19:43:46 > 099c13: ERR ] Unhandled exception. System.UriFormatException: Invalid URI: The hostname could not be parsed.
[07/26/2021 19:43:46 > 099c13: ERR ]    at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
[07/26/2021 19:43:46 > 099c13: ERR ]    at System.Uri..ctor(String uriString)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Grpc.Net.Client.GrpcChannel.ForAddress(String address, GrpcChannelOptions channelOptions)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.GrpcServiceCollectionExtensions.<>c.<AddGrpc>b__1_1(IServiceProvider p) in D:\a\1\s\src\DotNetWorker.Grpc\GrpcServiceCollectionExtensions.cs:line 58
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactory(FactoryCallSite factoryCallSite, RuntimeResolverContext context)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite singletonCallSite, RuntimeResolverContext context)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite singletonCallSite, RuntimeResolverContext context)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
[07/26/2021 19:43:46 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite singletonCallSite, RuntimeResolverContext context)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitIEnumerable(IEnumerableCallSite enumerableCallSite, RuntimeResolverContext context)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite singletonCallSite, RuntimeResolverContext context)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass1_0.<RealizeService>b__0(ServiceProviderEngineScope scope)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)
[07/26/2021 19:43:47 > 099c13: ERR ]    at Consumer.net5.Program.Main() in C:\home\site\repository\Consumer.net5\Program.cs:line 12
[07/26/2021 19:43:47 > 099c13: SYS ERR ] Job failed due to exit code -532462766
[07/26/2021 19:43:47 > 099c13: SYS INFO] Process went down, waiting for 60 seconds
[07/26/2021 19:43:47 > 099c13: SYS INFO] Status changed to PendingRestart

I, too, am using Dependency Injection for the TelemetryConfiguration object (due to #549)
If I then disconnect the External Git deployment from the Function App and use func azure functionapp publish locally, it succeeds and the Functions load in Azure without issue:
Uploading 6.95 MB [###############################################################################]
Upload completed successfully.
Deployment completed successfully.
Syncing triggers...
Functions in consumerzfk5ilpbbn6zu5:
    ClearDeadLetterServiceBusQueue - [TimerTrigger]

    EventGridProcessorAsync - [EventGridTrigger]

    EventHubProcessorAsync - [EventHubTrigger]

    ServiceBusQueueProcessorAsync - [ServiceBusTrigger]

    StorageQueueProcessorAsync - [QueueTrigger]

The code I'm deploying can be found here.

I don't think that the "554" is related. The error mentions an error parsing a URI, this is a DI issue

@alanokelly -- would it be possible to give us a sample that repro's what you're seeing? That'd help us understand what's different between local and Azure.


Added Red Black Trees

📥 Pull Request
Description
Added RBT to BST
Fixes #577
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@ajay-dhangar Please review and let me know if any changes required


Unable to process with LAYOUT set to DIAMOND #2

Same issue as before: https://github.com/ehendrix23/tesla_dashcam/issues/171.

Re-opened #171


Use hashbrown's new single-lookup insertion

With find_or_find_insert_slot and insert_in_slot, we can avoid an
extra insertion lookup after checking for existence. However, that also
reserves space for a new entry before checking existence, so it's a
little biased towards new items. For that reason, we're not using this
for map entry or set replace, as both imply a little more weight on
the expectation that it may already exist.

Benchmarks with rustc 1.72.0-nightly (e6d4725c7 2023-06-05) on Fedora 38, AMD Ryzen 7 5800X:
$ cargo benchcmp --threshold=5 master insert_in_slot
 name                           master ns/iter  insert_in_slot ns/iter  diff ns/iter   diff %  speedup
 entry_indexmap_150             2,110           2,265                            155    7.35%   x 0.93
 grow_fnv_indexmap_100_000      2,509,579       2,297,042                   -212,537   -8.47%   x 1.09
 indexmap_clone_for_sort_u32    13,637          12,636                        -1,001   -7.34%   x 1.08
 indexmap_merge_simple          237,821         225,027                      -12,794   -5.38%   x 1.06
 insert_indexmap_100_000        1,915,473       1,623,913                   -291,560  -15.22%   x 1.18
 insert_indexmap_10_000         144,566         126,376                      -18,190  -12.58%   x 1.14
 insert_indexmap_150            2,153           1,897                           -256  -11.89%   x 1.13
 iter_black_box_hashmap_10_000  6,049           4,800                         -1,249  -20.65%   x 1.26
 lookup_hashmap_100_000_single  13              12                                -1   -7.69%   x 1.08
 with_capacity_10e5_hashmap     161             152                               -9   -5.59%   x 1.06

Those are some good wins on insert*. The others are more confusing, some which have nothing to do with these changes at all. The loss on entry_indexmap_150 looks like just different inlining decisions, since I changed push, but it's close enough that I expect real-world scenarios could vary a lot more.


Brunch watch, doesn't delete asset files

brunch watch doesn't seem to delete asset files no longer being used.
Example
app/assets/index.html
$> rm app/assets/index.html
$> brunch watch
[16:44:39]: [Brunch]: compiled.

but it doesn't delete build/index.html
I'm not sure if this was a design choice or not, but just reporting it ;)

yep, it's a bug

This issue seems back with 1.7.20.

It works as intented right now! heh

@paulmillr Just to be clear, is it intended behavior that if I remove a file from app/assets/, it remains in public/?

Yes it does not attempt to clean out stale assets. Some users purposely leave things in their build assets dir.

Is there a command or option that overrides this behaviour @es128 ?
To be honest I'm struggling to imagine a use-case where you would delete the 'source' but want the 'compiled' version to remain - but surely it has to be the edge case?

I'm not sure how prevalent it is, but several people have definitely reported using it that way. Often using multiple tools writing into the same target dir iirc.

Is there a command or option that overrides this behaviour

rm -rf ./public/assets/* :wink:
There is no brunch option that I'm aware of at this point, but it seems like it would be a useful thing to add. It could probably even be done as a plugin

Often using multiple tools writing into the same target dir iirc.

Fair cop, hadn't considered that.
I'd personally target those resources at brunch's 'source' asset directory, as it's only copying those resources over anyway - however I'm assuming there are alternative workflow options available that contradict that.


Setup integration test with minio

I'll take this one if noone's assigned to it yet.

Sure, so at a high level:

Spin up minio via testcontainers before running the integration tests
Setup mino object storage with s3, gs and create the test hudi table
Run marked integration tests

I'll add more details today after work. Please feel free to add things I should keep in mind while I work on this.

@abyssnlp high-level looks good. a heads-up about testing data - since hudi-rs not yet supports hudi writer, we are using fixed pre-generated tables as the testing tables: see https://github.com/apache/hudi-rs/tree/main/crates/tests/data/tables Would like to see some detailed design around provisioning test tables through minio volumes

Sorry about delay.
Thanks for pointing to that. So we can mount the existing tables under here into the container before running the tests.
Something like:
.with_mount(Mount::bind_mount(canonicalize(Path::new("tests/data"))?.into_os_string().into_string().unwrap(),

However something that I found out about testcontainers  in Rust is that it doesn't support reusing the container for multiple tests so the integration tests would be for ex. in a single test function. More about it here. There are also workarounds. Alternative would be to use docker-compose to spin up minio before running integration tests and spin it down after.
So this is how I'm thinking about approaching it:

(optional) ./docker-compose.yaml for spinning up required containers for MinIO
crates/tests/src/common.rs - some utility code for ex. to create an s3 bucket, put the pre-generated tables
crates/tests/src/integration_test.rs - spin up minio using testcontainers and run integration tests
Integration tests are marked as a separate feature (integration_test) so they can be run separately

I had some questions as well.

Does this approach make sense? Would love to hear what you think
Do we plan on also running integration tests for Azure and GCP?

@abyssnlp sounds good to make use of docker-compose - it'll be convenient to evolve the tests as we probably need to add more components in future. to answer the questions

crates/tests is a crate to provide all kinds of common hudi test utilities, but we don't want to host actual tests in it.
we may want to install the hudi crates locally, to mimic how users install hudi from crates.io
we can organize the integration tests in a separate folder, not necessarily as a crate, since it's docker based, and we don't publish it either
we surely want to integ test for azure and gcp as well - just picked minio for easy start with s3.

Thanks for sharing your thoughts on it.
Having them separate from the crates sounds good. I've started some initial work on a local branch and managed to get Minio up with the pre-generated tables.
I'm currently running into some issues trying to read the tables via hudi-rs.
I've tried using both environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and local MinIO specific AWS_ENDPOINT and ALLOW_HTTP) and providing the config via the HudiDataSource::new_with_options as a Vec<&str, &str>.
I can confirm the object store config works for hudi::storage::Storage for ex. while trying to read the contents of .hoodie/hoodie.properties.
Might be some bad configuration on my end. I'll continue working on it this week and keep posting updates here.

@abyssnlp any plan to put this up in a PR?

@xushiyan Yes i'll put it up in a PR soon (today or tomorrow).


Create general guides for emergency situations

The following content comes to mind:

Ditching in water #2
Steeper turns are more efficient

Tradeoff between increased stall speed / chance of stall and turn efficiency — see this StackExchange answer

Startle factor and imperfect technique is highly relevant
Impossible turn and crossing runways

The main focus of these guides should be to educate about topics that most people seldom think about — or at least are expected not to do frequently. It should cover knowledge holes and raise awareness.
However, some parts may also re-iterate on topics that may even be covered in basic training. The best example would be "impossible turns and crossing runways" where most people probably covered impossible turns during their training but adding the awareness of crossing runways might end up being beneficial.
The crucial word here is "entropy". The guides may not be so extensive that no one will read them, but should still cover valuable insights in the necessary depth.