Still hscope troubles with LTS-8.5

When opening a new file or doing ,hl I get:
Error detected while processing function LoadHscope:
cs_read_prompt EOF: success
E609: Cscope error: p-course does not exist

Here's the output from installing HVN
ENV: [HVN_INSTALL_BASIC=]
ENV: [HVN_GENERATE_HOOGLE_DB=y]
--> Existing Haskell-Vim-Now installation detected at /home/torstein/.config/haskell-vim-now.
--- Syncing Haskell-Vim-Now with upstream...
Current branch master is up to date.
--- Installing system packages [libcurl-devel zlib-devel powerline] using [DNF]...
--- Installing with DNF...
Package libcurl-devel-7.51.0-6.fc25.x86_64 is already installed, skipping.
Package zlib-devel-1.2.8-10.fc24.x86_64 is already installed, skipping.
Package powerline-2.5-3.fc25.x86_64 is already installed, skipping.
--- Checking ctags' exuberance...
--- Setting git to use fully-pathed vim for messages...
--- Testing for broken Ruby interface in vim...
--- Test passed. Ruby interface is OK.
--- Backing up current vim config using timestamp 20170424_151200...
	/home/torstein/.config/haskell-vim-now/backup/.vim.20170424_151200
	/home/torstein/.config/haskell-vim-now/backup/.vimrc.20170424_151200
--- Creating vim config symlinks
	~/.vimrc -> /home/torstein/.config/haskell-vim-now/.vimrc
	~/.vim   -> /home/torstein/.config/haskell-vim-now/.vim
--- Installing plugins using vim-plug...

--- <---- HASKELL VIM NOW installation successfully finished ---->

Hscope seems to be present:
ls ~/.local/bin
codex  ghc-mod  ghc-modi  hasktags  hlint  hoogle  hscope  pointfree  pointful  refactor

The global stack resolver set in .stack/global-project/stack.yaml is lts-8.5

Hm, that doesn't happen locally for me, try deleting the hscope binary and running the haskell-vim-now installer again. Maybe it will pull a more recent hscope where the problem will be fixed.

@tsoernes any luck with the hscope issue after re-running the installer?

I have the same issue.

@patriques82 You might try following begriffs suggestion and deleting the hscope binary in ~/.local/bin and reinstalling. You might try both installing using the global resolver and if that doesn't work then delete it again and try with the project resolver, if different. I can't remember whether I resolved this issue or not as I do not use HVN anymore.

Just tried it again, and still not able to reproduce. On a new machine of Ubuntu 16.04.3 LTS (GNU/Linux 4.4.0-87-generic x86_64) I do this as root:
apt-get update
curl -sSL https://get.haskellstack.org/ | sh

export PATH="/root/.local/bin:$PATH"
curl -L https://git.io/haskell-vim-now > /tmp/haskell-vim-now.sh
bash /tmp/haskell-vim-now.sh

Then clone and build a project as a test:
git clone https://github.com/janrain/riak-haskell-client.git
cd riak-haskell-client/
stack init
stack build
vim src/Network/Riak.hs

The editor starts up fine. Then I press ,tg to generate tags, and subsequently am able to find uses of symbols with hscope by pressing C-\. Also pressing ,hc brings up a window of compiler warnings.
So maybe tell me more about your OS version and what project you're trying to build.

I just followed the steps you provided on my Ubuntu 16.04.2 LTS. And everything installs fine - as the first time I installed haskell-vim-now - no error messages. I can do everything except find usages with hscope, when it complains with "E567: no cscope connection".

I can do everything except find usages with hscope, when it complains with "E567: no cscope connection".

