disable public access to pikapods when cloudFlare reverse tunnel is active

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
hello
I am at great awe to this project, now sure how it escaped me until now...
I did a one-click install on pikapods and 2 more clicks and I had reverse tunnel setup with cloudflare (for free!).
Should I want to  disable access via xxx.pikapod.net  now no?  If so how do I accomplish that?
thanks a mil!
Tom
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.21.3
💻 Operating System and Arch
pikapods
🌐 Browser
Firefox
🐋 Docker Version
No response
🟩 NodeJS Version
No response

What do you mean by 'disable access'?

currently the app has access via cloudflare reverse tunnel and also via the public hostname assigned to it by pikapods (xxx.pikapod.net )
and it is accessible via both. I'd like to limit access only via cloudflare.
does that make sense?

That is not something we offer.
I don't see a need to limit access to just the cloudflare tunnel.
You probably want:
your.custom.domain -> cloudflare tunnel -> xxx.pikapod.net
Why not just CNAME your.custom.domain -> xxx.pikapod.net

It is not a problem in our side. You should ask Pikapod if you could remove the xxx.pikapod.net domain.

ok  i will close this ticket! thanks for the replies!


Feature: Send notifications upon community discussion activity

To help user-engagement we greatly need to increase the number of emails (notifications) we send to our users so they are included in the conversation and re-engaged to use the site.
This feature request would request the following...

Upon an new discussion being created in an community email all users of that community
Upon an comment/reply being made into that discussion, email all other participants of that community

A future consideration we will need to make after this feature is to help prevent considering these emails email spam incase we receive a lot of activity, a "simple" method programmatically to deal with this is only allow a certain maximum number of emails to be sent per-user per-type of email.  Eg: Only 3 per-day of community-related emails.  I would like/prefer if that is a "v2" future feature though.
Reference: This simplified logic is what I've used at two other social network platforms quite successfully in the past that requires very little programming/logic/thought to implement.  Please omit this from v1.

I would suggest that for comments/replies, only email previous participants of the thread, not the whole community, otherwise it may get quite spammy if there's a thread that only a few members are active in.

Needed for communities AND event discussions:

Ability to subscribe to discussions within a community
Push and email notifications for:

New messages in subscribed community
New messages in subscribed discussion
New reply to a comment you left

Adjust general subscription preferences in account settings (and perhaps a separate page for all subscriptions?)


Error page message "Request failed" instead of inline error from laravel

Hello,
I try to make this package functional, but I can not do it. I followed the instructions with composer create-project --prefer-dist cretueusebiu/laravel-nuxt.
I can connect, it works. I can also edit my information, great.
Sadly, for example on the profile page, when I try not to fill a data (for example, the name), I have an error screen.

In the reply json, I get the errors of Laravel well.
My question: why this screen appears instead of errors below the input? What did I do wrong?
And also, I can't run the npm run build, error : Error: ENOENT: no such file or directory, stat '/Users/.../miat/miath-app/dist/_nuxt'
It may be related, I do not know
I use Homestead.
Thank you for your help

Because of some changes the in recent versions of Nuxt, it now shows that error in the page instead bellow the input, but that's just when you are in dev mode.
You have now to wrap all request in a try/catch block.
Not sure about the last error though... Will investigate.

Hi @cretueusebiu
Thanks for the information. Indeed, it works with the catch.
By cons, I still have the problem with the npm run build.
Thank you !

Hi @cretueusebiu
Thanks for the information. Indeed, it works with the catch.
By cons, I still have the problem with the npm run build.
Thank you !

Which requests need to be in a try catch block? Any code samples please?

Any axios or form requests should be wrapped in a try/catch block.
try {
  this.form.post('/login')
} catch (e) {
}


Autostart Managers

Hey guys, I'm curating a list of autostart managers for phones so the user can directly be taken to the autostart screen for their respective oem. I currently have XIAOMI working but that's only because I personally own a XIAOMI device. I would encourage people to try out the library and definitely create a few PR's so we can get more oems working.
I just wanted to put this out here so users who do stumble upon this page can use this code in their app which may hopefully solve a few issues.
https://github.com/judemanutd/AutoStarter

Thanks @petrnalevka and good luck for your presentations.

Hello Jude, I did add a reference to AutoStarter here if that is fine https://dontkillmyapp.com/apidoc.. I think it will get a very good visibility so hopefully you will soon get some feedback on the missing vendors.. that would be great. I would use your library in my own projects as this is really helpful..

woaaah! This is super @petrnalevka thanks so much for that and I hope so too. Again great job maintaining this doc and the repo, fabulous job!!

Big thanks and crossing my fingers! Great job!


Updated README.md

Description
I added How to Contribute Section and  contributors profile images into main readme file and fixed issue: #9
Fixes #9
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] Documentation (non-breaking change that updates the documentation)

Checklist:

[x] I have read the Contribution Guidelines and Code of Conduct
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code

Could you move the contributing guide over to CONTRIBUTING.md and make a hyperlink that links over to the CONTRIBUTING.md file

Please check correction and tell me if you want further changes.

I made a few changes to both of the files. Is there anything that you want changed?

I made a few changes to both of the files. Is there anything that you want to add?

No it's OK.

Thanks!


Updated and fixed this Extension.

@sadrulhc @Cypher1 @AshokRajpurohit  Hello.
I make my own Chromium fork called Thorium > https://github.com/Alex313031/Thorium
I was wanting to modify the colors of some icons, but didn't know how to view the .icon files easily in the repo, but came across this extension after reading the README.md in //chromium/src/components/vector_icons/
However, I realized it no longer worked, so cloned it and worked on updating it to manifest V3, adding the proper urls for the new chromium websites, and making a logo for it. Also updated the apache license, added a readme.txt, and moved the .css, .js, and images to their own directories.
Am letting you know if you wanted to incorporate some/all of my changes. I would recommend at least updating the stuff in the manifest.json so that the extension works.
https://github.com/Alex313031/Chromium-Vector-Icons

Thanks. I'm no longer on the chrome team and was using this for generating icons for Chrome OS. I do appreciate the work (though I haven't reviewed it yet).
Cheers

@Cypher1 I like your PFP. BTW I make Thorium releases for Linux, Windows, Windows AVX2, MacOS, and Raspberry Pi. I'm also working on ThoriumOS, after honing my ChromiumOS project. > https://github.com/Alex313031/ChromiumOS

@Cypher1 Besides patches and small UI tweaks, the main point with Thorium and ThoriumOS is speed and being tip-o-tree. They are always built to trunk, and have compiler flags like AVX, AES, rust flags, and cflags and ldflags set to -O3 across the board, with some llvm tweaks and loop optimizations, on top of thinLTO and PGO. Im also going to look into using Polly by compiling my own LLVM checkout and pointing the Chromium toolchain to that, as well as looking into using fullLTO for some components like V8 and the content shell and webui.
When did you work on the chrome team, and what did you do, like what components did you work on?

Hey @Alex313031 I was on Crostini (now GuestOS iirc), working on the Cros-Adapter theme and internals. I'm<EMAIL_ADDRESS>if you wanted to look at my patches.

@Cypher1 Hey maybe you might know how to fix this or bypass it. Crostini will fail on first setup if the CPU has unmitigated CPU vulnerabilites. This happens on ChromiumOS, Cloudready, and ChromeOS Flex (new google branded cloudready). However, there are many Chromebooks with like sandy bridge or haswell chips, yet on them with stock ChromeOS crostini works fine. Is there something you can do when building CrOS or after the fact. Some people were able to get it to work by modifying the grub bootloader on partition 12/syslinux and adding full MDS mitigation, and some other people by adding a microcode payload to the initrd in the same grub file.
For example is there something I can modify in CrOS source? Or something I can change in the built image/installed OS to skip the checking. Or is ChromeOS using some sort of mitigation upstream specifically for these devices with older (skylake and older) chips?

@Cypher1 @sadrulhc @AshokRajpurohit I published it on the Web Store! > https://chrome.google.com/webstore/detail/chromium-vector-icon-pain/cnlndebkegcfnbiknohgneobakigplhf


Improved the WinGetUpdate script/function

Improved the WinGetUpdate with some checks and I did also make it possible for multiple aritechure to use it.
I'm hoping you find it educating and that it made your script better.
have a nice day

Fixed httpVersion issue nu also

Thank you, nice! Merged!


test5

There are 192 errors:

lib/layout/force-directed-layout.js, line 9 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 10 - CardinalPortPosition is defined but never used (no-unused-vars)
lib/layout/force-directed-layout.js, line 15 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 17 - Multiple spaces found before '='. (no-multi-spaces)
lib/layout/force-directed-layout.js, line 26 - Function 'layOutGraph' has a complexity of 9. (complexity)
lib/layout/force-directed-layout.js, line 27 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 28 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 29 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 30 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 31 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 32 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 33 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 33 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 34 - springForce was used before it was defined (no-use-before-define)
lib/layout/force-directed-layout.js, line 34 - Expected indentation of 6 characters. (indent)
lib/layout/force-directed-layout.js, line 35 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 36 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 37 - Expected indentation of 6 characters. (indent)
lib/layout/force-directed-layout.js, line 38 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 39 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 41 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 41 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 42 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 43 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 44 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 45 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 45 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 46 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 47 - Expected indentation of 6 characters. (indent)
lib/layout/force-directed-layout.js, line 48 - Expected indentation of 8 characters. (indent)
lib/layout/force-directed-layout.js, line 48 - A constructor name should not start with a lowercase letter. (new-cap)
lib/layout/force-directed-layout.js, line 48 - 'cardinalPortPosition' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 49 - Expected indentation of 6 characters. (indent)
lib/layout/force-directed-layout.js, line 50 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 51 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 52 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 52 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 53 - Expected indentation of 6 characters. (indent)
lib/layout/force-directed-layout.js, line 54 - Expected indentation of 8 characters. (indent)
lib/layout/force-directed-layout.js, line 54 - A constructor name should not start with a lowercase letter. (new-cap)
lib/layout/force-directed-layout.js, line 54 - 'cardinalPortPosition' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 55 - Expected indentation of 6 characters. (indent)
lib/layout/force-directed-layout.js, line 56 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 57 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 60 - Function 'springForce' has a complexity of 12. (complexity)
lib/layout/force-directed-layout.js, line 62 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 64 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 66 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 66 - edgeXLength was used before it was defined (no-use-before-define)
lib/layout/force-directed-layout.js, line 68 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 68 - edgeYLength was used before it was defined (no-use-before-define)
lib/layout/force-directed-layout.js, line 70 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 70 - edgeLength was used before it was defined (no-use-before-define)
lib/layout/force-directed-layout.js, line 72 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 72 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 73 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 74 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 75 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 77 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 78 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 79 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 81 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 82 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 83 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 84 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 85 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 87 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 89 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 91 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 93 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 95 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 96 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 96 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 97 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 97 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 98 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 99 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 99 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 100 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 100 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 101 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 102 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 104 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 104 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 105 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 106 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 107 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 108 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 110 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 111 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 112 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 113 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 114 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 114 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 115 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 116 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 117 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 119 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 120 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 120 - Missing space before value for key "x". (key-spacing)
lib/layout/force-directed-layout.js, line 121 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 121 - Missing space before value for key "y". (key-spacing)
lib/layout/force-directed-layout.js, line 123 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 124 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 125 - Missing space before value for key "x". (key-spacing)
lib/layout/force-directed-layout.js, line 125 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 125 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 126 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 126 - Missing space before value for key "y". (key-spacing)
lib/layout/force-directed-layout.js, line 128 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 129 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 130 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 131 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 132 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 135 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 136 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 137 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 145 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 152 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 152 - 'to' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 152 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 153 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 153 - 'from' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 153 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 154 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 155 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 155 - Expected literal to be on the right side of !=. (yoda)
lib/layout/force-directed-layout.js, line 155 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 155 - Expected '!==' and instead saw '!='. (eqeqeq)
lib/layout/force-directed-layout.js, line 155 - 'to' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 155 - 'from' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 156 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 157 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 157 - 'to' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 157 - 'from' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 158 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 158 - 'to' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 158 - 'from' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 159 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 160 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 160 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 161 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 162 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 165 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 166 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 167 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 172 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 172 - 'to' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 172 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 173 - 'from' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 173 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 173 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 174 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 175 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 175 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 175 - Expected literal to be on the right side of !=. (yoda)
lib/layout/force-directed-layout.js, line 175 - Expected '!==' and instead saw '!='. (eqeqeq)
lib/layout/force-directed-layout.js, line 175 - 'to' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 175 - 'from' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 176 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 176 - 'to' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 176 - 'from' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 177 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 178 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 181 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 182 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 183 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 188 - 'to' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 188 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 188 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 189 - 'from' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 189 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 189 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 190 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 191 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 191 - Expected literal to be on the right side of !=. (yoda)
lib/layout/force-directed-layout.js, line 191 - Infix operators must be spaced. (space-infix-ops)
lib/layout/force-directed-layout.js, line 191 - Expected '!==' and instead saw '!='. (eqeqeq)
lib/layout/force-directed-layout.js, line 191 - 'to' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 191 - 'from' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 192 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 192 - 'to' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 192 - 'from' is not defined. (no-undef)
lib/layout/force-directed-layout.js, line 193 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 194 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 197 - Expected indentation of 4 characters. (indent)
lib/layout/force-directed-layout.js, line 198 - Trailing spaces not allowed. (no-trailing-spaces)
lib/layout/force-directed-layout.js, line 199 - Expected indentation of 2 characters. (indent)
lib/layout/force-directed-layout.js, line 202 - Newline required at end of file but not found. (eol-last)
test/test-layout.js, line 43 - 'describe' is not defined. (no-undef)
test/test-layout.js, line 44 - 'it' is not defined. (no-undef)
test/test-layout.js, line 46 - A function with a name starting with an uppercase letter should only be used as a constructor. (new-cap)


better benchmark log

Actually adding the name of the benchmark to the log:
For example:
2022-08-12 13:27:56.886 TRACE main benchmark: End Benchmark: 930000 ns
2022-08-12 13:27:56.886 TRACE main benchmark: Read/Write Count (4, 0, 4, 0)
2022-08-12 13:27:56.968 TRACE main benchmark: Start Benchmark: one_fewer_deciding_failing ([])
2022-08-12 13:27:56.969 TRACE main benchmark: End Benchmark: 804000 ns
2022-08-12 13:27:56.969 TRACE main benchmark: Read/Write Count (0, 0, 0, 0)
2022-08-12 13:27:57.048 TRACE main benchmark: Start Benchmark: one_fewer_deciding_passing ([])

bot merge


storage: delete RowSets when drop table

Currently, when we call drop table, the RowSets don't get deleted. Considering we don't expect to support multi-thread DDL for now, we can simply change the process of drop table.
https://github.com/risinglightdb/risinglight/blob/53ccdf96f36267c4703386577eeeff1da18bdf13/src/storage/secondary/manifest.rs#L239-L250
When dropping table, we should also scan all RowSets belong to the table, and apply DeleteRowSet and DeleteDV changes. Therefore, we won't have problem recovering from a database where a table gets created then dropped.

hai, i can't find one struct that hold a mapping between table_id and rowset_id or dv_id, "scan all RowSets belong to the table", can only go through the storage directory to get the mapping?

You may first call self.version.pin_version to get a latest snapshot of the table, then get all rowsets belonging to this table, and finally delete them by notifying the vacuumer. No need to manually delete or iterate the folder by ourselves.
Another way to achieve is to modify the meaning of DropTable manifest entry. By calling DropTable, we can assume all rowsets belonging to that table are all deleted. Then we may need to change the recovery process and the vacuumer to ignore / delete rowsets if a table gets dropped.
Both approaches are okay. You may choose the one you want.


get encoder library from smaller repo, avoid silently failing if enco…

Gets encoder library from smaller repository
Avoid encoding tests silently fail if algorithm/encoding is not found
Points to new upstream encoder version with updated OID

Fixes #129
Fixes #130

Thanks for the fixes. But I fail to see a behavioural change in the code, so am I assuming right that it will fail in the same way if the OIDs between qsc-encoding lib and oqs-provider go out of sync again? Also, wouldn't it be more professional to have tests for this (both good and negative expected behaviour)?

It will not silently fail anymore. Good point with the test, I can add a negative test (show that the tests fail if a unknown encoding is set via env var).

Finally, is such duplication of OIDs between oqs-provider and qsc-encoder really necessary (or at the very least cannot be overruled at the API level)? It creates an undue dependency that we've just fallen into -- and can fall into again if I read Quantum-Safe-Collaboration/qsc-key-encoder@d7970ea correctly.

I'm not sure what's the best solution. How would you overrule at API level?
There needs to be a unique key to match. Another way the API supports is lookup by algorithm name. Here the issue is that the names are not really well defined, e.g, OQS name: SPHINCS+-SHAKE256-128s-robust and the name used in the reference implementation: sphincs-shake256-128s-robust. The names also don't identify the algorithm version. OIDs seem to define things more uniquely (ideally there will be a OID repo to pull from). The Falcon OID change was unrelated to key encoding (but signatures changed). Next time the key encoding could change which would require a new IETF draft revision.

How would you overrule at API level?

Client (oqs-provider) requests algorithm name (of qsc-encoder) w/o OID reference: It should be the responsibility of the client that algorithm name and OID match (or not, e.g., at an interop hackathon where people play with OIDs).

There needs to be a unique key to match.

Only when there are different encodings for the same algorithm name, right? Are there already different encoding for the same algorithm (name)? If it were coming to that, what about a SHA(256) over an (agreed upon) KAT to identify algs with the same name (but different versions/KATs)?

Added a commit with both.

Thanks. Then what am I doing wrong here (after the tests ran, using the resultant .crt files):
As expected:
> OPENSSL_MODULES=_build/lib LD_LIBRARY_PATH=.local/lib64 .local/bin/openssl x509 -in tmp/falcon1024.crt -text -noout -provider oqsprovider -provider default
[...]
        Subject: CN=test Server
        Subject Public Key Info:
            Public Key Algorithm: falcon1024
                falcon1024 public key:
                PQ key material:
[...]

Not quite expected:
> OPENSSL_MODULES=_build/lib LD_LIBRARY_PATH=.local/lib64 .local/bin/openssl x509 -in tmp/falcon512.crt -text -noout -provider oqsprovider -provider default
[...]
        Subject: CN=test Server
        Subject Public Key Info:
            Public Key Algorithm: falcon512
            Unable to load Public Key
808B1AEC977F0000:error:03000072:digital envelope routines:X509_PUBKEY_get0:decode error:crypto/x509/x_pubkey.c:463:
808B1AEC977F0000:error:03000072:digital envelope routines:X509_PUBKEY_get0:decode error:crypto/x509/x_pubkey.c:463:
        X509v3 extensions:
[...]

Trying with
OPENSSL_MODULES=_build/lib OQS_ENCODING_FALCON512=draft-uni-qsckeys-falcon-00/sk-pk OQS_ENCODING_FALCON512_ALGNAME=Falcon512 LD_LIBRARY_PATH=.local/lib64 .local/bin/openssl x509 -in tmp/falcon512.crt -text -noout -provider oqsprovider -provider default

yields the same result.
What did I do? Changed the Falcon512 OID. --> Is there still some dependency on it?

I could reproduce the error, however, I get an error even without changing the OID (Falcon1024 looks fine, Falcon512 shows the error). I will need to investigate why. There shouldn't be any OID dependency.

Not quite expected:
> OPENSSL_MODULES=_build/lib LD_LIBRARY_PATH=.local/lib64 .local/bin/openssl x509 -in tmp/falcon512.crt -text -noout -provider oqsprovider -provider default
[...]
        Subject: CN=test Server
        Subject Public Key Info:
            Public Key Algorithm: falcon512
            Unable to load Public Key
808B1AEC977F0000:error:03000072:digital envelope routines:X509_PUBKEY_get0:decode error:crypto/x509/x_pubkey.c:463:
808B1AEC977F0000:error:03000072:digital envelope routines:X509_PUBKEY_get0:decode error:crypto/x509/x_pubkey.c:463:
        X509v3 extensions:
[...]

Is this really the ouput after running the tests with changed Falcon512 OID (via env var)?
I tried it as well - first without using the external encoder, changing the Falcon512 OID via env var. Even here I get an error, but a slightly different one:
Subject: CN=test Server
        Subject Public Key Info:
            Public Key Algorithm: 1.3.99<IP_ADDRESS>
            Unable to load Public Key
4001FBEF01000000:error:03000072:digital envelope routines:X509_PUBKEY_get0:decode error:crypto/x509/x_pubkey.c:463:
4001FBEF01000000:error:03000072:digital envelope routines:X509_PUBKEY_get0:decode error:crypto/x509/x_pubkey.c:463:
        X509v3 extensions:

The "Public Key Algorithm" seems to have changed from 'falcon512' to the OID I set via env var. Shouldn't the name be unchanged?
Perhaps there are two different (maybe related) issues?
(1) when changing the OIDs -> applies not only when using the external encoder, and
(2) the error when parsing the falcon512, only happens when using the external encoder

I could reproduce the error, however, I get an error even without changing the OID (Falcon1024 looks fine, Falcon512 shows the error). I will need to investigate why. There shouldn't be any OID dependency.

I didn't set all env variables correctly when testing this. Trying again, it seems to all work ok, including changing the OID.
Testing Falcon with changed OIDs:
export OQS_ENCODING_FALCON512=draft-uni-qsckeys-falcon-00/sk-pk
export OQS_ENCODING_FALCON1024=draft-uni-qsckeys-falcon-00/sk-pk
export OQS_ENCODING_FALCON512_ALGNAME=Falcon512
export OQS_ENCODING_FALCON1024_ALGNAME=Falcon1024
export OQS_OID_FALCON512=1.3.9999.3.20
export OQS_OID_FALCON1024=1.3.9999.3.21

run scripts/runtests_encodings.sh

test Falcon1024

$ OPENSSL_MODULES=_build/lib LD_LIBRARY_PATH=.local/lib64 .local/bin/openssl x509 -in tmp/falcon1024.crt -text -noout -provider oqsprovider -provider default
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            52:1a:85:d8:b7:66:c8:0f:f6:86:07:4a:eb:24:6c:c9:55:94:8b:7d
        Signature Algorithm: falcon1024
        Issuer: CN=test CA
        Validity
            Not Before: Jan 23 08:00:00 2015 GMT
            Not After : Aug 23 09:00:00 2025 GMT
        Subject: CN=test Server
        Subject Public Key Info:
            Public Key Algorithm: falcon1024
                falcon1024 public key:
                PQ key material:
                    0a:70:9a:b5:96:8c:e7:e3:80:ae:9b:80:3c:21:c0:

test Falcon512

% OPENSSL_MODULES=_build/lib LD_LIBRARY_PATH=.local/lib64 .local/bin/openssl x509 -in tmp/falcon512.crt -text -noout -provider oqsprovider -provider default
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            13:b7:60:75:a4:0e:99:d8:a9:6f:07:61:5d:7d:e1:aa:05:9a:1f:15
        Signature Algorithm: falcon512
        Issuer: CN=test CA
        Validity
            Not Before: Jan 23 08:00:00 2015 GMT
            Not After : Aug 23 09:00:00 2025 GMT
        Subject: CN=test Server
        Subject Public Key Info:
            Public Key Algorithm: falcon512
                falcon512 public key:
                PQ key material:
                    09:b4:d2:f4:28:df:03:a1:42:3d:89:c9:a4:26:4c:

After unset OQS_OID_FALCON512, the above test fails as expected with a decoding error.

What did I do? Changed the Falcon512 OID. --> Is there still some dependency on it?

@baentsch looking at your test command a OQS_OID_FALCON512=... might be missing.

@baentsch looking at your test command a OQS_OID_FALCON512=... might be missing.

Nope. I changed generate.yml for the test...

Thanks for these fixes. I hope you can forgive me now being a "bit nervous" about the robustness of all this -- my question thus: Does https://github.com/IETF-Hackathon/pqc-certificates/pull/43 contain proper (proper in the sense of "in line with your RFC") certificates? Or should this data set be re-done after landing this PR to permit others to test "the right stuff"? Last question: Are you going to rebase the PR to remove the conflict?

Thanks for these fixes. I hope you can forgive me now being a "bit nervous" about the robustness of all this -- my question thus: Does IETF-Hackathon/pqc-certificates#43 contain proper (proper in the sense of "in line with your RFC") certificates? Or should this data set be re-done after landing this PR to permit others to test "the right stuff"?

The certs produced with the "hotfix" docker image are equivalent with the ones now in this PR. Thanks for being extra cautious!

Last question: Are you going to rebase the PR to remove the conflict?

Done.

The certs produced with the "hotfix" docker image are equivalent with the ones now in this PR.

Thanks for checking (and re-basing).


docs: readability improvements

Signed-off-by: Ryan Russell<EMAIL_ADDRESS>

Thanks @ryanrussell !


Consider removing "Task - " from terminal title after the introduction of icons in tabs

Right now this is what tasks look like in tabs:

Maybe since the icon will always be visible on the tab now we should remove it from the terminal's title.
The dropdown will still be available as a setting but we could expose a new dropdown-only title prefix or something so it still shows up there.

That makes sense to me. It's extra text that is taking up valuable real-estate

Do you think we should have Task - still show up in the dropdown or drop that too? It's also somewhat problematic there too and normally truncated:

I would still keep it in the dropdown. Maybe just for tasks not in a split pane though? I would have to see that's info I can correctly pass to the terminal.

I'll need to add something to IShellLaunchConfig first then

I just hardcoded the string since we want it basically everywhere else. Can make it more robust as needed.


cmd/go: "go run -compiler=gccgo main.go" doesn't work well with go1.19rc2

What version of Go are you using (go version)?

$ go version
go version go1.19rc2 linux/amd64

$ gccgo --version
gccgo (Debian 10.2.1-6) 10.2.1 20210110

Does this issue reproduce with the latest release?
Not for 1.18.x, just for 1.19rc2
What did you do?
go run -compiler=gccgo main.go

What did you expect to see?
Run well.
What did you see instead?
Errors:
../software/go/src/runtime/chan.go:21:2: cannot find package
../software/go/src/runtime/error.go:7:8: cannot find package
...

Running gccgo solely is also okay.

I can't recreate this.  Can you see when it stopped working?  Thanks.

As early as 1.19beta1.
1.18.4 is ok.
My gccgo version is 10, which is the newest version on debian.
My go env:
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/myname/.cache/go-build"
GOENV="/home/myname/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/myname/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/myname/go"
GOPRIVATE=""
GOPROXY=""
GOROOT="/home/myname/software/go"
GOSUMDB="on"
GOTMPDIR=""
GOTOOLDIR="/home/myname/software/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.4"
GCCGO="/usr/bin/gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3655385898=/tmp/go-build -gno-record-gcc-switches"

I can't recreate the problem with 1.19beta1 either.  I'm sorry, I don't know what is happening here.  Do you have GOROOT set in the environment?

No. I only set /home/myname/software/go/bin in PATH.

I just built the go1.19rc2 tag and the tip. The problem exists in the go1.19rc2 tag version but is fixed in tip.
I haven't time to bisect which revision fixed this problem.
If the tip will be merged into 1.19, then this issue may be closed now.


Request to add a new survey

Hi, thanks for your contributions to collating reasoning prompting methods!
Recently, we release a reasoning survey on natural language reasoning mainly from another perspective: the reasoning paradigm (end-to-end, forward, and backward).
Here are our survey and repository:
Nature Language Reasoning, A Survey
https://arxiv.org/pdf/2303.14725.pdf
https://github.com/FreedomIntelligence/ReasoningNLP
I believe our surveys and repositories can complementarily help people better understand the reasoning!

Great work, thanks!

Hi buddy, we have added your work.

thanks~


fix: change statusview item color to warn

I hope this style is properly added to all color schemes in future :sob: :smile:


rearranged logos into folders - Rearrenge logos #208

What issue is this referencing?
this pr fixes #208
Have you run the linting command in the README.md?

[x] yes! npm run lint-check

