fix(module:tabset): tab-link should be disabled

close #5543
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[ ] No

Other information

@danranVm  👀 新的实现中用的 <a *nzTabLink> 获取不到 nativeElement 了，现在在 #5759 中使用样式修复了


Password reset emails not functioning

PHP's mail() function is not working inside the container, probably because sendmail is not installed. I tried installing sendmail, but then sending mail just hangs. Will need some investigation on what the best course of action is here.

Will soon be a non-issue in Koken 0.21. More info soon.

Sorry, how was this fixed or resolved?

Sorry, how was this fixed or resolved?

Sorry, how was this fixed or resolved?

Koken seems not to be developed anymore, so either this issue has been resolved (current version is 0.22.24) or it will never be. NetObjects (who aquired Koken in 2015) seems to be completely dead.

Sorry, how was this fixed or resolved?

Koken seems not to be developed anymore, so either this issue has been resolved (current version is 0.22.24) or it will never be. NetObjects (who aquired Koken in 2015) seems to be completely dead.

@nicokaiser oh wow, so that explains why the docker hasn't been touched in four years.   The software is still useful.  This is too bad.

@nicokaiser oh wow, so that explains why the docker hasn't been touched in four years.   The software is still useful.  This is too bad.


remove default font loading from styles.scss

The default font is not always needed. Therefore, we spend extra time downloading it and in some cases we get CSP errors.

https://github.com/gravity-ui/page-constructor/pull/1078


Clarify outside immediate team PRs

The requirement for occasionally reviewing pull requests outside of a developer's immediate team is quite dependent on how teams are structured, for example it might be easier for someone on a reader revenue team to do an inter-team review than someone on editorial tools.
I think what this criteria was aiming to value is the ability to unblock delivery by providing useful PR reviews in contexts that are new to them, and have reworded it accordingly.

Is my assumption that this is the the aim is correct?
Does the new wording adequately covers this aim?

Looks good to me and I answer positively to your two questions


TLS should do cert verification by default

Change Envoy to reject upstream TLS unless
a) Valid cert chain is on by default
b) At least one of a) cert pinning, b) matching a specific SAN, c) auto SAN, etc. is configured.
or
a new bool allow_dangerous_tls_without_certificate_validation is set
See discussion on https://github.com/envoyproxy/envoy/issues/17700
https://github.com/envoyproxy/envoy/pull/18033

Sometimes for external server, this flag is useful at lease for testing purpose


color.py example

The example pytradfri/examples/example_color.py should probably use xyY colors instead of XYZ.  At least, for me, it gives a better representation of the color I want.  Note also that r,g,b all range from 0.0 to 1.0 by default, for colormath (I think).
Below is a modified example demonstrating some of this... sorry if it has been solved before.
#!/usr/bin/env python3
"""
This is an example of how the pytradfri-library can be used.
To run the script, do the following:
$ pip3 install pytradfri
$ Download this file (example_sync.py)
$ python3 example_sync.py
Where  is the address to your IKEA gateway. The first time
running you will be asked to input the 'Security Code' found on
the back of your IKEA gateway.
"""
from pytradfri import Gateway
from pytradfri.api.libcoap_api import APIFactory
from pytradfri.error import PytradfriError
from pytradfri.util import load_json, save_json
import uuid
import argparse
import threading
import time
defaultip='<IP_ADDRESS>'
CONFIG_FILE = 'tradfri_standalone_psk.conf'
parser = argparse.ArgumentParser()
parser.add_argument('host', metavar='IP', type=str,
help='IP Address of your Tradfri gateway',
default=defaultip, nargs='?')
parser.add_argument('-K', '--key', dest='key', required=False,
help='Security code found on your Tradfri gateway')
args = parser.parse_args()
if args.host not in load_json(CONFIG_FILE) and args.key is None:
print("Please provide the 'Security Code' on the back of your "
"Tradfri gateway:", end=" ")
key = input().strip()
if len(key) != 16:
raise PytradfriError("Invalid 'Security Code' provided.")
else:
args.key = key
def observe(api, device):
def callback(updated_device):
light = updated_device.light_control.lights[0]
#print("Received message for: %s" % light)
def err_callback(err):
    print(err)

def worker():
    api(device.observe(callback, err_callback, duration=120))

threading.Thread(target=worker, daemon=True).start()
print('Sleeping to start observation task')
time.sleep(1)

conf = load_json(CONFIG_FILE)
try:
identity = conf[args.host].get('identity')
psk = conf[args.host].get('key')
api_factory = APIFactory(host=args.host, psk_id=identity, psk=psk)
except KeyError:
identity = uuid.uuid4().hex
api_factory = APIFactory(host=args.host, psk_id=identity)
try:
    psk = api_factory.generate_psk(args.key)
    print('Generated PSK: ', psk)

    conf[args.host] = {'identity': identity,
                           'key': psk}
    save_json(CONFIG_FILE, conf)
except AttributeError:
    raise PytradfriError("Please provide the 'Security Code' on the "
                         "back of your Tradfri gateway using the "
                         "-K flag.")

api = api_factory.request
gateway = Gateway()
devices_command = gateway.get_devices()
devices_commands = api(devices_command)
devices = api(devices_commands)
lights = [dev for dev in devices if dev.has_light_control]
Print all lights
print(lights)
if lights:
light = lights[0]
else:
print("No lights found!")
light = None
if light:
observe(api, light)
# Example 1: checks state of the light (true=on)
print("State: {}".format(light.light_control.lights[0].state))

# Example 2: get dimmer level of the light
print("Dimmer: {}".format(light.light_control.lights[0].dimmer))

# Example 3: What is the name of the light
print("Name: {}".format(light.name))

# Check that the light can set color
print("Color: {}".format(light.light_control.can_set_color))

# Example 4: Set the light level of the light
dim_command = light.light_control.set_dimmer(254)
api(dim_command)

on_command = light.light_control.set_state(True)
api(on_command)

from colormath.color_conversions import convert_color
from colormath.color_objects import sRGBColor, XYZColor, xyYColor
def xyY_from_rgb(r,g,b):
xyY = convert_color(sRGBColor(r,g,b),xyYColor)
return xyY.xyy_x, xyY.xyy_y, xyY.xyy_Y
def set_color(api,light,r,g,b):
x,y,Y = xyY_from_rgb(r,g,b)
intx = int(x * 65535)
inty = int(y * 65535)
xy_command = light.light_control.set_xy_color(intx,inty)
api(xy_command)
set_color(api,light,1.0,0.0,0.0)
time.sleep(1)
set_color(api,light,0.0,1.0,0.0)
time.sleep(1)
set_color(api,light,0.0,0.0,1.0)
time.sleep(1)
set_color(api,light,1.0,1.0,1.0)
time.sleep(1)
def rainbow(api,light):
r,g,b = 1.0,0.0,0.0
set_color(api,light,r,g,b)
while g < 1.0:
g = g + 0.01
set_color(api,light,r,g,b)
set_color(api,light,r,g,b)
while r > 0.0:
r = r - 0.01
set_color(api,light,r,g,b)
set_color(api,light,r,g,b)
while b < 1.0:
b = b + 0.01
set_color(api,light,r,g,b)
set_color(api,light,r,g,b)
while g > 0.0:
g = g - 0.01
set_color(api,light,r,g,b)
set_color(api,light,r,g,b)
while r < 1.0:
r = r + 0.01
set_color(api,light,r,g,b)
set_color(api,light,r,g,b)
while b > 0.0:
b = b - 0.01
set_color(api,light,r,g,b)
set_color(api,light,r,g,b)
rainbow(api,light)
def bicolor(api,light):
colors = ((0.0,0.0,1.0),(1.0,1.0,1.0))
numcycles = 10
timecycle = 1
off_command = light.light_control.set_state(False)
api(off_command)
time.sleep(timecycle)

r,g,b = colors[0]
set_color(api,light,r,g,b)
on_command = light.light_control.set_state(True)
api(on_command)
for _ in range(numcycles):
    for color in colors:
        r,g,b = color
        set_color(api,light,r,g,b)
        time.sleep(timecycle)

bicolor(api,light)
off_command = light.light_control.set_state(False)
api(off_command)
Where are you using pytradfri (eg stand-alone, Home Assistant etc)
Version of pytradfri
Expected behaviour
Actual behaviour

We've struggled quite a bit to get colors to work and at one point decided to move color setting calculations out from the main living. We put some examples in the file you refer to just to show users how it could be done.
Please feel free to submit a PR suggesting your examples to the file!

As @ggravlingen mentioned we don't want to do any colour math in the project - if a downstream project wishes to do so, that's fine. But the accepted formats are those accepted by the gateway, which this project models.

OK, I'll go for the pull request if I feel I can add anything else.
Jeff
On Mon, Jul 16, 2018 at 2:47 AM Patrik<EMAIL_ADDRESS>wrote:

We've struggled quite a bit to get colors to work and at one point decided
to move color setting calculations out from the main living. We put some
examples in the file you refer to just to show users how it could be done.
Please feel free to submit a PR suggesting your examples to the file!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ggravlingen/pytradfri/issues/175#issuecomment-405170542,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACnADzoI7mWZleO5vEZOPjcV14OXAbgTks5uHET2gaJpZM4VGlx2
.

--
Prof. Jeffery W. Martin
Canada Research Chair (Tier 1)
Physics Department
University of Winnipeg
515 Portage Avenue
Winnipeg, MB R3B 2E9 CANADA
Adjunct Professor
Department of Physics and Astronomy
University of Manitoba
Winnipeg, MB R3T 2N2 CANADA
Visiting Scientist
TRIUMF
4004 Wesbrook Mall
Vancouver, BC V6T 2A3 CANADA
Phone:<PHONE_NUMBER> x6198 (in Vancouver);<PHONE_NUMBER> (in Winnipeg)
URL:  http://nuclear.uwinnipeg.ca
Local office at TRIUMF:  Trailer A, Room 10.

OK, closing this pending a potential PR.


prose.sh: image URL with suffix still requires additional ext: options

i.e.
/photo.jpg/ext:jpg

otherwise plain /photo.jpg only gives webp image.
btw: the image I uploaded was photo.jpg (with suffix).

Thanks for the bug report, this should be fixed now.  Could you please confirm on your end?

Thanks for the quick fix, I can confirm it's working in above cases.
One small issue I noticed with extensionless on Safari and macOS Catalina (version 10.15):

request

:method: GET
:scheme: https
:authority: bower.sh
:path: /profile
Accept: image/png,image/svg+xml,image/*;q=0.8,video/*;q=0.8,*/*;q=0.5
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6.1 Safari/605.1.15

response

:status: 200
Content-Type: image/webp

from MDN:

[!NOTE]
On Safari for macOS, WebP support depends on both Safari and macOS versions. You need Safari 14 or later as well as macOS Big Sur (11) or a more recent version. ^mdn

@neurosnap below is screen shot taken from Safari (15.6) on macOS Catalina (10.15) for example:


Add wayland to DEPENDS even without vulkan

When not using vulkan wayland is still needed to build flutter-engine.
This should fix #278

Haven't had time to test, but I believe the Wayland dependency is related to impeller option.  If this is the case I would prefer the dependency added to the package config flag responsible

Impeller is only activated by default  if Vulkan is in DISTRO_FEATURES, isn't it?


Do FLAP find_package only if BUILD_WITH_FLAP is on

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Trivial change (affects only documentation or cleanup)

Checklist:

[ ] I have tested this change with a run of GEOSgcm (if non-trivial)
[ ] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[ ] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

I need to fill this out and test, but I don't want to forget...

Closing as superseded by #611


ROS Configuration Issues for multiple sensors.

Hello,
We are a group working on an autonomous driving golf cart at RIT and are currently trying to test our bag file with Cartographer and have had no success. We get an error in RVIZ shown below,
Fixed Frame
No tf data. Actual error: Fixed Frame [map] does not exist.
We are using /tf and have configure the .lua file to what we believed to be correct but haven't been able to get Cartographer to run using our .bag file. We have ran through the demos provided by Cartographer and have been studying the Cartographer documentation but haven't been able to resolve the issue. Below are links to a Git repository and an image of the tf view frames. We believe that the error is caused by our system having a loam_gps node in between map and odom but haven't been able to adjust things properly to resolve the issue.
The system uses a Velodyne Puck (16 channel) and single channel velodyne along with a monocular camera.
Thank you for your assistance.
Below is a zip file containing the .lua file, and two launch files,
lua.zip
The bag file is located here:
https://drive.google.com/file/d/13IlYQUuf5hX2iJoB6IUzbK5iNJdSDTgw/view?usp=sharing
tf frames:

I can't help with your custom setup, but I would recommend to start with a very simple configuration without this Loam frame and then gradually add more complexity to find out what causes issues.


Timeout when connecting to Quilt + QSL server behind Velocity proxy

I'm trying to run a Quilt server behind Velocity.
When QSL is installed on the Quilt server, attempting to connect (through Velocity) results in the client hanging on the "Joining game..." screen for a few moments, followed by a "read timed out" error.
("the client" being a vanilla Minecraft client)
What does work:

Connecting to the Quilt server directly (bypassing Velocity)
Connecting through Velocity without QSL installed on the backend
Connecting through Velocity to an otherwise identical Fabric server (substituting QSL+QFAPI for the Fabric API)

Fabric Loader: fabric-server-mc.1.19.2-loader.0.14.10-launcher.0.11.1.jar
Fabric API: fabric-api-0.67.1+1.19.2.jar

The only thing that stands out to me in the logs is the following, printed to the client log when attempting to connect to the server:
[20:04:14] [Render thread/WARN]: Unknown custom packed identifier: qsl:registry_sync/handshake

Minecraft: 1.19.2
QSL: qfapi-4.0.0-beta.21_qsl-3.0.0-beta.21_fapi-0.67.0_mc-1.19.2.jar
Quilt Loader: 0.18.1-beta.16 (same with 0.17.6)
Velocity: 3.1.2-SNAPSHOT (git-2d072151-b185)

Client log: https://mclo.gs/2nCYdNG
Quilt server log: https://mclo.gs/EI40G0x
Velocity log: https://mclo.gs/dXmIbRM

Update:
The same configuration under Minecraft 1.18.2 works fine!?
QFAPI: qfapi-1.0.0-beta.28_qsl-1.1.0-beta.26_fapi-0.67.0_mc-1.18.2.jar

I thought https://github.com/QuiltMC/quilted-fabric-api/commit/d92a7d9e91bfea24b69733653cf69f44a7cf0a1e might have something to do with this issue, but qfapi-4.0.0-beta.1_qsl-3.0.0-beta.2_fapi-0.58.5_mc-1.19.1.jar (for 1.19.1), which includes the commit, also works fine!?
Frustrating!!!

I had the same issue while running this on my server, a specific qfapi version "fixed" it, with the main problem being that it locks me on updating mods on my server.
qfapi-4.0.0-beta.7_qsl-3.0.0-beta.10_fapi-0.59.0_mc-1.19.2.jar (as seen at https://github.com/roridev/soberana-server-mods/commit/61b60b2e426b1afe9b61607fda8073c401b86d1a)
I expect that a change in fabric api prior 0.59 broke compatibility with Velocity.

I can confirm that qfapi-4.0.0-beta.7_qsl-3.0.0-beta.10_fapi-0.59.0_mc-1.19.2.jar works, while the next (published) release, qfapi-4.0.0-beta.8_qsl-3.0.0-beta.13_fapi-0.59.0_mc-1.19.2.jar, does not.
Here's a diff between the two versions:
https://github.com/QuiltMC/quilted-fabric-api/compare/4.0.0-beta.7+0.59.0-1.19.2...4.0.0-beta.8+0.59.0-1.19.2
I suspect the issue has something to do with https://github.com/QuiltMC/quilted-fabric-api/commit/1fa160819ba22769bf1be1aa399ed7d759fd6e0b and/or QuiltedRegistrySync.java... but what do I know?

In theory Quilt's registry synchronization was built to be compatible with proxies, but I guess we can't exclude the possibility that something went wrong.

This is probably known, but qfapi-4.0.0-beta.23_qsl-3.0.0-beta.22_fapi-0.68.0_mc-1.19.2.jar, the (current) latest release of QFAPI, does not work :(
I would test 1.19.3, but Velocity doesn't support it quite yet, so no such luck...

Hmm, this issue is probably better-suited for the quilt-standard-libraries issue tracker, but I don't know how to move issues 🤷♀

This seems to point to registry sync but I think I'd like a confirmation that it is indeed caused by QSL alone and not QFAPI before moving the issue.
If someone can grab the test mod JAR of off QSL's GitHub Actions runs and test that would be appreciated!

This action? https://github.com/QuiltMC/quilt-standard-libraries/actions/runs/3653399966
I feel like I may have done something wrong...
https://gist.github.com/unilock/02e845517fea20fa7a212272c3d28109
(This is with only qsl-4.0.0-beta.2+1.19.3-testmod.jar in the mods folder. I also tried with all the libs from the build added as well, but ran into the same error.)

I think your error is most likely a Quilt Loader issue, try updating it?
I also know that on Fabric to make Velocity work well an additional mod was required on the servers iirc

That was on the latest version, unfortunately. Unless there's something newer than 0.18.1-beta.23?
Maybe you're thinking of FabricProxy-Lite? That (should) only be required when Velocity is set to "modern forwarding" mode, which I've disabled for the sake of testing.

Unfortunately, the issue still exists in Minecraft 1.19.3, Quilt Loader 0.18.1-beta.58, and qfapi-5.0.0-alpha.9_qsl-4.0.0-beta.5_fapi-0.72.0_mc-1.19.3.jar :(
This time, however! I was able to get the QSL test mod up and running. (from this action)
I recorded two logs from a Minecraft 1.19.3 / Quilt Loader 0.18.1-beta.58 server with only that mod; one in which I connected to the Quilt server through Velocity, and the other in which I connected directly.
With Velocity
Without Velocity
So I guess it is a QSL issue after all?

It is certainly a qsl issue.
I managed to "port" QForward to 1.19.3 in a very scuffed way, believing that was a problem with the way FabricProxy-Lite did modern forwarding, and since QForward explicitly targets quilt that wouldn't happen if the issue was on FabricProxy-Lite.
Neither QForward or FabricProxy-Lite work with QSL/QFAPI, but both of them work without QSL/QFAPI.

I did some more testing connecting to the server with a Quilt client with the test mod installed.
Client log: Quilt client -> Quilt server with Velocity
Client log: Quilt client -> Quilt server without Velocity
Server log: Quilt server -> Quilt client with Velocity
Server log: Quilt server -> Quilt client without Velocity
(also I got the server logs from testing with a vanilla client yesterday)
Server log: Vanilla client -> Quilt server with Velocity
Server log: Vanilla client -> Quilt server without Velocity

This should fix it for now. At least I hope as I didn't test it. Just change .zip into .jar
quilt_velocity_patch-0.0.0+1.19.3.zip

@Patbox With your mod installed, I'm able to connect to the Quilt server through Velocity! But I can't interact with anything (placing / breaking blocks, hitting mobs, etc.), and I'm constantly clipping into blocks, a la when a block is present on the server but not on the client - except the blocks are visible, and it happens with all blocks.
Chunks generate and mobs spawn and move around, at least.
Also, the Quilt server sometimes prints the following error when a player tries to join, followed by the player being kicked:
[16:43:48] [Netty Server IO #10/ERROR]: Received class net.minecraft.class_2828$class_2830 that couldn't be processed
java.lang.ClassCastException: class net.minecraft.class_3248 cannot be cast to class net.minecraft.class_2792 (net.minecraft.class_3248 and net.minecraft.class_2792 are in unnamed module of loader org.quiltmc.loader.impl.launch.knot.KnotClassLoader$Separate @1a5d0d94)
    at net.minecraft.class_2828$class_2830.method_11054(class_2828.java:16) ~[transformed-mod-minecraft.i0:0/:?]
    at net.minecraft.class_2535.method_10759(class_2535.java:167) ~[transformed-mod-minecraft.i0:0/:?]
    at net.minecraft.class_2535.method_10770(class_2535.java:152) ~[transformed-mod-minecraft.i0:0/:?]
    at net.minecraft.class_2535.channelRead0(class_2535.java:50) ~[transformed-mod-minecraft.i0:0/:?]
    at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:99) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:336) ~[netty-codec-4.1.82.Final.jar:?]
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:308) ~[netty-codec-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:336) ~[netty-codec-4.1.82.Final.jar:?]
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:308) ~[netty-codec-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:336) ~[netty-codec-4.1.82.Final.jar:?]
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:308) ~[netty-codec-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286) ~[netty-handler-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) ~[netty-transport-4.1.82.Final.jar:?]
    at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.82.Final.jar:?]
    at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.82.Final.jar:?]
    at java.lang.Thread.run(Thread.java:833) ~[?:?]
