Correct getNodeTree

This PR has been verified through a test in LionWeb Kotlin (see https://github.com/LionWeb-io/lionweb-kotlin/pull/1)
Changes:

Documentation of the method. The method supports receiving multiple ids, but the documentation was stating otherwise
I was getting an error when not specifying the clientId, and I think this was the intended behavior. I changed it in a way that providing no clientId should work, but providing somehow an invalid string should fail
The way in which we were providing the answer was incorrect

Note that this PR is based on top of #76

Thanks! I will press the "Rebase and merge" button then


Error: Invalid value of type number supplied to Option, expected string when tags/combobox is true

Error: Invalid value of type number supplied to Option, expected string when tags/combobox is true

once I try to click long value field page get blank and get stuck.

antd does not support the value of type integer => https://github.com/ant-design/ant-design/issues/2857.
One solution is to convert is to typecast to the string while mapping the data object, but it will also send the value to the backend as a string. So if it's an array of integers, then instead of [1, 2], it will get sent as ["1", "2"]. Would there be any side-effects if we do this change? @lakhansamani

@oshanz thank you for reporting, issue is fixed here
https://github.com/appbaseio/dejavu/pull/354


Calculate moments about gross centroid

Fixes #53.
Introduces moment_centroid and geometric_centroid_override to the ConcreteSection.__init__() method.
Where moment_centroid is now used to calculate moments:

Moment curvature analysis
Ultimate bending capacity
Moment interaction diagram
Biaxial bending diagram

Where user supplied moments are now assumed to be taken about moment_centroid:

Service stress analysis
Ultimate stress analysis

Where the geometric centroid (takes into account differing material properties) is still used in analysis:

Cracked area properties
Uncracked stress analysis
Cracked stress analysis

These three had to remain as is because the way elastic stress is calculated uses the area properties calculated using the reinforcement.
The above assumptions (have hopefully) been made clear in the documentation.
@Agent6-6-6 let me know if you have any comments with this one!

@robbievanleeuwen, FYI a lot of the tests I've written but not committed yet in Nzs3101 code PR because I was waiting for this to be addressed now pass with the exception of the neutral axis depth. I'll investigate further if I get a chance this weekend.
The weird thing is with axial load at zero and relatively shallow neutral axis I don't pass neutral axis tests based on independent check, but agree with moment capacities. But with tension or compression I get same answers... Need to look into it further.
But I get the correct moment capacities now at least with the moment being based around the gross section centroid.


Add k9s and nerdctl utils

nerdctl and k9s are extremely useful, and could be also reused in the recovery image.
This change also renames the iso/cOS.yaml to manifest.yaml. It also adds a build field with an optional list of packages to build.
See also: https://github.com/ibuildthecloud/os2/blob/master/Dockerfile#L60

tricky part for the ci bot: We could keep the old versions around of those as well, and do not trash the old version when we bump them. so they can be also picked up by version when running luet install

Finally green!


Chore - Update Encrypted GitHub Access Token

Context
Recently received an email by GitHub regarding potential security breach with Travis CI build logs. The access token used by this project was identified as part of the breach and the token was revoked immediately.

Definition of Done
Generate a new token and update the Travis configuration file to ensure builds keep working.

Travis CI confirmed to be working as normal.


Fix complex MERGE causes crash (#897)

Fixed the complex MERGE crash, which was due to storing variables in tuple positions that did not exist. This happened on MERGE commands where there wasn't a RETURN clause.
Added logic to catch these and handle appropriately. Meaning, discarding the variable results, instead of storing them.
Fixing this issue has highlighted the need to fix variable reuse in the MERGE transform itself. This is because MERGE preprocesses the path before handing it off to anything else.
Added regression tests.

I looked over it, and good job preventing the crash. If @muhammadshoaib could take a look too, that'd be great

Added @MuhammadTahaNaveed as well.


[WIP] Inline text editing

REDMINE-17336

Coverage remained the same at 99.208% when pulling 77e77fe670ae271aa8550dfb354e5bd0dbe3a886 on tf:slate-5 into fafd1b2b8a4c0c75713fd37f724955561eee59e3 on codevise:master.


Fix: Script variables was ignored on 'Intro Procedural Tilemap'

We need to calculate the size at 'onready' to be able to use the value that is assigned in the editor.
If you change the 'inner_size' or 'perimeter_size' from the Script Variables on the Editor, it will no take effect because it calculate 'size' before of assign the value.

Thanks


Ghost Importer: Current State, Problems and Future Improvements

This Issue is to pick up where Issue #4605  left off and consolidate the issues surrounding the importer into one place. It is also to generate a conversation on what people would like/expect to see from the importer.
Current State
As it stands the Importer can handle zip files containing images, markdown files and the official JSON formatted file but not raw JSON. It should probably be opened up to take raw JSON data as well.
Problems
There is some feedback at the moment if the import fails such as a post with an unknown user_id but there are other cases where it simply says the import has failed with no other useful information so we need to investigate all possible causes of failure and display more information if possible.
There is currently no visual feedback of potential problems. We check the import file for posts and tags that have a matching slug, title or name but we do not display this information or compare it with the current posts and tags in the database which leads to duplications. This can be found as well in Issue #4685
There is no visual feedback of what the import file contained (I am about to make a PR for this to get the ball rolling - it is fairly rough and ready at the moment but better no information at all)
There are comments in the codebase about implementing a Dry-run. i.e. testing the import file, comparing with the current database then providing feedback to the user prior to actually performing the import. We could decide to complete the whole import process if no problems are found or have a check box to let the user see details of the import first either way such as number of posts etc.
The feedback could come with options on how to merge the data - e.g. for a duplicate post - the user could either:

use current database version of post
use importer version of post
use both posts (incrementing onto current slug as currently happens)
use post with most recent published_at/updated_at value

The UI needs some love as well. I was playing around with moving the importer into a modal. This is okay but I am not sure it is really required, perhaps the feedback would be nicer in a modal rather than the labs page. There was some discussion on the UI in #3927
Large import files can really mess with Ghost - presumably the import times out somewhere so this needs further investigation and either files have to be intelligently chopped up/chunked somehow.
There was also discussion at some point about creating an export or backup (more like the migrations backup) when importing - this could be automatic or provided as an option to the user and this is something I think is necessary for the delete content button. A Backup is probably better than export (maybe choose a limit on backups in the codebase or through the admin-UI). Discussion on this would be great - such as whether people agree or disagree and preferred approach if any.
Future improvements

It would be nice if we could have specific importers from various other platforms either via some automated check of the file/page or via a dropdown menu.
Image acquistion - Checking through posts for images and downloading them automatically could be tricky but would greatly enhance the migration process.
Create flows in modals or otherwise for users to fix through problems found - e.g. if posts have an unknown user_id they could see the users available and select one, or create a new user rather than having to dig into the import file.

Required tasks

[x] refactor the importer: right now we have two different folders for the importer logic - sort that out
[x] improve logs and error information for the user
[x] investigate import failures with no information
[x] https://github.com/TryGhost/Ghost/issues/6967: tags loosing order after importing
[x] https://github.com/TryGhost/Ghost/issues/7275: prevent sending notification to Slack when importing blog data
[x] https://github.com/TryGhost/Ghost/issues/8349
[x] https://github.com/TryGhost/Ghost/issues/8365
[x] Look at #4685
[x] there were issues with duplicate posts_tags, authors with duplicate slugs and I think there was an issue where there were duplicate tags in the import file after sanitisation

Optional/Future tasks

[ ] add all weird edge cases as tests
[ ] Image Acquisition
[ ] https://github.com/TryGhost/Ghost/issues/8015: importing JSON database with wrong date format throws deprecation warning
[ ] discuss/implement backups
[ ] fix importer for large import files
[ ] split the importer processing up to allow for a dry-run option
[ ] provide more controls to user on how to merge duplicates
[ ] warnings we can add: two users are imported with same email, but different slug (slug is regenerated)
[ ] optimisation: trigger an export before import

@kirrg001 is this issue up to date? You fixed so many things with the importer already, I wonder if its worth closing this and waiting to see what problems people run into in the real world. Also we have both #8756 and #8517 open - all tracking remaining issues in the importer. I think we can reduce issue noise here 😁

Yeah it is up-to-date. I kept it open for future improvements - see list on top. But yeah agree, let's close it - if we want to add some more improvements from the list on top, we can still look it up here.


[KOGITO-6414] Operator fails reconciliation when specific KafkaTopic …

…exists
KOGITO-6414
Signed-off-by: Karel Suta<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[x] You've ran make before-pr and everything is working accordingly
[x] You've tested the new feature/bug fix in an actual OpenShift cluster
[x] You've added a RELEASE_NOTES.md entry regarding this change

How to retest this PR or trigger a specific build:

Run operator BDD testing
Please add comment: /jenkins test

Run RHPAM operator BDD testing
Please add comment: /jenkins RHPAM test

/jenkins test

Test errors seem unrelates

@sutaakar can you please cherry-pick for 1.15.x branch?

sure


Errors when styled-components is not installed

Trying to use this package in my app, but keep getting this error. We're running on Emotion rather than styled-components.
error - ./node_modules/@south-paw/react-obfuscate-ts/dist/react-obfuscate-ts.esm.js:2:0
Module not found: Can't resolve 'styled-components'

Hi! styled-components is a peer-dependency and needs to be installed in your project. I'll update the readme so this isn't missed by anyone else. Thank you for raising it :)

Better late than never - fixed in 2.0.0 release


feat: implement 404 when no matching page found

What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behaviour?
You can also link to an open issue here.
What is the new behaviour?
...
Does this PR introduce a breaking change?
What changes might users need to make in their application due to this PR?
Other information:
Please check if the PR fulfills these requirements:

[ ] Tests for the changes have been added
[ ] Docs have been added / updated

@toomuchdesign this is a proposed implementation for the 404 when matching page is not found. Its targeting another PR: https://github.com/toomuchdesign/next-page-tester/pull/131, thus the omitted PR description. If this approach seems fine, I will add some additional test cases to make sure we are correctly matching/constructing the http request parameters (pathname) as next.js does.

@toomuchdesign this is a proposed implementation for the 404 when matching page is not found. Its targeting another PR: https://github.com/toomuchdesign/next-page-tester/pull/131, thus the omitted PR description. If this approach seems fine, I will add some additional test cases to make sure we are correctly matching/constructing the http request parameters (pathname) as next.js does.

Are we going to need a pageObject to render error pages, too?

Are we going to need a pageObject to render error pages, too?

Are we going to need a pageObject to render error pages, too?

Probably, but I don't know the details yet. To implement error pages we will have to catch them at multiple places so its hard to say:

data fetching methods
initial render
client side navigation
client side render (not sure about this one actually -- would have to check nextjs)

Are we going to need a pageObject to render error pages, too?

Probably, but I don't know the details yet. To implement error pages we will have to catch them at multiple places so its hard to say:

data fetching methods
initial render
client side navigation
client side render (not sure about this one actually -- would have to check nextjs)

Any blockers to merge this @toomuchdesign ?
P.S. this is not targeting master so fell free to do any refactoring you had in mind after this one is merged.

Any blockers to merge this @toomuchdesign ?
P.S. this is not targeting master so fell free to do any refactoring you had in mind after this one is merged.

Let's merge!

Let's merge!


content: replace deprecated CUE_MODCACHE with new CUE_CACHE_DIR env var

fixes: https://github.com/cue-lang/cue/issues/2903

@myitcv should I close the pr?

This was addressed via https://github.com/cue-lang/cue/issues/2903#issuecomment-1974900105


Viafree.no not working in 1080p

Checklist

[ ] I'm reporting a broken site support issue
[X] I've verified that I'm running youtube-dl version 2020.03.24
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar bug reports including closed ones
[X] I've read bugs section in FAQ

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '-f', 'bestvideo[height=1080]+bestaudio', '--merge-output-format', 'mkv', '--prefer-ffmpeg', '--ffmpeg-location', 'C:\\Users\\Tommy Vange\\Documents\\YouTube DL\\ffmpeg.exe', '--cookies', 'C:\\Users\\Tommy Vange\\Documents\\YouTube DL\\cookies.txt', '--all-subs', '--write-sub', '--embed-subs', 'https://www.viafree.no/programmer/underholdning/paradise-hotel/sesong-11/episode-1']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2020.03.24
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.18362
[debug] exe versions: ffmpeg 4.2.2
[debug] Proxy map: {}
[Viafree] episode-1: Downloading webpage
[debug] Using fake IP <IP_ADDRESS> (NO) as X-Forwarded-For.
[mtg] 991993: Downloading video JSON
[mtg] 991993: Downloading streams JSON
[mtg] 991993: Downloading m3u8 information
ERROR: requested format not available
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpjwbwqymm\build\youtube_dl\YoutubeDL.py", line 808, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpjwbwqymm\build\youtube_dl\YoutubeDL.py", line 863, in process_ie_result
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpjwbwqymm\build\youtube_dl\YoutubeDL.py", line 1636, in process_video_result
youtube_dl.utils.ExtractorError: requested format not available

