Skip to content

fix: Remove shared memory key from the error response (#403) #409

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 23, 2025
Merged

fix: Remove shared memory key from the error response (#403) #409

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/shm_manager.cc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
// Copyright 2021-2023, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
// Copyright 2021-2025, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
//
// Redistribution and use in source and binary forms, with or without
// modification, are permitted provided that the following conditions
Expand Down Expand Up @@ -188,8 +188,8 @@ SharedMemoryManager::GrowIfNeeded(uint64_t byte_size)
}
catch (bi::interprocess_exception& ex) {
std::string error_message =
("Failed to increase the shared memory pool size for key '" +
shm_region_name_ + "' to " + std::to_string(*total_size_) +
("Failed to increase the shared memory pool size to " +
std::to_string(*total_size_) +
" bytes. If you are running Triton inside docker, use '--shm-size' "
"flag to control the shared memory region size. Error: " +
ex.what());
Expand Down
Loading