Dropdown inside responsive table row clipped even with data-bs-boundary set

A dropdown inside a responsive table row gets clipped even with data-bs-boundary set
Removing the table-responsive class from the parent div solves the issue, but we lose responsiveness.
Another workaround is to add style="position:static" to the dropdown class div, and it doesn't clip after.
Not sure if that's expected or should be considered an issue.
OS: Ubuntu 20.04
Browser: Firefox 87
Bootstrap<EMAIL_ADDRESS>Example:

                        Options

Item

Item

Item

Item

Item

@korki43 @mdo This explanation makes sense. When encountering this issue, is there a workaround?

@mrlife I just tested it in the codepen above and it still works. You can add position: static to the .dropdown div and it should not clip anymore.

@wadih Thanks, I don't know if it's just the version I'm on (4.6) but I can't get that to work. It does work great in the codepen.

@wadih Thanks, looks like my cause for this issue was due to implementing a solution to another issue here: https://github.com/twbs/bootstrap/issues/31885#issuecomment-717970534.

I've been struggling with this issue for days. But, for me, if I just remove the outer dropdown div (just delete it), it seems to work fine. Does that not work for anyone?

After more than a few hours and various attempts I found the working version:
const dropdowns = document.querySelectorAll('.dropdown-toggle')
const dropdown = [...dropdowns].map((dropdownToggleEl) => new bootstrap.Dropdown(dropdownToggleEl, {
    popperConfig(defaultBsPopperConfig) {
        return { ...defaultBsPopperConfig, strategy: 'fixed' };
    }
}));

I found that on iOS it starts clipping again IF and only IF the table is horizontally longer and has a scrollbar . If not, there is no clipping.
My solution now is to avoid using "table-responsive", and instead use a regular div with style = "overflow: auto"
That solves the clipping on iOS when the table is long enough to have a scrollbar horizontally
My solution has 2 components now:

Wrap the table in a div with style="overflow:auto" instead of using the table-responsive class

On the dropdown give class="position-static"

And that fixes the conditional clipping on iOS as well


Build on linux

How do i actually build the source to try out flax?