Description

When I try to download videos from viafree.no it only shows a maximum quality of 720p, but I know that video is available in 1080p. If I use a chrome video downloader extension, it works shows the 1080p version, but it is extremely tedious to download it from chrome and add the audio later when I could have youtube-dl do it for me.
It works fine if I choose 720p as the quality but when using 1080p it says that the format is not available.

As Some Other Sites , Downloading At 1080p Requires Authentication (Or Premium Subscription).
In case u have valid credentials or premium access , please supply username and password flags .

As Some Other Sites , Downloading At 1080p Requires Authentication (Or Premium Subscription).
In case u have valid credentials or premium access , please supply username and password flags .

I included cookies from the site, isn't that sufficient?

Can you tell me which chrome extension you are using ? I will try look at ydl implementation.

The 1080p is available if using another host for info:
'https://viafree.mtg-api.com/stream-links/viafree/web/%s/clear-media-guids/%s/streams'                     % (country, video['mpx_guid'])
However, the audio is separated from videos, so it is necessary to use the -f flag. It had been working on a solution, but when I asked for help, the response was useless. Nevertheless, someone more skillful may be able to solve this with the hint of the above host.


Create my custom Hugo theme

I didn't really find a minimal Hugo theme which matches my needs.
My custom Hugo theme should be:

responsive
simple
lightweight

I found hugo-coder which is pretty close to what I want. I'll use it for now and if needed, I can create my own theme.

I ended up forking hugo-coder.


Adding -IppUrl help information to Add-Printer.md

We added support for -IppUrl in add-printer cmdlet. Now updating the documentation on msdoc site. Also updated the -Name change and the fixed a typo.

looks like this should have been initiated from the doc team. I'll provide the content when needed,


Get file type in the module

If I download a story item for example, how can I get the file type of it if it's a pic (jpg/png)?

All pics (stories, posts) downloaded are in jpg format


Installation/run instructions needed

I can't find any instructions on how to install and run this for day-to-day use. Please add them and/or point me to them.

https://github.com/propeoplemd/cibox/blob/master/docs/Quickstart.md

@CharlesBelov shoot us with additional questions if there are any.
Also you can have a look at sessions about a project here http://docs.cibox.tools/en/latest/about/Videos-presentations/


Map div does not support 100% height CSS property

I tried to spread a map on to the full document. Unfortunately, when I set height css property as 100%, the map does not render. But, the map renders for static height pixels. I have created the following jsfiddle for reference: http://jsfiddle.net/QbP2U/5/

 $(window).on("resize", function () {             $("#map").height($(window).height());             map.invalidateSize();         }).trigger("resize");
Use this code to make it responsive height of the window

Omgan's comment above worked great for me with leaflet 1.0.2
I added a small change which was:
.height() - 220);
as this helped me adjust the alignment to the menu I was using. Also, I needed to remove any CSS I was trying to use to solve the problem.

Works perfectly, but the setting worked with (- 40)
$(window).on("resize", function () { $("#map").height($(window).height()-40); map.invalidateSize(); }).trigger("resize");

I followed what Omgan, dstrickler, and josejaner did. Also since I had my map initialized in a separate function initMap() I had to trigger resize in there as well like below....
function initMap() {     map = L.map('mapid').setView([40.060620, -77.523182], 17);     L.tileLayer('https://api.mapbox.com/styles/v1/mapbox/{id}/tiles/{z}/{x}/{y}?access_token={accessToken}', {         maxZoom: 18,         id: 'streets-v9',         accessToken: 'xxxxx'     }).addTo(map);     tilesLoaded = true;     $("#mapid").trigger("resize") }

Using height in CSS like below:
#map {     height: calc(100% - 44px);     width: 100%;     position: absolute !important; }
Full screen works fine but bounds no longer work correctly. All markers not visible. But if i set height like 800px the bound works fine.

@stripathix if you think this is an issue, I suggest you open a new one with a clear example illustrating the issue.
Given the information you provided, it sounds highly unlikely this is a Leaflet problem, but rather an issue with how your application uses it. For example, if your map container ever changes size after the map is initialized, make sure to call invalidateSize on your map instance.

You use a wrapper container set to position fixed or absolute to get height 100% working.
e.g.
.map-wrapper { width: 100%; height:100%; position: fixed;}
#map { width: 100%; height:100%; position: relative;}

See https://jsfiddle.net/robertpribpolestar/xg41w12v/3/

@dhanyn10 position: absolute; did the trick!

$(window).on("resize", function () { $("#map").height($(window).height()); map.invalidateSize(); }).trigger("resize");
Use this code to make it responsive height of the window

its perfectly fine working hack for it, i searched for this kind of solution for last couple of hours but at last i did found it and i am really happy. I test its responsiveness also, which is correct.

Oh FFS just use 100vh. And read https://developer.mozilla.org/en-US/docs/Learn/CSS/Introduction_to_CSS/Values_and_units about vh and vw and what 100% exactly mean.


Restructured SSL client context mapping to 2-level

The first level lookup key would be CA bundle & CA bundle path;
The second level lookup key would be cert & key;
This 2-level mapping prepares for the dynamic client cert updating API.
@shinrich

@masaori335 since you've been in this area recently, could you take a look too?

[approve ci debian]

[approve ci debian]


