[Bug] MC Chat can ping Discord Users and Roles, despite it being disabled in Config

Players can ping Discord Users by using the following Discord formatting:
Example Discord User ID:<PHONE_NUMBER>70555412

Results in the following:

Mod Version:
The current Config File is the following:

#General Mod Config
[general]
	#Should the mod be enabled or not
	enabled = true
	#Enable Additional Logging. Used for Fault Finding. WARNING: CAUSES LOG SPAM!
	debugging = false
	#Internal version control. DO NOT TOUCH!
	configVersion = 14

#Config specific to the discord bot
[botConfig]
	#The token of the Discord Bot to use. This will be encrypted on first load. See https://sdlink.fdd-docs.com/initial-setup/ to find this
	botToken = "REDACTED"
	#How often the Bot Status will update on Discord (in Seconds). Set to 0 to disable
	statusUpdateInterval = 30

	#Control what the Discord Bot will display as it's status message
	[botConfig.botStatus]
		#Do not add Playing. A status to display on the bot. You can use %players% and %maxplayers% to show the number of players on the server
		status = "Enjoying Minecraft with %players%/%maxplayers% players"
		#The type of the status displayed on the bot. Valid entries are: PLAYING, STREAMING, WATCHING, LISTENING, CUSTOM_STATUS
		botStatusType = "CUSTOM_STATUS"
		#The URL that will be used when the "botStatusType" is set to "STREAMING", required to display as "streaming".
		botStatusStreamingURL = "https://twitch.tv/twitch"

	#Define how the bot should handle channel topic updates on the chat channel
	[botConfig.topicUpdates]
		#Should the bot update the topic of your chat channel automatically every 6 Minutes
		doTopicUpdates = true
		#A topic for the Chat Relay channel. You can use %player%, %maxplayers%, %uptime% or just leave it empty.
		channelTopic = "Playing Minecraft with %players%/%maxplayers% people | Uptime: %uptime%"

	#Configure the in-game Discord Invite command
	[botConfig.invite]
		#If this is defined, it will enable the in-game Discord command
		inviteLink = "https://discord.com/invite/furcade"
		#The message to show when someone uses /discord command. You can use %inviteurl%
		inviteMessage = "Hey, check out our discord server here -> %inviteurl%"

#Config relating to the discord channels and webhooks to use with the mod
[channelsAndWebhooks]
	#A DIRECT link to an image to use as the avatar for server messages. Also used for embeds
	serverAvatar = "REDACTED"
	#The name to display for Server messages when using Webhooks
	serverName = "All of Fabric 6 Server"

	#Config relating to the discord channels to use with the mod
	[channelsAndWebhooks.channels]
		#REQUIRED! The ID of the channel to post in and relay messages from. This is still needed, even in webhook mode
		chatChannelID = "1202698663910973531"
		#If this ID is set, event messages will be posted in this channel instead of the chat channel
		eventsChannelID = "1202698663910973531"
		#If this ID is set, console messages sent after the bot started will be relayed here
		consoleChannelID = "1202698663910973531"

	#Config relating to the discord Webhooks to use with the mod
	[channelsAndWebhooks.webhooks]
		#Prefer Webhook Messages over Standard Bot Messages
		enabled = true
		#The URL of the channel webhook to use for Chat Messages. Will be encrypted on first run
		chatWebhook = "REDACTED"
		#The URL of the channel webhook to use for Server Messages. Will be encrypted on first run
		eventsWebhook = ""
		#The URL of the channel webhook to use for Console Messages. DOES NOT WORK FOR CONSOLE RELAY! Will be encrypted on first run
		consoleWebhook = ""

#Configure which types of messages are delivered to Minecraft/Discord
[chat]
	#Use linked account names in Discord/Minecraft messages, instead of the default ones
	useLinkedNames = true
	#Convert Discord to MC, and MC to Discord Formatting
	formatting = true
	#Should console messages be sent to the Console Channel
	sendConsoleMessages = false
	#The type of image to use as the player icon in messages. Valid entries are: AVATAR, HEAD, BODY, COMBO
	playerAvatarType = "HEAD"
	#Should messages sent with TellRaw be sent to discord as a chat? (Experimental)
	relayTellRaw = true
	#Should the entire command executed be relayed to discord, or only the name of the command
	relayFullCommands = false
	#Should messages from bots be relayed
	ignoreBots = true
	#Should SERVER STARTING messages be shown
	serverStarting = true
	#Should SERVER STARTED messages be shown
	serverStarted = true
	#Should SERVER STOPPING messages be shown
	serverStopping = true
	#Should SERVER STOPPED messages be shown
	serverStopped = true
	#Should the chat be relayed
	playerMessages = true
	#Should Player Join messages be posted
	playerJoin = true
	#Should Player Leave messages be posted
	playerLeave = true
	#Should Advancement messages be posted
	advancementMessages = true
	#Should Death Announcements be posted
	deathMessages = true
	#Should Messages from the /say command be posted
	sendSayCommand = true
	#Should commands be posted to discord
	broadcastCommands = false
	#Commands that should not be broadcast to discord
	ignoredCommands = ["particle", "login", "execute"]
	#Allow mentioning discord roles, users and channels from Minecraft Chat
	allowMentionsFromChat = false

#Change the format in which messages are displayed
[messageFormatting]
	#Prefix to add to Minecraft when a message is relayed from Discord. Supports MC formatting. Use %user% for the Discord Username
	mcPrefix = "§e[Discord]§r %user%: "
	#Server Starting Message
	serverStarting = "*Server is starting...*"
	#Server Started Message
	serverStarted = "*Server has started. Enjoy!*"
	#Server Stopping Message
	serverStopping = "*Server is stopping...*"
	#Server Stopped Message
	serverStopped = "*Server has stopped...*"
	#Player Joined Message. Use %player% to display the player name
	playerJoined = "*%player% has joined the server!*"
	#Player Left Message. Use %player% to display the player name
	playerLeft = "*%player% has left the server!*"
	#Achievement Messages. Available variables: %player%, %title%, %description%
	achievements = "*%player% has made the advancement [%title%]: %description%*"
	#Chat Messages. THIS DOES NOT APPLY TO EMBED OR WEBHOOK MESSAGES. Available variables: %player%, %message%
	chat = "%player%: %message%"
	#Death Messages. Available variables: %player%, %message%
	death = "%player% %message%"
	#Command Messages. Available variables: %player%, %command%
	commands = "%player% **executed command**: *%command%*"