[16:43:48] [Server thread/INFO]: PLAYER[/<IP_ADDRESS>:52313] logged in with entity id 801 at (70.71692527738146, 70.06815128297653, -242.27902987058494)
[16:43:48] [Server thread/INFO]: PLAYER joined the game
[16:43:48] [Server thread/INFO]: PLAYER lost connection: Server sent an invalid packet
[16:43:48] [Server thread/INFO]: PLAYER left the game

...but sometimes I can join just fine, and no error is printed.
This is with Quilt Loader 0.18.0-beta.60, qfapi-5.0.0-alpha.9_qsl-4.0.0-beta.5_fapi-0.72.0_mc-1.19.3.jar, and FabricProxy-Lite-2.4.0.jar.

Try installing polymer too, might fix that

@Patbox That works!!
The below seems to be working fine:

Interacting with blocks / mobs
Generating chunks
Chat ("can't be verified", as expected)
Commands
Joining / Leaving (consistently)
...Getting kicked / banned (via /kick / /ban)

(I haven't tested with more than one player)
However, after having installed a few mods (that are required both client-side and server-side), the Quilt server prints the following error:
[08:07:04] [Netty Server IO #3/ERROR]: Received class net.minecraft.class_2828$class_2830 that couldn't be processed
java.lang.ClassCastException: class net.minecraft.class_3248 cannot be cast to class net.minecraft.class_2792 (net.minecraft.class_3248 and net.minecraft.class_2792 are in unnamed module of loader org.quiltmc.loader.impl.launch.knot.KnotClassLoader$Separate @3af6d7a7)
	at net.minecraft.class_2828$class_2830.method_11054(class_2828.java:16) ~[transformed-mod-minecraft.i0:0/:?]
	at net.minecraft.class_2535.method_10759(class_2535.java:167) ~[transformed-mod-minecraft.i0:0/:?]
	at net.minecraft.class_2535.method_10770(class_2535.java:152) ~[transformed-mod-minecraft.i0:0/:?]
	at net.minecraft.class_2535.channelRead0(class_2535.java:50) ~[transformed-mod-minecraft.i0:0/:?]
	at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:99) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:336) ~[netty-codec-4.1.82.Final.jar:?]
	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:308) ~[netty-codec-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:336) ~[netty-codec-4.1.82.Final.jar:?]
	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:308) ~[netty-codec-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:336) ~[netty-codec-4.1.82.Final.jar:?]
	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:308) ~[netty-codec-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286) ~[netty-handler-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) ~[netty-transport-4.1.82.Final.jar:?]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.82.Final.jar:?]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.82.Final.jar:?]
	at java.lang.Thread.run(Thread.java:833) ~[?:?]

The mods common between the client and server:

Architectury API v7.0.66
Cloth Config v9.0.94
Expanded Storage v9.0.0-alpha.2
Extended Drawers v1.3.6
Jade v9.3.1
Roughly Enough Items v10.0.586

The mods on the server only:

FabricProxy-Lite v2.4.0
Polymer v0.3.7
(your Quilt-Velocity patch mod)

I'm unable to replicate @unilock's results using the Quilt-Velocity patch.
Quilt Loader 0.18.1-beta.60
latest.log
ls ./mods/ -1
fabric-api-0.73.0+1.19.3.jar.disabled
FabricProxy-Lite-2.4.0.jar
polymer-bundled-0.3.7+1.19.3.jar
qfapi-5.0.0-beta.1_qsl-4.0.0-beta.9_fapi-0.73.0_mc-1.19.3.jar
quilt_velocity_patch-0.0.0+1.19.3.jar

Quilt Loader 0.17.10
2023-01-27-6.log
ls ./mods/ -1
fabric-api-0.73.0+1.19.3.jar.disabled
FabricProxy-Lite-2.4.0.jar
polymer-bundled-0.3.7+1.19.3.jar
qfapi-5.0.0-beta.1_qsl-4.0.0-beta.9_fapi-0.73.0_mc-1.19.3.jar
quilt_velocity_patch-0.0.0+1.19.3.jar

Whats on client

The client is using Adrenaline 1.12.0+1.19.3.quilt, which shouldn't impact testing.
I can confirm that a vanilla client has the same issues on both quilt loader versions.

quilt_velocity_patch-0.0.0+1.19.3.zip
Test this one

Was able to connect using the second patch on the minimal server case. Will test with my other mods to see if its fully fixed.