Have you verified that you ran ",tg" in the project to generate tags? It should create an "hscope.out" file in your project directory. Whenever vim loads a Haskell file in a buffer it will search for he hscope file and will use it as the cscope database. This comes from line 64 in the vimrc.haskell file of haskell-vim-now:
function! LoadHscope()
let db = findfile("hscope.out", ".;")
if (!empty(db))
let path = strpart(db, 0, match(db, "/hscope.out$"))
set nocscopeverbose " suppress 'duplicate connection' error
exe "cs add " . db . " " . path
set cscopeverbose
endif
endfunction
au BufEnter /*.hs call LoadHscope()

Did this suggestion help?

Hi Joe, sorry for my late reply. When I ran ,tg only a codex.tags where generated. So that is the problem probably.

OK, I'll close this issue.

Hi Joe, Thank you for maintaining this useful Haskell resource.  This is a bit of a "meta", but despite my searching around, I can't seem to figure out the following.  What is the relationship between
hscope (a cscope alternative) and codex (a tag generator)?  Do they work sequentially to generate a tag file?

Several years ago I gave this talk about how the tools relate to one another - https://begriffs.com/posts/2015-07-27-haskell-source-navigation.html
(about 5:00 in I give a demo of the codex internals)

I recall watching (and rewatching) the video a few months ago.  I'll take another look.  Thank you!
My specific question is given the following:

codex generates the codex.tags file (if not the default setting, is set in my global .codex config)
vim/nvim uses hscope to jump to various definitions (vim -> hscope ref set with set csprg=hscope)
hscope references vim/nvim's tags setting to find the codex.tags file (vim -> codex.tag ref set with set tags+=codex.tags)

Given that, it does not explain why there is a hscope.out.tmp file.   In addition to using this opportunity to get a deeper understanding of this highly productive tool, I'm troubleshooting the automation/timing of updating the codex.tags file to reflect ongoing changes in the code base.  My modified HVN function LoadHscope() is connecting to the codex.tags file, but it's not updating it (like I can by running codex in the project root directory).
PS: I can imagine this might be a frustrating question for you as it defeats the purpose of the HVN configuration - In trying to confirm functionality I've hacked it and now am asking questions on how to fix it!  This said, I have read a lot of documentation. My hope is that by laying this out, we augment other's ability to troubleshoot and validate the functionality.

Hey, sorry I'm not going to invest time looking into it for free. I set myself a new personal policy.

HVN is a great contribution. Thank you for that.  I understand and appreciate your position.


Implement various improvements

Description
Thank you for implementing such a useful library. I've been using it very effectively. However, while using it, I thought of a few improvements that could be made, so I proceeded with some work. The details of the work are as follows. (As there was no specific PR template, I've written this in a general style.)
Detailed explanation of changes
1. Chaining as a Modifier function : https://github.com/hevinxx/visibility-tracker/commit/a5464d9b60a683e8da39a329f63612c495f7aa47
In the existing implementation, the View which exposure you wanted to check always had to be wrapped in a VisibilityTracker. This created additional line breaks and could harm readability, especially for deep UI hierarchies. Therefore, I added a function that can be called directly from the Modifier without creating additional line breaks.
Trade-off: When used as a Modifier function, the area judged for exposure can change depending on the chaining order.
(For example, when padding is applied before/after the onVisibilityChanged function)
2. Change in visibleRatio implementation : https://github.com/hevinxx/visibility-tracker/commit/e2e665bd79e1c739792d383b73fcb8700232408f
I changed visibleRatio from derivedStateOf to LaunchedEffect-based implementation.
According to the official documentation, derivedStateOf is suggested for use in situations where the number of recompositions and actual data state changes are mismatched. For example, it can be used for states that converge to a specific state, such as Boolean values or roundToInt.
However, visibleRatio is different. Except for some special situations, visibleRatio is composed of a combination of givenArea and contentBounds values, so its value changes every time. (Checking the exposure ratio of UI essentially means it's used in scrollable UI where exposed/unexposed states coexist. And in scrollable UI, givenArea and contentBounds change with each scroll, which means the visibleRatio value changes every time as well.)
Therefore, I thought there was no advantage to using derivedStateOf and modified it to an implementation based on LaunchedEffect.

Thank you for submitting first PR for this repository. I apologize for the delay in responding - I'm still learning how to manage an open source library and didn't notice the PR right away. Your proposed changes look good. I'll run some tests and then merge them. I'll also be updating the PR template and test code in the near future.

It seems you've edited the code from derivedStateOf to LaunchedEffect, perhaps thinking there was no advantage to using derivedStateOf. However, derivedStateOf does offer benefits. It allows us to keep visibleRatio as a val, preventing unintended modifications.
Though the project's current size may make it manageable to track changes, maintaining visibleRatio as a val through derivedStateOf would prevent it from being updated arbitrarily, which appears to be a better approach. Unless there's a specific reason for using LaunchedEffect, it might be more beneficial to stick with derivedStateOf to ensure visibleRatio remains immutable and its updates are more controlled.

The addition of the Modifier appears appropriate, and it seems to work fine in testing. Thank you for that. I'd like to merge your changes, but could you please resubmit your pull request with only the first commit? Once you've done that, I'll proceed with merging it.


Pressables

Close #15 by adding an animated pressable.
I need help knowing if this is the right way to handle onPress with RNGH. If anyone knows about that, please lmk.

Relevant tweet asking about that: https://twitter.com/FernandoTheRojo/status/1362432300898729984
Usage

Alright so the current implementation here is very wrong, will have to start it over and rethink it. I don't think I properly understood that you can only use shared values in worklets.
I think it should be something like:
<Pressable
  animate={function({ pressed }) {
    'worklet'

    return { opacity: pressed ? 0.5 : 1 }
  }}
/>


Create doc type

#56 can we take this approach
Pull Request type

[x] Bugfix
[x] Feature
[x] Refactoring (no functional changes, no api changes)
[x] Build related changes
[x] WHOSUSING.md
[x] Other (please describe):

NOTE: Please remember to run ./gradlew spotlessApply to fix any format violations.
Changes in this PR
Describe the new behavior from this PR, and why it's needed
Issue #
Alternatives considered
Describe alternative implementation you have considered

@v1r3n what to do next?

its not clear what this is supposed to do.  Closing this PR for now, please re-open if needed with more context.


Fix azure file copy issues in release build

PR Summary

Add * to azfilecopy command to upload contents of directory instead of the directory itself
Restrict macos to upload only osx tar.gz

PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

Merged early because it was release blocking


Esy 5740 clarity cookie consent

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Can we work on stuff that is part of the public release milestone?

Like easter eggs are fun and all, but we have a release goal of Thursday, that's 51 hours from now.
We need to get other things done that are more important
@thatoddmailbox @nywillb @willweinstein

@medensqui That sounds smart! But I am also working on things people send feedback about. (weekend planner boxes, HW view bugginess) Quick and good responses to feedback makes happy users. Happy users tell their friends and are more likely to use PlanHub.

@thatoddmailbox True! But once you're done with that, pls work on stuff that we need to do for public release! Remember easter eggs and new features are cool but we need to fix existing bugs, polish the webpage, and do all the things we said we needed for Day 1 first before we do things. Remember, CoursesPlus sometimes took 2 weeks to update things but we told people we were working on it and they were fine with it. So just pointing it out

@medensqui I know, but the center of all your planning stuff is more important than a bug on a page on Courses no one really uses.
(if it makes you feel any better, right now I'm working on #13)

@thatoddmailbox True. YAY
But def focus on feedback bugs esp. weinstein's cause they sound very undesireable
Also, I meant the bugs and stuff more than My Day
My Day is preferably ready Day 1 but not a priority

@medensqui !false.
Yeah @willweinstein appears to be experiencing some fun bugs. I sent a followup comment about it, but no response yet...

@thatoddmailbox False?
Yeah...

@medensqui NO
!false
DO YOU NOT SEE THE EXCLAMATION
IT MEANS THE OPPOSITE OF

@thatoddmailbox AH OK
WHY ARE WE USING CAPS

@medensqui IDK I FELT LIKE YELLING ok I'll stop now.

@medensqui Should I attempt a #13 again?

@thatoddmailbox Umm...It's something that needs to get fixed eventually. So I guess yeah!

@medensqui UGH I BROKE SOMETHING AND NOW GITHUB WON'T AUTOMATICALLY MERGE

@thatoddmailbox :tongue:

@thatoddmailbox HAHAHAHAHHA

@medensqui HA FIXED IT

@medensqui I think a smart idea would be to focus on bug fixes, polish, etc. and leave My Day for after the deadline. We only get one chance at a first impression, so it better be good! We could leave it in its current state (homepage & feature enable say "coming soon") and maybe have some super-secret beta version that is in early development, but I think that if we try to rush it for Thursday, it won't be very good.
?

@thatoddmailbox True!

@thatoddmailbox @nywillb @willweinstein CAN I JUST POINT OUT THAT PUBLIC RELEASE IS TOMMOROW! YES I SAID TOMMOROW! AND WE HAVE DONE 50% OF PUBLIC RELEASE STUFF. LETS FINISH IT

@medensqui CALM YOURSELF AAAAAGGGGHH
Also we can maybe push it to Friday.
Also I have to do #14 tonight so it doesn't break the live site.

@thatoddmailbox ok, focus on bugs. but it's really important. Ok
STOP WORRYING ABOUT STUDERPLANNER.TK AND WORRY ABOUT THE FRIKIN PUBLIC RELEASE
THERES NO POINT IN FIXING FRIKIN MINOR BUGS WHEN THERES NO PRODUCT

@medensqui GEEZ OK THE DOMAINS TOOK LIKE 2 MINUTES.
ALSO "ONE ROW STOPPED BEING REGISTERED IN HW VIEW" IS NOT MINOR

THE PUBLIC RELEASE MILESTONE IS FINISHED YAY

@thatoddmailbox YAY SO NOW LET'S START OUR OTHER MILESTONE. AHEM AHEM COUGH MY DAY AHEM AHEM

@medensqui yes i know but @c20et wants to submit it for the hackathon and we can't start it yet if we do.
idk if it is a good idea to submit it there, but...

@thatoddmailbox Meh
Idk...

@medensqui also even if we don't start my day until we are allowed to, they still would not like the base of planhub

@medensqui we should actually maybe figure out if that's what we're gonna do

@medensqui ?

@thatoddmailbox yeah...

@medensqui ??


Multimap.of(KVKVKV) #1608

Current coverage is 96.45% (diff: 94.73%)

Merging #1667 into master will increase coverage by <.01%

@@             master      #1667   diff @@
==========================================
  Files            89         89
  Lines         11174      11187    +13
  Methods           0          0
  Messages          0          0
  Branches       1887       1881     -6
==========================================
+ Hits          10777      10790    +13
  Misses          243        243
  Partials        154        154

Powered by Codecov. Last update 7e2a7f6...b1054f9

Awesome, thank you :-)


1.20.2 Support

Hey! I hope it is not difficult to add 1.20.2 support, I am surprised nobody opened an issue yet...
Thank you 🙏

Wait for support 1.20.2

Is it solved now ?

Is it solved now ?

NO😭


Adds simple type check on the api key to ensure string is passed. Thr……

Adds simple type check on the api key to ensure string is passed. Thows new error if key value is not a string.

Made a quick type check to help error reporting. Ran into this issue by a typo in my code.


Shadows don't work correctly on Safari

When the spotlight has a border-radius, the outer shadow is not displayed.

This seems to be caused by a bug in Safari: if the value of the shadow is too big, then the shadow is not displayed at all.
There is a question on Stack Overflow in which this problem is described, and a solution is suggested (using borders instead of box-shadows).

Using borders instead of box-shadow to avoid problems with Safari.


Add ws2022 image/build to cri-containerd tests

This change adds a new case to the getWindowsServerCoreImage and
getWindowsNanoserverImage functions to return ws2022 on a ws2022 or higher
build. The higher case is because of some recent efforts to improve down-level
compatability for Windows container images. For reference, the ltsc2022 image
works on a win11 host without hypervisor isolation.
Signed-off-by: Daniel Canter<EMAIL_ADDRESS>

Leaving this as a draft briefly because was curious on what's a better approach for the switch statement. We could take anything higher than ws2022 and just convert it to the ws2022 build so the switch will pick up the ws2022 image, or we can assign the build number to a variable and match anything that's V21H2 and higher to the ltsc2022 image(but then the rest of the switch is just odd). I've done both, one approach for the getWindowsNanoserverImage func and one for the getWindowsServercoreImage function

@ambarve Assigning you as we both share the constant pain of taking out that panic to run the tests locally 😂. Let me know what you think about the above.

I realise it's not part of this PR (It was discussed in #1155), but seeing it here, particularly in context of a comment referencing "21h1", I wish the osversion constant had been Server2022 or something, not V21H2, since my understanding is that Windows 11 will also be "21H2", and so will the next Windows 10 feature update, and so is the next Azure Stack HCI release, and they all represent different builds (except Azure Stack HCI, which matches Server 2022).
Since "21H2" is the point where all the Windows product lines are diverging their builds, it's probably a good point to avoid using that term, or alternatively, only using it for Windows Server.
In that alternative case, then this PR's reference to '21H1' (the comment I just commented on, which is why I'm thinking about this now), should probably needs to be "Windows 10 21H1", to be super-clear.
It kind of depends on future plans: If there's going to be container base layers for the Azure Stack HCI releases, then the "alternative" makes sense, as there will be a need to refer to SAC versions in the future, and the mixed LTSC/SAC-versioning has been a bit confusing in container tags.
However, if the next set of container base images are likely to be with the next Server LTSC release after Server 2022, which seems feasible due to the new kernel ABI stability work, then you won't need named osversion constants for the Azure Stack HCI SAC kernels, and so the >= test for "osversion.Server2022" would be fine, until we know which Server LTSC release won't be able to use LTSC 2022-based images.
Knowing those future plans might also help choose between the two approaches to handling this: Will the 'switch' slowly grow every six months; or is the long switch now "legacy" and in future it'll be the small set of if/else checks that is changed every five years or so.

@TBBle You've got an extremely fair point here and we're looking into it. Might be best to revert that V21H2 change until we know what our stance should be for this package/the constants going forward, things have gotten a bit more annoying now it seems :/. I think ideally we should segment the constants by client/server in some way now. @kevpar had suggested possibly having W10, W11, and WS prefixes to represent the Windows 10, Windows 11 and Windows Server build numbers respectively. We'll hopefully have an idea in the coming week

@TBBle Small update, gonna sync with some folks tomorrow on this and hopefully figure out a plan for names in this package going forward. We'd really wanna get the naming for 21H2 right seeming as how it represents three entirely different build numbers now -_- and who knows what the future holds.

In my opinion, I prefer the getWindowsNanoserverImage because it separates the "host build ➡ image build" mapping from the "image build ➡ MCR repository string" mapping. Particularly because that version explains why the first mapping isn't always identity, as it has been in the past.
And I expect the first mapping will slowly grow over the next few LTSC releases, particularly if there are overlaps in supported image build versions.

@TBBle I'm inclined to agree. I changed both to that style and undrafted! @ambarve PTAL

@ambarve pingaroo

@ambarve Let me know if this looks good


H619A Showing but switch just drops back to off without doing aything.

Govee Device SKU
H619A
Govee2MQTT Version
2024.01.24-ea3cd430
Describe the issue
Installed the new lights to the Govee app, everything works there, connected to my WIFI no problems, a few minutes later, it showed in the mqtt list, along side other lamps, heaters and lights that work beautifully. Try to switch on and nothing happens toggle just pops back to off, if I turn on and off at the app HA show on and off correctly, any help would be great.
Startup Diagnostics
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_TEMPERATURE_SCALE=C
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-02-01T11:48:43 INFO  govee::commands::serve] Starting service. version 2024.01.24-ea3cd430
[2024-02-01T11:48:43 INFO  govee::commands::serve] Querying platform API for device list
[2024-02-01T11:48:43 INFO  govee::commands::serve] Querying undocumented API for device + room list
[2024-02-01T11:48:45 INFO  govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-02-01T11:48:45 INFO  govee::commands::serve] Starting LAN discovery
[2024-02-01T11:48:45 INFO  govee::commands::serve] Waiting 10 seconds for LAN API discovery
[2024-02-01T11:48:45 INFO  govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
[2024-02-01T11:48:55 INFO  govee::commands::serve] Devices returned from Govee's APIs
[2024-02-01T11:48:55 INFO  govee::commands::serve] AB-Heater (E0:64:60:74:F4:1A:EE:86 H713B)
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Platform API: devices.types.heater. supports_rgb=true supports_brightness=true
[2024-02-01T11:48:55 INFO  govee::commands::serve]                 color_temp=None segment_rgb=None
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Quirk { sku: "H713B", icon: "mdi:heat-wave", supports_rgb: false, supports_brightness: false, color_temp_range: None, avoid_platform_api: false, ble_only: false, lan_api_capable: false, device_type: Heater, platform_temperature_sensor_units: Some(Farenheit), platform_humidity_sensor_units: None, iot_api_supported: false, show_as_preset_buttons: None }
[2024-02-01T11:48:55 INFO  govee::commands::serve]
[2024-02-01T11:48:55 INFO  govee::commands::serve] Cabinet Lights (8E:2A:A4:C1:38:00:60:09 H6141)
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-02-01T11:48:55 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=None
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Quirk { sku: "H6141", icon: "mdi:led-strip-variant", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: true, ble_only: false, lan_api_capable: false, device_type: Light, platform_temperature_sensor_units: None, platform_humidity_sensor_units: None, iot_api_supported: true, show_as_preset_buttons: None }
[2024-02-01T11:48:55 INFO  govee::commands::serve]
[2024-02-01T11:48:55 INFO  govee::commands::serve] Dining Room Atrium (CD:48:D0:39:32:35:74:6E H6061)
[2024-02-01T11:48:55 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-02-01T11:48:55 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..21)
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Quirk { sku: "H6061", icon: "mdi:hexagon-multiple", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true, device_type: Light, platform_temperature_sensor_units: None, platform_humidity_sensor_units: None, iot_api_supported: true, show_as_preset_buttons: None }
[2024-02-01T11:48:55 INFO  govee::commands::serve]
[2024-02-01T11:48:55 INFO  govee::commands::serve] Gym Heater (38:17:D4:AD:FC:D6:C2:C2 H713B)
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Platform API: devices.types.heater. supports_rgb=true supports_brightness=true
[2024-02-01T11:48:55 INFO  govee::commands::serve]                 color_temp=None segment_rgb=None
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Quirk { sku: "H713B", icon: "mdi:heat-wave", supports_rgb: false, supports_brightness: false, color_temp_range: None, avoid_platform_api: false, ble_only: false, lan_api_capable: false, device_type: Heater, platform_temperature_sensor_units: Some(Farenheit), platform_humidity_sensor_units: None, iot_api_supported: false, show_as_preset_buttons: None }
[2024-02-01T11:48:55 INFO  govee::commands::serve]
[2024-02-01T11:48:55 INFO  govee::commands::serve] LR-Cabinet (4D:B8:60:74:F4:AF:83:A6 H619A)
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-02-01T11:48:55 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..15)
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Quirk { sku: "H619A", icon: "mdi:led-strip-variant", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true, device_type: Light, platform_temperature_sensor_units: None, platform_humidity_sensor_units: None, iot_api_supported: true, show_as_preset_buttons: None }
[2024-02-01T11:48:55 WARN  govee::commands::serve]   This device should be available via the LAN API, but didn't respond to probing yet. Possible causes:
[2024-02-01T11:48:55 WARN  govee::commands::serve]   1) LAN API needs to be enabled in the Govee Home App.
[2024-02-01T11:48:55 WARN  govee::commands::serve]   2) The device is offline.
[2024-02-01T11:48:55 WARN  govee::commands::serve]   3) A network configuration issue is preventing communication.
[2024-02-01T11:48:55 INFO  govee::commands::serve]
[2024-02-01T11:48:55 INFO  govee::commands::serve] AB-Floor-Lamp (A5:07:D6:32:39:36:1D:3C H6076)
[2024-02-01T11:48:55 INFO  govee::commands::serve]   LAN API: ip=<IP_ADDRESS>
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-02-01T11:48:55 INFO  govee::commands::serve]                 color_temp=Some((2000, 9000)) segment_rgb=Some(0..7)
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Undoc: room=None supports_iot=true ble_only=false
[2024-02-01T11:48:55 INFO  govee::commands::serve]   Quirk { sku: "H6076", icon: "mdi:floor-lamp", supports_rgb: true, supports_brightness: true, color_temp_range: Some((2000, 9000)), avoid_platform_api: false, ble_only: false, lan_api_capable: true, device_type: Light, platform_temperature_sensor_units: None, platform_humidity_sensor_units: None, iot_api_supported: true, show_as_preset_buttons: None }
[2024-02-01T11:48:55 INFO  govee::commands::serve]
[2024-02-01T11:48:56 INFO  govee::service::http] http server addr is <IP_ADDRESS>:8056
[2024-02-01T11:49:04 INFO  govee::service::hass] Wait 4.5s for hass to settle on 90 entity configs
[2024-02-01T11:49:09 INFO  govee::service::hass] MQTT connected with status=CONNACK code 0: Connection Accepted.
Additional Logs
[2024-02-01T11:14:56 ERROR govee::service::hass] While dispatching Message { topic: "gv2mqtt/light/4DB86074F4AF83A6/command", payload: "{"state":"ON","brightness":100}", qos: AtMostOnce, retain: false, mid: 0 }: mqtt_light_command: state.device_set_brightness: Unable to control brightness for H619A_83A6 (4D:B8:60:74:F4:AF:83:A6 H619A)
[2024-02-01T11:15:00 INFO  govee::service::hass] Command for H619A_83A6 (4D:B8:60:74:F4:AF:83:A6 H619A): {"state":"ON","color_temp":174}
[2024-02-01T11:15:00 ERROR govee::service::hass] While dispatching Message { topic: "gv2mqtt/light/4DB86074F4AF83A6/command", payload: "{"state":"ON","color_temp":174}", qos: AtMostOnce, retain: false, mid: 0 }: mqtt_light_command: state.device_set_color_temperature: Unable to control color temperature for H619A_83A6 (4D:B8:60:74:F4:AF:83:A6 H619A)
[2024-02-01T11:15:01 INFO  govee::service::hass] Command for H619A_83A6 (4D:B8:60:74:F4:AF:83:A6 H619A): {"state":"ON","color_temp":186}
[2024-02-01T11:15:01 ERROR govee::service::hass] While dispatching Message { topic: "gv2mqtt/light/4DB86074F4AF83A6/command", payload: "{"state":"ON","color_temp":186}", qos: AtMostOnce, retain: false, mid: 0 }: mqtt_light_command: state.device_set_color_temperature: Unable to control color temperature for H619A_83A6 (4D:B8:60:74:F4:AF:83:A6 H619A)
[2024-02-01T11:15:01 INFO  govee::service::hass] Command for H619A_83A6 (4D:B8:60:74:F4:AF:83:A6 H619A): {"state":"ON","color_temp":500}
[2024-02-01T11:15:01 ERROR govee::service::hass] While dispatching Message { topic: "gv2mqtt/light/4DB86074F4AF83A6/command", payload: "{"state":"ON","color_temp":500}", qos: AtMostOnce, retain: false, mid: 0 }: mqtt_light_command: state.device_set_color_temperature: Unable to control color temperature for H619A_83A6 (4D:B8:60:74:F4:AF:83:A6 H619A)
[2024-02-01T11:15:05 INFO  govee::service::hass] Command for H619A_83A6 (4D:B8:60:74:F4:AF:83:A6 H619A): {"state":"ON","color_temp":500}
Home Assistant Logs
No response
Anything else?
No response

Sorry scrap that, the restart of the add on worked a treat. Sorry to waste your time.


Keeps pausing/resuming based on clicks to any item

On Ubuntu Linux 16.04, any time it's playing music, if I click any other item the music will pause (or play if paused).
It's making using the app impossible to use.
Version 3.1 downloaded direct from website.

While I'm not running 16.04, I am running 14.04 and 15.10 and I don't have this issue, can you explain in more detail what's happening?

@LiamDawe I had this issue yesterday for a brief period of time.  It appears to have been a bug in Google Play Music as a simple restart of the app fixed the issue

Weird, I did quit and restart a few times, but it's fine today.


How to add ripple?

Hi, is it possible to add ripple coin into api/coins?
Thank you

Is not in our plans


Support Python 3.13

Python 3.13 is expected to be released on 2024-10-01.
I have a branch ready to test this: py_313.
I have already tested ARMI against the dev versions of Python 3.13, but the problem right now is that SciPy does not yet support Python 3.13. So that is our current stopping block (thought it may be there are other libraries that also don't fully support 3.13 yet).

Update:

SciPy supported Python 3.13!
Now the road block is ruamel.yaml does not support Python 3.13; it won't even install.


[7.0.x] custom planet containers

Description

Forward port of https://github.com/gravitational/gravity/pull/1962.
Type of change

Bug fix (non-breaking change which fixes an issue)
Regression fix (non-breaking change which fixes a regression)
This change has a user-facing impact

Linked tickets and other PRs

Refs https://github.com/gravitational/gravity/issues/1940.

Requires https://github.com/gravitational/planet/pull/723, https://github.com/gravitational/gravity.e/pull/4328.

Ports https://github.com/gravitational/gravity/pull/1962.

TODOs

[x] Self-review the change
[x] Perform manual testing
[ ] Address review feedback

Testing done

Prerequisites

Custom planet container replacing the default package:

systemOptions:
  baseImage: quay.io/gravitational/planet:<custom-build>

Custom planet container for a (subset of) node profile

nodeProfiles:
  - name: profile
    systemOptions:
      baseImage: quay.io/gravitational/planet:<custom-build>

Clusters

[x] Installation, 3-node cluster, all control plane nodes
[x] Installation, 3-node cluster, one control plane, 2 workers
[x] Upgrade from a previous version (6.1.33), 3-node cluster
[ ] Upgrade from a previous version, run gc and expand (both controller plane and workers)
[ ] Installation, 1-node cluster,  then expand to 3-nodes (both controller plane and workers)

Checked the following for enterprise builds:

[x] That when logged out, it pulls stuff from default hub.
[x] That when logged into a hub (both via "tele login" and "tsh login"), it uses that hub.
[x] [!] That when --hub/--token/--repository provided, it uses the indicated hub. This did not work when using --token/--repository combination - seems like --hub is always required.
[x] Behavior of --state-dir flag, should be source for both packages and credentials (when logged in via tele login --state-dir), and when used in conjunction with --hub/--token/--repository flags.

Hi @a-palchikov, do you think that this pr will be a part of the next release version of 7.0.x ?

@dorsany I have a couple more things to take care as part of this PR that were discovered in the neighbor branch, but I hope it will.


Change Client to Axios and fix some code style

Changing HTTP client to Axios will resolve https://github.com/sebs/etherscan-api/issues/18.

Removed \dest
Fixed tests passing

Method Account Balance by known TokenName is deprecated at Etherscan
Method Get ETHER LastPrice Price return an internal error.

good to go?

hey.
I do not want to sound like a nitpicker, but can I get this one w.o. whitespace changes?
Then good to go. I am very thankful for this one.

@sebs, okey. I will return a whitespaces back ^_^

should be good to go now then? :D

@sebs, could you review?

see latest release

Thanks


Update the clomonitor name for WasmEdge

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~30 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

LGTM!
Sorry for my mistake. The clomonitor name of WasmEdge runtime is wasm-edge. So I created a new PR.


IrfanSkiljan.IrfanView.Plugins version 4.62

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

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

Microsoft Reviewers: Open in CodeFlow

Closed and replaced by https://github.com/microsoft/winget-pkgs/pull/102326


"The version of PEFT you are using is not compatible, please use a version that is greater than 0.5.0"

"The version of PEFT you are using is not compatible, please use a version that is greater than 0.5.0"

Hi,
Please uninstall peft and re-run.

Hi,
Please uninstall peft and re-run.

Thanks for your quick reply. The problem persists when I re-install it.
My operation is to uninstall peft
'pip uninstall peft'
Then, I installed peft with
cd peft/ pip install -e .
But it still has the same problem.

Hi,
You can try to uninstall peft and re-run without installation coz in finetune.py Line 16 we indicated the location of the package. If still have the same error, please check if you have installed the huggingface PEFT in the public environment.

The problem has been solved by uninstalling peft. Thanks for your assistance.


Run tsc before mocha in npm run fulltest

It's kind of annoying to run 5 minutes of mocha test just for the test to fail in the TypeScript compiler which is at least 5x times faster.

Use mocha run test instead of mocha run fulltest during iterative development and then its like 10s tests vs. 20s tsc (on my box). And if you want to run tsc, then run tsc, not mocha run fulltest.

The difference in timing is so weird. I moved Mocha first because Mocha was taking ~10s and TypeScript was taking ~20s. But I guess a Mocha fulltest takes longer.

What are you doing using npm run fulltest anyway? You should be doing npm test. npm run fulltest is really only to be done once.

My theory was: run npm run fulltest -> mocha passes -> tsc throws -> fix it -> re-run to make sure everything passes. I could shave off 5 minutes by making tsc throw before mocha passes.

Oh wow, I wasn't aware of what npm run test, where it seems to take sub 90 seconds for the entire test suite.
I guess, yeah, there's no reason to use npm run fulltest most of the time, but I think there's only upsides to this change no matter how minimal.

I'm saying:

You should be using npm test, not npm run fulltest. The full test is just a sanity check; having Travis run it is plenty enough safety for my tastes.

You should be using VS Code with live-highlighted tsc errors.

You should be using npm test, not npm run fulltest. The full test is just a sanity check; having Travis run it is plenty enough safety for my tastes.

(I'm assuming you haven't seen my previous comment.)

You should be using VS Code with live-highlighted tsc errors.

VSCode doesn't report errors for all files, only the ones you have currently open, or have opened recently.

Oh, yeah, also it's just npm test, the run part is optional.

As I said: The reason we currently do mocha before tsc is because on my laptop (and pre's, apparently), mocha takes 10 seconds and tsc takes 20 seconds.

As I said: The reason we currently do mocha before tsc is because on my laptop (and pre's, apparently), mocha takes 10 seconds and tsc takes 20 seconds.

Not for fulltest though..

Your change affects test, though.

I suppose I have no opinion on this in its new state.
@scheibo?


Suggest to have a refresh button to get the latest status of other two apps

Suggest to have a refresh button to allow users to get the latest status of other two apps otherwise I will close this page and then reopen it.

the page will refresh itself automatically. Have you found that the page is not refreshed?


[DNM] Add xfs bug to syslog error exceptions

Fixes: http://tracker.ceph.com/issues/17003
Signed-off-by: David Galloway<EMAIL_ADDRESS>

Is there evidence that this is truly something we should ignore?

http://oss.sgi.com/archives/xfs/2016-06/msg00206.html maybe?
I also found http://tracker.ceph.com/issues/3058

@jcsp @gregsfortytwo Can you guys weigh in on http://tracker.ceph.com/issues/17003#note-5 please?

Yeah, we have hit that with our own code before. A filter would need to check for xfs specifically. :(

Please don't do this - see my comment on the tracker.


In the as-you-type-formatter, insert a space after +685 (Samoa) when the number is a block. Issue #555

Committed as part of pull #637.


Add/doxygen

Before merging here are the few things required to setup

Setting up Gh-pages branch

Go to your mcpp directory and create an empty branch named gh-pages and run the commands

git checkout --orphan gh-pages
git rm -rf .
git commit --allow-empty -m "init"
git push origin gh-pages```

Setup github gh-pages on github settings

Settings > pages > Build and deployment > sources > select deploy from a branch
branch > select gh-pages >select /root dir

Change your URL in readme.md

So for this version i have setup the link so that the dictionary page is the current temporary main page for v1.
Just replace INSERT_YOUR_URL  with your url, please do not replace the html dir
Default would be https://YOUR_GITHUB_NAME.github.io/mcpp/

Required gh-pages branch to setup to pass all checks


Uncaught Error: getNodeFromInstance: Invalid argument.

I am using LazyLoad 3.0.10 in combination with react 15.2.0 amd react-dom 15.2.1
when openening the compontent the following error gets thrown:
Uncaught Error: getNodeFromInstance: Invalid argument.

this is a fragment of the code:
import LazyLoad from 'react-lazy-load';
import React from 'react';

    getGameMedia()
    {
        return(

                <LazyLoad height={300} offsetTop={200}>

                </LazyLoad>

        );
    }

Won't be fixing this as I'm focusing on 17 and 18 only now.


Create transfer and verify tester is working on happy path

Problem
What problem are we solving?
We need to verify that a transfer works and is reconciled through slow path.
Impact
Why does this matter? Who does it impact? How much does it impact them? What is the urgency?
Urgent to unblock tester.
Proposed Solution
[OPTIONAL] Thoughts on solution design. We could do  to solve this problem.

Write simple test scenario to send a single transfer and check it works.
Create new node script for single transfer.

Acceptance Criteria
From an end user perspective, the below criteria must be met to consider this done:

[ ] Transfer is boosted by router liq
[ ] Transfer is reconciled and router is reimbursed

update: in progress

@wanglonghong can you add some clarity here on blockers?

Next steps to do:

[ ] Create 2 xcalls to receive local tokens on both spoke domains.
[OnChain setup]

[ ] Call xcallIntoLocal on hub domain using sdk.
[ ] Send the root on hub domain to RootManager.
[ ] Propagate the aggregated root to spoke domains
[ ] Receive the aggregated root on both spoke domains on AdminSpokeConnector.
[OffChain setup]
[ ] Run the cartographer-poller at a regular interval --- this is what we're currently missing from current setup

[ ] Add router liquidity
[ ] Create an xcall and make sure both path working.

adding:

[ ] documentation of local setup

Updated documentation to latest, needs further updates once happy path works.

Created xcall with fast path!

fast path and slow path are working 🎉 🎉


Apply cross-env to lower-level package.jsons to fix Windows-specific …

…script errors.
Before submitting a pull request, please make sure the following is done:

Make sure your updates are reflected in both the React and HTML side of MDL.
If you've fixed a bug or added code that should be tested, add tests!
Make sure the test suite passes (npm test).

Nice 8)

Of course - it was your idea!  lol


In Angular and ReactRedux templates, the FetchData sample page fails if served over HTTPS with self-signed cert

The underlying issue is that Node.js doesn't respect the OS-configured trusted CAs (details - and note it's still the case in Node 8.x, even though this issue was marked closed). This means it doesn't recognise self-signed certs such as an IISExpress development cert, even if you agreed to register it as trusted in the OS. Instead, Node expects you to use a technique like this to manually load your trusted certs from files on disk.
The consequence is that, during server-side prerendering, API requests to https://localhost... will fail if the cert isn't chained to one of Node's built-in CAs. Hence you will get an error if you try to do server-side prerendering on the "fetchdata" page in the Angular or ReactRedux templates.
Possible workarounds

You can disable HTTPS validation at the entire Node process level using the code or env var process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";.
You can disable HTTPS validation on a per-request basis by setting the option agent: new (https.Agent)({ rejectUnauthorized: false }) on the call to Node's native https API, if you can access that.
Maybe - not tested - it might be possible to get Node to load the OS-trusted certs by some combination of the NPM packages trusted-ca (for Mac and some Linux distributions) plus node-windows-certs.

Workaround 3 would be best if it was robust, but it's hard to be sure of that, given that Linux distributions could put their CA cert store anywhere. It really feels like it should be a native feature in Node, not something hacked in at the application level.
Workaround 2 would be OK, since you'd only do it on requests that you know are going to your own backend server. However it's not really practical in the Angular case, because Angular apps are so deeply abstracted and there's no simple way of passing arbitrary options to Node's https API (reported as bug to request workaround). It would be OK in the ReactRedux case, but we don't want a solution that only works in one place.
Workaround 1 might be acceptable if we know your application was built in development mode. You wouldn't want this global flag set in production, hopefully.

This is now addressed in a couple of ways:

For the React-Redux template, the underlying domain-task/fetch API now takes care of this transparently. It knows if you're making a relative-URL request to your own server, and in that case, it skips cert validation on the request (since relative-URL requests by definition aren't even going to leave the machine, you don't really need to validate yourself). If you are making requests to external hosts that have self-signed certs, it's still up to you to get their public keys and add them to Node's CA config so they are trusted.
For the Angular template, we don't have a way to selectively bypass cert validation (reported), so we do the best we can, which is to let such a request fail during prerendering, but no longer cause prerendering as a whole to fail. Then, when the client-side code continues execution, it will re-request the data and fill in the UI, so it's mostly OK for the end user. Developers who absolutely need self-signed-cert API requests to complete during prerendering will still have to sort out the CA config themselves.


gps position measurement green lines visible

Hi
Im using the GPS enabled 2d cartographer branch.
on

https://github.com/larics/cartographer/tree/gps_landmarks

https://github.com/larics/cartographer_ros/tree/gps_landmarks

things appear to be working.. Atleast im not getting any obvious errors. Im also seeing the blue landmark appear, after about a minute.. I can also see the green lines on rViz..
My question is..
The green lines seem to appear randomly scattered around robot as it travels, and not actually where the robot has been. If the green lines are observed positions of the robot, How can they be observed where the robot has not been?
I am working is a slamtec 12m lidar and a IMU
My robot is mving outside but in a smal 10mx10m area..

Your question targets a fork of cartographer_ros, so I would suggest you to contact the author of that fork.

Your question targets a fork of cartographer_ros, so I would suggest you to contact the author of that fork.


Button color on hover

When I'm using Button component, I'm changing the background color. But on hover it is giving the default color. How do we solve this?

@kvinodhkumar87 that is due to the way theming works internally – you are only applying properties to the default static state of a button, not it's pseudo states (hover, focus, active).
I would suggest using a solution that allows you to specify the full style representation – className + css, or some css-in-js solution that can be passes as style, a className or as a wrapped component.

Changing the colour of an icon onHover is much worse, especially with the complexities of :hover nested selectors with css-in-js and the webpack headache.

This is resolved by more extensive theming support in later versions of EG. Closing as the issue is quite old.


Move sensitive identifiers from Github Actions workflow into secrets.

AWS account IDs are considered sensitive information.
https://github.com/cisagov/domain-manager-cicd/blob/aa48571a8a62570e019294663241f174d2a160f7/.github/workflows/cool.yml#L11-L12
Please remove these from the repository and store them as encrypted secrets.

@felddy Should cleaning the git history be part of the requirements?

@felddy @mcdonnnj Sorry, didn't realize account ids are considered sensitive information. I'm assuming all of this information would be considered sensitive as well then.
https://github.com/cisagov/domain-manager-cicd/blob/fd1ccd25405cdb1f9b6b040d28a44f8a08ad9fcc/cool/vars/staging.tfvars#L4-L7
Do you have already have a process for managing tfvars in an S3 bucket or something? Or do I have to add everything in as Github secrets?

@felddy @mcdonnnj Sorry, didn't realize account ids are considered sensitive information. I'm assuming all of this information would be considered sensitive as well then.
https://github.com/cisagov/domain-manager-cicd/blob/fd1ccd25405cdb1f9b6b040d28a44f8a08ad9fcc/cool/vars/staging.tfvars#L4-L7
Do you have already have a process for managing tfvars in an S3 bucket or something? Or do I have to add everything in as Github secrets?

Yes.  Those should also be evicted.
We have settled on using "profiles" as our method of distributing roles:
https://github.com/cisagov/freeipa-client-packer/blob/8a4c52db6f425e3c8c9f9164426dfe193bf45b95/terraform-test-user/main.tf#L2-L19
The profiles are stored locally in your AWS credentials
We created a tool that we use to synchronize credentials amongst our team since we have myriad profiles now in multiple workspaces:
https://github.com/cisagov/aws-profile-sync
It would probably be overkill to use it for a single profile or two that don't change often.

@felddy Should cleaning the git history be part of the requirements?

I don't think there is a need to edit the history for this.  I believe a cleanup is reasonable for this event.

Yes. Those should also be evicted.
We have settled on using "profiles" as our method of distributing roles:
https://github.com/cisagov/freeipa-client-packer/blob/8a4c52db6f425e3c8c9f9164426dfe193bf45b95/terraform-test-user/main.tf#L2-L19
The profiles are stored locally in your AWS credentials
We created a tool that we use to synchronize credentials amongst our team since we have myriad profiles now in multiple workspaces:
https://github.com/cisagov/aws-profile-sync
It would probably be overkill to use it for a single profile or two that don't change often.

@felddy Awesome. The reason I wasn't using a profile is it's a bit difficult to inject a profile into Github Actions, as we use it to run our deployments and terraform, but I'll figure out a simple way and get it out of the tfvars file.


Added Ecommerce SmartContract

have u raised the issue first @Satyam5665
for this .

@Satyam5665  please follow the guidelines to write the clean readme . For this you can refer to  any   readme present in my repo.
Also add some comments in your code  , for better  understanding  .
Thank  you :smile:


No traffic is communicated due to timeout

I have setup SwitchML P4 app and controller successfully and compiled the client library for RDMA backend but I'm having a similar issue as #8 that no communication happens after worker setup. I have two workers with disabled ICRC and have tried this both for hello_world example and allreduce benchmark. Here is the output of GLOG_logtostderr=1 GLOG_v=2 ./allreduce_benchmark for one of the workers (the other worker has a similar output and the behavior is the same for hello_world as well):
 ../third_party/stdarg.h ?? ../../switchml_bkp.cfg
I0902 11:34:34.264950 18461 context.cc:64] Starting switchml context.
I0902 11:34:34.265347 18461 config.cc:139] Using this configuration file 'switchml.cfg'.
I0902 11:34:34.265789 18461 config.cc:216] Printing configuration
I0902 11:34:34.265799 18461 config.cc:219]
[general]
    rank = 1
    num_workers = 2
    num_worker_threads = 4
    max_outstanding_packets = 4
    packet_numel = 64
    backend = rdma
    scheduler = fifo
    prepostprocessor = cpu_exponent_quantizer
    instant_job_completion = 0
    controller_ip_str = <IP_ADDRESS>
    controller_port = 50099
    timeout = 10000
    timeout_threshold = 100
    timeout_threshold_increment = 100
    --(derived)--
    max_outstanding_packets_per_worker_thread = 1
I0902 11:34:34.265834 18461 config.cc:270]
[backend.rdma]
    msg_numel = 64
    device_name = mlx5_0
    device_port_id = 1
    gid_index = 3
    --(derived)--
    num_pkts_per_msg = 1
    max_outstanding_msgs = 4
    max_outstanding_msgs_per_worker_thread = 1
I0902 11:34:34.265851 18461 rdma_backend.cc:42] Setting up worker.
I0902 11:34:34.266697 18461 rdma_endpoint.cc:65] Found Verbs device mlx5_0 with guid 0x98039b03008e0d50
I0902 11:34:34.266713 18461 rdma_endpoint.cc:65] Found Verbs device mlx5_1 with guid 0x98039b03008e0d51
I0902 11:34:34.266721 18461 rdma_endpoint.cc:79] Using Verbs device mlx5_0 gid index 3
I0902 11:34:34.290702 18461 rdma_endpoint.cc:116] GID 0 is 0x80fe 0x500d8efeff9b039a
I0902 11:34:34.290791 18461 rdma_endpoint.cc:116] GID 1 is 0x80fe 0x500d8efeff9b039a
I0902 11:34:34.290869 18461 rdma_endpoint.cc:116] GID 2 is 0 0x401a8c0ffff0000
I0902 11:34:34.290951 18461 rdma_endpoint.cc:116] GID 3 is 0 0x401a8c0ffff0000
I0902 11:34:39.579232 18461 context.cc:99] Switchml context started successfully.
Submitting 5 warmup jobs.
I0902 11:34:39.766185 18467 rdma_utils.h:193] Worker 0 bound to core 0 on NUMA node 0
I0902 11:34:39.766194 18469 rdma_utils.h:193] Worker 2 bound to core 2 on NUMA node 0
I0902 11:34:39.766386 18469 rdma_worker_thread.cc:129] Worker 2 QP 0:0x519 using rkey 5 for remote rkey 63210
I0902 11:34:39.766402 18467 rdma_worker_thread.cc:129] Worker 0 QP 0:0x517 using rkey 1 for remote rkey 63210
I0902 11:34:39.773722 18471 rdma_utils.h:193] Worker 3 bound to core 3 on NUMA node 0
I0902 11:34:39.773824 18471 rdma_worker_thread.cc:129] Worker 3 QP 0:0x51a using rkey 7 for remote rkey 63210
I0902 11:34:39.803228 18468 rdma_utils.h:193] Worker 1 bound to core 1 on NUMA node 0
I0902 11:34:39.803387 18468 rdma_worker_thread.cc:129] Worker 1 QP 0:0x518 using rkey 3 for remote rkey 63210

After no progress when I exit the process I get:
^CSignal 2 received, preparing to exit...
I0902 11:37:39.248157 18462 context.cc:105] Stopping switchml context
I0902 11:37:39.248188 18462 scheduler.cc:48] Waking up waiting threads
I0902 11:37:39.248227 18462 rdma_backend.cc:56] Cleaning up worker.
I0902 11:37:39.248417 18462 stats.cc:97] Stats:
    Submitted jobs: #5#
    Submitted jobs sizes: #[268435456,268435456,268435456,268435456,268435456,]#
    Submitted jobs sizes distribution: #Sum:<PHONE_NUMBER> Mean: 268435456.0000 Max: 268435456  Min: 268435456  Median: 268435456  Stdev: 0.0000    #
    Finished jobs: #0#
    Worker thread: #0#
        Total packets sent: #18#
        Total packets received: #0#
        Wrong packets received: #0#
        Correct packets received: #0#
        Number of timeouts: #17#
    Worker thread: #1#
        Total packets sent: #18#
        Total packets received: #0#
        Wrong packets received: #0#
        Correct packets received: #0#
        Number of timeouts: #17#
    Worker thread: #2#
        Total packets sent: #18#
        Total packets received: #0#
        Wrong packets received: #0#
        Correct packets received: #0#
        Number of timeouts: #17#
    Worker thread: #3#
        Total packets sent: #18#
        Total packets received: #0#
        Wrong packets received: #0#
        Correct packets received: #0#
        Number of timeouts: #17#
I0902 11:37:39.248509 18462 context.cc:130] Stopped switchml context
Warmup finished.
Submitting 10 jobs.
Signal handler thread is exiting

Here is the outputs on controller side:
SwitchML>show_switch_address

Switch MAC: 00:11:22:33:44:55 IP: <IP_ADDRESS>

SwitchML>show_rdma_workers

                                                   Received              Sent
 Worker ID     Worker MAC        Worker IP     Packets  /    Bytes      Packets  /    Bytes
     0      98:03:9b:83:1a:b2   <IP_ADDRESS>       0     /      0           0     /      0
     1      98:03:9b:8e:3d:ac   <IP_ADDRESS>       0     /      0           0     /      0

SwitchML>show_ports

  Port Up Valid Enabled Speed  FEC    Tx Packets        Tx Bytes        Rx Packets        Rx Bytes        Rx Errors        Tx Errors        FCS Errors
  1/0  1    1      1    100G  NONE       219             66345              68             10710              0                0                0
  2/0  1    1      1    100G  NONE       181             60116             106              8959              0                0                0
  3/0  1    1      1    100G  NONE       265             83132              33              6105              0                0                0
  4/0  1    1      1    100G  NONE       178             59180             133             12990              0                0                0

SwitchML>show_statistics

             Broadcasted         Recirculated       Retransmitted          Dropped
  Index    Set 0     Set 1     Set 0     Set 1     Set 0     Set 1     Set 0     Set 1
    0        0         0         0         0         0         0         0         0
    1        0         0         0         0         0         0         0         0
    2        0         0         0         0         0         0         0         0
    3        0         0         0         0         0         0         0         0
    4        0         0         0         0         0         0         0         0
    5        0         0         0         0         0         0         0         0
    6        0         0         0         0         0         0         0         0
    7        0         0         0         0         0         0         0         0

And on the switch side I get:
bf-sde.pm> show
-----+----+---+----+-------+----+--+--+---+---+---+--------+----------------+----------------+-
PORT |MAC |D_P|P/PT|SPEED  |FEC |AN|KR|RDY|ADM|OPR|LPBK    |FRAMES RX       |FRAMES TX       |E
-----+----+---+----+-------+----+--+--+---+---+---+--------+----------------+----------------+-
1/0  |23/0|132|2/ 4|100G   |NONE|Ds|Au|YES|ENB|UP |  NONE  |              68|             219|
2/0  |22/0|140|2/12|100G   |NONE|Ds|Au|YES|ENB|UP |  NONE  |             106|             181|
3/0  |21/0|148|2/20|100G   |NONE|Ds|Au|YES|ENB|UP |  NONE  |              33|             265|
4/0  |20/0|156|2/28|100G   |NONE|Ds|Au|YES|ENB|UP |  NONE  |             133|             178|

My environment is:
Switch: Wedge BF100-32x
SDE: 9.9.0
Python: 3.8
NICs: ConnectX-5
My ports.yaml has:
ports:
    1/0 : {speed: "100G", fec: "none", autoneg: "disable", mac: "98:03:9b:8e:82:98"}
    2/0 : {speed: "100G", fec: "none", autoneg: "disable", mac: "98:03:9b:83:1a:b2"}
    3/0 : {speed: "100G", fec: "none", autoneg: "disable", mac: "98:03:9b:83:34:d2"}
    4/0 : {speed: "100G", fec: "none", autoneg: "disable", mac: "98:03:9b:8e:3d:ac"}

And finally my config file is here:
switchml.cfg.txt
My guess is that the switch data plane as an end point is unreachable for some reason (but only one packet does not timeout so I'm not sure). Is there a way to ensure connectivity between
Thank you!

Also, I just noticed that if I ping between the workers and use tcpdump at the destination, the packets are arriving but with all zero values:

@OasisArtisan @AmedeoSapio I think this issue should be related to something simple like a misconfiguration but unfortunately I have not found a solution.

Although this is 2 years old, but for anyone stumbling on here in the future, we faced similar issue and solved it by disabling recirculation ports code in parser.p4 file. Also make sure you use switch ports that belong to the same pipe, and that they are not the ones hardcoded for recirculation. For ref look at https://github.com/p4lang/p4app-switchML/issues/33


feat(editors/subscriber/later-binding): add input requirement check

Closes #867
Check that the selected data and a later binding external reference match in terms of their CDC and bType specification.

The changes look good.
I have, I think found an issue in testing some files although it may be unrelated to this new feature and more related to some other later binding issue which I keep seeing but haven't nailed down and I must investigate.

I have created a more minimal example:
XAT_Prot2_Preconfigured_Check (1).scd.zip
For IED XAT_232_P2, there exists an unmapped ExtRef:
<ExtRef desc="RxExtIn1" intAddr="RxExtIn1;/Ind/stVal" pServT="GOOSE" pDO="Ind" pDA="stVal"/>
<ExtRef desc="RxExtIn1" intAddr="RxExtIn1;/Ind/q" pServT="GOOSE" pDO="Ind" pDA="q"/>

Both stVal and q have preconfigured restrictions (I manually removed the pre-existing mapping).
I expect on the right-hand side that the q values are greyed out because the bType for a general (boolean) and a quality value (Quality) are distinct.
I can look at this in more detail for some time if this is not clear enough -- but perhaps I have misunderstood?

The ExtRef is missing pLN. So far we do not restrict so long not all four attributes pLN, pDO, pDA and pServT are not given. Do you think this is incorrect @danyill ?

The ExtRef is missing pLN. So far we do not restrict so long not all four attributes pLN, pDO, pDA and pServT are not given. Do you think this is incorrect @danyill ?

Thank you for looking.
This whole referencing system is dubious as you point out.
I think Part 6, 9.3.13 allows for partial pXX referencing:

In this case any values at pDO and possibly pDA allow to specify the CDC
respective attribute type expected for this intAddr. Together with lnClass this allows to specify
a functionally expected input. The desc attribute allows to give it additional informal meaning,
the serviceType attribute the intended service quality. If at least the pDO attribute is specified,
then a missing pDA attribute includes at least all the operational value attribute(s) of the DO,
i.e. stVal, mag, t, q etc. It might allow binding of additional attributes supported by the service
type.

And also:

Specifying expected inputs (input templates) of logical devices or logical nodes from
the view of the IED configuration tool. The intAddr attribute shall be set to a non empty
value. The pDO might specify the needed input CDC via a standardized DO name,
additional pDA values might indicate the expected data type of an attribute and the
pLN might document the expected function providing the input. pServT might provide
the expected service type for this input value. These attribute values, if supplied by the
IED configurator, shall not be modified by the system configurator. A system
configurator binding to these input templates must assure that the CDC specified by
pDO and, if given, the attribute (base) type specified by pDA are met. For a final
engineered data flow also the pServT, if given, shall be met by the serviceType value.

This seems to indicate that pLN can be optional.
As long as we have a "relaxed" approach where the provision of pXX but not finding a match allows subscriptions to be done I think we are all good. We can improve this feature in future on request or as the need arises.
I do see some benefit in being able to specify only pDO and pDA because it means that the quality items will be nicely greyed out most of the time.
I think we should merge this unless you would like to do more :+1:

I would merge this as is. It goes easy on the fully specified restriction at the moment. I think this in the future we will see more vendors using all attributes than the other way around. To make the implementation adjust more with the idea in the standard, I would propose another algorithm that goes something like this.

get all DO, SDO based on the pDO
filter for option lnClass but at least filter DO, SDO used by the subscribing IED
map to DOTypes cdc.
filter all null and or undefined
put into Set.
take the first entry. There should be only one

for data attributes

get all DA, BDA based on the pDA
filter for optional lnClass but at least filter DA, BDA used by the subscribing IED
optional filter for given
map to DAs and BDAs bType.
filter all null and or undefined
put into Set.
take the first entry. There should be only one

That could be fast search but also not really reliable. LN to DO to DA is clear, but the other way around is not. However, we want to not be restrictive if we are not sure, so this would even fit the concept.


Wishlist: Support for Ubuntu 22.04 (and GCC 12)

The latest version which is installed by the action seems to be g++ (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0.
On my local I've got g++ (Ubuntu 11.2.0-19ubuntu1) 11.2.0.
It's way behind.

Related: GH-4.

@kenorb Don't be misled by the latest keyword, which actually installs the default version within the chosen distribution release (9 in focal, 11 in jammy).  You can install gcc 11 on 20.04 just fine, but you need to specify the version yourself.

Is it possible to support g++-12 for now? My project has some problem with g++-11, but works fine with g++-12. And I would like to use g++-12 in the workflow.

Is there any movement on this issue? I would really like to move to GCC12

Sorry, I was in no fit state to deal with my GitHub Actions for the past year. I'll try to keep up in the future.
Done and released. Jammy is the only Ubuntu version that supports GCC 12 though.


[erlang] provide exact error like compiler

When saving erlang function it is difficult to understand the error message.
It should provide exact compiler error.

We will have to use compile module.
To use that we will have
create a module,
put the function being saved into it,
and stub all other functions, used by the function being saved in the same module.


Improving the READMEs

Remove the duplicate item [13,17] => [17] in README
Correct the item numbers in README
Fix typo
Add 示范用例 section title in the Chinese README to match the English README

@yedeyu thanks but some duplication of #151 I will merge #151 first. then solve this conflicts.


Bad user experience

What's the Problem?
It is normal for a Windows user to be adapted to using Win + E to open the file explorer, having to click on the app makes you not want to use it, I have been installed for a long time and I always check if they have already added that option
Solution/Idea
replace default Win + E (windows explorer)
Alternatives
Or add any other key combination please
Files Version
2.0
Windows Version
Microsoft Windows [Version 10.0.19043.1202]
Additional comment
nothing else

@htmyname I think this should solve the issue 🙂
https://files-community.github.io/docs/#/articles/configure-win-e