Cmake links all abseil components and results in a link time error

No matter what I try, cmake builds the whole abseil and then links everything into my shared library. I could reproduce this with a minimal cmake example:
cmake_minimum_required(VERSION 2.8.12)
project(my_project)
set(CMAKE_CXX_FLAGS "-std=c++11 -fvisibility=hidden ${CMAKE_CXX_FLAGS}")
add_subdirectory(abseil-cpp)
add_library(my_lib SHARED main.cpp)
include_directories(SYSTEM abseil-cpp)
target_link_libraries(my_lib absl::hash absl::container)

main.cpp contains only the following:
#include <absl/container/flat_hash_map.h>
int foo(void) {
	absl::flat_hash_map<int,int> m;
	return 0;
}

For an actual project where I'm trying to use abseil, I get a linker error in debug mode that says the following:
/usr/sbin/ld: ../absail/absl/container/libabsl_container.a(raw_hash_set.cc.o): relocation R_X86_64_TPOFF32 against hidden symbol `_ZZN4absl18container_internal10RandomSeedEvE7counter' can not be used when making a shared object

The project in question is here.
Top level CmakeLists.txt
Shared object defining CMakeLists.txt
Abseil, at commit a06c4a1, is a submodule of my project. The build instructions are:

Clone bstaletic/ycmd and checkout aseil branch
git submodule update --init --recursive
mkdir build && cd build
cmake ../cpp -DCMAKE_BUILD_TYPE=Debug

Other build time dependencies are python headers. For python3 -DUSE_PYTHON2=OFF is needed.

Also, my Appveyor and Travis build fail with nonsense errors.
Appveyor: https://ci.appveyor.com/project/bstaletic/ycmd-noh9b/builds/20561052/job/y64dyb0cytehw06t
Travis: https://travis-ci.org/bstaletic/ycmd/builds/459085385
They are both mentioning (conflicting) redeclarations/redefinitions. This doesn't happen when I build on my own computer.

I'll look at the CI errors.  Could you try your example but with absl::core_headers instead of container and hash?  those two probably pull in a huge chunk of abseil between the two of them, whereas core_headers is the lowest-level target we have.

So, actual lists of pulled in dependencies:

absl::hash and absl::container

libabsl_dynamic_annotations.a
libabsl_internal_spinlock_wait.a
libabsl_int128.a
libabsl_numeric.a
libabsl_container.a
libabsl_base.a
libabsl_utility.a
libabsl_span.a
libabsl_internal_throw_delegate.a
libabsl_strings.a
libstr_format_extension_internal.a
libstr_format_internal.a
libabsl_str_format.a
libabsl_hash.a

just absl::core_headers

Building target my_lib explicitly didn't build any abseil component.

Getting back around to this.  We've been doing a lot of overhaul of our CMakeLists.txt files.  Is this still an issue?

The CI errors are different, and it definitely looks like an improvement.

Python 3.4 also has a dynamic_annotations.h header in which it defines AnnotateBenignRaceSized, though signatures don't match and it's causing Travis to fail.
On python2, however, travis reports the same linker error that I see.
MSVC 2015 and 2017 report the following error:

In int128.h lines 134 and 137 conflict, because, apparently wchar_t is the same as unsigned short. It's the declaration of absl::uint128::operator wchar_t and absl::uint128::operator unsigned short.
Same thing happens later on lines 478 and 471 for definitions.

Thanks for the update.
I'm a little confused, how is python being used here?

Our project links against libpython.so to expose some C++ classes/functions to python. That means there's #include <Python.h> in some place, that pulls in python's dynamic_annotations.h.
For the MSVC failures, if you think that is an okay solution, I can submit a PR that wraps the overloads in #ifdef _MSVC (or whatever the macro is).

Our project links against libpython.so to expose some C++ classes/functions to python. That means there's #include <Python.h> in some place, that pulls in python's dynamic_annotations.h.

cries.  We probably should have prepended AbslInternal to our names, and ABSL_ to the macros.  This will require some substantial migrations to fix as far as I can see.  Or Python could take an Abseil dep :P
For the MSVC that might work, but we would need to also release a migration tool for that as well, since that would be an api-breaking change.

Adding Alex who has more insight both on int128 and also the migration tools required for these bugfixes

cries. We probably should have prepended AbslInternal to our names, and ABSL_ to the macros. This will require some substantial migrations to fix as far as I can see. Or Python could take an Abseil dep :P

I took a quick look at dynamic_annotations.h and had a similar reaction when I saw that those things aren't namespaced.

For the MSVC that might work, but we would need to also release a migration tool for that as well, since that would be an api-breaking change.

According to compiler explorer wchar_t and unsigned short aren't the same and all trivial cases that I've tried on there actually allowed overloads on wchar_t/unsigned short. Still, Appveyor failed with the above mentioned error: https://ci.appveyor.com/project/bstaletic/ycmd-noh9b/builds/20825796/job/17hppomji75uemha#L412

For the MSVC bug, https://docs.microsoft.com/en-us/previous-versions/dh8che7s(v=vs.140) looks promising

Wow, thanks for that! Turns out, on MSVC, our project was explicitly using /Zc:wchar_t-. Though git blame wasn't useful to find out why as that flag was there since before the git repository was created, some... at least 5 years ago.
Anyway, Appveyor is healed.
That leaves us with the linker error and the conflict with the CPython function.
For the linker error, every search I've been able to make was about -fPIC or -shared missing somewhere. When I manually inline the absl::container_internal::RandomSeed() in absl::container_internal::ShouldInsertBackwards(), I get a slightly different linker error:
/usr/sbin/ld: ../absail/absl/container/libabsl_container.a(raw_hash_set.cc.o): relocation R_X86_64_TPOFF32 against `_ZZN4absl18container_internal21ShouldInsertBackwardsEmPaE7counter' can not be used when making a shared object; recompile with -fPIC

Indeed, all abseil components that are compiled are compiled into static libraries. Then I tried adding -fPIC to the global flags and it got linked correctly. But adding -fPIC manually and globally doesn't seem like the right thing to do. Did I miss anything?
Once again, thanks for the help.

For the linker error, this is what I'm currently doing:
list( APPEND LLVM_FLAGS "-fPIC" )
list( APPEND GCC_FLAGS "-fPIC" )

And this solved the linker error. I am fine with this, since -fPIC isn't global.

Let me check in to that.  I'm pretty sure we build with PIC internally, I'm surprised we don't externally.  I'm not sure if I missed it somewhere but can you detail the platform and toolchain you're using?
As for the MSVC bug, that's awesome!  I also wrote a change today to wrap the wchar_t typedefs so we're always picking up __wchar_t on MSVC.  So if for whatever reason you actually need that /Zwchar_t- option you should be good.

I'm able to reproduce the linker error on three completely different systems, all of which end up compiling without -fPIC.

My local - GCC 8.2.1, linux x86_64 or Clang 7.0.0
Travis - Ubuntu 14.04 GCC 4.9/Clang 3.4
CircleCI - macOS AppleClang <IP_ADDRESS>00038

With -fPIC and no /Zc:wchar_t-, "all" that's left is the conflicting dynamic_annotations.h, which is actually the same as the abseil one, only a couple years older (it says /* Copyright (c) 2008-2009, Google Inc.).

for -fFPIC we should add
set_property(TARGET ${_NAME} PROPERTY POSITION_INDEPENDENT_CODE ON)

just here:
https://github.com/abseil/abseil-cpp/blob/111ca7060a6ff50115ca85b59f6b5d8c8c5e9105/CMake/AbseilHelpers.cmake#L168-L170
src: https://cmake.org/cmake/help/latest/prop_tgt/POSITION_INDEPENDENT_CODE.html

Do we want to do that ourselves? Wouldn't that cause issues if our users didn't compile with PIC on?  Seems like we need to inherit that somehow from our users

I've tried it out on our project. Usually, compiling our benchmark looks like this:

Compile Boost.Filesystem and Boost.Regex into libBoostParts.a (static library with -fPIC)
Compile ycm_core.so, which is the C++ part of the project (dynamic  library with -fPIC)
Compile libbenchmark.a - the google benchmark library.
Link everything into a ycm_core_benchmarks executable.

I changed our CMakeLists.txt for ycm_core.so to compile a static library without -fPIC and left everything else the same. I confirmed that BoostParts was compiled with PIC and ycm_core without and the benchmarks worked.
Then I tried to compile our test suit and it worked as well. So current builds wouldn't be broken if PROPERTY POSITION_INDEPENDENT_CODE ON was set unconditionally.
However, I also measured the size and compile time of BoostParts with and without -fPIC. With -fPIC the size increased by 4kB (0.04%) and compile time increased by 0.03s (0.07%). In my opinion the added time and library size is negligible.

Yes, -fvisibility=hidden affects DSOs only. I am compiling Abseil into a DSO, otherwise relocation R_X86_64_TPOFF32 wouldn't be forbidden. -fvisibility=hidden made the DSO significantly smaller and even boosted performance a bit.
I've tried nm --dynamic ycm_core.so | grep absl which resulted in 0 symbols. nm ycm_core.so | grep absl however has shown 5252 symbols. So whatever links against my ycm_core.so won't be able to see any traces of abseil. This is the effect of -fvisibility=hidden.

I managed to create a minimal example that  shows the issue with missing -fPIC!
CMakeLists.txt:
cmake_minimum_required(VERSION 2.8.12)
project(my_project)
add_subdirectory(abseil-cpp)
set(THREADS_PREFER_PTHREAD_FLAG TRUE)
find_package (Threads REQUIRED)
add_library(my_lib SHARED foo.cpp)
target_link_libraries(my_lib absl::flat_hash_map Threads::Threads)

foo.cpp:
#include "abseil-cpp/absl/container/flat_hash_map.h"

int main(void) {
	absl::flat_hash_map<int, int> x;
	printf("%d\n", x.size());
}

Generate Makefile with cmake -DCMAKE_BUILD_TYPE=Debug and compile with make my_lib.
The linker error:
/usr/sbin/ld: abseil-cpp/absl/container/libabsl_internal_hashtablez_sampler.a(hashtablez_sampler.cc.o): relocation R_X86_64_TPOFF32 against `_ZZN4absl18container_internal12_GLOBAL__N_120GetGeometricVariableElE3rng' can not be used when making a shared object; recompile with -fPIC
/usr/sbin/ld: final link failed: nonrepresentable section on output
collect2: error: ld returned 1 exit status

I reproduced your error, and it looks like it's the rng in GetGeometricVariable.  However changing the rng to a static instead of thread_local reveals similar issues in the standard library.

usr/bin/ld: abseil-cpp/absl/container/libabsl_internal_hashtablez_sampler.a(hashtablez_sampler.cc.o): relocation R_X86_64_PC32 against symbol `_ZNSt14numeric_limitsIlE3maxEv' can not be used when making a shared object; recompile with -fPIC

