Lost journal entries on move + kill buffer

Hi,
I'm using org-journal on spacemacs and wanted to share a cautionary tale :)
I just happened to lose a few TODO entries that had been moved from the previous day after killing the new buffer. Unfortunately I assumed I was just throwing away a new entry that I didn't care about anyway.
Maybe org-journal could save me from myself, next time? Perhaps this could be done by saving the buffer to today's file (or some other backup place) immediately if it had to move TODO entries...

Good point, and I am very sorry that you lost data! This actually happened to me a few times, too, but never lead to data loss, since I always had some form of backup.
This happens mostly because org-journal preserves the buffer-modified flag even if it adds a new entry. I don't know why I built it that way, but I removed this functionality in the latest commit.
Now, creating a new entry (or moving TODOs) should mark the buffer as modified, and Emacs should prompt you to save it if you close it without saving.
Can you verify that this solves your problem?

I did get a notification that the buffer was modified, but I killed it anyway. In my case I'd pr

I am not sure this is something I am comfortable doing. If the user saved his journal a while ago, then edited something, then created a new journal entry, s/he would expect the file to still be unsaved. I don't want to mess with these basic Emacs concepts.
However, you can actually fix this particular problem yourself by (add-hook 'org-journal-after-entry-create-hook save-buffer). This should call save-buffer, whenever a new journal entry is created.

I agree that "save on new entry" is backwards, and I don't think that's what I really need. Rather, my (unusual) use-case seems to require a "save on new file" hook. Is such a thing available? I wouldn't mind adding this to my config file somewhere.

I took a quick look at org-journal-new-entry and was thinking whether the hook function for org-journal-after-entry-create-hook can do it?
My elisp is still on copy-paste-modify level and I don't quite understand how everything works, so here's a handwavy plan that may or may not make sense:
A bit before (run-hooks 'org-journal-after-entry-create-hook) you check whether you should call org-journal-carryover. If it were possible to externally use that same predicate (?), (when (and new-file-p org-journal-carryover-items) ...), I could conditionally save the buffer.

Since org-journal is dynamically scoped, I believe that new-file-p is visible from within the hook. So you should be able to do something like (add-hook 'org-journal-after-entry-create-hook (lambda () (when new-file-p (save-buffer)))). (I haven't tested this, though)

Ok, so I reproduced the issue today, being careful to make a backup of yesterday's file this time to try it multiple times. I do not get the save-before-quit notification (I must have only gotten it the first time due to having created an entry that I later didn't care about), so the fix from your first comment is definitely important (I haven't tested it though).
I also added the hook with the conditional save and it does work fine, so thanks for that as well.

I would be grateful if you could test for the save-before-quit notification, as that seems to be a useful feature ;-)

I would be happy to, just have to figure out how to tell spacemacs to look for org-journal somewhere else. My first attempt changing packages.el was unsuccessful, though.
Will try later today, possibly.

Tried it, works fine: new entries (regardless of new file or not) change the buffer modified flag.

Cool, thank you!


DBAAS1-73: Route / component scaffolding

Description
Add routes and placeholder pages/components for

cloud.linode.com/databases
cloud.linode.com/databases/create
cloud.linode.com/databases/{id} (redirects to /summary)
cloud.linode.com/databases/{id}/summary
cloud.linode.com/databases/{id}/backups
cloud.linode.com/databases/{id}/settings

How to test
Test the urls while toggling the flag.

@DevDW I just checked a bunch of tabs and it seems like that's a problem for all of the components that use <SafeTabPanel /> vs <NavTabs /> so I'll create a separate ticket to address this


Support Django >= 1.10

Fix get_field_by_name, get_all_related_objects, get_all_related_many_to_many_objects for Django >= 1.10

@ivlevdenis these changes are awesome, thanks for working on them! I haven't worked with 1.10 yet but I'm excited to try it out.
It looks like there are some merge conflicts, most likely with this recently merged PR that added DRF 3.4 compatibility: https://github.com/AltSchool/dynamic-rest/pull/120.
Please pull in the changes from #120 and update the compatibility table in README.md to reflect support for 1.10.

Looks great!


Meilisearch does not respect --max-indexing-memory argument

Describe the bug
The Meilisearch process is killed by Linux kernel (Out of memory) because uses a lot of memory. Even using  --max-indexing-threads and --max-indexing-memory arguments (or config) the process uses more memory than the specified. We set 100MB and grows up to 600-700MB.
To Reproduce
Steps to reproduce the behavior:

Use a Linux VPS/VM with 1 CPU and 2GB of RAM (we use Debian 11)
Run ./meilisearch-linux-amd64 --log-level=debug --max-indexing-threads=1 --max-indexing-memory=104857600
Add documents (we have ~10.000 records, ~75MB of plain text)
Wait for documents to be indexed
See the Killed output

Expected behavior
Process not being killed
Meilisearch version:
v1.0.2, v1.1.1
Additional context
Meilisearch debug output:
[2023-05-04T11:51:12Z DEBUG index_scheduler::batch] update: MergeDataIntoFinalDatabase { databases_seen: 6, total_databases: 12 }
[2023-05-04T11:51:12Z DEBUG index_scheduler::batch] update: MergeDataIntoFinalDatabase { databases_seen: 7, total_databases: 12 }
[2023-05-04T11:51:12Z DEBUG index_scheduler::batch] update: MergeDataIntoFinalDatabase { databases_seen: 8, total_databases: 12 }
[2023-05-04T11:51:12Z DEBUG TimerFinished] WordsPrefixesFst::execute(), Elapsed=74.215858ms
[2023-05-04T11:51:12Z DEBUG index_scheduler::batch] update: MergeDataIntoFinalDatabase { databases_seen: 9, total_databases: 12 }
[2023-05-04T11:51:12Z DEBUG milli::update::index_documents::helpers::grenad_helpers] Writing MTBL sorter...
[2023-05-04T11:51:13Z DEBUG milli::update::index_documents::helpers::grenad_helpers] MTBL sorter writen in 684.22ms!
[2023-05-04T11:51:13Z DEBUG TimerFinished] WordPrefixDocids::execute(), Elapsed=821.728114ms
[2023-05-04T11:51:13Z DEBUG milli::update::index_documents::helpers::grenad_helpers] Writing MTBL sorter...
[2023-05-04T11:51:13Z DEBUG milli::update::index_documents::helpers::grenad_helpers] MTBL sorter writen in 117.05µs!
[2023-05-04T11:51:13Z DEBUG TimerFinished] WordPrefixDocids::execute(), Elapsed=1.085624ms
[2023-05-04T11:51:13Z DEBUG index_scheduler::batch] update: MergeDataIntoFinalDatabase { databases_seen: 10, total_databases: 12 }
[2023-05-04T11:51:13Z DEBUG milli::update::prefix_word_pairs::word_prefix] Computing and writing the word prefix pair proximity docids into LMDB on disk...
[2023-05-04T11:51:21Z DEBUG TimerFinished] index_word_prefix_database(), Elapsed=8.591115147s
[2023-05-04T11:51:21Z DEBUG milli::update::prefix_word_pairs::prefix_word] Computing and writing the word prefix pair proximity docids into LMDB on disk...
[2023-05-04T11:51:26Z DEBUG TimerFinished] index_prefix_word_database(), Elapsed=4.967866167s
[2023-05-04T11:51:26Z DEBUG TimerFinished] WordPrefixPairProximityDocids::execute(), Elapsed=13.568378347s
[2023-05-04T11:51:26Z DEBUG index_scheduler::batch] update: MergeDataIntoFinalDatabase { databases_seen: 11, total_databases: 12 }
[2023-05-04T11:51:26Z DEBUG milli::update::words_prefix_position_docids] Computing and writing the word levels positions docids into LMDB on disk...
Killed

Debian log output:
May 04 11:51:30 vps kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/session-144716.scope,task=meilisearch-lin,pid=2406696,uid=1000
May 04 11:51:30 vps kernel: Out of memory: Killed process 2406696 (meilisearch-lin) total-vm:2170918328kB, anon-rss:766100kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:3108kB oom_score_adj:0
May 04 11:51:30 vps systemd[1]: session-144716.scope: A process of this unit has been killed by the OOM killer.

Hello @vaites
Sorry for the issue. This is something we are aware of. Indeed, Meilisearch needs to use at least some memory to work and it's hard to limit it. We are working on it (https://github.com/meilisearch/meilisearch/pull/3651).
I discussed with our tech lead @Kerollmops and here is what you can try

use --max-indexing-memory 0 -> Meilisarch will allocate the minimal memory possible
if it still does not work, you can increase the size of your machine (more than 2Gb or RAM), and still use --max-indexing-memory -0

Also, do you use geosearch in your document (add documents with _geo filed)?
Thanks in advance for your answer, and sorry again for the issue

Thanks @curquiza, will try setting zero as indexing memory and see how far it grows.
Anyway, we are not using geosearch. Just plain text and some integers for filters.

We used zero as memory limit and the RAM consumption is lower than before, but still grows to about 400-500MB.
I know that the issue can be complex to solve, and I noticed an advice on docs: It is possible that Meilisearch goes over the exact RAM limit during indexing., so I think there's no more option than get more RAM.
Close the issue if you want, and thanks for your help!

Thanks for your feedback @vaites, really appreciated.
We let it open so far, because it's still an issue, even if it's not something we can easily solve.

Ping from triage

Workarounds exist:

Workaround 1:  --max-index-memory 0 will work
Workaround 2: use the experimental flag --experimental-reduce-indexing-memory-usage drastically reduces RAM usage so that it is closer to --max-indexing-memory.

Size extra large, plus ongoing maintenance work to keep this true.

Thanks @dureuill, will try the experimental flag on our testing environment.

Hello people following this issue
We are going to release v1.7.0 which should fix a lot of issues with crashes due to memory consumption. You can already test the first release candidate (rc0), and later, the official release (11th March)
I close this issue in favor of https://github.com/meilisearch/meilisearch/issues/4393 which has more information and more investigation started on it.


Display Toasts / Notifications in-app

Problem
As a user, I want to use Formbricks targeting logic to display a toast (information banner) in-app to specific segments.
Solution
Formbricks is well positioned to display toasts as they are pretty much forms without inputs ;) Since teams already have Formbricks included, we should enable them to display a toast as well.
Tasks

Market Research: Research "Toast" experiences other tools offer
Do 1 user interview with a founder who requested this feature :)
Create Wireframes, discuss with Kristian and myself
Scope it & hand over to dev

Thanks a lot! :))

Hello i would like to take this up

we put this on hold bc we we'll cover this functionality in the upcoming app store


Revamp the contact us page

The "Contact Us" page needs improvement in terms of its appearance. We can enhance it by applying attractive CSS styles and reorganizing its layout. A straightforward approach would be to create a clear header at the top, followed by the contact form, and finish with a visually appealing footer.

assigned @prernadabi23


The same result for all the attributes.

As written in the title, I  obtain a row of the same images without any changes regardless to the attribute (column). I use custom data-set organized as RaFT.  Could you give an advise, what may cause it?

My result is the same and I just changed the attri_list_celeba.txt. May I ask have you solve it?

@SummerHuiZhang No, it is still the problem.

Same issue here--have you two (@acecreamu, @SummerHuiZhang) had any luck running the test script? Or same results?

@James-Oldfield Yes, if I understood your question correctly.
--mode train --rafd_image_dir data/train

did you solve this problem?
I'm having the same problem. Can please share a solution with me?
Thanks


[VS] PowerShell support

Product and Version [VS/VSCode]: VS
Target Platform or Language [e.g. Node.js]: PowerShell
Steps to Reproduce / Scenario:
Add PowerShell support to Visual Studio Intellicode

Normalizing labels

Any plans on implementing this?

Tagging @StevenBucher98

Powershell team have actually added command and parameter name completion... along with a host of other features:
https://learn.microsoft.com/en-us/powershell/scripting/learn/shell/tab-completion?view=powershell-7.3#built-in-tab-completion-features


Issue 160

Readded closeOnConfirm option.

There's no need in reverting this parameter, #160 can be solved without it: https://limonte.github.io/sweetalert2/#chaining-modals


Item Creation needs to be modified to adhere to 0.8.x

Relating to #441 and #442

Modified in 3.3.0


Added Xcode 11 (Swift 5) support

No the project builds with Xcode 11. Next step will be some modifications to support Dark Mode (iOS 13)

Thanks Patrick


Samsung TV Screen mirroring crashing after trying to use it with SecondScreen

After trying out SecondScreen 2.9.2 with a Samsung UE55F8090SL 139,7 cm (55 Zoll) Full HD Smart-TV via its Screen Mirroring functionality, it does not work anymore without SecondScreen also.
I have used the default profile, using 1920x1080 with 240dpi (not sure if the DPI matches).
The crash happens right after the Screen Cast connection is established, and the TV just says the connection is ended ("Screen Mirroring wurde beendet" in German).
Android still displays the cast icon from the Wfd service for several seconds then.
It looks more like a bug with the TV than SecondScreen of course, but I wonder what might have caused this: is the TV in an unhappy state now after some unsupported DPI was tried on it? Wouldn't only the resolution matter after all?
And since this keeps happening after having uninstalled SecondScreen, and not having used autostart since the initial failure, I wonder if there is some state/setting changed in Android that might still cause it to crash like that.
I am using Android 10, and have tried it after rebooting both the phone and the TV.
I have not yet tested it with another phone/device, but it was working just before trying out SecondScreen, which I wanted to use for improving the mirroring experience.

I have found that I can work around the issue by not using "Auto" for the advanced "Operating channel" Cast setting (to be enabled in developer settings, "Wireless display certification"). Using channel 1, 6, or 11 makes it work.
Using 36 does not work in some different way, and it says that it needs to disconnect from the main wifi there.
So the crash/issue appears to be with the Auto mode there then.
But it worked previously, and also still with another Android device, where SecondScreen has not been used.

It's also notable that the TV did not show up in the main window (opened from the quick settings icon), but only when going to settings from there. It was just scanning there.
After having connected via a changed/manual channel the setting is back to Auto, and also the TV shows up in the main/initial window again, where it works from now, apparently also in Auto mode again.
Therefore likely some (advanced) setting in this regard was still changed/wrong after uninstalling SecondScreen maybe, which appears now to be fixed again.
Feel free to close the issue, but I would be happy to know what might have happened here, and even more if that was/is an actual bug in SecondScreen, that can / has been fixed.

FWIW, after a reboot it still crashed now, but was available from the initial/main scanning screen. Going to settings and chosing an explicit channel could be used to work around it again.
It might be totally unrelated to SecondScreen, but pointers to settings that it changes and might have an impact here would be appreciated.


Fix For Reversed Motor Problems

We are copying the motor type information from DcMotorEx to the PhotonDcMotor

Should the same be done for servos?

We didn't see this issue with the servos. We can pass in a ServoType to the constructor, but we couldn't find a way to extract the existing ServoType from the original servo.

When will this be merged?


adapt for apparent new API version

I had to make some changes to make it work with the API that I was seeing.
It looks like they changed requests where you passed _method to that associated HTTP request.

Thank you for your work. Can we put this version on another branch? Reason is, I am not sure it will be backwards compatible. The current code works well with my setup and I am not sure if it will work if I use clientkey and the headers. I really don't have time to work on it currently to check. I am also worried that it will break the support for covers and switches.
I wonder why the API is different - we may need code that works for both the old and new API and should have a way to determine which one to use. What version is your gateway?
You obviously also made a lot of changes to make the code more efficient, like passing the 'config' as is and not unnecessarily breaking it down to different variables as I did (you can see I have very limited programing skills), but this also makes it harder for me to see which changes are related to making the code efficient and which changes actually change the way the code works. I will just need more time to look through.

You did an outstanding job for someone with "very limited programming skills" !
Absolutely, we can put this on another branch.  I just wanted to submit it for reference if someone else comes along.
I'd imagine there are parameters you're passing (like the JS client version) that tell the API to act differently.
Day two and it's still operating perfectly.


build: update TypeScript configuration

This Pull Request fulfills the following requirements:

[x] The commit message follows our guidelines.
[x] Tests for the changes have been added if needed.
[x] Does not affect documentation or it has been added or updated.
[x] Does not introduce cycles into the flow of execution.

Pull Request Test Coverage Report for Build 259974046

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 259967429:
0.0%

Covered Lines:
76

Relevant Lines:
76

💛  - Coveralls


ketcher.getSmiles() return error！

ketcher.getSmiles()  return [object Promise]！

@suzhouhu ,
ketcher.get*() methods return Promise as expected. If you  want to get SMILES string it is necessary to wait while promise is finished:
ketcher.getSmiles().then(result => console.log(result))
Regards,
Ketcher team

