Sharing pre-trained weights

Is there any plan to share the pre-trained pth for such models?

We have uploaded our pre-trained models, please refer to this link.

Amazing, thank you so much!


Template variable error

Describe the bug
it is not really a bug, but an error that appears in the log every time I restart HA
Configuration
Do you configure the integration in YAML or Config Flow (GUI)? :
YAML
sensors:

name: "General Waste" # Each week on Sunday
frequency: "weekly"
collection_days: sun
move_country_holidays: AU
state: AU
prov: VIC
name: "Recyclable Waste" # Every fortnight on Sunsday
frequency: "every-n-weeks"
collection_days: "sun"
period: 2
first_week: 1
move_country_holidays: AU
state: AU
prov: VIC
name: "Garden Waste" # Every other fortnight on Sunsday
frequency: "every-n-weeks"
collection_days: "sun"
period: 2
first_week: 2
move_country_holidays: AU
state: AU
prov: VIC

Error log/debug information
Logger: homeassistant.helpers.template
Source: helpers/template.py:1791
First occurred: 17:04:10 (585 occurrences)
Last logged: 17:04:18
Template variable error: 'None' has no attribute 'attributes' when rendering '{{ states.sensor.general_waste.attributes.days }} days'
Template variable error: 'None' has no attribute 'attributes' when rendering '{{ states.sensor.garden_waste.attributes.days }} days'
Template variable error: 'None' has no attribute 'attributes' when rendering '{{ states.sensor.recyclable_waste.attributes.days }} days'
Screenshots
Version
Integration version: 3.21
Home Assistant version: 2021.12.3 (docker)

Use the template {{ state_attr('sensor.general_waste','days') }} days etc instead.
see https://www.home-assistant.io/docs/configuration/templating/#states


File creation dates and times not preserved during tansfer

The values for created, last_modified, and last_read are not used when receiving files. Instead the values should be set for the files, preserving the values from the source.

This doesn't appear to be working on Windows.


Emacs

[x] Does .emacs get added to this repo? I think so.

Actually, no. It should be a separate repo completely
That repo gets cloned to .emacs.d/

[x] So, migrate from .emacs => .emacs.d/init.el s.t. the init file is also in the Emacs repo

Would provide an emacs state/context which could migrate between (potentially virtual) machines.

Some of that info is personal and so does not belong in a public repo. So, move .emacs out of this repo.

In 2020-03, forked out to separate repo, doc_emacs.d.


upgrade zlib include dir

fix zlib include dir error.
@siddontang @BusyJay @disksing PTAL

LGTM

LGTM


Additional caveats of go mod syncer

          @abdullah1308 please add your caveat notes.

Originally posted by @leecalcote in https://github.com/meshery/meshkit/issues/343#issuecomment-1672218214

@abdullah1308 didn’t complete this.


Test passes with typo in <link href ..> that prevents Lobster font loading

Challenge Import a Google Font has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
Notice in the <link href ...>  there is a typo...  ref="stylesheet" should be rel="stylesheet"
This prevents Lobster from loading, the web page preview never renders Lobster font
Yet, clicking run test proceeds with a pass and we move on
My code:
<link href="https://fonts.googleapis.com/css?family=Lobster" ref="stylesheet" type="text/css">

CatPhotoApp

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.

I could not pass the challenge with the typo, is Lobster installed locally on your machine?

Not that I know of.. I just tried it again.. Opened CodeCamp.. used Map to navigate to Import Google Font task, it was in the completed state with Lobster loading and rendering
Edited the   my changing "rel"  to "ref" and the rendering of Lobster font stopped in preview but Run Test still passes.
Where do I find in Lobster is loaded on my machine?

Even when I only use this link statement it still passes the test...

It appears there are problems in the validation of the import statement. I imported a different google font "Anton" like this...

and applied it to the h2 element like this...
h2 {
font-family:Anton;
}
and the test shows I passed the Import font step but failed the h2 element using Lobster. The import font step should have failed!  I imported the wrong font.


Add apache reverse proxy documentation.

Also includes a docker-compose example, and minimal vhost configuration.

Thanks for testing this! I'm not so sure about maintaining the whole Apache setup from this PR though (Dockerfile, full Apache config + Vhost config). I think it would be enough to just inline the virtual host config into the Readme details section as an example. Alternatively you could put the setup in your own repo, and we can link to that from the Readme. What do you think?

Thanks for testing this! I'm not so sure about maintaining the whole Apache setup from this PR though (Dockerfile, full Apache config + Vhost config). I think it would be enough to just inline the virtual host config into the Readme details section as an example. Alternatively you could put the setup in your own repo, and we can link to that from the Readme. What do you think?

That makes sense. Let me re-work this PR as you suggest:

add the virtual host config to the ReadMe
Create a tag in my repo in the branch with the docker compose setup
add a link in the ReadMe to the configuration in my repo

Thank you for the suggestion!

This PR now only includes updates to the Readme. If you don't like the link to my repo, we can just cut out the last commit.

Looks good, thanks.


Make dropdown list optional for Combobox component

@fspoettel As discussed I'll close this pull and make use of a custom EmailCombobox component.


Fix phylo workflow

Phlyo workflow is not currently integrated into the main workflow, or accessible at all. Fix this

Currently, the only part of the phylo workflows that runs by default is panaroo. This is caused by the following (in phylo.nf):
// By default, run panaroo
        else{
            PANAROO_RUN(gffs.collect{ meta, gff -> gff}.map( gff -> [[id: 'panaroo'], gff]))
            ch_core_gene_alignment.mix(PANAROO_RUN.out.aln.collect{meta, aln -> aln })
            ch_software_versions = ch_software_versions.mix(PANAROO_RUN.out.versions.ifEmpty(null))
        }

ch_core_gene_alignment is created as an empty channel and, after using the .mix() operator, it doesn't get reassigned, therefore it's sent forward as an empty channel - causing all following modules to not run.
Simple fix would be to reassign the result to ch_core_gene_alignment again, but that's somewhat repetitive - a better fix is to forgo creating an empty channel at first - setting the variable from the output of panaroo (like done in #21).


Rating improvements

Adds rating based on up/downvotes on detail and partial blades
Adds up/down votes to details blade for non-logged in requests
Adds database migration for calculating rating (for use in queries)
Adds Top Voted route and moves the Top X items in the navbar to a submenu

For reference, this is the rating algorithm used.
It was chosen because it satisfies two major requirements:

Beatmaps with more reviews should have an adjusted rating that is closer to their real rating, because the more reviews we have, the more certain we are that the score they give us is correct.
All ratings should be biased towards the average rating — 50%.


MDX Hot reloading

It's not yet clear to me why hot reloading of md files doesn't work as it normally would with Gatsby/requires a server restart at times. Requires investigation.

Hi @renvrant,
Thank you for creating this starter 👍  Do you have any clues about this issue. I would be glad to investigate 😄


Closes #219 | Create dataloader for scb-mt-en-th-2020

Please name your PR after the issue it closes. You can use the following line: "Closes #219 " where you replace the ISSUE-NUMBER with the one corresponding to your dataset.
Checkbox

[ ] Confirm that this PR is linked to the dataset issue.
[ ] Create the dataloader script seacrowd/sea_datasets/my_dataset/my_dataset.py (please use only lowercase and underscore for dataset naming).
[ ] Provide values for the _CITATION, _DATASETNAME, _DESCRIPTION, _HOMEPAGE, _LICENSE, _URLs, _SUPPORTED_TASKS, _SOURCE_VERSION, and _SEACROWD_VERSION variables.
[ ] Implement _info(), _split_generators() and _generate_examples() in dataloader script.
[ ] Make sure that the BUILDER_CONFIGS class attribute is a list with at least one SEACrowdConfig for the source schema and one for a seacrowd schema.
[ ] Confirm dataloader script works with datasets.load_dataset function.
[ ] Confirm that your dataloader script passes the test suite run with python -m tests.test_seacrowd seacrowd/sea_datasets/<my_dataset>/<my_dataset>.py.
[ ] If my dataset is local, I have provided an output of the unit-tests in the PR (please copy paste). This is OPTIONAL for public datasets, as we can test these without access to the data files.

Hello reviewers,
In addition to the PR, I would like to report that the DataCatalogue link in #219 does not work.
Instead, I found this link works for this dataset: https://seacrowd.github.io/seacrowd-catalogue/card.html?scb-mt-en-th-2020.
Therefore, one clarification: Should the dataset name be scb-mt-en-th or scb-mt-en-th-2020?
I think the dataset name reported in the title, card, and dataloader name should be unified.
Please let me know which dataset name is the correct one.

Hello reviewers,
In addition to the PR, I want to let you know (as reported in the comment section of issue #219) that the DataCatalogue link cannot be opened from here. Instead, I found this link works for this dataset: https://seacrowd.github.io/seacrowd-catalogue/card.html?scb-mt-en-th-2020.
Therefore, one clarification: Should the dataset name be scb-mt-en-th or scb-mt-en-th-2020? (UPDATE: it will be implemented with the snakecase dataloader name) I think the dataset name reported in the title, card, and dataloader name should be unified. Please let me know which dataset name is the correct one.

Hi @jen-santoso, let's stick with scb_mt_en_th.
I'll run this by @SamuelCahyawijaya to see what triggers the incorrect URL being generated.


Conductor download all

What Changed

Added an option to download all, along with documentation for the new view method

Issues

Fixes #577

Screenshots

:+1:
What are the columns in the tsv when you download all?

It's in the docstring for the method:

Returns:

   A tsv follow with the following fields: the contract's id

   (item_number) contract's parent id (parent_item_number),

   the contract's description (description), the contract's

   expiration date (expiration_date) the contract parent's

   expiration date (parent_expiration), the department name

   (department), the assigned user's email address (assigned_to),

   the contract's spec number (spec_number), the contract

   parent's spec number (parent_spec), and a string with

   the status of a contract

LGTM

Great, LGTM


mobile compatibility

[x] should report no error if opened on mobile
[x] should be able to purchase credit on mobile side

[ ] refresh the status automatically
[ ] mobile button logic


relocate Circuit Maintenance menu items under Circuit menu

Proposed Functionality
Not sure this was ever discussed, but it just seems logical to navigate to Circuits -> Circuit Notifications vs. Plugins -> Circuit Notifications.  Assuming URL doesn't change, why not?

Will get this in and release a 1.0.0 for this

duplicate of #202?

This is done


UNDERTOW-1476: Fix URLDecodingHandler when query string is empty

Added test cases to prevent future regressions.
This PR is the most important subset of #710

Closing in favor of #710


fix ingress.main.className for echo-server

echo-server failed to deploy using the ingress.main.ingressClassName setting from the template. Changing this to ingress.main.className allowed the service to deploy successfully.

I did create this feature request though on the library chart.
https://github.com/bjw-s/helm-charts/issues/139


[Feature]: Removing the Cap on Run Comparer

Description

It seems that Run Comparer is capped at ten runs.
This is even the case in the official example below.
https://wandb.ai/stacey/pytorch_gan_tutorial/reports/Run-Comparison-Table--VmlldzozNTM0Nw
Suggested Solution

Remove the Cap on Run Comparer :)
Benefits
Comparing different runs, especially in large projects.