Draft: add new relations behavior on deletion of related objects (#343)

created a simple test that asserts that relations are deleted when entities are deleted. I think thats a foreseeable outcome (especially as the merge systematic takes care of copying relations).
However, relations are also deleted if the relation_type is deleted. And while it makes sense that a relation shouldn't exist without a relation_type I think we shouldn't delete relations when the relation type is deleted. Researchers clean up there vocabs in the admin interface and while they are warned that relations will be deleted I think we should nonetheless set the relation_type to a configurable default and keep the relation. Thus the second test is currently failing.
The behavior I suggest is:

relations are deleted if target or source are deleted (current behaviour, tested with the new test)
relations are rewritten to the new entity if source or target gets merged (current behavior, test needs to be extended to cover that)
relation_types are rewritten to a default relation type if the original gets deleted (covered by the test, but current behavior is the deletion of the relation)

Can we have opinions on that? @gregorpirgie @steffres

Even though I'm only involved from users perspective, I think the reasoning is sound.
Having relations "vanish" "just because" "I only deleted the relation_type" could certainly be an issue with the MPR users.
Am 21.07.2022 11:05 schrieb Matthias Schlögl @.***>:
Can we have opinions on that? @gregorpirgiehttps://github.com/gregorpirgie @steffreshttps://github.com/steffres
—
Reply to this email directly, view it on GitHubhttps://github.com/acdh-oeaw/apis-core/pull/344#issuecomment-1191235611, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI5U6VNHYISXHORCCZSJAGLVVEHF7ANCNFSM54G2VMOQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I think @sennierer that the solution is very good. But I would also consider:

to set the default value to a value that has the same literal name across all relations (i.e. PersonPerson, PersonEvent, etc.)
something like ("no relationtype specified")
I mean we need one default type per RelationClass anyway, but it would be easier to handle them if all could be accessed by the same name.

And I think that it would be important than that editors never change that name; or, even better, to implement a save mechanism that disallows changing that name – so that relations with the default relationtype can only be assigned a new relationtype, but not changed by editing the default value itself. Which might happen if editors see that at a current state of a project all relations with the default value fall into a certain category and think of just renaming the relationtype.

@gregorpirgie I think you are right, we should aim for one string across all relationtypes. However, I think it could be configurable. Something along the lines of getattr(settings, "APIS_DEFAULT_RELATION_TYPE", "no relationtype specified") and I wouldnt care about users changing the default relation type. If the system doesnt find a relation_type with the set lable it just creates one. Gives the users the opportunity to change in batch if they made a mistake by deleting a relation_type and relieves us from implementing a probably rather complex logic to prevent the change.


Fill gaps in Rooms SDK Live Tests

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Change default environment variable names

As a developer when I run the Andy X Storage on docker, I would like to configure with ANDYX-ENVIRONMENT

Merged with v2/main


Mirantis Cloud Platform in platforms category

Please only report on one project or product per issue
Guidelines for getting added to the CNCF Cloud Native Landscape:

We generally will only list a company in one box, to represent its major or best known offering. We occasionally make exceptions for large companies.
Projects with at least 250 GitHub stars that clearly fit in an existing category are generally included.
We are unlikely to create a new category for products/projects as we'd rather find the best home with the current options.
We are generally not including commercial versions of open source software, when that version just includes minor tweaks.
Closed source products need to link to a clear description of your product; no stealth mode companies.
Your project or company needs a logo.

Project or Product name:
Mirantis Cloud Platform (MCP)
Is it open source? (if you are tempted to say partially, please answer no):
No. It is built from open source software and some salt/reclass files are in private Mirantis repos that are only available upon request.
What are the best URL(s) for it? Repo and homepage (if different) for open source, product homepage for closed source?:
https://www.mirantis.com/software/mcp/
What one category does it best belong in?
Platforms
What's the URL for the best logo (and it needs to include the name)?
https://www.mirantis.com/wp-content/uploads/2017/11/logo-mcp-lockup-v2-01.png
Anything else we need to know?:

Thanks for the detail @dvaneveren , MCP will be included in the upcoming 1.0 version!

Awesome, thanks @shawnpreissner!

Closing as this update was included in the most recent version https://github.com/cncf/landscape#current-version


[python][misc] GHA for Python dependency checks

Partial solution for #751
@mlin - we can add R equivalent test to this PR or do separately.  I'll need some help from you on what the appropriate installation and tests look like.

@mlin - do you want to add a workflow to this PR, or send me notes on an approach?  I'm fine with either.

@mlin can you complete the R work in a different PR?
I will add tasks to the original issue #751, one for Python one for R. We can close the ticket once both have been completed.

@pablo-gar @bkmartinjr Yes, no problem, I should be able to put in a separate PR for R tomorrow.

After discussion with @pablo-gar, decided to add a status badge and consider slack integration for a later date.


[ci] #3700: CI check for kagami validator

Description

Added a dumb CI check to verify that we can run kagami validator as a standalone binary with no errors.

Linked issue

Closes #3700

Benefits
Peace of mind. Even though this is not the most intended usage, our QA already came across this problem.

Checklist

[x] I've read CONTRIBUTING.md
[x] I've used the standard signed-off commit format (or will squash just before merging)
[ ] All applicable CI checks pass (or I promised to make them pass later)
[ ] (optional) I've written unit tests for the code changes
[ ] I replied to all comments after code review, marking all implemented changes with thumbs up

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
2440 unchanged lines in 48 files lost coverage.
Overall coverage decreased (-0.09%) to 59.344%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tools/kagami/src/validator.rs
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

client_cli/src/main.rs
1
0%

client/src/http_default.rs
1
0%

cli/src/main.rs
1
0%

core/src/smartcontracts/isi/asset.rs
1
29.79%

core/src/sumeragi/network_topology.rs
1
96.77%

derive_primitives/src/lib.rs
1
0%

macro/derive/src/lib.rs
1
94.59%

data_model/src/name.rs
2
94.25%

core/src/smartcontracts/isi/query.rs
3
96.69%

cli/derive/src/lib.rs
5
93.14%

Totals

Change from base Build<PHONE_NUMBER>:
-0.09%

Covered Lines:
19851

Relevant Lines:
33451

💛  - Coveralls

Closed as the issue lost relevance.


32bit Support

Hi,
we're using this lib in our rust project and it's great!
Unfortunately we now need to port our project to a 32-bit platform. There 64bit floating point operations are super slow. So we would like to switch to 32-bit floats.
In the osqp itself this seems to be possible using DFLOAT=ON. We’ve tried setting this flag in the build.rs but just that did not make it 😉
Could you give us a hint how much work it will be to port the crate to 32-bit float? Or do you even know of a fort that does it?
Would you be interested in a MR to add 32-bit float support?
Regards,
Jakob

It should be pretty straightforward to add 32-bit float support. Probably just needs a feature flag which switches the definition of osqp::float and osqp_sys::osqp_float as well as setting DFLOAT. Happy to accept a PR for this.

Hi,
thanks for you quick reply and sorry for my late one. I was on vacation...
With your help I managed to compile it as f32. But it did not give us the expected performance gain.
So we're now investigating further to find out why it’s slow on our hardware. I guess it’s something with the C compiler falgs.
As soon as I will find something I’ll open a Pull Request.
Regards,
Jakob

What Rust target are you using to compile?

I delieve the d16 of vfpv3-d16 relates to the fact that the architecture has 16 double-precision floating point registers, so I would expect very little performance improvements from switching to single precision floats.


set-session re-uses a token that may have been revoked by the server

Using set-session does not detect when a token has been revoked due to the "max number of sessions" limit configured in Cumulocity IoT.
Example

Activate a session (no error is thrown)

Using any follow up API calls results in 401 responses
ERROR   serverError: Token '04a5f818-3957-43ae-a7e4-b3fc7a8b86dc' not present for user<EMAIL_ADDRESS>GET https://iot.latest.stage.c8y.io/inventory/managedObjects?q=%24filter%3D+%24orderby%3Dname: 401 security/Unauthorized Token '04a5f818-3957-43ae-a7e4-b3fc7a8b86dc' not present for user<EMAIL_ADDRESS>

The token renewal time (on the server side) seems to also have an effect on the token being revoked.
% c8y devices list
2024-04-28T13:11:55.042+0200	ERROR	Authentication failed (statusCode=401). Try to run set-session again, or check the password
2024-04-28T13:11:55.042+0200	ERROR	serverError: SessionAuth: Token is terminated. Tenant id: t9679. Username<EMAIL_ADDRESS>Token id: 436afea3-ff75-4f06-91b7-ba19d1177a4f, issued at: 2024-04-28T11:00:06.775Z, valid until: 2024-04-30T11:00:06.775Z, revoked at: 2024-04-28T11:11:54.296Z. GET https://example.cumulocity.com/inventory/managedObjects?q=%24filter%3D+%24orderby%3Dname: 401 Authentication failed/Unauthorized SessionAuth: Token is terminated. Tenant id: t9679. Username<EMAIL_ADDRESS>Token id: 436afea3-ff75-4f06-91b7-ba19d1177a4f, issued at: 2024-04-28T11:00:06.775Z, valid until: 2024-04-30T11:00:06.775Z, revoked at: 2024-04-28T11:11:54.296Z.
2024-04-28T13:11:55.042+0200	ERROR	Authentication failed (statusCode=401). Try to run set-session again, or check the password


Standardize scores structure for tasks

I've created a PR https://github.com/embeddings-benchmark/mteb/pull/1034 to address an issue where main_score was not consistently appearing in the scores "at top level", particularly affecting PairClassification and Reranking tasks (e.g., see the TERRa results). I propose changing the structure from:
"cosine": {
  "accuracy": 0.5960912052117264,
  "ap": 0.5608760299515377
  // other metrics
}

to:
"cosine_accuracy": 0.5960912052117264,
"cosine_ap": 0.5608760299515377
// other metrics similarly structured

This approach aligns with what was previously done with STS metrics and may provide clearer and more consistent results across different tasks.

edit by @KennethEnevoldsen:
This would notably lead to breaking changes in the "ap" (which is "max_ap") scores for PairClassification and similarly for reranking. A solution for backward compatibility is to set "max_ap" -> "ap".

@Muennighoff, @orionw tagging you here as you are probably the most familiar with how/if this will cause issues in the leaderboard?

I'm fine with this change as it's more consistent with the changes that @KennethEnevoldsen made to the STS scores I think, no?
In the leaderboard I fixed backward compat by adding the legacy names here: https://huggingface.co/spaces/mteb/leaderboard/blob/main/app.py#L27

I believe this issue is resolved - will close it for now, but if I am missing anything let me know


Add test case for wheel installation with different path

Regression test for #4391 / https://github.com/astral-sh/uv/pull/4393

When you say "path" here, do you mean just the wheel's filename or the whole absolute path to it?
I don't think the path where the wheel file is located should matter  - pip does not care about it (regardless of location):

mypkg is already installed with the same version as the provided wheel. Use --force-reinstall to force an installation of the wheel.

I think we're just using the full file path. I can add test coverage for just the name too.

FWIW one case where I think using the full path would be weird is when you have a cronjob or similar that downloads a "latest" wheel from some place (GH actions build or similar) to a temporary location, which might be a /tmp/<randomname>/ folder, and then runs uv pip install /tmp/<randomname>/*.whl.
In such a case I think the expected behavior would be to reinstall only if the version changed (or if I provide a switch to force reinstalling)...

Here's the mentioned test case https://github.com/astral-sh/uv/pull/4398
We don't do what you want yet :)


Always build shaded jar for pinot-common

Because pinot-hadoop have dependency on pinot-common shaded jar, always build shaded jar for pinot-common

Codecov Report

Merging #3275 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master   #3275      +/-   ##
===========================================
+ Coverage     68.85%   68.9%   +0.04%
  Complexity        4       4
===========================================
  Files           983     983
  Lines         45283   45283
  Branches       6083    6083
===========================================
+ Hits          31180   31202      +22
+ Misses        12018   12004      -14
+ Partials       2085    2077       -8

Impacted Files
Coverage Δ
Complexity Δ

...a/manager/realtime/RealtimeSegmentDataManager.java
75% <0%> (-25%)
0% <0%> (ø)

...impl/dictionary/FloatOffHeapMutableDictionary.java
81.81% <0%> (-10.91%)
0% <0%> (ø)

...impl/dictionary/DoubleOnHeapMutableDictionary.java
68.88% <0%> (-6.67%)
0% <0%> (ø)

...y/aggregation/function/AvgAggregationFunction.java
61.44% <0%> (-2.41%)
0% <0%> (ø)

...edin/pinot/common/metadata/ZKMetadataProvider.java
74.82% <0%> (-1.37%)
0% <0%> (ø)

.../pinot/core/common/datatable/DataTableBuilder.java
78.94% <0%> (-1.17%)
0% <0%> (ø)

...lix/core/realtime/PinotRealtimeSegmentManager.java
72.48% <0%> (-1.06%)
0% <0%> (ø)

...e/impl/dictionary/LongOnHeapMutableDictionary.java
88.88% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...regation/function/customobject/QuantileDigest.java
52.77% <0%> (+0.44%)
0% <0%> (ø)
:arrow_down:

...not/transport/scattergather/ScatterGatherImpl.java
55.69% <0%> (+0.63%)
0% <0%> (ø)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

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


[core/many] Unpin dependencies

Many packages have erroneously pinned deps/devdeps. This PR tidies them up which helps shake out some unnecessary packages from our lockfile.

API change check
API changes are not detected in this pull request.


Video searching issue

Can you delete this issue? Plz

Hi guys, I'm a bit busy ATM, if you want I to go ahead and implement it, go for it. It's easy, basically just look at the network tab in browser for the url and params sent and replicate what I've already done for video search. Docs is in https://gitlab.futo.org/videostreaming/grayjay/-/blob/master/plugin-development.md and here https://gitlab.futo.org/videostreaming/plugins other plugins you can get inspiration from. Overall it should be like no more than 10 lines of codes, maybe less :)
I'll be happy to merge your contributions!

Has there been any update on this issue seems to be present?

Sorry don't have time to work on this at the moment, if anyone feels like please go on and have a look at fixing, it's pretty easy in fact. I'd be happy to merge any working contribution!


Update with v.9

Hi, Can you please update with v 9, I am reading your site documentation and trying this as an exercise simultaneously.

Can you add some comments in the sections where adding depts/orgs
Also how to get users only inside that organization? For e.g. manager find all his employee/users to approve purchases.

thanks
Sergy

Have you seed the document: http://www.aspnetboilerplate.com/Pages/Documents/Zero/Organization-Units


[MINOR][DOCS] Fix multi-line JavaDoc comments style in BlockManagerMaster

What changes were proposed in this pull request?

Fix multi-line JavaDoc comments style in BlockManagerMaster.
Also improve indentation in the before block in BlockManagerReplicationSuite for readability.
Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Only change some styles, should not affect tests.

Close this as it's too minor.


changed Jenkinsfile

Test if I myself can approve this PR

No ;-)

Now I can, but I don't do it ;-)


UP-4768: Add label and type to search portlet input - rel-4-3-patches

https://issues.jasig.org/browse/UP-4768
Issue
This form field should be labelled in some way. Use the label element (either with a "for" attribute or wrapped around the form field), or "title", "aria-label" or "aria-labelledby" attributes as appropriate.
When a form control does not have a name exposed to assistive technologies, users will not be able to identify the purpose of the form control. The name can be provided in multiple ways, including the label element. Other options include use of the title attribute and aria-label which are used to directly provide text that is used for the accessibility name or aria-labelledby which indicates an association with other text on a page that is providing the name. Button controls can have a name assigned in other ways, as indicated below, but in certain situations may require use of label, title, aria-label, or aria-labelledby.
Code Snippet
<input id="Pluto_31_ctf1_14_searchInput" class="searchInput form-control ui-autocomplete-input" name="query" value="" autocomplete="off">

This text input element does not have a name available to an accessibility API. Valid names are: label element, title attribute.
Code Snippet
<input id="Pluto_31_ctf1_14_searchInput" class="searchInput form-control ui-autocomplete-input" name="query" value="" autocomplete="off">

Resolution
Add aria-label and type="search"

Coverage decreased (-0.004%) to 22.867% when pulling 12e6556ac6cb1b6bc3e58dcfed08640e2345da33 on ChristianMurphy:UP-4768-label-search-inputs-rel-4-3 into e6b4afdd506529d90275b783e859c6be70f204ab on Jasig:rel-4-3-patches.


LabeledImageServer coordinate and downsample behaviour

Outline
Currently, LabeledImageServer has behaviour that is definitively broken with respect to coordinates, and some behaviour that is arguably unintuitive with respect to downsampling.
Coordinates
When querying a LabelledImageServer, we create a Pillow image and draw the geometries on it. This means that for any Region2D which does not begin at the origin, we are drawing geometries in a different coordinate space. To return a correct labelled image, we must first translate the geometries to remove the offset of the region request, such that (0,0) in the pillow image is the origin of the region request, rather than always being the origin of the full-sized labelled image as it currently is.
Relevant code:
https://github.com/qupath/qubalab/blob/2bc202787f70ebe1feec5eaa402086d8c97d915a/qubalab/images/labeled_server.py#L94-L125
Downsampling
The current behaviour is arguably unintuitive with respect to downsampling as demonstrated in the other 4 unit tests added. There is some discussion in #25 about whether this behaviour should change. In my view, if retaining the current behaviour, we should warn users (either in code or documentation but ideally both) that they may be receiving rasterised images, and that they should be supplying coordinates based on the downsampled image, rather than the full-sized image that the labeled image server is created from.
Code modifications
Currently, this PR just addresses the offset issue with coordinates.

that they should be supplying coordinates based on the downsampled image, rather than the full-sized image that the labeled image server is created from.

I’ll try this out next week, but it sounds dubious to me. I’d expect that the coordinates for read_region would correspond to downsample=1… but need to check what QuPath does. It is an awkward and fiddly issue, where I think we need to be consistent in both for now - while forming an opinion for how it should look if/when we reconsider the read_region thing entirely.

Tentatively suggesting[^1] that if we set the labeled server downsample in _build_metadata, downsampling/upsampling will behave "as advertised" (relative to the original image)[^2]. Then, if we do something like region = region.downsample_region(self._downsample) in _read_block, users won't have to transform their region requests into the coordinate space of the downsampled image.
However making sense of this in my head for different combinations of downsample in each case and writing suitable tests is not happening after 5pm on a Friday for me. Will revisit next week.
[^1]: at this point I am too confused to be confident
[^2]: although I think it's odd that downsample = 1 will upsample for some imageServers


useFieldArray in 2.0

2.0 has useField, but does not have useFieldArray, which would be more convenient than the render prop helper

BTW, it would be convenient to be able to use a non-context-based way to retrieve the arrayHelper
const form = useFormik()
form.getArrayHelper("friends");

Agree. Good idea

Maybe:
const formikbag = useFormik()
formikbag.getFieldArrayHelper("friends");

Didn't see this issue get tagged with v2 or not. If its up for the next release I would love to try and help out here on this one.

V2 user here--would love to see useFieldArray work its way in. Also happy to help.

would love to see this too

In the meantime, creating a custom hook really boosted performance compared to FieldArray for me (using immutability-helper and it's still a wip, but at least it's a start):
import {useField, useFormikContext} from 'formik'
import update from 'immutability-helper'

const useFieldArray = props => {
  const [field, meta] = useField(props)
  const {setFieldValue} = useFormikContext()

  const push = value => {
    const newFieldArray = update(field.value, {
      $push: [value]
    })
    setFieldValue(field.name, newFieldArray)
  }

  const swap = (indexA, indexB) => {
    // TODO
  }

  const move = (from, to) => {
    // TODO
  }

  const insert = (index, value) => {
    // TODO
  }

  const unshift = value => {
    const newFieldArray = update(field.value, {
      $unshift: [value]
    })
    setFieldValue(field.name, newFieldArray)
  }

  const remove = index => {
    const newFieldArray = update(field.value, {
      $splice: [[index, 1]]
    })
    setFieldValue(field.name, newFieldArray)
  }

  const pop = () => {
    // TODO
  }

  const replace = (index, value) => {
    // TODO
  }

  return [
    field,
    meta,
    {
      push,
      swap,
      move,
      insert,
      unshift,
      remove,
      pop,
      replace
    }
  ]
}

export {useFieldArray}

This is a great concept, did it ever get completed? I'd love to use this in my project. Thanks!

Not sure if you're asking me (or maybe Jared for an official one?), but in case anyone wants it, my custom hook: https://gist.github.com/joshsalverda/d808d92f46a7085be062b2cbde978ae6
Sorry in advance if you're not already using immutability-helper...
I think it's 1-1 with what formik provides. Can likely be improved, but it seems to be working fine for my use cases and all my tests pass so I'm happy 😄Not too worried since once this is officially implemented I'll end up deleting it anyways.
Had to use a ref to store an extra array since field.value didn't seem to update fast enough in things like loops where you might be pushing a lot of values in. Not sure if there's a better way to handle that 🤷♂

Any updates on that?

Just a note for anyone using my custom hook above: I discovered a pretty nasty bug that you may run into. If your array never changes then it's all good, but if it does change then you will run into it. Has to do with the ref I'm using, if field.value changes outside of the hook the ref won't get updated. There is probably a fix for it but I haven't had a chance to really dig into it too much yet.
Tried to look into implementing the hook inside formik directly but I'm not used to the typescript syntax, so not even sure where to start 😅

Any updates?

Just a need this also +1

+1 This would be really helpful. I like to break up forms into sub-components, and the useFormikContext() hook is great for enabling this, but when I wrap some child components inside of a <FieldArray>, I would love to be able to have a useFieldArray() hook that is wired up to the right array specified by the name prop of <FieldArray>.

another implementation https://gist.github.com/sibelius/1e89ed674332d412f2001c184a17701e

another implementation https://gist.github.com/sibelius/1e89ed674332d412f2001c184a17701e

It's important to memorize the functions and return value since eslint warns that they must be added to the useEffect dependencies and will run on each render

+1 I would massively benefit from this right now

+1 I would massively benefit from this right now

I'm using formik in some projects, and just tried out react-hook-form -- if this issue is bugging you, I'd recommend checking that library out. Since it uses uncontrolled components by default, it's been much more efficient for field arrays in my experience

I'm using formik in some projects, and just tried out react-hook-form -- if this issue is bugging you, I'd recommend checking that library out. Since it uses uncontrolled components by default, it's been much more efficient for field arrays in my experience

+1 react-hook-form, controlled forms are pretty bad idea especially when mixing with some kind of state library that has a lot of data in it. You can always remove the value attribute from the input, add a ref using useRef hook instead, and derive the value from the inputRef.current.value within a setTimeout which you reset on each onChange and when the timeout lapses make your api call. This will be much more performant than controlled fields and will scale indefinitely with any library.

+1 react-hook-form, controlled forms are pretty bad idea especially when mixing with some kind of state library that has a lot of data in it. You can always remove the value attribute from the input, add a ref using useRef hook instead, and derive the value from the inputRef.current.value within a setTimeout which you reset on each onChange and when the timeout lapses make your api call. This will be much more performant than controlled fields and will scale indefinitely with any library.

Why were our comments deleted? Is mentioning a competing library frowned upon here? This has been an open issue for nearly two years, and not every form library fits every use case. I have benefited from using formik and value the contributions made here, but silencing candid discussion in github issues concerns me quite a bit.

Why were our comments deleted? Is mentioning a competing library frowned upon here? This has been an open issue for nearly two years, and not every form library fits every use case. I have benefited from using formik and value the contributions made here, but silencing candid discussion in github issues concerns me quite a bit.

controlled forms are a pretty bad idea at scale

I don't know about this. I think controlled forms are fine when they are performant. The issues is that v2 is not very performant due to an over-reliance on Context. You can see two methods we're debating over here: #2931 under<EMAIL_ADDRESS>and /packages/formik/src/Formik.ts:useFormik. We're also pondering one that uses useMutableSource for concurrent mode.
The argument for controlled forms is that you can modify the state of the form based on dependent fields and other methods of combining programmatic updates with user input, and track where those edits come from in a way that is traceable, replayable, etc. Think a zip field that autofills your city and state. There are performant ways to do this, which we are discussing with fervor for a v3 API above.
There's an argument for uncontrolled forms as well, but I don't think the argument should be that they're better, just that they're different and work better for some use cases and not others. Such is the case with the react-hook-form api and the formik api.
In terms of a useFieldArray, this is definitely how FieldArray will work, if a FieldArray component even makes sense after exposing the hook. I'd probably deprecated it in v3 and remove it in v4 after exposing the hook for use in your custom components.

controlled forms are a pretty bad idea at scale

I don't know about this. I think controlled forms are fine when they are performant. The issues is that v2 is not very performant due to an over-reliance on Context. You can see two methods we're debating over here: #2931 under<EMAIL_ADDRESS>and /packages/formik/src/Formik.ts:useFormik. We're also pondering one that uses useMutableSource for concurrent mode.
The argument for controlled forms is that you can modify the state of the form based on dependent fields and other methods of combining programmatic updates with user input, and track where those edits come from in a way that is traceable, replayable, etc. Think a zip field that autofills your city and state. There are performant ways to do this, which we are discussing with fervor for a v3 API above.
There's an argument for uncontrolled forms as well, but I don't think the argument should be that they're better, just that they're different and work better for some use cases and not others. Such is the case with the react-hook-form api and the formik api.
In terms of a useFieldArray, this is definitely how FieldArray will work, if a FieldArray component even makes sense after exposing the hook. I'd probably deprecated it in v3 and remove it in v4 after exposing the hook for use in your custom components.

@davidroeca I don't personally condone the deletion of comments from open source communities. There has been a lot of off-topic chatter related to react-hook-form lately, seems people like it a lot! And there's no problem with that. As a contributor to Formik, there can definitely be some frustration around users who've recently switched deciding to add off-topic comments related to it, like
"hey, how do I do X in Formik?"
"idk just switched to react-hook-form and loving it" - someone not participating in current Formik discussion
I don't believe our Code of Conduct (the Contributor Covenant) clarifies what to do in this exact circumstance. I personally feel as though off-topic comments should be hidden if they don't contribute to conversation (with a reason, and NOT deleted!), but in the event that someone said something like "react-hook-form accomplishes it like X, and it works really well", it's quite easy to both show appreciation for another package (even a "competing library"!) and contribute to Formik's discussion simultaneously.
These are just my views and do not reflect those of the repository owner.

@davidroeca I don't personally condone the deletion of comments from open source communities. There has been a lot of off-topic chatter related to react-hook-form lately, seems people like it a lot! And there's no problem with that. As a contributor to Formik, there can definitely be some frustration around users who've recently switched deciding to add off-topic comments related to it, like
"hey, how do I do X in Formik?"
"idk just switched to react-hook-form and loving it" - someone not participating in current Formik discussion
I don't believe our Code of Conduct (the Contributor Covenant) clarifies what to do in this exact circumstance. I personally feel as though off-topic comments should be hidden if they don't contribute to conversation (with a reason, and NOT deleted!), but in the event that someone said something like "react-hook-form accomplishes it like X, and it works really well", it's quite easy to both show appreciation for another package (even a "competing library"!) and contribute to Formik's discussion simultaneously.
These are just my views and do not reflect those of the repository owner.

If you want to see what the FieldArray API might look like over Formik v3, I have a prototype here:
https://github.com/jawnstreams/formik/pull/22/files

If you want to see what the FieldArray API might look like over Formik v3, I have a prototype here:
https://github.com/jawnstreams/formik/pull/22/files

off-topic comments should be hidden if they don't contribute to conversation (with a reason, and NOT deleted!), but in the event that someone said something like "react-hook-form accomplishes it like X, and it works really well", it's quite easy to both show appreciation for another package (even a "competing library"!) and contribute to Formik's discussion simultaneously.

Seems like a more reasonable approach.
Looking forward to v3!

off-topic comments should be hidden if they don't contribute to conversation (with a reason, and NOT deleted!), but in the event that someone said something like "react-hook-form accomplishes it like X, and it works really well", it's quite easy to both show appreciation for another package (even a "competing library"!) and contribute to Formik's discussion simultaneously.

Seems like a more reasonable approach.
Looking forward to v3!

any update?

any update on this ?


Release 1.0.1

Let's release 1.0.1.
We go back to serving the js and css from amihaiemil.com since now Github allows HTTPS for custom gh-pages domains.

@rultor release it, tag is 1.0.1

@rultor release it, tag is 1.0.1

@amihaiemil OK, I will release it now. Please check the progress here

@rultor release it, tag is 1.0.1

@amihaiemil Done! FYI, the full log is here (took me 3min)

@rultor deploy it

@amihaiemil OK, I'll try to deploy now. You can check the progress here

@rultor deploy it

@amihaiemil Done! FYI, the full log is here (took me 3min)


Remove the center canvas button.

Jaco suggested removing the center button. This would prevent weird behavior that the user doesn't expect.
We could do this, but it would remain an issue for the #468 feature. This would be a temporary fix, but it might be a welcome one.
Originally posted by @philipsens in https://github.com/ibissource/frank-flow/issues/276#issuecomment-1018513593

:tada: This issue has been resolved in version 2.5.10 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Foundationdb support

Sorry, my English is not very good, but I want to know if you can add the visualization support of foundationdb

Hello @Goobercute
Thank you for the idea.

Is there any progress？

Unfortunately, I didn't find a working JDBC driver for FoundationDB.
For now, we can't add support of FoundationDB in DBeaver.
Some links:
https://mvnrepository.com/artifact/com.foundationdb/fdb-sql-layer-jdbc
https://forums.foundationdb.org/t/sql-layer-in-foundationdb/94/10


Remove unknown DocumentCloud documents

This processor removes all documents from DocumentCloud that we have no
reference of in our database ("files" table).

👍


fix to be compatible with ng9

Coverage increased (+0.09%) to 97.059% when pulling 37d20bd8ab176c2150bf2cb6b5bef4e23fa8fe0c on luizb:ng9fix into ceeab1eef526969fd095e9d784d7b3e4ffbafd9e on markdalgleish:master.


Tests don't work on 4.11.0+32bit

In our CI, we systematically test our libraries on 32bit platform (for ESP32 and ARM 32) and it seems that h2 does not work properly on such platform. Failures are reproducible with a simple switch to 4.11.0+32bit. From what I know, we don't reach the initial reader state on the Client_connection implementation - so, paf currently stuck on the loop only on 32bit platform (see this log of a cancelled job).

I can't spot the h2 failure. Is there a better log or stack trace somewhere?

This is the output with 4.11.0+32bit and a696a1c
     test_h2 alias lib_test/runtest
Testing `ocaml-h2 unit tests'.
This run has ID `B7468293-E299-4A60-B7FB-7CAE8E43D46C'.

  [OK]          headers          0   roundtripping.
  [OK]          headers          1   test remove.
  [OK]          headers          2   test replace.

Full test results in `~/dev/ocaml-h2/_build/default/lib_test/_build/_tests/ocaml-h2 unit tests'.
Test Successful in 0.000s. 3 tests run.
test_priority alias lib_test/runtest
Testing `httpaf unit tests'.
This run has ID `CA6818DE-625D-4764-961E-448E960A37BF'.

  [OK]          Reprioritization tests          0   Reprioritize simple.
  [OK]          Reprioritization tests          1   Reprioritize simple exclu...
  [OK]          Reprioritization tests          2   Reprioritize to dependency.
  [OK]          Reprioritization tests          3   Reprioritize to dependenc...
  [OK]          Priority_Queue_Tests            0   Priority queue tests.

Full test results in `~/dev/ocaml-h2/_build/default/lib_test/_build/_tests/httpaf unit tests'.
Test Successful in 0.001s. 5 tests run.
 test_frames alias lib_test/runtest (exit 2)
(cd _build/default/lib_test && ./test_frames.exe)
Fatal error: exception Sys_error("http2-frame-test-case: No such file or directory")
test_h2_client alias lib_test/runtest (exit 1)
(cd _build/default/lib_test && ./test_h2_client.exe)
Testing `ocaml-h2 unit tests'.
This run has ID `9A98671A-7822-48DA-A04E-3F82434021A0'.

> [FAIL]        client_connection          0   initial reader state.
  [FAIL]        client_connection          1   set up client connection.
  [FAIL]        client_connection          2   invalid connection preface fro...
  [FAIL]        client_connection          3   invalid connection preface fro...
  [FAIL]        client_connection          4   simple GET request.
  [FAIL]        client_connection          5   data larger than declared.
  [FAIL]        client_connection          6   stream error on idle stream.
  [FAIL]        client_connection          7   continuation frame (success).
  [FAIL]        client_connection          8   stream correctly transitions s...
  [FAIL]        client_connection          9   continuation frame on another ...
  [FAIL]        client_connection         10   push handler successful response.
  [FAIL]        client_connection         11   push handler cancels push.
  [FAIL]        client_connection         12   ping.
  [FAIL]        client_connection         13   stream level error handler cal...
  [FAIL]        client_connection         14   starting an h2c connection.
  [FAIL]        client_connection         15   non-zero `content-length` and ...
  [FAIL]        client_connection         16   premature remote close with pe...
  [FAIL]        client_connection         17   request, server sends RST_STRE...
  [FAIL]        client_connection         18   request, server sends RST_STRE...
  [FAIL]        client_connection         19   test connection shutdown.
  [FAIL]        client_connection         20   reading the response body as i...
  [FAIL]        client_connection         21   flow control.
  [FAIL]        client_connection         22   flow control -- can send empty...

┌──────────────────────────────────────────────────────────────────────────────┐
│ [FAIL]        client_connection          0   initial reader state.           │
└──────────────────────────────────────────────────────────────────────────────┘
[exception] File "lib/client_connection.ml", line 188, characters 4-10: Assertion failed

Logs saved to `~/dev/ocaml-h2/_build/default/lib_test/_build/_tests/ocaml-h2 unit tests/client_connection.000.output'.
 ──────────────────────────────────────────────────────────────────────────────

Full test results in `~/dev/ocaml-h2/_build/default/lib_test/_build/_tests/ocaml-h2 unit tests'.
23 failures! in 0.005s. 23 tests run.
test_h2_server alias lib_test/runtest (exit 1)
(cd _build/default/lib_test && ./test_h2_server.exe)
Testing `ocaml-h2 unit tests'.
This run has ID `521BB479-49C2-4DA8-A1A7-D60560ABBF4B'.

  [OK]          server_connection          0   initial reader state.
  [OK]          server_connection          1   shutdown reader closed.
> [FAIL]        server_connection          2   malformed frame.
  [FAIL]        server_connection          3   malformed frame.
  [FAIL]        server_connection          4   malformed frame.
  [FAIL]        server_connection          5   send frames after a padded frame.
  [FAIL]        server_connection          6   continuation frame on the same...
  [FAIL]        server_connection          7   continuation frame on another ...
  [FAIL]        server_connection          8   frame size error (frame size e...
  [FAIL]        server_connection          9   frame size error on a priority...
  [FAIL]        server_connection         10   connection preface read with m...
  [OK]          server_connection         11   settings that exceeds the maxi...
  [FAIL]        server_connection         12   open existing stream.
  [FAIL]        server_connection         13   dependent stream.
  [FAIL]        server_connection         14   server push.
  [FAIL]        server_connection         15   CONNECT method.
  [FAIL]        server_connection         16   CONNECT method (malformed).
  [FAIL]        server_connection         17   Client sends 0 max concurrent ...
  [FAIL]        server_connection         18   empty fixed streaming response.
  [FAIL]        server_connection         19   starting an h2c connection.
  [FAIL]        server_connection         20   non-zero `content-length` and ...
  [FAIL]        server_connection         21   premature remote close with pe...
  [FAIL]        server_connection         22   frame size error unknown frame.
  [FAIL]        server_connection         23   reading the request body as it...
  [FAIL]        server_connection         24   flow control.
  [FAIL]        server_connection         25   flow control -- can send empty...
  [FAIL]        server_connection         26   trailers.

┌──────────────────────────────────────────────────────────────────────────────┐
│ [FAIL]        server_connection          2   malformed frame.                │
└──────────────────────────────────────────────────────────────────────────────┘
[exception] File "lib/server_connection.ml", line 186, characters 4-10: Assertion failed

Logs saved to `~/dev/ocaml-h2/_build/default/lib_test/_build/_tests/ocaml-h2 unit tests/server_connection.002.output'.
 ──────────────────────────────────────────────────────────────────────────────

Full test results in `~/dev/ocaml-h2/_build/default/lib_test/_build/_tests/ocaml-h2 unit tests'.
24 failures! in 0.006s. 27 tests run.

Got it. Most of these just look like the submodules weren't pulled.
I'll look at the assertion failure though.

Oh this is great. The assertion is there for 32-bit system too! :D
I'll get to this soon, but first I need to figure out how to get a 32-bit system.

@anmonteiro use a Linux box or docker on macOS to be able to run 32bits code. With esy you can do the resolution below to force 32bits.
{
  "resolutions": {
    "ocaml": {
      "source": "esy-ocaml/ocaml#dd66cad318e04c7f2c753f8ce2fd8851e975f89a",
      "override": {
        "build": [
          "./esy-configure --prefix $cur__install --build=x86_64-pc-linux-gnu --host=i386-linux CC='gcc -m32' AS='as --32' ASPP='gcc -m32 -c' PARTIALLD='ld -r -melf_i386'",
          "./esy-build"
        ]
      }
    }
  }
}


Cannot debug jest tests using Node v8

Do you want to request a feature or report a bug?
Both?
Bug: When debugging using Node v8 inspector protocol instead of legacy debug it does not hit breakpoints
The slim debugging docs: https://facebook.github.io/jest/docs/en/troubleshooting.html#content
mention to use --debug-brk so maybe jest is behaving as designed and not intended to work with Node v8 and in that case this would be feature request :)
Original issue was thought to be VScode jest configuration, but perhaps it's limitation with jest?
https://github.com/Microsoft/vscode/issues/28007
What is the current behavior?
When using Node v6.10 debugging works as expected
When using Node v8 debugger does not stop at debugger statements or breakpoints
If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.
What is the expected behavior?
When using Node v8 debugging
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
Jest: v19.0.2
Node: v6.10.3 (working) / v8 (not-working)
npm: 3.10.10
OS: Windows 10 (14393.1198)
...
"devDependencies": {
    "@types/jest": "^19.2.3",
    "@types/node": "^7.0.18",
    "jest": "^19.0.2",
    "ts-jest": "^19.0.14",
    "typescript": "^2.3.2"
  },
  "jest": {
    "testMatch": ["**/dist/**/?(*.)(spec|test).js?(x)"],
    "moduleFileExtensions": [
      "ts",
      "tsx",
      "js",
      "json"
    ]
  }

