Objects added to Slots can't be manipulated as it was in previous version.

Hi guys,
Currently when attaching a container to a a slot I can't change some of container properties like scale and position, it looks like something is reseting the properties in the container, some properties like alpha for example works. It is something very useful that could be done on previous version.
It can easily be reproduced in the test project https://pixijs.io/spine-v8/examples/slot-objects.html you just need to include this line of code.
spineboy.addSlotObject("gun", logo1);
const gun = spineboy.getSlotObject("gun");
gun.scale.set(0.5);
Maybe is related to https://github.com/pixijs/spine-v8/issues/23 ?

Ok I found the part of code where you actually apply the bones properties to the container. I manage to achieve what I want by wrapping my object in to a separated container and attaching that container to the slot then I can manipulate the child object as desired.

Yup, exactly. It's designed like that. This is from the documentation:

It is possible to assign only one Pixi object per slot. Once the Pixi object has been added, its transform will be automatically modified by the Spine object.
To have more control over the added objects, you can add a Pixi Container where you are free to add as many Pixi objects as you want, offset their position, angle, scale, and so on.


Implement support for line number information

Section 6.2 of the DWARF 4 standard.

Taking a crack at this.

Follow along in #27.


[libresources] Add new port

Can someone explain to me what I need to do to resolve the issues. Is it from my side or not?

This port build failed on windows, you can download the failure log from: https://dev.azure.com/vcpkg/public/_build/results?buildId=85131&view=artifacts&pathAsName=false&type=publishedArtifacts.

This port build failed on windows, you can download the failure log from: https://dev.azure.com/vcpkg/public/_build/results?buildId=85131&view=artifacts&pathAsName=false&type=publishedArtifacts.

Weird although I do the check for 32/64 bits on 32 bits build the log shows:
[1/2] "D:/downloads/tools/cmake-3.25.1-windows/cmake-3.25.1-windows-i386/bin/cmake.exe" -E chdir "../../x86-windows-dbg" "D:/downloads/tools/cmake-3.25.1-windows/cmake-3.25.1-windows-i386/bin/cmake.exe" "D:/buildtrees/libresources/src/f1db3b80b7-f2c6d5164c.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=D:/packages/libresources_x86-windows/debug" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Enterprise/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=OFF" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/a/1/s/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x86-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/a/1/s/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x86" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/a/1/s" "-D_VCPKG_INSTALLED_DIR=D:/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
-- The C compiler identification is MSVC 19.34.31937.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.34.31933/bin/Hostx64/x86/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
bin2coff_EXECUTABLE = D:/buildtrees/libresources/x86-windows-dbg/Utilities/bin2coff/bin2coff.exe
ARCHITECTURE : x64
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

    CMAKE_INSTALL_BINDIR
    FETCHCONTENT_FULLY_DISCONNECTED

You can see here : https://github.com/as-shura/libresources/blob/master/additional_execution.cmake

Merge please

It cannot be merged. You have to remove the unrelated mupdf changes.
And maybe the name is too generic,
Just wait for proper review.

About libmupdf/CMakeLists.txt, please refer to PR #29635.

We didn't want the mupdf files to be removed but the mupdf changes.

I don't understandI think I will close this PR.

Closing this PR since it seems that no progress is being made. Please ping us to reopen if work is still being done.


invalid character '}' after top-level value

[x] This is a bug report

Expected behavior
$ terraform plan -out plan
# normal terraform output

Actual behavior
$ terraform plan -out plan
invalid character '}' after top-level value

Steps to reproduce the behavior
I have clue what causes this to happen, but it appears that CACHE/state.json sometimes gets an additional } appended. I usually fix it by doing:
rm -rf ~/Library/Caches/tfvm/v1/

Everything works correctly for an indeterminate amount of time after that.
I’m using tfvm symlinked as terraform. There are two things to note:

I usually have multiple tabs open in my terminal and may be running multiple terraform commands in separate environment directories.
I am using fish with IlanCosman/tide, which is an asynchronous smart prompt that will run terraform --version to include terraform version information in the prompt.

My theory is that multiple versions of tfvm are running and writing to the state file at the same time, resulting in munged output.
Output of tfvm info:
Tfvm version is v0.22.0.
Built from commitish a9eae97, on 2021-09-27 17:40:08+02:00 for darwin/arm64.
OS is darwin, arch is arm64.
Cache dir is /Users/austin/Library/Caches/tfvm.

It happened again just a few minutes after it happened this time.
``console
$ tfvm info
invalid character '}' after top-level value

**Output of `TF_LOG=trace tfvm <your command>`:**