Hi @MoH-assan , thank you for your request, could you also please share how this feature will impact your workflow so we could add it up when we file the Feature Request.

Thank you for the update @MoH-assan , filed it as a Feature Request and will update  you for any progress.


Error on One Click Heroku deploy

Since this evening, I've been getting the following error in Heroku logs:
`2021-04-09T21:10:40.492566+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2021-04-09T21:10:40.656931+00:00 app[web.1]: Fetching latest Lavalink.jar url...
2021-04-09T21:10:41.220446+00:00 app[web.1]: Error occured when fetching latest release url: TypeError: Cannot read property 'browser_download_url' of undefined
2021-04-09T21:10:41.323897+00:00 heroku[web.1]: Process exited with status 0`

I believe it is caused by latest release not having the Lavalink.jar attached.
I've implemented a check which will download the prior release if the latest release is not available.


xds/client: fix node metadata keys

Use the expected key names for namespace and instance IPs so the data is correctly unmarshalled in Istiod.

Hi @shashankram. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test


CS0029 - @ref causes compilation error see #17416

https://github.com/dotnet/AspNetCore.Docs/issues/17416
Removing the @ref makes it compile. eg
<AgentFullRecord @ref="agentForm" Agent="@selectedAgent" OnChanged="OnChanged" />
does not compile, but
<AgentFullRecord Agent="@selectedAgent" OnChanged="OnChanged" />
does
I have created an issue from this page as it referes to @ref, I cant find a more relavent one. its an easy issue to recreate. Read #17416. Instructions say to add comments to an existing issue even if its closed.

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

ID: 60c195c0-99f6-64f5-66a3-4e69109dc8ee
Version Independent ID: 24368808-4b90-f75a-e887-eb72a1c85f5b
Content: Build reusable UI components with Blazor
Content Source: docs/architecture/blazor-for-web-forms-developers/components.md
Product: dotnet-architecture
Technology: blazor
GitHub Login: @danroth27
Microsoft Alias: daroth

As a temporary solution, SDK 7.0.202 can be used

Yes, I also downgraded to lower "version": "7.0.203" for work around.

Hi folks. We believe this is a duplicate of https://github.com/dotnet/razor/issues/8718, which we are working to get addressed.

I'm facing the same issue.  Why is this closed?
Removing the @ref makes it compile. eg
<AgentFullRecord @ref="agentForm" Agent="@selectedAgent" OnChanged="OnChanged" />
does not compile, but

does
WHAT'S THE WORKAROUND?

@mrs99mrs99 I'm not able to reproduce this issue with VS 17.8.3. Can you create a small repo with a project that reproduces the problem you are seeing and share it with us?

To confirm, this now works for me (as of June).
From: mrs99mrs99 @.>
Sent: Wednesday, January 3, 2024 10:47 PM
To: dotnet/docs @.>
Cc: John Price @.>; Author @.>
Subject: Re: [dotnet/docs] CS0029 - @ref causes compilation error see #17416 (Issue #35449)
I'm facing the same issue. Why is this closed?
Removing the @refhttps://github.com/ref makes it compile. eg
<AgentFullRecord @refhttps://github.com/ref="agentForm" @.***" OnChanged="OnChanged" />
does not compile, but
does
WHAT'S THE WORKAROUND?
—
Reply to this email directly, view it on GitHubhttps://github.com/dotnet/docs/issues/35449#issuecomment-1876073357, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAJBQTRHPNCO6JK56STJMFDYMXNU5AVCNFSM6AAAAAAYLNGFDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWGA3TGMZVG4.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

I have removed all irrelevant code from my solution and have attached it as a zip.   The @ref is located in Teams, Pages, Organization, CreateOrganizationComponent.razor file.  Any help would be greatly appreciated.
Teams.zip

@mrs99mrs99 Thanks for sharing your project. When I build your project, I get the error: "The type name 'PopUp' does not exist in the type 'Teams'". The project defines both the global namespace Teams and a Teams component type. The _Imports.razor has an @using directive for global::Teams to differentiate between the two, but it looks like this isn't being handled correctly by the Razor compiler. If I rename Teams.razor to something else and change the @using directive to not be globally qualified, then the project compiles.
Since this appears to be a different issue than the original @ref issue discussed here, could you please open a new GitHub issue for this in the dotnet/razor repo? Also, instead of sharing the code as a zip file, it would help if you could share it as a GitHub repo.


I only want to format staged files, not linting
It possible with prettier, but prettier has limited functionality
Thx

There's this bit in our README about reformatting with eslint, would it work?
https://github.com/okonet/lint-staged#automatically-fix-code-style-with---fix-and-add-to-commit

@iiroj
This works, but if eslint finded errors this will stop the commit process
I want only to fix and continue, despite errors

I handled this by making this file:
const CLIEngine = require("eslint").CLIEngine;
const cli = new CLIEngine({
  fix: true,
});

const [,, ...files] = process.argv;
if (files.length) {
  const report = cli.executeOnFiles(files);
  CLIEngine.outputFixes(report);
}

process.exit(0);

and then run this via lint-staged (instead of eslint --fix:
    "src/**/*.js": [
      "node ./eslint-fix-only.js"
    ]
  },

@bman654
Thanks, I'll try!


usage of the Post process material

Hi,
I saw the recently update on the post process material domain. Some of the post processing shaders have been converted to this domain like ssao, blur etc. May i know will this be used to support custom post process step in future? If not, what can i do if i  would like to support custom post processing?
Thanks & Regards,
chengzg

The goal is to make custom post-processing available in the future yes. We need to figure out how we want to expose the FrameGraph API.

Any update on this? Could you perhaps provide a sketch of how one could do post processing now before the exposure of frame graph?
Is there a way to use the post process material without the frame graph?

You can do post processing by rendering to a texture and then rendering with that texture and custom material on the main surface. There was a bloom sample showing how to do this.

How do I render to two targets from one material definition?

If anyone is looking for the bloom sample: https://github.com/google/filament/tree/e8a7d9f0c29b26dd028306d27e4e6d44dd25b1fa/android/samples/sample-gltf-bloom


LVM - Thin volume creation not working with snap version of LXD 4.1

Yesterday, on a freshly installed Ubuntu 18.04 LTS server, on physical hardware, I installed the snap package for LXD. I then went on to manually create a LVM thinpool that I added as a storage device in LXD and referenced it in the default profile.
I think I lost 3 hours on this but there was simply no way I managed to get LXD to create a new thin volume. LXD always created a LVM loopback device when launching a new container.
I uninstalled the snap version, installed LXD via apt (in version 3, of course), didn't touch the existing thinpool at all, and ran the exact same configuration. LXD would create new volumes now without issues.
I'm not sure if this is an issue with version 4.1 or the snap version in general but at any rate, I couldn't get thin volume creation to work.

Please can you show us the commands you ran and the error you got. Thanks

Hi Tom, thanks for getting back to me so quickly.
# lxd init (defaults, without configuring storage)
# lvcreate -L 200G --thinpool lxdthin vg0
# lxc storage create lvmthin1 lvm source=vg0 lvm.use_thinpool=true lvm.vg.force_reuse=true lvm.thinpool_name=lxdthin
# lxc profile device add default root disk path=/ pool=lvmthin1
# lxc launch ubuntu:18.04 c1

Works with the apt version, does not work with 4.1 snap.

Ok thanks. So what indicates to you there is a problem?

As described, no thin volume is created, just a loopback device.
This is how I'm expecting it to look after creating container c1:
root@sb32 ~ # lvs
  LV                                                                      VG  Attr       LSize   Pool     Origin                                                                  Data%  Meta%  Move Log Cpy%Sync Convert
  containers_c1                                                           vg0 Vwi-aotz--  10.00g lxdthin  images_235aa7210a0821ff12ebf376dd119388a7aa1cdff4fc40752d7d8cbf3507b417 33.49
  images_235aa7210a0821ff12ebf376dd119388a7aa1cdff4fc40752d7d8cbf3507b417 vg0 Vwi-a-tz--  10.00g lxdthin                                                                          5.84
  lxdthin                                                                 vg0 twi-aotz-- 200.00g                                                                                1.75   11.32

The thin volumes are never created, though. This example is taken from the same machine with the apt version of LXD 3 installed.

Ok so the container fails to start presumably?

No, the container starts fine. As mentioned, there are no errors whatsoever, everything works. It just doesn't use the storage backend it's supposed to.

It's almost certainly doing the right thing, you just don't see it because the snap has its own LVM which does not share cache with the host one.

Can you run pvscan and pvscan --cache on the host, then look at lvs again see if maybe things are showing up now?

Hi Stéphane, I guess that's possible and it would explain why I didn't see any errors. I can't check now since I already moved on to the apt version of LXD. How complicated is it to update to the snap version again, is this a seamless process, would my containers just keep working as is? The machine is now in production so I wouldn't want to risk more than 15 minutes of downtime.

The process is pretty straightforward with 'snap install lxd --channel=4.0 && lxd.migrate' but it will shut down all containers and perform a major upgrade from 3.0 to 4.0 on top of the deb to snap data migration.
So it's fast but with a lot of moving pieces.