I couldn't get debugging to work on chrome so I setup debug from VSCode and things were good. Then it broke when I tried updating to node v8.  I reverted back to Node v6.10 to confirm and opened the issue with VScode. They took a look and thought maybe an issue with jest.
I was hoping someone could just confirm the issue or link a project that does have debugging setup and works for node v8 that I can try out.

https://github.com/facebook/jest/issues/1652

Ah, I see.  I guess this is duplicate of the referenced issue and since that is closed this one could also be closed.  I'll go upvote the node issue and pray some node people take a look


CSRF fix.

With these CSRF settings I can use the controller with qbittorrent-nox v3.3.1. If you try to login with a browser it will use the same HTTP header convention as in this pull request.

Approved!


HSEARCH-2352 Index.NO is being ignored for numeric fields (and also boolean or date fields for Elasticearch)

https://hibernate.atlassian.net/browse/HSEARCH-2352
Necessary for HSEARCH-2260.

Yes, I prefer this approach, it's far clearer. I think you should add a couple of constants to make it less fragile - see my comments inline. Apart from that, it looks good.

Done. I'll merge once the build has passed.

Merged. Thanks!


fixes #852

Reference Issues
Translation of Filter of Date Columns #852
Changes
Added makeT() function from localization.ts and declared const t

Fixed initial commit code where I did not wrap strings with t

