text:
feat(compaction): cut file by table

Signed-off-by: Little-Wallace bupt2013211450@gmail.com
I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
close https://github.com/risingwavelabs/risingwave/issues/5299
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)

The left is current PR while the right is main branch. We can see that after compact by table we save some resource and could make trivial move more effective.


text:
refactor(meta): use short prefix name for hummock meta store model

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Before this PR we prefix hummock meta store model's key with descriptive name like "cf/hummock_version_delta".
This PR changes these prefix to shorter "cf/hummock_#" for better write performance and storage efficiency.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
- [ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features).
- [ ] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

[x] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

This PR will break backward compatibility. Should provide a migration scripts to rewrite meta store.

This PR changes these prefix to shorter "cf/hummock_#" for better write performance and storage efficiency.

Should we use a more concise prefix instead of  "cf/hummock_#" ?

source: gharchive/pull-request

repo: risingwavelabs/risingwave

license_type: permissive

license_source: github-api


text:
Web Page Does Not Refresh When Pound Sign (#) is in File Path

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Other: <!-- Please describe: -->

Current behavior
When using live server to reload a web page on save from a file whose full file path contains a pound sign (#), live server does not recognize when a file has been changed to reload the changes.
C:/folder/#1/index.html does not reload
C:/folder/1/index.html does reload
Expected behavior
Live server should notice the change and update the browser accordingly.
Environment
Browser:

- [x ] Chrome (desktop) version 68.0.3440.106
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:

- Live Server: 5.1.1
- Platform:  Widows
- Visual Studio Code: 1.27.1

Others

I have the same problem.

source: gharchive/issue

repo: ritwickdey/vscode-live-server

license: mit

license_source: bigquery


text:
Can't delete magnets

Hi there,
I am testing a torrent activator magnet, but after done testing, I can't delete this magnet. I can delete normal magnets. Any feedback?.

This will be fixed in next release. I plan to do that soon.

Thanks for responding.
In addition, is there a way to pause/stop the torrent download?, as well as just to download specific files of the torrent, as oppose to download the whole torrent, for example, if the whole torrent has 10 episodes, can I just download 5 of them and block the other 5?.
Love this program!

license: MIT


text:
Unable to build rive-android for contribution

Description
Just want to build rive-android with debug mode as CONTRIBUTE.md step but I got a problem.
Error log
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':kotlin:configureCMakeDebug[arm64-v8a]'.
> [CXX1429] error when building with cmake using /Users/hoang.vu/Work/rive-android/kotlin/src/main/cpp/CMakeLists.txt: -- The CXX compiler identification is Clang 14.0.6
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Check for working CXX compiler: /Users/hoang.vu/Library/Android/sdk/ndk/25.1.8937393/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++ - skipped
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Configuring incomplete, errors occurred!
  See also "/Users/hoang.vu/Work/rive-android/kotlin/.cxx/Debug/4h3l715i/arm64-v8a/CMakeFiles/CMakeOutput.log".

  C++ build system [configure] failed while executing:
      /Users/hoang.vu/Library/Android/sdk/cmake/3.22.1/bin/cmake \
        -H/Users/hoang.vu/Work/rive-android/kotlin/src/main/cpp \
        -DCMAKE_SYSTEM_NAME=Android \
        -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \
        -DCMAKE_SYSTEM_VERSION=21 \
        -DANDROID_PLATFORM=android-21 \
        -DANDROID_ABI=arm64-v8a \
        -DCMAKE_ANDROID_ARCH_ABI=arm64-v8a \
        -DANDROID_NDK=/Users/hoang.vu/Library/Android/sdk/ndk/25.1.8937393 \
        -DCMAKE_ANDROID_NDK=/Users/hoang.vu/Library/Android/sdk/ndk/25.1.8937393 \
        -DCMAKE_TOOLCHAIN_FILE=/Users/hoang.vu/Library/Android/sdk/ndk/25.1.8937393/build/cmake/android.toolchain.cmake \
        -DCMAKE_MAKE_PROGRAM=/Users/hoang.vu/Library/Android/sdk/cmake/3.22.1/bin/ninja \
        -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/Users/hoang.vu/Work/rive-android/kotlin/build/intermediates/cxx/Debug/4h3l715i/obj/arm64-v8a \
        -DCMAKE_RUNTIME_OUTPUT_DIRECTORY=/Users/hoang.vu/Work/rive-android/kotlin/build/intermediates/cxx/Debug/4h3l715i/obj/arm64-v8a \
        -DCMAKE_BUILD_TYPE=Debug \
        -B/Users/hoang.vu/Work/rive-android/kotlin/.cxx/Debug/4h3l715i/arm64-v8a \
        -GNinja \
        -DCMAKE_VERBOSE_MAKEFILE=1 \
        -DANDROID_ALLOW_UNDEFINED_SYMBOLS=ON \
        "-DANDROID_CPP_FEATURES=no-exceptions no-rtti" \
        -DANDROID_STL=c++_shared
    from /Users/hoang.vu/Work/rive-android/kotlin
  BUILD TYPE: Debug

Device & Versions

MacbookPro Chip M3
Android Studio Koala
Device: Emulator Android15
SDK Level [Android SDK API Level 35]
ndk versrion : 25.1.8937393

[Update]
I also tried to build with the below command but got the error
 ./build.rive.for.sh -a arm64-v8a
~/Work/code/rive-android/kotlin/src/main/cpp

+ pushd /Users/[hoang.vu/Work/code/rive-android/kotlin/src/main/cpp/../../../../submodules/rive-cpp/../pls](http://hoang.vu/Work/code/rive-android/submodules/pls)

./[build.rive.for.sh](http://build.rive.for.sh/): line 158: pushd: /Users/[hoang.vu/Work/code/rive-android/kotlin/src/main/cpp/../../../../submodules/rive-cpp/../pls](http://hoang.vu/Work/code/rive-android/submodules/pls): No such file or directory

Base on the error content , I also tried to create pls  folder under the submodule but still get error at this line
+ premake5 --out=out/android/arm64/release --config=release --scripts=/Users/[hoang.vu/Work/code/rive-android/kotlin/src/main/cpp/../../../../submodules/rive-cpp/build](http://hoang.vu/Work/code/rive-android/submodules/rive-cpp/build) --with_rive_text --with_rive_audio=system --with_rive_layout --no-rive-decoders --os=android --arch=arm64 gmake2

Error: invalid option 'arch'

Any workaround here ?

It seems the problem comes from the Mac M3 chip ?

any update?

repo: rive-app/rive-android


text:
chore(cluster): increase storage reserved for system on ats

Changes

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

#723  👈
#721
#715
#714
#712
#711
#709
#708
#707
#706
#696
#695
#689
#688
#687
#686
#685
#684
#683
#682
#674
#673
#672
#671
#670
#669
#668
#667
#697
#641
#635
#633
#632 : 1 other dependent PR (#700 )
#628 : 1 other dependent PR (#629 )
#613
main

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

Join @NathanFlurry and the rest of your teammates on  Graphite

repo: rivet-gg/rivet


text:
🛑 1bitcoin is down

In 8838f35, 1bitcoin (https://www.satubitcoin.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 1bitcoin is back up in cb02371 after 37 minutes.

repo: rizalrenaldi/ruptime


text:
Visual selection?

Currently <Plug>DashSearch only takes the word under the cursor. Consider making this an operator so we can use text objects on it and also visual selections.

@stellarhoof I added the ability to search by visual selection in #58, its probably not the best way to do it but it seems to work for me.

@JGShaw Thank you. This is fine.

authors: JGShaw stellarhoof


text:
Question about regex

Can you explain what the regex in the following line is intended to accomplish?
route.pathname.replace(/\[[^\]]*]/g, '([\\w-]+)') + '$'

It doesn't seem to be working for me, if you could provide some examples of what it does that would be very helpful! For context, my rules like /app/* or /app/.* aren't doing anything, and as far as I can tell, my non-regex rules aren't functioning either.

Never mind, I understand what it does now. For anyone else wondering, it is meant to add support for dynamic routes. An example can be found on Regex101 here.
For a simple explanation, this:
/admin/[userId]/dashboard

Will get turned into this:
/admin/([\w-]+)/dashboard

For the purposes of matching routes. Other regex does not yet appear to be supported in routing for this library, so I'm going to look into adding it.

repo: rkanik/sveltekit-route-guard


text:
Trojan Detected

Upon downloading the ZIP folder; Windows Security detected:

Trojan:Win32/Wacatac.H!ml
containerfile: C:\Users_\Downloads\DatePicker-main.zip
file: C:\Users_\Downloads\DatePicker-main.zip->DatePicker-main/Distribution/DatePicker32.xll
webfile: C:\Users___\Downloads\DatePicker-main.zip|https://codeload.github.com/rkapl123/DatePicker/zip/refs/heads/main|pid:17972,ProcessStart:133183605089372705

Hi Steve!
Well, this is a quite far-spread problem with Excel-DNA based add-ins, as 1) some malware authors use Excel-DNA for their excel viruses and 2) virus scanners have sometimes too broad heuristics and exclude other add-ins that are not viruses.
I've checked downloading the zip packages in the tags and discovered that for me only edge came up with a virus warning. No warnings in firefox and chrome.
I'll put a correction to https://www.microsoft.com/en-us/wdsi/filesubmission...

I have put the false positive into MS Defenders submission site, they couldn't reproduce the malware scan anymore and advised me to update the signatures to the latest version:

Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
Run MpCmdRun.exe -removedefinitions -dynamicsignatures
Run MpCmdRun.exe -SignatureUpdate
After doing that the download of the tag zip package worked again without showing a virus.

Hi, I have similar issues by Palo Alto Cortex XDR antivirus, the following is an extrapolation from my event viewer:
"Suspicious DLL detected" for:
DatePicker-main\Distribution\DatePicker64.xll
DatePicker-main\Distribution\DatePicker32.xll
AppData\Roaming\Microsoft\AddIns\DatePicker.xll
"Suspicious process creation detected" for:
DatePicker-main\Distribution\enableAddin.vbs
Can you help me? Thanks
Antonio

Hi, the only way to resolve this is to make a false positive request at https://live.paloaltonetworks.com/t5/virustotal/virustotal-verdict-change-request-for-false-positive/td-p/287364 , they have a template that you can fill and report it as false positive.
-regards,
Roland

authors: DevDesk ascattolini rkapl123


text:
add a field in renter table for saving the current status

user should be able to update the current status of the renter

ACTIVE
INACTIVE

UI changes will be taken care in issue #59


text:
revert filetype detect, save localoptions

See https://github.com/rmagatti/auto-session/pull/179#issuecomment-1307567366
Save local options which will restore syntax highlighting, as well as wrap and number options

@rmagatti @zwhitchcox
I'd call this a breaking change, took me some time figuring out why my session switching was breaking.
Had to :e the first file every time I switched sessions, and in general just had weird behaviour.
@rmagatti Perhaps you could create a pinned issue with breaking changes like these? - For easy subscription.

I can create that issue for sure! I'm still unclear on what was breaking from this change as merely the defer function was removed that didn't actually even exist before if I'm not mistaken. Either way a breaking change issue is a great idea, thanks!

@MikaelElkiaer here it is:
https://github.com/rmagatti/auto-session/issues/186

I can create that issue for sure! I'm still unclear on what was breaking from this change as merely the defer function was removed that didn't actually even exist before if I'm not mistaken. Either way a breaking change issue is a great idea, thanks!

There might be more to it then than just this.
My syntax highlighting was gone whenever I would restore a session, until after adding the localoptions bit to restore options.

@MikaelElkiaer Sorry this gave you so much trouble, but I would not classify this as a breaking change. auto-session was just covering up a misconfiguration (not saving localoptions) with an ugly hack where it would delay the restoration of the session by 50 ms.
Aside from the race condition bugs this could cause, it also introduced a scenario where if the session restoration caused the directory to change, this would cause a new session restoration, which could cause the directory to change again, ad infinitum.
The syntax highlighting is a lower priority than the infinitely recursive directory changes.
That being said, I do think we could make it easier to figure out than combing through issues/PRs. It might be nice to add the localoptions note to the trouble shooting page on the wiki @rmagatti ...or maybe just add it as a note in the readme?
I could also just add this change back in, because it would not hurt anything other than slightly decreasing performance, but it might provide a better UX for some users.

The readme does recommend adding localoptions to sessioniptions already. It just doesn't really say what that does or doesn't do. Maybe this is a common enough occurrence that it might be worth explaining further in the readme, but maybe it's easier to tell people to :h sessionoptions in case they want to know what each of the recommended options (and others) do for session loading. I'll add something to the readme on this (unless one of you want to 😄)

How about we just say if more people comments on this saying that it gave them trouble we can add more documentation, but otherwise count this as documentation

authors: MikaelElkiaer rmagatti zwhitchcox

repo: rmagatti/auto-session


text:
pacaur -Syu --devel fails to update packages

I've tried to update my devel packages but it fails to install them.
pacaur version: 4.6.0
All the process is correct (fetching, building, compressing, ...) but pacaur tries to install always the same package. I've used the command pacaur -Syu --devel.

Log:
:: Starting AUR upgrade...
:: resolving dependencies...
:: looking for inter-conflicts...
:: hardcode-fixer-git latest revision -- fetching
:: numix-circle-icon-theme-git latest revision -- fetching
:: numix-icon-theme-git latest revision -- fetching
:: oh-my-zsh-git latest revision -- fetching
:: powerline-fonts-git latest revision -- fetching
:: vundle-git latest revision -- fetching

AUR Packages  (6):

Name                             Old Version           New Version

aur/hardcode-fixer-git           1:r442.d6c80a7-1      latest
aur/numix-circle-icon-theme-git  0.r3033.e179931-1     latest
aur/numix-icon-theme-git         0.r1763.292f2b2-1     latest
aur/oh-my-zsh-git                3859.bd6dbd1-1        latest
aur/powerline-fonts-git          r100.a44abd0-2        latest
aur/vundle-git                   0.10.2.603.4984767-1  latest

:: Proceed with installation? [Y/n] y
:: Retrieving package(s)...
:: hardcode-fixer-git build files are up-to-date -- skipping
:: numix-circle-icon-theme-git build files are up-to-date -- skipping
:: oh-my-zsh-git build files are up-to-date -- skipping
:: powerline-fonts-git build files are up-to-date -- skipping
:: vundle-git build files are up-to-date -- skipping
:: numix-icon-theme-git build files are up-to-date -- skipping
:: Checking numix-icon-theme-git integrity...
==> Making package: numix-icon-theme-git 0.r317.290d12e-1 (dom abr 10 01:31:45 CEST 2016)
==> Retrieving sources...
  -> Updating numix-icon-theme git repo...
Fetching origin
==> Validating source files with sha256sums...
    numix-icon-theme ... Skipped
:: Checking vundle-git integrity...
==> Making package: vundle-git 0.10.2.580.cfd3b2d-1 (dom abr 10 01:31:50 CEST 2016)
==> Retrieving sources...
  -> Updating vundle-git git repo...
Fetching origin
  -> Found vundle.vimrc
==> Validating source files with sha512sums...
    vundle-git ... Skipped
    vundle.vimrc ... Passed
:: Checking powerline-fonts-git integrity...
==> Making package: powerline-fonts-git r100.a44abd0-2 (dom abr 10 01:31:51 CEST 2016)
==> Retrieving sources...
  -> Updating fonts git repo...
Fetching origin
==> Validating source files with md5sums...
    fonts ... Skipped
:: Checking oh-my-zsh-git integrity...
==> Making package: oh-my-zsh-git 3143.4224c2a-1 (dom abr 10 01:31:53 CEST 2016)
==> Retrieving sources...
  -> Updating oh-my-zsh-git git repo...
Fetching origin
==> Validating source files with md5sums...
    oh-my-zsh-git ... Skipped
:: Checking numix-circle-icon-theme-git integrity...
==> Making package: numix-circle-icon-theme-git 0.r1677.fe74d83-1 (dom abr 10 01:31:56 CEST 2016)
==> Retrieving sources...
  -> Updating numix-circle-icon-theme git repo...
Fetching origin
==> Validating source files with sha256sums...
    numix-circle-icon-theme ... Skipped
:: Checking hardcode-fixer-git integrity...
==> Making package: hardcode-fixer-git 1:r395.a01f915-1 (dom abr 10 01:31:58 CEST 2016)
==> Retrieving sources...
  -> Updating hardcode-fixer-git git repo...
Fetching origin
==> Validating source files with md5sums...
    hardcode-fixer-git ... Skipped
:: Building numix-icon-theme-git package(s)...
==> Making package: numix-icon-theme-git 0.r1763.292f2b2-1 (dom abr 10 01:31:59 CEST 2016)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating numix-icon-theme git repo...
Fetching origin
==> Validating source files with sha256sums...
    numix-icon-theme ... Skipped
==> Extracting sources...
  -> Creating working copy of numix-icon-theme git repo...
Switched to a new branch 'makepkg'
==> Starting pkgver()...
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Compressing man and info pages...
==> Checking for packaging issue...
==> Creating package "numix-icon-theme-git"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: numix-icon-theme-git 0.r1763.292f2b2-1 (dom abr 10 01:32:08 CEST 2016)
==> Cleaning up...
:: Installing numix-icon-theme-git package(s)...
loading packages...
warning: numix-icon-theme-git-0.r1763.292f2b2-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)           Old Version        New Version        Net Change

numix-icon-theme-git  0.r1763.292f2b2-1  0.r1763.292f2b2-1    0,00 MiB

Total Installed Size:  24,47 MiB
Net Upgrade Size:       0,00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                    [##############################################] 100%
(1/1) checking package integrity                                                  [##############################################] 100%
(1/1) loading package files                                                       [##############################################] 100%
(1/1) checking for file conflicts                                                 [##############################################] 100%
(1/1) checking available disk space                                               [##############################################] 100%
:: Processing package changes...
(1/1) reinstalling numix-icon-theme-git                                           [##############################################] 100%
:: Installing vundle-git cached package...
loading packages...
warning: numix-icon-theme-git-0.r1763.292f2b2-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)           Old Version        New Version        Net Change

numix-icon-theme-git  0.r1763.292f2b2-1  0.r1763.292f2b2-1    0,00 MiB

Total Installed Size:  24,47 MiB
Net Upgrade Size:       0,00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                    [##############################################] 100%
(1/1) checking package integrity                                                  [##############################################] 100%
(1/1) loading package files                                                       [##############################################] 100%
(1/1) checking for file conflicts                                                 [##############################################] 100%
(1/1) checking available disk space                                               [##############################################] 100%
:: Processing package changes...
(1/1) reinstalling numix-icon-theme-git                                           [##############################################] 100%
:: Installing powerline-fonts-git cached package...
loading packages...
warning: numix-icon-theme-git-0.r1763.292f2b2-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)           Old Version        New Version        Net Change

numix-icon-theme-git  0.r1763.292f2b2-1  0.r1763.292f2b2-1    0,00 MiB

Total Installed Size:  24,47 MiB
Net Upgrade Size:       0,00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                    [##############################################] 100%
(1/1) checking package integrity                                                  [##############################################] 100%
(1/1) loading package files                                                       [##############################################] 100%
(1/1) checking for file conflicts                                                 [##############################################] 100%
(1/1) checking available disk space                                               [##############################################] 100%
:: Processing package changes...
(1/1) reinstalling numix-icon-theme-git                                           [##############################################] 100%
:: Installing oh-my-zsh-git cached package...
loading packages...
warning: numix-icon-theme-git-0.r1763.292f2b2-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)           Old Version        New Version        Net Change

numix-icon-theme-git  0.r1763.292f2b2-1  0.r1763.292f2b2-1    0,00 MiB

Total Installed Size:  24,47 MiB
Net Upgrade Size:       0,00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                    [##############################################] 100%
(1/1) checking package integrity                                                  [##############################################] 100%
(1/1) loading package files                                                       [##############################################] 100%
(1/1) checking for file conflicts                                                 [##############################################] 100%
(1/1) checking available disk space                                               [##############################################] 100%
:: Processing package changes...
(1/1) reinstalling numix-icon-theme-git                                           [##############################################] 100%
:: Installing numix-circle-icon-theme-git cached package...
loading packages...
warning: numix-icon-theme-git-0.r1763.292f2b2-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)           Old Version        New Version        Net Change

numix-icon-theme-git  0.r1763.292f2b2-1  0.r1763.292f2b2-1    0,00 MiB

Total Installed Size:  24,47 MiB
Net Upgrade Size:       0,00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                    [##############################################] 100%
(1/1) checking package integrity                                                  [##############################################] 100%
(1/1) loading package files                                                       [##############################################] 100%
(1/1) checking for file conflicts                                                 [##############################################] 100%
(1/1) checking available disk space                                               [##############################################] 100%
:: Processing package changes...
(1/1) reinstalling numix-icon-theme-git                                           [##############################################] 100%
:: Installing hardcode-fixer-git cached package...
loading packages...
warning: numix-icon-theme-git-0.r1763.292f2b2-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)           Old Version        New Version        Net Change

numix-icon-theme-git  0.r1763.292f2b2-1  0.r1763.292f2b2-1    0,00 MiB

Total Installed Size:  24,47 MiB
Net Upgrade Size:       0,00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                                                    [##############################################] 100%
(1/1) checking package integrity                                                  [##############################################] 100%
(1/1) loading package files                                                       [##############################################] 100%
(1/1) checking for file conflicts                                                 [##############################################] 100%
(1/1) checking available disk space                                               [##############################################] 100%
:: Processing package changes...
(1/1) reinstalling numix-icon-theme-git

Someone reported a somewhat [similar issue(https://bbs.archlinux.org/viewtopic.php?pid=1618610#p1618610) in the forums. This might be related.
Please provide a debug output.

Commit of interest: 89d673b61a632a22bdb07048dcab4fde62ad5969.

Here you are.

I can't say the debug output is really helpful... and of course I cannot reproduce.
Can you tell me more about your setup? Which shell are you using, and are you using third party tool such as powerpill?

Not using any third party plugin. I've tried in bash and zsh. Additionally,
I've also tested with LANG=es_ES.UTF-8 and LANG=en_US.UTF-8.
If you want me to do any additional test just tell me.
El 10 abr. 2016 11:22, "Remy Marquis" notifications@github.com escribió:
I can't say the debug output is really helpful... and of course I cannot
reproduce.
Can you tell me more about your setup? Which shell are you using, and are
you using third party tool such as powerpill?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/rmarquis/pacaur/issues/480#issuecomment-207950089

Yes please:

Also, if you could try to revert the "commit of interest" above and see if it fix your issue, that would be great.

I need to find out which commit is responsible for the issue, and in which circumstances it does appear.

Ah, think I found the issue. It seems it happens when PKGDEST is not defined. I'll have a closer look when I have access to my machine tonight.

Fixed in 46d78d3593ab9c3b3e93e731e1b9aa0c5c591036.

That was quick ;)

repo: rmarquis/pacaur

license: isc


text:
Updated domain record commands

"record" was missing

Coverage remained the same at 99.6% when pulling 0bbd09f1ce009f11e5757e1c01b20e9f005a0caa on mehmetdavut:patch-1 into d22c935af30bad51ca1e3d677368b4977ccb15ec on rmoriz:master.

Thanks!

authors: coveralls gregf mehmetdavut


text:
entities dont show on/off values when creating automation

When using conditions in automation, I dont see on/off value of sensors. I can only see not available/unknown

and what's the actual value ? In last days these values were not working for me and were undefined, I tried reload/restart and integration reinstall. However you can enter on/off value manually in the automation.

There are more entities, the actual value is off or on. I see it in the main dashboard. Going to try the manual input and reinstall. Restart didnt fix it.

But for sure this is not an integration issue of not showing popup values when using automation ...

Manual input worked. Im a novice in HA, so sorry for maybe stupid question and thanks for help!

The problem is that the sensor is called sensor.spot_electricity_is_cheapest_X_hours_block but HA would need the entity to be called binary_sensor.X to add the On/Off values there . This would be a breaking change and I'm not quite sure if it is worth it.

I believe, that it help a lot to fix this issue. I understand, that it is breaking changes, so what about to duplicate sensors for some time? It's up to you, how long the period will be.

Fixed in #68

authors: Bebeone111 kkoouu kukulich rnovacek rpajik


text:
settings.gradle patch not respecting single line multi project "includes"

The code in makeSettingsPatch will break existing settings.gradle configs where users happen to use single-line multi-project include statements, e.g.:
include ':app', ':react-plugin'
https://github.com/rnpm/rnpm-plugin-link/blob/master/src/android/patches/makeSettingsPatch.js#L20
To address this, I propose simply appending the new include statements to the file instead of searching for include ':app' and replacing it. It simplifies the code and is much less error prone.

Since this is a small and simple change, I have done up an existing PR to with my proposed changes https://github.com/rnpm/rnpm-plugin-link/pull/31

Nice! Thanks for your awesome contributions!

#31 is merged, so I assume we can close this issue.

Cool! Any ETA on when the latest bits can be published on to NPM? We can't wait to start using your work!

@geof90 published as 1.5.4

@Kureev awesome!!

So excited to see android going more stable!

authors: Kureev geof90 grabbou

repo: rnpm/rnpm-plugin-link


text:
Re-align CI and test scenarios with Ember Defaults

Removed old scenarios
Update ember-try config to match new blueprints
Extracted Node Test into their own step
Bumped minimum node version to 12 (oldest current LTS)

WIP:

[x] Should ember-auto-import be updated to v2 or added to try scenarios
[x] Qunit v4 doesn't support the setup method required by v5, drop this?

Should ember-auto-import be updated to v2 or added to try scenarios

ya, we'd need to do it anyways to support embroider. Let's upgrade auto-import.

Qunit v4 doesn't support the setup method required by v5, drop this?

since it seems innevitable to upgrade the auto-import(which is a breaking change, as far as I understand), I think we may have troubles making the ember-qunit@4 to work with auto-import@2. After thinking about it more, I think I was wrong with my intention to support ember-qunit@4. Let's drop it. For those who may want to use it still, there is a v1 release.

I'm stuck on jQuery (not a huge surprise). In Ember v4 the jquery-integration optional feature doesn't work anymore. Even if I install @ember/jquery though and turn off this flag I get Ember is not defined errors which I think come from https://github.com/ro0gr/ember-cli-page-object/blob/upgrade/ember%403.28/addon-test-support/adapters/acceptance.js#L3 (and a few other places with const { $ } = Ember;. I'm not sure familiar enough with what these different parts of the code do to know what's critical here.
Is it possible that in v2 these sort of legacy jQuery handlers can go away or rely on the -jquery that gets bundled by this addon? Or is it impossible to support Ember v4 without first dropping some things? Or am I missing what's going on and there is a fix?

@jrjohnson I'd like to simplify jquery stuff a bit in scope of v2(https://github.com/san650/ember-cli-page-object/pull/556#discussion_r780681443). I believe the best path forward for it is to remove adapters/{acceptance,integration,native-*} adapters and switch to consume the jquery dependency for some remaining places in the codebase. Feel free to remove those old adapters. I believe this should allow us to import jquery directly w/o a need for shims or some other magic:
import $ from 'jquery';

In general I'd like to get rid of jquery completely of course, but it should probably be done after the v2 is released.

Just an update on this. I've mostly converted to import $ from 'jquery';, however that is getting transpired somewhere to Ember.$. I'm trying to track down where/why that is happening.

This is strange. It should have been ignored due to https://github.com/jrjohnson/ember-cli-page-object/blob/align-scenarios-with-328/babel.config.js#L10


text:
🛑 Rova Website is down

In 976c0de, Rova Website (https://dev.getrova.com) was down:

HTTP code: 503
Response time: 508 ms

Resolved: Rova Website is back up in f2622c6 after 10 hours, 40 minutes.

repo: roava/rova-uptime-checks


text:
Prevent change shell during setup

Is there a flag to the setup script that prevents changing to zsh after installation? I would like zsh to become the default shell but not on the shell session during installation. This is because i have an installation script which halts when installing oh my zsh. I have to manually type exit before the script resumes in the old shell.

There isn't. But this might be nice to have. (And if you want to go fully-scriptable, you'd probably want is a full "non-interactive" flag for the installer, because there are other points it might block and wait on user input as well, like the password for chsh.) The line at the end where it sources ~/.zshrc after returning from the subshell (or inside the subshell, depending on how the installer was run) may be an issue too.
Since the installer is a core part of OMZ, changes to it take a while to go through. However, the installer doesn't care where it's run from, so you can easily make your own variant of it. Just create a new repo, copy the installer over, remove those last couple lines, and use the URL to your installer instead of the default one when doing your scripted installations.

Just create a new repo, copy the installer over, remove those last couple
lines, and use the URL to your installer instead of the default one when
doing your scripted installations.

That's how babun does it anyway, I think. A simple git clone and the zshrc
file modification is all that's needed, in fact.

I don't find the trigger line for starting the actual z-shell. There are a lot of things being sourced though

I'm not sure I understand what you're saying here.
Aside from its installer, nothing in Oh My Zsh starts zsh. It works the other way around: you start zsh somehow (for example, by starting a new terminal session), and zsh automatically loads ~/.zshrc as part of its startup sequence, and then ~/.zshrc loads Oh My Zsh by sourcing ~/.oh-my-zsh/oh-my-zsh.sh.

@apjanke i observed that after running sh -c "$(curl -fsSL https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh)" the prompt changes, then when i type exit i return to me previous prompt and my setup script continues. This is made me to belief that zsh was started as sub-shell by oh-my-zsh.

Ah: yes, during the installer, it is. But that's just a one-time quirk of the installer (sort of giving you a preview of what your zsh will look like from now on), and doesn't reflect normal usage of OMZ. (There's a longish discussion of this in #3664.)
Once it's installed, the normal sequence is: you start up a shell session, and OMZ is loaded automatically from ~/.zshrc.

Is it possible to disable this functionality? (the one-time quirk of the installer)

Easy change. Just comment out these last two lines
env zsh
. ~/.zshrc

thanks @apjanke shall i leave the issue open for the official option?

We can open a tracking issue related to the install script and point here. There are a number of issues with it and we should collect them. It doesn't matter if this one is closed, we got the feature request and we'll put it there.
TL;DR you can close this one thanks :grin:

Could wrap the code in a file descriptor check:
# Do not prompt user unless STDIN file descriptor is bound to TTY,
if [ -t 0 ]; then
  # chsh
  # env zsh
fi

Then run the install like:
0>/dev/null sh -c "$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh)"

I've done some hacking, for automating OMZ installation process:
sh -c "$(curl -fsSL https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh | sed '/\s*env\s\s*zsh\s*/d')" \

For other modifications, it's better to revert them after running the install script. See http://lezsakdomi-home.herokuapp.com/.bashrc and grep for oh-my-zsh

NO_INTERACTIVE=true sh -c "$(curl -fsSL https://raw.githubusercontent.com/subtlepseudonym/oh-my-zsh/feature/install-noninteractive/tools/install.sh)"

Hi there, I pulled the changes from #7266 in #5169, which mean you can now add --skip-chsh to the install script call, as well as set the environment variable CHSH to no so that the script doesn't attempt to change the default shell. You can also run it with --unattended so that zsh is not run at the end of the install.
If you want to help speed up the testing and merge (which should happen early next week), you can wget or curl it from the URL https://raw.githubusercontent.com/mcornella/oh-my-zsh/refactor-installer/tools/install.sh. Read the comments at the top of the script to know how to call it.
Thanks!

authors: Tomotoes apjanke flip111 leoj3n lezsakdomi mcornella

repo: robbyrussell/oh-my-zsh


text:
401 Unauthorized all the time from Postman with Token verified and sent as either headers or params

I have a backend REST API built with Node + Express + Passport and I'm trying to authenticate using a google access token. I am using this strategy.
I have looked through the package's documentation and issues on github but there was nothing that fixed the issue.
I have verified the access token against:
https://www.googleapis.com/oauth2/v1/tokeninfo?idToken with the id Token and https://www.googleapis.com/oauth2/v1/tokeninfo?acessToken with the access token and both are valid but none of them work. I have double-triple checked that I'm using the correct clientID and secret on the backend and on the frontend I get the token from.
Here's the relevant code:
>
> app.use(passport.initialize());
> passport.use(
>   new GoogleTokenStrategy(
>     {
>       clientID: config.get('google.clientID'),
>       clientSecret: config.get('google.clientSecret')
>     },
>     function(accessToken, refreshToken, profile, done) {
>       User.findOrCreate({ googleId: profile.id }, function(err, user) {
>         return done(err, user);
>       });
>     }
>   )
> );
>
> app.use('/user', passport.authenticate('google-token'), userRoute);

and I am importing at the top as follows:

const passport = require('passport');
const GoogleTokenStrategy = require('passport-google-token').Strategy;

The app isn't throwing out any kind of errors.

In my case this was being thrown because of the User.findOrCreate logic that I didn't even had defined. Facebook token passport package throws an internal server error because of that but the google one would just silently fail with no message.
I will define my findOrCreate logic later down the development process. For now, this works for testing:
  new GoogleTokenStrategy(
    {
      clientID: config.get('google.clientID'),
      clientSecret: config.get('google.clientSecret')
    },
    function(accessToken, refreshToken, profile, done) {
      return done(null, profile);
    }
  )
);```

Hey folks - Just FYI that this repo hasn't been active in a long time, and I'd love to hand it off. If anyone is interested in taking over, let me know! Otherwise I'll likely archive in the near future. Thanks.

authors: robertdimarco sebastiangug

repo: robertdimarco/passport-google-token


text:
tts_sync_state not working on swiftmac start-up

I have been debugging why setting mac-default-speech-rate doesn't seem to take effect. I noticed that Emacspeak is sending the rate on server start, but Swiftmac isn't setting it.
Steps to reproduce:

Set the speech rate using C-u C-e d r 0.7
Restart the TTS using C-e C-s. notice that the speech rate gets reset to default, even though all Emacs variables are still as you left them
Here is what Emacspeak sends log-swiftmac:
tts_sync_state all 1 1 0.7
The 0.7 is the rate that Swiftmac should be at which is getting ignored.

OK, so that means that it is not ignorable. It must be implemented.
Easy enough to put back and I will need to go update the docs.
I wonder if it makes sense to make that not use sync state, but to directly send it.

On Apr 17, 2024, at 06:04, Parham Doustdar @.***> wrote:
I have been debugging why setting mac-default-speech-rate doesn't seem to take effect. I noticed that Emacspeak is sending the rate on server start, but Swiftmac isn't setting it.
Steps to reproduce:
• Set the speech rate using C-u C-e d r 0.7
• Restart the TTS using C-e C-s. notice that the speech rate gets reset to default, even though all Emacs variables are still as you left them
Here is what Emacspeak sends log-swiftmac:
tts_sync_state all 1 1 0.7
The 0.7 is the rate that Swiftmac should be at which is getting ignored.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

--
Robert Melton
@.***

I think this clears up that tts_sync_state must be instant as well.  Will put it back.

fixed./

authors: parhamdoustdar robertmeta

repo: robertmeta/swiftmac


text:
Make size changing animation less funky

The current animation for changing size (e.g. "1234" to "12345") is a bit funky when the animation is slowed down. Investigate how to improve this behavior.

I believe that this is fixed by the latest levenshtein commit.

repo: robinhood/ticker


text:
Releases from helmfiles are ignored when the environment is specified

I'm facing the issue when releases defined in separate .yaml files and referenced via helmfiles: are ignored when I try to install the full stack for a certain environment.
Example:
#environments.yaml
environments:
  dev:
  staging:
  production:

#helmfiles/namespaces.yaml
repositories:
  - name: incubator
    url: https://kubernetes-charts-incubator.storage.googleapis.com/

releases:
  - name: namespaces
    namespace: default
    chart: incubator/raw
    values:
      - resources:
        - apiVersion: v1
          kind: Namespace
          metadata:
            name: redis
          spec:

#helmfile.yaml
bases:
- environments.yaml
---
helmfiles:
  - helmfiles/namespaces.yaml

repositories:
  - name: stable
    url: https://kubernetes-charts.storage.googleapis.com

helmDefaults:
  verify: false
  wait: false
  timeout: 600
  recreatePods: false
  force: true

releases:
  - name: redis
    namespace: redis
    chart: stable/redis
    version: ~9.2.1
    values:
      - usePassword: false
        cluster:
          enabled: false

Then, let's try to output the list of releases
ip113:helmfile andrewnazarov$ helmfile -e staging --log-level=debug list
processing file "helmfile.yaml" in directory "."
first-pass rendering starting for "helmfile.yaml.part.0": inherited=&{staging map[] map[]}, overrode=<nil>
first-pass uses: &{staging map[] map[]}
first-pass rendering output of "helmfile.yaml.part.0":
 0: bases:
 1: - environments.yaml

error in first-pass rendering: result of "helmfile.yaml.part.0":
 0: bases:
 1: - environments.yaml

first-pass produced: &{staging map[] map[]}
first-pass rendering result of "helmfile.yaml.part.0": {staging map[] map[]}
second-pass rendering result of "helmfile.yaml.part.0":
 0: bases:
 1: - environments.yaml

first-pass rendering starting for "environments.yaml.part.0": inherited=&{staging map[] map[]}, overrode=<nil>
first-pass uses: &{staging map[] map[]}
first-pass rendering output of "environments.yaml.part.0":
 0: environments:
 1:   dev:
 2:   staging:
 3:   production:

first-pass produced: &{staging map[] map[]}
first-pass rendering result of "environments.yaml.part.0": {staging map[] map[]}
vals:
map[]
defaultVals:[]
second-pass rendering result of "environments.yaml.part.0":
 0: environments:
 1:   dev:
 2:   staging:
 3:   production:

merged environment: &{staging map[] map[]}
merged environment: &{staging map[] map[]}
first-pass rendering starting for "helmfile.yaml.part.1": inherited=&{staging map[] map[]}, overrode=<nil>
first-pass uses: &{staging map[] map[]}
first-pass rendering output of "helmfile.yaml.part.1":
 0: helmfiles:
 1:   - helmfiles/namespaces.yaml
 2:
 3: repositories:
 4:   - name: stable
 5:     url: https://kubernetes-charts.storage.googleapis.com
 6:
 7: helmDefaults:
 8:   verify: false
 9:   wait: false
10:   timeout: 600
11:   recreatePods: false
12:   force: true
13:
14: releases:
15:   - name: redis
16:     namespace: redis
17:     chart: stable/redis
18:     version: ~9.2.1
19:     values:
20:       - usePassword: false
21:         cluster:
22:           enabled: false

first-pass produced: &{staging map[] map[]}
first-pass rendering result of "helmfile.yaml.part.1": {staging map[] map[]}
vals:
map[]
defaultVals:[]
second-pass rendering result of "helmfile.yaml.part.1":
 0: helmfiles:
 1:   - helmfiles/namespaces.yaml
 2:
 3: repositories:
 4:   - name: stable
 5:     url: https://kubernetes-charts.storage.googleapis.com
 6:
 7: helmDefaults:
 8:   verify: false
 9:   wait: false
10:   timeout: 600
11:   recreatePods: false
12:   force: true
13:
14: releases:
15:   - name: redis
16:     namespace: redis
17:     chart: stable/redis
18:     version: ~9.2.1
19:     values:
20:       - usePassword: false
21:         cluster:
22:           enabled: false

merged environment: &{staging map[] map[]}
processing file "namespaces.yaml" in directory "helmfiles"
changing working directory to "/Users/andrewnazarov/Repo/iris/test/helmfile/helmfiles"
first-pass rendering starting for "namespaces.yaml.part.0": inherited=&{staging map[] map[]}, overrode=<nil>
first-pass uses: &{staging map[] map[]}
first-pass rendering output of "namespaces.yaml.part.0":
 0: repositories:
 1:   - name: incubator
 2:     url: https://kubernetes-charts-incubator.storage.googleapis.com/
 3:
 4: releases:
 5:   - name: namespaces
 6:     namespace: default
 7:     chart: incubator/raw
 8:     values:
 9:       - resources:
10:         - apiVersion: v1
11:           kind: Namespace
12:           metadata:
13:             name: redis
14:           spec:

first-pass produced: &{staging map[] map[]}
first-pass rendering result of "namespaces.yaml.part.0": {staging map[] map[]}
vals:
map[]
defaultVals:[]
second-pass rendering result of "namespaces.yaml.part.0":
 0: repositories:
 1:   - name: incubator
 2:     url: https://kubernetes-charts-incubator.storage.googleapis.com/
 3:
 4: releases:
 5:   - name: namespaces
 6:     namespace: default
 7:     chart: incubator/raw
 8:     values:
 9:       - resources:
10:         - apiVersion: v1
11:           kind: Namespace
12:           metadata:
13:             name: redis
14:           spec:

changing working directory back to "/Users/andrewnazarov/Repo/iris/test/helmfile"
NAME 	NAMESPACE	INSTALLED	LABELS
redis	redis    	true

Without environment specified everything looks ok:
ip113:helmfile andrewnazarov$ helmfile --log-level=debug list
processing file "helmfile.yaml" in directory "."
first-pass rendering starting for "helmfile.yaml.part.0": inherited=&{default map[] map[]}, overrode=<nil>
first-pass uses: &{default map[] map[]}
first-pass rendering output of "helmfile.yaml.part.0":
 0: bases:
 1: - environments.yaml

error in first-pass rendering: result of "helmfile.yaml.part.0":
 0: bases:
 1: - environments.yaml

first-pass produced: &{default map[] map[]}
first-pass rendering result of "helmfile.yaml.part.0": {default map[] map[]}
second-pass rendering result of "helmfile.yaml.part.0":
 0: bases:
 1: - environments.yaml

first-pass rendering starting for "environments.yaml.part.0": inherited=&{default map[] map[]}, overrode=<nil>
first-pass uses: &{default map[] map[]}
first-pass rendering output of "environments.yaml.part.0":
 0: environments:
 1:   dev:
 2:   staging:
 3:   production:

first-pass produced: &{default map[] map[]}
first-pass rendering result of "environments.yaml.part.0": {default map[] map[]}
vals:
map[]
defaultVals:[]
second-pass rendering result of "environments.yaml.part.0":
 0: environments:
 1:   dev:
 2:   staging:
 3:   production:

merged environment: &{default map[] map[]}
merged environment: &{default map[] map[]}
first-pass rendering starting for "helmfile.yaml.part.1": inherited=&{default map[] map[]}, overrode=<nil>
first-pass uses: &{default map[] map[]}
first-pass rendering output of "helmfile.yaml.part.1":
 0: helmfiles:
 1:   - helmfiles/namespaces.yaml
 2:
 3: repositories:
 4:   - name: stable
 5:     url: https://kubernetes-charts.storage.googleapis.com
 6:
 7: helmDefaults:
 8:   verify: false
 9:   wait: false
10:   timeout: 600
11:   recreatePods: false
12:   force: true
13:
14: releases:
15:   - name: redis
16:     namespace: redis
17:     chart: stable/redis
18:     version: ~9.2.1
19:     values:
20:       - usePassword: false
21:         cluster:
22:           enabled: false

first-pass produced: &{default map[] map[]}
first-pass rendering result of "helmfile.yaml.part.1": {default map[] map[]}
vals:
map[]
defaultVals:[]
second-pass rendering result of "helmfile.yaml.part.1":
 0: helmfiles:
 1:   - helmfiles/namespaces.yaml
 2:
 3: repositories:
 4:   - name: stable
 5:     url: https://kubernetes-charts.storage.googleapis.com
 6:
 7: helmDefaults:
 8:   verify: false
 9:   wait: false
10:   timeout: 600
11:   recreatePods: false
12:   force: true
13:
14: releases:
15:   - name: redis
16:     namespace: redis
17:     chart: stable/redis
18:     version: ~9.2.1
19:     values:
20:       - usePassword: false
21:         cluster:
22:           enabled: false

merged environment: &{default map[] map[]}
processing file "namespaces.yaml" in directory "helmfiles"
changing working directory to "/Users/andrewnazarov/Repo/iris/test/helmfile/helmfiles"
first-pass rendering starting for "namespaces.yaml.part.0": inherited=&{default map[] map[]}, overrode=<nil>
first-pass uses: &{default map[] map[]}
first-pass rendering output of "namespaces.yaml.part.0":
 0: repositories:
 1:   - name: incubator
 2:     url: https://kubernetes-charts-incubator.storage.googleapis.com/
 3:
 4: releases:
 5:   - name: namespaces
 6:     namespace: default
 7:     chart: incubator/raw
 8:     values:
 9:       - resources:
10:         - apiVersion: v1
11:           kind: Namespace
12:           metadata:
13:             name: redis
14:           spec:

first-pass produced: &{default map[] map[]}
first-pass rendering result of "namespaces.yaml.part.0": {default map[] map[]}
vals:
map[]
defaultVals:[]
second-pass rendering result of "namespaces.yaml.part.0":
 0: repositories:
 1:   - name: incubator
 2:     url: https://kubernetes-charts-incubator.storage.googleapis.com/
 3:
 4: releases:
 5:   - name: namespaces
 6:     namespace: default
 7:     chart: incubator/raw
 8:     values:
 9:       - resources:
10:         - apiVersion: v1
11:           kind: Namespace
12:           metadata:
13:             name: redis
14:           spec:

merged environment: &{default map[] map[]}
changing working directory back to "/Users/andrewnazarov/Repo/iris/test/helmfile"
NAME      	NAMESPACE	INSTALLED	LABELS
namespaces	default  	true
redis     	redis    	true

The same story for helmfile diff and helmfile apply.
helmfile version v0.94.0
Also, the v0.94.1 has been checked for helmfile list. This issue looks like #1009, but not exactly the same.

The example could be simplified a bit by eliminating bases::
#helmfiles/namespaces.yaml
repositories:
  - name: incubator
    url: https://kubernetes-charts-incubator.storage.googleapis.com/

releases:
  - name: namespaces
    namespace: default
    chart: incubator/raw
    values:
      - resources:
        - apiVersion: v1
          kind: Namespace
          metadata:
            name: redis
          spec:

#helmfile.yaml
helmfiles:
  - helmfiles/namespaces.yaml

repositories:
  - name: stable
    url: https://kubernetes-charts.storage.googleapis.com

helmDefaults:
  verify: false
  wait: false
  timeout: 600
  recreatePods: false
  force: true

environments:
  dev:
  staging:
  production:

releases:
  - name: redis
    namespace: redis
    chart: stable/redis
    version: ~9.2.1
    values:
      - usePassword: false
        cluster:
          enabled: false

It seems I need to define environments for the subhelmfile as well like:
#helmfiles/namespaces.yaml
repositories:
  - name: incubator
    url: https://kubernetes-charts-incubator.storage.googleapis.com/

environments:
  dev:
  staging:
  production:

releases:
  - name: namespaces
    namespace: default
    chart: incubator/raw
    values:
      - resources:
        - apiVersion: v1
          kind: Namespace
          metadata:
            name: redis
          spec:

In that case, all releases are taken into consideration.

@andrewnazarov Hey! I've reread your original example and now realized the issue.
Yes, you need to define environments in every sub-helmfile involved, and that's how it works.
The expected use-case of this feature is "fail on a missing env detected". Like, say you had two environments prod and preview and two helmfile for app1 and app2 respectively. What if app2 missed prod env when you run helmfile -e prod? You'll probably want Helmfile to fail saying app2 has no environment named "prod".

Regardless of how it works today, I spotted two possible enhancements to Helmfile thanks to your report:

Based on https://github.com/roboll/helmfile/issues/1010#issuecomment-561358232, in your case helmfile -e prod should have failed due to an error like helmfiles/namespaces.yaml has no releases for env "prod", but it didn't. Maybe this is a bug?
Can we enhance Helmfile so that helmfile -e prod won't fail in your example? To make it possible, I would change Helmfile to NOT fail on helmfile -e prod when helmfile.yaml doesn't include environments at all.

@mumoshu In my case, the releases from sub-helmfiles were silently ignored. Thus, I was confused.
Basically there could be a few use cases for sub-helmfiles:

The umbrella helmfile with only references to external helmfiles
Regular helmfile with releases and stuff, but at the same time referencing to some external helmfiles.

I got the point about processing the sub-helmfile before the root one, so it's strange to take some part of the payload from the base.
On the other hand, it feels natural and DRY-compliant to define environments ones and use them everywhere. If I want to ignore the release for a certain env I can do if-logic.
So, I really don't know what is better. I can understand both approaches.
I would prefer either using "global" environments (taken from the "root" file) or at least be warned by the output somehow.

I got the point about processing the sub-helmfile before the root one

I just want to be clear on this - What do you mean by "processing" here?
Helmfile never processes, say, the namespaces releases in the sub-helmfile. It just double-render it, merge the parent helmfile.yaml onto it, then processes(sync,apply,etc) releases in the merged helmfile.yaml.

The umbrella helmfile with only references to external helmfiles
Regular helmfile with releases and stuff, but at the same time referencing to some external helmfiles.

Agreed.

so it's strange to take some part of the payload from the base.

What do you mean by here exactly?

it feels natural and DRY-compliant to define environments ones and use them everywhere. If I want to ignore the release for a certain env I can do if-logic.

Yeah, but the downside of this is that it makes sub-helmfiles less modularized i.e. depends on environments provided externally.

at least be warned by the output somehow.

How would you like to be warned in your case?

Helmfile never processes, say, the namespaces releases in the sub-helmfile. It just double-render it, merge the parent helmfile.yaml onto it, then processes(sync,apply,etc) releases in the merged helmfile.yaml.

Oh, I've got lost a bit.
It's stated:
helmfiles:
- # Path to the helmfile state file being processed BEFORE releases in this state file
  path: path/to/subhelmfile.yaml
  # Label selector used for filtering releases in the nested state.
  # For example, `name=prometheus` in this context is equivalent to processing the nested state like
  #   helmfile -f path/to/subhelmfile.yaml -l name=prometheus sync

I thought bases: are for merging.

What do you mean by here exactly?

Probably that was due to my misunderstanding. I thought sub-helmfile is run first, then the main file. In this case it's strange that some things (blocks, whatever) from the main helmfile should be taken into consideration when the sub-helmfile is applying. It seems I didn't understand the concept of helmfiles:.

Hm, actually from what I see in logs it seems it runs sub-helmfile first. Then, the main helmfile.

I thought sub-helmfile is run first, then the main file

Yes, you are correct.

some things (blocks, whatever) from the main helmfile are taken into consideration when the sub-helmfile is applying

What did you see for example? I thought nothing other than Environment.Name is inherited automatically.

Yes, you are correct.

Great! I was a bit embarrassed, now recovered:)

What did you see for example? I thought nothing other than Environment.Name is inherited automatically.

Nevermind this:).
Initially I meant that from one hand it's ok that one should explicitly define environments for sub-helmfiles process-wise, but on the other hand, it seems natural to grab things from the main helmfile to follow dry. But as you stated, you don't want such dependencies).

How would you like to be warned in your case?

Regarding the error message, probably a slight modification of the existed one would be sufficient. Like:
err: no releases found that matches specified selector() and environment(staging), in <subhelmfile_name>.

Yeah, but the downside of this is that it makes sub-helmfiles less modularized i.e. depends on environments provided externally.

But how to deal with third-party sub-helmfiles then?)

But how to deal with third-party sub-helmfiles then?)

@andrewnazarov I was considering the second point in my prev comment for that https://github.com/roboll/helmfile/issues/1010#issuecomment-561364261

That is, helmfile -e prod sync won't fail when namespaces.yaml missing environments: at all, but will fail when it has any non empty environments like environments:{"test": { whatever... }}.
WDYT @andrewnazarov ? Does that make sense?

Sorry for such a delay.
I really don't know what would be better. It was very confusing at first that releases defined in sub-helmfiles were ignored without any error or warning. Probably just a warning will be sufficient. One the other hand, if you know the actual behaviour, you'll be ready and implement things accordingly. So, it should be mentioned in docs for sure.
As I see, it's not only me expecting environments to be inherited (#1045). And probably it's better to concentrate on what you are proposing in #1048.
Right now I found a way how to deal with that, not the elegant though.

To revive this issue:

I think it would be really handy to be able to define environments in a remote / shared helmfile. This would reduce the boilerplate we run into having to copy/paste the environment block around in every helmfile.
Maybe rethink how releases are included in environments then? Releases are included in an environment through label selector matching perhaps?

authors: albertrdixon andrewnazarov mumoshu

repo: roboll/helmfile


text:
Robotcode debuger - GitHub Actions

Hello Daniel,
have you tried your debuger with GitHub Actions?
Thank you

Hi Marta,
No, not with Github Actions, but with Gitlab Pipelines. However, the procedure should be the same. Depending on where your test is running, you need to have network access to this machine to reach the debugger.
The easiest way to do this is with your own Github Actions Runner in your own network in a VM or a dedicated computer. You can find descriptions of how to set this up on the web.
Have you already tried it?

Thank you for your quick reply.
No, I have not yet.

repo: robotcodedev/robotcode


text:
krr cannot connect to clusters using certificates signed by a private CA, stored in system CA store

Describe the bug
A clear and concise description of what the bug is.
To Reproduce

Set up a Kubernetes cluster with the API server certificate signed by a private CA
Add the private CA to your system CA management tool (platform specific)
Add the cluster into your kubeconfig, don't explicitly provide the CA

Expected behavior
krr should be able to connect to the cluster, just as kubectl is able to.
Logs
on 0: [INFO] Listing scannable objects in private-cluster
on 0: [ERROR] Error trying to list hpa in cluster private-cluster:
      HTTPSConnectionPool(host='controller.private-cluster.com', port=443): Max retries exceeded with url:
      /apis/autoscaling/v2/horizontalpodautoscalers?watch=False (Caused by SSLError(SSLCertVerificationError(1, '[SSL:
      CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)')))
on 0: [ERROR] Will assume that there are no HPA. Be careful as this may lead to inaccurate results if object actually has HPA.

Desktop (please complete the following information):

OS: MacOS 13.5.2
Version KRR 1.6.0

Additional context
Even providing an "insecure" option would be helpful. Right now I need to run a local proxy that krr can connect to, which is a pain.

I had the same issue. Installing module pip_system_certs solved it.
All the ways to fix it (f.i. for MacOS) are mentioned here: https://stackoverflow.com/questions/50236117/scraping-ssl-certificate-verify-failed-error-for-http-en-wikipedia-org

I spent quite a lot of time, tried importing certificates into macos keychain and so on but it didn't work.
It would make sense to have an option to have a flag like --insecure to simply skip this certificate valdiation.

Yes, we should be able to add something like that.
Slightly off-topic, but we're currently doing user interviews to prioritize issues for KRR next year. If any of you are open to participating, can you please message me (Natan Yellin) on the Robusta slack. We'll send every participant a "Chief YAML Officer T-shirt" in appreciation.

Just add insecure-skip-tls-verify: true inside cluster item in your kubeconfig file.

apiVersion: v1
clusters:
- cluster:
    insecure-skip-tls-verify: true
    certificate-authority-data: CA_DATA
    server: https://kube:6443
  name: kubernetes
....

I had the same issue. Installing module pip_system_certs solved it. All the ways to fix it (f.i. for MacOS) are mentioned here: https://stackoverflow.com/questions/50236117/scraping-ssl-certificate-verify-failed-error-for-http-en-wikipedia-org

For me this does not seem to work for kubernetes calls, because the kubernetes lib uses urllib3 directly and not requests which is patched by the module pip_system_certs.
But the insecure-skip-tls-verify: true in the kube config file definitely works.

Is it possible to fix this issue from the code level?

Hi @Wyifei
Are you using self-sign certificate?
Did you try adding it using the env var as described [here](Trusting custom Certificate Authority (CA) certificate:)?

thanks for the details @Wyifei
Do you see the line added custom certificate when krr starts?

@arikalon1 yes

Thanks @Wyifei
Can you please share the entire krr output?
you're also welcome to join our Slack channel here:
https://bit.ly/robusta-slack
We're more responsive there

authors: Beauline Wyifei aantn arikalon1 camaeel ecourreges-orange jutley littlechicks

repo: robusta-dev/krr


text:
Disabling "Event" resources does not work

Hi, the option to ignore "Event" resources doesn't seem to work.
I tried to specify in the configuration similarly to other modules:
resourcesToWatch:
  event: false

or
resourcesToWatch:
  events: false

This does not help, I see in the logs that the corresponding module starts despite the configuration:
time="2023-01-27T10:09:55Z" level=info msg="Starting kubewatch controller" pkg=kubewatch-Event

On our large cluster, this gives a lot of noise in notifications to Slack. Thank you in advance!

Hi @petrov-e
Thanks for reporting it
What is the chart version you're using?
(You can easily see it with helm list)

@arikalon1
version: 3.3.6

Thanks.
I think there's a bug in that chart version.
Can you please try it with version 3.3.5?
Just add to the helm install command --version 3.3.5
Can you update if you see the same issue on 3.3.5?

There is no such problem in 3.3.5 version of the chart, since a different version of the image is used: docker.io/bitnami/kubewatch:0.1.0-debian-10-r571. There is no kubewatch-Event controller in this version.
But in this version there is a bug described here: https://github.com/robusta-dev/kubewatch/issues/20
"Missing" namespace. It looks like this:

Thanks for the update @petrov-e
We're looking into it

@petrov-e you are right that functionality is missing ( to disable events resources ) We will add it to the next version.
We just released 3.3.7 with a fix to the name space image you have added

Just deployed kubewatch in a development cluster and started to see the same issue. My events are related to the max dns search list:
Search Line limits were exceeded, some search paths have been omitted, the applied search line is: monitoring.svc.cluster.local svc.cluster.local cluster.local my.corp.com your.corp.com our.corp.com
This isn't easy to fix on our side since the max dns search is a current limitation. There is a feature gate available in 1.23 but it's in alpha:
https://v1-23.docs.kubernetes.io/docs/concepts/services-networking/dns-pod-service/
https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/
Certain events are definitely helpful, it would perhaps be better to exclude certain events from the notifications?

Thanks for reporting it @backaf
Would you be willing to contribute a PR for that enhancement? (adding exclusion filters to kubewatch)
Alternatively, if you're only interested in k8s warning events, if can you send the via Robusta, you could do the filtering there.

I'm definitely not experienced enough for such a PR, otherwise it would have sounded like a nice challenge :)
Currently I'm hitting the Teams webhook rate limits so I won't be able to use kubewatch in our clusters. I will take a look at Robusta, I didn't know about it! Thanks!

authors: RoiGlinik arikalon1 backaf petrov-e

repo: robusta-dev/kubewatch


text:
Unknown named parameter $sandbox

Hello! Have issue with adapter.
craftcms/cms: "4.5.10"
PHP 8.1.5 (cli) (built: Apr 12 2022 17:38:57) (ZTS Visual C++ 2019 x64)
Exception 'Error' with message 'Unknown named parameter $sandbox'.

What version of symfony/mailjet-mailer do you have in your composer.lock?

@boboldehampsink I am seeing the same error with symfony/mailjet-mailer locked at v6.0.19.

php: 8.2
craftcms/cms: 4.5.10
robuust/craft-mailjet: 1.0.4
symfony/mailjet-mailer: 6.0.19

Can you update symfony/mailjet-mailer? It must be at least version 6.3

authors: ManiakMill boboldehampsink yoannisj

repo: robuust/craft-mailjet


text:
Disable some tests in debug failing with stack overflow

Context

@ayazhafiz we'll need to fix this properly though, right?

authors: dlsmith folkertdev

repo: roc-lang/roc


text:
Unicode error on new version

I made a upgrade to the new version and i'm getting a JS error now:
`var raw_markers = [{'lat': u'-19.9520738', 'lng': u'-43.9490132', 'icon': '//maps.google.com/mapfiles/ms/icons/red-dot.png'}];``
You can see that it is including u in front of lat lng.
I checked in the source and it seems to be correct gmap.markers|tojson|safe , but when using pip install flask-googlemaps --upgrade it is not installing the same version that we have here.
Is something needed to update on pip? Maybe need to change the version? (from 0.2.2 to 0.2.3) ?

Hi @mariohmol I just released 0.2.3 with the latest changes from master.

Looks fine in 0.2.3 thanks for bringing it up

Is that not compatible with py2.6 anymore? getting a error
from flask.ext.googlemaps import GoogleMaps
File "/usr/lib/python2.6/site-packages/flask/exthook.py", line 77, in load_module
import(realname)
File "/usr/lib/python2.6/site-packages/flask_googlemaps/init.py", line 263
if {'north', 'east', 'south', 'west'} != set(kwargs['bounds'].keys()):
^
SyntaxError: invalid syntax

@mariohmol  good question, I dont know.
this line
if {'north', 'east', 'south', 'west'} != set(kwargs['bounds'].keys()):

can be replaced by
if set(('north', 'east', 'south', 'west')) != set(kwargs['bounds'].keys()):

If this is the only thing needed I thing we can change it and make it compatible again.

please!! =)

Here as well... changed here and worked https://github.com/rochacbruno/Flask-GoogleMaps/blob/master/flask_googlemaps/init.py#L391

@mariohmol check 0.2.4 (let me know if it works)

worked! thanks

authors: mariohmol rochacbruno

repo: rochacbruno/Flask-GoogleMaps


text:
fixtureFilePath array

It's usefull to have multiple files, for split many data in differentes files, this PR have no regression, filePath can be an array of path or (like actually) just a string

Why support node 4 & 6 , 8.9 in LST since november 2017

Hi
I check at least forNodeJs 4.x because the NodeJs version fragmentation show there are still a lot of people using NodeJs less thant 6.x (nearly 30% if I remember). So this is important to check if it could work too on their side.
So please not use for the moment the "async" keyword (which is only a shortcut to generate a Promise)
Maybe I should put more documentation, but we already could load multiple file with using this syntax:
sequelize_fixtures.loadFile('fixtures/*.json', models, {})

However, I will adapt the fixtureFilePath parameter to allow declare an array so use the following methods (instead made a for-loop):
sequelize_fixtures.loadFiles(['fixtures/users.json', 'fixtures/data*.json'], models, {})

Could do create an enhancement ticket please ?
Many thanks

Plus, Sequelize itself tries to be compatible with NodeJs 4.x: https://github.com/sequelize/sequelize/blob/master/package.json#L141
Regards

Yep *.json it's not good, for respect sql contraint I need to insert data in the right order and sync

Many thanks
Two feedbacks:

You shoud update line https://github.com/rochejul/sequelize-mocking/blob/master/lib/sequelize-mocking.js#L109 to specify the update of the fixtureFilePath for the method createAndLoadFixtureFile
Could you please add a unit test to check if we call welly the loadFiles method please ?

Many thanks again
Regards

I will perte jour pull request this week-end ans update the documentation and unit test
Regards

Many thanks: I have published on npm the 1.3.0-beta version with your updates
Regards

authors: julesGoullee rochejul

repo: rochejul/sequelize-mocking


text:
Add a transitive test property

This is a minimal reproducer that's essentially A ~> B ~> C. The that_subscribes_to matcher shows that this is equal to A ~> C but in practice Puppet doesn't work that way. The service is not restarted if the file is modified.
I don't know what is the expected behavior here, but it does mean that today it's not possible to test for real world behavior.
I've submitted this as a PR since it's the easiest way to submit code and show CI results for it.

@sanfrancrisko was there ever any progress on this discussion? We've just hit this problem again and while re-reading https://puppet.com/docs/puppet/7/lang_relationships.html#lang_rel_chaining_arrows I can't really tell if A ~> B ~> C should be equivalent to A ~> B, A ~> C, B ~> C or A ~> B, B ~> C?
More explicitly, the chaining example says "Resource declarations can be chained. That means you can use chaining arrows to make Puppet apply a section of code in the order that it is written. This example applies configuration to the package, the file, and the service, in that order, with each related resource notifying the next of any changes" (emph. mine) where one could interpret "any changes" as "any changes to itself" and not "any changes in the whole chain".

Please continue the discussion in https://github.com/puppetlabs/rspec-puppet/pull/29

authors: ekohl evgeni

repo: rodjek/rspec-puppet


text:
Implement computedFromAsync

ComputedFrom is mentioned in the async section of the docs https://dartsignals.dev/async/computed/ . But there is not a computedFromAsync function. This doc section should probably be moved to https://dartsignals.dev/core/computed/ . And an async version of computedFrom (computedFromAsync) implemented.

computedFrom is already async :laughing:


text:
sched: priority queues

Things Do:

[x] What is happening with task 4? why it didn't run? [check image]
[x] Dequeue. First, check when does a task need to be removed from the queue.
[x] Implement dequeue.
[x] Check that TIDs are correct. TID 0 not runnable, idle task is which tid?, first user task 1 or two (currently is 2, but it should be 1)...

Priority queues:
sched.c:
/* Priority queue array */
struct priority_queue priority_queues[PRIORITY_LEVELS];

We basically created a queue using a linked list:
sched.h:
/* struct priority_queue
 */
struct priority_queue
{
    struct task_struct *head;
    struct task_struct *tail;
};

We obviously support enqueue and dequeue.

In the future, it would be cool to explore implementing a priority queue using other data structures.

repo: roemvaar/oso


text:
add ci pipeline to main branch

the pipline does:

create artifact of the loca nvim installed plugins

thats it

finito la comedia

repo: roeybenarieh/NvimConfig


text:
Sometimes images are not pushed

i started a build and it gave an error that feature.jpg was missing
i uploaded an image (just started the build i did not publish)
build failed and said feature.jpg did not exists (no commit found in history)

Fixed by 7dbae7164c367f05f4dd9fd0efbc5b4e2a92eb42

authors: RubenMattan lucasvanhalst


text:
Read more effect

Is there a way to make a read more affect (possibly by making collapsed height prop a percentage)?

After doing a deep-dive into how one might make this, I've found that the easiest solution would be two nest a second instance of a collapse within another. It gets really complicated to handle 3 states for the collapse.
The implementation would look something like this. But instead of deliberately segmenting the content, you'd use the collapsedHeight option to something like 200, or whatever you'd like to collapse it too.

Thank you so much.

Is there a way to make that the nested component when expanded should not go on the next line (using span messes up the animation)

repo: roginfarrer/collapsed


text:
add 'gohack list' or shell completion support

Many package paths are long. To ease typing, I suggest either/both of:

add gohack list, which will emit all package paths in the module, for easy copy/paste
add shell completion, so that the tab key can do the work for me

Opinions?

Would go list (with suitable flags) not suffice here, for both? I say that assuming shell completion can be made to work given the line-based output of a command

go list -m all is a decent approximation. But gohack can do a bit better, by also indicating which modules are currently being hacked on (and what directory they are in). For the modules that are also being hacked on, it could also print whether the hacked version is dirty. Also, go list -m all emits version numbers, which aren't as relevant for gohack.
Maybe the command should be gohack status.

Erm. There is already a gohack status.
I was about to start working on a PR, but I think I'll wait for more feedback.

go list -f can probably give us whatever we need from a completions perspective, but the status showing "dirty" for -vcs hacks would definitely be useful.

authors: josharian myitcv

repo: rogpeppe/gohack


text:
Separate C code

Testing target C code with CGO can cause double linking.

Solved in noids branch

repo: rokath/cobs


text:
Add notices to require attribution to Celestia Labs for forked projects

https://opensource.stackexchange.com/questions/8161/license-that-requires-attribution-to-end-users

Updated in https://github.com/rollkit/rollkit/pull/770

authors: Manav-Aggarwal musalbas

repo: rollkit/rollkit


text:
Make transform stateless

This follows up on @tivac's suggestion in https://github.com/rollup/rollup/pull/658 – rather than tracking which CommonJS features are used and injecting them haphazardly using the intro hook, modules import commonjsHelpers. This is cleaner, and will allow the results of the transformation to be cached.
There is a wrinkle however: the synthetic ID used for the helpers goes through the same resolution process as any other ID. Since in this case that frequently means rollup-plugin-node-resolve, we end up passing trying to resolve whatever ID we use with the Node resolution algorithm, which will obviously fail.
So I'm proposing we adopt the following convention: plugins that generate synthetic helper modules, like this one, should use the null character (\0) in the ID. Plugins that implement resolveId should ignore IDs with the null character. (The reason I'm suggesting NUL is that it's invalid in filenames on both *nix and Windows.)
I've already taken the liberty of updating createFilter and node-resolve.
Any thoughts @rollup/collaborators?
Apologies for the bad git discipline, I managed to roll some extra stuff in here 😕

Neat! Prepending a module name with NUL is a decent hack. I'll update TypeScript accordingly.

authors: Rich-Harris Victorystick

repo: rollup/rollup-plugin-commonjs


text:
fake -c foo bar baz should catch all argvs starting with bar baz

$ fake -c foo bar baz
$ foo                   # reject
$ foo bar               # reject
$ foo bar baz           # accept
$ foo bar baz qux       # accept

this has been implemented.

repo: roman-neuhauser/fake


text:
Install jq at system-prep stage on all nodes.

Because it's useful -- for functionality, for operations, for tests that interact with json, etc.
Seems sensible to do it here than selectively in multiple places.

looks good.

authors: cgilmour pritesh

repo: romana/romana


text:
Base branch is fixed to main

Pull request defaults to the branch checked out in the workflow.

This statement appears invalid. From the source, I see that it is fixed to main branch which may not exist on legacy repos where the default used to be master.

@tristanlee85 I've opened a PR-8 which adds the support for a custom branch
In the meantime you can use the following action available on the marketplace which is fork of this repo and supports custom branch.

Addressed by #8

authors: emZubair romoh tristanlee85

repo: romoh/dependencies-autoupdate


text:
Add test to track #508

Also documents the current limitation around ron::Value.
* [ ] I've included my change in CHANGELOG.md

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (4697142) 100.00% compared to head (a9ff062) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##            master      #509   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           78        79    +1
  Lines        11063     11109   +46
=========================================
+ Hits         11063     11109   +46

Files Changed
Coverage Δ

tests/508_value_adjacently_tagged_bug.rs
100.00% <100.00%> (ø)

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

authors: codecov-commenter juntyr

repo: ron-rs/ron


text:
🛑 TROJAN 🇯🇵 Japan JPP 1 is down

In 5e23117, TROJAN 🇯🇵 Japan JPP 1 (https://jpt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇯🇵 Japan JPP 1 is back up in 2c509a0.

repo: roosterkid/opentunnel-status-server


text:
🛑 TROJAN 🇬🇧 United Kingdom UKO 2 is down

In 27f418a, TROJAN 🇬🇧 United Kingdom UKO 2 (https://ukt-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇬🇧 United Kingdom UKO 2 is back up in 8a083e0.


text:
🛑 XRAY 🇬🇧 United Kingdom UKO 1 is down

In 0ac6be0, XRAY 🇬🇧 United Kingdom UKO 1 (https://ukx-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇬🇧 United Kingdom UKO 1 is back up in 1a054d4.


text:
🛑 XRAY 🇩🇪 Germany DEH 1 is down

In 28715a8, XRAY 🇩🇪 Germany DEH 1 (https://dex-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇩🇪 Germany DEH 1 is back up in 48fef6a.


text:
🛑 TROJAN 🇺🇸 United States USO 1 is down

In 2b4920d, TROJAN 🇺🇸 United States USO 1 (https://ust-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇺🇸 United States USO 1 is back up in abd48a6.


text:
🛑 TROJAN 🇨🇦 Canada CAO 1 is down

In 9fd34e7, TROJAN 🇨🇦 Canada CAO 1 (https://cat-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇨🇦 Canada CAO 1 is back up in 83c623a.


text:
🛑 WG 🇸🇬 Singapore SGO 1 is down

In dc4fadc, WG 🇸🇬 Singapore SGO 1 (http://wg-sg-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: WG 🇸🇬 Singapore SGO 1 is back up in e60f18d.


text:
🛑 XRAY 🇩🇪 Germany DEH 1 is down

In b2f7437, XRAY 🇩🇪 Germany DEH 1 (https://dex-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇩🇪 Germany DEH 1 is back up in d865ad1.


text:
🛑 XRAY 🇺🇸 United States USF 1 is down

In 1a1938e, XRAY 🇺🇸 United States USF 1 (https://usx-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇺🇸 United States USF 1 is back up in 875b532.


text:
🛑 V2RAY 🇺🇸 United States USO 1 is down

In ba4eaff, V2RAY 🇺🇸 United States USO 1 (https://usv-4.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇺🇸 United States USO 1 is back up in 93c663f.


text:
🛑 V2RAY 🇳🇱 Netherlands NLI 2 is down

In 4aa7554, V2RAY 🇳🇱 Netherlands NLI 2 (https://nlv-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇳🇱 Netherlands NLI 2 is back up in 148f44c.


text:
🛑 XRAY 🇫🇷 France FRF 1 is down

In b87e437, XRAY 🇫🇷 France FRF 1 (https://frx-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇫🇷 France FRF 1 is back up in 8392f2e.


text:
🛑 V2RAY 🇫🇷 France FR 1 is down

In 4f66e53, V2RAY 🇫🇷 France FR 1 (https://frv-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇫🇷 France FR 1 is back up in 8ec9e28.


text:
🛑 V2RAY 🇳🇱 Netherlands NLI 1 is down

In 50c1a45, V2RAY 🇳🇱 Netherlands NLI 1 (https://nlv-6.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇳🇱 Netherlands NLI 1 is back up in 196d98e.


text:
🛑 V2RAY 🇺🇸 United States USO 1 is down

In ce9bb5b, V2RAY 🇺🇸 United States USO 1 (https://usv-4.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇺🇸 United States USO 1 is back up in a724265.


text:
🛑 XRAY 🇫🇷 France FRF 1 is down

In e5f2708, XRAY 🇫🇷 France FRF 1 (https://frx-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇫🇷 France FRF 1 is back up in cc46f85.


text:
🛑 TROJAN 🇺🇸 United States USO 1 is down

In 2b35f7b, TROJAN 🇺🇸 United States USO 1 (https://ust-2.optnl.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇺🇸 United States USO 1 is back up in 52bb60e.


text:
🛑 TROJAN 🇸🇬 Singapore SGP 1 is down

In c787b00, TROJAN 🇸🇬 Singapore SGP 1 (https://sgt-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇸🇬 Singapore SGP 1 is back up in 5bad902.


text:
🛑 V2RAY 🇫🇷 France FR 1 is down

In a2a9c32, V2RAY 🇫🇷 France FR 1 (https://frv-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇫🇷 France FR 1 is back up in 76896d8.


text:
🛑 SSH 🇺🇸 United States USD 1 is down

In c0b9ca0, SSH 🇺🇸 United States USD 1 (http://uss-3.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇺🇸 United States USD 1 is back up in 9792ee0.


text:
🛑 SSH 🇱🇺 Luxembourg LUF 1 is down

In 861f45b, SSH 🇱🇺 Luxembourg LUF 1 (http://lus-1.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇱🇺 Luxembourg LUF 1 is back up in dfa07b8.


text:
🛑 XRAY 🇺🇸 United States USF 1 is down

In ae277c7, XRAY 🇺🇸 United States USF 1 (https://usx-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇺🇸 United States USF 1 is back up in d5ffc70.


text:
🛑 TROJAN 🇸🇬 Singapore SGA 1 is down

In 10f42dd, TROJAN 🇸🇬 Singapore SGA 1 (https://sgt-3.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇸🇬 Singapore SGA 1 is back up in ca9173b.


text:
🛑 TROJAN 🇮🇩 Indonesia IDJ 1 is down

In c018a94, TROJAN 🇮🇩 Indonesia IDJ 1 (https://idt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇮🇩 Indonesia IDJ 1 is back up in 0d8240a.


text:
🛑 TROJAN 🇸🇬 Singapore SGO 1 is down

In 00b0f50, TROJAN 🇸🇬 Singapore SGO 1 (https://sgt-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇸🇬 Singapore SGO 1 is back up in 7f05da0.


text:
Installation error with gcc4.9?

Hi everyone,
I am having an issue installing root_numpy against root 6.04.14-x86_64-slc6-gcc49-opt.
I have the following error message:
  /afs/cern.ch/sw/lcg/contrib/gcc/4.9.1/x86_64-slc6/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.9.1/cc1plus: error while loading shared libraries: libmpc.so.3: cannot open shared object file: No such file or directory
  error: command '/afs/cern.ch/sw/lcg/contrib/gcc/4.9.1/x86_64-slc6-gcc48-opt/bin/gcc' failed with exit status 1

It works fine with root 6.04.10-x86_64-slc6-gcc48-opt
Anyone else noticed this?
Thanks!
Quentin

Looks like a local setup issue. I'll try the same on lxplus now.

I confirm. Strange that the path is /afs/cern.ch/sw/lcg/contrib/gcc/4.9.1/x86_64-slc6-gcc48-opt/bin/gcc instead of /afs/cern.ch/sw/lcg/contrib/gcc/4.9.1/x86_64-slc6-gcc49-opt/bin/gcc  (gcc49 instead of gcc48). And that file is actually present in /afs/cern.ch/sw/lcg/contrib/gcc/4.9.1/x86_64-slc6-gcc49-opt/lib.

It works if you first do this:
export LD_LIBRARY_PATH=/afs/cern.ch/sw/lcg/contrib/gcc/4.9.1/x86_64-slc6-gcc49-opt/lib:$LD_LIBRARY_PATH

That env on lxplus looks broken to me. Probably worth mentioning to Asoka et al.

authors: ndawe qbuat


text:
Fix for multiple .po files

With multiple .po files (de_DE.po, fr_FR.po) it will show the following error:
Error: Too many positional arguments: ./resources/lang/fr_FR.po
error Command failed with exit code 1.

Seems like update-po only accepts one argument and doesn't handle the *.po properly.

A bit annoying that they don't accept a glob for that subcommand — thank you for the PR 🙏

authors: retlehs sandrowuermli

repo: roots/sage


text:
#1718 wait for public IP before LND start

this should fix that LND is announcing a local IP to the network

Hey, i tested this code on my blitz successful:

Reboot
Cable Disconnect -> Screen with message to user gets displayed
Cable connect -> common info screen appears, no localIP found so far

Well done 👍

repo: rootzoll/raspiblitz


text:
Adjust tests after passing URDF to controllers

Follow-up of https://github.com/ros-controls/ros2_control/pull/1088

@bmagyar the changes look good to me, however, not sure why the tests are failing

authors: bmagyar saikishor


text:
Access RAPID arrays

New issue for @ScottYang1982's follow-up question in https://github.com/ros-industrial/abb_librws/issues/64#issuecomment-547776629, about how to access RAPID arrays.
Currently, the RWSInteface class has no function implemented to parse a RAPID array. However, it is possible to directly use the base class RWSClient instead.
Rough example:
void main()
{
  abb::rws::RWSClient::RWSResult rws_result;
  std::string value;

  // Note: This example assume the following:
  // - The RAPID task "T_ROB1" exists.
  // - The task has a module named "TRobMain".
  // - The module has a RAPID num array, of size 5, declared as "VAR num my_num_array{5};".
  abb::rws::RWSClient::RAPIDResource rapid_resource("T_ROB1", "TRobMain", "my_num_array");

  abb::rws::RWSClient rws_client("127.0.0.1");

  //--------------------------------------------------------------
  // Get the RAPID array
  //--------------------------------------------------------------
  rws_result = rws_client.getRAPIDSymbolData(rapid_resource);
  value = abb::rws::xmlFindTextContent(rws_result.p_xml_document, abb::rws::SystemConstants::RWS::XMLAttributes::CLASS_VALUE);

  std::cout << value << "\n";

  //--------------------------------------------------------------
  // Set the RAPID array
  // Note: Important to have the correct number of elements.
  //       Here it is assumed that the array has a size of 5.
  //--------------------------------------------------------------
  rws_result = rws_client.setRAPIDSymbolData(rapid_resource, "[1, 2, 3, 4, 5]");

  //--------------------------------------------------------------
  // Get the RAPID array
  //--------------------------------------------------------------
  rws_result = rws_client.getRAPIDSymbolData(rapid_resource);
  value = abb::rws::xmlFindTextContent(rws_result.p_xml_document, abb::rws::SystemConstants::RWS::XMLAttributes::CLASS_VALUE);

  std::cout << value << "\n";
}

The output should be something like this:
[0,0,0,0,0]
[1,2,3,4,5]

Closing as I believe this has answered the question.

authors: gavanderhoorn jontje