On linux, you just need to install LLVM 7 (see this place for the appropriate sources to add to APT for debian-based distros: https://apt.llvm.org/), libffi, and libmpfr through your package manager. After that, you should be able to run make to compile everything.

i have llvm 8 on my system (arch). and when i try make i get llvm-config: command not found

You need llvm 7 to build flax, not llvm 8. I'm not sure if llvm 8 would work since it is a different major version after all.
Once you've installed 7, you may want to check if llvm-config has been installed as llvm-config-7 instead, which would mean you have to export the LLVM_CONFIG variable for make by running
LLVM_CONFIG=llvm-config-7 make

instead of plain old make.

Ah yes, rolling release distros. I'm also on arch and i accidentally updated llvm to 8.0.0, so i'm kinda in the same situation as you right now. Though my llvm-config does show up, so that's a bit strange.
You could install llvm-7, but being arch i don't really recommend that, so we're kinda stuck.
i'll keep this issue open until flax gets updated to use llvm 8.

Commit 0f93013 merged into develop moves us from LLVM 7 to LLVM 9, so that should solve builds on rolling-release distros... at least for a few months.


Second Pull request connecting OLCA schema to Refactor

Hi Wes, You will all the changes I described today in this pull request and update.

You deleted the README.md file..please undelete that.
There are still too many EIA923 files in the data directory. Please just commit the final csv file(s) that you're importing into the script to use. The EIA923_generation.py will show how you got there.
Something seems very wrong in the egrid_filter.py file.  On line 62 you are creating the process dictionary directly from
emissions_and_waste_by_facility_for_selected_egrid_facilities ?  This data  does not have the generation in there yet, much less the factors. This needs to be addressed immediately if this is the case.
I would prefer if the sheets within eLCI_data each be a csv file (the 'region' sheet it not needed), but we can change this later.
The elci_summary.csv file should not be in the repository
If you address these items I will accept it.

Closing this as all changes have been made. Will create new


🚀 - @tiptap/extension-* dependencies should be marked as optional

Description
Reopening #1092 since PR #1093 was reverted.

I'm not sure if I should do this after the build crashed

The build failed because optional peer dependencies were not installed. You are relying on npm automatically installing peer dependencies, which other package managers like yarn don't do.
I don't see why it should be mandatory to install all the extensions even you are only using some of them.
@waterplea what's your opinion about this?

The build failed because optional peer dependencies were not installed. You are relying on npm automatically installing peer dependencies, which other package managers like yarn don't do.
I don't see why it should be mandatory to install all the extensions even you are only using some of them.
@waterplea what's your opinion about this?

Sounds like we need all those deps explicitly stated in our demo app/CI, but keep them optional in our library published package.json, right?

need all those deps explicitly
users will have to specify a lot of packages themselves

Sounds like we need all those deps explicitly stated in our demo app/CI, but keep them optional in our library published package.json, right?

Yes, that's the idea.

users will have to specify a lot of packages themselves

By default, npm installs non-optional peer dependencies automatically, but because you enabled legacy-peer-deps, they were not installed. The user will have to install manually some of the extensions, but in many cases just installing the StarterKit should be enough.
Still it might be a good idea to update the docs with information about the optional peer dependencies, what users need to install and how to configure extensions.

Do not use legacy-peer-deps

I am not. Your v1 branch is.

v1.x -> we use dependencies for legacy-peer-deps
main -> we use peerDependencies for user who don't use legacy-peer-deps

I think technically it's a good idea to not force people to install dependencies they might not need. Sure, most of our internal users will use full default kit, but if we are trying to develop a widely used modern solution, we should probably embrace this approach. We can add those packages with migration script for our current users and add it to the docs to reflect what you need to add if you want to use full toolset.

Sounds good to me.

@waterplea sure

Fixed by v2.x

@splincode @maskito/angular should be optional too.
Also, it might be a good idea to add a note to the docs.

I don't think we need Maskito at all in the editor?

color-input use it


Sprockets::CircularDependencyError after CoffeeScript syntax error

When I have a CoffeeScript syntax error, after the first call to my compiled JS asset, I get a Sprockets::CircularDependencyError until I restart the server. Sprockets 2.0.2, Rails 3.0.9.
My environment is set up in config.ru:

require ::File.expand_path('../config/environment',  __FILE__)
require 'sprockets'

map '/assets' do
  environment = Sprockets::Environment.new
  environment.append_path 'app/assets/coffeescripts'
  environment.append_path 'app/assets/javascripts'
  environment.append_path 'app/assets/stylesheets'
  environment.append_path 'vendor/assets/javascripts'
  run environment
end

map '/' do
  run Gpg::Application
end

Heh, I just ran into this too. Its fixed on the 2.2 branch which should be out soon.

Hello there!
I'm suffering badly by this one. Is 2.2 coming out soon?
And if not, is there a workaround?


Fixed false positive on test_run_handler

Description
As described in #410
We now compare the resulted text body to a hardcoded error message pod does not exist coming from kubelet.
By looking at the source code of the kubelet
This looks like this is not gonna change in the long term
Fixed Issues
Fixes #410
Contribution checklist

[x] I have read the Contributing Guidelines.
[ ] The commits refer to an active issue in the repository.
[ ] I have added automated testing to cover this case.

@lizrice
So when we get this error message we dont get a 404 status, but rather a 405 as well.
This was the problem. also, 404 gets returned regardless of authorization/authentication. only when a specific endpoint does not exist entirely

@lizrice oh I get what you were asking, Ill try maybe to send a post request, perhaps well get a 404 and can rely on that.


HSEARCH-3314 Restore support for (static) sharding

https://hibernate.atlassian.net//browse/HSEARCH-3314
~Based on #2037 , which should be merged first.~ => Done

Applied your suggestions and merged. Thanks!


chore(release): Revert release v2.2.5 to trigger it again

:tada: This PR is included in version 2.2.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update documentation github action to save artifacts

Description:
To enable the developer to see the created CUQIpy documentation after each update to a PR, the created CUQIpy documentation can be uploaded and accessed through the github action interface. (see for example this CUQIpy documentation artifacts https://github.com/CUQI-DTU/CUQIpy/actions/runs/11869024631).
DoD:

[ ] Update docs.yml file to add artifact upload section (we have similar setup in CUQI-Book added by @nabriis )
[ ] Decide if documentation build time is still acceptable (4min of increased docs build time is noticed, from 12min docs build time to about 16 min)
[ ] Get the update reviewed and approved

@nabriis fyi, keeping track of this

@jakobsj , can you please review the DoD. Thank you.

@amal-ghamdi DoD approved!


Change size of hold Icon

What

shrinks hold icon
Why

Fixes styling concerns for more button options

https://skype.visualstudio.com/SPOOL/_workitems/edit/2958022
How Tested

Hold button missing in mobile snapshots


Transition Downtime Index to the Design System

What

Use the Table component on the Downtime index page
Create new helper function to generate entries for the Downtime index table
Add test for new helper function
Add flash to design_system.html.erb
Update existing tests with new changes

Why
As part of the work to transition Publisher to the Design System from Bootstrap.
Relevant Trello Card. https://github.com/alphagov/publisher/pull/2027 Needs to be merged first
Visual Differences
Before

After

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
Follow these steps if you are doing a Rails upgrade.

Will raise 2/3rds width title with Nikin.


Add support for cases without iteration folder

Closes #557
Note logic should also be tested when implementing more ERT integration testing as planned for in #588

now including the case metadata file 😄 .. it was being ignored by git


fix(getUser&adminGetUser): username field now returns sub...

… rather than login username
Addresses Issue #334

Ah, not sure if this addresses (partially) or steps on issue #102...


Add note on compression choices for ZFS

After some feedback on lz4 vs zstd, here's some basic info on the choices.

Thank you!
Made one minor addition to header to put compression choices in the header.
For search, the file name and header are indexed.
So, added the choices to the header so they can be discovered when searched.


[6.0][Distributed] Diagnose missing import also for funcs in extensions

Description: When a distributed func was declared in an extension in a file that did not import the Distributed module, though the extension was made properly on a distributed actor, we would crash in synthesis in SILGen because synthesis refers to types in the distributed module and the import is necessary.
This patch properly diagnoses missing imports whenever a distributed func is used somewhere.
Reviewed by: @xedin
Risk: Low, only improved diagnostics rather than crashing the compiler for distributed func declarations.
Testing: CI testing, verified manually in Xcode project of original issue reporter
Original PR: https://github.com/apple/swift/pull/72923
Radar: rdar://125813581

@swift-ci please smoke test

@swift-ci please test

@swift-ci please test

Cherry pick AFTER https://github.com/apple/swift/pull/72974 to avoid conflicts

@swift-ci please test

@swift-ci please test

rebased post-https://github.com/apple/swift/pull/72974

@swift-ci please test Linux

@swift-ci please test


[tech-insights] upgrade to Backstage and remove deprecated usages

Hey, I just made a Pull Request!

Updates Backstage to v1.29.1
Removes deprecated API usage except the migration to the new Auth system

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@secustor are you already working on the new auth system switch? I haven't looked into it yet, but I could at least see what needed to be changed. Not sure where you where on the process though.


Add posts functionality

A social site is no good without the ability to create posts. Add functionality to allow users to create new posts that their followers can view.

[ ] Create new post endpoint
[x] Create post list endpoint
[x] Create single post detail endpoint
[ ] Create  post delete endpoint
[ ] Create unit tests for all the above

This functionality is related to #5

I have started working on this task.


Multiple plugs switching Entity ID

I have 2x Tapo P100 plugs under this integration. Both appear in HA, but it seems when I restart HA the entities switch (i.e. switch 1 acts as switch 2 and vice-versa), throwing automations etc out (e.g. a bug spray coming on instead of fairy lights).
Wondering if this is a bug or something in my setup...
``#P100 or P105 Plug
switch:

platform: tapo_p100_control
ip_address: xxx.xxx.xx.xx
email<EMAIL_ADDRESS>password: xxxxxxxxxxxxxxxx

platform: tapo_p100_control
ip_address: xxx.xxx.xx.yy
email<EMAIL_ADDRESS>password: xxxxxxxxxxxxxxxx
'`

Nice one guys. been looking for this for ages.


Add warnings to solver docs to tell user what happens if incorrectly-sized coresubsets are provided to refine

What's the new feature?
Add warnings to solver docs to tell user what happens if incorrectly-sized coresubsets are provided to refine
What value does this add?
Clarity for user
Is there an alternative you've considered?
No response
Additional context
No response

Should be reviewed by @tp832944


Streamlined for 6.4

Took the latest merge  and cleaned up variables, syntax issues, and overall presentation of the variables to alleviate confusion.

closed to resolve merge issues


Add markpress into Miscellaneous section

https://github.com/gamell/markpress

Thanks for the suggestion, but I'm going to pass on this. I would encourage you submitting to https://github.com/aharris88/awesome-cli-apps though :)

Cool thanks


Infinity build loop on ESP-IDF v4.1-rc (IDFGH-3745)

Hello!
Thanks for 4.1 rc, but all my attempts to build it on OSX failed.
OSX 10.15.6 (19G73)
Steps to install ESP-IDF:

Clean previous ESP-IDF dir completely
Clean Tools dir completely
Delete build dir of project
Download archive with v4.1-rc, install and export it
reboot system

After that i can't build any project on new version.
All attempts end in an endless loop.
I can find in console follow messages
"- Configuring done

Generating done
Build files have been written to: /Users/thecashit/Documents/LOOK.in/Firmware/blehr/build
[0/1] Re-running CMake ..."

And all starts from the beginning.
I also try to build one of examples - the behavior is the same.
I am attaching a log from the blehr example, maybe it will help
<SOME_PATH> is omitted path, its real in console.
idf.py build

Executing action: all (aliases: build)
Running cmake in directory /<SOME_PATH>/blehr/build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 --warn-uninitialized -DCCACHE_ENABLE=0 /<SOME_PATH>/blehr"...
Warn about uninitialized values.
-- Found Git: /usr/bin/git (found version "2.21.0 (Apple Git-122.2)")
-- IDF_TARGET not set, using default target: esp32
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /<SOME_PATH>/Toolchain/tools/tools/xtensa-esp32-elf/esp-2020r2-8.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
-- Check for working C compiler: /<SOME_PATH>/Toolchain/tools/tools/xtensa-esp32-elf/esp-2020r2-8.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
-- Check for working C compiler: /<SOME_PATH>/Toolchain/tools/tools/xtensa-esp32-elf/esp-2020r2-8.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /<SOME_PATH>/Toolchain/tools/tools/xtensa-esp32-elf/esp-2020r2-8.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++
-- Check for working CXX compiler: /<SOME_PATH>/Toolchain/tools/tools/xtensa-esp32-elf/esp-2020r2-8.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Project is not inside a git repository, or git repository has no commits; will not use 'git describe' to determine PROJECT_VER.
-- Project version: 1
-- Building ESP-IDF components for target esp32
Loading defaults file /<SOME_PATH>/blehr/sdkconfig.defaults...

-- Project is not inside a git repository, or git repository has no commits; will not use 'git describe' to determine PROJECT_VER.
-- Project version: 1
-- Building ESP-IDF components for target esp32
Loading defaults file /<SOME_PATH>/blehr/sdkconfig.defaults...

-- Project is not inside a git repository, or git repository has no commits; will not use 'git describe' to determine PROJECT_VER.
-- Project version: 1
-- Building ESP-IDF components for target esp32
Loading defaults file /<SOME_PATH>/blehr/sdkconfig.defaults...

Clean, fullclean, and removing build dir didn't help

Works after downgrade to xtensa installed from 4.1-beta2 version

Hi @thecashit,
I'm glad to hear that you found a solution to the problem. We'd like to understand if there's still something here that we need to fix in ESP-IDF.

Do I understand correctly that this works with esp-2019r2 toolchain but not with the esp-2020r2 toolchain? This is a little unexpected as this part of the toolchain does not have much overlap with the build system.
Are you able to post the output from idf.py reconfigure when using the working toolchain, please? (should look similar to the output above.)
Have you tried upgrading back to esp-2020r2 again? Does the problem immediately come back?

Thanks,
Angus

@projectgus Thnx for answer

Correct, when i use esp-2020r2 it was infinity loop on configuration. esp-2019r2 works well
Please see attached output

idf.py reconfigure

Executing action: reconfigure
Running cmake in directory /<SOME_PATH>/blehr/build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 --warn-uninitialized -DCCACHE_ENABLE=0 /<SOME_PATH>/blehr"...
Warn about uninitialized values.
-- Unexpected file in components directory: /<SOME_PATH>/Toolchain/esp-idf/components/.DS_Store
-- Component directory /<SOME_PATH>/Toolchain/esp-idf/components/tinyusb does not contain a CMakeLists.txt file. No component will be added
CMake Warning at /<SOME_PATH>/Toolchain/esp-idf/tools/cmake/git_submodules.cmake:52 (message):
  Git submodule components/mbedtls/mbedtls is out of date.  Run 'git
  submodule update --init --recursive' to fix.
Call Stack (most recent call first):
  /<SOME_PATH>/Toolchain/esp-idf/tools/cmake/build.cmake:78 (git_submodule_check)
  /<SOME_PATH>/Toolchain/esp-idf/tools/cmake/build.cmake:160 (__build_get_idf_git_revision)
  /<SOME_PATH>/Toolchain/esp-idf/tools/cmake/idf.cmake:48 (__build_init)
  /<SOME_PATH>/Toolchain/esp-idf/tools/cmake/project.cmake:7 (include)
  CMakeLists.txt:5 (include)

-- Project is not inside a git repository, or git repository has no commits; will not use 'git describe' to determine PROJECT_VER.
-- Project version: 1
-- Building ESP-IDF components for target esp32
Loading defaults file /<SOME_PATH>/blehr/sdkconfig.defaults...
-- Adding linker script /<SOME_PATH>/blehr/build/esp-idf/esp32/esp32_out.ld
-- Adding linker script /<SOME_PATH>/Toolchain/esp-idf/components/esp32/ld/esp32.project.ld.in
-- Adding linker script /<SOME_PATH>/Toolchain/esp-idf/components/esp32/ld/esp32.peripherals.ld
-- Adding linker script /<SOME_PATH>/Toolchain/esp-idf/components/esp_rom/esp32/ld/esp32.rom.newlib-time.ld
-- Adding linker script /<SOME_PATH>/Toolchain/esp-idf/components/esp_rom/esp32/ld/esp32.rom.ld
-- Adding linker script /<SOME_PATH>/Toolchain/esp-idf/components/esp_rom/esp32/ld/esp32.rom.libgcc.ld
-- Adding linker script /<SOME_PATH>/Toolchain/esp-idf/components/esp_rom/esp32/ld/esp32.rom.newlib-data.ld
-- Adding linker script /<SOME_PATH>/Toolchain/esp-idf/components/esp_rom/esp32/ld/esp32.rom.syscalls.ld
-- Adding linker script /<SOME_PATH>/Toolchain/esp-idf/components/esp_rom/esp32/ld/esp32.rom.newlib-funcs.ld
-- Components: app_trace app_update asio bootloader bootloader_support bt cbor coap console cxx driver efuse esp-tls esp32 esp_adc_cal esp_common esp_eth esp_event esp_gdbstub esp_http_client esp_http_server esp_https_ota esp_https_server esp_local_ctrl esp_netif esp_ringbuf esp_rom esp_serial_slave_link esp_websocket_client esp_wifi espcoredump esptool_py expat fatfs freemodbus freertos heap idf_test jsmn json libsodium log lwip main mbedtls mdns mqtt newlib nghttp nvs_flash openssl partition_table perfmon protobuf-c protocomm pthread sdmmc soc spi_flash spiffs tcp_transport tcpip_adapter ulp unity vfs wear_levelling wifi_provisioning wpa_supplicant xtensa
-- Component paths: /<SOME_PATH>/Toolchain/esp-idf/components/app_trace /<SOME_PATH>/Toolchain/esp-idf/components/app_update /<SOME_PATH>/Toolchain/esp-idf/components/asio /<SOME_PATH>/Toolchain/esp-idf/components/bootloader /<SOME_PATH>/Toolchain/esp-idf/components/bootloader_support /<SOME_PATH>/Toolchain/esp-idf/components/bt /<SOME_PATH>/Toolchain/esp-idf/components/cbor /<SOME_PATH>/Toolchain/esp-idf/components/coap /<SOME_PATH>/Toolchain/esp-idf/components/console /<SOME_PATH>/Toolchain/esp-idf/components/cxx /<SOME_PATH>/Toolchain/esp-idf/components/driver /<SOME_PATH>/Toolchain/esp-idf/components/efuse /<SOME_PATH>/Toolchain/esp-idf/components/esp-tls /<SOME_PATH>/Toolchain/esp-idf/components/esp32 /<SOME_PATH>/Toolchain/esp-idf/components/esp_adc_cal /<SOME_PATH>/Toolchain/esp-idf/components/esp_common /<SOME_PATH>/Toolchain/esp-idf/components/esp_eth /<SOME_PATH>/Toolchain/esp-idf/components/esp_event /<SOME_PATH>/Toolchain/esp-idf/components/esp_gdbstub /<SOME_PATH>/Toolchain/esp-idf/components/esp_http_client /<SOME_PATH>/Toolchain/esp-idf/components/esp_http_server /<SOME_PATH>/Toolchain/esp-idf/components/esp_https_ota /<SOME_PATH>/Toolchain/esp-idf/components/esp_https_server /<SOME_PATH>/Toolchain/esp-idf/components/esp_local_ctrl /<SOME_PATH>/Toolchain/esp-idf/components/esp_netif /<SOME_PATH>/Toolchain/esp-idf/components/esp_ringbuf /<SOME_PATH>/Toolchain/esp-idf/components/esp_rom /<SOME_PATH>/Toolchain/esp-idf/components/esp_serial_slave_link /<SOME_PATH>/Toolchain/esp-idf/components/esp_websocket_client /<SOME_PATH>/Toolchain/esp-idf/components/esp_wifi /<SOME_PATH>/Toolchain/esp-idf/components/espcoredump /<SOME_PATH>/Toolchain/esp-idf/components/esptool_py /<SOME_PATH>/Toolchain/esp-idf/components/expat /<SOME_PATH>/Toolchain/esp-idf/components/fatfs /<SOME_PATH>/Toolchain/esp-idf/components/freemodbus /<SOME_PATH>/Toolchain/esp-idf/components/freertos /<SOME_PATH>/Toolchain/esp-idf/components/heap /<SOME_PATH>/Toolchain/esp-idf/components/idf_test /<SOME_PATH>/Toolchain/esp-idf/components/jsmn /<SOME_PATH>/Toolchain/esp-idf/components/json /<SOME_PATH>/Toolchain/esp-idf/components/libsodium /<SOME_PATH>/Toolchain/esp-idf/components/log /<SOME_PATH>/Toolchain/esp-idf/components/lwip /<SOME_PATH>/blehr/main /<SOME_PATH>/Toolchain/esp-idf/components/mbedtls /<SOME_PATH>/Toolchain/esp-idf/components/mdns /<SOME_PATH>/Toolchain/esp-idf/components/mqtt /<SOME_PATH>/Toolchain/esp-idf/components/newlib /<SOME_PATH>/Toolchain/esp-idf/components/nghttp /<SOME_PATH>/Toolchain/esp-idf/components/nvs_flash /<SOME_PATH>/Toolchain/esp-idf/components/openssl /<SOME_PATH>/Toolchain/esp-idf/components/partition_table /<SOME_PATH>/Toolchain/esp-idf/components/perfmon /<SOME_PATH>/Toolchain/esp-idf/components/protobuf-c /<SOME_PATH>/Toolchain/esp-idf/components/protocomm /<SOME_PATH>/Toolchain/esp-idf/components/pthread /<SOME_PATH>/Toolchain/esp-idf/components/sdmmc /<SOME_PATH>/Toolchain/esp-idf/components/soc /<SOME_PATH>/Toolchain/esp-idf/components/spi_flash /<SOME_PATH>/Toolchain/esp-idf/components/spiffs /<SOME_PATH>/Toolchain/esp-idf/components/tcp_transport /<SOME_PATH>/Toolchain/esp-idf/components/tcpip_adapter /<SOME_PATH>/Toolchain/esp-idf/components/ulp /<SOME_PATH>/Toolchain/esp-idf/components/unity /<SOME_PATH>/Toolchain/esp-idf/components/vfs /<SOME_PATH>/Toolchain/esp-idf/components/wear_levelling /<SOME_PATH>/Toolchain/esp-idf/components/wifi_provisioning /<SOME_PATH>/Toolchain/esp-idf/components/wpa_supplicant /<SOME_PATH>/Toolchain/esp-idf/components/xtensa
-- Configuring done
-- Generating done
-- Build files have been written to: /<SOME_PATH>/blehr/build

That's pretty strange but i update toolchain to esp-2020r2 and now it works well.
So, i think the problem MAYBE appear in fresh install but i made fresh install again in attempts to make it works and it didn't help.

At this moment seems like problem on our side. If it will appears again i will create issue or reopen this,
Thx for fast answer

@thecashit Thanks for the update. Yes, please reopen if it reappears.
However I just noticed something, that you were using the archive ZIP file.
You must have downloaded the esp-idf-v4.1-rc.zip file less than two hours after it was released, and we have a known issue (#3265) that CMake can get into an infinite build loop if some files are newer than the current system time. (This seems like something in CMake, so far it's proven hard for us to fix.)
The timestamps in the esp-idf-v4.1-rc.zip are all around 2020-07-30 19:15 - ZIP format doesn't include any time zone information.
What zip extraction tool did you use on MacOS, and is it possible that the local time when v4.1-rc was not working was before this time (locally) and then it started working after this time?

@projectgus
So, we have a problem with BLE & Wi-Fi coexistence(issue , sadly not solved) and it its blocker for us so i downloaded 4.1-rc immediately after getting email about new version.
Out GMT offset is +5 so it it most
It looks like this is exactly the behavior that you describe. The next attempts were about 5 hours later and could just coincide with the Toolchain downgrade

Hi @thecashit ,
Sorry to hear that the coexistence issue wasn't resolved, but glad to have figured this out.
Will see what we can do about creating the zip with overriden timestamps or timezone so they're in the past for everyone.

@projectgus Thnx for you work!

Quick update, I'm afraid it doesn't look like the zip tools we have available (info-zip and 7zip) give us a way to override the timestamp when making the zip.
So this is effectively a duplicate of the build system timestamp problem #3265 . Will have to look again for a solution to that issue.

Can someone explain how to downgrade to xtensa installed from 4.1-beta2 version? This seems to be the current workaround to the issue. I am getting this same issue when trying to build the LCD example on the ESP32-S2 Kaluga board.

Hi @lambrou,
If your system has the correct time set (i.e. not months in the past) then the issue mentioned here should only happen if you grab an ESP-IDF release zip file within 24 hours of when it was made, and should fix itself within 24 hours once the timestamps for the files in the zip move to the "past".
We haven't released anything in the past few days, so it seems likely the issue you're looking at is different. Could you please open a new ticket and supply as much information as possible about versions, build output, etc?

@thecashit Thanks for the update. Yes, please reopen if it reappears.
However I just noticed something, that you were using the archive ZIP file.
You must have downloaded the esp-idf-v4.1-rc.zip file less than two hours after it was released, and we have a known issue (#3265) that CMake can get into an infinite build loop if some files are newer than the current system time. (This seems like something in CMake, so far it's proven hard for us to fix.)
The timestamps in the esp-idf-v4.1-rc.zip are all around 2020-07-30 19:15 - ZIP format doesn't include any time zone information.
What zip extraction tool did you use on MacOS, and is it possible that the local time when v4.1-rc was not working was before this time (locally) and then it started working after this time?

This, in sum of a new instalation problem because of the certificates, had the problem of the whole thing. Thank you for this tip. The creation of an object can't be later than its build.

Seems like this is still an issue in latest stable when using IDF example extracted from a zip file. Simple solution is to run touch -d "2 days ago" * on all project files.


Clicking the "next track" button causes the song you were listening to "blip" before the next track starts.

This is a little weird to describe, but basically whenever I click the "Next track" button the current song stops playing while Psst loads the next song (which takes about 1s or less, no real problems there).
the issue is that after that brief loading pause, there's a like fraction-of-a-second spurt of audio from the previous track, before the next track starts.
this doesn't occur when a song ends and it moves onto the next song in the list, only when clicking "Next track"
edit: it also occurs when selecting a new song (simply clicking on a song in your library to play, while a song is playing)
Arch Linux, psst-git r561.0292319-1

Duplicate of #251


Application Question

Hi,  Im not sure if this is the correct venue to ask this so I will apologize in advance if it's not but have anyone developed a loan servicing/management type application with the serenity framework?
Thanks

since Issues are supposedly for Serenity-code specific issues, you get limited answers. But you can try with the community at the Slack channel. (Invite yourself at https://serenityslackinvitation.herokuapp.com) =)


[Bug]: not fully responsive

Bug Description
It lacks the responsiveness in small screen sizes.
Provide a detailed description of the bug
The whole website lacks the responsiveness in small screen sizes like mobile, tablet.
I can fix this by using media queries and css styling properties. I want to work on this and make the whole website responsive.
Please assign me this task with hacktoberfest and gssoc-ext tag.
Thankyou!
Expected Behavior
The whole website should have to be responsive it improves the user experience.
What browsers are you seeing the problem on?
No response
Put here any screenshots or videos (optional)
Problem's screenshots

By submitting this issue, you agree to

[X] I agree to follow this project's Code of Conduct
[X] I’ve read all the issues in the issue section, and this has not been reported yet.

Other Information

[X] I'm a GSSoC '24 Extended contributor
[X] I'm a Hacktoberfest '24 contributor
[ ] I am willing to work on this issue (optional)

Feature Description:
Implementing the responsiveness of the site for the best user experience so that the user can visit and use the site using device.
Provide a detailed description of the feature
Using css and tailwindcss to grasp easy and efficient ui responsiveness for PC, Laptop, Tablet, Mobile devices
Thankyou!
By submitting this issue, you agree to
I agree to follow this project's Code of Conduct
I’ve read all the issues in the issue section, and this feature has not been proposed yet.
Other Information
I'm a GSSoC '24 Extended contributor
I'm a Hacktoberfest '24 contributor
I am willing to work on this feature


feat(search): Rangeify search matches for remote treesitter with prelabelling

The Search matcher can take a rangeify function that can map the search match to one or more ranges that are all labelled for jumping (or selecting)

May want to make this able to return zero ranges to skip the current match too

remote_ts mode is added that uses the treesitter containing nodes to map search matches to treesitter nodes, thus we can search and select treesitter nodes in one fell swoop (the labels are shown earlier than the current example in the readme)
Also the remote plugin is enhanced so if the jump step has config.jump.pos = "range" then there is no second operator-pending mode to select the textobject, it directly uses the range of the jump step.

One open question is what happens to equal ranges in the labelling step? Is that wasting labels?
Maybe the rangeify argument should go in search.rangeify becuase it is modifying the behaviour of searching?

That's a great idea! I'll look into it!

It works using the example, I think the only inconvenience is the search matches are not highlighted. There would have to be a way to distinguish the range for jumping and the range for highlighting. That affects way more of the code than I am comfortable touching

I've refactored the flash code a bit to make it easier to implement something like your pull request.
I think it makes more sense to do something like the below? Instead of adding a new rangeify option?
The code below is not ideal yet and also doesn't highlight patterns yet, but I have to go here in a bit.
local Treesitter = require("flash.plugins.treesitter")
local Search = require("flash.search")
local Matcher = require("flash.search.matcher")
local Remote = require("flash.plugins.remote")

---@class Flash.Treesitter2: Flash.Matcher
---@field search Flash.Search
local R = {}

function R.new(win, state)
  local self = setmetatable(Matcher.new(win), { __index = R })
  self.search = Search.new(win, state)
  return self
end

function R:get(opts)
  self.matches = {}
  for _, m in ipairs(self.search:get(opts)) do
    vim.list_extend(self.matches, Treesitter.get_nodes(self.win, m.pos))
  end
  return self.matches
end

function R:labels(labels)
  return self.search:labels(labels)
end

setmetatable(R, {
  __call = function(_, win, state)
    return R.new(win, state)
  end,
  __index = Matcher,
})

vim.keymap.set({ "n", "x", "o" }, "R", function()
  Remote.save()
  require("flash").jump({
    matcher = R,
    jump = { pos = "range" },
    highlight = {
      label = { before = true, after = true, style = "inline" },
      matches = false,
    },
  })
  Remote.restore()
end)

That works too, and probably more flexible if the user wants to do other things, but I think the most common case by far will end up being taking the Search results and flat_map-ing it by some function. This is quite a bit of boilerplate for that.
maybe flash.search could have a function like mapped(function) and the result can be assigned to matcher directly

Oh highlighting the pattern is somewhat easier than I thought, I was thinking the FlashMatch class can have an optional field highlight_range that contains {pos, end_pos} and you use match.highlight_range or match

Yeah that makes sense. I'll see if I can add something like that!
I've also noticed a very weird issue where the remote window's cursor position gets set to the cursor position of the current window. I've been looking into it quite a bit and I don't think it's flash doing this.
I've currently added a hack to remote to also restore the remote view, but that's not ideal.
Is this something that you also have seen?

I think I haven't noticed it only because I haven't used across windows yet

I refactored some of the code to make this all even easier:

a matcher function is now hooked into Matcher.get, so it can use the from/to opts
the label skip code has been moved to the labeler class, so it's no longer needed to do anything special for this

Updated code example:
local Treesitter = require("flash.plugins.treesitter")
local Search = require("flash.search")
local Remote = require("flash.plugins.remote")

vim.keymap.set({ "n", "x", "o" }, "R", function()
  Remote.save()
  require("flash").jump({
    matcher = function(win, state, opts)
      local search = Search.new(win, state)
      local matches = {}
      for _, m in ipairs(search:get(opts)) do
        vim.list_extend(matches, Treesitter.get_nodes(win, m.pos))
      end
      return matches
    end,
    jump = { pos = "range" },
    highlight = {
      label = { before = true, after = true, style = "inline" },
      matches = false,
    },
  })
  Remote.restore()
end)

But it doesn't work properly with multi window. Will look into that right now.

Finally was able to fix that operator pending issue in remote windows.
The regular jump code now has similar logic to remote baked in for operator mode in remote windows.
I'll refactor the code more tomorrow:

always return to the original window when doing a remote operator pending op. I can't think of any use-case where you'd want to stay at the remote window after the op
the remote module, should now only do what it was originally created for. The rest is already handled in the normal jump code

I refactored some of the code to make this all even easier:
* a matcher function is now hooked into `Matcher.get`, so it can use the from/to opts

* the label skip code has been moved to the labeler class, so it's no longer needed to do anything special for this

Updated code example:
local Treesitter = require("flash.plugins.treesitter")
local Search = require("flash.search")
local Remote = require("flash.plugins.remote")

vim.keymap.set({ "n", "x", "o" }, "R", function()
  Remote.save()
  require("flash").jump({
    matcher = function(win, state, opts)
      local search = Search.new(win, state)
      local matches = {}
      for _, m in ipairs(search:get(opts)) do
        vim.list_extend(matches, Treesitter.get_nodes(win, m.pos))
      end
      return matches
    end,
    jump = { pos = "range" },
    highlight = {
      label = { before = true, after = true, style = "inline" },
      matches = false,
    },
  })
  Remote.restore()
end)

So I used this config and it works but when I initially launch neovim and use just R it selects the range and returns to original jump location in visual mode selecting more than desired. After doing an operation like cR it works as expected allowing me to change the range and jumping back on mode change. Strangely, after doing an operation now normal R starts working as expected and only selects the range.

I just pushed a bunch of changes and the issue you're describing should also be fixed by that.
@morfert updated example:
vim.keymap.set({ "n", "x", "o" }, "R", function()
  require("flash").jump({
    matcher = function(win, state, opts)
      local search = Search.new(win, state)
      local matches = {}
      for _, m in ipairs(search:get(opts)) do
        vim.list_extend(matches, Treesitter.get_nodes(win, m.pos))
      end
      return matches
    end,
    jump = { pos = "range" },
    highlight = {
      label = { before = true, after = true, style = "inline" },
      matches = false,
    },
    remote_op = {
      restore = true,
    },
  })
end)

You can now also configure remote_op = {restore = true, motion = true} by default.
This will make ys behave like yr for remote operator pending operations.
So in that case, you no longer need to have a r mapping.
I actually prefer this, but that may be confusing to configure it like that by default?

I think it makes sense, I personally pretty much never found myself using leap or search in operator or visual mode in the way it normally works (extend the selection to the jump target), I'd usually jump there then use a textobject or treehopper. Having that in one key in op pending mode works really well for me. Idk how others use it though

Thanks for the help, I think this PR can be closed because everything I described and implemented can be done on master

I was a bit too quick with my changes. Options are slightly updated:
  -- options for remote operator pending mode
  remote_op = {
    -- restore window views and cursor position
    -- after doing a remote operation
    restore = false,
    -- For `jump.pos = "range"`, this setting is ignored.
    -- `true`: always enter a new motion when doing a remote operation
    -- `false`: use the window's cursor position and jump target
    -- `nil`: act as `true` for remote windows, `false` for the current window
    motion = false,
  },

So the code below will behave like yr for remote window ops only:
    require("flash").jump({
      remote_op = {
        restore = true,
        motion = nil,
      },
    })

Thanks for the help, I think this PR can be closed because everything I described and implemented can be done on master

yep, thanks. I'll look into your highlights PR in a bit!

The above example should probably set config.search.incremental = false. Actually I think it would be useful to set search.incremental = false in the default config for treesitter mode. Right now it is only hardcoded into flash.plugins.treesitter, which means that inheriting from mode = "treesitter" doesn't get that setting.


[Feature request] Move non-real-time related contents to other repository

Currently this repository contains information on real-time with PREEMPT_RT and Docker as well as a lot of information about Docker in general and particular about Docker and the Robot Operating System ROS/ROS2. The contents relating to ROS/ROS2 should be moved to a separate repository containing best practices for ROS in order to make the repository more concise.

I just created a new repository docker-for-ros that these contents will be migrated to over the next couple of days.


Thank you! migrated from cloudwatch-adapter to keda

hi Florent,
just wanted to thank you for taking the time and effort to publish this. Invaluable in our smooth migration from cloudwatch-adapter to keda. Leaving this here in case any future googlers come past
snippet: values.yaml
# URL of the default metrics provider which provides the base path, for example:
#
# defaultProviderUrl: prometheus-adapter.prometheus.svc.cluster.local
defaultProviderUrl: k8s-cloudwatch-adapter.custom-metrics.svc.cluster.local

# A list of the metrics providers you want to support, for example:
#
metricsProviders:
- name: keda
  prefix: "s\\d" #s0-my-service-scaler-metric #note the first \ is for yaml
  strip_prefix: false
  service: keda-operator-metrics-apiserver.keda.svc.cluster.local

Hey @afirth , that's great to hear, I'm happy this project helped you! :)


Transfer multiple inputs rebase

Rebase of #120
Don't know if working appropriately.

Codecov Report

Merging #125 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master    #125   +/-   ##
======================================
  Coverage    82.2%   82.2%
======================================
  Files          21      21
  Lines         281     281
======================================
  Hits          231     231
  Misses         50      50

Impacted Files
Coverage Δ

src/transaction/makeTransferTransaction.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

As there are breaking changes, we will need to update everything. So I propose to handle this PR next week after we first create a new release of the JS driver including the metadata search: #124 for this week. So:

This week new release of JS driver including and five-bells-conditions repository #124
Next week new realese of JS driver including this PR #125 . Update of any tutorial is needed

When creating a transfer transaction the user has to specify the 'transaction' and the 'output_index' that he/she is spending. For example:
Transaction.makeTransferTransaction(
        [{ tx: transferTx, output_index: 0 }],
        [aliceOutput],
        metaData
    )

Travis do not mark this as an error, but maybe we want to change to camelcase:
Transaction.makeTransferTransaction(
        [{ tx: transferTx, outputIndex: 0 }],
        [aliceOutput],
        metaData
    )

Anyways I would like to merge this PR. Is needed for sub-divisible assets. Can you @jernejpregelj check it?


Updates ?

Hi tehre, do u plan to release some updates on popunder ?
Tnx

Potentially but there's no such plan for now.

Old => closing


HADOOP-17742. fix distcp fail when copying to ftp filesystem

There is more Detailed information.
https://issues.apache.org/jira/browse/HADOOP-17742#

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 34s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
35m 17s

trunk passed

+1 :green_heart:
compile
0m 33s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 31s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
0m 27s

trunk passed

+1 :green_heart:
mvnsite
0m 40s

trunk passed

+1 :green_heart:
javadoc
0m 30s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 28s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
spotbugs
0m 49s

trunk passed

+1 :green_heart:
shadedclient
13m 56s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 27s

the patch passed

+1 :green_heart:
compile
0m 25s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 25s

the patch passed

+1 :green_heart:
compile
0m 22s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
0m 22s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 16s

the patch passed

+1 :green_heart:
mvnsite
0m 25s

the patch passed

+1 :green_heart:
javadoc
0m 20s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 18s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
spotbugs
0m 48s

the patch passed

+1 :green_heart:
shadedclient
13m 45s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
20m 41s

hadoop-distcp in the patch passed.

+1 :green_heart:
asflicense
0m 35s

The patch does not generate ASF License warnings.

93m 50s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3067/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3067

JIRA Issue
HADOOP-17742

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux ba7d4d3a0ded 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / fe796ebc9e484f225997ba15b9905447072e26e4

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3067/1/testReport/

Max. process+thread count
546 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3067/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

This is problematic, I will resubmit.


PEP257 doc strings cleanup needed

pip install pep257
pep257 khmer

Going to work on this …

Fixed by #936


unable to resolve base groovy classes

The server is unable to resolve base groovy classes or annotations, but it is able to resolve grapes which have been installed in ~/.groovy/grapes.
I'm using groovy from homebrew brew install groovy which installs groovy in /usr/local/Cellar/groovy/2.5.8. I have tried to set GROOVY_HOME without success.
For example:
@Grapes([
        @Grab('mysql:mysql-connector-java:8.0.11'),
        @Grab('joda-time:joda-time:2.10'),
        @Grab('org.slf4j:slf4j-api:1.7.25'),
        @Grab('ch.qos.logback:logback-classic:1.2.3'),
    @Grab('org.mongodb:mongodb-driver:3.7.1'),
    @Grab('org.mongodb:bson:3.8.0'),
    @Grab('javax.xml.bind:jaxb-api:2.2.3'),
    @Grab('org.apache.commons:commons-lang3:3.7'),
    @Grab('com.mashape.unirest:unirest-java:1.4.9'),
    @GrabConfig(systemClassLoader = true)
])

....

import groovy.transform.Field

I get:
unable to resolve class groovy.sql.Sql
 @ line 1, column 1.

unable to resolve class Grapes ,  unable to find class for annotation
 @ line 1, column 1.

unable to resolve class Grapes ,  unable to find class for annotation
 @ line 1, column 1.

and
unable to resolve class groovy.transform.Field
 @ line 17, column 1.

The Groovy language server needs to be configured with a list of paths that can either be to a .jar file or a directory containing .jar files.
See here:
https://github.com/prominic/groovy-language-server/blob/master/src/main/java/net/prominic/groovyls/GroovyServices.java#L179
and here:
https://github.com/prominic/groovy-language-server/blob/master/src/main/java/net/prominic/groovyls/config/CompilationUnitFactory.java#L116
Here's an example configuring the language server from coc.nvim. I believe project relative paths will also work.
{
  "languageserver": {
    "groovy": {
      "trace.server": "off",
      "command": "java",
      "args": [
        "-jar",
        "/path/to/groovy-language-server/build/libs/groovy-language-server-all.jar"
      ],
      "filetypes": ["groovy"],
      "settings": {
        "groovy": {
          "classpath": [
            "/path/to/.groovy/grapes/org.codehaus.groovy/groovy-sql/jars/groovy-sql-3.0.1.jar",
            "/path/to/.groovy/grapes/org.codehaus.groovy/groovy/jars/groovy-3.0.1.jar",
            "/path/to/groovy/libs",
            "./libs"
          ]
        }
      }
    }
  }
}

I finally had time to figure out how to do this in Emacs with lsp-mode. I actually just added support for it:
https://github.com/emacs-lsp/lsp-mode/pull/2139
Closing.


no AD/LDAP login after upgrading from 4.6.0-0.okd-2020-12-12-135354 to 4.6.0-0.okd-2021-01-17-185703

Describe the bug
I am upgrading a cluster from 4.6.0-0.okd-2020-12-12-135354 to 4.6.0-0.okd-2021-01-17-185703. The cluster has been upgraded successfully from earlier releases already 7 times.
I have another problem with this cluster - the upgrade does not succeed, it is still stuck with the MCO not progressing. But this should IMO not affect the authentication.
For the MCO problem I opened another issue, will link it below.
Any login attempt fails like this:
$ oc login --server=https://api.devqs.ars.de:6443 -u user -p password
Error from server (InternalError): Internal error occurred: unexpected response: 500

Version
4.6.0-0.okd-2020-12-12-135354 to 4.6.0-0.okd-2021-01-17-185703
How reproducible
always
Log bundle
Unfortunately, must-gather fails:
# oc adm must-gather
[must-gather      ] OUT Using must-gather plugin-in image: quay.io/openshift/okd-content@sha256:c46390d74c9ac6152264da87b5667eacc42871cf4eb9ab444cd953ae56b81b07
[must-gather      ] OUT namespace/openshift-must-gather-lb75x created
[must-gather      ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-zz8lq created
[must-gather      ] OUT pod for plug-in image quay.io/openshift/okd-content@sha256:c46390d74c9ac6152264da87b5667eacc42871cf4eb9ab444cd953ae56b81b07 created
[must-gather-vfwbk] OUT gather did not start: Get https://api.devqs.ars.de:6443/api/v1/namespaces/openshift-must-gather-lb75x/pods/must-gather-vfwbk: unexpected EOF [must-gather      ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-zz8lq deleted
[must-gather      ] OUT namespace/openshift-must-gather-lb75x deleted
error: gather did not start for pod must-gather-vfwbk: Get https://api.devqs.ars.de:6443/api/v1/namespaces/openshift-must-gather-lb75x/pods/must-gather-vfwbk: unexpected EOF

look at the logs for the pods in openshift-authentication.  That should probably give you an idea what's failing...
I've had issues with certs not have SAN entries and had to regenerate certs for my LDAP servers that I authenticate with.
https://github.com/openshift/okd/issues/443

look at the logs for the pods in openshift-authentication.  That should probably give you an idea what's failing...
I've had issues with certs not have SAN entries and had to regenerate certs for my LDAP servers that I authenticate with.
https://github.com/openshift/okd/issues/443

Yes, this was the case. The DC's certificate did not have SAN attribute.
Now fixed.
Thanks!

Yes, this was the case. The DC's certificate did not have SAN attribute.
Now fixed.
Thanks!

awesome!

awesome!


error:tf_sampling_so.so: undefined symbol: _ZTIN10tensorflow8OpKernelE

when I run command_train_v2.sh ,I get this mistake "tf_sampling_so.so: undefined symbol: _ZTIN10tensorflow8OpKernelE".I have already  modified the file "tf_sampling_comling.sh".By the way ,I run these files in anaconda virtual environment python2.7,tensorflow-gpu1.13.0.

I am getting the same error when i am compiling on windows environment. What could be the reason ?


Create a new Referral Partner page

Epic
No response
Description
We want to be able to incent companies to recommend FlowForge to their customers. Therefore we are going to introduce a referrnal program.
To accept partner request, we need a web page added to our site that describes the program and includes a Hubspot form to accept contact information requests.
The page should be linked in the Company section of the footer.
Acceptance Criteria
No response

Here is the proposed text for the page.
Title: Introducing the FlowForge Referral Program
Many companies are realizing the benefits of using FlowForge for their Node-RED development. We want to encourage them to recommend FlowForge to other potential users. That's why we're excited to offer a referral program that rewards others for spreading the word about our platform.
If you're a current FlowForge customer, you can earn rewards by referring other companies to use our platform. For each referral that leads to a new customer, you'll receive a referral bonus.
Sign-up today to receive more details of our FlowForge Referral Program.

Here is the Hubspot form code.


Prose no longer loads non-personal repositories, github is giving 404

Up until very recently (last day or so), prose loaded repositories from organizations you're a part of just fine. Now prose cannot load them and the github endpoint that prose is trying to hit (https://api.github.com/repos/[org]/[repo]) gives a 404. Personal repositories still work. Anybody experiencing this/know what's going on?

@andrew-luminal confirm that you're logged in?

My bad, this was an internal org issue -- we turned on required third-party at the org level but that wasn't communicated to the whole team. Sorry to pollute this thread!

No problem, thanks for using Prose!


Use maven-antrun-plugin to remove data dir instead of maven-clean-plu…

…gin so that mvn clean would remove target dir

Thanks for the PR it has been merged. Do you mind closing this?

Thanks! closing


Proof of concept image import/translation workflows.

Codecov Report

Merging #90 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #90   +/-   ##
=======================================
  Coverage   79.27%   79.27%
=======================================
  Files          20       20
  Lines        1549     1549
=======================================
  Hits         1228     1228
  Misses        246      246
  Partials       75       75

Continue to review full report at Codecov.

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


java: Dedup the version string in all Maven configurations.

After this change, the version is defined in a single place in the Maven config.

Looks like this isn't working by design: http://stackoverflow.com/questions/10582054/maven-project-version-inheritance-do-i-have-to-specify-the-parent-version
Instead, we should use a release plugin to update the version everywhere.


fix(1467, 1623): improve number inputs

Description
A continuation of work in #1647 to improve user experience for number inputs by

Adding input=decimal to use a more accessible keyboard on iOS (#1467 )
Using built-in html validation of number type to enforce that numbers are integers, and convert any float inputs (if they somehow get past client-side validation) to Long on the back end (#1623)
Validate min and max client-side using built-in html validation before submitting

Screenshots:
On iOS 12 before adding decimal input:

On iOS 12 after adding decimal input:

Validation for integer input:

Validation for min/max:

Checklist

[x] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)
Fixes #1467; Fixes #1623;

I left some high level comments, but in general the Number type is defined as an Integer as it, so we should keep it that way without a broader discussion to redefine it, or differentiate Int vs float.
go/uat-question-requirements ->
https://docs.google.com/document/d/1HYVHBno6dk7fmS5w6V6Y3jxERHGfDoQKTtzBZr27Y6o/edit#

Updatied this to use the same onSubmit validation method as the other question types in validation.ts. Invalid input now looks like this (feel free to suggest a better error message):

This PR still relies on the built-in HTML validation for the number input type to enforce min and max instead of rendering those errors in the error div. Would it be better to write our own client-side validation?

Updated this to use the same onSubmit validation method as the other question types in validation.ts. Invalid input now looks like this (feel free to suggest a better error message):
This PR still relies on the built-in HTML validation for the number input type to enforce min and max instead of rendering those errors in the error div. Would it be better to write our own client-side validation?

I don't really have an opinion, so whatever looks better to you.

Looking good!

Just wanted to make sure you saw the comments in number.ts and ApplicantData.java

Just wanted to make sure you saw the comments in number.ts and ApplicantData.java

I reverted the changes in ApplicantData.java and removed number.ts (moved the validation logic to validation.ts instead) so I can't see the comments anymore.


Automated cherry pick of #2697: Fix service traffic requiring SNAT

Cherry pick of #2697 on release-1.3.
#2697: Fix service traffic requiring SNAT
For details on the cherry pick process, see the cherry pick requests page.

/test-all

Codecov Report

Merging #2703 (d37815a) into release-1.3 (aa6218f) will decrease coverage by 19.47%.
The diff coverage is 0.00%.

@@               Coverage Diff                @@
##           release-1.3    #2703       +/-   ##
================================================
- Coverage        60.50%   41.02%   -19.48%
================================================
  Files              285      158      -127
  Lines            23006    19259     -3747
================================================
- Hits             13919     7901     -6018
- Misses            7588    10610     +3022
+ Partials          1499      748      -751

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
41.02% <0.00%> (-0.05%)
:arrow_down:

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


Azure PowerShell task no longer persists Azure auth context when the task completes

Type: Bug
Task Name: AzurePowerShell
Environment
Azure Pipelines
https://dev.azure.com/iqmetrix/RQ/_releaseProgress?_a=release-environment-logs&releaseId=24564&environmentId=104457
Hosted agent, using Azure Pipelines and ubuntu-18.04
Issue Description
Prior to PR #13239 you could use the Azure PowerShell task to authenticate with your Azure subscription and establish a context, and then subsequent tasks in the pipeline would also be authenticated via that context. The PR changed the scope of the context, so now any pipelines relying on the context to already exist break, saying "Run Connect-AzAccount to login".
To reproduce this, use the Azure PowerShell task to authenticate with the Azure subscription, and then add a regular PowerShell task to your pipeline and have it access resources in the subscription, such as reading from Key Vault. This worked fine in v4.171.1 of the AzurePowerShell task, but no longer works in v4.173.0, and I believe the the mentioned PR is responsible for it.
Unfortunately Azure DevOps does not allow us to use previous versions of the task, so we can't rollback to the working version.
Task logs
I've attached a zip with the log files. The tasks of interest are "3_Login to Azure.log" and "22_Retrieve AKV Secretes and Create Folder.log".
ReleaseLogs_24564.zip
Error logs
The task itself does not return any errors, it simply does not behave as it previously did. It used to leave the Azure context in tact, but now the context disappears once the Azure PowerShell task completes.

@20shivangi to address this

I'll mention that I understand PR #13239 increases security, but at the same time it introduces a breaking change that can break existing pipelines. Ideally the user would be able to choose the scope on the task UI; default it to the more secure process scope, but still allow it to use the previous user-scope behaviour so that users can get their pipelines back up and running quickly. Bumping the task version would be a good idea as well.

@deadlydog Earlier we were using set-azcontext command in the scope of currentUser, due to which all the non-azureps tasks were able to use the Az context so we limited the context to the scope of process. But due to this, some pipelines started breaking where people were using az context created by azureps task.
So for now, we have reverted this change back. Our change has started being deployed,  it will reach all the rings in 2-3 days.
Please wait for sometime. Thanks for your patience.

Closing it as the issue has been fixed, feel free to re-open if face any issue.


Footer submenu scrolling issue

Hello, why does the menu slide at the bottom even though there are spaces on the bottom menu edges in the footer, how do I edit it, I want it to stay organized.

You can try to inject the following styles in the Ghost Admin:
<style>
#ghost-portal-root iframe {
  right: -16px;
}
</style>

Please next time open a different issue if it's not related to the same topic.

You can try to inject the following styles in the Ghost Admin:
<style>
#ghost-portal-root iframe {
  right: -16px;
}
</style>

Please next time open a different issue if it's not related to the same topic.

unfortunately it didn't work

It seems that you need to add !important to it, I updated my comment.

ok now thank you very much


feat: add safeHash function for producing minimal but non-colliding hashes

More I'm thinking, this is probably not the best idea. Considering hash of similar inputs is so rarely happening with this new util we have two downsides:

Hash output is not consistent! Depending on what previous inputs we used to call function, result can differ to avoid collision with previous results (hash(x) is not always y!)
It can implicitly cause memory leaks when calling with many different inputs.

Moving away to use a more collision-resistant hash instead.


brpop raise redis.exceptions.TimeoutError if socket_timeout is less than brpop timeout

I'm using redis as a queue, and the StrictRedis client is create with socket_timeout set to 5, When I 'brpop' to wait for some message, it always raise redis.exceptions.TimeoutError after 5 seconds.
I am aware of some workarounds, but all feels wrong to me:

do not set socket_timeout
set timeout on brpop smaller than socket_timeout
catch TimeoutError for brpop, and start brpop again (will this cause current connection be marked as bad and thrown away?)
have another StrictRedis client with no socket_timeout, dedicated to brpop operation only

So is it possible for the client to temporary overwrite the socket read timeout for the connection which will be used for block operation like brpop. Or there is already some other workaround I am not aware of.
Thanks
Here is the example:
>>> import redis
>>> r = redis.StrictRedis(socket_connect_timeout=5, socket_timeout=5)
>>> r.brpop('abcd', timeout=100)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "build/bdist.linux-x86_64/egg/redis/client.py", line 1166, in brpop
  File "build/bdist.linux-x86_64/egg/redis/client.py", line 565, in execute_command
  File "build/bdist.linux-x86_64/egg/redis/client.py", line 577, in parse_response
  File "build/bdist.linux-x86_64/egg/redis/connection.py", line 569, in read_response
  File "build/bdist.linux-x86_64/egg/redis/connection.py", line 224, in read_response
  File "build/bdist.linux-x86_64/egg/redis/connection.py", line 162, in readline
  File "build/bdist.linux-x86_64/egg/redis/connection.py", line 133, in _read_from_socket
redis.exceptions.TimeoutError: Timeout reading from socket

The answer depends on why you're using socket_timeout. If you're only interested in preventing socket.connect from hanging indefinitely, then take a look at the socket_connect_timeout argument instead. socket_connect_timeout was introduced in 2.10.0.
If you're using socket_timeout to limit the amount of time waiting on socket.recv, then that's at odds with the BRPOP operation. In this case, I'd suggest using a separate client instance with a different socket_timeout setting.

Thanks for your response.
Hanging on recv, if something bad happened to the socket, may cause trouble to my program, so I have to set socket_timeout, or maybe socket_keepalive is enough?
Anyway, having another instance of StrictRedis is my best choice for now, I think.


Connection Priority

How can I change priority?
Tried to use gatt.requestConnectionPriority(1) after services discovered and then stop receiving messages from BLE.

There are currently no plans to implement support for priority in this codebase.


Metadata & Image on sdk.mint()

hi.
how can i set image for a mint request.
also i would like to know how is for metadata & attributes?

solved!
according to rarible documentation, meta data of an item will fetch from IPFS url that set in the mint request
so i used Pinata sdk to uploading meta data json using pinJSONToIPFS method and i set uri property in mintResponse.submit request to IPFS url that Pinata given to me.
also i used rarible.nft.preprocessMeta to verify meta data that i give to pinJSONToIPFS.

Hey @4myr, hope you are doing well!
I have a question about rarible.nft.preprocessMeta. How did you use that function, which args did you pass? Thanks!


fix: rename appId to clientId

Codecov Report
Base: 82.10% // Head: 82.10% // No change to project coverage :thumbsup:

Coverage data is based on head (8dedb3a) compared to base (91c39e1).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #155   +/-   ##
=======================================
  Coverage   82.10%   82.10%
=======================================
  Files          28       28
  Lines        2386     2386
=======================================
  Hits         1959     1959
  Misses        307      307
  Partials      120      120

Impacted Files
Coverage Δ

driver/management.go
100.00% <ø> (ø)

driver/driver.go
90.83% <100.00%> (ø)

driver/grpc.go
85.52% <100.00%> (ø)

driver/http.go
77.37% <100.00%> (ø)

driver/internal.go
74.60% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Upgrade node version

Hi @tiangolo !
Thanks for this  image which is now part of my workflow :+1:
I think it would be nice to get node 11 and node 12 versions for this image. I don't think it requires a lot of modifications, but i don't know how to test everything works as expected with non latin characters (working from France on european projects only).

Thanks, good idea. I'll try to do it.

Angular CLI 8+ also does not work with the current release in Docker hub. It uses Node 10.5 - but Angular CLI 8 requires 10.9 or later (latest today is 10.16).
It would be great if you could make a new/updated build of the current version also.

Ran into the same issue today trying to upgrade Angular and realizing the latest version of this image doesn't support Angular 8+

Thanks! And sorry for the long delay. :see_no_evil:
I no longer use nor recommend this Docker image, I think you are much better off building a Docker image yourself, so I updated all the docs to explain how to do it: https://github.com/tiangolo/node-frontend
The only extra step is creating and copying a simple nginx.conf file that you can copy-paste.
Given that, I'll now close this one. But thanks for the interest! :coffee:


Kitematic Windows 10 - Not downloading Mongo Container

Expected behavior
+New
Select "Create" for new container
Downloads container
Actual behavior
The container starts to download, and then...
We're sorry, there seems to be an error
context canceled
Information about the Issue
Windows 10 Pro
Kitematic
Trying to install mongo and mongo-express containers

Please look at
https://github.com/docker/kitematic/issues/4214
for what seems to be the same issue.


Integration with hid-rdf

Hi there! I have discovered this library through https://usb.org/sites/default/files/hutrr109-soc_1.pdf , I wonder where else I could have found this earlier 😅
I have a complementary library to this one: hid-rdf
Its end goal is similar to that of Waratah, but it tries to achieve all of it using modern C++ (plus a hint of Python to generate usage pages code). Some nice things I have achieved with the hid-rdf library:

it allows creating HID report descriptor building blocks (by using template parameters) that are reusable in different compositions
it is a standalone C++ library that can serve for both host and device side HID report descriptor operations
it supports compile-time verification and attribute detection (max report lengths, max report ID, number of TLCs) of HID report descriptors

I wonder if it could be used by Waratah in some way. Let me know what you think.

Yes, the roll-out for this tooling has been relatively slow; particularly since Report-Descriptors are one of those things that is only done once in a project.
Thanks mate, hid-rdf looks really neat!  As you say, it looks like hid-rdf tries to solve the same problem, but in a different way; so it's not obvious to me how/if these projects could leverage each other.
As an aside, it looks like you're generating the HUT by hand.  Since HUT1.3, the PDF now includes the tables as a JSON attachment.  Parsing/referencing this I reckon will be much more convenient.  (An upcoming Waratah feature will parse this attachment directly from the PDF)


Remove old ui transaction

remove old transaction stuff that will be replaced by transactions modal.
stubbed out new get user transactions action to get account transactions from augur-node, it's currently not used.
it can be wired up later.

This pull request fixes 1 alert when merging dca5a1c9d9ea8f568a8874e1538b6695ff5a014d into ff65dacaaee21d6b442cacb0278512853b97005b - view on LGTM.com
fixed alerts:

1 for Superfluous trailing arguments

Comment posted by LGTM.com

This pull request fixes 1 alert when merging 9ec9f5a1ae4261dd735bdb4c30808a1a5f05fe58 into e46c3fc89861a3893d1a292c7bb31b12fdae68fc - view on LGTM.com
fixed alerts:

1 for Superfluous trailing arguments

Comment posted by LGTM.com


[paho] update to 1.4 (Photon)

Library name: Eclipse Paho
New version number: 1.4 (Photon)
The subscription callback includes the MQTT clientid who did the publish of the message is available in 1.4, hence the request.
link to paho on github paho.mqtt.cpp

@Laro88 ,Thanks for posting this issue,I found the latest version released on paho-mqtt github is 1.3.6, but did not find version 1.4, can you provide me with the link to the latest version?

Hi @JonLiu1993.
Apologies, just saw on Paho that there (finally) was a new release, but it actually seems to be a front for one subproject being 1.4
The underlying feature with the client seems not to be included yet.


Cannot compile, error C1001

  Generating Code...
D:\1\td\td\telegram\logevent\LogEventHelper.h(47): fatal error C1001: Internal compiler error. [D:\1\td\build\tdcore.vcxproj]
  (compiler file 'd:\agent\_work\2\s\src\vctools\Compiler\Utc\src\p2\main.c', line 181)
   To work around this problem, try simplifying or changing the program near the locations listed above.
  If possible please provide a repro here: https://developercommunity.visualstudio.com
  Please choose the Technical Support command on the Visual C++
   Help menu, or open the Technical Support help file for more information

Always get that error.
I've tried compiling tdlib in the virtual machine, installing the latest VS2019 with only the English package selected, and I've tried increasing the system memory to 8GB, but to no avail.

This is an MSVC bug. There is a workaround for it in the latest version. You need to ignore git checkout ... line in the build instructions to build the latest version.

It works, thank you!


Update Virtualbox to 5.2.8

DevSuite should offer to install latest version of Virtualbox available now which is 5.2.8

Resolved with https://github.com/redhat-developer-tooling/developer-platform-install/pull/1312.


explicitly remove ember-source from ember-try scenarios that rely on bower

I opened up 234 in ember-try when exploring addon-docs for this library. No one's answered me yet, so I don't know what the consensus on this behavior is, but I think in the meantime we should drop this into our scenarios to ensure that we are in fact testing what we think we are testing.
I've checked and other libraries that test against ember < 2.12 where you must use bower and they also use the ember-try option that explicitly removes a package. ember-bootstrap, ember-qunit, ember-cli-mirage to name a few of the bigger ones.

Coverage remained the same at 98.378% when pulling 85f4c2c0f6430bd5bfc1c9286ac2f6ad9470fc8d on mistahenry:bugfix/bower_based_ember_try_scenarios into 568074dc9fca9479b009e568073e5aa437b7e23f on san650:master.


ZEPPELIN-1071 ] Ace-editor hidden auto-complete additional events.

What is this PR for?
Does not hide popup for Ace editor-autocomplete
If the page move or click on an event occurs, the auto-completion should be hidden.
What type of PR is it?
Bug Fix
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1071
How should this be tested?

Call the auto-complete in the code window (ctrl + shift + space)
Click anywhere without closing the pop-up.

Screenshots (if appropriate)
Before

After

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

LGTM!

LGTM!

LGTM and merge if there're no more discussions


eliminate abiguity of the DRS spec (GDEV-1030)

by removing unused options and making all used fields required.

Hi @mephenor, since Moritz is not available, maybe you can have a brief look?

This has been adapted from the DRS spec at https://editor.swagger.io/?url=https://ga4gh.github.io/data-repository-service-schemas/preview/release/drs-1.1.0/swagger.yaml


Supported Projection identifier names

Currently, if a Projection Acme\Foo\Bar\Domain\Projection\Baz\BazProjector is referenced (for replaying in CLI), either of these writings is possible:
acme.foo.bar:baz
foo.bar:baz
bar:baz
baz
Supporting all those different writings adds a lot of very complicated and hard to follow code (see https://github.com/neos/Neos.Cqrs/pull/54/files#diff-f97f8582f39d113750d81d5962d41460R158 ff.), while the benefit of being able to write any of those is debatable. If your Projection name is unique, being able to use only baz is the optimal shorthand. If however you have an ambiguous Projection name, then you can simply type the fully qualified name, which still takes less time than possibly attempting three different writings.
Also, it makes documentation more complicated, because all those cases need to be explained.
I therefore suggest that we only support the fully qualified projection name, and the shortest name version. This would highly reduce code complexity in the above mentioned class.

Actually, I'm undecided regarding this feature.
What would be completely fine with me as well would be using the fully qualified class name. Why not … I can copy that from the output of projection:list equally easy as the identifier (which I also need to look up).
But I'm also not against keeping this. Sure, why not. The code complexity … well, it's there, it works and we won't need to really touch it again.

It's exactly the same logic we use to find the shortest unambiguous CLI command identifier:
While it makes sense to use the full identifier for cron jobs & deployment tasks it's very convenient to be able to use the short command on the CLI and I would be extremely unhappy if I had to type the full command every time.
Same with
flow projection:replay some.long.packagekey:projection

If you think it's a problem that this internal code is in the ProjectionManager we could extract the logic to the CLI command controller but I'll fight for that UX ;)

yes, all fine, it's very convenient during development. But I would argue that it's too risky to use the short identifier in cron-jobs or automated tasks, and that's what some people will do …

But I would argue that it's too risky to use the short identifier in cron-jobs or automated tasks, and that's what some people will do

But that's exactly the same for the command identifiers!?
So should we get rid of that feature altogether?

I would be extremely unhappy if I had to type the full command every time.

Just to restate it: You don't have to every time - as long as your Projection short names are unique, all is fine.
flow projection:replay projection
But if you have multiple projection, why do you want to attempt to write flow projection:replay packagekey:projection if that again could fail? You lose more time if it does, and we carry more unmaintainable code with us to support this border-case.
I see two use cases:

during development: you should know exactly if your projection name is ambiguous or not, and hence can optimize typing to choose shortest or fully qualified name (if I know that a projection name is duplicated I mostly don't know where exactly that other projection lives, so I couldn't be sure any of the semi-qualified names is safe)

during deployment: you should always use fully qualified names, anything else is madness

As @albe wrote, we have these two use cases and I think both are important. I would just leave the feature implemented like it is, but people automating tasks should be (made) aware of the fact that they should rather use full identifiers for automation (like for commands).

OK, let me add one more scenario anyways:
Imagine you work on a large Flow application that covers multiple bounded contexts (with at least some of which are event-sourced). Because you're a well-behaved developer you split it into multiple packages, for example:
YourCompany.SuprApp (<-- Application logic)
YourCompany.SuprApp.Crm
YourCompany.SuprApp.Billing
YourCompany.SuprApp.Community
YourCompany.SuprApp.Support
...
If the app grows the likelihood that you have overlapping aggregate/read-model names (and thus projection names) increases (e.g. in the above you most probably have multiple "user" or "customer" models).
During development I want to be able to type
flow projection:replay crm:users

or
flow projection:replay community:users

Ok, but you don't want to be able to type
flow projection:replay SuprApp.Crm:users
too, do you? So still the solution is over-engineered (in a bad way).
But of course, if you both say that the code is good enough as is, I won't break a war on this.

we could extract the logic to the CLI command controller

This could be a compromise to at least keep the infastructural code clean from this usability-induced mess.

if you both say that the code is good enough as is

I don't think it's pretty but it works and has a small footprint. But I'm more than happy if someone comes up with a cleaner version that achieves the same!

we could extract the logic to the CLI command controller

This could be a compromise to at least keep the infastructural code
clean from this usability-induced mess.

Yes, I agree. We decided against this in the Flow CommandManager but I can't think of another place where this would be needed. I'll take care.

I moved the logic into the command controller as discussed

With #100 btw


ImportError: cannot import name 'Disaggregator' from 'nilmtk.disaggregate' (unknown location)

Why am I wrong here?

After I added the new disaggregator library, a new problem appeared.

Hi @Timelesssssss. This code does not run with the latest version of NILMTK yet. I would say please use this disaggregator class if you are willing to tinker with NILTMK.
Otherwise please consider using this instead
https://github.com/nilmtk/nilmtk-contrib/tree/master/disaggregate

OK，thanku very much，I will try these!

Hi @Timelesssssss , you can also try:
from nilmtk.legacy.disaggregate import Disaggregator


Global method API changes and global context

type Context interface {
	SetContainer(Container) Context
	Container() Container
	SetResolver(Resolver) Context
	Resolver() Resolver
	Raw() context.Context
}

Codecov Report

Merging #7 (d8d63bb) into master (f09bea0) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #7   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          399       405    +6
=========================================
+ Hits           399       405    +6

Impacted Files
Coverage Δ

container.go
100.00% <ø> (ø)

context.go
100.00% <100.00%> (ø)

di.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Lexonomy.eu slower than local installations?

I just happen to have the project "KSSS-2500-meniji" on Lexonomy.eu and our local installation, and I noticed that on .eu the entry loading works a bit slower, sometimes the difference is more noticeable. Is that due to server workload or something like that?
It is nothing major but I would still like to know why this occurs.

Sometimes, server may have high workload, mainly data processing for other tasks. Usually, response should be fast. So if you notice some serious issue with lexonomy.eu speed, please contact support, and we will take care of it


GRPC Handler: descriptorSetFilePath config regression (it does not work with json file)

Describe the bugs
descriptorSetFilePath  json file does not work (binary too I think)
I will explain the bug that occurred with the .json spec file. So below you have a reproducible example in codesandbox with a defined .json proto file descriptor.
The problem is that you are doing some weird stuff at the end of the getCachedRootJson which completely broke the introspectionCache.descriptorSetJson.
In the getMeshSource protoLoader.loadFileDescriptorSetFromObject expect exactly the file provided in the descriptorSetFilePath as JSON. Since you are doing some black magic with root.ToDescriptor and cie the descriptorSetJson  is completely unusable : the descriptor contains 3 files, your descriptorSetJson after calling the getCachedRootJson is only 2.
To Reproduce
https://codesandbox.io/s/graphql-mesh-bug-iqfzv
Expected behavior
It must work normally without problems. I apply a patch that replaces some of your code like that :
const packageDefinition = protoLoader.loadFileDescriptorSetFromObject(decodedDescriptorSet);
replaced by :
const packageDefinition = protoLoader.loadFileDescriptorSetFromObject(JSON.parse(await require('fs/promises').readFile(this.config.descriptorSetFilePath)));

It's a really bad patch but it fixes the problem for my use case.

Environment:
"@graphql-mesh/cli": "0.30.2",
"@graphql-mesh/grpc": "0.14.9",
"graphql": "15.5.1"

Available in the latest version!


NETOBSERV-1974: use ovnk-lib to get net event messages

Description

import ovnk-lib to get messages
add unmarshal hooks for specific decoding of Loki line values
implement a hook to write decoded messages for net events

Dependencies

Ovn-k: (not necessary to deploy, it's only code dependency) https://github.com/ovn-kubernetes/ovn-kubernetes/pull/4818
Agent: https://github.com/netobserv/netobserv-ebpf-agent/pull/458
FLP: https://github.com/netobserv/flowlogs-pipeline/pull/760

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.

[x] 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):

[x] 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).

/retest

/ok-to-test


Handle the sale queries - ensure it works only for old sales

Part of https://github.com/saleor/saleor/issues/12539

Resolves in https://github.com/saleor/saleor/pull/13521


Update README.md

Add install plugin information
Hey, I just made a Pull Request!
Just include install plugin information
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

@ericksposito this is a super helpful update for users of the New Relic dashboard plugin!  Nice one!
Are you able to help finish it out by rebasing with latest off master as @Rugvip noted a few months ago???? If so that would be super helpful.  Thanks!


Errors when creating generic email connectors

When trying to create generic erasure or consent email connector I get value is not a valid email toast error when in fact it is. Test email is really mandatory although not marked as such BUT once populated we get a new error Must supply at least one identity_type.
create a connector in the old way OR the integration tab > fill out the form with valid email not populating test email > click Save > see valid email error > populate test email > click Save > see identity_type error

Update- was able to reproduce the value is not a valid email error. The issue is the FE passes in "" for test_email_address which it should pass in null if not provided by the user.
After using null, the 2nd error Must supply at least one identity_type. could not be replicated, both in Postman or in the UI.


fix(config): add metadata for Sensative strips

Add metadata to Sensative strips

Took a bit to review, but thanks :)


Add kerchunk opener to repr route

The recently-added https://github.com/pangeo-forge/liveocean-feedstock had a successful production run:

https://pangeo-forge.org/dashboard/recipe-run/1391?feedstock_id=91

Our xarray repr generation route doesn't support kerchunk, so instead of a dataset repr the frontend is displaying:
status code: 404
An error occurred while fetching data from URL: https://api.pangeo-forge.org/repr/xarray/?url=https://ncsa.osn.xsede.org/Pangeo/pangeo-forge/pangeo-forge/liveocean-feedstock/liveocean.zarr
{"detail":"An error occurred while fetching the data from URL: https://ncsa.osn.xsede.org/Pangeo/pangeo-forge/pangeo-forge/liveocean-feedstock/liveocean.zarr. Dataset not found."}

Let's add some conditional logic for that rather than assuming all datasets are zarr, here:
https://github.com/pangeo-forge/pangeo-forge-orchestrator/blob/fb5caaf6994d1b73004b447ab00e5687ab941f2e/pangeo_forge_orchestrator/routers/repr.py#L24-L25
xref #198 #199
cc @rsignell-usgs this is why the frontend is not displaying the dataset repr for liveocean. But I think https://ncsa.osn.xsede.org/Pangeo/pangeo-forge/pangeo-forge/liveocean-feedstock/liveocean.zarr should be your full dataset (despite the inaccurate .zarr suffix, which is because of #199)?

👋 gentle bump on this issue!
It looks like this is now affecting the first two recipes on the frontend, which makes it fairly prominent.

Thanks for the ping @katamartin.
@andersy005, noticed your 👍, do you have interest in + bandwidth to work on this?

@cisaacstern, this is on my TODO list, but won't be able to work on it until later next week :)

Sounds great. I'll assign you here, @andersy005. From my perspective, no stress re: timeline. Of course lmk if you end up needing feedback/review on this.

@katamartin, out of curiosity, does next/vercel offer the possibility of running any type of integration testing against a live instance of our backend application? For every PR, we have the option of deploying a review instance of the backend, and also merges to main deploy to a staging instance. In #226, I am working on an integration test wiring these instances to Google Dataflow, as part of debugging #220. Similarly, should we consider some scheduled tests of the frontend against these dev/staging instances of the backend? I am imaging some future where we require checks such as:
✅ Dataflow integration passing
✅ Next.js frontend integration passing

Before we deploy to prod. (Anderson maybe you have some insight on how to do this too. When we spoke the other week, I think we agreed that frontend integration testing was not the highest priority, but here we have a prime example of when it would have helped already 😅 .)

@cisaacstern ooh can definitely see how that would be useful here! Unfortunately, not sure that there are great out-of-the-box options.
As I see it, we would need to wire up deploys for the pangeo-forge.org project to this repo and get those frontend deploys to point to the backend preview deploy URLs. It looks like there's definitely no Vercel tooling for the latter (https://github.com/vercel/vercel/discussions/5231) and I'm not sure how well-supported the former would be either.


WFLY-4021 allow Hibernate orm latest (main) to be referenced via major.minor alias

Windows Build 872 is now running using a merge of b3c19868b668802eb55bea38cc51fff40007d375

Linux with security manager Build 748 is now running using a merge of b3c19868b668802eb55bea38cc51fff40007d375

Linux Build 5761 is now running using a merge of b3c19868b668802eb55bea38cc51fff40007d375

Linux with security manager Build 748 outcome was SUCCESS using a merge of b3c19868b668802eb55bea38cc51fff40007d375
Summary: Tests passed: 795, ignored: 371 Build time: 0:05:14

Windows Build 872 outcome was SUCCESS using a merge of b3c19868b668802eb55bea38cc51fff40007d375
Summary: Tests passed: 2913, ignored: 366 Build time: 0:51:09

Linux Build 5761 outcome was SUCCESS using a merge of b3c19868b668802eb55bea38cc51fff40007d375
Summary: Tests passed: 2912, ignored: 366, muted: 1 Build time: 0:53:35


New package: YingYang48.VsHex version D11

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/112009&drop=dogfoodAlpha

@wingetbot waivers Add Validation-Domain


Proper support for custom mass properties in 2D/3D physics bodies

Default center of mass in 2D:
Compute center of mass based on shapes by default in 2D, same as in 3D.
This change breaks compatibility because it was always using the center of the body before, although in common cases the computed center of mass is still going to be at the center.
Custom center of mass:
Can be set through the physics server using:
PhysicsServer2D.body_set_param(get_rid(), PhysicsServer2D.BODY_PARAM_CENTER_OF_MASS, center_of_mass)
Can be reset through the physics server using:
PhysicsServer2D.body_reset_mass_properties(get_rid())
3D uses a similar API.
Edit: Now can be set in RigidBody2D and RigidBody3D nodes as well with properties:
center_of_mass_mode: set to Auto or Custom
center_of_mass: custom center of mass (relative to the body's center)
Custom inertia:
Can be set through the physics server using:
PhysicsServer2D.body_set_param(get_rid(), PhysicsServer2D.BODY_PARAM_INERTIA, inertia)
Can be reset through the physics server using:
PhysicsServer2D.body_reset_mass_properties(get_rid())
Can be also set on rigid body nodes through the inertia property, with 0 meaning default calculated inertia.
3D has a similar API, although it's also possible to setup a custom inertia on specific axes, and set the other ones to 0 in order to keep the default computation. That's useful to make a body rotate more or less easily on a specific axis, without affecting other axes.
Full list of changes:
-Added support for custom inertia and center of mass in 3D
-Added support for custom center of mass in 2D
-Calculated center of mass from shapes in 2D (same as in 3D)
-Updated forces and joints to use center of mass in 2D
-Fixed mass properties calculation with disabled shapes in 2D/3D
-Removed first_integration which is not used in 2D and doesn't seem to make a lot of sense (prevents omit_force_integration to work during the first frame)
-Support for custom inertia on different axes for RigidBody3D
-mass property uses a more reasonable slider range by default (max 1000), with the possibility to set higher values
Closes #https://github.com/godotengine/godot-proposals/issues/945
Fixes #12353
Supersedes #29867
Addresses issue from https://github.com/godotengine/godot/pull/49185#pullrequestreview-671757775

Can this be cherry-picked to 3.x by setting the default center_of_mass to use Custom, Vector3(0,0,0) to avoid breaking compatibility?

@Zoomulator Ok, it should be possible but I need to check what can be safely backported as there are changes in the way things are calculated in the physics server itself.

@pouleyKetchoupp I worried that there might be adjacent changes in 4.0.
I'd greatly appreciate it if you gave it a try, if it's not too much trouble! 😄


How to extend the user response to the front

Hi there,
I'm new to feathers and currently learning how everything works together using the nuxt-feathers boilerplate at https://github.com/silvestreh/feathers-nuxt
I would like to extend the response from the users service to include more fields besides just the _id and email.
Found this documentation on how to extend the authenticate service and when console.log(context.result) I see the added fields.
Yet, none of them is caught in the nuxt client. Only the _id and email.
Any suggestions on how to do that would be much appreciated. Thanks.

Editing the after part of the hook in users/hooks.js and having:
get: [
      context => {
        context.result.foo = 'bar';
      }
    ]

Results in the client auth user having the foo property.


Codewars has been changed

It no longer uses a pre tag, so I modified the userstyle to reflect that

I also added the code blocks in the description

Thanks a lot!

No problem :)


When calling 'CreateCoreWebView2Controller' in Webview2, it takes about 3 seconds, but I want to reduce it to 1 second. I wonder if there is a better way

Hello, my name is Jaeho.
I wonder how is solves that calling 'CreateCoreWebView2Controller' in Webview2(win32, version 1.0.1072.54), it takes about 3 seconds, but I want to reduce it to 1 second. I wonder if there is a better way.

Hello. This repo is for questions about test automation with Microsoft Edge WebDriver, not the WebView2 control. Please post your question to https://github.com/MicrosoftEdge/WebView2Feedback instead.


Changing the package dependency to hip-rocclr

Looks good to me, but maybe we should update the cuda case in another PR