Ah right, I have just learnt that the update of the /static/locales/en.client.json file is handled automatically:
https://github.com/gristlabs/grist-core/pull/888
Congrats @thomasweaver627 for your first PR!

Congrats @thomasweaver627 for your first PR!

Thank you @fflorent!!


The kserve install failed with TARGET_OPERATOR=rhods

kserve install failed with the following error .
[perfci@f23-h33-000-6018r ~]$ oc -n redhat-ods-operator describe subs/rhods-operator
...
  Conditions:
    Message:               constraints not satisfiable: no operators found from catalog rhods-catalog in namespace openshift-marketplace referenced by subscription rhods-operator, subscription rhods-operator exists
    Reason:                ConstraintsNotSatisfiable
    Status:                True
    Type:                  ResolutionFailed
    Last Transition Time:  2023-08-22T19:06:09Z
    Message:               targeted catalogsource openshift-marketplace/rhods-catalog missing
    Reason:                UnhealthyCatalogSourceFound
    Status:                True
    Type:                  CatalogSourcesUnhealthy
  Last Updated:            2023-08-22T19:06:09Z

RHODS 1.31 does not have alpha channel so it needs to test with 1.32

This is done


Added action dependency after all actions have been cleaned initially.

This was discovered after discovering issue #50.  If I have the following code:
public function configure()
{
    // ...
    $this->addActions(array(
        new BatchActionCollection(),
        new ListAction(),
    ));
}