Thank you very much
发自我的iPhone
------------------ Original ------------------
From: Andrei Mazol @.>
Date: Wed,May 25,2022 8:38 PM
To: epam/ketcher @.>
Cc: 刘鹄中 @.>, Mention @.>
Subject: Re: [epam/ketcher] ketcher.getSmiles() return error！ (Issue #1645)
@suzhouhu ,
ketcher.get*() methods return Promise as expected. If you  want to get SMILES string it is necessary to wait while promise is finished:
ketcher.getSmiles().then(result => console.log(result))
Regards,
Ketcher team
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Missing BuildVer local variable file

The variables.var file is referenced in the program package, but missing from the commit

Yes, it is intentionally defined in the package file - thought not actually present in the package, resulting in a "missing" icon.
On the very first build with pre-build script, the Variables.var file is generated correcting the icon.
As soon as the var file is added to this repository, it will be tracked regardless of the ignore. We could use custom configuration settings, but this would be required by every collaborator. I would say we could add the var file to the release download, but I would like more feedback before adding it to the repo.

Thanks for the feedback.  First compile I had an AS build error due to this missing var file.  This probably means my script did not successfully complete and generate the file.  Since then, I'm unable to reproduce any problems with the script, and the var file is properly generated  (even if I remove it from the directory before build).


With the release of jackson-jr record deserialisation should be available and therefore manual mapping should not be necessary

The QueryClient#toSearchResponse() should not be manually mapping the values anymore and could use records instead.
The project uses jackson-jr 2.18 already. The issue is resolved here: https://github.com/FasterXML/jackson-jr/issues/162

Hii @Giovds, I have solved this issue in my local, all the tests are passing. Can u pls assign me the task. Attaching Snapshot for better understanding :
Changes

Tests

Resolved with #62


Automatically show info in xp tracker

The skills in the Xp Tracker can be initialize with the StatsPanel already open and toggle that feature with a button in the Xp Tracker config

I think this will be solved in #1419

OK, I'm actually getting trigger every time i opened the xp tracker. if #1419 will solved it is fine, if not, this request will solve my (and certainly many other people) problem with the xp tracker.


[firebase_auth] no SMS arrives on iOS 13

When I try verify number :
await FirebaseAuth.instance.verifyPhoneNumber(
phoneNumber: "+$phoneNumber",
timeout: const Duration(seconds: 30),
verificationCompleted: verificationCompleted,
verificationFailed: verificationFailed,
codeSent: codeSent,
codeAutoRetrievalTimeout: codeAutoRetrievalTimeout);
On iPhone 8 + (iOS 13) I get AuthException: verifyPhoneNumberError Invalid token.
But it worked 2 days ago.
On Android it works well.
/Users/ivanonishchenko/repos/flutter/bin/flutter doctor --verbose
[✓] Flutter (Channel beta, v1.10.7, on Mac OS X 10.15.1 19B88, locale en-RU)
• Flutter version 1.10.7 at /Users/ivanonishchenko/repos/flutter
• Framework revision e70236e36c (5 weeks ago), 2019-10-02 09:32:30 -0700
• Engine revision 9e6314d348
• Dart version 2.6.0 (build 2.6.0-dev.0.0<PHONE_NUMBER>)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/ivanonishchenko/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• ANDROID_HOME = /Users/ivanonishchenko/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.2, Build version 11B52
• CocoaPods version 1.8.4
[✓] Android Studio (version 3.5)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 41.0.2
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
[✓] Connected device (1 available)
• SM G9730 • R28M31YDE3M • android-arm64 • Android 9 (API 28)
• No issues found!
Process finished with exit code 0

Hi @IvanOnishchenko
can you please provide your flutter run --verbose ?
Thank you

Hi @iapicca
flutter run --verbose
[  +31 ms] executing: [/Users/ivanonishchenko/repos/flutter/] git -c log.showSignature=false log -n 1
--pretty=format:%H
[  +93 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] e70236e36ce1d32067dc68eb55519ec3e14b6b01
[        ] executing: [/Users/ivanonishchenko/repos/flutter/] git describe --match v*.. --first-parent
--long --tags
[ +137 ms] Exit code 0 from: git describe --match v*.. --first-parent --long --tags
[   +2 ms] v1.10.7-0-ge70236e36
[   +8 ms] executing: [/Users/ivanonishchenko/repos/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +18 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/beta
[        ] executing: [/Users/ivanonishchenko/repos/flutter/] git ls-remote --get-url origin
[  +12 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +69 ms] executing: [/Users/ivanonishchenko/repos/flutter/] git rev-parse --abbrev-ref HEAD
[  +24 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] beta
[   +7 ms] executing: sw_vers -productName
[  +37 ms] Exit code 0 from: sw_vers -productName
[        ] Mac OS X
[        ] executing: sw_vers -productVersion
[  +19 ms] Exit code 0 from: sw_vers -productVersion
[        ] 10.15.1
[        ] executing: sw_vers -buildVersion
[  +23 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 19B88
[  +32 ms] executing: /usr/bin/xcode-select --print-path
[  +18 ms] Exit code 0 from: /usr/bin/xcode-select --print-path
[        ] /Applications/Xcode.app/Contents/Developer
[   +1 ms] executing: /usr/bin/xcodebuild -version
[+1010 ms] Exit code 0 from: /usr/bin/xcodebuild -version
[        ] Xcode 11.2
Build version 11B52
[  +88 ms] executing: /Users/ivanonishchenko/Library/Android/sdk/platform-tools/adb devices -l
[+3153 ms] Exit code 0 from: /Users/ivanonishchenko/Library/Android/sdk/platform-tools/adb devices -l
[   +1 ms] List of devices attached
[        ] * daemon not running; starting now at tcp:5037
* daemon started successfully
[  +14 ms] executing: /Users/ivanonishchenko/repos/flutter/bin/cache/artifacts/libimobiledevice/idevice_id
-h
[ +111 ms] /usr/bin/xcrun simctl list --json devices
[ +226 ms] No supported devices connected.
[   +9 ms] "flutter run" took 4,787ms.
#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:276:7)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:528:11)

#3      FlutterCommand.run.
(package:flutter_tools/src/runner/flutter_command.dart:457:33)

#4      AppContext.run. (package:flutter_tools/src/base/context.dart:157:29)

#5      _rootRun (dart:async/zone.dart:1124:13)
#6      _CustomZone.run (dart:async/zone.dart:1021:19)
#7      _runZoned (dart:async/zone.dart:1516:10)
#8      runZoned (dart:async/zone.dart:1463:12)
#9      AppContext.run (package:flutter_tools/src/base/context.dart:156:18)

#10     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:446:20)
#11     CommandRunner.runCommand (package:args/command_runner.dart:197:27)

#12     FlutterCommandRunner.runCommand.
(package:flutter_tools/src/runner/flutter_command_runner.dart:416:21)

#13     AppContext.run. (package:flutter_tools/src/base/context.dart:157:29)

#14     _rootRun (dart:async/zone.dart:1124:13)
#15     _CustomZone.run (dart:async/zone.dart:1021:19)
#16     _runZoned (dart:async/zone.dart:1516:10)
#17     runZoned (dart:async/zone.dart:1463:12)
#18     AppContext.run (package:flutter_tools/src/base/context.dart:156:18)

#19     FlutterCommandRunner.runCommand
(package:flutter_tools/src/runner/flutter_command_runner.dart:367:19)

#20     CommandRunner.run. (package:args/command_runner.dart:112:25)
#21     new Future.sync (dart:async/future.dart:224:31)
#22     CommandRunner.run (package:args/command_runner.dart:112:14)
#23     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:251:18)
#24     run.. (package:flutter_tools/runner.dart:63:22)

#25     _rootRun (dart:async/zone.dart:1124:13)
#26     _CustomZone.run (dart:async/zone.dart:1021:19)
#27     _runZoned (dart:async/zone.dart:1516:10)
#28     runZoned (dart:async/zone.dart:1500:12)
#29     run. (package:flutter_tools/runner.dart:61:18)

#30     AppContext.run. (package:flutter_tools/src/base/context.dart:157:29)

#31     _rootRun (dart:async/zone.dart:1124:13)
#32     _CustomZone.run (dart:async/zone.dart:1021:19)
#33     _runZoned (dart:async/zone.dart:1516:10)
#34     runZoned (dart:async/zone.dart:1463:12)
#35     AppContext.run (package:flutter_tools/src/base/context.dart:156:18)

#36     runInContext (package:flutter_tools/src/context_runner.dart:63:24)

#37     run (package:flutter_tools/runner.dart:50:10)
#38     main (package:flutter_tools/executable.dart:65:9)

#39     main
(file:///Users/ivanonishchenko/repos/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#40     _startIsolate. (dart:isolate-patch/isolate_patch.dart:303:32)
#41     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)
Thank you!

It works now. I used wrong App Id


IIS SNI not working after Certificate Renewal

Hello,
i just had a very nasty incident with one of our database server.
After a scheduled certificate renewal the IIS suddenly ignored the SNI settings of the bindings and all requests to the server were answered with the wrong certificate (in this case the standard certificate of the server).
All attempts to rebinding the certificates, setting the sni, reset the iis didn't help at all.
At the end i had to restore the server from a backup.
Has anyone ever observed anything like this before?

There have been scattered reports of this happening over the years. Typically it means that a certificate mapping at the kernel level (i.e. what you see with netsh http show sslcert) somehow comes into existance that overrules all others, which can be fixed by deleting the offender with a command like netsh http delete sslcert ipport=<IP_ADDRESS>:443
win-acme doesn't manipulate the mapping at that level directly, but I think it's possibly a symptom of a bug in Microsofts library that we rely on to manage IIS bindings. My gut feeling tells me it tends to happen more when there are IP-specific, non-SNI bindings being newly created, but nobody's ever been able to find a clear reproducable case. If you still have log files that might be helpful.


Fw 3457 refactor mediabrowsers

reuse SearchSelector in MediaBrowser components
moved main/aside elements from reusable components into page-level containers
reuse ArrayBrowserField for media/category selectors
renamed various ArrayFields

Sonarbot failed this for duplication, but even sonarbot agrees that all the duplication would go away after merging. (It's all the files I split in two-- presumably the new files are being compared to the old files on the master branch.) Is there a way to ignore it?


Add files via upload - ESUPEC

@Lino116 Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@Lino116 You might miss my previous comment. Please react.

@Lino116 I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Cobertura updates/adherence

Currently SQLCover doesn't populate the filename field in its Cobertura report. Per the DTD, this is a required field.
Since many downstream tools that consume Cobertura will assume this field has a value, I think it is better to put something rather than nothing, to make a stronger attempt to adhere to the format and increase output ingestion compatibility.
There is also a 0.4 DTD available vs the 0.3 in use currently.

I have started a project based on this with added features like branch coverage, execution message output and additional fixes.
You can check if you are interested
https://github.com/sayantandey/SQLServerCoverage.
Here's the sample of Cobertura report generated
I have added distribution for common platforms and details to build it for other platforms.


Light Mode cannot display a matching Fore Color.

The light mode works very buggy for me. The fore color of objects (labels, picture box and much more) cannot be changed further in light mode. I can't adapt to myself. I am using Visual Basic WinForms Net 4.8

`
Imports WinBlur
Imports WinBlur.UI
Public Class Form1
Private Sub Form1_Load(sender As Object, e As EventArgs) Handles MyBase.Load
    Me.BackColor = Color.Black
    Me.ForeColor = Color.White
    SetBlurStyle(Me, BlurType.Mica, Mode.DarkMode)
    Me.BackColor = Color.Black
    Me.ForeColor = Color.White
End Sub

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
    Me.BackColor = Color.White
    SetBlurStyle(Me, BlurType.Mica, Mode.LightMode)
    Me.BackColor = Color.White
    Me.ForeColor = Color.DimGray
End Sub

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click
    Me.BackColor = Color.Black
    Me.ForeColor = Color.White
    SetBlurStyle(Me, BlurType.Mica, Mode.DarkMode)
    Me.BackColor = Color.Black
    Me.ForeColor = Color.White
End Sub

End Class
`
Mica Test.zip

What do you mean by cannot be changed further in light mode? Can you be more clear with your issue?

Yeah, I've seen the issue now after testing your source code. I will be trying to fix this, because I also tried manually changing the Forecolor of the buttons but it still didn't work. What I can recommend is using a framework like Guna UI/Bunifu until this gets fixed.
Thank you for reporting this issue.


[typing] TypeVar for broadcast rather than object

The type for broadcast should probably be defined using TypeVar, rather than object since we only want to enforce that the input type is the same as the output type.
Something like:
T = TypeVar("T", bound=object)
def broadcast(self, obj: T, src: int = 0) -> T:
   ...

This would avoid requiring cast at the call-site when broadcasting elements.
https://github.com/PyTorchLightning/pytorch-lightning/blob/f79a13e4956554eb68b103c12054bdb7cd4dbe1a/pytorch_lightning/plugins/training_type/training_type_plugin.py#L90

Dear @kandluis,
Great catch !
Would you mind making a PR to update the typing ?
Best,
T.C


Revisions button isn't quite right

Description
When there's a published model with no changes, why does the button say Save & Publish and why is the Publish button active??
I wouldn't expect to see any s&p button and the publish one inactive.
Steps to reproduce

View a published model

Environment
Environment
Application Name: Zakat Foundation of America
Laravel Version: 11.13.0
PHP Version: 8.3.8
Composer Version: 2.7.6
Environment: local
Debug Mode: ENABLED
URL: zakat.test
Maintenance Mode: OFF
Timezone: America/Los_Angeles
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: null
Cache: file
Database: mysql
Logs: stack / daily
Mail: smtp
Queue: sync
Session: file
Livewire
Livewire: v3.5.1
Statamic
Addons: 13
Sites: 3 (zakat.org (EN), zakat.org (AR), zfinstitute.com (ZFI))
Stache Watcher: Disabled
Static Caching: Disabled
Version: 5.11.0 PRO
Statamic Addons
aryehraber/statamic-captcha: 1.12.0
edalzell/forma: 3.0.1
jacksleight/statamic-bard-mutator: 2.3.1
jacksleight/statamic-distill: 0.7.1
jonassiewertsen/statamic-livewire: 3.6.0
statamic-rad-pack/runway: 7.5.1
statamic/seo-pro: 6.0.3
transformstudios/events: 5.4.3
transformstudios/front: 3.0.1
transformstudios/github: dev-main
transformstudios/neon: dev-feature/enable-revisions
transformstudios/review: 5.0
transformstudios/simple: 5.1.7

This is the way Statamic does it.


Support using Git binary for some operations

Related: #2

@wlynch this PR has a large diff but it's largely in tests. I've reimplemented three gitinterface APIs using the Git binary in place of go-git. They are GetFilePathsChangedByCommitUsingBinary, KnowsCommitUsingBinary, and GetCommitsBetweenRangeUsingBinary. Note that most of the diff is because I've copied the tests for the go-git equivalents. The reason the tests aren't the same is because with the Git binary, we can't use an in-memory repo. We could, if you prefer, switch the go-git tests to use on-disk repo as the test cases for all three are otherwise identical (caveat: some errors returned differ).

With this feature flag enabled, we see some significant performance improvements when verifying file policies. It'll be interesting to see if we can help go-git with improvements by comparing the two. On https://github.com/gittuf/benchmark-file-rules, we see the following when using go-git:
$ time gittuf verify-ref --from-entry b3f629d7d1fcd951449765ebc3336c982dcecde7 main

real    0m7.431s
user    0m8.800s
sys     0m0.875s

When we switch to the Git binary:
$ time gittuf --use-git-binary verify-ref --from-entry b3f629d7d1fcd951449765ebc3336c982dcecde7 main

real    0m0.676s
user    0m0.843s
sys     0m0.072s

@adityasaky it would be great to get a pprof profile for this specific process, so that we can identify bottlenecks in go-git.

@pjbgf apologies for the delay, I'll try and capture those ASAP. We added support for profiling recently (#284).

Closing in favour of #367


Branch bp/GH-25

Codecov Report

Merging #26 into master will increase coverage by 0.25%.
The diff coverage is 93.75%.

@@            Coverage Diff             @@
##           master      #26      +/-   ##
==========================================
+ Coverage   85.08%   85.34%   +0.25%
==========================================
  Files           3        3
  Lines         409      423      +14
==========================================
+ Hits          348      361      +13
- Misses         61       62       +1

Impacted Files
Coverage Δ

flask_authorize/mixins.py
77.83% <93.75%> (+1.11%)
:arrow_up:

Continue to review full report at Codecov.

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


Added mesh visualization and edge element finding

Standalone functions for now. I'll work on integrating them into celeri.py and/or celeri_vis.py

Thanks for all these suggestions @brendanjmeade! black auto formatting took care of most of them, and I do think the ismember package is pretty nice to have, but I mainly think that because it replicates the behavior I'm used to from Matlab!

@jploveless Merged!


lm.fit error

Hi! Can you please verify whether "timepoints" is in minutes or hours? I am getting the following error:
Error in lm.fit(x, y, offset = offset, singular.ok = singular.ok, ...) :
incompatible dimensions
I ran the following arguments:
x = growthrateR(platefile, platemap, timepoints=90, window=1.5, time.min=-Inf, time.max=Inf, plate.clean=TRUE)
My plate OD readings were obtained every 1.5 hours.

Hi! timepoints is in minutes.
Two things I can think that may be causing your error:

The time column in your plate file may have been automatically formatted to 00:00:00 MM/DD/YYYY by Excel. Try manually changing the formatting to numeric, and ensuring that the values are: 0, 90, 180, etc.
Because you set window and timepoints are the same (90 mins), you're "regressing" just 1-2 points. Try increasing window to a time window that will include at least three measurements.


Add files via upload

@priyem007 glbimr.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


Broken Link on freeCodeCamp github page

Main page:
https://github.com/freeCodeCamp/freeCodeCamp
Click on "Academic Dishonesty" link:
https://www.freecodecamp.org/academic-honesty-policy

To clarify for anyone willing to tackle this issue - the broken link is in the README

@akkatracker I can fix this issue. Should I create a pull request.

@mpmaan go for it! Make sure to follow the instructions given in the Contributing Guidelines :)
https://github.com/freeCodeCamp/freeCodeCamp/blob/staging/CONTRIBUTING.md


PersonController Callback Fix

PersonController had multiple errors which prevented example and tutorial from working correctly. Removed deprecated callback style from $http.get result, and fixed Json serialization bugs

@maschram,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

@maschram, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, .NET Foundation Pull Request Bot

OK, change made

@maschram  Thanks!
@scottaddie  please review.


Minor Bug fix and Readme update

Minor bug fix in rosdep deleting motoman dependency and added link to IKfast tutorial.

Thank you!


SCB-561 Support ipv6

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run go build go test go fmt go vet to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.05%) to 73.519% when pulling 3924ae6eaad3d93b31d894a8f4fdd82dfa3a9338 on little-cui:master into c071d7ad70e83962f22d5b5845f466a1be8eb48d on apache:master.

Codecov Report

Merging #343 into master will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #343      +/-   ##
==========================================
+ Coverage   69.92%   69.95%   +0.02%
==========================================
  Files          17       17
  Lines        3412     3412
==========================================
+ Hits         2386     2387       +1
  Misses        861      861
+ Partials      165      164       -1

Impacted Files
Coverage Δ

server/service/rule.go
77.25% <0%> (+0.42%)
:arrow_up:

Continue to review full report at Codecov.

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


Create foldlList "list" function

Just so it's on record that we made a function that takes a list of sentences and creates a sentence by putting commas between the elements, ending in a "_, and _". Ex.
(foldlList [this, other, that]) -> this, other, and that

I'm pretty sure I had already created such a function.  But quite likely not in a very visible place [i.e. it's my fault you guys didn't know about it].
We need to better document our sentence combinators.

added foldle1 which uses first value in the list as the accumulator for foldle.


Each navigation changes value of a reactive variable

Describe the bug
I am really surprised with this problem!
If you click on the "Edit Iban" link the first time isValid is true. Then you click on "Home" and again on "Edit Iban". This time the isValid is false. And the same again. The boolean changes each time! Crazy! :smile:
Animated GIF

Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-6mhfes
System Info
System:
  OS: Windows 10 10.0.19044
Binaries:
  Node: 16.15.0 - C:\Program Files\nodejs\node.EXE
  npm: 8.8.0 - C:\Program Files\nodejs\npm.CMD
npmPackages:
  @sveltejs/adapter-static: 1.0.0-next.29 => 1.0.0-next.29
  @sveltejs/kit: 1.0.0-next.323 => 1.0.0-next.323

Severity
blocking all usage of SvelteKit

I hate regexes. Thank you @Rich-Harris. The world is a better place thanks to you.


Fix traffic_manager build when mime-sanity-check is enabled

When building ATS 9.1.0 on Debian with --enable-mime-sanity-check option, build fails with undefined reference error for mime_hdr_sanity_check method.

[approve ci]

Cherry-picked to v9.1.x branch
Cherry-picked to v9.2.x


Add Raw Remap Range Directive

Adds a __RANGE_DIRECTIVE__ to the Raw Remap processing, to insert the
Delivery Service Range Request Handling directives there, instead of
before the Raw Remap.
Normally, Raw Remap always needs to be at the end of the remap line,
but in some cases, specifically when custom remaps are modifying
the Range header, it's necessary to put the Range Request directives
(@plugin=slice.so, @plugin=cache_range_requests.so, etc) after
the custom Raw Remap text.
This makes that possible.
Tested manually, verified range directives are placed over __RANGE_DIRECTIVE__ in the Raw Remap, range directives are placed as normally if no directive exists, range plugins aren't double-placed. Includes unit tests verifying same.
Fixes #4755
Includes tests.
Includes docs.
Includes changelog.

[x] This PR fixes #4755

Which Traffic Control components are affected by this PR?

Traffic Ops ORT

What is the best way to verify this PR?
Run tests.
Create a Delivery Service with a Range Request Handling: Slice, and a Raw Remap of sometext __RANGE_DIRECTIVE__, queue updates, verify the @plugin=slice.so is after sometext in remap.config on the cache.
Remove __RANGE_DIRECTIVE__ from the Delivery Service, queue, verify Raw Remap Text is at the end of the line like it should be.
If this is a bug fix, what versions of Traffic Control are affected?
This is somewhat between a bug fix and a feature. It's a feature that fixes a critical issue in a new feature in 4.1, #4455

master
4.1

The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

Pinged @traeak to review, since he saw the original issue, and is probably most qualified to say if it's fixed. (Can't actually add as a reviewer, since he's not a committer.)


[Add]

Details

on clicking

after downloaded

Screenshots
No response
Type of Contribution

[ ] Update to an existing Animated Button
[X] Adding a new Button
[ ] Resolving a bug
[ ] Proposal to the Repository
[ ] Changes related to documentation or README.md
[ ] Other Changes

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue
[X] I am a GSSoC'23 contributor

has full animation

please assign it to me

https://github.com/Spyware007/Animating-Buttons/assets/120590200/01ba1e43-f4c5-4c09-9c86-0bc2ae0d4acf

Bro It Hardly Take a sec to download the zip file. Will it dynamically adjust for it?

Bro It Hardly Take a sec to download the zip file. Will it dynamically adjust for it?

i will reduce the time for the animation

i will reduce the time for the downloading part please assign it to me

Bro The Animation Is Taking more than 10 seconds.
Sorry But We can't Accept It


rabbitmq-server: 3.9.14 -> 3.10.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/rabbitmq/rabbitmq-server/releases.
meta.description for rabbitmq-server is: "An implementation of the AMQP messaging protocol"
meta.homepage for rabbitmq-server is: "https://www.rabbitmq.com/"
meta.changelog for rabbitmq-server is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 3.10.6 with grep in /nix/store/i9n994cpsb8f8b1g2qr14sx888ixwx9v-rabbitmq-server-3.10.6
found 3.10.6 in filename of file in /nix/store/i9n994cpsb8f8b1g2qr14sx888ixwx9v-rabbitmq-server-3.10.6

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
rabbitmq-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/i9n994cpsb8f8b1g2qr14sx888ixwx9v-rabbitmq-server-3.10.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rabbitmq-server https://github.com/r-ryantm/nixpkgs/archive/c86d33886de6c60d80ec56d89d7e10ba885b0482.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/i9n994cpsb8f8b1g2qr14sx888ixwx9v-rabbitmq-server-3.10.6
ls -la /nix/store/i9n994cpsb8f8b1g2qr14sx888ixwx9v-rabbitmq-server-3.10.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

rabbitmq-server

Maintainer pings
cc @turion for testing.

Result of nixpkgs-review pr 183793 run on x86_64-linux 1

1 package built:

rabbitmq-server


2D animation

Add support for 2D animation using sheets and bones. Support for Spine and Spriter exported animations.

You might want to consider supporting Creature as well:
https://github.com/kestrelm
https://creature.kestrelmoon.com/
In particular, the CreaturePack format is super compact and has very few dependencies.

Looks very nice. I agree it's something we should integrate/support.


Fix electron initialization

Electron app initialization seems to have changed. See electron-quick-start/main.js

@omidkrad Do you also go by username ctoran? I'm just trying to confirm via our CLA records.

@EisenbergEffect yes, but will make future contributions with this ID.

Thanks. I'll just put a note in our database for the future.


Test 1 of the digital bookplates UI to add 979 tags

[x] Deploy latest libsys-airflow code to dev
[x] Unpause the add 979 fields DAG
[x] Upload a file of instance IDs to add 979 fields to
[x] Write up any bug tickets

Bug ticket #1306


Allow @Mixin to be used for methods as well

This one allows Mixins to be used as method parameters, in particular for subcommands that are defined as methods.

Codecov Report

Merging #525 into master will increase coverage by 0.09%.
The diff coverage is 93.93%.

@@             Coverage Diff              @@
##             master     #525      +/-   ##
============================================
+ Coverage     89.01%   89.11%   +0.09%
- Complexity      284      285       +1
============================================
  Files             4        4
  Lines          3906     3932      +26
  Branches        959      964       +5
============================================
+ Hits           3477     3504      +27
  Misses          214      214
+ Partials        215      214       -1

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/picocli/CommandLine.java
89.14% <93.93%> (+0.1%)
160 <0> (+1)
:arrow_up:

Continue to review full report at Codecov.

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


Barometer Sensor Integration

Description: Connect barometer to BITS

Currently waiting on delivery of batteries for the barometer. Nic will bring up to Boulder when it arrives.

This has been tabled.


How do I manage onClick events?

I am attempting to implement onClick events on react-nvd3 components. Is there a way I can use onClick events on a react-nvd3 component?

@stephanbochet I have to check this. Could you provide an example about what you're trying to do?

I managed to temporarily solve the issue by using jQuery to get the series, name and value of the element clicked on a chart.
componentDidUpdate: function() {
    $(".nv-chart").mouseup(function (e) {
        console.log(e.toElement["__data__"]);
    });
}


Build fails on CentOS 7 aarch64

# uname -msr
Linux 5.4.72-v8.1.el7 aarch64

# gcc --version
gcc (GCC) 10.2.1 20210130 (Red Hat 10.2.1-11)
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

# git log --oneline -n 3
eb93814 (HEAD -> master, origin/master, origin/HEAD) Merge pull request #131 from nelhage/dependabot/github_actions/actions/checkout-2.4.0
6c5cceb Bump actions/checkout from 2.3.5 to 2.4.0
145f59d Merge pull request #130 from nelhage/dependabot/github_actions/actions/checkout-2.3.5

# make
cc -MD -Wall -Werror -D_GNU_SOURCE -g    -c -o reptyr.o reptyr.c
In file included from platform/platform.h:32,
                 from reptyr.c:37:
platform/../ptrace.h:80:29: error: field ‘regs’ has incomplete type
   80 |     struct user_regs_struct regs;
      |                             ^~~~
make: *** [reptyr.o] Error 1

I also tried compiling tag 0.8.0; no luck either with identical error.
I searched issues and found a similar error in #116. Not sure how this is related though.
Sorry I can't contribute much; not a C developer 🙁

I hit this as well. AFAIK arm64 has never had a user_regs_struct on linux, it is called user_pt_regs.


Correct file path

Coverage decreased (-0.06%) to 64.11% when pulling 0e3195ea96f94eb834ef3e4bba9dd42a8f58fb30 on tianxiaoliang:master into ec1aab27eb99f185bbec0591341c772a59aa8b59 on ServiceComb:master.


No example with VMs in the same subnet

There is no example with application order of NSG rules for VMs inside the same subnet.
In the real life today even if NSG is applied to subnet is limit communication between VMs inide the same subnet.

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

ID: 5e905802-0b08-4b3b-25ec-0f88c023bc32
Version Independent ID: f31325e5-49ea-b28c-336e-10f2a3fc12b4
Content: Azure security groups overview
Content Source: articles/virtual-network/security-overview.md
Service: virtual-network
GitHub Login: @malopMSFT
Microsoft Alias: malop;kumud

@ivanignatiev
Thanks for your feedback! We will investigate and update as appropriate.

@ivanignatiev
Thanks for your feedback! We will investigate and update as appropriate.

@ivanignatiev how NSGs evaluate rules is described Here. for 2 VMs in the same subnet, the subnet NSG is evaluated first, then the outbound NICs NSG is next, and last is the inbound NICs NSG.
Please let me know if you need any additional information.

@TravisCragg-MSFT Current example presented in documentation is based on the case VM <-> Internet. If possible to add few examples (or extend the current one) with internal to VNet communications VM <-> VM, i.e. :

VM1 and VM2 in Subnet 1 with NSG1 applied to Subnet1
VM1 in Subnet1 and VM2 in Subnet2, with NSG1 applied to Subnet1 and NSG2 applied to Subnet2

And/or say in the documentation explicitly that NSG associated with Subnet always controls traffic even if VMs are in the same Subnet, because often people imagine NSG as a firewall so when we say that NSG at Subnet level can block/allow traffic inside the Subnet - everybody has impression that traffic goes out of Subnet and returns back each time.
So, I propose to clarify those points in the documentation.
Thank you!

@ivanignatiev Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@TravisCragg-MSFT  thank you ! I will appreciate also some examples with Internal Load Balancers and NSG at Subnet and NIC levels.

I too would like to reinforce the need to document the "east-west" behaviour of NSG's as described by ivanignatiev on Dec 18th 2018.   The "How Traffic Is Evaluated" section only covers North-South traffic, and for completeness should cover east-west traffic for VM1<->VM2 and maybe even VM1<->VM3.
Thanks.. JD

@KumudD @malopMSFT This issue was owned by Jim Dial, Assigning you two as you are now the current owner.

Any update on this? I agree with OP - it's not too obvious from any of the MS Azure docco what happens you add a deny 'any source' to 'any destination' on a subnet level NSG as an explicit over-ride rule for example. In this case it actually blocks traffic between VMs in the same subnet unless you explicitly open the required ports to allow intra subnet communication

I am very glad I found this thread, I was having the exact same confusion and also not realizing NSGs applied to East-West traffic in the same subnet. I hope this documentation is updated soon!

More confusion! The Cloud Adoption Framework guide specifically says that NSGs do NOT block East West traffic inside of a subnet. I've submitted a request on that page, but I would say it's pretty urgent that the Microsoft docs AGREE with each other.
Link and copy of confusing language below:
https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-networking#best-practice-secure-northsouth-and-eastwest-traffic
Best practice: Secure north/south and east/west traffic
When securing VNets, it's important to consider attack vectors.
Using only subnet NSGs simplifies your environment, but only secures traffic into your subnet. This is known as north/south traffic.
Traffic between VMs on the same subnet is known as east/west traffic.
It's important to use both forms of protection, so that if a hacker gains access from the outside they'll be stopped when trying to attach machines located in the same subnet.

@cmcapellan I ended up logging a Premier support request and have had confirmation from MS support that a subnet level NSG rule is essentially applied to the NIC of each VM on that subnet.
I don't understand why they can't explicitly just call this out in the documentation - all their digrams only show north/south traffic flows... should be pretty easy to update this doc with a simple diagram and explanation rather than have their customers figure it out the hard way...

This doc issue has been addressed.
#please-close


Lint/MissingSuper: exclude method_missing and respond_to_missing?

Contrary to the other hooks, these have very valid cases to be completely taken over:
# accept everything:
def method_missing(method, *args)
  nil
end

# or delegate all
def method_missing(method, *args)
  delegate_to.send(method, *args)
end

While a class has a "right" to expect its other hooks to be called, these hooks aren't necessarily called the same way.
From https://github.com/testdouble/standard/issues/195#issuecomment-729863480

I'm fine with the proposed change, but I think it should be clearly explained in the cop's documentation why are those hooks treated differently.

I did my best while staying concise.

Looks good! Thanks!


Unable to clone: fatal: early EOF

Cloning into 'openui'...
remote: Enumerating objects: 1053, done. fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

Would be nice to get a CodeSandbox of this. Its been impossible trying to get this repo working.

The readme has instructions for a GitHub code space or Gitpod.  The error you're getting is a network error on GitHub's side and should go away if you retry.

The readme has instructions for a GitHub code space or Gitpod.  The error you're getting is a network error on GitHub's side and should go away if you retry.

Apologies I wish delete this issue as it was totally user side.


fixes with dataset counts for non admin users

fix to #472 currently when the dataset is viewed by non-admin users and anon users it reflects the number of the public records by corresponding org.

@Samweli please take notes

@seabilwe this PR is merged before running git action workflow and might not reflect on the testing site, once a newer one is made it's going to reflect on the testing site.


update: actions/checkout@v4

Due to the end of support for Node.js 16, I would like to update the actions to use Node.js 20.
see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

I see that only a specific version of the software crashes.
I would like to solve the cause of the problem, so I will try various forks. I would like to ask for another CI when I think the problem has been resolved.

A warning has been introduced in https://github.com/ruby/ruby/pull/10428, indicating that ostruct will become a bundled gem starting from Ruby 3.5.
Upon checking the CI error logs, I saw this warning and added the dependency to the gemspec:
output from parser-cmd (stderr):
  /opt/hostedtoolcache/Ruby/3.3.5/x64/lib/ruby/3.3.0/json/common.rb:3: warning: ostruct was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0.
  You can add ostruct to your Gemfile or gemspec to silence this warning.

After making this change, the CI passed successfully, so I believe this resolves the necessary updates for GitHub Actions.
I would appreciate it if you could review the changes again. Thank you for your time.

@ksaito422 Thank you for the PR, but please do not add a dependency to ostruct. The perfect_toml gem itself does not depend on the ostruct gem. Only the test script does. I guess adding gem "json", ">= 2.7.2" to Gemfile will solve the issue.

@ksaito422 Thank you for the PR, but please do not add a dependency to ostruct. The perfect_toml gem itself does not depend on the ostruct gem. Only the test script does. I guess adding gem "json", ">= 2.7.2" to Gemfile will solve the issue.

Thanks for the advice. I had overlooked the dependency there.
I have addressed it, please check.

Thanks!


Invalid behavior when trying to install a non-existing plugin

Workaround for an invalid plugin status returned from the 'install_plugin_install_status' when trying to install a non-existing plugin.

Cherry-picked: 4a70fec820288c48630c41230678b4c0b292e513
Thanks for the fix.


Input validation failed

Module: 02
Lab/Demo: 02
Exercise 01
Task: 02
Step: 2
Description of issue
The lab steps say to create an Azure Automation account and choose "any unique name". I have entered a large number of unique and random names but validation always fails. I am using godeploy.it lab environment.
Repro steps:
Just follow the steps

Based on that resource group name, I'm guessing the lab is using Go Deploy's Cloud Share feature. Possibly they have some policy on names (perhaps a maximum length). Your first point of contact should be Go Deploy.
That name you've picked is certainly available (just not right now, because I've created an Automation Account using that name to test it).

@craigbeeremct Than you for your time and reply. You are right this is godeploy (I mentioned it I believe in the op). I did raise a case with their support (which was very quick I have to admit) and I was provided with a response that it should be fixed. I have not tested it due to time constraints, but I will report here as soon as I verify.

MOC Labs Review did not experience this issue.

Closing issue #6 as it was subsequently tested, and issue was not experienced.


Building on Mac OS fails

Config:
CC = gcc
CFLAGS = -O2 -Wall -Wextra -pedantic -std=gnu11 -fPIC
LDFLAGS = -lmbedtls -lmbedx509 -lmbedcrypto

Using gmake as specifically instructed.
Compiler:
gcc -v
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
Apple clang version 11.0.3 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin19.4.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Linker:
ld -v
@(#)PROGRAM:ld  PROJECT:ld64-556.6
BUILD 13:10:29 Apr  7 2020
configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em
LTO support using: LLVM version 11.0.3, (clang-1<IP_ADDRESS>) (static support for 26, runtime is 26)
TAPI support using: Apple TAPI version 11.0.0 (tapi-1100.0.11)

/usr/local/opt/gcc/bin/gcc-9 didn't build at all.  Got stuck on stdio.h.
Building:
gmake
gmake -C mbedtls lib
gmake[1]: Entering directory '.../hactool/mbedtls'
gmake[1]: Leaving directory '.../hactool/mbedtls'
gmake hactool
gmake[1]: Entering directory '.../hactool'
gcc -I ./mbedtls/include -c -O2 -Wall -Wextra -pedantic -std=gnu11 -fPIC -D_BSD_SOURCE -D_POSIX_SOURCE -D_POSIX_C_SOURCE=200112L -D_DEFAULT_SOURCE -D__USE_MINGW_ANSI_STDIO=1 -D_FILE_OFFSET_BITS=64 -o save.o save.c
gcc -I ./mbedtls/include -c -O2 -Wall -Wextra -pedantic -std=gnu11 -fPIC -D_BSD_SOURCE -D_POSIX_SOURCE -D_POSIX_C_SOURCE=200112L -D_DEFAULT_SOURCE -D__USE_MINGW_ANSI_STDIO=1 -D_FILE_OFFSET_BITS=64 -o sha.o sha.c
...
ld: warning: ld: warning: ignoring file ./mbedtls/library/libmbedtls.a, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format ( 0x21 0x3C 0x61 0x72 0x63 0x68 0x3E 0x0A 0x2F 0x20 0x20 0x20 0x20 0x20 0x20 0x20 )
ignoring file ./mbedtls/library/libmbedx509.a, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format ( 0x21 0x3C 0x61 0x72 0x63 0x68 0x3E 0x0A 0x2F 0x20 0x20 0x20 0x20 0x20 0x20 0x20 )
ld: warning: ignoring file ./mbedtls/library/libmbedcrypto.a, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format ( 0x21 0x3C 0x61 0x72 0x63 0x68 0x3E 0x0A 0x2F 0x20 0x20 0x20 0x20 0x20 0x20 0x20 )
Undefined symbols for architecture x86_64:
  "_mbedtls_cipher_cmac_finish", referenced from:
      _aes_calculate_cmac in aes.o
  "_mbedtls_cipher_cmac_starts", referenced from:
      _aes_calculate_cmac in aes.o
  "_mbedtls_cipher_cmac_update", referenced from:
      _aes_calculate_cmac in aes.o
  "_mbedtls_cipher_finish", referenced from:
      _aes_encrypt in aes.o
      _aes_decrypt in aes.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [Makefile:17: hactool] Error 1
gmake[1]: Leaving directory '.../hactool'
gmake: *** [Makefile:11: all] Error 2

Branch: master, origin/master
Commit: f55d6f2506a38ef05ec0ab99ec4041313d5e6d7a
System (OS): macOS 10.15.4

This builds completely fine for me OOB on Catalina with this config. Looks like you've somehow built mbedtls with the wrong architecture.
export CC=clang
export AR=ar
export CFLAGS = -O2 -Wall -Wextra -pedantic -std=gnu11 -fPIC
export LDFLAGS = -lmbedtls -lmbedx509 -lmbedcrypto```

Can try this config & do a `make clean_full` to clean mbedtls first.

Commit: 2b0c791f9485f78ee359f45c91b97a48d534e9e6
> gmake clean_full
rm -f *.o hactool hactool.exe
gmake -C mbedtls clean
gmake[1]: Entering directory '.../hactool/mbedtls'
gmake[2]: Entering directory '.../hactool/mbedtls/library'
gmake[2]: Leaving directory '.../hactool/mbedtls/library'
gmake[2]: Entering directory '.../hactool/mbedtls/programs'
gmake[2]: Leaving directory '.../hactool/mbedtls/programs'
gmake[2]: Entering directory '.../hactool/mbedtls/tests'
gmake[2]: Leaving directory '.../hactool/mbedtls/tests'
gmake[1]: Leaving directory '.../hactool/mbedtls'

Config:
CC = gcc
CC = clang
AR = ar
CC1 = /usr/local/opt/gcc/bin/gcc-9
CFLAGS = -O2 -Wall -Wextra -pedantic -std=gnu11 -fPIC
LDFLAGS = -lmbedtls -lmbedx509 -lmbedcrypto

Building:
gmake
gmake -C mbedtls lib
gmake[1]: Entering directory '.../hactool/mbedtls'
gmake[2]: Entering directory '.../hactool/mbedtls/library'
  CC    aes.c
...
clang -o hactool save.o sha.o aes.o extkeys.o rsa.o npdm.o bktr.o kip.o packages.o pki.o pfs0.o hfs0.o nca0_romfs.o romfs.o utils.o nax0.o nso.o lz4.o nca.o xci.o main.o filepath.o ConvertUTF.o cJSON.o -L ./mbedtls/library -lmbedtls -lmbedx509 -lmbedcrypto
ld: warning: ignoring file ./mbedtls/library/libmbedtls.a, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format ( 0x21 0x3C 0x61 0x72 0x63 0x68 0x3E 0x0A 0x2F 0x20 0x20 0x20 0x20 0x20 0x20 0x20 )
ld: warning: ignoring file ./mbedtls/library/libmbedcrypto.a, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format ( 0x21 0x3C 0x61 0x72 0x63 0x68 0x3E 0x0A 0x2F 0x20 0x20 0x20 0x20 0x20 0x20 0x20 )
ld: warning: ignoring file ./mbedtls/library/libmbedx509.a, building for macOS-x86_64 but attempting to link with file built for unknown-unsupported file format ( 0x21 0x3C 0x61 0x72 0x63 0x68 0x3E 0x0A 0x2F 0x20 0x20 0x20 0x20 0x20 0x20 0x20 )
Undefined symbols for architecture x86_64:
...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [Makefile:17: hactool] Error 1
gmake[1]: Leaving directory '.../hactool'
gmake: *** [Makefile:11: all] Error 2

Why are you adding extra bits to the config I posted in https://github.com/SciresM/hactool/issues/96#issuecomment-653614711?
This builds fine OOB on a fresh Catalina install with xcode command line tools. Would personally recommend staying far, far away from brew or whatever that is you're using. It's clearly broken.

Just how I keep old entries in case I want to switch them on again quickly.
Xcode: 11.4.1

k. One last shot.
Try exactly this config as written. No modifications of any kind.
export CC=/usr/bin/clang
export AR=/usr/bin/ar
export CFLAGS = -O2 -Wall -Wextra -pedantic -std=gnu11 -fPIC
export LDFLAGS = -lmbedtls -lmbedx509 -lmbedcrypto

and then run /usr/bin/make directly.
Whatever you're trying to compile hactool with is broken. If using direct paths to official apple tools doesn't work then your machine is hosed and I'd reinstall your OS.

That seemed to do it, thanks.
Besides trying to keep the config.mk file clean, I noticed the ar is different, but I was also using gmake earlier based on the readme mention.  Used regular apple's make this time.
~/D/s/hactool (master=) gmake clean_full
rm -f *.o hactool hactool.exe
gmake -C mbedtls clean
gmake[1]: Entering directory '.../hactool/mbedtls'
gmake[2]: Entering directory '.../hactool/mbedtls/library'
gmake[2]: Leaving directory '.../hactool/mbedtls/library'
gmake[2]: Entering directory '.../hactool/mbedtls/programs'
gmake[2]: Leaving directory '.../hactool/mbedtls/programs'
gmake[2]: Entering directory '.../hactool/mbedtls/tests'
gmake[2]: Leaving directory '.../hactool/mbedtls/tests'
gmake[1]: Leaving directory '.../hactool/mbedtls'
~/D/s/hactool (master=) which make
/usr/bin/make
~/D/s/hactool (master=) which clang
/usr/bin/clang
~/D/s/hactool (master=) which ar
/usr/local/bin/ar
~/D/s/hactool (master=) pbpaste > config.mk
~/D/s/hactool (master=) cat config.mk
export CC=/usr/bin/clang
export AR=/usr/bin/ar
export CFLAGS = -O2 -Wall -Wextra -pedantic -std=gnu11 -fPIC
export LDFLAGS = -lmbedtls -lmbedx509 -lmbedcrypto
~/D/s/hactool (master=) ls -l hactool
-rwxr-xr-x 1 Pysis staff 473K 2020-07-03 16:54 hactool

fwiw apple make is gnu make.
 % make --version
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i386-apple-darwin11.3.0

If I try from the repos, I get this:
~ sudo dkp-pacman -S hactool
:: Synchronizing package databases...
 dkp-libs is up to date
 dkp-osx is up to date
resolving dependencies...
looking for conflicting packages...

Packages (1) hactool-1.3.2-1
...
(1/1) checking available disk space                                         [###########################################] 100%
error: Partition / is mounted read only

That's the issue with Catalina https://github.com/devkitPro/pacman/issues/15
It's been fixed with latest pacman installer https://github.com/devkitPro/pacman/releases/latest


promiseUtils

Thanks for the project I've been using this for a "universal app" I've been working on.
I've come across the sequence method you have in the promiseUtils I was just wondering why its written the way it is? from what I can see the following snippet below is doing what you need?
I'm asking more in the way of my own "understanding the code" and not suggesting any changes.
const items = [1,2,3]
const res = Promise.all(items.map(i => i * 2))
res.then((a) => console.log(a))
// Array [
//  2,
//  4,
//  6
// ]

Promise.all doesn't execute in any particular order. Here, we need to ensure the promises are running sequentially. Because data loaded by one action might be required by another component down the chain. Let me know if this answers your question.

That makes sense , thanks for your time


Trivially true CHECK(to != kLoadStage || to != kComputeStage);

The condition in https://github.com/dmlc/tvm/blob/75f91c45d7135f366ce653cb2b2d26de2cf25df0/vta/src/runtime.cc#L498
is always true whatever to is. Should it be && instead of ||, or should one of the sides have from as in the previous line?

That's my understanding of the CHECK in the previous line, but this one can't guard against anything, can it?
Unless kLoadStage and kComputeStage are accidentally changed to be equal, which would be a rather bigger problem, but probably not the intention :)

Ah,  you are right, thanks for pointing it out, a fix is welcomed :)

The problem is that I don't know what the fixed check should be, I only have guesses which I mentioned in the original post.

It should be  CHECK(from != kLoadStage || to != kComputeStage);


Expand introduction

like in the paper or with MPfit (https://www.physics.wisc.edu/~craigm/idl/cmpfit.html).

Also rename requirements to hardware requirements and comment the last section (how to cite) for now.

I had a go, see at http://gpufit.readthedocs.io/en/latest/introduction.html and improve.


Error on 'npx supabase start' When Linking New Local Project to Existing Remote Supabase Project

Describe the bug
When running npx supabase start in a new local project and attempting to link to an existing Supabase project, the process fails with the error: "Migration failed. Reason: An error occurred running 'storage-schema'". This is particularly interesting because I don't have any migrations in my project.
To Reproduce
Steps to reproduce the behavior:

Initialize a fresh Supabase folder by running npx supabase init.
Log in to your Supabase account by running npx supabase login.
Link your remote Supabase project by executing npx supabase link --project-ref PROJECT_REF.
Enter your database password.
Run npx supabase start.
Observe the error as shown in the screenshot.

Expected behavior
I expect that all containers would successfully run, allowing me access to the local Supabase Studio.
Screenshots
Screenshot of error
Project Structure
Desktop:

OS: MacOS 14.0 (23A344)
Docker Client: OrbStack
Version of CLI: 1.136.2
Version of Node.js: v18.17.0

Additional context
I've successfully run npx supabase start in another project I am working on, which makes it surprising that this issue occurs in a fresh project that I am trying to link to an existing remote Supabase project.

Same exact behaviour here, I've tried to use the beta version (1.137.0) but it's not working as well.

Could you also run npx supabase services and share the output here?
Perhaps there is an incompatibility with the storage version after linking.

Thanks for your quick response, @sweatybridge! Sure thing. This is the output of my npx supabase services:
`

SERVICE IMAGE
LOCAL
LINKED

supabase/postgres
<IP_ADDRESS>
<IP_ADDRESS>

supabase/gotrue
v2.132.3
v2.132.3

postgrest/postgrest
v10.2.0
v10.2.0

supabase/realtime
v2.25.50
-

supabase/storage-api
v0.46.3
v0.46.3

supabase/edge-runtime
v1.32.0
-

supabase/studio
20240101-8e4a094
-

supabase/postgres-meta
v0.75.0
-

supabase/logflare
1.4.0
-

bitnami/pgbouncer
1.20.1-debian-11-r39
-

darthsim/imgproxy
v3.8.0
-

`

My npx supabase services output:
supabase/postgres      │ <IP_ADDRESS>             │ <IP_ADDRESS>
supabase/gotrue        │ v2.132.3             │ v2.132.3
postgrest/postgrest    │ v12.0.2              │ v12.0.2
supabase/realtime      │ v2.25.50             │ -
supabase/storage-api   │ v0.46.3              │ v0.46.3
supabase/edge-runtime  │ v1.32.0              │ -
supabase/studio        │ 20240101-8e4a094     │ -
supabase/postgres-meta │ v0.75.0              │ -
supabase/logflare      │ 1.4.0                │ -
bitnami/pgbouncer      │ 1.20.1-debian-11-r39 │ -
darthsim/imgproxy      │ v3.8.0               │ -

I add I can't run even supabase start on locally (macos 14.1 (23B2073)) with the CLI being at v1.136.2.
It get stuck at the Starting database from backup step and it quits after some minutes printing database is not healthy.
In my Docker Desktop app I read:

2024-01-24 20:40:14 PostgreSQL Database directory appears to contain a database; Skipping initialization
2024-01-24 20:40:14
2024-01-24 20:39:23 2024-01-24 19:39:23.300 GMT [10] LOG:  could not open configuration file "/etc/postgresql-custom/read-replica.conf": No such file or directory
2024-01-24 20:39:23 2024-01-24 19:39:23.300 GMT [10] FATAL:  configuration file "/etc/postgresql/postgresql.conf" contains errors
2024-01-24 20:40:14 2024-01-24 19:40:14.650 GMT [10] LOG:  could not open configuration file "/etc/postgresql-custom/read-replica.conf": No such file or directory
2024-01-24 20:40:14 2024-01-24 19:40:14.650 GMT [10] FATAL:  configuration file "/etc/postgresql/postgresql.conf" contains errors

The only thing I did is to upgrade supabase CLI though the brew CLI.
I've noticed that because on my Github action I kept having the error message @martijnvanderpol reported on the screenshot and I couldn't deploy my changes.

I have the same issue, with or without migrations present, even on a clean project with no prior configuration. Supabase CLI v1.137.0 (beta) is also affected.
/app/dist/database/migrate.js:104
            const error = new Error(`Migration failed. Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/server.js:23:9 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/server.js:23:9
}

Node.js v18.19.0

Experiencing the same issue:
/app/dist/database/migrate.js:104
            const error = new Error(`Migration failed. Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/scripts/migrate-call.js:10:5 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/scripts/migrate-call.js:10:5
}

Node.js v18.19.0
error running container: exit 1

Experiencing the same issue
/app/dist/database/migrate.js:104
const error = new Error(Migration failed. Reason: ${e.message});
^
Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
at /app/dist/database/migrate.js:104:27
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /app/dist/database/migrate.js:149:28
... 2 lines matching cause stack trace ...
at async /app/dist/server.js:23:9 {
cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /app/dist/database/migrate.js:98:32
at async /app/dist/database/migrate.js:149:28
at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
at async /app/dist/server.js:23:9
}
Node.js v18.19.0
service not healthy: [supabase_storage_Projects]

We're having this issue after updating Supabase CLI (version 1.136.2) and running supabase start.  Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/server.js:23:9 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/server.js:23:9
}

Node.js v18.19.0
/app/dist/database/migrate.js:104
            const error = new Error(`Migration failed. Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/server.js:23:9 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/server.js:23:9
}

Node.js v18.19.0
/app/dist/database/migrate.js:104
            const error = new Error(`Migration failed. Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/server.js:23:9 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/server.js:23:9
}

Node.js v18.19.0
/app/dist/database/migrate.js:104
            const error = new Error(`Migration failed. Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/server.js:23:9 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/server.js:23:9
}

Node.js v18.19.0
/app/dist/database/migrate.js:104
            const error = new Error(`Migration failed. Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/server.js:23:9 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/server.js:23:9
}

Node.js v18.19.0
/app/dist/database/migrate.js:104
            const error = new Error(`Migration failed. Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/server.js:23:9 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/server.js:23:9
}

Node.js v18.19.0
/app/dist/database/migrate.js:104
            const error = new Error(`Migration failed. Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/server.js:23:9 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/server.js:23:9
}

Node.js v18.19.0
/app/dist/database/migrate.js:104
            const error = new Error(`Migration failed. Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/server.js:23:9 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/server.js:23:9
}

Node.js v18.19.0
/app/dist/database/migrate.js:104
            const error = new Error(`Migration failed. Reason: ${e.message}`);
                          ^

Error: Migration failed. Reason: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
    at /app/dist/database/migrate.js:104:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/dist/database/migrate.js:149:28
    ... 2 lines matching cause stack trace ...
    at async /app/dist/server.js:23:9 {
  cause: Error: An error occurred running 'storage-schema'. Rolled back this migration. No further migrations were run. Reason: role "anon" already exists
      at /app/node_modules/postgres-migrations/dist/run-migration.js:36:15
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async /app/dist/database/migrate.js:98:32
      at async /app/dist/database/migrate.js:149:28
      at async connectAndMigrate (/app/dist/database/migrate.js:48:9)
      at async runMigrationsOnTenant (/app/dist/database/migrate.js:35:5)
      at async /app/dist/server.js:23:9
}

Node.js v18.19.0
service not healthy: [supabase_storage_xyz]
Try rerunning the command with --debug to troubleshoot the error.

I can confirm there is an incompatibility with the latest version of storage which starts managing roles in a non-idempotent way https://github.com/supabase/storage/blame/master/migrations/tenant/0002-storage-schema.sql#L21.
The temporary workaround is to revert to an old version of storage by rm supabase/.temp/storage-version.
I will also make a patch release after discussing with the storage team on what's the intended behaviour.

Thanks for the temporary workaround! @sweatybridge

Hey! Thanks for figuring it out. It seems to have solved the specific error I mentioned earlier. However, I'm now encountering a new error. After removing the .temp folder, re-linking with my remote project, and running npx supabase start again, this issue surfaced. I did update to CLI version 1.136.3.
New error log:
realtime-dev.supabase_realtime_studio-on-tour-2024 container logs:
08:55:40.926 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create".

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create". Alternatively you may configure Ecto to use
another table and/or repository for managing migrations:

    config :realtime, Realtime.Repo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.8.3) lib/ecto/adapters/sql.ex:932: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.14.3) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2
    (ecto_sql 3.8.3) lib/ecto/adapters/sql.ex:1024: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.8.3) lib/ecto/migrator.ex:696: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.8.3) lib/ecto/migrator.ex:510: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.8.3) lib/ecto/migrator.ex:422: Ecto.Migrator.run/4
    (ecto_sql 3.8.3) lib/ecto/migrator.ex:146: Ecto.Migrator.with_repo/3
    nofile:1: (file)

Output of npx supabase services:

SERVICE IMAGE
LOCAL
LINKED

supabase/postgres
<IP_ADDRESS>
<IP_ADDRESS>

supabase/gotrue
v2.132.3
v2.132.3

postgrest/postgrest
v10.2.0
v10.2.0

supabase/realtime
v2.25.50
-

supabase/storage-api
v0.46.3
v0.46.3

supabase/edge-runtime
v1.32.0
-

supabase/studio
20240101-8e4a094
-

supabase/postgres-meta
v0.75.0
-

supabase/logflare
1.4.0
-

bitnami/pgbouncer
1.20.1-debian-11-r39
-

darthsim/imgproxy
v3.8.0
-

There's likely a conflict with this version of postgres image with realtime migrations. One way to fix it is to delete supabase/.temp/postgres-version file so it uses the latest pinned version. I will also make a patch to cli to ignore these incompatible versions.
Alternatively you may want to update your hosted project to the latest postgres version.

So the earliest version of pg15 that is compatible with cli for local development is <IP_ADDRESS>. I've updated the beta release of cli to ignore versions before that. You can try it out with
npx supabase@beta start

Great! That did the trick for me, even without upgrading the remote Postgres version to v15. I'll do that later. Thanks so much for your quick actions, @sweatybridge!