#Change in which channel messages appear
[messageDestinations]

	#Control where CHAT messages are delivered
	[messageDestinations.chat]
		#The Channel the message will be delivered to. Valid entries are CHAT, EVENT, CONSOLE
		channel = "CHAT"
		#Should the message be sent using EMBED style messages
		useEmbed = false
		#Embed Layout to use
		embedLayout = "default"

	#Control where START messages are delivered
	[messageDestinations.start]
		#The Channel the message will be delivered to. Valid entries are CHAT, EVENT, CONSOLE
		channel = "EVENT"
		#Should the message be sent using EMBED style messages
		useEmbed = false
		#Embed Layout to use
		embedLayout = "default"

	#Control where STOP messages are delivered
	[messageDestinations.stop]
		#The Channel the message will be delivered to. Valid entries are CHAT, EVENT, CONSOLE
		channel = "EVENT"
		#Should the message be sent using EMBED style messages
		useEmbed = false
		#Embed Layout to use
		embedLayout = "default"

	#Control where JOIN messages are delivered
	[messageDestinations.join]
		#The Channel the message will be delivered to. Valid entries are CHAT, EVENT, CONSOLE
		channel = "EVENT"
		#Should the message be sent using EMBED style messages
		useEmbed = false
		#Embed Layout to use
		embedLayout = "default"

	#Control where LEAVE messages are delivered
	[messageDestinations.leave]
		#The Channel the message will be delivered to. Valid entries are CHAT, EVENT, CONSOLE
		channel = "EVENT"
		#Should the message be sent using EMBED style messages
		useEmbed = false
		#Embed Layout to use
		embedLayout = "default"

	#Control where ADVANCEMENT messages are delivered
	[messageDestinations.advancements]
		#The Channel the message will be delivered to. Valid entries are CHAT, EVENT, CONSOLE
		channel = "EVENT"
		#Should the message be sent using EMBED style messages
		useEmbed = false
		#Embed Layout to use
		embedLayout = "default"

	#Control where DEATH messages are delivered
	[messageDestinations.death]
		#The Channel the message will be delivered to. Valid entries are CHAT, EVENT, CONSOLE
		channel = "EVENT"
		#Should the message be sent using EMBED style messages
		useEmbed = false
		#Embed Layout to use
		embedLayout = "default"

	#Control where COMMAND messages are delivered
	[messageDestinations.commands]
		#The Channel the message will be delivered to. Valid entries are CHAT, EVENT, CONSOLE
		channel = "EVENT"
		#Should the message be sent using EMBED style messages
		useEmbed = false
		#Embed Layout to use
		embedLayout = "default"

	#Control where messages that match none of the above are delivered
	[messageDestinations.custom]
		#The Channel the message will be delivered to. Valid entries are CHAT, EVENT, CONSOLE
		channel = "EVENT"
		#Should the message be sent using EMBED style messages
		useEmbed = false
		#Embed Layout to use
		embedLayout = "default"

#Manage access to your server, similar to whitelisting
[accessControl]
	#Enable Access Control
	enabled = false
	#Does the player need to be a member of your discord to join
	requireDiscordMembership = false
	#Can players verify multiple Minecraft Accounts
	allowMultipleAccounts = false
	#Optional: The player requires any of these roles to be able to join your server
	requiredRoles = []
	#Optional: Players with these roles will never be allowed access to your server
	deniedRoles = []
	#Optional: Role name or ID to assign to verified player accounts
	verifiedRole = ""
	#Should players with verified accounts, be banned from Minecraft if they get banned on discord
	banPlayerOnDiscordBan = false
	#Should members with verified accounts, be banned from discord when they are banned on Minecraft
	banMemberOnMinecraftBan = false

	#Configure messages shown to players when they don't meet verification requirements
	[accessControl.verificationMessages]
		#The message shown to players that are not verified
		accountVerification = "This server requires account verification. Your verification code is: {code}. Please visit our discord server for instructions on how to verify your account."
		#Message to show to players that are not a member of your discord
		nonMember = "Sorry, you need to be a member of our discord server to join this server"
		#Message to show when player doesn't have one of the required roles. Use {roles} to display the names of configured roles
		requireRoles = "Sorry, but you require any of the following roles: {roles}"
		#Message to show when player has a role from the deniedRoles list
		roleDenied = "Sorry, but you are not allowed to access this server."

#Execute Minecraft commands in Discord
[minecraftCommands]
	#Allow executing Minecraft commands from Discord
	enabled = false
	#Command Prefix. For example ?weather clear
	prefix = "?"
	#List of command permissions
	permissions = []

#Configure messages that will be ignored when relaying to discord
[ignoredMessages]
	#Filter certain types of messages from being relayed back to discord
	ignoredMessages = true
	#List of entries to process
	entries = []
	#Ignore messages sent from certain threads
	ignoredThreads = []

I can confirm this would be an issue, without any testing or looking at the code.
I know for a fact we only filter out <@, so doing <@@ would bypass that filter. Thanks for pointing this one out

I can confirm this would be an issue, without any testing or looking at the code.
I know for a fact we only filter out <@, so doing <@@ would bypass that filter. Thanks for pointing this one out.
This would even work as far back as v1 of this mod

This also works for Roles

As a temporary work around, you could set up a message filter to replace the @ with % or something else to make it invalid.
Rough example
#Configure messages that will be ignored when relaying to discord
[ignoredMessages]
	#Filter certain types of messages from being relayed back to discord
	ignoredMessages = true

	#List of entries to process
    [[ignoredMessages.entries]]
      search = "@"
      replace = "%"
      searchMode = "CONTAINS"
      action = "REPLACE"

As a temporary work around, you could set up a message filter to replace the @ with % or something else to make it invalid.
Rough example
#Configure messages that will be ignored when relaying to discord
[ignoredMessages]
	#Filter certain types of messages from being relayed back to discord
	ignoredMessages = true

	#List of entries to process
    [[ignoredMessages.entries]]
      search = "@"
      replace = "%"
      searchMode = "CONTAINS"
      action = "REPLACE"

The workaround works :+1:

Thanks for the feedback. I've been a little burned out from work, so I've been slow to do updates, but this can be a pretty serious issue, so I'll add a proper fix for this over the weekend

Proper fix finally released with 3.1.0


404 url link for the remarkable website

https://github.com/pybee/remarkable is a 404 page when you click on "Source Code" on this web page:

Wrong project!


disable iptable by default

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes https://github.com/openyurtio/openyurt/pull/1770
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

@huiwq1990 Thanks for your pull request, but i don't think that we should configure --enable-dummy-if to false by default. Instead, I think it should default to true so that pods in the container network can access kube-apiserver via yurthub.

@huiwq1990 Thanks for your pull request, but i don't think that we should configure --enable-dummy-if to false by default. Instead, I think it should default to true so that pods in the container network can access kube-apiserver via yurthub.


"no creation date could be found"

when i try to use this plugin nothing happens , i see only the message on subject

Can you make sure you have block time stamps enabled in settings?
On 5 Feb 2022, 1:45 PM +0400, Stefano @.***>, wrote:

when i try to use this plugin nothing happens , i see only the message on subject
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

And it only starts tracking creation date after you've turned it on. So past notes won't ahve creation dates.
On 5 Feb 2022, 1:45 PM +0400, Stefano @.***>, wrote:

when i try to use this plugin nothing happens , i see only the message on subject
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Can you make sure you have block time stamps enabled in settings?

oops no, now enabled!

And it only starts tracking creation date after you've turned it on. So past notes won't ahve creation dates.

even if i reindex the graph?

Yeah, logseq only tracks the creation date once the option has been enabled in settings unfortunately.


[feature] GRPC-Dart server and app/web example

I am development a web application using grpc-dart.
grcp.dart for server-side
grpc_web.dart for client-side (with AngularDart).
It´s working fine for me.
But I feel that other people may not initially know how to develop an application using grpc in Dart.
My suggestion is to include examples in this stagehand package of client-side (mobile and web) as well as server-side applications.

Much needed. Dart is now so popular among app developers. Why not some dash of gRPC and a quick way of getting started with dart?

Hey @mkustermann, is there a decent grpc client and grpc server hello world we could adapt for this requested example?
/cc @mit-mit @jonasfj

cc @sigurdm

Maybe use this example code? https://grpc.io/docs/tutorials/basic/dart/#example-code-and-setup

Hmm - not sure what decent means - there is: https://github.com/grpc/grpc-dart/tree/master/example/helloworld
Also https://github.com/grpc/grpc-dart/tree/master/example/grpc-web has an example of using grpc-web .
I once made a simple example of using grpc_web from flutter-web: https://github.com/sigurdm/grpc_web_flutter_example


Running the Demo locally throws error.

`bundle.js:562 Warning: _class(...): No 'render' method found on the returned component instance: you may have forgotten to define 'render', returned null/false from a stateless component, or tried to render an element whose type is a function that isn't a React component.
bundle.js:83107 Uncaught TypeError: inst.render is not a function`
I am not sure what I am doing wrong here to get this error. I cloned the repo then I ran npm install and then I ran npm start and I got an error just trying to run the demo at all. It's also unclear how to insert it as a folder in the general codebase.
Any help would be greatly appreciated. Thanks!

After doing a bisect, this was triggered by commit f3329ee, but seems to be because of a requirement in React 0.14 that was dropped in 0.15, as per the docs:

NOTE:
In React v0.14, stateless functional components were not permitted to return null or false (a workaround is to return a  instead). This was fixed in React v15, and stateless functional components are now permitted to return null.

I'm guessing the fix is to do Content || <noscript /> since rsg is using react 14 for dev?

Unfortunately that didn't work, since Content exists, it just doesn't have a render method (or a return value).  After looking into it, it's a bug that wasn't hit before because there was a check specifically for a render method on a class.
The problem is that example/components/Features/Additional examples in tabs.js has no render method, but I'm putting together a fix since it's blocking my work on #63.


When mounted via fstab it always mounts read only.

I am sure this was working previously, but after a rebuild of the machine  (using scripts) I can no longer get the bucket to mount as a read write volume when using fstab. Any help appreciated!
Mounting Using Ubuntu 18.0.4 running on Amazon EC2 with a machine role that has permissions to access the S3 bucket.
/etc/fstab
goofys#ross-incoming-binaries /mnt/s3 fuse _netdev,allow_other,--file-mode=0666,--dir-mode=0777,--debug_s3,--debug_fuse 0 0
running mount -l
ross-incoming-binaries on /mnt/s3 type fuse (ro,relatime,user_id=0,group_id=0,default_permissions,allow_other)
Output from system log:
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: s3.INFO Switching from region 'us-east-1' to 'eu-west-1'
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: [1.7K blob data]
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: [424B blob data]
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: s3.DEBUG DEBUG: Validate Response s3/HeadObject failed, not retrying, error NotFo
                                                                status code: 404, request id: 4228656EEEA3D67D, host id: aGQ+26NBRPHhhgXN
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: [1.7K blob data]
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: fuse.DEBUG Op 0x00000001        connection.go:395] <- init
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: fuse.DEBUG Op 0x00000001        connection.go:478] -> OK ()
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: main.INFO File system has been successfully mounted.
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: [425B blob data]
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: s3.DEBUG {
                                                          Bucket: "ross-incoming-binaries",
                                                          IsTruncated: false,
                                                          KeyMarker: "",
                                                          MaxUploads: 1000,
                                                          NextKeyMarker: "",
                                                          NextUploadIdMarker: "",
                                                          UploadIdMarker: ""
                                                        }

If I run goofys manually using the following it seems work correctly:
sudo goofys -f --debug_s3 --debug_fuse --file-mode=066dir-mode=0777 ross-incoming-binaries /mnt/s3
Output from mount -l
ross-incoming-binaries on /mnt/s3 type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions)

Further to this, we were building Goofys from the latest master and not using release 0.23.1.
The issue occurs in the latest master only - not on version 0.23.1 taken as a released binary. Looks like this could be a potential regression at the moment with the work being done.

Also, have this issue. dfb5c81 revert doesn't help.
Bisect guide me to this commit: 1971d6d

I am able to reproduce this wtih 1971d6dbc8443f5bd26fd5d1268c5470cb79d127 the issue seems to come from the underlining fuse library. if I switch the submodule to cb66eea2377fb365bbeb3055585db6e9ea3e8226 the issue goes away

@kahing Yeah, sorry, I mean that https://github.com/kahing/goofys/commit/1971d6dbc8443f5bd26fd5d1268c5470cb79d127 added this issue


Accessing ECMWF Data

For some reason, right when your team started collaborating with the ECMWF, they changed their licensing structure on July 1st, 2023 . This meant that my order placed in April was canceled with no notification. How can we access the data and go about doing research? Please reference this issue,
https://github.com/ecmwf/ecmwf-opendata/issues/30

Closing as this is a question for ECMWF and not related to our project.


Adjusted code for Xstate V5

In this PR I've done the following:

Updated the XState peer dependency version to ^5
Added jotai-effect to simplify handling state machine subscriptions
Upgraded the example and tests to work with the new code and follow best practices through the setup() function

This PR also closes #5

@dai-shi @arjunvegda Let me know if there are any review comments that need adjusting. Thank you

Added jotai-effect to simplify handling state machine subscriptions

How hard would it be to implement it here without jotai-effect?

Added jotai-effect to simplify handling state machine subscriptions

How hard would it be to implement it here without jotai-effect?

Not hard at all, I used it mostly because I thought the previous onMount + cleanup function was a bit hacky and hard to read but I could revert it and it should work just as well

@dai-shi Update on using jotai-effect
Without effect we run into some problems because of onMount's behaviour. I wasn't able to get it to reliably re-trigger the onMount, which means that after calling RESET, or because of react's strict mode it ends up unsubscribing from the changes in state, causing the whole screen to be unresponsive.
I could keep working but to be it seems a decent tradeoff both in readability, consistency and bundle size considering the gzipped package weights less than 2kb
gist url: https://gist.github.com/brunocangs/a20305a33c0c48aa7c10dc5b54d3544c

Without effect we run into some problems because of onMount's behaviour. I wasn't able to get it to reliably re-trigger the onMount,

Haven't thought about it deeply, but I understand there can be a difference. But, it's how it works as of now, right?
That said, I would like to see them as separate PRs.

This PR: Migrate to XState 5
Another PR: Fix with jotai-effect

That said, I would like to see them as separate PRs.

This PR: Migrate to XState 5

Managed to get an implementation that works both in dev and in prod by decoupling the subscription logic into other atoms, so I can reset them in a more predictable way. Would love a review to sanity check it's not causing any weird leaks @dai-shi.
With this implementation I think the jotai-effect isn't necessary

Did some deeper debugging and noticed that the unsubscribe function wasn't getting called on reset. Made some adjustments to fix it.
Tests pass

Not a deep review at all, but the diff looks clean to me.
I wonder if @davidkpiano has a chance to take a look.

It generally looks good to me! 💯

Our test coverage isn't very good and there might be some regressions. But it's better to move forward than stopping. Let's merge.


add message for server endpoint

displays correct URLs both for running locally and when running
on aiida lab

@yakutovicha This requires the AIIDALAB_DOMAIN environment variable, which I've added in the latest version of the ansible scripts


Specify Mutation Per Type

will this work with mot also ?
I have constant mutant now i need to decide how many mutant i need  ??
for that type?

Hi @maulikhdave9601672767 . I'm not 100% sure that I understand the question. There is currently no way to specify how many mutant Stryker will generate per type. It will just generate as much as it can based on your code.
You can, however, exclude mutators: https://github.com/stryker-mutator/stryker/tree/epic/mutation-switching/packages/core#mutator

thanks for really quick reply.
i m using MOQ in unit test will stryker will work with that also?

yes, Stryker doesn't care about which specific moching framework or assertion framework you use. Which test runner are you using? Mocha, jest-node, karma en jest are supported.

great help


Movement values onDrag with scroll

Describe the bug
On the desktop where scroll isn't disabled dragging an item out of bounds causes the movement value to be incorrect and drift from the mouse.
Sandbox or Video
https://codesandbox.io/s/romantic-satoshi-z8ugn?file=/src/App.tsx
https://user-images.githubusercontent.com/3036610/126230258-1c9cfaa8-e8d9-44e8-b8f7-7f1edac05da1.mov
Information:

'@use-gesture/react'
Device: Desktop
OS: macOS BigSur
Browser: Safari

Checklist:

[x] I've read the documentation.
[x] If this is an issue with drag, I've tried setting touch-action: none to the draggable element.