Also, I tried building my_lib as a static library and everything worked perfectly.  I think the moral of the story here is you just have to use -fPIC for shared libraries.  Are there any objections to closing this at this point?

I don't mind closing the issue, but I've got a question. Currently I'm using list( APPEND LLVM_FLAGS "-fPIC" ) to insert -fPIC into abseil's flags. It feels like a hack to poke around, what I assumed are, abseil internals. Should I keep using LLVM_FLAGS or keep watching abseil development for a different, supported, way to insert necessary flags?

Looks like you want to use CMAKE_POSITION_INDEPENDENT_CODE as suggested by @Mizux earlier.
I added set(CMAKE_POSITION_INDEPENDENT_CODE TRUE) to your CMakeLists.txt file from above and confirmed everything built and linked.
I'm closing this, please feel free to reopen

Great, that worked! Thanks for helping out.


It worked for me after killing other containers and a docker system prune -a.


How to use C# Wix in my cake script?

I have a server machine in which i didn't installer Wix Toolset software. Instead included the Wix nuget in my cake script. What are the steps that i have to follow to compile my wix file?
Whether the wix nuget package included in cake will automatically download and install the wix in my server machine? Or else what i have to follow?

64 bit system

Windows Server 2012 R2

CI Server.

@vadivel1234 GitHub issues is for issues within Cake and not questions. I would suggest that you ask questions on StackOverflow using the cakebuild tag, or visit our Gitter chatrom.


scaleway-cli: 2.7.0 -> 2.8.0

Diff: https://github.com/scaleway/scaleway-cli/compare/v2.7.0...v2.8.0
Description of changes
https://github.com/scaleway/scaleway-cli/releases/tag/v2.8.0
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.


improved the dark mode feature of the "aboutus" section

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #2110
Description
I have updated the dark mode of the "about us" section.

Type of PR

[ ] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[ ] I have made this change from my own.
[ ] I have taken help from some online resources.
[ ] My code follows the style guidelines of this project.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers and screenshots after making the changes.

please review at the changes

should i close this PR or you have any other changes in mind?

No please don't close.I will try to make the changes the way u commented
On Tue, 2 Jul, 2024, 6:32 pm Riti Chandak, @.***> wrote:

@nandani-goyal https://github.com/nandani-goyal should i close this PR
or you have any other changes in mind?
—
Reply to this email directly, view it on GitHub
https://github.com/anuragverma108/SwapReads/pull/2142#issuecomment-2203102580,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEIMMFALMSO7YRJIDTQ4JGLZKKQGPAVCNFSM6AAAAABJ4G6XCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBTGEYDENJYGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Update scalaz-core to 7.4.0-M8

Updates org.scalaz:scalaz-core from 7.4.0-M7 to 7.4.0-M8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalaz", artifactId = "scalaz-core" } ]

labels: test-library-update, semver-pre-release

Superseded by #119.


New-mgDeviceManagementDeviceCompliancePolicy_Create Cannot create an abstract class