That patch seems to have fixed the (very few) content mods I was using 👌
(note that I've been using Quilt Loader 0.18.1-beta.58)
More testing should probably be done with more mods. I can get to that later.

what is the status on this issue? im using latest quilted fabric api alongside all the needed mods and velocity. on 1.19.4 and i still have such issues

Someone reported the same issue in FabricProxy-Lite, but I believe this is caused by your mods, because the timeout occurs in the PLAY phase, not the LOGIN phase that FabricProxy-Lite affects.
If this cannot be fixed at the moment, I suggest mentioning in the mod's description that it does not work with Velocity.

As an update: quilt_velocity_patch is still working fine with my "vanilla-compatible" Quilt server after updating to 1.19.4.
@james58899 Yes, this is an issue with Quilt / Velocity; it's unrelated to FabricProxy-Lite.

Since this issue has been confirmed(?) to be related to QSL's registry sync networking code specifically, might it make sense to move this to its issue tracker instead? (QuiltMC/quilt-standard-libraries)
(I am making the assumption that the issue does indeed have to do with QSL, because @Patbox's "quilt_velocity_patch" mixes into org.quiltmc.qsl.registry.impl.sync.ServerRegistrySyncNetworkHandler, and doesn't touch QFAPI at all.)

It is yes

Should an issue be opened on their tracker, then?
I assume this has already been discussed elsewhere, given the member names in quilt_velocity_patch (haha), but I can't find where that might've happened?

This issue confuses us a lot, since it is at the same times:

"An issue on the side of velocity"

"Unrelated to fabricproxy-lite"

"Fixed by a patch applied to Quilt's implementation of ServerRegistrySyncNetwork"

"Can be replicated with just QFAPI/QSL"

"Older versions without the Registry Sync rewrite don't exhibit that behaviour"

Where should we report this bug.
Is it here since a change to this project caused the interaction to misbehave, or on Velocity, since its a problem on their side, even thought admittedly this was already been discussed and went nowhere.

Quilt sent a PLAY state packet before Velocity switched from LOGIN state to PLAY, so Velocity discarded the packet, and Quilt waited for the response timeout^1.
I think this issue can be fixed by both sides, but I don't see related issue reports in Velocity. If the Quilt developer thinks it should be fixed by Velocity, please open an issue at Velocity, otherwise Quilt should fix it itself.

I managed to work around the issue on 1.19.2 by backporting Polymer's "sendGameJoinBeforeSync" functionality from >=1.19.3, then using that in conjunction with quilt_velocity_patch (which works as-is on 1.19.2).
My fork of Polymer including said backport: https://github.com/unilock/polymer/tree/dev/1.19.1-proxyfix
The combination of Polymer + quilt_velocity_patch works on 1.19.4 as well, if that wasn't clear. (Provided sendGameJoinBeforeSync is enabled - which it should be by default if another proxy compatibility mod is detected (FabricProxy-Lite, etc.))

Btw, feel free to pr that backport, just maybe move mod checks from registry sync manipulator to polymer/impl/compat one instead

Minecraft 1.20.1 quilt server still has the issue Unknown custom packed identifier: qsl:registry_sync/handshake when behind a proxy which can still be fixed by installing polymer


transit assignment updates for v9 network

What existing problem does the pull request solve and why should we include it?
What is the testing plan?
Demonstrate the code is solid by discussing how results are verified and covered by tests

[ ] Code for this PR is covered in tests
[ ] Code passes all existing tests

Code formatting
Code should be PEP8 compliant before merging by running a package like black

[ ] Code linted

Applicable Issues
Please do not create a Pull Request without creating an issue first.
Put closes #XXXX in your comment to auto-close the issue that your PR fixes.
Issues List

closes...
closes...

Thank you for the update. As I'm not familiar with the transit assignment logic, could you point out where specifically my review can be helpful?

Thank you for the update. As I'm not familiar with the transit assignment logic, could you point out where specifically my review can be helpful?

Hi Jayne, I'm still drafting the transit assignment changes, but they should be ready later today. Could you please review the highway assignment changes you merged from develop_bart (for example the toml files)? I got several merge conflicts when I checked in my changes. Thanks!


🐛Bug - Rules missing

Hi @BrookJeynes @bradystroud @Aibono1225
The rules widget is broken because it's missing rules.

Figure: I created this rule 2 months ago

Figure: Rule is not there
Acceptance Criteria:
The rules widget should display all rules edited or created by a user

Hey @Aibono1225 I just wrote a new rule and it seems to be suffering from the same problem that it doesn't show up in the widget:
https://www.ssw.com.au/rules/relational-database-design/

Update after investigation, here is what @bradystroud and I found for this issue:
Context: We refactored the code for the widget so that it requests data from the widget-history.json instead of making multiple requests to the GitHub. See the PR: https://github.com/SSWConsulting/SSW.Rules.Widget/pull/31
We found that there are problems with the data source, the data in the widget-history.json is not complete.

Figure:  Why is the Widget missing some rules
There are two possible reasons for incomplete data in the database:

When someone modifies an existing rule, the previous information about the person making the changes will be replaced (Database update).  https://github.com/SSWConsulting/SSW.Rules.Functions/blob/d9a51836bcf17bf9ae3fce1503c54200ff466bbf/Functions/Functions/History/UpdateRuleHistory.cs#L63

If "UpdateRuleHistory" fails, the execution of "UpdateHistorySyncCommitHash" will still continue, hence any missed data will not be readded to the CosmosDB.
https://github.com/SSWConsulting/SSW.Rules/blob/34f46dd9b2551c1fba89524146e2764c21b62ddd/.azure/scripts/update-rule-history.ps1#L69C1-L83

This is completed😊 below is the new screenshot of the people page:


WriteGetObjectResponseRequest: Content-Type

Describe the bug
I have ran into an issue with 1.9.220 of the aws-sdk-cpp when using the WriteGetObjectResponseRequest and attempting to configure the Content-Type.  When setting it .  When reviewing the issues, I had found: WriteGetObjectResponseRequest: Content-Type #1665, but the ticket was already closed.  I would like reopen it.
Expected Behavior
I'd like to set the content-type to be something other than just "text/plain"
Current Behavior
The content-type is always text/plain
Reproduction Steps
  S3::Model::WriteGetObjectResponseRequest request;
  request.WithRequestRoute(route);
  request.WithRequestToken(token);
  request.SetBody(objectStream);
  request.SetContentType("application/json"); // <-- curl -v show "text/plain" instead
  auto outcome = client.WriteGetObjectResponse(request);

Possible Solution
N/A
Additional Information/Context
No response
AWS CPP SDK version used
1.9.220
Compiler and Version used
9.4.0
Operating System and version
Ubuntu Linux 20.04

It seems that the root cause of this issue is that Content-Type is simply not set in aws-cpp-sdk-s3/source/model/WriteGetObjectResponseRequest.cpp.    I patched in the following to correct the issue:
`{

ss << GetContentType();

headers.emplace("x-amz-fwd-header-content-type", ss.str());

ss.str("");

}`


Bash Scripts Not Stopping on Sub-shell Failures

I found this issue while working with deployhl72fhir.bash and confirmed that the same issue exists in at least one more .bash script. The start of the scripts has set -euo pipefail, however this is not honored in the sub-shells. This results in confusing behavior, like scripts saying they succeeded when they actually failed.
I don't have time for a PR now (apologies), but wanted to submit this for tracking. Probably the easiest solution is to implement what is suggested here and require Bash >= 4.4 since Bash 4+ is required already.
Example of what the user sees when this issue arises:

Ideally this should be done in ARM, and this script could just be a wrapper around group deploy

Using the az cli causes deployment failures as the resources are not fully provisioned, causing subsequent commands to fail. The process of prompting the user for 12 variables is tedious.

Bash shells are being factored out during backlog sprints.   Thanks for the notes, we will address the use of sub-shells as quickly as we can


might be not compatible with lastest ddc framework

Thanks for the this handy addon.
In my setting it is not working with latest ddc.
call ddc#custom#patch_global('filterParams', {
  \ 'converter_truncate': {
  \    'maxAbbrWidth': 40,
  \    'maxKindWidth':20,
  \    'maxMenuWidth':40},
  \ })

In the screenshot, the long word was not truncated.

Happy new year and many thanks for taking care of it!

any updates on this? Many thanks!

Sorry for the delay.

Thanks for the example codes! Yes pum ui works. I was using the native ui and that is not compatible. Sorry I didn’t make myself clear in the beginning.
在 29.03.2023，09:50，Haruki Matsui @.***> 写道：

Sorry for the delay.

—
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmatsui54%2Fddc-converter_truncate%2Fissues%2F13%23issuecomment-1488104986&data=05|01||5a5992b2c56f4210056d08db302a4094|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638156730253421161|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=9j2ZIt74HlBRUzoWY5ALlJQnzfthURVyzyjZYE7ikzQ%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABF77F3VBXPXJBOUDBXBKUTW6PST5ANCNFSM6AAAAAATOIZFLI&data=05|01||5a5992b2c56f4210056d08db302a4094|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638156730253421161|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=sIFdkDeee6nTGxIEgUKLm7n8MfbOUeIDprdrf7S7etc%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>

I was using the native ui and that is not compatible.

Really?
Yes, you are right. Now I am confused why it didn't work in my setting for quite a while. Maybe some misconfigurations.


Example code is not displayed on Utils > Request page

Describe the change
Upon visiting the following page, none of the code examples are being displayed.
URL: https://h3.unjs.io/utils/request
SS:

URLs
https://h3.unjs.io/utils/request
Additional information

[ ] Would you be willing to help?

Ok. So all the examples are bundled at the bottom of the page 🙈

yeah this is affecting variois pages. going to hazard a guess that this is an issue closer to https://github.com/unjs/undocs
maybe similar to https://github.com/unjs/undocs/issues/132?


Fix strict mode error

When running this example I got the error message:
ReferenceError: Strict mode forbids implicit creation of global property 'pageWidth'

  phantomjs://code/rasterize.js:29 in global code

This small change seems to fix it.

Created an issue here:
14825

Landed! Thank you!


拉勾网使用skywalking进行调用链路监控

Please answer these questions before submitting pull request

Why submit this pull request?

[ ] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

Ref #443

Coverage remained the same at 12.199% when pulling 69b738fcfd39411e8df3e86c9d4c58772dda243b on mliu111477:patch-1 into 72a39e1f282346046c75a85dd670ba8ba0808896 on apache:master.


File uploaded to S3 with space can't be downloaded with GetObjectAsync