I don't think this is a bug, I've looked through the docs and issues to try find a solution but I'm not able to understand what the problem is. I'd like to eventually control the scroll and move the draggable item up and down the page. Is it easy to fix? Could I get some pointers on what a solution would look like? Thanks!

The problem that you have is that selecting the text from the dragged item also triggers the browser scrolling. You should probably add user-select: none to your CSS to disable selecting the text on your dragged element.
This isn't a simple problem by any means AFAIK, the logic would be to add scrolling logic when your dragged element comes near the edges of the scrollable parent. If your element has absolute positioning, you'll probably have to compensate the scroll offset to keep your element under your mouse. Another tactic would be to use fixed positioning when the element is being dragged so that its positioning is independent from the scroll offset, but then you would have to recalculate the rest position when you remove the fixed positioning and perform a nice transition.
On this sort of complex usecases, I would look at using dedicated libs such as https://github.com/atlassian/react-beautiful-dnd or at least looking at how they do it internally.
Another way would be to try using framer-motion which has FLIP transitioning built-in, but you'd still have to handle the scroll logic on your end.

Thanks for the detailed response. Please feel free to close the issue. I'll update when I have a shareable demo.

I found some code you posted on a different issue for controlling the window scroll with react spring 😄. Modified it to use the api values to update the position and calculate the difference in height. It's a bit janky I think because of how I'm updating the scrollDiff var. Do you know how to make it smoother?
https://codesandbox.io/s/romantic-satoshi-z8ugn?file=/src/App.tsx
https://user-images.githubusercontent.com/3036610/126379479-7411e280-83e7-4e68-8494-baf33c238033.mov

I have the same issue with dragging and scrolling, but the solution with scrollDiff has the problem.
https://codesandbox.io/s/compassionate-rain-36ddxh
https://user-images.githubusercontent.com/20453923/156874637-f80d17ae-2bf7-4acb-90d6-0fbb2ed7b29d.mp4
It looks like we should add scrollDiff into movement value when calling next onDrag handler. But using memo is a weird path, I think so.
Have lib tricks for changing movement, distance at the next call nicer?


hssi: add sample app (#1605)

Signed-off-by: Tim Whisonant<EMAIL_ADDRESS>

Coverage decreased (-15.06%) to 67.154% when pulling 58f0e15b6c75bfca2de204d4cd2c18be6178be77 on feature/hssi into dabf8a822f3ffcaad6e1799ca1ae454e393ac6a2 on master.


translation: Data Analyst agent into Korean

What does this PR do?
this is PR presents the korean translation of Data analyst agent: get your data’s insights in the blink of an eye ✨ cookbook.

Who can review?
@jeongiin, @harheem, @boyunJang, @ahnjj, @SeungAhSon,@jun048098,@win2dvp21

@ahnjj  고맙습니다 once it's reviewed by another Korean speaker we can merge 🫰🏻

LGTM! 번역 감사합니다!

@ahnjj we just merged a Korean recipe, toctree and index md has a merge conflict. Can you resolve it? We can merge afterwards.

Sorry, another Korean recipe was merged, can you resolve again and we can merge this one
Also feel free to send a join request to this org.

Sorry, another Korean recipe was merged, can you resolve again and we can merge this one Also feel free to send a join request to this org.

Thank you for your help!
Since I've just resolved this, can you help with me to be merged?

@ahnjj if you can resolve the merge conflict we can merge
also don't forget to join this org: https://huggingface.co/huggingcooks


proxy-wasm support

What is the problem your feature solves, or the need it fulfills?
Proxy WASM is an spec that allows HTTP filters to be implemented in WASM (supported in Envoy and in-progress for OpenResty).
Describe the solution you'd like
Integration of proxy wasm to pingora to allow for filters built on this spec to operate.
Describe alternatives you've considered
n/a
Additional context

I'm looking for the same. It seems that a possible implementation may be wrapping a WASM Runtime inside ProxyHttp trait and forward events to WASM modules.
Unfortunately there is no TCK (yet) to probe that a proxy-wasm implementation works as expected.

This something the ISRG River project will work on. See https://www.memorysafety.org/blog/introducing-river/.

That announcement was well timed :)

A blocker for proxy-wasm support is body modification not being allowed.

It looks like the blocker issue with body modification is already solved
Do you have any plans to implement proxy-wasm in the near time?

looking forward to supporting proxy-wasm


Fix travis builds

The job log ends as follows:
tests/test_sources.py::TestISTAT::test_gh_75
77659
tests/test
77660
77661
The job exceeded the maximum log length, and has been terminated.
Hence, the test suite should be fixed.

Partially fixed by #108.

Fixed in #108


Implement multiple label

Add support for multiple labels in CREATE, MERGE and MATCH clause.
Important Notes:

Before merging, please rerun the workflow again. Any tests that were added after this branch was last updated will fail because this PR makes minor changes in how vertex and edge objects are output.

Update:

Base of this PR is changed to a new remote branch multiple_label_16, which is based off master.

@rafsun42 The second CREATE command has AB and C as labels but the relation for AB and _agr_AB_C was not created.
multi-label-PR-review=# CREATE EXTENSION age;
CREATE EXTENSION
multi-label-PR-review=# SET search_path=ag_catalog;
SET
multi-label-PR-review=# SELECT create_graph('graph');
NOTICE:  graph "graph" has been created
 create_graph
--------------

(1 row)

multi-label-PR-review=# SELECT * FROM cypher('graph', $$CREATE (x:A:B:C)$$) as (a agtype);
 a
---
(0 rows)

multi-label-PR-review=# \dt+ graph.*
                                            List of relations
 Schema |       Name       | Type  |   Owner    | Persistence | Access method |    Size    | Description
--------+------------------+-------+------------+-------------+---------------+------------+-------------
 graph  | A                | table | taha-linux | permanent   | heap          | 8192 bytes |
 graph  | B                | table | taha-linux | permanent   | heap          | 8192 bytes |
 graph  | C                | table | taha-linux | permanent   | heap          | 8192 bytes |
 graph  | _ag_label_edge   | table | taha-linux | permanent   | heap          | 8192 bytes |
 graph  | _ag_label_vertex | table | taha-linux | permanent   | heap          | 8192 bytes |
 graph  | _agr_ABC         | table | taha-linux | permanent   | heap          | 16 kB      |
(6 rows)

multi-label-PR-review=# SELECT * FROM cypher('graph', $$CREATE (x:AB:C)$$) as (a agtype);
 a
---
(0 rows)

multi-label-PR-review=# \dt+ graph.*
                                            List of relations
 Schema |       Name       | Type  |   Owner    | Persistence | Access method |    Size    | Description
--------+------------------+-------+------------+-------------+---------------+------------+-------------
 graph  | A                | table | taha-linux | permanent   | heap          | 8192 bytes |
 graph  | B                | table | taha-linux | permanent   | heap          | 8192 bytes |
 graph  | C                | table | taha-linux | permanent   | heap          | 8192 bytes |
 graph  | _ag_label_edge   | table | taha-linux | permanent   | heap          | 8192 bytes |
 graph  | _ag_label_vertex | table | taha-linux | permanent   | heap          | 8192 bytes |
 graph  | _agr_ABC         | table | taha-linux | permanent   | heap          | 16 kB      |
(6 rows)

@rafsun42 The second CREATE command has AB and C as labels but the relation for AB and _agr_AB_C was not created.

With merge it caused an assertion failure
multi-label-PR-review=# CREATE EXTENSION age;
CREATE EXTENSION
multi-label-PR-review=# SET search_path=ag_catalog;
SET
multi-label-PR-review=# SELECT create_graph('graph');
NOTICE:  graph "graph" has been created
 create_graph
--------------

(1 row)

multi-label-PR-review=# SELECT * FROM cypher('graph', $$CREATE (x:A:B:C)$$) as (a agtype);
 a
---
(0 rows)

multi-label-PR-review=# SELECT * FROM cypher('graph', $$MERGE (x:AB:C)$$) as (a agtype);
TRAP: failed Assert("IsA(sss, SubqueryScanState)"), File: "src/backend/executor/cypher_merge.c", Line: 312, PID: 42605
postgres: taha-linux multi-label-PR-review [local] SELECT(ExceptionalCondition+0x6e)[0x56187d565e11]
../postgres-16/pgsql/lib/age.so(+0x17d16)[0x7fb668ebdd16]
../postgres-16/pgsql/lib/age.so(+0x17fc7)[0x7fb668ebdfc7]

@MuhammadTahaNaveed Thanks for reporting this. The logic for generating intersection relation was shortsighted. It appends the individual label names together without any separator. So, both CREATE (:A:B:C) and CREATE (:AB:C) generates the same relation name _agr_ABC. The expectation is they should generate different relation name.
One solution can be using a special separator character and disallowing it in label names. For example, the % character  (it is already disallowed I believe). So, the intersection relations will be _agr_A%B%C and _agr_AB%C respectively.
What's your thoughts?

@MuhammadTahaNaveed Thanks for reporting this. The logic for generating intersection relation was shortsighted. It appends the individual label names together without any separator. So, both CREATE (:A:B:C) and CREATE (:AB:C) generates the same relation name _agr_ABC. The expectation is they should generate different relation name.
One solution can be using a special separator character and disallowing it in label names. For example, the % character  (it is already disallowed I believe). So, the intersection relations will be _agr_A%B%C and _agr_AB%C respectively.
What's your thoughts?

Yeah, I agree that there should be a seperator. Maybe hyphen(-) will be more appropriate than (%)? Hyphen is also not allowed in label names.

@MuhammadTahaNaveed Updated the PR to fix the issues.

@rafsun42 The PR has conflicts as well as not running the 7 checks for some reason.


Adding @cloudinary/ng package removes ng-reflect-* attributes

New issue for cloudinary/frontend-frameworks
Before proceeding, please update to the latest version and test if the issue persists
For which package is this issue?
@cloudinary/ng
Describe the issue in a sentence or two.
After I add the @cloudinary/ng package, the ng-reflect-* attributes throughout my client application are removed. It looks like the behavior probably originates from this PR, where prod mode is enabled: https://github.com/cloudinary/frontend-frameworks/pull/63
Issue Type (Can be multiple)
[ ] Build - Can’t install or import the SDK
[ ] Performance - Performance issues
[ ] Behaviour - Functions aren’t working as expected
[ ] Documentation - Inconsistency between the docs and behaviour
[ ] Incorrect Types
[x] Other (Specify) - unexpected side effects
Steps to reproduce
Import CloudinaryModule from @cloudinary/ng into app.module.ts
Error screenshots
Before importing CloudinaryModule:

After importing CloudinaryModule:

Browsers (if issue relates to UI, else ignore)
[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Other (Specify)
[x] All
Versions and Libraries (fill in the version numbers)
package SDK version
Node - 14.17.0
NPM - 6.14.13
Config Files (Please paste the following files if possible)
Package.json
{
"name": "test-cloudinary-ng",
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"watch": "ng build --watch --configuration development",
"test": "ng test"
},
"private": true,
"dependencies": {
"@angular/animations": "~13.2.0",
"@angular/common": "~13.2.0",
"@angular/compiler": "~13.2.0",
"@angular/core": "~13.2.0",
"@angular/forms": "~13.2.0",
"@angular/platform-browser": "~13.2.0",
"@angular/platform-browser-dynamic": "~13.2.0",
"@angular/router": "~13.2.0",
"@cloudinary/ng": "^1.1.0",
"@cloudinary/url-gen": "^1.6.0",
"rxjs": "~7.5.0",
"tslib": "^2.3.0",
"zone.js": "~0.11.4"
},
"devDependencies": {
"@angular-devkit/build-angular": "~13.2.4",
"@angular/cli": "~13.2.4",
"@angular/compiler-cli": "~13.2.0",
"@types/jasmine": "~3.10.0",
"@types/node": "^12.11.1",
"jasmine-core": "~4.0.0",
"karma": "~6.3.0",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage": "~2.1.0",
"karma-jasmine": "~4.0.0",
"karma-jasmine-html-reporter": "~1.7.0",
"typescript": "~4.5.2"
}
}
Repository
Here's a repo that reproduces the issue: https://github.com/nixallover/debug-cloudinary-ng/pull/1

Hi @nixallover,
We are checking right now; we will keep you posted on any insights.
Thanks

Awesome, thank you! Let me know if I can provide any more info.

Sure, no problem.

Oh, that's great news, thanks @momoip! I'll keep an eye out for the update 🎉

Sure.  I'll let you know once I hear back from our Dev team.  Thanks for the patience.

@nixallover Please see the latest release:)

HI @nixallover
Let us know if you have further questions about the release.


Fix delay in rename_error windows save loop, should be 100msec, not 1sec

Found this when I was rooting through all the uses of delay_usec in the codebase when doing the other PR, if this new behaviour breaks things somehow, at least now it does what it says it should be doing. (and waiting 1 second between each iteration seems like a long time)
related to #14339

Now that Godot 3.1 has been released, we only plan to cherry-pick critical bug fixes to the 3.0 branch, unless there is very strong support in favor of a specific non-critical issue. Removing cherrypick label for 3.0.


Issue with Extra Contexts and World Guard

Description
any attempt to permit a specific group to have any sort of permission to build in a world guard region (either adding the group to members, or owners of an area or adding the permission to that group specifically manually) Crashes my server once any block is actually broken, even blocks outside of that region once the player is in the region will result in a crash. the log is insanely long the console flips out for a few minutes every time it happens preventing me from obtaining most of it but i will get what i can
Reproduction Steps
Install luck perms
install world guard
install Extra contexts
Ensure Permissions are in place
Create a region
/rg addmember -w world test g:default
break a block as a default member within that region
wait a few seconds after no block drops
Expected Behaviour
Default player should receive item and the server should continue to work
Server Details
Spigot Latest Version
LuckPerms Version
v5.3.74
Logs and Configs
https://gist.github.com/6d78ef6182b28fb6e2c0d8bf08a41dd1#file-minecraft-crash-log
Extra Details
I Do have a lot of plugins that could be causing problems but i have nothing else related to permissions or block/region management and it seems to me that there is some sort of communication issue that is the problem between world guard and luck perms because i had a really hard time getting it to acknowledge luck perms groups existed at first and don't remember how i got that to work

As this issue may crash certain low-powered browsers, could I please ask you to copy the log into a GitHub gist, and send the link for the gist instead? Make sure to edit the issue to delete the log here and replace it with a link to the gist. Thanks!

can do thank you for giving me a heads up

The mininimum amount of plugins i was able to recreate this with was
DiscordSRV
ExtraContexts
GriefPrevention
Luckperms
MythicMobs
WorldEdit
WorldGuard
Was the error i got this time
https://gist.github.com/soupcoup/986101d843f8189a60ff85df40bbc3bb#file-gistfile1-txt

The way you described adding permissions originally is through the /rg command mentioned in the issue.  Make sure it's also enabled in the ExtraContexts config.


[4.x dev] Added support for handler-url and headers per job

See the discussion: https://github.com/stackkit/laravel-google-cloud-tasks-queue/discussions/137
The idea is that you can have the handler url defined per job, so the job can decide where this task must be handled (e.g. low performance or high performance containers).
Also, while we're at it, added the option to have task headers per job. Might be useful to have job specific headers, which can be picked up by the handler and act accordingly.
I'm looking forward to any feedback.