```console
TF_LOG=trace tfvm info
invalid character '}' after top-level value

A subset of my state file:
{
 "lastUpdateTime": "2022-11-03T11:12:32.69432-04:00",
 "terraformReleases": [
    {
     "os": "windows",
     "arch": "386",
     "download_path": "/terraform/0.11.5/terraform_0.11.5_windows_386.zip",
     "sha256_checksum": "47f6b634c78c27ae0f765817cc80a4411f91bdf7f4e593f8d83abcb58290a710"
    },
    {
     "os": "windows",
     "arch": "amd64",
     "download_path": "/terraform/0.11.5/terraform_0.11.5_windows_amd64.zip",
     "sha256_checksum": "c16be99bae3b252875ff58749adc7d4d32e25d2fe3d858d0090018f3b82d7aa"
    }
   ]
  }
 ]
}}

Removing the final } fixes everything…for now.
I might suggest that if JSON parsing fails on state.json, rather than panicing, starting from a clean version might be the best choice.

Hey Austin, thanks for reporting this. Yes, when I think about it, it totally makes sense. I will deal with it when I have made it through my second covid infection (no worries, it's all o.k.). A solution could be switching to atomic writes (via natefinch/atomic for example) so no file corruptions can occur. See you soon, Conni

Hey @halostatue I have just released v0.24.0, which should fix the issue.
The state is written to a temp file and subsequently move in an atomic way. So when tfvm is run concurrently either the first or the second should "win" in a consistent way.
Looking forward to hear your feedback.
Conni

I’m on vacation right now, so it will be a couple of weeks before there’s a chance of this showing up again.

@halostatue No hurry, enjoy your vacation!

Apologies. I thought that I had upgraded tfvm, but I had not and I was coming to tell you that the problem still existed (I had seen it last week). I expect to be doing a bit more Terraform work in the new year, so I should have this tested properly by about January 15.

Hey Austin, thank you for coming back. Hope you have enyojed your vacation.
No need to hurry. Best Conni
On Tue, 27 Dec 2022, 06:41 Austin Ziegler, @.***> wrote:

Apologies. I thought that I had upgraded tfvm, but I had not and I was
coming to tell you that the problem still existed (I had seen it last
week). I expect to be doing a bit more Terraform work in the new year, so I
should have this tested properly by about January 15.
—
Reply to this email directly, view it on GitHub
https://github.com/cbuschka/tfvm/issues/38#issuecomment-1365627560, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJVT4POHOVNAPYJGJ6FZ5DWPJ6QBANCNFSM6AAAAAARWHQ57U
.
You are receiving this because you were assigned.Message ID:
@.***>

This appears to be fixed.

Hey @halostatue thanks for the verification. Looking forward to hear from you :) Best Conni


Cambiados errores en inglés y añadidos comentarios sobre la clase StaticContentUnitTest

@catalindumitrache76 you have to create the pull request from your fork's master to this repo's master

I have reopened the pull request and close it again in order to add background to the previous decision.  Note that your pull request is into the bugfix/disable-sonarqube branch rather than in the master branch. Next time, you must perform the pull request against UNIZAR-30246-WebEngineering/lab1-git-race master branch.


Update references to rc3 roslyn bits

@vasily-kirichenko  @CyrusNajmabadi  @cartermp
This PR contains the latest roslyn bits.  It seems as if between RC2 and RC3 there was a breaking change ...
https://github.com/Microsoft/visualfsharp/blob/master/vsintegration/src/FSharp.Editor/Navigation/FindReferencesService.fs#L144
IStreamingFindReferencesService was removed here: https://github.com/dotnet/roslyn/commit/1db055b7776c3c80b93f5fa00f371beee131a3fe
and replaced with IFindUsagesService.
I guess to re-enable FindAllReferences with the latest bits we need to make some changes, @vasily-kirichenko would you take this PR and make the necessary changes to the editor please?
Thanks
Kevin

Does this also fix the inline rename error (#2328)

@saul It should, although we'd have to uncomment out the attribute which exposes the service to the Roslyn Workspace.  That's the next step after getting Roslyn references updated properly.

@brettfo has already don this vs2017_rtm --- so he will now merge it into master.


Constant should be capitalized, throwing error

This throws an error in Python 3.11.8
[Scrape / SHA256 Lookup] NameError: name 'false' is not defined. Did you mean: 'False'?
[Scrape / SHA256 Lookup]                    ^^^^^
[Scrape / SHA256 Lookup]     disable_nfkd = false
[Scrape / SHA256 Lookup]   File "/root/.stash/scrapers/fansdb/SHALookup/config.py", line 9, in <module>

Oops, Thanks!


AMPA Install Issue

Hi There,
I am trying to install Oracle A-Team Mobile Persistence Accelerator (Build <IP_ADDRESS>.68) and getting following error.
"Unable to load the application file.Workspace MobilePersistenceAccelerator.jws already migrated to newer version (<IP_ADDRESS>.0)."
Jdeveloper Version 12.1.3
MAF extension: 2.2.2
Mac OS Yosemite 10.10.5
Any help is welcome.
thanks

This AMPA release can only be used with MAF 2.3 and JDeveloper 12.2.1, see the release notes:
https://github.com/oracle/mobile-persistence/wiki/Release-Notes-<IP_ADDRESS> https://github.com/oracle/mobile-persistence/wiki/Release-Notes-<IP_ADDRESS>
Kind regards,
Steven Davelaar.

On 12 Apr 2016, at 16:41, nikunjoracle<EMAIL_ADDRESS>wrote:
Hi There,
I am trying to install Oracle A-Team Mobile Persistence Accelerator (Build <IP_ADDRESS>.68) and getting following error.
"Unable to load the application file.Workspace MobilePersistenceAccelerator.jws already migrated to newer version (<IP_ADDRESS>.0)."
Jdeveloper Version 12.1.3
MAF extension: 2.2.2
Mac OS Yosemite 10.10.5
Any help is welcome.
thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub https://github.com/oracle/mobile-persistence/issues/7

Thanks Steven for quick response.
Is there a way i can get older version of Oracle A-Team Mobile Persistence Accelerator to work with my existing Jdeveloper (12.1.3) and MAF (2.2.2) version?
Or
Do you recommend upgrading to MAF 2.3 and Jdeveloper 12.2.1?
thanks
Nikunj

Nikunj,
Using the drop down list on GitHub home page, you can select another build than master. You can pick build tagged with 12.1.3.x.x.x, However, the developers guide is written for latest <IP_ADDRESS>.68 production build, and MAF 2.3 has fixes for some UI freeze issue that happened when refreshing the UI through background thread.
So, I would recommend to upgrade to JDev 12.2.1 / MAF 2.3. The only annoying thing is that deployment of MAF 2.3 apps fails pretty randomly (not related to AMAP). Solution is to remove the deploy dir and try again. I have logged bugs for this and MAF dev team is currently working on this.
Steven.

On 12 Apr 2016, at 17:03, nikunjoracle<EMAIL_ADDRESS>wrote:
Thanks Steven for quick response.
Is there a way i can get older version of Oracle A-Team Mobile Persistence Accelerator to work with my existing Jdeveloper (12.1.3) and MAF (2.2.2) version?
Or
Do you recommend upgrading to MAF 2.3 and Jdeveloper 12.2.1?
thanks
Nikunj
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub https://github.com/oracle/mobile-persistence/issues/7#issuecomment-208950494

thanks Steven for feedback.
Quick question: As you mentioned MAF 2.3 has some issue currently (not related to AMPA). So I don't think its Production ready as we going to deploy our App in Production in early July. (You provided solution...i haven't played around with MAF 2.3 version)
Any comments?
thanks
Nikunj

Nikunj,
MAF 2.3 is a production release, so it is production ready, and I am using it for a couple of weeks without any issues except for the intermittent deployment failures.
I hope the MAF team will bring out a patch pretty soon to fix the deployment issues.
Steven.

On 12 Apr 2016, at 17:19, nikunjoracle<EMAIL_ADDRESS>wrote:
thanks Steven for feedback.
Quick question: As you mentioned MAF 2.3 has some issue currently (not related to AMPA). So I don't think its Production ready as we going to deploy our App in Production in early July. (You provided solution...i haven't played around with MAF 2.3 version)
Any comments?
thanks
Nikunj
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub https://github.com/oracle/mobile-persistence/issues/7#issuecomment-208958526

Thanks Steven,
I will upgrade to MAF 2.3 in test environment and play around it along with latest AMPA release.
thanks
Nikunj


brew audit command failing with Unable to resolve dependency: user requested 'did_you_mean (= 1.0.0)'

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[x] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

To help us debug your issue please explain:

What you were trying to do (and why)
What happened (include command output)
What you expected to happen
Step-by-step reproduction instructions (by running brew commands)

I wanted to update the selenium-server-standalone formula, and was curious about the use of versions in the formula file. I typed brew audit selenium-server-standalone and got the following output:
➜  ~ brew audit --verbose --debug selenium-server-standalone
==> Installing or updating 'rubocop' gem
Error: Unable to resolve dependency: user requested 'did_you_mean (= 1.0.0)'

I ran it again with debug:
➜  ~ brew audit --debug selenium-server-standalone
/usr/local/Homebrew/Library/Homebrew/brew.rb (Formulary::FormulaLoader): loading /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/selenium-server-standalone.rb
==> Installing or updating 'rubocop' gem
Error: Unable to resolve dependency: user requested 'did_you_mean (= 1.0.0)'
/Library/Ruby/Site/2.3.0/rubygems/resolver.rb:231:in `search_for'
/Library/Ruby/Site/2.3.0/rubygems/resolver.rb:283:in `block in sort_dependencies'
/Library/Ruby/Site/2.3.0/rubygems/resolver.rb:277:in `each'
/Library/Ruby/Site/2.3.0/rubygems/resolver.rb:277:in `sort_by'
/Library/Ruby/Site/2.3.0/rubygems/resolver.rb:277:in `with_index'
/Library/Ruby/Site/2.3.0/rubygems/resolver.rb:277:in `sort_dependencies'
/Library/Ruby/Site/2.3.0/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:52:in `block in sort_dependencies'
/Library/Ruby/Site/2.3.0/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:69:in `with_no_such_dependency_error_handling'
/Library/Ruby/Site/2.3.0/rubygems/resolver/molinillo/lib/molinillo/delegates/specification_provider.rb:51:in `sort_dependencies'
/Library/Ruby/Site/2.3.0/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:165:in `initial_state'
/Library/Ruby/Site/2.3.0/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:106:in `start_resolution'
/Library/Ruby/Site/2.3.0/rubygems/resolver/molinillo/lib/molinillo/resolution.rb:64:in `resolve'
/Library/Ruby/Site/2.3.0/rubygems/resolver/molinillo/lib/molinillo/resolver.rb:42:in `resolve'
/Library/Ruby/Site/2.3.0/rubygems/resolver.rb:188:in `resolve'
/Library/Ruby/Site/2.3.0/rubygems/request_set.rb:385:in `resolve'
/Library/Ruby/Site/2.3.0/rubygems/request_set.rb:397:in `resolve_current'
/Library/Ruby/Site/2.3.0/rubygems.rb:243:in `finish_resolve'
/Library/Ruby/Site/2.3.0/rubygems/rdoc.rb:15:in `<top (required)>'
/Library/Ruby/Site/2.3.0/rubygems/core_ext/kernel_require.rb:59:in `require'
/Library/Ruby/Site/2.3.0/rubygems/core_ext/kernel_require.rb:59:in `require'
/Library/Ruby/Site/2.3.0/rubygems/commands/install_command.rb:280:in `load_hooks'
/Library/Ruby/Site/2.3.0/rubygems/commands/install_command.rb:156:in `execute'
/usr/local/Homebrew/Library/Homebrew/utils.rb:234:in `install_gem!'
/usr/local/Homebrew/Library/Homebrew/utils.rb:242:in `install_gem_setup_path!'
/usr/local/Homebrew/Library/Homebrew/style.rb:20:in `check_style_impl'
/usr/local/Homebrew/Library/Homebrew/style.rb:14:in `check_style_json'
/usr/local/Homebrew/Library/Homebrew/dev-cmd/audit.rb:149:in `audit'
/usr/local/Homebrew/Library/Homebrew/brew.rb:89:in `<main>'

I would expect the rubocop update to complete successfully, but instead it seems to have an issue with satisfying its dependencies.
Here is my system's brew diagnostics as requested:
➜  ~ brew doctor
Your system is ready to brew.
➜  ~ brew config
HOMEBREW_VERSION: 1.8.1-6-g5556aba
ORIGIN: https://github.com/Homebrew/brew
HEAD: 5556aba0ce3e7e2027cbf97742b83bf51c38445a
Last commit: 18 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 3e44f3013698ca5923b3416fdf960c5f40509a37
Core tap last commit: 2 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DEV_CMD_RUN: 1
CPU: quad-core 64-bit kabylake
Homebrew Ruby: 2.3.7 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 10.0 build 1000
Git: 2.19.1 => /usr/local/bin/git
Curl: 7.54.0 => /usr/bin/curl
Java: 11, 10.0.2, 9.0.4, 1.8.0_162
macOS: 10.13.6-x86_64
CLT: <IP_ADDRESS>.1.1539992718
Xcode: 10.0 => /Applications/Xcode-10.app/Contents/Developer
XQuartz: 2.7.11 => /opt/X11

Should be fixed by https://github.com/Homebrew/brew/pull/5234, please confirm if not.


officially support redis using requirements

This PR adds official support for redis, see https://trello.com/c/GIJQA0kg/177-redis-out-of-experimental

Code PR merged, listing for review tomorrow

Makes sense. Good to know that we can add memory & database if need be. (Whitespace fixed) Leaving @hflynn the fun of wrangling travis.


Rating

### Tasks
- [ ] #2431
- [ ] #2432
- [ ] #2433
- [ ] #2434
- [ ] #2435

Searched SourceGraph, excluding UITK repo, 43 usage <Rating. Should be low priority


[BUG] Creeper Overhaul Creepers are not scared of Feline Origin

Describe the bug
Mobs from the Creeper overhaul mod do not avoid the Feline origin, besides the retextured minecraft:creeper
To Reproduce
Steps to reproduce the behavior (add and remove steps as needed, describe clearly):

Load into a world.
Select the Feline origin.
Summon or encounter a mob from the Creeper Overhaul mod.

Expected behavior
Modded Creeper should avoid you when you come near it, but it becomes aggressive or acts as normal otherwise.
Screenshots
N/A.
Modpack Version:
1.19.2 1.0.0 Beta
Additional context
N/A

 Make modded creepers scared of felines.

This can't be fixed as origins:scare_creepers isn't data-driven, and would require a different mod altogether.


Post processor @Bean should be marked static

Thanks for creating this project. Quick observation.
Starting an application gives me this warning:
WARN org.springframework.context.annotation.ConfigurationClassEnhancer -
  @Bean method EnableEncryptablePropertySourcesConfiguration
    .enableEncryptablePropertySourcesPostProcessor is non-static and returns
    an object assignable to Spring's BeanFactoryPostProcessor interface. This
    will result in a failure to process annotations such as @Autowired,
    @Resource and @PostConstruct within the method's declaring
    @Configuration class. Add the 'static' modifier to this method to avoid these
    container lifecycle issues; see @Bean javadoc for complete details

See @Bean Javadoc, section titled BeanFactoryPostProcessor-returning @Bean methods

https://github.com/ulisesbocchio/jasypt-spring-boot/blob/master/jasypt-spring-boot/src/main/java/com/ulisesbocchio/jasyptspringboot/configuration/EnableEncryptablePropertySourcesConfiguration.java#L66
I see that the post processor uses the (non-static) environment variable.
I suppose since there are no other annotated methods in the class to worry about, it should be fine. Would be nice to avoid that warning though. If not, maybe a comment in the class explaining this pitfall?

Yeah, I'm aware of this. It's a Spring Lifecycle issue that doesn't affect the lifecycle of the beans of this project. You can shut off the warning by adding this to your logback.xml:
<logger name="org.springframework.context.annotation.ConfigurationClassEnhancer" level="ERROR"/>

I'm looking into a different way to bootstrap Jasypt intro Spring Boot that will eventually avoid this issue.

This is fix as of version 1.6, enjoy

Thanks!


Tooltip is too big to fit -_-

Issue description:
I love tooltips just as much as the next guy. But, this one is a little too large for me!
What happens:
https://sx.artdude.uk/hotlink-ok/darkosto/Cf6n-96b10-1481134960.png
What you expected to happen:
Not to have a mile long tool tip
Steps to reproduce:

Mouse over Solderer
???
Profit
...

Version (Make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge: 2185
Refined Storage: 1.2.9

Does this issue occur on a server? [yes/no]
probably!
If a (crash)log is relevant for this issue, link it here:
[pastebin/gist/etc link here]

But don't you just love tooltips that cover your whole screen?

The only reason that tooltip is there because I was getting so much "issue" reports about it (aka users just not understanding that you need a Controller first). But it can use some extra lines yes :P


Extract MurmurHash functions into their own source files.

The implementation were copied from
https://code.google.com/p/smhasher/source/browse/trunk/MurmurHash2.*

There's no real need for this at this point.


gnostic-go-generator: -output doesn't like non package names

I know the docs say that -out is also the package name, but the error message is confusing. when I do something like -output=/tmp/bookstore I get
Plugin error: [constants.go:3:9: expected 'IDENT', found '/']

I think it would be nice to have a friendlier error.
I've traced this to goimports errors. related to #110
https://github.com/googleapis/gnostic/blob/d55a06a32dc7468c645ac01d93d37d4dd47ca062/plugins/gnostic-go-generator/renderer.go#L63
I made some changes like
diff --git a/plugins/gnostic-go-generator/renderer.go b/plugins/gnostic-go-generator/renderer.go
index 93fd47d..31efb8e 100644
--- a/plugins/gnostic-go-generator/renderer.go
+++ b/plugins/gnostic-go-generator/renderer.go
@@ -60,7 +60,9 @@ func (renderer *Renderer) Render(response *plugins.Response, files []string) (er
                }
                // run generated Go files through imports pkg
                if filepath.Ext(file.Name) == ".go" {
-                       file.Data, err = imports.Process(file.Name, file.Data, nil)
+                       if file.Data, err = imports.Process(file.Name, file.Data, nil); err != nil {
+                               response.Errors = append(response.Errors, fmt.Sprintf("ERROR %v", err))
+                       }
                }
                response.Files = append(response.Files, file)
        }

The last error gets reported twice though due to named returns, and I was thinking it would be really nice to still write out the files so that the user can inspect the problem in context.
thoughts?

The code I put above is really for better error messaging.
I'm working on a PR for cleaning the package name.

Closed by #112


Fix: Queue 'stats_publish_rate' is not an integer.

I am getting errors when trying to update the queue after creation.
I think the issue is obvious since we get 0.6 or just 0.0 as a value of publish_rate meanwhile Terraform expects an Int64.
│ Error: Error updating Resource
│
│   with ably_queue.kafka-connect-ably-example,
│   on ably.tf line 35, in resource "ably_queue" "kafka-connect-ably-example":
│   35: resource "ably_queue" "kafka-connect-ably-example" {
│
│ Could not update resource, unexpected error: json: cannot unmarshal number 0.6 into Go struct field Stats.stats.publishRate of type int

Thanks for the report. I'll check if any other stats may be floats too.


Playwright + Native Node Test Runner

The current test setup is broken in 2.0.0, need to rework
Backend test

Drop jest
Fully switch to Node.js test runner

e2e test

Drop cypress
Switch to playwright (Because the codegen feature looks promising)

Any plan of dropping Nodejs 14 and 16?

Will re-implement those dropped old test cases (jest & cypress) in a new pull request for easier code review.

@louislam just that we are clear:
If you would like testcases in some area to improve via contributions (=> not just you), that is something that we (other contributors) can help with if you tell people where you would like a testcase.


Kaggle Connector Update

Connector now checks for up to 20 MB csv files.
Error messages

For wrong file path
For non-csv files
For having greater than 20mb files
For failed connection/failed parsing

Uses new User/Token authentication

Backwards compatible so it won't break or trigger authflow for existing connector users.

Auth help button/url (shows a Help button during authentication linking to the API token help page)
Updated logo
Misc transparent refactoring and code updates (script)

Updated.


Branch dg edits

Codecov Report

Merging #194 (c7bf255) into master (6f1049c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #194   +/-   ##
=========================================
  Coverage     74.52%   74.52%
  Complexity      695      695
=========================================
  Files           110      110
  Lines          2073     2073
  Branches        239      239
=========================================
  Hits           1545     1545
  Misses          463      463
  Partials         65       65

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6f1049c...c7bf255. Read the comment docs.


adds a LICENSE file for all direct and indirect dependencies, include…

…s with docker images
Signed-off-by: Sean Winn<EMAIL_ADDRESS>Adds a LICENSE.all file listing all direct and indirect dependencies, adds it to docker images for compliance

How is LICENSE.all generated? Is it possible to automate some or all of this?

@twpayne  the file is generated by the makefile target licenses-all which I completely forgot to include in the original PR, thanks


java.lang.NoClassDefFoundError: net/minecraftforge/fml/relauncher/IFMLLoadingPlugin

Minecraft throws the above error when I run InventoryTweaks and Forge <IP_ADDRESS>5-1.7.10. The error is not thrown when only Forge is installed. I get this same error with Aroma1337Core, but not with all mods. Here is my full log.

Check versions more carefully.


Implement simple forum using simple_discussion gem

Implement simple discussion gem

Coverage decreased (-0.04%) to 85.845% when pulling d69fca8078be2212e2ef65ce5419d56d39ed1f33 on stories/implement_simple_forum into 97900cb11340df4e3243c7394043c84d4290fb50 on master.

What will be the entry point for this discussion forum?

What should be the entry point for this discussion forum? Navbar Link?

It's in the footer currently.

No, I meant footer isn't really the right entry point, so where should we add the link. considering navbar already has way too many options.

What exactly is the issue with having forum link in the footer ?

The forum should be considered a primary feature and thus should have a prominent entry point. Footer nav is for when your users reach the end, and instantly accessible navigation tool waiting to help them move freely around the website. In short, more of secondary navigation.
What we can do is put the forum link in the simulator navbar so that's it's highly visible to people using the simulator.


revamp docs site for console launch

I'm having a hard time with the active link style in the left navigation pane. I guess it looks too much like the section headers. I was trying to click right down the line in the "Deployment" section while reviewing, but I kept clicking in the wrong place. Can we try the active link as a different color than the section headers? Maybe the same color as the other links, but bolded?

These docs are becoming extensive enough that we should think about adding search.

Link color has been addressed. Search will come at some point.


Unmanaged crash when incoming video data has no pixel format

I'm writing an app that connects to various RTSP video camera feeds, and every once in a while, a corrupt video stream (which also fails to show on raw ffmpeg or VLC) would not only fail, but also crash my UWP app with an uncatchable memory violation error.
When debugging, I noticed that this error occurred when FFmpeg failed to correctly identify the pixel format for the incoming string, leading the avVideoCodecCtx->pix_fmt set to AV_PIX_FMT_NONE (i.e. -1). When this is passed to sws_getContext in UncompressedVideoSampleProvider::AllocateResources, it spawns the "attempt was made to access invalid memory" error I ultimately get in my C# code.
For now, I've forked the library and added an explicit check, before the call to AllocateResources, which throws an exception (that can be handled by my C# code) that the feed is invalid, and that's a good enough solution for me. However, it might not be the correct general-purpose handling for the library.
I can create a PR for my fix, but I'm guessing you would prefer to fix it some other way. In any case, cleaner error handling (whether via exception or HRESULT) is probably required for these scenarios.

@mcosmin222 We will have to fix this in our fork as well.


Exception type: System.InvalidOperationException

Exception type: System.InvalidOperationException
Message: An attempt was made to transition a task to a final state when it had already completed.
Stack Trace:    at WalletWasabi.Fluent.Desktop.Program.Main(String[] args)
Inner Exception:

Are you using the latest version? If not update Wasabi Wallet.
This issue is the same as https://github.com/WalletWasabi/WalletWasabi/issues/13099.

Without the inner exception this issue is impossible to address.


Research underlying issues using the TADA::idCensoredData function "Conflict between Condition and Limit" flag

Research question: Are the mismatches being found a result of this hierarchy/WQP implementation or are they user submission errors?
Is your feature request related to a problem? Please describe.
The idCensoredData function in CensoredDataSuite.R flags rows where detection limit metadata does not match:
cens$TADA.CensoredData.Flag = ifelse(cens$TADA.Detection_Type%in%c("Non-Detect","Over-Detect","Other")&cens$TADA.Limit_Type%in%c("Non-Detect","Over-Detect","Other")&!cens$TADA.Detection_Type==cens$TADA.Limit_Type,"Conflict between Condition and Limit",cens$TADA.CensoredData.Flag)
Describe the solution you'd like
WQP includes a hierarchy for delivering detection limit data that looks only at Result Detection Limit Type, not the combination of detection limit and detection condition fields.

Hierarchy
Result Detection Limit Type
Upper (+), lower (-), or other (0) limit

1
Practical Quantitation Limit
-

2
Lower Quantitation Limit
-

3
Sample-Specific Quantitation Limit
-

4
Estimated Quantitation Limit
-

5
Contract Quantitation Limit
-

6
Minimum Reporting Level
-

7
Reporting limit
-

8
Sample-specific min detect conc
-

9
Laboratory Reporting Level
-

10
Lower Reporting Limit
-

11
Sample Detection Limit
-

12
Lower limit of detection
-

13
Instrument Detection Level
-

14
Estimated Detection Level
-

15
Method Detection Level
-

16
Measurement Uncertainty
0

17
Long Term Method Detection Level
-

18
Interim Reporting Level
-

19
Daily detection limit
-

20
Blank-adjusted method detect limit
-

21
Contract Detection Limit
-

22
Upper Quantitation Limit
+

23
Upper Reporting Limit
+

24
Upper Calibration Limit
+

25
Field Holding Time Limit
0

26
Laboratory Holding Time Limit
0

27
Drinking Water Maximum
0

28
Systematic Uncertainty
0

29
Statistical Uncertainty
0

30
Water Quality Standard or Criteria
0

31
Specified in workplan
0

32
Taxonomic Loss Threshold
0

Describe alternatives you've considered
If this is a hierarchy WQP implementation issue, one solution may be to update the hierarchy to consider the combination of detection condition and limit fields. Alternatively, WQP can serve all limits in a JSON within the cell. For TADA, if this is a hierarchy issue, we may want to consider joining all detection limits as part of TADAdataRetrieval, and including logic to tell the function to look for if specific combinations if they are available (i.e., implementing the combination of detection condition and limit fields hierarchy within TADA - could then be transferrable to WQP as well after testing).
Alternatively, if this is a user submission error issue, WQX/WQP teams may be able to set requirements/QAQC checks for valid combinations using the logic we have already developed for TADA.
Additional context
Add any other context or screenshots about the feature request here.
](https://usepa.sharepoint.com/:w:/r/sites/WaterQualityPortal/_layouts/15/Doc.aspx?sourcedoc={6FA18F0E-8941-4788-AF00-8F83B4D079BB}&file=WQXDetectionLimitsBestPracticesGuide.docx&nav=eyJjIjozNjQwOTc0OTJ9&_DSL=1&action=default&mobileredirect=true)

@ehinman Any thoughts on this?

Definitely something worth evaluating in the data. My hunch is that most of the conflicts with left censored (condition) <--> right-censored (limit type) are user errors, since the right-censored limit types all have higher ranks than the left-censored limit types and would be skipped over if a left-censored limit type was also populated. In situations where it's right-censored (condition) <--> left-censored (limit type), we'd need to do some digging into all the limit types provided....if the condition is right-censored and ANY lower limits were provided, I think those would take precedent as the limit type populated in the result phys chem profile.
We could use TADA to select the most parsimonious condition-limit type combination if multiple limit types are provided. I think in this case, it might be wise to commit to trusting the condition over the limit types provided, and only drilling down so far as to whether they represent left- or right-censored. A tricky example, if the detection condition is "Not Detected" but the limit types provided are "Reporting limit" and "Practical Quantitation Limit", which do you choose? The condition (left-censored) matches both limit types (which describe left-censored limits). Perhaps then we could rely on the hierarchy table posted above to choose the "preferred" limit type?


Adding a few tests

I'm working on a bit of a refactor of modulesync. I started by writing some tests and figured I'd submit some of them first.

@danzilio could you push this again so we can trigger Travis-CI? We just turned it on for this repo.


current master does not build

fails with
Failed to execute goal on project BlazarService: Could not resolve dependencies for project com.hubspot:BlazarService:jar:1.0-SNAPSHOT: The following artifacts could not be resolved: com.hubspot:SingularityBase:jar:0.4.9-hs_stable-SNAPSHOT, com.hubspot:SingularityClient:jar:0.4.9-hs_stable-SNAPSHOT: Could not find artifact com.hubspot:SingularityBase:jar:0.4.9-hs_stable-SNAPSHOT in snapshots
Guess that there should not be a hubspot specific version in there.

Sorry about that, I forgot those snapshots aren't pushed to maven central. I'll update it to use a release version

I updated it to use the Singularity 0.4.11 release and also pushed a release of Blazar to Maven Central (version 0.3). You can see an example dropwizard config with all required fields here. There isn't much documentation and so far we've been developing it specifically for our own use so it may be hard to get up and running. Let us know if you run into any other issues.


New location for sms plugin

I have moved my sms plugin from:
https://github.com/aharris88/phonegap-sms-plugin
to:
https://github.com/cordova-sms/cordova-sms-plugin
Could you please update any references to this repo? Thanks.

Also, it now supports Windows Phone 8.


Comparing this with nuxt.js

Hi, this is not really an issue but a question..
how's this compare with static page generated by nuxt.js using "nuxt generate"

you better take a look at https://vuejs.org/v2/guide/ssr.html

Nuxt.js is a higher-level framework built on top of the Vue ecosystem which provides an extremely streamlined development experience for writing universal Vue applications.


feature: add update command

Signed-off-by: HusterWan<EMAIL_ADDRESS>Ⅰ. Describe what this PR did
add update container interface
Ⅱ. Does this pull request fix one issue?
fixes #631
Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #764 into master will decrease coverage by 0.31%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #764      +/-   ##
==========================================
- Coverage   13.96%   13.65%   -0.32%
==========================================
  Files         101      102       +1
  Lines        6108     6248     +140
==========================================
  Hits          853      853
- Misses       5200     5340     +140
  Partials       55       55

Impacted Files
Coverage Δ

ctrd/container.go
0% <0%> (ø)
:arrow_up:

cli/main.go
0% <0%> (ø)
:arrow_up:

daemon/mgr/container_types.go
15.38% <0%> (-0.49%)
:arrow_down:

daemon/mgr/container.go
2.9% <0%> (-0.23%)
:arrow_down:

cli/update.go
0% <0%> (ø)

client/container.go
0% <0%> (ø)
:arrow_up:

ctrd/utils.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4b484e3...0a3eff9. Read the comment docs.

I think that we should add some CLI integration test case for this update command. @HusterWan

Updated, PTAL @allencloud

LGTM, thanks a lot for your work.


Added pageUp and pageDown keys

Added the ability to navigate slides with pageUp and pageDown as requested in issue #310

Ok pushed the changes.

Thanks!


Is it possible to run hbGPS without accelerometer data?

First of all, thanks for this tool!
Would it possible to run hbGPS without accelerometer data, for instance to get only trips' duration, distance and type?

Good question. This actually already works and I justed test it. What you need to do is:

Point argument GGIRpath to an empty folder. It does not matter what folder it is as long as it is empty.
Make sure argument outputFormat is not set to "PALMS", it does not matter what you fill in as long as it is not "PALMS", e.g. "notPALMS".

This will then no longer try to imitate PALMS output format, but should include all the information you need.
As a next step in the hbGPS development we may need to:

Modify code to also allow for only using GPS data and still allow for imitating PALMS output format.
Add new input argument to indicate whether GPS recordings without matching ACC should be skipped or not.
Add documentation for all this.

I cannot promise that I will do this anytime soon as I do not have funding for spending more time on hbGPS at the moment. If you see funding opportunities or know someone with an interest in helping to maintain the repository then pm me (v.vanhees at acceleting.com)

Thanks!
It worked.
I am looking into this for a colleague, so I don't know if they have funding for this. If they do, I think they will be interested in working with you.
Best,
Renato.


Build on heroku fails

from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/lib/language_pack/instrument.rb:35:in `trace'