then the initialisation of the BatchActionCollection will fail as it can't find the list action required (as the List action hasn't been initialized yet).  This commit moves the dependency check to after the first pass over the raw actions, so that all actions are present in the array, before running the check.

+1, please merge :)


▲  Something went wrong

npx create-solid my-scalper-app
bun create solid ./my-solid-app
yarn create solid ./my-solid-app

Select Is this a Solid-Start project? — YES
Apple M1 Pro, macOS Sonoma, MBP 2021

Select Is this a Solid-Start project? — *

NO*:

Could you provide your node version? The CLI doesn't work with <=18 I believe.

node --version
v18.19.1

Thanks! I'll be able to test soon and see what I find

I can't reproduce this on my end :(

Would you be able to try npx @begit/cli solidjs/solid-start --subdir examples/basic basic-example on your system? It's possible that it's begit that's broken here. Also this will give you a working example to work from if the CLI doesn't currently work for you

Thanks for reproducing! Would you be able to try that same command again? I've just pushed an update to begit which should make the error messages much better.

 % npx @begit/cli solidjs/solid-start --subdir examples/basic basic-exampl
file:///home/xxx/.npm/_npx/3afe89fd084d6a83/node_modules/@begit/core/dist/index.js:36
  return json[0].sha;
                 ^