I'm importing a fully formed JSON, exported from another tenant, it looks like the request being sent by this command is truncating the input JSON, in the request body there appears to be multiple missing fields and values
[https://graph.microsoft.com/beta/deviceManagement/deviceCompliancePolicies]
Headers:
FeatureFlag                   : 00000043
Cache-Control                 : no-store, no-cache
User-Agent                    : Mozilla/5.0,(Windows NT 10.0; Microsoft Windows 10.0.19045; en-US),PowerShell/2024.2.2
Accept-Encoding               : gzip
SdkVersion                    : graph-powershell-beta/2.19.0
client-request-id             : cc1f5074-d62a-4378-a733-653c8b5c8146
Body:
"AdditionalProperties": {
<EMAIL_ADDRESS>[https://graph.microsoft.com/v1.0/$metadata#deviceManagement/deviceCompliancePolicies(id,displayName,description,scheduledActionsForRule())/$entity]
<EMAIL_ADDRESS>"#microsoft.graph.iosCompliancePolicy",
<EMAIL_ADDRESS>https://graph.microsoft.com/v1.0/$metadata#deviceManagement/deviceCompliancePolicies(guid)/microsoft.graph.iosCompliancePolicy/scheduledActionsForRule
},
"description": "Compliance Policy for Corporate iOS devices",
"displayName": "Import-test-MDM-comp",
"scheduledActionsForRule": [
{
"id": "5517726c-e0e8-4afc-9087-0380ea6bbc97"
}
]
}
DEBUG: ============================ HTTP RESPONSE ============================
Status Code:
BadRequest
Headers:
Vary                          : Accept-Encoding
Strict-Transport-Security     : max-age=31536000
request-id                    : 7e0df90c-e8ec-4bb4-85a1-f0f004f21e09
client-request-id             : cc1f5074-d62a-4378-a733-653c8b5c8146
x-ms-ags-diagnostic           : {"ServerInfo":{"DataCenter":"UK South","Slice":"E","Ring":"5","ScaleUnit":"003","RoleInstance":"LO2PEPF00003336"}}
Date                          : Thu, 01 Aug 2024 11:12:27 GMT
Body:
{
"error": {
"code": "ModelValidationFailure",
"message": "Cannot create an abstract class.",
"innerError": {
"message": "Cannot create an abstract class.",
"date": "2024-08-01T11:12:27",
"request-id": "7e0df90c-e8ec-4bb4-85a1-f0f004f21e09",
"client-request-id": "cc1f5074-d62a-4378-a733-653c8b5c8146"
}
}
}

Hi @stevejmonk, issues for the Graph PowerShell SDK itself should be filed in this repository: https://github.com/microsoftgraph/msgraph-sdk-powershell
If this is not an issue with one of the sample scripts, but the Graph PowerShell SDK itself, please file an issue there. Going to close this for now, but please let me know if I misunderstood and it can be re-opened.
It also may be worth looking at wrapping your GET request with .ToJsonString() from the initial tenant. For example:
(Get-mgDeviceManagementDeviceCompliancePolicy -DeviceCompliancePolicyId "FOO").ToJsonString()
Will return the raw JSON response, which may be easier to work with for policy import/export depending on your scenario rather than manipulating a complex object.


Intermittent CI failures

Lets post screenshots of intermittent CI failures here before we restart the build.
That way we can refer back to them when we go to investigate the issue properly.

https://github.com/shotover/shotover-proxy/issues/142 might resolve some of them

https://github.com/shotover/shotover-proxy/runs/4147769243?check_suite_focus=true


fix(deps): bump

Applied mkpr on undefined
/tmp/mkpr.sh

:tada: This PR is included in version 1.0.10 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.10 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Media Query not Actually Turning Off Sticky Behaviour

When using the 'media-query' attribute as described in the docs the sticky behaviour of the element does not stay off when the query matches. Instead, the 'isSticking' flag toggles on each scroll event. The result is that the sticky behaviour gets turned on and off and causes the scroll to jump back to the top of the page.

I have the same issue.

Try making the changes linked to above, @pbtura.
It works great for me if I change the first conditional in checkIfShouldStick() to:
if ($scope.disabled === true || mediaQueryMatches ()) {
    if(isSticking) unStickElement ();
    return false;
}

+1


Configurations to Consume Curl, Freetype2 and Icu Components in iTwinNativeThirdParty

This upgrade allow us to consume relevant configurations of Curl, Freetype2 and Icu components in iTwinNativeThirdParty. The reason of doing this upgrade is that now we want to consume the duplicate/similar components from a central location.
As the Curl component coming from iTwinNativeThirdParty is currently consuming ares version 1.18.1 that is why the makefile there do not have $(o)ares_rand$(oext) : $(AresLibDir)ares_rand.c ${MultiCompileDepends} but with this upgrade the component generated there will be on ares version 1.19.1 and need this statement which is already present on central location.
The Freetype2 component present at imodel-native has following additional statement in freetype2.mke which is not present in iTwinNativeThirdParty:
BUILD_NO_STACK_CHECK = 1   # Don't want to modify third party code, but hopefully these get fixed in a future version.
It seems to be added for ignoring warnings from the third-party code so I assume we do not need conditional execution for this statement.
Freetype2 component in iTwinNativeThirdParty is currently consuming version 2.12.1 and with this upgrade it will be on version 2.13.0 and consume the respective settings.

deferring to @chuckkir to approve; please wait on his approval before merging

sure

deferring to @chuckkir to approve; please wait on his approval before merging

sure but @chuckkir would be out probably until 26th and there are a couple of PR's in iTNTP that would need this change as a prerequisite.

just noticed hes out on vacation; lets go ahead and merge then


Raise ArgumentError when passing invalid keys to has_selector?

It's a relatively common misconception that you can use :content as a key - e.g.
has_selector?('h1', :content=>'wooo!')

which would silently pass, even when 'wooo!' is nowhere to be found.  This change should make that error much more obvious.
Related issues : https://github.com/jnicklas/capybara/issues/525
It would be nice to raise an error on passing a block in - eg
@session.should have_selector("//p") do |p_tag|
  p_tag.should have_selector("//a")
end

which seems to be a common error on people switching to capybara via webrat.  However, that's a bit more tricky and would probably need fixing at the rspec-matcher level, since the block doesn't make it as far as has_selector? and gets silently discarded.

ValidKeys on Selector could be replaced with something like this :
diff --git a/lib/capybara/selector.rb b/lib/capybara/selector.rb
index 1bff91d..0b85a04 100644
--- a/lib/capybara/selector.rb
+++ b/lib/capybara/selector.rb
@@ -15,6 +15,10 @@ module Capybara
       def remove(name)
         all.delete(name.to_sym)
       end
+
+      def valid_keys
+        all.map{|selector| selector.custom_filters.keys}.flatten.uniq
+      end
     end

     def initialize(name, &block)

?
I'm not sure what you mean about the implementation for checking query keys, though.  There's 3 places that keys passed to has_selector?() are used - node/matchers.rb, query.rb, and selector.rb.  Whichever one is responsible for checking the keys will have to also check the keys of the other 2.  I could move assert_valid_options to a class method to Query if you like?

Closing this pull request, we already have an open issue for this in #525, and I don't like this implementation


SourceKitLSP: use AbsolutePath to compute the filename

Rather than treating the filename as an opaque string and splitting on /, use AbsolutePath to perform the basename operation on the path. This ensures that we split the path properly on platforms which do not use the POSIX path separator /.

@swift-ci please test


Next breaking release (3.x.y) roadmap

Either remove stuff in destructors or remove close functions. But we can't let non-trivial class destructors be called by the GC.

<EMAIL_ADDRESS>Class destructors are not permitted to allocate since called by the GC.
Class destructors are best leaved empty or like in Glamour, with a message to stderr that doesn't allocate.

Either do not own Derelict.load calls, or allow to use a custom dynlib path. For SDL, allow to use a custom runtime version since DerelictSDL allows it.
remove calls to .unload() for Derelict loaders, this might hide unreleased objects, but at least, it won't prevent to work with other libraries using derelict
try to find a way to have scoped ownership for resources

Unfortunately would be a breaking change for anything that rely on GC behaviour to work now.

We need an bool isInGC()  function

Final solution for both classes and struct resources (now that a struct destructor could be called for the GC too).
In a close() function, if called by the GC, printf a warning and leak, else regular clean-up (RAII / Unique / scoped! was used).

Since this will be a breaking release, you can switch to using std.experimental.logger from Phobos, instead of it being a DUB dependency.

Not before a while, since std.experimental.logger only exist since DMDFE 2.067, and the latest GDC and LDC are still 2.066.

Yep, only if LDC and GDC move to 2.067.

remove gfm.math.funcs.min and gfm.math.funcs.max

db60dd1c512df7db4eb2c40d1ae57e644091c5e1
In GFM 3.x.y, actual resource clean-up will crash when called by the GC. This covers all cases and combinations.
close() methods will be removed in favor of destroy since what destructors will only ever do is call close().
Destructors will be written in a way that support multiple calls.

Removed support for 2.065 frontends in gfm:math.
New dependency: imageformats, replaces stb_image translation with shorter, more idiomatic code that is fixable. JPEG works again. https://github.com/lgvz/imageformats

Version 3.0.0 is out.
Changelog added to the Wiki: https://github.com/d-gamedev-team/gfm/wiki/Changelog


Should labelTagName default to LABEL?

In https://github.com/phetsims/scenery/issues/748 I made it default to LABEL, but perhaps it should be a p or something. @jessegreenberg @mbarlow12 what do you think? What is the best default?

I changed the default label tag name to 'p', but first I had to go through commits made in #748  called "remove unneeded calls to options with default values". In those commits I removed "labelTagName: 'label'` options. Manually reverted above.
@mbarlow12 could you please review this.

Yikes this is old! @zepumph all looks good. Closing.


MountManager support

Hello,
Does the latest version of DokanNet support the latest version of Dokany, with MountManager?
Thanks

Hi,
Yes, it work. (tested by @viciousviper )


update TensorFlow version to the beta

Nice that the fix for https://github.com/tensorflow/tensorflow/issues/26098 made into the beta. Thanks!


Milestone3 Feedback

Group46 Feedback
Update on the process: we decided to give everybody feedback on their Milestone 3, and then give you all an opportunity to re-submit after applying the feedback.
There are some items here that will be noted as "for Milestone 5" - for those items, we don't expect you to complete that until Milestone 5.
For all other feedback items, you should apply the feedback and resubmit on Gradescope (we will reopen the submission page later this week).
You should take about one week from when you receive your feedback to resubmit your milestone, though this is somewhat flexible. The absolute last day to re-submit Milestone 3 is Nov. 24 at 6 PM (no grace period).
Group feedback

please show your work to Dr. Moosvi during office hours to get his opinion on how to improve your work.

-Make sure you run a spell check to catch spelling errors, for e.g, this one: https://github.com/jupyterlab-contrib/spellchecker
Analysis 1 (Sumer)
Major Feedback

research interest is not complex enough.

I see some visualizations present, but there is no analysis done and no explanation for what your graphs mean.

You must analyze the visualizations with written statements. Answering the research question should be the primary goal of the project.

For Task4, you are using hard coded path.

For project_functions1.py, you are using a hard coded path. method chaining is not done properly, Please revise your work.

Minor Feedback
Points of Pride
Analysis 2 (Raghav)
Major Feedback (for Milestone 5)

research interest is not complex enough.

I see some visualizations present, but there is no analysis done and no explanation for what your graphs mean.

You must analyze the visualizations with written statements. Answering the research question should be the primary goal of the project.

For project_functions2.py, something is wrong with it and it is not showing properly, Please revise your work.

Minor Feedback

Scale of count plot needs to be adjusted.

Scatter plot is not showing properly.

Points of Pride
Analysis 3 ()

Empty analysis files. This is very concerning! Please let us know if there is a problem in your group. If a teammate has dropped the course, please move their content to the ungraded folder so it isn't graded.

Major Feedback (for Milestone 5)
Minor Feedback
Points of Pride

HelloI have worked on milestone 1 with the other two members of my group and we submitted the same together I wonder why my submission is not visible, if anything you can ask the concerned group members.Thanks and regards Jusnoor Kaur Sachdeva 12543336Sent from my iPhoneOn 16-Nov-2022, at 12:39 PM, Iadel95 @.***> wrote:
Assigned #1 to @jusnoorkaur.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: @.***>


Refactor-ish tasks for version 3

Some things to try for the next release, no guarantee I'll get around to them but it'll be neat to help clean up the codebase while I'm working on it:

[ ] ~Add extension methods to traverse models as if they were DOM elements, namely the ability to get the 'first element child' like https://developer.mozilla.org/en-US/docs/Web/API/Element/firstElementChild~
[ ] ~Convert the ChildModelIterator into a general purpose model iterator.  In conjunction with the above, that can replace the need for a specific child model iterator.~
[x] Find some way to better identify the model vs event extension methods in IModelExtensions: I got confused recently as it's not always clear which methods operate on what kind of objects
[x] The whitespace creation in the insertModelWithWhitespace extension method could do with some work - it inserts Windows line ends instead of platform-specific ones, and its opposite removeModel doesn't have a "with whitespace" version which could clear up some formatting issues in the resulting output

Worked on what I could, but wow whitespace handling is a little annoying when you have to do it yourself!  As for the other stuff, it's also kind of in the difficult basket no wonder it's been kinda ad-hoc all these years! 😅


feat: accordion copilot-11963

This PR introduces offset annotations for accordion and accordion items which will be used in the body field of a content type.
Accordion is used to group contextual data together in the form of header and content

Accordion holds the attributes of layout and anchorName
AccordionItem has attributes as header and panel.

Header stores the title of the content in the panel.
Panel holds the content

@copilot-robot prerelease

@copilot-robot prerelease

@copilot-robot prerelease

@copilot-robot prerelease

@copilot-robot prerelease

@copilot-robot prerelease

@copilot-robot prerelease

@copilot-robot prerelease


V5.32 documentation

Needs one approval.
DO NOT MERGE.

@justinegeffen @lindy65 If one of you can help approve this tomorrow (Monday), will be much appreciated 🙏


Problem running tests with Swift 5.5.2

I've been using this action with Swift 5.5.1 for the ParseSwift repo and have ran into very little issues. Every once in awhile 1/10 times it doesn't build the project and I need to rerun my CI; not a big deal.
For Swift 5.5.2, this issue is consistent as I can't run the tests at all. In addition, the Swift 5.5.2 takes a lot longer to build. I do have more async/await files in 5.5.2 (I ignore these in 5.5.1), but the difference in time is on 5.5.1 takes ~ 3 minutes to build and run the whole test suite and in 5.5.2 takes > 5 minutes to build, start the test and fail on the first test. My setup in actions is below:
windows:
    runs-on: windows-2019
    steps:
      - uses: actions/checkout@v2
      - uses: MaxDesiatov/swift-windows-action@v1
        with:
          swift-version: "5.5.2"
          shell-action: swift test --enable-test-discovery -v
      #    shell-action: swift test --enable-test-discovery --enable-code-coverage -v
      #- name: Upload coverage to Codecov
      #  uses: codecov/codecov-action@v2
      #  with:
      #    env_vars: WINDOWS
      #    fail_ci_if_error: false

Failed action in 5.5.2 with the above action setup: https://github.com/parse-community/Parse-Swift/runs/4843124003?check_suite_focus=true#step:3:7963
Successful action in 5.5.1: https://github.com/parse-community/Parse-Swift/runs/4842818376?check_suite_focus=true#step:3:7391
On both versions, the CI is build/test/passing in Linux using the swifty-linux-action which is why I believe it should build/pass in Windows. You can see the PR where I was testing this here: https://github.com/parse-community/Parse-Swift/pull/320

Thanks for reporting the issue! Would you mind trying if it also reproducible with this action? This would help us understand if the problem is specific to the action or to Swift 5.5.2 distribution for Windows in general https://github.com/compnerd/gha-setup-swift

Sure, I'll try and report back soon...

It looks like it's having the same issue: swift-5.5.2-RELEASE
Below is what I tried:
windows:
    runs-on: windows-2019
    steps:
      - uses: compnerd/gha-setup-swift@main
        with:
          branch: swift-5.5.2-release
          tag: 5.5.2-RELEASE

      - uses: actions/checkout@v2
      - run: swift build
      - run: swift test --enable-test-discovery --enable-code-coverage -v
    #steps:
    #  - uses: actions/checkout@v2
    #  - uses: MaxDesiatov/swift-windows-action@v1
    #    with:
    #      swift-version: "5.5.1"
    #      shell-action: swift test --enable-test-discovery --enable-code-coverage -v
      - name: Upload coverage to Codecov
        uses: codecov/codecov-action@v2
        with:
          env_vars: WINDOWS
          fail_ci_if_error: false

I checked your PR but could find logs for Windows 5.5.2. What exact error messages for test failures are you seeing? Would there be a way to share the whole build/test log for Windows 5.5.2 somewhere to examine?
Thanks!

What seems weird is it doesn't have any trouble building any of the async/await files or the test files that test them.  Also, there's no async/await tests in APICommandTests, so I would expect that all of the tests in this file pass, but fail on something like, ParseAnanlyticsAsyncTests. I made sure to name files I conduct async and combine tests with Async and Combine respectively.

I think that this might be a crash that I've seen with XCTest. I'm not sure what's the cause of it yet.  It really needs a build and someone to investigate it.  There's a bunch of overlap in terms of deadlines (5.5, 5.6, rebranch) and I need help to cover everything.


Refactor JSONSchema external format

Added protocol, specification, meta models
Added Parsers and Composers for specifications
Added Parser and Compiler for meta-model

Closing this PR as it has conflicts and is still in draft. Please re-open if required.


Don't get a TLS cert for Rancher and 404 error on UI domain

Hi Vito,
sorry for bothering you again...
I followed your instructions from #13 to install rancher (with my cluster you already now from #87 and #88 using proxy protocol at the load balancer).
The installation itself worked without problems but I get a 404 when accessing the rancher UI (which looks like the same issue as in #50, but unfortunately there is no solution given, other than something like "helm screwed it up and suddenly it works").
That's what I did:
$ RANCHER_DOMAIN=rancher.MY.DOMAIN
$<EMAIL_ADDRESS>
$ helm upgrade --install \
    --namespace cattle-system \
    --set hostname=$RANCHER_DOMAIN \
    --set letsEncrypt.email=$RANCHER_LE_MAIL \
    --set ingress.tls.source=letsEncrypt \
    rancher \
    rancher-stable/rancher
...

$ kubectl -n cattle-system rollout status deploy/rancher
Waiting for deployment "rancher" rollout to finish: 0 of 3 updated replicas are available...
Waiting for deployment "rancher" rollout to finish: 1 of 3 updated replicas are available...
Waiting for deployment "rancher" rollout to finish: 2 of 3 updated replicas are available...
deployment "rancher" successfully rolled out

But when I try to access the rancher UI at http(s)://rancher.MY.DOMAIN I get a nginx 404 error page (and a self sign cert error on the https URL).
Interestingly I get no log output from the ingress-nginx-controller when accessing the domain, so it looks the requests are handled by an earlier instance (probably from the Hetzner load balancer?).
Here some debug information from cert-manager etc.
$ kubectl -n cert-manager logs cert-manager-67599dcc49-6cjlf -f
I0713 15:01:35.593129       1 setup.go:111] cert-manager/issuers "msg"="generating acme account private key" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-production" "related_resource_namespace"="cattle-system" "resource_kind"="Issuer" "resource_name"="rancher" "resource_namespace"="cattle-system" "resource_version"="v1"
I0713 15:01:35.595215       1 conditions.go:201] Setting lastTransitionTime for Certificate "tls-rancher-ingress" condition "Ready" to 2022-07-13 15:01:35.594377499 +0000 UTC m=+115760.151940114
I0713 15:01:35.595818       1 trigger_controller.go:200] cert-manager/certificates-trigger "msg"="Certificate must be re-issued" "key"="cattle-system/tls-rancher-ingress" "message"="Issuing certificate as Secret does not exist" "reason"="DoesNotExist"
I0713 15:01:35.595839       1 conditions.go:201] Setting lastTransitionTime for Certificate "tls-rancher-ingress" condition "Issuing" to 2022-07-13 15:01:35.595836264 +0000 UTC m=+115760.153398879
I0713 15:01:35.620217       1 controller.go:161] cert-manager/certificates-trigger "msg"="re-queuing item due to optimistic locking on resource" "key"="cattle-system/tls-rancher-ingress" "error"="Operation cannot be fulfilled on certificates.cert-manager.io \"tls-rancher-ingress\": the object has been modified; please apply your changes to the latest version and try again"
I0713 15:01:35.620289       1 trigger_controller.go:200] cert-manager/certificates-trigger "msg"="Certificate must be re-issued" "key"="cattle-system/tls-rancher-ingress" "message"="Issuing certificate as Secret does not exist" "reason"="DoesNotExist"
I0713 15:01:35.620306       1 conditions.go:201] Setting lastTransitionTime for Certificate "tls-rancher-ingress" condition "Issuing" to 2022-07-13 15:01:35.620301974 +0000 UTC m=+115760.177864606
I0713 15:01:35.785737       1 setup.go:219] cert-manager/issuers "msg"="ACME server URL host and ACME private key registration host differ. Re-checking ACME account registration" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-production" "related_resource_namespace"="cattle-system" "resource_kind"="Issuer" "resource_name"="rancher" "resource_namespace"="cattle-system" "resource_version"="v1"
I0713 15:01:35.925798       1 controller.go:161] cert-manager/certificates-key-manager "msg"="re-queuing item due to optimistic locking on resource" "key"="cattle-system/tls-rancher-ingress" "error"="Operation cannot be fulfilled on certificates.cert-manager.io \"tls-rancher-ingress\": the object has been modified; please apply your changes to the latest version and try again"
I0713 15:01:35.931658       1 conditions.go:261] Setting lastTransitionTime for CertificateRequest "tls-rancher-ingress-zgfrg" condition "Approved" to 2022-07-13 15:01:35.931650704 +0000 UTC m=+115760.489213325
I0713 15:01:35.965291       1 conditions.go:261] Setting lastTransitionTime for CertificateRequest "tls-rancher-ingress-zgfrg" condition "Ready" to 2022-07-13 15:01:35.965284041 +0000 UTC m=+115760.522846655
I0713 15:01:36.559589       1 setup.go:309] cert-manager/issuers "msg"="verified existing registration with ACME server" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-production" "related_resource_namespace"="cattle-system" "resource_kind"="Issuer" "resource_name"="rancher" "resource_namespace"="cattle-system" "resource_version"="v1"
I0713 15:01:36.559692       1 conditions.go:95] Setting lastTransitionTime for Issuer "rancher" condition "Ready" to 2022-07-13 15:01:36.559683198 +0000 UTC m=+115761.117245844
I0713 15:01:36.589541       1 setup.go:202] cert-manager/issuers "msg"="skipping re-verifying ACME account as cached registration details look sufficient" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-production" "related_resource_namespace"="cattle-system" "resource_kind"="Issuer" "resource_name"="rancher" "resource_namespace"="cattle-system" "resource_version"="v1"
E0713 15:01:38.959554       1 controller.go:210] cert-manager/challenges/scheduler "msg"="error scheduling challenge for processing" "error"="Operation cannot be fulfilled on challenges.acme.cert-manager.io \"tls-rancher-ingress-zgfrg-3634216738-4270270854\": the object has been modified; please apply your changes to the latest version and try again" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1"
I0713 15:01:40.303308       1 pod.go:71] cert-manager/challenges/http01/ensurePod "msg"="creating HTTP01 challenge solver pod" "dnsName"="rancher.MY.DOMAIN" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1" "type"="HTTP-01"
I0713 15:01:40.357402       1 pod.go:59] cert-manager/challenges/http01/selfCheck/http01/ensurePod "msg"="found one existing HTTP01 solver pod" "dnsName"="rancher.MY.DOMAIN" "related_resource_kind"="Pod" "related_resource_name"="cm-acme-http-solver-n2vkp" "related_resource_namespace"="cattle-system" "related_resource_version"="v1" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1" "type"="HTTP-01"
I0713 15:01:40.357540       1 service.go:43] cert-manager/challenges/http01/selfCheck/http01/ensureService "msg"="found one existing HTTP01 solver Service for challenge resource" "dnsName"="rancher.MY.DOMAIN" "related_resource_kind"="Service" "related_resource_name"="cm-acme-http-solver-k87jj" "related_resource_namespace"="cattle-system" "related_resource_version"="v1" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1" "type"="HTTP-01"
I0713 15:01:40.357620       1 ingress.go:99] cert-manager/challenges/http01/selfCheck/http01/ensureIngress "msg"="found one existing HTTP01 solver ingress" "dnsName"="rancher.MY.DOMAIN" "related_resource_kind"="Ingress" "related_resource_name"="cm-acme-http-solver-m5tfr" "related_resource_namespace"="cattle-system" "related_resource_version"="v1" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1" "type"="HTTP-01"
E0713 15:01:40.548783       1 sync.go:186] cert-manager/challenges "msg"="propagation check failed" "error"="wrong status code '404', expected '200'" "dnsName"="rancher.MY.DOMAIN" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1" "type"="HTTP-01"
I0713 15:01:40.566349       1 pod.go:59] cert-manager/challenges/http01/selfCheck/http01/ensurePod "msg"="found one existing HTTP01 solver pod" "dnsName"="rancher.MY.DOMAIN" "related_resource_kind"="Pod" "related_resource_name"="cm-acme-http-solver-n2vkp" "related_resource_namespace"="cattle-system" "related_resource_version"="v1" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1" "type"="HTTP-01"
I0713 15:01:40.567110       1 service.go:43] cert-manager/challenges/http01/selfCheck/http01/ensureService "msg"="found one existing HTTP01 solver Service for challenge resource" "dnsName"="rancher.MY.DOMAIN" "related_resource_kind"="Service" "related_resource_name"="cm-acme-http-solver-k87jj" "related_resource_namespace"="cattle-system" "related_resource_version"="v1" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1" "type"="HTTP-01"
I0713 15:01:40.567890       1 ingress.go:99] cert-manager/challenges/http01/selfCheck/http01/ensureIngress "msg"="found one existing HTTP01 solver ingress" "dnsName"="rancher.MY.DOMAIN" "related_resource_kind"="Ingress" "related_resource_name"="cm-acme-http-solver-m5tfr" "related_resource_namespace"="cattle-system" "related_resource_version"="v1" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1" "type"="HTTP-01"
E0713 15:01:40.575406       1 sync.go:186] cert-manager/challenges "msg"="propagation check failed" "error"="wrong status code '404', expected '200'" "dnsName"="rancher.MY.DOMAIN" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1" "type"="HTTP-01"
I0713 15:01:40.787889       1 setup.go:202] cert-manager/issuers "msg"="skipping re-verifying ACME account as cached registration details look sufficient" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-production" "related_resource_namespace"="cattle-system" "resource_kind"="Issuer" "resource_name"="rancher" "resource_namespace"="cattle-system" "resource_version"="v1"
I0713 15:01:50.550420       1 pod.go:59] cert-manager/challenges/http01/selfCheck/http01/ensurePod "msg"="found one existing HTTP01 solver pod" "dnsName"="rancher.MY.DOMAIN" "related_resource_kind"="Pod" "related_resource_name"="cm-acme-http-solver-n2vkp" "related_resource_namespace"="cattle-system" "related_resource_version"="v1" "resource_kind"="Challenge" "resource_name"="tls-rancher-ingress-zgfrg-3634216738-4270270854" "resource_namespace"="cattle-system" "resource_version"="v1" "type"="HTTP-01"