Have you taken a look at our contributing guidelines?

[x] yes!

My node version matches the one suggested when running nvm use?

[ ] yes!

@innith , Thanks for an excellent job! Appreciate 😄

I have checked pr. Please merge @MandyMeindersma.

@allcontributors add @innith for code

@allcontributors add @olimpiuus for bugs
Because of all the issues that you made yesterday 💪

@allcontributors add @olimpiuus for bugs


Add only_show_errors and no_color

Add only_show_errors and no_color to doc new features introduced by https://github.com/Azure/azure-cli/pull/12604.
We may need to update the help message of --only-show-errors accordingly.
> az version -h

    --only-show-errors : Only show errors, suppressing warnings.

Docs Build status updates of commit ce8fd11:
:clock10: Full build: the average full build time is 7 min(s) 22 sec(s), this is based on the last 544 build(s) for this repository.

Docs Build status updates of commit ce8fd11:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-configuration.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


add generic location to sourced-by-fp users

What does this pull request aim to achieve? 💯
Resolves #830
Thanks @cvaldez98 for helping me find this  - this should address the issue we found specifically with these FP-specific organizations:
TypeError: Cannot destructure property 'address' of 'location' as it is undefined.

You will need to re-run docker-compose exec backend-service npm run import-posts for success.

[ ] I have checked that no one else is working on similar changes.
[ ] I have read the latest README and understand the development workflow.
[ ] The name of this branch is: feature/<branch_name> (need to have cloned the repo not forked).
[ ] This branch is rebased/merged with the latest master.
[ ] There are no merge conflicts.
[ ] There are no console warnings and errors.
[ ] On the right hand side of this PR, I have linked the appropriate issue(s) under "Issues" and added a project progress under "Projects".

@idjevm @Naraujo13 @robinv85 @silenceway , whenever you have a few, please review this PR. It will unblock us on another issue- https://github.com/FightPandemics/FightPandemics/issues/825

Just tested, works as intended, this should hopefully unblock me from issue #825. Thanks @joshmorel

Thanks I'll go ahead and merge


SSH handshake err: ssh: handshake failed: EOF

The SSH to the macos109 vmware-iso machine could not proceed. I get this log:
2024/05/21 22:32:43 packer-plugin-vmware_v1.0.11_x5.0_darwin_amd64 plugin: 2024/05/21 22:32:43 [INFO] Attempting SSH connection to <IP_ADDRESS>:22...
2024/05/21 22:32:43 packer-plugin-vmware_v1.0.11_x5.0_darwin_amd64 plugin: 2024/05/21 22:32:43 [DEBUG] reconnecting to TCP connection for SSH
2024/05/21 22:32:43 packer-plugin-vmware_v1.0.11_x5.0_darwin_amd64 plugin: 2024/05/21 22:32:43 [DEBUG] handshaking with SSH
2024/05/21 22:32:43 packer-plugin-vmware_v1.0.11_x5.0_darwin_amd64 plugin: 2024/05/21 22:32:43 [DEBUG] SSH handshake err: ssh: handshake failed: EOF
2024/05/21 22:33:05 packer-plugin-vmware_v1.0.11_x5.0_darwin_amd64 plugin: 2024/05/21 22:33:05 [DEBUG] TCP connection to SSH ip/port failed: dial tcp <IP_ADDRESS>:22: i/o timeout

It works in EC but not in 10.9 nor 10.10. Please see here:
https://github.com/hashicorp/packer/issues/12994#issue-2315338366


docs(usage) updates patch doc to include patch-file

Codecov Report
Patch and project coverage have no change.

Comparison is base (7ded52d) 69.91% compared to head (0c19def) 69.91%.

:exclamation: Current head 0c19def differs from pull request most recent head 1f063a3. Consider uploading reports for the commit 1f063a3 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #38   +/-   ##
=======================================
  Coverage   69.91%   69.91%
=======================================
  Files          11       11
  Lines        1559     1559
=======================================
  Hits         1090     1090
  Misses        408      408
  Partials       61       61

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

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


Shape mismatch in train.py

Hi!
Running python train.py on the cub dataset, I'm dealing with this problem:
RuntimeError: output with shape [1, 227, 227] doesn't match the broadcast shape [3, 227, 227]
It occurs in these lines:
 for x, Y in dl_tr:
Y = Y.to(device)
opt.zero_grad()
Where's the problem and how can I solve it?

My belief is that there might be one (or more) images in CUB which have depth shape 1 instead of 3. The easiest solution would be to find those images (just write a script which simply opens the images and checks their size, and then finds those with size different to XxYx3) and rewrite them by simply copying the z channel 3 times.

Thank you, it actually worked


Package request: mouse-actions

Project description
mouse-actions allows to execute some commands from mouse events such as:

Clicks / wheel on the side / corners of the screen,
Or drawing shapes.

Metadata

homepage URL: https://github.com/jersou/mouse-actions
source URL: https://github.com/jersou/mouse-actions
license: mit
platforms: unix, linux, darwin

Hi, I don't know how to contribute to nixpkgs yet so I made a flake with a working default.nix. For anyone who is curious while I read up on submitting a package, here is what I'm doing:
{ lib, fetchFromGitHub, rustPlatform, pkg-config, virtualgl, xorg, libevdev }:
rustPlatform.buildRustPackage rec {
  pname = "mouse-actions";
  version = "v0.4.4";

  src = fetchFromGitHub {
    owner = "jersou";
    repo = pname;
    rev = version;
    hash = "sha256-02E4HrKIoBV3qZPVH6Tjz9Bv/mh5C8amO1Ilmd+YO5g=";
  };
  cargoHash = "sha256-GRClGC6+3J/YW5jVh7iAb2idD6/PycG854XbBIkfB/c=";
  buildInputs = [ xorg.libX11 xorg.libXi xorg.libXtst libevdev ];
  nativeBuildInputs = [ pkg-config virtualgl ];
  meta = with lib; {
    # TODO: better description
    description =
      "A way to execute some commands from mouse events, a mix between Easystroke and Comiz edge commands";
    homepage = "https://github.com/BurntSushi/ripgrep";
    # TODO: license
    license = licenses.unlicense;
    # TODO: how to add myself as a maintainer? (rgri)
    maintainers = [ ];
  };
}

Criticism is of course welcome.

Hi, I don't know how to contribute to nixpkgs yet so I made a flake with a working default.nix. For anyone who is curious while I read up on submitting a package, here is what I'm doing:
{ lib, fetchFromGitHub, rustPlatform, pkg-config, virtualgl, xorg, libevdev }:
rustPlatform.buildRustPackage rec {
  pname = "mouse-actions";
  version = "v0.4.4";

  src = fetchFromGitHub {
    owner = "jersou";
    repo = pname;
    rev = version;
    hash = "sha256-02E4HrKIoBV3qZPVH6Tjz9Bv/mh5C8amO1Ilmd+YO5g=";
  };
  cargoHash = "sha256-GRClGC6+3J/YW5jVh7iAb2idD6/PycG854XbBIkfB/c=";
  buildInputs = [ xorg.libX11 xorg.libXi xorg.libXtst libevdev ];
  nativeBuildInputs = [ pkg-config virtualgl ];
  meta = with lib; {
    # TODO: better description
    description =
      "A way to execute some commands from mouse events, a mix between Easystroke and Comiz edge commands";
    homepage = "https://github.com/BurntSushi/ripgrep";
    # TODO: license
    license = licenses.unlicense;
    # TODO: how to add myself as a maintainer? (rgri)
    maintainers = [ ];
  };
}

Criticism is of course welcome.

Use repo = "mouse-actions" since pname and repo are semantically different.
with regards to the meta info, you can use the upstream's meta info
and add yourself to the maintainer list and make a separate commit for that
here are the docs
then put your name on the meta.maintainers of that package.
you should be able to build the package if you added your name to the maintainer list
then on your pull request, the commits would include you adding yourself to the maintainers and the nix expression for the package
check the docs for more info and feel free to ask more questions

Thanks for the advice! I've tried to follow all of it- I've opened #265056.

Guys, question... in order to request the mouse-actions-gui should I create a new request?

I don't have the answer to that, maybe someone else can comment on the precedent. Besides that, @waldman do you have a workflow/config using mouse-actions that can be used to test functionality? I had to write some udev rules to make it work (it is almost ready for merge).

I use this functionality A LOT for tab management on my browsers:

Press 2 Button+Drag to the right => Next Tab (Ctrl+Tab)
Press 2 Button+Drag to the left => Previous Tab (Shift+Ctrl+Tab)
Press 2 Button+Drag down => Close Tab (Ctrl+w)
Press 2 Button+Drag up => Reload Tab (Ctrl+r)

