Can't run ./build.ksh with ksh93u+m

I just built ksh93u+m, statically linked, default options, added the kshrc provided by them to /etc and then cloned this repo and tried to build:

I am on Andes/Alpine, which uses Busybox.

Simple: mktemp wasn't installed.
I think the check/dependencies target may need to be run sooner, or maybe just don't use mktemp since we wouldn't need all this security just for some junk files.

Simple: mktemp wasn't installed. I think the check/dependencies target may need to be run sooner, or maybe just don't use mktemp since we wouldn't need all this security just for some junk files.

mktemp is installed tho.

Strange... Maybe check the PATH?

Where exactly is mktemp being used tho? So that I plug a a set -v or maybe a set -x there.

It's used to create the $trash directory.

It's the most jokingly-said phrase possible, but "it works on my machine".

Can I set the "trash" env to point to a local dir or smth?

It's the most jokingly-said phrase possible, but "it works on my machine".

Would you mind doing a git diff origin/master to check if your local repo differs from the remote?

Sure, just edit out the build.ksh file. It's pretty readable because I wanted to keep it just as a set of instructions.

It's the most jokingly-said phrase possible, but "it works on my machine".

Would you mind doing a git diff origin/master to check if your local repo differs from the remote?

Sure. Give me one minute.

The only thing that differs here is the header of helpers.shi:
$ git diff origin/copaclang
diff --git a/build-system/internals/helpers.shi b/build-system/internals/helpers.shi
index 40e6db2..8b0dfbe 100644
--- a/build-system/internals/helpers.shi
+++ b/build-system/internals/helpers.shi
@@ -1,5 +1,5 @@
 # vim: set filetype=sh :
-# Internal helper library for the Copacabana build system.
+# General helper library for the Copacabana build system.
 # Meant to be used with Korn Shell 93.

The only thing that differs here is the header of helpers.shi:
$ git diff origin/copaclang
diff --git a/build-system/internals/helpers.shi b/build-system/internals/helpers.shi
index 40e6db2..8b0dfbe 100644
--- a/build-system/internals/helpers.shi
+++ b/build-system/internals/helpers.shi
@@ -1,5 +1,5 @@
 # vim: set filetype=sh :
-# Internal helper library for the Copacabana build system.
+# General helper library for the Copacabana build system.
 # Meant to be used with Korn Shell 93.

That's the default branch, right? I used git clone URL, I didn't add -b

Sure, just edit out the build.ksh file. It's pretty readable because I wanted to keep it just as a set of instructions.

It's defined here:
https://github.com/Projeto-Pindorama/copacabana/blob/766d46588f472ee9f80a7b6b2f1fcf8a7d126334/build.ksh#L29

That's the default branch, right? I used git clone URL, I didn't add -b

Yes, it is, but you can check with git branch and see if you're on it.

I did, its copaclang on my end

The issue is that you didn't use mkdir -p to create the directory mktemp is supposed to create the temp dir in. And also, think its better to define $TRASH_PREFIX on ./build.ksh instead of some internal helper, for readability's sake.

And also, think its better to define $TRASH_PREFIX on ./build.ksh instead of some internal helper, for readability's sake.

It's defined on a .INI file.

Could you consider using the log_ functions defined here? I think they look more appealing than the current log output of ./build.ksh, but its a matter of personal taste. https://github.com/xplshn/Andes/blob/master/layout/etc/profile.d/std.sh

And also, think its better to define $TRASH_PREFIX on ./build.ksh instead of some internal helper, for readability's sake.

It's defined on a .INI file.

Ahh, okay. Sorry then. My bad

The issue is that you didn't use mkdir -p to create the directory mktemp is supposed to create the temp dir in. And also, think its better to define $TRASH_PREFIX on ./build.ksh instead of some internal helper, for readability's sake.

Well, can I? I would, for sure.
I'm refactoring all of the build system and this part is bugging me.

By the way, it currently doesn't compile anything, I will be rewriting the pkgbuild files at Alambiko and make some modifications here in my end.

By the way, it currently doesn't compile anything, I will be rewriting the pkgbuild files at Alambiko and make some modifications here in my end.

Ah... ah... I thought it, did..? I thought that it'd build a rootfs at least. Think mkroot from Toybox is a good starting point, you build with that and then you can swap out all of Toybox binaries with Heirloom, and leave only the toybox binaries that heirloom doesn't have (yet).
BTW: It isn't able to find true, which is a builtin, I used bigdl add busybox/true to explicitly add the true command as an external command into ~/.local/bin, which is part of my $PATH, but it didn't change much.

By the way, it currently doesn't compile anything, I will be rewriting the pkgbuild files at Alambiko and make some modifications here in my end.

Ah... ah... I thought it, did..? I thought that it'd build a rootfs at least.

The 0.4. rootfs was made manually by me back in 2022, now I'm trying to automatize the process with all of this.

Think mkroot from Toybox is a good starting point, you build with that and then you can swap out all of Toybox binaries with Heirloom, and leave only the toybox binaries that heirloom doesn't have (yet).

I have taken it in consideration to do pure cross-compiling of Copacabana. I'm just worried with some complex packages that we will have to deal with when making a desktop operating system, such as libdbus, pipewire, Xorg, KDE etc.

BTW: It isn't able to find true, which is a builtin, I used bigdl add busybox/true to explicitly add the true command as an external command into ~/.local/bin, which is part of my $PATH, but it didn't change much.

Weird.
Maybe I'm committing some of Sun's error with this, but this build-system isn't meant to be the most portable thing in the entire universe since I think only of building Copacabana from itself or from some other Linux system using at least some part of Copacabana's userland, that is, Heirloom NG, so I think most of these bugs can be avoided using Heirloom NG.
By the way, maybe we can fix these anyway in the platform checks, such as hashing true into busybox true if we end up finding busybox in the system.

By the way, it currently doesn't compile anything, I will be rewriting the pkgbuild files at Alambiko and make some modifications here in my end.

Ah... ah... I thought it, did..? I thought that it'd build a rootfs at least.

The 0.4. rootfs was made manually by me back in 2022, now I'm trying to automatize the process with all of this.

Think mkroot from Toybox is a good starting point, you build with that and then you can swap out all of Toybox binaries with Heirloom, and leave only the toybox binaries that heirloom doesn't have (yet).

I have taken it in consideration to do pure cross-compiling of Copacabana. I'm just worried with some complex packages that we will have to deal with when making a desktop operating system, such as libdbus, pipewire, Xorg, KDE etc.

Oh. I thought that you weren't going to ship those until v2 or later. Check out iglunix, GNU-less Linux distro, great amount of packages for what it is. Its all MUSL.
I think KDE is a bit overkill, maybe Trinity would appeal more to the kind of people who would use a Linux distro with utilities originally made by Sun Microsystems. Or maybe no desktop at all (me), or maybe no graphical environment at all (me)...

BTW: It isn't able to find true, which is a builtin, I used bigdl add busybox/true to explicitly add the true command as an external command into ~/.local/bin, which is part of my $PATH, but it didn't change much.

Weird. Maybe I'm committing some of Sun's error with this, but this build-system isn't meant to be the most portable thing in the entire universe since I think only of building Copacabana from itself or from some other Linux system using at least some part of Copacabana's userland, that is, Heirloom NG, so I think most of these bugs can be avoided using Heirloom NG.
By the way, maybe we can fix these anyway in the platform checks, such as hashing true into busybox true if we end up finding busybox in the system.

No need. Making it POSIX would be the best to ensure that it builds on POSIX systems... Comparing heirloom to other utils will uncover bugs in heirloom, so that's, good...

I think KDE is a bit overkill, maybe Trinity would appeal more to the kind of people who would use a Linux distro with utilities originally made by Sun Microsystems. Or maybe no desktop at all (me), or maybe no graphical environment at all (me)...

Well, the question is that I want to give options in the same measure that things keep formalized.
I want to ship KDE as the default desktop environment, but also have an option to install Enlightenment 16 as a simple window manager or to install the system with nothing beside its base; all of these can be decided on the install.
I like Trinity, but KDE have gotten better optimized lately (since at least 2020) and it provides a pretty much plain experience as an UNIX desktop.
Anyway, we still have to make dbus, pipewire and such work because other software may depend on these.

No need. Making it POSIX would be the best to ensure that it builds on POSIX systems... Comparing heirloom to other utils will uncover bugs in heirloom, so that's, good...

The biggest problem here is that I've abused "booleans" (/bin/true and /bin/false) instead of using integers or more portable measures.
I think these can be fixed per using a compatibility fix on the platform checks, though.

I think KDE is a bit overkill, maybe Trinity would appeal more to the kind of people who would use a Linux distro with utilities originally made by Sun Microsystems. Or maybe no desktop at all (me), or maybe no graphical environment at all (me)...

Well, the question is that I want to give options in the same measure that things keep formalized. I want to ship KDE as the default desktop environment, but also have an option to install Enlightenment 16 as a simple window manager or to install the system with nothing beside its base; all of these can be decided on the install. I like Trinity, but KDE have gotten better optimized lately (since at least 2020) and it provides a pretty much plain experience as an UNIX desktop. Anyway, we still have to make dbus, pipewire and such work because other software may depend on these.

As long as these never become part of base... (dbus, pipewire, *udev)
I think mdev does the work just fine and libudev-zero can be installed as a dependency of wayland things by the packages of kde, etc.
Also, I suggest not trying to package the world (everything out there), because it'd be lots of time/work, and I think what currently needs attention is the base itself.
For now, if you want to do a base and graphical release, you could ship a single-file GUI environment, like I have:

The only thing I have added to my system is this file + the config file of sway and the mesa package. The .blob/.AppBundle can be generated from an Alpine Linux install (since its small, and lots of its packages are using -static libraries where possible, also, its musl based, so the .AppBundles/.blobs are lighter.)

No need. Making it POSIX would be the best to ensure that it builds on POSIX systems... Comparing heirloom to other utils will uncover bugs in heirloom, so that's, good...

The biggest problem here is that I've abused "booleans" (/bin/true and /bin/false) instead of using integers or more portable measures. I think these can be fixed per using a compatibility fix on the platform checks, though.

I think staying withing $0 and avoiding calls to external programs as much as possible is the way to go. See the pure sh bible, it also enhances readability to create constructs/function to replace external commands/shorten other constructs, such as: ifXdo (a call to [ "$X ] && "$@")

As long as these never become part of base... (dbus, pipewire, *udev)

You can rest assured: it won't.
The main reason of me creating Copacabana was to understand how to build a better future learning with a past that was forgotten in books and old UNIX systems, but also not ignoring necessities of the present.
Just like CDE didn't became inherent part of Solaris, AIX nor any other UNIX systems when it came out, KDE won't become inherent part of Copacabana's base system, it's just part of the (yet theoretical) desktop.tar.xz stage.

As long as these never become part of base... (dbus, pipewire, *udev)

You can rest assured: it won't. The main reason of me creating Copacabana was to understand how to build a better future learning with a past that was forgotten in books and old UNIX systems, but also not ignoring necessities of the present. Just like CDE didn't became inherent part of Solaris, AIX nor any other UNIX systems when it came out, KDE won't become inherent part of Copacabana's base system, it's just part of the (yet theoretical) desktop.tar.xz stage.

Have you considered sets for packages with lots of dependencies, such as kde? I think you could take a look at the Illumos-based system Tribblix, which uses a very simple yet great, in my opinion, approach to package management.

For now, if you want to do a base and graphical release, you could ship a single-file GUI environment, like I have

That's really interesting for other reasons, but for the environment I would like to start "proto-packaging" things like it will be on pacote.
I don't think pacote will be done until the end of this month, but at least we can start generating tarballs for each package.

Have you considered sets for packages with lots of dependencies, such as kde? I think you could take a look at the Illumos-based system Tribblix, which uses a very simple yet great, in my opinion, approach to package management.

Sure! I've thought about these alone, but later I had seen what Tribblix does.
The best part is the fact that it uses a SVR4-esque package managenment, so we would still use pacote in the base of it.

I think staying withing $0 and avoiding calls to external programs as much as possible is the way to go. See the pure sh bible, it also enhances readability to create constructs/function to replace external commands/shorten other constructs, such as: ifXdo (a call to [ $X ] && "$@")

I've taken KornShell 93 exactly for this reason, mostly because it provides many things that in POSIX are nonexistent and that would need to be mimicked by external programs.
To address this issue of true/false, maybe we could create an Bool() function that check whether it's false or true.

I'm closing because the issue is on my end. I was trying to build copaclang without using a heirloom-ng $PATH. I haven't tested that yet. But I'll close the issue.

I think staying withing $0 and avoiding calls to external programs as much as possible is the way to go. See the pure sh bible, it also enhances readability to create constructs/function to replace external commands/shorten other constructs, such as: ifXdo (a call to [ $X ] && "$@")

I've taken KornShell 93 exactly for this reason, mostly because it provides many things that in POSIX are nonexistent and that would need to be mimicked by external programs.
To address this issue of true/false, maybe we could create an Bool() function that check whether it's false or true.

Makes sense. I was going to suggest Go instead of SH scripting. But then realized that had it not been because this is shell I wouldn't have been able to correct the mktemp line so easily, test again, modify and test again.

I think some ideas here are interesting, you can move something to a new issue if you wish to. I'm a little bit occupied working on the build system right now, but I will re-read the issue later and open a new issue for some of the advices you've given.

I was going to suggest Go instead of SH scripting.

Compiling a program to call a compiler to compile other programs sounds insane, I think shell is the way to go in this specific case, using plain and readable shell scripts, just like the AT&T crew would've done or Sun did until being sold to Oracle.
Many scripts here are still clumsy, so some refactor and more boilerplate (or façade) functions may be needed.

I think some ideas here are interesting, you can move something to a new issue if you wish to. I'm a little bit occupied working on the build system right now, but I will re-read the issue later and open a new issue for some of the advices you've given.

Okay, excellent! I'm going to do some work with bigdl. A complete overhaul is underway.

@takusuman Could you simply do "$DIR_PREFIX/$DIR_WHATEVER" so that it works with the POSIX mktemp? ("" is escaped in a ', commands should treat the "" as part of the filename).
]~/Documents/ItAll/copacabana< ./build.ksh
+ progname=build.ksh
+ dirname build.ksh
+ cd .
+ pwd -P
+ progdir=/home/anto/Documents/ItAll/copacabana
+ tasks=/home/anto/Documents/ItAll/copacabana/build-system/tasks
+ . /home/anto/Documents/ItAll/copacabana/build-system/internals/makier.ksh
+ _make checks/platform
+ lang=.ksh
+ tasks=/home/anto/Documents/ItAll/copacabana/build-system/tasks
+ tak=checks/platform
+ shift
+ printf %s/%s%s /home/anto/Documents/ItAll/copacabana/build-system/tasks checks/platform .ksh
+ . /home/anto/Documents/ItAll/copacabana/build-system/tasks/checks/platform.ksh $'\'\''
+ . /home/anto/Documents/ItAll/copacabana/build-system/internals/posix-alt.shi
+ . /home/anto/Documents/ItAll/copacabana/build-system/internals/log.shi
+ . /home/anto/Documents/ItAll/copacabana/build-system/internals/helpers.shi
+ BUILD_KSH=true
+ readonly BUILD_KSH
+ nawk '{ gsub("-", ""); print $NF; }'
+ printf %s 'Version AJM 93u+m/1.1.0-alpha+fa0ee840 2024-07-31'
+ KSH93_RELEASE=20240731
+ readonly KSH93_RELEASE
+ export BUILD_KSH KSH93_RELEASE
+ . /home/anto/Documents/ItAll/copacabana/build-system/internals/rconfig.shi
+ . /home/anto/Documents/ItAll/copacabana/build-system/internals/disks.shi
+ rconfig /home/anto/Documents/ItAll/copacabana/build-system/machine.ini
+ rconfig /home/anto/Documents/ItAll/copacabana/build-system/work.ini
+ rconfig /home/anto/Documents/ItAll/copacabana/build-system/fhs.ini
+ mktemp -d '"/tmp"/CopaBuild.XXXXXX'
mktemp: No such file or directory
+ trash=''
]~/Documents/ItAll/copacabana<

Good night.
Pardon for the delay, let me see what I can do.

I think that happened because of the new INI parser "bullet-proofing", I will fix that as soon as possible.

As long as these never become part of base... (dbus, pipewire, *udev)

I was going to ask: what about OpenPAM/LinuxPAM? Does it go in the base? I've been thinking about this lately.

As long as these never become part of base... (dbus, pipewire, *udev)

I was going to ask: what about OpenPAM/LinuxPAM? Does it go in the base? I've been thinking about this lately.

Have you seen how Gentoo has a SElinux & an Apparmor version? I think that the kernel and other closely related things such as the security blanket used and the PAM implementation that pair it should be in a different set as base, but maybe this adds more complexity... Still, if it is kept separated, that means that in the future, you'll have the flexibility to offer other configurations/options, just like Gentoo

Still, if it is kept separated, that means that in the future, you'll have the flexibility to offer other configurations/options, just like Gentoo

I want to kind of keep it as uniform because of stability, so reporting failures and bugs is easier than a system that you build completely from scratch. My thought on this is to have the stability that one would find in classic Solaris, SunOS, IRIX, etc.
I know that PAM is complex, but OpenPAM may be a palliative to it since it's considered simpler compared to LinuxPAM (as long as I've read). Anyway, I want to avoid linking some vital system utilities to it, such as the /sbin/login program.

OpenPAM as the default then I suppose. You should look at the work of Iglunix & Glauccus, both distros could be considered Linux based OSes and not GNU/Linux distributions


wallet sync calls batch_script_get_history internally when configured with Electrum blockchain

When setting up BDK with the Electrum blockchain and calling wallet_sync, then effectively WalletSync::wallet_setup will be called, which internally calls batch_script_get_histroy:
https://github.com/bitcoindevkit/bdk/blob/master/src/blockchain/electrum.rs#L142
Note: I noticed this in the logs, because we still see batch_script_get_history related errors when the wallet is syncing.
This might be another (small?) part of our memory growth. I find the implementation quite complex and could not fully understand with what scripts batch_script_get_history will be called, so it's hard for me to estimate how much memory we are talking about.

We cannot easily overcome this problem without reporting the memory growth problem in rust_electrum_client upstream.

This project is unmaintained


adding Massachusetts medicare exclusions crawler

I wasn't able to use the context.fetch_html and context.fetch_resource to get the data because it was returning with status code = 403.

try this https://zavod.opensanctions.org/metadata/#http-options


Dockerfile & shell files lint

Fixes #50

@Azanul can you fix it.

@Azanul can you fix lint errors.
And make sure shell lint is working here.

I did fix the errors but seems like I'll have to deal with warnings and style changes too

@Azanul We could ignore   DL3007,DL3018 here.

DL3007,DL3018

I think I should add a hadolint config file too

@Azanul We could ignore  DL3007,DL3018 here.

I think I should add a hadolint config file too

@Azanul remove the hadolint config file

Convert
RUN curl -fL -Lo /tmp/redis-${REDIS_VERSION}.tar.gz ${REDIS_DOWNLOAD_URL}/redis-${REDIS_VERSION}.tar.gz && \
    cd /tmp && \
    tar xvzf redis-${REDIS_VERSION}.tar.gz && \
    cd redis-${REDIS_VERSION} && \
    make && \
    make install BUILD_TLS=yes

to
RUN curl -fL -Lo /tmp/redis-${REDIS_VERSION}.tar.gz ${REDIS_DOWNLOAD_URL}/redis-${REDIS_VERSION}.tar.gz && \
    tar xvzf redis-${REDIS_VERSION}.tar.gz

WORKDIR /tmp/redis-${REDIS_VERSION}

RUN make && \
    make install BUILD_TLS=yes

@Azanul
i am not sure whether shell check actually ran or not ?
How could run complete in 0s

@shubham-cmyk Looks like it's working

@shubham-cmyk Looks like it's working
https://github.com/OT-CONTAINER-KIT/redis/actions/runs/6435805690/job/17477866384