I'll close this issue as we have an open packaging issue about the out of sync cache behavior on the packaging side.
If you decide to go with the migration, let us know if everything behaves as expected.


Add hr style

It's great to be able to write html with little thought to style and classes. I like using
 to break up content. I tried to keep with the simple style.

In semantic HTML,
 is defined only as representing a thematic break in content, not as a visual line. I tried and failed to have
 render as double space between paragraphs, but that will be fixed with #14 (in progress).

Any kind of break will do. I'm glad
 is coming. Thanks!


private classes should still have documentation

It is common to provide a group of static functions defined on a particular "utility" class, but the constructor is marked @private so that no instance of the class can be made.  Another usage of this is the Singleton pattern, where the constructor is used to make the singleton instance, but the constructor is private to ensure no one else can make an instance.
In the version prior to v0.7.0 this was working perfectly: on a class whose constructor is marked @private

the class description is shown;
the constructor documentation is absent;
the (public) static functions are shown.
the (public) instance methods are shown

In the current version, a class whose constructor is marked @private is not documented at all.
For example, here is how such a class was shown in the prior version:
class JointUtil
------------------

struct
Provides utility functions for creating Joints.

Static Functions
--------------------

JointUtil.addSingleFixedJoint(sim, body, attach_body, normalType, normal)

Creates a single Joint to attach a RigidBody to a fixed point on the myphysicslab.lab.engine2D.Scrim, at the current world position of the attachment point.

Parameters
sim myphysicslab.lab.engine2D.ContactSim
the ContactSim to which the Joint is added

body myphysicslab.lab.engine2D.RigidBody
the RigidBody to add joints to

...rest omitted...

Here is the definition of that class
/** Provides utility functions for creating {@link myphysicslab.lab.engine2D.Joint
Joints}.

@constructor
@struct
@private
*/
myphysicslab.lab.engine2D.JointUtil = function() {
  throw new Error();
};

If I remove the @private directive from the constructor, the class is documented as before, without the constructor (but with class description and static functions), even though the constructor is presumably public. But this is related to issue #37

This is due to changes related to #26

For me this is all working fine and this "bug" could be closed.  I believe that this commit fixed it:
e5e70f46917ba2777848d1e9bb7840145f456b7d


Replace criticalcss with penthouse

Honestly, not sure i this is truly necessary.  I did a lot of debugging and changing things both with here on the server with criticalcss/penthouse and in the ruby gem.  The first working solution I got had this branch running (and I currently have it live in prod).  I'm somewhat unfamiliar with the difference between criticalcss and penthouse - though, it seems that criticalcss hasn't seem a commit in almost a year and penthouse is more actively developed.
So, if you want to give it a shot and merge it, here ya go! :)

Interesting - you have this working in production now? I can pull it down and try it out.
Worth noting that the phantomjs project has been abandoned by it's maintainer; https://www.infoq.com/news/2017/04/Phantomjs-future-uncertain. Would be good to see which critical css libraries switch to chrome headless and migrate to that!

Got this merged and am using it in my production app; seems to be a pretty painless transition, thanks for your help!


Add support for Boa in addition to (or instead of) QuickJS

Hello.
It looks like Boa’s conformance with test262 is on part with QuickJS now. Would you be open to adding support for Boa in functions, perhaps behind a feature flag?
Thanks.
https://boajs.dev/blog/2024/03/07/boa-release-18
https://github.com/boa-dev/boa
https://test262.fyi/

Hi @yerke,
Those are some amazing news, thanks for bringing this to our attention as we've wanted to use Boa in the past.
We will have a look at this. It might take some time as we have a lot of things going on in the background. What I had a quick look at:

Size - Boa will increase the engine size by ~4MB which is mostly acceptable
Performance - For simple expressions it looks great, but when we need to "pre-compile" modules the performance takes a dive.

Some questions on performance if you are familiar with boa (@yerke):

Are we able to pre-compile JavaScript modules such as day.js and big.js? (this is essentially serialisation of the context/module state)
Are we able to limit the time of Boa.JS context without spawning a new system thread? I'm happy with using tokio green threads if that's possible?

We’re also excited about potential prospect of bringing the full business rules engine into browsers through WASM.

Hi @stefan-gorules,
I am not very familiar with Boa myself, unfortunately. I am mostly interested in it from the point of making Gorules easier to build/consume.
I did read their docs and examples a bit to help answer your questions.
Re compilation of JS modules: Boa provides API to load, link, and evaluate modules: https://docs.rs/boa_engine/latest/boa_engine/module/struct.Module.html#method.load
Example of using modules: https://github.com/boa-dev/boa/blob/main/examples/src/bin/modules.rs
Re runtime limits: I have seen they mention it in their blog post: https://boajs.dev/blog/2024/03/07/boa-release-18#runtime-limits

Boa devs in the Discord channel said that link method actually does compiles modules to the bytecode.

I see. Based on this example https://github.com/boa-dev/boa/blob/main/examples/src/bin/modules.rs it seems that you still need Context in order to link (and therefore compile) a module. And from what I can tell based on the docs, there's no way to Clone a Context or create a base VM snapshot that can be serialized / deserialized for quick re-use.
Our ideal approach is mostly aligned with what LLRT by Amazon is trying to achieve, just in context of rules engines and workflows.

@stefan-gorules If I understand correctly, you can just clone Module struct and then it will be reused. Boa devs told me the same:

as long as you keep using the same Module object, the module will reuse the same bytecode.


[search-field] Nightwatch => Wdio

Summary
Converted Nightwatch tests to WebdriverIO, removed a duplicate test page, and added clickable text to a couple of test pages.
Accessibility issues logged in #1370
Additional Details
Part of #1302
Thanks for contributing to Terra.
@cerner/terra

While no test is explicitly is named as such, Callback, Auto Search Delayed, and Minimum Length all test Auto Search being enabled.


Correctly elide type annotations

If we write something like:
id (a: t) (b: t) -> t = b

This should be the same as writing:
id a b: t -> t -> t = b

That is, the type variable t across the annotations for a, b, and the return type should be quantified as the same name.
However, the lowering pass lowers these as three separate type annotations, which means they technically become separately quantified, since they reside in three separate type annotations.
I fear this kind of scoping might be tricky to get recover in the type-checking phase, so I should fix the lowering phase to collapse the three annotations into a single type annotation.
@XijiaoLi  something to keep in mind while you work on type inference; to be safe, stick with the postfix type annotation syntax (using :) for now.

Isn't that just a scope-of-type-variables issue? @j-hui doesn't your "scoping" pass go through and make all names globally unique by assigning them, say, a unique integer? The same thing should be done with type variables.

My scoping pass does not do that---it just checks that everything is scoped correctly. I can easily change it to name mangle the program but I haven't seen a need for that yet.

This is being handled in #103


[BP-1.11][FLINK-18539][datastream] Fix StreamExecutionEnvironment#addSource(SourceFunction, TypeInformation) doesn't use the user defined type information

What is the purpose of the change
Fix StreamExecutionEnvironment#addSource(SourceFunction, TypeInformation) doesn't use the user defined TypeInformation as the output type of the DataStream.
The root cause is that StreamExecutionEnvironment#getTypeInfo doesn't use the user defined typeInfo if SourceFunctin implements ResultTypeQueryable. But the priority of user defined type info should be the highest.
Brief change log

Fix StreamExecutionEnvironment#getTypeInfo to use ResultTypeQueryable#getProducedType only if user defined type is null.

Verifying this change

Added an unit test for this

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @becketqin , this is a cherry-pick back to release-1.11 branch.

@flinkbot run azure

Build is passed, merging...


PWA Module breaks Nuxt Devtools Module

I haven't gotten to the specific root of the issue, but using both the PWA module and the Devtools module results in the devtools module functionally breaking and entering a redirect loop. Disabling SW network intercept or removing the PWA module resolves the issue.
Broken:

Working:

It looks like the service worker is doing something very bizzare to the iframe that the devtools loads.

