Hovering z-index of a component sharing the border

I have been wondering about the necessity of z-index when hovering for the past few months. I think that the reason why z-index is given is related to display of a border between elements, but  I do not understand exactly why it is necessary.
Related components (sharing the border)
Currently, the following components have z-index: 1 when hoverring:

Button group (added from bfc4aaf)
List group (added from #24813)

But the following components don't have:

Pagination
Elements in input group (added from  bfc4aaf but removed at #25020)

My points:
1. List group item issue
When hovering a list item, the border flickers slightly. It may be correct when items are links or buttons. But it is strange if it is a static list. You can see in the Contextual classes docs
2. Necessity (Clarify the design specifications)
If I may ask, could you clarify the reasons to bring it to the front when hovering? This will also be related to #25165.

Component states should obey a common z-index scale: default (initial), hover (1), active (2), focus (3)

3. Consistency
If the hovering z-index is the correct specification, please consider adding it to pagination and input group as well.
Thanks.

Pagination has the z-index on hover, and input group has it in general for buttons and add-ons from the looks of it. Let me know if there are any specific lines that need updating that I missed, though!


Show registration type on a card

Some events have "Same Day Only" registration (e.g. CCCX) it would be nice to show it on a card instead of registration link.


Sticky scroll renders above right-click context menus

Does this issue occur when all extensions are disabled?: No (because the context menu is not tall enough, so it's not really an extension bug)

Version: 1.76.0 (user setup)
Commit: 92da9481c0904c6adfe372c12da3b7748d74bdcb
Date: 2023-03-01T10:22:44.506Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

Steps to Reproduce:

enable sticky scroll
Right click where the menu overlaps the sticky area
Screenshot:

Maybe #160620

Hi, I am testing on the latest insiders release (https://code.visualstudio.com/insiders/) and the issue appears to be fixed as @bpasero said. Let me know if the problem persists.

Cool, thanks


Consider removing some module API methods

simulate is a special case of generate with an empty choice trie. it is possible to JIT-compile an implementation of generate specialized to this case by passing an EmptyChoiceTrie as the constraints. Therefore, there isn't really much of a performance reason to keep simulate around.
However, we should keep assess because it expects a complete choice trie. This is something that is hard to specialize on using JIT compilation. It makes sense to have a specialized procedure for this.
I also considered removing extend, which is a special case of fix_update. The point of extend is that it is an error if any addresses are deleted. This property gives large opportunity for specialization over fix_update; for example there is no discard choice trie needed. However, the args-change value and the constraints should together determine whether or not there will be deleted addresses anyways. But this is not a property that can be trivially encoded in the type of the constraints trie and the args-change value. Therefore, I will keep it. It should be clear that it is a special case of fix_update and exists as an (optional) performance optimization. There should be a default implementation provided for abstract Generators that just calls fix_update, and checks at the end that the discard trie is empty.

Fixed by https://github.com/probcomp/Gen/pull/35


VSC docker debugging + GUI from withing container

unfortunately still no proper documentation for the added features since it's still WIP but anyone working with VSC insider version will be able to work this out.  Also, matplotlib-cpp is not yet with 3d scatter plot. I will try to PR the original author to include it upstream.  At the moment, running tmexample will just open a sample 3d surface just to show GUI is working from the container...

changed Debug into Release ..

Oops. I found my other comments aren't visible to you. Sorry for the inconveniences.
Since we have decided that matplotlib-cpp seems not to be an ideal solution. Should we wait for a better one?

yes. I'm going for another render engine ogre3d ... it looks much better
but I need more time to demo it ... I'll add another example and not ride
on tmexample this time ...
On Thu, May 30, 2019 at 7:31 PM Martin Chang<EMAIL_ADDRESS>wrote:

Oops. I found my other comments aren't visible to you. Sorry for the
inconveniences.
Since we have decided that matplotlib-cpp seems not to be an ideal
solution. Should we wait for a better one?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/etaler/Etaler/pull/13?email_source=notifications&email_token=AAXET3GISX4BHJK6TOXUHMLPX76N5A5CNFSM4HPWXAE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWSZ77Q#issuecomment-497393662,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXET3H2525O6RMYL3R53HLPX76N5ANCNFSM4HPWXAEQ
.

I guess I'll close this PR for now. Fell free to re-open it if you have other related things to push.


Ellipse shape for selection area & universal command for build on win/unix/os x

This patch adds functionality to label an image with the ellipse-shaped area. Also I have fixed the command for build from CI=true to set CI=true, cause the first command doesn't work on windows machines.

@lrlunin First of all, absolutely great work! Here are a couple of minor things I've noticed that needs attention:

mathjs is not in the package.json
saved completions are not loaded for some reason
the Node name Ellipse 97.00 x 128.00, θ = 52.31793070243489, center = (474.00,580.00) I'd format the theta to two points after the dot

All in all, it looks just a step away from being merged! Thanks for your contribution!

@deppp Sorry for missed bugs. Now I have completely tested it with different examples. It should work fine now. As I noticed mathjs is in package.json. Indeed this library will be not used and can be deleted from packaging and source files. Should I do it?


Wrong SQL error

Describe the bug
I ran a valid SQL code but it was reported as having error. Same code worked on other SQL clients.
To Reproduce
Steps to reproduce the behavior:

Create an SQLite database that has a session_data table with the columns: deletedAt, StudentId, and session
Run this code in Antares against the database: select * from session_dataWHERE (deletedAtIS NULL AND (StudentId= 2224 ANDsession = "2022/2023" ) )
See error

Expected behavior
It should run the SQL query without errors
Screenshots

Application (please complete the following information):

App client SQLite
App version 0.7.1
Installation source: apt

Environment (please complete the following information):

OS name: Zorin Pro OS
OS version 16
DB name  SQLite
DB version N/A

Hi @damms005,
i suggest you to use single quotes for string literals, the legacy support of double quotes for strings isn't enabled in better-sqlite3 (SQLite module used by Antares).


[Fix] subscribe to return unique_ptr

already done https://github.com/olympus-robotics/hephaestus/pull/54


Users CSV: users import / export

[x] handle csv double quoted in import
[ ] Raise error if more columns than expected during split (EDIT : there is no split, we use the csvToJson and it already raises an error if number of columns does not corresponds)

@LucasBrazi06 did you mean something specific to be done for the "raise error" part ? more than what's already done ? because for now when the file contains more column than expected we already have an error like "provided file invalid"

No, extra columns should be ignored, only required ones trigger errors.

What I meant is that if you have 4 columns in the headers and you get 5 in a given line, you reject it but only the faulty line and you continue to process the rest of the users.

Why it's iceboxed :
Check if we do something with the withTag flag ?
Do we keep it as flag and add an option to the UI ? as flag is always set to true for now ...


TSC Meeting (12th Sept 2023)

Sept 2023 @StackStorm/tsc 1 hour meeting plan:

See https://github.com/StackStorm/community/issues/33 for the schedule.
TLDR; Jitsi link: https://meet.jit.si/StackStormTSC

Attendees

Carlos
Chaimaa
Dale Smith @ Orchestral
Eugen
Haven
Scott

Topics discussed
New Participants

Scott has recently started using StackStorm for auto-remediation and is interested in St2 progress towards u22.04 py3.10.
Haven works with Scott and is interested in hardening St2 and running St2 as non-root in containers.
Chaimaa has worked in the R&D team to deploy St2 to multiple internal and external clients, helped automated daily tasks for the   N.O.C. (network operation centre), has experimented with ChatOps and would like to try NoOps, has expressed interest in contributing to the jira pack and possibly documentation.

Blog / Web site
Dale presented the proposition to restart the web site migration from WordPress to Eleventy as documented here https://github.com/StackStorm/community/issues/123  with the objective to bring some vitality and better public facing energy to the website.
There are still on-going discussions for and against the use of Eleventy vs Hugo.
Python 3.10 / Ubuntu 22.04 support
Status quo, progress remains predominantly blocked due to numerous module dependency incompatibilities and would benefit from addition community assistance.  Scott expressed the possibility of getting involved if time permits.

With regards to the Python3.10 dependency incompatibilities, I've got this version running on 3.11. There weren't any major incompatible language or library changes between the two, so dependencies should just work on 3.10
I did run into the mess around gunicorn, but they've finally cut a release after like 3 years, so you should be able to pin the latest tag version instead of the commit
I also had to make a tweak to the Orquesta engine to get it working due to the deprecated collections imports being actually removed in Python 3.10
I know none of this is concrete or anything, but StackStorm works in Python 3.10/3.11. We just need to get the test suite updated to actually pass with the current mainline.

What version of Mongo did you test against?  I was under the impression that there would have to be a lot of code update to bump the mongo dependencies.

With regards to the Python3.10 dependency incompatibilities, I've got this version running on 3.11. There weren't any major incompatible language or library changes between the two, so dependencies should just work on 3.10
I did run into the mess around gunicorn, but they've finally cut a release after like 3 years, so you should be able to pin the latest tag version instead of the commit that I have there.
I also had to make a tweak to the Orquesta engine to get it working due to the deprecated collections imports being actually removed in Python 3.10
I know none of this is concrete or anything, but StackStorm works in Python 3.10/3.11. We just need to get the test suite updated to actually pass with the current mainline.

That's good to know, that brings it to same state as python 3.9 then. Really pleased that gunicorn release has been done - we've been waiting on that for a while.

What version of Mongo did you test against?  I was under the impression that there would have to be a lot of code update to bump the mongo dependencies.

I tested against the version included in the ansible-st2 playback, which I think is version 4.x

@AndroxxTraxxon The build in orquesta main branch was fixed and is 🟢 now, so you should be unblocked to work on the https://github.com/StackStorm/orquesta/pull/253. Try to fix the merge conflicts and experiment with the build matrix you're trying to add.

Thanks! I'll give it a go!


[Suggestion] Powered Spawner spawn exact copy of Entity

I'd like to have a Powered Spawner that spawn exact copy of Entity (Entity with NBT) that i catched with Soul Vial. I would suggest having a config option (even setted to false by default) that allow such behaviour.

If you want to dupe things, just use creative mode...


Improve ux when selecting nodes

We should start off by showing all nodes and then narrowing it down with filters if needed.
e.g. If I'm looking for a node it doesn't matter to me if it's certified or not so I should be able to see all of them. If then I want a certified, dedicated or GPU node, I can choose those so it filters the results.

I thought the idea was for certified nodes to show up first.
And; how do we inform the benefits of silver and gold farms?

WIP:

trying to show all certified/uncertified nodes at first without applying filters

Still investigating

Couldn't investigate on development as graphql was down

Work Completed:

Added a chip for certified nodes
All nodes load regardless of the certified filter at first
Work in Progress (WIP):

Investigation and Solution:

Investigating why does it retrieve the certified nodes even when the filter is false

Work Completed:

Added a watch for the selectedNode so it the calculator recalculates.
Added a warning within the calculator div telling the user that a certified node is being used.
pr is pending review.

Work in Progress (WIP):
Investigation and Solution:

Work Completed:

Added a condition to recalculate cost when the certified filter is off but the user chooses a certified node
pr is ready for review

Work in Progress (WIP):
Investigation and Solution:

Verified,
Devnet, 3fc8787.
All the nodes are now shown for the user first, and three toggles have been added: GPU, dedicated, and certified to specify node type; also, node region, country, farm name, and ID can be specified.

cannot find a certified node to test the calculator is working as expected

devnet
ebf75a3

@ramezsaeed There's no certified nodes on devnet, you should test against mainnet.

verified on : dashboard.bknd1.ninja.tf
version : 2.3.0-alpha6

Verified:

Mainnet (Ninja)
2.3.0-alpha6


Check accessibility

After testing accessibility with Voice Over, here is a list to task to be done:

[x] Fix accessibility on System Designer web site
[ ] Fix toolbar navigation
[ ] Fix menu navigation
[ ] Fix element selection focus on workspace with tab
[ ] Add font size control
[x] Check accessibility level of Ace / Code Mirror editors

One missing accessibility feature is control over the size of the fonts used throughout the UI.
I have macular degeneration in both eyes which makes reading small fonts very difficult.

Thank you for your feedback !
I have added it to the list. I will check if 3rd party tools I use manage that.
A temporary solution would be maybe to use the web version of System Designer with integrated zoom feature of browsers. Only downside is that "Command +" / "Control +" shortcuts are overriden to ease items creation with keyboard.

Thank you for acknowledging my request 😀
I'm looking forward to see System Designer support this, in the meantime I
can make do with Android's full screen magnification.
I thoroughly enjoy using System Designer, thank you for creating it 🙏
Tjerk
On Sun., Jan. 2, 2022, 7:24 p.m. Erwan Carriou, @.***>
wrote:

Thank you for your feedback !
I have added it to the list. I will check if 3rd party tools I use manage
that.
A temporary solution would be maybe to use the web version of System
Designer with integrated zoom feature of browsers. Only downside is that
"Command +" / "Control +" shortcuts are overriden to ease items creation
with keyboard.
—
Reply to this email directly, view it on GitHub
https://github.com/design-first/system-designer/issues/16#issuecomment-1003803251,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALMMFG75KKFZSPMJZQ63LHLUUDUFFANCNFSM4CRPF56A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

Hi Erwan,
I ran into an issue and noticed that I was not using the latest version.
I renamed the existing installation (5.0.2) and then installed the latest
(5.1.0).
I now get the following error:
sh: 1: electron: not found
Then I renamed the latest installation and restored the previous
installation and now I get the same error with the previous installation.
I'm dead in the water...
Please, where did I go wrong and how do I fix it?
Tjerk
On Sun., Jan. 2, 2022, 7:24 p.m. Erwan Carriou, @.***>
wrote:

Thank you for your feedback !
I have added it to the list. I will check if 3rd party tools I use manage
that.
A temporary solution would be maybe to use the web version of System
Designer with integrated zoom feature of browsers. Only downside is that
"Command +" / "Control +" shortcuts are overriden to ease items creation
with keyboard.
—
Reply to this email directly, view it on GitHub
https://github.com/design-first/system-designer/issues/16#issuecomment-1003803251,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALMMFG75KKFZSPMJZQ63LHLUUDUFFANCNFSM4CRPF56A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

Can you tell me what did you do to install System Designer ? Is it an update from the Mac App Store ? And can you tell me what is your environment (macOS with intel / M1 chip) ?
I will try to reproduce your issue. But what you can do is delete the app and reinstall it.

I installed using the Build instructions on GitHub, in Crostini (Linux)
under Chrome OS, ie. git clone, followed by npm i
On Tue., Jan. 4, 2022, 1:50 p.m. Erwan Carriou, @.***>
wrote:

Can you tell me what did you do to install System Designer ? Is it an
update from the Mac App Store ? And can you tell me what is your
environment (macOS with intel / M1 chip) ?
I will try to reproduce your issue. But what you can do is delete the app
and reinstall it.
—
Reply to this email directly, view it on GitHub
https://github.com/design-first/system-designer/issues/16#issuecomment-1005081901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALMMFG44YHNB4Q3Y65CSCCDUUM6QZANCNFSM4CRPF56A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

You clone this repo or https://github.com/design-first/system-designer-electron ?
So you just clone the repo, do npm i and then npm run start ?
Try npm ci instead npm I to start from a clean base.

I tried again using npm ci and this time it worked.
I ran npm ci in system-designer, system-designer-electron and
system-runtime.
In my previous attempt I only ran npm i in the system-designer folder.
So it's all good now, thank you for your help.
I have confirmed that the issue I ran into on 5.0.2 still exists in 5.1.0 -
I'll create a bug report.
Tjerk
On Tue., Jan. 4, 2022, 6:24 p.m. Erwan Carriou, @.***>
wrote:

You clone this repo or
https://github.com/design-first/system-designer-electron ?
So you just clone the repo, do npm i and then npm run start ?
Try npm ci instead npm I to start from a clean base.
—
Reply to this email directly, view it on GitHub
https://github.com/design-first/system-designer/issues/16#issuecomment-1005246077,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALMMFG52YEMUX57OQXCVXPDUUN6TTANCNFSM4CRPF56A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

See issue #143
On Tue., Jan. 4, 2022, 9:40 p.m. Terry Herckenrath, @.***>
wrote:

I tried again using npm ci and this time it worked.
I ran npm ci in system-designer, system-designer-electron and
system-runtime.
In my previous attempt I only ran npm i in the system-designer folder.
So it's all good now, thank you for your help.
I have confirmed that the issue I ran into on 5.0.2 still exists in 5.1.0

I'll create a bug report.

Tjerk
On Tue., Jan. 4, 2022, 6:24 p.m. Erwan Carriou, @.***>
wrote:

You clone this repo or
https://github.com/design-first/system-designer-electron ?
So you just clone the repo, do npm i and then npm run start ?
Try npm ci instead npm I to start from a clean base.
—
Reply to this email directly, view it on GitHub
https://github.com/design-first/system-designer/issues/16#issuecomment-1005246077,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALMMFG52YEMUX57OQXCVXPDUUN6TTANCNFSM4CRPF56A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>


GridViewReverse

I want to imitate the display of IOS mobile phone system photo album，My GridView has four items in each row. I want to reverse the GridView completely (the first is in the last, and the last is in the first), GridView.builder If the reverse field is set to true, each column is arranged in reverse order, but not in each row. I think this is a bug in the router. Please fix it, thanks!!!

Hi @18335180686
can you please provide the flutter doctor -v and minimal reproduction code?
Thanks.

@18335180686
Please elaborate on your issue by providing flutter doctor -v and most importantly a minimal complete reproducible code sample that shows the issue. What's the expected behavior are you looking for when using GridViewReverse and what are you seeing now ?
Thanks.

@<PHONE_NUMBER>6
请通过提供flutter doctor -v（最重要的是，提供一个最小的，完整的，可再现的代码示例来说明问题）来详细说明您的问题。使用GridViewReverse时，您正在寻找什么预期行为？现在看到了什么？
谢谢。

I hope that the GridView as a whole is arranged in reverse order, including rows and columns. But at present, only the columns are in reverse order, and the rows are still in normal order. The first picture is the effect of my code running, but I want it will be the effect of the second one.
——————————
|—20—21—22—23—｜
|—16—17—18—19—｜
|—12—13—14—15—｜ This is the first picture
|—8 — 9 —10 —11 —｜
|—4 — 5 — 6 — 7 —｜
|— 0— 1 — 2 — 3 — ｜
——————————
| —23—22—21—20—｜
| —19—18 —17—16 —｜
| —15—14—13—12—｜
| —11— 10—9 — 8 —｜ This is the second picture
| — 7 — 6 — 5 — 4 —｜
| — 3 — 2 — 1 — 0 — ｜
——————————
Here are examples of code and flutter doctor：
GridView.builder(
reverse: true,
itemBuilder: (context, index) {
return Text("index:$index");
},
itemCount: 100,
gridDelegate: SliverGridDelegateWithFixedCrossAxisCount(
crossAxisCount: 4,
),
);
flutter doctor -v
[✓] Flutter (Channel stable, 1.22.1, on Mac OS X 10.15.7 19H2, locale zh-Hans-CN)
• Flutter version 1.22.1 at /Users/tutu/Documents/flutter
• Framework revision f30b7f4 (12 days ago), 2020-10-08 10:06:30 -0700
• Engine revision 75bef9f6c8
• Dart version 2.10.1
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at /Users/tutu/Library/Android/sdk
• Platform android-30, build-tools 28.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.0.1, Build version 12A7300
• CocoaPods version 1.8.4
[✓] Android Studio (version 4.0)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 50.0.1
• Dart plugin version 193.7547
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

@<PHONE_NUMBER>6
是设计使然，如果您使用reverseto true，它将反转列而不是行。
查看此文档以获取有关reverse工作原理的更多详细信息。

OK, thank you. How can I achieve the effect I want? Is there any property that can be controlled? Or can we only write logic to realize this function?

Please see https://flutter.dev/community for resources, you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing this as working as intended. If you disagree, write in comments and I'll reopen.
Thanks.


open_file_failed -- failed

Not sure if this is an issue w/ the docs or a bug
Failed file open attempts, useful to detect threat actors making mistakes
https://man7.org/linux/man-pages/man3/errno.3.html
evt.res=ENOENT - No such file or directory
evt.res=EACCESS - Permission denied

macro: open_file_failed
condition: (evt.type in (open,openat,openat2) and fd.typechar='f' and fd.num=-1 and evt.res startswith E)
list: file_operation_paths
items: [/bob]
macro: create_symlink
condition: (evt.type in (symlink, symlinkat) and evt.dir=<)
macro: open_write
condition: (evt.type in (open,openat,openat2) and evt.is_open_write=true and fd.typechar='f' and fd.num>=0)
macro: open_read
condition: (evt.type in (open,openat,openat2) and evt.is_open_read=true and fd.typechar='f' and fd.num>=0)
macro: open_file_failed
condition: (evt.type in (open,openat,openat2) and fd.typechar='f' and fd.num=-1 and evt.res startswith E)
macro: rename
condition: evt.type in (rename, renameat)
macro: mkdir
condition: evt.type = mkdir
macro: remove
condition: evt.type in (rmdir, unlink, unlinkat)
macro: modify
condition: rename or remove
macro: file_operation
condition: (open_read or open_write or modify or open_file_failed or create_symlink or evt.type in (link,linkat))
rule: Any File Related Operation in Path
desc: Detect any file operation on a single path
condition: (fs.path.name pmatch (file_operation_paths) or fs.path.source pmatch (file_operation_paths) or fs.path.target pmatch (file_operation_paths) or fd.name pmatch (file_operation_paths)) and file_operation
output: >
Some File Related Operation on Path (evt.type=%evt.type path=%fs.path.name source=%fs.path.source
target=%fs.path.target %user.name=%user.name proc.cmdline=%proc.cmdline proc.pcmdline=%proc.pcmdline container.id=%container.id container.name=%container.name image=%container.image.repository)
priority: DEBUG
source: syscall

tried w/ 'E' and that failed as well (edited)

How to reproduce it

Expected behaviour

I expected a new Detect to be shown for open_file_failed, which it did not.
Screenshots

Environment

Falco version:

Tried on 0.35 and 0.36
Falco version: 0.35.0
Libs version:  0.11.2
Plugin API:    3.0.0
Engine:        17
Driver:
API version:    4.0.0
Schema version: 2.0.0
Default driver: 5.0.1+driver
Falco version: 0.36.2
Libs version:  0.13.4
Plugin API:    3.1.0
Engine:        26
Driver:
API version:    5.0.0
Schema version: 2.0.0
Default driver: 6.0.1+driver

System info:

5.14.0-362.13.1.el9_3.x86_64

Cloud provider or hardware configuration:
OS:
NAME="AlmaLinux"
VERSION="9.3 (Shamrock Pampas Cat)"
ID="almalinux"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.3"
PLATFORM_ID="platform:el9"
PRETTY_NAME="AlmaLinux 9.3 (Shamrock Pampas Cat)"
ANSI_COLOR="0;34"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos"
HOME_URL="https://almalinux.org/"
DOCUMENTATION_URL="https://wiki.almalinux.org/"
BUG_REPORT_URL="https://bugs.almalinux.org/"

ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9"
ALMALINUX_MANTISBT_PROJECT_VERSION="9.3"
REDHAT_SUPPORT_PRODUCT="AlmaLinux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.3"

Kernel:

Installation method:

RPM
Additional context

entirely my fault, open file failed not same as rm.


[Fix/enhancement] dockerimage labels check and attempted to deduplicate

Relates to: https://github.com/opendatahub-io/notebooks/issues/292

Docker image labels reviewed
Description

This change tries to deduplicate some strings in our docker image labels with ability to propagate some common values directly from the Makefile so we don't need to change these values with every release branch or for every newly introduced docker image.
There were some minor fixes in the labels introduced too in this commit.

Notable points for discussion:

I used value of the RELEASE variable for the build-ref at the moment - I understand that this may not be ideal. We may introduce separate value for this in Makefile or we can try to compute the value (either ref hash or branch name) dynamically in Makefile too. But in general - the value of the RELEASE should match what we've used so far.
Also, some labels (authoritative-source-url and build commit ref at least) could be propagated directly from Makefile - in this case I mean by using the --label parameter. There are two drawbacks I can think of:

We could lost them in case of an individual build because this way these won't be enforced by Dockerfile itself
In this Dockerfile we have a slightly different naming for some labels which includes s2i infix - we would have to assure we don't change it wrongly.

Actually - do we want these s2i infixes?

I didn't touch the Anaconda Base Dockerfile - looks like the labels there should deserve review too.

How Has This Been Tested?

I did a brief build of one image so far to check the idea behind the changes works. Will do more once the conversation here is finalized:
make codeserver-ubi9-python-3.9 -e IMAGE_REGISTRY=quay.io/jstourac/workbench-images

Result images can be seen in https://quay.io/repository/jstourac/workbench-images?tab=tags&tag=latest
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

Hey Jan! This changes looks good to me  :slightly_smiling_face:  I added a small comment on the proposal!

Okay, I rebased and updated with the change so that the AUTHORITATIVE_SOURCE_URL is now propagated also from Makefile. And I also used the BUILD_COMMIT_REF value in the io.openshift.build.source-location value.

Regarding the Anaconda - there are two LABEL definitions in the Dockerfile:
https://github.com/opendatahub-io/notebooks/blob/main/base/anaconda-python-3.8/Dockerfile#L25C1-L34C48
LABEL summary="$SUMMARY" \
      description="$DESCRIPTION" \
      io.k8s.description="$DESCRIPTION" \
      io.k8s.display-name="Anaconda Python 3.8" \
      io.openshift.expose-services="8080:http" \
      io.openshift.tags="anaconda,builder,python,python38,python-38,anaconda-python38" \
      name="anaconda-python38" \
      version="1" \
      usage="s2i build https://github.com/sclorg/s2i-python-container.git --context-dir=3.8/test/setup-test-app/ ubi8/python-38 python-sample-app" \
<EMAIL_ADDRESS>for now..."

and
https://github.com/opendatahub-io/notebooks/blob/main/base/anaconda-python-3.8/Dockerfile#L87C1-L91C98
LABEL name="odh-notebook-base-ubi8-anaconda-python-3.8" \
      summary="Anaconda based Python 3.8 base image for ODH notebooks" \
      description="Anaconda Base Python 3.8 builder image based on UBI8 for ODH notebooks" \
      io.k8s.display-name="Anaconda Python 3.8 base image for ODH notebooks" \
      io.k8s.description="Anaconda Base Python 3.8 builder image based on UBI8 for ODH notebooks"

Is there anything what we want to do with it? Do we want to update the second section to similar format as is e.g. in:
https://github.com/opendatahub-io/notebooks/blob/main/base/ubi9-python-3.9/Dockerfile#L3C1-L11C91
LABEL name="odh-notebook-base-ubi9-python-3.9" \
      summary="Python 3.9 base image for ODH notebooks" \
      description="Base Python 3.9 builder image based on UBI9 for ODH notebooks" \
      io.k8s.display-name="Python 3.9 base image for ODH notebooks" \
      io.k8s.description="Base Python 3.9 builder image based on UBI9 for ODH notebooks" \
      authoritative-source-url="https://github.com/opendatahub-io/notebooks" \
      io.openshift.build.commit.ref="main" \
      io.openshift.build.source-location="https://github.com/opendatahub-io/notebooks/tree/main/base/ubi9-python-3.9" \
      io.openshift.build.image="quay.io/opendatahub/workbench-images:base-ubi9-python-3.9"

Regarding the Anaconda - there are two LABEL definitions in the Dockerfile:
...
Is there anything what we want to do with it? Do we want to update the second section to similar format as is e.g. in:
https://github.com/opendatahub-io/notebooks/blob/main/base/ubi9-python-3.9/Dockerfile#L3C1-L11C91
LABEL name="odh-notebook-base-ubi9-python-3.9" \
      summary="Python 3.9 base image for ODH notebooks" \
      description="Base Python 3.9 builder image based on UBI9 for ODH notebooks" \
      io.k8s.display-name="Python 3.9 base image for ODH notebooks" \
      io.k8s.description="Base Python 3.9 builder image based on UBI9 for ODH notebooks" \
      authoritative-source-url="https://github.com/opendatahub-io/notebooks" \
      io.openshift.build.commit.ref="main" \
      io.openshift.build.source-location="https://github.com/opendatahub-io/notebooks/tree/main/base/ubi9-python-3.9" \
      io.openshift.build.image="quay.io/opendatahub/workbench-images:base-ubi9-python-3.9"

Updating the 2nd part exclusively the jupyter/anaconda-x part , same as other would be prefered.

Thank you, @harshad16, for your review. I'll try to find some time for this this week :slightly_smiling_face:

The PR looks great, my major concern is this would break the current CI build from openshift CI
and that doesn't completely rely on makefile.
https://github.com/openshift/release/blob/358594a0d50341051cdd9eb1137757a734fab063/ci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-main.yaml#L8
the CI , doesn't take in build args, which make cause this issue.
Result image of this PR needs to be tested.

The PR looks great, my major concern is this would break the current CI build from openshift CI and that doesn't completely rely on makefile. https://github.com/openshift/release/blob/358594a0d50341051cdd9eb1137757a734fab063/ci-operator/config/opendatahub-io/notebooks/opendatahub-io-notebooks-main.yaml#L8 the CI , doesn't take in build args, which make cause this issue. Result image of this PR needs to be tested.

Due to this, we are changing this PR to the draft.


update ml-lodlive dependency

An updated version of ml-lodlive has been released (0.4.0). Please update bower.json to reference this version, as it has many fixes and improvements.
Note: for the purposes of this component, this release is mostly backwards compatible.

Did you by any chance run a test were you installed this together with ml-lodlive#0.4.0 to see how well that works?

I have added you as collaborator. Feel free to open a PR and/or mess about.. ;)


please do portable with own venv, im tired of all the repos havin issues with dependencies and outdated commands...

(myenv) F:\frame interEMA>python interpolate.py
Traceback (most recent call last):
File "interpolate.py", line 12, in
from webui_utils.simple_utils import sortable_float_index
File "F:\frame interEMA\webui_utils\simple_utils.py", line 97, in
mantissa_width : float | None = None):
TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'

@2blackbar Thank you! It's been on the TODO list for some time to make a simple installer.

If you use Python 3.10.9 you'll avoid this particular problem

Another user ran into this issue and this solved it for them

It's straightforward to set up a new Anaconda environment with a specific Python version

https://numdifftools.readthedocs.io/en/stable/how-to/create_virtual_env_with_conda.html


Github Action to build and test anchor project

Do you have the action to build anchor project in specific version?

Yeah, the previous post answers this nicely.


Main Value Update

in main.py
Value update needs to be able to find frequency
Current plan is to check ADC value rapidly then once value is lower mark as high point.

added temp/humidity/battery missing current and voltage

added frequency and voltage. pretty much done on the software side, only thing missing is adjustment factor for adc


updated viscosity (1.6.5)

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

Closed in favour of https://github.com/caskroom/homebrew-cask/pull/23827.


dagre: nodesepFunc not working when workerEnabled == true

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

Steps to reproduce

set workerEnabled = true in dagre config
nodesepFunc is not called

Environment
Info

g6
4.1.8

System
-

Browser
-

Since the web-worker could only read the plain variables but not functions, the nodesepFunc is not available for worker mode.

hi, thanks for your answer. Currently, if we want to vary nodesep depending on node properties and have web  worker enabled, do you know any workaround forr this?

For now, it can be only assigned to a constant if you wanna run dagre in web-worker


Block syntax for scanning, finishing, pausing and resuming.

What do you think about supporting a block style syntax for enabling/disabling N+1 detection.
For example:
Prosopite.scan do
  example.run
end

in addition to:
Prosopite.scan
example.run
Prosopite.finish

Similarly, pausing could be something like:
Prosopite.pause do
  code_with_n+1()
end

in addition to:
Prosopite.pause
  code_with_n+1()
Prosopite.resume

@oskarpearson Oh nice! This is great, and also looks like my next two questions are also being considered:

having the block return the results
nesting blocks

Let me know if I can do anything to help. Looking forward to both of these!

@oskarpearson @charkost I saw that these changes have all landed on main. Any chance you're able to cut a new release of this gem soon? I'm anxious to get my hands on block syntax 😅


chore: Bump superchain-registry version

Overview
Bumps the version of superchain-primitives to a version that contains https://github.com/ethereum-optimism/superchain-registry/pull/311.

#306  👈
main

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

Join @clabby and the rest of your teammates on  Graphite

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 79.6%. Comparing base (0e1457d) to head (b7f6777).

Additional details and impacted files

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

Once https://github.com/ethereum-optimism/superchain-registry/pull/318 is merged, we should be able to use the bumped version


Search engine optimization

Hi there, first of all, thanks a lot for the nice app!
While comparing the search engine of the app with the official Hacker News search, I found that it was giving less accurate results (e.g. on "Gpt4-Turbo"). Additionally, it does not seem to be possible to search with "All Time" as a timespan.
I therefore wanted to ask, if Glider is using the official Hacker News search? And if not if there's a specific reason for it.
Thanks!

I'm assuming that when you mention the "official Hacker News search", you're referring to the Hacker News search powered by Algolia at https://hn.algolia.com/. That would indeed be the same source that Glider is using for its search functionality.
I cannot reproduce the mentioned lower accuracy. I'm seeing basically the same results between this app and the web page. It would be helpful if you could provide some side-by-side results that show a quality discrepancy. The main difference between this app and the web page (with its default settings) is that Glider disables typo-tolerance because I found that that can result in some curious matches.
It is possible to search without any time span, but it might not be immediately obvious if you haven't been exposed to the chip UI element much before. It's possible to deselect the currently selected date filter to enter the default "all time" mode.

Yes sorry for not being clear, I also corrected the issue title which was misleading.
Here are 2 screenshots comparing the search results:

Maybe it is just a different ordering of results that is being used?

I see. Initially you referenced "Gpt4-Turbo", which shows very similar results on Glider and Algolia, but you're right that "Gpt4 Turbo", without the dash, results in a lot more matches on the latter.
It does turn out that the typo-tolerance setting in Algolia is what makes up the difference. In this case the "correct" search term would be "GPT-4 Turbo". As mentioned I've had some weird results with typo-tolerance enabled, but there's an argument to be made that skipping the dash should be tolerated here. Let me meditate on it.

Ah yes I see. I wasn't sure in the beginning about what triggered the difference so I played around with it.
What you said makes sense, thanks!


Fix regression for default values completion (#150)

fix default values on completion regression
fix completion with empty uri

Signed-off-by: Aurélien Pupier<EMAIL_ADDRESS>

@lhein please review asap as it is fixing regression affecting one of the most used workflow: completion with an empty uri


Are the "legacy voices" from Streamlabs covered with this?

Hello.
Anyone knows a way to test the Streamlabs "Legacy Voices"? I just look up with this and no one of the ones that work doesn't seems from them.
What is the API these voices come from?
Thanks!

I wasn't actually aware of those so called "Legacy Voices" when I made this. I suspect they were deprecated for quite some time and eventually removed from Streamlabs. Sorry but I don't know of any other APIs that have these voices available. And I don't even know what they were called so that I could search for them.

Thanks anyway!
They were never deprecated, they are there for years and you can still use them right now for Twitch alerts and things like that, although as their name say they look like the "old" version (they don't have names, and only one per language) and maybe they wanna get rid of them but they never did because some people still use them...? idk.
Also, i don't find anywhere in the Streamlabs website where says from where the API voices comes from, not only the Legacy ones, also the "Polly" ones.
In any case, very nice project! Thanks!


[HOLD for payment 2023-11-02] [$500] Chat - Reply in thread show on first thread message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @namhihi237
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1697012817574599
Action Performed:

Click FAB button
Click Request money.
Input amount => Next
Select a workspace
Click request
Click request preview
Click. Pay elsewhere on header
Hover on paid message click reply in thread
Hover on first thread message, Observe that the reply in thread icon appears

Expected Result:
The reply in thread icon does not appears on first thread message
Actual Result:
The reply in thread icon appears
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/93399543/f4f2e003-69c6-4a73-b98d-ced8fd216756

Android: mWeb Chrome

https://github.com/Expensify/App/assets/93399543/cadbd0c3-6531-4097-8231-1a03f57fa3a2

iOS: Native

https://github.com/Expensify/App/assets/93399543/430dd1ca-d35b-4d53-808f-73f22687631e

iOS: mWeb Safari

https://github.com/Expensify/App/assets/93399543/8a67ad17-644c-4f75-acdb-3756e88661ef

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/93399543/7185fadd-067c-4f26-9a53-e026ff418e98
https://github.com/Expensify/App/assets/93399543/80642435-4355-4dc1-a6fe-61dfc7acd75e

MacOS: Desktop

https://github.com/Expensify/App/assets/93399543/e905c466-f923-4c1b-bb0b-cfbe215be878

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01b28c57e1c51d2db4
Upwork Job ID:<PHONE_NUMBER>974400512
Last Price Increase: 2023-10-18
Automatic offers:

namhihi237 | Contributor | 27269498
namhihi237 | Reporter | 27269499

Proposal
Please re-state the problem that we are trying to solve in this issue.
The reply in the thread icon does not appear on the first thread message
What is the root cause of that problem?
We have the logic to show the reply icon in the thread here:
https://github.com/Expensify/App/blob/d1ff84b571d365a7c5167a729bdc0ce0888daa41/src/pages/home/report/ContextMenu/ContextMenuActions.js#L128-L131
We have only tested the first message for the report action which is isCommentAction here:
https://github.com/Expensify/App/blob/d1ff84b571d365a7c5167a729bdc0ce0888daa41/src/pages/home/report/ContextMenu/ContextMenuActions.js#L128
But in case we hover on the first IOU message, it does check is first message.
What changes do you think we should make in order to solve the problem?
We should check isThreadFirstChat for the whole thing.
const isCommentAction = reportAction.actionName === CONST.REPORT.ACTIONS.TYPE.ADDCOMMENT
return (isCommentAction || isReportPreviewAction || isIOUAction) && !ReportUtils.isThreadFirstChat(reportAction, reportID);

What alternative solutions did you explore? (Optional)
N/A

Proposal
Please re-state the problem that we are trying to solve in this issue.
The reply in the thread icon does not appear on the first thread message
What is the root cause of that problem?
We didn't check isThreadFirstChat about isIOUAction .
What changes do you think we should make in order to solve the problem?
We need to add checking isThreadFirstChat about isIOUAction .
const isIOUAction = reportAction.actionName === CONST.REPORT.ACTIONS.TYPE.IOU &&
!ReportActionsUtils.isSplitBillAction(reportAction) && !ReportUtils.isThreadFirstChat(reportAction, reportID);

https://github.com/Expensify/App/blob/f5578523a10653b03de827e38f99f3ba54241a69/src/pages/home/report/ContextMenu/ContextMenuActions.js#L130

What alternative solutions did you explore? (Optional)

Couple of proposals ready for review @eVoloshchak

I can't assign @namhihi237 because they need to leave a comment on this issue.

Payment summary:
Reporter + Contributor: @namhihi237 - $800 for reporter role and contributor work to be paid via Upwork ✅
C+: @eVoloshchak to be paid $750 via manual request

The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/24412
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/24412/files#r1383952244
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: it's a fairly simple bug, I don't think an additional discussion is needed

Regression Test Proposal

Create a workspace
Click the FAB button
Click Request Money and select the manual tab
Input amount => Click Next
Select a workspace
Click request
Click Request preview
Click Pay elsewhere on the header
Hover on the paid message and click reply in thread
Hover on the first thread message, Verify that the reply in thread icon does not show

Do we agree 👍 or 👎

Regression steps look good. Proposed in https://github.com/Expensify/Expensify/issues/334067.
We're all done here, thanks everyone.

$750 payment approved for @eVoloshchak based on summary above.


Ensured notebook_extension aborts outside notebook context

This PR ensures that when running the notebook extension outside an IPython context it skips the notebook initialization steps. This allows for a HoloViews notebook which loads the extension to be deployed as a bokeh app.

I think the ip parameter is unnecessary and should be removed. Otherwise, looks good!

Happy to merge when the tests pass.

Looks good and tests are green. Merging.


Put Widget methods in lifecycle order

Fix #377

Okay I couldn't get CI to restart, but I've run the tests on windows manually and I'm satisfied. Thanks!


Enabled quering supported flash modes and setting a flash mode, defining camera preview width and height and captured photo quality

close #34

close #34

any plans to publish a new release?

Yeah, I on it :-)


Update fuel-core version to 0.7.0

fuel-core v0.7.0 is released. To use that we will need to update the following:

fuel-types 0.5
fuel-vm 0.9
fuel-crypto 0.5
fuel-tx 0.10
fuel-asm 0.5

No longer relevant after https://github.com/FuelLabs/sway/pull/1683


allow to pass empty pin set if pinning is not enforced

I want to resolve #8

Improved in #10 based on my changes...


Fix Dependency Issues for Cadence 1.0

make sure all downward dependecies have the stable cadence updates done, so that our feature/stable-cadence branch is updated appropriately.
As discussed, we're going to move flow-cli to v2 for this change, as this would make most sense with the semver guidelines.
The process moving forward would be any updates to feature/stable-cadence we will update to v2, so pre-draft releases will look liike
v2.0.0.stable-cadence.1
v2.0.0.stable-cadence.2
v2.0.0.stable-cadence.3
...
instead of currently where it is
v1.X.stable-cadence
V1.Y.stable-cadence
...

this PR starts the migration of flowkit out of the cli, so that we can have a separate v2 feature branch for stable cadence
https://github.com/onflow/flow-cli/pull/1373


PropertyList cannot be clicked right away from another window

When another window has focus and you click on buttons in the property list, you have to click twice to activate the button.
Seen in v1.4.12

feaedb3 fixes the issue
That is version 1.4.16


Feature Request - Grafana/Prometheus dashboard

Hi @Darkweak ,
Hope you are all well !
I wanted also tyo suggest the creation of grafana dashboard with a prometheus exporter.
For my part, I am using a gin-gonic/prometheus middleware for feeding a grafana dahsboard. It also use a geoip2 middleware for a world map panel.

Ref.

Gin+Prometheus+Geoip: https://github.com/penglongli/gin-metrics/issues/2

Cheers,
Luc Michalski

Possible resources of interest if you pick up this feature:

https://prometheus.io/docs/guides/go-application/
https://github.com/prometheus/client_golang
https://github.com/armon/go-metrics
https://github.com/spacemonkeygo/monkit#metrics

Added to the next release ✌

Available in the 1.5.11 final version.


port: Nat.fib extension for norm_num

@digama0 Here's a port of the Nat.fib extension that we wrote (well, the one that I wrote poorly and that you rewrote from scratch :wink:)

I'm a bit surprised that typechecking takes a relatively large amount of time, and I worry that there's some mistake I've made that's causing the kernel to do too much reduction work.
For example:
-- type checking took 906ms
example : Nat.fib 10000 + Nat.fib 10001 = Nat.fib 10002 := by norm_num1

-- tactic execution of Lean.Parser.Tactic.refl took 1.18s
-- type checking took 1.17s
example : Nat.fib 10000 + Nat.fib 10001 = Nat.fib 10002 := by rfl

At least it's better that rfl, but less than I'd expect.
For comparison, I changed the extension to generate a rfl proof to avoid time spent unifying in the elaborator:
/-- Evaluates the `Nat.fib` function. -/
@[norm_num Nat.fib _]
def evalNatFib : NormNumExt where eval {u α} e := do
  let .app _ (x : Q(ℕ)) ← Meta.whnfR e | failure
  let sℕ : Q(AddMonoidWithOne ℕ) := q(instAddMonoidWithOneNat)
  let ⟨ex, p⟩ ← deriveNat x sℕ
  have y := Nat.fib ex.natLit!
  have ey : Q(ℕ) := mkRawNatLit y
  have pf : Q(Nat.fib $ex = $ey) := (q(Eq.refl $ey) : Expr)
  let pf' : Q(IsNat (Nat.fib $x) $ey) := q(isNat_fib $p $pf)
  return .isNat sℕ ey pf'

-- type checking took 1.27s
example : Nat.fib 10000 + Nat.fib 10001 = Nat.fib 10002 := by norm_num1

As a followup, I defined fib as an axiom, and norm_num can prove Nat.fib 10000 + Nat.fib 10001 = Nat.fib 10002 in 30ms, so somehow the current implementation is causing fib to be reduced by the kernel...

One oddity that seems worth mentioning is that
example : Nat.fib 10000 = Nat.fib 10000 := by norm_num1

is fast (and one can check it does generate the full Nat.fib proofs, it's not just a trivial rfl), but
example : Nat.fib 10000 + 0 = Nat.fib 10000 := by norm_num1

triggers a slow kernel check.

I can confirm that this seems to be a problem with any norm num extension where the kernel reduction is slow. In #3892 I can reproduce
example : Nat.minFac 1277 + 0 = 1277 := by norm_num1 -- slow

(slow means ">8000ms", fast means "<50ms")

Here is a minimal example of something similar, but I'm not sure if it's exactly the same issue. This might be slow in the elaborator, not the kernel.
def A : Nat → Nat → Nat
| 0,     m     => m + 1
| n + 1, 0     => A n 1
| n + 1, m + 1 => A n (A (n + 1) m)
termination_by _ a b => (a, b)

example : A 3 5 + 0 = A 3 5 := rfl -- slow

bors r+


Write step-by-step guide on how to check consensus to be epoch 0.16 compatible

add a docs/epoch-compatibility.md with ## epoch 0.16 headline and description

Step by step buide on how to check consensus to be epoch 0.16 compatible:
Checking Peering between 2 nodes, Sync and Gossiping Blocks/Txs

Check that all elements of the genesis block are equal;
Check that we can connect as peers;
Check that we can gossip transactions between eachother;
Check that we can gossip blocks between eachother;
Check that if one of the nodes is on longer chain, when connected with eachother, the node with short chain will get the longer remote chain (This is done through sync);
Check that if on same height, the more difficult chain will be accepted by the other node (when on a fork, and with same top_block_height, the nodes decide on if their chain is supperior by checking the difficulty);

Checks for serialization for different types of Transactions:
Spend tx:

Create a SpendTx, with specific amount of tokens to send, specific amount of fee, to a specific pubkey;
Add the transaction to the pool
Mine the next block
Get the value of txs_hash key inside the Header
Do the same in Epoch
Get the txs_hash from the block in epoch

If the txs_hash in elixir == txs_hash in epoch, the SpendTx is valid between the two nodes
Naming txs:
TBA..
Oracle txs:
TBA..
Channel txs:
TBA..
@d-velev, @nedelcho-delchev-tues, @Artur64, @cheezus1, @DanielaIvanova
Please everyone related to one of the topics here, fill free to edit my comment and fill the TBA spaces, with information on how to check if we are compatible on this subject with epoch.
If you think that more should be added, fill free to add new checks as well. If you find mistakes, fill free to fix them too.


Add a few more HTTP methods

When writing a program to talk to a restful API, a few more HTTP methods
are needed, e.g.:

PUT to replace a target resource in whole
PATCH to update a target resource
DELETE to delete a target resource

Hmm, it looks like the standard doesn't support other methods used in form submission. Withdrawing the PR.


[mattermost-team-edition] read only file system on start up

While installing the mattermost team edition helm chart on my GKE for the first time, i got a read only file system error without modifying anything :
Error message :
{"level":"error","ts":1563295457.9649801,"caller":"app/config.go:54","msg":"Failed to update config","error":"failed to persist: failed to write file: open /mattermost/config/config.json: read-only file system","errorVerbose":"open /mattermost/config/config.json: read-only file system
**My values.yaml file : **
Image tag
image:
tag: 5.12.1
Persistense for mattermost
persistence:
data:
enabled: true
size: 20Gi
storageClass: standard
accessMode: ReadWriteOnce
Ingress params to access the cluster from outside
ingress:
enabled: true
annotations:
kubernetes.io/ingress.class: nginx
certmanager.k8s.io/cluster-issuer: XXX
hosts:
- XXX
tls:
- secretName: XXX-tls
hosts:
- XXX
Mysql Params
mysql:
enabled: true
mysqlRootPassword: "Password"
mysqlUser: "USer"
mysqlPassword: "Password"
mysqlDatabase: db_name
repository: mysql
tag: 5.7
imagePullPolicy: IfNotPresent
persistence:
enabled: true
storageClass: standard
accessMode: ReadWriteOnce
size: 10Gi
Config File for mattermost
configJSON: {
"ServiceSettings": {
"SiteURL": "XXXX",
"GoogleDeveloperKey": "XXXXX",
"EnablePostUsernameOverride": true,
"EnablePostIconOverride": true,
"EnableLinkPreviews": true,
},
"TeamSettings": {
"SiteName": "XXX",
"EnableCustomBrand": true,
},
"EmailSettings": {
"SendEmailNotifications": true,
"RequireEmailVerification": true,
"SMTPUsername": "XXX",
"SMTPPassword": "XXX",
"EnableSMTPAuth": true,
"SMTPServer": "XXX",
"SMTPPort": "587",
"ConnectionSecurity": "STARTTLS",
"EnableEmailBatching": true,
},
"PluginSettings": {
"Enable": true,
"EnableUploads": true,
}
}

Same issue
│ {"level":"info","ts":1565862568.4581082,"caller":"app/server.go:216","msg":"Current working directory is /mattermost"}                                                                                │ {"level":"info","ts":1565862568.4581385,"caller":"app/server.go:217","msg":"Loaded config","source":"file:///mattermost/config/config.json"}                                                                                │ {"level":"error","ts":1565862568.462423,"caller":"app/config.go:54","msg":"Failed to update config","error":"failed to persist: failed to write file: open /mattermost/config/config.json: read-only file system","errorVerbose":"open /mattermost/config/config.json: read-on  │ ly file system\nfailed to write file\ngithub.com/mattermost/mattermost-server/config.(*FileStore).persist\n\t/go/src/github.com/mattermost/mattermost-server/config/file.go:117\ngithub.com/mattermost/mattermost-server/config.(*commonStore).set\n\t/go/src/github.com/matte  │ rmost/mattermost-server/config/common.go:72\ngithub.com/mattermost/mattermost-server/config.(*FileStore).Set\n\t/go/src/github.com/mattermost/mattermost-server/config/file.go:97\ngithub.com/mattermost/mattermost-server/app.(*Server).UpdateConfig\n\t/go/src/github.com/ma  │ ttermost/mattermost-server/app/config.go:53\ngithub.com/mattermost/mattermost-server/app.NewServer\n\t/go/src/github.com/mattermost/mattermost-server/app/server.go:229\ngithub.com/mattermost/mattermost-server/cmd/mattermost/commands.runServer\n\t/go/src/github.com/matte  │ rmost/mattermost-server/cmd/mattermost/commands/server.go:64\ngithub.com/mattermost/mattermost-server/cmd/mattermost/commands.serverCmdF\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/commands/server.go:53\ngithub.com/mattermost/mattermost-server/vend  │ or/github.com/spf13/cobra.(*Command).execute\n\t/go/src/github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra/command.go:762\ngithub.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra.(*Command).ExecuteC\n\t/go/src/github.com/mattermost/matte  │ rmost-server/vendor/github.com/spf13/cobra/command.go:852\ngithub.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra.(*Command).Execute\n\t/go/src/github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra/command.go:800\ngithub.com/mattermost/mat  │ termost-server/cmd/mattermost/commands.Run\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/commands/root.go:15\nmain.main\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/main.go:30\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:20  │ 0\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1337\nfailed to persist\ngithub.com/mattermost/mattermost-server/config.(*commonStore).set\n\t/go/src/github.com/mattermost/mattermost-server/config/common.go:73\ngithub.com/mattermost/mattermost-server/config.(  │ *FileStore).Set\n\t/go/src/github.com/mattermost/mattermost-server/config/file.go:97\ngithub.com/mattermost/mattermost-server/app.(*Server).UpdateConfig\n\t/go/src/github.com/mattermost/mattermost-server/app/config.go:53\ngithub.com/mattermost/mattermost-server/app.NewS  │ erver\n\t/go/src/github.com/mattermost/mattermost-server/app/server.go:229\ngithub.com/mattermost/mattermost-server/cmd/mattermost/commands.runServer\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/commands/server.go:64\ngithub.com/mattermost/mattermos  │ t-server/cmd/mattermost/commands.serverCmdF\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/commands/server.go:53\ngithub.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra.(*Command).execute\n\t/go/src/github.com/mattermost/mattermost-serv  │ er/vendor/github.com/spf13/cobra/command.go:762\ngithub.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra.(*Command).ExecuteC\n\t/go/src/github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra/command.go:852\ngithub.com/mattermost/mattermost-s  │ erver/vendor/github.com/spf13/cobra.(*Command).Execute\n\t/go/src/github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra/command.go:800\ngithub.com/mattermost/mattermost-server/cmd/mattermost/commands.Run\n\t/go/src/github.com/mattermost/mattermost-server  │ /cmd/mattermost/commands/root.go:15\nmain.main\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/main.go:30\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1337"}                              │ {"level":"info","ts":1565862568.5106914,"caller":"mlog/sugar.go:19","msg":"Scheduling next survey for Sep 5, 2019","plugin_id":"com.mattermost.nps"}

│ {"level":"info","ts":1565862568.4581082,"caller":"app/server.go:216","msg":"Current working directory is /mattermost"}                                                                                │ {"level":"info","ts":1565862568.4581385,"caller":"app/server.go:217","msg":"Loaded config","source":"file:///mattermost/config/config.json"}                                                                                │ {"level":"error","ts":1565862568.462423,"caller":"app/config.go:54","msg":"Failed to update config","error":"failed to persist: failed to write file: open /mattermost/config/config.json: read-only file system","errorVerbose":"open /mattermost/config/config.json: read-on  │ ly file system\nfailed to write file\ngithub.com/mattermost/mattermost-server/config.(*FileStore).persist\n\t/go/src/github.com/mattermost/mattermost-server/config/file.go:117\ngithub.com/mattermost/mattermost-server/config.(*commonStore).set\n\t/go/src/github.com/matte  │ rmost/mattermost-server/config/common.go:72\ngithub.com/mattermost/mattermost-server/config.(*FileStore).Set\n\t/go/src/github.com/mattermost/mattermost-server/config/file.go:97\ngithub.com/mattermost/mattermost-server/app.(*Server).UpdateConfig\n\t/go/src/github.com/ma  │ ttermost/mattermost-server/app/config.go:53\ngithub.com/mattermost/mattermost-server/app.NewServer\n\t/go/src/github.com/mattermost/mattermost-server/app/server.go:229\ngithub.com/mattermost/mattermost-server/cmd/mattermost/commands.runServer\n\t/go/src/github.com/matte  │ rmost/mattermost-server/cmd/mattermost/commands/server.go:64\ngithub.com/mattermost/mattermost-server/cmd/mattermost/commands.serverCmdF\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/commands/server.go:53\ngithub.com/mattermost/mattermost-server/vend  │ or/github.com/spf13/cobra.(*Command).execute\n\t/go/src/github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra/command.go:762\ngithub.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra.(*Command).ExecuteC\n\t/go/src/github.com/mattermost/matte  │ rmost-server/vendor/github.com/spf13/cobra/command.go:852\ngithub.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra.(*Command).Execute\n\t/go/src/github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra/command.go:800\ngithub.com/mattermost/mat  │ termost-server/cmd/mattermost/commands.Run\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/commands/root.go:15\nmain.main\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/main.go:30\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:20  │ 0\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1337\nfailed to persist\ngithub.com/mattermost/mattermost-server/config.(*commonStore).set\n\t/go/src/github.com/mattermost/mattermost-server/config/common.go:73\ngithub.com/mattermost/mattermost-server/config.(  │ *FileStore).Set\n\t/go/src/github.com/mattermost/mattermost-server/config/file.go:97\ngithub.com/mattermost/mattermost-server/app.(*Server).UpdateConfig\n\t/go/src/github.com/mattermost/mattermost-server/app/config.go:53\ngithub.com/mattermost/mattermost-server/app.NewS  │ erver\n\t/go/src/github.com/mattermost/mattermost-server/app/server.go:229\ngithub.com/mattermost/mattermost-server/cmd/mattermost/commands.runServer\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/commands/server.go:64\ngithub.com/mattermost/mattermos  │ t-server/cmd/mattermost/commands.serverCmdF\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/commands/server.go:53\ngithub.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra.(*Command).execute\n\t/go/src/github.com/mattermost/mattermost-serv  │ er/vendor/github.com/spf13/cobra/command.go:762\ngithub.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra.(*Command).ExecuteC\n\t/go/src/github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra/command.go:852\ngithub.com/mattermost/mattermost-s  │ erver/vendor/github.com/spf13/cobra.(*Command).Execute\n\t/go/src/github.com/mattermost/mattermost-server/vendor/github.com/spf13/cobra/command.go:800\ngithub.com/mattermost/mattermost-server/cmd/mattermost/commands.Run\n\t/go/src/github.com/mattermost/mattermost-server  │ /cmd/mattermost/commands/root.go:15\nmain.main\n\t/go/src/github.com/mattermost/mattermost-server/cmd/mattermost/main.go:30\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1337"}                              │ {"level":"info","ts":1565862568.5106914,"caller":"mlog/sugar.go:19","msg":"Scheduling next survey for Sep 5, 2019","plugin_id":"com.mattermost.nps"}

Same issue.  @mehdouch77 @ywang146 have you figured this out?  Any help Mattermost folks?

The problem is that /mattermost/config/config.json is mounted from a secret and is read only.
My workarround was create a new volume for /mattermost/config and create a config.json inside it.
With that I could change the configs on the admin UI,

@kiov  Can you show me your deployment. yaml?
I tried to remounted config. json, but it never started properly<EMAIL_ADDRESS>

Same issue. I added below settings to values.yaml, and then it works.
Note that config.json is perhaps able to be changed on the admin UI, but it would be overwritten when the pod restarts.
Also note that it's insecure because the tokens in config.json are put into the persistent volume.
extraInitContainers:
  - name: copy-config
    image: "alpine:latest"
    imagePullPolicy: IfNotPresent
    volumeMounts:
    - mountPath: /mattermost/config/config.json
      name: config-json
      subPath: config.json
    - mountPath: /mattermost/data
      name: mattermost-data
    command: ["/bin/ash", "-c", "cp -f /mattermost/config/config.json /mattermost/data/config.json"]
extraEnvVars:
  - name: MM_CONFIG
    value: "/mattermost/data/config.json"

Same issue. I added below settings to values.yaml, and then it works.
Note that config.json is perhaps able to be changed on the admin UI, but it would be overwritten when the pod restarts.
Also note that it's insecure because the tokens in config.json are put into the persistent volume.
extraInitContainers:
  - name: copy-config
    image: "alpine:latest"
    imagePullPolicy: IfNotPresent
    volumeMounts:
    - mountPath: /mattermost/config/config.json
      name: config-json
      subPath: config.json
    - mountPath: /mattermost/data
      name: mattermost-data
    command: ["/bin/ash", "-c", "cp -f /mattermost/config/config.json /mattermost/data/config.json"]
extraEnvVars:
  - name: MM_CONFIG
    value: "/mattermost/data/config.json"

I will determine whether to copy according to whether there is a config.json file in the folder /mattermost/data/.
This may temporarily solve the coverage problem  when the pod restarts.
    command: ["/bin/ash", "-c", "if [[ ! -f \"/mattermost/data/config.json\" ]] ;then echo \"copy configJSON\"; cp -f /mattermost/config/config.json /mattermost/data/config.json;else echo \"configJSON exist\"; fi;"]

    extraInitContainers:
    - name: copy-config
      image: "alpine:latest"
      imagePullPolicy: IfNotPresent
      volumeMounts:
      - mountPath: /mattermost/config/config.json
        name: config-json
        subPath: config.json
      - mountPath: /mattermost/data
        name: mattermost-data
      command: ["/bin/ash", "-c", "if [[ ! -f \"/mattermost/data/config.json\" ]] ;then echo \"copy configJSON\"; cp -f /mattermost/config/config.json /mattermost/data/config.json;else echo \"configJSON exist\"; fi;"]
    extraEnvVars:
      - name: MM_CONFIG
        value: "/mattermost/data/config.json"

 {"level":"info","ts":1581544225.523905,"caller":"app/server.go:222","msg":"Loaded config","source":"file:///mattermost/data/config.json"}
│ {"level":"error","ts":1581544225.5526595,"caller":"app/config.go:54","msg":"Failed to update config","error":"failed to persist: failed to write file: open /mattermost/data/config.json: permission denied","errorVerbose":"open /mattermost/data/config.json: permission denied\nf

is the proposed solution working for you?

@masterkain I haven't encountered such an error. Maybe you should check permissions in directory/mattermost/data . And persistence.data.accessMode in values.yaml

    extraInitContainers:
    - name: copy-config
      image: "alpine:latest"
      imagePullPolicy: IfNotPresent
      volumeMounts:
      - mountPath: /mattermost/config/config.json
        name: config-json
        subPath: config.json
      - mountPath: /mattermost/data
        name: mattermost-data
      command: ["/bin/ash", "-c", "if [[ ! -f \"/mattermost/data/config.json\" ]] ;then echo \"copy configJSON\"; cp -f /mattermost/config/config.json /mattermost/data/config.json;else echo \"configJSON exist\"; fi;"]
    extraEnvVars:
      - name: MM_CONFIG
        value: "/mattermost/data/config.json"

 {"level":"info","ts":1581544225.523905,"caller":"app/server.go:222","msg":"Loaded config","source":"file:///mattermost/data/config.json"}
│ {"level":"error","ts":1581544225.5526595,"caller":"app/config.go:54","msg":"Failed to update config","error":"failed to persist: failed to write file: open /mattermost/data/config.json: permission denied","errorVerbose":"open /mattermost/data/config.json: permission denied\nf

is the proposed solution working for you?

Hi, are you using the "old" version 5.13.2? The latest one is not run under the root but unter the mattermost user (2000:2000) and default persistenVolume mount permission are root:root

@simonxlh @kissi7 I think I'm using release-5.17, will try adjusting for the new mattermost user, thanks for the hints

To make the above work with the latest version, change the command to set file owner like so:
    command: ["/bin/ash", "-c", "if [[ ! -f \"/mattermost/data/config.json\" ]] ;then echo \"copy configJSON\"; cp -f /mattermost/config/config.json /mattermost/data/config.json && chown 2000:2000 /mattermost/data/config.json;else echo \"configJSON exist\"; fi;"]

Any updates on this?

using mattermost/mattermost-team-edition:5.31.0 I can't start the pod. tested some command as you can be see below with the same results.
│ Error: failed to load configuration: failed to create store: unable to load on store creation: failed to persist: failed to write file: open /mattermost/data/config.json: permission denied

    extraInitContainers:
    - name: copy-config
      image: "alpine:latest"
      imagePullPolicy: IfNotPresent
      volumeMounts:
      - mountPath: /mattermost/config/config.json
        name: config-json
        subPath: config.json
      - mountPath: /mattermost/data
        name: mattermost-data
      # command: ["/bin/ash", "-c", "if [[ ! -f \"/mattermost/data/config.json\" ]] ;then echo \"copy configJSON\"; cp -f /mattermost/config/config.json /mattermost/data/config.json;else echo \"configJSON exist\"; fi; chown 2000:2000 /mattermost/data/config.json; chgrp 2000 /mattermost/data/config.json; "]
      command: ["/bin/ash", "-c", "if [[ ! -f \"/mattermost/data/config.json\" ]] ;then echo \"copy configJSON\"; cp -f /mattermost/config/config.json /mattermost/data/config.json && chown 2000:2000 /mattermost/data/config.json;else echo \"configJSON exist\"; fi;"]
      # command: ["/bin/ash", "-c", "cp -f /mattermost/config/config.json /mattermost/data/config.json"]
    extraEnvVars:
      - name: MM_CONFIG
        value: "/mattermost/data/config.json"

any hint?

using mattermost/mattermost-team-edition:5.31.0 I can't start the pod. tested some command as you can be see below with the same results.
│ Error: failed to load configuration: failed to create store: unable to load on store creation: failed to persist: failed to write file: open /mattermost/data/config.json: permission denied

    extraInitContainers:
    - name: copy-config
      image: "alpine:latest"
      imagePullPolicy: IfNotPresent
      volumeMounts:
      - mountPath: /mattermost/config/config.json
        name: config-json
        subPath: config.json
      - mountPath: /mattermost/data
        name: mattermost-data
      # command: ["/bin/ash", "-c", "if [[ ! -f \"/mattermost/data/config.json\" ]] ;then echo \"copy configJSON\"; cp -f /mattermost/config/config.json /mattermost/data/config.json;else echo \"configJSON exist\"; fi; chown 2000:2000 /mattermost/data/config.json; chgrp 2000 /mattermost/data/config.json; "]
      command: ["/bin/ash", "-c", "if [[ ! -f \"/mattermost/data/config.json\" ]] ;then echo \"copy configJSON\"; cp -f /mattermost/config/config.json /mattermost/data/config.json && chown 2000:2000 /mattermost/data/config.json;else echo \"configJSON exist\"; fi;"]
      # command: ["/bin/ash", "-c", "cp -f /mattermost/config/config.json /mattermost/data/config.json"]
    extraEnvVars:
      - name: MM_CONFIG
        value: "/mattermost/data/config.json"

any hint?

Here is the config change to do to have it working:
extraEnvVars:
  - name: MM_CONFIG
    value: "/mattermost/data/config.json"

extraInitContainers:
  - name: copy-config
    image: "alpine:latest"
    imagePullPolicy: IfNotPresent
    volumeMounts:
    - mountPath: /mattermost/config/config.json
      name: config-json
      subPath: config.json
    - mountPath: /mattermost/data
      name: mattermost-data
    command: ["/bin/ash", "-c", "if [[ ! -f \"/mattermost/data/config.json\" ]] ;then echo \"copy configJSON\"; cp -f /mattermost/config/config.json /mattermost/data/config.json && chown 2000:2000 /mattermost/data/config.json;else echo \"configJSON exist\"; fi;"]

Nothing new from previous posts, just gathered the solutions provided.
It is a hack though, and the chart needs a fix to have 5.30+ working out of the box. (wink wink maintainers <3)


[DDW-1000] Integrate legacy wallet transactions list V2 API endpoint

This PR introduces the Legacy Wallet transactions list API V2 endpoint.
Todos

[x] Display UNRESOLVED transaction inputs
[x] Japanese Translations for UNRESOLVED transaction inputs

Screenshots
No Addresses

Unresolved addresses

Testing Checklist

Slack QA thread

**NOTE: **
It is not possible to test Legacy wallet transactions because we don't have wallet with transactions
1. Test Storybook stories

[ ] Test Storybook story under: WalletTransactionsList -> transactions with unresolved income addresses
[ ] Test Storybook story under: WalletTransactionsList -> transactions without income addresses

2. In-App testing

[ ]  Transactions without income addresses

Run yarn v2-api-importer to get wallets with funds

Check transaction details on one off wallets and From address should be: No Addresses

[ ]  Transactions with unresolved income addresses

Run yarn v2-api-importer to get wallets with funds

Create Test Wallet

Send ADA from one of imported wallets to Test Wallet

Check Test Wallet transaction details and From address should be: Open this transaction in Cardano explorer link.

Review Checklist
Basics

[ ] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance and unit tests are passing (yarn test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[ ] There are no flow errors or warnings (yarn flow:test)
[ ] There are no lint errors or warnings (yarn lint)
[ ] There are no prettier errors or warnings (yarn prettier:check)
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

@daniloprates please review this one 🙏

@tomothespian The font sizes/styles look different between 1, 2 & 3:

@tomothespian In the minimum resolution, the word "Addresses" is split:

@tomothespian The font sizes/styles look different between 1, 2 & 3:

@gnpf this is how is defined in designs:
https://zpl.io/adl6D1a

my bad... sorry
will fix it in a moment

@tomothespian code changes look good and everything works good.
Please check the comments from @gnpf AND make sure the fonts are correctly rendered.
This is very important as the row heights have to be exactly the same since we have that virtual list rendering here. If you look more closely when toggling expanded/collapsed transaction state you can see that there is some hickups with the rendering of the expanded transaction size - as if it first renders with height X and then in the next second decreases in size to X-10px or so.
 It would be great if you can show me on call

https://zpl.io/adl6D1a - updated this screen
(you can view last 3 versions to see that the latest one is more balanced, even it has some strange font size)

@tomothespian In the minimum resolution, the word "Addresses" is split:

@gnpf this one is done

@gnpf @a-rukin styles updated! Can you please check again.


Font in hover for custom trees is too large

Please see the screenshot below

@Tyriar in case you have any suggestions for what to do here.
@misolori I think the font size in the hover is consistent with the font size in all hovers. I'm not sure how to reconcile that with the tree font size.

@alexr00

I'm not sure how to reconcile that with the tree font size.

I haven't described my perception correctly, my perception is less that the font size is not aligned with the font size of the tree item. My perception is that the font of the issue hover description is too large. The description in a Code hover appears to use a smaller font. Therefore I suggest to use the same font size as in the code hover.

Duplicate of https://github.com/microsoft/vscode/issues/107278?

Yes, duplicate of https://github.com/microsoft/vscode/issues/107278, thanks!


Converting CSHARP-OOPROC sample to modern ASP.NET with styles

We'd like to show this new AI repo + samples using the more modernized ASP.NET (core) syntax.

Updated HTTP triggers to use IActionResult return types
In (tuple) multiple return/output type applying [HttpResult] attribute on HTTP IActionResult
Attempting to use [FromBody] model binding instead of Deserialize on json [NOT YET WORKING]
Removing all static's which is more ILogger and DI friendly
Styles with https://csharpier
Updating package references in .csproj to the latest SDK and Worker package versions that understand [HttpResult]

    <PackageReference Include="Microsoft.Azure.Functions.Worker" Version="1.22.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.2.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore" Version="1.3.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.17.3-preview2" />

Any idea @mattchenderson or @fabiocav why [FromBody] returns a null body object of type EmbeddingsRequest, but if I deserialize myself it is ok?

@paulyuk , @aishwaryabh has made changes for ASP .NET Core for all dotnet isolate samples,
Can you please check latest of main and if we can discard this PR now?

Closing this PR as Aishwarya already updated the samples for ASP .Net Core style.


Explicitly return empty array for no pods in Daemon Sets

What?

Resolves https://github.com/Shopify/kubernetes-deploy/issues/160
find_pods was previously returning nil when no latest_pods were found
This PR explicitly returns an empty array []

cc/ @wvanbergen @KnVerey

Thanks!


Peer Review - Pilot IITB Standard on Product Mgt

[ ] 1st Review
[ ] 2nd Review
[ ] Final Review

duplicate of #1958


⚠ Bofrost.be has degraded performance

In 2b88ea7, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1199 ms

Resolved: Bofrost.be performance has improved in a322b22 after 6 minutes.


fix(analytics): add missing usage events causing warning in logs

Not having this was causing logs like this in gms which caused confusion.
INFO  c.l.m.k.t.DataHubUsageEventTransformer:74 - Invalid event type: HomePageViewEvent
WARN  c.l.m.k.DataHubUsageEventsProcessor:56 - Failed to apply usage events transform to record: ...

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Expected to fail with ManuallyCreateLineageEvent being missing

Code check did fail https://github.com/datahub-project/datahub/actions/runs/3989112410/jobs/6841138499 with
Missing {'ManuallyCreateLineageEvent'} from DataHubUsageEventType.java. Please add

Added it now. So should pass now.

Code check passed now https://github.com/datahub-project/datahub/actions/runs/3989151394/jobs/6841229205
Passed

Tested on local and don't see the warning showing up anymore in gms logs.

Work on fixing the failing cypress is being done in https://github.com/datahub-project/datahub/pull/7116


Can we get info about the number of times a statement is executed in xml reports?

I'd like accurate hit counts in the xml export. Currently the hits value can only be a zero or one, representing whether the line was executed instead of how many times.
I'm specifically speaking about this section of the code:
https://github.com/nedbat/coveragepy/blob/5a94109e646870aef6188de25ba314f73fa1245d/coverage/xmlreport.py#L213
            # Q: can we get info about the number of times a statement is
            # executed?  If so, that should be recorded here.
            xline.setAttribute("hits", str(int(line not in analysis.missing)))

Can we get that info? It looks like this segment of code was written 14 years ago, so I'm hoping it is now possible.

I'm sorry, but coverage.py still doesn't collect information about the number of times a line is run. See #669.


Fix package for non Linux systems

This is a fix for using the package on Windows and MacOS

Replace timeout package.
Make RInChI code work on Windows.
Disable RInChI support for MacOS

This solves issue #1

@marcosfelt  - FYI


extract_feature_v1.py. I think there is a missing l2_norm in line 75.

Hi.
while idx + batch_size <= len(loader.dataset):
            batch, _ = iter(loader).next()
            if tta:
                fliped = hflip_batch(batch)
                emb_batch = backbone(batch.to(device)).cpu() + backbone(fliped.to(device)).cpu()
                features[idx:idx + batch_size] = l2_norm(emb_batch)
            else:
      75:          features[idx:idx + batch_size] = backbone(batch.to(device)).cpu()
            idx += batch_size

        if idx < len(loader.dataset):
            batch, _ = iter(loader).next()
            if tta:
                fliped = hflip_batch(batch)
                emb_batch = backbone(batch.to(device)).cpu() + backbone(fliped.to(device)).cpu()
                features[idx:] = l2_norm(emb_batch)
            else:
                features[idx:] = l2_norm(backbone(batch.to(device)).cpu())

Line 75 seems to have missing l2_norm as the other 3 cases have.
I'd thank an explanation why l2_norm is necessary. If the aim is to search in the database who that person is, normalizing doesn't seem a good idea.
Thanks.

Hi.
while idx + batch_size <= len(loader.dataset):
            batch, _ = iter(loader).next()
            if tta:
                fliped = hflip_batch(batch)
                emb_batch = backbone(batch.to(device)).cpu() + backbone(fliped.to(device)).cpu()
                features[idx:idx + batch_size] = l2_norm(emb_batch)
            else:
      75:          features[idx:idx + batch_size] = backbone(batch.to(device)).cpu()
            idx += batch_size

        if idx < len(loader.dataset):
            batch, _ = iter(loader).next()
            if tta:
                fliped = hflip_batch(batch)
                emb_batch = backbone(batch.to(device)).cpu() + backbone(fliped.to(device)).cpu()
                features[idx:] = l2_norm(emb_batch)
            else:
                features[idx:] = l2_norm(backbone(batch.to(device)).cpu())

Line 75 seems to have missing l2_norm as the other 3 cases have.
I'd thank an explanation why l2_norm is necessary. If the aim is to search in the database who that person is, normalizing doesn't seem a good idea.
Thanks.

Thank you. We have updated accordingly:)


Jesse: Watch statelike.com.pk

Jesse requests the watch of the watch_keyword statelike\.com\.pk. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

statelike\.com\.pk has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Rejected by Jeff Schaller in Charcoal HQ. Reason: 'typo; correct one is in #9547'


Check for errors on updating conditions in the controller

This issue is a continuation of https://github.com/kubernetes-incubator/service-catalog/pull/923/files#r121129995
cc/ @derekwaynecarr

I am taking this one