Problem is that I believe on this app is almost impossible to craft the settings above on the configuration file without the GUI. (I used easystroke (https://github.com/thjaeger/easystroke) for this for almost 10 years but now it's deprecated in favor of mouse-actions. =/

can anyone comment about mouse-action and waylant compatibility ? the readme says it works in degraded mode but not sure how what that means

Closing with the merge of #265056.


Minimal example in help not working

When I do help optimizerFORCES
the following minimal example is displayed:
sdpvar x y p
solver = optimizerFORCES([x + y == p], x^2+y^2, options, p, {x,y})
solution = solver{5} % solve problem for p = 5

... but this is not working

Thanks. Issue has been fixed with commit c6841a5db98cc0bb338e7ccaf74f46eb785a1673.


Read/Write Global variables

How to read/save to global variables from inside on_message handler?!
as far as i know ,telegram python API has context.user_data['Var']=val

Basic python.
Define your variable outside a handler, then use global my_var inside of the handler and write to it like you normally would.

@ColinTheShark  yes i found out that ,lol .
thanks anyway


Feature: Async DataSource options for seeding

Is your feature request related to a problem? Please describe.
You cannot use an async data source to seed the database. The seeder needs a sync data source, not a promise. If you give a file that exports a promise of a data source, the seeder will not work and will throw an error saying that it cannot get or load the database options.
OptionsError: The database options could not be located/loaded.

Describe the solution you'd like
To be able to use a file that exports Promise<DataSource> for seeding, as this would allow DataSourceOptions to be fetched asynchronous. This would be more flexibility and scalability for seeding different environments.
Describe alternatives you've considered
As a workaround we have now hardcoded the DataSourceOptions for seeding locally.
Additional context

I have the same issue, but i have the options locally..
OptionsError: The database options could not be located/loaded.at Function.notFound .
I did the exact steps that are in the documentation.
this is my data-source.ts
OptionsError: The database options could not be located/loaded.
at Function.notFound
this is my dataSource file
import { DataSource, DataSourceOptions } from 'typeorm';
import { runSeeders, SeederOptions } from 'typeorm-extension';
import { User } from './registration/entities/user.entity';
(async () => {
const options: DataSourceOptions & SeederOptions = {
type: 'mysql',
host: 'localhost',
port: 3306,
username: 'root',
password: '123456',
database: 'ausentismo',
entities: [User],
seeds: ['./.seeder.ts'],
factories: ['./.factory.ts'],
};
const dataSource = new DataSource(options);
await dataSource.initialize();
await runSeeders(dataSource);
})();

I have the same problem!

If I understood you correctly, you want to return an asynchronous function that resolves to an initialized data-source?
export async function useDataSource() : DataSource {
    const options: DataSourceOptions & SeederOptions = {
    type: 'mysql',
    host: 'localhost',
    port: 3306,
    username: 'root',
    password: '123456',
    database: 'ausentismo',
    entities: [User],
    seeds: ['./.seeder.ts'],
    factories: ['./.factory.ts'],
    };

    const dataSource = new DataSource(options);
    await dataSource.initialize();

    return dataSource;
}

If you want to initialize the data source with a top level await, this would only be possible in an esm context.

@MartinDybdahlM @javiermatias @andrearruda82  ??

Sorry for the late reply... Thats exactly what i am trying to achieve. But when i try to seed using typeorm-extension seed:run -d <path to datasource> i get the error above

released in v3.1.0


can't get the latest version because the link doesn't do anything

Prerequisites

[x] Can you reproduce the problem with Debug -> Reload Without Extensions?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?
[x] Did you read the Troubleshooting guide?

For more information on how to write a good bug report read here
For more information on how to contribute read here
Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
Please include the OS and what version of the OS you're running.
Please include the version of Brackets. You can find it under Help -> About Brackets (Windows and Linux) or Brackets -> About Brackets (macOS)

This is still an issue on Firefox. I think it may be a CORS problem as getting the following warning:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://s3.amazonaws.com/files.brackets.io/updates/stable/en.json?_=1519830279540. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
Also, why isn't it just a hyperlink? Just looked at the HTML code and it's a bit sad that such a beautiful editor for making standards-compliant websites discards standards on its own site.


RegExp as filename patterns?

In some cases, it's not very convenient to use glob syntax for filename patterns and other options are not enough. Maybe, makes sense to allow to use regexp syntax for that?

Could you share the examples that only can do with regex syntax not the glob syntax? I am fine with glob syntax for my current needs.


RPi-#61. Controller parse control.json

What is this PR for?
Make controller enable to parse LED.json, OF.json, and light LED and OF.
What type of PR is it?
[Feature]
Todos

[Debug] -   Task

What is the Github issue?
Resolve https://github.com/NTUEELightDance/LightDance-RPi/issues/61
How should this be tested?
Currently none
Screenshots (if appropriate)
None
Questions:

Do the license files need updating? No
Are there breaking changes for older versions? Yes Yes Yes
Does this need new documentation? Yes

@Kenchu123 Don't merge this pr yet.

RPi-#61. Controller parse control.json


Fix: WindowManager.add when assign is string

I think WindowManager.add() is not working as intended when given a string to the assign argument.
Sorry by advance if y misunderstood how it is supposed to work.

getattr(self.layout, assign) actually does the same thing, since Layout's getattr is overridden to allow finding slots:
https://github.com/bczsalba/pytermgui/blob/eb2350ce93313291c4c4a25c475ff4e504c831ba/pytermgui/window_manager/layouts.py#L381-L391
Thank you for the effort though!


Migration to .NET 7

Notable Changes

Migrates the projects to .NET 7
Updates view models to use MVVM Community toolkit source generators and commands
Migration from MessagingCenter to the MVVM Toolkit Messenger
Package updates to the latest
Small bugfixes

@michaelstonis  can you check the build errors

@michaelstonis  looks like just unit tests now ;)

yea, it would probably help if I pulled in those changes. Should be squared away now.


Add failure summary report to spec_reporter.

@os97673
Scrolling through hundreds -- or in our case thousands -- of test results to locate the failure message for one or a handful of tests is rather painful.  This adds an error summary report to the end of the spec reporter, but before the final test summary is printed.  It omits skipped tests.
You can view the resulting output of this PR by running bundle exec rake gallery, or:
  1) Failure: MinitestReportersTest::BadTest#test_a [minitest-reporters/test/gallery/bad_test.rb:6]:
        Expected: 1
          Actual: 2

  2) Failure: MinitestReportersTest::BadTest#test_b [minitest-reporters/test/gallery/bad_test.rb:14]:
        --- expected
        +++ actual
        @@ -1,2 +1,2 @@
         "ab
        -c"
        +d"

  3) Error: MinitestReportersTest::BadTest#test_boom:
        RuntimeError: A random exception
            minitest-reporters/test/gallery/bad_test.rb:18:in `test_boom'

Finished in 0.01229s
6 tests, 5 assertions, 2 failures, 1 errors, 1 skips

You might want to check out #133. I've added a flag to only print out failed tests.

as discussed in #133 we need to create a new reporter, thus I'm closing the PR


[FancyZones] Zone Editor snapping / Zone Equalizing

📝 Provide a description of the new feature
I feel like using the grid option with custom zone layouts ends up a bit frustrating if you want to split a zone into 2 halves.
So I suggest adding a slight mouse snap to the center of the zone's edge.
In addition, the dragging gesture in the editor could have a "balance" option next to the "merge" option where all the selected zones are set to the same size.
It seems handy for example when you need 3 equally-sized zones in a row/column.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

@KatzenGit
those improvements are needed, we are tracking them in https://github.com/microsoft/PowerToys/issues/7875
Feel free to add you comments there.
Thanks.


ImportError: cannot import name ChainMap

Hi Sir,
I tried installing the project according to the readme steps, But i am getting ImportError when I run the command "python manage.py runserver", I tried using docker installation but I am getting the same ImportError, the stack trace is as given below:
ExplainToMe$ python manage.py runserver
Traceback (most recent call last):
File "manage.py", line 6, in
app = create_app()
File "/home/swathimithran/ExplainToMe/ExplainToMe/app.py", line 46, in create_app
f(app)
File "/home/swathimithran/ExplainToMe/ExplainToMe/app.py", line 27, in register_blueprints
from . views import root, api
File "/home/swathimithran/ExplainToMe/ExplainToMe/views/init.py", line 2, in
from . root import root
File "/home/swathimithran/ExplainToMe/ExplainToMe/views/root.py", line 4, in
from collections import ChainMap
ImportError: cannot import name ChainMap

Thanks for reporting this, I've recently ported the code to Python 3 by default and Chainmap was moved out of stdlib in Python 3. I'll patch this issue, but if you want to run this on Python 2, you need to install Chainmap using.
pip install chainmap

And wrap the code that imports chainmap in a try..except
try:
     from collections import ChainMap
except ImportError:
     from chainmap import ChainMap

https://github.com/jjangsangy/ExplainToMe/commit/4758d02baa685440084bb3d3b050c35ecce5123c: The fix has been implemented and it's live.


Very high cpu requirement for development

In my case, the dev application is taking up 33% cpu approx which is extraordinarily high! Has anyone else seen this issue? How can I find out what's going on here?

I've noticed this as well. Might be that webpack is doing some unnecessary work. Not sure at the moment.

Duplicate of https://github.com/chentsulin/electron-react-boilerplate/issues/1110. Let's merge this into that discussion.

This issue is #1110. Kindly update the number of original issue here.

Fixed


fleetd: support operators in metadata

This PR allows users to define metadata in units, such as "ram=1024". Precisely we can define the operator in the [X-Fleet] section in a unit as below:
[X-Fleet]
MachineMetadata=ram>=1024

Supported operators are "<=", ">=", "!=", "==", "<", ">".
This PR also contains more checks in fleetctl, more test cases in unit tests, and a new functional test.
Originally written by @wuqixuan.
Fixes https://github.com/coreos/fleet/issues/1143
Supersedes https://github.com/coreos/fleet/pull/1294

Updated the functional test TestMetadataOperator.

Now the test checks not only success cases, but also failure cases.
Fixed a broken unit generation code in runMetaOp().
Fixed a wrong cleanup command, from "fleetctl stop" to "fleetctl destroy".
Removed unnecessary template index in the sample unit file metadata-op.service.


Revise devshell design in light of https://zimbatm.com/notes/1000-instances-of-nixpkgs

I hope we can kick off a discussion on how the design of the beloved numtide/devshell could be revised in light of https://zimbatm.com/notes/1000-instances-of-nixpkgs which I very much favor.
Let's have a discussion first and then maybe gather momentum for an implementation?

Generally, I see 3 ways to avoid instances of nixpkgs with flakes:
Default option
For packages, use nixpkgs.legacyPackages.${system} in your flake and rely on the parent flake setting the "follows" to use the same instance of nixpkgs. This is the simplest approach. One downside is that you can't pass your own instance of nixpkgs around anymore. If all you did previously was extend nixpkgs with overlays that's fine. But if you patched nixpkgs or set config options such as allowUnfree (side note; we should create a nixpkgs-unfree repo that mirrors nixpkgs but with allowUnfree set to true), this approach is limiting. Nonetheless, I think this should be the default approach.
Inputs constructor
For devshell, mkShell is actually a constructor. As a user, I think the expectation is that you can use your own inputs and overrides. Especially with devshell.toml, a current limitation is that only inputs from nixpkgs can be used. What we want is to somehow inject all the packages from all the inputs for the current system.
inputs@{ self, nixpkgs, treefmt, devshell }:
{
  devShell.x86_64-linux = devshell.mkShell2
    {
      packages = { // devshell could propose devshell.lib.packageFromInputs to make that shorter.
        nixpkgs = nixpkgs.legacyPackages.${system};
        treefmt = treefmt.packages.${system};
      };
      configuration = {
        packages = [
          # now packages take a prefix, compatible with devshell.toml
          "treefmt.treefmt"
          "nixpkgs.hello"
        ];
     };
  };
}

Also export an overlay
As the last resort, a flake could also export an overlay of itself.


OpeningHoursDay contains two properties for weekday

It is a bit confusing that OpeningHoursDay model contains both a property WeekDay and Weekday.
@{
    OpeningHoursModel openingHours = Model.Content.GetOpeningHours();

    var upcomingDays = openingHours.GetUpcomingDays(7);

Åbningstider

    foreach (var day in upcomingDays)
    {
<EMAIL_ADDRESS>/>
        @day.WeekDay

        @day.Weekday

    }
}

It seems that WeekDay return the same as WeekDayName - name of the actually weekday name, while Weekday returns Our.Umbraco.OpeningHours.Model.Items.OpeningHoursWeekdayItem

WeekDay is actually an enum, but I can see the possible confusion between the two names. I have pushed a commit that changes WeekDay to DayOfWeek ;)


Add side navigation

Extra changes made to original sidenav branch:

Replaced <a> with <button class="iui-button"> and followed accessibility guidelines.
Border removed from top, left, bottom (because the sidenav will be against the edge of the viewport and/or up against the header component)
Overflow fixes
New Icon classes

This expander looks weird to me..

Maybe we should put it down?

Or we should not even have it cause it is not present in standards..

Do we want to handle submenus now?

This expander looks weird to me..

Maybe we should put it down?

Or we should not even have it cause it is not present in standards..

As with most of these decisions there's a story tied to it. 😅
The original design had the expand / collapse arrow at the top of the side navigation.  I tried using the app icon + 3 lines within the header to expand / collapse but the UX team ran some labs and it was not easily discovered by the user.  I didn't realize our standards were still showing this entry point, I thought we had updated the docs since then. 😬
So I tried proposing we move it to the bottom & asked the iTwin Hub team to implement it like this.  It has not undergone any user tests, so I'm unsure which way to go.  I might take a look at the code and see if I can set it up in a way where we could easily place the expander at the top OR bottom.  Eventually we will want a set standard.  I'll reach out to UX for some help on that.

UPDATE: Just checked, no code change needed to move the expander to the bottom.

Yeah, I moved some code around to make that possible but it's still not perfect. Borders break if there are multiple buttons in the bottom section

Yeah, I moved some code around to make that possible but it's still not perfect. Borders break if there are multiple buttons in the bottom section

I've found a fix for the border issue.

Do we want to handle submenus now?

We do need to add submenus, but I fear that would hold up the PR much longer.  I'll be honest, I have not thought ahead on how we might accomplish that either, particularly the part where the active tab's right border gets knocked out.


Support container types for concrete classes

(Fine to enforce that they have a no-arg constructor if needed)
The use case is that a typical requirement for a type container is enforcing something close to "locality" for the aliases/case classes to the package being used, and forcing the class to be an interface is too restrictive (I think! even with defaults)
So eg
import path.UsingThisLikeNamespaceTypes.Stack;

@TypeContainer(suffix="Types", "unsuffix"="")
class UsingThisLikeNamespace {
   @TypeAlias interface Stack extends LinkedList<Integer> {}

   // Then lots of static or non-static methods that use Stack or case classes or whatever
}

Eg see the State monad example

In the generated class, the Aliases/Cases, etc. would still be "static" classes, right? i.e. you don't need to instantiate the container class.

I don't know what else I want to do in/with the container class (ie it's not just a container, it's also the namespace for all my logic - that's important because that's what lets me keep the case classes and type aliases "local" in a natural way), so I don't want to restrict what I do with it, all I know is that I want to declare Halva artefacts inside it and have them appear in (eg) MyClassName+Types
So eg two examples:

I just want a central "library" class containing all my types - in which case an interface is fine
Eg the State monad example - the type alias is a tiny part of that

So, in the monad example, would the StateExample container extend StateExample? Maybe it should be an option in @TypeContainer.

The way I'd like to write the actual code looks something like this:
package oh.hai;

import oh.hai.ExampleTypes.Stack;
import static oh.hai.ExampleTypes.Stack.Stack;
import oh.hai.ExampleTypes.Point;
import static oh.hai.ExampleTypes.Point.Point;
//...

@TypeContainer(suffix="Types", unsuffix="")
public class Example {
   @TypeAlias interface Stack extends ConsList<Stack> {}
   @CaseClass interface Point { double x(); double y(); }

   // Business logic

   int main(String[] args) {
      // Eg
      final Stack s = Stack(List(1, 2, 3));
      final Point p = Point(1.0, 1.0);
   }
}

So although the code is going into a different class (ExampleTypes vs Example), as a developer everything looks like it's local etc.

In your example above, the generated class would be ExampleTypes. So, should all the methods, etc. in Example be copied into ExampleTypes or should ExampleTypes extend Example? What's clumsy is that main() expects the generated types to exist but they won't exist until processing. After processing, main() would have to Reference (or have a static import for) ExampleTypes.Stack or something similar.

Hmm interesting, having used now TypeContainer a bit more I see what you mean.
Seems like there are two ways of doing it, neither of which is great:

you'd be forced to create your own ExampleTypes_, containing the "local" data model, and then Example with the logic, importing the generated ExampleTypes
or you write your case classes etc at the top of Example, hit rebuild, and then go write the logic, which is kinda ugly but not a million miles different from creating the data model in a separate file and hitting rebuild?

I feel like some people are going to prefer 1 and some 2?
(In the latter case, ExampleTypes doesn't inherit from Example, it's linked to Example only by the common name stem)


Fix Linux build

Seems like  Clang 9.0.1 moved its warnings to the stderr making the Linux build fail because of Xerces warnings. This change adds -Wno-memset-transposed-args to the Xerces flags

/azp run


feat: move providers to wallet state

Description
This moves the provider-setting logic from the silo'd src/context/WalletProvider/<WalletName>/components/Connect.tsx components, to the memoized wallet provider context. Since the provider is now consumed from a single source of truth, this makes sure event handlers are added to one unique instance, both on wallet pairing (wallet connect screen) and load (app refresh)

[x] Wallet context as a single source of provider truth
[x] Types
[x] Programmatic wallet provider detection based on local wallet type / selected wallet connect option

Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes https://github.com/shapeshift/web/issues/2585
Risk
High. Affected areas are:

Wallet pairing (after app load, and after disconnecting a wallet than reconnecting the same or another wallet)
Wallet detection (MetaMask lookalikes should be properly detected, with prioritization and multiple wallets error-handling still working)
Wallet features (address getting, broadcast, fees estimate, network detection and switch)
Wallet refresh on load
Wallet disconnected state

Testing
Engineering

Regression testing according to the criteria above
Event handlers should be firing while reloading any MetaMask-like wallet as well as WalletConnect. This can be tested by switching chains/accounts, which should disconnect the app
Event handlers should still work when connecting a wallet through the wallet connect modal vs. reloading the app

Operations

Ensure all wallet features still work
Regression test that switching from a MetaMask-like or WalletConnect to native/KK/Portis still works

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #2586   👈

PR #2588

This comment was auto-generated by Graphite.

Moving to draft as event listeners will also need to be handled at wallet context level, or we won't be able to properly listen to them on loaded wallets on app reload


spec index is missing a link to the change log

It looks like "change log" in "Updates to this specification are noted in the change log." is not hyperlinked to the actual change log

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2690ef79-7c15-86fa-58bb-500e4f5a9b94
Version Independent ID: 12a633e1-c7b9-87ad-fd11-1bc4d12bcbb2
Content: OpenType specification - Typography
Content Source: typographydocs/opentype/spec/index.md
Product: typography
GitHub Login: @PeterCon
Microsoft Alias: alib

Fixed for OT 1.8.4


Android Studio Error Creating Project

Steps to Reproduce

Install Flutter in C:/src/flutter
Install Android Studio Flutter depend.
Setup up Env
Open Android Studio -> Start New Project -> ...ERROR

Logs

flutter doctor

By the way, it works if I install the app in "C" drive. Can anyone explain why is that, I setup ENV so it should work for other folders too (e.g Desktop)


chore(richtext-lexical): lazy import React components to prevent client-only code from leaking into the server

Description
Fixes #4085

[X] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[X] Chore (non-breaking change which does not add functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Change to the templates directory (does not affect core functionality)
[ ] Change to the examples directory (does not affect core functionality)
[ ] This change requires a documentation update

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

TODO:

[ ] Subpath exports. Export Clientside stuff by default and put utilities in utilities.ts, or export serverside stuff-only by default and put clientside stuff in components.ts?
[ ] Check once again if all utilities can now be imported on the server without weird errors


[repo] Create an enclave-cc repository

As there seems to be an agreement on the enclave-cc approach, I propose that we create a new repo called enclave-cc for hosting the components and documents related to it.
At first, copies of the IC shim and rune will be hosted there, allowing us to make progress towards an initial PoC.
A more formal design proposal and documentation would eventually also be hosted in that repo.

cc @mythi

Looks good to me. It is a best place to hold all development efforts.

Repo is created now: https://github.com/confidential-containers/enclave-cc
Thanks for the feedback.


Problem with Unicode in Terminal of Visual Studio Code

In Visual Studio 1.89.1 on Windows 21H1 Build 19043.1526 this file is wrong shown in terminal:
https://gist.githubusercontent.com/PhMajerus/3467813988c0bbff9de0e67e538d0206/raw/5539303c172ca0df82e1e87f3b5015d97ac7ca32/Demo screen.txt
For it is needed to install Cascadia Code 2404.23:
https://github.com/microsoft/cascadia-code/releases/tag/v2404.23
(on that side you can also see a screenhsot, where the "Demo screen.txt" file is displayed corrent)
Then go in Visual Studio Code on the left bottom to the "Manage" icon and select "settings".
Under ""Text Editor" -> "Font" change Font Family from "Consolas, 'Courier New', monospace" to "Cascadia Mono".
Then you can see the right font displays some parts right. But at the end it looks wrong.

In Windows-Terminal 1.19.11213.0 with used Cascadia Mono 2404.23, then it shows all right.
And in the terminal of Ubuntu, it shows it right, too, if Cascadia Mono 2404.23 is selected as font.

does changing terminal.integrated.gpuAcceleration help?

No, don't help.
I have tested with "auto", "on", "off" and "canvas".
With "off" the font is widen a little but. But all other is exactly the same.

What it looks like on macOS:

This means that it's an issue with Conpty advancing the cursor the wrong amount. So you'll have to wait for the conpty component to be updated in Windows 11 to see this fixed.

This is likely a problem with the conpty backend we use. You can try to reproduce the problem in Windows Terminal and if it happens there as well, report to microsoft/terminal.
If you cannot reproduce in Windows Terminal, chances are it's fixed in a later version of Windows. You can read more about how we consume conpty here.
/label terminal terminal-conpty windows


Multiple services

Consider this scenario
passetto adds a postgresql service. But the user (nammayatri) may add their own postgresql service. Can the two DB coexist?
What we can do
Should we adjust the module API to accomodate for this? For eg., instead of:
services.postgresql.enable = true;

do we instead do:
services.postgresql."some-name".enable = true;

And consistently use this API for all services?
Concrete goal
This should work in nammayatri which has its own postgresql, as well as a postgres db used for passeto.

This makes sense! I think we can already do this if have a different dataDir and serve on a different port.

It would look more like this,
services.postgresql = lib.mkOption {
  type = types.submodule ({name, ...}: {
    options = {
      dataDir = lib.mkOption {
        type = types.str;
        default = "./data/${name}";
      };
    }
  });
}

Note how dataDir's default is determined from the attrset key (name).


Feat: Add Blocks view on Milestone payload

Description of change

[x] Add backend support to fetch from chronicle API for milestone data
[x] Test that the backend chronicle fetch works (needs updated Chronicle instance)
[x] Tabify the milestone page (check/reuse TabbedSection that introduced for Address page)
[x] Add one more tab with the list of Blocks (check figma below)
[x] Adapt the designs of Block pages (all versions) to figma designs

Resolves https://github.com/iotaledger/explorer/issues/495
Type of change

Enhancement (a non-breaking change which adds functionality)

Change checklist

[] My code follows the contribution guidelines for 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
[] 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

Removed the advanced button toggle on Block pages (there is only rarely rendered ReceiptPayload left that uses it, which was hardcoded to "true" from Block pages side).
For the nonce, i'm not sure about moving it to metadata as technically is not part of the blockMetadata but it's on the Block itself, so i left it where it is.


Avoid redundant metadata validation on linking changes

Background:
We added a change  https://github.com/ebi-ait/ingest-core/pull/101 is causing a lot of validation messages in the queue and also causing linking during importing to be very slow. This change is to set back the metadata to draft for every linking change so that the submission will go back to Draft and let the user revalidate the graph.
The issue with that change:
If a process is linked 3 times,  to file, to protocol and to the biomaterial, the process metadata JSON will be validated 3 times as well when its JSON hasn't even changed. This is causing 2 redundant validation. And if there are 70k+ linking, this is going to do 70k * no. of entities (let's say 2-3) draft events to go to the validation queue. These are a lot of messages which go to the metadata validation queue and validator and lots of requests to the core and state tracker for the validating and valid state transitions.
The following submission took 10hrs~ to finish linking:
{
"expectedBiomaterials": 2086,
"expectedProcesses": 7237,
"expectedFiles": 6397,
"expectedProtocols": 36,
"expectedProjects": 1,
"actualLinks": 76295,
"expectedLinks": 76295,
"totalCount": 15757,
"submissionDate": "2022-03-30T11:45:22.610Z",
"updateDate": "2022-03-30T21:56:53.867Z",
...
"_links": {
"self": {
"href": "https://api.ingest.archive.data.humancellatlas.org/submissionManifests/624442d2b06b223527d3df68"
}
...

Diagram showing metadata redundant validation
sequenceDiagram

  participant Broker
  participant Core
  participant State as State Tracker
  participant Validator

  Broker-->>Core: creates metadata 1
  Core-->>Core: creates metadata with initial validationState DRAFT
  Core-->>State: sends message that there is new metadata in DRAFT

  Core-->>Validator: sends message for metadata 1
  Validator-->Core: sets metadata 1 validationState to VALIDATING
  Core-->>State: sends a message that a metadata 1 is set to VALIDATING

  Validator-->>Validator: validates metadata 1 json against json schema and ontology api
  Validator-->Core: sets metadata 1 validationState as VALID or INVALID + validation error
  Core-->>State: sends a message that a metadata 1 is set to VALID/INVALID

  State-->>State: checks if submission should be set to DRAFT/VALIDATING/VALID/INVALID
  State-->>Core: sets submission state to DRAFT/VALIDATING/VALID/INVALID
 PUT /commitValidating or
 PUT /commitValid ...

  Broker-->>Core: links metadata 1 to metadata 2
  Core-->>Core: sets both to DRAFT
  Core-->>Validator: sends message for metadata 1 and metadata 2

  Validator-->>Validator: validates metadata 1 json against json schema and ontology api
  Validator-->Core: sets metadata 1 validationState as VALID or INVALID + validation error
  Core-->>State: sends a message that a metadata 1 is set to VALID/INVALID

  State-->>State: checks if submission should be set to DRAFT/VALIDATING/VALID/INVALID
  State-->>Core: sets submission state to DRAFT/VALIDATING/VALID/INVALID
 PUT /commitValidating or
 PUT /commitValid ...

  Validator-->>Validator: validates metadata 2 json against json schema and ontology api
  Validator-->Core: sets metadata 2 validationState as VALID or INVALID + validation error
  Core-->>State: sends a message that a metadata 2 is set to VALID/INVALID

  State-->>State: checks if submission should be set to DRAFT/VALIDATING/VALID/INVALID
  State-->>Core: sets submission state to DRAFT/VALIDATING/VALID/INVALID
 PUT /commitValidating or
 PUT /commitValid ...

Solution:
Set the metadata back to draft iff the submission state is Graph Valid

Testing is failing but uncertain if this is due to issues with State Tracker or with issues with the code. Alegria and Jacob to pair on this.

This will actually fix https://github.com/ebi-ait/dcp-ingest-central/issues/633 because it will no longer set the metadata entity to Draft if its submission is not Graph Valid. The first submission will always be in Exported (or state after Submitted).

This is now in staging and ready for testing if @ami-day has time

@aaclan-ebi  - what needs testing here? please specify.

Tested in dev and it took only 46 minutes to import 70k links compared to ~5hrs before
"submissionDate": "2022-04-01T12:06:09.416Z",
"updateDate": "2022-04-01T12:52:00.703Z",

@aaclan-ebi does this still need a wrangler?

No, this one doesn't need a wrangler. it's a non-functional change.  But it's linked to the dcp-633 that one needs wrangler testing.


searching should hide from the map view

Right now, searching only filters down in the list view. This should filter down for the map as well.

resolved with https://github.com/bluewhale-org/withcalories/commit/cfeab50fd656e6bcca065e1f5850b261b381e2f9


Fix unwanted LBP notifications when a contact host is down (JAVA-613).

Other then my comment about the unit test, this looks good to me :+1:

Yes, when the driver is initializing, the contact points are tried in order, and once a connection succeeds, the remaining hosts are passed as ADDED (rationale: we don't want to waste time trying all the contact points, but if we tried some of them and know they are down, it's better to mark them down right now rather than retrying them later in the init process).
The test does rely on the iteration order of {{Metadata.hosts}}. This depends on the hashcodes of the hosts, which are computed from their IP addresses. I had assumed that this wouldn't change across environments but now I realize that what can change are the IPs, depending on {{CCMBridge.IP_PREFIX}}.
I agree with your commit and I would have done it the same way, but as you noted JAVA-618 break this again. So I guess the only option left is to retry.

Implemented the retry in the test.

I like the idea of the retry w/ JAVA-618 being a future possibility, and it looks good to me!   I think 10 attempts should be sufficient, there's a theoretical ~1/1000 (2^-10) chance of the test failing, if that ever gives us problems we could bump up maxTries. :+1:

Merged manually to 2.0.9_fixes (it doesn't show as merged here because that was not the original target).


plot_label with facet_wrap

Add the ability to specify a facet variable in the plot_label function so that the labels only show up on certain facets.

Duplicate of #157


GKEv2 UI, Doesn't show node pools for registered clusters

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Register a GKE cluster with node pools
Go to edit cluster:

I don't see  any node pools
Result:
I can see node pools in API:

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.5-6f71d4c7346c63a60c671d59185e1595fe826ac7-head
Installation option (single install/HA):

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

(paste the output here)

Docker version (use docker version):

(paste the output here)

I think the problem is in the UI merging the upstream and downstream attributes, specifically here: https://github.com/rancher/ui/blob/cfd4dfa03f6a6bef36a404a85df14501c4513fe3/app/models/cluster.js#L1024-L1030
The field is called nodePools for GKE, not nodeGroups.


Mysql error in upgrading PS<IP_ADDRESS> to PS1.7.5 using 1-click, and cannot display admin/module page.

The following 3 mysql errors displayed in window, when upgrading PS<IP_ADDRESS> to PS1.7.5 using 1-click, and cannot display admin/module page.
[WARNING] SQL <IP_ADDRESS> 1060 in ALTER TABLE ps_supply_order_receipt_history CHANGE employee_firstname employee_firstname VARCHAR(255) DEFAULT ”, CHANGE employee_lastname employee_firstname VARCHAR(255) DEFAULT ”: Duplicate column name ’employee_firstname’
[WARNING] SQL <IP_ADDRESS> 1060 in ALTER TABLE ps_product CHANGE reference supplier_reference varchar(64) DEFAULT NULL, CHANGE supplier_reference supplier_reference varchar(64) DEFAULT NULL: Duplicate column name ‘supplier_reference’
[WARNING] SQL <IP_ADDRESS> 1060 in ALTER TABLE ps_stock_available ADD location VARCHAR(255) NOT NULL DEFAULT ” AFTER out_of_stock: Duplicate column name ‘location’
It says Upgrade has been successful.
But I cannot display admin/module page (debug 'off') only an error is displayed.
When I set debug 'on', the actual listing of the admin/module shows up, perfectly OK. But again in setting dubug to 'off' the admin/module list does not show up, only error below shows up.
Oops! An Error Occurred
The server returned a “500 Internal Server Error”.
Something is broken. Please let us know what..

Hi @gray-b,
The warnings are not a serious problem. A fix is available in #11814
about your issue, it could be a cache issue.
Could you please try to clear cache manually by deleting all the folder into var/cache (prod & dev).
If, it is still NOK, thanks to remove the 1-click upgrade module.
Thanks !

If I remove the 1-click upgrade module, how can I do an upgrade (apart  from a manual one). Or do you want me to reinstall the 1-click upgrade module ?

@gray-b, in your issue you just said that the upgrade has been successful, so the auto-upgrade is completed & now you have the last version <IP_ADDRESS>, so you can remove the 1-click upgrade module.

Sorry what I meant to say was how do I then do an upgrade in the future.

@gray-b, in the future, you need to install the latest version of the 1-click upgrade module.
Thanks!


Add --progress-images to CLI

Uses similar code to the web GUI for saving intermediate images.
Fixes #75
Fixes #99
Fixes #154
Fixes #224

Are you sure this fixes #75?

I did some testing on this. Here are my notes.

You need to rebase this on top of the development changes. A lot of refactoring was done. So you'll need to update your code.
I did step 1 and realized that the Seed value for saving the images being returned is None. You need to fix that.
Even saving an image per step, I did not see any drastic performance loss. It's pretty fast.

But I did notice something.
I know for a fact that k_euler_a at 20 steps gives a totally different image when compared to k_euler_a at 50 steps for the same seed. I presumed when I save the intermediate images, I will see the transitioning through all these images. But that is not what I see. I see a noisy version of the final output right until the final step when it is a pretty clean version. Irrespective of what step count I use or what sampler I use.
Any reason why that is the case? Why isn't k_euler_a generating the different output as it should at different steps?

@kevinschaul, thank you so much for contributing this nice feature. As my collaborators have mentioned, it would be best if you could rebase this PR against the development branch. The code is evolving quickly, and over time it becomes increasingly difficult to merge in contributions. I hope you understand.

@kevinschaul @lstein I have a very nice implementation of this feature locally using -save_progress. I think I will make a new PR with that feature added to this and add kevin as the co-author.

Hi all, apologies I was away from keyboard this weekend. Thanks for all the tips. I'm happy to close this and help get #694 merged instead.


Misbehaviour: wrong timestamp being used in trusting period checks

In checking for misbehaviour, we use host_timestamp() as the timestamp used in “trusting period checks”. This is not the timestamp we want to be using though, since this gives the timestamp associated with the latest  “trusted consensus state”, whereas we want to be using the timestamp of the header we’re processing.
Equivalent in ibc-go (assuming ctx.BlockTime() is the height of the header being processed, which I think it is).

This is not a bug; I think this was a misunderstanding of mine while doing #584.


Add prometheus-podman-exporter deployment

This PR adds prometheus-podman-exporter container deployment
which serves for reporting health of containerized services.
Related: OBSDA-574
Related: OSPRH-1052
Closes: OSPRH-5007

/test pre-commit-test

/lgtm

/test pre-commit-test

/lgtm


corretto8: init at <IP_ADDRESS>

Motivation for this change
AWS Corretto is a distribution of OpenJDK that comes with additional performance and security patches, and long-term support until at least June 2023.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

As maintainers of the existing OpenJDK 8 package:
r? @edwtjo @NeQuissimus
I'd be interested to hear what you folks think about this "override openjdk8" approach; it saves a ton of code duplication and refactoring compared to writing an entirely new derivation.

@andrew-d What is the status of this?


Here are the first two Node.js assignments, Landing Page and Cars and…

… Cats.

Can't really review your code if you have them in zips :) would try and add the files not the zip


Add banner to upgrade alby lndhub to alby account

Feature description
Still many seem to use the lndhub connector with the Alby lndhub. Those users should connect their alby account and no longer use the lndhub connector
Describe the solution
show a banner if the user is using an lndhub connector and the host is ln.getalby.com
Describe alternatives
No response
Additional context
No response
Are you working on this?
None

Closed with #3140


Add me to Repository

Ann Allen
<EMAIL_ADDRESS>AnnAllen-NOAA

Ann-
You have been added as an admin to this repository. Please move forward with the rest of the pre-meeting prep and let us know if you have any questions!
Cheers- Shannon


additional permission steps in openshift for running applications

Addons needed oc adm policy add-scc-to-user anyuid -z default -n istio-system  permission as grafana/prometheus  were using uid 0
also by default openshift denies privileged containers which is needed as part of sidecar deployment, hence to bypass that error.
oc adm policy add-scc-to-user privileged -z default -n <target-namespace>

Jenkins job istio.github.io/presubmit passed


The components section looks unattractive, the coloring ratio strains the eyes.

What's the style idea?
We need to improve
by adding new color components to make the user feel good and attract them to use the website again and again, leading to a better user experience.
Making the components transparent doesn't look good.
I have a good grasp of CSS styling. I have created many clones and developed my own website, OvenOasis. I have a good command of coloring ratios and I am confident that I can make this website more attractive.
Please assign this project to me under GSSOC'24.
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

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

please assign this to me

Hey, can you please assign me this issue if it is not solved? This is my first time making an open-source contribution, and I really want to showcase my skills. I am very familiar with languages like Java, HTML, CSS, and JS. Apart from coding, I'm an ux/ui freelancer as well.

Do you want to be assigned @Mdazar123

@Rakesh9100,
I am very proficient in the design aspect of projects and always give my 100% effort. I am eagerly waiting to be assigned a task and am ready to contribute

Go ahead @Mdazar123

Thank you, @Rakesh9100, for assigning this task to me. I truly appreciate the opportunity and am eager to contribute my best efforts.

Pls provide your PR @Mdazar123

Hi @Rakesh9100,
I apologize for the delay in submitting my PR. My semester mid Exams are currently underway, which has occupied most of my time. However, my exams will be over by Saturday evening, and I will make sure to submit the PR by then.

Are you ready with your PR @Mdazar123

Hi @Rakesh9100,
I apologize for the delay; it was due to the Bakrid celebrations.
I have created a pull request for this issue : #1078
Thank you for your understanding and patience.


[Coverity CID :188752]Security best practices violations in /subsys/shell/shell.c

Static code scan issues seen in File: /subsys/shell/shell.c
Category: Security best practices violations
Function: help_options_print
Component: Other
CID: 188752
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

file refactored, does not apply anymore.