systemd-shutdown[1]: Waiting for process: cpptools, cpptools-srv, node

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:  1.88.1
OS Version: Ubuntu 22.04 (client and remote system)

(This is a copy of https://github.com/microsoft/vscode-cpptools/issues/12184, but now "moved" to the main vscode repo, since it sounds like a core issue in vscode, rather than just in the cpptools extension per comments in that bug)
Environment

OS and Version: Ubuntu 22.04
VS Code Version:
C/C++ Extension Version:
If using SSH remote, specify OS of remote machine: Both vscode GUI and backend are running on Ubuntu 22.04 (separate machines)

Bug Summary and Steps to Reproduce
Bug Summary:

vscode/cpptools delays system shutdown for minutes.

Steps to reproduce:

Connect to system using remote explorer.
Use vscode for a while.
Close vscode window (disconnects from machine in question)
SSH back to the machine outside vscode
Run poweroff
Using a BMC/KVM, watch the shutdown process on the console. See sytemd-shutdown delaying shutdown for a few minutes because cpptools, cpptools-srv, node processes are still running.

Expected behavior:
At step 5, the system powers off almost immediately.
Configuration and Logs
NA; will add any logs later, after the machine has rebooted.
Other Extensions
Many.
Additional context
No response

sean-mcmanus commented 3 days ago •
Normally, cpptools is supposed to shutdown when the connection to VS Code ends, but and it also has a timeout that should self-terminate the process after 4 minutes.  I'm not sure what else more we could do, i.e. what did you want us to change? Can you run a command that kills all cpptools and cpptools-srv processes, e.g pkill cpptools?

I guess the issue is that when it's killed, sometimes it doesn't exit, and always it just respawns a new process. I closed vscode, then logged in using ssh in a terminal and couldn't get rid of cpptools:
swarren@machinename:~$ ps auxww|grep cpp
swarren     2855  3.0  0.4<PHONE_NUMBER>00 ?       Sl   13:17   2:12 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    15801  0.0  0.5 4305140 667508 ?      Sl   13:28   0:01 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools-srv 2855 {6F8242E4-7297-4CB9-8177-AD5AC3795EAA}
swarren    15869  0.0  0.5 4313500 725156 ?      Sl   13:28   0:01 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools-srv 2855 {B1750B7C-BDA4-4FEB-8423-38F4491CD7A1}
swarren    15973  0.2  0.5 4335020 742460 ?      Sl   13:28   0:10 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools-srv 2855 {37ED71D9-5E46-416A-B263-34A5F81430CB}
swarren    16023  0.0  0.3 4296368 471864 ?      Sl   13:28   0:00 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools-srv 2855 {F58067BB-4330-4CC0-BCFA-5B24E63EAB99}
swarren    18866  0.3  0.5 4331372 691056 ?      Sl   14:09   0:04 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools-srv 2855 {68A095C9-CDC0-4260-BEB1-8327434A3714}
swarren    19121  0.0  0.0   6612  2276 pts/0    S+   14:29   0:00 grep --color=auto cpp
swarren@machinename:~$ pkill cpptools
swarren@machinename:~$ ps auxww|grep cpp
swarren    19124  263  0.0<PHONE_NUMBER>6 ?        Sl   14:30   0:02 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19156  0.0  0.0   6480  2352 pts/0    S+   14:30   0:00 grep --color=auto cpp
swarren@machinename:~$ ps auxww|grep cpp
swarren    19124  226  0.2<PHONE_NUMBER>44 ?       Sl   14:30   0:09 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19159  0.0  0.0   6480  2280 pts/0    S+   14:30   0:00 grep --color=auto cpp
swarren@machinename:~$ pkill cpptools
swarren@machinename:~$ ps auxww|grep cpp
swarren    19124  115  0.2<PHONE_NUMBER>36 ?       Sl   14:30   0:12 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19161 76.7  0.4<PHONE_NUMBER>36 ?       Dl   14:30   0:03 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools-srv 19124 {FCA2F388-9DBA-4C6B-B3B7-D09A30BE74AE}
swarren    19190  7.0  0.0  42888 29004 ?        S    14:30   0:00 /usr/bin/python3 /usr/share/apport/apport -p19161 -s11 -c0 -d1 -P19161 -u5070 -g30 -- !swarren-data!home-.vscode-server!extensions!ms-vscode.cpptools-1.19.9-linux-x64!bin!cpptools-srv
swarren    19192  0.0  0.0   6480  2256 pts/0    S+   14:30   0:00 grep --color=auto cpp
swarren@machinename:~$
swarren@machinename:~$
swarren@machinename:~$
swarren@machinename:~$ ps auxww|grep cpp
swarren    19124 90.8  0.2<PHONE_NUMBER>36 ?       Sl   14:30   0:12 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19161 43.8  0.4<PHONE_NUMBER>36 ?       Dl   14:30   0:03 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools-srv 19124 {FCA2F388-9DBA-4C6B-B3B7-D09A30BE74AE}
swarren    19190  1.7  0.0  42888 29004 ?        S    14:30   0:00 /usr/bin/python3 /usr/share/apport/apport -p19161 -s11 -c0 -d1 -P19161 -u5070 -g30 -- !swarren-data!home-.vscode-server!extensions!ms-vscode.cpptools-1.19.9-linux-x64!bin!cpptools-srv
swarren    19194  0.0  0.0   6480  2252 pts/0    S+   14:30   0:00 grep --color=auto cpp
swarren@machinename:~$ kill 19124 19161
-bash: kill: (19124) - No such process
-bash: kill: (19161) - No such process
swarren@machinename:~$ ps auxww|grep cpp
swarren    19197  303  0.0  68440 39208 ?        Sl   14:30   0:03 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19228  0.0  0.0   6480  2424 pts/0    S+   14:30   0:00 grep --color=auto cpp
swarren@machinename:~$ ps auxww|grep cpp
swarren    19197  127  0.0<PHONE_NUMBER>4 ?        Sl   14:30   0:10 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19230  0.0  0.0   6480  2244 pts/0    S+   14:30   0:00 grep --color=auto cpp
swarren@machinename:~$ ps auxww|grep cpp
swarren    19197  116  0.0<PHONE_NUMBER>4 ?        Sl   14:30   0:11 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19232  0.0  0.0   6480  2224 pts/0    S+   14:30   0:00 grep --color=auto cpp
swarren@machinename:~$ kill 19197
swarren@machinename:~$ ps auxww|grep cpp
swarren    19197  101  0.0<PHONE_NUMBER>0 ?                Sl   14:30   0:02 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19268  0.0  0.0   6480  2244 pts/0    S+   14:30   0:00 grep --color=auto cpp
swarren@machinename:~$ ps auxww|grep cpp
swarren    19237  100  0.1<PHONE_NUMBER>92 ?       Sl   14:30   0:44 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19323 87.6  0.3 4312072 482416 ?             Sl   14:30   0:53 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19364  0.0  0.0   6480  2256 pts/0    S+   14:31   0:00 grep --color=auto cpp
swarren@machinename:~$ kill 19237 19323
-bash: kill: (19323) - No such process
swarren@machinename:~$ ps auxww|grep cpp
swarren    19366  183  0.0  59192 30128 ?        Sl   14:31   0:01 /home/swarren/.vscode-server/extensions/ms-vscode.cpptools-1.19.9-linux-x64/bin/cpptools
swarren    19397  0.0  0.0   6480  2364 pts/0    S+   14:31   0:00 grep --color=auto cpp

Colengms commented 3 days ago
Hi @swarren . Given that node is also preventing shutdown, this would seem to be a VS Code issue. It hosts node to run the extension. If VS Code itself is lingering and not shutting down node, then our TypeScript component would not shut down, and the native processes still running would seem to be due to still being associated with a live connection to our TypeScript component.

remote related, is this @roblourens ?

Can you give me the full command line arguments of the node process that's having the issue?

I believe that's already in this comment:
https://github.com/microsoft/vscode/issues/210253#issuecomment-2052177096
At least, if I exit the vscode GUI, then ssh into the machine using a standalone ssh client, then tried to kill the various node, vscode, cpptools processes, I saw processes that wouldn't go away, and the full command-lines of those are in that comment. However, I can't tell you the specific process that blocks shutdown, since when I tell the machine to shut down, any ssh session gets killed, and I can't make a new one, so I can't see which specific subset of those processes is still around. The machine is physically remote so I can only get in via ssh, not local console.

Sorry for the slow response. Not sure what the problem is at shutdown time. I see that the cpptools process is being restarted and I think that this is just something that the extension starts. I assume that the node processes in the shutdown log are the extension host and/or remote vscode server procesess. I don't know why the system would have trouble stopping them.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Fixed the C++ build to work in mac

Motivation
C++ Build won't compile on Mac, https://github.com/yahoo/pulsar/issues/198
Modifications

Explicitly specified GTEST_INCLUDE_PATH
Fixed the commands used to get version details

Result
Am able to build the c++ client on my mac

You can merge it once the travis build passes. It's better to create a script with the steps to build in mac.
👍

@jai1 I've added a few changes I needed in the comment.
I still have a link issue, since the cmake is trying to link with /usr/lib/libssl.dylib, instead of the openssl from brew

@jai Actually, I've got it working with
cmake . -DOPENSSL_ROOT_DIR=/usr/local/opt/openssl


Create Security Policy

Closes #304
I've created the SECURITY.md file considering the new GitHub feature, report vulnerability through security advisory.
If want to use this feature, it must be activated for the repository:

Open the repo's settings
Click on Code security & analysis
Click "Enable" for "Private vulnerability reporting (Beta)"

If you rather not enable it, there is also the possibility to receive the vulnerability report through an email. In this case just let me know what would be the email and I'll submit the change.
Besides that, feel free to edit or suggest any changes to this document. It is supposed to reflect the amount of effort the team can offer to handle vulnerabilities.

Hey! This issue/PR has been idle for quite some time. Do you plan on considering these changes? Is there anything I can do to help on addressing it?
I plan on waiting up to 2 more months before closing the PR, but let me know if you rather keep it open.
Thanks!

I'm sorry, but fastutil is kinda maintenance mode and I don't think this is necessary at this point.

Sure, no problem. Thanks for the return!


userData["file_path"] contains only file name in 0.41; full file path is not available for rules

We have a custom RuleSet for ktlint, and in some of the rules we use userData["file_path"] to analyze the absolute path to file and perform some custom checks. This key in userData was missing in 0.40.0 due to #997 and was re-intriduced in 0.41.0, but now contains only file name. This makes full path not available for rules.
It would be nice to have it back. From my point of view, it would require changing Paths.get(fileName) in ExperimentalParams to Paths.get(fileName).toAbsolutePath() or adding a separate key in userData in case the first option breaks something in ktlint. I'll be happy to make a PR with this change, please advice on the recommended way to put this data.

This seems to have been fixed in https://github.com/pinterest/ktlint/commit/9ebf6ec166723e9f6402799ff5bffa057c9347bc


DrillPick on 2D map broken based on zoom level

When you have a 2D map enabled and you try to use the drillpick or pick methods the results will either be correct or empty depending on the zoom level of the map. It seems like the more zoomed out you are it can say there are 0 things picked, but if you zoom in it will correctly detect things. This doesn't seem to be an issue with the 3D map.
Expected Behavior of Sandcastle:

Have a mouse move handler that will call drillPick whenever moved and print to the console the results

Instructions to replicate in sandcastle below:

Enable the console tab of the sandcastle.
Move cursor around the map. Move cursor on the striped rectangle on top of Australia. You will observe that the drillpick is recording nothing in the console.
Zoom in and move the mouse. After passing some random threshold you will start seeing messages in the console for drillpick results that correspond to the rectangle entity.
Zoom out again and the console messages stop.

Tested Environments:

CentOS Desktop + Chrome + NVIDIA GPU
Windows 10 Laptop/Desktop + Firefox  + Some GPU
Windows 10 Desktop + Firefox + Chrome + GTX 1080 Ti

I can't confirm if we've had this issue with older versions of cesium
This is pretty critical for what we are doing since our maps default in 2D mode and the drillpick is the basis for basically all of our event handling. A fix would be great, but if there is a known workaround we would gladly take it
Thanks
https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/#c=dVNdT+MwEPwrVl9IpeJ+IF4gVHdXIoFEr9UFuJdIJ2Nvi4VjR7YTlEP979hxQ9L2bvNgez07mh1vKqJRxeEdNLpBEt7RAgwvc/zc5KIz2hwXSlrCJeizEfpAhoKEpWJw1aLTNoPTRfIzmd2i3fA6k5kM1JiSHDTBBqznjT4yifbBwFguieVKoi+6BdHW7Yi8wBut8lvYagATdVU+prPZ6DBzfpK5mITossOwPZQH0nLLwWDCWCtOA7VEbgU4WT29VCnNvGAwnd5fLfZA7nQ2wZORU3Xpl2lYzn1y2JOZOyrNiXBsPftTq3kBy/3dWqsCtK37xvmACuRCCaU75/wJ/767f0yOrFCM/Qv64+HpGKmhAGKv0GWX3rW2ZXLv3KaUtHm0XJXGPX0FkVdjh96sAK7caDXO1m609k43o4OZ5kKsOX0LNdhY9+BrZbhnDPzBa2mUM1WobRSIwt2ueTrH/kokE8eTm1LnvkwLQiHx7HcBFB0ooMQRmEDnvz2Tn9B7WZT2e9Nc1Cppu/3q8bTt3agF/0fHY10AXq6e0uTPcvWcePTwejAaxMbWAuah9hvPC6UtKrWIMB5byAvhZ238UtI3sJiaRnQ8botixivE2U02OPpTswGighjjbjalECn/C9lgHo8d/qBMKOLmebuqQAtSe8jrdP4QkhjjeOyOp1VWKfFCdI/xEw

Thanks for providing a code example. Looks like this worked in 1.45, and seems to have broken in 1.46, somewhere in this PR: https://github.com/AnalyticalGraphicsInc/cesium/pull/6393
A git bisect shows this commit is responsible: https://github.com/AnalyticalGraphicsInc/cesium/pull/6393/commits/3e5c7243ba332f804521252c5a0a5388bebdeb75.
Initially I thought it was related to https://github.com/AnalyticalGraphicsInc/cesium/pull/7908, which was the exact same problem, but this seems to be a different underlying cause. @likangning93 any ideas?

Actually, one working @likangning93 just mentioned offline is giving the rectangle entity a height: 0, so it's not clamped to ground, which fixes it (if you're OK with having your entity not clamped to the terrain).


Exposure log not being checked

Describe the bug
It looks like that the exposure log is not being checked at all

Expected behaviour
Exposure log is checked at least once
Technical details

iOS 13.5.1

Additional context
App is installed 24+ hours

At the moment there are no submitted diagnoses keys available to check it again your collected random IDs. It will take a few days for the first diagnoses keys.


Fix action execution params static values getting evaluated

Description
When passing static values in execution params argument of an action run, and referencing it in the action, it would try to evaluate it via bindings. Added a change that would force binding brackets if a user wants to evaluate this param, and it would pass the string as is if no binding brackets {{ }} are wrapped around the param value

With binding

{{
  Api1.run(undefined, undefined, { message: "{{ Text1.text }}" })
}}

Without binding

{{
  Api1.run(undefined, undefined, { message: "Hello" })
}}

Type of change

Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

@hetunandu tests are failing

Have made this a draft PR because this is not a good solution. We shouldn't have bindings inside bindings. That's not valid JS. Hence, it breaks the user's mental model of "Everything inside the curly braces is valid JS".

Closing. Will implement a better fix in another branch


Leader board practice project with webpack and git flow

In this project:-

I set up a JavaScript project for the Leaderboard list app, using webpack and ES6 features, notably modules.
I have developed a first working version of the app following a wire frame.
Thank your for reviewing my project!!!.

Hello @juaryimami  for this project you have to follow the Git-flow, I am not blocking your approval brother .For future Lead board project activity you should create pull request from the feature branch to development branch(default branch) , After you finished Lead board project you will merged the result to main branch. I am  not here discourage you but it helps you for future project, Please update it .

git flow release start '0.1.0' isn't it a good git flow practice bro.

after making updates the I merge to my devleopment ranch by
git flow release finish '0.1.0' this is what i do.

Hello @juaryimami  I understand you brother and you are right. but it's stated in one of the project requirement that why i suggested you to make changes but at this moment request for reviewer and the reviewer will approve it ,still in the future i recommend you to follow the project requirement .

ok thanks bro


TextEncoder is not a constructor

In version 1.0.4 calling the text encoder like
new TextEncoder('utf-8').encode(value).length
causes the following error
TypeError: fastestsmallesttextencoderdecoder__WEBPACK_IMPORTED_MODULE_0__.TextEncoder is not a constructor
This error does not occur in v1.0.3

Thank you for bringing this to my attention. The soonest that I shall be able to look into it will be at around 5:00PM EST (9:00PM UTC). Thank you so much! I wish I had a free slot right now where I could do something about it.

After learning the webpack build system, cross-referencing multiple articles, and studying the generated code in the bundle output file, I believe I have identified that the problem is providing webkit with a ES6 flavour of the soup which can be accomplished, according to this article, via the "module" and "es2015" entries in the package.json file. This inadvertently appears to also be a possible solution to #3

Success (I think)! I have pushed up a new version of the library to integrate an ES6 module alternative to the library because it appears as though ES6 modules are easier for webpack to swallow (please don't quote me on this--I just learned webpack today, so I do not know much about webpack).
Below is a download link for a "poor-man's" test used to validate whether or not the library is compatible with webpack. After opening the console on the demo.html page and refreshing, the number 15 appeared in the console and no errors were reported. Thus, I assume that my changes have fixed the issues with webpack. I realize that this is not a very good benchmark, but I am at a loss to find any better way to test this library's compatibility with webpack.
As I am still very new and inexperienced with ES6 modules and webpack, I would really appreciate your inspection and critique of my work in order to verify that everything has been done correctly with best-practices and so forth. Thank you so much for bringing this issue to my attention and explaining the problem so clearly and concisely. I really appreciate that you have spent your time to contribute to this project.
~ Happy coding!

Download my "poor-man's" webpack test

Thanks for looking at this so quickly. I've tried using it in my project and it is working.

Thank you so much for getting back to me so quickly. I shall apply these changes to my other npm libraries.

I have not had time to look into why this is occurring, but when I run test using jest the tests fail as encode is not a function. FYI I am using create-react-app.

I am sorry, but I do not fully understand your comment as I sometimes struggle with English. Are you saying that my fixes do not actually work? If my fixes do not actually work, then please tell me and attach a zip file of your project to your comment so that I can debug it myself in the hopes of finding the problem.
Because I am unfamiliar either with react or with webpack, I am at a loss to find probable explanations. Thus, I do not know how to proceed with finding the error other than by using your project in its current state. If you are concerned about the privacy, piracy, and privy of your project, then please upload the project to an external website where you can delete the file as soon as I have downloaded it.
Further, after I am finished debugging the problem with FastestSmallestTextEncoderDecoder in your project, I can promise to purge your project from my SSD hard disk.

Your fix works when running the code in the browser, but it does not work when running tests using jest.
I have created a mock project to show you the issue with testing that I am experiencing
User/Repository:JamesMHenderson/fastestsmallesttextencoderdecoderreact
Run npm test to run the test
You will see that running the tests causes the fllowing error
TypeError: (intermediate value).encode is not a function
  2 |
  3 | export const ByteLength = (text) => {
> 4 |   return new TextEncoder('utf-8').encode(text).length;
    |                                   ^
  5 | };
  6 |

  at encode (src/encode.js:4:35)
  at Object.<anonymous> (src/encode.test.js:5:14)

Thank you so much for bringing this to my attention. I am reopening the issue and getting right on it. Thank you for all your help.
~ Happy coding!

Ooooops! I found my very silly mistake. Closure Compiler mangles property names and I forgot to explicitly mark the encode and decode property names as not to be mangled.
TextDecoder.prototype.decode = decode; // BAD
TextEncoder.prototype.encode = encode; // BAD

TextDecoder.prototype["decode"] = decode; // GOOD
TextEncoder.prototype["encode"] = encode; // GOOD

I have made these fixes and pushed up version 1.0.7 of this library. After updating and running yarn test, it appears that both tests have passed. Thank you so much for bringing this issue to my attention and providing follow-up on it.
Please tell me whether my changes have fixed your project. Thank you.
~ Happy Coding!

Thank you.
I've tested the changes in my mock project and it is working. I will check tomorrow that this is working in my actual project.
I did pull this repository locally to see if I could work out what this issue is but I couldn't run any of the npm scripts. Please could you provide instructions to set this up?

Thank you even more.
Thank you for getting back to me so quickly. You have been so helpful with finding and eliminating this bug.
As for the instructions, please see the development section of the README.
~ Happy coding!


Annotate zerver/lib

Automated message from Dropbox CLA bot
@sharmaeklavya2, it looks like you've already signed the Dropbox CLA. Thanks!

Cool, looks great, except a few things:

We should check redis accepts text_type and not binary_type for its keys
we should report the typeshed bug (if you haven't already) for sort(cmp=...).

Do you know how to check that? I have never used redis before.

Well we use the python-redis library to talk to it: https://pypi.python.org/pypi/redis, and it's all installed in a Zulip development environment, so I think one should be able to test it fairly quickly

Redis accepts both text_type and binary_type as type of keys and values. I tested this with non-ASCII characters. It automatically encodes everything using 'utf-8'.
It always returns binary_type when queried.

I think redis returning binary_type could cause problems in python 3. I inspected the code but I didn't find anything problematic.

OK, sounds good.  This file doesn't use the return type from redis, so I've merged this.  Thanks for investigating @sharmaeklavya2 (but can you report the typeshed bug with sort with a cmp argument?).


Interactive navigation for tree with millions of files is really slow

I observe some weird behavior with dua on large trees.
The scanned directory is 13M files total (across all subdirectories). It took dua ~7-8 hours to load it at 200 threads (it's a network mount, as described in #224); memory usage when in interactive mode is ~1.5GB.
I'm in interactive mode, in a directory with 1000 entries (all are subdirectories), with subtree containing 2M entries total.
I try to enter a subdirectory, it has under 193 entries (all are subdirectories), with its subtree containing just 2k entries. It takes ~10 seconds.
I try to enter its subdirectory, it has 8 entries (all are subdirectories), subtree containing 48 entries. It takes around a second.
I try to enter its subdirectory, it has 1 entry (subdirectory), subtree containing 5 entries, 3 levels deep inside of it there are 2 files. Navigating inside of it only takes a (noticeable) fraction of second for every action.
Navigating (using the u key) from the subdirectory with subtree containing 5 entries to subtree containing 48 entries takes around a second.
Pressing u key there (to get to the subdirectory with subtree containing 2k entries) takes ~10 seconds.
Pressing u key again (to get to the subdirectory with subtree containing 2M entries) takes around a minute.
Pressing u key again to get to the subdirectory with 8 entries and subtree containing 9M entries takes under a second, so this seems to be related to the number of entries in a directory, not to the size of its subtree.
By "takes XX seconds" I mean that the UI is stuck in the previous state and is completely unresponsive all this time; yet, oddly enough, dua CPU usage hovers around zero all this time.
(For reference, doing ls on the same directories takes under a second.)
That's on dua v2.26.0 from Alpine package repository (Alpine uses musl instead of libc, not sure if that's relevant here).

When thinking about this use-case I can also think of another improvement: How useful would it be to be able to dump the graph in some format, say JSON, so it could be made accessible by other tooling? Waiting 8 hours for something that is lost when hitting q seems like waste to be avoided.
From there I could absolutely imagine to add additional sub-commands that can handle these snapshot files, to compute changes between them for example. The simplest case would probably be to be able to use the UI to visualise such a snapshot, instead of re-scanning the underlying tree.
Maybe @piotrwach is interested in this as well :).

@Byron Yes, I may be interested :) Depending on how it is implemented I think dua could then also be used for analysing directory trees from other source. like for example S3,. E.g. all that would be required is to dump the object listing in the right format:
<name> <size> <mtime>

