relocation truncated error when compiling elf_to_hex.c file to create the Mem Hex files

Hi all,
I don't know if it is only with my gcc version 11.1.0 but I am getting the next error when I tried to use the elf_to_hex.c file to compile with the Makefile in Tests/elf_to_hex.
The error:
gcc -g -o elf_to_hex  elf_to_hex.c  -lelf
/tmp/cc4D9tPQ.o: in function `c_mem_load_elf':
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:94:(.text+0x25a): relocation truncated to fit: R_X86_64_PC32 against symbol `bitwidth' defined in .bss section in /tmp/cc4D9tPQ.o
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:98:(.text+0x2a2): relocation truncated to fit: R_X86_64_PC32 against symbol `bitwidth' defined in .bss section in /tmp/cc4D9tPQ.o
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:130:(.text+0x394): relocation truncated to fit: R_X86_64_PC32 against symbol `min_addr' defined in .bss section in /tmp/cc4D9tPQ.o
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:131:(.text+0x39f): relocation truncated to fit: R_X86_64_PC32 against symbol `max_addr' defined in .bss section in /tmp/cc4D9tPQ.o
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:132:(.text+0x3aa): relocation truncated to fit: R_X86_64_PC32 against symbol `pc_start' defined in .bss section in /tmp/cc4D9tPQ.o
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:133:(.text+0x3b5): relocation truncated to fit: R_X86_64_PC32 against symbol `pc_exit' defined in .bss section in /tmp/cc4D9tPQ.o
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:134:(.text+0x3c0): relocation truncated to fit: R_X86_64_PC32 against symbol `tohost_addr' defined in .bss section in /tmp/cc4D9tPQ.o
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:155:(.text+0x4c6): relocation truncated to fit: R_X86_64_PC32 against symbol `min_addr' defined in .bss section in /tmp/cc4D9tPQ.o
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:156:(.text+0x4d6): relocation truncated to fit: R_X86_64_PC32 against symbol `min_addr' defined in .bss section in /tmp/cc4D9tPQ.o
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:157:(.text+0x4f3): relocation truncated to fit: R_X86_64_PC32 against symbol `max_addr' defined in .bss section in /tmp/cc4D9tPQ.o
/home/jairom/Documents/TUD_Projects/05_Semester/Piccolo/Tests/elf_to_hex/elf_to_hex.c:158:(.text+0x515): additional relocation overflows omitted from the output
collect2: error: ld returned 1 exit status
make: *** [Makefile:7: elf_to_hex] Error 1

The problem can be solved adding the the flag -mcmodel=medium. According to what I have read is because this particular C file requires a large amount of memory in the stack that could not be fulfilled using a 32 bits AS operations. Is this a unique problem from my environment?
Thank you for your time,
Jairo M

@jrmejiaa Thank you for posting this. I see the same error on Ubuntu 22.04 (gcc 11.4.0). adding -mcmodel fixed it.
gcc -g -o elf_to_hex  elf_to_hex.c  -lelf --mcmodel=medium


SARAALERT-946: Add Risk Assessment and Monitoring Plan tooltips to last Enrollment wizard screen

Description
Jira Ticket: SARAALERT-946
Adds tooltips to Risk Assessment and Monitoring Plan fields within the Enrollment wizard to align with the monitoree's profile view.
Demo/Screenshots

Important Changes
app/javascript/components/enrollment/steps/PublicHealthManagement.js

Adds appropriate InfoTooltip to MONITORING PLAN and RISK ASSESSMENT fields.

Testing Recommendations

Confirm that tooltips are present in the Enrollment wizard within the PUBLIC HEALTH RISK ASSESSMENT AND MANAGEMENT SECTION.

Checklists
Submitter:

[x] This PR describes why these changes were made.
[x] This PR is into the correct branch.
[x] This PR includes the correct JIRA ticket reference.
[x] Comment added to the relevant JIRA ticket(s) with a link to this PR
[x] Code diff has been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
[ ] If UI changes have been made, Chrome Dev Tools Lighthouse accessibility test has been executed to ensure no 508 issues were introduced.
[ ] Tests are included and test edge cases
[x] Tests have been run locally and pass (remember to update Gemfile when applicable)
[ ] Test fixtures updated and documented as necessary

@sgober  :

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code
[ ] If applicable, you have tested changes against a large database, and considered possible performance regressions
[ ] Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

@timwongj  :

[x] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[x] You have tried to break the code
[ ] If applicable, you have tested changes against a large database, and considered possible performance regressions
[x] Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

@hackrm  :

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code
[ ] If applicable, you have tested changes against a large database, and considered possible performance regressions
[ ] Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

@sgober 6edf2679c6742edb107de2ae75a691fccb86eada
Let me know if this is what you had in mind!


Add an end-to-end test server.

BUG=191643395
DO NOT SUBMIT until we have resolved blocking bugs:

b/192584837 Extrenuous labels from go exporter
b/192584818 Span kind is not set in go exporter

@tbarker25 Looks like test failures are the e2e test server go.mod being out of date when running codecoverage.  Would you mind taking a look or bumping the dependencies?

@0xc0d would you mind leaving a comment with the text @googlebot I consent? This will let the bot track the fact that you are okay with your contribution as part of this PR.

@googlebot I consent

@googlebot I consent.


Add PEER_ADDRESS tag

Add peer.address tag according to OpenTracing Specification Semantic Conventions v1.1.

Coverage decreased (-0.2%) to 76.009% when pulling 6c2f6b6fb4a026b6067bd271f7844a10ce3a2dbe on qudongfang:Add-PERR_ADDRESS-Tag into d91d7072e141fa66265946b5164c249bf3045017 on opentracing:master.

@carlosalberto can you approve / merge?


Caret can disappear from script editor

Tested versions
4.3 beta1
System information
Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; <IP_ADDRESS>33) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)
Issue description
Might be related to #90569
https://github.com/godotengine/godot/assets/2223172/599a67a5-f82f-495c-be0c-4376a9fe1173
Seems to happen randomly. Also it's specific to the affected CodeEdit, as other scripts don't have the issue:
https://github.com/godotengine/godot/assets/2223172/da55b249-6b6e-438b-bf5b-5383995f4c69
Steps to reproduce

🤷♂
Caret is not visible

Minimal reproduction project (MRP)
N/A

If you disable caret blink in the editor (either in the editor settings or by hacking around the editor source), does this still occur?

Yes.

Same problem happens if text field in a standalone sub Window and in 4.3.dev6. But not happen in 4.3.beta1.
This is a MRP for this situation.
test_caret_blink_in_window.zip
Maybe it's not the same situation with KoBeWi's. But maybe related.

Got the same issue for a while (maybe from 4.3-dev5 release or a previous version), sometimes when renaming scene or script or even a directory, no caret at all. Pretty annoying.

Same problem happens if text field in a standalone sub Window and in 4.3.dev6. But not happen in 4.3.beta1.
This is a MRP for this situation.

This may be due to an intentional check in the code that hides the caret for unfocused windows (like many operating systems tend to do).

I think this might be related to #92634


Update inline call with keyword arguments

This fixes ruby-3 build

2.3 fails for an unrelated reason, rubocop is now 2.4+

I'll merge it but I won't cut a release


Create update-interactive.html

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Remember to delete this note before submitting your pull request.
For pull requests on 1.15 Features: set Milestone to 1.15 and Base Branch to dev-1.15
For pull requests on Chinese localization, set Base Branch to release-1.14
For pull requests on Korean Localization: set Base Branch to dev-1.14-ko.<latest team milestone>
If you need Help on editing and submitting pull requests, visit:
https://kubernetes.io/docs/contribute/start/#improve-existing-content.
If you need Help on choosing which branch to use, visit:
https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/assign @haibinxie
Please make the file get approval.

You forgot something

@zhangx501 please update the PR as per @xichengliudui 's inline comments.
/assign @chenrui333
for approval after the PR is ready to merge.

@chenrui333
Please give this PR appoval.

@zhangx501  预览：https://deploy-preview-15867--k8s-v1-14.netlify.com/zh/docs/tutorials/kubernetes-basics/update/update-interactive/
左侧菜单丢失了..

内容方面没啥问题，没有做文档检查。


Uplift code quality in metamist repo

This is the beginning of the code quality uplift in metamist. This PR addresses all of the security issues, hotspots and bugs.
A separate PR will be started to reduce the tech debt in the repo.

Is it possible to go back to a previous analysis so we can see the reports you're addressing?
(Or I guess we could cause it to analyse dev or main again…)

Is it possible to go back to a previous analysis so we can see the reports you're addressing?
(Or I guess we could cause it to analyse dev or main again…)

That's an excellent question! I'm looking into that to figure out the best configuration for "New Code". This should allow us to compare main (or, in the case of metamist, probably dev) to the newest code that is analysed in order to compare.


Try to rebuild for gitlab: error TS2403

Running with gitlab-runner 15.8.0 (12335144)
  on runner1 Nv4XYxct, system ID: r_A6woA5FUkvYB
Resolving secrets
00:00
Preparing the "docker" executor
00:03
Using Docker executor with image docker:[2](https://gitlab.lifepeak.de/lifepeak/fivem/skripts/fivem_lua_linter/-/jobs/721#L2)0-dind ...
Pulling docker image docker:20-dind ...
Using docker image sha256:70ae571e74c1d711d[3](https://gitlab.lifepeak.de/lifepeak/fivem/skripts/fivem_lua_linter/-/jobs/721#L3)d[5](https://gitlab.lifepeak.de/lifepeak/fivem/skripts/fivem_lua_linter/-/jobs/721#L5)bf[6](https://gitlab.lifepeak.de/lifepeak/fivem/skripts/fivem_lua_linter/-/jobs/721#L6)f4[7](https://gitlab.lifepeak.de/lifepeak/fivem/skripts/fivem_lua_linter/-/jobs/721#L7)eaaf6a51dd260fe0036c7d6[8](https://gitlab.lifepeak.de/lifepeak/fivem/skripts/fivem_lua_linter/-/jobs/721#L8)94c008e7d24297 for docker:20-dind with digest docker@sha256:85a1b877d0f59fd6c7eebaff67436e26f460347a79229cf054dbbe8d5ae9f936 ...
Preparing environment
00:01
Running on runner-nv4xyxct-project-5-concurrent-0 via eb67cc2c6b5b...
Getting source from Git repository
00:01
Fetching changes with git depth set to 20...
Reinitialized existing Git repository in /builds/lifepeak/fivem/skripts/fivem_lua_linter/.git/
Checking out 1465411c as main...
Removing node_modules/
Removing yarn.lock
Skipping Git submodules setup
Executing "step_script" stage of the job script
00:09
Using docker image sha256:70ae571e74c1d711d3d5bf6f47eaaf6a51dd260fe0036c7d6894c008e7d24297 for docker:20-dind with digest docker@sha256:85a1b877d0f59fd6c7eebaff67436e26f460347a79229cf054dbbe8d5ae9f936 ...
$ apk add nodejs yarn && yarn
fetch https://dl-cdn.alpinelinux.org/alpine/v3.17/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.17/community/x86_64/APKINDEX.tar.gz
(1/9) Installing brotli-libs (1.0.9-r9)
(2/9) Installing c-ares (1.18.1-r1)
(3/9) Installing libgcc (12.2.1_git20220924-r4)
(4/9) Installing icu-data-en (72.1-r1)
Executing icu-data-en-72.1-r1.post-install
*
* If you need ICU with non-English locales and legacy charset support, install
* package icu-data-full.
*
(5/9) Installing libstdc++ (12.2.1_git20220924-r4)
(6/9) Installing icu-libs (72.1-r1)
(7/9) Installing nghttp2-libs (1.51.0-r0)
(8/9) Installing nodejs (18.12.1-r0)
(9/9) Installing yarn (1.22.19-r0)
Executing busybox-1.35.0-r29.trigger
OK: 82 MiB in 65 packages
yarn install v1.22.19
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
$ tsc -b
node_modules/@types/node/globals.d.ts(347,13): error TS2403: Subsequent variable declarations must have the same type.  Variable 'AbortSignal' must be of type '{ new (): AbortSignal; prototype: AbortSignal; abort(reason?: any): AbortSignal; timeout(milliseconds: number): AbortSignal; }', but here has type '{ new (): AbortSignal; prototype: AbortSignal; }'.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error Command failed with exit code 1.
Cleaning up project directory and file based variables
00:01
ERROR: Job failed: exit code 1

Can you help wie with the error ?
I try to rebuild your project for gitlab.
If you need further logs just ask.
node_modules/@types/node/globals.d.ts(347,13): error TS2403: Subsequent variable declarations must have the same type.  Variable 'AbortSignal' must be of type '{ new (): AbortSignal; prototype: AbortSignal; abort(reason?: any): AbortSignal; timeout(milliseconds: number): AbortSignal; }', but here has type '{ new (): AbortSignal; prototype: AbortSignal; }'.

It works quit well 4 Month ago.


PIB, RAM, and ATB alignment synchronization

PIB, RAM, and ATB have a control field defined to enable generation of alignment synchronization packets. However, these components do not have a trace format (E-trace or N-trace) configuration. As the alignment synchronization sequence is protocol specific, should there should be equivalent of trTeFormat control provided for these components.

Closing with the following comment:
NOT DONE: It was not a intention to mix and match different trace protocols, but provide control spec to be identical/re-used by both - at least not now. Such things can be added as future revision/addition (if needed). ARC was against specifying future things, so why do it here. As interfaces between trace components are not defined (by this spec …), nothing prevents ‘trTeFormat’ to be passed from encoder to funnel and sinks.

What is the motivation for making trTeFormat as WARL and not RO?


Hide esling output in browser but show in terminsal

Is your feature request related to a problem? Please describe.
Hello. I often use console.log. It is forbidden in my eslint config. I dot't know how to work with it properly. I don't want to see warning messages about my console.log in browser.
Describe the solution you'd like
I guess an option to hide output of some checkers in browser would be enough.
Describe alternatives you've considered
If you have better solution please describe it.
Thanks.
Additional context
No response
Validations

[X] Read the docs.
[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.

To disable your eslint rule temporarily, just add // eslint-disable-line. If you want, you can add a TODO comment as a reminder.

This is what I do now and what I would like to change.

@timsofteng you can do
 plugins: [
...
   checker({
      typescript: true,
      overlay: false,
   }),
...
]


Nonsensical version tracking and listing

Brief description of your issue
On the below screenshot you can see Winget suggesting 4 updates for packages that are all on the latest version:

Firefox Developer edition:
The version actually installed is 119.0 Beta 5, the latest available for that release channel, but Winget detects a non-beta release of 119.0 (which will never exist since developer edition only gets beta channel builds) and suggests me "upgrade" to the previous beta.
This is problematic for 2 reasons:

Winget should be aware of which packages list the beta build on their version info or not, and avoid recommending beta build updates to those who do not.
According to semantic versioning 119.0 is a more updated release than 119.0b4, so even if I was theoretically running 119.0 release, it would be newer than beta 4 and therefore Winget is suggesting me a downgrade.

Microsoft Windows Desktop Runtime - 3.1.32
Winget is suggesting me to replace the 3.x desktop runtime with a completely incompatible version of the .NET desktop runtime (which for the record I have installed as well).
This is a serious issue as it would cause an update loop, as the 3.1.32 runtime is not overwritten by the 6.0.22 one and therefore will still show an update available after the install of the "updated" package.
Epic Games Launcher
This program is on the latest version according to the launcher's internal updater (15.15.0-2846563), neither the version Winget claims the program currently is or the one Winget claims is the latest can be found anywhere in the program, including the executable's version details.
Ideally Winget would not touch programs like these that include their own installers, but unfortunately the closest we have to a package ignore list is pinning, which breaks the program's internal updaters.
Python 3.12.0
Perhaps the most puzzling of them all, Winget detects my Python 3.12 install as an unknown version Python 3.11 install and is trying to get me to update to the version it currently is at. This is an issue for 2 reasons:

Why is it detecting Python 3.12.0 as a version of Python 3.11 when they are different packages on Winget?
If it thinks it's Python 3.11.x why is trying to upgrade to Python 3.12, a non-directly compatible release?

All of these are recurring issues that manifest themselves frequently and cause me to have to avoid the convenient winget upgrade --all command.
Steps to reproduce
Install the aforementioned packages and run winget upgrade
Expected behavior
Only packages with newer versions available would show updates.
Actual behavior
Inexistent updates show as available.
Environment
Windows Package Manager v1.6.2771
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.2361
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.2771.0

Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

Some of this is related to:

#2995

Python is split out in the repository as separate packages, but the matching logic still detects the newer versions due to the metadata written by the installer. One possible workaround for this package is to pin it to the version or "range" of versions you want.
When you see a ">" or a "<" in a version, it's an indication that the manifest is using a "marketing version" (packageVersion) rather than what the installer actually writes to the registry (Apps & Features displayVersion). Often the reason is due to the installed "displayVersion" not having a corresponding manifest in the community repository.

Looking to Python.Python to see if there is 0 file..

Yes, 0 file was existed

Action before Id column which is Upgrade Code.
Id15 could be the ProductCode for the setup.


[Volunteer] Support Admin Internationalization

#4613

Codecov Report

Merging #4640 (a70b1e1) into master (a032239) will decrease coverage by 0.06%.
The diff coverage is 85.83%.

@@             Coverage Diff              @@
##             master    #4640      +/-   ##
============================================
- Coverage     67.35%   67.29%   -0.06%
+ Complexity     8001     7998       -3
============================================
  Files          1097     1099       +2
  Lines         31571    31641      +70
  Branches       2861     2860       -1
============================================
+ Hits          21264    21294      +30
- Misses         8633     8664      +31
- Partials       1674     1683       +9

Impacted Files
Coverage Δ

...ache/shenyu/admin/controller/DetailController.java
37.50% <0.00%> (ø)

...pache/shenyu/admin/controller/FieldController.java
37.50% <0.00%> (ø)

...enyu/admin/controller/ProxySelectorController.java
30.00% <0.00%> (ø)

...tener/http/HttpLongPollingDataChangedListener.java
5.88% <0.00%> (ø)

...pache/shenyu/admin/model/dto/DashboardUserDTO.java
75.92% <ø> (ø)

...dmin/model/dto/DashboardUserModifyPasswordDTO.java
0.00% <ø> (ø)

...u/admin/service/impl/DashboardUserServiceImpl.java
70.86% <0.00%> (ø)

...shenyu/admin/service/impl/ResourceServiceImpl.java
69.64% <0.00%> (ø)

.../apache/shenyu/common/constant/AdminConstants.java
0.00% <ø> (ø)

...ache/shenyu/admin/service/impl/ApiServiceImpl.java
24.44% <50.00%> (ø)

... and 31 more

... and 22 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

hi It's not a good realization.
We should use spring's internationalization.
see
https://docs.spring.io/spring-framework/docs/5.1.3.RELEASE/spring-framework-reference/core.html#spring-core
Generally, in the web scenario, the locale context is obtained through the LocaleContextHolder.

messageSource.getMessage("test.message",   LocaleContextHolder.getLocale())

see :AcceptHeaderLocaleResolver

it's ok . i will closed this pr. and think about spring's internationalization.


typo in the wiki article : "How to constantly up-skill yourself as a developer"

What Happened?
In the article, "How to constantly up-skill yourself as a developer" paragraph : Write about what you learn. In Point 1 : it should be 'then' instead of 'than'.

What Browsers Are You Seeing the Problem On?
No response
Relevant Log Output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I would love to fix this :)

@gururani-abhishek Open a PR linking it to this issue?


prepare artifact error

Harbor deployed with http mode.
version: v2.0.1
$ HARBOR_SIZE=small HARBOR_URL=http://admin:Harbor12345@<IP_ADDRESS>:31114 go run mage.go prepare

INFO[0008] GoError: failed to push <IP_ADDRESS>:31114/project-1619059710385-013/repository-001:v01, error: failed to do request: Head "https://<IP_ADDRESS>:31114/v2/cpaas-system/repository-001/blobs/sha256:4a969632bc3938f5b516bb39eb3a9d098b698179bfde42a512b499786cb4246f": http: server gave HTTP response to HTTPS client  source=console
INFO[0008] GoError: failed to push <IP_ADDRESS>:31114/project-1619059710385-013/repository-001:v02, error: failed to do request: Head "https://<IP_ADDRESS>:31114/v2/cpaas-system/repository-001/blobs/sha256:b4edb9e6688f4f5efe5a186240b73287c9435bd529b6ab39b509f02e7482ba05": http: server gave HTTP response to HTTPS client  source=console
INFO[0008] GoError: failed to push <IP_ADDRESS>:31114/project-1619059710385-013/repository-001:v03, error: failed to do request: Head "https://<IP_ADDRESS>:31114/v2/cpaas-system/repository-001/blobs/sha256:9cc3a79d2828d644a90300491d6b7df84fd33bf951e8636505522f82a32ac453": http: server gave HTTP response to HTTPS client  source=console

Closed by https://github.com/heww/xk6-harbor/commit/763e178b450f873e077c56cdd1d1b73f33fbaead
Please use  K6_ALWAYS_UPDATE=true HARBOR_SIZE=small HARBOR_URL=http://admin:Harbor12345@<IP_ADDRESS>:31114 go run mage.go prepare to fetch the latest k6 and reprepare the user data.


How to Use Skypefx Effects library.

Please I want to use the Skypefx library written by you to process wav files and play.
How do I do it.

well the demo windows application shows it being used to play and process audio files, so you can try it out. It's quite an old project. These days I'd implement the effects as ISampleProvider instances, and then chain them together passing my input file through and into a sound device.

Please do u know Unity3D
On May 5, 2016 7:49 PM, "Mark Heath"<EMAIL_ADDRESS>wrote:

well the demo windows application shows it being used to play and process
audio files, so you can try it out. It's quite an old project. These days
I'd implement the effects as ISampleProvider instances, and then chain them
together passing my input file through and into a sound device.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/naudio/NAudio/issues/89#issuecomment-217257565

sorry I'm afraid I've never used Unity3D


fix class name

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


[pylint] ignoring pylint error - github issue for it on pylint repo

This PR is for an issue with Pylint that raises an EO611 No name k in module x. Occurred while running pipeline on #25344 that lazy loads certain imports using PEP 562.

/check-enforcer override


Change the HAL API to snake_case() from camelCase()

This is to follow the STM32 HAL implementations in stmicro-stm32, which were converted to snake_case() when they were extracted from the main microzig repository into their own separate repository.

Thank you!


Data Race between Serve() and Shutdown()

Problem statement
Between the functions Serve() and  Shutdown() is a data race on the variable servers. This occurs because the goroutine that starts the server writes into servers on this line. Before it starts a goroutine to handle shutdowns here. In the handleShutdown() method servers is accessed again which causes a data race:
==================
WARNING: DATA RACE
Read at 0x00c0000ac180 by goroutine 27:
  goswagger-race/restapi.(*Server).handleShutdown()
      .../goswagger-race/restapi/server.go:418 +0xba

Previous write at 0x00c0000ac180 by main goroutine:
  goswagger-race/restapi.(*Server).Serve()
      .../goswagger-race/restapi/server.go:220 +0x1b5a
  main.main()
      .../goswagger-race/cmd/example-server/main.go:60 +0x64a

Goroutine 27 (running) created at:
  goswagger-race/restapi.(*Server).Serve()
      .../goswagger-race/restapi/server.go:178 +0x26e
  main.main()
      .../goswagger-race/cmd/example-server/main.go:60 +0x64a
==================
==================
WARNING: DATA RACE
Read at 0x00c0004ce010 by goroutine 27:
  goswagger-race/restapi.(*Server).handleShutdown()
      .../goswagger-race/restapi/server.go:425 +0x1a6

Previous write at 0x00c0004ce010 by main goroutine:
  goswagger-race/restapi.(*Server).Serve()
      .../goswagger-race/restapi/server.go:220 +0x1b20
  main.main()
      .../goswagger-race/cmd/example-server/main.go:60 +0x64a

Goroutine 27 (running) created at:
  goswagger-race/restapi.(*Server).Serve()
      .../goswagger-race/restapi/server.go:178 +0x26e
  main.main()
      .../goswagger-race/cmd/example-server/main.go:60 +0x64a
==================

Swagger specification
https://github.com/amuttsch/goswagger-race/blob/master/swagger.yaml
Steps to reproduce
To reproduce clone my repo https://github.com/amuttsch/goswagger-race , run go run -race cmd/example-server/main.go and wait a few seconds.
Environment
swagger version: 0.19.0
go version: 1.12
OS: Linux
Related to #1781

This was quite an easy fix, I moved the goroutine creation for the shutdown at the end of the method.

I'd like to add a testcase for this, can someone guide me how to write a test that generates a server, provides a main.go and runs go test?

this one, does something similar: https://github.com/go-swagger/go-swagger/blob/master/generator/build_test.go

Thanks, I'll have a look

I'm at the point where I can run go run test -race for my test fixture. But the output of the GenerateServer function in the generator package differs from the swagger generate command, e.g. swaggerSpec, err := loads.Embedded(restapi.SwaggerJSON, restapi.FlatSwaggerJSON) is missing from the generated main file.
			opts := testGenOpts()

			opts.Target = filepath.Dir(spec)
			_ = os.Mkdir(opts.Target, 0755)
			opts.Spec = spec
			opts.IncludeMain = true

			fmt.Println(opts.Target)

			err := GenerateServer("", nil, nil, &opts)

See https://github.com/amuttsch/go-swagger/blob/testing/generator/test_test.go and https://github.com/amuttsch/go-swagger/blob/testing/fixtures/bugs/1943/datarace_test.go

I think I found the missing flag: opts.ExcludeSpec = false


Lint or Diff error, i don't know but cannot get ride of it.

Issue
I can't get ride of diff showing in the code. it's always there whatever i do.
aider: latest
model: all model
Git repo: none

Version and model info
No response

Thank you for filing this issue.
In doubt you can disable the internal linter with adding the additional command line argument --no-auto-lint to aider when starting.
-> https://aider.chat/docs/config/options.html#--auto-lint


Speed up repo cloning for the catalog command

Description
Fixed the temporary folder path and repository URL that is sent to go-getter.
Fixes #2831.

LGTM!

Thanks for the review!


cmake: linker: remove unused symbols __tls_start,end,size

The linker variables __tls_start, __tls_end and __tls_size are not used in the zephyr project, so remove them for now.

@keith-packard can you take a look?


Add more redo metrics

Measure size of redo WAL (new histogram), with bounds between 24B-32kB
Add 2 more buckets at the upper end of the redo time histogram We often (>0.1% of staging's REDO operations replayed of several hours each day) take more than 250ms to do the redo round-trip to the postgres process. We need to measure these redo times more precisely.

We often (>0.1% of staging's REDO operations replayed of several hours each day) take more than 250ms to do the redo round-trip to the postgres process

Ouch! Would love to know what's happening there.


Fix exception for bad unit number

Instead of raising an error, simply print a warning and skip the out of bounds number

After digging through School Idol Tomodachi API, I think I have a better solution to solve this. SIT API has game_id field when querying card info, which directly translates to unit_id in the in-game database.


Strange event bug

I discovered strange bug which may be either related CycleJS or some tricky case in my own code.
Or even be a bug in virtual DOM. I don't know yet.
In example with multiple sliders (e.g. this https://github.com/ivan-kleshnin/cyclejs-examples/tree/master/src/3.4-slider-colors) sliders not always react on deletion.
Slider sends remove event but global Intent does not get it.
Video proof: https://docs.google.com/file/d/0B9bW0B92XgnASmNTbzZWM216cWM/edit
The strangest thing about it is that this behavior looks undeterministic. That's why I say there is a chance about some desync between virtual DOM nodes. Sometimes it works and sometimes not. The only fact I found by trial is that first render works ok. Removals before first addition worked in 100% cases.

At first thought I was about to suggest you need to add the key to every Slider, but you are already doing that. I need to debug this. I think I have time today to take a look.

I can reproduce the bug and I can confirm it's a real bug in Cycle. I'm working on it.

Good news: I found a proper fix for the bug.
Not so good news: I'm going to take more time to make proper automated tests for these stuff, and won't release the bug fix before I have these tests, so you will have to wait a bit until the tests + bug fixes are ready.

If you're curious, this is the fix: https://github.com/staltz/cycle/commit/b2d1b704df383f36c4a9c3d5043913a8bcb04555

so you will have to wait a bit until the tests + bug fixes are ready

That's ok. I'm happy I've not tried to debug this: very involved stuff :smile:

Sadly, this fix branch does not include no /lib nor /src so this is again incompatible with browserify.

@ivan-kleshnin can you test with v0.16.3 ?

@staltz, sure

@staltz I checked 0.17.0 against my examples.
Everything looks fine, #87 and #89 are gone :thumbsup:

Good :)


mv k8sassist interfaces - [closed]

In GitLab by @luotian-github on May 17, 2018, 02:40
Merges updatek8s18 -> updatek8s18
mv k8sassist interfaces

In GitLab by @wknet123 on Nov 13, 2019, 10:55
closed


Small fixes on sensor naming popup

Capital first letter should be offered automatically.
Popup goes behind the keypad.
There is too much padding on input field (too much space between the name and line)

Capital first letter should be offered automatically.
Easy fix. Will be included to 1.15

Popup goes behind the keypad.
There is too much padding on input field (too much space between the name and line)

Will try to implement with 1.16 milestone. This will require migration to freshier version of Compose (and Kotlin version as well).

Let's include this in 2.1

QA passed


Move kube-vip manifest modification step to pre-kubeadm commands for Nutanix

Because this command was being placed in postKubeadmCommands section of the preKubeadmCommands, the control plane nodes were unable to get properly initialized since the kube-vip pod wouldn't have the necessary permissions to acquire the lease it needs to for managing the VIP.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/override eks-anywhere-e2e-presubmit
Irrelevant but stuck in retesting churn


Pass _use_quadrants to get_image_quadrants (fixes #284)

Hello @leon-vv! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file abel/transform.py:

Line 104:80: E501 line too long (86 > 79 characters)
Line 105:80: E501 line too long (89 > 79 characters)

Looks good to me!


Support for OSX

Is there a future release planned with OSX Support?

Hi @nofelmahmood! No plans for macOS yet, but let's hold it for the upcoming WWDC - quite possible that the next OS releases will make it much easier to do cross-platform development.


Raycast extension for Nodepad

Is your feature request related to a problem? Please describe.
It's not related to a problem. However, it'd be great if I could create Nodepad links via a Raycast extension.
Describe the solution you'd like
A Raycast extension called "Notepad" sends an API request to the Notepad API, providing the code selected with the cursor. If the user subscribes to Raycast Pro, the extension can automatically generate a markdown description for it. Perhaps two commands can be implemented: one with AI steps and one without.
Describe alternatives you've considered
Not having the Raycast extension :/
Additional context
No additional context.

I'm currently focusing on it! It should be available soon


Rerendering row causes list to jump / snap unexpectedly

I have a list of Events that users can star. However, whenever I star that event (and therefore add the event ID to starredIds), the list snaps to the row nearest to the top. Is there a way to prevent this? It feels like bad UX.
class MyList extends Component {
  render() {
    const { events, starredIds, starFn, unstarFn } = this.props;
    let { width } = Dimensions.get("window");

    let eventsAndStars = events.map(event => {
      return { ...event, starred: _.includes(starredIds, event.id) };
    });

    let dataProvider = new DataProvider((r1, r2) => {
      return r1 !== r2;
    });

    return h(RecyclerListView, {
      dataProvider: dataProvider.cloneWithRows(eventsAndStars),
      ref: "list",
      oncontentsizechange: () => {
        try {
          this.refs.list.scrolltoindex(0);
        } catch (e) {
          console.log("scrolling to top went wrong: ", e);
        }
      },
      style: styles.container,
      layoutProvider: new LayoutProvider(
        index => 0,
        (type, dim) => {
          dim.width = width;
          dim.height = 90;
        }
      ),
      showsVerticalScrollIndicator: false,
      rowRenderer: (type, event) => {
        const {
          id,
          name,
          description,
        } = event;
        const starred = _.includes(starredIds, event.id);
        const now = new Date();
        return h(MyRow, {
          id,
          name,
          description,
        });
      }
    });
  }
}

Do not recreate layout provider on every render. Layout provider is not supposed to change. Changing layout provider invokes anchoring mechanism. Ideally, layout provider should change only if you are switching a listview to gridview or totally changing layouts for your list where you would want the first visible item to be preserved. That's what is happening here. Even data provider shouldn't be recreated everytime, only when data changes.

Great thanks!

@naqvitalha If we can't update layout provider, then how do you account for content that changes in height then?


Github Pages deployment showing 404

Describe the bug
When i tried to see the github pages website through the environments section, it is showing me 404 file not found error.
To Reproduce
OS: MacOS
Browser: Chrome
Go to the environment section and open the github pages link.

@thesmartdeveloperr
Thanks for reporting the bug.
The actual URL is 가 아닌 이다.
The actual URL is https://nhn.github.io/tui.image-editor/latest/, not http://nnn.github.io/tui.image-editor/.
I think latest/ is missing. I'll check it out.


Jarad cdx

My apologies that this seems to have occurred in the wrong base repository.  Is it still possible to do the merge for these new articles?  They can be published at any time (This has been long pending new documentation).

Moved to private repo for review.


When wrongly configuring s3-integrator Postgresql charm will get stuck in error state and needs to be redeployed

Steps to reproduce
Deploy postgresql charm
Follow backup and restore tutorial
I forgot to set up tls-ca-chain config that was required in this case
And now postgresql charm gets stuck in error state not being able to get out of it wihout hacking inside charm hooks or redeploying it
Expected behavior
Not to get stuck in error state if the user makes a configuration mistake but to get into blocked state
Actual behavior
# juju status
[..]
postgresql/0                 active    idle   0        <IP_ADDRESS>  5432/tcp
postgresql/1*                error     idle   1        <IP_ADDRESS>  5432/tcp  hook failed: "s3-parameters-relation-changed"
postgresql/2                 active    idle   2        <IP_ADDRESS>  5432/tcp

You can NOT get out of this state even

By re-running the hook
By updating the config
By updating the config and re-running the hook
By removing the relation
By removing the relation and re-running the hook

Versions
Operating system: Ubuntu 22.04
Juju: 3.5.4
Charm revision: 14/stable rev468
Log output
Did not collect it at the moment
Additional context
You could hackily get out of this situation wihout redeploying by skipping the hook and then removing the relation

On a terminal "A"

juju debug-hooks postgresql/1
# Now you are on a tmux session waiting for a hook to get triggered

On a terminal "B"

juju resolved postgresql/1
# Trigget the hook to re-run

On terminal "A"

# tmux session is waiting for you to manually execute the reaction to the s3-parameters-relation-changed hook
exit 0
# to make juju belive the hook was run okay
exit
# to exit the juju-debug session

Now the hook has been skipped and you can remove the relation
Update the config
And re-add the relation with the proper configuration

Any updates on this? We're seeing it here too:
is-managed-database-prod-marketing-airbyte-marketo@is-bastion-ps6:~$ jsft
Model                                               Controller                         Cloud/Region           Version  SLA          Timestamp
is-managed-database-prod-marketing-airbyte-marketo  juju-controller-35-production-ps6  prodstack6/prodstack6  3.5.3    unsupported  21:18:19Z

App                    Version  Status  Scale  Charm                      Channel        Rev  Exposed  Message
backups-s3-integrator           active      1  s3-integrator              latest/stable   32  no
data-integrator                 active      1  data-integrator            latest/stable   41  no
landscape-client                active      6  landscape-client           latest/stable   69  no       Client registered!
postgresql             14.12    active      3  postgresql                 14/stable      468  yes
telegraf                        active      6  telegraf                   latest/stable   75  yes      Monitoring tls-certificates/0 (source version/commit 23.10)
tls-certificates                active      1  tls-certificates-operator  latest/stable   22  no
ubuntu-advantage                active      6  ubuntu-advantage           latest/stable   95  no       Attached (esm-apps,esm-infra,livepatch)

Unit                      Workload  Agent  Machine  Public address  Ports     Message
backups-s3-integrator/0*  active    idle   0        <IP_ADDRESS>
  landscape-client/2      active    idle            <IP_ADDRESS>              Client registered!
  telegraf/2              active    idle            <IP_ADDRESS>    9103/tcp  Monitoring backups-s3-integrator/0 (source version/commit 23.10)
  ubuntu-advantage/2      active    idle            <IP_ADDRESS>              Attached (esm-apps,esm-infra,livepatch)
data-integrator/1*        active    idle   2        <IP_ADDRESS>
  landscape-client/1      active    idle            <IP_ADDRESS>              Client registered!
  telegraf/1              active    idle            <IP_ADDRESS>    9103/tcp  Monitoring data-integrator/1 (source version/commit 23.10)
  ubuntu-advantage/1      active    idle            <IP_ADDRESS>              Attached (esm-apps,esm-infra,livepatch)
postgresql/0*             error     idle   3        <IP_ADDRESS>    5432/tcp  hook failed: "s3-parameters-relation-changed"
  landscape-client/3      active    idle            <IP_ADDRESS>              Client registered!
  telegraf/3              active    idle            <IP_ADDRESS>    9103/tcp  Monitoring postgresql/0 (source version/commit 23.10)
  ubuntu-advantage/3      active    idle            <IP_ADDRESS>              Attached (esm-apps,esm-infra,livepatch)
postgresql/1              waiting   idle   4        <IP_ADDRESS>    5432/tcp  Awaiting restart operation
  landscape-client/5      active    idle            <IP_ADDRESS>              Client registered!
  telegraf/5              active    idle            <IP_ADDRESS>    9103/tcp  Monitoring postgresql/1 (source version/commit 23.10)
  ubuntu-advantage/5      active    idle            <IP_ADDRESS>              Attached (esm-apps,esm-infra,livepatch)
postgresql/2              waiting   idle   5        <IP_ADDRESS>    5432/tcp  awaiting for cluster to start
  landscape-client/4      active    idle            <IP_ADDRESS>              Client registered!
  telegraf/4              active    idle            <IP_ADDRESS>    9103/tcp  Monitoring postgresql/2 (source version/commit 23.10)
  ubuntu-advantage/4      active    idle            <IP_ADDRESS>              Attached (esm-apps,esm-infra,livepatch)
tls-certificates/0*       active    idle   1        <IP_ADDRESS>
  landscape-client/0*     active    idle            <IP_ADDRESS>              Client registered!
  telegraf/0*             active    idle            <IP_ADDRESS>    9103/tcp  Monitoring tls-certificates/0 (source version/commit 23.10)
  ubuntu-advantage/0*     active    idle            <IP_ADDRESS>              Attached (esm-apps,esm-infra,livepatch)

With the hook failure logs:
unit-postgresql-0: 21:12:06 DEBUG unit.postgresql/0.juju-log s3-parameters:19: Endpoint provider result: https://radosgw.ps6.canonical.com/is-managed-database-prod-marketing-airbyte-marketo-backup
unit-postgresql-0: 21:12:06 DEBUG unit.postgresql/0.juju-log s3-parameters:19: Selecting from endpoint provider's list of auth schemes: "sigv4". User selected auth scheme is: "None"
unit-postgresql-0: 21:12:06 DEBUG unit.postgresql/0.juju-log s3-parameters:19: Selected auth type "v4" as "v4" with signing context params: {'region': 'us-east-1', 'signing_name': 's3', 'disableDoubleEncoding': True}
unit-postgresql-0: 21:12:06 ERROR unit.postgresql/0.juju-log s3-parameters:19: Uncaught exception while in charm code:
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-postgresql-0/charm/./src/charm.py", line 1866, in <module>
    main(PostgresqlOperatorCharm)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 553, in main
    manager.run()
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 529, in run
    self._emit()
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 518, in _emit
    _emit_charm_event(self.charm, self.dispatcher.event_name, self._juju_context)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/main.py", line 139, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 347, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 853, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 943, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/lib/charms/data_platform_libs/v0/s3.py", line 768, in _on_relation_changed
    getattr(self.on, "credentials_changed").emit(
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 347, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 853, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/ops/framework.py", line 943, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/lib/charms/tempo_k8s/v1/charm_tracing.py", line 735, in wrapped_function
    return callable(*args, **kwargs)  # type: ignore
  File "/var/lib/juju/agents/unit-postgresql-0/charm/src/backups.py", line 657, in _on_s3_credential_changed
    self._create_bucket_if_not_exists()
  File "/var/lib/juju/agents/unit-postgresql-0/charm/lib/charms/tempo_k8s/v1/charm_tracing.py", line 735, in wrapped_function
    return callable(*args, **kwargs)  # type: ignore
  File "/var/lib/juju/agents/unit-postgresql-0/charm/src/backups.py", line 294, in _create_bucket_if_not_exists
    bucket.create(CreateBucketConfiguration={"LocationConstraint": region})
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/boto3/resources/factory.py", line 581, in do_action
    response = action(self, *args, **kwargs)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/boto3/resources/action.py", line 88, in __call__
    response = getattr(parent.meta.client, operation_name)(*args, **params)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/botocore/client.py", line 569, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/botocore/client.py", line 980, in _make_api_call
    request_dict = self._convert_to_request_dict(
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/botocore/client.py", line 1047, in _convert_to_request_dict
    request_dict = self._serializer.serialize_to_request(
  File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/botocore/validate.py", line 381, in serialize_to_request
    raise ParamValidationError(report=report.generate_report())
botocore.exceptions.ParamValidationError: Parameter validation failed:
Invalid type for parameter CreateBucketConfiguration.LocationConstraint, value: None, type: <class 'NoneType'>, valid types: <class 'str'>
unit-postgresql-0: 21:12:06 ERROR juju.worker.uniter.operation hook "s3-parameters-relation-changed" (via hook dispatching script: dispatch) failed: exit status 1

Turns out, my issue is due to not set region. I've set it but then ran into https://github.com/canonical/postgresql-operator/issues/689
It would be nice if the charm could handle this better and allow to change or set the region rather than the workaround of removing the relation, resolve --no-retry, then re-adding the relation.

Hey @hloeung ! Thank your for opening a bug report!
There is a possible fix under review at #701


Move to MAX-Framework

Move this model to MAX-Framework.

Other than my comment about versioning both the framework and any model update to use it, this LGTM (from a code side, I didn't test the model)


Feat: Context Menu

• Added context menu
can trigger by right clicking an area of the children area.
• Uses same structure as the Dropdown component

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Screen zoom randomly broke

Describe your problem here.
ooookay so I have been having a lot of trouble with Psych Engine and had to put a lot of these things; so this time, I started using the "Add Camera Zoom" event, which the first few days it mimicked how at the start of every section, it does that quick zoom then zooms back out. I thought this was cool, but I tried using it again today and for some reason now it doesn't do that quick in and out motion, but instead only zooms in and stays like that. It even says in the description that it does it in MILF, so I looked in MILF and lo and behold it does what it's supposed to, why has it randomly stopped working??
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

Putting "setProperty('camZooming', true)" in the on create function fixed it for me.
I'm not sure what turns it off, but you can force it back on.

Putting "setProperty('camZooming', true)" in an on create function fixed it for me.
I'm not sure what turns it off, but you can force it back on.
(In a Lua file)

you do the same thing but change true to false

Putting "setProperty('camZooming', true)" in an on create function fixed it for me.
I'm not sure what turns it off, but you can force it back on.
(In a Lua file)

you do the same thing but change true to false

I know changing it to false will turn it off pffft but what I'm talking about is I don't know what in the source code makes it turn off for specific songs. The only thing I see in Playstate is that it gets set off after the song ends, (and when the variable is created I think) and doesn't get turned back on until the opponent hits their first note. (For some reason???) (And unless you're playing the tutorial)
So I think the idea is that the camera isn't supposed to bump until the singing starts (which would normally start with the opponent singing) and it in the process makes the camera zoom event not bump but rather stay zoomed in.


Issue with k8s.io/zh/docs/tutorials/kubernetes-basics/expose/expose-intro/

This is a Bug Report
Problem:
not a Chinese version(It should be)
Proposed Solution:
translation
Page to Update:
https://kubernetes.io/zh/docs/tutorials/kubernetes-basics/expose/expose-intro/

/language zh

/assign

@TomorJM Still working on this?

@TomorJM Still working on this?

yeah, and sorry for the delay
i will commit a PR this week

/close
done.


carthage update --platform iOS fails

Following the instructions

From Terminal, change directories into the YourProjectName/CognitiveConcierge-iOS folder and run the following command to install the necessary dependencies (This may take some time):

this error is raised:
$ carthage update --platform iOS
*** Cloning swift-sdk
*** Cloning Starscream
*** Checking out Starscream at "3.0.5"
*** Checking out swift-sdk at "v0.29.0"
*** xcodebuild output can be found in /var/folders/cs/560yb9sn0xv9h_gw47z5l1140000gn/T/carthage-xcodebuild.W7WOKH.log
*** Downloading swift-sdk.framework binary at "v0.29.0"
*** Skipped building Starscream due to the error:
Dependency "Starscream" has no shared framework schemes for any of the platforms: iOS

If you believe this to be an error, please file an issue with the maintainers at https://github.com/daltoniam/Starscream/issues/new

@ptitzler are you running the latest version of carthage and xcode?
We just got the travis job running successfully after much neglect, and we've tested things out locally and they are working. Please re-open if you're still seeing an error.

Carthage was at version 0.30.1. After I upgraded XCode to 9.4.1 the problem went away!


I want to use it only in Python

When I use AutoFormat, it always formats code snippets in my markdown.

What format program are you trying to use, and can you provide debug info as listed in the README.md?

Closing until further info provided


[Service Bus]: registerMessageHandler is not deterministic

Is your feature request related to a problem? Please describe.
The call to registerMessageHandler accept's an onError callback which throws an Error for any connection related issue or MessageError for any issue thrown while handling an incoming message.
This creates a problem when trying to determine the result of the connect operation.

If Fail: onError is invoked with the error
If Success: Nothing

If the flow requires several operations, running in sequence with one being registerMessageHandler and the other, running after a successful connection, this is not easy to achive.
One can use the onError callback to catch such issues but if no error occurs?
Describe the solution you'd like
registerMessageHandler should return a promise that will resolve when connection is up and it's ready to receive message.
The promise will throw if it fails, i.e. if the receiver is already in state of receiving messages or if there was a problem connecting to service bus.
The onError will be used for MessageError and for connection errors that occur AFTER the initial connection resolves.
In addition, the flow is will now be more clear, as registerMessageHandler.
I guess there is an API problem here, as this is a breaking change... but I think this one is required.

@shlomiassaf - one change we've been talking about (to solve a slightly different but related issue) is to provide a way for the user to do a "init connection" without having to do a send/receive operation. So this would occur via an explicit call (where that method exists is under discussion).
Would something like that also work for your needs?

@richardpark-msft yes.
It will now be a 2 step operation?
What happens if there is no connection when registering?
What happens on disconnect?
Thabks

@shlomiassaf - basically we'd give the user a choice of when the initialization happens - either explicitly (new functionality we could add) or implicitly (what we do today).
So no change to normal user's workflow but, for people that want more control, you'd have a way of triggering the connection initialization at an explicit time rather than just on first send/receive.
(As I said, just an idea we're kicking around. Any feedback is welcome!)

Another option we are considering is to make the createReceiver() method return a promise. Whether the promise gets resolved or rejected depends on whether the receiver links was successfully established or not.
Regarding disconnect, we already have code in place to recover broken links when faced with retryable errors. On exhausting all retries or on facing a non retryable error, the onError callback gets called. Though we do need a sample that shows best practice for when that happens.

@ramya-rao-a I think that returning a promise from createReceiver() might do some damage, for several reasons.

It's a breaking API, createReceiver is currently lazy and this might break stuff due to unhandled promise rejections.

createReceiver should not connect automatically on creation unless explicitly instructed to as it connects to the bus in various ways (receiveMessages, registerMessageHandler, renewMessageLock, etc...) and some of them allow a lazy strategy which will no longer be available

I think that createSender and  createReceiver should behave the same, both sync.

If we look at the API, all of the relevant methods in Receiver return a Promise except for registerMessageHandler which does not return (void)
This is the issue in the design of the API and that method should return a Promise and the onError should only pop up for connection issues arising after the initial connection.
Since this will be a huge breaking change, I think that @richardpark-msft suggestion to add the initialization method is perfect since it does not break the API anywhere and does allow handling initial connection errors.
await receiver.init()
receiver.registerMessageHandler(onMessage, onError, options)
// onError will only throw on handling issues or if the connection has issues after the initial connection

@richardpark-msft @ramya-rao-a
Here's another example for why this is critical, the following code describes the bug:
import { ServiceBusClient, ReceiveMode } from '@azure/service-bus';

async function run() {
  const serviceBusClient = ServiceBusClient.createFromConnectionString('YOUR KEY HERE');
  const queueClient = serviceBusClient.createQueueClient('YOUR_ENTITY_ID_HERE');

  const receiver = queueClient.createReceiver(ReceiveMode.peekLock);
  receiver.registerMessageHandler(async () => {}, e => console.error(e));

  // uncomment for it to work
  // await new Promise( r => { setTimeout(r, 2000); })

  await queueClient.close();
  await receiver.close();
  await serviceBusClient.close();
}

run();

The code above will never exit, leaving us with a memory leak because the connection never closes.
This is because it happens to fast and the library, when closed is called, thinks it is not connected...
The actual state of the connection at that point is not opened but also not closed (actually, local is opened remote is closed)
Because there's no way for the user to identify when the connection is done an artificial "setTimeout" is required, which ofcourse is not something one can count on.
I would expect having a promise to know when it's done, as well as a cancellation token to cancel the operation if I would like to stop before it finishe.

Here's the workaround if anyone needs it for the time being:
import { OnMessage, OnError, MessageHandlerOptions, MessagingError, Receiver } from '@azure/service-bus';

function registerMessageHandler(receiver: Receiver, onMessage: OnMessage, onError: OnError, options?: MessageHandlerOptions): Promise<void> {
  return new Promise( (resolve, reject) => {
    let done = false;
    const onErrorRouter: OnError = err => {
      if (done || err instanceof MessagingError) {
        onError(err);
      }
      else {
        done = true;
        reject(err);
      }
    };

    const poll = () => {
      setTimeout(() => {
        if (receiver.isReceivingMessages()) {
          done = true;
          resolve();
        } else if (!done) {
          poll();
        }
      }, 10);
    };

    receiver.registerMessageHandler(onMessage, onErrorRouter);
    poll();
  });
}

First, thank you for keeping the conversation going with this @shlomiassaf - you've been our reference customer as we talk about how to implement this!
What you've written above looks like just an outright bug in our logic, ignoring the method that we use to determine if the connection is open or not. The main issue here is that we also have background reconnect logic as well. So all of that needs to properly obey close().
We will be looking into this this month - I'll post updates as we have them.

@richardpark-msft On another subject, I would appreciate if you guys take a look at a new library I built that allows using @azure/service-bus with NestJS.
This can significantly increase the exposure of service bus to a lot of JS developers.
Thanks!

@shlomiassaf, I've got a tentative solution that looks good to our team that will fix the issue you posted above. The fix is pretty simple - it just makes sure that if we're closing the receiver that we wait until initialization has completed before returning.
The init process isn't easily cancellable at the moment so this is a simpler way of ensuring that you don't end up with an object that appears closed but does have a receiver link open. I'll be posting a PR for this sometime today after some more testing.
On re-reading the issue, I did have a question about something you wrote earlier about making createReceiver() async:

It's a breaking API, createReceiver is currently lazy and this might break stuff due to unhandled promise rejections.

Can you elaborate more on the "unhandled promise rejections" part? Is the concern that users might not realize they're getting back a Promise? Or something else?
Just for some information - in the newer version of the library (7.0.0-preview.2) our plan is to make createReceiver() async (this is already done for createSender() and createSessionReceiver()). This means the link will be active and ready immediately rather than waiting for first operation. Our goal is to move initialization higher in the stack so the usage model will be simpler - if you have a Receiver (or Sender) the object is live and ready to be used.
BTW, implementing a lazy strategy will still be possible - ServiceBusClient itself will remain a lazy initialized object.

Yes, since createReceiver() returns void and changing it to return a promise will not break anything in the user applications.
I guess that with such a huge change moving from 1 to 7, this should pass without much noise but not sure that all of the consumers will refactor their code so it will handle that promise...

Update:

There are no planned changes for v1 of the Service Bus package
In the new v7 of the Service Bus package, we are exploring alternatives to make the streaming receive mode be more deterministic.

Thanks for your time & patience!


console.log hunt 🔫

Replace calls to native console.log with a simple custom logger that can be switched off

Direct calls to console.log are evil. Always wrap them in a custom function or remove them once you don't need them anymore.
If all the logs are wrapped in a shared function, other developers can just bypass a single line of code instead of having to look into every files...


Can't use node:path.sep in browser

Hello, I just found this lib and it's exactly what I needed but I cant use it directly because it's use the directory seperator from node and I would like to use it in a browser using Vite.
Is it's possible to remove the dependency of nodejs ?
Also it's may be possible that the path you parsing is not using the OS separator
I get this error message ;
Module "node:path" has been externalized for browser compatibility. Cannot access "node:path.sep" in client code. See http://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
Thanks

Fixed


Pin all dependencies, use dependabot to keep ourselves up to date

There are pros and cons of using dependency ranges, but one of the main cons is that it makes builds not reproducible
It is also possible that a new upgrade will break our tests and we will only know when it happens
I think that like in https://github.com/openrewrite/rewrite/issues/1479, we should pin all our dependencies and use #1483 to keep ourselves up to date

Dependabot is not reliable for Gradle at this point. I would prefer we stick with dynamic versions and use Gradle's dependency locking mechanism. I would be happy with a github action workflow that attempts to update lock files daily, and if tests pass commits the result.

Unless @yeikel wants to submit a PR, I'll submit one later this evening for Gradle dependency locking and rich version constraints (as shown via the attached issue).

Unless @yeikel wants to submit a PR, I'll submit one later this evening for Gradle dependency locking and rich version constraints (as shown via the attached issue).

Feel free to do so and thank you

Spoke with @sambsnyd a bit on this one and it's a bit more complicated that described here.
In short, right now dependency upgrades are provided for free. In particular, this makes updates to the recipe libraries and the build plugins quite easy by not requiring much thought other than triggering the desired downstream build. By introducing dependency locking, this would mean that transitives would also need to have locks updated as part of a rolling release cycle (ex. openrewrite/rewrite -> openrewrite/rewrite-gradle-plugin). By implementing this naively, additional work for openrewrite transitive repositories would need to be incurred as part of the development and release processes.

Great summary Shannon, you've saved me the effort of having to write it. :)
I'd be happy to have a lock file checked in and automatically updated upon successful CI build. There are many reasons reproducible builds are desirable.
Automatically taking the latest version of most dependencies really streamlines the release process. More than once I've wasted time debugging, not realizing there was a lock file pinning dependencies.
Is there an option to have a lock file that doesn't lock by default? Less of a "lock", more of a ledger or record. If anyone knows how to configure that behavior I'd be interested to hear about it

Would a guard along the lines of the below working you think, @sambsnyd? This would allow you to enable locks when you desire a reproducible build (ie. Patch releases) or newcomers trying to build the project achieving a stable build. Then being able to stay up to date in the general case.
I would think we would enable dependency lock updating during all release builds that are not patch releases, where instead we would be using the lock state from that release. Then during the nightly builds as well.
if (hasProperty("dependency-lock") || gradle.startParameter.isWriteDependencyLocks) {
  // Enable dependency locking
}

In particular, this makes updates to the recipe libraries and the build plugins quite easy

I was thinking we would exclude org.openrewrite and build plugins from locks.


Include predictions for the heat of adsorption

This seems to require the addition of isosters in the code as well, as results from isotherms at different temperatures do not look promising. For the isosters the differential equation form of Clausius-Clapeyron can be used.

Add option between CC and Dubinin-Polanyi methods.

Closed the issue since the option to compute the heat of adsorption was added in the last pull request. The option is however in its early phase, so a separate issue can be created to track its improvement.


Sponsorship Paymaster Audit & Remediations

work on audit remediations
work on test coverage
work on deployment scripts
review accounting test cases + negative tests

Meeting with Juno from spearbit today.

Meeting with Juno from spearbit today.

chainlight not spearbit.

https://github.com/chainlight-io/2024-q4-biconomy-audit-issues-client/issues


No string enums and type safety for observable properties and event types

This pull request aims to remove string enums for event types, and add type safety for observable properties and event types by adding union type generics (defaulting to string) to Event, Observable and Object.

API doc generation currently fails because JSDoc does not recognize dynamic types like change:${ObservableProperties}. This could be fixed by converting such types in jsdoc-plugin-typescript.

Closing this for now. Let's see where the string enum removal leads to.
I'd really like to see our event handling work without anything special (event type enums, JSDoc plugin), and ideally we could even get rid of Object and observable properties.


vc_dispmanx_display_open failed! (Pi Zero W - Raspbian Buster)

I successfully got a 2.8" ili9341 to work a Raspberry Pi 3B+. Now I'm trying the sam display with a Raspberry Pi Zero W. The screen flashes briefly and then i get this error:
pi@raspberrypi:~/fbcp-ili9341/build $ sudo ./fbcp-ili9341
bcm_host_get_peripheral_address: 0x20000000, bcm_host_get_peripheral_size: 33554432, bcm_host_get_sdram_address: 0x40000000
BCM core speed: current: 250000000hz, max turbo: 400000000hz. SPI CDIV: 30, SPI max frequency: 13333333hz
Allocated DMA channel 7
Allocated DMA channel 1
Enabling DMA channels Tx:7 and Rx:1
DMA hardware register file is at ptr: 0xb4b70000, using DMA TX channel: 7 and DMA RX channel: 1
DMA hardware TX channel register file is at ptr: 0xb4b70700, DMA RX channel register file is at ptr: 0xb4b70100
Resetting DMA channels for use
DMA all set up
Initializing display
Resetting display at reset GPIO pin 27
Setting TFT backlight on at pin 17
InitSPI done
vc_dispmanx_display_open failed!

Am I doing something wrong?
Configuration:
cmake -DILI9341=ON -DGPIO_TFT_DATA_CONTROL=22 -DGPIO_TFT_RESET_PIN=27 -DGPIO_TFT_BACKLIGHT=17 -DSPI_BUS_CLOCK_DIVISOR=30 -DBACKLIGHT_CONTROL=ON -DSTATISTICS=0 ..

Wiring:
Display | Raspberry
MISO | 21
LED | 11
SCK | 23
MOSI | 19
DC | 15
RESET | 13
CS | 24
GND | GND
VCC | 5V

Setup:

If DispmanX cannot be loaded, then it is not a wiring nor a fbcp-ili9341 config/build issue, but something is going wrong with the display driver load. The only reason I have observed that to happen is mentioned in issue #75, when hardware VC4 KMS GL driver is used (dtoverlay=vc4-kms-v3d in /boot/config.txt) instead of the default driver. Try double-checking if that might be the reason here?

Thanks for the quick reply. 😃
Unfortunately I haven't touched the /boot/config.txt file and dtoverlay=vc4-kms-v3d is commented
pi@raspberrypi:~ $ sudo cat /boot/config.txt
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d

Even if I comment out the pi4 section I get the same error.

Oh, this is on the new Raspbian Buster? It looks like there are some changes on Buster.
Briefly googling, https://www.raspberrypi.org/forums/viewtopic.php?t=243429 suggests "Dispmanx is still there with FKMS (or legacy)." Perhaps raspi-config needs a specific GL driver config line to enable FKMS or legacy driver - not exactly sure, haven't yet updated to Buster, but worth a shot.

I tried all the three options without luck

Hmm, no immediate idea either, I'm afraid. Reading https://github.com/raspberrypi/firmware/issues/1154 suggests that DispmanX should work on Buster, at least when used on a Pi 4. Did the same Raspbian Buster image work on a Pi 3B+? (or was the successful Pi 3B+ test on Stretch?)
In absence of better ideas, downgrading to Stretch should fix the issue.

The successful test on the Pi 3B+ was on Stretch.
I've just downgraded the Pi Zero W to Stretch too and it works now.

What i'm observing is that with Buster, if HDMI is connected to the Pi, vc_dispmanx_display_open does not fail.
If no HDMI is attached, then this reliably happens.

Thanks for the important info! If it turns out to be not fixable/configurable in software, an appropriate action may be to raise the issue in https://github.com/raspberrypi/firmware/

I configured
hdmi_group=2
hdmi_mode=87
hdmi_cvt=640 480 60 1 0 0 0
hdmi_force_hotplug=1

for my config.txt and the display is working fine under buster on a Pi 3B. Those seem to be enough to force the HDMI to be on (as well as set to an almost-readable resolution for the TFT).

btw, for some reason, on the buster image that i have been testing, without enabling SPI, fbcp-ili9341 still works, with my ST7789 display.

Yeah, that is expected - fbcp-ili9341 does not use the kernel spi driver but directly accesses the spi peripheral for fastest performance. This can actually conflict with the kernel spi driver so it is best to disable the kernel spi option altogether so that they will not try to simultaneously access spi.

Awesome, thanks for explaining that!

Confirmed trying out locally on Raspbian Buster with a Pi 4B, setting hdmi_force_hotplug=1 enables dispmanx API to work. (either with dtoverlay=vc4-fkms-v3d or without). I'll close this as resolved.

I encountered the same issue while trying to run fbcp-ili9341 on a Pi Zero using DietPi (based on Raspbian Lite buster).B
hdmi_force_hotplug=1 wouldn't do any good.
What I found is, I had a GPU memory split set at 16MB in /boot/config.txt (gpu_mem_512=16).
This, somehow, caused vc_dispmanx_display_open to fail.
Removing the line (defaults to 64MB I think), or setting it to 32MB (haven't tried other options) solved the issue.

Figured I'd put up what fixed this problem for me, in the hopes that it helps someone else in the future:
Check sudo tvservice -s.  If you get:
state 0x2 [TV is off]

you will need to make sure the "tv is on" before running ./fbcp-ili9341 like so:
sudo tvservice -p
to turn it on with "preferred" settings.  If you see something like
Powering on HDMI with preferred settings

you should be good to go!


Editing docs

Making spelling/grammar edits to docs

Hello, I am a PR summary agent on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!


🐞 Drag-collapsing Inspector sidebar in full-screen breaks layout

Description
Dragging the Inspectors sidebar to collapse causes the main layout to break: an empty space appears in place of the collapsed sidebar. Trying to open the sidebar again causes a further layout shift, inducing the sidebar anchor placement.
To Reproduce

Open CodeEdit
Click on "Hide or show the Inspectors" sidebar toggle icon in the top right corner
Drag the sidebar by the left edge (to the right) to collapse
See the main file content area now has an empty black area on the right

Expected Behavior
Dragging the Inspectors sidebar to collapse - collapses the sidebar without breaking the main layout
Version Information
CodeEdit: 0.0.3-alpha (32)
macOS: 13.3.1
Xcode: 14.3 (14E222b)
Additional Context
No response
Screenshots
https://user-images.githubusercontent.com/16290753/230754579-f4e45f9d-e473-476a-b8b2-4c81d99d5d80.mp4

This also removes width from the window when drag-collapsing not in full-screen.

This issue is caused by the current STTextView implementation, so hopefully it gets resolved once https://github.com/CodeEditApp/CodeEditTextView/pull/211 is merged.


Add possibility to work with multiple open api docs validation in 1 test

In my current tests i need to work with multiple servers with own docs in one test:
describe('Some feature', () => {

  before(async () => {
    const axios = require('axios');
    const response = await axios.get('http://loginservice:3000/api-json');
    const openApiSpec = response.data;
    chai.use(chaiResponseValidator(openApiSpec));
  });

  it('complex flow', async () => {
    // request to service that has own doc
    const loginres = await axios.get('http://loginservice:3000/user/auth');
    expect(loginres).to.satisfyApiSpec;

    // request to another service, that also has own doc
    const res = await axios.get('http://searchservice:3000/search/', {headers: loginres.data.token});
    expect(res.status).to.equal(200);
    //
    expect(res).to.satisfyApiSpec;
  });
});

Potential solution that i see, is to create 2 chai instances:
const searchChai = require('chai')
const loginChai = require('chai')

describe('Some feature', () => {
  before(async () => {
    const axios = require('axios');
    const response = await axios.get('http://loginservice:3000/api-json');
    const openApiSpec = response.data;
    loginChai.use(chaiResponseValidator(openApiSpec));

    const axios = require('axios');
    const response = await axios.get('http://searchservice:3000/api-json');
    const openApiSpec = response.data;
    searchChai.use(chaiResponseValidator(openApiSpec));
  });

  it('complex flow', async () => {
    // request to service that has own doc
    const loginres = await axios.get('http://loginservice:3000/user/auth');
    loginChai.expect(loginres).to.satisfyApiSpec;

    // request to another service, that also has own doc
    const res = await axios.get('http://searchservice:3000/search/', {headers: loginres.data.token});
    searchChai.expect(res).to.satisfyApiSpec;
  });
});

But this looks pretty hard to support, and such approach is not possible to apply to jest version of this validatior.
Would be nice to get some api that will allow to assert against provided spec, something like:
Something like:
  it('complex flow', async () => {
    // request to service that has own doc
    const loginres = await axios.get('http://loginservice:3000/user/auth');
    expect(loginres).to.satisfyApiSpec('./loginservice.json');

    // request to another service, that also has own doc
    const res = await axios.get('http://searchservice:3000/search/', {headers: loginres.data.token});
    expect(res).to.satisfyApiSpec('./seachservice.json');
  });

Thanks for this suggestion @Xotabu4. There may already be a workaround to do what you want, but let's check if it works. Even if it does, this enhancement may be nice as syntactic sugar.
I think currently expect(res).to.satisfyApiSpec validates res against the OpenAPI spec that was most recently loaded into the particular instance of chai. So although you can't currently use multiple OpenAPI specs at the same time for an instance of chai, you may be able to switch to different OpenAPI specs even in the same it block:
const axios = require('axios');

describe('Some feature', () => {
  it('complex flow', async () => {
	const { data: loginOpenApiSpec } = await axios.get('http://loginservice:3000/api-json');
    chai.use(chaiResponseValidator(loginOpenApiSpec));

    const loginres = await axios.get('http://loginservice:3000/user/auth');
    expect(loginres).to.satisfyApiSpec;

    // request to another service, that also has own doc
	const { data: searchOpenApiSpec } = await axios.get('http://searchservice:3000/api-json');
    chai.use(chaiResponseValidator(searchOpenApiSpec));

    const searchres = await axios.get('http://searchservice:3000/search/', {headers: loginres.data.token});
    expect(searchres).to.satisfyApiSpec;
  });

Does this work?
Even if it does, however, I agree it's a bit messy.
If you don't need multiple OpenAPI specs in the same it block, you can separate them in  different describe blocks (see our test file as an example)
But if you do need multiple OpenAPI specs in the same it block, this enhancement may be nice as syntactic sugar

Closing as there hasn't been an update for a while, but feel free to reopen or upvote this issue if anyone would like action on it 😄


Typo Fix

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/3605

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

@LolaJacobsen PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


NETOBSERV-1606: Add PODs tolerations config to ebpf agent, flp and console plugin

Description
there is recent ask to add tolerations config to the different no components
Dependencies

n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[ ] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[ ] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[ ] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[ ] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

/ok-to-test

/ok-to-test

Codecov Report
Attention: Patch coverage is 62.28070% with 43 lines in your changes are missing coverage. Please review.

Project coverage is 66.39%. Comparing base (dcaf464) to head (77b1884).
Report is 7 commits behind head on main.

Files
Patch %
Lines

...pis/flowcollector/v1beta2/zz_generated.deepcopy.go
0.00%
28 Missing and 3 partials :warning:

pkg/helper/flowcollector.go
76.00%
6 Missing and 6 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #618      +/-   ##
==========================================
+ Coverage   65.70%   66.39%   +0.69%
==========================================
  Files          65       65
  Lines        8509     7357    -1152
==========================================
- Hits         5591     4885     -706
+ Misses       2559     2115     -444
+ Partials      359      357       -2

Flag
Coverage Δ

unittests
66.39% <62.28%> (+0.69%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

/label qe-approved

/approve


Fixes #587 Support negative numbers as command option values

Decided to create some unit tests for the tokenizer, as it would've been too much of a mess to test all of this through CommandApp. That's obviously up for debate, but at least the tokenizer tests helped me with this.

Hey @phil-scott-78, thanks for reviewing. Actually, CommandTreeTokenizer does have (logical) 100 % test coverage already. It is not immediately obvious, as this PR is the first stage that actually adds tests specifically for the Tokenizer; previously, the tokenizer has only been tested through CommandAppTests which test the entire parsing and execution pipeline. However, some of the test scenarios there (say, CommandAppTests.Parsing.InvalidShortOptionName.Should_Return_Correct_Text) do exercise these failure modes.
I would personally prefer to have 100 % coverage specifically with the tokenizer test suite, but writing all that is slightly beyond the scope of this issue. Would you expect to see (tokenizer level) tests for the failure scenarios of the ScanShortOptions tokenizer branch or what? TBH, the tokenizer test set in this PR doesn't cover all short option tokenization features (even the happy paths) either, grouped properties probably being the most important missing part. Given that there's no precedent for tokenizer tests in the project, I'm happy to do extra work to set a good example, let's just agree on the goal first.

this PR is the first stage that actually adds tests specifically for the Tokenizer; previously, the tokenizer has only been tested through CommandAppTests which test the entire parsing and execution pipeline

This is a significant improvement that @jouniheikniemi has introduced and I would be keen to see this PR, once review comments are addressed 😊, merged into the codebase.  Particularly since I have a raft of CommandTreeTokenizer tests I would like to add myself, ideally into the same class being introduced in this PR.

This should be closed as it's been fully included in https://github.com/spectreconsole/spectre.console/pull/1048  [I don't have permission to close another person's PR]

I was about to get back to your review comments, but it seems you'd rather pick up the ball yourself; fine with me. Closing the PR. Thanks!

I was keen to merge your excellent work @jouniheikniemi - thanks for your contribution.


some extra packages

@athanclark, do you mind rebasing on master and to add these packages in a single commit? Thanks!

quickcheck-combinators currently doesn't build on GHC 8.0.2.

whoops i missed Ryan's comment. I'm disabling quickcheck-combinators, please open a new PR if it gets fixed.

The pred-trie tests are also failing:
test/Data/Trie/PredSpec.hs:24:10: error:
    Duplicate instance declarations:
      instance Arbitrary a => Arbitrary (NonEmpty a)
        -- Defined at test/Data/Trie/PredSpec.hs:24:10
      instance [safe] Arbitrary a => Arbitrary (NonEmpty a)
        -- Defined in ‘Test.QuickCheck.Arbitrary’

And the tries benchmarks:
bench/Build.hs:6:1: error:
    Failed to load interface for ‘Data.Tree’
    It is a member of the hidden package ‘rerebase-1.0.3’.
    Perhaps you need to add ‘rerebase’ to the build-depends in your .cabal file.
    It is a member of the hidden package ‘containers-<IP_ADDRESS>’.
    Perhaps you need to add ‘containers’ to the build-depends in your .cabal file.
    Use -v to see a list of the files searched for.

bench/Build.hs:10:1: error:
    Failed to load interface for ‘Data.Tree.Knuth.Forest’
    It is a member of the hidden package ‘rose-trees-<IP_ADDRESS>’.
    Perhaps you need to add ‘rose-trees’ to the build-depends in your .cabal file.
    Use -v to see a list of the files searched for.

bench/Build.hs:12:1: error:
    Failed to load interface for ‘Data.Map’
    It is a member of the hidden package ‘rerebase-1.0.3’.
    Perhaps you need to add ‘rerebase’ to the build-depends in your .cabal file.
    It is a member of the hidden package ‘containers-<IP_ADDRESS>’.
    Perhaps you need to add ‘containers’ to the build-depends in your .cabal file.
    Use -v to see a list of the files searched for.

bench/Build.hs:13:1: error:
    Failed to load interface for ‘Data.HashMap.Lazy’
    It is a member of the hidden package ‘unordered-containers-<IP_ADDRESS>’.
    Perhaps you need to add ‘unordered-containers’ to the build-depends in your .cabal file.
    It is a member of the hidden package ‘rerebase-1.0.3’.
    Perhaps you need to add ‘rerebase’ to the build-depends in your .cabal file.
    Use -v to see a list of the files searched for.

bench/Build.hs:14:1: error:
    Failed to load interface for ‘Control.Monad.State’
    It is a member of the hidden package ‘rerebase-1.0.3’.
    Perhaps you need to add ‘rerebase’ to the build-depends in your .cabal file.
    It is a member of the hidden package ‘mtl-2.2.1’.
    Perhaps you need to add ‘mtl’ to the build-depends in your .cabal file.
    It is a member of the hidden package ‘monads-tf-<IP_ADDRESS>’.
    Perhaps you need to add ‘monads-tf’ to the build-depends in your .cabal file.
    Use -v to see a list of the files searched for.

@bergmark @RyanGlScott Sorry I took so long! Just got these builds fixed with the latest versions published to hackage. Thank you for your help identifying these!


error: failed to compile bore-cli v0.5.0

intermediate artifacts can be found at /var/folders/6y/6qbpvpzj2gd7qw_msjl5j48c0000gn/T/cargo-installdzv1zj
Caused by:   package clap_lex v0.7.0 cannot be built because it requires rustc 1.74 or newer, while the currently active rustc version is 1.63.0

Please update your rustc version to rustc 1.74 or newer.


Create tukorea.txt

Official domain in the link below:
https://tukorea.ac.kr/
IT course provided in the link below:
https://www.tukorea.ac.kr/en/3537/subview.do

@fiedith I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host tukorea.kr not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Can't sign up with github account

The authorization on github's side worked, but then coming back only yields "Failed to connect account" if I click on "Link Your GitHub Account" again.
Could it be the length of my account? Maybe codewars has a minimum >= 3?

Yeah the minimum length is currently set to 3. I'm trying to remember if there was a specific reason why we set that.

jhoffner,
Is there an issue with signing up for code wars?

still cant sign up, everytime I
[ press "enlist", the site just refresh, and turn out I need to re-insert email address ] <--- loop

I'm having exactly the same problem as @RisnD21
Does anyone have a solution for this? (Using google chrome if that matters)

Same here. The page just refreshes, the form is still there with the data but nothing happens.

+1
It just refresh, you can't sing up.

I was able to create an account with some help! I was trying to create it with firefox but nothing worked, but it finally did when I tried it with Google Chrome.

I also switch the browser, on Chrome doesn't work but on Mozilla it work!

doesn't work for me in chrome, safari, firefox


IPAM docs are out of date wrt manual allocation

http://docs.weave.works/weave/latest_release/ipam.html says "The specified range is for exclusive use by the IP allocator...", however this restriction went away with #1200

fixed by a73a65b48adee70fffd87dd50a70743ccaf20fac


Disconnecter clair

Hey,
I know that Clair routinely queries CVE databases to build its internal database. There is a scenario that I can deploy Quay with Clair in a disconnected environment?
Thanks, Matan.

Clair currently does not support deployment in a disconnected environment. RFE's should be placed in the [Quay](https://github.com/quay/quay} project repository


[Feature] Support record-level timestamp

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Paimon can own the record-level metadata like timestamp as the Paimon append table is used like a queue, timestamp for records in queue is useful.
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

hi schnappi17 I am learning pamion recently and I am very interested in this project, I would like to do some simple functions for this if you are willing to assign it to me, I will try to learn and complete it
@schnappi17

@zhilinli123 assigned to you.

@zhilinli123 assigned to you.

Is this timestamp like hudi will come with this data in the query and add an additional timestamp field to each write table


Project page is down

Hi!
I am entering in https://material.angular.io/ and it is returning an empty page

I can confirm this was happening for me to. Constantly hard refreshed and it worked sooner or later.

It 's fixed now. I close the issue.
Thanks!


[incubator-kie-issues-1439] UserTask Decouple codegen and interface from engine

depends on:https://github.com/apache/incubator-kie-drools/pull/6052
Closes: https://github.com/apache/incubator-kie-issues/issues/1439

PR job #10 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-runtimes -u https://github.com/apache/incubator-kie-kogito-runtimes/pull/3631 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-runtimes-pr/job/PR-3631/10/display/redirect
Test results:

PASSED: 1456
FAILED: 1

Those are the test failures:

org.jbpm.process.TimerTest.testTimer
expected: 4 but was: 5