Thanks! I left some feedback. Let me know what you think.

Thanks! I left some feedback. Let me know what you think.

Thanks for the feedback!

Thanks for your work @aaajeetee!
As I understand, with this PR we would be able to add HasTaskHandlerUrl interface to our jobs and then implement taskHandlerUrl() to achieve queue based routing like this?:
public function taskHandlerUrl(): string
{
    return 'https://example.com/' . $this->queue;
}

Quite possibly extracting this to a trait we can reuse. However, I do not see the need for us to route individual jobs and forgetting to implement HasTaskHandlerUrl (human error) will lead us wondering why it doesn't work.
I think there is a simpler approach for our use case and I hope you'll consider it. For example, we could setup config like this
'cloudtasks' => [
    'handler'               => env('STACKKIT_CLOUD_TASKS_HANDLER', ''),
    'service_account_email' => env('STACKKIT_CLOUD_TASKS_SERVICE_EMAIL', ''),
    'signed_audience'       => env('STACKKIT_CLOUD_TASKS_SIGNED_AUDIENCE', true),
    // The default handler
    'handler'               => env('STACKKIT_CLOUD_TASKS_HANDLER'),

    // New config values
    'use_queue_based_routing' => env('STACKKIT_CLOUT_TASKS_USE_QUEUE_BASED_ROUTING', false),
    'queue_based_routing_prefix' => env('STACKKIT_CLOUT_TASKS_QUEUE_BASED_ROUTING_PREFIX', env('APP_URL')),
],

And then CloudTasksQueue::getHandler() could look like this:
public function getHandler(): string
{
    if ($this->config['use_queue_based_routing']) {
        return $this->config['queue_based_routing_prefix'] . $this->queue;
    }

    return Config::getHandler($this->config['handler']);
}

[!NOTE]
I wrote this by hand and haven't tested it. Perhaps building the route should happen in Config class which could ensure that use_queue_based_routing is a valid URL and would add a trailing / if it's missing one.

Thanks for your work @aaajeetee!
As I understand, with this PR we would be able to add HasTaskHandlerUrl interface to our jobs and then implement taskHandlerUrl() to achieve queue based routing like this?:
public function taskHandlerUrl(): string
{
    return 'https://example.com/' . $this->queue;
}

Quite possibly extracting this to a trait we can reuse. However, I do not see the need for us to route individual jobs and forgetting to implement HasTaskHandlerUrl (human error) will lead us wondering why it doesn't work.
I think there is a simpler approach for our use case and I hope you'll consider it. For example, we could setup config like this
'cloudtasks' => [
    'handler'               => env('STACKKIT_CLOUD_TASKS_HANDLER', ''),
    'service_account_email' => env('STACKKIT_CLOUD_TASKS_SERVICE_EMAIL', ''),
    'signed_audience'       => env('STACKKIT_CLOUD_TASKS_SIGNED_AUDIENCE', true),
    // The default handler
    'handler'               => env('STACKKIT_CLOUD_TASKS_HANDLER'),

    // New config values
    'use_queue_based_routing' => env('STACKKIT_CLOUT_TASKS_USE_QUEUE_BASED_ROUTING', false),
    'queue_based_routing_prefix' => env('STACKKIT_CLOUT_TASKS_QUEUE_BASED_ROUTING_PREFIX', env('APP_URL')),
],

And then CloudTasksQueue::getHandler() could look like this:
public function getHandler(): string
{
    if ($this->config['use_queue_based_routing']) {
        return $this->config['queue_based_routing_prefix'] . $this->queue;
    }

    return Config::getHandler($this->config['handler']);
}

Note
I wrote this by hand and haven't tested it. Perhaps building the route should happen in Config class which could ensure that use_queue_based_routing is a valid URL and would add a trailing / if it's missing one.

Thanks for your suggestion. I understand your use case and see that in your case the "url per job" would add unnessecary overhead in your application.
I'm happy to add this config as well, but that means there are 4 ways to get a handler url:

none (= fallback to current url)
"default" (= the default configured handler url)
per job
queue-based (+ prefix).

I am not sure if that is the way to go? I think there can be even more use cases, which in turn can lead to more config options.
Perhaps, if there are so many different use cases, why not allow a closure to be used in the handler url? The closure could get the current job as argument.
With this closure (and job), all above mentioned use cases can be implemented I guess. The important part is that (the right) argument(s) get passed to this closure.
I know the current version (v3) of the package supports closure as well, but it does not have any arguments. (I am currently using this closure in my project with a hacky workaround to have job-specific handler urls)
What do you think @marickvantuil and @Plytas ?

You are right. Supporting all these use cases is very convenient from package consumers perspective, but might turn out to be maintenance hell. I think ultimately the decision will have to be made by Stackkit team.
Perhaps we could open the customization in a Laravel'y way. We could add an ability to add this to your own service provider:
CloudTasks::configureHandlerUsing(function ($job): string {
    //perform whatever you need to perform and return task handler url
});

You are right. Supporting all these use cases is very convenient from package consumers perspective, but might turn out to be maintenance hell. I think ultimately the decision will have to be made by Stackkit team.
Perhaps we could open the customization in a Laravel'y way. We could add an ability to add this to your own service provider:
CloudTasks::configureHandlerUsing(function ($job): string {
    //perform whatever you need to perform and return task handler url
});

I like this the most to be honest, good suggestion.

@Plytas @aaajeetee Really like that idea as well!

So I've updated the code. I have added a (static) configureHandlerUrlUsing method on the CloudTasksQueue class. Let me know what you think of this.
If this is the road we want to go, do we want the same implementation for the headers (setTaskHeaders) method? Because now you can call 1 method statically and the other one "magically" via Queue::connection()->setTaskHeaders().
Also, if you have mixed queue connections in your application, I can see this going wrong ("call to undefined function setTaskHeaders on XYQueue" for example).

If this is the road we want to go, do we want the same implementation for the headers (setTaskHeaders) method?

Agreed, same implementation would be preferred. Thanks!

Apologies for the late reply, but I updated the code accordingly. Let me know what you think.

Looks good to me, thank you! I hope to release 4.x soon, I'm just finishing things up and doing some more testing.


Refactored Post Model

I removed the commentsNo column as that will be redundant to safe on the DB, rather it should be calculated on compute time, imagine a user deletes the comment, we would have to go back to the post DB and delete too & many other drawbacks that will affect processing time.
Also changed the default of a post to be published, because that's what we want when I user hits the button to publish, we only save as a draft when a user clicks on draft or enables it, in that scenario we just add to the req body (status: Draft).

I removed the commentsNo column as that will be redundant to safe on the DB, rather it should be calculated on compute time, imagine a user deletes the comment, we would have to go back to the post DB and delete too & many other drawbacks that will affect processing time.
Also changed the default of a post to be published, because that's what we want when I user hits the button to publish, we only save as a draft when a user clicks on draft or enables it, in that scenario we just add to the req body (status: Draft).

the commentsNo automatically checks the amount of comments concerning that post so if one its deleted it will update it, i haven't added that yet it will  check the comment.findAll({where:{postId:thisParticularPost}}) and get the length , so it updates automatically


Fannie Mae Historical Loan Credit Performance Data

What dataset are you requesting?
US residential mortgage perforamance dataset from Fannie Mae Data Dynamics.

Here the Multifamily dataset
here the Single Family dataset