$ kubectl get certificate -n cattle-system
NAME                  READY   SECRET                AGE
tls-rancher-ingress   False   tls-rancher-ingress   36m

$ kubectl describe certificate -n cattle-system
Name:         tls-rancher-ingress
Namespace:    cattle-system
Labels:       app=rancher
              app.kubernetes.io/managed-by=Helm
              chart=rancher-2.6.6
              heritage=Helm
              release=rancher
Annotations:  <none>
API Version:  cert-manager.io/v1
Kind:         Certificate
Metadata:
  Creation Timestamp:  2022-07-13T15:01:35Z
  Generation:          1
  Managed Fields:
   ...
Spec:
  Dns Names:
    rancher.MY.DOMAIN
  Issuer Ref:
    Group:      cert-manager.io
    Kind:       Issuer
    Name:       rancher
  Secret Name:  tls-rancher-ingress
  Usages:
    digital signature
    key encipherment
Status:
  Conditions:
    Last Transition Time:        2022-07-13T15:01:35Z
    Message:                     Issuing certificate as Secret does not exist
    Observed Generation:         1
    Reason:                      DoesNotExist
    Status:                      False
    Type:                        Ready
    Last Transition Time:        2022-07-13T15:01:35Z
    Message:                     Issuing certificate as Secret does not exist
    Observed Generation:         1
    Reason:                      DoesNotExist
    Status:                      True
    Type:                        Issuing
  Next Private Key Secret Name:  tls-rancher-ingress-bwtw5
Events:
  Type    Reason     Age   From                                       Message
  ----    ------     ----  ----                                       -------
  Normal  Issuing    51m   cert-manager-certificates-trigger          Issuing certificate as Secret does not exist
  Normal  Generated  51m   cert-manager-certificates-key-manager      Stored new private key in temporary Secret resource "tls-rancher-ingress-bwtw5"
  Normal  Requested  51m   cert-manager-certificates-request-manager  Created new CertificateRequest resource "tls-rancher-ingress-zgfrg"