TypeError: Cannot read properties of undefined (reading 'sha')
    at fetchLatestCommit (file:///home/xxx/.npm/_npx/3afe89fd084d6a83/node_modules/@begit/core/dist/index.js:36:18)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async downloadToFile (file:///home/xxx/.npm/_npx/3afe89fd084d6a83/node_modules/@begit/core/dist/index.js:40:16)
    at async downloadAndExtract (file:///home/xxx/.npm/_npx/3afe89fd084d6a83/node_modules/@begit/core/dist/index.js:85:19)
    at async downloadRepo (file:///home/xxx/.npm/_npx/3afe89fd084d6a83/node_modules/@begit/core/dist/index.js:93:5)
    at async Object.handler (file:///home/xxx/.npm/_npx/3afe89fd084d6a83/node_modules/@begit/cli/dist/index.js:44:7)
    at async Object.run (/home/xxx/.npm/_npx/3afe89fd084d6a83/node_modules/cmd-ts/dist/cjs/command.js:154:30)
    at async runSafely (/home/xxx/.npm/_npx/3afe89fd084d6a83/node_modules/cmd-ts/dist/cjs/runner.js:26:24)
    at async run (/home/xxx/.npm/_npx/3afe89fd084d6a83/node_modules/cmd-ts/dist/cjs/runner.js:10:20)
    at async main (file:///home/xxx/.npm/_npx/3afe89fd084d6a83/node_modules/@begit/cli/dist/index.js:52:3)

Node.js v20.15.1

Thanks! Looks like the request retrieving the most recent commit's sha isn't returning the correct value. Does this link work for you? https://api.github.com/repos/tommypop2/begit/commits?per_page=1
It's basically the same thing that the CLI does under the hood to fetch the latest commit hash.

It will return 'API rate limit exceeded '
I have already add GITHUB_API_TOKEN environment variable.
https://github.com/Tommypop2/begit/blob/71549357966bacfcc2a372f9d57c7b51b906b2a0/packages/core/src/utils.ts#L29
Add GITHUB_API_TOKEN to header will fix this issue
https://docs.github.com/en/rest/authentication/authenticating-to-the-rest-api?apiVersion=2022-11-28

Ah, ok. Yeah I think I'll try using the to the GITHUB_API_TOKEN env variable on each request, and, if that fails, I'll resort to git ls-remote (degit actually does this by default)

@lakako I've just added support for the BEGIT_GH_API_KEY env variable to begit. Would you mind retrying the above begit command with this environment variable set.
I opted to not use GITHUB_API_TOKEN because people might have this set with the intention of another program using it and I felt hooking into it could mean begit is making requests with an API key that the user doesn't want used for that purpose

I’ve been seeing this “Something went wrong” error for a week at work. I’ve assumed it is to do with being behind a corporate proxy or a similar network/auth related issue, because that’s been an ongoing issue in various projects.
However, those network and auth issues are resolved, yet “pnpm create solid” with all default options fails with “Something went wrong” consistently.
Is there any way to turn on more verbose debugging or logging?
I tried the curl mentioned above and it returns valid json.
Thanks for any help!

Run npx @begit/cli@latest solidjs/solid-start --subdir examples/basic basic-exampl. the problem has gone.
but run 'pnpm create solid@latest' still cause ▲  Something went wrong

That's interesting. When I run the npx command I get a trace that ultimately complains about a self signed certificate in the chain. That's highly likely because of the corporate environment I'm in, however all other network activity is fine, including plain curl with no environment variables.
Any ideas?

I don't like it, but setting NODE_TLS_REJECT_UNAUTHORIZED=0 in the environment works around it.
Unsettling because everything else works with ssl fine, but a way forward.
I wonder if fetch is not using the machines certificate chain?

OK, some success! The env var NODE_EXTRA_CA_CERTS needs to be set, in my case (unbuntu) to /etc/ssl/certs/ca-certificates.crt but your mileage may vary. With that set, things work.

@lakako I've just released a new version of create-solid, which uses the updated begit version, so it should resolve your issue :)

@aellerton Great things work now!! Do other CLI tools work properly with your setup without modification? I suspect it's where begit uses the github API to fetch the most recent commit hash, whereas tools like degit or tiged use git ls-remote and parse the stdout.
I thought I fixed the incredibly vague "Something Went Wrong" error a while ago, but evidently I haven't :( I'll have to try fixing it again soon

@Tommypop2 It works fine. Thank you.

Closing this as everything seems to be resolved.


fix: avoid duplicate parameter names

same change as in base repo:

https://github.com/Rich-Harris/devalue/pull/27

but rebased to match nuxt fork's state
resolves #11

Thanks <3


Modify Job.getJobs according to v1.5 changes

Flink changes the response from /jobs in v1.5.
https://github.com/apache/flink/pull/4805
They moved the grouped keys like jobs-runnning, jobs-cancelled to the jobs key.

I released 2.3.0
https://github.com/matsumana/flink_exporter/releases/tag/2.3.0
Thank you.


OAS: Endpoint reclustering

If we learned over time sufficient information to group endpoints together - do it.
Remember historical OperationIDs into custom property.

Closing since it's outdated.


Bug in UFF Geometry Optimization with unrecognized atom types (Se2+2)

Configuration:

RDKit Version: 2019.09.2
Operating system: Ubuntu Linux 18.04
Python version (if relevant): 3.7.5
Are you using conda? Yes
If you are using conda, which channel did you install the rdkit from? rdkit

Description:
I am trying to do geometry optimization (GO) for some selenium-containing organic compounds.
The Se is sp2 hybridized, which UFF doesn't have parameters for.
I have read on other threads (#200) that in this case it should fall back on "more relaxed defaults",
however I've found that it often ends up producing unrealistic geometries with ridiculous bond lengths (even when the GO runs for many iterations and returns 0).
I'm working with rather large molecules, and this bug only occurs sometimes (due to the randomness of configuration generation), so instead I've written a script (see below) that distorts simple molecules in a way similar to the GO results I've observed.
Specifically, I take furan (https://en.wikipedia.org/wiki/Furan) and selenophene (https://en.wikipedia.org/wiki/Selenophene), which are analogous sp2 hybridized aromatic molecules. The only difference is the type of heteroatom (Se vs O). UFF has all parameters for furan but not for selenophene. The script moves the heteroatom progressively farther outside of the ring, and records the change in energies. These are before/after pics (for furan; selenophene looks analogous):
Before distortion (should be low energy):

After distortion (high energy):

(the script also saves these as .mol files for you to visualize if you want)
The results of this code are that:

furan behaves as expected, with the energy in the second image being much higher than the first.
selenophene shows almost no energy difference between the 2 configurations shown, which is very unphysical. This is similar to the observation by @JLVarjo in #200 where the potential gradients are approximately 0 for the improperly parametrized atom.
if I manually change the hybridization of the Se atom to sp3 (which UFF has parameters for), then the Se atom behaves similar to oxygen. This suggests that the GO isn't falling back on Se3+2 geometry when the hybridization is not manually changed.

I think this is a bug, similar to #200, and that the fallback behaviour for unrecognized atoms should be different. @greglandrum can you comment on this?

My code
from rdkit import Chem
from rdkit.Chem import AllChem

def get_uff_energy(mol, confId):
    return AllChem.UFFGetMoleculeForceField(mol, confId=confId).CalcEnergy()

def stretch_5ring_heteroatom(mol, mol_name):
    """
    Function to distort the ring and get the energies from the distortion
    """

    # Track the energies
    energy_dict = dict()

    # Embed the molecule and export embedding
    AllChem.EmbedMolecule(mol)
    Chem.MolToMolFile(mol, f"{mol_name}_E0_reference.mol")
    energy_dict['E0'] = get_uff_energy(mol, 0)

    # Calculate the vector displacement to move the 5th atom out
    #######################################
    print(f"Atom type being displaced: {mol.GetAtomWithIdx(4).GetSymbol()}")
    conf = mol.GetConformer(0)
    atom_positions = conf.GetPositions().copy()  # Just to prevent modification

    # Average the positions of atoms 1-2 to get the vector position on
    # the ring across from the heteroatom
    # (details not important, just visualize the resulting molecules
    # if you are confused by this procedure)
    point_across = (atom_positions[1] + atom_positions[2]) / 2
    displacement_vec = atom_positions[4] - point_across

    # Displace the hetero atom in 2 rounds
    for alpha in [1, 2]:
        conf.SetAtomPosition(4, atom_positions[4] + alpha * displacement_vec)
        Chem.MolToMolFile(mol, f"{mol_name}_E{alpha}_displaced.mol")
        energy_dict[f"E{alpha}"] = get_uff_energy(mol, 0)

    return energy_dict

# Test with Furan (which should show heavy response to displacement)
furan = Chem.AddHs(Chem.MolFromSmiles("c1ccco1"))
print(f"Furan Energies: {stretch_5ring_heteroatom(furan, 'furan')}")
# ^^ something like:
# Furan Energies: {'E0': 36.290385123719425, 'E1': 3570.7886473008466, 'E2': 16626.470844761654}
# this is expected since its a huge stretch (see resulting mol files to check geometries)

selenophene = Chem.AddHs(Chem.MolFromSmiles("c1ccc[se]1"))
print(f"selenophene Energies: {stretch_5ring_heteroatom(selenophene, 'selenophene')}")
# ^^ throws error: UFFTYPER: Unrecognized atom type: Se2+2 (4)
# ^^ Energies DON'T CHANGE WITH DISTANCE
# {'E0': 26.92499940076006, 'E1': 26.92499940076159, 'E2': 26.92499940076264}

# Try changing the hybridization of the Se to sp3, which is in the UFF model
selenophene.GetAtomWithIdx(4).SetHybridization(
    Chem.rdchem.HybridizationType.SP3)
print(f"sp3 selenophene Energies: {stretch_5ring_heteroatom(selenophene, 'sp3-selenophene')}")
# ^^ Shows expected behaviour
# {'E0': 30.208983893823742, 'E1': 2939.3392928450435, 'E2':
# 12475.228375067853}

* selenophene shows almost **no energy difference** between the 2 configurations shown, which is very unphysical. This is similar to the observation by @JLVarjo in [Unrecognised atom type in UFF for S atom #200](https://github.com/rdkit/rdkit/issues/200) where the potential gradients are approximately 0 for the improperly parametrized atom.

Just reminding that the abovementioned side-note-bug (exploded conformations with lacking UFF parameters) of #200 still remains (tested with RDKit 2024.03.6), even though that ticket was closed as the main issue was apparently fixed.


[fastecdsa] ECC corner cases

Ensure 2Q = inf for ord(Q)=2 points
Better inf handling post scalar multiplication
Unit tests

Co-authored-by: Luis Rivera-Zamarripa<EMAIL_ADDRESS>Co-authored-by: Jesús-Javier Chi-Domínguez<EMAIL_ADDRESS>Tagging @luinxz and @JJChiDguez for review.
This PR solves 2 defects:

You cannot always reduce scalars modulo curve.q. Only if the input point has order curve.q.
Point doubling did not handle the ord(Q) = 2 case correctly.

Edit: the golden subgroup values in the tests are from sagemath.

Thanks for identifying these issues and submitting the fixes, I’ll review these tomorrow and get them merged if I don’t see any issues.

Sorry for the massive delay on merging this and many thanks for the fix!

For reference, this (and some other fixes) have been released in v2.1.4on pypi.


Enhancement - Modify the string value of alias to be in LowerCase or Uppercase

Could we add two more steps to modify the value of an alias to be in lowercase or uppercase? Or, could Iridium accept argument(s) when running Javascript? Thanks a lot.

This has been implemented in release 0.0.90.
https://autogeneral.gitbooks.io/iridiumapplicationtesting-gettingstartedguide/content/releases.html

Thanks a lot.
Verified the steps and now close it.


Add shift-click compatability for grid filters

Shift-clicking a grid filter when the GUI of a grid is open, the grid filter goes in the storage system rather than one of the filter slots. This is pretty annoying. It should go into the filter slot, not the storage system.

@raoulvdberge Thanks,


fix: compile error in FluentTreeItem when trying to specify 'stopPropagation'

Hello, when I try to specify onclick:stopPropagation and I have already defined an onclick handler, I receive the following compile error:

The component parameter 'onclick' is used two or more times for this component. Parameters must be unique (case-insensitive). The component parameter 'onclick' is generated by the 'onclick:stopPropagation' directive attribute.

The code I'm using is:
<FluentTreeItem @onclick="OnNavigationItemClick" @onclick:stopPropagation="true">
</FluentTreeItem>

@code{
    private Task OnNavigationItemClick(MouseEventArgs args) { ... }
}

I'm new to using this behavior and so I'm not sure if I'm doing something wrong, but I tested this just using a div and didn't receive this error.
I'm using v2.2.0-preview.2 of the package.

The @onclick:stopPropagation only woks on HTML DOM elements. See also https://learn.microsoft.com/en-us/aspnet/core/blazor/components/event-handling?view=aspnetcore-7.0#stop-event-propagation


files.upload fail in latest version 2.3.1

Description
I've moved by bot application code to latest version 2.3.1 after which png files are not being uploaded to channels.
file_buf  is BytesIO object
            file_buf.seek(0)
            jsn = dict()
            jsn["channels"] = self.gdict[channel_name]
            jsn["file"] = base64.b64encode(file_buf.read()).decode()
            jsn["initial_comment"] = caption
            jsn["mimetype"] = "image/png"
            jsn["filetype"] = "png"
            jsn["pretty_type"] = "PNG"
            out = self.bot.api_call(
                "files.upload",
                json=json.dumps(jsn)
            )

In return I'm getting "no_file_data" error. How can I upload a image in 2.3.1 WebClient api?

@abbazs Sorry for our belated response here. 🙇
You cannot have any binary data in the JSON text data structure.
The recommended way is using files_upload method. The method internally calls api_call wisely. Here is a simple snippet demonstrating how to use it for your use case.
from io import BytesIO
import os
import json
import logging
from slack import WebClient

token = os.environ["SLACK_BOT_TOKEN"]
webclient = WebClient(token=token)
logging.basicConfig(level=logging.DEBUG)

with open('./test-image.png', 'rb') as f:
    out = webclient.files_upload(
        file=BytesIO(f.read()),
        channels="C123,C234",
        initial_comment="This is a test",
        mimetype="image/png",
        filetype="png",
        pretty_type="PNG"
    )

Allow me to close this issue now. Hope this is helpful to you despite the long delay.


[Normalize.css]->[Others]

Normalize.css
makes browsers render all elements more consistently and in line with modern standards.
Link: https://necolas.github.io/normalize.css/
Checklist:

[x] I have performed a self-review of submitted resource and its follows the guidelines of the project.

Not a design resource.


Update drugbank

update drugbank knowledge source

tentatively slated for inclusion in the KG2.8.4pre build

While testing out the update, I ran the report scripts on the old vs new DrugBank JSON. The report script failed, so 172fedc also features updates to the report script so that it will finish. Below is are the outputs of the report scripts. One important thing to note is that the version in the node name will have the same version number (5.1) since that is what is given in the drugbank.xml file. However, I know that the previous version is 5.1.9 from its name in the S3 bucket and that the current version is 5.1.10 since that was the tag when I downloaded it.

New

Old

{
    "_number_of_nodes": 15236,
    "_number_of_edges": 3018286,
    "_report_datetime": "2023-06-20 21:54:08",
    "number_of_nodes_by_curie_prefix": {
        "identifiers_org_registry": 1,
        "DRUGBANK": 15235
    },
    "number_of_nodes_without_category__by_curie_prefix": {},
    "number_of_nodes_by_category_label": {
        "information_resource": 1,
        "chemical_entity": 3008,
        "small_molecule": 12227
    },
    "number_of_nodes_by_source": {
        "identifiers_org_registry:drugbank": 15236
    },
    "number_of_edges_by_predicate_curie": {
        "DRUGBANK:category": 64973,
        "DRUGBANK:drug-interaction": 2866931,
        "DRUGBANK:external-identifier": 19614,
        "DRUGBANK:external-identifier-protein": 93,
        "DRUGBANK:pathway": 3780,
        "DRUGBANK:inhibitor": 4131,
        "DRUGBANK:group": 18032,
        "DRUGBANK:atc-code": 5383,
        "DRUGBANK:atc-code-level": 17177,
        "DRUGBANK:binder": 502,
        "DRUGBANK:agonist": 1390,
        "DRUGBANK:target": 10814,
        "DRUGBANK:antibody": 84,
        "DRUGBANK:ligand": 706,
        "DRUGBANK:activator": 253,
        "DRUGBANK:inducer": 181,
        "DRUGBANK:substrate": 110,
        "DRUGBANK:cofactor": 193,
        "DRUGBANK:antagonist": 2191,
        "DRUGBANK:chaperone": 17,
        "DRUGBANK:modulator": 85,
        "DRUGBANK:downregulator": 27,
        "DRUGBANK:stimulator": 18,
        "DRUGBANK:product_of": 41,
        "DRUGBANK:allosteric_modulator": 12,
        "DRUGBANK:negative_modulator": 32,
        "DRUGBANK:positive_allosteric_modulator": 983,
        "DRUGBANK:inverse_agonist": 29,
        "DRUGBANK:partial_agonist": 84,
        "DRUGBANK:potentiator": 162,
        "DRUGBANK:blocker": 134,
        "DRUGBANK:regulator": 44,
        "DRUGBANK:intercalation": 2,
        "DRUGBANK:inhibitory_allosteric_modulator": 3,
        "DRUGBANK:adduct": 2,
        "DRUGBANK:multitarget": 7,
        "DRUGBANK:stabilization": 10,
        "DRUGBANK:partial_antagonist": 1,
        "DRUGBANK:suppressor": 3,
        "DRUGBANK:weak_inhibitor": 2,
        "DRUGBANK:binding": 10,
        "DRUGBANK:degradation": 1,
        "DRUGBANK:antisense_oligonucleotide": 5,
        "DRUGBANK:incorporation_into_and_destabilization": 1,
        "DRUGBANK:cleavage": 10,
        "DRUGBANK:neutralizer": 2,
        "DRUGBANK:oxidizer": 3,
        "DRUGBANK:inactivator": 6,
        "DRUGBANK:nucleotide_exchange_blocker": 1,
        "DRUGBANK:inhibition_of_synthesis": 1,
        "DRUGBANK:carrier": 1,
        "DRUGBANK:translocation_inhibitor": 2,
        "DRUGBANK:gene_replacement": 1,
        "DRUGBANK:chelator": 2,
        "DRUGBANK:component_of": 4
    },
    "number_of_edges_by_predicate_type": {
        "category": 64973,
        "drug-interaction": 2866931,
        "external-identifier": 19614,
        "external-identifier-protein": 93,
        "pathway": 3780,
        "inhibitor": 4131,
        "group": 18032,
        "atc-code": 5383,
        "atc-code-level": 17177,
        "binder": 502,
        "agonist": 1390,
        "target": 10814,
        "antibody": 84,
        "ligand": 706,
        "activator": 253,
        "inducer": 181,
        "substrate": 110,
        "cofactor": 193,
        "antagonist": 2191,
        "chaperone": 17,
        "modulator": 85,
        "downregulator": 27,
        "stimulator": 18,
        "product of": 41,
        "allosteric modulator": 12,
        "negative modulator": 32,
        "positive allosteric modulator": 983,
        "inverse agonist": 29,
        "partial agonist": 84,
        "potentiator": 162,
        "blocker": 134,
        "regulator": 44,
        "intercalation": 2,
        "inhibitory allosteric modulator": 3,
        "adduct": 2,
        "multitarget": 7,
        "stabilization": 10,
        "partial antagonist": 1,
        "suppressor": 3,
        "weak inhibitor": 2,
        "binding": 10,
        "degradation": 1,
        "antisense oligonucleotide": 5,
        "incorporation into and destabilization": 1,
        "cleavage": 10,
        "neutralizer": 2,
        "oxidizer": 3,
        "inactivator": 6,
        "nucleotide exchange blocker": 1,
        "inhibition of synthesis": 1,
        "carrier": 1,
        "translocation inhibitor": 2,
        "gene replacement": 1,
        "chelator": 2,
        "component of": 4
    },
    "number_of_edges_by_predicate_curie_prefixes": {
        "DRUGBANK": 3018286
    },
    "number_of_predicates_by_predicate_curie_prefixes": {
        "DRUGBANK": 55
    },
    "number_of_edges_by_source": {
        "identifiers_org_registry:drugbank": 3018286
    },
    "types_of_pairs_of_curies_for_xrefs": {},
    "types_of_pairs_of_curies_for_equivs": {},
    "number_of_nodes_by_source_and_category": {
        "identifiers_org_registry:drugbank": {}
    }
}

{
    "_number_of_nodes": 14595,
    "_number_of_edges": 2913688,
    "_report_datetime": "2023-06-20 21:52:51",
    "number_of_nodes_by_curie_prefix": {
        "identifiers_org_registry": 1,
        "DRUGBANK": 14594
    },
    "number_of_nodes_without_category__by_curie_prefix": {},
    "number_of_nodes_by_category_label": {
        "information_resource": 1,
        "chemical_entity": 2682,
        "small_molecule": 11912
    },
    "number_of_nodes_by_source": {
        "identifiers_org_registry:drugbank": 14595
    },
    "number_of_edges_by_predicate_curie": {
        "DRUGBANK:category": 62058,
        "DRUGBANK:drug-interaction": 2768080,
        "DRUGBANK:external-identifier": 19185,
        "DRUGBANK:external-identifier-protein": 93,
        "DRUGBANK:pathway": 3780,
        "DRUGBANK:inhibitor": 3686,
        "DRUGBANK:group": 17278,
        "DRUGBANK:atc-code": 5152,
        "DRUGBANK:atc-code-level": 16436,
        "DRUGBANK:binder": 471,
        "DRUGBANK:agonist": 1344,
        "DRUGBANK:target": 10877,
        "DRUGBANK:antibody": 61,
        "DRUGBANK:ligand": 704,
        "DRUGBANK:activator": 195,
        "DRUGBANK:inducer": 182,
        "DRUGBANK:substrate": 95,
        "DRUGBANK:cofactor": 193,
        "DRUGBANK:antagonist": 2149,
        "DRUGBANK:chaperone": 17,
        "DRUGBANK:modulator": 82,
        "DRUGBANK:downregulator": 11,
        "DRUGBANK:stimulator": 19,
        "DRUGBANK:product_of": 40,
        "DRUGBANK:negative_modulator": 32,
        "DRUGBANK:positive_allosteric_modulator": 983,
        "DRUGBANK:inverse_agonist": 29,
        "DRUGBANK:partial_agonist": 81,
        "DRUGBANK:potentiator": 162,
        "DRUGBANK:blocker": 115,
        "DRUGBANK:intercalation": 2,
        "DRUGBANK:inhibitory_allosteric_modulator": 2,
        "DRUGBANK:allosteric_modulator": 11,
        "DRUGBANK:adduct": 2,
        "DRUGBANK:multitarget": 7,
        "DRUGBANK:stabilization": 9,
        "DRUGBANK:partial_antagonist": 1,
        "DRUGBANK:suppressor": 3,
        "DRUGBANK:weak_inhibitor": 2,
        "DRUGBANK:binding": 10,
        "DRUGBANK:degradation": 1,
        "DRUGBANK:antisense_oligonucleotide": 5,
        "DRUGBANK:incorporation_into_and_destabilization": 1,
        "DRUGBANK:neutralizer": 3,
        "DRUGBANK:cleavage": 9,
        "DRUGBANK:oxidizer": 3,
        "DRUGBANK:inactivator": 6,
        "DRUGBANK:nucleotide_exchange_blocker": 1,
        "DRUGBANK:inhibition_of_synthesis": 1,
        "DRUGBANK:translocation_inhibitor": 2,
        "DRUGBANK:gene_replacement": 1,
        "DRUGBANK:regulator": 10,
        "DRUGBANK:chelator": 2,
        "DRUGBANK:component_of": 4
    },
    "number_of_edges_by_predicate_type": {
        "category": 62058,
        "drug-interaction": 2768080,
        "external-identifier": 19185,
        "external-identifier-protein": 93,
        "pathway": 3780,
        "inhibitor": 3686,
        "group": 17278,
        "atc-code": 5152,
        "atc-code-level": 16436,
        "binder": 471,
        "agonist": 1344,
        "target": 10877,
        "antibody": 61,
        "ligand": 704,
        "activator": 195,
        "inducer": 182,
        "substrate": 95,
        "cofactor": 193,
        "antagonist": 2149,
        "chaperone": 17,
        "modulator": 82,
        "downregulator": 11,
        "stimulator": 19,
        "product of": 40,
        "negative modulator": 32,
        "positive allosteric modulator": 983,
        "inverse agonist": 29,
        "partial agonist": 81,
        "potentiator": 162,
        "blocker": 115,
        "intercalation": 2,
        "inhibitory allosteric modulator": 2,
        "allosteric modulator": 11,
        "adduct": 2,
        "multitarget": 7,
        "stabilization": 9,
        "partial antagonist": 1,
        "suppressor": 3,
        "weak inhibitor": 2,
        "binding": 10,
        "degradation": 1,
        "antisense oligonucleotide": 5,
        "incorporation into and destabilization": 1,
        "neutralizer": 3,
        "cleavage": 9,
        "oxidizer": 3,
        "inactivator": 6,
        "nucleotide exchange blocker": 1,
        "inhibition of synthesis": 1,
        "translocation inhibitor": 2,
        "gene replacement": 1,
        "regulator": 10,
        "chelator": 2,
        "component of": 4
    },
    "number_of_edges_by_predicate_curie_prefixes": {
        "DRUGBANK": 2913688
    },
    "number_of_predicates_by_predicate_curie_prefixes": {
        "DRUGBANK": 54
    },
    "number_of_edges_by_source": {
        "identifiers_org_registry:drugbank": 2913688
    },
    "types_of_pairs_of_curies_for_xrefs": {},
    "types_of_pairs_of_curies_for_equivs": {},
    "number_of_nodes_by_source_and_category": {
        "identifiers_org_registry:drugbank": {}
    }
}

Another thing to note: based on
    "number_of_nodes_by_source_and_category": {
        "identifiers_org_registry:drugbank": {}
    }

I do not think count_number_of_nodes_by_source_and_category is working.

This is completed as of KG2.8.4pre, so I am going to close out this issue.

Great work!  Thank you.