Is this open data?
No, currently available under Royalty-free data license
What is the use case for this dataset?
In the context of FINOS TechSprint 2024, the goal is to develop a proof-of-value (POV) for the business and proof-of-concept (POC) for the technological feasibility that simulates the effects of physical risk models and transition risk models on market risk and credit risk in trading activities, taking as the initial example a securitised portfolio of mortgages (MBS). More information here https://github.com/finos/traderX/discussions/191
Which organization produces the dataset?
Fannie Mae
Which format is the data in?
Refer to the links above
Which format would you like the data in?
TBD
How often does the data update?
Here the link to the refresh calendar
Who else would use this data ?
Mortgage Back Securities (MBS)  are estimated to be around $10 to $12 trillion in total value. This data is relevant for banks, insurance companies and asset managers. The data can be used to build climate-focused applications and AI models, such as predictive and anomaly detection models, that can assess the climate risk exposure of borrowers more accurately. By analyzing patterns in loan repayments, borrower behavior, and climate-related factors (such as extreme weather events or carbon footprint), these models can identify early signs of financial distress driven by climate risks.
Other Comments
POC:

David Kelly (BIP) is TechSprint Use Case Project Lead
John Mark Walker (Fannie Mae) is FINOS AI Strategic Initiative Executive Sponsor

Others:
This issue is part of FINOS LLM Exploration Project and aims to validate the fit-for-purpose of OS-C Data Commons (and in particular Data Request) as "A comprehensive data contribution framework document that financial institutions can follow to contribute data securely and efficiently to an open financial dataset." More info here (slide 17)

Thanks for creating this record of interest.  To set expectations, this data request form creates a potential work item that the OS-Climate community can prioritize, but the OS-Climate project does not make any promises that it will onboard the data.
@ericbroda copying in Eric Broda, who may have some advice on such data might be federated via the Data Bazaar.  It would still require somebody to take ownership of doing the federation, but the Data Bazaar metadata and management might present a more favorable ROI equation than simplying trying to onboard the data without such structural/architectural support.


MacOS native title frequently misaligned

I've been seeing this come up pretty recently in the past couple weeks.

/duplicate https://github.com/microsoft/vscode/issues/106001


#12 Map::remove_entry() and Map::get_key_value()

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 3min)


ASoC: Remove errorMsg and replace it with err type

There is a function errorMsg which prints to the stderr stream when there is an error. In production open must never print to stderr because it may conflict with other things present in the product, and can cause debugging to become very hard.
For example, the below code can be turned into:
// roundOffTitleColor rounds off 24 bit Color to the terminals maximum color capacity for Title.
func (b Box) roundOffTitleColor(col color.RGBColor, title string) string {
	switch detectTerminalColor() {
	case terminfo.ColorLevelNone:
		errorMsg("[warning]: terminal does not support colors, using no effects")
		return title
	case terminfo.ColorLevelMillions:
		return col.Sprint(title)
	default:
		return col.C256().Sprint(title)
	}
}

// roundOffTitleColor rounds off 24 bit Color to the terminals maximum color capacity for Title.
func (b Box) roundOffTitleColor(col color.RGBColor, title string) (string, err) {
	switch detectTerminalColor() {
	case terminfo.ColorLevelNone:
		return title, errors.New("terminal does not support colors")
	case terminfo.ColorLevelMillions:
		return col.Sprint(title), nil
	default:
		return col.C256().Sprint(title), nil
	}
}

then, do the changes as per the need.
This is a very breaking change so this has to be some with cautious.

Hey @Delta456, Can I work on this?

Hey @Delta456, Can I work on this?

Sure

Hye @Delta456, I've created the PR, will you please check and tell me if this is correct or not?


domainPartition not respected in new scratch orgs

Summary
Setting the domainPartition to "none" in the project-scratch.def does not disable the "Use partitioned domains" checkbox/setting.
From what I can see in the docs I should be able to influence this setting with this config;
   "settings": {
      "myDomainSettings": {
          "domainPartition": "none"
        }
   }

Steps To Reproduce:

Set the "myDomainSettings" as per above.
Create a new scratch org

Expected result
A new scratch org is created with the "Use partitioned domains" checkbox un-checked, and there to be no .scratch. in the domain URL.
Actual result
A new scratch org is created with the "Use partitioned domains" checkbox checked, and the domain URL includes .scratch..
System Information

Which shell/terminal are you using? bash

If you are using sfdx

Run sfdx version --verbose --json

If you are using sf

Run sf version --verbose --json

{
  "cliVersion": "sfdx-cli/7.168.0",
  "architecture": "linux-x64",
  "nodeVersion": "node-v16.14.2",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 1.3.0 (core)",
    "@oclif/plugin-commands 2.2.0 (core)",
    "@oclif/plugin-help 5.1.12 (core)",
    "@oclif/plugin-not-found 2.3.1 (core)",
    "@oclif/plugin-plugins 2.1.0 (core)",
    "@oclif/plugin-update 3.0.0 (core)",
    "@oclif/plugin-version 1.1.2 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.4 (core)",
    "@oclif/plugin-which 2.1.0 (core)",
    "alias 2.1.0 (core)",
    "apex 1.2.0 (core)",
    "auth 2.2.3 (core)",
    "community 2.0.1 (core)",
    "config 1.4.19 (core)",
    "custom-metadata 2.0.0 (core)",
    "data 2.1.2 (core)",
    "generator 2.0.2 (core)",
    "info 2.0.1 (core)",
    "limits 2.0.1 (core)",
    "org 2.2.0 (core)",
    "packaging 1.6.0 (core)",
    "schema 2.1.1 (core)",
    "signups 1.2.0 (core)",
    "source 2.0.13 (core)",
    "telemetry 2.0.0 (core)",
    "templates 55.1.0 (core)",
    "trust 2.0.3 (core)",
    "user 2.1.0 (core)",
    "@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
    "@salesforce/sfdx-scanner 2.13.8 (user)",
    "salesforce-alm 54.8.1 (core)",
    "sf-package-version-checker 0.0.0 (link) /home/todd/projects/mc/sf-package-version-checker",
    "sfdx-plugin-mobilecaddy 0.0.1 (link) /home/todd/projects/mc/sfdx-plugin-mobilecaddy",
    "sfignore 0.0.1 (user)"
  ],
  "osVersion": "Linux 5.14.0-1054-oem",
  "shell": "bash",
  "rootPath": "/home/todd/.nvm/versions/node/v16.14.2/lib/node_modules/sfdx-cli"
}