/__nuxt_devtools__/client/modules/overview, though I believe it loads a different path under /__nuxt_devtools__/client/* initially.

dev plugin is using /^\/$/: https://github.com/vite-pwa/vite-plugin-pwa/blob/main/src/plugins/dev.ts#L135

are you using custom service worker (injectManifest strategy)?

Ah, this may have been a copy pasta fail on my part. Somehow navigateFallback got set to / in my config. Apologies!

@RichiCoder1 so, can this be closed?


Allow empty metric help

This is necessary for prometheus compatibility, which has optional HELP section.

I am concern about other encoders that depends on this value from a code and payload perspective.
What about if we only check that "help" is not NULL but instead for the caller we force them to set an empty string like "" ?

I am concern about other encoders that depends on this value from a code and payload perspective.

I did check existing encoders to make sure NULL description is handled. Only msgpack encoder needed some modification, text/influx encoders don't seem to use description. Opentelemetry uses description, but it already handles NULL values.

since we need to do a release shortly let's keep it simple, I prefer we don't touch the encoders for now


Previously, DPlayer.min.js is 126KB, now DPlayer.min.js + DPlayer.min.css is 80KB

Thanks, big lao!

btw, this line will be removed sinc webpack strips all console.log now, you can adjust it a bit to preserve that.

And the docs should also be updated since DPlayer.min.css is required now.

Done! Thanks!


Umbrella Issue for Features of CLI MVP version

Basic Usage

[x]   version:     show your current cli version #40
[x]   env:     set your environment #57
[x]   ls:  list your apps  https://github.com/cloud-native-application/RudrX/issues/34 https://github.com/cloud-native-application/RudrX/pull/56
[x]   show:     get detail spec of your app https://github.com/cloud-native-application/RudrX/issues/58  @erdun
[x]   status:     get running status of your app https://github.com/cloud-native-application/RudrX/issues/59
[x]   delete:     remove your app https://github.com/cloud-native-application/RudrX/issues/6
[x]   workloads:     list all workload types #62
[x]  rudr <workload-type>: run <appname> : eg:   rudr deployment:run myapp #63
[x]   traits:    list all trait types  #8 #60
[x]  rudr <trait> <appname>:    eg:	rudr route myapp --domain myapp.com https://github.com/cloud-native-application/RudrX/issues/18

[x] bind #72
[x] unbind  #73

[x] Update Readme

Advanced Usage:

[x] support CUE as definition template file #35 @wonderflow
[x]   ~appset:   bundle your apps~ #20 （we don't support this feature in MVP）
[x]   ~snapshot:     make a snapshort for your app~  #37 （we don't support this feature in MVP）
[x]   plugins:   discovery/install plugins https://github.com/cloud-native-application/RudrX/issues/19 @zzxwill
[x]   dashboard:     run a dashboard locally @ryanzhang-oss  https://github.com/cloud-native-application/RudrX/pull/154
[x]   completion:     build auto completion shell script #88 @sunny0826
[x]   admin:   administrator operations, like install/init  https://github.com/cloud-native-application/RudrX/issues/12

add a issue #88  for completion and accept it

Closing as all of them has been done.


Broken Link Checker shows links in languages that are disabled

Describe the Bug
The broken link checker shows broken links that still exist in disabled languages
Steps to Reproduce

Go to https://admin.integreat-app.de/deutschlandvorlage/analytics/linkcheck/invalid/
Hover over the link for the source or click on it
See that it links to bulgarian content

Expected Behavior
Link should not show up bcs language is disabled (not just invisible)
Actual Behavior
Link in Bulgarian is shown
Additional Information

I'm pretty sure that this should be an infra ticket.
We can still check for bugs in the code base, but I think the race conditions are responsible for this inconsistent state and we need to rebuild the link database on the production server.

Ahh, but if it is only limited to disabled languages, it might be actually a valid ticket, sorry.
I guess we did not think about deleting all links when disabling a language and to re-create them when enabling a language? 🤔


typo correct

typo correct: extrat "to" removed

Thanks for this. :bow:
Have included it in one of the doc update PRs that needed to run all the CI anyway to speed things up.


Does this support for v 39?

Does this support for v 39?
I used the caddy for a simple server, but i see "alt-svc:quic=":443"; ma=2592000; v="38,37,36,35"" from the response header.

Yes, we've been supporting Q039 for about half a year.
The problem is that Caddy hasn't updated its vendored quic-go for such a long time, see https://github.com/mholt/caddy/pull/1968.


Checklist for New Features

(1) When adding or modifying functionality that affects other developers, always update the readme
(2) If you've included functionality that requires that a new process is ran, the app should be configured for development, staging and production environments, and should run that process without any extra work on the developer's behalf; vagrant and capistrano, for example. This lower's the bar for other developers to merge and work on your feature! and eliminates confusion, saving time overall!

Closing this as the mentioned best practices are taken into account. Thanks!


Client Allocation Request for: ipfsidc

Client Allocation Questions
Core Information

Name: ipfsidc
Website / Social Media: ipfsidc.kr
Region: Asia excl. Greater China
DataCap Requested: 5TiB
Addresses to be Notarized: f2q73zlq7itctk4k42wkbdfgg6ze7wwxco3c4rzci
Notary Requested: steven004

@techkotha999 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Hey @techkotha999 , thanks for your interest in loading data into Filecoin network. The information you provided is helpful. And if you could provide more information to the following questions, that would be wonderful.

yourself/ your organization (with links to official website/social media/news mentions etc)
Your history working on IPFS/Filecoin (notable contributions to the community, type of engagement shown over time etc)
Use case: type/source/quantity/diversity/scarcity of the data you plan to store on Filecoin
Miners you intend to allocate DataCap with allocation proportion(with redundancy/location/specific requirement of storage miners), if you are working with a service provider to store your data to Filecoin network, please name the provider.
How could people retrieve the data you store in Filecoin Network, do you have a tool/app for it?
What's your next plan for the data you plan to store in Filecoin Network? For-profit or not?
Would you be OK in posting deal transactions here?

Thanks

Closed due to no response.


chore(NODE-5382): add 4.x release workflow

Description
What is changing?

Copied the release from main workflow
Changed the branch trigger to 4.x
Changed default-branch to 4.x
added npm tag "4x"

Is there new documentation needed for these changes?
No
What is the motivation for this change?
Automagic releases for 4.x
Release Highlight

Double check the following

[/] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: type(NODE-xxxx)[!]: description

Example: feat(NODE-1234)!: rewriting everything in coffeescript

[/] Changes are covered by tests
[/] New TODOs have a related JIRA ticket

Depends on #3747, that PR just copies the scripts to 4.x so that release_notes workflow has access to them when it checks out the release PR which was branched from 4.x not main


I added inline annotation to all the controller to fix the minification problem.

thanks, i missed this


AsyncStorage extracted from react-native core

I use RN 0.59.8 and am now seeing this warning message:
Warning: Async Storage has been extracted from react-native core and will be removed in a future release. It can now be installed and imported from '@react-native-community/async-storage' instead of 'react-native'. See https://github.com/react-native-community/react-native-async-storage

I will try to fix it recently.

Any progress on that?

Update to the latest version V3.0.1-rc.5


Changing deviceSize() to static let deviceSize

How about changing
 open func deviceSize() -> Size {
    return Device.size()
 }

to
public static let deviceSize = Device.size()

So you can use deviceSize like this
if size == DeviceLayoutConstraint.deviceSize {
    self.constant = constant
    layoutIfNeeded()
}

This change might boost up performance little bit.

Thank you for opening issue on DeviceLayout
I'm use func deviceSize() as Dependeny Injection for Unittest
in mock object, can test autolayout constant really set correct constant per device
so something to need for Unittest injecting Size
I agree that use static let variable DeviceSize for performance
because current func deviceSize() always calculate Device.size() in every constraint
it's good to use like singleton (device size never change)
if use public static let deviceSize = Device.size() can not test Unittest
alternative solution is use static var than static let but it's not good solution I think
Perspective in OOP, class Device have a responsibility for having static size of Device (once allocated or assigned) than DeviceLayoutConstraint if possible
how about use like below? :)
    //Mark: Add static let inside Static struct because func deviceSize() cause naming redeclation
    private struct Static {
        static let deviceSize: Size = Device.size()
    }

    open func deviceSize() -> Size {
        return Static.deviceSize
    }

    //Mark: unittest mock object it can test constant per expectedDevice
    class DeviceLayoutConstraintSpy: DeviceLayoutConstraint {
        var expectedDeviceSize: Size!

        override open func deviceSize() -> Size {
            return expectedDeviceSize
        }
    }

reflected in #16 thank you :)


Fancy Zone Dock to Desktop

Description of the new feature / enhancement
In OneNote there is an option in View > Views > Dock to Desktop
I would like to be able "Dock" an application to the left or right hand side of the desktop
This behavior is slightly different than current fancy zones in that the "Zone" is not available to other programs, and the monitor is effectively resized to the remainder of the area.
Another way to implement this would be create the add an "allow list" or a "deny list"
Scenario when this would be used?
When I launch certain programs, I want them to target a column zone on the side of the monitor
However, these dock style zones have limited practical application and I typically don't want them to be included when moving windows between zones,
I also want the windows in the "dock" them kept "On-Top" and readily available.
Supporting information
One example is that I want to "dock" my MS To Do app

I also want the windows in the "dock" them kept "On-Top" and readily available.

Could the new PowerToy "Always On Top" helps? /needinfo

@franky920920: I know exactly what @SomeCallMeTom refers to, and the semi-new "always on top" functionality wouldn't work for this. The "Dock to Desktop" function of OneNote is one of the most clever features of OneNote, and it'd be amazing to have something like this available for arbitrary applications. I think this is a great suggestion. Thinking about how one could implement it however hurts my brain, but in a good way .

/dup https://github.com/microsoft/PowerToys/issues/17216

sorry, /dup https://github.com/microsoft/PowerToys/issues/71


to #9801: fix delete job of quartz not work

https://github.com/apache/dolphinscheduler/issues/9801

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.0.6-prepare@7d91ad3). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 839f4f4 differs from pull request most recent head 6246bd6. Consider uploading reports for the commit 6246bd6 to get more accurate results

@@               Coverage Diff                @@
##             2.0.6-prepare   #10645   +/-   ##
================================================
  Coverage                 ?   20.90%
  Complexity               ?     1602
================================================
  Files                    ?      540
  Lines                    ?    22841
  Branches                 ?     2714
================================================
  Hits                     ?     4776
  Misses                   ?    17574
  Partials                 ?      491

Continue to review full report at Codecov.

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

This is strange, this PR doesn't change the dependency, but the license check failed.


I have a few questions.

Hello. I have a few questions and posted them here.
Questions:

When I build a standalone cluster with Flink, if I put the lib folder of alink into the lib folder of Flink other than jobmanager, I cannot connect to jobmanager.
Is it OK to put the lib folder of alink into the lib folder of Flink only on the jobmanager side?

I'm currently doing machine learning, but I'm not sure if the data is too large, or if "An error occurred while calling z:com.alibaba.alink.common.utils.OperatorCsvCollector.collectToCsv.
: org.apache.flink.shaded.netty4.io.netty.handler.codec.TooLongFrameException: Response entity too large: DefaultHttpResponse( decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Access-Control-Allow-Origin: *
The error message "content-length: 118885457 Try to raise [rest.client.max-content-length]" will be displayed.
I followed the message and set "rest.client.max-content-length:600000000" in jobmanager and each taskmanager, but it did not improve the situation.
How can I fix this problem?
jobmanager_log.txt
taskmanager_<IP_ADDRESS>_52178-5e5e89_log.txt
taskmanager_<IP_ADDRESS>_54290-a0709a_log.txt

For the second problem, what is the total size of your data? Could you give an estimation?
And which way to use PyAlink?  useLocalEnv or useRemoteEnv or else?
As for the first problem, what do you mean by "cannot connect to jobmanager"? Are there any exceptions?

Answer from the first question.
The size of the data set is 137MB.
I am trying to use PyAlink's "VectorAssembler" and "SVC" to perform binary classification.
I am using useRemoteEnv to connect to the cluster.
The answer to the following question is that I have downloaded the jar file from PyAlink and put it in the lib folder of Apache Flink. /bin/taskmanager start" from the taskmanager side to connect to the jobmanager.
If I don't put the jar file from PyAlink in the lib folder of the taskmanager side, it works fine.
Sorry for my poor English...

The cause of this problem was that I didn't put the config in remoteEnv() config. I've solved the problem and will close it.
I'm sorry to have taken up so much of your time.


Vector test failing on powerpc

Hi, it seems that the VectorTest.Destructor test is failing on Debian's powerpc and powerpc64 architectures :/
I have not looked into the issue, but I guess that this might be related to ppc's big endianness.
You can find the logs for both here:

https://buildd.debian.org/status/logs.php?pkg=zycore-c&arch=powerpc
https://buildd.debian.org/status/logs.php?pkg=zycore-c&arch=ppc64

More generally, the build logs for all architectures are here: https://buildd.debian.org/status/logs.php?pkg=zycore-c

Yeah, big-endian is currently completely unsupported and this would require fixes all over the code-base.

Oh ok, thanks for the fast reply! powerpc isn't an "official" Debian architecture, so this isn't really a big deal. Feel free to close this, or to keep it open as a kind of todo item :)

Cool. Let's leave this open as a low priority TODO item and as a reference for other people who are wondering about the BE support status. I adjusted the title to improve discoverability.


Callback "on change"

Is there any callback function "on change"? I would like to update hidden form fields with the crop points every time the crop information changes. Thanks.

Yep - there's an update option: http://foliotek.github.io/Croppie/#update
We also trigger an update event that you can listen for with event listeners.

can give example for Venilla js croppie?


Modal opens at bottom of the screen.

Details: when using with windicss, the modal opens up at the bottom of the screen.

Seems like this has been fixed in windicss!

@gaurovsoni Yes. I just tested the latest version of Windi CSS and the modal works perfectly now 🥳


Working with keys that have '.' (dot) in it

It seems that after pull request https://github.com/matthewcheok/JSONCodable/pull/53 JSONCodable got functionality for encoding/decoding nested types (https://github.com/matthewcheok/JSONCodable/pull/53/commits/9782c0fc77679c92fcd5d9a8a082305db121e2d1). However the problem we are having is that our API JSON responses have some keys with . in them. This makes it impossible to encode (and probably parse) the JSONs using the library.
For example this JSON is not parseable correctly with the lib:
{
   "one.key" = "value"
}

Is there a way to fallback to a more low-level approach avoiding the key.components(separatedBy: ".") part in each of func encode(_ value: key:) overload?

This seems to be more of an edge case while what we optimized for seemed to be more common and expected. Your welcome to submit a PR for this functionality as perhaps an OptionSet on the JSONEncoder initializer, otherwise we will keep this in mind for potential implementation in the future.


Implement FormData.set method and handle Blob instances

Summary

The proposed changes brings FormData's implementation one step closer to spec compliance by:

Implementing .set method.
Adding support to filename argument on both .set and .append for Blob and File values.
Handling Blob instances in .getParts instead of just blob-like objects with the uri property.

Additionally, I've took the opportunity to improve FormDatas test suite overall by adding more test cases.
It's worth noting that according to the implementation of URL.createObjectURL, the call may fail if the native blob module is not available. However, I don't know which circumstances determine its availability:

Is it the native platform?
Is it the React Native version?

Changelog

[JavaScript] [Added] - Implement FormData.set.
[JavaScript] [Added] - Add support to filename argument on both FormData.set and FormData.append for Blob and File values.
Test Plan

Run the following command at the root of React Native's directory:
npm t -- FormData-test.js

Any chance we can get some feedback with this ?


Removed EpochsVectorizer from docs

Closes #3673

@kingjr merge if you're happy

@Eric89GXL Appveyor isn't happy, shall we discard it?

Sorry I missed the ping. Yeah it should be okay

Thanks @kaichogami !


added missing props to API description

I added the missing Props wrapperClassName, animationDuration and animationEndStyle to the API section of README.md

Thanks for helping! ❤


Potential improvements to docs

Hey @arthurfiorette, great work here! It's very exciting to have a way to provide TS type definitions, it was a huge sticking point to working with JSON columns in Prisma.
While setting it up for $WORK, I ran into a few stumbling blocks:

It wasn't obvious to me that index.ts was just a demo file, and didn't have specific significance of being called index.ts to the plugin. All that matters is that it's included in the tsconfig.json
In a monorepo, simply having the file in include isn't sufficient to get types, you also need to ensure the file is imported at runtime if it's separated out, e.g.

// package1/prisma/jsonTypes.ts
declare global { ... }

// package1/src/client.ts
import '../prisma/jsonTypes.ts' // if this is omitted, types are silently `any`

export const client = new PrismaClient(...)

// package2/src/index.ts
import { client } from 'package1/src/client.ts'

// now types will be correct

If you think these notes would add clarity and you'd like them in the docs, I'm happy to throw together a quick PR.

Hey, super thanks for your feedback! You're up to update the docs in a PR?

Yep happy to!
On Sat, May 6, 2023 at 13:32 Arthur Fiorette @.***>
wrote:

Hey, super thanks for your feedback! You're up to update the docs in a PR?
—
Reply to this email directly, view it on GitHub
https://github.com/arthurfiorette/prisma-json-types-generator/issues/67#issuecomment-1537218219,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHSOTAOHH3J5ZENHA44UX3XE2YMRANCNFSM6AAAAAAXYK6EAI
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

--
Sent from a tiny screen; please excuse brevity or errors, or both.


Remove extension already provided in Boardwalk

Coverage remained the same at 100.0% when pulling 7443e42ac0676536e6a0449aa4527596010398dc on boardwalk_update into 229e8a5f866920c03506b06d6468b7a312ce887f on master.


Handle spurious acks

Currently there are two cases where the ack processing can get stuck:

An application sends a spurious additional ack

The WS code tries to deliver this to the eventstream code, while the ES code is trying to wait for a message
Eventually results in We were not available to process it after ... seconds in the logs

The ES code receives an update to the eventstream, while it's waiting for an ack

This results in the WS code never being able to deliver the ack, so never delivering the next message

The proposed change in this PR adds a buffer of 1 to the channel between the WS and ES code, and changes the timeout into a default when delivering the ack. This prevents the deadlock possibility. There are always either 0 or 1 acks in the pipe.

Tried this with my local FireFly stack and it seems to correctly detect spurious acks. Can't tell if the unit test is actually testing it as desired, but it's possible I'm not following the test entirely.

Codecov Report

Merging #136 (29d35d9) into main (d7fd3fd) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 29d35d9 differs from pull request most recent head a18d636. Consider uploading reports for the commit a18d636 to get more accurate results

@@           Coverage Diff           @@
##             main     #136   +/-   ##
=======================================
  Coverage   97.60%   97.60%
=======================================
  Files          56       56
  Lines        6380     6380
=======================================
  Hits         6227     6227
  Misses        117      117
  Partials       36       36

Impacted Files
Coverage Δ

ethconnect/internal/ws/wsconn.go
98.90% <0.00%> (ø)

Continue to review full report at Codecov.

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


D3 v4 resources

Hey!
I don't really know if this is the right place to ask this question or not, but I'll ask anyway!
I am new to D3 and I am looking for resources to study and understand it, there are a lot of resources for the previous version but not for this one.
What does one suggest?

D3 4.0 came out 12 days ago; D3 3.0 came out 1,297 days ago (December 12, 2012) and D3 2.0, which is only slightly different than D3 3.0, came out 1,783 days ago (August 23, 2011). My point is that there will be more resources for D3 4.0 in the future, after more time has passed after its release.
Also, the tutorials that predate D3 4.0 are hardly irrelevant now. Even though there are a lot of changes in D3 4.0, many of these changes are superficial (such as the renamings). Reading tutorials written for D3 3.x is still an excellent use of your time for learning D3 if you also read them in conjunction with the detailed release notes and release summary.
The D3 wiki is publicly-editable and you are welcome to contribute to its organization. I noticed someone has created a category for 4.x-specific tutorials, which might be helpful, though as I said, I wouldn’t discount tutorials that predate 3.x because many of them are still extremely relevant and may only need minor updates, if anything.

Here are all the D3 v4 Blocks.
Kudos to @enjalot for releasing the new "search by version" feature to Blockbuilder.org, which makes the above link possible.


Style updates

Coverage increased (+0.009%) to 94.162% when pulling 06fa66a020c4bc587a37edadf6b0e7d863ee5044 on toc into 901ec3f8727f91ebc73dc3ae7e61b21e2c6efd35 on master.


Remove heartbeat constants

Randomly saw this dead code

actually it's not dead, it's just used in a different place. a bit confusing.


'undetached' is not removed after close the modal.

I created a modal with this configuration
    $('.ui.modal').modal(
      closable: true,
      detachable: false
    )

The modal added undetached in body, but after close it the body keeps these classes:
'dimmable undetached'

Closing because no test case.


Not able to upload video files

Uploading images works really well. Thanks for writing this plugin!
However, when uploading video files, I get this in the console: [object Object] and nothing else and the video file is not uploaded to Cloudinary. I am uploading an mp4 file. Are there any special options I need to pass in?

According to: https://cloudinary.com/documentation/upload_videos
You would need { resource_type: "video" }
So something like:
var cloudinary = require('cloudinary');
var cloudinaryStorage = require('multer-storage-cloudinary');

var storage = cloudinaryStorage({
  cloudinary: cloudinary,
    params: {
    folder: 'foo',
    format: 'mp4',
    resource_type: 'video'
  }
});

should work. Will test for myself when I get home.
Note: resource_type is not supported as a direct param to CloudinaryStorage so you will have to use the overriding params object like the example above. Should be added I suppose.

Have tested, videos are being uploaded correctly with the resource_type flag.


Remove -H flag from curl commands

Now that https://github.com/istio/istio/pull/7995 is fixed, we can remove the -H flag from the curl commands.
This reverts the change made in #2181.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: frankbu
If they are not already assigned, you can assign the PR to them by writing /assign @frankbu in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: vadimeisenbergibm
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: frankbu
If they are not already assigned, you can assign the PR to them by writing /assign @frankbu in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Try to remove the need of angular-babel in Meteor 1.3

Try to add all the features angular-babel has to the official ecmascript package so that we won't need to add it anymore in Meteor 1.3.
If not released in Meteor 1.3, update angular-babel to use the latest Babel as similar as possible to Meteor's.
Need to add "es7.decorators" and add babelHelpers like in here: https://github.com/Urigo/angular2-meteor/blob/feature/meteor1.3/tests/packages/babel-runtime/babel-runtime.js#L277-L337
Also related:
https://github.com/meteor/meteor/issues/6028
https://github.com/meteor/meteor/issues/6057
@pbastowski @kamilkisiela

@Urigo
We could also recommend that people use TypeScript instead of angular-babel / ecmascript packages, because:

it already supports Decorators, and
in most cases TypeScript can be used as a direct drop-in replacement for Babel (this is especially easy if the user does not care about type checking, just transpiling to ES5)

People would have to use the .ts extensions instead of .js, but that's about it. I have replaced Babel with TypeScript in one of my production apps without any side effects. I see this as a viable option.
Do you think this is an option?

@pbastowski that's a good idea.
I think we should provide the 2 options though, and specifically make the ES2015 option easier.
On the Typescript point, what package do you use today?  please have a look at this discussion about adding an official typescript package - https://github.com/Urigo/angular2-meteor/issues/102

I agree, that Meteor's own ecmascript package should either provide decorators by default or allow us to easily add optional Babel components.
As far as typescript goes, I use my pbastowski:typescript package in my projects. It works exactly the same as my angular-babel package, except that it uses the TypeScript compiler instead of Babel. Also, it does not ng-annotate, but I think we don't need ng-annotate any more, especially if users use my angular2-now library, which includes injection into classes.
So, whose typescript package will be the one to rule them all :)  ???

About Typescript - look in the issue - this one - https://github.com/barbatus/ts-compilers

Hi @pbastowski,
If we start using typescript in 1.3 as you suggest, and I will be glad if we could, are we going to miss the source mapping mechanism that we have right now? You now this is a big issue for me! And you helped me to solve this issue in the current version.
I mean: are we going to "see" our typescript code in chrome debugger (or just the transpiled one)?
Thanks and bye ...

I think we can close this issue, since Meteor supports now .babelrc (https://github.com/meteor/meteor/issues/6028) and we can solve the issue with the decorators :)


Add LTS v4.2.16 to conda-forge and resolve CVEs

Fixed CVE-2024-45231 -- Avoided server error on password reset when email sending fails. Fixed CVE-2024-45230 -- Mitigated potential DoS in urlize and urlizetrunc template filters.

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


SQL: redundant explanations (probably) should be collapsed by pruning rules

In the mobile_data demo, macrobase-sql returns two singleton explanations when in fact the two correspond to the same tuples.
e.g.,
macrobase-sql> SELECT * FROM DIFF(SPLIT (SELECT *, percentile(battery_drain) AS percentile from mobile) WHERE percentile > .99) ON *;
67156 [main] INFO  QueryEngine  - Using user_id, state, hw_make, firmware_version, app_version as candidate attributes for explanation
67265 [main] INFO  APLSummarizer  - Encoded in: 109 ms
67265 [main] INFO  APLSummarizer  - Encoded Categories: 2
67299 [main] INFO  APLSummarizer  - Number of results: 2
2 rows

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|    app_version     |      user_id       |      hw_make       |       state        |  firmware_version  |      support       |    global_ratio    |   outlier_count    |    total_count     |
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|        v50         |         -          |         -          |         -          |         -          |      .873185       |     89.883198      |       902.0        |       1003.0       |
|         -          |         -          |       Emdoor       |         -          |         -          |      .873185       |     89.883198      |       902.0        |       1003.0       |
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Can provide CSV on request.

So, these redundant explanations are not going to be caught by the pruning rules. (I confirmed this by running the same query through the BasicBatchPipeline, and I got the same result.) When v50 and Emdoor are individually considered as order-one candidates, they each meet the minRatio and support thresholds separately. After that, they're never checked again, because they're considered saved explanations, and there's no check afterwards to see if two separate explanations overlap. (In this case, the overlap is 100%.)
This is the sort of thing that @sahaana's explanation collapsing would help—we need to have that additional check to handle this case.


Patches the single sort case where on node toString is not called.

The important lines of this PR are in request.js.  The rest is simply the result of the build - if you prefer to build yourself, feel free to just take the small change and reject this PR.
The core of the issue here is when there is only one sort specified and you are running the search on node, server-side, it is not calling toString automatically.  This is resulting in a different sorting of results between client and server.
I did not know where you wanted this tested, so I left that out.
Thanks!

thanks for catching this!
merged


invalid node type error

Apologies for the poor error report, but I'm getting the following error when opening templ files.
Please let me know if I can provide anything further:
treesitter/highlighter: Error executing lua: ...ed-0.9.4/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 1320 for language templ

It does seem to be any file, for example it does it here: https://github.com/a-h/templ/blob/main/examples/blog/posts.templ
I'm up to date yes.
It started this week, I don't remember updating but it's entirely possible I did so without thinking.
I updated neovim in case that was the issue, am on 0.9.4

Can you paste the contents of these files:

$HOME/.local/share/nvim/site/pack/packer/start/nvim-treesitter/queries/templ/highlights.scm
$HOME/.local/share/nvim/site/pack/packer/start/nvim-treesitter/queries/templ/injections.scm

hm maybe you won't have this exact path if you don't use packer, but you should have these files somewhere.

Manage to find them, I'm using lazy:
; inherits: go
(component_declaration
  name: (component_identifier) @function)

[
  (tag_start)
  (tag_end)
  (self_closing_tag)
  (style_element)
] @tag

(attribute
  name: (attribute_name) @tag.attribute)

(attribute
  value: (quoted_attribute_value) @string)

[
  (element_text)
  (style_element_text)
] @string.special

(css_identifier) @function

(css_property
  name: (css_property_name) @property)

(css_property
  value: (css_property_value) @string)

[
  (expression)
  (dynamic_class_attribute_value)
] @function.method

(component_import
  name: (component_identifier) @function)

(component_render) @function.call

(element_comment) @comment @spell

"@" @operator

[
  "templ"
  "css"
  "script"
] @keyword

; inherits: go
((element_comment) @injection.content
  (#set! injection.language "comment"))

((script_block_text) @injection.content
  (#set! injection.language "javascript"))

((script_element_text) @injection.content
  (#set! injection.language "javascript"))

((style_element_text) @injection.content
  (#set! injection.language "css"))

Thanks, they're the same as mine. I have no idea what's happening, it works fine for me.
What does :checkhealth say ?
Do you maybe have other .scm files in your queries/templ directory ?

Oh interesting, I'm getting this for other grammars too:
==============================================================================
nvim-treesitter: require("nvim-treesitter.health").check()

Installation ~
- WARNING `tree-sitter` executable not found (parser generator, only needed for :TSInstallFromGrammar, not required for :TSInstall)
- OK `node` found v20.9.0 (only needed for :TSInstallFromGrammar)
- OK `git` executable found.
- OK `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
  Version: Apple clang version 12.0.0 (clang-1<IP_ADDRESS>)
- OK Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI.

OS Info:
{
  machine = "x86_64",
  release = "22.6.0",
  sysname = "Darwin",
  version = "Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64"
} ~

Parser/Features         H L F I J
  - c                   ✓ ✓ ✓ ✓ ✓
  - gitcommit           ✓ . . . ✓
  - go                  ✓ ✓ ✓ ✓ ✓
  - javascript          ✓ ✓ ✓ ✓ ✓
  - json                ✓ ✓ ✓ ✓ .
  - lua                 ✓ ✓ ✓ ✓ ✓
  - norg                ✓ . ✓ . ✓
  - query               ✓ ✓ ✓ ✓ ✓
  - rust                x ✓ ✓ ✓ ✓
  - templ               x . . . ✓
  - tsx                 ✓ ✓ ✓ ✓ ✓
  - typescript          ✓ ✓ ✓ ✓ ✓
  - vim                 ✓ ✓ ✓ . ✓
  - vimdoc              x . . . ✓

  Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
         +) multiple parsers found, only one will be used
         x) errors found in the query, try to run :TSUpdate {lang} ~

The following errors have been detected: ~
- ERROR rust(highlights): ...ed-0.9.4/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 662 for language rust
  rust(highlights) is concatenated from the following files:
  | [ERROR]:"/Users/joe.davidson/.local/share/nvim/lazy/nvim-treesitter/queries/rust/highlights.scm", failed to load: ...ed-0.9.4/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 662 for language rust
- ERROR templ(highlights): ...ed-0.9.4/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 1320 for language templ
  templ(highlights) is concatenated from the following files:
  | [ERROR]:"/Users/joe.davidson/.local/share/nvim/lazy/nvim-treesitter/queries/go/highlights.scm", failed to load: ...ed-0.9.4/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 1320 for language templ
  |    [OK]:"/Users/joe.davidson/.local/share/nvim/lazy/nvim-treesitter/queries/templ/highlights.scm"
- ERROR vimdoc(highlights): ...ed-0.9.4/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 746 for language vimdoc
  vimdoc(highlights) is concatenated from the following files:
  | [ERROR]:"/Users/joe.davidson/.local/share/nvim/lazy/nvim-treesitter/queries/vimdoc/highlights.scm", failed to load: ...ed-0.9.4/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 746 for language vimdoc

I managed to resolve it by following this issue:
https://github.com/nvim-treesitter/nvim-treesitter/issues/3092
Nothing to do with your repo, sorry!

No worries!


Source code of "Average of 3 integers" program.

This program calculates average of 3 integers
Author: Abdullah Ibrahim
Last modification date : 28/03/2022

اللي تحتي فلاح

/assign


laravel 10

dockeruser@e2fe84719edc:~$ composer require outofoffice/password-generator
./composer.json has been updated
Running composer update outofoffice/password-generator
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - gldrenthe89/nova-string-generator-field[v3.0, ..., v3.0.2] require illuminate/support ^9.0 -> found illuminate/support[v9.0.0, ..., v9.52.7] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires gldrenthe89/nova-string-generator-field 3.* -> satisfiable by gldrenthe89/nova-string-generator-field[v3.0, v3.0.1, v3.0.2].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require outofoffice/password-generator:*" to figure out if any version is installable, or "composer require outofoffice/password-generator:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
dockeruser@e2fe84719edc:~$

I’ll look into this later tonight and ensure it works well with Laravel 10. Thanks for reporting this.

I have tried installing outofoffice/password-generator on a fresh Laravel 10.8 install. I was not able to replicate this issue. The only dependency that my package has is a PHP dependency and after looking at your issue closer it seems like the issue is being caused by another package you have installed called gldrenthe89/nova-string-generator-field.
I have tried installing that (gldrenthe89/nova-string-generator-field) package on the fresh Laravel 10.8 install and got the same error as you did. I'd recommend you remove this package or find another way of bypassing this check. Since the issue isn't caused by outofoffice/password-generator I will be closing this issue. Thanks


Check whether GL context supports the expected API

I couldn't test it yet myself (GPU supports GL 4.5), so we'll need to see if it behaves
as expected on systems that don't support OpenGL 3.3 or GL ES 3.0.

Works as expected with MESA_GL_VERSION_OVERRIDE env. variable.


⚠ Bofrost.es has degraded performance

In 76997f8, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1565 ms

Resolved: Bofrost.es performance has improved in 7786726 after 16 minutes.


Defer to upstream PEAR ValidClassName sniff.

As suggested in https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/pull/649#issue-168558657
Closes #649

It looks like the PEAR sniff doesn't check for CamelCaps.

It looks like the PEAR sniff doesn't check for CamelCaps.

It doesn't use the CamelCaps function, but it does check for them - see: https://github.com/squizlabs/PHP_CodeSniffer/blob/master/CodeSniffer/Standards/PEAR/Sniffs/NamingConventions/ValidClassNameSniff.php#L59

OK. It looks like it uses a more generic Invalid error code rather than the more explicit NotCamelCase that is in WPCS.

True, but that shouldn't really matter or does it ? The error message itself is a bit more generic as well, but we could alter that via the config.
Message in WP sniff:
%s name "%s" is not in camel caps format where 1: token type (class, interface) and 2: the class name.
Message in PEAR sniff:
%s name is not valid; consider %s instead where 1: the class name and 2: CamelCaps version of the class name.


Compatibility with react-virtuoso

Looks like quite a few people, me included, are struggling to get simplebar to work with react-virtuoso virtualization library
@Grsmto would you mind taking a look?
The library is providing access to its scroll element via a Scroller components prop
People got it working with "rc-scrollbars" lib.
Given that react-virtuoso is becoming a defacto standard virtualization lib it would be nice to have a reference implementation, if possible.

Hi @tlthiem ,
I did an example on Codesandbox, let me know if that works: https://codesandbox.io/p/sandbox/lucid-morning-dkhpgx
important part is that I had to override some CSS from react-virtuoso wrapper like this:
.simplebar-content > * {
  position: static !important;
}

idk if there is a cleaner way to do that, but seems to work. Hope that helps.

Hi @tlthiem ,
I tried a few things but couldn't find a good way of doing it. It will require Simplebar to mount before react-virtuoso can mount. So there will be a re-render, like in the example provided in the issue you referenced: https://codesandbox.io/p/sandbox/lucid-morning-dkhpgx

Alright, thanks for clarifying that there is no better way. Appreciate it!


No longer convert 503s into 504s from scytale

Codecov Report

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

@@            Coverage Diff             @@
##           master      #56      +/-   ##
==========================================
- Coverage   80.03%   79.96%   -0.08%
==========================================
  Files           6        6
  Lines         536      534       -2
==========================================
- Hits          429      427       -2
  Misses        106      106
  Partials        1        1

Impacted Files
Coverage Δ

src/tr1d1um/communication.go
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Use bower for front-end dependencies

web pack for bundling with sass and babel loaders seems like a better option


Variables in Helm

Kyverno Version
1.6.x
Kubernetes Version
1.20.x
Kubernetes Platform
EKS
Description
https://github.com/kyverno/policies/issues/856
how can i avoid Helm interpreting Kyverno policies containing variables which  deployed through Helm   as Helm variables.
{{ request.operation == 'CREATE' && resources[kind=='NetworkPolicy'].length > 0 && resources[kind=='NetworkPolicy'].spec.podSelector.matchLabels == request.object.spec.template.metadata.labels }}"
Steps to reproduce

syntax highlighting

Expected behavior
solve the error
Screenshots
No response
Kyverno logs
No response
Slack discussion
No response
Troubleshooting

[X] I have read and followed the documentation AND the troubleshooting guide.
[X] I have searched other issues in this repository and mine is not recorded.

Not a policies issue. Please use a discussion of Slack thread.


Initial package release

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8062e01). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             master        #1   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?         6
  Lines             ?       222
  Branches          ?        35
==========================================
  Hits              ?       222
  Misses            ?         0
  Partials          ?         0

Continue to review full report at Codecov.

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


Emojis in tables messes up the column alignment

My assumption is this is due to emojis taking up two unicode codepoints but getting rendered using only spot.  As a result, the columns are off.

Reproduction:
from rich.console import Console
from rich.table import Table
console = Console()
table = Table(title="Emoji Table")
table.add_column("emoji", justify="left", no_wrap=True)
table.add_row(":smiley:")
table.add_row(":no_entry:")
table.add_row(":white_heavy_check_mark:")
console.print(table)

Your assumption is correct!
I'm afraid there is not much that can be done. Terminals don't always keep up with the latest changes to the unicode database.
My suggestion would be to find another "tick" symbol. There are a few in unicode. You should be able to find one that existed in unicode for longer, and will render with the correct size in the terminal.

Ah - interesting.  I would've assumed the issue was in the padding / measuring libraries in this repo and not in the terminal implementation.

It's kind of an interaction of both. The only real solution would be to know what version of the unicode database the given terminal is using, and that's just not exposed anywhere.
btw what terminal are you using? Those characters work fine in iTerm, Ubuntu, and Windows Terminal.

Got it.  I use OSX's terminal

I tried to use ⭐ emoji and it seems impossible to make render ok when using export_html. I am using iTerm2 but the fact that the outcome is dependent on current terminal make the emoji and tables a real issue. Any idea on how to address it?

As you have discovered, the browser renders emoji differently from the terminal.
The only solution I have thought of would be to parse out emoji, and force them in to a span with a width that matches the terminal. I think that would work, but it will make the export function more complex.
It’s not high on my list of priorities. But if you file an issue for this I’ll Likely get to it eventually. Maybe sooner if I get sponsorship.


feat: add registry input

adds an optional registry input to the github action, might want to revisit this as some people might want to push images to different registries, so this functionality could also be added (optionally) to the recipe.yml

Does it make sense to have that bash if and have an empty string for the default, or should it just have ghcr.io or whatever as the default and always pass that to the cli?

Thanks for that, I feel pretty silly now

looks to be working on my end: https://github.com/gerblesh/uhypr/actions/runs/7947758489/job/21696975833


[nrf noup] ci: limit build agent selection

Only build agent should be used for building jobs.
Signed-off-by: Chris Bittner<EMAIL_ADDRESS>

@carlescufi

Linked with: https://github.com/NordicPlayground/fw-nrfconnect-nrf/pull/730

@nvlsianpu


startJVM crashes Apple M1

jpype.startJVM() crashes with A fatal error has been detected by the Java Runtime Environment
I also tried to build and test jpype but the first test seemed to abort  without printing error message (The second code block contains the output).
I would appreciate any tips for debugging!
startJVM() crash:
% python3 -m venv venv
% cd venv
% source bin/activate
(venv) % export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
(venv) % PATH=${PATH}:$JAVA_HOME/bin
(venv) % pip install JPype1
Collecting JPype1
  Using cached JPype1-1.4.1-cp39-cp39-macosx_10_9_universal2.whl
Collecting packaging
  Using cached packaging-23.1-py3-none-any.whl (48 kB)
Installing collected packages: packaging, JPype1
Successfully installed JPype1-1.4.1 packaging-23.1
(venv) % python3
Python 3.9.6 (default, May  7 2023, 23:32:44)
[Clang 14.0.3 (clang-14<IP_ADDRESS>.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import jpype
>>> print(jpype.getDefaultJVMPath())
/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home/lib/libjli.dylib
>>> jpype.startJVM()
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0xa) at pc=0x0000000101ff8918, pid=18600, tid=259
#
# JRE version:  (17.0.8+9) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (17.0.8+9-LTS-211, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-aarch64)
# Problematic frame:
# V  [libjvm.dylib+0x414918]  CodeHeap::allocate(unsigned long)+0x1c8
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/user/venv/hs_err_pid18600.log
#
#
zsh: abort      python3

JPype build log and test failure:
(venv) % git clone https://github.com/jpype-project/jpype.git
Cloning into 'jpype'...
remote: Enumerating objects: 17772, done.
remote: Counting objects: 100% (2179/2179), done.
remote: Compressing objects: 100% (721/721), done.
remote: Total 17772 (delta 1563), reused 1953 (delta 1405), pack-reused 15593
Receiving objects: 100% (17772/17772), 4.78 MiB | 21.57 MiB/s, done.
Resolving deltas: 100% (13108/13108), done.

(venv)  % python3 setup.py test
/Users/user/venv/lib/python3.9/site-packages/setuptools/dist.py:487: UserWarning: Normalizing '1.5.0_dev0' to '1.5.0.dev0'
  warnings.warn(tmpl.format(**locals()))
running test
WARNING: Testing v
[hs_err_pid18600.log](https://github.com/jpype-project/jpype/files/12318912/hs_err_pid18600.log)
ia this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox.
WARNING: The wheel package is not available.
WARNING: The wheel package is not available.
WARNING: The wheel package is not available.
WARNING: The wheel package is not available.
WARNING: The wheel package is not available.
running egg_info
creating JPype1.egg-info
writing JPype1.egg-info/PKG-INFO
writing dependency_links to JPype1.egg-info/dependency_links.txt
writing entry points to JPype1.egg-info/entry_points.txt
writing requirements to JPype1.egg-info/requires.txt
writing top-level names to JPype1.egg-info/top_level.txt
writing manifest file 'JPype1.egg-info/SOURCES.txt'
package init file 'jpype/_pyinstaller/__init__.py' not found (or not a regular file)
reading manifest file 'JPype1.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.jar' under directory 'native'
warning: no files found matching '*.class' under directory 'native'
no previously-included directories found matching 'test/classes/*'
warning: no previously-included files matching '*.pyc' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'NOTICE'
adding license file 'AUTHORS.rst'
writing manifest file 'JPype1.egg-info/SOURCES.txt'
running build_ext
Call build extensions
Jar cache is missing, using --enable-build-jar to recreate it.
  javac -cp lib/asm-8.0.1.jar -d build/temp.macosx-10.9-universal2-3.9/org.jpype/classes -g:none -source 1.8 -target 1.8 -encoding UTF-8 native/java/org/jpype/JPypeContext.java native/java/org/jpype/JPypeKeywords.java native/java/org/jpype/JPypeSignal.java native/java/org/jpype/JPypeUtilities.java native/java/org/jpype/PyExceptionProxy.java native/java/org/jpype/classloader/DynamicClassLoader.java native/java/org/jpype/classloader/JPypeClassLoader.java native/java/org/jpype/html/AttrGrammar.java native/java/org/jpype/html/AttrParser.java native/java/org/jpype/html/Html.java native/java/org/jpype/html/HtmlGrammar.java native/java/org/jpype/html/HtmlHandler.java native/java/org/jpype/html/HtmlParser.java native/java/org/jpype/html/HtmlTreeHandler.java native/java/org/jpype/html/HtmlWriter.java native/java/org/jpype/html/Parser.java native/java/org/jpype/javadoc/DomUtilities.java native/java/org/jpype/javadoc/Javadoc.java native/java/org/jpype/javadoc/JavadocException.java native/java/org/jpype/javadoc/JavadocExtractor.java native/java/org/jpype/javadoc/JavadocRenderer.java native/java/org/jpype/javadoc/JavadocTransformer.java native/java/org/jpype/manager/ClassDescriptor.java native/java/org/jpype/manager/MethodResolution.java native/java/org/jpype/manager/ModifierCode.java native/java/org/jpype/manager/TypeAudit.java native/java/org/jpype/manager/TypeFactory.java native/java/org/jpype/manager/TypeFactoryNative.java native/java/org/jpype/manager/TypeManager.java native/java/org/jpype/pickle/ByteBufferInputStream.java native/java/org/jpype/pickle/Decoder.java native/java/org/jpype/pickle/Encoder.java native/java/org/jpype/pkg/JPypePackage.java native/java/org/jpype/pkg/JPypePackageManager.java native/java/org/jpype/proxy/JPypeProxy.java native/java/org/jpype/ref/JPypeReference.java native/java/org/jpype/ref/JPypeReferenceNative.java native/java/org/jpype/ref/JPypeReferenceQueue.java native/java/org/jpype/ref/JPypeReferenceSet.java
warning: [options] bootstrap class path not set in conjunction with -source 8
warning: [options] source value 8 is obsolete and will be removed in a future release
warning: [options] target value 8 is obsolete and will be removed in a future release
warning: [options] To suppress warnings about obsolete options, use -Xlint:-options.
Note: native/java/org/jpype/classloader/DynamicClassLoader.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.

Constructing Javadoc information...
Building index for all the packages and classes...
Standard Doclet version 20.0.2+9-78
Building tree for all the packages and classes...
Generating test/classes/jpype/doc/Test.html...
Generating test/classes/jpype/doc/package-summary.html...
Generating test/classes/jpype/doc/package-tree.html...
Generating test/classes/constant-values.html...
Generating test/classes/overview-tree.html...
Building index for all classes...
Generating test/classes/allclasses-index.html...
Generating test/classes/allpackages-index.html...
Generating test/classes/index-all.html...
Generating test/classes/search.html...
Generating test/classes/index.html...
Generating test/classes/help-doc.html...
=============================================== test session starts ================================================
platform darwin -- Python 3.9.6, pytest-7.4.0, pluggy-1.2.0 -- /Users/user/venv/bin/python3
cachedir: .pytest_cache
rootdir: /Users/user/venv/jpype
configfile: setup.cfg
testpaths: test, jpype/_pyinstaller
collected 1732 items

test/jpypetest/test_array.py::ArrayTestCase::testArrayCtor1 zsh: abort      python3 setup.py test

I had the same problem

Anyone found a solution? Experiencing same issues

Unfortunately I have no insight into this problem.   I would search the archives.    It must be some mismatch between the assumptions of the JVM and Python.

Unfortunately I do not have access to that machine.   There is no reason for a sigbus to be happening unless the code was not compiled with exception support.   We take Java exceptions and make them C++ exceptions.   There is a master try block on every piece of code to ensure it can’t segfault when it gets to Python C layer.

Github seems to offer Apple Silicon macos runners to open source projects for free now: https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/

Another workaround that helps as long as the Java side isn't heavily multithreaded:
Create a java jar with a class like this and add it to the classpath:
package com.my.package.name;
public class UncaughtExceptionPrinter implements Thread.UncaughtExceptionHandler {
@Override
public void uncaughtException(Thread t, Throwable e) {
e.printStackTrace();
}
}
And add this on top of the Python program to debug:
from com.my.package.name import UncaughtExceptionPrinter
from java.lang import Thread
Thread.currentThread().setUncaughtExceptionHandler(UncaughtExceptionPrinter())
From then on uncaught exceptions lead to a textual error message instead of a crash.

I had this same issue with the Python 3.9 that was bundled with Xcode.  I installed the official Python 3.12 release and the issue went away.

Can still reproduce the issue with Python 3.12.2.


DecimalNumberContext.exponentSymbol should be a String not char

This will break a few parsers as they assume a character (in different projects eg walkingkooka.text.cursor.parser.BigDecimalParser)

Closed by #17


Analyzer should offer an API for analyzing an AST without generating source first

This issue was originally filed by @zoechi

What steps will reproduce the problem?
1.
I made an attempt to build a graphical designer which produces Dart code as output.
I prefer building an AST instead concatenating strings.
It seems that there is no API to make the analyzer analyze the AST without generating source code from the AST first.
This seems very inefficient to me because the first thing the analyzer seems to doing is parsing the source and generating an AST.
See also this discussion https://groups.google.com/a/dartlang.org/forum/#!topic/misc/XIOYIAwzCLE
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Dart VM version: 1.3.0-dev.0.1 (Thu Feb 27 08:23:24 2014) on "linux_x64"
Analyzer 0.11.10
Please provide any additional information below.

The analyzer now has an AST that supports both reading and writing. The Angular compiler uses it to great benefit, and many other tools use the provided visitors (SimpleAstVisitor, RecursiveAstVisitor, etc) as well to work with Dart AST.


allow a "description" for taxonomic coverage when using auto infer from source data feature on IPT

IPT version 2.7.6
It is not possible to include a brief description for taxonomic coverage when I checked "Automatically infer from source data".

GBIF populated the field with "N/A"
dataset page on GBIF: https://www.gbif.org/dataset/081daea5-fe6a-4303-bcc3-126b65d0adeb#taxonomicCoverages

eml: https://api.gbif.org/v1/dataset/081daea5-fe6a-4303-bcc3-126b65d0adeb/document
<taxonomicCoverage>
    <generalTaxonomicCoverage>N/A</generalTaxonomicCoveragegeneralTaxonomicCoverage>

Is it possible to have the "description" field enabled when using "Automatically infer from source data" please? It will be very helpful for us as this is a recommendation from the data audit we received from Pensoft.
Thank you so much!!

Thank you for contacting us.
Yes, we'll fix that


Colour filled - event

I stuck in one issue that, when I finish colouring in my art after that I want to display popup like painting has been completed so can you please let me know that by using which method or condition I can easily get callback when I finish colouring in design.
Thanks in advance.

You can probably do that whenever the delegate?.viewDidEndDrawing() method is called and then apply some logic to check if the drawing is "complete"
My guess is that you could check which mask was being processed, read the pixels from that region and check if all have alpha > 0. Then keep track on which masks are "full" and send the warning once all are done. I hope the performance hit isn't that bad

You can probably do that whenever the delegate?.viewDidEndDrawing() method is called and then apply some logic to check if the drawing is "complete"
My guess is that you could check which mask was being processed, read the pixels from that region and check if all have alpha > 0. Then keep track on which masks are "full" and send the warning once all are done. I hope the performance hit isn't that bad


[regression-test] Analyze each table after loading all tables

Analyze may rely on row count reported by BEs, if we analyze immediately
after loading to a table, the row count of the table may be still 0
which may lead to improper behavior of analyze manager.
This change will introduce extra 70 seconds wait time for the cases affected.
"70s" is slightly lager than default value (60s) of tablet_stat_update_interval_second fe.conf.
To reduce this duration, change tablet_stat_update_interval_second
to a smaller value, say 10 seconds and change 70s to 15s.

run buildall


Remove ecdsa dependency

This PR proposes to remove the ecdsa dependency completely by refactoring to use jwcrypto and pyjwt. This change is motivated by the recent CVE that demonstrated the potential vulnerabilities in ecdsa. But regardless of any specific vuln, the maintainers of the ecdsa library have commented to suggest that it is not intended for "production use":
https://github.com/tlsfuzzer/python-ecdsa?tab=readme-ov-file#Security
By removing python-jose this PR does remove functionality from the jwt module (e.g. specifying alternate hash algorithms or JWT_OPTIONS). But as of today, these features appear to be unused. However please let me know if I'm mistaken here. As far as this PR is concerned though, the output of JWT.create_token() has not changed.
I believe this PR extends the work done in PR #398 by fully removing the package in question. It should also address:
Issues #395
Issues #388

@justinabrokwah-okta - I'm curious to get your thoughts here, I think you might be the most familiar with the current implementation.

@justinabrokwah-okta - I'm curious to get your thoughts here, I think you might be the most familiar with the current implementation.

Thanks so much for this PR, sorry for the delay in response. I'll try to take a look at this today but skimming through, it looks like an overdue change to make. Also tagging @bryanapellanes-okta for visibility

@agburch Thank you so much for your contribution!  I'll review this week and consult with @justinabrokwah-okta .  If no issues or concerns arise, I'll plan to merge and publish a new release by the end of next week.