Where are the cute yellow blobs?

This package is part of the noto project.  Visit
google.com/get/noto for more information.

Built on 2017-10-24 from the following noto repository:
-----
Repo: noto-emoji
Tag: v2017-09-13-design-refresh
Date: 2017-09-20 10:08:23 GMT
Commit: d5ac67b140cc63aa512bbb3d164e15737dd97564

Update color emoji font and assets for new design.

This design is the one used in Android O.

The blobs are dead.  Long live the blobs.

I had a feeling this day would come.
Please bring back the cute little yellow blobs.

Gone, but not forgotten.
It is possible to go back in git history and get the blob versions of the
images you want, then rebuild the color emoji font with a custom image set.
You'd still have to install the font on the devices you use, though. I
think on Android you have to root the device to install custom system fonts.
On Nov 18, 2017 6:42 PM, "Justine Tunney"<EMAIL_ADDRESS>wrote:

[image: emoji_u1f625]
https://user-images.githubusercontent.com/49262/32986849-b2ddaf16-cc8f-11e7-8878-0d4f4782007e.png
I had a feeling this day would come.
Please bring back the cute little yellow blobs.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlei18n/noto-emoji/issues/185, or mute the thread
https://github.com/notifications/unsubscribe-auth/AJepDLN5VYdtXUk5TUW0hkwuczot4Arxks5s35WvgaJpZM4QjOz4
.

That makes me sad, because those yellow blobs were the reason why I adopted Google Hangouts. So I hope Google reconsiders.
If not, then I'd at least like to have the choice to easily opt in to yellow blobs, on websites I operate.
I'm noticing that the only place where a yellow blob font file still seems to exist, is https://noto-website.storage.googleapis.com/pkgs/NotoColorEmoji-unhinted.zip. But this ttf file raises major errors when I try to load it on Mac OS. On Linux, it is greyscale. I've also been unsuccessful at getting it to work inside Chrome Mac, Firefox Linux, etc.
What I would like to see happen is a woff2 upload to GCS (and hopefully the other formats too, and ideally via Google Fonts) so I can do something like this:
@font-face {
  font-family: 'Yellow Blob Color Emoji';
  src: local('Yellow Blob Color Emoji'), url(https://fonts.gstatic.com/s/yellowblobcolor/v18/uYECMKoHcO9x1wdmbyHIm3-_kf6ByYO6CLYdB4HQE-Y.woff2) format('woff2');
  unicode-range: U+1F300-1F5FF, U+1F600-1F64F, U+1F680-1F6FF, U+1F910-1F9EF, U+2600-26FF;
}

Using color web fonts in browsers is still very complicated. OpenType has four different ways to store color glyphs (SVG, sbix, CBDT and COLR), each operating system supports only some of those (or none), and each web browser engine supports some or none, depending on the operating system it is running on.

Wow I didn't know showing color fonts in a browser would be that complicated.
Thankfully we have the Google Fonts service. @davelab6 @garretrieger @laerm0 I would like to see the priority of https://github.com/google/fonts/issues/1173 elevated so we can serve the cute yellow blobs.
This is the kind of problem Google Fonts was invented to solve. I'm sure you guys remember back in the day when no one could figure out how to serve the hodgepodge of EOT, TTF, OTF, WOFF, and WOFF2. Google Fonts was our savior. But as we converge on a future where everything supports WOFF2 I'm sure you're all hungry for a challenge.

I think WOFF and WOFF2 are mostly about how the font is packaged and delivered, but at a lower level it is still similar to ttf or otf "on the inside".
Wikipedia says:

WOFF is essentially OpenType or TrueType with compression and additional metadata.

Since the only standards for color fonts we have are baked into Opentype, and WOFF includes essentially Opentype fonts, WOFF/WOFF2 inherits the features and issues of Opentype wrt color emoji support.
tl;dr WOFF2 has Opentype in it, and as @twardoch mentioned, browsers and OSes are still working on color support in Opentype fonts.
I think many people are shocked by how hard color fonts are, myself included.
(That said, there is no technical barrier to packaging up a .ttf or .otf with the old blobby emoji, converting that to a .woff, and serving that, just that support on site visitors' machines will be hit and miss for now. Ubuntu should be fine by next April: [[Article]](http://www.omgubuntu.co.uk/2017/11/ubuntu-finally-long-last-time-support-color-emoji) I believe this font as a WOFF works in at least Edge and Firefox on Windows. Not sure about macOS/iOS or other browsers on Windows.)
["contributor" note: I am listed as "contributor" here, but my commits were a few minor fixes to some SVGs. I don't really develop for this repo, nor have any expert knowledge, I'm just somebody interested in browser support for color emojis.]

I think you can skip WOFF for color fonts and create a WOFF2 file directly as the browsers that supports color fonts also supports WOFF2.
And happy to now that color fonts are coming to Ubuntu next year! 🎉 We'll update the dedicated color website then!
@DeeDeeG Do you know which formats Ubuntu will support? (OpenType-SVG, sbix, COLR, CBDT? - only one or multiple?)

The difference between WOFF2, WOFF, EOT and TTF has been quite trivial, because those formats differ in compression only (it's really like the difference between .tar.gz, .zip and .rar).
After decompression, it's TTF or OTF in browser memory, and there, for monochrome fonts, all of us, including Google Fonts, can rely of 20+ years of experience with how OpenType work in apps and OSes.
Color fonts present a challenge. First, they're very new so there are still tons of users who don't have OSes capable of rendering them yet.
So what should Google Fonts serve as fallback? Monochrome fonts? (We're not just taking here about a particular flavor of emoji — color fonts can represent any text characters). Or maybe some complicated polyfills that replace color glyphs with bitmaps or SVGs? Are such polyfills available?
Since color font support is a moving target, the way they're served by Google Fonts would need to be updated often. At this point, having a viable infrastructure for serving color web fonts would be quite high maintenance. And there aren't yet to many opensource color fonts that users would be dying to see on their webpages. Doing it just for the blobs is tough to justify the effort.
There is also the actual problem of what the color fonts can be: the COLR flavor supports just plain vectors and simple fills, the SVG flavor is vector+bitmaps, with gradients, strokes etc. The CBDT and sbix flavors are PNGs packed inside a font. So not every flavor can render each artwork. The COLR flavor would work for your blob-style emoji but not for emojis in the style for iOS.
Then, there is the file size. The sbix flavor supported natively by iOS and the CBDT flavor with native support on recent Androids are both PNG-based inside.
The Apple Color Emoji font that ships with iOS is over 90 MB large! That's because the emoji are stored in several master sizes up to 1024px. When a website uses only a few emoji, it would be stupid to serve a 90MB WOFF2 just so the user can see the blobs. So these fonts would need to be smaller. But how small? What px size should Google Fonts choose as master sizes — and how soon would they have too remake those to include bigger sizes?
Of course I would love to see color fonts on the web sooner. I was involved in developing the SVG extensions of OpenType and have written about the topic over four years ago: https://blog.fontlab.com/font-tech/color-fonts/color-font-format-proposals/
Since that blog entry, things have evolved a bit, and all four flavors are part of the standard. But their platform support is spotty, in some flavors the fonts can be large, and designers haven't — in those four years — quite brought the flurry of interesting designs (though it is a bit of the chicken and egg problem).
So, I'm only very cautiously optimistic :)

And, as the excellent https://www.colorfonts.wtf/ website points out, Chrome currently doesn't support any color font flavor, really.
I think we ought to concentrate on lobbying browser vendors to support OpenType+SVG based WOFF2 (since all browsers have an SVG renderer already, right? :) ). We can forget about the other flavors for the purpose of the web, I think. Even OT+SVG can support PNG bitmaps after all.

On Mon, Nov 20, 2017 at 1:45 AM, Adam Twardoch<EMAIL_ADDRESS>wrote:

And, as the excellent https://www.colorfonts.wtf/ website points out,
Chrome currently doesn't support any color font flavor, really.

I expect @jungshik would have somewhat more complete information on this.

Since browser infrastructure has not yet matured to the point where we can choose yellow blobs, would it be possible for Google to temporarily rollback the yellow blob turndown? Then, once we have the ability to choose, I would not object to Google moving forward with its intentions to have Android & Hangouts emoji look like all the other emojis.

Hi, thanks for including me on this, but the Google Fonts team has no input on this matter. While I'm with you on loving the blobs, this decision is far above my pay grade and @twardoch is very correct on the technical issues of serving color web fonts.

[Sorry all for being a bit off-topic, I wanted to address @Jolg42's question. I'll try to keep this contained to one comment.]
@Jolg42

@DeeDeeG Do you know which formats Ubuntu will support? (OpenType-SVG, sbix, COLR, CBDT? - only one or multiple?)

I would love to say, because this is indeed exciting and interesting for us color font (emoji) lovers and Ubuntu fans. But I am just a regular user of Ubuntu, not a developer there, so I don't have the answer.
I would suggest this: give the daily images of Ubuntu 18.04 a spin (maybe now and in a month or two from now), and try to load several formats of color fonts in various browsers. Here's where to get all four formats:
sbix: copy AppleColorEmoji from a Mac you own
COLR/CPAL: Copy Segoe UI Emoji from a Windows computer you own
SVGinOT: Twemoji color font or similar by @eosrei, various from colorfonts.wtf
CBDT/CBLC: Noto Color Emoji from this repo, the get noto website or the Android source tree.
A few things to test:

Can color fonts be installed? (hasn't been a problem so far)
Can color fonts be rendered in-browser as a locally installed [system] font? Through @font-face?
Can other apps (e.g. LibreOffice, Gedit) render color fonts? Do color emoji show up in app titlebars? (Do they show up, but in grayscale?)
[Arguably not a bug, unclear whether this will be addressed:] Are monochrome fonts such as Symbola and DejaVu Sans/Serif loading before color emoji, so that there is a mix of black/white emoji and color emoji, from different fonts, or does just the color emoji show.
For the above tests: Which formats work, which formats have issues?

(Again, I don't know the answer, but it's easy to infer CBDT/CBLC i.e. Noto Emoji will be supported, due to @behdad's work on cairo being completed and upstreamed recently as a group effort by a few people. That's the only technical advancement I had heard of tbh, but it's well possible those patches included support for other formats, or that other work has been done and I hadn't heard of it. -- Hands-on testing, or asking the ubuntu maintainers, are the only true ways to know, though.)

On Mon, Nov 20, 2017 at 1:45 AM, Adam Twardoch @.***> wrote:
And, as the excellent https://www.colorfonts.wtf/ website points out,
Chrome currently doesn't support any color font flavor, really.

> I expect @jungshik would have somewhat more complete information on this.
I'm at loss what @twardoch  meant.   The table in the cited web page is completely off. Only on Android ? It must be kidding.
Chrome on Android/Linux/Chrome OS support CBDT/CBLT color font (web and local fonts) as well as sbix color font (local font) [1]
Chrome on Windows 10 (if not 8) supports COLR format
Chrome on macOS supports sbix format. (local [1] )
Anyway, there's a WiP to make CBDT/CBLT and sbix supported across platforms using FreeType (see
https://chromium-review.googlesource.com/c/chromium/src/+/706248 ). With that submitted, at least two color formats will be supported on all platforms by Chrome.
[1] I have a fix to make sbix web font work as well, but haven't submitted it because I failed to make a test sbix font to use in layout test ( https://bugs.chromium.org/p/chromium/issues/detail?id=605334 ).  Or, maybe I did make a test sbix font, but simply forgot to land the CL.

@jungshik can I assign this to you so you can update it when Chrome's status changes?  Or perhaps we should close this and add a more specific bug and reference this?

@jart you could try this one:
NotoColorEmoji.zip
it worked for me ;)

+1 Bring back the old emojies!!!

+1 on the new emojis are bland and poorly executed, the old ones were individually good enough to put on t-shirts.

Case in point, I have a t-shirt with this one on it, and I would love to see hangouts/android go back to the set which contained it. It's a mistake to mess with such success.

is weird that i have android 7.1.1, and in notifications i still see the blobs

The blobs weren't changed to the circular emoji until 8.0 @asturur

oh so i m not updating  :)
But new emoji were not added right? There are no emoji in blob version for latest unicode versions.

Android decided years ago to change the emoji style, and there have been no updates to the blobs since.  That horse is out of the barn.  The images we maintain support Android's requirements, so we won't take changes that revert them to the blob style, and there is no funding to create new images in that style.  Currently the repo is not structured to support multiple stylistic variants of the emoji, though it's relatively straightforward to build a font with whatever images you want as long as they are the expected format and size.

The blobs might not have a future as Google's flagship emoji, but they could have a new home with the community if you start a GitHub repo for them. For example, MS-DOS was recently immortalized on GitHub by Microsoft. Could we do that?

Could we do that?

Yes, as long as you follow the license, you are free to modify and distribute this project or older versions. But it's a lot of work to update the font for the new Unicode versions every year.
Here's one project that is trying to maintain the older emoji style:
https://github.com/C1710/blobmoji

I love the blobs but this repo will continue to track Google's latest emoji.


Skip checking subscription if freePlanFlag is enabled

Summary
Fix https://github.com/giselles-ai/giselle/pull/126 logic bug.
I've deleted !isEmailFromRoute06 condition unintentionally.


[Bug]: When autocomplete wtih a password manager the password while deleteting a resource it close the modal

Error Message and Logs
No error log
Steps to Reproduce

Use a password manager (for my personal usage it is bitwarden)
create a resource
try to delete it and the moment you need to fill the password use your password manager to autocomplete

Example Repository URL
No response
Coolify Version
v4.0.0-beta.347
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 22.04
Additional Information
It is a minor issue but would enjoy to try to fix it

Added autocomplet='off' to all inputs where it does not makes sense. Releasing the fix in the next version.

This issue remains in version v4.0.0-beta.349:
Demo:
https://github.com/user-attachments/assets/0b087f4b-e38e-423e-af44-9723c0b95537
The moment you select the correct credentials to be filled, the modal window gets dismissed and the action you were trying to do (in this case deleting a resource) cancelled.
Steps to Reproduce
1- Use a password manager
2- create a resource
3- try to delete it and the moment you need to fill the password use your password manager to autocomplete
Example Repository URL
No response
Coolify Version
v4.0.0-beta.349
Are you using Coolify Cloud?
Yes


VSCode truncating Jupyter output

[(https://github.com/microsoft/vscode-python/issues/9401)]

Bug: Notebook Editor, Interactive Window, Editor cells
Steps to cause the bug to occur
Python
VSCode jupyter lab notebook  gives the Truncate Output warning even after changing the settings. I am not sure whether output is actually being truncated
The notebook at one time output a voluminous amount of data, however I changed the script so it printed to file instead; changed the text output limit to 0;  stopped kernel and cleared output several times; tried copying notebook under a new name
Environment

Jupyter server running: Local

Python Extension : 2020.5.80290

VS Code version: 1.45.1

**Python  3.7.6, Anacdonda Extension Pack 1.0.1

OS: WSL Ubuntu 18.04 2

Virtual environment: conda

------------------------------------------------------------------------------------------------->
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

Dupe of #11777


[Feature Request] Enable Image Deletion in Inspection Mode via "Delete" Key

Hi, I would like to request a new feature for the inspection mode. It would be incredibly convenient to have the option to delete the currently viewed image by simply pressing the "Delete" key on the keyboard.
Additionally, it would be helpful to include a "Delete" option in the menu near the existing "Copy prompt" button.

What is Inspection Mode?

What is Inspection Mode?

I would like to clarify my previous feature request since there seems to have been some misunderstanding.
By "Inspection Mode," I mean the fullscreen image viewer that allows you to browse images in detail. In this mode, it would be very convenient to have the ability to delete the currently viewed image by pressing the "Delete" key on the keyboard.
Additionally, it would be great to have a "Delete" option in the dropdown menu that appears near the "Copy Prompt" button in this same viewing mode.
This feature would streamline the workflow significantly by allowing users to quickly manage their images without leaving fullscreen mode.

Yes, that's right. But I can't figure out how to open it with the settings tab. I'm using
version: v1.10.1
sd-webui-infinite-image-browsing | https://github.com/zanllp/sd-webui-infinite-image-browsing.git | main | 1a0f0712 | 2024-11-24 18:07:18 | unknown

，
and then  scroll into bottom

Thanks


Incompatible with excavated variants

https://pastebin.com/J9TbqgLr
@lukebemish @LordDeatHunter

Alright, looks like something messes with the registry in an unexpected fashion. I don't think this is on my side, but if it is feel free to give me another ping or open an issue on EV.

This issue is not on your side. This is likely an issue where our DefaultedRegistryMixin is loading Alloy Forgery way too early, causing an class inheritance error down the lane. We are planning a fix which should mitigate this issue.

As Sunconure11 mentioned in https://github.com/Safrodev/Archon/issues/4, the issue is related to More Bundles.
The root of the issue is that they are accidentally sealing the EnchantmentTarget class using a Mixin plugin, see https://github.com/BelgianSalamander/MoreBundles/issues/12 for more details on this.
Once this has been resolved this issue will be closed.

Closing this as it was fixed in More Bundles 0.2.1


More flexible paths for saving tensorboard data

🚀 Feature

I'd like more flexibility in the directory hierarchy used for writing tensorboard data.
Specifically, I want to make the experiment-name directory optional, removing one level in the hierarchy.
Also I'd like to be able to specify the name of the version directory.  Currently it is "version_N" but if the constructor version parameter is a string, I think it could just directly use that.
Motivation
You could specify the version on the command line or generate it from the current datetime, which I find more meaningful than "version_73".  Likewise if the tensorboard data is not going to be preserved, it's much more readable in the tensorboard gui to skip the experiment name.
Pitch
I have a branch with working code + tests
https://github.com/bobkemp/pytorch-lightning/tree/tensorboard-path-generalisation
Alternatives
None
Additional context

@bobkemp could you post examples and use cases of what you mean? also, you can submit a PR to make the changes easier to see.

Here's the directory layout you could have and how it appears in TensorBoard.
I think the change also cleans up the code a little, removing duplication.

Without experiments directory:
TensorBoardLogger(tensorboard_dir, name="")
checkpoints/version_0
checkpoints/version_0/events.out.tfevents.1581113035.glia.8401.0
checkpoints/version_0/meta_tags.csv
Without experiments directory and with explicitly named version directory:
TensorBoardLogger(tensorboard_dir, name="", version="2020-02-07-220525")
checkpoints/2020-02-07-220525
checkpoints/2020-02-07-220525/events.out.tfevents.1581113127.glia.8438.0
checkpoints/2020-02-07-220525/meta_tags.csv
Current code:
TensorBoardLogger(tensorboard_dir)
checkpoints/default
checkpoints/default/version_0
checkpoints/default/version_0/events.out.tfevents.1581112657.glia.8299.0
checkpoints/default/version_0/meta_tags.csv
checkpoints/default/version_1
checkpoints/default/version_1/events.out.tfevents.1581112777.glia.8341.0
checkpoints/default/version_1/meta_tags.csv

PR 804


As a designer, I want to easily know the stylable parts of any given element in the app I’m building

Currently, I have to browse the individual element API docs to learn about the stylable parts and the different states they can have.
This approach is cumbersome, as I don’t necessarily know which element’s documentation I need to look at (because of inheritance and composition) and because the API docs are just text without any illustrations what the parts correspond to visually.
Alternatively, I can use the browser inspector to search for all part attributes and look for the nearest shadow root to see which custom element I should target.
This approach is cumbersome because the DOM can be quite complex and it’s hard to spot the part attributes from all of the surrounding markup. Also, I’m not sure which other attributes are part of the public styling API.

What I might want to do instead, is activate some sort of developer tool and point it to any visible part of the app, and the tool would tell me the correct part name and the custom element it is contained in.

I'm going to address this partially in the api-viewer, see https://github.com/web-padawan/api-viewer-element/issues/42


add Policy re. unstable tests to README

@awasum OK for you?
@nikpawar89 makes sense?
@xurror @maektwain @fynmanoj @thesmallstar @DBryzz @wkk91193 @nemux @nnatarajan FYI!

The latest "force push" just now just added @Ignore // TODO FINERACT-123 and Of course, we very much appreciate you then jumping onto any such bugs and helping us figure out how to fix all ignored tests!.

Why is the other Travis PR test failing?
I see this:
    java.lang.AssertionError at AccountingScenarioIntegrationTest.java:588```

Is this a flaky test? Something must be broken somewhere.

I suggest that instead of having all this details stated out in one big paragraph, wouldn't it be better if the instructions were listed out in points form?. Reading a huge paragraph is kind of tedious and difficult to track. I have no problem with it though. Just think it would look better that way

That is an excellent point, you are absolutely right, it was a bit "dense"... how about how it's now - better?

I suggest that instead of having all this details stated out in one big paragraph, wouldn't it be better if the instructions were listed out in points form?. Reading a huge paragraph is kind of tedious and difficult to track. I have no problem with it though. Just think it would look better that way

That is an excellent point, you are absolutely right, it was a bit "dense"... how about how it's now - better?

Yeah, definitely. That looks more like it.

+1 from me.

I've exceptionally self merged this README only change PR based on the 2 votes of support expressed by @xurror and @nikpawar, because I have too much gray hear to re-re-base it following the successful build and merge of #785 and then wait for it to build and turn green...


Fail to Run Meshcat Example

Hello,
Thanks for maintaining this nice repo.
I just installed the package using conda, and trying to run some examples.
Especially, I am running two examples meshcat-viewer-dae.py and python meshcat-viewer.py, but getting the warning below and the empty scene on the web.
/opt/anaconda3/lib/python3.8/runpy.py:127: RuntimeWarning: 'meshcat.servers.zmqserver' found in sys.modules after import of package 'meshcat.servers', but prior to execution of 'meshcat.servers.zmqserver'; this may result in unpredictable behaviour
  warn(RuntimeWarning(msg))
You can open the visualizer by visiting the following URL:
http://<IP_ADDRESS>:7000/static/

Am I missing any procedure to run the example?

How did you install meshcat?

How did you install meshcat?

Yes I installed it by following pip install meschat.

Yes I installed it by following pip install meschat.

You need to run it in an interactive manner, with:
python meshcat-viewer.py

You need to run it in an interactive manner, with:
python meshcat-viewer.py

It works!
I really appreciate your help.

It works!
I really appreciate your help.


Add functionality for calculating CAAQS SO2 metric value

Functionality for calculating the SO2 metric should follow the methodologies, procedures, and requirements in the Guidance on Application of Provincial Interim Air Quality Objectives for NO2 and SO2.


having a problem without knowing how to fix this.

Hi. I am currently trying to use your imagePicker in my own project, but I get this error even in my test that I created with your code. Do you have any idea?

I have a problem in installing via cocoapods.
fingents-Mac-mini-3:HoneyBadger fingent$ pod install
Updating local specs repositories
CocoaPods 0.39.0.beta.4 is available.
To update use: gem install cocoapods --pre
[!] This is a test version we'd love you to try.
For more information see http://blog.cocoapods.org
and the CHANGELOG for this version http://git.io/BaH8pQ.
Analyzing dependencies
[!] Unable to satisfy the following requirements:

RMImagePicker (~> 0.1.4) required by Podfile

Here is the podfile. Appreciate your help.
Uncomment this line to define a global platform for your project
platform :ios, '6.0'
target 'HoneyBadger' do
pod "RMImagePicker","~> 0.1.4"
end
target 'HoneyBadgerTests' do
end


Use object-assign

A much nicer way to define options.

Rather keep dependencies to a minimum.

If we were to add dependencies for something like this it would be babel instead and use destructuring.

If we were to add dependencies for something like this it would be babel instead and use destructuring.

Why is including Babel (and thus introducing a need for a compile step before publishing) better than simply doing the "node way" using a module?

I did not say better. I said that's what we would do. Just a preference.


Should config FW_PACKAGE_REPLACES translate to RPM's obsoletes?

Framewerk supports a FW_PACKAGE_REPLACES variable that corresponds to the .deb format's "Replaces" field. Perhaps for .rpm this should correspond to the "obsoletes" field.

Yeah, it probably should.  Any idea where it goes now?  May not go anywhere, but I swear I've used it.

This was done in PR https://github.com/dukesoferl/fw/pull/16


Add ids to delete-warning-page redirects

JIRA link
https://companieshouse.atlassian.net/browse/ROE-2395
Change description
Update the warning redirect urls to contain the ids as from the beneficial owner statements page.
Work checklist

[x] Tests added where applicable
[ ] UI changes meet accessibility criteria

Merge instructions
We are committed to keeping commit history clean, consistent and linear.  A BREAKING CHANGE can be part of commits of any type,
types other than fix: and feat: are allowed, for example build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others,
footers other than BREAKING CHANGE: <description> may be provided.

We normally add the JIRA ticket id to the GitHub PR Title too. @dlloyd1-ch .

Have managed to test locally using 'Save and Resume' to get to the BO delete warning page.


ARROW-3381: [C++] Add bz2 codec

AppVeyor build here: https://ci.appveyor.com/project/pitrou/arrow/builds/19685443

The R build failure is unrelated (see ARROW-3593).

AppVeyor build: https://ci.appveyor.com/project/pitrou/arrow/builds/19748138

R failure is unrelated. Will merge.


Make JSON field selectors configurable

This adds a new --selector=<field>[:<prefix>] option to the JSON import. The field contains the event name, which when prefixed with the optional prefix is used for selecting the event type.
This previously existed as a hard-coded option for the Zeek Stremaing JSON and Suricata Eve JSON readers, which still exist unchanged.
The following commands are now equivalent:
# Import Suricata Eve JSON
vast import suricata
vast import json --selector=event_type:suricata

# Import Zeek Streaming JSON
vast import zeek-json
vast import json --selector=_path:zeek

:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/vast, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
File-by-file. I left some notes as review comments that are helpful to look at.
Note that this is based on #1888 to avoid merge conflicts.

How could I interpret this with the upcoming schema module changes? Would prefix just be the module?

How could I interpret this with the upcoming schema module changes? Would prefix just be the module?

Yes, exactly.


Extra generations even if all field names are in the completion

Testing with Llama-3 70B, was seeing duplicate generations.
I traced it to this code in predict.py:
        for completion in completions:
            if all((completion.get(key, "") != "") for key in field_names):
                finished_completions.append(completion)
                continue
            finished_completions.append(
                extend_generation(completion, field_names, stage, max_depth, original_example),
            )

Not exactly sure why the "if" check fails incorrectly.
I fixed it by doing this:
        for completion in completions:
            extend_gen = False
            for key in field_names:
                if key not in completion:
                    extend_gen = True
                    break

            if extend_gen:
                finished_completions.append(
                    extend_generation(completion, field_names, stage, max_depth, original_example),
                )
            else:
                finished_completions.append(completion)

So the change is sometimes you want a filed in the completion without any content?

So... the correct fix looks like below:
        for completion in completions:
            if all((completion.get(key, "") != "") for key in field_names if key not in example):
                finished_completions.append(completion)
                continue
            finished_completions.append(
                extend_generation(completion, field_names, stage, max_depth, original_example),
            )

do you want the model to fill hint?

@mikeedjones No. Its an input field that can be empty

My proposed fix above is not enough. When there is a legitimate extend generations scenario but there is an empty input field, the code still gets into a loop and ends with "Max depth exceeded - failed to complete in one pass - increase max_tokens".
The function "get_all_fields_following_missing_field" should really be implemented as "get_all_output_fields_following_missing_output_field".
How to distinguish input vs output fields given an instance of the Example class?? Seems to me you need to pass the Signature instance as an argument all the way down
The work-around for now is to never leave an input field empty.


Unable to reproduce correct results from demo.ipynb

Hello,
I am trying to learn the method described in the demo.ipynb file, but I am encountering difficulties in reproducing the correct results. Despite following the instructions provided, the outcomes differ from what is expected.
Could someone please offer some guidance or suggestions on how to resolve this issue? Any help would be greatly appreciated.
Thank you!

Do the exact examples from the demo notebook work for you?
Some time ago I did another example on applying the demo notebook to some images. Could you try if that runs as is as well?

Thank you very much for your response. I have been able to run the example successfully.


fix(element-templates-modal): get local and global element templates

Which issue does this PR address?
Closes https://github.com/camunda/camunda-modeler/issues/2012
Acceptance Criteria

[ ] Corresponds to the concept
[ ] Corresponds to the design

Definition of Done

[ ] corresponds to the design principles
[ ] corresponds to the code standards
[ ] passes Continuous Integration checks
[ ] available as feature branch on GitHub

[ ] contains the cleaned up commit history
[ ] commit messages satisfy our commit message guidelines
[ ] a single commit closes the issue via Closes #issuenr

Can you elaborate how this fixes the problem at hand? How is that change in the plug-in API required for element templates to work?

Could you also update the commit to reference the correct issue (#2012)?

@nikku The reason local element templates weren't shown anymore is that config.get('bpmn.elementTemplates') is missing a second parameter which is the active tab. App#getConfig was introduced for that reason. When calling getConfig the caller doesn't have to know about the active tab. BpmnEditor uses getConfig, too, for that reason. Another fix would be to get hold of the active tab and to call Config#get with it.

Makes perfect sense. Thanks for taking the time to elaborate.
You could put that into the commit as a two liner description, too.


FEAT: Add new skin button variations

Add new bodyState and variants for buttons

expand bodyState
form variant
borderless attribute

Let's make a list of what's left to be done?

bodyState: reset, none


Xcode beta 6

My teammate tells me there are beta 6 issues. I'll look at them unless you folks are already working on them. Any news? Thank you.

Can you elaborate on the Beta 6 issues? We’re using beta 6 as well and have not seen any issues so far.

Thanks, I have looked and I think this might be the only one, pretty straightforward fix:


UISINVCOMP-35 Apply ignoreDatesOrder prop to Date Range filter.

Description
Apply ignoreDatesOrder prop to Date Range filter.
Screenshots
https://github.com/user-attachments/assets/af5473b5-ebe9-4d32-9ed0-89c1a8ff9b14
Issues
UISINVCOMP-35
Related PRs
https://github.com/folio-org/stripes-smart-components/pull/1530

Once the user selects “Apply”, show red error message below the To date that says, Start date is greater than end date

Aren't date filters working as expected?


Could not resolve dependency: npm ERR! peer svelte@">= 3.31.0 < 5.0" from<EMAIL_ADDRESS>

When running npm update while using Svelte 5 I get the following error:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/svelte
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer svelte@">= 3.31.0 < 5.0" from<EMAIL_ADDRESS>npm ERR! node_modules/svelte-flatpickr
npm ERR<EMAIL_ADDRESS>from the root project

Did you get around this? Would really like to use this in Svelte 5.

You can always go npm update --force or npm i svelte-flatpickr --force, but unless there is going to be ongoing support for this package I don't recommend using it.


Add doc for deploy to azure from acr, #60.

Signed-off-by: Pan Li<EMAIL_ADDRESS>

For layout review https://github.com/yaweiw/azure-spring-cloud-playground/blob/029d8a397171fb2369dbe6cb90c51630cbc9664c/DEPLOY_TO_AZURE.adoc


Unable to find a specification for KontaktSDK-OLD depended upon by BeaconCtrl

After a pod install i had the following: Unable to find a specification for KontaktSDK-OLD depended upon by BeaconCtrl
I think that Kontakt updated their sdk and their pod

Hi,
Thank you for your interest in Beacon Control, and for reporting this issue to us. We’ve already addressed this problem once with Kontakt, and they fixed it by creating the “-OLD” pod. Now it seems they’ve upgraded it. We think this might be a mistake on their side, we’ll look into it and let you know.

On 26 Apr 2016, at 12:40, Jean-philippe Arnaudin<EMAIL_ADDRESS>wrote:
After a pod install i had the following: Unable to find a specification for KontaktSDK-OLD depended upon by BeaconCtrl
I think that Kontakt updated their sdk and their pod
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub https://github.com/upnext/BeaconControl_iOS_SDK/issues/2

Hi,
Thank you for your answer i disabled the Kontakt.io part for the moment. And it should work till Kontakt did their update.
Have a nice day.
Ps: It is a nice open source project :)

Any news on this?

I have solved it by using this workaround from this answer
Add the following to the end of the podfile
pre_install do |installer|
# workaround for #3289
Pod::Installer::Xcode::TargetValidator.send(:define_method, :verify_no_static_framework_transitive_dependencies) {}
end


feat: update OCIMachineTemplate webhook validations

What this PR does / why we need it:
Adding more validation to the OCIMachineTemplate webhook
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #71

unit
?       github.com/oracle/cluster-api-provider-oci      [no test files]
ok      github.com/oracle/cluster-api-provider-oci/api/v1beta1  0.284s  coverage: 8.3% of statements
?       github.com/oracle/cluster-api-provider-oci/cloud/config [no test files]
ok      github.com/oracle/cluster-api-provider-oci/cloud/ociutil        0.610s  coverage: 30.3% of statements
ok      github.com/oracle/cluster-api-provider-oci/cloud/scope  176.358s        coverage: 81.9% of statements
?       github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks    [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/compute       [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/identity      [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity        [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer   [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/vcn   [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn  [no test files]
ok      github.com/oracle/cluster-api-provider-oci/controllers  26.349s coverage: 70.7% of statements

e2e

after updates
unit
?       github.com/oracle/cluster-api-provider-oci      [no test files]
ok      github.com/oracle/cluster-api-provider-oci/api/v1beta1  0.270s  coverage: 9.1% of statements
?       github.com/oracle/cluster-api-provider-oci/cloud/config [no test files]
ok      github.com/oracle/cluster-api-provider-oci/cloud/ociutil        0.461s  coverage: 30.3% of statements
ok      github.com/oracle/cluster-api-provider-oci/cloud/scope  176.079s        coverage: 81.9% of statements
?       github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks    [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/compute       [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/identity      [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity        [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer   [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/vcn   [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn  [no test files]
ok      github.com/oracle/cluster-api-provider-oci/controllers  26.317s coverage: 71.0% of statements

e2e
Ran 5 of 21 Specs in 1881.020 seconds
SUCCESS! -- 5 Passed | 0 Failed | 0 Pending | 16 Skipped


Add ui for SearchStopRow

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#135
#134  👈
#133
main

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

Join @ksharma-xyz and the rest of your teammates on  Graphite


chore(deps): Update Zeebe deps to 1.0.0

I have updated Zeebe deps to 1.0.0. It breaks backward compatibility.

@aivinog1 thank you for contributing :cake:
I'll enable the build pipeline first and have a look at your changes afterward :rocket:

@saig0 Hey, I've rebaised and squashed, can you check this out? :)


Export database content

Export database content: for the time being, we are going to have the run.py script output a CSV file that contains:
Bibcode where the feature was found (e.g. 2000M&PS...35.1043T)
Target (e.g. Moon)
Feature type (e.g. Oceanus)
Feature name (Oceanus Procellarum)
Feature id (4395) - this is found in the source data from the gazeteer and is used to create the link to the online page for it (https://planetarynames.wr.usgs.gov/Feature/4395)
As specified in https://docs.google.com/document/d/11TvdloUDrbTXS7YbPg-8YKEzYUeiMv5Xu8esszt1jI8/edit?usp=sharing by Alberto

Last year the count of feature name appearing in all the papers for a specific feature name/feature type/target was included as well. Should it be there, or should I remove it?
@aaccomazzi

If I understand this question correctly, the count is superfluous because one can get it by simply counting the number of instances a particular feature appears in the CSV file (which is the number of articles where feature X appears). Am I getting this right?
A more interesting metric would be the number of times the feature appears within a given paper. With this number we could compute, if we wanted, TF/IDF for each feature in each paper, which may be a useful metric for retrieval further down the line. Is this something you can easily generate?

So instead of summing all the instances per feature name and report it, you want to see them individually, you can sum them later if you want? OK.


Adding two robotics laboratories (DEE - UFMG)

Hi!, just adding two robotics laboratories (DEE - UFMG).
Regards,

I've just accepted the PR but I have a question: are there more labs in the MACRO group? I mean, is CORO part of MACRO. If not, I think it is better to separate them into two items of the same level

@h3ct0r I've just accepted the PR but I have a question: are there more labs in the MACRO group? Is CORO part of MACRO? If not, I think it is better to separate them into two items of the same level.

@mateus-amarante Yes, CORO is part of MACRO. They are other labs too, but I'm only related to CORO. When I get the complete list of MACRO related labs, I will send another PR with the updates!


[BUG] 404 on Chrome, but not Firefox or Edge

Environment
Self-Hosted (Docker)
System
Chrome 104.0.5112.102
Version
Dashy V-2.1.1
Describe the problem
When loading dashy I get this error in browser console:
Refused to apply style from 'https://dash.myhm.space/css/chunk-vendors.d8067ad8.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
which is then followed by a bunch of 404's for several other chunk-vendors file
this issue only occurs on Chrome, as I can load the site no problem on Firefox and Edged
attached are the logs from dashy
_my-dashboard_logs.txt
s
Additional info
No response
Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

Try clearing the cache

I have tried clearing cache already, as well as rebuilding the container for Dashy

after a few hours it just randomly started working again, so idk what happened.


Look into if we should let PBR handle sphinx

https://docs.openstack.org/pbr/3.0.0/#sphinx-autodoc

Snippet has been added to config. Unclear if it's doing anything


Fix/xss vuejs

fix #10

I did not succeed to fix with Trumbowyg but it's in the admin part :/
Anyway if you have a solution, please do not hesitate to submit it.
Thanks you @x1mdev

Looking good @guillaumebriday , I'll get back to you soon

Hey !
Look what @taylorotwell posted today https://medium.com/@taylorotwell/js-frameworks-server-side-rendering-and-xss-722805009892
👍

I just saw it, I kinda triggered taylor there. Made a blog/Twitter post about it after reporting a PoC to him via email
With kind regards,
Martijn Baalman | X1M IT Security
https://www.x1m.nl
Sent from iPhone.

From: Guillaume Briday<EMAIL_ADDRESS>Sent: Wednesday, March 7, 2018 5:04:27 PM
To: guillaumebriday/laravel-blog
Cc: x1m; Mention
Subject: Re: [guillaumebriday/laravel-blog] Fix/xss vuejs (#12)
Hey !
Look what @taylorotwellhttps://github.com/taylorotwell posted today https://medium.com/@taylorotwell/js-frameworks-server-side-rendering-and-xss-722805009892
👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/guillaumebriday/laravel-blog/pull/12#issuecomment-371187703, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVdwOZIvRkKLnj_V-FmS4PeprRaxDY0yks5tcAUJgaJpZM4ST9OW.


Open Issue on alert

Just like the comment on alert feature, it would be nice if the action could open a new issue on alert and/or with the results. This way, the action does not have to be linked to a PR, for example if we want to have a scheduled benchmarking run on a certain branch.
This would go hand in hand with  #154 (Output a Markdown result directly for custom integration), as there could be one common representation of the result that could be used in the comment, job summary, new issue, or direct for custom integration.

Hi @jbmichel14
Thank you for creating this issue. Implementing #154 would allow us to easily integrate the creation of an issue on alert as a separate step. That could be the first step to enable this functionality.
What would be the use case for this option though? How would you imagine this creation of an issue work? Just add a configuration option similar to comment-on-alert and let the user of the action figure out when to enable it?

Thanks for your answer. The use case is keeping track of the performance on every new merge into the main branch, and have the result displayed in a new issue (in case of alert). This way, the action doesn't have to be linked to a PR. And yes, I imagine the creation of the issue to be similar as comment-on-alert.


DateTimer - format DATETIME to d.m.Y dont work

Describe the bug
I have a DATETIME column in the database and am trying to display it using the DateTimer form object. I want to display the date as d.m.Y. That does not work.
Y-m-d, on the other hand, works.
Value in the database
1996-03-11 00:00:00
DateTimer::make('foo.date_time')
                    ->title('foo)
                    ->enableTime(false)
                    ->format('d.m.Y)
                    ->allowInput(),

Screenshots

Ah, thanks. I missed that.


fix: remove the .dockerignore to avoid problems with COPY inside Dockerfile

Signed-off-by: Harikrishnan Balagopal<EMAIL_ADDRESS>

Don't we need the src.zip


Too out-of-date to be of any use whatsoever

This article is so out-of-date that very, very little of what is pictured and described matches what the user sees, rendering this article completely useless.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 1da38d28-fbc3-b3a8-c3d8-c7cd7d2ce39b
Version Independent ID: e1f69e15-9955-22c2-3364-4ebd6f2b30f6
Content: Show, sort, and filter data in a canvas app gallery - Power Apps
Content Source: powerapps-docs/maker/canvas-apps/show-images-text-gallery-sort-filter.md
Service: powerapps
Sub-service: canvas-maker
GitHub Login: @lancedMicrosoft
Microsoft Alias: lanced

Thanks for your comment, @duncfair. This issue has been assigned to the doc author for review.


Private Code Hosts - initial part

Part of issue
Includes:

allow list solution
site-to-stie VPN for AWS
DNS proxy for private code hosts domain

In separate:

AWS Private Link
AWS access/accounts

This is our code host support page

This seems to be mis-intention, all pages under /cloud path has this warning (unless the "support" you mean is the internal support)

The customer-facing docs should live on https://docs.sourcergpah.com

This is our code host support page

This seems to be a mis-intention, all pages under /cloud path has this warning (unless the "support" you mean is the internal support)

The customer-facing docs should live on https://docs.sourcergpah.com

Yes, this is for us internally, to help setup/diagnose etc, but b/c we have it public anyway, I meant to explicitly said this is not for customer to use as the main source of truth :)
For customers I will open PR in docs, when I have all puzzles together.


Migrate to shadow-cljs

Migrates the build of re-frame itself to shadow-cljs.
Also better supports consumers of re-frame using shadow-cljs via inclusion of deps.edn.
Should not break consumers of re-frame using any other build system, including figwheel.
Uses the recently released lein-shadow 0.1.5 to manage shadow-cljs.edn and package.json.

@superstructor should we also change across the /example apps?


Command line application

Is there any way to add this framework to a command line application ?
I tried different ways but still get :

dyld: Library not loaded: @rpath/libswiftCore.dylib
Referenced from: /Users/****/Library/Developer/Xcode/DerivedData/TestProcedureKit-bvthfxsvvstphsaqrqphdvgtxzqu/Build/Products/Debug/ProcedureKit.framework/Versions/A/ProcedureKit
Reason: image not found

Hi @altab-ch, how are you setting up the command line application?

Hi danthorpe,
As explained in your installation guide, I tried to drag and drop the project and tried to install through cocoapods. I did not try to setup anything else in the command line app.
I also tried to install the framework in a regular Cocoa app and it is working fine.
I guess I should configure additional stuff to make this framework work in a command line app.
Best regards,

Additional information:
When I add the framework through cocapods, I get a warning:

Not running swift-stdlib-tool: ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES is enabled, but the product type 'Command-line Tool' is not a wrapper type

After googling, it seems a bit tricky to solve.

Hi @altab-ch - well, it certainly has worked before, because we added TaskProcedure in ProcedureKitMac explicitly for command line applications. But, admittedly we don't have integration tests for a command line app.
I will try to look into it, and see what the situation is. Sorry I can't provide a definitive answer right now 😔

Hi @altab-ch - not sure if you're still working on command line applications, but this open source project might help you out: https://github.com/CIKit/Buildkite


Make it easier to interrupt a running computation

Forked from https://github.com/FStarLang/fstar-mode.el/issues/50.  It would be nice to be able to kill Z3 from Emacs, or more generally to interrupt the current calculation. Questions:

Is there a small example of code that takes Z3 a long time that I could use for testing?
Could F* process a ^C signal and kill Z3 on its own?

Please try the 51-kill-z3 branch and tell me if C-c C-c helps there (I couldn't test it, as I don't have a small, slow example on hand)

It seems to work, but I'm getting quite a few errors from Z3, and some of the lines in the killed block are underlined with the error: unknown assertion failed.

A couple more observations:

the cursor jumps to the top most line of the file upon a "successful" C-c C-c.
C-c C-c does not seem to work on the very first block.
If there is no busy block, then pressing C-c C-c seems to kill the process the next time C-c C-n is pressed

Hope that helps a bit. If you need any testing or further info, I'm happy to help!

Doesn't work for me on Mac OS X (C-c C-c does nothing).
This small example should give you ample time to kill the Z3 process:
module N

val ack: nat -> nat -> nat
let rec ack m n =
  if m = 0 then n + 1
  else if n = 0 then ack (m - 1) 1
  else ack (m - 1) (ack m (n - 1))

#set-options "--max_fuel 16 --z3rlimit 2000"

let test =
  assert (ack 2 8 == 19)

Doesn't work on Mac OS X because process-attributes returns nil.
Found this on reddit:
Should be noted that this is limited to platforms supporting process-attributes. That excludes OS X, and probably other systems without /proc. Windows is supported, though.

@s-zanella Thanks for the test.  It should be easy to run a command instead of killing z3 from ELisp on macOS.  That being said, testing suggests that F* isn't always robust to Z3 dying (in most cases, killing Z3 causes F* to exit too, which confirms what @kkohbrok observed):
z3 exited inadvertently

Unexpected error; please file a bug report, ideally with a minimized version of the source program that triggered the error.
Unexpected output from Z3: got output lines:

Thus I'm not sure that killing z3 is the way to go.  Maybe the signals approach would work better? Or maybe F* can be made more resilient to z3 crashes?

In my experience (I've doing this a lot) killing Z3 works in most situations. I came across a couple of situations where this crashed F*, but I found this quite uncommon and the feature very useful in practice.
Of course a proper solution handling signals from F* will be more elegant and robust.

In my experience (I've doing this a lot) killing Z3 works in most situations. I came across a couple of situations where this crashed F*, but I found this quite uncommon and the feature very useful in practice.

Noted, thanks.

Actually, looks like sending a SIGINT twice does the trick.  How odd.

Ok.  @kkohbrok, can you try it again? On my machine I need to press C-c C-c it twice. Not sure why yet.
@s-zanella I changed the script it to use ps if list-system-processes isn't available.  Can you try again? Hopefully glibc's macOS port has kill; otherwise I'll apply a similar workaround for signal-process.

On Mac OS X list-system-processes is available, but it returns a list of pid nil nil. I got it working after modifying the script to always use ps.
Thanks! That's a big improvement over using a shell and figuring out which Z3 process to kill when running several F* instances at the same time.
I also see the behaviour you observe @cpitclaudel: I need to hit C-c C-c twice for the Z3 process to stop. Looks like a quirk of how Z3 handles signals. It must be catching SIGINT to e.g. display statistics before quitting.
By sending SIGTERM rather than SIGINT, Z3 exits immediately but produces garbage output (same problem as @kkohbrok) and the cursor jumps to the beginning of the buffer.

Here are some observations I made with the current version on linux:

first block still not retractable
it takes two to four C-c C-c to kill actually retract a busy section. When it does work, it still shows "assertion failed" warnings in some parts of the code. For the following example, it takes two time C-c C-c if the block includes only one test and four times C-c C-c if the block includes both tests

module Test

val ack: nat -> nat -> nat
let rec ack m n =
  if m = 0 then n + 1
  else if n = 0 then ack (m - 1) 1
  else ack (m - 1) (ack m (n - 1))

#set-options "--max_fuel 16 --z3rlimit 2000"
let test =
  assert (ack 2 8 == 19)

let test2 =
  assert (ack 2 8 == 19)

C-c C-c followed by C-c C-n kills the process when no section is busy.

The fact that the first block is not retractable can be explained: F* spends most of its time lax typechecking dependencies when pushing the first block of a file and can't be interrupted with C-c C-c because there's no active Z3 process to interrupt.

Assertion failures on C-c C-c are expected: we're interrupting the Z3 process in the middle of a query, which from the point of view of F* is the same as Z3 failing to verify the query.

I can't reproduce the C-c C-c followed by C-c C-n behaviour you see. May be specific to Linux.

It takes two to four C-c C-c to kill actually retract a busy section. When it does work, it still shows "assertion failed" warnings in some parts of the code. For the following example, it takes two time C-c C-c if the block includes only one test and four times C-c C-c if the block includes both tests

Interesting.  I see this here too, and I'm not sure why Z3 behaves that way.
The assertion failures are indeed expected; I think they are fine (I expect this to be a temporary solution anyway, until F* can process signals)

C-c C-c followed by C-c C-n kills the process when no section is busy.

Right — it seems that F* keeps an instance of Z3, and gets confused if it dies.  I disabled C-c C-c when no section is busy.

Ok, let's try this for now.  Please report further issues, if any, in new threads :)


Feature request: 'id' support on Web

When trying to pass the id option to createMMKV on the web, it throws an exception about this not being supported.
I realise that there can't really be truly separate stores on web because of how localStorage works, but it could be reasonably emulated (and the caveats about that emulation noted in the documentation) by namespacing the keys.
I'd be happy to contribute this feature, but I'd like to check if there was a reason it wasn't implemented initially that I might not have thought about.

I mean yes it can be supported by using a wildcard character (like \\), I just didn't think this was necessary.
I could draft a version up, if you have a PR I'd also appreciate that


Fix battery level calculation for Nest Protect by adding support for battery voltage conversions

Based on the great work of https://github.com/iMicknl/ha-nest-protect/pull/276 and https://github.com/iMicknl/ha-nest-protect/pull/273.
Let's test this one first in the beta branch. I am working on improving the beta branch and actually making this the new main version!

@rmcginty added your work in this branch, with some small fixes + added you as the contributor, so your name should show up in the changelog 😁.


Skip isBlockScopedNameDeclaredBeforeUse error in interface or type declarations

Fixes #35947.

Two questions:

Is there an existing utility that checks whether a node is in a type/interface declaration?
The first commit is unrelated to the fix, is it OK to keep it separate?

@typescript-bot perf test this


AMD SEV technology enablement

This is the placeholder issue for tracking the progress of AMD Memory Encryption features (SEV, SEV-ES, SEV-SNP) enablement in KubeVirt.
Original discussion from the mailing list: https://groups.google.com/g/kubevirt-dev/c/a6XlT0qRNAY/m/IWFAOu2xAAAJ
/kind enhancement
Implementation

[x] Basic SEV support
https://github.com/kubevirt/kubevirt/pull/6166
[ ] Encrypted State (SEV-ES)
https://github.com/kubevirt/kubevirt/pull/7742
[ ] Secure Nested Paging (SEV-SNP)
[ ] Attestation
~[WIP] Libvirt API: https://listman.redhat.com/archives/libvir-list/2021-December/msg00800.html~
virDomainSetLaunchSecurityState API implemented in libvirt 8.0.0 (allows injecting a secret into a running VM)
virsh nodesevinfo command implemented in libvirt 8.0.0 (provides platform certificates)
(!) Proposal to generalize the attestation flow in libvirt: https://listman.redhat.com/archives/libvir-list/2022-February/228809.html
https://github.com/kubevirt/kubevirt/pull/7197
https://github.com/kubevirt/kubevirt/pull/7595
[ ] Support rotation of the platform certificates
[ ] Support external kernel / initrd / cmdline
[ ] Avoid using EFI vars storage with confidential guests
[ ] Expose attestation data SEVPlatformInfo and SEVMeasurementInfo in VMIStatus
[x] Expose /dev/sev device to pods only if the feature gate is enabled
https://github.com/kubevirt/kubevirt/pull/8099

Testing

[x] Update the test image for CI
https://github.com/kubevirt/kubevirt/pull/6958
https://github.com/kubevirt/kubevirtci/pull/713
[ ] Run functional tests on AMD hardware
[ ] Use encrypted image for testing
[WIP] GRUB: https://lists.gnu.org/archive/html/grub-devel/2022-02/msg00064.html

Documentation

[x] Initial design proposal
https://github.com/kubevirt/community/pull/141
[ ] Update user-guide
https://github.com/kubevirt/user-guide/pull/539
[ ] Ensure the design proposal and user-guide are in sync with the implementation

How the plan for testing looks like? Would it be possible to test this with non-root? Thanks, @vasiliy-ul !

HI @xpivarc . The actual test cases are provided with the implementation PR (well, only one test case so far...). Though for testing the feature there are a couple of prerequisites that are still missing: 1) we need to have a guest VM with recent kernel and UEFI boot support. The relevant PRs (switch to Fedora 35) are under discussion at the moment; 2) the feature requires specific hardware to run on. I am not sure if there is a test machine with AMD EPYC CPU available in kubevirt CI cluster for that. For now I tested and verified manually on AMD machine.
Regarding non-root: I cannot think of any potetnial issue at the moment. Qemu will just need to have RW access to /dev/sev device which can be setup in the same way as other devices (e.g. /dev/kvm). So in theory it should work with non-root... but I might be too optimistic :)

HI @xpivarc . The actual test cases are provided with the implementation PR (well, only one test case so far...). Though for testing the feature there are a couple of prerequisites that are still missing: 1) we need to have a guest VM with recent kernel and UEFI boot support. The relevant PRs (switch to Fedora 35) are under discussion at the moment; 2) the feature requires specific hardware to run on. I am not sure if there is a test machine with AMD EPYC CPU available in kubevirt CI cluster for that. For now I tested and verified manually on AMD machine.

As far as I know, we are missing the hw in our clusters.

Regarding non-root: I cannot think of any potetnial issue at the moment. Qemu will just need to have RW access to /dev/sev device which can be setup in the same way as other devices (e.g. /dev/kvm). So in theory it should work with non-root... but I might be too optimistic :)

Thanks for the response. It is also our assumption but we want to be sure :) I would appreciate it if you give it a try.
/cc @vladikr

It is also our assumption but we want to be sure :) I would appreciate it if you give it a try.

Hi @xpivarc . I tried to run a SEV guest with non-root. Everything was fine. The access to /dev/sev is properly configured for qemu user and I think that libvirt does not actually talk to the device directly (it only queries the domain for SEV info). So, seems there are no issues with that.

@vasiliy-ul Thank you!

/remove-lifecycle stale

Hi all, this is up-to-date right? We don't have SEV-ES yet

@hw-claudio not yet. We are still integrating the SEV CI nodes to be able to test the code changes

@alicefr noticed the bot inactivity message, are the SEV CI nodes integrated now, is AMD SEV-ES functional?

/remove-lifecycle rotten

Is this live with ES/SNP?  Currently working with libvirt on one of our clusters and would love to be able to fold this into our CoCo build.

SEV-ES is already enabled. SNP is WIP in kernel/qemu/libvirt (not yet upstreamed), hence not supported in KubeVirt so far.
/remove-lifecycle rotten

Hi, AFAIK now SNP is in upstream kernel, upstream qemu, upstream libvirt, so we can proceed with SNP? THanks, CLaudio

snp is upstream now in linux 6.11, qemu 9.1.
libvirt has announced official support, but it still requires specific quirks in the xml.
i'm going to try (if audio permits) asking in the kubvirt community meeting today what this means for kubevirt.

snp is upstream now in linux 6.11, qemu 9.1. libvirt has announced official support, but it still requires specific quirks in the xml.
i'm going to try (if audio permits) asking in the kubvirt community meeting today what this means for kubevirt.

SNP support can be added to upstream KubeVirt when all the bits (i.e. libvirt, qemu, edk2, etc.) land in centos. Otherwise, we cannot build SNP-capable container images. Additionally, we will need proper hardware to run e2e tests. For now, I just have a draft implementation in my fork https://github.com/vasiliy-ul/kubevirt/commits/sev-snp/

land in centos.

fedora rawhide should have all the packages. is centos  now trailing rawhide? dunno how this works these days.

https://github.com/vasiliy-ul/kubevirt/commits/sev-snp/

that wont work out of the box with current upstream qemu/libvirt. should i send patches to your fork?

fedora rawhide should have all the packages. is centos now trailing rawhide? dunno how this works these days.

Upstream KubeVirt images are based on centos 9 stream.

that wont work out of the box with current upstream qemu/libvirt. should i send patches to your fork?

No need to send patches. This should work when centos adopts the new libvirt, qemu, etc. and KubeVirt bumps the container images. Then I can submit the implementation as a PR for the KubeVirt repo. Until then it is mostly an experimental set of patches to play with if you have proper hardware. I personally build custom images from that for testing meanwhile.

BTW, qemu is still RC 9.1.0-rc1

@vasiliy-ul Hi Vasiliy, may I ask when the SNP enablement PR will be submitted? Is the attestation affected or do we need some extra work for the attestation? Thanks.

@vicaya @zhencliu AFAICT @vasiliy-ul will not be active on Kubevirt in the near future.
Would one of you want to take over implementing this?
If not, I can try to dig around to figure who has enough bandwidth / interest to promote this.

The current state of the upstream bits is fairly complete so all that's really needed is a single line in the xml.
I could do that but I don't understand what you'd want to do about the attestation. ES is broken, and SNP works entirely different, shifting the attestation to user space or secure boot. This isn't something that belongs into kubevirt imo..

Thanks for the update @iholder101 , and thanks for taking over this @aep, yes, forget my questions about attestation, it looks the attestation will be brought in other patches in future (learnt from the previous MR comments if I understood correctly)


Sidechain inputs not working?

I can't tell if this a problem in my DAW (Reason on Windows) or ysfx. The same problem exists with ReaJS.
I'm trying to access the sidechain inputs via spl2 and spl3. It seems these never get any input, and the back of Reason rack shows these channels as gray instead of green like the main inputs. The values just stay 0 in my script.
I posted about ReaJS here:
https://forum.cockos.com/showthread.php?t=277907
But I suspect the problem there is ReaJS. I don't have another DAW to verify this on.
Are spl2/3 accessible with ysfx? Thanks.

Out of curiosity I tried this with ysfx running under Bluecat Patchwork (VST host). In this case it does work, and Patchwork has its sidechain inputs green in Reason. I suspect this an issue with Reason. It seems like it detects whether the VST has sidechain inputs only at initial load. The blank script ysfx initial load only has 2 inputs, and the 4 inputs come only when the script is loaded. Probably Reason doesn't notice this change in inputs once the script is loaded.


python3Packages.aiotractive: 0.5.3 -> 0.5.4

Description of changes
https://github.com/zhulik/aiotractive/releases/tag/v0.5.4

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

3 packages built:

home-assistant-component-tests.tractive
python310Packages.aiotractive
python39Packages.aiotractive


Why transform only applicable when navigation mode is enable

Describe the bug
Let's say we have more than one camera where each camera has its own coordinate system. Thus, before applying to filter it should be transformed into a common coordinate frame (car). So I believe transformer_->Transform(&objects); should be applied even when navigation mode is disabled.
Also, if this transform is enabled is camera_process_subnode.cc, transform in the object_camera_filter.cc is not needed.
https://github.com/ApolloAuto/apollo/blob/v3.1_dev/modules/perception/obstacle/camera/filter/object_camera_filter.cc#L111 , https://github.com/ApolloAuto/apollo/blob/v3.1_dev/modules/perception/obstacle/camera/filter/object_camera_filter.cc#L196
Please correct me if my assumption is wrong.
Desktop (please complete the following information):

OS: Ubuntu 14.04
Browser Chrome

@GPrathap
Your assumption seems wrong.
Although the code of this camera_process_subnode.cc does not as clean as others, the logic has no problem.
When it is under the navigation mode, the objects transform from camera coordinate to car coordinate transformer_->Transform(&objects); before filter_->Filter(timestamp, &objects, options);.
While, when use_navigation_mode is false, the objects were filtered filter_->Filter(timestamp, &objects, options); directly. But the camera to world transformation is packeted into option if (!GetCameraTrans(timestamp, options.camera_trans.get())) {, and then transformed in filter filter_->Filter(timestamp, &objects, options);.
Right, the navigation mode is on relative coordination(the car coordination). Otherwise, the world coordination.

@xmyqsh Did you see the difference between transformer_->Transform(&objects); and transform which happens inside transformed in filter void ObjectCameraFilter::TransformObject(std::shared_ptr obj,
const Eigen::Matrix4f& pose). What I believe is that both cases it should be in the same way.
And why do you think trasformation is happes two differnt places based on navigation mode?

@GPrathap
Haha, I have said this code part is not clean.
See here,
if (FLAGS_use_navigation_mode) {
    options.camera_trans = std::make_shared<Eigen::Matrix4d>();
    options.camera_trans->setIdentity();
  } else {
    options.camera_trans = std::make_shared<Eigen::Matrix4d>();
    if (!GetCameraTrans(timestamp, options.camera_trans.get())) {
      AERROR << "failed to get trans at timestamp: " << timestamp;
      return;
    }
  }

I think you have not noticed this line options.camera_trans->setIdentity();

Yes, if you dont understand better not to comment :)

@GPrathap
Got it. You are right, guys!! Bugs here.
I haven't digged into object_camera_filter.cc before.

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


How to load and use on demand？

Thanks for your feedback. I will support dynamic import soon.

You can use dynamic import in v0.15.0. See dynamic import


PyEval_SaveThread/PyEval_RestoreThread causing segfaults?

Not really a high-level numba question per se, but I would be very grateful if any numba/llvm gurus here could help me figure this out :)
I was playing around with llvmlite trying to use numba's helper classes to compile various snippets, and it all works great except for when I try to release the GIL via PyEval_SaveThread / PyEval_RestoreThread (sort of following the multithreaded example, or just by inspecting llvm of a simple function wrapped in @numba.njit with nogil=True).
The example below segfaults however it works fine when the two PyEval calls are commented out:
# test_llvm.py
from __future__ import print_function

import ctypes
from numba import typing
from numba.targets import cpu
from llvmlite import binding as llvm

mod = """
; ModuleID = 'test'

define i32 @f() {
  %thread = tail call i8* @PyEval_SaveThread()
  tail call void @PyEval_RestoreThread(i8* %thread)
  ret i32 42
}

declare i8* @PyEval_SaveThread()
declare void @PyEval_RestoreThread(i8*)
"""

typing_ctx = typing.Context()
cpu_ctx = cpu.CPUContext(typing_ctx)
codegen = cpu_ctx.jit_codegen()
library = codegen.create_library('lib')
module_ref = llvm.parse_assembly(mod)
module_ref.verify()
library.add_llvm_module(module_ref)
library.finalize()
func_ptr = library.get_pointer_to_function('f')
cfunc = ctypes.CFUNCTYPE(ctypes.c_int32)(func_ptr)
assert cfunc() == 42

$ python test_llvm.py
Fatal Python error: PyEval_SaveThread: NULL tstate
fish: Job 2, “python test_llvm.py” terminated by signal SIGABRT (Abort)

Is there anything else in particular that has to be done to release the GIL? And why would it return NULL for main thread's state?
Thanks!

ctypes already releases the GIL: https://docs.python.org/3/library/ctypes.html#ctypes.CFUNCTYPE

Got it!


Json format

Hello, I'd like to use this library for translating my website. But I have all langage ressource in json format. I tryied to adapt a new format in your code but I'm not fluent in php so I didn't succeed. Do you planify a json plugin as yml?

Wait a second, doesn't #9 fix this?

obviously it does


chore: Rename zpow_coe_nat to zpow_natCast

... and add a deprecated alias for the old name. This is mostly just me discovering the power of F2

bors merge

bors merge


How to combine it with fancybox ?

I use fancybox. When I use lazyload with fancybox, the image does not appear, but when I click its link, the new image will be uploaded.

Can you better describe what's happening?

That's my code. Thanks for your answer :)

Hi @akbarsaputrait,
thank you for sharing the code.
Can you better describe what's happening? The sentence "When I use lazyload with fancybox, the image does not appear, but when I click its link, the new image will be uploaded." doesn't sound very clear to me.

It looks like you're trying and getting some screenshots using an AJAX call, then you cycle through all the resulting data and append the images inside the element #ss_yesterday, as lazy loading images.
My question is: why are you loading those images lazily? In my opinion, you can just load them "eagerly", putting the image's URL in the src instead of the data-src. You shouldn't have performance issues since the images are already loaded after the AJAX call is complete.

@verlok Thank you so much, for your answer. I glad to know about that! :smile:


Issue 38 service results

This implements service result machinery for slayer that matches commands.
After we get this to where we are happy with it, there is still work to do to share code between the result infrastructure for services and commands. This should probably be implemented with something like a Slayer::Resulting module, or something of the sort that both Command and Service simply inherit.

Coverage increased (+0.5%) to 100.0% when pulling 2754735a33f1d743141b9da9bc5a26e8d5b5ace2 on issue-38-service-results into 7f451b07ba23d19dc5a40641cdc2b8465a284a1b on breaking/v0.4.0.


Update saxon9he.jar to version <IP_ADDRESS>

Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

This updates to the next minor version which is considered to be the most stable and reliable version by the upstream maintainers, so it should be save.

@zuphilip, do you know how to debug the CI failure for ci/dockercloud? I get error 404 when I want to see the details of that failure.

do you know how to debug the CI failure for ci/dockercloud

The failure was caused by the unsupported python entry in Dockerfile and is fixed now.

The fix for Dockerfile requires also replacing python2 by python3 in script/validate/hocr. It was used for hocr-spec-python which should work with Python 3, too.

The update from Python 2 to Python 3 is not only needed to fix docker build, but also required in the OCR-D context.


Merge ts branch into master.

... and release to npm, since this is really useful. :-)

when will this pull request be released to npm? :)

@alexkrauss Is is possible to clean up the template folder by making filenames more explicits? For instance node-typedef.mustache doesn't sound like a good name. In the test you added, can you check if the generated file is typescript valid? using tslint for instance?

@wcandillon What names would you suggest then?
In the test, the result is already checked against a predefined expectation, so I'm not sure, adding a tslint check adds anything except overhead. I was thinking of this more as a unit test, with a predefined input and output... One could also think about proper integration testing, but then we would also have to make sure that the generated type definitions match the generated code... This is certainly more work.

@alexkrauss Thank you so much for doing this. I have made a branch that superseeds this. I reused the typeconvertion function you wrote.


Fix node6 native

The intercept fails for native modules in node6. In that case. absPath remains undefined, which causes path.extname to fail in node 6, as it no longer accepts undefined.
The behavior of path.extname in node 4 when undefined is passed in is to return an empty string, so the fix is to check for undefined and return an empty string directly if it is.
These are the relevant lines: https://github.com/nickb1080/intercept-require/blob/master/lib/index.js#L108-L130
The error is easy to reproduce, use n to easily switch between node versions. I added a test as well. To reproduce, first merge my first commit, run the test under node 6 and see it fail. Then merge the second commit and see it pass.

Whoops I had just run into this a couple days ago and fixed it, and published to npm (1.1.0) but didn't push to GitHub The relevant fix is mostly https://github.com/nickb1080/intercept-require/blob/master/lib/index.js#L124
Does this fix satisfy your issue? I've pulled your test case in and it passes.


util: Implement core diagnostics

@MinaFarhan these are some changes that I made to clean up things further. Notice that I added the necessary boost include into the linter. I have also adjusted a few minor things.
I have tested this and some problems remain in operation that I would like you to troubleshoot:
I got one error on the assert(m_name_to_test_map.size() < Diagnose::TestSize) on wallet startup. I have not reproduced this. Very strange. This should not happen based on my read of the code.
I am getting bus errors on the boost::asio::io_service: here are two different stack traces. You need to troubleshoot this.
Thread 1 "gridcoinresearc" received signal SIGBUS, Bus error.
boost::asio::detail::epoll_reactor::descriptor_state::perform_io (this=0x555557948710, events=1) at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:745
745 op_queue_[j].pop();
Missing separate debuginfos, use: zypper install libminiupnpc17-debuginfo-2.2.2-bp154.1.81.x86_64 libx265-199-debuginfo-3.5-pm154.2.9.x86_64
(gdb) bt
#0 boost::asio::detail::epoll_reactor::descriptor_state::perform_io (this=0x555557948710, events=1)
at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:745
https://github.com/MinaFarhan/Gridcoin-Research/pull/1 0x000055555554f240 in boost::asio::detail::epoll_reactor::descriptor_state::do_complete (bytes_transferred=, ec=...,
base=, owner=0x555556358510) at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:774
https://github.com/gridcoin-community/Gridcoin-Research/issues/2 boost::asio::detail::epoll_reactor::descriptor_state::do_complete (owner=0x555556358510, base=, ec=...,
bytes_transferred=) at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:766
https://github.com/gridcoin-community/Gridcoin-Research/issues/3 0x000055555554f637 in boost::asio::detail::scheduler_operation::complete (bytes_transferred=1, ec=..., owner=0x555556358510,
this=0x555557948710) at /usr/include/boost/asio/detail/scheduler_operation.hpp:40
https://github.com/gridcoin-community/Gridcoin-Research/pull/4 boost::asio::detail::scheduler::do_run_one (this=this@entry=0x555556358510, lock=..., this_thread=..., ec=...)
at /usr/include/boost/asio/detail/impl/scheduler.ipp:401
https://github.com/gridcoin-community/Gridcoin-Research/pull/5 0x000055555554f981 in boost::asio::detail::scheduler::run (this=0x555556358510, ec=...)
at /usr/include/boost/asio/detail/impl/scheduler.ipp:154
https://github.com/gridcoin-community/Gridcoin-Research/issues/6 0x000055555555c22e in boost::asio::io_context::run (this=) at /usr/include/boost/asio/impl/io_context.ipp:62
https://github.com/gridcoin-community/Gridcoin-Research/pull/7 DiagnoseLib::VerifyClock::runCheck (this=) at ./wallet/diagnose.h:356
https://github.com/gridcoin-community/Gridcoin-Research/pull/8 0x00005555555485ad in DiagnosticsDialog::on_testButton_clicked (this=this@entry=0x555556cd2bc0) at qt/diagnosticsdialog.cpp:300
https://github.com/gridcoin-community/Gridcoin-Research/pull/9 0x000055555560dd5c in DiagnosticsDialog::qt_static_metacall (_a=0x7fffffffb500, _id=0, _c=QMetaObject::InvokeMetaMethod, _o=0x555556cd2bc0)
at qt/moc_diagnosticsdialog.cpp:72
https://github.com/gridcoin-community/Gridcoin-Research/pull/10 DiagnosticsDialog::qt_metacall (this=0x555556cd2bc0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffffb500)
at qt/moc_diagnosticsdialog.cpp:109
https://github.com/gridcoin-community/Gridcoin-Research/pull/11 0x00007ffff546c2a9 in doActivate (sender=0x555556cd2930, signal_index=9, argv=0x7fffffffb500) at kernel/qobject.cpp:3912
https://github.com/gridcoin-community/Gridcoin-Research/pull/12 0x00007ffff5465782 in QMetaObject::activate (sender=sender@entry=0x555556cd2930,
m=m@entry=0x7ffff6d584e0 QAbstractButton::staticMetaObject, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffffffb500)
at kernel/qobject.cpp:3946
https://github.com/gridcoin-community/Gridcoin-Research/pull/13 0x00007ffff675a772 in QAbstractButton::clicked (this=this@entry=0x555556cd2930, _t1=) at .moc/moc_qabstractbutton.cpp:308
https://github.com/gridcoin-community/Gridcoin-Research/pull/14 0x00007ffff675a98a in QAbstractButtonPrivate::emitClicked (this=0x555556a6beb0) at widgets/qabstractbutton.cpp:415
https://github.com/gridcoin-community/Gridcoin-Research/pull/15 0x00007ffff675bdea in QAbstractButtonPrivate::click (this=0x555556a6beb0) at widgets/qabstractbutton.cpp:408
https://github.com/gridcoin-community/Gridcoin-Research/issues/16 0x00007ffff675bfdd in QAbstractButton::mouseReleaseEvent (this=0x555556cd2930, e=0x7fffffffbaa0) at widgets/qabstractbutton.cpp:1044
https://github.com/gridcoin-community/Gridcoin-Research/pull/17 0x00007ffff66aeb48 in QWidget::event (this=0x555556cd2930, event=0x7fffffffbaa0) at kernel/qwidget.cpp:9020
https://github.com/gridcoin-community/Gridcoin-Research/pull/18 0x00007ffff675d1ab in QAbstractButton::event (this=this@entry=0x555556cd2930, e=e@entry=0x7fffffffbaa0) at widgets/qabstractbutton.cpp:1001
https://github.com/gridcoin-community/Gridcoin-Research/pull/19 0x00007ffff67fd69f in QPushButton::event (this=0x555556cd2930, e=0x7fffffffbaa0) at widgets/qpushbutton.cpp:709
https://github.com/gridcoin-community/Gridcoin-Research/pull/20 0x00007ffff666e3bc in QApplicationPrivate::notify_helper (this=this@entry=0x5555563683e0, receiver=receiver@entry=0x555556cd2930,
e=e@entry=0x7fffffffbaa0) at kernel/qapplication.cpp:3632
https://github.com/gridcoin-community/Gridcoin-Research/pull/21 0x00007ffff6675730 in QApplication::notify (this=, receiver=0x555556cd2930, e=0x7fffffffbaa0) at kernel/qapplication.cpp:3076
https://github.com/gridcoin-community/Gridcoin-Research/pull/22 0x00007ffff542ec23 in QCoreApplication::notifyInternal2 (receiver=0x555556cd2930, event=0x7fffffffbaa0) at kernel/qcoreapplication.cpp:1064
https://github.com/gridcoin-community/Gridcoin-Research/pull/23 0x00007ffff542ee0e in QCoreApplication::sendSpontaneousEvent (receiver=receiver@entry=0x555556cd2930, event=event@entry=0x7fffffffbaa0)
at kernel/qcoreapplication.cpp:1474
https://github.com/gridcoin-community/Gridcoin-Research/issues/24 0x00007ffff667471f in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x555556cd2930, event=event@entry=0x7fffffffbaa0,
alienWidget=0x555556cd2930, nativeWidget=0x555556cd2bc0, buttonDown=buttonDown@entry=0x7ffff6d8a670 <qt_button_down>, lastMouseReceiver=...,
--Type for more, q to quit, c to continue without paging--
spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614
https://github.com/gridcoin-community/Gridcoin-Research/pull/25 0x00007ffff66c931c in QWidgetWindow::handleMouseEvent (this=this@entry=0x555556dd1cb0, event=event@entry=0x7fffffffbf00)
at kernel/qwidgetwindow.cpp:683
https://github.com/gridcoin-community/Gridcoin-Research/pull/26 0x00007ffff66cc38d in QWidgetWindow::event (this=0x555556dd1cb0, event=0x7fffffffbf00) at kernel/qwidgetwindow.cpp:300
https://github.com/gridcoin-community/Gridcoin-Research/pull/27 0x00007ffff666e3bc in QApplicationPrivate::notify_helper (this=this@entry=0x5555563683e0, receiver=receiver@entry=0x555556dd1cb0,
e=e@entry=0x7fffffffbf00) at kernel/qapplication.cpp:3632
https://github.com/gridcoin-community/Gridcoin-Research/pull/28 0x00007ffff66751a0 in QApplication::notify (this=0x7fffffffccb0, receiver=0x555556dd1cb0, e=0x7fffffffbf00) at kernel/qapplication.cpp:3156
https://github.com/gridcoin-community/Gridcoin-Research/pull/29 0x00007ffff542ec23 in QCoreApplication::notifyInternal2 (receiver=0x555556dd1cb0, event=0x7fffffffbf00) at kernel/qcoreapplication.cpp:1064
https://github.com/gridcoin-community/Gridcoin-Research/pull/30 0x00007ffff542ee0e in QCoreApplication::sendSpontaneousEvent (receiver=receiver@entry=0x555556dd1cb0, event=event@entry=0x7fffffffbf00)
at kernel/qcoreapplication.cpp:1474
https://github.com/gridcoin-community/Gridcoin-Research/pull/31 0x00007ffff5d1b0cb in QGuiApplicationPrivate::processMouseEvent (e=0x555556bdfe40) at kernel/qguiapplication.cpp:2282
https://github.com/gridcoin-community/Gridcoin-Research/pull/32 0x00007ffff5d1c675 in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x555556bdfe40) at kernel/qguiapplication.cpp:2002
https://github.com/gridcoin-community/Gridcoin-Research/pull/33 0x00007ffff5cf444b in QWindowSystemInterface::sendWindowSystemEvents<EMAIL_ADDRESS>at kernel/qwindowsysteminterface.cpp:1169
https://github.com/gridcoin-community/Gridcoin-Research/pull/34 0x00007fffe7d49d0a in xcbSourceDispatch (source=) at qxcbeventdispatcher.cpp:105
https://github.com/gridcoin-community/Gridcoin-Research/pull/35 0x00007ffff04797fb in g_main_dispatch (context=0x7fffe0005000) at ../glib/gmain.c:3381
https://github.com/gridcoin-community/Gridcoin-Research/pull/36 g_main_context_dispatch (context=context@entry=0x7fffe0005000) at ../glib/gmain.c:4099
https://github.com/gridcoin-community/Gridcoin-Research/pull/37 0x00007ffff0479ba0 in g_main_context_iterate (context=context@entry=0x7fffe0005000, block=block@entry=1, dispatch=dispatch@entry=1,
self=) at ../glib/gmain.c:4175
https://github.com/gridcoin-community/Gridcoin-Research/pull/38 0x00007ffff0479c2c in g_main_context_iteration (context=0x7fffe0005000, may_block=may_block@entry=1) at ../glib/gmain.c:4240
https://github.com/gridcoin-community/Gridcoin-Research/pull/39 0x00007ffff549102c in QEventDispatcherGlib::processEvents (this=0x55555652bb90, flags=...) at kernel/qeventdispatcher_glib.cpp:423
https://github.com/gridcoin-community/Gridcoin-Research/issues/40 0x00007ffff542d48a in QEventLoop::exec (this=this@entry=0x7fffffffc2a0, flags=<EMAIL_ADDRESS>at kernel/qeventloop.cpp:232
https://github.com/gridcoin-community/Gridcoin-Research/pull/41 0x00007ffff5436cc7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1375
https://github.com/gridcoin-community/Gridcoin-Research/pull/42 0x00007ffff5d0ff9c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867
https://github.com/gridcoin-community/Gridcoin-Research/pull/43 0x00007ffff666e315 in QApplication::exec () at kernel/qapplication.cpp:2824
https://github.com/gridcoin-community/Gridcoin-Research/pull/44 0x000055555552365f in StartGridcoinQt (argc=, argv=0x7fffffffd8e8, app=..., optionsModel=...) at qt/bitcoin.cpp:698
https://github.com/gridcoin-community/Gridcoin-Research/pull/45 0x0000555555507ad5 in main (argc=, argv=0x7fffffffd8e8) at qt/bitcoin.cpp:530
Thread 1 "gridcoinresearc" received signal SIGBUS, Bus error.
boost::asio::detail::epoll_reactor::descriptor_state::perform_io (this=0x555556c99430, events=1) at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:745
745 op_queue_[j].pop();
(gdb) bt
#0 boost::asio::detail::epoll_reactor::descriptor_state::perform_io (this=0x555556c99430, events=1)
at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:745
https://github.com/MinaFarhan/Gridcoin-Research/pull/1 0x000055555554f250 in boost::asio::detail::epoll_reactor::descriptor_state::do_complete (bytes_transferred=, ec=...,
base=, owner=0x555556358510) at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:774
https://github.com/gridcoin-community/Gridcoin-Research/issues/2 boost::asio::detail::epoll_reactor::descriptor_state::do_complete (owner=0x555556358510, base=, ec=...,
bytes_transferred=) at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:766
https://github.com/gridcoin-community/Gridcoin-Research/issues/3 0x000055555554f647 in boost::asio::detail::scheduler_operation::complete (bytes_transferred=1, ec=..., owner=0x555556358510,
this=0x555556c99430) at /usr/include/boost/asio/detail/scheduler_operation.hpp:40
https://github.com/gridcoin-community/Gridcoin-Research/pull/4 boost::asio::detail::scheduler::do_run_one (this=this@entry=0x555556358510, lock=..., this_thread=..., ec=...)
at /usr/include/boost/asio/detail/impl/scheduler.ipp:401
https://github.com/gridcoin-community/Gridcoin-Research/pull/5 0x000055555554f991 in boost::asio::detail::scheduler::run (this=0x555556358510, ec=...)
at /usr/include/boost/asio/detail/impl/scheduler.ipp:154
https://github.com/gridcoin-community/Gridcoin-Research/issues/6 0x000055555555c7de in boost::asio::io_context::run (this=) at /usr/include/boost/asio/impl/io_context.ipp:62
https://github.com/gridcoin-community/Gridcoin-Research/pull/7 DiagnoseLib::VerifyClock::runCheck (this=) at ./wallet/diagnose.h:362
https://github.com/gridcoin-community/Gridcoin-Research/pull/8 0x000055555554854d in DiagnosticsDialog::on_testButton_clicked (this=this@entry=0x555556cf7f10) at qt/diagnosticsdialog.cpp:292
https://github.com/gridcoin-community/Gridcoin-Research/pull/9 0x000055555560e42c in DiagnosticsDialog::qt_static_metacall (_a=0x7fffffffb500, _id=0, _c=QMetaObject::InvokeMetaMethod, _o=0x555556cf7f10)
at qt/moc_diagnosticsdialog.cpp:72
https://github.com/gridcoin-community/Gridcoin-Research/pull/10 DiagnosticsDialog::qt_metacall (this=0x555556cf7f10, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffffb500)
at qt/moc_diagnosticsdialog.cpp:109
https://github.com/gridcoin-community/Gridcoin-Research/pull/11 0x00007ffff546c2a9 in doActivate (sender=0x5555569e68a0, signal_index=9, argv=0x7fffffffb500) at kernel/qobject.cpp:3912
https://github.com/gridcoin-community/Gridcoin-Research/pull/12 0x00007ffff5465782 in QMetaObject::activate (sender=sender@entry=0x5555569e68a0,
m=m@entry=0x7ffff6d584e0 QAbstractButton::staticMetaObject, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffffffb500)
at kernel/qobject.cpp:3946
https://github.com/gridcoin-community/Gridcoin-Research/pull/13 0x00007ffff675a772 in QAbstractButton::clicked (this=this@entry=0x5555569e68a0, _t1=) at .moc/moc_qabstractbutton.cpp:308
https://github.com/gridcoin-community/Gridcoin-Research/pull/14 0x00007ffff675a98a in QAbstractButtonPrivate::emitClicked (this=0x555556a2a400) at widgets/qabstractbutton.cpp:415
https://github.com/gridcoin-community/Gridcoin-Research/pull/15 0x00007ffff675bdea in QAbstractButtonPrivate::click (this=0x555556a2a400) at widgets/qabstractbutton.cpp:408
https://github.com/gridcoin-community/Gridcoin-Research/issues/16 0x00007ffff675bfdd in QAbstractButton::mouseReleaseEvent (this=0x5555569e68a0, e=0x7fffffffbaa0) at widgets/qabstractbutton.cpp:1044
https://github.com/gridcoin-community/Gridcoin-Research/pull/17 0x00007ffff66aeb48 in QWidget::event (this=0x5555569e68a0, event=0x7fffffffbaa0) at kernel/qwidget.cpp:9020
https://github.com/gridcoin-community/Gridcoin-Research/pull/18 0x00007ffff675d1ab in QAbstractButton::event (this=this@entry=0x5555569e68a0, e=e@entry=0x7fffffffbaa0) at widgets/qabstractbutton.cpp:1001
https://github.com/gridcoin-community/Gridcoin-Research/pull/19 0x00007ffff67fd69f in QPushButton::event (this=0x5555569e68a0, e=0x7fffffffbaa0) at widgets/qpushbutton.cpp:709
https://github.com/gridcoin-community/Gridcoin-Research/pull/20 0x00007ffff666e3bc in QApplicationPrivate::notify_helper (this=this@entry=0x5555563683e0, receiver=receiver@entry=0x5555569e68a0,
e=e@entry=0x7fffffffbaa0) at kernel/qapplication.cpp:3632
https://github.com/gridcoin-community/Gridcoin-Research/pull/21 0x00007ffff6675730 in QApplication::notify (this=, receiver=0x5555569e68a0, e=0x7fffffffbaa0) at kernel/qapplication.cpp:3076
https://github.com/gridcoin-community/Gridcoin-Research/pull/22 0x00007ffff542ec23 in QCoreApplication::notifyInternal2 (receiver=0x5555569e68a0, event=0x7fffffffbaa0) at kernel/qcoreapplication.cpp:1064
https://github.com/gridcoin-community/Gridcoin-Research/pull/23 0x00007ffff542ee0e in QCoreApplication::sendSpontaneousEvent (receiver=receiver@entry=0x5555569e68a0, event=event@entry=0x7fffffffbaa0)
at kernel/qcoreapplication.cpp:1474
https://github.com/gridcoin-community/Gridcoin-Research/issues/24 0x00007ffff667471f in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x5555569e68a0, event=event@entry=0x7fffffffbaa0,
alienWidget=0x5555569e68a0, nativeWidget=0x555556cf7f10, buttonDown=buttonDown@entry=0x7ffff6d8a670 <qt_button_down>, lastMouseReceiver=...,
--Type for more, q to quit, c to continue without paging--
spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614
https://github.com/gridcoin-community/Gridcoin-Research/pull/25 0x00007ffff66c931c in QWidgetWindow::handleMouseEvent (this=this@entry=0x555556c92100, event=event@entry=0x7fffffffbf00)
at kernel/qwidgetwindow.cpp:683
https://github.com/gridcoin-community/Gridcoin-Research/pull/26 0x00007ffff66cc38d in QWidgetWindow::event (this=0x555556c92100, event=0x7fffffffbf00) at kernel/qwidgetwindow.cpp:300
https://github.com/gridcoin-community/Gridcoin-Research/pull/27 0x00007ffff666e3bc in QApplicationPrivate::notify_helper (this=this@entry=0x5555563683e0, receiver=receiver@entry=0x555556c92100,
e=e@entry=0x7fffffffbf00) at kernel/qapplication.cpp:3632
https://github.com/gridcoin-community/Gridcoin-Research/pull/28 0x00007ffff66751a0 in QApplication::notify (this=0x7fffffffccb0, receiver=0x555556c92100, e=0x7fffffffbf00) at kernel/qapplication.cpp:3156
https://github.com/gridcoin-community/Gridcoin-Research/pull/29 0x00007ffff542ec23 in QCoreApplication::notifyInternal2 (receiver=0x555556c92100, event=0x7fffffffbf00) at kernel/qcoreapplication.cpp:1064
https://github.com/gridcoin-community/Gridcoin-Research/pull/30 0x00007ffff542ee0e in QCoreApplication::sendSpontaneousEvent (receiver=receiver@entry=0x555556c92100, event=event@entry=0x7fffffffbf00)
at kernel/qcoreapplication.cpp:1474
https://github.com/gridcoin-community/Gridcoin-Research/pull/31 0x00007ffff5d1b0cb in QGuiApplicationPrivate::processMouseEvent (e=0x555556c64410) at kernel/qguiapplication.cpp:2282
https://github.com/gridcoin-community/Gridcoin-Research/pull/32 0x00007ffff5d1c675 in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x555556c64410) at kernel/qguiapplication.cpp:2002
https://github.com/gridcoin-community/Gridcoin-Research/pull/33 0x00007ffff5cf444b in QWindowSystemInterface::sendWindowSystemEvents<EMAIL_ADDRESS>at kernel/qwindowsysteminterface.cpp:1169
https://github.com/gridcoin-community/Gridcoin-Research/pull/34 0x00007fffe7d49d0a in xcbSourceDispatch (source=) at qxcbeventdispatcher.cpp:105
https://github.com/gridcoin-community/Gridcoin-Research/pull/35 0x00007ffff04797fb in g_main_dispatch (context=0x7fffe0005000) at ../glib/gmain.c:3381
https://github.com/gridcoin-community/Gridcoin-Research/pull/36 g_main_context_dispatch (context=context@entry=0x7fffe0005000) at ../glib/gmain.c:4099
https://github.com/gridcoin-community/Gridcoin-Research/pull/37 0x00007ffff0479ba0 in g_main_context_iterate (context=context@entry=0x7fffe0005000, block=block@entry=1, dispatch=dispatch@entry=1,
self=) at ../glib/gmain.c:4175
https://github.com/gridcoin-community/Gridcoin-Research/pull/38 0x00007ffff0479c2c in g_main_context_iteration (context=0x7fffe0005000, may_block=may_block@entry=1) at ../glib/gmain.c:4240
https://github.com/gridcoin-community/Gridcoin-Research/pull/39 0x00007ffff549102c in QEventDispatcherGlib::processEvents (this=0x55555652c740, flags=...) at kernel/qeventdispatcher_glib.cpp:423
https://github.com/gridcoin-community/Gridcoin-Research/issues/40 0x00007ffff542d48a in QEventLoop::exec (this=this@entry=0x7fffffffc2a0, flags=<EMAIL_ADDRESS>at kernel/qeventloop.cpp:232
https://github.com/gridcoin-community/Gridcoin-Research/pull/41 0x00007ffff5436cc7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1375
https://github.com/gridcoin-community/Gridcoin-Research/pull/42 0x00007ffff5d0ff9c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867
https://github.com/gridcoin-community/Gridcoin-Research/pull/43 0x00007ffff666e315 in QApplication::exec () at kernel/qapplication.cpp:2824
https://github.com/gridcoin-community/Gridcoin-Research/pull/44 0x00005555555235ff in StartGridcoinQt (argc=, argv=0x7fffffffd8e8, app=..., optionsModel=...) at qt/bitcoin.cpp:698
https://github.com/gridcoin-community/Gridcoin-Research/pull/45 0x0000555555507a75 in main (argc=, argv=0x7fffffffd8e8) at qt/bitcoin.cpp:530

Thank you