@sweatybridge -- also running into these issues, but I don't have any local file called supabase/.temp/postgres-version. Instead, I just keep seeing these errors:
2024-01-29 19:58:46 2024-01-30 00:58:46.773 GMT [10] LOG:  could not open configuration file "/etc/postgresql-custom/read-replica.conf": No such file or directory
2024-01-29 19:58:46 2024-01-30 00:58:46.774 GMT [10] FATAL:  configuration file "/etc/postgresql/postgresql.conf" contains errors
2024-01-29 19:58:48 2024-01-30 00:58:48.535 GMT [10] LOG:  could not open configuration file "/etc/postgresql-custom/read-replica.conf": No such file or directory
2024-01-29 19:58:48 2024-01-30 00:58:48.535 GMT [10] FATAL:  configuration file "/etc/postgresql/postgresql.conf" contains errors
2024-01-29 19:58:51 2024-01-30 00:58:51.900 GMT [10] LOG:  could not open configuration file "/etc/postgresql-custom/read-replica.conf": No such file or directory
2024-01-29 19:58:51 2024-01-30 00:58:51.900 GMT [10] FATAL:  configuration file "/etc/postgresql/postgresql.conf" contains errors
2024-01-29 19:58:58 2024-01-30 00:58:58.457 GMT [10] LOG:  could not open configuration file "/etc/postgresql-custom/read-replica.conf": No such file or directory
2024-01-29 19:58:58 2024-01-30 00:58:58.457 GMT [10] FATAL:  configuration file "/etc/postgresql/postgresql.conf" contains errors
2024-01-29 19:59:11 2024-01-30 00:59:11.404 GMT [10] LOG:  could not open configuration file "/etc/postgresql-custom/read-replica.conf": No such file or directory
2024-01-29 19:59:11 2024-01-30 00:59:11.404 GMT [10] FATAL:  configuration file "/etc/postgresql/postgresql.conf" contains errors

Until I comment out the line importing that file in /etc/postgresql/postgresql.conf

That's a separate error tracked here https://github.com/supabase/cli/issues/1892

Hello mine worked after doing these steps

supabase link
supabase start

just did supabase link before doing supabase start

Hello mine worked after doing these steps

supabase link
supabase start

just did supabase link before doing supabase start

This was the solution for me!


Still this relevant?

Is this project still relevant?
Im tried different versions of modimporter and also modUtil but other mods works fine.
When trying to install Twitch integration mod game doesn't give me load my save.
Can I do something to let this mod work or it's need update?
Thanks :)

It is out of date at this time. I will try find time to get it fixed hopefully in the next month or so