AWSSDK.S3/<IP_ADDRESS> in a .NETCoreApp,Version=v1.1 CLI app on OS X.
Create an S3 bucket, attach an SNS notification on the bucket for PUT events
Configure SNS to dump the notification into SQS.
Upload to S3 a file with a space in its name ("this image.jpg") to an S3 bucket.
Process the SQS message that has embedded JSON with the S3 file (key) name in it.
Use this snippet of code to download the S3 object.
 var response = await s3Client.GetObjectAsync(myClass.S3.Bucket.Name,
                          myClass.S3.Object.Key);

(works fine if file is named "thisimage.jpg" but not "this image.jpg")
When the uploaded file is "this image.jpg", the key is returned as "this+image.jpg" in the S3 -> SNS -> SQS notification JSON.  However, in the S3 web UI, the key is "this image.jpg".   Furthermore, the S3 web UI lists the URL to the file as https://region/bucket/this+image.jpg
Upon calling GetObjectASync, this exception gets thrown.  Here's the dump:
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Amazon.S3.Internal.AmazonS3ExceptionHandler.<InvokeAsync>d__1`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Amazon.Runtime.Internal.ErrorCallbackHandler.<InvokeAsync>d__5`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Amazon.Runtime.Internal.MetricsHandler.<InvokeAsync>d__1`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at CloudtrailToAzure.Program.<GetAndUploadAttachment>d__20.MoveNext() in <path to my code removed>

Am I doing something wrong?

What was the actual exception that was thrown? The stack trace you have listed does not contain that information.
Initial read suggests that this is an issue in the S3 -> SNS -> SQS data flow, and not specifically a .NET SDK issue. You would need to identify where the + is being injected into the key name (SNS or SQS?) and follow up with that service team, through their respective forums: SNS forum or SQS forum. This repo is for mainly for reporting issues and bugs with the .NET SDK, and from the current information it sounds like this would be an issue with any SDK, so I'm inclined to close this issue.

I think you're right that this is a service issue versus one with the SDK.
For what it's worth, here's the full exception thrown immediately after calling GetObjectAsync using the key provided by the JSON notification (which inserts a "+" wherever a space is in the filename).  Looks like my cut-and-paste was cut off.

Exception Amazon.S3.AmazonS3Exception: The specified key does not exist. ---> Amazon.Runtime.Internal.HttpErrorResponseException: Exception of type 'Amaz
on.Runtime.Internal.HttpErrorResponseException' was thrown.
at Amazon.Runtime.HttpWebRequestMessage.d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.Runtime.Internal.HttpHandler1.<InvokeAsync>d__91.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.Runtime.Internal.RedirectHandler.d__11.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.Runtime.Internal.Unmarshaller.<InvokeAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.S3.Internal.AmazonS3ResponseHandler.d__11.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.Runtime.Internal.ErrorHandler.<InvokeAsync>d__51.MoveNext()
--- End of inner exception stack trace ---
at Amazon.Runtime.Internal.HttpErrorResponseExceptionHandler.HandleException(IExecutionContext executionContext, HttpErrorResponseException exception)
at Amazon.Runtime.Internal.ErrorHandler.ProcessException(IExecutionContext executionContext, Exception exception)
at Amazon.Runtime.Internal.ErrorHandler.d__51.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.Runtime.Internal.CallbackHandler.<InvokeAsync>d__91.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.Runtime.Internal.CredentialsRetriever.d__71.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.Runtime.Internal.RetryHandler.<InvokeAsync>d__101.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Amazon.Runtime.Internal.RetryHandler.d__101.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.Runtime.Internal.CallbackHandler.<InvokeAsync>d__91.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.Runtime.Internal.CallbackHandler.d__91.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.S3.Internal.AmazonS3ExceptionHandler.<InvokeAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.Runtime.Internal.ErrorCallbackHandler.d__51.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.Runtime.Internal.MetricsHandler.<InvokeAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at CloudtrailToAzure.Program.d__20.MoveNext() in

Reproducing:
Immediately after uploading "this image.jpg" into the S3 section of the AWS Console, I see these file properties.   Note I've obscured a couple of fields - but you can see the difference between the key (file name) and the link - which has introduced a "+" (https://region/bucket/key)

If you run this snippet of code, the key returned is "this image.jpg" (different than the JSON notification provided by the S3 bucket).  The file can be successfully downloaded by GetObjectAsync.

static async Task BrowseBucket()
{
            var s3Client = new AmazonS3Client(accessKey,secretKey,Amazon.RegionEndpoint.USWest1);
            ListObjectsRequest request = new ListObjectsRequest();
            request.BucketName = "obscured-bucket-name";
            ListObjectsResponse response = await s3Client.ListObjectsAsync(request);
            foreach(var v in response.S3Objects)
            {
                Console.WriteLine("The key is " + v.Key + " ");
                var getObjectResponse = await s3Client.GetObjectAsync(request.BucketName,
                        v.Key);
            }
}

Can you point me in the right direction of the S3 team?
Is there another method to call to work around this issue?

I tried configuring SNS, SQS, and Lambda notifications for a bucket, and all three receive incorrect (space replaced by plus) keys, so it looks like this is an S3 issue.
The S3 forum is a good starting point. I'm also going to contact the team internally about this.
As this is not an issue with the .NET SDK, I'm going to close the issue, but feel free to add more information here if you feel it is relevant. I'll also update the issue if I learn anything.

Fair enough.  Thanks for taking the issue up internally.  I'll just have to filter key names (file names) prior to calling GetObjectAsync and hope I don't clobber anything else.   Thanks.

I tried uploading a file named this im + age blah.txt and the key in the event ended up being this+im+%2B+age+blah.txt. It looks like S3 is url-encoding the keys before sending them, so perhaps you could run something like WebUtility.UrlDecode(eventKey) to get the "correct" key. But right now that's just a theory on my part.


Manage templates repositories for Packer

PR progress checklist (to be filled in by reviewers)

[X] Changes to documentation are appropriate (or tick if not required)
[ ] Changes to tests are appropriate (or tick if not required)
[ ] Reviews completed

What type of PR is this?
Primary type

[ ] [build]    Changes related to the build system
[ ] [chore]    Changes to the build process or auxiliary tools and libraries such as documentation generation
[ ] [ci]       Changes to the continuous integration configuration
[X] [feat]     A new feature
[ ] [fix]      A bug fix
[ ] [perf]     A code change that improves performance
[ ] [refactor] A code change that neither fixes a bug nor adds a feature
[ ] [revert]   A change used to revert a previous commit
[ ] [style]    Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)

Secondary type

[ ] [docs]     Documentation changes
[ ] [test]     Adding missing or correcting existing tests

Does this PR introduce a BREAKING CHANGE?
No.
Related issues and/or pull requests
Describe the changes you're proposing
Manage templates repositories for Packer, like Bento project from Chef
Documentation checklist

[X] Updated the README (e.g. Available states).
[X] Updated pillar.example.

Thanks for the PR, @kartnico -- let's try to get some eyes on it from people who have previously contributed to this formula.
@arthurlogilab @andreimoustache Would either of you be able to glance at this PR and give some general feedback.  If it's OK with either of you, we can go ahead and merge.

This is exactly why it's so important to get the right feedback.  Really appreciate your review, @arthurlogilab!


unmaintained openstack releases

Hello,
I saw you dropped support of unmaintained releases - https://github.com/EmilienM/devstack-action/pull/21
But while it is not recommended to install these releases, a lot of people might have them installed internally and I have to check my library against them for backward compatibility. Are you planning to support them or would you accept PR with support for them?

You can still install whatever version you like. We just removed the CI jobs to avoid testing the unmaintained & unsupported releases in OpenStack. But you can still use this Github Action to deploy any OpenStack version that you like, at your own risk.

Well, not really. Trying to install unstable/yoga release shows error with git as it tries to fetch stable/yoga branch which doesn't exist anymore - https://github.com/php-opencloud/openstack/actions/runs/8550781380/job/23428430991?pr=408
I'll try to override TARGET_BRANCH as you did before https://github.com/EmilienM/devstack-action/commit/e82a9cbead099cba72f99537e82a360c3e319c69

Yes, adding TARGET_BRANCH=unstable/yoga to conf_overrides installs it properly. But I guess it's better to at least document or better add it automatically.


Firebase transactions with read operations after write operations

Environment details

npm version: 6.14.6
Node.js version: 12.8.3
node engine: 12
@google-cloud/firestore version: 4.5.0
firebase-admin: 9.6.0
firebase-functions: 3.13.2

Steps to reproduce
Docs states that you can execute reads after writes, but as it turns out you cannot. Is that a bug or misleading documentation?

Call a cloud function or trigger background function

const onFirestoreTestsWrite = functions.firestore
  .document('tests/{testId}')
  .onWrite(async (change, context) => {
    await admin.firestore().runTransaction(async (t) => {
      const testDoc = await admin.firestore().collection('tests').doc().get();
      t.set(testDoc.ref, {});
      t.get(testDoc.ref);
    });
  });

const tests_get = async (req, res) => {
  try {
    const test = await admin.firestore().runTransaction(async (t) => {
      const testDoc = await admin.firestore().collection('tests').doc().get();
      t.set(testDoc.ref, {});
      return t.get(testDoc.ref);
    });
    res.send({id: test.id});
  } catch (e) {
    res.status(400).send({ error: e['message'] });
  }
};

Will result in error:
Error: Firestore transactions require all reads to be executed before all writes.
    at Transaction.get (/workspace/node_modules/@google-cloud/firestore/build/src/transaction.js:76:19)
    at /workspace/lib/firestore/tests-write.js:46:11
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Transaction.runTransaction (/workspace/node_modules/@google-cloud/firestore/build/src/transaction.js:323:26)
    at async /workspace/lib/firestore/tests-write.js:43:5

@rafikhan yep, there's part about isolation, but also a note:

Only the server client libraries support transactions with read operations after write operations. For transactions in the mobile/web SDKs, document reads must come before document writes.

We will fix the documentation. The SDKs do not support read after writes. The Mobile and Server SDKs only differ in how they obtain locks for documents that are read as part of a transaction.

Filed b/186414961 for documentation fix.

Documentation has been updated internally and will be rolled out with the next update,


Support for persistent newcommand definitions

The following works as expected:
# README

$\newcommand{\f}{\mathbf{f}}
\|\f\|^2$

But if I put newcommand in a different line this will not work:
# README

$\newcommand{\f}{\mathbf{f}}$

$\|\f\|^2$

Mathjax for example will keep commands persistent through the document. This is very useful if I want to define some macro at the top of the document and use it in a bunch of equations below.
I humbly request this feature.

I agree. This will be very useful.


MSID: 91745 Version: 2 DOI: 10.1101/2<IP_ADDRESS>1875

MSID: 91745
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>1875
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=91745
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>1875

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/91745v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>1875
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/91745/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

error: [author-corresp-no-email] Author Benoît Perez-Lamarque has the attribute corresp="yes", but they do not have a child email element or an xref with the attribute ref-type="corresp".
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c12) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c15) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c67) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c76) has a publication-type='other'. Is that correct?


I deployed the app locally and tried to signup a student I got below error

Exception Type:	OperationalError
Exception Value:
no such table: main.classroom_student__old

The issue was related to subject data in database, it is working fine when I cleaned existing data and migrated everything as fresh.

closing as it is solved

closing as it is solved

Hey! Same issue for me as well!
What did you do exactly?
Can you tell me the steps please.

how was it fixed ,

how was it fixed ,

Change the Django version in requirements.txt file to Django==2.2.7.
Install them and follow the steps as mentioned in the repo.

how was it fixed ,

Change the Django version in requirements.txt file to Django==2.2.7.
Install them and follow the steps as mentioned in the repo.

It's showing an error

Sorry, I guess the error is because of the full-stop at the end of 2.2.7 ,  just keep it Django==2.2.7
And it'll work probably.

Sorry, I guess the error is because of the full-stop at the end of 2.2.7 , just keep it Django==2.2.7
And it'll work probably.

ya i have installed it successfully ...but when i tried to sign up as a student it is showing  the following

operational error

Exception Type:	OperationalError
Exception Value:
no such table: main.classroom_student__old

The issue was related to subject data in database, it is working fine when I cleaned existing data and migrated everything as fresh.

i didn't get it ...

The issue was related to subject data in database, it is working fine when I cleaned existing data and migrated everything as fresh.

Can u elaborate how to do it..

For those still having this error, Here is what I did

Changed the Django version number to 2.2.7 in requirements.txt ( This step isnt necessary I think)
Remove db.sqlite file from django folder
Run 'python manage.py migrate'
Start server and Create a Student account first, then create a teacher account, order is important.

Cheers

When I executed this project I got this error too. And, solutions in here didn't work. If this issue is still open, I would like to work on the issue.


Fix overwritting the input file for IOSvc from the command line

Originally posted in https://github.com/key4hep/k4FWCore/issues/241#issuecomment-2384294263
BEGINRELEASENOTES

Fix overwritting the input file for IOSvc from the command line. The k4FWCore wrapper of the ApplicationMgr checks the number of events (needed for multithreading) and if the file exists but this was happening right after the parsing of the file, without taking into account the input file can be overwritten from the command line.
Add a test where the input file is being overwritten from the command line

ENDRELEASENOTES

For completeness another test could be added checking the case whe IOSvc.Input is not assigned in the steering file but set from cli

Thanks, I tested it locally and it works (party!)

I think this should be ready; I have added another check for reading from multiple files. I'm not aware of any other bugs and passing through the command line overwrites the choice in the steering file (if any) correctly


[UI] Protocol field on load balancer service not correct size

Rancher Versions:
Server: 1.3.1
healthcheck: N/A
ipsec: N/A
network-services: N/A
scheduler: N/A
kubernetes (if applicable): N/A
Docker Version:
N/A
OS and where are the hosts located? (cloud, bare metal, etc):
N/A
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
N/A
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Reporting this small issue/UI glitch on behalf of a Windows user and i'm able to reproduce the issue in a VM:
Click "Upgrade" on the "Load balancer" service and click "Add Service Rule". Select "HTTPS" in the dropdown menu and notice that the field not contains all of the text.
This is shown correctly in OS X with Chrome/Firefox but with Windows with Firefox/Chrome it dosen't have room for all the text (see screenshot below).
OS: Windows 7 and 10
Chrome: 55.0.2883.87 m
Firefox: 50.0.2
Results:
The dropdown field does not show HTTPS entirely and can make it possible to mix HTTP and HTTPS if not paying closely attention. This might also be the case with other fields in Rancher when running Windows.

Version - master 1/19
Yes this is indeed a problem in Windows, but also Firefox on Mac.

Thanks for confirming. I only tested with Safari and Chrome on OS X.

Also applys to Other parts of the ui, like the host scheduler.

These were widened at some point..


textual display errors

This was just by installing Oh-my-zsh through curl on a fresh install of OS X El Capitan. Not too sure whats happening here but I've also seen similar looking things when using the immediately after using the nano command

@harryparkdotio Do you (or maybe zsh?) have a custom PS1 environment variable set? I was having similar graphical corruption that was caused by me improperly escaping color escapes in my PS1 env var. It annoyed me for a week before I decided to figure it out.
I was defining my PS1 as:
RESET=$(tput sgr0)
BOLD=$(tput bold)
BLACK=$(tput setaf 0)
RED=$(tput setaf 1)
GREEN=$(tput setaf 2)
YELLOW=$(tput setaf 3)
BLUE=$(tput setaf 4)
MAGENTA=$(tput setaf 5)
CYAN=$(tput setaf 6)
WHITE=$(tput setaf 7)

HOST='\h'
CWD='\w'
GIT='$(__git_ps1 " (%s)")'
TIME='\t'
PS1="\n[$GREEN$TIME $RED$HOST$WHITE:$BLUE$CWD$YELLOW$GIT$WHITE]"
PS1="$PS1\n    $PURPLE\$$RESET "

The colors should actually have escaped square brackets around them like so:
RESET="\[$(tput sgr0)\]"
BOLD="\[$(tput bold)\]"
BLACK="\[$(tput setaf 0)\]"
RED="\[$(tput setaf 1)\]"
GREEN="\[$(tput setaf 2)\]"
YELLOW="\[$(tput setaf 3)\]"
BLUE="\[$(tput setaf 4)\]"
MAGENTA="\[$(tput setaf 5)\]"
CYAN="\[$(tput setaf 6)\]"
WHITE="\[$(tput setaf 7)\]"

HOST='\h'
CWD='\w'
GIT='$(__git_ps1 " (%s)")'
TIME='\t'
PS1="\n[$GREEN$TIME $RED$HOST$WHITE:$BLUE$CWD$YELLOW$GIT$WHITE]"
PS1="$PS1\n    $PURPLE\$$RESET "

Perhaps that will help?
Good luck!

Thanks for the help, but I actually don't have any custom PS1 environment variables set in either my .zshrc or my hyper → preferences. Still experiencing these issues, including when using nano

This issue has been fixed in v1.0.0.


Update gulp-nsp

.Before this fix I was getting the following error when running gulp publish:
return m ? m.index + 1 : c.length;
                              ^
TypeError: Cannot read property 'length' of undefined

This pull request fixes that error. I also believe it should fix the follwing issue: https://github.com/yeoman/generator-node/issues/180

I've basically used usage example from https://github.com/nodesecurity/gulp-nsp
It seems they have new API now.

Okay, just keep the previous nsp name.

Thanks.

@SBoudrias Could you please do a release? I am AFK...

@hemanth Yep works for me now :+1:.


Missing blade ward enchant

Links to WOTLK Wowhead for each item:
https://www.wowhead.com/wotlk/item=46027/formula-enchant-weapon-blade-ward
This enchant is not in the sims as I can tell, but it does drop in game.

I could implement this if the details are confirmed; wowhead thread has a lot of different numbers, and I don't know what's correct for classic.


Add docs explaining basic instructions for adding a new provider

These are some instructions for adding support for a provider. #550
It's short on code because we are moving to an external apiserver, so our controller is likely going to see some changes. In the meantime, the contracts here should help contributors start implementing controllers and actuators.

This change is

/assign @jessicaochen

/assign @medinatiger

I tried to rebase on my host and my local branch is messed up now (the last commit I had was on Github and not my local git copy). So I prefer just merging as-is than breaking the branch even more.

/hold cancel


-C uses last pipe colour from previous invocation

If I run pipes.sh; pipes.sh -C, instead of drawing without colour, the second invocation always draws with the last colour drawn from the first invocation. Obviously some terminal escape state is lying around. This seems related to, but distinct from, #5.
I'm no expert on tput and friends, but I see two potential ways of fixing this, which both seem to work.

Insert a call to tput reset just before entering the main animation loop. This ensures that drawing always starts from a clean state.
stty -echo
tput reset # <<<<<<<<<<<<<<<<<<<<< Added line
tput smcup || FORCE_RESET=1
tput civis
tput clear
# any key press exits the loop and this script
while REPLY=; read -t 0.0$((1000/f)) -n 1 2>/dev/null; [[ -z $REPLY ]] ; do

Insert a call to tput reset into cleanup. This ensures that the script always cleans up after itself.
cleanup() {
    # clear up standard input
    read -t 0.001 && cat </dev/stdin>/dev/null

    # terminal has no smcup and rmcup capabilities
    ((FORCE_RESET)) && reset && exit 0

    tput reset # <<<<<<<<<<<<<<<<<<<<< Added line
    tput rmcup
    tput cnorm
    stty echo
    ((NOCOLOR)) && echo -ne '\e[0m'
    exit 0
}

Personally I think the second option seems more responsible, but it could be that there's a third option that makes more sense. Again, I'm no expert on this stuff.

Using st-0.7 and xterm-297 on Linux, this issue doesn't happen, @parkercoates, what's your OS and terminal emulator?
As you have mentioned #5, 3816faf98045f76a02513fe375d23dd87fed1972 was made to fix this issue, this should be the same to be fixed in #5, apparently it didn't fix for all.  What exactly did you do to reproduce the bug?  Run the command and immediately press Q, I even tried
./pipes.sh -p100 -r0 -R; ./pipes.sh -C

to fill up the screen, but still can't reproduce.
If it's confirmed by others, then we could take tput reset approach and revert that commit.

@livibetter, you're right that this issue is dependent on the environment. I can reproduce the issue with konsole, but xterm and gnome-terminal don't seem to be affected. I have no idea whether this is actually a bug in Konsole or an unspecified difference in behaviour. As I said, I'm no expert on terminal control codes.
If you wanted to give me a minimal test case to try, I'd be happy to take the issue up with the Konsole developers.

@parkercoates I can't give you a minimal test case since I don't have KDE/konsole to create one with.  However, since it's konsole, it should have good amount of users, I'd vote for the tput reset workaround providing it won't break other emulators else, which I don't believe it would.  You should submit another PR and specially refer to this issue in comment.
I also wonder what if #34 is also the same, all depending on the environment.
This repo needs an issue report template/form for those information to be filled in when reporting.


Show log.ok on success.

Hmm it seems tests use undefined. Not sure if I'll have the time to fix that so feel free to adapt this PR if you have time.

I'll merge it and fix the tests.

fixed the tests, merged and published a new version.
Thanks for the PR :+1:


there is a horizontal scrollbar ---- ui grid

why there is a horizontal scrollbar when i use "ui grid" like this:

1

2

3

4

Grids use negative margins. If you have a page level full width grid use padded grid


Wierd benchmark results

So, I wanted to see how Crystal handles some stuff differently from Ruby, and got some very strange results.
Crystal Code:
puts "Starting Tests"
s_t = Time.now
a = 0
b = [] of Int32
c = ""
d = {} of Symbol => String
d[:string] = ""
10000.times do
  a += 1
  b << a
  c += "#{b}"
  #d[:string] << c
end
e_t = Time.now
puts "Finished testing in #{e_t - s_t} sec"

Ruby Code:
puts "Starting Tests"
s_t = Time.now
a = 0
b = []
c = ""
d = {}
d[:string] = ""
10000.times do
  a += 1
  b << a
  c += "#{b}"
  #d[:string] << c
end
e_t = Time.now

puts "Finished testing in #{e_t - s_t} sec"

Ruby did it on my pc in 11 sec.
Crystal reached 14Gig RAM and I had to close it (after around 1.5 min).
Why is that ?

Because string handling, Ary will probably write a more elaborate answer. The following beats Ruby in release mode by far:
puts "Starting Tests"
s_t = Time.now
a = 0
b = [] of Int32
d = {} of Symbol => String
String.build do |c|
  10000.times do
    b << a
    a += 1
    c << "#{b}"
  end
end
e_t = Time.now
puts "Finished testing in #{e_t - s_t} sec"

@barachy did you mean the Ruby version takes 11 minutes (not seconds). I run it and it took about 500 seconds to finish.
I don't know why Crystal allocates more memory, it's probably related to how boehm GC works.
In any case, using + for string concatenation in a loop is bad, both in Ruby and Crystal, because + creates a new string and you have to copy lots of bytes. As @jhass showed, the efficient way to build a string is using String.build. Also, when building a string like that there's no need for "#{b}", you can just do c << b.
Now, let's compare Ruby and Crystal using string building. In Ruby it's:
puts "Starting Tests"
s_t = Time.now
a = 0
b = []
c = ""
d = {}
d[:string] = ""
10000.times do
  a += 1
  b << a
  c << "#{b}"
end
puts c.length
e_t = Time.now
puts "Finished testing in #{e_t - s_t} sec"

Prints "289463389" and it takes 11 seconds on my machine... which makes me think this was your original benchmark, maybe? Maybe then you tried to port it to Crystal and found that << doesn't exist for String, so you changed it to +=?
The Crystal version:
puts "Starting Tests"
s_t = Time.now
a = 0
b = [] of Int32
d = {} of Symbol => String
c = String.build do |c|
  10000.times do
    a += 1
    b << a
    c << b
  end
end
puts c.length
e_t = Time.now
puts "Finished testing in #{e_t - s_t} sec"

Prints "289463389" and takes 1.71 seconds. The variant with c << "#{b}" takes 1.85 seconds: not a big difference, but slower.

Would it be too radical to just remove the "+" operator from String? It's a common pitfall for beginners (and not-so-beginners) in many languages!
When I was starting to learn Java I remember @asterite would always remind me not to build strings through "+", and to resort to StringBuilder instead.
I always wondered why the most expensive way of concatenating strings got the cheapest syntax (probably a legacy from C?).
Nothing beats "+" (or "&" or whatever operator they use to concatenate strings on your language of choice) when it comes to succinctness, yet we use it for an expensive operation! There should be some sort of commensurability between the effort to write something and how convenient it is.

@asterite  point on about the "Maybe then you tried to port it to Crystal and found that << doesn't exist for String, so you changed it to +=?" I even didn't see that I haven't re-changed it back.
I guess I just need to learn the syntex more, thanks on the detailed answer !

@mverzill. The concatenation operator is handy for simple cases.

@mverzilli I thought about that many times. I just tried it with the compiler's code base but, indeed, in some cases it's handy.


Some Material name don't work

*Description of issue:
Hello,
I have a 1.12.2 server on PaperSpigot with the last version of JobsReborn.
I would like to use some of the material names in 1.12.2 like MELON_BLOCK or REDSTONE_LAMP_ON, but it does not work, even after trying the legacy_name, or whatever, is this a bug or is there a particular handling to carry out ? Thank you :)
ERROR (DELETE IF YOU HAVE NO ERROR):
####################
## Job Cultivateur has an invalid Break type property: MELON_BLOCK!
## Job Ingenieur has an invalid Break type property: REDSTONE_LAMP_ON!
####################

CONFIG SECTION (DELETE IF NOT RELEVANT):
#####################################
## PASTE RELEVANT CONFIG SECTION HERE
##
##      REDSTONE_LAMP_ON:
##        income: -10.5
##        points: -10.5
##      MELON_BLOCK:
##        income: 3.0
##        points: 3.0
##        experience: 3.0
#####################################

Server Type (Spigot/Paperspigot/etc): Paper Spigot
Server Version (using /ver): git-Paper-1613 (MC: 1.12.2)

Did you tried with lower-cased chars such as melon_block?

Yep, with the same problem :/

Use the melon instead of melon_block
The redstone_lamp_on is not been added, and we try to use the legacy_redstone_lamp_on material, but this not added now.

Job Cultivateur has an invalid Break type property: MELON (melon)! Material must be a block! Doesn't work either :/

In this commit fixes the melon and added the redstone_lamp_on material. This will be able in the next release.
To work this use: melon_block and legacy_redstone_lamp_on

Oh thank you !
But sorry to be so embarrassing but I found other items for which the action of eating this time does not work :/
Job Cultivateur has an invalid Eat type property: POTATO_ITEM!
 Job Cultivateur has an invalid Eat type property: CARROT_ITEM!

Use potato and carrot

Already tried, but it doesn't seem well detected, because I don't receive the payment of the trade.

Try with potatoes and carrots

Sadly still not working :/

Is there a build server or a way to get the "fixed" jar file ? :)

melon or melon_block as well as many blocks (or mobs) are not recognized anymore for paiements under last build for a 1.13.2 server

These material names are work correctly with the dev version. It is only one changes for the melon is not recognized correctly and should be fixed in the dev release. So install it and test. If some materials are not work just see this instructions to improve. If this listed materials still not work with this instructions, then this issue will related to client issue and not plugin, because the materials are correctly specified in the code.

Since my last message my server went to version 1.14.4 and there , yes everything works (most of things that didn"t in 1.13.2) but in version 1.13.2 i never succeed to have a jobs plugin that was fully working , now it's ok :)


⚠ Bofrost.at has degraded performance

In 8e61c42, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2270 ms

Resolved: Bofrost.at performance has improved in 4c080e4 after 6 minutes.


Feature Request: Allow filtering Combo Picker by keyword and snippet text instead of just Name

Sometimes what I remember is part of the keyword shortcut or a word or 2 of the snippet text, as opposed to the specific title.

Hi.
Thanks for the request. I agree, as I also noted that sometimes searching the title is not enough.


Add a  to each page

This is a feature I needed that I thought might be generally useful. This adds a <link rel="canonical"> to each page's <head> section linking to the page's canonical absolute URL (according to baseUrl).
I noticed this was very similar to logic already done by the RSS and sitemap code, so I refactored slightly so all three could share the same URL generation code.
It seemed like this might want to fit into the path types structure (e.g. as a new type AbsoluteUrl), but I didn't understand that quite well enough to extend it.
Motivation
I believe this is considered a best practice for SEO, as e.g. it combines the Google juice for https://your-site.com/page and https://your-site.com/page?utm-tracking=nonsense.
In my case I had a more concrete need for this to work around a quirk of my hosting setup. I wanted to host my digital garden at a subdirectory of my existing blog domain (https://five-eights.com/garden). I'm using Netlify for hosting, which supports this setup via proxy rewrites. This mostly worked out of the box (thanks to Quartz's careful use of relative URLs!). However, it bumps into a couple of Netlify edge cases:

Netlify is opinionated about canonical links, and if the page itself doesn't define one, it infers one (!) and adds it as an HTTP response header
the inferred canonical URL is apparently just wrong for proxy-rewritten requests (it just gets set to https://five-eights.com/, no suffix, regardless of which /garden page is being requested)

I found that setting a canonical link in the page suppressed the weird Netlify behaviour.

hey! thanks for the contribution :) do you know if there are any negative implications of having an incorrectly set <link rel="canonical">? quite a few folks never actually update baseURL so I want to make sure that this change won't break SEO for them

Good question - I'm no expert but I suspect it wouldn't be great. (I've poked at the Google Search Console a bit and it seems to yell at you if your canonical URLs are inconsistent, although I don't think it prevents indexing altogether.) It probably wouldn't make your site fall off the internet entirely, though.
What do you think about changing the default baseURL to undefined (or null, I don't know which is the best practice in Typescript)? That would disable the canonical links (as already implemented). I think that would fix the problem for most people who didn't update baseURL - they wouldn't get this feature anyway until they updated from upstream, and then they'd get the new default at the same time. Unfortunately that would merge conflict with everyone who had updated baseURL :(
Another option would be to special-case the feature disabled when the baseURL was equal to the default (although that would break it for you specifically!).

Here's an idea:
Let's add a includeRelCanonical option to Component.Head() so that if it's enabled, we can use the baseURL (and disable it by default)

Here's an idea:
Let's add a includeRelCanonical option to Component.Head() so that if it's enabled, we can use the baseURL (and disable it by default)

That's a good idea, thanks for working with me on this!
I've added the option to the top-level GlobalConfiguration (and to quartz.config.ts) because that seemed like a reasonable place to set the value of the option. I know that isn't exactly what you suggested, so if you'd rather keep it out of the default config file, I can move it - I think if so, that would mean hardcoding (in my fork) includeRelCanonical=true in renderPage.tsx where Head is invoked, or otherwise finding a way to pass the property into that higher-level component?
I put the default value in a slightly odd place in the file to reduce the likelihood of merge conflicts for people who have customized baseUrl.
Let me know what you think about this version, happy to make further edits! (I may be a bit slower to respond than before - I was on a break from work, but now back to the day job.)

I would prefer to keep it in the Head component. Quartz components can take in options because they are functions that return components (e.g. https://github.com/jackyzha0/quartz/blob/v4/quartz/components/Footer.tsx) and then this can be passed in quartz.layout.ts where Components.Head is initialized (likely something like Components.Head({includeRelCanonical: true})

I can help guide you through this change if you need more pointers, lmk

hey @samstokes, I'm going to close this due to inactivity but feel free to lmk if you'd like to reopen and continue working on it :)


[Teams] Messaging Extension Preview Send/Edit

Add OnTeamsMessagingExtensionBotMessagePreviewSendAsync
and OnTeamsMessagingExtensionBotMessagePreviewEditAsync
to ActionBasedMessagingExtensionFetchTaskBot
Fixes: https://github.com/microsoft/botbuilder-dotnet/issues/2619

Pull Request Test Coverage Report for Build 81261

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.1%) to 79.639%

Totals

Change from base Build 81231:
1.1%

Covered Lines:
4099

Relevant Lines:
5147

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.3.1

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.3.1


Add option to restrict AWS accounts for Privatelink-enabled deployments

AWS Privatelink support was added as part of this PR - https://github.com/wandb/terraform-aws-wandb/pull/169
We would like to provide an option with Privatelink-enabled deployments to restrict private access to specific AWS accounts only - https://docs.aws.amazon.com/vpc/latest/privatelink/configure-endpoint-service.html. This is required so a rogue user in a company couldn't create a private endpoint to their deployment from their personal AWS account and exfiltrate company data.

private_link_allowed_account_ids is the only way to enable Private Link and this specifically locks it down to the individual aws accounts.

Aah ok. So we could close this then? I think I asked you internally too and you had shares this, so my apologies.


libcint: 4.1.1 -> 4.3.0

Motivation for this change
Update to latest version. https://github.com/sunqm/libcint/releases/tag/v4.3.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build libcint


Template ref type inference doesn't work when using defineComponent (but does work in

Vue - Official extension or vue-tsc version
2.1.10
VSCode version
N/A
Vue version
3.5.13
TypeScript version
5.7.2
System Info
System:
    OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1265U
    Memory: 32.74 GB / 46.72 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 18.20.4 - ~/.nvm/versions/node/v18.20.4/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v18.20.4/bin/npm
    pnpm: 9.5.0 - ~/.nvm/versions/node/v18.20.4/bin/pnpm
  Browsers:
    Chrome: 131.0.6778.139
    Chromium: 128.0.6613.84

package.json dependencies
No response
Steps to reproduce
Bind a template ref to a native HTML element in a component that uses

Then write the same code, but using defineComponent:
<template>

{{ msg }}

        <input ref="input" v-model="msg">
        <button @click="focusInput">Focus</button>

</template>

What is expected?
In both cases, vue-tsc should automatically infer the type of the input template ref as HTMLInputElement, and so it accepts input.value?.focus() because HTMLInputElement has a focus method.
What is actually happening?
In the


Remove reference to deprecated static-compiler plugin

I think it might confuse people?

I'm ok with removing the reference if it is confusing, but the statement is accurate (it was inspired by static compiler...)

Let me rephrase "confusing": Now that most people aren't using static-compiler anymore (and static-compiler is deprecated), I think the reference isn't helpful to users - they just click through and see that it's deprecated. I guess the only remaining purpose is to give credit to static-compiler, but, as the author of static-compiler, I really don't care. ;)
But if you want to leave it in that's fine too.

I guess the only remaining purpose is to give credit to static-compiler

Confirm, this was my intent.


implement logging and recovery (checkpointing is not included)

WIP

"TestRedo" and "TestUndo" testcased on log_recovery_test.go are passed.
So, this modifications are merged to main.


npm package?

Would you consider publishing these components as an npm package? Bower is deprecated now, and it would simplify usage workflow for creating codelabs.

Do you mean this on bower install ?

@sinedied I'm afraid we will not be fixing this but we're working on a complete drop-in replacement using just Custom Elements spec, without Polymer or other frameworks/libs, in https://github.com/googlecodelabs/codelab-elements. See https://github.com/googlecodelabs/codelab-components/issues/49 for more details.
I've linked this from https://github.com/googlecodelabs/codelab-elements/issues/6 to make sure it's on the list.

@x1ddos Thanks, the new version seems interesting!