Any idea what I did wrong here?
Thanks!

@jr-dimedis maybe two things to check:

you can use watchIngressWithoutClass: "true" in your ingress-nginx.yaml

controller:
  kind: DaemonSet
  watchIngressWithoutClass: "true"
  ingressClassResource:
    default: "true"
  config:
    use-forwarded-headers: "true"
    compute-full-forwarded-for: "true"
    use-proxy-protocol: "true"
  service:
    annotations:
      load-balancer.hetzner.cloud/location: nbg1
      load-balancer.hetzner.cloud/name: my-workloads
      load-balancer.hetzner.cloud/use-private-ip: "true"
      load-balancer.hetzner.cloud/algorithm-type: least_connections
      load-balancer.hetzner.cloud/hostname: lb.my-domain.com
      load-balancer.hetzner.cloud/uses-proxyprotocol: "true"
      load-balancer.hetzner.cloud/http-redirect-https: "false"

My Rancher Domain is a CNAME for lb.my-domain.com - check your DNS-record

Hey @Privatecoder!
My DNS was Ok. But I applied all your settings - and yes, now it works! :) Thanks a bunch!!!
I checked the docs for watchIngressWithoutClass and from my understanding this is necessary, because Rancher's ingress obviously does not set an ingressClassName so there was no ingress controller responsible for it? Is this interpretation correct?
Thanks!

Cool & yes, this is also my understanding of this setting.


fix zh_Hant_TW translations

Hi, I am a Taiwanese Programmer.
I'm using flask-admin in my project, but the translation is not accurate.
I modified some of the text to match the majority of usage.

Thanks @nurockplayer !

Can you tell me how to use translations with flask admin  ?


ServiceTimeout

Describe the bug
The issue I have reported earlier started to appear frequently again. I am utilizing the Microsoft Service in UK-South.
Please see the link to that case below:
https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/490
To Reproduce
SessionId: 5be2ed83c1554f80a906cc4dab152704
SessionId: 7942ec015c8d48d7810fee563850a32e
SessionId: 650e33483de34fd0a808553562810ec1
SessionId: f0f8da0e6aa24c40bfa109589e77078e
SessionId: 24c0fc3da74a40df950e418d31701648
SessionId: ea4ef226afc74015b14b0b0eb666e6b9
SessionId: bfcd95e732824e4fbfba580e5e97571d
SessionId: 034c278e6df64432830353a8fa26064e
SessionId: 034c278e6df64432830353a8fa26064e
More detailed outputs:
[Thu, 20 May 2021 17:19:08 GMT] [Transcription Engine] [Error Cancelled] [ServiceTimeout] [Due to service inactivity, the client buffer exceeded
maximum size. Resetting the buffer. SessionId: 5be2ed83c1554f80a906cc4dab152704]
[Thu, 20 May 2021 17:19:08 GMT] [Transcription Engine] [Stopping continuous recognition]
[Thu, 20 May 2021 17:19:08 GMT] [Transcription Engine] [Error Cancelled] [RuntimeError] [0x13 (SPXERR_START_RECOGNIZING_INVALID_STATE_TRANSITION
)
[CALL STACK BEGIN]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x201de0) [0x7fba55a99de0]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x2021a7) [0x7fba55a9a1a7]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x202b32) [0x7fba55a9ab32]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x1ca2e6) [0x7fba55a622e6]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(std::__future_base::_State_baseV2::_M_do_set(std::funct
ion<std::unique_ptr<std::__future_base::_Result_base, std::__future_base::_Result_base::_Deleter> ()>, bool)+0x25) [0x7fba559c298b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xea99) [0x7fba8dc23a99]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x15c033) [0x7fba559f4033]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x15cd23) [0x7fba559f4d23]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x12be36) [0x7fba559c3e36]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x1ae9a3) [0x7fba55a469a3]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x10de44) [0x7fba559a5e44]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb8c80) [0x7fba8c934c80]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7fba8dc1c6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fba8e35751d]
[CALL STACK END]
SessionId: 5be2ed83c1554f80a906cc4dab152704]
[Thu, 20 May 2021 14:17:14 GMT] [Transcription Engine] [Error Cancelled] [ServiceTimeout] [Due to service inactivity, the client buffer exceeded maximum size. Resetting the buffer. SessionId: 034c278e6df64432830353a8fa26064e]
[Thu, 20 May 2021 14:17:14 GMT] [Transcription Engine] [Stopping continuous recognition]
[Thu, 20 May 2021 14:17:14 GMT] [Transcription Engine] [Error Cancelled] [RuntimeError] [0x13 (SPXERR_START_RECOGNIZING_INVALID_STATE_TRANSITION)
[CALL STACK BEGIN]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x201de0) [0x7fba55a99de0]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x2021a7) [0x7fba55a9a1a7]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x202b32) [0x7fba55a9ab32]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x1ca2e6) [0x7fba55a622e6]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(std::__future_base::_State_baseV2::_M_do_set(std::function<std::unique_ptr<std::__future_base::_Result_base, std::__future_base::_Result_base::_Deleter> ()>, bool)+0x25) [0x7fba559c298b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xea99) [0x7fba8dc23a99]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x15c033) [0x7fba559f4033]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x15cd23) [0x7fba559f4d23]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x12be36) [0x7fba559c3e36]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x1ae9a3) [0x7fba55a469a3]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x10de44) [0x7fba559a5e44]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb8c80) [0x7fba8c934c80]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7fba8dc1c6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fba8e35751d]
[CALL STACK END]
SessionId: 034c278e6df64432830353a8fa26064e]
[Thu, 20 May 2021 13:36:22 GMT] [Transcription Engine] [Error Cancelled] [ServiceTimeout] [Due to service inactivity, the client buffer exceeded maximum size. Resetting the buffer. SessionId: 7e19a3d41c7a46d2b1215325d71792d9]
[Thu, 20 May 2021 13:36:22 GMT] [Transcription Engine] [Stopping continuous recognition]
[Thu, 20 May 2021 13:36:22 GMT] [Transcription Engine] [Error Cancelled] [RuntimeError] [0x13 (SPXERR_START_RECOGNIZING_INVALID_STATE_TRANSITION)
[CALL STACK BEGIN]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x201de0) [0x7fba55a99de0]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x2021a7) [0x7fba55a9a1a7]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x202b32) [0x7fba55a9ab32]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x1ca2e6) [0x7fba55a622e6]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(std::__future_base::_State_baseV2::_M_do_set(std::function<std::unique_ptr<std::__future_base::_Result_base, std::__future_base::_Result_base::_Deleter> ()>, bool)+0x25) [0x7fba559c298b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xea99) [0x7fba8dc23a99]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x15c033) [0x7fba559f4033]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x15cd23) [0x7fba559f4d23]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x12be36) [0x7fba559c3e36]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x1ae9a3) [0x7fba55a469a3]
/tmp/speech-sdk-native-3276505505964877569/libMicrosoft.CognitiveServices.Speech.core.so(+0x10de44) [0x7fba559a5e44]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb8c80) [0x7fba8c934c80]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7fba8dc1c6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fba8e35751d]
[CALL STACK END]
SessionId: 7e19a3d41c7a46d2b1215325d71792d9]
Expected behavior
Version of the Cognitive Services Speech SDK
client-sdk-1.16.jar
Platform, Operating System, and Programming Language
openjdk 1.8
ubuntu 16.04 LTS
Additional context
Once some fixed were applied, the issue appeared to be resolved for several months, however, later on reappeared again

@johnpaulu Thanks for the report, could you please update to the latest Speech SDK version 1.17.0 ? We have improvements to the problem seen here "Due to service inactivity, the client buffer exceeded". Let us know if that helps.

Thanks, it helped to significantly reduce those errors, but still we have experienced one today
Fri, 21 May 2021 14:18:09 GMT
Due to service inactivity, the client buffer exceeded maxim
um size. Resetting the buffer. SessionId: c47dfcf437564c9796352a1485636101

and now also second time today after the upgrade to speech sdk 1.17
[Fri, 21 May 2021 15:26:17 GMT] [Transcription Engine] [Error Cancelled] [ServiceTimeout] [Due to service inactivity, the client buffer exceeded maximum size. Resetting the buffer. SessionId: e1b34d717b8e4fd49e30f7fdfd0085f2]

and also third one
[Fri, 21 May 2021 15:26:17 GMT] [Transcription Engine] [Error Cancelled] [ServiceTimeout] [Due to service inactivity, the client buffer exceeded maximum size. Resetting the buffer. SessionId: e1b34d717b8e4fd49e30f7fdfd0085f2]
Thanks a lot for looking into that

@johnpaulu Could you please provide SDK log by following these instructions?
https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/how-to-use-logging

Please find the attached SDK logs below for 4 different cases. Thanks.

stt_2021-05-22_e7305372-f794-4756-98d3-d48b8881657a.txt
stt_2021-05-22_ff9ca2c6-a8c1-43f8-b14b-18b0bdf02213.txt

stt_2021-05-22_8a03fd79-59bd-44cd-8296-d1e9af7f4b97.txt.zip

and the last one
stt_2021-05-22_b759373f-9734-4802-b1d5-dc19d1c00196.txt.zip

@johnpaulu Thank you for the logs. Looking at it now.

@johnpaulu Can you please try the following? Set this string property on SpeechConfig to increase the client buffer size. Do a few runs and share new logs. If you see ServiceTimeout error, certainly share that log. But even if you don't see, please share a couple of logs from good runs:
config.SetProperty("SPEECH-MaxBufferSizeMs", "90000");
Thanks,
Darren

please find below

sdk logs 1.zip

sdk logs 2.zip

thanks

Thanks @johnpaulu, looking at the logs now

@johnpaulu are you using Phrase List Grammar in your recognition sessions?
https://docs.microsoft.com/en-us/dotnet/api/microsoft.cognitiveservices.speech.phraselistgrammar?view=azure-dotnet

No, as indicated in my previous ticket, I am using continuousRecognitionWithFileAsync sample from https://github.com/Azure-Samples/cognitive-services-speech-sdk/blob/master/samples/java/jre/console/src/com/microsoft/cognitiveservices/speech/samples/console/SpeechRecognitionSamples.java

I've looked at the logs. I am following up with the speech service team so they can look at telemetry for your session IDs, to understand why the service slows down after about 10 minutes of recognition. I will give update here once I have more info. As a work around, we recommend using Batch Transcription if you need to transcribe multiple long WAV files. Sample code for Batch Transcription can be found here
Darren

@johnpaulu I heard back from our Speech Service folks that there was a recent regression in speech recognition response time when your requests hits a new pod. If you transcribe long WAV file, there is a reconnection between the SpeechSDK client and the Service that happens every 10 minutes, and that may result in the request falling on a new pod of machines in the service. They are working hard to fix it, but I don't have an estimated time for the fix yet. The work around for now is to try and increase the value of "SPEECH-MaxBufferSizeMs" even further, or switch to using Batch Transcription as mentioned in my previous comment.