from /app/tmp/buildpacks/b7af5642714be4eddaa5f35e2b4c36176b839b4abcd9bfe57ee71c358d71152b4fd2cf925c5b6e6816adee359c4f0f966b663a7f8649b0729509d510091abc07/bin/support/ruby_compile:15:in `<main>'

!     Push rejected, failed to compile Ruby app.
!     Push failed

Could you give more info on what you’re trying to do, and some more logs? I don’t have much to go on with this.


Issue with k8s.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-interactive/

This is a Bug Report

Problem: localhost:8001 is not reachable in all the excercises
Proposed Solution:
Page to Update:
https://kubernetes.io/...

I followed the instructions for the tutorial and it all worked OK for me.
Be sure to heed the note on step 3

Note: Check the top of the terminal. The proxy was run in a new tab (Terminal 2), and the recent commands were executed the original tab (Terminal 1). The proxy still runs in the second tab, and this allowed our curl command to work using localhost:8001.

/triage support


Deploy other well known .yaml files, cron.yaml, index.yaml, etc...

Detect them in the project root and offer up a checkbox for the user to deploy them together with the app.

There are potentially many files, and their purpose will be unclear to new users who see them in project explorer.  So I suggest that we put *.yaml and Dockerfile in an /appengine subdirectory with a README.

The Cloud SDK recognizes 5 "config" yamls. cron, dispatch, dos, index, and queue. Everything else is a "service" yaml e.g. app.yaml.

Ok.  I'll write the samples with the Dockerfile and *.yaml in the project root.

Only the service yamls (as Jim says) are associated with the code, which is why that's the one that has always been deployed. I think that if we add an option to deploy these files we need to do it in a separated way. Probably a separated dialog that allows the user to select what "other" .yaml files to deploy.

Sounds good.  In terms of UI, maybe I can right-click on a .yaml file and
choose "Publish to App Engine..."?
On Fri, Feb 17, 2017 at 10:38 AM, Ivan Naranjo<EMAIL_ADDRESS>wrote:

Only the service yamls (as Jim says) are associated with the code, which
is why that's the one that has always been deployed. I think that if we add
an option to deploy these files we need to do it in a separated way.
Probably a separated dialog that allows the user to select what "other"
.yaml files to deploy.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-visualstudio/issues/403#issuecomment-280731268,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALO54vNsFD2IH8_AuLRR3VbK412_s5Xqks5rdek5gaJpZM4L5vwV
.

And to be honest the cron.yaml, index.yaml etc do not need to be at the root because they don't deploy code, they are really just configuration. They could be in a separate directory with a README as suggested. The only one that needs to be at the root is app.yaml since it delivers code.


Improve notes about CDN limitations

Ticket: #1925
Let’s rewrite the CDN limitation section again based on the new information provided by @palmiak. It looks like when Maciej talked about «Push CDN», he was talking about the same as the following section by Jared:

However, there may be some CDN setups that work fine with the above filters (for example: one that’s merely watching the contents of the wp-content/uploads directory and copying it to the CDN). For example, the filters seem to work fine with the default setups for WPEngine and Pantheon.

I changed the text to first hint about the differences between Push and Pull CDN and then describe how this relates to Timber.

Coverage remained the same at 94.324% when pulling 719d9d65aa5207ce59eb068efc8d85515a96d5cf on cdn-notes into dd57f2b7c285afb9bd8349ef379ef3f223271735 on master.

@jarednova Cool, yeah, additional headings surely help! I just added them.
However, from looking at #1929, there are also issues when working with WPEngine, which you mentioned should work. I’m guessing this needs yet another round of clarifications. Do we have any knowledge about CDN plugins that work flawlessly?

@gchtr I only used W3Total Cache with maxCDN (which is a typical pull zone). I don't know anything about those hosting related CDNs (like WPEngine) we would need to test them one by one.

Yeah, this info is definitely an improvement. A good @todo to come out of it would be to take a few popular WP hosts and describe their current compatibility. Even if it's a limited list, it might encourage others (or who knows, the hosts themselves?) to state where they are

Cool! I will start a new issue with a basic table of what we currently now.


Replaced ...spread operator in all cases excet short FixedPitch oscil…

…lations to prevent stack fill crashes.

Also removed some debug I accidentally left in. Apparently 50 people have downloaded this from npm since I published it yesterday, so... better patch it.


final prevents modification of other subpath

object template t;

final "/a/b/c" = 1;
"/a" = {
    SELF['e'] = 2;
    SELF;
};

gives
evaluation error [/tmp/t.pan:4.1-7.2]
/a cannot be modified; /a/b/c is marked as final
>>> call stack trace
>>> [/tmp/t.pan:4.1-7.2]
>>> ====================

@ned21 i labeled this as a bug

this is probably due to my limited understanding what SELF is.
i always assumed that SELF was some form of pointer-to, and eg "/a" = {SELF;}; is a noop.

@stdweird did this get fixed somewhere? Or is it a non-issue?

no, it's quite complicated to solve.

:fearful:


Async chunk loading breaks complex expressions in globalObject option

Bug report

What is the current behavior?
// webpack.config.js
  output: {
    library: 'myLib',
    libraryTarget: 'umd',
    globalObject: 'typeof self !== \'undefined\' ? self : this',
  },
  optimization: {
    splitChunks: {
      chunks: 'all',
      minSize: 1,
    }
  }

// index.js
  await import('./chunk')

generates code
var chunkLoadingGlobal = typeof self !== 'undefined' ? self : this["webpackChunkmyLib"] = typeof self !== 'undefined' ? self : this["webpackChunkmyLib"] || [];
/******/ 		chunkLoadingGlobal.forEach(webpackJsonpCallback.bind(null, 0));

The ternary expression for globalObject isn't protected as an expression, but gets mixed with the surrounding code.
In case the condition is true (typeof self !== 'undefined') and consequent path is taken, the result of this expression ends up being the equivalent of
var chunkLoadingGlobal = self

which then throws in the next line
Uncaught TypeError: chunkLoadingGlobal.forEach is not a function

Similar code also gets generated to the async chunk
typeof self !== 'undefined' ? self : this["webpackChunkmyLib"] =

which would also fail if the execution ever got that far.
If the current behavior is a bug, please provide the steps to reproduce.
Full minimal reproducible example in noppa/webpack-global-object-issue-repro.

What is the expected behavior?
The code in globalObject option should be treated as an arbitrary expression and either lifted to a variable or wrapped in parenthesis
var root = typeof self !== 'undefined' ? self : this
var chunkLoadingGlobal = root["webpackChunkmyLib"] = root["webpackChunkmyLib"] || [];

The problem is easily enough fixed on the user's side:
-     globalObject: 'typeof self !== \'undefined\' ? self : this',
+     globalObject: '(typeof self !== \'undefined\' ? self : this)',

and I get that this issue could end up closed as "working as intended". However, I think that this limitation should then at least be mentioned in the docs and/or some kind of warning should be given. The nasty thing about the current behavior is that the code only breaks under very specific conditions:

The app must contain async chunks. Without them, globalObject is only used in expression

```
     })(typeof self !== 'undefined' ? self : this, function() {
```
which doesn't break the way the `chunkLoadingGlobal` code does. Simply adding `/* webpackMode: "eager" */ ` to the import will "fix" the issue.

The condition in ternary must be true, as the RHS of the ternary actually works fine. In practice this means that the app crashes in browser (where self is defined) but not in Node.

Thus, the broken globalObject code is already widely used in the wild: grep.app search for unparenthesized ternaries in globalObject option.
I believe that at least these issues could be caused by this:

StackOverflow jsonpArray.push is undefined when the output library code splits
Related issue in vue-cli
#9766 not for the OP of that issue but maybe for the commenters saying that setting jsonpFunction didn't fix the issue for them

Other relevant information:
webpack version:  5.26.3 and 4.46.0
Node.js version: 15.6.0
Operating System:
Additional tools:

To be honestly using () is always good, because it is always protect your code, but yes we can fix it

Still valid


JSON Schemas external files

I have a project where during the tests I'm validating API JSON responses against written JSON schemas. My idea is to generate API documentation form it with minimal effort.
I have tried to reference to my schemas from the base schema without any result.
For example, I have base schema file for /confirmation resource - confirmation_api.json:
{
  "id": "/confirmation",
  "$schema": "http://json-schema.org/draft-04/schema#",
  "title": "Confirmation",
  "description": "Requests within confirmation path",
  "type": "object",
  "definitions": {
    "confirmation_token": {
      "type": "integer",
      "description": "Confirmation token",
      "example": 1
    }
  },
  "links": [
    {
      "title": "Confirm account",
      "description": "Confirm your account",
      "rel": "self",
      "href": "/api/v1/confirmation?confirmation_token={#/definitions/confirmation_token}",
      "method": "GET",
      "authentication_needed": false,
      "targetSchema": { "$ref": "show_confirmation.json" }
    }
  ]
}

and my schema file which I use for testing etc. show_confirmation.json
{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "type": "object",
  "required": ["id", "email", "created_at", "updated_at"],
  "properties": {
    "id" : { "type" : "string" },
    "email" : { "type" : "string" },
    "created_at" : { "type" : "string", "format": "date-time" },
    "updated_at" : { "type" : "string", "format": "date-time" }
  }
}

I was only able to load it to the base schema properties by properties: { "$ref": "show_confirmation.json#/properties" } but that is not what I want to achieve.
Is doca supporting reference to the schema from an external file? If yes what am I missing?

@Reedian in general, references to external files are supported.
Where is the properties: { "$ref": "show_confirmation.json#/properties" } part?  I don't see it in either file.  Also, what are the file names of each of these and are they in the same directory?  Is the second one show_confirmation.json?

@handrews I haven't included properties because it is not the part of my question, only the sidenote. Updated original message with file names.

@Reedian assuming those two files are in the same directory, that should work.
What is the error you are seeing?

@handrews exactly, they are in the same directory. I'm not seeing any error. It just does not get rendered.

As you can see on the screenshot above the response object is empty. My expectations were rather to see the response which I have defined in show_confirmation.json.

@Reedian I have reproduced this with both the bootstrap and internal cloudflare theme, and I am baffled.  Although this seems to be the same as #75 which I have shamefully forgotten about repeatedly (for a variety of reasons).  I'm going to poke at both examples a bit more, but may close this in favor of tracking the issue in the older ticket.

@handrews okay I will close the issue. Just for information please tell me are you planning to fix it anytime soon?

@Reedian I'm still trying to figure out why it happens, given that a similar construct works in numerous other doca-generated projects.  I definitely want to fix it.

@handrews closing this one. Fingers crossed that you will find solution :)


url resolution in css files, global css support and sass support at separate branch

What kind of change does this PR introduce?
[x] Bug fix
[x] Feature
[x] Docs update
What is the new behavior?

Added Global css feature via import statement
Fixed bug of url resolution in css files https://github.com/AngularClass/angular2-webpack-starter/issues/730
Added Sass/Scss support in separate branch

I think most of this was handled by #1304. If there is something from here that master is missing, feel free to rebase and open a new pull request. Thanks @hafizahmedattari.


New languages and regions

@aahill

@rlagh2 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


WFCORE-1112 use logger.debugf instead of manual string concatenation

Fix for ticket https://issues.jboss.org/browse/WFCORE-1112
org.jboss.logging.BasicLogger#debugf allow not replace template if debug level not available

Can one of the admins verify this patch?

this is okay to test

this is ok to test

:+1:
Thanks!


NTR fix the basket

Coverage remained the same at 42.148% when pulling 38c41af6f9c5437392c79c95ca2c5e2e9ea5fcf8 on NTR-fix-basket into e1afd89f41edc30d4a2d9bc84ee9508e2659785e on master.


ImportError: cannot import name 'ParamSpec' from 'typing_extensions'

I used Python 3.8 and requirement. txt but encountered an import error. I have tried many versions of Python, but they all report different errors.
ImportError: cannot import name 'ParamSpec' from 'typing_extensions' (gxz_sde/lib/python3.8/site-packages/typing_extensions.py)

I have the same problem, tensorflow and jax are not compatible


Modify the IfcObject's property/quantity

Hi,
Is it possible to modify the IfcObject's property/quantity value and then save ifc file with updated fields?

Yes, this is possible.
GG provides a method to find a property set (or quantity set) by name.  You can create it if it doesn't exist.
There is a method on a pset to add a property.  This will displace any existing property of the same name.
You do need to be careful.  A property (or quantity) set might be common to multiple elements.  And the property/quantity
itself might be referenced in multiple property/quantity sets.  So it's best to check, and duplicate the pset (if it is common)
and generate the property anew rather than simply change the assigned value.
If you want to generate an example file and have problems, you can create a pull request and I'll review it.


Make entire SettingsRow toggle the setting (closes #455)

(put this in a new PR to not merge from master into dev)
fixes #455

Checklist

[x] Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
[x] If this PR comes from a fork, please Allow edits from maintainers
[x] Set a speaking title. Format: {task_name} (closes #{issue_number}). For example: Use logger (closes # 41)
[x] Link your Pull Request to an issue (if applicable)
[x] Create Work In Progress [WIP] pull requests only if you need clarification or an explicit review before you can continue your work item.
[x] Make sure that your PR is not introducing unnecessary reformatting (e.g., introduced by on-save hooks in your IDE)
[x] Make sure that your PR does not contain changes in strings.xml (see issue #332)
[x] Make sure that your PR does not contain compiled sources (already set by the default .gitignore) and / or binary files

Description

#455 mentioned the settings being only toggleable by hitting the switch. This PR makes the entire SettingsRow toggle the switch, making it behave like stock Android settings.

(copy from the other PR, but still relevant)
This would need to be remembered for all settings added in the future
Todo: maybe fix the animation, stock Android has a little animation, filling the box from where you tapped. In the current implementation, it lights up the entire box immediately

Hi @tomjschwanke ,
thanks for your contribution! But it isn't as easy as it's in your PR, at least for the settings tracing switch. We already had your proposal implemented but removed it because we had to introduce more complexity to the switch and the row. And to be consistent we also removed it for the simpler notification switch rows.
So with the clickable row states like this can occur - the text says Stopped but the switch is On.

Reproduce:

Start with Active Exposure Logging
Disable Bluetooth
Click on the row
Tracing is Stopped and the switch is Off
Click on the switch (not the row)
Result: The text says Stopped but the switch is On

That's only one wrong state maybe there are others. If you can fix this I'm happy to include your PR, but you would have to provide a list of manual tests. After this I'll verify that everything is working like expected and also that accessibility isn't broken with this new click target.
I also included the logic for the switch, images and text states, can be found here.

The following table explains the different stati which can appear in the ui.
This follows this prioritization: Tracing, Bluetooth, Connection will only be relevant in one exact case, Bluetooth is relevant in two different cases, but independently from the Connection status. And in every other case Tracing will be shown.

Cheers,
Luka

Ahh I get it. Hitting the switch doesnt work now, as the switch doesn't have an OnClickListener anymore (thats on the Row now)
We'd just need to set an OnClickListener on both and update the other accordingly, I will look into this.
I can't follow your steps, as I am unable to sign the app with the correct key, so once I come up with a potential fix, you'd need to test it.

I have changed it back to the way it was before, but added additional OnClickListeners for the Rows. Notification settings now toggle when clicking either on the Row or on the Switch. The tracing switch should behave the same. Before, I was able to change the Switch but it had no effect (as there was no OnClickListener bound to it) but now when I hit the switch, it gives me the Error message (because it's not signed).
The only issue I still have right now is, when the user slides the switch instead of clicking on it, the setting (+text) doesn't change, this issue exists in the production version too, however. I'll look into this.

Scanned with Accessibility scanner by Google
As you can see, it does not interfere with touch-targets, the switches remain the only ones (which should maybe actually be changed, the apps suggestion is to make the touch targets bigger).
I have already merged the switch sliding fix into this locally to test it, and everything is working.
Tapping on the row --> Option toggled
Tapping on the switch --> Option toggled
Sliding the switch --> Option toggled if position changed

When using talkback, tapping on the settings says "on" / "off" depending on the switch position. It only reads this on the second tap. This also happens in the production version, so this PR doesn't change that.

It seems to work fine with Talkback :)

I have no idea, why it fails the check, it's up to date with dev and quickbuild on dev passes, while on here it complains about deprecated features being used

Thank's for the fast implementation, the builds due to a missing space.
Click on Details on Circle CI in this PR

Than you can open this Report: https://2305-268027139-gh.circle-artifacts.com/0/reports/ktlint/ktlintMainSourceSetCheck.txt

To reproduce this locally run gradle quickBuild. Your error should be fixed by running gradle ktlintFormat.

Thanks, I'm not used to CircleCI and style enforcement yet.
I have fixed it now and it runs quickBuild successfully


transition typos

There are typos at a transition name attribute. one, two
I guess it should be v-img-fade and I can't see transition about img-fade now.

Thank you very much @jkiimm for the report!
I've fixed first one and deleted second, since it wasn't necessary.
Appreciate your attentiveness!


Open apps with parameter

I'm using this plugin, and work perfectly when I open other apps without parameter. Now I'm building 2 flutter apps, in first apps, I want to click button then open 2nd apps but with parameter, like to tell 2nd app to open specific page or to show some message. Can this handled by this plugin? thanks

@SevenHeaven93 that's not supported by the plugin yet

bump  Any update on this @echonox ?

@cookseym sorry for the late response I'm not the owner of this plugin @pichillilorenzo is, I would gladly invest some free time to make a pull request but I'm very busy at the moment.


[Frontend] Integrate GET Join Us API

Deliverables -

[ ] Go to admin dashboard(by logging in using admin credential, which can be found in project readme) => Click on Join Us tab. It should call the GET Join Us API and should show the list of data in the form of card. [one data in one card]
[ ] Each card should have a delete button/icon [based on whichever ui looks better ]

The api can be found at https://github.com/HITK-TECH-Community/Community-Website/blob/main/backend/app/routes/joinUs/index.js

I would like to work on it but do we have any existing design for cards ?

I would like to work on it but do we have any existing design for cards ?

@Lalit3716 You should be able to use https://github.com/HITK-TECH-Community/Community-Website/tree/main/frontend/src/pages/Broadcast/Component/AllBroadcasts/Card this component for the same.

I would like to work on it but do we have any existing design for cards ?

@Lalit3716 You should be able to use https://github.com/HITK-TECH-Community/Community-Website/tree/main/frontend/src/pages/Broadcast/Component/AllBroadcasts/Card this component for the same.

Oh Okay! You can assign this to me then!

Hi, I am extremely sorry to inform you that I will be unable to do this task due to unavailability of time on my side.
Kindly assign this issue to someone else.
Thank You!

Can I work on this issue?

Sure @Aman16-ai Please go ahead


Fix key of field without quoting issue

Fixes #586

Dear @markphelps , do you mind review this PR or give some suggestion?

Dear @dgsb, do you mind review this PR or give some suggestion?


Fix race condition in strict mode and annotate_pod_ip=true

Issue #, if available:
When ANNOTATE_POD_IP = false and NETWORK_POLICY_ENFORCING_MODE=strict --> all works fine
ipamd will send a request to NPA to attach probes to the new pod. NP agent returns success after attaching the probes. Then ipamd will mark pod as ready and running. Once the pod is ready network policy controller will discover the pod and add it to the policy endpoints. When NPA reconciles the policy endpoints, it notices the probes are already attached and just updates the maps accordingly
When ANNOTATE_POD_IP = true and NETWORK_POLICY_ENFORCING_MODE=strict --> issue
With ANNOTATE_POD_IP = true, pod can be discovered and added to policy endpoint by controller even before pod is ready and running. So in this case, we are hitting a race condition where we are trying to attach probes to pod from two different go routines. One which started from ipamd request and other which started from reconcile policy endpoint request. Both routines are trying to attach the probes at same time and as a result the internal data structures are not being updated correctly. Due to this network policies are not being applied to the right map ids
Description of changes:
Have a lock per pod which will be used while attaching the probes to the pod. While attaching probes, take the lock and attach the probes and release the lock after updating all the data structures. In this case even if two go routines come at the same time, one will wait for the lock and start only after the first one has completed attaching the probes. So when second one  checks if probes are already attached, it will be true and does nothing

Testing *

Simulated the race condition with some sleeps.
Logs before the change
"level":"info","ts":"2024-10-23T06:48:15.213Z","logger":"controllers.policyEndpoints","caller":"controllers/policyendpoints_controller.go:316","msg":"Processing Pod: ","name:":"tester1-6b498cbd59-zqwbw","namespace:":"test","podIdentifier: ":"tester1-6b498cbd59-test"}
{"level":"info","ts":"2024-10-23T06:48:15.213Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:462","msg":"AttacheBPFProbes for","pod":"tester1-6b498cbd59-zqwbw"," in namespace":"test"," with hostVethName":"eni81e6d8fec9f"}
{"level":"info","ts":"2024-10-23T06:48:15.213Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:682","msg":"Load the eBPF program"}
{"level":"info","ts":"2024-10-23T06:48:15.213Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:684","msg":"In loadBPFProgram, Waiting for 7 secs for enforceNpToPod to complete attaching probes"}
{"level":"info","ts":"2024-10-23T06:48:19.290Z","logger":"rpc-handler","caller":"rpc/rpc_handler.go:59","msg":"Received Enforce Network Policy Request for Pod","Name":"tester1-6b498cbd59-zqwbw","Namespace":"test"}
{"level":"info","ts":"2024-10-23T06:48:19.290Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:770","msg":"No map instance found"}
{"level":"info","ts":"2024-10-23T06:48:19.290Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:462","msg":"AttacheBPFProbes for","pod":"tester1-6b498cbd59-zqwbw"," in namespace":"test"," with hostVethName":"eni81e6d8fec9f"}
{"level":"info","ts":"2024-10-23T06:48:19.290Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:682","msg":"Load the eBPF program"}
{"level":"info","ts":"2024-10-23T06:48:19.323Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:698","msg":"Prog Info: ","Pin Path: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_ingress"}
{"level":"info","ts":"2024-10-23T06:48:19.324Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:702","msg":"PinPath for this pod: ","PinPath: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_ingress"}
{"level":"info","ts":"2024-10-23T06:48:19.324Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:705","msg":"Prog Load Succeeded","for ":"ingress","progFD: ":19}
{"level":"info","ts":"2024-10-23T06:48:19.324Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:574","msg":"Attempting to do an Ingress Attach ","with progFD: ":19}
{"level":"info","ts":"2024-10-23T06:48:19.327Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:473","msg":"Successfully attached Ingress TC probe for","pod: ":"tester1-6b498cbd59-zqwbw"," in namespace":"test"}
{"level":"info","ts":"2024-10-23T06:48:19.327Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:682","msg":"Load the eBPF program"}
{"level":"info","ts":"2024-10-23T06:48:19.349Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:698","msg":"Prog Info: ","Pin Path: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_egress"}
{"level":"info","ts":"2024-10-23T06:48:19.349Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:702","msg":"PinPath for this pod: ","PinPath: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_egress"}
{"level":"info","ts":"2024-10-23T06:48:19.349Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:705","msg":"Prog Load Succeeded","for ":"egress","progFD: ":21}
{"level":"info","ts":"2024-10-23T06:48:19.349Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:608","msg":"Attempting to do an Egress Attach ","with progFD: ":21}
{"level":"info","ts":"2024-10-23T06:48:19.349Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:488","msg":"Successfully attached Egress TC probe for","pod: ":"tester1-6b498cbd59-zqwbw"," in namespace":"test"}
{"level":"info","ts":"2024-10-23T06:48:19.349Z","logger":"controllers.policyEndpoints","caller":"controllers/policyendpoints_controller.go:773","msg":"Active policies available against","podIdentifier":"tester1-6b498cbd59-test"}
{"level":"info","ts":"2024-10-23T06:48:19.349Z","logger":"rpc-handler","caller":"rpc/rpc_handler.go:81","msg":"Active policies present against this pod and this is a new Pod to the local node, configuring firewall rules...."}
{"level":"info","ts":"2024-10-23T06:48:19.349Z","logger":"rpc-handler","caller":"rpc/rpc_handler.go:83","msg":"Waiting for 5 secs before enforcing policies againts pod"}
{"level":"info","ts":"2024-10-23T06:48:22.247Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:698","msg":"Prog Info: ","Pin Path: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_ingress"}
{"level":"info","ts":"2024-10-23T06:48:22.247Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:702","msg":"PinPath for this pod: ","PinPath: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_ingress"}
{"level":"info","ts":"2024-10-23T06:48:22.247Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:705","msg":"Prog Load Succeeded","for ":"ingress","progFD: ":23}
{"level":"info","ts":"2024-10-23T06:48:22.247Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:574","msg":"Attempting to do an Ingress Attach ","with progFD: ":23}
{"level":"info","ts":"2024-10-23T06:48:22.248Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:473","msg":"Successfully attached Ingress TC probe for","pod: ":"tester1-6b498cbd59-zqwbw"," in namespace":"test"}
{"level":"info","ts":"2024-10-23T06:48:22.248Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:682","msg":"Load the eBPF program"}
{"level":"info","ts":"2024-10-23T06:48:22.292Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:698","msg":"Prog Info: ","Pin Path: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_egress"}
{"level":"info","ts":"2024-10-23T06:48:22.292Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:702","msg":"PinPath for this pod: ","PinPath: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_egress"}
{"level":"info","ts":"2024-10-23T06:48:22.292Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:705","msg":"Prog Load Succeeded","for ":"egress","progFD: ":25}
{"level":"info","ts":"2024-10-23T06:48:22.292Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:608","msg":"Attempting to do an Egress Attach ","with progFD: ":25}
{"level":"info","ts":"2024-10-23T06:48:22.292Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:488","msg":"Successfully attached Egress TC probe for","pod: ":"tester1-6b498cbd59-zqwbw"," in namespace":"test"}
{"level":"info","ts":"2024-10-23T06:48:22.292Z","logger":"controllers.policyEndpoints","caller":"controllers/policyendpoints_controller.go:329","msg":"Successfully attached required eBPF probes for","pod:":"tester1-6b498cbd59-zqwbw","in namespace":"test"}
{"level":"info","ts":"2024-10-23T06:48:22.292Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:726","msg":"Pod has an Ingress hook attached. Update the corresponding map","progFD: ":23,"mapName: ":"ingress_map"}
{"level":"info","ts":"2024-10-23T06:48:22.292Z","logger":"ebpf-client","caller":"utils/utils.go:163","msg":"L4 values: ","protocol: ":254,"startPort: ":0,"endPort: ":0}
{"level":"info","ts":"2024-10-23T06:48:22.292Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:982","msg":"Current L4 entry count for catch all entry: ","count: ":0}
{"level":"info","ts":"2024-10-23T06:48:22.293Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:984","msg":"Total L4 entry count for catch all entry: ","count: ":0}
{"level":"info","ts":"2024-10-23T06:48:22.293Z","logger":"ebpf-client","caller":"utils/utils.go:163","msg":"L4 values: ","protocol: ":254,"startPort: ":0,"endPort: ":0}
{"level":"info","ts":"2024-10-23T06:48:22.293Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:785","msg":"ID of map to update: ","ID: ":175}
{"level":"info","ts":"2024-10-23T06:48:22.293Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:740","msg":"Pod has an Egress hook attached. Update the corresponding map","progFD: ":25,"mapName: ":"egress_map"}
{"level":"info","ts":"2024-10-23T06:48:22.293Z","logger":"ebpf-client","caller":"utils/utils.go:163","msg":"L4 values: ","protocol: ":254,"startPort: ":0,"endPort: ":0}
{"level":"info","ts":"2024-10-23T06:48:22.293Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:982","msg":"Current L4 entry count for catch all entry: ","count: ":1}
{"level":"info","ts":"2024-10-23T06:48:22.293Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:984","msg":"Total L4 entry count for catch all entry: ","count: ":1}
{"level":"info","ts":"2024-10-23T06:48:22.293Z","logger":"ebpf-client","caller":"utils/utils.go:182","msg":"L4 values: ","protocol: ":6,"startPort: ":443,"endPort: ":0}
{"level":"info","ts":"2024-10-23T06:48:22.293Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:785","msg":"ID of map to update: ","ID: ":176}

Logs after the change
{"level":"info","ts":"2024-10-23T07:07:02.756Z","logger":"controllers.policyEndpoints","caller":"controllers/policyendpoints_controller.go:316","msg":"Processing Pod: ","name:":"tester1-6b498cbd59-h24t2","namespace:":"test","podIdentifier: ":"tester1-6b498cbd59-test"}
{"level":"info","ts":"2024-10-23T07:07:02.756Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:452","msg":"Got the lock and going ahead with attach probes"}
{"level":"info","ts":"2024-10-23T07:07:02.756Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:464","msg":"AttacheBPFProbes for","pod":"tester1-6b498cbd59-h24t2"," in namespace":"test"," with hostVethName":"eni44d70feca88"}
{"level":"info","ts":"2024-10-23T07:07:02.756Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:684","msg":"Load the eBPF program"}
{"level":"info","ts":"2024-10-23T07:07:02.756Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:686","msg":"In loadBPFProgram, Waiting for 7 secs for enforceNpToPod to complete attaching probes"}
{"level":"info","ts":"2024-10-23T07:07:06.828Z","logger":"rpc-handler","caller":"rpc/rpc_handler.go:59","msg":"Received Enforce Network Policy Request for Pod","Name":"tester1-6b498cbd59-h24t2","Namespace":"test"}{"level":"info","ts":"2024-10-23T07:07:06.828Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:772","msg":"No map instance found"}
{"level":"info","ts":"2024-10-23T07:07:09.800Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:700","msg":"Prog Info: ","Pin Path: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_ingress"}
{"level":"info","ts":"2024-10-23T07:07:09.801Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:704","msg":"PinPath for this pod: ","PinPath: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_ingress"}
{"level":"info","ts":"2024-10-23T07:07:09.801Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:707","msg":"Prog Load Succeeded","for ":"ingress","progFD: ":19}{"level":"info","ts":"2024-10-23T07:07:09.801Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:576","msg":"Attempting to do an Ingress Attach ","with progFD: ":19}
{"level":"info","ts":"2024-10-23T07:07:09.803Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:475","msg":"Successfully attached Ingress TC probe for","pod: ":"tester1-6b498cbd59-h24t2"," in namespace":"test"}
{"level":"info","ts":"2024-10-23T07:07:09.803Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:684","msg":"Load the eBPF program"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:700","msg":"Prog Info: ","Pin Path: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_egress"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:704","msg":"PinPath for this pod: ","PinPath: ":"/sys/fs/bpf/globals/aws/programs/tester1-6b498cbd59-test_handle_egress"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:707","msg":"Prog Load Succeeded","for ":"egress","progFD: ":21}{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:610","msg":"Attempting to do an Egress Attach ","with progFD: ":21}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:490","msg":"Successfully attached Egress TC probe for","pod: ":"tester1-6b498cbd59-h24t2"," in namespace":"test"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:495","msg":"Done with attach probes"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"controllers.policyEndpoints","caller":"controllers/policyendpoints_controller.go:329","msg":"Successfully attached required eBPF probes for","pod:":"tester1-6b498cbd59-h24t2","in namespace":"test"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:728","msg":"Pod has an Ingress hook attached. Update the corresponding map","progFD: ":19,"mapName: ":"ingress_map"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"utils/utils.go:163","msg":"L4 values: ","protocol: ":254,"startPort: ":0,"endPort: ":0}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:986","msg":"Total L4 entry count for catch all entry: ","count: ":0}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:452","msg":"Got the lock and going ahead with attach probes"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:787","msg":"ID of map to update: ","ID: ":183}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:759","msg":"Pod already has Ingress Probe attached - ","Name: ":"tester1-6b498cbd59-h24t2","Namespace: ":"test"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:763","msg":"Pod already has Egress Probe attached - ","Name: ":"tester1-6b498cbd59-h24t2","Namespace: ":"test"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:464","msg":"AttacheBPFProbes for","pod":"tester1-6b498cbd59-h24t2"," in namespace":"test"," with hostVethName":"eni44d70feca88"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:495","msg":"Done with attach probes"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"controllers.policyEndpoints","caller":"controllers/policyendpoints_controller.go:773","msg":"Active policies available against","podIdentifier":"tester1-6b498cbd59-test"}
{"level":"info","ts":"2024-10-23T07:07:09.829Z","logger":"rpc-handler","caller":"rpc/rpc_handler.go:81","msg":"Active policies present against this pod and this is a new Pod to the local node, configuring firewall rules...."}
{"level":"info","ts":"2024-10-23T07:07:09.830Z","logger":"rpc-handler","caller":"rpc/rpc_handler.go:83","msg":"Waiting for 5 secs before enforcing policies againts pod"}
{"level":"info","ts":"2024-10-23T07:07:09.830Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:742","msg":"Pod has an Egress hook attached. Update the corresponding map","progFD: ":21,"mapName: ":"egress_map"}
{"level":"info","ts":"2024-10-23T07:07:09.830Z","logger":"ebpf-client","caller":"utils/utils.go:163","msg":"L4 values: ","protocol: ":254,"startPort: ":0,"endPort: ":0}
{"level":"info","ts":"2024-10-23T07:07:09.830Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:984","msg":"Current L4 entry count for catch all entry: ","count: ":0}
{"level":"info","ts":"2024-10-23T07:07:09.830Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:986","msg":"Total L4 entry count for catch all entry: ","count: ":0}
{"level":"info","ts":"2024-10-23T07:07:09.830Z","logger":"ebpf-client","caller":"utils/utils.go:163","msg":"L4 values: ","protocol: ":254,"startPort: ":0,"endPort: ":0}
{"level":"info","ts":"2024-10-23T07:07:09.830Z","logger":"ebpf-client","caller":"ebpf/bpf_client.go:787","msg":"ID of map to update: ","ID: ":184}

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The logic and the code behind lock looks good to me.

If the newer log messages that show the attachProbs lock taking effect is seen in the agent logs output, please share it.

Another comment. Looking at the code itself, I do not see ANNOTATE_POD_IP is to true is leading to the race, but irrespective the lock to avoid race seems alright.
We have to run the cyclonus test to ensure that we aren't introducing any regression with this change.

Thanks for the review @orsenthil. I added logs in the description. In logs before the change we can see the race condition where attach probes is happening twice. In logs after change, we can see the lock being taken by one thread and second one is waiting on the lock till first one completes
Regarding ANNOTATE_POD_IP, I added some details in the description. In strict mode IPAMD calls network agent to attach probes. NPA attaches the probes and returns success to IPAMD and IPAMD will mark pod as ready and running. The pod will be discovered by np controller only after pod enters ready state
When ANNOTATE_POD_IP=true, pod will be discovered by NP controller even before pod enters ready state. Cx usually set this to true for fast NP reconciliation. So in this case we are hitting the race condition. NPA from IPAMD call is in the process of attaching the ebpfprobes. Now NP controller reconcile request comes, it will check if probes are already attached. NP agent in other thread is in the process of attaching the probes and did not complete updating all internal datastructures. When reconcile request thread checks if probes are attached -> result is no and it will try to attach the probes. Both go routines are now happening parallely and end result is internal data structures not being updated correctly

Completed running cyclonus tests on the change. All tests passed


FPS Counter [REQ]

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
should add FPS Counter on top left or right make it customize

Shift + F5.


Several data store depending on the dapp

Hi,
Is it possible to have different data store for the same address, depending on the dapp I am on?
Sorry to put that in the issues, I would normally go to Stackoverflow, but as it is an early stage project, I thought it would make more sense here.

Not yet, we want to gather more feedback on our initial release. Thanks for raising though, now we know that there is demand for it :)


chore(main): release 0.4.4

:robot: I have created a release beep boop
0.4.4 (2024-02-22)
Miscellaneous Chores

release 0.4.3 (50fba0c)
release 0.4.4 (03c4d6c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/socialgene/sgnf/releases/tag/v0.4.4 :sunflower:


[ansible/artifactory] Fix for #273 - Intermediate TLS configuration

PR Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] Title of the PR starts with installer/product name (e.g. [ansible/artifactory])
[X] CHANGELOG.md updated
[ ] Variables and other changes are documented in the README.md

What this PR does / why we need it:
This updates the NGinx https encryption to the "Intermediate" recommendations of the Mozilla foundation. Artifactory is supposed to secure the software supply chain. Having good encryption for data in transit is often required for compliance reasons. The current settings are outdated, moreover TLSv1.1 is no longer compliant.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #273
Special notes for your reviewer:
Testing the result can be done with https://observatory.mozilla.org/

Thank you for raising the PR.
We will review it internally and get back to you if any changes are required.

@bbaassssiiee can you pls rebase to jp-10.12.3 branch to fix conflicts   so that I can plan to merge to master

@bbaassssiiee Pls squash all your commits to single one

@@bbaassssiiee can you pls rebase to jp-10.12.3 branch (happened after other 2 PRs merged)


Unclear about backing option for CloudStor

File: docker-for-aws/persistent-data-volumes.md, CC @johndmulhausen
At the top of the document, backing is defined:

[...]In Docker for AWS, Cloudstor has two backing options:

relocatable data volumes are backed by EBS.
shared data volumes are backed by EFS.

Later on, in the Use a unique volume per task using EBS section:

[...]Besides backing=local, the following volume options are available:

And further, in one of the examples:

[...],volume-opt=backing=local,[...]

Is local a valid value? Or should this be relocatable? If local is valid, it should be documented.
Thank you!

cc @ddebroy

'local' is a doc error. Thanks for pointing it out!


When a list is scrolling, children can't be tapped

Fixes #5023 better than #5222 did.
The key difference is that since the controller's state is now used in the build function, we have to setState() in the _stop() function and in the status handler.
Also added more tests.


Clarify SharePoint Azure SQL MI instructions

Clarifies that you must use the New-SPConfigurationDatabase to create a new farm using Azure SQL Managed Instance, or Connect-SPConfigurationDatabase to join an existing farm using Azure SQL Managed Instance.
Clarifies that SharePoint doesn't support connecting to Azure SQL Managed Instance using Windows authentication.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


Workers will now retry (but not re-resolve) on some ExecuteFetch failures

@enisoc @alainjobart
First pass at retrying for errors.  Wanted to get your thoughts on this approach - still need to add re-resolving, but I think it should be straight-forward with this approach.
Existing tests pass, but nothing is explicitly testing tablets temporarily going away. I'd like to add something to our test suite along those lines (maybe vtctl Pause/Resume commands, or maybe just easy ways for disabling and enabling queryservice).

Coverage increased (+0.01%) when pulling 8db47cdcf46e3b18aac09e83bd122dad6042f926 on aaijazi_workers_retry_on_error into 8083fcacaa29c3a37baa2cbaab179a495faa189d on master.

Coverage increased (+0.02%) when pulling 8db47cdcf46e3b18aac09e83bd122dad6042f926 on aaijazi_workers_retry_on_error into 8083fcacaa29c3a37baa2cbaab179a495faa189d on master.

Coverage increased (+0.02%) when pulling e10510f6db4e55c94bdfea70b0320bd931dda727 on aaijazi_workers_retry_on_error into 54c2da34fdcd2ab0ffad4330efca5d8082dab1b7 on master.

As discussed in person, going to hold off on adding unit tests at the time. I'm going to submit as-is, and come back to this later to add re-resolving.


ci: introduce skywalking-eyes

Introduce apache/skywalking-eyes to check the license header.

Also, the existing license headers are the one specific to ASF projects, so we'd better fix them

Codecov Report

Merging #106 (4ac4d19) into master (9cca3cc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #106   +/-   ##
=======================================
  Coverage   65.95%   65.95%
=======================================
  Files          15       15
  Lines         702      702
=======================================
  Hits          463      463
  Misses        195      195
  Partials       44       44

Impacted Files
Coverage Δ

config_discovery.go
88.88% <ø> (ø)

correlation.go
87.50% <ø> (ø)

internal/idgen/idgen.go
0.00% <ø> (ø)

noop.go
66.66% <ø> (ø)

plugins/http/client.go
48.78% <ø> (ø)

plugins/http/server.go
50.00% <ø> (ø)

propagation/propagation.go
50.53% <ø> (ø)

reporter/grpc.go
54.35% <ø> (ø)

reporter/log.go
0.00% <ø> (ø)

sampler.go
67.64% <ø> (ø)

... and 5 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9cca3cc...4ac4d19. Read the comment docs.

License Expected — Waiting for status to be reported

Pending check is missing. I think you need to keep it or update .asf.yml first in another PR.

License Expected — Waiting for status to be reported

Pending check is missing. I think you need to keep it or update .asf.yml first in another PR.

This is not ASF project so we don't have .asf.yml 😉 Just remove that require


default server leads to a security problem by unneeded users

My Setup

Operating System: Win/macOS/Linux (all clients)
App Version: 2.17.5

[x] I have tested with the latest version
[x] I can simulate the issue easily

Description
After installing the desktop client, the server open.rocket.chat is set as default in the input line for the server. In our environment we observe quite a lot of users who do not enter our own "internal" server URL after installing the client (although our documentation clearly states our server address), but simply click on "connect", thereby connecting to the open.rocket.chat server and entering their local access data, but think or are believed to be connected to the server of their own organization. This way, user data of an organization is transferred to third parties, Rocket.Chat. I trust Rocket.Chat as an organization of course, but from a security point of view this is ultimately a security risk. Admittedly, this is of course misconduct on the part of the users, but it is still a security risk that inexperienced users disclose their local user data. This problem could be solved by a version of the desktop client pre-built with the server data, but then an admin would have to package the clients for each operating system including the mobile apps. This would involve considerable effort. Of course I understand that Rocket.Chat wants to offer its own open platform as low-threshold as possible. But this might be a security risk for other systems.

Current Behavior
open.rocket.chat is set as default
Expected Behavior
no default server or a secure way not to "accidentally" connect to it

In our organization we do not have that issue at all.
All you need to do is add servers.json file to folder *c:\Program Files\Rocket.Chat\resources* and configure your own server in servers.json file.
So every Rocket.Chat.Electron application will connect to your RC server at startup.
And no security breach at all.

We also had to configure that, but despite having rolled out the server.json to all clients, a handfull still managed to connect to the wrong server - after several months that is.
If the server.json is present, it should hide the server bar on the left.  They frantically called us to fix it. Anyway, there should be an option to completely hide or restrict access to other servers. But I guess that would be an improvement suggestion for the server section.

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.
Thank you!


Menu Stops Working on SPA using Angular

All,
I am working on a project and we have implemented the jQuery mmenu and have come across an issue that we are unable to resolve.  The issue presents itself on after we scroll to the bottom of a page that has a lot of content.  When we scroll back to the top of the page and attempt to show/hide the menu it stops responding and we have to refresh the page.  Not optimal.
Can you point us in a direction that will help resolve this issue?
Randy Sigmond

Is there an online example I could have a look at?
Otherwise I'm going to close this issue.

Fred,
Thank for your response, you can close this issue.
Thank you,
Randy Sigmond
U.S. Department of Defense
Defense Contract Audit Agency, HQ
Ph:<PHONE_NUMBER>
<EMAIL_ADDRESS>-----Original Message-----
From: Fred Heusschen<EMAIL_ADDRESS>Sent: Monday, February 02, 2015 2:11 PM
To: BeSite/jQuery.mmenu
Cc: Sigmond, Randy, Mr, DCAA
Subject: Re: [jQuery.mmenu] Menu Stops Working on SPA using Angular (#256)
Is there an online example I could have a look at?
Otherwise I'm going to close this issue.
—
Reply to this email directly or view it on GitHub https://github.com/BeSite/jQuery.mmenu/issues/256#issuecomment-72517495 . https://github.com/notifications/beacon/AJwnWZYBY32nk3gL9dsNrdC6IHa8FUk6ks5nn8MygaJpZM4DKFCE.gif


Floaters in the rendering visualizations

Hi!
Thanks for your great work! We intend to evaluate some Tum sequences with your code. We found that there are some floaters in the rendering image and depth(We provide some visualizations about fr2_xyz and fr3_long_office sequence). Can you give me some suggestions or experience about this phenomenon? Do you think Hash collision is a potential cause?
Thanks!

Hi @ming82871, thanks for your interest in our work. There are several potential reasons for this issue. 1) For rendering these results, have you used depth-guided sampling? As our truncation region is quite small, you need to use either depth-guided sampling or importance sampling (or just a sufficiently large amount of sample points) to make sure there are sample points within the truncation region. 2) Co-SLAM keeps and trains on only a small fraction of pixels with a small number of iterations for efficiency, you may not be able to get a high PSNR for rendering due to the insufficient number of pixels used for training.

Hello, excuse me, how to do visualization


assertj-core 3.18.1

Thanks, but we'd prefer to only use Dependabot for library bumps - it makes it easier for us to reason about to have just a single source of Java dependency bump PRs.
Sorry, but I'll close this and the other related tickets.


Add: reverseString algorithm

Please have a look at https://github.com/amanmehara/programming/blob/master/CONTRIBUTING.md and make changes accordingly.
I'll approve and merge afterwards! 😃

@mahendrabp closing this as there is no response for last 2 weeks.
Please reopen and submit after incorporating suggested changes.


mkpr

Applied mkpr on package.json
{"op":"remove","path":"/scripts/posttest"}

Coverage remained the same at 87.261% when pulling 4e96310e467492265e6eb6aedea1ffe548a1266a on mkpr/1 into a9b42237c7107f6ef2e8bd68c04a9a142e65001c on master.


Control screensaver

Looks like a screensaver is enabled by default. An option to change the time, or to disable it completely, would be useful.

Good point!

To disable it, edit the file /etc/kbd/config:
BLANK_TIME=0
BLANK_DPMS=off
POWERDOWN_TIME=0

Hmm just enabled it 15 mins ago and console's blank again, there's more to it I guess..

Another source suggests: To prevent the screen from going blank try adding consoleblank=0 to the end of the first line of /boot/cmdline.txt. Testing..

Forgot to doc the zero...


Unquoted property name caused renaming issue with Google Closure Compiler

Hi,
Can these property be defined using quoted string literal?
https://github.com/moment/moment/blob/d5262a01beec4f6ed1b0ad73ba2da66782b2f60b/lib/locale/relative.js#L2-L14
When I tried to compile moment.js with Google Closure Compiler and moment js externs, these property name is renamed. I think it's better to use string literal like:
var defaultRelativeTime = {
    'future' : 'in %s',
    'past'   : '%s ago',
    's'  : 'a few seconds',
    'm'  : 'a minute',
    'mm' : '%d minutes',
    'h'  : 'an hour',
    'hh' : '%d hours',
    'd'  : 'a day',
    'dd' : '%d days',
    'M'  : 'a month',
    'MM' : '%d months',
    'y'  : 'a year',
    'yy' : '%d years'
};

This should not be required, as these are all valid JavaSCript identifiers.  See http://stackoverflow.com/questions/4348478/what-is-the-difference-between-object-keys-with-quotes-and-without-quotes