jiebi/CodeConvo huggingface dataset:
Change:
stdenv.mkDerivation (finalAttrs: { pname = "lunacy"; <del> version = "9.5.0"; </del> <ins> version = "9.6.0"; </ins> src = fetchurl { url = "https://lcdn.icons8.com/setup/Lunacy_${finalAttrs.version}.deb"; <del> hash = "sha256-dG2xLoqRQJsaR7v00iN46GP4jB8WVrxayn2CSQLCUlQ="; </del> <ins> hash = "sha256-PvQGDUC9BsIql4xMM1OH45gq3YtJMKJcYg4N2o18hno="; </ins> }; unpackCmd = ''

Discussion:
Package name: Latest released version: 0.9.6 <!-- Search your package here: --- Current version on the unstable channel: 0.9.5 Current version on the stable/release channel: N/A <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This should be 9.5.0 -9.6.0 right?
Yes, off course. In Flatpak version is updated to 0.9.6 version number.
Thanks for your hard work, everyone
Change:
reptyr = callPackage ../os-specific/linux/reptyr {}; <del> rescuetime = callPackage ../applications/misc/rescuetime { }; </del> <ins> rescuetime = libsForQt5.callPackage ../applications/misc/rescuetime { }; </ins> reuse = callPackage ../tools/package-management/reuse { };

Discussion:
Describe the bug To Reproduce Steps to reproduce the behavior: 19.09 channel rescuetime to start it Expected behavior The application should start without problems. Additional context Related Metadata Maintainer information:
Change:
pypandoc pyperclip pyyaml <ins> psutil </ins> rich scipy sounddevice

Discussion:
A small difference in the dependencies used by aider and nixpkgs causes aider to crash. aider 0.56.0 something should get a stack overflow See <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
was closed by mistake so opened this
Thanks for opening this issue. Discussion started here It is clear that v1.44.22 of is what causes the issue but I'm not sure what could be done. maybe you have an idea?
There is an open issue in the repo, we have to wait for the dependencies to be updated upstream unfortunately. On the next update of this dependency ill be sure to try to run aider. Sorry for the inconvenience !
Why don't you use ?
the issue on aider's repo was closed the fix is to not use the wrong version of litellm :sweat:
it's not so simple for python packages. each one is a forest of carefully balanced dependencies.
Latest aider update matches with the latest litellm update, so we should be good in a couple of days
Change:
{ execjs = { <del> version = "2.3.0"; </del> source = { <ins> remotes = ["https://rubygems.org"]; sha256 = "1yz55sf2nd3l666ms6xr18sm2aggcvmb8qr3v53lr4rir32y1yp1"; </ins> type = "gem"; <del> sha256 = "097v02bhmzc70j7n0yyf8j0z5wms88zcmgpmggby4hnvqxf41y1h"; </del> }; <ins> version = "2.7.0"; </ins> }; <del> json = { version = "1.8.2"; </del> <ins> ffi = { </ins> source = { <ins> remotes = ["https://rubygems.org"]; sha256 = "0zw6pbyvmj8wafdc7l5h7w20zkp1vbr2805ql5d941g2b20pk4zr"; </ins> type = "gem"; <del> sha256 = "0zzvv25vjikavd3b1bp6lvbgj23vv9jvmnl4vpim8pv30z8p6vr5"; </del> }; <ins> version = "1.9.23"; </ins> }; <del> libv8 = { version = "3.16.14.11"; </del> <ins> rb-fsevent = { </ins> source = { <ins> remotes = ["https://rubygems.org"]; sha256 = "1lm1k7wpz69jx7jrc92w3ggczkjyjbfziq5mg62vjnxmzs383xx8"; </ins> type = "gem"; <del> sha256 = "000vbiy78wk5r1f6p7qncab8ldg7qw5pjz7bchn3lw700gpaacxp"; </del> }; <ins> version = "0.10.3"; </ins> }; <del> ref = { version = "1.0.5"; </del> <ins> rb-inotify = { dependencies = ["ffi"]; </ins> source = { <ins> remotes = ["https://rubygems.org"]; sha256 = "0yfsgw5n7pkpyky6a9wkf1g9jafxb0ja7gz0qw0y14fd2jnzfh71"; </ins> type = "gem"; <del> sha256 = "19qgpsfszwc2sfh6wixgky5agn831qq8ap854i1jqqhy1zsci3la"; </del> }; <ins> version = "0.9.10"; </ins> }; sass = { <del> version = "3.4.11"; </del> <ins> dependencies = ["sass-listen"]; </ins> source = { <ins> remotes = ["https://rubygems.org"]; sha256 = "19wyzp9qsg8hdkkxlsv713w0qmy66qrdp0shj42587ssx4qhrlag"; </ins> type = "gem"; <del> sha256 = "10dncnv7g5v8d1xpw2aaarxjjlm68f7nm02ns2kl8nf3yxi6wzdf"; </del> }; <ins> version = "3.5.6"; </ins> }; <del> therubyracer = { version = "0.12.1"; </del> <ins> sass-listen = { dependencies = ["rb-fsevent" "rb-inotify"]; </ins> source = { <ins> remotes = ["https://rubygems.org"]; sha256 = "0xw3q46cmahkgyldid5hwyiwacp590zj2vmswlll68ryvmvcp7df"; </ins> type = "gem"; <del> sha256 = "106fqimqyaalh7p6czbl5m2j69z8gv7cm10mjb8bbb2p2vlmqmi6"; </del> }; <del> dependencies = [ "libv8" "ref" ]; </del> <ins> version = "4.0.0"; </ins> }; uglifier = { <del> version = "2.7.0"; </del> <ins> dependencies = ["execjs"]; </ins> source = { <ins> remotes = ["https://rubygems.org"]; sha256 = "0dycp9c5xiricla6sgvg0vf22i3axs5k1v1607dvl7nv1xkkaczi"; </ins> type = "gem"; <del> sha256 = "1x1mnakx086l83a3alj690c6n8kfmb4bk243a6m6yz99s15gbxfq"; </del> }; <del> dependencies = [ "execjs" "json" ]; </del> <ins> version = "4.1.10"; </ins> }; <del> } </del> <ins> } </ins>  No newline at end of file

Discussion:
The consul-ui packages currently fails to build on 18.03 and master. On 18.03, applying the following patch causes the build to succeed: however, on master, it fails with: I've tried various things including using different versions of ruby and bundler, but none have solved the issue.
Change:
, pantheon }: <del> stdenv.mkDerivation rec { </del> <ins> stdenv.mkDerivation (finalAttrs: { </ins> pname = "epiphany"; <del> version = "46.0"; </del> <ins> version = "46.1"; </ins> src = fetchurl { <del> url = "mirror://gnome/sources/${pname}/${lib.versions.major version}/${pname}-${version}.tar.xz"; hash = "sha256-9DSPLPUcB8DBBtEwFy1NI/LNQGh3Hh3gB7dYyireVmA="; </del> <ins> url = "mirror://gnome/sources/epiphany/${lib.versions.major finalAttrs.version}/epiphany-${finalAttrs.version}.tar.xz"; hash = "sha256-Jg+BRp7WR0bCsRQ/Lzi+3NloR3hlZ7CX2fcv072dsUI="; </ins> }; nativeBuildInputs = [

Discussion:
Package name: Latest released version: 46.0 <!-- Search your package here: --- Current version on the unstable channel: 46.0 Current version on the stable/release channel: 46.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: Fixes very annoying bug for users with nvidia dGPU notebooks on gnome using external displays. Reports of the Bug:
Change:
# which is done by dlopening $out/lib/security/pam_foo.so # $out/etc was also missed: pam_env(login:session): Unable to open config file <del> preConfigure = '' configureFlags="$configureFlags --includedir=$out/include/security" '' + stdenv.lib.optionalString (stdenv.hostPlatform.libc == "musl") '' </del> <ins> preConfigure = stdenv.lib.optionalString (stdenv.hostPlatform.libc == "musl") '' </ins> # export ac_cv_search_crypt=no # (taken from Alpine linux, apparently insecure but also doesn't build O:)) # disable insecure modules

Discussion:
Describe the bug pamtime only uses the example config file in NixOS and is useless without overriding and rebuilding almost every other package. To Reproduce Steps to reproduce the behavior: to add to all pam.d config files. and add . and attempt to ssh as into the machine log in. Expected behavior In the example above, I would expect ssh to forbid from logging in at any time. Additional context Ideally, upstream linux-pam would allow pamtime to be configured at run time similarly to pamenv. However, I would still expect to be able to use pamtime without overriding the linux-pam package to manually change the location of In the current setup, pamtime only ever looks at the example file in the linux-pam package which makes it effectively useless. If the package is overridden to use a different location for that one file, a massive number of packages then needs to be rebuilt manually as they in one way or another depend on pam. Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(locus): nixpkgs:
It looks like we may just need to pass and to fix this.
Try this PR:
Change:
rtw88-firmware = callPackage ../os-specific/linux/firmware/rtw88-firmware { }; <ins> rtw89-firmware = callPackage ../os-specific/linux/firmware/rtw89-firmware { }; </ins> s3ql = callPackage ../tools/backup/s3ql { }; sass = callPackage ../development/tools/sass { };

Discussion:
Project description The driver supports Realtek 8852AE, which is a wifi card for some new laptops. Without the driver, the wireless interface would be missing for those computers. (My new Lenovo laptop uses this card and I cannot connect to WiFI currently... I'm not entirely sure how to package this) Metadata homepage URL: source URL: license: GPA 2.0 platforms: Linux
Change:
}; inherit (jami) jami-daemon jami-client-qt; <del> jitsi-meet-electron = callPackage ../applications/networking/instant-messengers/jitsi-meet-electron { electron = electron_17; }; </del> <ins> jitsi-meet-electron = callPackage ../applications/networking/instant-messengers/jitsi-meet-electron { }; </ins> zenstates = callPackage ../os-specific/linux/zenstates {};

Discussion:
The package can no longer be installed because one of its dependencies () has been marked EOL. Steps to reproduce the behavior: Please run and paste the result.
Change:
checkedSystemdBootBuilder = pkgs.runCommand "systemd-boot" { nativeBuildInputs = [ pkgs.mypy ]; } '' <del> install -m755 ${systemdBootBuilder} $out </del> <ins> mkdir -p $out/bin install -m755 ${systemdBootBuilder} $out/bin/systemd-boot-builder </ins> mypy  --no-implicit-optional  --disallow-untyped-calls  --disallow-untyped-defs  <del> $out </del> <ins> $out/bin/systemd-boot-builder </ins> ''; finalSystemdBootBuilder = pkgs.writeScript "install-systemd-boot.sh" '' #!${pkgs.runtimeShell} <del> ${checkedSystemdBootBuilder} "$@" </del> <ins> ${checkedSystemdBootBuilder}/bin/systemd-boot-builder "$@" </ins> ${cfg.extraInstallCommands} ''; in {

Discussion:
Because systemd-boot- gets stored straight up as (as a file in ), Python imports will crawl through the whole directory to try and find local .py files that can be imported. This can take very long and a lot of RAM. We hit into this on which has 40M entries in its right now, causing to take 5-10minutes and 10GB of RAM to execute. Steps to reproduce the behavior: up your with a LOT of entries to a new configuration with systemd-boot as the configured bootloader. Switching to a new configuration doesn't take 5+ minutes and 10GB of RAM, but is instead near-instantaneous. n/a Stack trace taken 1min into the execution of the script showing it's stuck trying to import stuff: This is on NixOS 23.05 but I don't see any change that would impact this in 23.11 or master. Would love a backport all the way to 23.05 if possible since we still haven't updated :) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Just to track the backport.
Maybe needs to be spinned off into a separate issue, but I think there are more Python scripts affected by this, such as or . Quick search:
No strong opinion, I don't personally care about getting those fixed right now so it might be easier if you filed it as a new issue if you're interested in working on it.
Will close this because this specific issue is solved, but feel free to open other issues for the other python scripts that suffer from this problem.
Change:
buildInputs = [ qtbase qtimageformats gtk3 libsForQt5.libdbusmenu enchant2 lz4 xxHash dee ffmpeg_4 openalSoft minizip libopus alsaLib libpulseaudio range-v3 <del> tl-expected microsoft_gsl hunspell </del> <ins> tl-expected hunspell </ins> # TODO: Shouldn't be required: pcre xorg.libpthreadstubs xorg.libXdmcp utillinux libselinux libsepol epoxy at-spi2-core libXtst ];

Discussion:
, CVSSv3=7.8 (nixos-20.03) Scanned versions: nixos-20.03: . Cc Cc
Change:
<ins> diff --git a/opencv_contrib/cudaoptflow/CMakeLists.txt b/opencv_contrib/cudaoptflow/CMakeLists.txt index e5b823ab4a..a728060d0b 100644 --- a/opencv_contrib/cudaoptflow/CMakeLists.txt +++ b/opencv_contrib/cudaoptflow/CMakeLists.txt @@ -11,18 +11,6 @@ ocv_define_module(cudaoptflow opencv_video opencv_optflow opencv_cudaarithm open set(NVIDIA_OPTICAL_FLOW_1_0_HEADERS_COMMIT "79c6cee80a2df9a196f20afd6b598a9810964c32") set(NVIDIA_OPTICAL_FLOW_1_0_HEADERS_MD5 "ca5acedee6cb45d0ec610a6732de5c15") set(NVIDIA_OPTICAL_FLOW_1_0_HEADERS_PATH "${OpenCV_BINARY_DIR}/3rdparty/NVIDIAOpticalFlowSDK_1_0_Headers") -ocv_download(FILENAME "${NVIDIA_OPTICAL_FLOW_1_0_HEADERS_COMMIT}.zip" -               HASH ${NVIDIA_OPTICAL_FLOW_1_0_HEADERS_MD5} -               URL -                 "https://github.com/NVIDIA/NVIDIAOpticalFlowSDK/archive/" -               DESTINATION_DIR "${NVIDIA_OPTICAL_FLOW_1_0_HEADERS_PATH}" -               STATUS NVIDIA_OPTICAL_FLOW_1_0_HEADERS_DOWNLOAD_SUCCESS -               ID "NVIDIA_OPTICAL_FLOW" -               UNPACK RELATIVE_URL) -if(NOT NVIDIA_OPTICAL_FLOW_1_0_HEADERS_DOWNLOAD_SUCCESS) -  message(STATUS "Failed to download NVIDIA_Optical_Flow_1_0 Headers") -else() -  add_definitions(-DHAVE_NVIDIA_OPTFLOW=1) -  ocv_include_directories(SYSTEM "${NVIDIA_OPTICAL_FLOW_1_0_HEADERS_PATH}/NVIDIAOpticalFlowSDK-${NVIDIA_OPTICAL_FLOW_1_0_HEADERS_COMMIT}") -endif()  No newline at end of file +add_definitions(-DHAVE_NVIDIA_OPTFLOW=1) +ocv_include_directories(SYSTEM "${NVIDIA_OPTICAL_FLOW_1_0_HEADERS_PATH}") </ins>

Discussion:
Describe the bug OpenCV 4 fails to build with cuda enabled due to missing NVIDIA optical flow sdk To Reproduce Steps to reproduce the behavior: -build -A opencv4 Expected behavior Either we disable OpenCV 4's option to compile with the NVIDIA optical flow SDK or allow compilation against the NVIDIA optical flow sdk headers. See: I've done some preliminary work towards this on the following branch:
Change:
LUA_PATH  = "${lgi}/share/lua/${lua.luaversion}/?.lua;;"; postInstall = '' <del> wrapProgram $out/bin/awesome  </del> <ins> # Don't use wrapProgram or or the wrapper will duplicate the --search # arguments every restart mv "$out/bin/awesome" "$out/bin/.awesome-wrapped" makeWrapper "$out/bin/.awesome-wrapped" "$out/bin/awesome"  </ins> --set GDK_PIXBUF_MODULE_FILE "$GDK_PIXBUF_MODULE_FILE"  --add-flags '--search ${lgi}/lib/lua/${lua.luaversion}'  --add-flags '--search ${lgi}/share/lua/${lua.luaversion}' 

Discussion:
On NixOS 19.03 When running the Awesome Window Manager, if it's restarted within the same X session (e.g. by sending a or with the default shortcut ), the same options are to the command line. Example of relevant NixOS configuration: using into an X session that uses the a terminal and run that is highlighted twice in line with awesome, e.g. by pressing that the number of times that is highlighted has doubled, i.e. the options have been appended to the previous command. Note that is not affected, i.e. the options for those modules is not re-appended on restarts: NixOS system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: awesome 4.3 (Too long) Compiled against Lua 5.2.4 (running with Lua 5.2) D-Bus support: execinfo support: xcb-randr version: 1.6 LGI version: 0.9.2
AwesomeWM restarts via . In NixOS, is used to generate a wrapper around the real binary. calls with . I guess this is what makes awesomeWM run the wrapper again on restart. Without this would directly restart itself instead of the wrapper, I think. output in tools like would change, showing the real binary instead of the wrapper as the command being run (this could be an unintended side effect of dropping the argument).
I see. I am not sure about actual consequences of this behavior, but it seems to worth a fix. Would using directly rather than help?
I have tried this out and That is correct, and in fact the issue of the repeated options disappears altogether This does not happen with my patch (see below) where I rename the executable the same way does, but I use without the argument. (Incidentally, I have discovered that calling creates a file , obviously because of the wrapper) What do you think? could this be merged (I already have the commit so submitting a PR would be quick)
Well, I'd prefer a version that sounds less like "awesome is doing something wrong". How about "or the wrapper will duplicate the --search arguments every restart"?
Sure, your wording make definitely more sense and is more accurate. If that's OK, I can prepare a PR.
Change:
<ins> { lib, buildPythonPackage, fetchFromGitHub, flit-core, mdformat, mdit-py-plugins, pytestCheckHook, }: buildPythonPackage rec { pname = "mdformat-gfm-alerts"; version = "1.0.1"; pyproject = true; src = fetchFromGitHub { owner = "KyleKing"; repo = "mdformat-gfm-alerts"; rev = "refs/tags/v${version}"; hash = "sha256-2EYdNCyS1LxcEnCXkOugAAGx5XLWV4cWTNkXjR8RVQo="; }; build-system = [ flit-core ]; dependencies = [ mdformat mdit-py-plugins ]; nativeCheckInputs = [ pytestCheckHook ]; pythonImportsCheck = [ "mdformat_gfm_alerts" ]; meta = { description = "Format 'GitHub Markdown Alerts', which use blockquotes to render admonitions"; homepage = "https://github.com/KyleKing/mdformat-gfm-alerts"; changelog = "https://github.com/KyleKing/mdformat-gfm-alerts/releases/tag/v${version}"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ sigmanificient ]; }; } </ins>

Discussion:
Project description An plugin for . "Alerts" are a block quote variation of admonitions that were proposed in this and are currently a separate extension of the . Metadata homepage URL: source URL: license: mit platforms: all (python) This package will allow to properly process the admonition in md files as written on GitHub. Without the plugin will escape the square brackets in the admonitions. will become the following without the : Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<ins> diff --git a/ccx_2.15/src/Makefile b/ccx_2.15/src/Makefile index 9cab2fc..6e977b8 100755 --- a/ccx_2.15/src/Makefile +++ b/ccx_2.15/src/Makefile @@ -1,6 +1,6 @@ CFLAGS = -Wall -O3  -I ../../../SPOOLES.2.2 -DARCH="Linux" -DSPOOLES -DARPACK -DMATRIXSTORAGE -DNETWORKOUT -FFLAGS = -Wall -O3 +FFLAGS = -Wall -O3 CC=cc FC=gfortran @@ -18,15 +18,10 @@ OCCXF = $(SCCXF:.f=.o) OCCXC = $(SCCXC:.c=.o) OCCXMAIN = $(SCCXMAIN:.c=.o) -DIR=../../../SPOOLES.2.2 +LIBS = -lpthread -lm -lc -lspooles -larpack -lopenblas -LIBS =  -       $(DIR)/spooles.a  -	../../../ARPACK/libarpack_INTEL.a  -       -lpthread -lm -lc - -ccx_2.15: $(OCCXMAIN) ccx_2.15.a  $(LIBS) -	./date.pl; $(CC) $(CFLAGS) -c ccx_2.15.c; $(FC)  -Wall -O3 -o $@ $(OCCXMAIN) ccx_2.15.a $(LIBS) +ccx_2.15: $(OCCXMAIN) ccx_2.15.a +	$(CC) $(CFLAGS) -c ccx_2.15.c; $(FC)  -Wall -O3 -o $@ $(OCCXMAIN) ccx_2.15.a $(LIBS) ccx_2.15.a: $(OCCXF) $(OCCXC) ar vr $@ $? </ins>

Discussion:
Three-Dimensional Structural Finite Element Program Website: Current stable: v2.15 Example of other distro builds:
I propose that we rename this package to calculix-ccx. Should I open a new ticket for that ? Edit: request -
Change:
- [c2FmZQ](https://github.com/c2FmZQ/c2FmZQ/), an application that can securely encrypt, store, and share files, including but not limited to pictures and videos. Available as [services.c2fmzq-server](#opt-services.c2fmzq-server.enable). <ins> - [preload](http://sourceforge.net/projects/preload), a service that makes applications run faster by prefetching binaries and shared objects.  Available as [services.preload](#opt-services.preload.enable). </ins> ## Backward Incompatibilities {#sec-release-23.11-incompatibilities} - `network-online.target` has been fixed to no longer time out for systems with `networking.useDHCP = true` and `networking.useNetworkd = true`.

Discussion:
Project description Runs as a daemon and records statistics about usage of programs using Markov chains; files of more frequently-used programs are, during a computer's spare time, loaded into memory. Metadata homepage URL: source URL: license: gpl2 platforms: linux
Same here! Preload can really help out when using Linux on older hardware or when using programs that generally take long to start.
Change:
rev = "refs/tags/v1.14.1"; hash = "sha256-ZVSdk6LeAiZpQrrzLxphMbc1b3rNUMpcxcXPP8s/5tE="; }; <ins> cutlass = fetchFromGitHub { owner = "NVIDIA"; repo = "cutlass"; rev = "v3.0.0"; sha256 = "sha256-YPD5Sy6SvByjIcGtgeGH80TEKg2BtqJWSg46RvnJChY="; }; </ins> in <del> stdenv.mkDerivation rec { </del> <ins> effectiveStdenv.mkDerivation rec { </ins> pname = "onnxruntime"; <del> version = "1.16.3"; </del> <ins> inherit version; </ins> src = fetchFromGitHub { owner = "microsoft";

Discussion:
Project description ONNX Runtime: cross-platform, high performance ML inferencing and training accelerator . Onnxruntime is already packaged. I would like to have the version with gpu support to be able to package obs-backgroundremoval with gpu support (). Related: Metadata homepage URL: source URL: license: mit platforms: linux
Obs-backgroundremoval includes tensorrtproviderfactory.h to build
need it, too
Is it possible to add gpu support to the obs-backgroundremoval as this issue is closed?
It may be possible. If anyone wants to open a PR for that, please base it on the current update PR
Change:
--zsh <($out/bin/atlas completion zsh) ''; <ins> passthru.tests.version = testers.testVersion { package = atlas; command = "atlas version"; version = "v${version}"; }; </ins> meta = with lib; { description = "A modern tool for managing database schemas"; homepage = "https://atlasgo.io/";

Discussion:
Package name: atlas Latest released version: 0.15.0 <!-- Search your package here: --- Current version on the unstable channel: 0.14.1 Current version on the stable/release channel: Not packaged <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
I've made some progress on the updating the package with the new dependencies. Currently, I've encountered an issue where it can't find postgres.h. I'm sure it's something simple I'm missing, and I don't have the time right now. So, I thought I would share what I got so far. (:
Yup I'm stuck there as well. I think the issue has to do with this change in atlas: cmd/internal/sqlparse/pgparse: move to pgquery () I was able to find this from discourse: Trying the solution mentioned in the discourse leads to a different error and the runVend flag does not work either.
For those who need cloud support, look at the derivation in this comment: