Electron 7 crashes on Sentry.init

Updated Electron to 7.1.0 and since then the app crashes the moment Sentry.init is called. Does Sentry support that version?
Thanks

We didn't run any tests with Electron 7 yet but thanks for highlighting it doesn't work.
We will take a look.

If you could let me know if there is a bug (even before fixing it), that would be great. I'm currently considering alternatives, but I'd love to keep using Sentry.

I've tested the included example app with<EMAIL_ADDRESS>and the app does not crash on init.
Can you give some reproduction steps? An example repository would help!

When you open the app for the first time it works just fine. It starts crashing only when you try to open it after the first crash. If you clear the App crashes folder, then it works again.
I should've mentioned that before, sorry...

When testing 7.1.1 I can see that Electron is now writing dump files to a reports directory that it never did before so they will not be uploaded but I still can't get the app to crash:

Electron on Windows started using crashpad at v6.
I've created a branch which ensures that on these versions it now uses the crashpad logic which fixes sentry on v6 but there are still issues with v7 related to electron-fetch:
https://github.com/arantes555/electron-fetch/issues/17
I've tried<EMAIL_ADDRESS>which was released a few hours ago but still no luck so it might be time to replace that dependency as it has broken things before.

If I understand correctly - you were able to make the app crash but you found out that it doesn't send any errors to sentry on Windows.
I forgot to mention that I'm on Mac (10.15.1) but it also crashed on Windows last time I checked.
We'll also try running electron with a debugger and narrow down the issue.
Thanks for looking into this!

The issues with electron-fetch and Electron v7 affected all platforms.

@timfish I think this affects a lot of people (as you can see the electron/electron#21240), it'd be awesome if you could move it to stable channel sooner imho 🙌🧡

i can fully confirm the behaviour @ranihorev described (using sentry 1.0.0).
In my case it did happen with electron 7.1.1 and 7.1.2
After upgrading to the sentry 1.1.0-beta.0 the problem was solved.
Please see https://github.com/electron/electron/issues/21240


Fix defaulting of Replicas spec

Currently the default values are ignored because these specs are set to 0 by webhook. Update the type from int32 to *int32 to avoid that behavior and ensure the expected default values are used.

/test ironic-operator-build-deploy-kuttl


gender inclusive language

change "he\she is" to "they are"

@emberstevens : Thanks for your contribution! The author, @billmath, has been notified to review your proposed change.


fix mod

fixes https://github.com/willow-ahrens/finch-tensor/issues/53

Minor comment: Could we add a regression test?

Is this not tested in the array api tests?

I'll be fairly busy the next couple of weeks, so I'd appreciate help on these tests.

I added a regression test. Thanks @willow-ahrens!


[ Support Question ] The value for inverse... is invalid

Can you help me figure out what this error means?
      "message": "The value for \"inverse\" on \"post\" in type \"Comment\" is invalid, the inversely related field must define its inverse as \"post\".",

My schema looks like this:
type Comment {
  id: ID! @unique
  createdAt: DateTime @createdTimestamp
  updatedAt: DateTime @updatedTimestamp
  author: User @relation(name: "commentsByUser")
  body: String
  post: Post @relation(name: "commentsOnPost")
}

enum postType {
  TEXT
  LINK
}

type Post {
  id: ID! @unique
  createdAt: DateTime @createdTimestamp
  updatedAt: DateTime @updatedTimestamp
  author: User @relation(name: "postsByUser")
  type: postType
  comments: [Comment!] @relation(name: "commentsOnPost")
}

type User {
  id: ID! @unique
  createdAt: DateTime @createdTimestamp
  updatedAt: DateTime @updatedTimestamp
  userName: String! @unique
  posts: [Post!] @relation(name: "postsByUser")
  comments: [Comment!] @relation(name: "commentsByUser")
}

Am I not defining my relations correctly?

Hmm it doesn't look like you are doing anything wrong, I'll take a look and see what the issue may be

Here is a repo for reproduction if you get the chance.  Currently I have all the @relations commented out to get it working, but once they are uncommented it throws.
Also, if you're in there poking around, I think the template strings and seperate merged schema files make for a clean structure (assuming it works).  Maybe if you like it I could PR something similar into the examples

I'm also getting "The value for inverse... is invalid" but my workaround is to change the name of a field. Steps to reproduce:

paste this minimal schema into the [genie playground] (https://genie-team.github.io/graphql-genie-client/) and save it

`type Person {
id: ID! @unique
name: String!
devices: [Device!]
bugReports: [BugReport!]
}
type Device {
id: ID! @unique
hostname: String!
person: Person
}
type BugReport {
id: ID! @unique
summary: String!
person: Person
}`
2 Paste this query and execute it:
{   devices {     id   } }

Error message is

The value for \"inverse\" on \"bugReports\" in type \"Person\" is invalid, the inversely related field must define its inverse as \"bugReports\"."
My workaround is to change the name of the "person" field in "bugReport" to "raisedBy" . Relation directives don't seem to make any difference to the outcome.

I am getting this issue too. Please how do we resolve?

Hi. Chiming in here because I wrote this error message. I think it is perfectly clear what it means and how to address the issue, but it is opaque to users of this because inverse isn't explicitly defined here.
@acoreyj inverse field needs to be defined on both sides of a relationship for now. I could relax this requirement by trying to automatically assign it if one side is assigned, I just thought it was more explicit this way.

@daliwali even the examples are failing.  Since this project was inspired by prisma.  It would be nice if it accepts relationships same way prisma does.
I am trying to use genie as an offline alternative of prisma to cache large data in IndexedDB

@darmie there is the option to not specify an inverse like how prisma does it. that's up to @acoreyj

@acoreyj I am really looking forward to a solution right now.  I would appreciate if this issue is resolved soon.

@daliwali I think this is a legit bug and maybe not pilot error, since the examples are failing.  Time to take a closer look?

Here's the check: https://github.com/fortunejs/fortune/blob/169edd5b8b0ba6de08f1049e843e4c7afe7c170b/lib/record_type/ensure_types.js#L46-L50
Here's the test case: https://github.com/fortunejs/fortune/blob/d14401b4d328eb98681dbd0db15f16f2114ba2ea/test/unit/record_type.js#L170-L177
It is an issue with graphql-genie.

Thanks for the help guys, looking into this today

@light24bulbs  @warwickgrigg
Hey all this is now fixed in the latest version.
The issue was a bug where if multiple types had a relation to the same other type and had the same field name it would setup the inverses wrong for one of them.
So since comments: [Comment!] was on 2 different types it was incorrectly computing the inverse for one of them, causing the error to be thrown by Fortune.

Thank you @acoreyj if we pull the latest version for NPM, this issue will be fixed?

@darmie that is correct, anything >= .0.4.20


Buildroot 2024.11 Cage service configuration

Hello,
I am trying to build a Buildroot minimal system for Cage. Based on https://github.com/Hjdskes/buildroot I created a recipe to test this system on Qemu, before launch to build it for a real PC. I don´t know if this is the correct place to ask about, or better on the mentioned Hjdskes buildroot project (As far I can see it belongs the same project web)
Systems seems to build and at the end when rootfs-overlay patches are applied I got this message:
Failed to preset unit: Cannot alias<EMAIL_ADDRESS>as display-manager.service
And I don´t know if it is for that reason the system does not boot. only remains in the terminal stating that systemd has finished.
Welcome to Buildroot 2024.11-rc1!
systemd[1]: Hostname set to <dimcqemu>.
systemd[1]: Initializing machine ID from random generator.
systemd[1]: Installed transient /etc/machine-id file.
systemd-ssh-generator[45]: Disabling SSH generator logic, since sshd is not installed.
systemd[1]: /etc/systemd/system/default.target:1: Assignment outside of section. Ignoring.
systemd[1]: Reached target default.target.
[  OK  ] Reached target default.target.
systemd[1]: Startup finished in 4.102s (kernel) + 2.116s (userspace) = 6.218s.

I suspect from this line:
systemd[1]: /etc/systemd/system/default.target:1: Assignment outside of section. Ignoring.

But I could not find what assignement is outside section... The services are configured in the same way that rpi-buildroot from hjdskes.
This is the stating command for qemu:
qemu-system-x86_64 -M pc -kernel output/images/bzImage -drive file=output/images/rootfs.ext2,if=virtio,format=raw -append "rootwait root=/dev/vda console=tty1 console=ttyS0" -serial stdio -net nic,model=virtio -net user -device virtio-vga

This is my Buildroot config:
BR2_x86_64=y
BR2_GLOBAL_PATCH_DIR="$(BR2_EXTERNAL_TPOP_OS_PATH)/board/tp_qemu/patches"
BR2_DOWNLOAD_FORCE_CHECK_HASHES=y
BR2_TOOLCHAIN_BUILDROOT=y
BR2_TOOLCHAIN_GLIBC=y
BR2_TOOLCHAIN_GCC_ATOMIC=y
BR2_TARGET_GENERIC_HOSTNAME="dimc_qemu"
BR2_TARGET_GENERIC_ISSUE="Welcome to TetraPak OS"
BR2_TARGET_GENERIC_ROOT_PASSWD="tpopadmin"
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_GENERIC_GETTY_PORT="tty1"
BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW=n
BR2_TARGET_TZ_INFO=y
BR2_SYSTEM_DHCP="eth0"
BR2_SYSTEM_BIN_SH_BASH=y
BR2_INIT_SYSTEMD=y
BR2_ROOTFS_POST_BUILD_SCRIPT="$(BR2_EXTERNAL_TPOP_OS_PATH)/board/tp_qemu/dimc_qemu/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="$(BR2_EXTERNAL_TPOP_OS_PATH)/board/tp_qemu/post-image.sh"
BR2_ROOTFS_POST_SCRIPT_ARGS="$(BR2_DEFCONFIG)"
BR2_ROOTFS_USERS_TABLES="$(BR2_EXTERNAL_TPOP_OS_PATH)/board/tp_qemu/dimc_qemu/usertable.txt"
BR2_ROOTFS_OVERLAY="$(BR2_EXTERNAL_TPOP_OS_PATH)/board/tp_qemu/dimc_qemu/rootfs_overlay"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.6.32"
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(BR2_EXTERNAL_TPOP_OS_PATH)/board/tp_qemu/dimc_qemu/linux.config"
BR2_LINUX_KERNEL_NEEDS_HOST_LIBELF=y
BR2_PACKAGE_UTIL_LINUX_AGETTY=y
BR2_PACKAGE_UTIL_LINUX_LOGIN=y
BR2_PACKAGE_SYSTEMD_LOGIND=y
BR2_PACKAGE_BASH=y
BR2_PACKAGE_MESA3D=y
BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_VC4=y
BR2_PACKAGE_MESA3D_DRIVER=y
BR2_PACKAGE_MESA3D_OPENGL_ES=y
BR2_PACKAGE_MESA3D_OPENGL_EGL=y
BR2_PACKAGE_CAGE=y
BR2_PACKAGE_LIBGTK3=y
BR2_PACKAGE_LIBGTK3_WAYLAND=y
BR2_PACKAGE_CANTARELL=y
BR2_PACKAGE_ADWAITA_ICON_THEME=y
BR2_PACKAGE_HOST_QEMU=y
BR2_PACKAGE_HOST_QEMU_SYSTEM_MODE=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_6=y
BR2_PACKAGE_LINUX_PAM=y
BR2_PACKAGE_WAYLAND=y
BR2_PACKAGE_LIBWAYLAND=y
BR2_PACKAGE_LIBINPUT=y
BR2_PACKAGE_WAYLAND_PROTOCOLS=y
BR2_PACKAGE_XSERVER_XORG=n
BR2_PACKAGE_XSERVER_XORG_DRIVER_INPUT_EVDEV=n
BR2_PACKAGE_FBFONT=y
BR2_PACKAGE_FBUTILS=y
BR2_PACKAGE_LIBEGL=y
BR2_PACKAGE_LIBDRM=y
BR2_PACKAGE_COREUTILS=y
BR2_PACKAGE_NANO=y
BR2_PACKAGE_BASH_COMPLETION=y
BR2_PACKAGE_HTOP=y
BR2_PACKAGE_PROCPS_NG=y

All post-build, post-image and patch actions are the default ones stated on qemu configuration on default buildroot github.
Any help is welcome, and also any additional info request.
Regards
Fran

Hello,
I did some test and remove the overlay rootfs, and I am able to log in to the embedded system with the user/password configured. After login I realized that the package Cage had not been installed, or even compiled if you look and compilation logs.
For this, this is not a matter of cage itself... is a matter of buildroot...
Regards
Fran


fix: Change order of master deploy

Description
My previous PR #4606 is overwriting all other folders in ghpages/master since it is the final step. This changes it to the first step in that process.
If it makes more sense, we could instead change the master/std path to be master/lib and this would allow for a link to both master/lib/core and master/lib/std instead of master/core and master/std. This would mean that we would also have to look out for places we use the links for std in and update them accordingly.
Checklist

[ ] I have linked to any relevant issues.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book).
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
[ ] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[ ] I have requested a review from the relevant team or maintainers.

@Braqzen do you have a preference wrt my initial comment?

@Braqzen do you have a preference wrt my initial comment?

I don't see the benefit of adding another layer of nesting via the //lib/ step as opposed to then starting from master. Moreover, core is available and some things should be visible but at the same time there's other code in there used internally and so it shouldn't be linked to.
If we need to start changing things then that's additional work, which is fine if there is a benefit to the distinction in the paths.
I'm somewhat indifferent because I don't feel like I have the full context of why this should be done. We could have a chat internally if you'd like to catch me up on the context


Better control of warnings for users

The warnings/logger implementation in parcels is a bit clunky; it would be nice to refactor this with a more advanced(?) library. It would especially be nice if users could control which messages they turn on and off.
For example, for some cases where it is expected that particle sets are empty for some time during the simulation, users may want to silence the ParticleSet is empty on writing as array at time XXXX warning

I'd be able to take this one on, motivated by my recent experiences with the ParticleSet is empty message. I wanted to check in before rewriting it to see if you all had an opinion on what a refactor/rewriting of this would look like.
Currently, the warnings in Parcels are implemented through the logging library. I was curious if there is any interest in transitioning to using the warnings library. This has several advantages, in my opinion:

Using the warning library will enable users to set their own level of warning using the warnings context manager, which has the advantage of being consistent with other libraries, such as numpy.exceptions, pandas.errors, and astropy.utils.exceptions.
Users explicitly managing their own warnings using standard library functionality is better than including another kwarg as input to functions that would manage silencing internally and might go missed by many users. When I tried to suppress Parcels warning in some recent runs where I expected empty ParticleSets, I was surprised that my usual way of handling warnings wasn't working.
Warnings could then also be included in documentation with some hints on how to solve them, e.g., a ChunkWarning is issued when chunks are not set optimally, encouraging the user to check the chunking on I/O files.

The reason I wanted to check first is that there is one thing that could be seen as a negative if this is implemented, depending on the goals of the existing logger implementation. The default behavior of the warning library is to only show warnings once, so for the case of the empty ParticleSet warning, the default behavior would change from showing on every iteration to only showing once.
I think this could be mitigated with an example in the tutorials showing how to use the warnings context manager if you desire old behavior (e.g., warnings.simplefilter('always', category=EmptyParticleSetWarning)), and that the overall positives of an updated warnings implementation outweigh the negatives, but I'm curious to see if anyone disagrees before I get working on it.

Thanks for your willingness to pick this up, @andrew-s28! I agree with @VeckoTheGecko that your strategy makes sense; so please go ahead and propose some changes. Note that it doesn't need to be a fully functional PR; even a start would already be great. We're here to help :-)

@andrew-s28 just a note we've installed formatting across the codebase in the last couple days (#1655). I recommend merging with latest master to avoid conflicts

Thanks for the heads up @VeckoTheGecko. Just synced my fork, so should be good to go! I'll keep an eye on it going forward, since it seems there's lots of great developments happening quickly.
PS thank you and @erikvansebille for all the work that is going into the project. I found the new projects tab really helpful for seeing where I could contribute (and the overall direction of the package development), so I think it is working well.

Related to this is the parameter netcdf_decode_warning used in the codebase.
netcdf_decodewarning : bool
            Whether to show a warning id there is a problem decoding the netcdf files.
            Default is True, but in some cases where these warnings are expected, it may be useful to silence them
            by setting netcdf_decodewarning=False.

No action required at the moment. I'll discuss and have a think about how we can deprecate this transparently with users.

@VeckoTheGecko sounds good.
I should have a draft PR ready in the next couple of days, since I am assuming there will be some feedback in how I structure the new warnings classes and we can discuss from there.


Fix rust tests by adding serde as a dev dependency

Public-Facing Changes
None
Description
Fix rust tests by adding back serde as a dev dependency.

TBH I'm a bit of a newbie with Cargo versioning but it looks like "1.0.145" means "greater than 1.0.145 and less than 2.0.0" whereas "1" would mean "greater than 1.0.0 and less than 2.0.0" right?
https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html


Very slow detection

Hi, what may cause the detection to be so slow?
It takes like 4/5 seconds before to detect the command.
Is it annyang related?
Because the example on your website (https://www.talater.com/annyang/), looks very fast detected.....

Are you using HTTPS or HTTP in your site? It works much, much faster in HTTPS because it is able to turn off continuous mode.
You can also turn continuous mode off yourself on HTTP by passing it in the options annyang.start({continuous: false });
It should work faster, but will also cause Chrome to repeatedly ask for permission to use the mic after every recognition (which isn't done in HTTPS)

@TalAter thank you understood now :)


Review cronjob

Review snapshots cronjob that was using empty namespaces, promote cronjobs to v1beta1

I'm getting this error when I look at logs on the master node:
Someone (/<IP_ADDRESS>:55532) speaks http plaintext instead of ssl, will close the channel

This is related to #175
On Wed, 11 Apr 2018 at 04:36, Steve Sloka<EMAIL_ADDRESS>wrote:

I'm getting this error when I look at logs on the master node:
Someone (/<IP_ADDRESS>:55532) speaks http plaintext instead of ssl, will close the channel
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/upmc-enterprises/elasticsearch-operator/pull/174#issuecomment-380307630,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFbljF6AL9BqmVzGIeayDMDcuVp5MO4Uks5tnWwngaJpZM4TIU7J
.

--
Giancarlo Rubio

I did, check the last changes

Ahh GH didn't refresh properly, LGTM


Flux: Navigation menu Improvements

Intead of grouping things, I think it makes more sense to divide things up, similar to how Flux CLI does:
❯ flux get
The get sub-commands print the statuses of Flux resources.


⚠ GitHub has degraded performance

In 8470c7d, GitHub (https://www.githubstatus.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 297 ms

Resolved: GitHub performance has improved in 227a01a.


Add Accept-Encoding to the request headers to reduce bandwidth usage and improve overall efficiency

Is your feature request related to a problem? Please describe.
The request header should include {"Accept-Encoding": "gzip"}. As with web3py by default, this option greatly reduces the amount of data transferred in the request, which can easily run out of gigabit bandwidth when connecting to a local LAN node because the transmitted data is uncompressed. Although the use of uncompressed requests can effectively reduce the CPU pressure on the node, whether it is a remote node or a local node, the bandwidth is full and affects the normal operation of the device.
Describe the solution you'd like
This feature change could be committed to the ethers-rs project, but I think the need to increase request efficiency is more relevant to this project, so I submit the issue here.

this is a good idea. I do think it could only be implemented as part of ethers-rs though, because afaict ether-rs doesn't expose these types of header options to users
ethers-rs is also being refactored into Alloy, so perhaps it would be best to ask for this kind of functionality in the Alloy issue tracker


fix popup/tooltip issue in the featurelayer

Code fix from https://github.com/Esri/esri-leaflet/pull/1350
Fixes #60 ... Note that the same issue with Leaflet 1.7 exists as here: https://github.com/Esri/esri-leaflet/issues/1354
Code to test this:
<!DOCTYPE html>

    <meta charset="utf-8" />
    <title>Esri Leaflet Debugging Sample</title>
    <meta
      name="viewport"
      content="initial-scale=1,maximum-scale=1,user-scalable=no"
    />

    <link
      rel="stylesheet"
<EMAIL_ADDRESS>    />

       sample application for debugging

Hi @patrickarlt and @gavinr
This should fix the issue.

This was released in v3.0.1.

Thank you very much @gavinr and @patrickarlt !


Make controller a field in App struct

Right now controller is a separate struct:
type Controller struct {
	Controller string `json:"controller,omitempty"`
}

see here
We should put it in App struct as well because right now looking at the app struct it is not possible to make out if controller is field in there or not. This will help with the OpenAPI generation of code. So I suggest that we keep the field controller inside the App struct as well.

I think that this was done like this to make parsing YAML file easier.  Am I right @containscafeine .
When we added controller field we basically started accepting multiple different YAML files (each controller has its own structure) and we had to start doing two-pass Unmarshalling (first and second)
Is there another way to do this?

We can have it like the way it is, just add this field also in App, so that the automatic parsing of the spec.go works just fine.

I'm afraid that it won't be possible, as there will be no App struct once #116 gets in.
Check spec.go in that PR

@kadel yep, Controller is a separate struct for 2 pass unmarshalling, that's the only way I could find when I looked around :(
But after the refactor, the App struct will be renamed to DeploymentSpecMod, but I'm okay with having this extra Controller field in all the Controller structs like in DeploymentSpecMod, JobSpecMod, etc if it's absolutely required for the OpenAPI stuff, but it will be a no-op field, and we should not be confusing it and using it in place of the Controller.Controller field.


#2 Horse/Donkey texture

Mod indirectly breaks the texture placement on donkeys and horses.
Noticeably, if the horse texture is intact, then donkey texture is broken, hence vise-versa.

Is this actually an issue?  This seems to be totally unrelated and was
closed right after it was made
—
Reply to this email directly, view it on GitHub
https://github.com/OffsetMods538/Better-Frost-Walker/issues/5#issuecomment-1685019260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BB7KQKY2ULDCXWK4JV3PZODXWDGMLANCNFSM6AAAAAA3UGVFVE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


port lint: lint checksums much more thoroughly

This PR builds upon discussion originating in macports/macports-guide#21, and work started in #101.
The changes here make port lint perform a much more thorough vetting of checksum stanzas in Portfiles.
Any checksum type that isn't part of the canonical list specified in portchecksum is counted as an error, as well as any unrecognized field or token.  (This will also catch situations where a filename is hanging without any checksums specified for it, erroring out.) . Errors also happen when a particular checksum does not resemble its specified type (ie., md5 1234).
In the case of deprecated checksum types, warnings are issued.  Warnings are also issued in the case that a set of checksums does not include the current set of recommended checksum types (sha256, rmd160 & size, also as per portchecksum).
As part of this work, it was realized that portlint had no tests.  This adds a test suite for portlint, but is currently only testing the checksum linting logic.  At the moment, not very much else in portlint seems to be written in a testable way, but I am not a TCL expert, so perhaps I'm wrong.
As just mentioned, I am not an experienced TCL developer, so this was very likely not done in the most succinct/cleanest way.  Thanks in advance.

Thanks so much for working on this! @jmroot has pointed out tcl issues above.

Merged! Thanks, @herbygillot!

Thank you @pmetzger and @jmroot.


change Slot to interface rather than abstract class

move existing slot base class implementation to AbstractSlot

since default methods cannot override java.lang.Object methods

make DefaultValueSlot extend Slot
reason being, other interfaces used for Slots (e.g. DefaultValueSlot) cannot extend an abstract class, therefore, potentially unsafe casting needs to be performed when working with these interfaces because it is not guaranteed their implementations are also implementations of Slot.

@rabidgremlin would be good if you force push master branch to fix the line ending issue, otherwise review by ignoring whitespace

see #26


Xmonda

Hey,
how about xmonad workspace support?
Can I hope for?
Best regards

https://github.com/jaagr/polybar/wiki/Module:-xworkspaces

Oh... Should have read this. Thanks a lot


Crash in realm::util::EncryptedFileMapping::flush() - realm::OutOfDiskSpace

How frequently does the bug occur?
Sometimes
Description
We've been seeing a realm::OutOfDiskSpace crash for quite some time now (> 3 months) when initializing our Realm database. According to the data provided by Google Firebase, it's occurring on devices that should seemingly have plenty of disk space - one crash is reported on a device with 368MB RAM free and 645MB disk space free. Our initialization code attempts to recover from any thrown exceptions and falls back to an in-memory Realm if our normal initialization fails twice. This crash seems to be happening within the Realm library and therefore we can't recover from it ourselves.
Stacktrace & log output
Fatal Exception: realm::OutOfDiskSpace

Crashed: com.google.firebase.crashlytics.ios.exception
0  ???                            0x10a147a0c (Missing)
1  ???                            0x10a147a0c (Missing)
2  ???                            0x10a147df0 (Missing)
3  ???                            0x10a140b94 (Missing)
4  ???                            0x10a13b310 (Missing)
5  ???                            0x18502781c (Missing)
6  ???                            0x185036910 (Missing)
7  ???                            0x10a13aaa8 (Missing)
8  ???                            0x10a13a748 (Missing)
9  ???                            0x19a072fa0 (Missing)
10 ???                            0x19a072f2c (Missing)
11 Realm                          0x2d8ffc realm::util::EncryptedFileMapping::flush() + 140
12 Realm                          0x2d8e74 realm::util::EncryptedFileMapping::~EncryptedFileMapping() + 40
13 Realm                          0x2e1ad4 realm::util::munmap(void*, unsigned long) + 392
14 Realm                          0x2dcc58 realm::util::File::write(char const*, unsigned long) + 212
15 Realm                          0x1577f0 realm::SlabAlloc::attach_file(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, realm::SlabAlloc::Config&) + 548
16 Realm                          0x18e9f0 realm::DB::open(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, bool, realm::DBOptions) + 1840
17 Realm                          0x191a14 realm::DB::open(realm::Replication&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, realm::DBOptions) + 124
18 Realm                          0x197124 realm::DB::create(std::__1::unique_ptr<realm::Replication, std::__1::default_delete<realm::Replication> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, realm::DBOptions) + 344
19 Realm                          0x3ae99c realm::_impl::RealmCoordinator::open_db() + 1084
20 Realm                          0x3af918 realm::_impl::RealmCoordinator::do_get_realm(realm::Realm::Config, std::__1::shared_ptr<realm::Realm>&, realm::util::Optional<realm::VersionID>, realm::util::CheckedUniqueLock&) + 72
21 Realm                          0x3af73c realm::_impl::RealmCoordinator::get_realm(realm::Realm::Config, realm::util::Optional<realm::VersionID>) + 400
22 Realm                          0x44274c realm::Realm::get_shared_realm(realm::Realm::Config) + 120
23 Realm                          0x12dab0 +[RLMRealm realmWithConfiguration:queue:error:] + 869 (shared_ptr.h:869)
24 RealmSwift                     0x67e28 Realm.init(configuration:queue:) + 92 (<compiler-generated>:92)
25 Remind101                      0x260830 static RDDependencyStore.createRealmInstance(inMemoryIdentifier:) + 411 (RDDependencyStore.swift:411)
26 Remind101                      0x25f168 closure #1 in static RDDependencyStore.setupRealm(attemptRecovery:) + 214 (RDDependencyStore.swift:214)
27 Remind101                      0x25ef70 static RDDependencyStore.setupRealm(attemptRecovery:) + 632 (<compiler-generated>:632)
28 Remind101                      0x25d6b8 RDDependencyStore.init() + 84 (RDDependencyStore.swift:84)
29 Remind101                      0x4ec1c0 RDAppDelegate.loadSingletons() + 52 (RDDependencyStore.swift:52)
30 Remind101                      0x4ed100 RDAppDelegate.application(_:didFinishLaunchingWithOptions:) + 98 (RDAppDelegate.swift:98)
31 Remind101                      0x4ed8a0 @objc RDAppDelegate.application(_:didFinishLaunchingWithOptions:) + 144 (<compiler-generated>:144)
32 ???                            0x187e27980 (Missing)
33 ???                            0x187e29414 (Missing)
34 ???                            0x187e2f560 (Missing)
35 ???                            0x1874831ac (Missing)
36 ???                            0x1879ec458 (Missing)
37 ???                            0x187483d44 (Missing)
38 ???                            0x187483804 (Missing)
39 ???                            0x187483b54 (Missing)
40 ???                            0x187483390 (Missing)
41 ???                            0x18748b8d4 (Missing)
42 ???                            0x1878f9e84 (Missing)
43 ???                            0x187a05268 (Missing)
44 ???                            0x18748b5cc (Missing)
45 ???                            0x1872b34b4 (Missing)
46 ???                            0x1872b1e34 (Missing)
47 ???                            0x1872b30dc (Missing)
48 ???                            0x187e2d700 (Missing)
49 ???                            0x1879234e4 (Missing)
50 ???                            0x194a5a5d8 (Missing)
51 ???                            0x194a85d44 (Missing)
52 ???                            0x194a696a4 (Missing)
53 ???                            0x194a85a0c (Missing)
54 ???                            0x18502781c (Missing)
55 ???                            0x18502b30c (Missing)
56 ???                            0x194aadfa0 (Missing)
57 ???                            0x194aadc30 (Missing)
58 ???                            0x194aae184 (Missing)
59 ???                            0x1853b507c (Missing)
60 ???                            0x1853b4f78 (Missing)
61 ???                            0x1853b427c (Missing)
62 ???                            0x1853ae25c (Missing)
63 ???                            0x1853ad9f4 (Missing)
64 ???                            0x19ca7e734 (Missing)
65 ???                            0x187e2b75c (Missing)
66 ???                            0x187e30fcc (Missing)
67 Remind101                      0x1b844 main + 12 (RDAppDelegate.swift:12)
68 ???                            0x185069cf8 (Missing)

Can you reproduce the bug?
Not yet
Reproduction Steps
Cannot reproduce. Here's our stripped-down initialization logic:
private class func setupRealm(attemptRecovery: Bool = true) -> Realm {
    do {
        return try self.createRealmInstance()
    }
    catch let exception {
        // Deletes our entire realm directory, calls RLMRealm.resetRealmState()
        self.resetRealm()

        if attemptRecovery {
            return RDDependencyStore.setupRealm(attemptRecovery: false)
        }

        return try! self.createRealmInstance(inMemoryIdentifier: "InMemoryRealmFallback")
    }
}

private class func createRealmInstance(inMemoryIdentifier: String? = nil) throws -> Realm {
    var config = Realm.Configuration.defaultConfiguration

    if let inMemoryIdentifier = inMemoryIdentifier {
        config.inMemoryIdentifier = inMemoryIdentifier
        config.encryptionKey = nil
    }
    else {
        guard let realmDirectory = self.realmDirectory() else {
            throw RLMError(.fail)
        }

        if (try? realmDirectory.checkResourceIsReachable()) != true {
            // Create a directory for our Realm and all its auxiliary files.
            // Disable file protection for this directory.
            try FileManager.default.createDirectory(at: realmDirectory,
                                                    withIntermediateDirectories: false,
                                                    attributes: [.protectionKey : FileProtectionType.none.rawValue])
        }
        else {
            // Directory exists. Just confirm file protection is off.
            try FileManager.default.setAttributes([.protectionKey : FileProtectionType.none.rawValue],
                                                  ofItemAtPath: realmDirectory.path)
        }

        config.fileURL = realmDirectory.appendingPathComponent(kRealmDBName).appendingPathExtension(kRealmExtension)
        config.encryptionKey = try self.realmKey() // Matches Realm's sample code for generating an encryption key
    }

    // Have to manually set the objectTypes because generic base classes are not recognized below iOS 14.5
    if #unavailable(iOS 14.5) {
        config.objectTypes = [
            // <all of our classes...>
        ]
    }

    config.deleteRealmIfMigrationNeeded = false
    Realm.Configuration.defaultConfiguration = config

    return try Realm(configuration: config) // <= Last line of the stack trace in our code
}

In some instances we're able to capture and log an initial failure before the application crashes. These instances included one of these two messages:
Error code 28: ftruncate() inside prealloc() failed: No space left on device
Error code 1: ftruncate() failed: No space left on device

As mentioned, this is happening on devices that Firebase reports as having more than 100MB of free disk space, and it's happening after we've deleted our existing Realm file and even as we try to fall back to an in-memory Realm instance.
Version
10.20.0, 10.28.2
What SDK flavour are you using?
Local Database only
Are you using encryption?
Yes, using encryption
Platform OS and version(s)
iOS 14 and 15
Build environment
ProductName:	macOS
ProductVersion:	12.4
BuildVersion:	21F79

/Applications/Xcode.app/Contents/Developer
Xcode 13.4.1
Build version 13F100

/Users/alexleffelman/.rbenv/shims/pod
1.11.3
Realm (10.28.2)
RealmSwift (10.28.2)

/bin/bash
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin21)

carthage not found
(not in use here)

/usr/bin/git
git version 2.32.1 (Apple Git-133)

Hi @LeffelMania,
What is the expected Realm's size we are talking about?
"Large memory allocations are guaranteed to be page-aligned" means this is might be impossible to allocate a single block in low memory condition.
How does the app handles low memory warnings?
Did you try to fill the Device's space to emulate the condition?

We don't track the size of Realms out in the wild, but my fairly large personal account shows a Realm of size 573KB, which feels pretty small to me, but I have no frame of reference for that.
The app doesn't really respond to low memory conditions. My two responses to that question would be 1) disk space isn't memory, and this is presenting as an out-of-disk-space crash, and 2) this is happening immediately upon launching the app, so there hasn't really been an opportunity for us to run up our memory consumption yet at this point.
I haven't filled a device and tried to reproduce yet, but I will to do that very soon with an old device I have.

Realm creates a file for inMemory Realms so the lack of storage can be an issue, nut we're talking about rather small files (about 0.5MB)
The other thing is
   // by the definition of F_PREALLOCATE, a proceeding ftruncate will not fail due to out of disk space
   // so this is some other runtime error and not OutOfDiskSpace

Also I have found the interesting ticket in realm-core https://github.com/realm/realm-core/issues/3005
@finnschiermer could you please рудз me with that?

Hi @LeffelMania Are you pinning versions of the Realm anywhere? You can check if versions are being pinned by setting maximumNumberOfActiveVersions on the Realm configuration.

We are not pinning versions anywhere; that property isn't used in our configuration.

@LeffelMania are you only seeing this crash on devices with limited storage space available? i.e < 1000mb free storage available? If so I have a feeling the issue here is that the device is running out of VM space and the OS is killing apps to allow for system processes to continue running.

The available disk space and RAM reported by Firebase for these issues is all over the place. I did a scan of 40 instances over the last two weeks and saw reported free disk space in the range from 20MB all the way to 1.94GB, and available RAM from 45MB to 1.07GB. So unfortunately I can't say that it's only happening to devices with no space left.
Also, the OS presumably wouldn't be killing the app that the user just opened in order to continue running; this crash is appearing as soon as the user launches the app and we're initializing the Realm database for the first time. That seems an odd time for the OS to clean up our process to conserve resources, but I'm not in a position to rule it out obviously.
I've emailed y'all a bundle of crash logs to your realm-help address so you can inspect device properties and stack traces further.

@tgoyne do you have any ideas what can cause this? The error appears during initial extension of the file to match a page boundary. My understanding is that Failing at this point is basically only possible if the file system is completely full. Could lack of access rights cause the problem?

👋 any movement on this? It's still one of our biggest crashes in production.

any news?


PRODTASKS-297: Default to all Koji archive types if provided list is …

…empty

what is PRODTASKS-297?

@ausil Internal JIRA reference. Please contact myself or @dwalluck on internal IRC for further details.

@rnc lets keep those internal and reference something public and accessible please


[TASK] Add Input States to Bridge dApp Control Cards for Improved Visual Feedback

Description
Our bridge dApp control cards do not currently provide visual feedback to users on the status of their actions within the dApp, which can cause confusion and accessibility issues. By implementing input states for our control cards, we can provide users with clear visual feedback on the status of their actions, enhancing the user experience and accessibility of our application.

dependency: https://github.com/orgs/webb-tools/projects/7/views/19?pane=issue&itemId=25251569

@monaiuu can you add the relevant figma links and options here.

https://github.com/webb-tools/webb-experiences/issues/132

Addressed in V2.


RuntimeError: [ PARAMETER_MISMATCH ] Failed to set input blob with precision: I64, if CNNNetwork input blob precision is: FP64

Hi
I get the error:
RuntimeError: [ PARAMETER_MISMATCH ] Failed to set input blob with precision: I64, if CNNNetwork input blob precision is: FP64
whenever i run with --init-image?
terminal> python3 demo.py --prompt "test image" --init-image ./output.png --mask ./output-mask.png --strength 0.5
The image I'm passing is the one created from the last run (I'm trying to do some inpainting). I believe it's saying that the image is Formatted as int-64 when its looking for float-64.  Since it was generated from the engine, that leads me to believe it does some type of float => int conversion when writing the final image? Is that right?  Do we need to up-convert images int => float before passing it to the engine?

I'm getting the same error after using jpg images

thank goodness its not just me

Yes, I've been trying to debug the issue but I haven't worked yet with
Torch to see. I will try later an older version to see if it works.
El jue, 29 dic 2022 a la(s) 12:20, Albert @.***)
escribió:

thank goodness its not just me
—
Reply to this email directly, view it on GitHub
https://github.com/bes-dev/stable_diffusion.openvino/issues/110#issuecomment-1367442753,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIQW5VFXXMFZ23UVTEKLWTWPW23VANCNFSM6AAAAAATH3SIRI
.
You are receiving this because you commented.Message ID:
@.***>

--
Asdrúbal Iván Suárez Rivera

Same, would you like to work together on the issue?

the same problem, have you guys fixed it?

Not yet, I'm not sure how to solve but I can help working on that @alabasterfox @thathappiness

@asdrubalivan @thathappiness same, what's the best way to compare notes?

I have started to get similar issue - RuntimeError: [ PARAMETER_MISMATCH ] Failed to set input blob with precision: I32, if CNNNetwork input blob precision is: FP64
After forcing variable "t" to be float the above error seems to resolve.
In line https://github.com/bes-dev/stable_diffusion.openvino/blob/master/stable_diffusion_engine.py#L186 change "t" : t   to "t": float(t)

After some testing with both demo.py and demo_web.py, I am confirming that making arisha07's change in stable_diffusion_engine.py
from:
            # predict the noise residual
            noise_pred = result(self.unet.infer_new_request({
                "latent_model_input": latent_model_input,
                "t": t,
                "encoder_hidden_states": text_embeddings
            }))

to:
            # predict the noise residual
            noise_pred = result(self.unet.infer_new_request({
                "latent_model_input": latent_model_input,
                "t": float(t),  // <== updated
                "encoder_hidden_states": text_embeddings
            }))

has resolved the issue in my SD engine as well

Maybe this can be committed to the official package?


Shim in empty directories into workers

As of now, Pachyderm will record empty directories in a repository, but it won't check those out and shim them into a running worker.  Some users have use cases where they need to see all directories even if they are empty.

We are seeing this issue with our ML pachyderm setup where the first pipeline calls a script that downloads files from S3 and creates a particular directory structure, with some of these directories empty. The following pipeline runs through all directories and populates them according to some predefined rules. The second pipeline does not know about how the directory structure was created or which directories should be present. Therefore, when some of the empty directories are missing, the second pipeline does not populate all required directories / files.

Here a dummy pipeline scripts to reproduce the problem:
pipeline-with-empty-dirs.json.zip


IaC with Cloudformation

The folder structure should be the name of the project and then the sub folder structure should be named as cloudformation
The changes in the files look good Please revert the PR with the appropriate folder structure changes

I have changed the folder structure


Reloading doesn't work quite often

I can reproduce this quite reliably. It seems to me that the project doesn't get reloaded most of the time between ghcid restarts.
My workflow is the following:

at the project root I have a ghcid-run.sh file with contents similar to the followiing:

#!/bin/sh
ghcid -W \
  --command 'stack ghci' \
  --test ':main -n LocalMockGhcid --run-mode Mock --app-snowflake-node 0 --log-level "Level 0" --gpio-pir-pin "Pin 16" --node-id 1234 --network-interface=enp4s0 --cookie-max-age 86400 --auth-server-key foobabbabababa'

I'd like to:

ignore warnings
use stack ghci as the repl command
run a particular --test command.
The test command in this case simply fires up my main function with some arguments.

However, ghcid simply doesn't seem to detect file changes anywhere in the project for most of the time, and I need to keep restarting it to get it to start reloading on changes.
Version info:
Auto reloading GHCi daemon v0.7.5

I'm using NixOS:
Linux quasar-nixos-tr 5.4.6 #1-NixOS SMP Sat Dec 21 10:05:23 UTC 2019 x86_64 GNU/Linux

Can you pass --verbose and share the full log. That will tell us what files it is waiting on and see why it's broken.

@ndmitchell thanks for the quick response.
Here's the output with --verbose, and as the logs at the end say: I made some changes to /Network/Frontend/Login/Lib.hs and it seems to me that ghcid catches the notification (via  changes in TAGS instead of the .hs file) but doesn't restart the :main function.
I'm unsure of the inner workings of ghcid so I'm not sure if this helps.

Another strange thing I'm noticing is that changes in my ~ are being picked up:
%WAITING: Notify signaled
%NOTIFY: Modified "/home/ashesh/.histfile" 2020-03-16 09:43:41.875765261 UTC False
%WAITING: Notify signaled
%NOTIFY: Modified "/home/ashesh/.histfile" 2020-03-16 09:44:08.402526586 UTC False
%WAITING: Notify signaled
%NOTIFY: Modified "/home/ashesh/.histfile" 2020-03-16 09:44:11.965825107 UTC False
%WAITING: Notify signaled
%NOTIFY: Modified "/home/ashesh/.histfile" 2020-03-16 09:45:04.60124685 UTC False
%WAITING: Notify signaled
%NOTIFY: Modified "/home/ashesh/.histfile" 2020-03-16 09:46:03.79569727 UTC False
%WAITING: Notify signaled
%NOTIFY: Modified "/home/ashesh/.psql_history" 2020-03-16 10:08:18.717236727 UTC False

Is that expected?

The abstraction Ghcid uses says that if anything in a directory changes it then checks all files and continues on if any of the interesting ones change. That's partly for cross-platform happiness. Since your .ghci file is in ~ it watches the home directory, but these fire a change which is immediately ignored, so fairly cheap.
I think the issue is that by default ghcid won't run the tests if there are warnings. You can override that behaviour with --warnings. Does that solve it?

@ndmitchell thanks, I understand the reasoning behind watching ~ for changes.
As for the warnings, I do have the -W in my ghcid-run.sh but that doesn't seem to do the trick.
It seems to me that the reloading works some times: and it continues to work for that session. And sometimes it just doesn't. I have to keep restarting ghcid-run.sh until it reloads on each change.

Is the -W getting to ghcid or not? I just pushed a patch to HEAD that makes ghcid show the arguments it got when run with --verbose. Would be good to ensure that the warnings and test really do get through.
Is the trace you attached earlier for one of the times where it got stuck? It said it was watching the files::
%WAITING: /home/ashesh /home/ashesh/code/homebot/rpi/motion-detect-camera /home/ashesh/code/homebot/rpi/motion-detect-camera/app /home/ashesh/code/homebot/rpi/motion-detect-camera/src/Cluster /home/ashesh/code/homebot/rpi/motion-detect-camera/src/Control /home/ashesh/code/homebot/rpi/motion-detect-camera/src/Lib/Parse /home/ashesh/code/homebot/rpi/motion-detect-camera/src/Network /run/user/1000/haskell-stack-ghci/7b57b5b9

Is the file you were trying to modify in one of those directories?
Can you also try passing --poll as that avoids the file watching and instead polls for files.

@ndmitchell
I'm assuming the -W is getting to ghcid: the code has several warnings and by default the behaviour is only to run --test when there are no warnings.
And yes, the trace was when ghcid was stuck. I'm not sure if the directories being watched are watched with any depth at all: or is the watching only at the depth of the directory? Or are we watching dirs. recursively?
If we're watching files recursively, the answer is yes, the file is in the same hierarchy. If not, then it isn't, but it is somewhere in ./src.
I'll try with the --poll and later with the HEAD and report back.

@ndmitchell I can confirm that the --poll option also doesn't work for me. I've not yet tried your changes from HEAD but it seems to me that the reloads work properly (without --poll) for the first few times and then completely stop after a while. And sometimes the reloading doesn't work at all and sometimes it does for hours.
Restarting the ghcid process several times fixes the issue and then it gets stuck again.
In this case the codebase has no warnings, so running ghcid without -W and --test reloads okay.
The --test command fires up a Wai application server which is a never ending process. So my guess is that --test is a process that should exit (was that the intention of the --test flag?)
In any case, it seems to me that the fact that reloading works intermittently points to some problem.
If you can point me to the relevant part of the code or to where I can get started, I wouldn't mind taking a look myself.

It doesn't watch recursive directories. The --test program is expected to exit, and if it doesn't, we send a ctrl-c to it.
From the sounds of it, it seems that ghcid wasn't watching where you were changing? It watched a parent directory, but not the final in question. So is it always not watching there? Or do you sometimes change files it is watching? Assuming the problem is it isn't watching the right place, then you need to figure out why it isn't watching there. Generally it watches by looking at error messages and :show modules to figure out what is loaded. All of that is in the trace, so the thing to do is figure out why it doesn't think your file is interesting. And that's likely to be a mis-parsed error, an unreported dependency or something similar. While you could go to the code, the verbose output is usually more illuminating until you have identified what's wrong.


log_wrappers: add tikv_alloc dep

This fixes the error generated by check-bins-for-jemalloc.sh
I also added more info to the error message in the script,
indicating how to fix the problem.
Fixes https://github.com/tikv/tikv/issues/4220

em, seem the log wrapper module is introduced after the tikv_alloc, I am a little surprised that we miss checking it. seem that there is no CI for the alloc check, we should add it.
PTAL @zhouqiang-cl @cwen0


Improve support for TLS v1.3

Improve support for TLS v1.3

Add TLS v1.3 to documented options.
Add CLI support
Add test cases.

Proposed Changes
Please describe the big picture of your changes here to communicate to the
VerneMQ team why we should accept this pull request. If it fixes a bug or
resolves a feature request, be sure to link to that issue.
Types of Changes
What types of changes does your code introduce to this project?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes issue #XXXX)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (correction or otherwise)
[ ] Cosmetics (whitespace, styles...)
[ ] DevOps (Build scripts, pipelines...)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

[ ] I have read the CODE_OF_CONDUCT.md document
[ ] All tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if needed)
[ ] Any dependent changes have been merged and published in related repositories
[ ] I have updated changelog (At the bottom of the release version)
[ ] I have squashed all my commits into one before merging

Further Comments
If this is a relatively large or complex change, kick off the discussion by
explaining why you chose the solution you did and what alternatives you
considered, etc.

Does VerneMQ wants to support OTP 22?

@mths1 Thanks. I think the 3 OTP versions rule is good for us: 23, 24, 25. In other words: fine dropping 22 compatibility.


refactor(app): refactor PreventRobotCaching section

Overview
refactor Prevent Robot Caching section
close RAUT-938  partially

Test Plan
Go to Advanced Settings in App Settings

Check Prevent Robot Caching section is rendered correctly
The config value is updated when clicking the toggle button

Changelog

create a new component for  Prevent Robot Caching section
create a new test for  Prevent Robot Caching section
update AdvancedSettings component and test

Review requests

Risk assessment
low

[ ] solve conflicts


Make provisioning more resilient to single-region provision failures

I'm assuming CloudFormation wait conditions are used for stack creation timeouts. But we are frequently seeing stack creation time vary wildly between different regions, e.g. two regions will complete in 15 minutes and the third will timeout after 30 minutes. When this occurs multiple times in a row, I start to feel as though there must be a better way to get new stacks provisioned.
Would it be possible to modify the provisioning to pass some large value for the CloudFormation wait condition, and then poll the stack creation status; and when a majority of regions complete before some timeout A, repeatedly retry provisioning the failing regions until a second timeout B?

@marckubischta There is a way to configure stack creation timeout. From porter help debug

STACK_CREATION_TIMEOUT
Override rollback time with a string parsed by
https://golang.org/pkg/time/#ParseDuration
This is clamped to the min and max duration supported by STS AssumeRole
Example:
export STACK_CREATION_TIMEOUT=1h
porter create-stack -e dev

Let me know if that will suffice

@marckubischta bump

I think you misunderstood my scenario. I'm not looking to just increase the timeout; I still want to have stack creation time out after 30m. What I am asking for is a way to detect when the majority of regions have successfully provisioned, and in this case, re-run the provisioning for the failed regions.

I think the distinction between is between

region A completes in 10 minutes, region B completes in 20 minutes, neither have any anomalies other than one taking a long time. A timeout to encompass the longer time is sufficient.
Region A completes in 10 minutes, region B encounters some issue, where the stack will never complete but will only fail when it hits a timeout. Lengthening the timeout is not helpful if the stack is stalled. The incomplete stack is torn down and a retry deploy is a noop on region A, and region B gets a new deploy attempt.

Ideally we would be able to detect the situations where a given stack is a lost cause and cancel the creation as early as possible. That seems like a pretty difficult problem though which makes Marc suggestion of interest, even though It is far from elegant.
Reflecting on the most common stall scenarios, what would be more helpful is a timeout on getting a complete signal from an individual instance and aggressively terminate those that fail to bootstrap. I'm not sure porter has the necessary visibility to do that though. At least not trivially.

Ideally we would be able to detect the situations where a given stack is a lost cause

Agreed but there's no way for porter to know if the failure was legitimate or not. I think at best it could see a majority succeeded and perform the retry as long as sts token expiration / stack creation timeout < retry count, otherwise porter will fail to poll for stack events during a retry that exceeds sts token expiration.
I tend to favor failing fast over retrying in this scenario. #22 will address this issue much better in the long term by bypassing CloudFormation altogether.


Pr/separation from styleguide

This isn't ready to merge. I'm trying to remove our dependencies on our sofe services


Plugin Activation

I am new to micro and installed this plugin via the command mentioned on the plugins page:
> micro -plugin install nord-colors

which creates the directory ~/.config/micro/plug/nord-colors/. However, I don't seem to be able to activate it. My first attempt was to run
> set colorscheme nord-colors

which resulted in nord-colors is not a valid colorscheme. Inspecting the created directory, I saw that the definition files seemed to be of the form nord-16.micro
so I also tried
> set colorscheme nord-16

which resulted in the same error. Would you mind clarifying how I can "activate" the nord colors? Maybe it works differently since this is considered a plugin and not a colorscheme.

I am aware of this issue and am trying to fix it. The issue is that the .lua file that is supposed to add the colorscheme files to micro is not running correctly. Until I figure it out, you can manually install by moving the colorschemes (.micro files) to the colorschemes directory.
mkdir ~/.config/micro/colorschemes
mv ~/.config/micro/plug/nord-colors/*.micro ~/.config/micro/colorschemes

Perfect, that works.
Thanks a lot for your help!

The issue still seems to exist, even with the new .lua file. This may take some time to fix, until then, anyone who has this issue can use the commands listed above to manually enable the colorschemes.

The issue is now fixed; make sure to run the nordsetup command to set up the files after installation. I will make an issue on the main Micro GitHub later to address the issue of runtime files not being visible at startup.

You should be able to use AddRuntimeFile similar to how it is done here: https://github.com/Theodus/micro-monokai-dark. Is there a problem with that method?

Unfortunately, using AddRuntimeFile runs after micro checks for the colorscheme, so it always says nord-tc is not a valid colorscheme even when I can enable it directly after. Also, using AddRuntineFile as the other plugins do without importing micro/config leads to a lua error, since it is not defined.
I can post a more detailed issue on the micro main channel if you would like.

I think it should work fine if you run it in the script top-level (not inside the init function). For example:
VERSION = "1.1.3"

local config = import("micro/config")

config.AddRuntimeFile("nordcolors", config.RTColorscheme, "colorschemes/nord-tc.micro")
config.AddRuntimeFile("nordcolors", config.RTColorscheme, "colorschemes/nord-tc-light.micro")
config.AddRuntimeFile("nordcolors", config.RTColorscheme, "colorschemes/nord-16.micro")
config.AddRuntimeFile("nordcolors", config.RTColorscheme, "colorschemes/nord-16-light.micro")
config.AddRuntimeFile("nordcolors", config.RTHelp, "help/nordcolors.md")

I will check that to make sure


Who uses PDF417_EXTRA_METADATA from ResultMetadata struct?

In continuation of my effort to deprecate the current usage model of the ResultMetadata class, I'd like to get rid of the PDF417_EXTRA_METADATA use case. The information stored under that key can be divided in 2 parts:

segmentIndex to sort codes that spread across multiple symbols. This is basically a duplication of what STRUCTURED_APPEND information is for the QRCode and is currently used in the blackbox tests.
OPTIONAL_FIELD entries such as fileName or sender that are purely PDF417 specific.

Number 1) can be mapped to the structured append keys (and later ported into plain members of the Result class) and 2) can be ignored if no one uses them anyway or moved over to a single format specific 'custom data' struct, much like what you get behind PDF417_EXTRA_METADATA right now, but without the ResultMetadata class in-between.
I'd like to know if anyone uses PDF417_EXTRA_METADATA at all. @huycn, @gong-xiaomei, @Sarmini-M, @vkrause, @tailsu ?

We aren't using any of this to my knowledge, I didn't even know this existed :)

I just committed a change dealing with the structured append part of the meta data. And due to lack of interest, I will simply drop the other half from the public interface until someone actually has a use for it.


KAFKA-7613: Enable -Xlint:try, fixing warnings

Fix all existing javac warnings about try statements and remove -Xlint:-try from the javac options in build.gradle. This addresses part of KAFKA-7613, but further work will be needed for the other warnings.
A couple of @SuppressWarnings("try") were needed to avoid having to override close() on interfaces extending AutoCloseable. The problem with those is AutoCloseable.close() is declared to throw Exception, which allows InterruptedException, which generates a warning.
try-with-resources with an ignored variable causes a warning, and I favoured rewriting these rather than suppressing the warning.

@ijuma would you be able to review this?

@ijuma would you be able to take a look at this, since you opened the original issue?

Yes, I should be able to review this tomorrow.

@ijuma did you have any further feed back about this? And would you be able to re-run the tests?

Rebased for conflict. @ijuma could you re-run the tests and maybe take another look?


The right way to register custom doctrine type

Hello, first of all, thanks for this great tool!
Could you explain the right way and right place to register custom doctrine type for all suites which uses Doctrine/Doctrine2 modules please?

I solve my problem with \Codeception\Module::_beforeSuite.


QnAMaker: include metadata and source in QnAMakerResult

QnAMaker can include metadata (AKA filters) that are returned with the answers. Currently, the Microsoft.Bot.Builder.CognitiveServices.QnAMaker library does not support it.
This PR adds the missing properties "metadata" and "source" from the answer response in the QnAMakerResult model (https://westus.dev.cognitive.microsoft.com/docs/services/597029932bcd590e74b648fb/operations/59703a928eb8131608e2f7a5).

@jonicis I was looking for the same information returned from Qna and found this PR already raised. I need this change as well in next version sooner. MS team please merge the change in master.

@jwiley84, Any time line on getting this merged in Master and release.

MS Team, I need this change released, please help.

@jwiley84, Any updates on above PR merged and released.

See QueryResults  and QnAMakerOptions class in botbuilder-dotnet repo.
They include metadata (StrictFilters, MetadataBoost)

Any hope of getting this one in v3 as well.

Thank you for opening an issue against the Bot Framework Cognitive Services repo. As part of the Bot Framework v4 release, we’ve moved all the Luis and QnA work to platform SDK repo. We will continue to support and offer maintenance updates via this repo.
From now on, https://github.com/Microsoft/botframework-sdk repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the Bot Framework repo found here:
https://github.com/Microsoft/botframework-sdk/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team


Script not working at all for me...

Hello,
I couldn't find a way to make your script work even if I tried... I really like the look and feel of your menu and would really like to use it so would it be possible for you to send me a working "complete" version of the script? I'm fairly new to jquery and js so I don't understand much what can be wrong...
Thank you!

This repo hosts a complete and working version of the script, we need more info to help you.


Document when to use/ when not to use fluid rescaling

Closing this, since in v2, you can just ditch the fluid: prefix.


Compute requirement

Hello, Excellent work by the team. May I know what sort of computational resources (no. of GPUs, RAM etc.) I will require for both reproducing this (LISA) and further fine tuning. Thanks

For the 7B model, training can be done with 8 * 3090 GPUs (24GB VRAM) (actually, the number of GPUs can be lowered by increasing the grad_accumulation_steps as long as you make sure grad_accumulation_steps * num_GPUs * batch_size keeps the same). For training the 13B model, currently, you may need GPUs with no less than 40GB.

Thank you for quick reply!


refactor: adapt to new network data APIs

Brief Information
This pull request is in the type of (more info about types):

[ ] build
[ ] ci
[x] docs
[ ] feat
[ ] fix
[ ] perf
[x] refactor
[ ] test

Related issues (all available keywords):

resolve #552
resolve #268

Details

[x] API adaptation
[x] filter out edges with samll weight to make graph charts sparse and clear
[x] make the networks look better
[x] add docs to explain the edge triming strategy
[x] update screenshots in READMEs

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA

Others

Hi @frank-zsy, I'm working with edges filtering(triming) and my idea is to choose a fixed value(1~3 maybe) as the threshold so edges with smaller value will be simply dropped.
At the moment I find edge values in a repo's developer network are also global. For example, frank-zsy -> tyn1998 is always 15.8 no matter the edge is in hypertrons-crx's developer network, open-digger's developer network or developer's developer network. While currently node values in a repo's developer network is local to that specific repo.
Back to the edges filtering topic. There is chance that an actually unwanted edge is reserved just because its global value is greater than the threshold, however the fact is, its local value is very small which means the two developers have little connection in that repo. But the edge is not removed in this scenario.
In contrast to the current network data, I find edge values in old repo's developer network data differ from repo to repo:

What do you think of the issue? Can it be an issue?

The Graph was trimmed(fine tuned) for better look.
e.g. Hypercrx:

e.g. OpenDigger:

docs to explain edge triming strategy:

At the moment I find edge values in a repo's developer network are also global. For example, frank-zsy -> tyn1998 is always 15.8 no matter the edge is in hypertrons-crx's developer network, open-digger's developer network or developer's developer network. While currently node values in a repo's developer network is local to that specific repo.
What do you think of the issue? Can it be an issue?

Yes, in current implementation, relationships between developers' are always global relationships rather than in project relationship. In project relationship requires issue level collaboration but not repo level which is more difficult than repo level right now since issue is not represented in Neo4j database.

@tyn1998 Networks without some low weight edges surely looks better.

Yes, in current implementation, relationships between developers' are always global relationships rather than in project relationship. In project relationship requires issue level collaboration but not repo level which is more difficult than repo level right now since issue is not represented in Neo4j database.

OK, so we will use these data.

Networks without some low weight edges surely looks better.

Well, networks for big repos such as vscode are still dense because edge values of those networks are generally higher than the thresholds(for repo-repo is 5, for developer-developer is 2.5) so hardly an edge is cut:

I considered "percent" rather a fixed threshold first but for me the "percent" strategy makes less sense so I chose the latter one.

If you think the strategy applied is satisfying, this PR will be reviewed by someone and then merged.

I think the density for vscode network is quite desirable too, good to me~

@wj23027 @andyhuang18 Hi guys, would you mind pulling this branch to your machines and have a test?
@wxharry could you please review this PR and approve it?
And happy new year!

Hi~happy new year. I fetched this branch and test it right now

This is the result of testing on my machine~

Hi, Thank your contribution. Here is some questions I had during the test.

seperate cluster. As we simply remove edges below the threshold, there could be a completely seperate cluster without the current repo in the Project Correlation Network. It could be confusing sometimes. We might need to at least explain that to the users.

useless mocking code. Looks like all the code that use mocking are removed, do we still need the code within src/mock/?

Hi @wxharry, thanks for reviewing the code.

I do worry those possible separate clusters might confuse users. I have added explanation on removed edges and assumed that users can understand why some edges disappear. But it is still counterintuitive, rihgt? Maybe I can modify the code to always reserve edges that containing the current repo/user, what do you think?
As you pointed out, we do not need them anymore. In fact, I removed these code in https://github.com/hypertrons/hypertrons-crx/pull/547/commits/4c3d2677f8da86dfe0a56bbe3d1be86f3868fc35 to get a minimal Hypercrx. But that is for a further iteration plan so I think we should remove them in this PR, too.

I do worry those possible separate clusters might confuse users. I have added explanation on removed edges and assumed that users can understand why some edges disappear. But it is still counterintuitive, rihgt? Maybe I can modify the code to always reserve edges that containing the current repo/user, what do you think?

I don't have any idea, either. IMO, it is fine to have some separate nodes or small clusters. But the cluster I mentioned before is way too large and it doesn't include the target repo.

As you pointed out, we do not need them anymore. In fact, I removed these code in 4c3d267 to get a minimal Hypercrx. But that is for a further iteration plan so I think we should remove them in this PR, too.

Got it. Looking forwards to the new hypercrx. 😆

Maybe I can modify the code to always reserve edges that containing the current repo/user, what do you think?

I will try it out and attach some screenshots here, then we make a decision.

Well, it's difficult to make a decision cause both have pros and cons. But still, I like the sparse version(the one in left side below) a bit more. How about you guys? @wxharry @frank-zsy @zhicheng-ning @xgdyp @will-ww
Contrast:

I like the sparse version(the one on left side below) a bit more. How about you guys?

As for me, disconnected graph makes me confusion when I first saw it. Users may lose information between different subgragh. One of my suggestions is to show the full connection information by default and provide a custom option to show sparse version if the technical implementation is not too difficult.

I prefer the sparse version as well. I suggest we keep the sparse version in this pr since this pr is about new data APIs and may open an issue for further discussion on how to deal with the graph display.

I suggest we keep the sparse version in this pr since this pr is about new data APIs and may open an issue for further discussion on how to deal with the graph display.

Good idea, in fact the networks before refactoring had some edges removed (they had been removed before data files were generated). While the threshold seemed smaller than the ones we adopt here.

As for me, disconnected graph makes me confusion when I first saw it. Users may lose information between different subgragh. One of my suggestions is to show the full connection information by default and provide a custom option to show sparse version if the technical implementation is not too difficult.

This is a great idea and I'll consider it when we improve the networks next time. Thank you @zhicheng-ning!
Hi @wxharry, you may review the PR and approve it :-)

/approve


165 feature local trajectory planning with frenet trajectory planner

Description
This PR introduces the frenet trajectory planner to our project. It enables to create a new trajecotry during runtime when a object ist detected in front.
Fixes #165
Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Does this PR introduce a breaking change?
No
Most important changes
New method in motion planning.
utils.py file that has some utility methods to free up space in the motion planning file.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works (might be obsolete with CI later on)
[x] New and existing unit tests pass locally with my changes (might be obsolete with CI later on)

Changes done please re-review


proposal: new package simpleinput for Go education

Problem:
Every few months, someone will post on Reddit that they're trying to make an intro-to-CS-style input prompt and they're confused why their code using fmt.Scan* doesn't work (inevitably because the input has a space and they're ignoring errors). I think that just for the use case of education, there should be something that does the thing that they want.

Here are some typical posts

https://www.reddit.com/r/golang/comments/alvdhl/force_golang_to_scan_a_number_instead_of_a_single/
https://www.reddit.com/r/golang/comments/atlehx/flushing_standard_input_before_scanf/
https://www.reddit.com/r/golang/comments/2h5qnw/using_numerical_values_from_slices/
https://www.reddit.com/r/golang/comments/wv1i2z/can_someone_tell_me_what_im_doing_wrong_im_trying/
https://www.reddit.com/r/golang/comments/hkz1im/what_is_the_most_idiomatic_way_of_getting_input/
https://www.reddit.com/r/golang/comments/8umvpt/unclear_on_scan/
https://www.reddit.com/r/golang/comments/4hktbe/read_user_input_until_he_press_ctrlc/
https://www.reddit.com/r/golang/comments/tq3wpc/scanln_and_scanf_jump_after_entering_string_value/
https://www.reddit.com/r/golang/comments/qja60y/issues_with_fmtscanf_reading/
https://www.reddit.com/r/golang/comments/kee82p/i_am_bit_confused_about_golangs_scanf/
https://www.reddit.com/r/golang/comments/bkqos6/differences_between_scan_functions/
https://www.reddit.com/r/golang/comments/whfi8p/question_about_fmtscan/
https://www.reddit.com/r/golang/comments/p2tnio/in_golang_is_there_is_any_way_to_take_input/
https://www.reddit.com/r/golang/comments/s85xxl/having_trouble_with_scanning_input_new_to_language/

You can find more by searching site:https://reddit.com/r/golang fmt.scan.

New programmers aren't a huge source of new Go users. On the other hand, even if most Go programmers come from other languages, it is convenient when learning the language to be able to write simple intro-to-CS-style question/response programs to get a feel for the language. There ought to be something very simple that novice can find without knowing anything about Go or IO. Obviously, novices could and probably should be using bufio.Scanner already, but they aren't finding it today. Instead they look in fmt (because they are already using fmt.Println) and find the Scan family of functions. Then they are frustrated when it does not work the way they expect.
Proposed solutions
Proposed solution one is simple: mark the Scan functions as deprecated to hide them from the documentation. Even Rob Pike regrets adding the Scan functions.
Proposed solution two is to add a new package just for education purposes.
// Package simpleinput provides function for basic reading from os.Stdin.
// Functions in this package are concurrent safe.
// For better performance, use bufio directly.
package simpleinput

// SetSource sets the source that simpleinput buffers reads from.
// By default, it uses os.Stdin.
func SetSource(io.Reader)

// Source returns the underlying io.Reader that simpleinput buffers reads from.
func Source() io.Reader

// Error returns the last error encountered by simpleinput, if any.
func Error() error

// Read reads from Source until it receives an error, typically io.EOF.
func Read() string

// ReadLine reads one line from Source. It removes "\n" and "\r\n" from its output.
func ReadLine() string

// ReadLines reads Source until it encounters an error.
// It removes "\n" and "\r\n" from its output.
func ReadLines() []string

Obviously, none of this is strictly necessary, but it would help Go learners, particularly those new to programming.
Cf. #54620

How about https://go.dev/doc/faq#x_in_std? Suggesting better fmt scanning APIs is one thing, but if these APIs are primarly for new Go users, perhaps they should be in a Go module that's aimed and promoted to them.
At the same time, I would be conflicted with APIs targetting new users only. If I was learning a language, I would want to learn the "normal" or "proper" way to accomplish a task, not an oversimplified way that I should probably un-learn later.

I think it's a fair question whether Go wants to target new users or just say that's out of scope. However, if the decision is made that targeting new users is in scope, then I don't think it makes any sense to use an external module. You can already find tons of simple input packages online. The forums are full of people who haven't found those modules because they are looking in the standard library for the equivalent of Python's input() and then they get burned using fmt.Scanln instead of what they really want.

I don't think it would be fair to say Go doesn't target new users. It has grown in users at a very fast pace for ten years now :)
It is true that new users will tend to look at the standard library first, but ultimately they will follow the advice of the documentation they are reading. There are plenty of "blessed" modules outside of the standard library, such as x/crypto and x/net, and they don't need to be in the standard library either. If there was a module like x/guardrails or somesuch, I'm sure that pages like tour.golang.org could point to it or show examples with it.

The question of why should this be in the standard library seems really straightforward to me. A simpleinput package really only has value in the standard library. The point is to make learning Go easier, and as soon as modules are involved, it's not easier.

If I was learning a language, I would want to learn the "normal" or "proper" way to accomplish a task, not an oversimplified way that I should probably un-learn later.

In Python, practically all learning material uses print() and input(), neither of which did I ever use in my years of programming Python professionally. It's normal to have an inefficient "easy mode" for beginners. Learning styles vary and some people want to learn the "real" way to do things earlier and some people prefer to just get things working and fill in the details later. Neither is better than the other, but I think the latter style is more common.

If we are going to do this, I think we should be more idiomatic and have Read and friends return (string, error).

After reading this proposal I tried to think about some typical "getting started"-type programs that I might write when learning a new language. It's harder for me to relate to "learning to program" because it's been some time, but I also tried to remember some early programs I wrote.
Here's what came to my mind:

Number guessing game: generate random number, prompt for guesses, and print "guess higher", "guess lower", or "correct!" depending on the relationship between the guess and the goal number.
I distinctly remember writing a program like this in my early experiments with programming, based on an example in the Commodore 64 User Guide. This sort of prompt-and-response program seems well-suited to the API described here, if combined with the writing functions in fmt.

Advent of Code challenges: I have anecdotal evidence that some participants in Advent of Code intentionally choose a language they don't already know and use these challenges as a vehicle for learning.
Advent of Code challenges commonly involve loading in some data in a simple delimited text format, doing some computation based on that data, and printing a result. ReadLines from this proposal in particular seems like it would be useful in many of the Advent of Code challenges.

I don't really have a strong opinion about whether it's important to make these easy to achieve, but similar features do seem to help learners of Python as stated above, and Python is typically presented as an example of a good language for beginners. My examples above also lead me to think that the simpleinput API proposed here would be useful for the sorts of problems I can imagine beginners wanting to use to experiment.
I share Ian's sense that it would be better to make these functions follow typical Go error handling patterns, because that seems like an important part of Go's design that I'd want to learn quickly as a beginner, rather than deferring until later. I think a Read (string, error) does still address the stated problem with fmt.Scanf where beginners don't think to check the error, because they'll want to access the string result and therefore won't be able to avoid learning how to handle multiple return values, which will hopefully then encourage learning what to do with that error result. The pattern they'd learn doing that will then set them up for working with almost every fallible API in Go.


How to prevent back-link click event (implementing back confirmation)?

I need to implement a < Back click confirmation, but the event seems to be uninterruptible =
Tried every combination of @back-click.stop.prevent with capture, only prevent, etc.
My event is triggered, but the page still navigates back =\
Relevant code:
<f7-navbar back-link="Voltar" @back-click.stop.prevent="confirmSelectStore()">

Handler:
 methods:
        {
            confirmSelectStore()
            {
                alert(1);
            }
        }

f7-vue warps everything, so if you want to handle native event, you should not use f7-navbar, use original div instead.
template:
<f7-page>

Page Title

</f7-page>

script:
   methods: {
      		handle_back(e) {
      			console.log('doing something before back')
      			// doing something here
			//	this.$f7router.back()  // manually go back if you want
      		},
    }

A similar common mistake for F7-vue is, you're not allowed to use v-model to bind f7-input/f7-checkbox/f7-toggle.
Either listening to @input, or using native div wrap

Yeah, it is impossible. The workaround can be the following:
<template>
  ...
  <f7-navbar>
    <f7-nav-left>
      <f7-link @click="backConfirm">Back</f7-link>
    </f7-nav-left>
    <f7-nav-title></f7-nav-title>
  </f7-navbar>
  ...
</template>


New factory for the embedded ansible cloud credential

New factory for the embedded ansible cloud credential. This PR is part of the https://github.com/ManageIQ/manageiq-automation_engine/pull/303.

@mkanoor Please review. We need this for the import/export PR.


E-mail validity

Hi, there is a problem with email matching. In your validator is the correct e-mail this: "a@b". This can be seen even in the example in docs. Try it.

This comes up a lot. a@b is in fact a valid email address according to the W3C spec that defines what constitutes a valid email address. See #455, #272, #31 and others.


VSCode won't start on Ubuntu 14.04 "libxkbcommon.so.0: no version information available"

VS Code Version: 1.53.1
OS Version: Ubuntu 14.04 LTS

VSCode doesn't start on Ubuntu 14.04. Running code in the terminal returns : /usr/share/code/bin/../code: /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0: no version information available (required by /usr/share/code/bin/../code). Running code --verbose returns:
    /usr/share/code/bin/../code: /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0: no version information available (required by /usr/share/code/bin/../code)
    /usr/share/code/code: /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0: no version information available (required by /usr/share/code/code)
    /usr/share/code/code: /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0: no version information available (required by /usr/share/code/code)
    /usr/share/code/code: /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0: no version information available (required by /usr/share/code/code)
    Fontconfig warning: "/etc/fonts/fonts.conf", line 86: unknown element "blank"
    (electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
    /proc/self/exe: /usr/lib/x86_64-linux-gnu/libxkbcommon.so.0: no version information available (required by /proc/self/exe)
    [main 2021-02-10T20:33:58.858Z] Starting VS Code
    [main 2021-02-10T20:33:58.858Z] from: /usr/share/code/resources/app
    [main 2021-02-10T20:33:58.858Z] args: {
      _: [],
      diff: false,
      add: false,
      goto: false,
      'new-window': false,
      'reuse-window': false,
      wait: false,
      help: false,
      'list-extensions': false,
      'show-versions': false,
      version: false,
      verbose: true,
      status: false,
      'prof-startup': false,
      'prof-v8-extensions': false,
      'disable-extensions': false,
      'disable-gpu': false,
      telemetry: false,
      debugRenderer: false,
      logExtensionHostCommunication: false,
      'skip-release-notes': false,
      'disable-telemetry': false,
      'disable-updates': false,
      'disable-crash-reporter': false,
      'crash-reporter-id': 'fb6c53c2-864f-4aa4-a72a-d6661fdd5ef9',
      'skip-add-to-recently-opened': false,
      'unity-launch': false,
      'open-url': false,
      'file-write': false,
      'file-chmod': false,
      'driver-verbose': false,
      force: false,
      'do-not-sync': false,
      trace: false,
      'force-user-env': false,
      'force-disable-user-env': false,
      'open-devtools': false,
      __sandbox: false,
      'no-proxy-server': false,
      nolazy: false,
      'force-renderer-accessibility': false,
      'ignore-certificate-errors': false,
      'allow-insecure-localhost': false,
      logsPath: '/home/dcorbeil/.config/Code/logs/20210210T123358'
    }
    [main 2021-02-10T20:33:58.866Z] Resolving machine identifier...
    [main 2021-02-10T20:33:58.866Z] Resolved machine identifier: ae00e040eff80681886657f15d4fcd2ca67f17bbc716ecb5131a5cc6ce40ef41
    [main 2021-02-10T20:33:58.867Z] Main->SharedProcess#connect
    /usr/share/code/code --verbose --no-sandbox: relocation error: /usr/share/code/resources/app/node_modules.asar.unpacked/spdlog/build/Release/spdlog.node: symbol _ZNKSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE7compareEPKc, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference

Steps to Reproduce:

Run code in terminal
Observe the error message

I reverted to version 1.52 and as expected, no problem.

Does this issue occur when all extensions are disabled?: Yes

OS Version: Ubuntu 14.04 LTS

This Ubuntu version is too old, unfortunately, please update to at least 16.04. I believe that's the minimum we support.


Clickable Cards

Simply allows cards to be pressed with an onPressed VoidCallback. For compatibility it simply uses a GhostButton in the cards child. In the event that a card is clickable, it's padding is used in the ghost button and not the card, otherwise it functions as cards always have.

I Would use this!

While the idea is great, I think this should be done with another approach. I believe the card, being part of the layout component, should not be directly clickable. I have pushed several commits to implement this feature with another approach. Let me know what else is needed or if you think this pull request is still necessary. Next time please open an issue first so we can discuss the possible approach when adding new component capability.

Some designs with a grid of cards in some apps especially content management apps have loads of different data models that all need this kind of layout, making something clickable vs not means conditional builds, it's significantly easier to just add / nullify an onPressed property.
Only other alternative would be creating a CardButton widget, mirroring all of the card properties which it looks like you have, if you are maintaining that debt of keeping property parity between CardButton and Card then it's fine, but I'm mostly trying to reduce the amount of breaking changes I introduce to myself across all my projects, which is why I diddnt create my own CardButton widget and instead just opted to add the property to Card.
I use my fork of shadcn, not this one, this change has been in there for a while and I've found it really nice to add functionality to existing widgets so If you feel this isnt really a good fit, that's fine as I'm essentially rebasing your changes into my repo for anything that doesn't fit into shadcn_flutter nicely.
In my mind its just an optional field, while it doesn't "fit" in the layout/surface/control model, I'm more in the business of getting functional & reliable UI out the door without having juggle widgets on my clipboard, or refactor lots of files. I believe this change is a great example that.
TLDR: Would have to refactor files to use CardButton, If its no big deal to you, merging means less conflict resolution my fork has to do to stay updated, not merging is also fine because my products use my fork of shadcn_flutter and rebasing is always an option for me.

I'll just use the CardButton then


How can i add gradient in background color of navbar?

Version

react-native-router-flux v3.30.2
react-native v0.28.0

Check out the API docs here: https://github.com/aksonov/react-native-router-flux/blob/master/docs/API_CONFIGURATION.md#navigation-bar
You can pass in a navigationBarStyle - if that doesn't get it perfect, you can create your own NavBar by copying src/NavBar.js to your own file and using navBar={MyNavBarComponent}.

@cridenour thanks :+1:


Add "Refactor  [Ctrl+R]" entry to the "Find" menu

The new and very welcome addition of refactoring is not easily discoverable.
Please add a "Refactor" entry to Bracket editor menu, for example to the "Find" menu, below "Replace" or below "Replace in Files".

@jnareb Would you be interested in submitting a PR?

I use Brackets, I don't program it. I can try.

@jnareb No problem - I can add it. :)


chore: add biome configuration file to react and utils workspace

Running the command pnpm run lint after pnpm run prepack will fail as biome is not properly filtering the distribution folders from packages/utils and packages/react

adds biome configuration file to those packages (react, and utils) including their own specific ignore patterns adn extending the main configuration file

Thanks! Yeah I noticed that and wasn't sure how to fix (I thought it was fine in CI since the step runs after, but I guess release doesn't?)

I got a question though, is this adoption of biome a migration to stop using Eslint?! and if so, should we remove eslint configurations from the repo? also, why are you moving from Eslint?!

Yes, it formats and lints simultaneously and is faster/simple to use. It doesn't format CSS or MDX yet though, so I kept Prettier for those ones on the website. Forgot to remove the eslint config file and possibly some comments in certain places after I rebased with the new version I guess, although they don't harm anything I think...


feature(cbi-194-default-full-node-rpc): Add full node in left menu at first order for default

Block Viewer uses Full Node DNS as a default. Ticket url

Check the PR.


nodePackages.expo-cli: drop

expo-cli is deprecated upstream, see https://www.npmjs.com/package/expo-cli and https://blog.expo.dev/the-new-expo-cli-f4250d8e342.
part of #229475
closes #349434 as the package is being dropped
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[x] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[x] (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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This kinda slipped through the cracks for a bit. resolved the merge conflicts!


time counting start in first keydown

Problem:
When user focus on input, then press something non-characters (like backspace, Fn + somethings, home/end,...), time still counting

Fixed: https://github.com/monodyle/typings-app/commit/10f3846a9d4796a4b89565040bbb897fda73763b#diff-84099094c0c18f11b3c43fe0e8959b97R93


Spawning language server with cmd: lua-language-server failed. The language server is either not installed, missing from PATH, or not executable.

Hey @tjdevries, Thank for the Video: https://www.youtube.com/watch?v=stqUbv-5u2s
I get this error after removing my current ~/.config/nvim and replacing with the one in this repo!

You don't have any other configuration?

I'm also getting lua errors. I've tried deleting all the directories and starting over. Also upgraded all packages with brew
   90 ## The following errors have been detected:
   91   - ERROR: vim(highlights): ...im/0.8.1/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at position 2765 for language vim
   92     vim(highlights) is concatenated from the following files:
   93     | [ERROR]:"/Users/martinphee/.local/share/nvim/site/pack/packer/start/nvim-treesitter/queries/vim/highlights.scm", failed to load: ...im/0.8.1/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at               position 2765 for language vim

No I moved the whole /nvim dir to somewhere else before starting this. @tjdevries
This issue was happening in v8.1.0 and v8.0.0, I fixed it by installing v0.9.0-dev.

Hm, 0.9 fixed it for you?

yes

Can you try with latest version of how we're initializing and running the servers? should be better now.

Yes, thanks @tjdevries, the language server is fixed. But I still get this error in 0.8.1 version:

Have you run ":TSUpdate" in the old version?

I think "yes". I can't be sure thought, hard to remember as I tried everything!

Will close now cause I think all of this should be handled by Mason now.

The neovim is not finding the LSP in the neovim PATH because it has not yet been added to the neovim PATH. This task is handled by Mason. But if nvim-lspconfig tries to access the LSP server before the appropriate PATH gets added by Mason then we encounter the error:
Spawning language server with cmd: `lua-language-server` failed. The language server is either not installed, missing from PATH, or not executable.

The solution is given here:
https://github.com/williamboman/nvim-lsp-installer/discussions/509#discussioncomment-3337756
So you need to make sure that Mason gets loaded before nvim-lspconfig does, i.e. require("mason").setup() runs before require("nvim-lspconfig").setup()
If you are using Lazy.nvim then this solves the problem, adding mason as a dependency of nvim-lspconfig.
{
    "neovim/nvim-lspconfig",
    dependencies = {
        "williamboman/mason.nvim",
    },
}


Keep track of CWD in README

This is analogue to what was already done in the Build the containers section.

Thanks! That was a bit sloppy of me ☺


Remove govee.state entity

This entity was useless and without a unique_id we had no way to remove it from the autogen dashboard.

So, I just setup this integration and was wondering how I can remove thist entity from my dashboard.


nng_recvmsg: Object closed after 61000 messages

I'm doing a stress test with a pairv1 protocol and the socket is closing around 61000 messages with 1000 msg/second.
Even if i slow it down (500msg/sec), it drops the connection too around 61000 messages in the dialer side.
I've found a similar problem in the closed issues, but i'm following the right instructions and still having the problem.
The connection code:
  nng::socket sockx = nng::pair::v1::open();
  sock = std::make_shared<nng::socket>( sockx.release() );
  sock->dial(URL.c_str());

The rest, is just as it supose to be and i've create a repository with most part of the code:
https://github.com/amunhoz/nng_application
Another important thing, it is a node addon project.

Will make more tries... meanwhile i'll let this closed.


fix for the changes to now show tide info

simple fix to now show tide information since update

@scottie let me check and merge.
Thanks for Contributing.