I am also having the same error that seems unrecoverable even if I recreate the stream and speech recognizer.  We are using a PushAudioStream in eastus and it runs fine for quite some time then it starts getting in bad shape after maybe an hour or more.
07-16 16:30:02.995:  Reason=Error ErrorDetails=Due to service inactivity, the client buffer exceeded maximum size. Resetting the buffer. SessionId: 3086c544e32935a488bc94fd9ab6381c
07-16 16:30:02.995: Reason=Error ErrorDetails=Due to service inactivity, the client buffer exceeded maximum size. Resetting the buffer. SessionId: 3086c544e32935a488bc94fd9ab6381c
I don't think this is local buffer issue it seems more like the Speech Service gets in a bad state.  We are only ever passing in 10 seconds or so of audio at a time and are running RecognizeOnceAsync.  This is also running on an Android 8.1 device.

Closing since there was no activity here.


fix: require release-name to have <= 40 characters

What issues does your PR fix?

fixes #588

What does your PR do?

Lowers the maximum length of the helm release name to 40 (down from 43)
This is needed because the embedded PostgreSQL and Redis charts will create a StatefulSets having a name that is 54 characters long when the helm release is 41 characters long, making it unable to create Pods (https://github.com/kubernetes/kubernetes/issues/64023)
As an escape hatch for people with existing deployments that have release names between 41 and 43 characters, a hidden value called allowLongReleaseName has been added, which reverts to the previous limit of 43.

Checklist
For all Pull Requests

[x] Commits are signed off
[x] Commits have semantic messages
[x] Documentation updated
[x] Passes ct linting

For releasing ONLY

[ ] Chart.yaml version bumped
[ ] CHANGELOG.md updated

@seunggabi thanks heaps for finding this issue!
Hopefully, we can collaborate more in the future.


ensure that server and client implementation return the same types

our gridproxy go client implements the Client interface.
but there is actually no guarantee that the http server will return the same types.
the server then should have a member that implements the client interface.

is the PR scope still the same for the issue?
if not please close and create another issue

yes it's the same, the pr only resolves this issue. there're just some conflicts, will resolve them

resolved conflicts


XSpec occupies xs: and xsl: namespace prefixes

The issue is analogous to #466, but for the xs and xsl prefixes.
Reproduction steps:

Run xspec/test/xspec-prefix-conflict.xspec to test XSLT and XQuery. It passes.
Copy xmlns:x="x-urn:test:xspec-prefix-conflict" from line 4, paste it, and modify it to read xmlns:xs="x-urn:test:xspec-prefix-conflict".
On line 8, change x:param-mirror-function to xs:param-mirror-function.
Run the test again. It errors out.
Repeat steps 2-4 with the prefix xsl instead of xs. It errors out when testing XSLT.

Note: I don't know of a specific use case for using the "xsl" or "xs" prefix for namespaces other than "http://www.w3.org/1999/XSL/Transform" and "http://www.w3.org/2001/XMLSchema", respectively. I only noticed this issue while working on #598 .

I haven't tested it, but these prefixes might be the case too
https://github.com/xspec/xspec/blob/a5ab424e3b8629efb95b3761029bb0181ba12dd1/src/compiler/generate-xspec-tests.xsl#L48-L52

these prefixes might be the case too

You're probably right. While looking at #777, I found that in test/xspec-777.xspec, if I changed the parameter declaration to
<x:param as="document-node(element(test))" href="xspec-777.xml" name="impl:test" xmlns:impl="my-namespace"/>

then there was an error in the generated XSLT.

Looks like we'll eventually need to replace impl: and test: lexical QNames with EQName.

Sounds good (whenever someone has the spare time). Maybe I can work on this bug fix, but it wouldn't be that soon.

Fixed in #982

Reopening for xsl.

xsl fixed in #1099.


Incorrect Disclaimer

The disclaimer seems to be wrong, it says:
"Selfbots violate discord & PokeCord TOS and you can get banned. Be careful about how you use the bot."
When really it should say:
"Selfbots violate discord & PokeCord TOS and you WILL get banned. Be careful about how you use the bot."
I hope you fix this soon :)

Lol Miles himself opened an Issue? GG.

Fixed in https://github.com/Hyperclaw79/PokeBall-SelfBot/commit/df76fe57cebce14feb1e2987c8e366a6b1c7604c.

I assume that you not removing the "Be careful..." part implies that some of the features are within the scope of PokeCord ToS. Correct me if I am wrong.


[BUG] check_type() fails on typeguard v3

Describe the bug
Due to API change of typeguard, io_context.py fails at check_type() call since argname parameter is now dropped.
Steps/Code to reproduce bug
Run an example using typeguard>=3.0
Expected behavior
To not fail
Environment details (please complete the following information)

OS/Platform: Miniconda (Windows)
Python Version: 3.9
Method of MONAI Deploy App SDK install: pip
SDK Version: 0.5.0

Thank you @onurulgen for raising this issue.
This has been a known bug, and addressed in the main branchpull request, but before releasing the new App SDK package, a dev user would need to ensure the local typeguard~=2.12.1, and sets the pip package decorator in the application, e.g. env(pip_packages=["typeguard~=2.12.1"])

Addressed in release 0.5.1


New Feature: support for reads compressed in gzip and bzip2 format

This PR adds support for reads compressed in gzip and bzip2 format; compression formats are auto-detected and compressed reads are decompressed to a temporary file for subsequent processing by the ECTyper pipeline.
Galaxy tool definition XML file is also updated to support the broader ecosystem of Galaxy FASTQ types (no longer requiring space-expensive implicit conversion for many pipelines.)

Thank you for your contribution. On a quick glance, all looks good and the support for compressed files would really be useful for the raw reads inputs in FASTQ format.  Also thank you for fixing the galaxy wrapper files, I will use those changes and include them in the ToolShed release so that compressed files are also better supported by the Galaxy Project instance.
I will do more checks in my VMs and Galaxy instances and then report here and merge. This PR probably will be included as part of the next release (version 1.0.5)

Any word from the testing or a timeframe for release?

Hi, just checking in again, wondering how the testing is going

Hi, I was on vacation the past week. I am now doing testing and we should be done soon.  Do you need just source code merge or new conda and Galaxy release? I was just thinking of doing new feature merge and new release later. Let me know your plans and new feature release purpose. As alternative we can do 1.0.1 release.

I am getting gzip input file name error for the compressed reads that need to be fixed. The genome name regex needs to be fixed.
Command: ectyper -i SRR12852136_1.fastq.gz -o test --verify
In addition, I am thinking to add ability to combine both forward and reverse reads, but that feature could wait. Most use cases use assemblies anyway.
2022-07-20 22:42:07,510 ectyper      INFO     BLAST output file against reference alleles is written at test/blast_output_alleles.txt
Traceback (most recent call last):
  File "/usr/local/bin/ectyper", line 4, in <module>
    __import__('pkg_resources').run_script('ectyper==1.0.0', 'ectyper')
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 651, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1448, in run_script
    exec(code, namespace, namespace)
  File "/usr/local/lib/python3.9/dist-packages/ectyper-1.0.0-py3.9.egg/EGG-INFO/scripts/ectyper", line 13, in <module>
    ectyper.run_program()
  File "/usr/local/lib/python3.9/dist-packages/ectyper-1.0.0-py3.9.egg/ectyper/ectyper.py", line 161, in run_program
    final_predictions = predictionFunctions.add_non_predicted(
  File "/usr/local/lib/python3.9/dist-packages/ectyper-1.0.0-py3.9.egg/ectyper/predictionFunctions.py", line 581, in add_non_predicted
    'species': ecoli_dict[gname]["species"]
KeyError: 'SRR12852136_1.fastq'

Alright, never mind - trying to debug this has simply resulted in more bugs and the inability to complete any planemo tests, and I'm just not familiar enough with the codebase to figure out what's wrong. Plus I no longer need ECTyper to have native support for compressed reads anyway.

No worries, I will fix it shortly. It is a nice feature to have and would be bad to miss it.

This feature will be implemented in the version 2.0.0 of the tool and is now available at v2.0.0 branch at https://github.com/phac-nml/ecoli_serotyping/tree/v2.0.0. Now both gunzip compressed FASTA and FASTQ inputs are supported


refactor: eliminate StyleManager in favor of StyleNode

refactor: eliminate StyleManager in favor of StyleNode
rename it all

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#179
#178  👈 (View in Graphite)
#177
#176
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Garmire group (Cancer Center, Hawaii) works (SSrGE + Granatum + website of GarmireGroup)

Garmire group works (SSrGE + Granatum + website of GarmireGroup).
Cancer Center, University of Hawaii, Honolulu, USA.

Inferring SNVs from scRNA-seq reads and rank them according to their correlations with Gene expressions.
Developing a Web Portal to facilitate data processing for single-cell, with a particular emphasis for non-computational scientists

Thanks!


Noisy pointclouds

I notice the pointclouds from the driver are very noisy, see image below. There seem to be a large number of 'ghost points' between the actual object and the camera itself.
I don't notice this behaviour in the intel SDK, so I'm assuming it's not a hardware or firmware issue. It's also appearing on different realsense cameras, so it must be a driver issue. Filtering is not really an option, due to the large amount of points.
Is there a reason or explanation for this noise? Are there any workarounds or solutions?

I am sorry, but we were also experiencing noise with Intel depth cameras (RealSense and the next gen. DS4 tablet camera). It might be a problem with Linux drivers, but we've noticed a lot of noise on the grayscale image acquired directly from linux device, so I tend to think it is a hardware issue. Filtering 640x480 grayscale image may prove to be not so hard as it seems, and SDK might be doing this behind the scenes. A good solution to this problem would be to read the IR image from Windows without using the SDK. You can open the IR camera in Skype, for example, but it will not be properly encoded. To reencode the image you can launch our node under Windows and see where the noise is coming from. Good luck!


groupMembershipClaims is giving me over 100 groups, I'm in only 8...?

It says that I'm supposed to only be getting the groups that the signed in user is a member up. So how am I getting all the groups? And I don't mean all as in that's the value I put, I mean all the groups that I'm not a member of. How is that happening?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3f7ced07-0b71-715f-749b-180567591c72
Version Independent ID: 8c533d7b-a058-3f1a-c296-9c0305f85f13
Content: Understanding the Azure Active Directory app manifest
Content Source: articles/active-directory/develop/reference-app-manifest.md
Service: active-directory
GitHub Login: @CelesteDG
Microsoft Alias: celested

@DanJ210 Thank you for your query . We will investigate and update this thread.

@DanJ210 groupMemebrshipClaims incudes nested group memberships as well. Can you validate if the groups you are included are part of any other groups ?

@DanJ210 I am checking in to see if the above answer was helpful. Let me know if you have any other questions.

@ManojReddy-MSFT I'm guessing that's why. I don't have the ability to check groups within groups but getting over 100 seems like quite of a lot of nesting when I'm only in like 8 or 10 groups. Maybe I'm just not familiar with AD enough to know that's normal.
Perhaps the docs need a note just to alert that it's possible for a user to return 100s of nested groups. After getting so many groups back I can no longer access the site I was developing. Tells me BadRequest HTTP Error 400. The size of the request headers is too long. I've turned off the returning of groups so I'm no longer getting that large amount of info but I still get the error and I have to use a different browser. I have cleared cookies so I'm not sure why I'm still getting the error.
But yea it seems that getting so many results back is bad for a browser. Specifically Microsoft Edge.

@DanJ210 It is quite common in AD where a single group is part of more than 50+ groups. You can probably cange the setting to just ask for Security Groups instead of all groups.
Also to ensure that the token size doesn’t exceed HTTP header size limits, Azure AD limits the number of object Ids that it includes in the groups claim. If a user is member of more groups than the overage limit (150 for SAML tokens, 200 for JWT tokens), then Azure AD does not emit the groups claim in the token. Instead, it includes an overage claim in the token that indicates to the application to query the Graph API to retrieve the user’s group membership. You can learn more about this here. So ideally you should not get headers that are too big for browsers to handle. Can you try decoding yout token at https://jwt.ms and see if you are still getting the groups ?
@CelesteDG Can we include this information in this article as well ?

@DanJ210 I am working with the author to see if this information can be included in this article. I wanted to check in with you to see if you have any further questions.

@DanJ210 - Thank you for your question. @ManojReddy-MSFT I'm confirming with our feature team and will update the description as needed to address the question. Thank you.

@CelesteDG I'd be surprised if I'm in over 100+ sub groups from being within 8 AD groups. Right now I'm not using groups anymore. The solution for my issue was to use Application Roles using the Application Manifest. So groups were no longer needed luckily. But still strange that I get 100+ back.


Problems at 'Hello World' step npm issues, willing to work through!

Running npm install produces:
41 vulnerabilities (1 low, 6 moderate, 29 high, 5 critical)
Running npm audit fix produces:
8 vulnerabilities (1 low, 7 high)
Now am faced with a situation which will produce breaking changes!!
As a developer who is an npm and wasm novice this looks like a potentially big climb when I am not even sure the previous steps are correct.
I am willing and able to work through this or step back and start again but I think I need some help. Judging by other issues raised so do others!
$ npm ls
<EMAIL_ADDRESS>~/code/wasm-rust/rust-and-webassembly-book/wasm-game-of-life/www
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>$ npm ls -g
~/.nvm/versions/node/v20.11.1/lib
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

I had the same problem and @abdounasser202 's input addressed it

Think I'm giving up on using rust+wasm and will look for something else, as besides it being near a year of the setup being horribly outdated in this guide and having to even find this info to get anywhere, I can't even get it to go past this part. I've redone this multiple times, triple checked my work, it still keeps doing this even once I get past the dependency hell of this using depreciated and removed features:
anna@coblyn ~/awoken-fantasy/wasm-game-of-life/www $ npm run start

><EMAIL_ADDRESS>start
> webpack-dev-server

<i> [webpack-dev-server] Project is running at:
<i> [webpack-dev-server] Loopback: http://localhost:8080/
<i> [webpack-dev-server] On Your Network (IPv4): http://<IP_ADDRESS>:8080/
<i> [webpack-dev-server] Content not from webpack is served from '/home/anna/awoken-fantasy/wasm-game-of-life/www/public' directory
assets by path *.js 275 KiB
  asset bootstrap.js 268 KiB [emitted] (name: main)
  asset index_js.bootstrap.js 6.85 KiB [emitted]
asset b0dc0ef40f24c755ae73.module.wasm 1.51 KiB [emitted] [immutable]
asset index.html 297 bytes [emitted] [from: index.html] [copied]
runtime modules 31.6 KiB 15 modules
modules by path ./node_modules/ 175 KiB
  modules by path ./node_modules/webpack-dev-server/client/ 71.8 KiB 16 modules
  modules by path ./node_modules/webpack/hot/*.js 5.17 KiB 4 modules
  modules by path ./node_modules/html-entities/lib/*.js 78.9 KiB 4 modules
  ./node_modules/ansi-html-community/index.js 4.16 KiB [built] [code generated]
  ./node_modules/events/events.js 14.5 KiB [built] [code generated]
modules by path ../pkg/ 1.39 KiB (javascript) 1.29 KiB (webassembly)
  ../pkg/wasm_game_of_life.js 203 bytes [built] [code generated]
  ../pkg/wasm_game_of_life_bg.wasm 40 bytes (javascript) 1.29 KiB (webassembly) [built] [code generated] [1 error]
  ../pkg/wasm_game_of_life_bg.js 1.15 KiB [built] [code generated]
modules by path ./*.js 337 bytes
  ./bootstrap.js 279 bytes [built] [code generated]
  ./index.js 58 bytes [built] [code generated]

ERROR in ../pkg/wasm_game_of_life_bg.wasm
Module parse failed: Unknown element type in table: 0xNaN
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
Error: Unknown element type in table: 0xNaN
    at parseTableType (/home/anna/awoken-fantasy/wasm-game-of-life/www/node_modules/@webassemblyjs/wasm-parser/lib/decoder.js:1018:13)
    at parseTableSection (/home/anna/awoken-fantasy/wasm-game-of-life/www/node_modules/@webassemblyjs/wasm-parser/lib/decoder.js:1274:24)
    at parseSection (/home/anna/awoken-fantasy/wasm-game-of-life/www/node_modules/@webassemblyjs/wasm-parser/lib/decoder.js:1406:24)
    at Object.decode (/home/anna/awoken-fantasy/wasm-game-of-life/www/node_modules/@webassemblyjs/wasm-parser/lib/decoder.js:1740:25)
    at decode (/home/anna/awoken-fantasy/wasm-game-of-life/www/node_modules/@webassemblyjs/wasm-parser/lib/index.js:253:21)
    at WebAssemblyParser.parse (/home/anna/awoken-fantasy/wasm-game-of-life/www/node_modules/webpack/lib/wasm-async/AsyncWebAssemblyParser.js:61:19)
    at /home/anna/awoken-fantasy/wasm-game-of-life/www/node_modules/webpack/lib/NormalModule.js:1303:19
    at processResult (/home/anna/awoken-fantasy/wasm-game-of-life/www/node_modules/webpack/lib/NormalModule.js:937:11)
    at /home/anna/awoken-fantasy/wasm-game-of-life/www/node_modules/webpack/lib/NormalModule.js:1030:5
    at /home/anna/awoken-fantasy/wasm-game-of-life/www/node_modules/loader-runner/lib/LoaderRunner.js:407:3
 @ ../pkg/wasm_game_of_life.js 1:0-52 4:15-19 5:0-21
 @ ./index.js 1:0-42 3:0-10
 @ ./bootstrap.js 4:0-20

webpack 5.95.0 compiled with 1 error in 167 ms

These days using trunk results in a much better experience than npm.


Don't reset source and destination dropdowns if they are still valid

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Currently when configuring a connection, changing the selected module will always reset the source and destination endpoints, and changing the source endpoint will always reset the destination endpoint.
This pull request changes this behavior such that the selected source and destination endpoints are maintained whenever the new configuration is still valid.
Why should this Pull Request be merged?
Having the source and destination endpoints constantly reset was a major pain point when I recreated all of the test assets.
What testing has been done?
Hand testing of the UI.

@jashnani this pull request addresses a major usability issue I had when recreating all of the test assets. There is not a user story behind this, but the changes were trivial enough that I wanted to have a functional demo so that we could decide whether or not we wanted to change the existing behavior.


FEATURE: SD-2661 Upgrade sample data to a new version

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/108/ : SUCCESS in 23s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-oss-check/113/ : SUCCESS in 4s

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/109/ : SUCCESS in 12s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-oss-check/114/ : SUCCESS in 4s

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/110/ : SUCCESS in 13s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-merge-compliance-check/50/ : SUCCESS in 13s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-sonarqube-scan-zuul-gate/48/ : SUCCESS in 38s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-fossa-scanning-zuul/11/ : FAILURE in 10s (non-voting)


Prepare for FastBoot 1.0

ember-fastboot/ember-cli-fastboot#387
Fixes #76.

This looks great @josemarluedke, thanks for putting it together. Have you tested it?

Yes, I tested out by adding ember-cli-fastboot to the dummy app and booting it up. Works gray.

Super, you're the best.

Released in v1.3.0, made a minor jump because of the upgrade to bugsnag.js library. Thanks again.


Mobile App Creation Wizard - Add explanations of fields on mobile app creation wizard

Description
Add explanations of fields on mobile app creation wizard. E.g. a hover over question mark (?) to explain what is needed in the field.
Steps to reproduce

Navigate to your OpenShift service catalog
Select iOS App and click next
It would be useful to give an explanation on all fields during these wizards.

In the customer/user point of view, it is a bug because they cannot understand and know what should be imputed.

Hi @davidffrench,
Thanks for your feedback. This repo is now deprecated and is replaced by Mobile Developer Console. Could you please give it a try and if you still experience the same problem, please open a new issue in that project.
Thanks.


aspellDicts.is, aspellDicts.nb: fix build on darwin

Description of changes
ZHF #199919.
(Maybe also Homebrew/homebrew-core#28074?)
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

An earlier commit rebuilt all dictionaries on Linux. This was later fixed so that the label was removed.

Ah, thanks, I missed that detail :-)


iss12: Inter OperationSet Operations

Add functionality which allows inter operationSet operations.

Functionality added in new design of visualEEG.


Chocolatey package

With Windows support imminent (see #3), it would be great to see a Chocolatey package for Doxide. There are even packages available for MkDocs and Material for MkDocs already, which should make Doxide installation on Windows as simple as:
choco install doxide mkdocs mkdocs-material

Happy for anyone to have a look at this.

Windows support is now live, so no blockers for this ticket!

Commit 2d866a3 includes preliminary Chocolately packages in the choco subdirectory. Testing required.

The Chocolatey packages have now been submitted to community.chocolatey.org. Currently working their way through automated testing and moderation.

Done! Moderators have approved: https://community.chocolatey.org/packages/doxide


SerDe org.embulk.spi.unit.ByteSize with a Jackson Module

Several Embulk classes have had annotated with Jackson's annotations like @JsonCreator, @JsonProperty, and @JsonValue. To remove Jackson from embulk-core, those annotations need to be removed.
Instead of the annotations, the classes can still be serialized/deserialized by registering a Jackson Module to ObjectMapper with appropriate JsonSerializer and JsonDeserializer implemented. It works only for SerDe with ModelManager, though. (It won't work for arbitrary ObjectMapper, but we give it up. We haven't observed such a plugin so far.)
It is a replacement from annotations to a SerDe Module for org.embulk.spi.unit.ByteSize.

Thanks! Needs #1431 and #1432 to be merged before merging this.

Thanks!


Disable scrolling on a specific View Controller.

Is it possible , if i select one segment i can programatically disable scroll on that specific view controller. and when i switch segments . i can get the scrolling back. ?

You can use self.segmentedPager.pager.scrollEnabled = NO;
rf. #30

This will disable scrolling across all the 4 view controller i have. I want to disable scroll only on the last segment which shows the 4th view controller.

You can try implementing the delegate method like this :
- (void)segmentedPager:(MXSegmentedPager*)segmentedPager didSelectViewWithIndex:(NSInteger)index {
   segmentedPager.pager.scrollEnabled = (index != 4);
}

This is not working.


Do not display clone button in modal windows.

Well, this one-liner supresses the clone button in modal windows.  I fished around for some fancy way to accomplish this until I discovered the embedType property.  This will be good to know for future development

I will merge this one liner into development, I don't want to get to far ahead of development with adding new fields.


[🐛] This library does not require Manifest.permission.CAMERA, if you add this permission in manifest then you have to obtain the same

Hi,
I'm going to use the latest version of this library. and when i try to use it, it sent me this error:
"This library does not require Manifest.permission.CAMERA, if you add this permission in manifest then you have to obtain the same."
I need camera permission for another packages so i can not delete it, what am i suppose to do to solve this problem?
react native version: 0.61.5
image picker version: 3.1.3
thank you

You'd have to request the permission using something like react-native-permissions.

You'd have to request the permission using something like react-native-permissions.

You'd have to request the permission using something like react-native-permissions.

You'd have to request the permission using something like react-native-permissions.

I have this issue as well - we're getting the permissions just fine, but it's popping up an alert with that error message that I can't seem to turn off.

I have this issue as well - we're getting the permissions just fine, but it's popping up an alert with that error message that I can't seem to turn off.

I'm getting the same issue when calling launchImageLibrary even though I removed the CAMERA permission from AndroidManifest. Any idea what could cause this, and how to fix it?
I tried ./gradlew clean and reinstall the app in case there was some caching issue after I removed the permission, but no luck...

I'm getting the same issue when calling launchImageLibrary even though I removed the CAMERA permission from AndroidManifest. Any idea what could cause this, and how to fix it?
I tried ./gradlew clean and reinstall the app in case there was some caching issue after I removed the permission, but no luck...

Note: This library does not require Manifest.permission.CAMERA, if your app declares as using this permission in manifest then you have to obtain the permission before using launchCamera.
It worked for me.
import { PermissionsAndroid } from 'react-native';
const requestCameraPermission = async () => {
  try {
    const granted = await PermissionsAndroid.request(
      PermissionsAndroid.PERMISSIONS.CAMERA,
      {
        title: "App Camera Permission",
        message:"App needs access to your camera "
        buttonNeutral: "Ask Me Later",
        buttonNegative: "Cancel",
        buttonPositive: "OK"
      }
    );
    if (granted === PermissionsAndroid.RESULTS.GRANTED) {
      console.log("Camera permission given");
    } else {
      console.log("Camera permission denied");
    }
  } catch (err) {
    console.warn(err);
  }
};

Good job.

`import {launchCamera, launchImageLibrary} from 'react-native-image-picker';
const App = () => {
const requestCameraPermission = async () => {
try {
const granted = await PermissionsAndroid.request(
PermissionsAndroid.PERMISSIONS.CAMERA,
{
title: "App Camera Permission",
message:"App needs access to your camera ",
buttonNeutral: "Ask Me Later",
buttonNegative: "Cancel",
buttonPositive: "OK",
}
);
if (granted === PermissionsAndroid.RESULTS.GRANTED) {
console.log("Camera permission given");
openCamera();
} else {
console.log("Camera permission denied");
}
} catch (err) {
console.warn(err);
}
};
const openCamera = () => {
//Alert.alert('asdasd');
const options = {
storageOptions: {
path: 'images',
mediaType: 'photo',
},
includeBase64: true,
};
launchCamera(options, response => {
  console.log('Response =', response);
});

};
return (

hello
<Button title={'Open camera'} onPress={() => requestCameraPermission()} />

);
};
export default App;`


[FEATURE] Convert audit logs to Elastic Common Schema

Is your feature request related to a problem?
The Security Analytics module is being built. This depends on Elastic Common Schema, the current audit logging however does not. I can imagine that it would help to implement detection on the audit logs and in general it's always good to use 1 standard.
What solution would you like?
Map the audit logs to ECS
What alternatives have you considered?
Doing it myself during ingest time through logstash
Do you have any additional context?

[Triage] @ict-one-nl This looks like its not related to the audit logs that the security plugin writes, but associated with the new plugin security-analytics, transfering it.  Please let me know if this was done incorrectly - thanks.


have bigger font & less text

right now, text isn't legible due to the fact that the ink spreads, adapt the svgs for this

Must adapt outline font to a single line font


Show error if JSON is invalid

Via https://github.com/sveltejs/svelte/issues/938 — if a gist contains invalid JSON, the REPL doesn't appear to mind: https://svelte.technology/repl?version=1.42.0&gist=2afe785004bcdc4c1bcca6f03f2ed7f9
It should show an error instead.

The error is shown as I see now, but it's subtle and hard to decipher.
Generally there are 2 or 3 different places where errors are shown, and sometimes it's top of the panel, sometimes as in this case it's at the bottom.

I can send a PR that would use https://github.com/json5/json5 instead of vanilla JSON.parse for parsing the json field into data. That will effectively allow writing in the data panel in the same way one would do in normal JS code.

I agree that this would be better. One thing that concerned me a bit about using JSON5 is that it would be somewhat jarring when the component updates the data, because it would have to stringify the current state in a way that is unlikely to match the user's formatting.
So I whipped up a little module that makes it possible to update the string in place: https://github.com/Rich-Harris/golden-fleece
The idea is that you take a JSON5 string, throw a new object at it, and it will 'patch' the string to add the new values non-destructively. (It isn't at all battle-tested yet!)
A PR would be awesome if you have time! Thank you 😀

Heh, nice module. Will try to find time early this (coming) week.
Though IMO having a prettier-like experience with reformat-on-blur would be OK too.

this is now implemented


ft:Remove skip condition if E2E test

Also updates names of location constraints so they match Integration.

PR has been updated. Reviewers, please be cautious.

CONFLICT (add/add): Merge conflict in tests/unit/testConfigs/configTest.js
CONFLICT (add/add): Merge conflict in tests/locationConfigTests.json
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/utils.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/put/put.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/objectPutCopyPart/objectPutCopyPartAzure.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/objectCopy/objectCopy.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/mpuComplete/mpuAwsVersioning.js
CONFLICT (add/add): Merge conflict in package.json
CONFLICT (add/add): Merge conflict in lib/data/wrapper.js
CONFLICT (add/add): Merge conflict in lib/data/multipleBackendGateway.js
CONFLICT (add/add): Merge conflict in lib/data/external/utils.js
CONFLICT (add/add): Merge conflict in lib/data/external/AzureClient.js
CONFLICT (add/add): Merge conflict in lib/data/external/AwsClient.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutCopyPart.js
CONFLICT (add/add): Merge conflict in lib/api/objectCopy.js
CONFLICT (add/add): Merge conflict in lib/Config.js


Merge dev into main for 2023-12-11

Bump docker/metadata-action from 4.4.0 to 5.3.0
Bump actions/setup-python from 4 to 5
Bump google-github-actions/setup-gcloud from 1 to 2
Bump tibdex/github-app-token from 1 to 2
Update conda-lock.yml and rendered conda environment files.
Replace ferc714 @multi_asset with asset factory  (#3123) for better subsetting functionality.
Update conda-lock.yml and rendered conda environment files.
[pre-commit.ci] pre-commit autoupdate
[pre-commit.ci] auto fixes from pre-commit.com hooks
Update .pre-commit-config.yaml

Somehow I messed this up and it's coming from the CEMS branch, not dev, so this PR should not go through.


Question about Zero-Copy Deserialization lifetime error

Why am I getting this lifetime error?

Thanks!

Check out https://serde.rs/lifetimes.html and https://serde.rs/borrow.html.

Thanks, I got it working for structs with #[serde(borrow)] but how can I make it work for enums?
#[derive(Debug, Clone, PartialEq, Serialize, Deserialize)]
pub enum Msg<'a> {
	#[serde(borrow)]
	System(SystemTransaction<'a>),
	#[serde(borrow)]
	Item(ItemTransaction<'a>),
}

error: proc-macro derive panicked
help: message: 2 errors:
	# unknown serde variant attribute `borrow`
	# unknown serde variant attribute `borrow`

@Boscop this is a field attribute, not a variant one:
#[derive(Debug, Clone, PartialEq, Serialize, Deserialize)]
pub enum Msg<'a> {
	System(#[serde(borrow)] SystemTransaction<'a>),
	Item(#[serde(borrow)] ItemTransaction<'a>),
}

#929 tracks making it work for newtype variants. I would love a PR if anyone has time to implement it.


what 's the meaning of tracking_points?

For a tracker.byte_tracker_3dcenter, I can see the tracking code is
           tracking_points = np.concatenate([(cams[:,[2,1]]+1)*image_scale, cam_trans[:,[2]]*depth_scale, cams[:,[0]]*image_scale/2],1)             tracked_ids, results_inds = self.tracker.update(tracking_points, det_confs)
the tracking_points is 4 float number.
I want to konw the meaning of the 4 float numbers. Are the the coordernates of a bbox?

Hi,
The tracking points consist of four things:
1.The normalized x coordinate of body center (close to pelvis) on image plane;
2. The normalized y coordinate of body center (close to pelvis) on image plane;
3. The depth z of body center (close to pelvis) in our predefined camera space;
4. The scale s of a human on image plane.
Yes, we use the 3D body center for tracking.

2023年2月16日 11:05，anzisheng @.***> 写道：
For a tracker.byte_tracker_3dcenter, I can see the tracking code is
tracking_points = np.concatenate([(cams[:,[2,1]]+1)*image_scale, cam_trans[:,[2]]*depth_scale, cams[:,[0]]*image_scale/2],1) tracked_ids, results_inds = self.tracker.update(tracking_points, det_confs)
the tracking_points is 4 float number.
I want to konw the meaning of the 4 float numbers. Are the the coordernates of a bbox?
—
Reply to this email directly, view it on GitHub https://github.com/Arthur151/ROMP/issues/418, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEISGDHH74ZTS7FA6EC5343WXWKRFANCNFSM6AAAAAAU5TSPMI.
You are receiving this because you are subscribed to this thread.

Hi, thanks for your reply.
As you mentioned "use the 3D body center for tracking", I want to know how to track 3d body center which I get from multi camera?