I've asked the domain to find out what's expected here.  It's either a bug, or the docs haven't been updated (see how sboxes don't support none ?  Maybe scratch orgs are like that, too.
I'll let you know what I find out.

Thanks for the quick response @mshanemc, I really appreciate it.
And just to clarify we can un-check the "Use partitioned domains" checkbox via the UI once the scratch has been created.

Ahh, I totally sped right past this part: This field is read-only in the API.

Thanks @mshanemc , I had missed that entirely too.
I know this issue is now rightly closed, but wondering if you know of why this might be read-only or if there's scope to modify this (could I perhaps create an Idea)?

You could definitely create an idea.
pure speculation: the ability to toggle these in the UI is available for the transition period, and that longer-term these partitions are just on (similar to how mydomain works on any new orgs...you can't undo that).


Term 2 Simulator crashes on macOS

Hi,
I am trying to run "Term 2 Simulator v1.45" on MacOS high sierra. The app crashes every time. I have also tried the lower version of the simulator, but no luck.
Any suggestions?
Thank you.

Just to inform:
Downloaded term2 v1.45 and ran it successfully on High Sierra.
I tried with highest screen resolution and highest graphics.
However, the application seems to be using up a lot of my CPU. With medium screen resolution and highest graphics my build-in fan started making considerable noise already.
I suggest you try with lowest settings as well.
Furthermore, I assume it requires some c++ compiler and perhaps other dependencies on your computer (havent read through the project yet though). Are you aware of anything that might not be set up correctly on your local mac?


Support AfNetworking 4.0

ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of new apps that use UIWebView APIs starting from April 2020. See https://developer.apple.com/documentation/uikit/uiwebview for more information.
After you’ve corrected the issues, you can upload a new binary to App Store Connect.
Best regards,
The App Store Team

Quick update as of now:
ITMS-90809: Deprecated API Usage - App updates that use UIWebView will no longer be accepted as of December 2020. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).

I found workoround for this issue. put this code on podfile
pre_install do |installer|
puts 'pre_install begin....'
dir_af = File.join(installer.sandbox.pod_dir('AFNetworking'), 'UIKit+AFNetworking')
Dir.foreach(dir_af) {|x|
real_path = File.join(dir_af, x)
if (!File.directory?(real_path) && File.exists?(real_path))
if((x.start_with?('UIWebView') || x == 'UIKit+AFNetworking.h'))
File.delete(real_path)
puts 'delete:'+ x
end
end
}
puts 'end pre_install.'
end


No error message when when Rabbit MQ authentication fails

When Sensu 0.20.3 server fails to log on to Rabbit MQ it does not produce an adequate error message in the logs to debug the issue. It just says "unsubscribing", even with LOG_LEVEL=debug
from sensu-server.log:
{"timestamp":"2015-09-22T03:58:53.442768+0000","level":"debug","message":"subscribing to keepalives"}
{"timestamp":"2015-09-22T03:58:53.443006+0000","level":"debug","message":"subscribing to results"}
{"timestamp":"2015-09-22T03:58:53.445557+0000","level":"warn","message":"reconnecting to transport"}
{"timestamp":"2015-09-22T03:58:53.445668+0000","level":"warn","message":"unsubscribing from keepalive and result queues"}
{"timestamp":"2015-09-22T03:58:53.445743+0000","level":"debug","message":"not currently the leader"}

@dkamenov the AMQP protocol is not very friendly as far as error reporting and messages, we can only guess if a connection failure is due to authentication. The AMQP lib does a best effort to determine when the failure occurred, during the connection process.

Perhaps that is true (I am not familiar with the protocol), but it looks like sensu knows when it can't bind to the queues, even if it does not know exactly why. Maybe a more descriptive error message, e.g "Could not bind to queues, check Rabbit MQ connection parameters". "Unsubscribing from queues" is just plain misleading when it couldn't subscribe in the first place.
In my case, I had installed sensu and dependencies on Amazon EC2, captured an AMI from that and spun up a new VM. On the new VM, the existing Rabbit MQ config was invalid (depends on hostname or something like that) and it wouldn't subscribe. As a workaround, I am adding the vhost/queue creation/set_permissions to the startup script

I spent way too long debugging an issue because of this. Had to use strace to see the "authentication failure" message being returned from RabbitMQ.

Hi @anlutro, I'm sorry to hear that you've spent so much time diagnosing RabbitMQ connection issues. We've just recently released Sensu 0.24 which includes upstream changes which should provide more context around AMQP connection errors. See discussion in https://github.com/sensu/sensu/issues/842 for more detail.
I think there's still some work to be done here however, as those new errors aren't logged. I've opened sensu/sensu-transport#30 to see if we can improve this situation.

@anlutro @dkamenov I've created PR sensu/sensu-transport#34 to address this issue. If you can try it and report back feedback that'd be great.

Additional logging implemented in sensu/sensu-transport#34 will ship in Sensu 0.27

0.27.0-1 is in the unstable repositories, it fixes this issue. Will soon be promoted to stable.


Create add_dataset.rst

What does this implement/fix? Explain your changes.
Adds a section in the developers' guide for contributing new datasets to sktime

Now merged - thanks @Riyabelle25 🎉


Apostrophes in wordlists

The vocab RPG game is awesome, thanks btw. When RPGing on iOS, the default apostrophe key on the English keyboard doesn't register as the "correct" one. Example for won't here.
When entering the neutral vertical apostrophe via long-press in iOS, the answer is validated as correct.
I'm never worked in typescript but is possible to wrap either the answer value or input value with a function that fixes weird apostrophe entries?
        // Setup answer input
        const answer = this.add.dom(x, VocabRPGGame.HEIGHT - 30).createFromCache("answer_input")
        const answerField = document.getElementById("answerField") as HTMLInputElement
        const checkAnswer = () => {
            const input: string = answerField.value.trim()
            if (!input) return

            // Check the answer
            let correct = false
            if (Array.isArray(this.word.en)) {
                // There's multiple correct answers, see if it matches any of them
                if (this.word.en.includes(input)) correct = true
            } else if (this.word.en == input) {
                correct = true
            }

The apostrophe in the Japanese keyboard is oddly slanted -- maybe this trips the validation function also.

I have added a few character replacements in 944b6d633cdd0725d187cba0d64330546530fe8f.
The changes should be live, let me know if there are still problems 🙂

Awesome, thanks!


PARQUET-919: Account for ARROW-683 changes, but make no functional changes. Set PARQUET_ARROW=on by default

Bumped the Arrow version

green build: https://travis-ci.org/wesm/parquet-cpp


HW raid smart check and exim queue check

SMART check for MegaCLI hardware RAID
Check for exim mail queue size

@kepes @kovvik  Can you take a look at the Travis issues please, then I will take a look at this.
Thanks!


Rotate: Wrapping the rotate removal under a try-catch block.

The original code would raise an OperationError is the backup path doesn't exist. This is not the only reason a rmtree would fail, insufficient permissions, invalid SELinux contexts, etc.
This commit wraps the rmtree functionality in a try-catch block to catch and log any exceptions that may happen.

LGTM, thanks @corey-hammerton


upgrade_oh_my_zsh marked as deprecated

It seems that the Oh My Zsh community decided to introduce a new omz command to centralize OMZ-related actions and moved the update mechanism to it: https://github.com/ohmyzsh/ohmyzsh/commit/3935ccce647c722bcfdaa771b01613079db20935. So now, when using this plugin's upgrade_ohl_my_zsh command which calls the old upgrade_oh_my_zsh function, it displays this:

Maybe consider replacing the call to the deprecated command with the new omz update?
Cheers.

Done. Thank you for the heads up!


[traffic-gen-in-vm] Refactor TRex client

Currently, there is a dedicated file to start the TRex service.
Consolidate all the TRex functionality under trex.Client.
Reorder the exported methods in the following order:

StartServer
WaitForServerToBeReady
ClearStats
StartTraffic
GetPortStats

Tested against an OpenShift Virtualization 4.14 cluster.

Tested against an OpenShift Virtualization 4.14 cluster.


Sign up citizen UI

Dev Summary

There weren't any back buttons in the mocks but they seem necessary

Test Plan

repro steps:

localhost:3000
click X button
expected:

Resources

stackoverflow is cool

@jonathanchuangcodes re: your standup comments (from last week 😞 sorry i'm late on this reply)

back buttons: just add em in yourself for now, maybe just grouped with the other skip and next buttons, so in line and right aligned with them

but also, side note, i don't think we want a skip button on the location page at least

re: https://react-svgr.com/ go for it and give it a try!!


typos in mnist example

I have some very small suggestions for cosmetically improving this example:
https://github.com/google/flax/blob/master/linen_examples/mnist/train.py

line 31, 122: onp -> np

line 55: init_shape = jnp.ones((1, 28, 28, 1), jnp.float32) is not a shape tuple, it's a tensor of data.
Consider renaming to init_val' or input_val`.

line 131.  eval_model(model, test_ds):. The model argument is actually the dict of parameters, not a module.
Consider renaming to params to be consistent with eval_step.

This will be fixed by #829

This will be fixed by #829