Yup Looks Like it is working

Yup Looks Like it is working. It is very fast though.

It that skepticism or joy?

Yup Looks Like it is working. It is very fast though.

It that skepticism or joy?

Joy.
I was not sure earlier maybe the runner is not able to calculate the time.


Error: Parameter with logical ID 'AuthModeLastUpdated' was not found in the template

I have an amplify app and I exported it using export command to my cdk app.
When I run cdk deploy I have this following error :
Error: Parameter with logical ID 'AuthModeLastUpdated' was not found in the template

Experiencing the same issue
"Error: Parameter with logical ID 'AppSyncApiName' was not found in the template"

Same issue. @Khaldoun488 or @jjnaude did either of you find a workaround?

Nope :-(.
Abandoned the approach. The reason why I was trying to export my amplify project to CDK in the first place was because I wanted to deploy it to the AF-South region. I am in South Africa and had been prototyping on US-East-1, but for production purposes the latency for users in southern africa is too great. Turns out AF-South does not support Amplify. So I thought I could still deploy to AF-South by first exporting to CDK. After struggling with this for a few hours I tried deploying to EU-West-2, and the latency still isn't great, but it is acceptable for now. Hopefully someone solves this soon.


Directives changing the type of scalar

Is your feature request related to a problem? Please describe.
Currently I am using a mix of number ID and string ID for a project.
This is annoying since I can't override the default to be always number so the casting needs to happen inside the resolvers.
What I would like is adding a directive that does the casting for me. But then the typing would be wrong.
Describe the solution you'd like
(FYI I will code it once this is discussed by the community)
I think we should add a new setting for the typescript generator to allow directives to change the mapping of the scalar.
So let's take an example:
directive @AsNumber on
  | ARGUMENT_DEFINITION
  | INPUT_FIELD_DEFINITION

input MyInput {
  someId: ID! @AsNumber
}

type MyType {
  id: ID!
}

extend type Mutation {
  myMutation(id: ID! @AsNumber, input: MyInput!): MyType
}

We could then have a config like:
config:
  directives:
    AsNumber: 'number'

Describe alternatives you've considered
Mapping the ID inside the resolvers. This is really annoying when you have complex nested input objects with arrays.
Additional context

That sounds like an interesting addition! Although, I think the config option name should be more clear!
I recently started working on something similar for using a custom resolver function type based on the directive applied on the field: https://github.com/dotansimha/graphql-code-generator/pull/6330

@n1ru4l I build a first draft of it. It works great from the small testing I have done, I would appreciate your input on it 🙏

Implemented in https://github.com/dotansimha/graphql-code-generator/pull/6609


Auto link Trackers

If user is logged in, when manga info is grabbed or selected auto link to the tracking site

I hope this will be done soon would make my life so much easier

+1 to this ^^

Please make this optional per-tracker. In other words, under tracker settings, it should be possible to enable/disable automatically adding it.
Personally, while I think this would be useful, I'm satisfied with automatically adding the linked tracker entries instead of having to search for them.

Thinking of one way of doing it, since there can be diverse names for the same manga, would be if, for example, 10 people or more than half of the users added a specific mal, anilist, or other track from one mangadex manga, auto add the tracking to that. That way it will auto-select to the related manga in the trackers. One slider option could enable this feature. It would be a great feature since there is almost 200 manga i'm reading

@MaxEhrhart this is not needed since mangadex has relation links on the manga

To add. I already am storing every id for each manga. So its really trying to cleanly auto track. Which is hard to do cause that code is a bit of a mess

In 2.10.0


[Bug] Dashboard not work

Search before asking

[X] I had searched in the issues and found no similar issues.

Environment
Windows
EventMesh version
master
What happened
After the runtime address is configured on the Overview page, other pages do not get this configuration.

How to reproduce

Get the latest code.
Excute the command.
npm run dev
Visit http://localhost.3000 in your browser.
Configure the runtime address.
Visit the CLIENTS -> HTTP page.

Debug logs
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

hello my friend
i have the same problem
do you found a solution?

It's a known problem of the frontend. The frontend always tries to connect to the runtime on localhost. You can fix this by using a reverse proxy.
This issue is open for contribution. The source code is available at https://github.com/apache/eventmesh-dashboard/tree/nextjs-dashboard.


How to use web display result in unreal engine?

how to convert the web display result to mesh in unreal engine?
I can not find the save button

Hi, sorry to reach back such late. You need to implement THREE.OBJExporter to export the modeled road to a .obj file. You can refer to my messy version of the project here using the index.html.

Hi, Thank you. I may get a opendrive obj format file by convert the json file to obj by three.js convert web page
在 2018-12-19 17:09:56，"xmssp"<EMAIL_ADDRESS>写道：
Hi, sorry to reach back such late. You need to implement THREE.OBJExporter to export the modeled road to a .obj file. You can refer to my messy version of the project here using the index.html.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Make ready for Flask 2

Requires https://github.com/inveniosoftware/invenio-base/pull/160
Also requires https://github.com/klen/Flask-Collect/issues/85 to be fixed, or some workaround.

Created a fork of Flask-Collect, which fixes the above mentioned issue.
https://github.com/inveniosoftware/Flask-Collect-Invenio


[HUDI-3886] Adding default null for some of the fields in col stats in MDT schema

What is the purpose of the pull request
Adding default null for some of the fields in col stats in MDT schema
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@alexeykudinkin : can you stamp this

@nsivabalan done


Typescript project references cache not invalidated when @types/** version changes in package.json

Acknowledgement

[X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment
I'm tackling a monorepo utilizing TypeScript (v4.9.5) with project references for type checking across the repository. Recently, we transitioned to a new Node.js version (18.19.1), necessitating an update to @types/node in the package.json.
Upon running tsc -b tsconfig.json -v, TypeScript failed to type check the repository, citing the previous emitted cache as up to date. Consequently, it failed to detect errors in the code pertaining to changes in types introduced by the newer Node.js version.
When invoking tsc with the -b flag, my expectation was that TypeScript would invalidate the old cache due to the version change in @types/node. However, it didn't, indicating that the cache was already updated with the changes.
Is this behaviour expected?

You're nearly 5 TypeScript versions behind; can you try with a more recent version? Very possible this was fixed as there have been many build mode fixes in the last year+.

@jakebailey thanks for the quick response, but could you confirm if this is something that has been fixed in the next versions? Our monorepo is huge, and while we are actively planning on upgrading it to TS 5.0+, it's still might take us a few months, but if the upgrade does not fix it, we would have to actively plan out a solution for this particular edge case

There have been quite a few fixes to incremental mode since 4.9; I don't think I can remember if any in particular address this specific behavior. @sheetalkamat may have a better memory than I do.

tsc -b only checks for timestamps of files that are your "input" files specified in tsconfig.json and not all the unlisted dependencies. That means the change in node version would need you to force the rebuild instead of just normal build, unless you configure it some other way (which is not recommended)

@sheetalkamat thanks for the clarification. Closing this

@sheetalkamat - is there a way to bust cache for third party dependencies similar to
Input files?


Allow to Drag and drop files from explorer into working file to produce a URL link

VSCode Version: 1.4.0
OS Version: OSX El Capitan

Would like the ability to drag a file from the integrated explorer and have it create the relevant link in my html/js file - in the same way that Visual Studio Professional does

Thanks to @geektrainer for showing off this neat feature.

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!

duplicate of #34647


About padding sentences

Hi Ilivans,
In your implementation, you padded all training set to a fixed length: 250

X_train = zero_pad(X_train, SEQUENCE_LENGTH)
batch_ph = tf.placeholder(tf.int32, [None, SEQUENCE_LENGTH])
But I want to calculate this factor for each mini-batch, that's why I have to declare batch_ph of shape [None, None]. So in the attention.py file: sequence_length = inputs_shape[1].value will be "None" then the error will be appear in the command: exps = tf.reshape(tf.exp(vu), [-1, sequence_length]):
"Failed to convert object of type <class 'list'> to Tensor. Contents: [-1, None]. Consider casting elements to a supported type."
Do you have any idea for this problem?
Thank you in advance!

Hi Le The Anh,
Actually, I don't know when it's necessary to make variable maximum sequence length.
Nevertheless, it seems I have managed to solve your problem. The solution is to use tf.Tensor object as a shape argument for tf.reshape.
Let me know if there are any questions left.


Italic comment for C++

Hi
really like your "one" color scheme. thank you!
I used Vim with one color scheme to edit a cpp file today, and noticed that the comments are not italic, italic comment works fine with other file types.
italic comment for C++ used to work. not sure what is going wrong, might be vim itself.
Can you have a look please?
Thanks
B

Thanks! Appreciate you like this colorscheme.
The issue is not Vim, but a setting in the colorscheme that I just fixed. It's now fixed, let me know if that works properly.

Hi rakr
Thank you for the quick fix.
Yes, I really like your one color scheme.
Thank you :)
B

No worries, have a good one.


Which domain types do we need?

The CF conventions also cover domain types in chapter 9 "Discrete Sampling Geometries". They include Point, TimeSeries (we: PointSeries), Trajectory, Profile, TrajectoryProfile (we: Section) and have in addition to ours TimeSeriesProfile (which we would call ProfileSeries). Grid is not mentioned explicitly as it is the default way of how to store data in CF. They also define how to represent data for collections of same-type coverages and introduce a ragged array representation for that where e.g. the sequences of vertical coordinates for several profiles are stacked behind each other with an additional "count" variable to separate the profiles again (they also have an alternative ragged form with an "index" variable for real-time data where the count is unknown before-hand).
It is interesting that they don't have a MultiPointSeries ("MultiTimeSeries") type. Does this indicate that such coverage is very rare?

I can't think of a use case for MultiPointSeries. I don't think I've ever seen data like that.

I can't think of a use case for MultiPointSeries. I don't think I've
ever seen data like that.

Ok, let's remove it then.

From #7: We may need a MultiPolygon domain type which is useful when you cannot use a Grid with bounds, e.g. for things like land parcels.
I wonder if profiles for Polygons make sense, as in PolygonProfile or PolygonProfileSeries. What's the use case here?

I guess a PolygonProfile(Series) would occur when you have a timeseries (or profile) that has been aggregated from point data so that it is representative of a polygon. But I'm not sure we have a concrete use case yet. I'd be happy to remove them for the moment, although it may be worth considering "reserving" some names for future use so we don't end up with confusing names.

Linked to https://github.com/Reading-eScience-Centre/coveragejson/issues/24

Closing this. If any specific domain type is needed, let's open a new issue.


README

closes #7

PR-Codex overview
This PR updates the project description and adds several badges and information to the README.md file.
Detailed summary

Updated the project description in the pom.xml file.
Added several badges and information to the README.md file:

Self XDSD badge.
EO principles badge.
DevOps by Rultor.com badge.
IntelliJ IDEA recommendation badge.
Maven workflow badge.
Maven Central badge.
Javadoc badge.
Codecov badge.
Hits-of-Code badge.
Lines-of-Code badge.
PDD status badge.
License badge.

Added project architect information.
Added motivation section.
Added principles section.
Added "How to use" section with Maven dependency information.
Added "How to Contribute" section with instructions for contributing to the project.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@h1alexbel thank you for your Pull Request. I'll assign someone to review it soon.
If this PR solves a todo from the code, please don't forget to remove it.

@h1alexbel please review this Pull Request. Deadline (when it should be merged or closed) is 2023-08-13T11:09:16.279289.
You should check if the requirements have been implemented (partially or in full), if there are unit tests covering the changes and if the CI build passes. Feel free to reject the PR or ask for changes if it's too big or not clear enough.
Estimation here is 30 minutes, that's how much you will be paid. You will be paid even if this PR gets rejected.

@rultor merte

@rultor merge

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 2min)

@h1alexbel thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard.


react-clone-referenced-element added to ignore

I get a syntax issue when using ListView which depends on react-clone-referenced-element.
Runtime Error
  - SyntaxError: Unexpected token ...
        at transformAndBuildScript (node_modules/jest-runtime/build/transform.js:306:10)
        at Object.<anonymous> (node_modules/react-native/Libraries/CustomComponents/ListView/ListView.js:44:28)
        at Object.ListView (node_modules/react-native/Libraries/react-native/react-native.js:39:23)

Thank you! We recommend to add this to your own preprocessorIgnorePattern, see http://facebook.github.io/jest/docs/tutorial-react-native.html#preprocessorignorepatterns-customization


TypeError: can't pickle _thread.RLock objects

ta.version : 0.6.3
I want to pickle and save the best model I get with Talos:
p = {
'batch_size': [512, 1024],
'epochs': [10],
'learn_rate': [0.1, 0.2, 0.3],
 'momentum': [0.2, 0.4, 0.6]}

scan_results = ta.Scan(x_train, y_train, params=p, model=create_model, experiment_name='exp', x_val=x_val, y_val=y_val, fraction_limit=0.1, seed=69420)

model_id = scan_results.data['val_acc'].astype('float').argmax() - 1
model = model_from_json(scan_results.saved_models[model_id])
model.set_weights(scan_results.saved_weights[model_id])

with open("best_model.pkl", 'wb') as output:
    pickle.dump(model, output, pickle.HIGHEST_PROTOCOL)

However, I'm facing the following error:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-5-35e5937f77d1> in <module>()
     59 # Save users dictionary
     60 with open("best_model.pkl", 'wb') as output:
---> 61     pickle.dump(model, output, pickle.HIGHEST_PROTOCOL)

TypeError: can't pickle _thread.RLock objects

I've tested that I can pickle a simple Keras as a stand-alone. However, I can't pickle the model I get from Talos.Scan.

Have a look at #156.

Also, it's not related with this directly, but I recommend upgrading Talos to >0.6.5 or then 1.0.

I'm closing this because it has nothing to do with Talos (but with Pickling and Tensorflow). It would be great if you can update the ticket with your resolution once you've found one.

I'm closing this because it has nothing to do with Talos (but with Pickling and Tensorflow). It would be great if you can update the ticket with your resolution once you've found one.

Thank you for your reply. Yes, you're right, it has something with Keras and Tensorflow. I will update as soon as I find a solution.

Also, it's not related with this directly, but I recommend upgrading Talos to >0.6.5 or then 1.0.

Please, how to upgrade Talos? When I do pip install talos, it installs version: 0.6.4


upgrade to league/oauth2-client:1.0.0-beta2

Doesn't this revert the toArray stuff you PR'd recently?

It does not revert. The toArray method is required in the ResourceOwnerInterface as of the beta2 release. The previous PR was a head start on that requirement. That solution manipulated the raw response data into a strict return array. After some discussion around that methods intent, it was decided that the toArray method is best suited to return the raw response. this PR includes that amendment and the appropriate changes to the test suite.
This PR will bring the package up to beta2 standards :)

Awesome, thanks!


[State Restoration][WIP] Restorable TextFormField

Description
Enabled the TextFormField to restore their scroll offset and their text content with the state restoration framework. It does not yet account for state restoration in the Form itself.
Related Issues
https://github.com/flutter/flutter/issues/62916
Tests
I added the following tests:

Tests to ensure that TextFormField is restorable.

Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

closing for now, haven't worked on this for a while and there are a bunch of merge conflicts building up

closing for now, haven't worked on this for a while and there are a bunch of merge conflicts building up


Missing parameter -Status for Get-AzVMRunCommand

Documentation suggests using Get-AzVMRunCommand with -Status parameter to get latest output from RunCommand script.
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/run-command-managed#get-execution-status-and-results-1
Get-AzVMRunCommand AzVMRunCommand -ResourceGroupName "myRG" -VMName "myVM" -Name "RunCommandName" -Status
However, no parameter -Status defined for Get-AzVMRunCommand and running sample command caused error.
https://docs.microsoft.com/ja-jp/powershell/module/az.compute/get-azvmruncommand?view=azps-7.3.2
Get-AzVMRunCommand: A parameter cannot be found that matches parameter name 'Status'.

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

ID: 187ea459-7121-0d9f-db71-be056218c415
Version Independent ID: 447d4d3a-f488-6516-9cc4-db1ad06bd9e5
Content: Run scripts in a Linux VM in Azure using managed Run Commands (preview) - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/run-command-managed.md
Service: virtual-machines
GitHub Login: @cynthn
Microsoft Alias: cynthn

في الثلاثاء، ٥ أبريل، ٢٠٢٢ ٠٩:٠٩ thiruma0203 @.***> كتب:

Documentation suggests using Get-AzVMRunCommand with -Status parameter to
get latest output from RunCommand script.
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/run-command-managed#get-execution-status-and-results-1
Get-AzVMRunCommand AzVMRunCommand -ResourceGroupName "myRG" -VMName "myVM"
-Name "RunCommandName" -Status
However, no parameter -Status defined for Get-AzVMRunCommand and running
sample command caused error.
https://docs.microsoft.com/ja-jp/powershell/module/az.compute/get-azvmruncommand?view=azps-7.3.2
Get-AzVMRunCommand: A parameter cannot be found that matches parameter
name 'Status'.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com
http://docs.microsoft.com ➟ GitHub issue linking.

ID: 187ea459-7121-0d9f-db71-be056218c415
Version Independent ID: 447d4d3a-f488-6516-9cc4-db1ad06bd9e5
Content: Run scripts in a Linux VM in Azure using managed Run
Commands (preview) - Azure Virtual Machines
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/run-command-managed#feedback
Content Source:
articles/virtual-machines/linux/run-command-managed.md
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/virtual-machines/linux/run-command-managed.md
Service: virtual-machines
GitHub Login: @cynthn https://github.com/cynthn
Microsoft Alias: cynthn

—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/91013, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYNVVDXAMU66XYKAE2FA5W3VDPKLDANCNFSM5SRUQD3Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@thiruma0203
Thank you for reaching out. At this time we are reviewing the ask and will provide an update as appropriate

@ju-shim Do you know what is happening with -status?

Hello @ju-shim
Any update on this?

Hello @thiruma0203,
I have assigned the issue to the content author to investigate further and update the document as appropriate.

#reassign @ju-shim

#reassign @ericd-mst-github
Apologies for the delay on addressing this issue. This is now assigned to the right content author and they will be able to address this issue and provide the right doc updates if necessary. Thank you for your patience!

#reassign: @ericd-mst-github

Hello, I apologize for the delay. We have reviewed with engineering and the -status parameter is not valid and there is a PowerShell bug for the cmd itself that is looking to be resolved by next week.
We have the '-Expand InstanceView` parameter as a workaround and updated our docs. Please let us know if that parameter is not working.


[BUG] The location field generated by logstash GeoIP filer does not get recognised as GeoJSON type (geo_point)

Describe the bug
The geoip filter in logstash generates a geopoint.location field, among others, that should be recognised as geo_json field but is instead split into 2 separate fields, geopoint.location.lon and geopoint.location.lat as numbers. This prevents the location to be used in map visualisations.
To Reproduce
Steps to reproduce the behavior:

Add this to the logstash filter (in my case the ip address is nested inside log_message)

filter {

    ...

    geoip {
        source => "[log_message][forwarded_ip_address]"
    }
}

data is successfully uploaded on my OpenSearch service
location is not recognised as a geo_point but instead I see 2 separate number fields geopoint.location.lon and geopoint.location.lat despite the template containing the following:

"geoip": {
          "dynamic": true,
          "properties": {
            "ip": {
              "type": "ip"
            },
            "latitude": {
              "type": "half_float"
            },
            "location": {
              "type": "geo_point"
            },
            "longitude": {
              "type": "half_float"
            }
          }
        },

Expected behavior
geopoint.location should not be split into separate fields but recognised as geo_point type.
Host/Environment (please complete the following information):

OS: AWS OpenSearch as a service
Version 1.2.0

Additional context
According to this page on AWS OpenSearch docs, ecs_compatibility must be set to disabled. This is relevant to the geoip filter and its mentioned it causes the filter to generate different outputs. At this point I wonder if this is the culprit since I cannot try another installation of OpenSearch other than the one I have on AWS.
Here is my "full"  logstash config if relevant:
input {
    file {

        ...

        codec => json {
            target => "[log_message]"
        }
  }
}

filter {

    ...

    geoip {
        source => "[log_message][forwarded_ip_address]"
    }
}

output {

  ...

  opensearch {

        ...

        ecs_compatibility => disabled
  }
}

Do you have a ticket with the Managed AWS OpenSearch support yet? I think you should open one.

Hi, @dblock
Sorry.
No I haven't. I'll do that. So you are saying that what I've done looks ok from what you can see?

Am I wrong to read this as something specific to the managed service? Can you reproduce the same problem in OpenSearch OSS?

I have a similar problem.
Opensearch 2.3.0
Logstash OSS 8.4.0
Ubuntu 20.04.5
filter:
geoip {
        database => "/opt/logstash/geoip/GeoLite2-City.mmdb"
        source => "visitor_ip"
        target => "geoip"
}

In discover, I see only geoip.geo.location.lon and geoip.geo.location.lat

At the same time, there is data in json:
"geoip": {
      "geo": {
        "location": {
          "lon": 24.7323,
          "lat": 59.433
        },
        "country_name": "Estonia",
        "country_iso_code": "EE",
        "city_name": "Tallinn"
      },
      "ip": "XX.XX.XX.XX"
    }
  },

I have a similar problem.
Opensearch 2.3.0 Logstash OSS 8.4.0 Ubuntu 20.04.5
filter:
geoip {
        database => "/opt/logstash/geoip/GeoLite2-City.mmdb"
        source => "visitor_ip"
        target => "geoip"
}

In discover, I see only geoip.geo.location.lon and geoip.geo.location.lat

At the same time, there is data in json:
"geoip": {
      "geo": {
        "location": {
          "lon": 24.7323,
          "lat": 59.433
        },
        "country_name": "Estonia",
        "country_iso_code": "EE",
        "city_name": "Tallinn"
      },
      "ip": "XX.XX.XX.XX"
    }
  },

The problem was solved by adding a parameter ecs_compatibility => "disabled"


improve(cli,client): track postinstall trigger

TODO

[x] ~send to telemetry~
[x] client unit tests
[x] ~client integration test~
[x] ~cli test~

Note: We agreed to skip the integration testing b/c of how expensive it would be to do.


vspk-javascript: generate locale file for every enum

Sample generated file content:
{
    "NUGatewayPersonalityEnum": {
        "DC7X50": "DC7X50",
        "EVDF": "EVDF",
        "EVDFB": "EVDFB",
        "HARDWARE_VTEP": "HARDWARE_VTEP",
        "NETCONF_7X50": "NETCONF_7X50",
        "NETCONF_THIRDPARTY_HW_VTEP": "NETCONF_THIRDPARTY_HW_VTEP",
        "NUAGE_210_WBX_32_Q": "NUAGE_210_WBX_32_Q",
        "NUAGE_210_WBX_48_S": "NUAGE_210_WBX_48_S",
        "OTHER": "OTHER",
        "VDFG": "VDFG",
        "VRSB": "VRSB",
        "VRSG": "VRSG",
        "VSA": "VSA",
        "VSG": "VSG"
    }
}

@natabal Code generator would generate one such file for every enum.
I shall write a python script within vsd-react-ui which will compare the content in generated locale files  against the content in src/i18n/locales/en/locales.json and append any missing locales.
Is this okay?


Make comms_ctx a required argument (not optional) to avoid possible conflicts

This is part of #205


Consider updating the @pulumi/pulumi package version requirement

As per community slack, we currently target version 0.16:
https://github.com/pulumi/pulumi-cloudflare/blob/master/sdk/nodejs/package.json#L16

This was done as part of #4.


clustergen: add all-shards cluster

Adds an all-shards cluster, which contains the shard definitions for each cluster specified in the ClickhouseInstallation. This is used by our query nodes to allow scattering reads across all clusters in the CHI while respecting the shard/replica.
Please check items PR complies to:

[x] All commits in the PR are squashed. More info
[x] The PR is made into dedicated next-release branch, not into master branch1. More info
[x] The PR is signed. More info

fixes #1291

Or even all-clusters-shards

You are ignored our recommendations about non-mental name all-shards #1291 (comment) could you please use another name like all-clusters?

Let me check what happened, I pushed the wrong code. We have it as chi-<cluster>

You are ignored our recommendations about non-mental name all-shards #1291 (comment) could you please use another name like all-clusters?

Fixed now. I've pushed the proper code, which changed the name to what you suggested in #1291 - chi-<cluster name>.  Please let me know if you'd prefer something else. Or maybe we could make it configurable?


Block device assignment should support xen and kvm device names

@eatonphil this still outstanding?

Yep.
On May 30, 2017 6:40 PM, "Matthew Parke"<EMAIL_ADDRESS>wrote:

@eatonphil https://github.com/eatonphil this still outstanding?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/linode/manager/issues/1404#issuecomment-305029284,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADvnmBJVMp3BkjSi6VqO7amXwOLmcv2Zks5r_Jr4gaJpZM4MhGXU
.

The Rescue and Config disk lists should show xvda instead of sda (etc).

src/linodes/linode/settings/advanced/components/CreateOrEditConfig.js
src/linodes/linode/components/RescueMode.js

The api will accept "sda" or "xvda" lettering as appropriate.  It will return "xvda" for disk configs and the config list page currently does not handle that properly.


removed properties from score spec

Description
We are planning to deprecate resource properties in the Score spec: https://github.com/score-spec/spec/issues/61
What does this PR do?
It removes resource properties from the example score.yaml files we store in this repo
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New chore (expected functionality to be implemented)

Checklist:

[x] My change requires a change to the documentation.

[x] I have updated the documentation accordingly.

[x] I've signed off with an email address that matches the commit author.

Ready for the code review.


cloudflared: 2023.2.1 -> 2023.2.2

Description of changes
https://github.com/cloudflare/cloudflared/releases/tag/2023.2.2
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

1 package built:

cloudflared


check clean up

Codecov Report

Merging #256 (430a31b) into main (afa7233) will decrease coverage by 0.15%.
The diff coverage is 63.63%.

@@            Coverage Diff             @@
##             main     #256      +/-   ##
==========================================
- Coverage   94.84%   94.68%   -0.16%
==========================================
  Files          21       21
  Lines        2481     2483       +2
==========================================
- Hits         2353     2351       -2
- Misses        128      132       +4

Impacted Files
Coverage Δ

R/get_vaa.R
80.00% <ø> (ø)

R/subset_nhdplus.R
88.18% <63.63%> (-1.04%)
:arrow_down:

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 afa7233...430a31b. Read the comment docs.


Update versioning-basics-best-practices.md

Removed content about storage usage that has been causing customer confusion.
Please use this template to ensure easier processing of your pull request
Category

[x] Content fix
[ ] New article

Related issues
Contents of the Pull Request
Removed some text that was misleading. Also fixed the absolute link in the build report.
Guidance

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

File
Status
Preview URL
Details

Community/versioning-basics-best-practices.md
:bulb:Suggestion
View
Details

Community/versioning-basics-best-practices.md

Line 92, Column 14: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/sharepoint/governance/versioning-content-approval-and-check-out-planning' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 6f011d0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/versioning-basics-best-practices.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@kaarins - Thanks for making that clearer.
On the absolute link thing, I've been ignoring those warnings because it allows us to test the links in the articles here. Without the absolute links, they don't work. How do you handle this on your end? We had someone looking into this a few months ago, but I don't think we ever heard anything back from them.
cc: @daisyfell @pamgreen-msft


Health logs for find / replace in files, instant search usage.

Sould be helpful in seeing how people are using the new search features.

Targeting this to master.


Login url

Looks like this one was from some debugging/testing and there are a lot of gate and fiat changes since. Do we want to just get rid of this PR and branch?


Agent SSL error: peer certificate cannot be authenticated

I'm seeing the following error when running with agent sdk in embedded mode:
[DEBUG] runtime_error sending metric data: Peer certificate cannot be authenticated with given CA certificates (CURLcode=60)

From the commandline curl, I can set the environment variable CURL_CA_BUNDLE (see point 4 in curl documentation), but this does not affect programs using libcurl.
What CA bundle is the agent attempting to use? Can I change it through an environment variable or other means?

This happens when running the embedded collector inside nginx. I've tested the embedded collector in a simple "hello world" program, and it works fine, with SSL. So the problem must be some interaction between nginx, the newrelic collector client, and libcurl and/or libssl.
I'm not familiar enough with these libraries to guess... is there some global SSL state that nginx might be modifying that then breaks the collector client?

I was able to solve the problem by configuring nginx to pass the environment variable SSL_CERT_FILE, to its forked worker processes, which it does not do by default. (see documentation for nginx env directive)
env SSL_CERT_FILE;


update version to ZLint

Adding a wrapper function that returns a ZLintResult object w/ version and timestamp.

@kumarde based on our conversation from this morning, I'm going to close this.

@zakird no worries. I'm starting work on a PR to address those concerns now.


Wrap asset paths in a getter function

Currently, we're using pathlib to find the paths to asset files, but it is a bit messy:
https://github.com/letsbuilda/tower/blob/dfa9148a9aa1e5199260d03b0e0ddb33f063fd83/src/tower/__main__.py#L35
We should wrap this in a function that takes a path relative to the assets directory, and returns the full relative path. An example implementation could look like:
def get_asset_path(file_name: str) -> str:
    path = (Path(__file__).parent.parent.parent / "assets").joinpath(file_name)
    return str(path)

full_path = get_asset_path("levels/level_1.tmx")

We should also move the assets directory inside of the package directory, to reduce the number of .parents required. That will also put it in the right place if we are able to implement importlib.resources in the future.

Isn't this resolved now since we now have ASSETS_DIR in constants.py?


[Latex] Update transform to skip and warn for incompatible objects from mime bundles

Is your feature request related to a problem? Please describe.
When building latex there are certain objects that may be incompatible with the static document concept that pdf provides (i.e. animated gif files). We should add sphinx warnings and raise SkipNode for bundles that contain incompatible objects that aren't listed in the priority list
Describe the solution you'd like
This will need to modify cell_output_to_nodes and cell_output_to_nodes_inline
cell_output_to_nodes is contained in jupyter-sphinx.
Discussion Points:
@choldgraf what is the difference between cell_output_to_nodes and the _inline version in myst-nb? We will need to pass a builder context to these functions to allow detection when running the latex builder so that we can apply this in context.
This might be a nice opportunity to upstream the _inline version if that is the correct place for it to live, but I am a little confused with roles and responsibilities here. Is it documented what we rely on jupyter_sphinx for?

@choldgraf I see that jupinx-sphinx is in jupyter organisation so failed to push to it. Should I use a fork to make a PR for the upstream of cell_output_to_nodes_inline?

@mmcky perhaps you want to close this, or reclarify it purpose, given that rendering process is now reasonably different

hey @chrisjsewell this issue was really about supporting rich mime types such as svg graphics in LaTeX side. There are a few ways to tackle this issue on the LaTeX side such as svg package support in preamble or conversion to a static image format such as png as a sphinx transform (which is probably the better way to go).
Has this changed with recent updates?

Is it mainly SVG, or is there any other MIME types you have in mind? Otherwise, this is a duplicate of #178
On the user feedback side, currently we do not warn if a MIME bundle contains no type present in the priority list, because this was incompatible with the glue stuff (at least for a simple check):
https://github.com/executablebooks/MyST-NB/blob/4b3f51f20dedc8a96c8371341a3f0d8201dce610/myst_nb/render_outputs.py#L172-L180
We do warn though if no renderer is available for a MIME type:
https://github.com/executablebooks/MyST-NB/blob/4b3f51f20dedc8a96c8371341a3f0d8201dce610/myst_nb/render_outputs.py#L266-L270
We can certainly add more MIME type renderers or LaTeX specific renderers into the process now, either on the "default" renderer, or as a separate renderer subclass that the user would switch to with the nb_render_plugin config option


add request log view function

Is your feature request related to a problem? Please describe.
Now, we can't check request log from Static web app.
We think it is helpful for us to check request log when investigation.
So, We would like to add it.
Describe the solution you'd like
Sending request log to Application Insights or Blob so that we can check.
Describe alternatives you've considered
Additional context

I second this. It would be amazing to be able to see the request logs to analyse what is going on.

Hey @sanha0 and @gorootde!
We created a new discussion  to improve monitoring and logging experience in SWA. Feel free to contribute with your thoughts and suggestions!


[Bug]: Error on Lab  04 Prompt Design in Vertex AI

File Name
prompt/examples/*
What happened?
Last progress verification is not working:

inspecting networking is getting 302 error

On first lab (Prompt Design in Vertex AI):
I already tried open and finishing all notebook on examples folders and not working , this step 7 is not found.
Relevant log output
No response
Code of Conduct

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

Other problem is Beginner: Introduction to Generative AI Learning Path
Prompt Design in Vertex AI (https://www.cloudskillsboost.google/paths/118/course_templates/976)
This Task 2 is not completing too,

Even doing ok its not working

Hi @elismasilva
Have you found a solution to this yet ? I am having the same issue, with the same training (Prompt design in Vertex AI)
In my case, it will validate the last step (Improve response quality by including examples), but it won't validate any of the 5 previous steps of Task 2. Open generative-ai folder
That tells me i don't have any cloud setting wrong or missing. Or it would not validate any of the 6 steps. I tried using Chrome, as I thought Google would have "unintentionally" made it difficult on Firefox, which is the browser I use. But it does not work with Chrome either.

Hi @elismasilva
Have you found a solution to this yet ? I am having the same issue, with the same training (Prompt design in Vertex AI)
In my case, it will validate the last step (Improve response quality by including examples), but it won't validate any of the 5 previous steps of Task 2. Open generative-ai folder
That tells me i don't have any cloud setting wrong or missing. Or it would not validate any of the 6 steps. I tried using Chrome, as I thought Google would have "unintentionally" made it difficult on Firefox, which is the browser I use. But it does not work with Chrome either.

Hi, these types of issues are not related to this GitHub repository. Please contact Qwiklabs/Cloud Skills Boost support<EMAIL_ADDRESS>with this issue.


Bump package versions

Updates sats-connect related packages.
Fixes https://github.com/secretkeylabs/sats-connect/issues/180

@aryzing i will close since we already included the changes in another PR 👍


Add expm1 Spark function

Bug description

We find the function expm1, but no registration and implementation
The function is registered and executed with the native way
As the std::expm1 mentioned, it can provide more accuracy for the returned value. So current proposal way is to used the std lib way.

System information
Velox System Info v0.0.2
Commit: 4bf0fa0c9ae93b2f944548f93f4d792e49d67dfa
CMake Version: 3.22.1
System: Linux-<IP_ADDRESS>-microsoft-standard-WSL2
Arch: x86_64
C++ Compiler: /usr/bin/c++
C++ Compiler Version: 11.4.0
C Compiler: /usr/bin/cc
C Compiler Version: 11.4.0
CMake Prefix Path: /usr/local;/usr;/;/usr;/usr/local;/usr/X11R6;/usr/pkg;/opt
Relevant logs
No response

CC: @rui-mo @PHILO-HE

It seems this PR is related https://github.com/facebookincubator/velox/pull/9667.

It seems this PR is related fix.

Right. It's fixed by #9667


Simplify BindAttribute - rename PredicateProvider

This change renames IPropertyBindingPredicateProvider to
IPropertyFilterProvider. The changes here are mostly renames of
parameters/variables from predicate -> propertyFilter. I did a
find+replace and left the term 'predicate' in some of the docs because it
refers to a predicate in the abstract sense.
This change also simplifies BindAttribute and removes support for type
activation.

:shipit:


Clarify translation context popping

This shifts our t overrides to store the value on the stack since we only ever care about the last value on the array.
@andrewculver some of this is hard to test, since I don't have an app on me. How have you vetted this before?

Looks like there's more stuff I didn't grasp let me look at that later — or just revert the logic in the locale prefix deriving method, might not be that much clearer really.


Packr with external module?

I have a module A which contains a static HTML page with some CSS/JS. I'd like to import A from a separate golang project (call it B), and be able to serve the same HTML/CSS/JS from B.
Currently this doesn't seem to work - is there something I'm missing?

@bobby-brennan I wasn't able to replicate this... I created a moduleA repo here: https://github.com/timraymond/moduleA which is what I think you're trying to do. I was able to import this and read the contents of templates in moduleA.
Maybe I'm not following. Could you provide a small reproduction test case and the error that you're seeing to help debug this?

I think I've gotten this working in packr2 - will reopen if I run into the issue again.
Thanks!


Bulk lead Import

As described in http://developers.marketo.com/documentation/rest/import-lead/
Any plans to implement this feature in your library?
~Ori

Not currently as I don't have access to a Marketo instance to test on. Pull requests are welcome though.

I already have what I think is a half-baked solution to this issue. It doesn't conform to the service description standard created in service.json, however, with a few additional lines in src/Client.php I was able to upload a CSV file to our Marketo account. It's the Response object parsing I'm having an issue with. Just need to familiarize myself a little bit more with how Guzzle deals with responses.
class Client extends GuzzleClient
{
    /**
     * {@inheritdoc}
     */
    public static function factory($config = array())
    {
        $default = array(
            'url' => false,
            'munchkin_id' => false,
            'version' => 1,
            'bulk' => false
        );

        $required = array('client_id', 'client_secret', 'version');
        $config = Collection::fromConfig($config, $default, $required);

        $url = $config->get('url');

        if (!$url) {
            $munchkin = $config->get('munchkin_id');

            if (!$munchkin) {
                throw new \Exception('Must provide either a URL or Munchkin code.');
            }

            $url = sprintf('https://%s.mktorest.com', $munchkin);
        }

        $grantType = new Credentials($url, $config->get('client_id'), $config->get('client_secret'));
        $auth = new Oauth2Plugin($grantType);

        if($config->get('bulk') === true) {
            $restUrl = sprintf('%s/bulk/v%d', rtrim($url, '/'), $config->get('version'));
        } else {
            $restUrl = sprintf('%s/rest/v%d', rtrim($url, '/'), $config->get('version'));
        }

        $client = new self($restUrl, $config);
        $client->addSubscriber($auth);
        $client->setDescription(ServiceDescription::factory(__DIR__ . '/service.json'));

        return $client;
    }

    /**
     * Import leads via a CSV file upload
     *
     * @param object $client
     * @param array $args
     * @return $object
     */
    public function importLeadsCsv($client, $args) {
        $request = $client->post($client->getBaseUrl().'/leads.json',
                                 null,
                                 array('format' => 'csv',
                                        'file' =><EMAIL_ADDRESS>                                      )
                                );
        return $request->send();
    }

Response looks like this:
Guzzle\Http\Message\Response Object
(
    [body:protected] => Guzzle\Http\EntityBody Object
        (
            [contentEncoding:protected] =>
            [rewindFunction:protected] =>
            [stream:protected] => Resource id #95
            [size:protected] =>
            [cache:protected] => Array
                (
                    [wrapper_type] => PHP
                    [stream_type] => TEMP
                    [mode] => w+b
                    [unread_bytes] => 0
                    [seekable] => 1
                    [uri] => php://temp
                    [is_local] => 1
                    [is_readable] => 1
                    [is_writable] => 1
                )

            [customData:protected] => Array
                (
                    [default] => 1
                )

        )

    [reasonPhrase:protected] => OK
    [statusCode:protected] => 200
    [info:protected] => Array
        (
            [url] => https://[redacted].mktorest.com/bulk/v1/leads.json
            [content_type] => application/json;charset=UTF-8
            [http_code] => 200
            [header_size] => 257
            [request_size] => 310
            [filetime] => -1
            [ssl_verify_result] => 0
            [redirect_count] => 0
            [total_time] => 1.628529
            [namelookup_time] => 8.4E-5
            [connect_time] => 0.186105
            [pretransfer_time] => 0.56366
            [size_upload] => 691
            [size_download] => 92
            [speed_download] => 56
            [speed_upload] => 424
            [download_content_length] => 92
            [upload_content_length] => 691
            [starttransfer_time] => 0.673526
            [redirect_time] => 0
            [certinfo] => Array
                (
                )

            [primary_ip] => [redacted]
            [primary_port] => 443
            [local_ip] => [redacted]
            [local_port] => [redacted]
            [redirect_url] =>
        )

    [effectiveUrl:protected] => https://[redacted].mktorest.com/bulk/v1/leads.json
    [headers:protected] => Guzzle\Http\Message\Header\HeaderCollection Object
        (
            [headers:protected] => Array
                (
                    [server] => Guzzle\Http\Message\Header Object
                        (
                            [values:protected] => Array
                                (
                                    [0] => nginx
                                )

                            [header:protected] => Server
                            [glue:protected] => ,
                        )

                    [date] => Guzzle\Http\Message\Header Object
                        (
                            [values:protected] => Array
                                (
                                    [0] => Fri, 30 Jan 2015 06:02:07 GMT
                                )

                            [header:protected] => Date
                            [glue:protected] => ,
                        )

                    [content-type] => Guzzle\Http\Message\Header Object
                        (
                            [values:protected] => Array
                                (
                                    [0] => application/json;charset=UTF-8
                                )

                            [header:protected] => Content-Type
                            [glue:protected] => ,
                        )

                    [content-length] => Guzzle\Http\Message\Header Object
                        (
                            [values:protected] => Array
                                (
                                    [0] => 92
                                )

                            [header:protected] => Content-Length
                            [glue:protected] => ,
                        )

                    [connection] => Guzzle\Http\Message\Header Object
                        (
                            [values:protected] => Array
                                (
                                    [0] => keep-alive
                                )

                            [header:protected] => Connection
                            [glue:protected] => ,
                        )

                    [set-cookie] => Guzzle\Http\Message\Header Object
                        (
                            [values:protected] => Array
                                (
                                    [0] => BIGipServersj-restapi_https=4262002698.47873.0000; path=/
                                )

                            [header:protected] => Set-Cookie
                            [glue:protected] => ,
                        )

                )

        )

    [headerFactory:protected] => Guzzle\Http\Message\Header\HeaderFactory Object
        (
            [mapping:protected] => Array
                (
                    [cache-control] => Guzzle\Http\Message\Header\CacheControl
                    [link] => Guzzle\Http\Message\Header\Link
                )

        )

    [params:protected] => Guzzle\Common\Collection Object
        (
            [data:protected] => Array
                (
                )

        )

    [protocol:protected] => HTTP
    [protocolVersion:protected] => 1.1
)

Thanks. Could you use the service description file as per the other methods?
Also, code should follow the PSR-2 coding style.
Lastly, have you tested the importLeadsCsv method? It doesn't seem that you're actually sending the file in the request?

All methods are functional as shown in the code above. I tested it and successfully uploaded multiple CSV files on our Marketo instance.
I will look into converting the implementation to conform with Service description format and PSR-2 coding style.
Thanks for your feedback!

Please see Pull Request https://github.com/dchesterton/marketo-rest-api/pull/15
If any other contributors with access to a Marketo instance could test it would be greatly appreciated.


Proposal for Improving App Mining by Adding App Category Context

What is the problem you are seeing?
Lack of app category context being taken into consideration by algo.
How is this problem misaligned with goals of app mining?
Lack of app categories seems to discourage new developers from attempting to tackle the more intricate or more complex applications that add diversity and utility to the ecosystem.  For example, why would a new app developer try to compete with a simple app that has very little learning curve? When the new developer knows they will still be graded so to speak against apps that have a nearly non-existent learning curve?
What is the explicit recommendation you’re looking to propose?

Introduction of app categories that the app developer chooses from a predetermined list of categories when registering their app into the app mining rewards program that is derived from the app.co categories.

Require TMUI test users who do the actual voting/scoring to be categorically assigned and aligned to test apps that are of the appropriate target demographic of the apps category. (and possibly other reviewers)

Restructure Payouts: Since there is already 14 categories (per app.co currently)
We could divide the 100k USD worth of BTC by the 14 categories, then divvy the pot per category out by a multiple that is .5  (perhaps even have the multiplier slide as we scale up to 1 million payouts)

Here is a gif that shows how a couple categories, and what the top 10 ranked apps payout structure could look like (bare in mind the multiplier doesn't change in this gif just the total pot size to give a sense of how payouts would look at 100k and how they would look at 1million)

Describe your long term considerations in proposing this change. Please include the ways you can predict this recommendation could go wrong and possible ways mitigate.
Potential problems would be too many categories, might result in spreading rewards out too thin.
Additional context
Doing testing according to a loosely targeted user base demographic by app category should  also help avoid a echo chamber of apps in the ecosystem and by extension should inspire more diversity and utility.  Since If the rewards are by in large only going to blogging apps or note taking apps, then we will wind up have a disproportional amount of app developers chasing the same type of app. (since thats the type of app that tends to be favored by users who participate in app mining)
Note about scaling up:  Based on current exchange rates, if things were scaled for payouts of top 6 apps per category while at 100k total pot, then to top 10 apps per category when at 1 million total pot.
We would go from 84 total apps getting paid a min of $111.61 USD  to max of $3.5k USD. To top 140 apps getting paid at least a min of $69.75 USD to a max of $35.7k USD.

Obviously the rewards of app mining should not be the developers underlying motives, for them to start building apps, but rather bringing it to an MVP status to be self sustaining (and in turn bringing value to the ecosystem).
However, app mining is most definitely a form of incentive for on boarding, thus in my opinion, we should do everything we can to help foster as many high quality apps as we can get by rewarding as many apps developers as possible with as much as possible.

While I agree we need categories to help focus TryMyUI reviews, my concern is that, in terms of payouts, it shifts the concern from 'Why is my app valued the way it is?' to 'Why is my app category valued the way it is?'

Thanks for adding this. I think this has merit and will likely happen at some point. Some operational challenges I predict:

Who will arbitrate the categories? A new app reviewer? Whatever entity this is would probably need to contend with non-stop complaints re category decisions. Who would we trust to handle this?

What happens when apps occupy multiple categories? Or want to migrate from a high-competition category to a low-competition category for obvious reasons?

it shifts the concern from 'Why is my app valued the way it is?' to 'Why is my app category valued the way it is?'

@dantrevino ... I understand what you you mean, but I disagree, simply because, if the categories are equal total pot per, then favoritism couldn't be claimed as there is no clear preference of category.
And in the event of any insistence of one app category being claimed to be of a of a higher value then the others, the claimer should be met with a rebuttal that exposes how it is impossible for any one individual or small group of individuals to determine what the actual masses deem as valuable without significant amounts of analytics and data to back up the claim.
I think in essence we should not be trying to put the cart before the horse here. The objective currently should be to on board developers of all shapes and sizes so to speak, instead of trying to lump everyone into one basket that winds up creating more noise then signal.

Who will arbitrate the categories? A new app reviewer? Whatever entity this is would probably need to contend with non-stop complaints re category decisions. Who would we trust to handle this?

Couldn't we just have the developer set their app category the app manifest.json as well as specify the they will start out in at start of their registration.
Then the lead up time, just prior to the app mining round starting, a snap shot of the app categories, as specified in the apps manifest.json, are taken, to ensure the appropriate testers are testing and to ensure they are part of the appropriate payout category.

What happens when apps occupy multiple categories?

Good question, but the simplistic solution would be obviously to just limit to a single primary choice only for quality assurance purposes.

What happens when the app want to migrate from a high-competition category to a low-competition category for obvious reasons?

If snap shot step happens of manifest.json to determine category prior to round starting, then in my opinion if the dev thinks it s a better fit, then why try to prevent that. If they are simply trying to game the system cuz that category is low quantity, then they should still rank near the bottom of that category because ideally testers scores would have a decent amount of weight associated to a question about if the app seems like a good fit in that category or not.

@hstove to add more context here.

I am not against the idea of having categories to get better TryMyUI testers. However, I still think that doing payouts by category is not a good idea. It is easy to see the list of apps per category before this 'snapshot' could be done. It would be trivial to look at all the apps in each category, and determine which category you could shoehorn your app into such that you rank higher than all of them.
Moreover, I think that this is not a good idea on an even more fundamental level. I do want to encourage innovation, but I don't think payouts by category helps that. Moreover, I don't think that it's a bad thing if multiple of the top apps are competing with each other in the same 'category'. It is certainly possible that some categories will find more success in the decentralized space, and we shouldn't hinder that. Also, competition is good for innovation.

We discussed this internally and concluded that this makes sense with 100s of apps and well over $100K in payouts and we will reconsider this when those happen.


Yenküp Manifest File

The file for Yenküp to be ready to installed with winget
Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I want to disscubsribe thx


Generated files are not ignored

Describe the bug
The generated file target is not ignored and leads to duplicate types
If your documents path includes the generated file, like:
overwrite: true
schema: "http://localhost:3001/api/graphql"
generates:
  client/src/graphql/types.ts:
    documents:
      - "client/src/**/*.{ts,tsx}"
    plugins:
      - "typescript"
      - "typescript-operations"
      - "typescript-react-apollo"
    config:
      withComponent: false
      withHooks: true
      withHOC: false

Then you end up with:
  ✖ client/src/graphql/types.ts
    Not all operations have an unique name

It'd be great if the generated file was automatically excluded.
To Reproduce
Steps to reproduce the behavior:

Use the above config with a query in a ts file
Run the following command: graphql-codegen
Run it again

Expected behavior
It should work and not error.
Schema/Documents
N/A
Environment:

OS: macOS 10.14.3
Codegen: 1.0.2
Node: 10.x

Additional context
N/A

Fixed in 1.0.4

@dotansimha Did this regress from 1.3.1 to 1.5.0 by any chance?

@rgiese Could you reproduce it?

Not readily (it's a bit of a big Lerna-ified monster) but if you can't think of anything obvious that might have caused this, I can try and stand up something isolated.

I'm having something similar when I run the command from circleCi.
On my local machine it runs fine but that could be due to speed.
On the circleCi machine doing my build I'm getting a loop:
Generating schema... 88ms
Saving Prisma Client (TypeScript) at /home/circleci/repo/src/generated/prisma-client
Saving Prisma GraphQL schema (SDL) at /home/circleci/repo/src/generated/schema.graphql
  ✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate ./src/generated/gqlTypes.ts
      ✔ Load GraphQL schemas
      ⠙ Load GraphQL documents
        Generate
  ✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate ./src/generated/gqlTypes.ts
      ✔ Load GraphQL schemas
      ⠹ Load GraphQL documents
        Generate
  ✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate ./src/generated/gqlTypes.ts
      ✔ Load GraphQL schemas
      ⠸ Load GraphQL documents
        Generate
  ✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate ./src/generated/gqlTypes.ts
      ✔ Load GraphQL schemas
      ⠼ Load GraphQL documents
        Generate
  ✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate ./src/generated/gqlTypes.ts
      ✔ Load GraphQL schemas
      ⠴ Load GraphQL documents
        Generate
  ✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate ./src/generated/gqlTypes.ts
      ✔ Load GraphQL schemas
      ✖ Load GraphQL documents
   ...

The relevant part of my config is setup as follows:
schema: ./src/generated/schema.graphql
documents:
  - './src/**/*.{ts,tsx}'
  - './src/**/*.graphql'

@richardwardza Removing the ./ prefix from documents & the generates key seems to have fixed this for me.
schema: "http://localhost:3000/api/graphql"
generates:
  packages/editor/src/graphql.types.tsx:
    documents: "packages/editor/src/**/*.{ts,tsx}"
    plugins:
      - "typescript"
      - "typescript-operations"
      - "typescript-react-apollo"

@ecoleman @richardwardza I fixed this in: https://github.com/dotansimha/graphql-code-generator/commit/a38a82e845d1b5e66643e3307dca7d540d8e7b19

@dotansimha Hi, we just noticed in our team that the above fix is working on UNIX systems (generated file is ignored) but not on Windows machines.

Thanks @smajl , I fixed it in graphql-toolkit :)

Fixed in 1.7.0


Merge 1.6.9

Codecov Report

Merging #734 into master will decrease coverage by 13.64%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #734       +/-   ##
===========================================
- Coverage   68.28%   54.64%   -13.65%
===========================================
  Files         393      393
  Lines       20983    21335      +352
===========================================
- Hits        14329    11658     -2671
- Misses       6654     9677     +3023

Impacted Files
Coverage Δ

cmd/--cellar.rb
0% <0%> (-100%)
:arrow_down:

rubocops.rb
0% <0%> (-100%)
:arrow_down:

cmd/--prefix.rb
0% <0%> (-100%)
:arrow_down:

cmd/config.rb
0% <0%> (-100%)
:arrow_down:

dev-cmd/formula.rb
0% <0%> (-100%)
:arrow_down:

cmd/--env.rb
0% <0%> (-95.66%)
:arrow_down:

cmd/missing.rb
0% <0%> (-93.75%)
:arrow_down:

cmd/desc.rb
0% <0%> (-91.67%)
:arrow_down:

cmd/migrate.rb
0% <0%> (-91.67%)
:arrow_down:

help.rb
0% <0%> (-90.91%)
:arrow_down:

... and 161 more

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 dcbc83b...3ba4c2e. Read the comment docs.


section links in READMEs' table of content not referenced properly

I think it's the same as this ticket right? https://github.com/jina-ai/jina/issues/2872 @Kelton8Z

I think it's the same as this ticket right? jina-ai/jina#2872 @Kelton8Z

not exactly, that issue regards README of the examples repo, this one I meant the READMEs of actual examples


Fix flaky frontend test

Twice recently I've had frontend tests fail on CI in a PR that did not touch frontend at all. For example, https://github.com/mitodl/ocw-studio/runs/5854057454?check_suite_focus=true
Acceptance Criteria:

[ ] Figure out why and fix it.

Another possible example: https://github.com/mitodl/ocw-studio/runs/7197287993?check_suite_focus=true

Possibly related: https://github.com/mitodl/ocw-studio/issues/269.

Another example: https://github.com/mitodl/ocw-studio/runs/7362418653?check_suite_focus=true

any update on this @Wassaf-Shahzad ?

Sorry no @pdpinch I could not reproduce this locally

To determine this issue's impact and existence, I ran the SingletonsContentListing.test multiple times. (Thanks to https://github.com/mitodl/ocw-studio/issues/1207#issuecomment-1185785648, I did not have to run the entire suite).

Test
Count

Passed
159

Failed
4

Total
163

Although it could use more runs for a more accurate number, we can say this issue impacts 2.4% of the PRs.
I ran a few experiments but unfortunately, I could not determine the cause of the problem yet.
Here's a sample of the error message
  ● SingletonsContentListing › loads content detail from the API if needed without content context

    AssertError: expected stub to not have been called but was called once
        stub('/api/websites/suscipit-autem-enim-sapiente-qui/content/eos/', 'GET', { body: undefined, headers: undefined, credentials: undefined }) => {
      body: {
        text_id: 'ec6675ae-91bd-4bdd-b7a2-1579864907ce',
        title: 'Quia facere veritatis',
        type: 'molestiae',
        updated_on: '2006-03-25T18:23:21.117Z',
        markdown: 'Quasi alias minima harum voluptatem dolor aut odit corporis. Consequatur magni aut officia quis quia. Doloribus est non quo quibusdam in ab cumque sed. Amet enim perspiciatis. Voluptas earum temporibus voluptates animi dolorum.',
        metadata: { description: 'Eum quidem architecto accusantium.' },
        content_context: [],
        url_path: 'At et consequatur eaque iure. Occaecati saepe doloremque repellendus facere quo molestiae quos amet. Occaecati cumque dolorem. Ipsa et aperiam voluptatem quia consequuntur impedit tempore quis voluptas. Minima reiciendis adipisci eaque animi cumque. Quis fuga tempora hic cumque voluptas asperiores.'
      },
      status: 200
    } at Object.execute (/src/static/js/util/integration_test_helper_old.tsx:65:31)

      170 |       // API should not initially be called since we already have the first item in our websiteContentDetails
      171 |       // entities state
    > 172 |       sinon.assert.notCalled(contentDetailStub)
          |                    ^
      173 |       const tabLink = wrapper.find("NavLink").at(tabIndexToSelect)
      174 |       act(() => {
      175 |         // @ts-expect-error Not mocking whole event

      at Object.fail (node_modules/sinon/lib/sinon/assert.js:120:25)
      at failAssertion (node_modules/sinon/lib/sinon/assert.js:66:20)
      at Object.notCalled (node_modules/sinon/lib/sinon/assert.js:95:17)
      at static/js/components/SingletonsContentListing.test.tsx:172:20

The random failures are caused by HTTP Sinon stubs with duplicate URLs. I'm not sure exactly where the issue initiates, but my experiments have led me to the following conclusion.
In static/js/components/SingletonsContentListing.test.tsx, whenever contentDetailStub at line 53 and contentDetailStub at line 153 are used with the same URL, the test fails.
Furthermore,
singletonConfigItems = [
      makeSingletonConfigItem(),
      makeSingletonConfigItem(),
      makeSingletonConfigItem()
    ]

Creates three items which can have the same name property. This property is used in the content URL. The names, by default, are generated by the casual generator.
There is a probability that casual will return the same value multiple times in a single test run, the URL relying on those values will also have a probability of being identical.
After the changes in https://github.com/mitodl/ocw-studio/pull/1700, I ran SingletonsContentListing.test 500 times. Not a single one failed.


Update environment-variables.md

Fixes #120 . I changed the proposed solution from "The workspace directory a copy of your repository" to "The workspace directory - a copy of your repository" for better readability.

Why:

What's being changed:

Check off the following:

[ ] All of the tests are passing.
[ ] I have reviewed my changes in staging.
[ ] For content changes, I have reviewed the localization checklist
[ ] For content changes, I have reviewed the Content style guide for GitHub Docs.

Amazing @casals! Thanks for another one 🔥 I'll let the @github/docs-content-ecosystem team know ⚡


Add rspec tests and travis file

Adds the first batch of rspec test for the loader file.
Adds a travis file with includes both tests suites so we can tests both at the same time during the transition. Minitests suite is currently marked as allowed failure as I could not get to pass all the tests locally.

Travis tests can be seen here https://github.com/Itxaka/ansible-viz/pull/1


Add generic option to control return value for .json and .parse

Please read the section on 'rules we won't implement'


Add Function Mock BBE and Group Test BBE to index.json

Purpose
Add Function mock BBE and Group Test BBE to index.json
Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Depot integration

This is hack to leverage depot.dev for building. This will change in
the future and this is only a quick experiment.
Signed-off-by: Darren Shepherd<EMAIL_ADDRESS>

Steps to use this:

Get a depot.dev account and proejct
Configure acorn to use an external registry by setting the install flag --internal-registry-prefix to your external registry of choice
Create a secret in your acorn proejct: 1acorn -j dev secret create depot-builder-key --data projectId=${PROJECT_ID},token=${TOKEN}`


Assigned full semver to Action dependencies

Current dependencies on/for this PR:

main

PR #1106

PR #1107   👈

This comment was auto-generated by Graphite.


Modularize / Document template.sh.in

I'd like to add some custom scripts to set up devices. (specifically to install docker). Currently I put this code in template.sh.in, but it would be nice if I could separate it into a separate file.

Does the provisioner zip the entire aws-greengrass-provisioner/src/main/resources/shell directory and transfer all the files over to the device?
What environmental variables get written to these .in files? There seems to be env vars for all the scripts, and certificates, but it is unclear where they are set and how to add a new one. It would be pretty cool if I could do something similar to the start script in template:

if [ "$START" = true ]; then
    ./${START_SCRIPT}
fi

with my docker script:
if [ "$DOCKER" = true ]; then
    ./${DOCKER_INSTALL_SCRIPT}
fi

but I don't know how I'd go about this.

Modularizing the installer script would definitely help some users that have specific configurations they want to consistently build. I'll look into this.