Such file then could be loaded in dua in interactive mode. What this would potentially also allow is interactively analysing file systems on other machines without actually running dua there: ssh remote-server find /directory/to/scan -t f | dua i --from-traversal

I absolutely love your thoughts! With this feature, dua i would become a front-end for viewing and organizing a graph data structure, which of course can also be created by other tools then.
ssh find… | dua i --from-traversal seems like a separate feature though as that new data structure wouldn't be involved directly. I also don't see how a simple find would produce all the data that's needed per entry, which I find critical to make this 'remote crawler that isn't dua' scenario work (after all, if dua was on the remote one could just use that). However, if that could be made to work, that would definitely be a nice feature to have as well.
For the terminal application input now is just a stream of events, and it doesn't have to care at all about their source anymore.


Slice doesn't work using symbols

Hi Hashie Team,
It appears that slice is not working. I noticed this when upgrading from ruby 2.4.5 to 2.5.8.
We had been using hashie 3.6. Upgrading to hashie 4.1 produced the same results.
Slice only seems to work with strings not symbols. Here is some test code:
require 'hashie'

class MyHash < Hash
  include Hashie::Extensions::IndifferentAccess
  include Hashie::Extensions::MethodAccess
  include Hashie::Extensions::DeepFind
  include Hashie::Extensions::DeepLocate
end

my_hash = MyHash[test: 'a value']

puts "This works: #{my_hash.slice('test')}"
puts "This doesn't: #{my_hash.slice(:test)}"

output looks like this:
This works: {"test"=>"a value"}
This doesn't: {}

Also, it appears that my_hash.slice('test') returns a Hash.

Looks like a legit bug/non feature. Feel free to PR!

Is there a spot in the codebase that would be a similar solution? I.e. overriding a Hash method. Something I could look at as an example?

This is likely due to IndifferentAccess. The fix probably is to call convert_key on each of the arguments to #slice.

Closed via #531


clion project

Hello,
I am trying to open your project in clion on Windows.  And throws me this error:
Cannot get compiler information: 	Cannot run program "xtensa-esp32-elf-gcc" (in directory "C:\msys32\home\berti\esp32-examples\cmake-build-debug"): CreateProcess error=2, The system cannot find the file specified
I changed the path for xtensa-esp32-elf-gcc, but its not working I tried C:\\msys32\\opt\\xtensa-esp32-elf\\xtensa-esp32-elf\\ and C:\\msys32\\opt\\xtensa-esp32-elf\\ and both doesnt work. Which is right?

I may well have found your (the repo owner - masoncj) repo the same way - I'd love it if you could add a "How to use CLion with this repo" section or something.  The CMake nonsense kept me away from it for a while, but your addition of a CMakeLists.txt was pretty helpful...

Assuming you've followed the steps here: https://esp-idf.readthedocs.io/en/latest/get-started/index.html#setup-toolchain, you should have a binary somewhere called xtensa-esp32-elf-gcc. I would have expected CMake to use this (appropriately modified) line to find that binary:
set(CMAKE_FIND_ROOT_PATH /usr/local/xtensa-esp32-elf/)

That was not the case for me. A good enough workaround has been to just put the full path of the xtensa-esp32-elf-gcc binary in the CMAKE_C_COMPILER variable. Something like this:
set(CMAKE_C_COMPILER /usr/local/esp/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc)


Windows node issues

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
What happened:
I have a hybrid windows/linux kubernetes cluster in azure. I was able to get certmanager itself to run on the linux nodes with a nodeSelector. When I deploy a container to a windows node with an ingress configured to use CM, CM creates a pod named cm-example-domain-com-tls-random. This pod ends up in imagePullBackOff as it seems to be trying to place it on the windows node but the image is linux.
What you expected to happen:
CM to correctly place the pod so it can start
How to reproduce it (as minimally and precisely as possible):
Create a hybrid cluster, install cert-manager into the linux nodes using a nodeSelector. create clusterissuer, create windows deployment/ingress/service/etc with the ingress configured to use the issuer.
Anything else we need to know?:
kubectl describe
Events:
Type     Reason                 Age               From                   Message

Normal   Scheduled              6m                default-scheduler      Successfully assigned <names changed to protect the innocent-tls-tvqx to 11499k8s9011
Normal   SuccessfulMountVolume  6m                kubelet, 11499k8s9011  MountVolume.SetUp succeeded for volume "default-token-mnx2k"
Normal   SandboxChanged         5m (x2 over 6m)   kubelet, 11499k8s9011  Pod sandbox changed, it will be killed and re-created.
Warning  Failed                 5m                kubelet, 11499k8s9011  Failed to pull image "quay.io/jetstack/cert-manager-acmesolver:v0.2.3": rpc error: code = Unknown desc = failed to register layer: re-exec error: exit status 1: output: ProcessBaseLayer C:\ProgramData\docker\windowsfilter\31b483a99331bc851ca1a609a3fb34ac34b367bd78e52d7f8e80d0578ea5b5a2: The system cannot find the path specified.
Warning  Failed                 5m (x3 over 6m)   kubelet, 11499k8s9011  Error: ErrImagePull
Warning  Failed                 5m                kubelet, 11499k8s9011  Failed to pull image "quay.io/jetstack/cert-manager-acmesolver:v0.2.3": rpc error: code = Unknown desc = failed to register layer: re-exec error: exit status 1: output: ProcessBaseLayer C:\ProgramData\docker\windowsfilter\49576ff2b6ed85ebd044a018b3975f20c37478c4ada9efc21176f6eb55c63760: The system cannot find the path specified.
Normal   Pulling                4m (x4 over 6m)   kubelet, 11499k8s9011  pulling image "quay.io/jetstack/cert-manager-acmesolver:v0.2.
3"
Warning  Failed                 1m (x20 over 5m)  kubelet, 11499k8s9011  Error: ImagePullBackOff
Environment:

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeSta
te:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeSta
te:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Cloud provider or hardware configuration**:
Azure
Install tools:
nginx-ingress
Others:

With the new manifest list support in Docker, it'd be awesome to push various archs and os's for at least the acmesolver.
If we cross compile using go, is there a particular base image we should be using to run the binary, or does scratch work okay? (I've not much experience running windows containers!)

We're getting our toes wet with a hybrid (Windows/Linux) Kubernetes cluster and just encountered this issue. I haven't used any Docker images that are multi-platform aware, but it's a good idea. It's important to note that (on Windows) host/container OS versions (ltsc2016 or 1709) must match (it's much more strict than Linux in this regard.) There are some exceptions for 1907 Hyper-V hosts, but in general it's a good assumption that containers matching each of the main microsoft/windowservercore tags have to be maintained. Unfortunately, Docker on Windows doesn't support the scratch image.
Step 1/3 : FROM scratch
Windows does not support FROM scratch

As a short-term fix it'd be nice to be able to add nodeSelector tags to the cert-manager-acmesolver pods that are created. I'll probably have to hack up a solution for that in order to get our cluster to issue certs.

@jbiel you could add a 'taint' to your Windows nodes to only schedule things on those nodes that 'tolerate' Windows. That should achieve your goal even before @munnerz finally capitulates 😄 and lets users add arbitrary annotations/labels/nodeSelectors/tolerations to cert-manager-acmesolver pods.
I see that 1.10 is adding CRI support for Windows containers, and I think Microsoft in 1709 added support for some Linux networking features needed for k8s networks and Calico. Exciting times!

Any news on this thread? The cert-manager-acmesolver is still deployed into the windows node so the certificates couldn't be generated

Any news on this thread? The cert-manager-acmesolver is still deployed into the windows node so the certificates couldn't be generated

Anyone have hints on this should be solved?


Webhook does not execute command but always reports 'ok'

Hello,
I am using Webhook version 2.8.0 in Ubuntu 22.04 and am attempting to trigger the execution of different commands from both gitlab webhook push as well as a simple browser-page get.  None of my tests have worked and I was wondering if anyone can offer advice on further debugging.
I am running webhook as root from the console using the following command:
 /usr/bin/webhook -hooks /etc/webhook.conf -debug
I have tried various webhook.conf files, [1], [2] and [3] below.  In all cases, the debugging output shows webhook receiving the Gitlab push or web browser get requests with output "ok" or status 200.  However, the scripts are never executed.  Sample debug output from script [3] is below.  Deleting the 'hooktest.sh' file referenced in config [3] still resulted in an 'ok' response from webhook.
Is there something wrong with my configuration?  I'm not sure how to debug further.
Thank you,
Jon
[1] The example provided in the documentation here
[
  {
    "id": "test-file-webhook",
    "execute-command": "/bin/ls",
    "command-working-directory": "/tmp",
    "pass-file-to-command":
    [
      {
        "source": "payload",
        "name": "binary",
        "envname": "ENV_VARIABLE", // to use $ENV_VARIABLE in execute-command
                                   // if not defined, $HOOK_BINARY will be provided
        "base64decode": true,      // defaults to false
      }
    ],
    "include-command-output-in-response": true
  }
]

[2] My desired configuration, which triggers a ruby script R10k
[
  {
    "id": "r10k-webhook",
    "execute-command": "/opt/puppetlabs/puppet/bin/r10k",
    "command-working-directory": "/etc/puppetlabs/r10k",
    "pass-arguments-to-command": [
      {
        "source": "string",
        "name": "deploy"
      },
      {
        "source": "string",
        "name": "environment"
      },
      {
        "source": "string",
        "name": "-p"
      }
    ],
    "include-command-output-in-response": true,
    "response-message": "Triggering R10K",
    "trigger-rule": {
      "match": {
        "type": "value",
        "value": "r10k",
        "parameter": {
          "source": "header",
          "name": "X-Gitlab-Token"
        }
      }
    }
  }
]

[3] Simple shell script to touch a file in the /tmp directory
[
  {
    "id": "touch",
    "execute-command": "/tmp/hooktest.sh",
    "command-working-directory": "/tmp",
  }
]

Where the contents of the test script for [3] are:
#!/bin/sh

/usr/bin/touch /tmp/WebhookRun

Debug output from webhook config [3] is:
root@puppet:/etc/puppetlabs/r10k# /usr/bin/webhook -hooks /etc/webhook.conf -debug
[webhook] 2023/08/24 14:48:18 version 2.8.0 starting
[webhook] 2023/08/24 14:48:18 setting up os signal watcher
[webhook] 2023/08/24 14:48:18 attempting to load hooks from /etc/webhook.conf
[webhook] 2023/08/24 14:48:18 found 1 hook(s) in file
[webhook] 2023/08/24 14:48:18   loaded: touch
[webhook] 2023/08/24 14:48:18 serving hooks on http://<IP_ADDRESS>:9000/hooks/{id}
[webhook] 2023/08/24 14:48:18 os signal watcher ready
> [9f4024] GET / HTTP/1.1
> [9f4024] Host: puppet.staging:9000
> [9f4024] Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8
> [9f4024] Accept-Encoding: gzip, deflate
> [9f4024] Accept-Language: en-US,en;q=0.5
> [9f4024] Connection: keep-alive
> [9f4024] Dnt: 1
> [9f4024] Sec-Gpc: 1
> [9f4024] Upgrade-Insecure-Requests: 1
> [9f4024] User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0
> [9f4024]
< [9f4024] 0
< [9f4024]
< [9f4024] OK
[webhook] 2023/08/24 14:48:25 [9f4024] 200 | 2 B | 295.701µs | puppet.staging:9000 | GET /

I figured it out immediately after posting this question.  The log message
serving hooks on http://<IP_ADDRESS>:9000/hooks/{id}

Suggested that the URL must have '/hooks/touch' as in the config [3], so I was sending the wrong URLs.
The correct URL for config [3] was 'http://puppet.staging:9000/hooks/touch' in my instance, and it worked as expected.
I will leave this comment in case anyone experiences the same problem.

issue closed


Handle url config for makara connections

Nice, thanks!

Oops, didn't notice that most versions were broken. Mind taking a look at those tests?

https://travis-ci.org/taskrabbit/makara/builds/82242328

Working on it... :)
B mobile phone

On Sep 26, 2015, at 10:58 AM, Mike Nelson<EMAIL_ADDRESS>wrote:
Oops, didn't notice that most versions were broken. Mind taking a look at those tests?
—
Reply to this email directly or view it on GitHub.

@mnelson updated and pushed.  Would you like a new PR for that (assuming it passes, which I expect it to).

Made a followup PR https://github.com/taskrabbit/makara/pull/94


Prefer stable cert-manager apiversion

Use the stable v1 apiversion for cert-manager issuer when available.
This enables updating the helm-managed issuer resource before upgrading to cert-manager version >= v1.6.0.
Otherwise Helm is not able to upgrade the Rancher Helm release afterwards, because the release references an API version which was removed by applying the CRDs for the new cert-manager version.

Why this is not yet merged? it blocks rancher upgrades with cert-manager >= 1.6.0


[feat] Define bootstrap node and allow generating bootstrap command

With 2 out of 3 most important commands done (apply and upgrade respectively), it would be nice if we could also generate the bootstrap command.
What we need for that, is to allow a single(!) controlplane node to be flagged as bootstrap: true (or something comparable).
Then we could use its IP to generate a bootstrap command as well.

@Ornias1993 I'm not sure about adding bootstrap: true to the config file, what about having a --node flag just like the other gencommand subcommand?

@Ornias1993 I'm not sure about adding bootstrap: true to the config file, what about having a --node flag just like the other gencommand subcommand?

Thats cool! :)
Saves having to reference IPs all the time and just fetch it from the config file, thats the most important part imho!


Upload To Testflight (Xcode 11.1): INFO: Invalid checksum on resource download for:

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
upload_to_testfight fails with Xcode 11.1
Command executed

Complete output when running fastlane, including the stack trace and command used

[15:01:34]: ----------------------------------
[15:01:34]: --- Step: upload_to_testflight ---
[15:01:34]: ----------------------------------
[15:01:34]: Login to App Store Connect<EMAIL_ADDRESS>[15:01:36]: Login successful
[15:01:37]: Ready to upload new build to TestFlight (App: xxxx)...
[15:01:38]: Going to upload updated app to App Store Connect
[15:01:38]: This might take a few minutes. Please don't interrupt the script.
[15:02:47]: [iTMSTransporter] [2019-10-08 15:02:47 EEST]   INFO: Invalid checksum on resource download for: https://contentdelivery.itunes.apple.com/transporter/repositories/j2se8/2.0.0/bundles/org.apache.logging.log4j.api-2.11.2.jar expected: 3f7ee51e3dd0830de799dae0b90243dd, received: 4cf6ebbac28c65b9fffd58cc363df6c0
[15:02:47]: [iTMSTransporter] java.lang.reflect.InvocationTargetException
[15:02:47]: [iTMSTransporter] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[15:02:47]: [iTMSTransporter] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[15:02:47]: [iTMSTransporter] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[15:02:47]: [iTMSTransporter] 	at java.lang.reflect.Method.invoke(Method.java:498)
[15:02:47]: [iTMSTransporter] 	at com.apple.transporter.launcher.Application.start(Application.java:220)
[15:02:47]: [iTMSTransporter] 	at com.apple.transporter.launcher.Application.main(Application.java:658)
[15:02:47]: [iTMSTransporter] Caused by: com.apple.transporter.bootstrap.BundleNotFoundException: bundle=[org.apache.logging.log4j.api] version=[2.11.2,3.0.0) not found.
[15:02:47]: [iTMSTransporter] 	at com.apple.transporter.bootstrap.BootstrapperPhase1.downloadNeededBundles(BootstrapperPhase1.java:269)
[15:02:47]: [iTMSTransporter] 	at com.apple.transporter.bootstrap.BootstrapperPhase1.bootstrap(BootstrapperPhase1.java:97)
[15:02:47]: [iTMSTransporter] 	at com.apple.transporter.bootstrap.BootstrapperPhase1.bootstrap(BootstrapperPhase1.java:59)
[15:02:47]: [iTMSTransporter] 	at com.apple.transporter.launcher.Launcher.launchBootstrapper(Launcher.java:37)
[15:02:47]: [iTMSTransporter] 	... 6 more

@richardtop did you resolve the issue above? If so, do you mind sharing how? I'm running into the same issue now.

It seems that it was a temporary issue with the Apple platform.


docs: update PPP

Codecov Report

Merging #265 (a9e54f0) into master (5ec3180) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #265   +/-   ##
=========================================
  Coverage     74.79%   74.79%
  Complexity      573      573
=========================================
  Files            83       83
  Lines          1956     1956
  Branches        183      183
=========================================
  Hits           1463     1463
  Misses          435      435
  Partials         58       58

Continue to review full report at Codecov.

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


Deprecation warning for ingress in extensions/v1beta1 while it was created using the networking.k8s.io/v1 API

Description
I am running Kubernetes v1.21 on AWS with the control plane managed by the EKS service.
I installed Grafana with a manifest that defines an Ingress using the networking.k8s.io/v1 API.
Ingresses are then implemented as an Application Load Balancer (ALB) in AWS by the aws-load-balancer-controller deployment. I am running v2.4.0 of that deployment, which is the latest version.
Expected behaviour
Running the deprecations plugin should not find that Ingress to be deprecated.
Setup
Kubernetes version: v1.21.5
Deprecations module version: v1.3.2
Grafana chart: official helm chart repo and github source files v6.17.10
helm: v3.5.1
Deprecations Plugin output
$ kubectl deprecations --context mycontext --k8s-version v1.21.5
W0222 16:15:18.147687   22639 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

RESULTS:
Deprecated APIs:

Ingress found in extensions/v1beta1
	 ├─ Ingress is a collection of rules that allow inbound connections to reach the endpoints defined by a backend. An Ingress can be configured to give services externally-reachable urls, load balance traffic, terminate SSL, offer name based virtual hosting etc. DEPRECATED - This group version of Ingress is deprecated by networking.k8s.io/v1beta1 Ingress. See the release notes for more information.
		-> OBJECT: shared-tools-grafana namespace: grafana

Manifest file for Ingress
Full source
Pertinent info only:
{{- if .Values.ingress.enabled -}}
[...]
apiVersion: {{ include "grafana.ingress.apiVersion" . }}
kind: Ingress
[...]

In our values, we set grafana.ingress.apiVersion to networking.k8s.io/v1
Yaml output of Ingress
No extensions/v1beta1 API is reported in here.
$ kubectl get ingress shared-tools-grafana -n grafana -o yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    alb.ingress.kubernetes.io/actions.ssl-redirect: '{"Type": "redirect", "RedirectConfig":
      { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/certificate-arn: arn:aws:acm:eu-central-1:REDACTED:certificate/REDACTED
    alb.ingress.kubernetes.io/healthcheck-path: /
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS": 443}]'
    alb.ingress.kubernetes.io/scheme: internal
    alb.ingress.kubernetes.io/tags: Stack=Monitoring,Environment=sandbox,Region=eu-central-1
    alb.ingress.kubernetes.io/target-type: ip
    kubernetes.io/ingress.class: alb
    meta.helm.sh/release-name: shared-tools
    meta.helm.sh/release-namespace: default
  creationTimestamp: "2022-02-22T16:16:03Z"
  finalizers:
  - ingress.k8s.aws/resources
  generation: 1
  labels:
    app.kubernetes.io/instance: shared-tools
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: grafana
    app.kubernetes.io/version: 8.2.5
    helm.sh/chart: grafana-6.17.10
  managedFields:
  - apiVersion: networking.k8s.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:alb.ingress.kubernetes.io/actions.ssl-redirect: {}
          f:alb.ingress.kubernetes.io/certificate-arn: {}
          f:alb.ingress.kubernetes.io/healthcheck-path: {}
          f:alb.ingress.kubernetes.io/listen-ports: {}
          f:alb.ingress.kubernetes.io/scheme: {}
          f:alb.ingress.kubernetes.io/tags: {}
          f:alb.ingress.kubernetes.io/target-type: {}
          f:kubernetes.io/ingress.class: {}
          f:meta.helm.sh/release-name: {}
          f:meta.helm.sh/release-namespace: {}
        f:labels:
          .: {}
          f:app.kubernetes.io/instance: {}
          f:app.kubernetes.io/managed-by: {}
          f:app.kubernetes.io/name: {}
          f:app.kubernetes.io/version: {}
          f:helm.sh/chart: {}
      f:spec:
        f:rules: {}
    manager: helm
    operation: Update
    time: "2022-02-22T16:16:03Z"
  - apiVersion: networking.k8s.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .: {}
          v:"ingress.k8s.aws/resources": {}
      f:status:
        f:loadBalancer:
          f:ingress: {}
    manager: controller
    operation: Update
    time: "2022-02-22T16:16:07Z"
  name: shared-tools-grafana
  namespace: grafana
  resourceVersion: "53785142"
  uid: REDACTED
spec:
  rules:
  - host: grafana.internal.REDACTED
    http:
      paths:
      - backend:
          service:
            name: shared-tools-grafana
            port:
              number: 80
        path: /
        pathType: Prefix
status:
  loadBalancer:
    ingress:
    - hostname: internal-k8s-grafana-sharedto-REDACTED-REDACTED.eu-central-1.elb.amazonaws.com

An idea that just crossed my mind: could it be that the go library your use to connect to the cluster is an outdated version that requests Ingresses using the former networking.k8s.io/v1beta1 api, then your code receives it using that api and finds it deprecated ?

I have the same problem, got "Ingress found in extensions/v1beta1" but actually there is "networking.k8s.io/v1" used. This is when I use kubepug on Windows.
But in Linux all is ok (different AKS cluster).
Maybe problem with Windows binary?

Ah right, I did not mention it but I was using MacOS.
I just tried on Linux (ubuntu 20.04 if that matters) and it gives me the same result as described.

I just installed kubepug and encountering the same issue, it's identifying all of the ingresses currently in my cluster.  When I do a kubectl get ingress I do not see any with extensions/v1beta1 listed.  On my end, running microk8s v1.21.9 on Ubuntu 20.04.4, kubepug v1.3.2.

I have the same issue on MacOS.

I did the following changes, and eventually it works for me.

upgraded k8s to 1.22.6
upgraded go from ~1.7 to 1.8
reinstalled kubepug (with krew)

I'm also having this issue when connecting to a 1.21 EKS cluster from my Linux machine (Fedora) using kubepug v1.3.3. Any suggestions?
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.9", GitCommit:"b631974d68ac5045e076c86a5c66fba6f128dc72", GitTreeState:"clean", BuildDate:"2022-01-19T17:51:12Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21+", GitVersion:"v1.21.5-eks-bc4871b", GitCommit:"5236faf39f1b7a7dabea8df12726f25608131aa9", GitTreeState:"clean", BuildDate:"2021-10-29T23:32:16Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}

$ kubectl krew list
PLUGIN        VERSION
deprecations  v1.3.3
krew          v0.4.3

from the kubernetes API perspective i think it was expected as per explained here. you can test it by using kubectl it self in k8s version 1.21
❯ kubectl get ingresses.v1beta1.extensions -A | head -n 2
Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
NAMESPACE   NAME                        CLASS          HOSTS                        ADDRESS         PORTS     AGE
gitlab      gitlab-minio                gitlab-nginx   minio.<IP_ADDRESS>.nip.io      <IP_ADDRESS>   80, 443   92d

❯ kubectl get ing/gitlab-minio -n gitlab -o jsonpath='{.apiVersion}'
networking.k8s.io/v1

i just skip for ingress detection since it will resolved in 1.22 as mentioned before.

I did the following changes, and eventually it works for me.
* upgraded k8s to `1.22.6`

* upgraded `go` from ~1.7 to 1.8

* reinstalled kubepug (with krew)

How skip check extensions/v1beta1 ?

After updating deprecations plugin via krew to v1.4.0 issue have been gone and Ingresses are no longer listed.
Upgrades available for installed plugins:
* deprecations v1.3.4 -> v1.4.0

After updating deprecations plugin via krew to v1.4.0 issue have been gone and Ingresses are no longer listed.
Just for the record: Using version v1.4.0 the issue still exists for us.

@0xErnie can you please point me to how to reproduce it?
Is it a Kubernetes v1.21, and you run Kubepug against it for what target version?
Thanks!

ok, found the problem, fixes coming next :)

fixed in https://github.com/rikatz/kubepug/pull/403/commits/a3ce8c88934bf0af510b399e6a779c8a794851cc

Fixed on #403, please reopen here or let me know if it is not working. The next release (v1.5.0-alpha.1) will contain the fix.
Thanks for using the project :)


[Bug]: Chromium doesn't install with Yarn 3.3.0 ("Could not find Chromium")

Bug description
Steps to reproduce the problem:
Reduced test case repo is here: https://github.com/davidcalhoun/puppeteer-yarn-postinstall-bug

mkdir puppetteer-yarn-test && cd puppetteer-yarn-test (create a new directory)
yarn init, then hit enter to all the prompts to accept all the defaults.  This will initialize a new project.
Open package.json and add "type": "module" (needed for using ES Modules import syntax in test.js below).
yarn set version stable (upgrades from Yarn 1 to Yarn 3)
touch .puppeteerrc.cjs and use your editor (e.g. nano .puppeteerrc.cjs) to copy in the recommended config for Puppeteer 19 from the Puppeteer docs.
yarn add --dev puppeteer
touch test.js and use your editor to copy in the search example code.
yarn node test.js

Notice on step 6 that Yarn mentions it needs to build Puppeteer (assuming it's running Puppeteer's postinstall script), but it completes suspiciously fast:
...
// Puppeteer 19 - it doesn't seem to be doing anything here, and Chromium never installs
➤ YN0000: ┌ Link step
➤ YN0007: │ puppeteer@npm:19.2.2 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 0s 727ms
...

Also note that no files are present in the expected path ./cache/puppeteer which we defined in .puppeteerrc.cjs on step 5.
Workaround
Downgrading to Puppeteer 17 as mentioned here works:

yarn remove puppeteer
yarn add --dev<EMAIL_ADDRESS>yarn node test.js

Notice with Puppeteer 17 that the postinstall seems to do actually be doing something as expected.  It takes ~9 seconds on my machine, versus <1 second on Puppeteer 19 (probably a no-op?):
...
// Puppeteer 17 output - it successfully takes the time to install Chromium
➤ YN0000: ┌ Link step
➤ YN0007: │ puppeteer@npm:17.1.3 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 9s 366ms
...

Puppeteer version
19.2.2
Node.js version
16.16.0
npm version
npm 9.1.1 and yarn 3.3.0
What operating system are you seeing the problem on?
macOS
Configuration file
/**
 * Copied from recommended Puppeteer v19 config found at
 * https://pptr.dev/guides/configuration#changing-the-default-cache-directory
 */

const {join} = require('path');

/**
 * @type {import("puppeteer").Configuration}
 */
module.exports = {
  // Changes the cache location for Puppeteer.
  cacheDirectory: join(__dirname, '.cache', 'puppeteer'),
};

Relevant log output
dcalhoun@Davids-MBP-2 puppeteer-yarn-postinstall-bug % yarn node test.js
file:///Users/dcalhoun/dev/puppeteer-yarn-postinstall-bug/.yarn/cache/puppeteer-core-npm-19.2.2-830fad0e0f-5d27545666.zip/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:94
                    throw new Error(`Could not find Chromium (rev. ${this.puppeteer.browserRevision}). This can occur if either\n` +
                          ^

Error: Could not find Chromium (rev. 1056772). This can occur if either
 1. you did not perform an installation before running the script (e.g. `npm install`) or
 2. your cache path is incorrectly configured (which is: /Users/dcalhoun/dev/puppeteer-yarn-postinstall-bug/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
    at ChromeLauncher.resolveExecutablePath (file:///Users/dcalhoun/dev/puppeteer-yarn-postinstall-bug/.yarn/cache/puppeteer-core-npm-19.2.2-830fad0e0f-5d27545666.zip/node_modules/puppeteer-core/lib/esm/puppeteer/node/ProductLauncher.js:94:27)
    at ChromeLauncher.executablePath (file:///Users/dcalhoun/dev/puppeteer-yarn-postinstall-bug/.yarn/cache/puppeteer-core-npm-19.2.2-830fad0e0f-5d27545666.zip/node_modules/puppeteer-core/lib/esm/puppeteer/node/ChromeLauncher.js:160:25)
    at ChromeLauncher.launch (file:///Users/dcalhoun/dev/puppeteer-yarn-postinstall-bug/.yarn/cache/puppeteer-core-npm-19.2.2-830fad0e0f-5d27545666.zip/node_modules/puppeteer-core/lib/esm/puppeteer/node/ChromeLauncher.js:64:37)
    at async file:///Users/dcalhoun/dev/puppeteer-yarn-postinstall-bug/test.js:4:19

@davidcalhoun I am unable to reproduce. I followed the steps in your rep and got Chrome version installed in .cache/puppeteer inside the repo root. Also, test.js runs fine.

Still, unable to repro. Are there any other details that are missing from the repro? Perhaps some environment variables are set?

Thank you for checking, I checked with a coworker and they also can't reproduce from the repo I linked to.  I'm also seeing this Could not find Chromium happening on our Github Actions CI but I'm trying to narrow it down locally first.

It looks like the download might be failing? If you run the installation with the env var DEBUG=puppeteer:* you should see where Puppeteer attempts downloading the binary to (not sure if yarn would send the logs to stdout but works with npm).


Uncaught Error: variable @bran is undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 0.176.0
System: linux 3.13.0-45-generic
Thrown From: Atom Core
Stack Trace
Uncaught Error: variable @bran is undefined
At /usr/share/atom/resources/app/node_modules/less-cache/node_modules/less/lib/less/parser.js:604

Error:
  at new Parser (/usr/share/atom/resources/app/node_modules/less-cache/node_modules/less/lib/less/parser.js:333:27)
  at Object.module.exports.grammars.LESS.render (/home/nick/.atom/packages/preview/lib/renderer.coffee:73:21)
  at PreviewView.module.exports.PreviewView.renderPreviewWithRenderer (/home/nick/.atom/packages/preview/lib/preview-view.coffee:270:27)
  at PreviewView.renderPreviewWithRenderer (/home/nick/.atom/packages/preview/lib/preview-view.coffee:1:1)
  at PreviewView.module.exports.PreviewView.renderPreview (/home/nick/.atom/packages/preview/lib/preview-view.coffee:155:6)
  at PreviewView.renderPreview (/home/nick/.atom/packages/preview/lib/preview-view.coffee:1:1)
  at later (/usr/share/atom/resources/app/node_modules/roaster/node_modules/underscore/underscore.js:724:25)

Commands
  2x -1:05.3 core:backspace (atom-text-editor.editor.is-focused)
     -1:04.4 editor:newline (atom-text-editor.editor.is-focused)
     -1:03.9 core:move-right (atom-text-editor.editor.is-focused)
     -1:03.7 core:move-up (atom-text-editor.editor.is-focused)
     -1:03.4 core:move-down (atom-text-editor.editor.is-focused)
     -1:03.1 core:move-left (atom-text-editor.editor.is-focused)
     -1:02.7 core:move-right (atom-text-editor.editor.is-focused)
  6x -1:02.5 core:move-left (atom-text-editor.editor.is-focused)
     -1:00.9 core:move-right (atom-text-editor.editor.is-focused)
 10x -1:00.8 core:backspace (atom-text-editor.editor.is-focused)
     -0:59.5 core:move-up (atom-text-editor.editor.is-focused)
  2x -0:59.3 editor:newline (atom-text-editor.editor.is-focused)
  2x -0:59.0 core:move-up (atom-text-editor.editor.is-focused)
  2x -0:56.0 core:move-right (atom-text-editor.editor.is-focused)
  3x -0:55.3 core:move-down (atom-text-editor.editor.is-focused)
     -0:54.9 core:move-left (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "editor": {
    "invisibles": {}
  }
}

Installed Packages
# User
angularjs, v0.1.0
atom-beautify, v0.21.2
git-blame, v0.4.0
git-log, v0.2.0
go-plus, v3.2.1
language-jade, v0.3.0
last-cursor-position, v0.7.0
linter-less, v0.3.1

# Dev
No dev packages

Autocomplete typing a darken(.. function in a LESS file.

Is this reproducible in safe mode (atom --safe)?

Looks like a dupe of https://github.com/atom/atom/issues/5443, so closing this one.


Remove Breadcrumb

We're actually not going to use the smart_start layout this year. We created a new summer_courses layout that already has the breadcrumb removed along with some other updates.
So I think I'd prefer to keep the old smart_start layout how it was when we were using it.


feat(typescript_indexer): add references to imports of 3rd party modules

Adds ref/imports edges from imports to modules declared in .d.ts files.

@evmar can you take a look?
This PR depends on https://github.com/kythe/kythe/pull/4164 so it will fail until the other PR is merged.

@evmar friendly ping


is it possible to get the logs of the container which is crashlooping?

Hi,
Thanks for this fork, and development.
The main issue I face with stern, is that it's not able to get the logs of pods, which are crashlooping. Is it possible ?

wow!! it's working. Thanks


ISKON Events Card Misalignment Overlapping Footer

Description
Describe the bug:
The last card displaying ISKON events is positioned incorrectly, appearing on the footer section, which makes it unattractive.
Expected behavior:
The ISKON events cards should be positioned correctly within the designated area, without overlapping the footer section.
Actual behavior:
The last card overlaps with the footer section, making it unattractive and disrupting the layout.
Reproduction Steps
Steps to reproduce the behavior:
1.Navigate to the 'Features' section.
2.Scroll down to the ISKON events cards.
3.Observe the position of the last card in relation to the footer section.
Expected result:
The last card should be displayed within the designated area, above the footer section.
Actual result:
The last card overlaps with the footer section, causing a layout issue.
Screenshots

I kindly request to be assigned to this issue. As a Technical Executive at the IEEE CUIET Organization, I am well-positioned to address this matter. I am committed to delivering optimal results and have prior experience with similar projects, which I believe will enable me to make a meaningful contribution.
reference for prior work / projects :-|
https://www.linkedin.com/in/akshit-verma-596a0824b/


'utf-8' codec can't decode vocab.pt in pretrain models

When I use pretrain models like USPTO_MT_model.tar.bz2 or simple_pretrain.tar.bz2, it occurs that:
Traceback (most recent call last):
  File "/home/hcp/Chem/t5chem/test.py", line 6, in <module>
    tokenizer = SimpleTokenizer(vocab_file=os.path.join(pretrain_path, 'vocab.pt'))
  File "/home/hcp/Chem/t5chem/t5chem/mol_tokenizers.py", line 204, in __init__
    super().__init__(vocab_file=vocab_file, max_size=max_size, **kwargs)
  File "/home/hcp/Chem/t5chem/t5chem/mol_tokenizers.py", line 75, in __init__
    self.create_vocab(vocab_file=vocab_file)
  File "/home/hcp/Chem/t5chem/t5chem/mol_tokenizers.py", line 101, in create_vocab
    self.vocab: Vocab = Vocab.load(vocab_file)
  File "/home/hcp/Chem/t5chem/t5chem/mol_tokenizers.py", line 51, in load
    tokens = [line.strip() for line in f]
  File "/home/hcp/Chem/t5chem/t5chem/mol_tokenizers.py", line 51, in <listcomp>
    tokens = [line.strip() for line in f]
  File "/home/hcp/miniconda3/envs/t5chem/lib/python3.9/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 64: invalid start byte

Looking for your reply!

And it seems that vocab.pt cannot be used in train --data_dir data/sample/regression/ --output_dir model/ --task_type regression --pretrain ./pretrain_model/pretrain/simple.It occurs that:
Namespace(data_dir='data/sample/regression/', output_dir='model/', task_type='regression', run_name='', pretrain='./pretrain_model/pretrain/simple', vocab='', tokenizer='', random_seed=8570, num_epoch=100, eval_steps=5000, log_step=1000, batch_size=32, init_lr=0.0005, num_classes=None, command=<function train at 0x7f5e65edbb80>)
Some weights of T5ForProperty were not initialized from the model checkpoint at ./pretrain_model/pretrain/simple and are newly initialized because the shapes did not match:
- lm_head.weight: found shape torch.Size([100, 256]) in the checkpoint and torch.Size([2, 256]) in the model instantiated
You should probably TRAIN this model on a down-stream task to be able to use it for predictions and inference.
Traceback (most recent call last):
  File "/home/hcp/miniconda3/envs/t5chem/bin/t5chem", line 8, in <module>
    sys.exit(main())
  File "/home/hcp/miniconda3/envs/t5chem/lib/python3.9/site-packages/t5chem/__main__.py", line 33, in main
    command(args)
  File "/home/hcp/miniconda3/envs/t5chem/lib/python3.9/site-packages/t5chem/run_trainer.py", line 146, in train
    raise ValueError(
ValueError: Can't find a vocabulary file at path './pretrain_model/pretrain/simple'.

When I use pretrain models like USPTO_MT_model.tar.bz2 or simple_pretrain.tar.bz2, it occurs that:
Traceback (most recent call last):
  File "/home/hcp/Chem/t5chem/test.py", line 6, in <module>
    tokenizer = SimpleTokenizer(vocab_file=os.path.join(pretrain_path, 'vocab.pt'))
  File "/home/hcp/Chem/t5chem/t5chem/mol_tokenizers.py", line 204, in __init__
    super().__init__(vocab_file=vocab_file, max_size=max_size, **kwargs)
  File "/home/hcp/Chem/t5chem/t5chem/mol_tokenizers.py", line 75, in __init__
    self.create_vocab(vocab_file=vocab_file)
  File "/home/hcp/Chem/t5chem/t5chem/mol_tokenizers.py", line 101, in create_vocab
    self.vocab: Vocab = Vocab.load(vocab_file)
  File "/home/hcp/Chem/t5chem/t5chem/mol_tokenizers.py", line 51, in load
    tokens = [line.strip() for line in f]
  File "/home/hcp/Chem/t5chem/t5chem/mol_tokenizers.py", line 51, in <listcomp>
    tokens = [line.strip() for line in f]
  File "/home/hcp/miniconda3/envs/t5chem/lib/python3.9/codecs.py", line 322, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 64: invalid start byte

Looking for your reply!

Hi, I just updated this repo and now it loads plain text rather than *.pt file, you may need to git pull the lastest commits (make sure you have 1.2.0 version).

And it seems that vocab.pt cannot be used in train --data_dir data/sample/regression/ --output_dir model/ --task_type regression --pretrain ./pretrain_model/pretrain/simple.It occurs that:
Namespace(data_dir='data/sample/regression/', output_dir='model/', task_type='regression', run_name='', pretrain='./pretrain_model/pretrain/simple', vocab='', tokenizer='', random_seed=8570, num_epoch=100, eval_steps=5000, log_step=1000, batch_size=32, init_lr=0.0005, num_classes=None, command=<function train at 0x7f5e65edbb80>)
Some weights of T5ForProperty were not initialized from the model checkpoint at ./pretrain_model/pretrain/simple and are newly initialized because the shapes did not match:
- lm_head.weight: found shape torch.Size([100, 256]) in the checkpoint and torch.Size([2, 256]) in the model instantiated
You should probably TRAIN this model on a down-stream task to be able to use it for predictions and inference.
Traceback (most recent call last):
  File "/home/hcp/miniconda3/envs/t5chem/bin/t5chem", line 8, in <module>
    sys.exit(main())
  File "/home/hcp/miniconda3/envs/t5chem/lib/python3.9/site-packages/t5chem/__main__.py", line 33, in main
    command(args)
  File "/home/hcp/miniconda3/envs/t5chem/lib/python3.9/site-packages/t5chem/run_trainer.py", line 146, in train
    raise ValueError(
ValueError: Can't find a vocabulary file at path './pretrain_model/pretrain/simple'.

Thank you for catching this issue! The vocab.pt file in the old compressed file is incompatible with the current code version. I've notified the website administrator to update the model weights file, though this may take some time. In the meantime, please try this workaround:
replace the old .pt file with the .txt file using the following command:
cp t5chem/vocab/simple.txt models/pretrain/simple/vocab.txt

This is what I did starting from a fresh new machine:
pip install t5chem --index-url https://pypi.org/project/
wget https://yzhang.hpc.nyu.edu/T5Chem/data/sample_data.tar.bz2
wget https://yzhang.hpc.nyu.edu/T5Chem/models/simple_pretrain.tar.bz2
tar -xjvf sample_data.tar.bz2
tar -xjvf simple_pretrain.tar.bz2

wget https://raw.githubusercontent.com/HelloJocelynLu/t5chem/refs/heads/main/t5chem/vocab/simple.txt
cp simple.txt models/pretrain/simple/vocab.txt

t5chem train --data_dir data/sample/regression/ --output_dir model/ --task_type regression --pretrain models/pretrain/simple
t5chem predict --data_dir data/sample/regression/ --model_dir model/

Then this is what I got:

This is what I did starting from a fresh new machine:

Thank you very much for your reply! You are the most prompt author I have ever encountered in handling issues!XD I have tried the content of your previous response, and I am now able to start training and making predictions. Thank you for your assistance, and I wish you a successful scientific research journey!


Log resque errors

https://github.com/CartoDB/cartodb-central/issues/2200
Also see https://github.com/CartoDB/cartodb-central/pull/2334

Acceptance 🍏 -> https://rollbar.com/carto/CartoDB/items/36067/


Since v5.16.0 cannot get tarball file: 404 "file not found"

verdaccio version: 5.16.0 and upper
node version: v16.14.0
package manager<EMAIL_ADDRESS><EMAIL_ADDRESS>os: linux
platform: docker
We had Verdaccio 5.15.4 with Minio storage (RELEASE.2022-10-24T18-35-07Z).
config.yml contains the lines:
store:
  minio:
    port: 9000
    region: us-east-1
    endPoint: <IP_ADDRESS>
    accessKey: minioadmin
    secretKey: minioadmin
    useSSL: false

It worked fine.
After upgrading to 5.18.0 we get errors on "yarn add @our/package":
yarn add v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://our-verdaccio-site.com/commander/-/commander-9.4.1.tgz: Request failed \"404 Not Found\""

If you try to get tarball file with the direct link - https://our-verdaccio-site.com/commander/-/commander-9.4.1.tgz - the same error appears: 404 "file not found".
The file commander-9.4.1.tgz exists in Minio though.
The error appears only since v5.16.0 (I tried 5.16.0, 5.16.1, 5.16.2, 5.16.3, 5.17.0, 5.18.0)
Debug logs:
01.12.2022, 21:09:59 debug--- [Minio] ReadStream<commander/commander-9.4.1.tgz> is opened
01.12.2022, 21:09:59 debug--- [Minio] ReadStream<commander/commander-9.4.1.tgz> received 28174 bytes
01.12.2022, 21:09:59 debug--- [Minio] ReadStream<commander/commander-9.4.1.tgz> is finishing

Could you share a docker compose or something that reproduce how you run minio?

Yes, of course.
version: "3.8"
services:

  minio:
    image: minio/minio:RELEASE.2022-10-24T18-35-07Z
    container_name: minio
    volumes:
      - /opt/minio:/data
    command:
      - server
      - /data
      - --console-address=:9001
    ports:
      - 9000:9000
      - 9001:9001
    restart: always

networks:
  default:
    name: minio-network

It think is missing the part you run your image, how do you include the plugins etc

Additionally if you want a playground, you can PR on this repo: https://github.com/verdaccio/e2e-5.x
Create your own docker compose with mini and create a smoke test just like:
https://github.com/verdaccio/e2e-5.x/blob/main/.github/workflows/docker-proxy-nginx-e2e.yml
It's very simple and would be great to have for future releases avoid regressions.

Here is verdaccio docker-compose.yml. We have separated minio and verdaccio docker-compose files for some reasons.
version: "3.8"
services:

  verdaccio:
    image: verdaccio/verdaccio:5.15.4
    container_name: verdaccio
    volumes:
      - ./verdaccio/config.yaml:/verdaccio/conf/config.yaml
      - ./verdaccio-minio:/verdaccio/plugins/verdaccio-minio
    environment:
      - VERDACCIO_PUBLIC_URL=https://our-verdaccio-site.com
    ports:
      - 4873:4873
    restart: always

networks:
  default:
    name: verdaccio-network

It works fine.
After upgrading to 5.18.0 we get error 404 (see above).

same for me

fixed at https://github.com/verdaccio/verdaccio/releases/tag/v6.0.2


refactor!: use vim.api.nvim_set_hl()

Completely broken.

Not sure why it's never going into table conditional in https://github.com/andersevenrud/nordic.nvim/pull/70/files#diff-87af52ac4b5511b195aa96dd5bdea0128de6210195d900717f6e55f58c004c66R111.
I am trying to make output from nordic functions to return objects that are ready to be injected into vim.api.nvim_set_hl().

Ignore that comment. I clearly misread something in the docs. Stand by...

Well, not that far off :sweat_smile: I was unaware of the naming and that the gui attribute is now split into properties.
                local definition = {
                    fg = group[2] or 'NONE',
                    bg = group[3] or 'NONE',
                    sp = group[5] or 'NONE',
                }

                if group[4] then
                    definition[group[4]] = true
                end

                vim.api.nvim_set_hl(0, group[1], definition)

One thing I don't know about here is underline though, because that's an option, and I don't know if underline supports a non-bool value :man_shrugging: I can't find the definition of this in the docs for some reason...

Thanks! Will look into it tomorrow. But basically you are against changing group configurations the way I did in fidget.lua or standard.lua? Should make it easier for that very PR, but could get rid of those table[n] maps.
Thanks for looking into it!

But basically you are against changing group configurations

Nope.
I just didn't understand the impact of using this function.
But now that I get it this should be fairly easy to do. The fastest way is to change the tables from this:
{ name | table, fg, bg, style, sp }

to:
{ name | table, { fg = '', bg = '' } }

Then finally:
    local function load_group(list)
        for _, group in ipairs(list) do
            if type(group) == 'function' then
                load_group(group(unpack(arguments)))
            elseif type(group[1]) == 'table' then
                load_group(vim.tbl_map(function(highlight)
                    return { highlight, group[2] }
                end, group[1]))
            else
                vim.api.nvim_set_hl(0, group[1], group[2])
            end
        end
    end

FYI: I updated the description with some tasks

There's actually an even simpler way for this, but I'm not sure how I feel about it because it involves using some black Lua magic to have a mix between a list and an associative array:
-- This works :o
local t = { "foo", fg = "bar" }
print(t[0])
print(t.fg)

Which means that technically one can do this:
{ name | name[], fg = '', bg = '', ... }

        for _, group in ipairs(list) do
            if type(group) == 'function' then
                load_group(group(unpack(arguments)))
            elseif type(group[1]) == 'table' then
                load_group(vim.tbl_map(function(highlight)
                    return { highlight, group }
                end, group[1]))
            else
                local definition = {}
                for k, v in pairs(group) do
                  if type(k) == 'string' then
                    definition[k] = v
                  end
                done
                vim.highlight.create(group[1], definition)
            end
        end

I will come back to it, but most likely not in next couple of weeks unfortunately.

Alright. Take your time :)


[BUG] jsonable_encoder does not take the Config into account for Enums

Describe the bug
When calling jsonable_encoder on a pydantic object that makes use of an Enum for a field, the JSON response contains the Enum.field.value, whereas the default behavior should be to use Enum.field.name (as per the Config.use_enum_values which is False by default)
in the code, file encoders.py, around line 26:
def jsonable_encoder
...
    if isinstance(obj, Enum):
        return obj.value

To Reproduce
Steps to reproduce the behavior:

Create a file with

from enum import Enum
from pydantic import BaseModel

class AuditType(Enum):
    rank = "RankValue"
    count = "CountValue"

class AuditBase(BaseModel):
    type: AuditType = None

Add a test which calls jsonable_encoder on an instance

from fastapi.encoders import jsonable_encoder
obj_in = AuditBase(type=AuditType.count)
print(jsonable_encoder(obj_in))

See error, i.e {'type': 'CountValue'} instead of {'type': 'count'}

Expected behavior
The expected behavior should be to check the value of the Config.use_enum_values and return the name or the value appropriately
Environment:

FastAPI Version 0.18.0
Python version 3.7.2

Thanks for the report. I'll check it.

I'm delaying this until https://github.com/samuelcolvin/pydantic/pull/520 is resolved.
It will change how responses are encoded from Pydantic models in a much cleaner way. And it will solve several issues at the same time (most probably including this).

Pydantic has a recent/new ORM mode.
I just finished a deep integration of it into FastAPI. It is released in version 0.30.0 :tada:
Now, if you use a response_model, Pydantic will take whatever is returned by your path operation function and use it directly. Without being passed through jsonable_encoder.
If you use ORM object (SQLAlchemy, Peewee, etc) you should use Pydantic's orm_mode = True to tell Pydantic to extract the data from the ORM objects. The new docs are here: https://fastapi.tiangolo.com/tutorial/sql-databases/
Also, in case I'm misunderstanding the question, specific to the configs set in Pydantic models, I'm pretty sure the jsonable_encoder was updated at some point to use the configs from the model, maybe your specific issue was solved by that change in a previous version?

I assume this was solved in recent versions, so I'll close this issue.
But feel free to add more comments or create new issues.


x/mint: understand and refactor keeper tests

Background
This is a follow-up to #1839
Some tests in x/mint keeper are complex and poorly understood. We need to refactor them for clarity if applicable. This includes:

TestMintCoinsToFeeCollectorAndGetProportions
TestDistrAssetToDeveloperRewardsAddrWhenNotEmpty

Acceptance Criteria

investigate the above tests
refactor if needed
add comments to make them clear

Hi @p0mvn. Could  I work on this issue?

Hey, we're trying to formulate some testing standards / architecture of module tests and the like right now. Really appreciate the enthusiasm!
I feel like this was made into its own issue too soon, whereas it should have been a sub-item in #1839 until we stopped working on that :sweat_smile: (or self-assigned when the issue was made!)
I think this will be better for informing testing standards & 'module audit standards' were trying to develop if Roman has time to tackle directly. (Also he's already started on this) If you'd like to help out with tests, would you be down to work on:

https://github.com/osmosis-labs/osmosis/issues/1756
Auditing / reviewing the pool-incentive module ? That hasn't been started, and would love for you to be involved in some of this auditing / review process!

Thank you for your advice @p0mvn. I'll ask carefully so as not to waste time!


Extra page without inserting the icon for TabBar

Howdy,
I have recently run into situation that I need an extra page/view that not include the icon into the TabBar, my current solution is adding an extra if as below
Line 303 in src/TabBar.js
{routes.map((route, i) => {
    const focused = index === i;
    const outputRange = inputRange.map(inputIndex => inputIndex === i ? 1 : 0.7);

Replace with
{routes.map((route, i) => {

    // skip if not required to display icon
    if (i.hideIcon) return;

    const focused = index === i;
    const outputRange = inputRange.map(inputIndex => inputIndex === i ? 1 : 0.7);

Then in the state setup
state = {
    index: 0,
    routes: [
        { key: '1', icon: 'home' },
        { key: '2', icon: 'magnify' },
        { key: '3', hideIcon: true }
    ]
};

Also setup as normal for 3 keys (as above example)
_renderScene = ({route}) => {
    switch (route.key) {
        ...
    }
}

Happy to do a PR if this sounds good.
Cheer!

I think you can achieve it by following too,
_renderHeader = (props) => {
  const navigationState = props.navigationState(route => !route.hide);
  const jumpToIndex = index => props.jumpToIndex(props.navigationState.indexOf(navigationState[index]));
  return <TabBarTop {...props} navigationState={navigationState} jumpToIndex={jumpToIndex} />;
};

Same for renderFooter.
I've not tried it though. Try and lemme know if it works for you.

There might be a miss understanding,
I believe solution you provided was trying to hide all icons (which your code works as I tried).
The situation I ran into was having 6 routes but only need to display icon of 4 in the TabBar

@mrjcka Hmm... no, it wasn't to hide all icons

I tried again, it does works!
Cheers!

How do I make it so that if I go to a hidden tab, the underline below the selected tab is not the last visible tab?


write the test summary into file (into DEPLOY dir) instead of into ENV

ENV size is limited, test summary should rather be saved into the deploy dir; + print it's path, maybe the path could be exposed as an ENV

Done


schema: fix: make att.course.log member of att.accidental

This PR makes att.course.log member of att.accidental, so @accid is available for course and string.
Closes #1542

Pinging @janjusolja, @DILewis, @reinierdevalk (@music-encoding/ig-tablature) to double-check that this change/fix is in line with IG needs.


为什么我运行的时候总提示 the model and loaded state dict do not match exactly?

是框架的问题吗？
missing keys in source state_dict: backbone.conv1.weight, backbone.bn1.weight, backbone.bn1.bias, backbone.bn1.running_mean, backbone.bn1.running_var, backbone.layer1.0.conv1.weight, backbone.layer1.0.bn1.weight, backbone.layer1.0.bn1.bias, backbone.layer1.0.bn1.running_mean,............

我有同样的问题，请问您解决了吗？


Remove usage of standalone Tag to avoid race condition

Description of your changes

I encountered situation when Tag and SecurityGroup were having race condition and discovery tag was disappearing from the external security group resource
It is safe to deprecate Tag usage as we have SSA with the switch to Functions

I have:

[x] Read and followed Upbound's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested
e2e together with https://github.com/upbound/configuration-aws-eks-karpenter/ and associate discovery
Plus uptest below

/test-examples

/test-examples


Allow Filtering of EBS Volumes from Snapshot Job

Hello cmachler..!
if we do c drive backup it will not take backup everything while system running. if we deploy every app on D drive. (i.e. device_name = "xvdb"). we want to take only specific drive not all attached drive.
How can we filter volumes in your script and backup only those devices.?
Hope you understand the need.

That would have to be an enhancement to the script to exclude specific EBS volumes from snapshots by the job. I will take a look at this when I can, or I open this up to anyone in the community to work on this feature.
But yes I do see the need for filtering volumes.

Hello cmachler,
I have used "lambda-ebs-backup.py" script in lambda function using all the steps you have provided  however, when I run a "Test" the lambda function it get "Execution result: succeeded" but it doesn't find any instance in region. The message in logs shows  "Found 0 instances that need backing up in region us-east-1".  I have 80 instances running in us-east-1 region.  And I have set Lambda environment variable "aws_regions" =  "dXMtZWFzdC0x" (without " ").
I have attached the script which I have used.
lambda-ebs-backup.docx
Please suggest what could be the issue here.

Please elaborate process of "Add the SNS Topics ARN you want publish as a Lambda environmenet variable "aws_sns_arn""

@mkatkade please double check your IAM permissions with regards to no instances being found. As for SNS ARN please see the following AWS documentation (http://docs.aws.amazon.com/sns/latest/dg/CreateTopic.html) for more information.
FYI next time please open a new issue instead of commenting on an existing issue that is a different topic.

@ramdevops1 I just added this functionality, to skip volumes perform the following:

Add the tag key to the instance Skip_Backup_Volumes
To the above key add the value with the single volume-id or multiple volume-id's in a CSV string.

Let me know if you have any questions.

I want to customize snapshot name .
How can I change ?


Enable Dwarf EH for FreeBSD

Let's see where we are with this.

And it "just works"!

cool beans

@WalterBright it should work on all x86 targets where you use gcc. ;-)

I doubt it will work on OSX, because the MACH-O object format does fixups and PIC code differently.

I thought you switched to Clang on osx?  I was thinking about the other BSDs and Solaris actually.


Rebase next onto master

With the EOL of Node 4 imminent, let's rebase next onto master, and start working on 1.0 on master.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #145   +/-   ##
=======================================
  Coverage   96.66%   96.66%
=======================================
  Files          10       10
  Lines         330      330
  Branches       19       19
=======================================
  Hits          319      319
  Misses         11       11

Impacted Files
Coverage Δ

test/fixtures.ts
100% <100%> (ø)
:arrow_up:

test/test-kitchen.ts
100% <100%> (ø)
:arrow_up:

src/util.ts
94.11% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


feat: enable format json for log

to test:
export LOG_APP_FORMAT=json
make run-sandbox

result:
web.1 |<EMAIL_ADDRESS>alert: no DSN provided, error reporting disabled
web.1 |  (node:17369) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
web.1 |  (Use `node --trace-warnings ...` to show where the warning was created)
web.1 |  {"level":"info","message":"Functions metrics is listening on port 8101"}
web.1 |<EMAIL_ADDRESS>alert: no DSN provided, error reporting disabled
web.1 |  (node:17370) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
web.1 |  (Use `node --trace-warnings ...` to show where the warning was created)
web.1 |  {"level":"info","message":"Functions is listening on port 8100"}

I think that your change inside lib/support/log.js doesn't affect log.
The exported logger inside this file didn't import and used in another files. Note that morgan logger was used as default https://github.com/globocom/functions/master/lib/http/routes.js#L37

hey @ceelsoin !
The Morgan log is used only for express application and can be override by envvar
LOG_MONGAN_FORMAT={"method":":method","request_uri":":url","status":":status"}

Others files import /support/log to log errors / debug, You can find here

Lol, i double checked here and it is been used like you sent. But no makes sense two loggers in use. Winston can assume logger from http requests instead of multer.

Returning for this
For we can approve, please provide these log options inside readme.md


enhancement request for new wunderground api

A new wunderground api for personal weather stations has been released and a new node pkg supporting it exists: https://www.npmjs.com/package/weather-underground-node
Would love to see support for it added to homebridge-weather-plus.

Thanks for the link. I will look into this.

I can confirm the current plugin cannot fetch data from the PWS API. Would be great if this can be added. So far the weather plus plugin is the best of its kind.

Here is a link to the new API documentation: https://docs.google.com/document/d/1eKCnKXI9xnoMGRRzOL1xPCBihNV2rOet08qpE_gArAY/edit

Added in v2.8.0


Breaking change in 2.26.0 in iam-assumable-role module

Changes of this commit https://github.com/terraform-aws-modules/terraform-aws-iam/commit/f34e1035fbb8d5ec2646659eb921ce8933797965#diff-4c5de4a6dab157fe74e11cc36213e70dfcd41643b5d643776cfe1a5abc04350a are breaking changes, forcing people to modify their code using version 2.26.0 of the module iam-assumable-role.
But according to the versioning, it should not cause some breaking change like this, otherwise it should have been release in 3.0.0.

ditto... hit this too.  Was using ~>2.22, so didn't expect such a breaking change to arrive in a minor version release. Deleted all our iam policy bindings, causing stuff to fail.

Changed in https://github.com/terraform-aws-modules/terraform-aws-iam/pull/96

I agree, will revert now. I didn't think about BC this time :(

v3.1.0 has been just released, while
v2.25.0 is the latest in v2.
Apologize for the confusion.

The top level README.md probably needs updates to show the newly required number_of_role_policy_arns and number_of_custom_role_policy_arns variables.  Current examples won't work.

Well, I guess they will, since they say version = "~> 2.0", but probably should update that to 3.0, and fix the examples.

Good catch. Fixed in #105, released v3.2.0.


Update levigo to the latest version to fix building errors on MacOS.

Update levigo to the latest version to fix building errors on MacOS 10.15.3 with leveldb version 1.22 (not tested on Other platforms).
Also update protobuf to the latest version.

@coocy could you rebase this PR? Some updates have been made.

Merged in https://github.com/omniscale/imposm3/commit/b7e153bfbfd4a8d6ce83a370d4bb9278eaf8df71


Tic tac toe

This is a CLI Based Tic Tac Toe Game written by me from Scratch using C++.
2D Array is being used to play the game and vector is also included to play against Computer
Code for issue #1

Nice work there, if your are interested in reviewing and emerging PRs I can provide you the write access

@ron2111 I can help with C/C++ Codes

Just take care of these things before merging the PRs,

Updation on project_doc.md
Name in the contributors list
Project should be under the respective techstack folder only
Don't merge projects with more than 100 file changes
Guide the contributors in case of merge conflicts

and if you find any problem/query comment it and assign it any of the collaborators:
@prathimacode-hub
@ron2111
@aflah02

Sure, I'll try my best in helping out

@ron2111 I can help with C/C++ Codes

Ok, accept the invite then.


chore(perm-dev): Updated permissions assigned to GithubToken

Proposed changes
Updated the permissions needed to run this action according to the permissions it requires.  Some people have the GitHub Token permissions defined in a least permissive manner, so this will allow them to fork your repo and more clearly identify inherent permissions being granted.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Further comments
This is a super small update just granting the default github.token used by an action the correct permissions required.

Hey @actuarysailor, thank you for the PR ❤


Improve documentation

Proposed changes
This PR improve documentation.
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update only documentation, not any source code.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[ ] I have signed the CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
N/A

Codecov Report

Merging #53 (e3a85fe) into main (b15711a) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head e3a85fe differs from pull request most recent head 3f00bda. Consider uploading reports for the commit 3f00bda to get more accurate results

@@           Coverage Diff           @@
##             main      #53   +/-   ##
=======================================
  Coverage   88.64%   88.64%
=======================================
  Files           2        2
  Lines         634      634
=======================================
  Hits          562      562
  Misses         72       72

Continue to review full report at Codecov.

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


Add Vonage SMS provider

What kind of change does this PR introduce?
Introduce new SMS provider Vonage
What is the current behavior?
The only available SMS providers are Twilio and MessageBird.
What is the new behavior?
Change the following env variables, users will be able to send SMS with Vonage SMS API.
GOTRUE_SMS_PROVIDER=vonage
GOTRUE_SMS_VONAGE_API_KEY="<api_key>"
GOTRUE_SMS_VONAGE_API_SECRET="<api_secret>"
GOTRUE_SMS_VONAGE_FROM="<brand or from>"

Additional context
Implementation displays the message from Vonage API if an error occurs.
SMS API error codes

As per https://twitter.com/kiwicopple/status/1479442937545203716

Hey @devkiran, thanks so much for your contribution! This is awesome 💥 we now have a new sms provider! :)

@kangmingtay you're welcome. Happy to help 👍

@devkiran great work! I was just looking to add this and saw your contribution. Nice.
Big thank you from team Vonage. :)
@kangmingtay If there is more that needs to be added on frontend or documentation side, I am happy to help.


Fix Package Installation Pop-Up When Opening Template

Steps to Reproduce

Choose File -> Open Template
Select the Formal Letter Template
Click Load Template

Actual Result
After a few seconds, a Package Installation dialog will pop-up.  If the user does not choose Install or Cancel within a few seconds, the pop-up automatically closes.  This happens for all templates except for Plain Cover Letter.
Expected Result
The pop-up should not automatically close without user input.

It depends of your LaTeX settings. This situation occurs if you selected sth like "ask me for installing package" during LaTeX installation. I fixed it by reinstalling LaTeX with "always install packages" option. I think (not 100% sure) that it's not Open-LaTeX-Studio issue.

As @aQaTL mentioned, those popups come from the LaTeX distribution, not from Open LaTeX Studio. Still, maybe it's worth investigating whether we can improve anything on our side, when user chose not to install packages automatically.

All that's happening with autoinstall is just masking the issue.  There is a real issue in the dialog message timing out before user hit's install or cancel.  Definitely worth looking into.


Add tests

Need add tests
Performance test for translate function
Unit tests also for translate function and for another

Done


Moved queriesArray from render() to local state

Before:

queriesArray is reloaded during each render, but for some re-rendering caused by prop-change like tables, queriesArray doesn't change.

After:

queriesArray is moved to local state of TabbedSqlEditors, and is only reloaded during switching tabs or queries object is updated.

needs-review @mistercrunch

LGTM!


[es-dev-server] expose types

A couple of users have requested us to expose types for es-dev-server. I prefer not to hand write types. For a couple of projects I've been turning on strict type checking using js docs + .d.ts files which is working out pretty well.

it's time to work on that 👍

We still want to do this


Use a premade UI library

Could potentially lead to huge improvements in user experience and visuals
Saves time on custom styling
Styles are in the library's side, meaning that we don't need to duplicate code to keep the same styles across components

Added Material UI in #23.