You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe your environment
Visual Studio 2017 version 15.0
VC++ version: 14.10
_MSC_VER: 1910
Following error are reported while building a sample trace application:
Error C2280 'absl::otel_v1::variant_internal::Union<T0,bool,int64_t,uint64_t,double,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::Span>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::SpanContext>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::baggage::Baggage>> &absl::otel_v1::variant_internal::Union<T0,bool,int64_t,uint64_t,double,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::Span>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::SpanContext>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::baggage::Baggage>>::operator =(const absl::otel_v1::variant_internal::Union<T0,bool,int64_t,uint64_t,double,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::Span>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::SpanContext>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::baggage::Baggage>> &)': attempting to reference a deleted function Project4 c:\users\labhas\obs\otel\opentelemetry-cpp\api\include\opentelemetry\nostd\internal\absl\meta\type_traits.h 166
Error C4996 'std::equal::_Unchecked_iterators::_Deprecate': Call to 'std::equal' with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' Project4 c:\program files (x86)\microsoft visual studio\2017\enterprise\vc\tools\msvc\14.10.25017\include\xutility 2889
Steps to reproduce
#include "opentelemetry\context\context.h"
int main()
{
}
will give the first error
And
#include "opentelemetry\context\context_value.h"
int main()
{
}
will give second error
What is the expected behavior?
No error
What is the actual behavior?
Error as mentioned below
Additional context
Our CI pipeline runs on VS2019, so these errors are not seen there.
The text was updated successfully, but these errors were encountered:
Describe your environment
Visual Studio 2017 version 15.0
VC++ version: 14.10
_MSC_VER: 1910
Following error are reported while building a sample trace application:
Error C2280 'absl::otel_v1::variant_internal::Union<T0,bool,int64_t,uint64_t,double,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::Span>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::SpanContext>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::baggage::Baggage>> &absl::otel_v1::variant_internal::Union<T0,bool,int64_t,uint64_t,double,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::Span>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::SpanContext>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::baggage::Baggage>>::operator =(const absl::otel_v1::variant_internal::Union<T0,bool,int64_t,uint64_t,double,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::Span>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::trace::SpanContext>,opentelemetry::v1::nostd::shared_ptr<opentelemetry::v1::baggage::Baggage>> &)': attempting to reference a deleted function Project4 c:\users\labhas\obs\otel\opentelemetry-cpp\api\include\opentelemetry\nostd\internal\absl\meta\type_traits.h 166
Error C4996 'std::equal::_Unchecked_iterators::_Deprecate': Call to 'std::equal' with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' Project4 c:\program files (x86)\microsoft visual studio\2017\enterprise\vc\tools\msvc\14.10.25017\include\xutility 2889
Steps to reproduce
will give the first error
And
will give second error
What is the expected behavior?
No error
What is the actual behavior?
Error as mentioned below
Additional context
Our CI pipeline runs on VS2019, so these errors are not seen there.
The text was updated successfully, but these errors were encountered: