Build Marker Array after all markers have loaded?

I was wondering if there is an easy way to retrieve all map markers.
I was hoping there was an output method that would push the marker to an array during the *ngFor loop
I did see someone who used ViewChild to retrieve all map markers AfterViewInit
is this the best way ATM?

What do you want to do with these markers?
I'm closing this as this is no bug or feature request. feel free to comment below

When the user pans the map I need to return all markers within the current bounds of the map.

You can use the boundsChange output AgmMap, save the new bounds in your state, iterate all markers and use the contains method of LatLngBounds to find out which markers are in the new bounds. You dont need the marker instances directly. The coords are enough

That's my problem, from where do I get an array of markers? Currently i am creating an array of markers as the data comes in.

@Defmetalhead there's no problem :) when you create the markers, you know the coords an all markers on the map (thats basically the array of coords from your data). With that it's all you need

@SebastianM thank you very much for the help.

No problem
Defmetalhead<EMAIL_ADDRESS>schrieb am Di. 12. Juni 2018 um
20:44:

@SebastianM https://github.com/SebastianM thank you very much for the
help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SebastianM/angular-google-maps/issues/1425#issuecomment-396693732,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQzRF5wiQ2lJo73wvnpzyyQo8VutDpsks5t8AwngaJpZM4UjPlG
.


Remove proxy.config.http.cache.allow_empty_doc

Removes proxy.config.http.cache.allow_empty_doc
This feature was originally deprecated in TS-3979 (6a36346df8e)

Hmm, The default value is 1 . Forget it.

[approve ci autest]


functionality merged from pull request #520 not present in 0.10.4

I need the functionality introduced in https://github.com/Kotlin/anko/pull/520, but it doesn't seem to be present in 0.10.4. Ideas?
For the time being, I've written the extension in manually :(

It will be released in 0.10.5


How to calculate the x,y-tile-coordinates from lat,long if given images in EPSG25832-projection method?

Hello there,
I have a question regarding the creation of the WMTS server requests.
From this german governmental-website I can get the address for their WMTS server: https://www.wmts.nrw.de/geobasis/wmts_nw_dop. I can successfully integrate it into josm as an image layer (wmts:https://www.wmts.nrw.de/geobasis/wmts_nw_dop) and it gets displayed correctly.
I can watch the server request made by josm in the terminal, which is something like:2019-09-26 18:54:31.651 INFO: GET https://www.wmts.nrw.de/geobasis/wmts_nw_dop/tiles/nw_dop/EPSG_25832_16/16/17680/35107 -> HTTP_1 200 (13.3 kB)
You can view this tile image: https://www.wmts.nrw.de/geobasis/wmts_nw_dop/tiles/nw_dop/EPSG_25832_16/16/17680/35107
In the rviz-satellite-plugin I entered the string for the request: https://www.wmts.nrw.de/geobasis/wmts_nw_dop/tiles/nw_dop/EPSG_25832_16/{z}/{y}/{x}
If I let rviz_satellite figure out the y and x, I'm getting trash in rviz:

I think this is because the images/tiles are in EPSG25832-projection method, but rviz-satellite thinks in Mercator-projection. And I need the images to be in EPSG25832, because of other data which gets displayed.
If you look at the WMTSCapabilities.xml of the map-server you can see there are images available up to zoom level 16 and other info: https://www.wmts.nrw.de/geobasis/wmts_nw_dop/tiles/nw_dop/EPSG_25832_16/1.0.0/WMTSCapabilities.xml
I had a look at the methods, which rviz-satellite seems to use to calculate the x and y, which is something like this:
// in Coordinates.h:
int const n = 1 << zoom;
double x = n * ((coord.lon + 180) / 360.0);
double y = n * (1 - (std::log(std::tan(lat_rad) + 1 / std::cos(lat_rad)) / M_PI)) / 2;

But I think I need to do something like this, because of the EPSG25832/UTM projection:
https://en.wikipedia.org/wiki/Transverse_Mercator_projection
I already had a look at https://josm.openstreetmap.de/doc/org/openstreetmap/gui/jmapviewer/Tile.htm to see how openstreetmap does it, but I didn't find anything.
So all in all: How to calculate the x,y-tile-coordinates from lat,long if given images in EPSG25832-projection method (which josm/osm does succesfully)?

Hey Moritz,
could it be that the tiles are just twisted wrong? Would the tiles be correct if you rotate them 90° to the right and then mirror it along the x-axis (so that the old top of the tile is the new bottom)? I have a line in the code that mirrors some axis: https://github.com/gareth-cross/rviz_satellite/blob/40bc9c5caf4fee1079333d37792e029da082700c/src/aerialmap_display.cpp#L416-L419
You could try to adjust that line if you didn't already.

I'm closing this issue for now.


Delegate called twice: dayView(dayView: DayView, didUpdate event: EventDescriptor)

When I drag an event after long-pressing it (without releasing!), after dropping it I'm seeing the delegate function always called twice.
This is caused by the snap animation in commitEditing. What happens on mouse release:

handlePanGesture is called and since the state is ended, it calls commitEditing
the snap animation starts
immediately, before the animation ends, timelineDidLongPress is called
since editedEventView is still there (animation did not finish and completionHandler was not called to set it to nil), the animation starts again
the completion handler is called for both animations

Are you having any issues because of this?

Kind of, when the event is updated the app is reacting to changes. Right now there's no visible issue but I will add some more functionalities around this.
A simple solution would be to use a weak reference to editedEventView in TimelinePagerView:370 (for the completionHandler in the commitEditing function, and add a guard to unwrap it. The second time the completion handler is called is should be nil since after the first call to dayView(dayView:didUpdate) I'm calling endEventEditing().

Would you be able to implement this change?

Long press into drag and drop (without releasing the touch in between).
I'll add this to my todo list, should be a simple fix but need to test it thoroughly.

Feel free to propose the PR at this stage, so that I could test it as well. I also recommend testing with https://github.com/richardtop/CalendarApp since it's an end-to-end implementation of the calendar instead of the one embedded into this application.


Update IDL-Parser

Merge https://github.com/eProsima/Micro-XRCE-DDS-Gen/pull/74 into the ArduPilot fork in advance of upstream.
Required for:

https://github.com/ArduPilot/ardupilot/pull/26095

Dependencies

[x] Merge https://github.com/ArduPilot/OMG-IDL-Parser/pull/1 and update IDL-Parser submodule

I've updated the submodule hash, URL and specified the branch in 4ae7d0ab77d7976f4cfb8aa1c9e55ab82b4b8368.

I've updated the submodule hash, URL and specified the branch in 4ae7d0a.

LGTM @Ryanf55 - I've rebuilt microxrceddsgen using this branch and verified that https://github.com/ArduPilot/ardupilot/pull/26095 is building, so should be good to merge.
Is there anything in CI that requires updating before this can be merged?


[Enhancement]: TPE3 frame in ID3v2.3 should be used for narrator.

The TPE3 frame in ID3v2.3 is intended for “Conductor/Performer Refinement,” but it’s often used in audiobooks or spoken word media to denote the narrator. Many media players and library management tools recognize this frame and display it appropriately.
•	Example: TPE3 = “Narrated by John Doe”
When trying to do the following with a file which uses ID3v2.3 the following fails silently:
tone tag --meta-narrator
The fix is just to map it to TPE3 for ID3v2.3.
Additionally, whenever tone fails to update a file a return value should be given so that a script can handle the failure. POSIX systems and windows allow to you use the return values between 1-254 for whatever you want ( BSD has sysexits.h, but it is not a hard rule at all ).  Being able to programmatically errors would be very useful, at the moment you have to update and then open the file again to see if the changes you requested succeeded. I am happy to write this up in more detail if you want it as its own feature request.

@BrianAker
Thank you for taking the time. Accoring to MP3Tag Mapping TPE3 is used for Conductor, not Narrator.
Narrator has no mapping for id3v2. Since I'm following these pretty accurately with minor exceptions, I'd recommend to use --meta-conductor="Authors Name" to fix this for your use case. If you don't want to specify the narrator twice, you can also use --meta-conductor="Authors Name" --meta-equate="conductor,narrator" to overcome the problem.
However, since there is a possibility to use an extended field in id3v2 (TXXX:NARRATOR), I would implement this in addition to the conductor mapping to have at least any narrator mapping for id3v2.
Targeted for next release.

Waiting for response here:
https://github.com/Zeugma440/atldotnet/issues/289

Thanks!

Should be fixed in 0.2.0.


train_dataset and eval_dataset in run_openai_gpt.py

Running examples/run_openai_gpt.py w/ the default arguments throws an error:
$ python run_openai_gpt.py --output_dir tmp --do_eval
Traceback (most recent call last):
  File "run_openai_gpt.py", line 259, in <module>
    main()
  File "run_openai_gpt.py", line 153, in main
    train_dataset = load_rocstories_dataset(args.train_dataset)
  File "run_openai_gpt.py", line 49, in load_rocstories_dataset
    with open(dataset_path, encoding='utf_8') as f:
FileNotFoundError: [Errno 2] No such file or directory: ''

Looking at the code, it looks like train_dataset and eval_dataset need to be explicitly set.  Any suggestions on what they should be set to?
Thanks!
cc @thomwolf

Hi Ben,
Please read the relevant example section in the readme.

@thomwolf I see that the data is downloaded and cached in case of not providing the train_dataset and eval_dataset parameters: https://github.com/huggingface/pytorch-pretrained-BERT/blob/master/examples/run_openai_gpt.py#L152-L153, but it fails here: https://github.com/huggingface/pytorch-pretrained-BERT/blob/master/examples/run_openai_gpt.py#L162. So either we make the parameters required or do some additional steps which requires untar of the downloaded data and pointing towards that data. Let me know what you think.


[Issue]: Abnormal Placement of Scroll-to-Top Button Near Chatbot Open Button[Other]

What would you like to share?
Issue:
The scroll-to-top button on the page is positioned unusually close to the chatbot open button, causing a potential usability concern.
Details:
Upon scrolling down the page, the scroll-to-top button becomes visible. However, its proximity to the chatbot open button is causing confusion for users. This close placement may lead to accidental clicks or hinder the ease of accessing the chatbot functionality.
Expected Behavior:
The scroll-to-top button should be positioned in a location that prevents overlap or confusion with other interactive elements, such as the chatbot open button. Users should be able to easily identify and interact with both buttons without interference.
Steps to Reproduce:
Scroll down the page to reveal the scroll-to-top button.
Observe its placement in relation to the chatbot open button
Additional information
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

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

Please label it fir GSSOC'24 and /assign me the issue, I would like to work on it
@Rakesh9100

Proceed @SahilThakur02


Publish to Maven Central

Is this possible to build release 0.5 and publish to Maven Central ?

This is really straightforward using Maven build, but I have no clue how to achieve this using Gradle.

I've built a release and it was published in github packages.
Also I've created https://issues.sonatype.org/browse/OSSRH-73239 to publish it to maven central.

It is published now to Maven central

Excellent, thanks !


(chore) Latest Ergo dev

Signed-off-by: Jerome Simeon<EMAIL_ADDRESS>

Coverage remained the same at 93.663% when pulling 2f53555b1c664f339ade86a60fb9a7786f5ee21c on jeromesimeon:js-chore-up-ergo into 9bc4a5638e325bc34e48e6d80ae17e0951ffd31f on accordproject:cicero-0.11.


[Feature] DoReMi

[x] DoReMi implementation
[ ] Validate the implementation with wikicorpus dataset

.

@obrienwrite ?

#bordingschool
On Sat, Jan 27, 2024, 6:38 PM XλRI-U5 @.***> wrote:

@obrienwrite https://github.com/obrienwrite ?
—
Reply to this email directly, view it on GitHub
https://github.com/huggingface/nanotron/pull/34#issuecomment-1913421531,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAN35N4SFYJHFUSPGVPKRDYQW233AVCNFSM6AAAAABCDZ5V42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGQZDCNJTGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


[TypingIndicator] Indicator shown on "About Me"

Before you submit an issue please restart your discord. If the issue is still there feel free to write a bug report.
Describe the bug
Indicator shown on "About Me"
To Reproduce
Steps to reproduce the behavior:

Go to 'About Me'
See error

Expected behavior
No Indicator shown on "About Me"
Screenshots

Information (please complete the following information):

OS: windows
Plugin Version: 0.5.4
Discord version:  Stable
Compact Mode enabled? no]

Additional context
none

that is not from TypingIndicator, but some plugin from @Strencher (InvisibleTyping or something like that)

whoops my bad, was half asleep when I made this


Add "Remember Me" Checkbox and Eye button for password visibility for Improved User Experience

Describe the feature
Description:
I would like to request the addition of a "Remember Me" checkbox to the login form. This feature will enhance the user experience by allowing users to stay logged in across sessions without having to re-enter their credentials every time they visit the site.
Benefits:
Improved User Convenience: Users won't need to log in repeatedly, making it easier for frequent users.
Time-Saving: Reduces the time spent on the login process.
Enhanced User Retention: Users are more likely to return to a website where they don’t have to log in repeatedly.
Considerations:
Implement secure storage of user session data.
Provide clear information to users about the "Remember Me" functionality.
Ensure options for users to manage their sessions and manually log out.
Please assign this issue to me under gssoc
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hello @srivastav2006 !
You can start working on this issue.
Happy Coding ✨


Add example cell type metadata file

I added this line to the external instructions, but did not add the example cell type project metadata file -  https://github.com/AlexsLemonade/scpca-nf/blob/619e638d10eef6de342639bf28f232d56ac3f5de/external-instructions.md?plain=1#L400-L401 .... Woops! We'll need that example file!
That said, I am actually wondering whether we should simplify the metadata files to just three columns: project id, singler file, and cellassign file. The singler_ref_name and cellassign_ref_name columns aren't actually used anywhere. We use the file names of course -
https://github.com/AlexsLemonade/scpca-nf/blob/619e638d10eef6de342639bf28f232d56ac3f5de/modules/classify-celltypes.nf#L125-L135
But a grep of the repo shows that columns singler_ref_name and cellassign_ref_name are never used (plus that info is completely, and systematically!, encapsulated in the file name).
I would be in favor of removing name fields from the metadata file to make it a bit simpler to prepare. @allyhawkins @jashapiro, any thoughts on this?

I think I would prefer to keep the ref_name. I think it's nice to have a more human readable version of the reference name. Also if we were to ever combine the tables (reference metadata and project cell type metadata), we would have that column to use.

I think I would prefer to keep the ref_name.  I think it's nice to have a more human readable version of the reference name.

I am convinced!

Ah! When the rellink didn't work I assumed the file wasn't there. The file was there... just a bad link!
Going to pop this fix into #573.
https://github.com/AlexsLemonade/scpca-nf/blob/619e638d10eef6de342639bf28f232d56ac3f5de/examples/example_project_celltype_metadata.tsv


xUnit.net Test Support 2.1.7 reports incorrect runtimes for xunit 2.0.0

Hi,
I have xUnit.net Test Support 2.1.7 installed in VS 2013 and when I run my tests in resharper a 55s test run is reported as 5.37.250.
I have full parallel mode on -- no xunit. appsettings defined.
Am I missing something?

JetBrains ReSharper 8.2 C# Edition
Build <IP_ADDRESS>0 on 2014-03-20T07:53:08
Plugins: 3
#1. Untitled v<IP_ADDRESS> by Anonymous
#2. “NuGet support for ReSharper” v<IP_ADDRESS>071 by JetBrains
#3. “xUnit.net unit test provider” v<IP_ADDRESS>611 by “Matt Ellis”
Visual Studio 12.0.30723.0.
Copyright © 2003–2015 JetBrains s.r.o. All rights reserved.

Hmm, that tells me a different version

Will try {un,re}install

Is this still an issue? Please reopen if so.


Display listening addresses (local addresses) in Node window's Information tab

It would be useful to display listening addresses (local addresses) in the "Information" tab of Node window (localaddresses part of getnetworkinfo output).

This issue should be closed as it's duplicated with #564 which work is in progress already. Thx.


This New Feature is Scary! What if we use service account and some one other than PBI Admin swaps it with personal auth?

[Enter feedback here]

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

ID: 92e0c038-1195-d758-ccf4-903b689139ca
Version Independent ID: 181904c0-1ec5-0a1d-4cbf-a5a639bbdfeb
Content: Add or remove a gateway data source - Power BI
Content Source: powerbi-docs/connect-data/service-gateway-data-sources.md
Service: powerbi
Sub-service: powerbi-gateways
GitHub Login: @arthiriyer
Microsoft Alias: arthii

The New Feature of moving Gateway Datasources from Admin Portal to general will lead to lots of confusion and problems , https://docs.microsoft.com/en-us/power-bi/connect-data/service-gateway-data-sources - updated 05/06.
Why was this removed from Admin Portal?

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

Thanks for your comment, @karthikk24.
This looks like product feedback or a product question, rather than documentation feedback. You can submit product feedback or feature ideas by going to Power BI Ideas.
You can also engage with the Power BI engineering team by being active in the Power BI Community.


⚠ Bofrost.at has degraded performance

In 0fd4e7b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1405 ms

Resolved: Bofrost.at performance has improved in e298779.


Changed the footer and the alignment of the text

I Have changed the Footer of the website and some misalignment of the text
1.
BEFORE

AFTER

BEFORE

*AFTER

BEFORE

AFTER

@Its-Aman-Yadav Hey PA ,
I have Done changes , kindly look into it


Update lsp-types and rayon

Brings in https://github.com/gluon-lang/lsp-types/pull/129 for https://github.com/rust-analyzer/rust-analyzer/issues/2651#issuecomment-568554427

bors r+

Thanks @udoprog!


Fix typo in Bool.swift

Fix typo in documentation where the "Prints " comment had a parenthesis at the end, probably from coping and pasting out of the code example.

@swift-ci Please test

@swift-ci Please smoke test and merge

@auswahlaxiom That only tends to work when you have privileges 😛
Seriously, thanks for the patch.
@swift-ci please smoke test and merge


Test automation

Write tests for 100% coverage and automate testing using Travis.

 Test-automatisering

Would very much like to gain insights into how this is done. How about writing or referring a blog post when successful?


Client broken after latest update

After the latest territorial update as of the 27th of may 2024 the client is broken. When trying to play multiplayer you get a: Game was updated please reload.

The client has now been updated (see commit https://github.com/fxclient/FXclient/commit/3db6d61262a7578c5045c8eb38fa91261c6f6c47)


Chen, L., & Norman, J. 1965. Foochow-English Glossary is inaccessible from ERIC - seeking alternate download site.

類型 / Type

[ ] 糾錯 => 請先搜索一下之前有無別人提出過。
[+] 新資源

內容

Chen, L., & Norman, J. 1965. Foochow-English Glossary is inaccessible from ERIC - seeking alternate download site.

Hi @jensopetersen. Sorry I could not attend to you until now. Do you mind sending me a message at my email address ztl8702 at msn dot com and I will see if I can find a local copy for you.

Check out my email. Closing as resolved.


Initializing the Flask API for playground

Restructured code for the Backend server

@everythingfunctional @milancurcic @arjenmarkus please review this PR, I've made some changes to the backend code which differ in implementation from the first one


Added manually defined prisms to make HLS run

My HLS wasn't running properly in projects which depend upon marconi-core. The error was about Marconi.Core.Type not exporting prisms for IndexerError, which it did. Manually defining the prisms makes the problem go away.

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[x] Commit sequence broadly makes sense and have useful messages
[ ] Important changes are reflected in changelog.d of the affected packages
[ ] Relevant tickets are mentioned in commit messages

PR

[ ] (For external contributions) Corresponding issue exists and is linked in the description
[x] Targeting main unless this is a cherry-pick backport
[x] Self-reviewed the diff
[x] Useful pull request description
[ ] If relevant, reference the ADR in the PR and reference the PR in the ADR
[x] Reviewer requested

cabal clean solved the problem


[stable/ark] s3ForcePathStyle must be a string

Is this a BUG REPORT or FEATURE REQUEST?:
This is a bug report.
Version of Helm and Kubernetes:

Helm 2.9.1
Kubernetes v1.10.6-gke.2

Which chart:
stable/ark
What happened:
I tried to configure the the backupStorageProvider using a values.yaml. As I'm using Minio as my S3 backend, I needed to set s3ForcePathStyle to true and so I did:
configuration:
  backupStorageProvider:
    name: aws
    bucket: ark
    config:
      region: eu-west-1
      s3Url: http://minio.minio.svc.cluster.local:9000
      s3ForcePathStyle: true

The configmap.yaml in turn generated the following YAML for the Ark config:
apiVersion: ark.heptio.com/v1
kind: Config
metadata:
  name: default
backupStorageProvider:
  name: aws
  bucket: ark
  config:
    region: eu-west-1
    s3Url: http://minio.minio.svc.cluster.local:9000
    s3ForcePathStyle: true

What you expected to happen:
I expected this to work, i.e. Ark starting and not prepending the bucket name into the minio URL, but instead appending it as a path element.
Instead, Ark errored out with
time="2018-08-27T19:15:02Z" level=error msg="Error retrieving configuration" error="v1.Config: BackupStorageProvider: v1.ObjectStorageProviderConfig: CloudProviderConfig: Config: ReadString: expects \" or n, but found t, error found in #10 byte of ...|thStyle\":true,\"s3Url|..., bigger context ...|config\":{\"region\":\"eu-west-1\",\"s3ForcePathStyle\":true,\"s3Url\":\"http://minio.minio.svc.cluster.local:|..." logSource="pkg/cmd/server/server.go:348"

I suspect this to be similar/related to kubernetes/kubernetes#57509, as in the value of labels must be strings. This is confirmed by Ark doing a manual cast to bool.
The error can be fixed by specifying "true" in my values.yaml and changing the configmap.yaml to do
  {{- with .s3ForcePathStyle }}
    s3ForcePathStyle: {{ . | quote }}
  {{- end }}

How to reproduce it (as minimally and precisely as possible):
Deploy Ark as documented and then try to set a raw bool value, then look at the log of the Ark pod.

I had the same problem and fix with the same solution.


accelerate_with_tensorrt binding dimension problem?

I have tried to use
stream = accelerate_with_tensorrt(
    stream, "engines", max_batch_size=2,
)

, and this is the result

this seems to be the main error message:
[E] 3: [executionContext.cpp::nvinfer1::rt::ExecutionContext::validateInputBindings::2045] Error Code 3: API Usage Error (Parameter check failed at: runtime/api/executionContext.cpp::nvinfer1::rt::ExecutionContext::validateInputBindings::2045, condition: profileMaxDims.d[i] >= dimensions.d[i]. Supplied binding dimension [2,4,67,120] for bindings[0] exceed min ~ max range at index 2, maximum dimension in profile is 64, minimum dimension in profile is 64, but supplied dimension is 67.     )

I found the problem, it was because I was trying to use a different dimension of image in Streamdiffusion than 512x512

I have solved this problem:
The engine needs to be rebuilt (delete 'engines' folder) , with these arguments passed into accelerate_with_tensorrt :
resolutiondict = {'engine_build_options' : {'opt_image_height': WIDTH , 'opt_image_width': HEIGHT}}
stream = accelerate_with_tensorrt(
    stream, "engines", max_batch_size=BATCH_SIZE,engine_build_options=resolutiondict
)


inveniogc: convert all sql left joins to intbitset operations

After fixing some extremely slow sql queries (#428, thanks, @kaplun) , and backporting this inveniogc to my systems (trivially), inveniogc still hangs my test server.   After digging the system with mytop, it is evident that left join kills MySQL very badly, and inveniogc cannot complete. Please convert all them to intbitset operations.
The consequences are important; database tables keep growing and occupy a lot (a lot!) of disk space, like 3.1 GB only for keeping (obsolete) session information.

Do you have this patch in your installation?
Commit 7fc855b312bfd1c5df6d5a5972ddf01e010da63c
Author: Tibor Simko<EMAIL_ADDRESS>Date:   Wed Jul 4 14:48:56 2012 +0200
installation: new index on session.session_expiry

* Adds index on session.session_expiry.  Helps in speeding up
  the garbage collection process based on session expiry times.

It seems so:
 $ echo 'show create table session;' | dbexec | sed 's/\\n/\n/g'
 Table   Create Table
 session CREATE TABLE `session` (
  `session_key` varchar(32) NOT NULL DEFAULT '',
  `session_expiry` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `session_object` longblob,
  `uid` int(15) unsigned NOT NULL DEFAULT '0',
  UNIQUE KEY `session_key` (`session_key`),
  KEY `uid` (`uid`),
  KEY `session_expiry` (`session_expiry`)
 ) ENGINE=MyISAM DEFAULT CHARSET=utf8

It is in the same machine where I have run inveniogc.

Are there any news on this end? We just ran into it as well even though it just took longer for us to hit the wall. (Thought this was already fixed.)

In Invenio-1.2.x, thanks to 06d7f5f0e61c7926503be462355f0995ea456441 the default storage engine for sessions becomes http://redis.io/, thus allowing for auto-expiration and no longer this sort of troubles. If you are still using Invenio-1.1.x you can try backporting the above patch...

For the time beeing I'll then have to try the backport. Thanks :)

If you use native sessions, then you can clean them all fast at a quiet server time (say over the weekend) like this:
sudo apache2ctl stop
echo "TRUNCATE session" | /opt/invenio/bin/dbexec
sudo apache2ctl start

This will force logout upon everybody, hence the importance of doing it when the server is mostly idle.  The old sessions will be killed rapidly in this way and the rest of inveniogc should then proceed faster.
P.S. If you want to be more permissive and keep recent sessions, you could do something like DELETE FROM session WHERE session_expiry < '2015-08-01 00:00:00'.

I think the query that is actually blocking the system is:
result = run_sql("""SELECT u.id
    FROM user AS u LEFT JOIN session AS s
    ON u.id = s.uid
    WHERE s.uid IS NULL AND u.email = ''""")
    write_message(result, verbose=9)

Which indeed is a left join and might explain why it is so slow. BTW you might want to set:
CFG_WEBSEARCH_PREV_NEXT_HIT_FOR_GUESTS = 0
CFG_WEBSESSION_DIFFERENTIATE_BETWEEN_GUESTS = 0

in your invenio-local.conf file. This should allow not allocating unnecessary session and guest users.

And note that when the session table is empty, this query would be ultra fast...  so no blocker anymore.

Closing this issue, as there are workarounds, as per the legacy code base freeze.


elmPackages.nodejs: 14.19.1 -> 14.19.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for elmPackages.nodejs is: "Event-driven I/O framework for the V8 JavaScript engine"
meta.homepage for elmPackages.nodejs is: "https://nodejs.org"
meta.changelog for elmPackages.nodejs is: "https://github.com/nodejs/node/releases/tag/v14.19.2"
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 14.19.2 with grep in /nix/store/7gbbivcqxxlml744fhkl7y06khqsc28d-nodejs-14.19.2
found 14.19.2 in filename of file in /nix/store/7gbbivcqxxlml744fhkl7y06khqsc28d-nodejs-14.19.2

Rebuild report (if merged into master) (click to expand)

402 total rebuild path(s)

215 package rebuild(s)

215 x86_64-linux rebuild(s)
187 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
antennas
antora
balanceofsatoshis
bat-extras.prettybat
bitwarden-cli
botamusique
castnow
cinnamon.xreader
code-server
commitlint
concurrently
create-cycle-app
cryptpad
deltachat-desktop
discourse
discourseAllPlugins
element-desktop
element-desktop-wayland
elmPackages.create-elm-app
elmPackages.elm
elmPackages.elm-analyse
elmPackages.elm-coverage
elmPackages.elm-doc-preview
elmPackages.elm-git-install
elmPackages.elm-language-server
elmPackages.elm-live
elmPackages.elm-optimize-level-2
elmPackages.elm-review
elmPackages.elm-test
elmPackages.elm-upgrade
elmPackages.elm-verify-examples
elmPackages.elm-xref
elmPackages.nodejs
emojione
epgstation
ethercalc
fast-cli
flexoptix-app
flood
gnomeExtensions.pop-shell
google-clasp
grafana-image-renderer
gtop
hueadm
hyperspace-cli
image_optim
imapnotify
imgbrd-grabber
iosevka
isso

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7gbbivcqxxlml744fhkl7y06khqsc28d-nodejs-14.19.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A elmPackages.nodejs https://github.com/r-ryantm/nixpkgs/archive/6fc17d4b0e199c63c8db10134fd51160ce46ddef.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7gbbivcqxxlml744fhkl7y06khqsc28d-nodejs-14.19.2
ls -la /nix/store/7gbbivcqxxlml744fhkl7y06khqsc28d-nodejs-14.19.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @cillianderoiste @gilligan @cko @marsam for testing.

addressed by https://github.com/NixOS/nixpkgs/pull/171593


Automated PR: Cookstyle Changes

Hey!
I ran Cookstyle 7.32.2 against this repo and here are the results.
This repo was selected due to the topics of chef-cookbook
Changes
Issues found and resolved with attributes/default.rb

120:58 refactor: Chef/RedundantCode/MultiplePlatformChecks - You can pass multiple values to the platform? and platform_family? helpers instead of calling the helpers multiple times. (https://docs.chef.io/workstation/cookstyle/chef_redundantcode_multipleplatformchecks)

Released as: 2.11.3


looks like 'instrument' is broken

In my package.js it's listed I'm using
"grunt-istanbul": "^0.4.0"
When I run grunt coverage I get
Running "instrument" task
Fatal error: Cannot read property 'instrument' of undefined
Looks like instrument task is not generating instrument code. When I change grunt-istanbul to 0.3.0 everything works as expected.

Hi,
Got the same error. I debuged and saw that its coming from the following line:
https://github.com/taichi/grunt-istanbul/blob/master/tasks/helpers.js#L98
Then I update it with the following code:
          if (f && f.instrument) {

But this time I am getting the following error:
Fatal error: An error occurred in an async call.
cause stack is ...
  Error: ENOENT, stat 'instrumented/server.js'
async call history is ...
 [ { function: 'readStat',
    location: '/home/bor/sunucu/mdm-server/node_modules/grunt-istanbul/tasks/helpers.js:88:43',
    mapping: { name: 'server.js', stat: [Object] } } ]

I got the same. Rollback to 0.3.0

For me, setting lazy: false for instrument task makes it run successfully. So the problem is probably in the lazy handling...


Performance stability

I cannot find anything about the performance stability. We are thinking about using Windows VMs in Azure to performance test our application. At the moment we use a Docker Web Application in Azure but we see regression and progression in the performance without changes to our application. So I'm interested in if the Windows VMs have the same performance over time (with a machine that stays the same) but this is not in this guide.

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

ID: ff5b5898-88d9-7aec-1516-e157e92564a7
Version Independent ID: f9807092-172c-d8d0-fc7d-17204faea51b
Content: Windows Virtual Machines Overview
Content Source: articles/virtual-machines/windows/overview.md
Service: virtual-machines-windows
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the feedback! We are currently investigating and will update you shortly.

@YvonneArnoldus As you are question is being addressed on MSDN, I will close this issue here. Thanks.


Deployment described in the tutorial -> https://developers.sap.com/tutorials/cap-service-deploy.html -> failed

Deployment described in the tutorial -> https://developers.sap.com/tutorials/cap-service-deploy.html -> failed
Execution all the steps for the tutorial but the following steps:
cds build --production -> executed correctly
cf push -f gen/db -> is NOT executed correctly with the following error log:
ERROR Unable to build dependencies: exit status 1
Failed to compile droplet: Failed to run all supply scripts: exit status 14
Exit status 223
Cell cfeb172d-f2c7-42d1-a157-58148983025c stopping instance 9ec3e79a-4c01-40af-858e-d0cb44df76a9
Cell cfeb172d-f2c7-42d1-a157-58148983025c destroying container for instance 9ec3e79a-4c01-40af-858e-d0cb44df76a9
Cell cfeb172d-f2c7-42d1-a157-58148983025c successfully destroyed container for instance 9ec3e79a-4c01-40af-858e-d0cb44df76a9
Error staging application: App staging failed in the buildpack compile phase
FAILED
What I see as an outcome on the terminal:
Othcome_cf_push.txt
(unfortunately was not able to find a log file mentioned there)

Hi @oesipova,
At the time you tested it there were problems that have now been fixed. Please try again and create a new ticket if the problem persists.
Best regards,
Iwona


ItemSeperator not rendered correctly with useCallback

Current behavior
When loading in items in an infinitive scroll list (with onEndReached), the top most ItemSeperator of the item that is loaded in is not rendered. When scrolling away from the not rendered ItemSeperator and back again, the ItemSeperator is loaded in again correctly.
The problem is with renderItem being memoized in a useCallback. Is that even necessary since the cells get reused anyway? If not, the fix is quite simple, but perhaps it should be mentioned in the docs.

Expected behavior
ItemSeperator should be rendered initially.

To Reproduce
const DATA = [
  {
    title: 'First Item',
  },
  {
    title: 'Second Item',
  },
  {
    title: 'First Item',
  },
  {
    title: 'Second Item',
  },
  {
    title: 'First Item',
  },
  {
    title: 'Second Item',
  },
  {
    title: 'First Item',
  },
  {
    title: 'Second Item',
  },
  {
    title: 'First Item',
  },
  {
    title: 'Second Item',
  },
];

const TestList: React.FC = () => {
  const [data, setdata] = useState(DATA);

  const onEndReached = () => {
    setdata(prev => [...prev, ...DATA]);
  };

  const renderItem = useCallback(() => {
    return <Text>test</Text>;
  }, []);
  return (
    <FlashList
      data={data}
      renderItem={renderItem}
      estimatedItemSize={20}
      ItemSeparatorComponent={() => (
        <View style={{height: 1, width: '100%', backgroundColor: 'red'}} />
      )}
      onEndReachedThreshold={0.1}
      onEndReached={onEndReached}
    />
  );
};

Platform:

[ ] iOS not tested
[x ] Android

Environment
1.0.4

You can actually skip memoizing renderItem with separators. The list's update logic doesn't depend on reference of this callback. I'll fix it anyway in the future.

My solution is to skip memorization as well as I already thought it is unnecessary anyway. I guess a short note in the docs would be enough. Good to know that the update logic is not affected though.

@alexco2 Well there is an impact but it's limited to pagination. When you add more data to the list as of now it skips updating items that are already there. This is the reason why separator is not updating. I need to find a way to update the last item.

@naqvitalha thank you for the explanation :)

I made a video of the issue in case anyone would find it helpful
https://user-images.githubusercontent.com/57633368/206434112-52da140b-a4f8-4550-a31e-d92efc3d717c.MOV

Are there any updates on this problem?

is there any update?


Fix performance test file

Fixed require statement inside performance test.

Thanks for finding this! What situation were you in when this issue came up?

Thanks for finding this! What situation were you in when this issue came up?

@kaylareopelle Found while running performance tests. This was actually an error I made in an earlier PR.


File PySSC.py generated from SAM have the variable "double" not declared.

There's three functions that uses the variable "double":

	def data_set_array_from_csv(self, p_data, name, fn) :
		f = open(fn, 'rb');
		data = [];
		for line in f :
			data.extend([n for n in map(double, line.split(b','))])
		f.close();
		return self.data_set_array(p_data, name, data);

	def data_set_matrix_from_csv(self, p_data, name, fn) :
		f = open(fn, 'rb');
		data = [];
		for line in f :
			lst = ([n for n in map(double, line.split(b','))])
			data.append(lst);
		f.close();
		return self.data_set_matrix(p_data, name, data);

	def data_get_matrix(self,p_data,name):
		nrows = c_int()
		ncols = c_int()
		self.pdll.ssc_data_get_matrix.restype = POINTER(c_number)
		parr = self.pdll.ssc_data_get_matrix( c_void_p(p_data), c_char_p(name), byref(nrows), byref(ncols) )
		idx = 0
		mat = []
		for r in range(nrows.value):
			row = []
			for c in range(ncols.value):
				row.append( double(parr[idx]) )
				idx = idx + 1
			mat.append(row)
		return mat

After changing double to float in the functions mentioned, occurred anothers errors, it seems problem reading integer instead of a float number inside the pysam lib:

Fixed with PR #590

@leo-smi Can you check what value is being read in for system_use_lifetime_output ? Sending the files you're working with would be helpful also.
Assuming you've used the Python 3 code generator, it should say
ssc.data_set_number( data, b'system_use_lifetime_output', 0 )

Merged into patch PR 590 and merged into develop PR 596

There it is the files, just run "SMI.py", I think the path will work automatically...
sim_python.zip

@leo-smi Thanks for sending. I was able to identify the error. In PySSC.py, please change line 4 to c_number = c_double.


GitHub Data Collection for DeepAQAtik

Related Issue #412
Created a python script for collecting GitHub issues at regular intervals:

Added functions to fetch github issues of a repository tagged with certain labels.
The repository is queried at regular intervals.

@llxia @LongyuZhang Please check the updated PR.
Updates:

Fetch all new open github issues for the specified repos
Store the issue relationships in MongoDB
Store the issue content on filesystem

I believe that the following things are left (not addressed in the latest addition):

since parameter is not stored on DB (Do we need to store since for each repo separately or a single value for all repos?)
Test issue contents are not saved

Please let me know what you think of this. Thank you so much!

since parameter is not stored on DB (Do we need to store since for each repo separately or a single value for all repos?)

It would be better to have various since values for different repos, so the program will not re-collect all repos in the case when it stops after collecting a few repos. Some other repos you can include are adoptium/infrastructure and eclipse-openj9/openj9 to test.

Test issue contents are not saved

Do you mean test output contents? For this PR, we can collect only the git issue contents first as the original data, and then fetch Jenkins output based on these data, which can be done later. Thanks.

Hi @LongyuZhang @llxia
I have added a since parameter for each repo and these are stored on the database (and picked from it). Please let me know your thoughts on this. I believe this concludes the github data collection part for DeepAQAtik, looking forward to your thoughts and suggestions on the same.
Thank you
Avishree

I have made some changes based on @llxia's comments on the name of the database. However as the PR has already been merged, that commit is not being shown here. Please let me know if I should be submitting another PR for the latest changes.
@LongyuZhang @llxia
Thank you

yes, just submit another PR to update. Thanks @avishreekh


add gradio support

to add gradio support

Thanks for the PR! I'll be taking a look at this soon.

@csris ok, I have updated the code. Thank you!

Thanks! Will look.


Xarray versioning to switch to CalVer

Xarray is planning to switch to Calendar versioning (calver). This issue serves as a general announcement.
The idea has come up in multiple developer meetings (#4001) and is part of a larger effort to increase our release cadence (#5927). Today's developer meeting included unanimous consent for the change. Other projects in Xarray's ecosystem have also made this change recently (e.g. https://github.com/dask/community/issues/100). While it is likely we will make this change in the next release or two, users and developers should feel free to voice objections here.
The proposed calver implementation follows the same schema as the Dask project, that is; YYYY.MM.X (4 digit year, two digit month, one digit micro zero-indexed version. For example, the code block below provides comparison of the current and future version tags:
In [1]: import xarray as xr

# current
In [2]: xr.__version__
Out[2]: '0.19.1'

# proposed
In [2]: xr.__version__
Out[2]: '2022.01.0'

cc @pydata/xarray

Note that PEP 440 normalizes integers in version strings, so leading zeros are ignored and the version as it appears in PyPI would be 2022.1.0, as that displays the normalized version string.
On my own packages which I use calver for I have opted to not have leading zeros such that the "canonical" version matches the "normalized" version to avoid any confusion that may cause.

Do others have thoughts here? I would support stripping the leading zeros from the MM part of the version string in favor of consistency here.

I'm in favor of a non-zero-padded version for the benefit of having canonical/normalized versions that also match git tags/history

Note that PEP 440 normalizes integers in version strings, so leading zeros are ignored and the version as it appears in PyPI would be 2022.1.0, as that displays the normalized version string.
On my own packages which I use calver for I have opted to not have leading zeros such that the "canonical" version matches the "normalized" version to avoid any confusion that may cause.

No opinion either way here but 2022.01.0 is an easier string to sort.
@jrbourbeau is this something dask has thought about?

note that PEP440 itself is not really consistent: it mentions both normal and zero-padded CalVer.
Also, in the issue in which dask discussed this, one of the people involved with the PyPA stated that the difference between omitting or keeping the zero-padding is purely aesthetic (both can be parsed using packaging.version.Version / packaging.version.parse). I assume that means we're free to choose? The YYYY.MM.X scheme seems to be fairly common now, though.

setup.py sdist bdist_wheel creates files in dist/ that have the leading zeros removed.
I did git tag v2022.01.0 and then built the wheel/sdist and got: xarray-2022.1.0-py3-none-any.whl and xarray-2022.1.0.tar.gz and xarray.__version__ gave 2022.1.0
I do understand the appeal of leading zeros, I started off using them myself, but pypi/setuptools/etc will bring in inconsistencies that you will either need to fight against or give into the consistent way, which is sans leading zero (that is the path I chose)

@jrbourbeau is this something dask has thought about?

Thanks for the ping @Illviljan. Zero-padding dates did come up in the Dask calver discussion starting here https://github.com/dask/community/issues/100#issuecomment-704445214. In a nutshell, there was a slight preference towards using zero-padding (i.e. 2022.01.0 instead of 2022.1.0) because the calendar nature of the version is more explicit and string sorting and full-fledged package sorting (like one would do with packaging.version) give the same result.
As pointed out https://github.com/dask/community/issues/100#issuecomment-704468187 either convention is valid from a Python packaging perspective. FWIW I'm not aware of any issues that have come up from Dask using a zero-padded version number. The main thing that comes to mind is when checking out git tags for a specific release (e.g. git checkout 2021.04.0 and git checkout 2021.4.0 are not equivalent). That said, to my knowledge, this hasn't been an issue in practice.

After thinking on this one a bit, I'm back to thinking we should zero-pad the months. I don't think there is a clear right choice here, with both options offering pros/cons. Thanks @ksunden in particular for sharing your perspective). I suggest we try this in 2022.02.0. See #6214 for more details.

Using semver can be handy to signal breaking changes. Any thoughts on how xarray will handle breaking changes with calver? Any release can break, or during select periods, after a timeout, etc.?

Breaking changes will continue to be very rare, and whenever possible will be preceeded by deprecation or future warnings for multiple months.


Allow actor message dependencies within a phase

Actual behavior
Leapp framework tells me that it can't solve dependency between actors even though it should be able to solve it.
Original state:

State in which Leapp should be able to solve dependency order:

To Reproduce
Steps to reproduce the behavior

install leapp and leapp-repository
consume RpmTransactionTasks in PesEventsScanner
run leapp upgrade --debug
See error:

2019-04-05 09:18:00.445 DEBUG    PID: 636 leapp.repository.system_upgrade_el7toel8: Loading workflow modules
leapp.exceptions.CyclingDependenciesError: Could not solve dependency order for 'pes_events_scanner'

Expected behavior
There's no cycle within a phase. So I would expect Leapp to solve the order this way:
Facts Phase:

TransactionWorkarounds and RpmTransactionConfigTasksCollector (the order does not matter)
PesEventsScanner

Checks Phase:

SCTPChecks
FilterRpmTransactionTasks

Isn’t the problem that the peseventscanner produces the same message it consumes? In this case this cannot work and is the reason for the error.

Yes, it produces message of the same model as it consumes. I don't think that should be disallowed. The dependency order is possible to "calculate". In this case there's no cyclic dependency.

No this is not a bug and a won't fix and indeed this is not as easy as you suggest. There was a deliberate design decision not to allow this, because the algorithm cannot know when the message should be scheduled.
Consider these 4 actors:

You end up with something like this:

Now if I would do as you said, how would I now prioritize either Actor1 or Actor2?
If you want to solve this, let the PES data produce a different message and let the consumer of that message consume that as well.


Update github username

Pull request showed: Co-authored-by: mattfsourcecode<EMAIL_ADDRESS>Corrected in: https://github.com/mattfsourcecode/fastify-swc-typescript-server/pull/5


A Possible solution for Issue #62)

Allows the use of botAuth behind a gateway. (Issue #62)
The addition of the servicePath property allows the botauth get and post routes to be different from the callback and auth urls (which use basePath). Thus, I can run a bot as service and use a gateway to map the callbacks to the bots  servicePaths.

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


Prevents git checkout during teardown

This Pull Request modifies git_checkout to prevent unnecessary checkouts during teardown by testing if config.tilt_subcommand == "up"

❤

thanks!


allow user to display a custom component when table has no children

I would love a way to display a custom component when there's no data to show in the table rather than just text.
Hoping this pull request can at least start the discussion, or, if it looks good, provide the solution. Open to any input.

@glittershark any thoughts on this?

rebased


Can u make it work at safari and mac ?

I wanted to know if you can fix it to ios and safari ? I would be very happy about it !

I will likely do some work for OSX if the new standalone client supports OSX, as I am planning on getting a Macbook myself. But currently I'm not planning on supporting the flash client on OSX.

Im pretty sure it wont support osx but thanks anyway :s

If the new client supports macOS I will definitely contribute on making it work there :-)

Is there a new client being released?! Did they mentioned anything about Mac this time? #outoftheloop

Quoting Mirade:

it is only planned to support Windows (Windows XP SP3 or newer). You can try running Tibia 11 on other OS, of course, but the client does not officially support them at the moment. Please understand that we cannot make any promises at the moment as to whether or not other OS will be officially supported some time in the future.

It seems they would be even dropping linux support, so...


Adds 🪝 useWindowSize - Resolves #59

Added a direction option to limit the resize direction.
I didn't add a double-click event handler to deliberate with you more about it and add it in the subsequent iterations.

@saeedalipoor – After playing with this in an actual plugin UI, I think it’s better to allow resizing across the entire right and bottom edges (as opposed to just the bottom-right corner). I made a PR to your branch that includes some substantial changes! See https://github.com/saeedalipoor/create-figma-plugin/pull/1.


Add bsf clean command

It often gets untidy while developing for a new feature or testing out things locally to manually delete the autogenerated bsf files/dirs such as: bsf/, bsf-result/, bsf.hcl, bsf.lock.
We should have a bsf clean that should clean all these autogenerated files.
Note: This command should only work under the BSF_DEBUG_MODE.
We already have a cleanup logic under cmd/init so we can reuse that.

Hi @rakshitgondwal, how have you been?
I would like to work on this issue, can you please guide me a little bit?

Hi @Suraj-kumar00, we need to create a new bsf clean command that will clean up all the autogenerated files. Only thing is that this command should be under the BSF_DEBUG_MODE. We have a a couple other commands under that such as bsf precheck, similarly clean should be implemented.
You can reuse this logic as well: https://github.com/buildsafedev/bsf/blob/a2c73d1a07c03290df94270b30c687bac5491b41/cmd/init/init.go#L150

Hey is this issue still up?
If yes I would like to work on it!

Hey @hanshal101, you can go ahead and make a PR


Introduce Padding-Free Plugin to FMS-Acceleration

Description
This PR introduces a new padding-free plugin to FMS-Acceleration

Make sure go through this checklist https://github.com/foundation-model-stack/fms-acceleration/tree/main/plugins/framework#adding-new-plugins


ENH:MAINT:special:Rewrite amos F77 code

Reference issue
Part of #18566
Relevant issues will be added
What does this implement/fix?
The rewrite of the AMOS library.
Additional information
Not as big as cdflib, should be tested meticulously for the edge cases.
Total gotos left: ~40 (out of too many)

[ ] Add missing documentation from Fortran sources
[ ] Add tests
[ ] Get some benchmarks

I managed to make some progress in a quite unexpected direction.
Because the code is so unorthodox, doing real arithmetic with complex ops, jumping from one for loop into the middle of another and feeling no shame and so on, Cythonization didn't cut it so I switched to C as another goto infested lang. Anyways, I quickly realized why I stopped coding in these langs because it's been roughly 30 years and still nobody managed to agree on what a complex number type should be. So probably at some point #include <complex.h> will be a headache for somewhere some system.
It's been really challenging and I unrolled as many GOTOs as I could. At least we have airy/airye function in working state. I tested a bit and results agree with fortran code. We are at about 25% and I'll clean the cython code when I'm done 😢
If you have objections to style or strategy please tell me as I hardly know what I am doing.

I am pretty confident about airy and biry code in C as I tested in many regions and compared with Fortran code and WolframAlpha.
I'll test the the remaining Bessel ones and start dealing with the wrappers.

Tested on Win10 and Linux Mint. Only one test is barely failing rel err 1.09e-13 instead of 1.0e-13. Let's see what happens in the CI.
Happy new year all 🎉 🎆

Status update;

Py3.12 job does not understand the .real and .imag attributes of the NumPy Complex doubles (See the failing job). Is this anything related to NumPy 2.0?

I tried to find the source of the mismatch in the test

but whatever is happening is happening in the wrappers probably at the lowest registers between C and Fortran. Unfortunately                          this ~1e-58 number is then multiplied with a very large number and the result is not possible to hit that same relative accuracy. Hence I made the test relative tolerance to be 2e-13 instead of 1e-13.

If the first one is resolved and second item is acceptable, then this is ready to be reviewed.

Py3.12 job does not understand the .real and .imag attributes of the NumPy Complex doubles (See the failing job). Is this anything related to NumPy 2.0?

I'm just guessing but is https://github.com/numpy/numpy/pull/24085 related?

Ah yes, probably. Let me use the NPY_CREAL and NPY_CIMAG just to be on the safe side.

Impressive effort @ilayn!
This isn't quite reviewable line by line, so I guess we should look at test coverage, build warnings, etc. It maybe also be useful to run clang-format over the new code now.

It maybe also be useful to run clang-format over the new code now.

https://github.com/ilayn/scipy/pull/6 does this with the .clang-format file in special/special, however it seems like there is no option to stop it from adding whitespace around binary operators... probably not a good idea.

This isn't quite reviewable line by line, so I guess we should look at test coverage, build warnings, etc.

Indeed, that's one of the tricky things to do with such rewrite but our test coverage is pretty ruthless and discovered quite many bugs. Hence while it is possible that some if branch is missed, still the majority of the functionality is there.

It maybe also be useful to run clang-format over the new code now.

Judging by what @lucascolley showed it is a bit too intrusive in the binary operator spacing but I liked a few changes it made. I'll do that semi-manually. It turns out that PEP8 has really conditioned me to write narrow code and C folks are taking none of it :)

Reorganized the commits and cleaned up the history, removed the cython parts. So if no additional comments are coming in, I am ready for clicking this in.

This isn't quite reviewable line by line, so I guess we should look at test coverage, build warnings, etc. It maybe also be useful to run clang-format over the new code now.

I checked the test coverage with gcov and it is around 70% but some larger branches aren't hit. however, I ran out of time to work out if those are branches we don't ever use (some functions switch between cephes and amos) or missing test coverage

I'll finish reviewing and hopefully merge the cdflib PR by the end of the week and hope to have this one done next week.

Anyways, I quickly realized why I stopped coding in these langs because it's been roughly 30 years and still nobody managed to agree on what a complex number type should be.

We have MSVC to thank for that. 😑

Ha, it's not less feat to go through this so thanks @steppi
Funny that you picked binu because I think I wrote that one at least 3 times. And the part you stumbled upon is exactly where I didn't get right apparently, the conditions are so weirdly tangled that I made a true false diagram for it. I'm surprised that it is still broken.
So we are looking at this flow
https://github.com/scipy/scipy/blob/87f8428b227dd8962d8658482bd8a150a31292a4/scipy/special/amos/zbinu.f#L34-L47
So first jumps, then falls through then jumps further and if not then falls through. The reason I have those extra conditions are these if else sillyness. Fortunately we don't have another occurence of this so I am pretty confident about the remaining parts since I tested quite a number of them.

OK apparently I fixed this in my local work but did not pass it over to the PR

This binu is such an annoying piece of code.

Yeah, it's the trickiest one in my opinion. If that had been perfect, I think I would have just gave everything else a spot check and merged. I'm feeling better about things again after your explanations. I should be able to find time to finish reviewing within the coming week.

No worries, that's really good catch. Let's hope I didn't make more labor intensive mistakes.

@steppi apologies for getting back to this again but I think you found a bug in the fortran code itself.  The reason I am convinced that this is a Fortran bug is because my code also goes into the same branches and not into UOIK as you mentioned it should go.
_amos.c:890: BESI CALLING BINU
_amos.c:1334: BINU AZ < RL check 21.2132034355964265 <? 21.7842717294324260
_amos.c:1334: BINU dfnu < RL check 99.2000000000000028 <? 1.0
_amos.c:1334: BINU az+az < dfnu*dfnu check 42.4264068711928530 <?<PHONE_NUMBER>000000057
_amos.c:1373: BINU CALLING UOIK
_amos.c:1373: BINU with z 15.0000000000000000 15.0000000000000000
_amos.c:3665: UNIK sr = 1.000261219004686 0.02285839549794466
_amos.c:3709: UNIK: cwrk[15]  0.1003696526628773 -0.001146695339458976
_amos.c:1373: BINU RETURNED FROM UOIK NW = 0
_amos.c:1373: BINU cy[0] 0 0
_amos.c:1394: BINU CALLING BUNI
_amos.c:2156: BUNI CALLING UNI1
_amos.c:3665: UNIK sr = 1.000261219004686 0.02285839549794466
_amos.c:3709: UNIK: cwrk[15]  0.1003696526628773 -0.001146695339458976
_amos.c:3665: UNIK sr = 1.000261219004686 0.02285839549794466
_amos.c:3709: UNIK: cwrk[15]  0.1003696526628773 -0.001146695339458976
_amos.c:3726 UNIK: K AFTER LOOP 9
_amos.c:3749: UNIK AFTER INIT=0 case INIT = 9
_amos.c:3709: UNIK: sum  0.9991673468996691 0.0001136141289952106
_amos.c:3709: UNIK: phi  0.04004169811642799 -0.000457465253649459
_amos.c:3709: UNIK: cwrk[15]  0.1003696526628773 -0.001146695339458976
_amos.c:3709: UNIK: con[0]  0.3989422804014327
_amos.c:3342: UNI1 csr[1] 1
_amos.c:3342: UNI1 s2 -2.064590884330946e-55 -1.112777373104005e-55
_amos.c:3342: UNI1 y[0] -2.064590884330946e-55 -1.112777373104005e-55
_amos.c:2156: BUNI RETURNED FROM UNI1 NW = 0
_amos.c:1394: BUNI y[0] -2.064590884330946e-55 -1.112777373104005e-55
_amos.c:1394: BINU RETURNED FROM BUNI NW = 0, NLAST 0
_amos.c:1394: BINU cy[0] -2.064590884330946e-55 -1.112777373104005e-55
_amos.c:892: BESI RETURNED FROM BINU WITH NZ = 0
0 0 -2.0645908843309458552e-55 -1.1127773731040049375e-55i

I guess copied the Fortran code a bit too good.

Hmm I am more confused now because then my fixed version is diverged from the Fortran code itself.

OK the current SciPy which uses Fortran also does not pass 1e-15 rtol level too
C:\Users\ilhan> ipython
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 8.19.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import scipy

In [2]: scipy.__version__
Out[2]: '1.12.0rc1'

In [3]: import scipy.special as ssp

In [4]: ssp.iv(99.2, 15+15j)
Out[4]: (-2.0645908843310788e-55-1.1127773731040388e-55j)

In [11]: assert_allclose(ssp.iv(99.2, 15+15j), mpmath,rtol=1-15)

[..snip..]

AssertionError:
Not equal to tolerance rtol=-14, atol=0

Mismatched elements: 1 / 1 (100%)
Max absolute difference: 1.28411573e-68
Max relative difference: 5.47508521e-14
 x: array(-2.064591e-55-1.112777e-55j)
 y: array(-2.064591e-55-1.112777e-55j)

So I think I'll just take a break for today and tomorrow I'll do another round.

I am not sure where I confused myself but I used my working code and swapped places following your lead and indeed tests pass. And moreover, I reverted the modified test since that also passes too. Let's see how it goes. Overall, I think this indeed was a very good catch. And the test suite is quite comprehensive it seems.

Thanks @steppi much appreciated.

@steppi do you think we should update the docstrings as currently they state along the lines of: Wrapper for a C translation of the AMOS [1]_ routines `zairy` and `zbiry`. which I guess now is not 100% correct. I suggested in ilayn#7 to change to Wrapper for a C translation of the AMOS [1]_ routines `zairy` and `zbiry`. however, perhaps this is too much detail for the end user. Do you have a view here?

Sorry. I didn't find any sign of https://github.com/ilayn/scipy/pull/7 mentioned in the comment chain above. I would have waited to merge this if I'd known you had this concern.
Honestly, I thought the docstrings were fine as is. I was thinking of the AMOS routines in the abstract, not tied to any particular implementation. Now that you mention it though, letting users know these are translations might save people from some confusion around our functions giving slightly different results from AMOS in some cases.
For the future. I expect these functions to diverge further and further from AMOS over time as we make improvements. If so,  I think the docstrings should be updated again to say our implementations are based on those of Amos, citing D.E. Amos' Computation of Bessel functions of a complex argument, which discusses the math behind the implementations.

Sorry. I didn't find any sign of https://github.com/ilayn/scipy/pull/7 mentioned in the comment chain above. I would have waited to merge this if I'd known you had this concern.

No problem at all. There is just too much to look at with these Fortran stuff so we are always forgetting stuff.
But indeed I would also using the abstract terminology of citing Amos' paper. The interested readers would discover where we got the implementations at the top of the license comments anyways.


[WFCORE-5767] Add the Elytron OIDC Client related dependencies to Core

https://issues.redhat.com/browse/WFCORE-5767
Moving the Elytron OIDC Client related dependencies from WildFly to Core. The modules that actually make use of these dependencies will remain in WildFly.

@fjuma Do you need to add it to https://github.com/wildfly/wildfly-core/blob/main/core-feature-pack/common/src/main/resources/license/core-feature-pack-common-licenses.xml ?

@boris-unckel Good question. Since these dependencies aren't actually being used by anything in Core and only get used by the Elytron OIDC layer in WildFly, I think we can leave these in the https://github.com/wildfly/wildfly/blob/main/elytron-oidc-client/galleon-common/src/main/resources/license/elytron-oidc-feature-pack-licenses.xml file.

+1 this should not impact the modules provisioned by the core feature pack so should not need listing in the licenses.


Looking for latest Caliptra verification status

I'm looking for validation status (testplan, functional coverage results, code coverage results, ...). In the doc folder there is an xls with some information (https://github.com/chipsalliance/caliptra-rtl/blob/main/docs/Caliptra_TestPlan.xlsx) but doesn't seem to be complete and the last update I see is from August 2023.
Is there any other place where verification status is tracked?

Web dashboard is being built to have the latest/greatest reported into it. In terms of test plan items, you are correct that most of them should have been moved to 100% and they will be reflected into dashboard along with FPV report.


Fix issue #12 'Schema  values are not camelized when 'convert_casing'…

… is enabled'

Thanks, I've fixed in 8dc493eae424c072a1817905c2635e8934fd4071

Excellent, the fix works as expected!


feat: encoding > allowReserved support

Closes #497
WIP: needs code style refinement
Checklist

[x] Tests have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

support for encoding.allowReserved flag
encoding.style is only applied for application/application/x-www-form-urlencoded
encoding.style is applied to all uri parts (before it was only applied to first one)
i'm using qs package to decode UrlEncoded payload. It was used internally by fastify's form-body plugin

Does this PR introduce a breaking change?
No

I've dropped some comments, but the direction is overall ok!
Can you add a changelog line?

Changelog line added 👍

Looks great feature wise!


Add mu kafka consumer producer

What this does?
https://github.com/47deg/marlow/issues/515
https://github.com/47deg/marlow/issues/542
This PR is about creating APIs for building Kafka consumer and producer with minimum effort with fs2-kafka and models defined and generated using sbt-mu-srcgen.
The kafka poc has been updated to use the APIs
https://github.com/naree/mu-kafka-sandbox
An example in the IT test and good entry point to the API use.
https://github.com/higherkindness/mu-scala/blob/add-mu-kafka-consumer-producer/modules/kafka/src/test/scala/higherkindness/mu/kafka/it/example/MuKafkaServiceSpec.scala#L88-L95
Two types of developers were considered as the target users

FP developers with cats-effect experience only
FP developers with experience in both cats-effect and fs2-stream

The idea is not to shield developers from accessing fs2-stream but provide simple APIs to start from.
Additionally, I made the assumption that the developers would be familiar with
concurrent programming and understand how to select the correct ContextShift.
This PR is one of features for mu-kafka.
Still to come in later PRs.

Documentation
Message key generation and propagation strategy
IT Testing with Docker
Multiple messages types per topic
At least once message processing paradigm
Transaction
Config
Metrics

Checklist

[x] Reviewed the diff to look for typos, println and format errors.
[ ] Updated the docs accordingly.

Can this be merged? Thanks!

Can this be merged? Thanks!

Yes, I will rebase first and merge it.

I'll merge this now. We'll need some follow-up PRs to iterate on the design, resolve some of the TODOs in the code and things pointed out in commments above, and add documentation for the feature.
I think the next thing to try would be making use of fs2-kafka's Serializer and Deserializer type classes so we don't have to define our own.

Thanks @naree!


Concerto.instanceOf is misleading or buggy: It can be successful on non valid data

Bug Report 🐛
The new Concerto.instanceOf call works on non-valid data so can easily be confusing and give the impression that an object is an instance of a class even when it isn't.
[This could be considered "as designed" but I think the call and doc are misleading and will lead to confusion and users believing they have performed validation when they haven't.]
Example:
const ModelLoader = require('./lib/modelloader');
const Concerto = require('./lib/concerto');

const cto = `
namespace test
concept C {
  o String foo
}
concept C1 extends C {
}
concept C2 extends C1 {
}
concept D {
  o String bar
}
concept D1 extends D {
}
concept D2 extends D1 {
}
`;
const json1 = { // valid
  $class: 'test.C2',
  foo: 'bliblablu'
};
const json2 = { // valid
  $class: 'test.D2',
  bar: 'bliblablu'
};
const json3 = { // not valid
  $class: 'test.C2',
  bar: 'bliblablu'
};

const tests = [
  { obj: json1, $class: 'test.C' },
  { obj: json1, $class: 'test.D' },
  { obj: json2, $class: 'test.C' },
  { obj: json2, $class: 'test.D' },
  { obj: json3, $class: 'test.C' },
  { obj: json3, $class: 'test.D' },
];

async function run() {
  const mm = await ModelLoader.loadModelManagerFromModelFiles([cto],['test.cto']);
  const concerto = new Concerto(mm);

  tests.forEach(({ obj, $class }) => {
    console.log(`JSON ${JSON.stringify(obj)} INSTANCE OF ${$class} =  ${concerto.instanceOf(obj,$class)}`);
  });
}
// Launch!
run()

Run:
zsh-5.8$ node test.js
JSON {"$class":"test.C2","foo":"bliblablu"} INSTANCE OF test.C =  true
JSON {"$class":"test.C2","foo":"bliblablu"} INSTANCE OF test.D =  false
JSON {"$class":"test.D2","bar":"bliblablu"} INSTANCE OF test.C =  false
JSON {"$class":"test.D2","bar":"bliblablu"} INSTANCE OF test.D =  true
JSON {"$class":"test.C2","bar":"bliblablu"} INSTANCE OF test.C =  true // returns true even if the object isn't an instance of `test.C`
JSON {"$class":"test.C2","bar":"bliblablu"} INSTANCE OF test.D =  false

Expected Behavior
Instance of should fail for non valid data.
Current Behavior
Instance of sometimes returns true for non valid data.
Possible Solution
I think the current call is fundamentally not between an object and a class, but simply looking into the type hierarchy. I would either:

change the call so it fails (throws an error?) on non-valid data
change the call so it is between two classes rather than between an object and a class

This is very odd, the implementation appears to ignore all properties (except for $class) entirely!
https://github.com/accordproject/concerto/blob/master/packages/concerto-core/lib/concerto.js#L217


Housekeep app needs to support arbitrary run lengths

resolution_fixed   |    by<EMAIL_ADDRESS>
In current suites app/housekeep/rose-app.conf has
prune-remote-logs-at=-P3M
prune{share/cycle}=-P3M
prune{work}=-P3M

However the rose housekeep app isn’t very smart and looks for files with a date stamp exactly 3 months earlier to the current run date. If a run is using 6 month chunks nothing matches and so nothing gets cleaned up.

Issue migrated from trac:326 at 2024-01-31 18:30:08 +1100

<EMAIL_ADDRESS>changed status from assigned to closed

<EMAIL_ADDRESS>set owner to mrd599

<EMAIL_ADDRESS>commented

The intention was to keep the work and log directories from the last 3 jobs in case of some unexpected problem. Note that this is separate to the ability to restart because the necessary files for that are in the archive directory.
This can be done for any resubmission period by repeating the offset argument in a rose date calculation
   # Target date for cleanup is 3 runs previous
   TMPDATE=$(rose date -c --offset=-[RESUB] --offset=-[RESUB] --offset=-[RESUB])
   OFFSET=$(rose date -c ref $TMPDATE)

Suite change https://code.metoffice.gov.uk/trac/roses-u/changeset/46949
Note that if the resubmission period is increased during the run there will be a few directories missed in the cleanup.

<EMAIL_ADDRESS>set resolution to fixed


No styles when running demo

I followed the instructions to run the demo but got this.

It looks like styles are partly missing.
The environment is:
  › node -v
v4.2.2
  › npm -v
3.7.3

I think #2 is related:
Clone repo, install, npm run watch spits out the following error:
[1] /Users/laeg/Projects/React/redux-auth-demo/node_modules/redux-auth/bootstrap-theme.js:2
[1] ype:"submit",className:"pull-right",icon:this.props.icon,disabled:n,className:
[1]                                                                     ^^^^^^^^^
[1] SyntaxError: Duplicate data property in object literal not allowed in strict mode
[1]     at exports.runInThisContext (vm.js:73:16)
[1]     at Module._compile (module.js:443:25)
[1]     at Module._extensions..js (module.js:478:10)
[1]     at Object.require.extensions.(anonymous function) [as .js] (/Users/laeg/Projects/React/redux-auth-demo/node_modules/babel-register/lib/node.js:138:7)
[1]     at Module.load (module.js:355:32)
[1]     at Module._load (module.js:310:12)
[1]     at Function.module._load (/Users/laeg/Projects/React/redux-auth-demo/node_modules/piping/lib/launcher.js:32:16)
[1]     at Module.require (module.js:365:17)
[1]     at require (module.js:384:17)
[1]     at Object. (/Users/laeg/Projects/React/redux-auth-demo/src/views/partials/RequestTestButton.js:17:23)
commenting the following (line 1229, 1230)
 icon: this.props.icon,```

Allows for the site to be displayed and renders the styling

I think this has something to do with the webpack bundle being 15 MB (huge). The first time I ran npm run watch, it took 19 seconds to compile it all. It took maybe 10 seconds for the styles to load in the browser, even though the HTML showed up right away. When I tried a different time (after a reboot, so everything had been reset in between), I let it sit again for 30 seconds and no styles loaded, but after pressing refresh, they showed up right away. I'm sure you tried refresh, but I'm just mentioning my experience.

I think it's just slow. The demo is loading 3 bootstrap and material ui after all. I wouldn't recommend doing that in production.
I did just update the webpack build system - it seems faster to me now.


Comparison issues

@gerargz,
I just noticed that these two comparisons are always false.
https://github.com/microbit-foundation/DAPLink/blob/44a2522d35038eb51f04b363a6bb4ff437e46467/source/daplink/interface/swd_host.c#L1070
https://github.com/microbit-foundation/DAPLink/blob/44a2522d35038eb51f04b363a6bb4ff437e46467/source/daplink/interface/swd_host.c#L1081
Is this how it should be or is it a typo?

Thanks for the report @MarianSavchuk, and great catch!
This has been addressed upstream in PR  https://github.com/ARMmbed/DAPLink/pull/853, which has been already merged there 🎉


Unable to install Brain.js on PopOS

What is wrong?
When I run npm i brain.js in the folder of my project, I get the following error:
npm ERR! code 1
npm ERR! path /home/user/Documents/chessy/node_modules/gl
npm ERR! command failed
npm ERR! command sh -c prebuild-install || node-gyp rebuild
npm ERR! prebuild-install warn install No prebuilt binaries found (target=20.5.0 runtime=node arch=x64 libc= platform=linux)
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using<EMAIL_ADDRESS>npm ERR! gyp info using<EMAIL_ADDRESS>| linux | x64
npm ERR! gyp info find Python using Python version 3.11.4 found at<EMAIL_ADDRESS>npm ERR! gyp info spawn<EMAIL_ADDRESS>npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/home/user/Documents/chessy/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/user/Documents/chessy/node_modules/gl/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/user/Documents/chessy/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/user/.cache/node-gyp/20.5.0/include/node/common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/user/.cache/node-gyp/20.5.0',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/home/user/Documents/chessy/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/user/.cache/node-gyp/20.5.0/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/home/user/Documents/chessy/node_modules/gl',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! /bin/sh: 1: python: not found
npm ERR! gyp: Call to 'python commit_id.py check ..' returned exit status 127 while in angle/src/angle.gyp. while loading dependencies of binding.gyp while trying to load binding.gyp
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/home/user/Documents/chessy/node_modules/node-gyp/lib/configure.js:325:16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:294:12)
npm ERR! gyp ERR! System Linux 6.2.6-76060206-generic
npm ERR! gyp ERR! command "/home/linuxbrew/.linuxbrew/Cellar/node/20.5.0/bin/node" "/home/user/Documents/chessy/node_modules/.bin/node-gyp" "rebuild"
npm ERR! gyp ERR! cwd /home/user/Documents/chessy/node_modules/gl
npm ERR! gyp ERR! node -v v20.5.0
npm ERR! gyp ERR! node-gyp -v v9.4.0
npm ERR! gyp ERR! not ok

Whenever I try to sort of omit this error and do yarn add brain.js, I run the app and get the message Error: Cannot find module 'gpu.js'.
I use Brain.js in Next.js.
Version information
Nodejs:
v20.5.0
Browser:
Google Chrome
Brain.js:
Unable to install, but mean to install the latest version possible.
How important is this (1-5)?
It, I think, is 5, because I cannot install the library from the very get-go.
Other Comments
I never have this error on Windows.

I also have noticed that many people have created similar issues, but none of them has got a clear solution that works.

Your error message - Error: Cannot find module 'gpu.js' - means you have to also do npm install gpu.js

Your error message - Error: Cannot find module 'gpu.js' - means you have to also do npm install gpu.js

I wish it was as simple as that.
It shows
error /home/user/Documents/chessy/node_modules/gl: Command failed.
Exit code: 1
Command: prebuild-install || node-gyp rebuild
Arguments:
Directory: /home/user/Documents/chessy/node_modules/gl
Output:
prebuild-install warn install No prebuilt binaries found (target=20.5.0 runtime=node arch=x64 libc= platform=linux)
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp info find Python using Python version 3.10.6 found at "/usr/bin/python3"
gyp info spawn /usr/bin/python3
gyp info spawn args [
gyp info spawn args   '/home/user/Documents/chessy/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/user/Documents/chessy/node_modules/gl/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/user/Documents/chessy/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/user/.cache/node-gyp/20.5.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/user/.cache/node-gyp/20.5.0',
gyp info spawn args   '-Dnode_gyp_dir=/home/user/Documents/chessy/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/user/.cache/node-gyp/20.5.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/user/Documents/chessy/node_modules/gl',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
/bin/sh: 1: python: not found
gyp: Call to 'python commit_id.py check ..' returned exit status 127 while in angle/src/angle.gyp. while loading dependencies of binding.gyp while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/home/user/Documents/chessy/node_modules/node-gyp/lib/configure.js:325:16)
gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:294:12)
gyp ERR! System Linux 6.2.6-76060206-generic
gyp ERR! command "/home/linuxbrew/.linuxbrew/Cellar/node/20.5.0/bin/node" "/home/user/Documents/chessy/node_modules/gl/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /home/user/Documents/chessy/node_modules/gl
gyp ERR! node -v v20.5.0
gyp ERR! node-gyp -v v9.4.0
gyp ERR! not ok

Looks like gyp finds python (as python3) but your shell doesn't.
For kicks, can you share the output of running simply python --versionandpython3 --version` in bash respectively?
I think a simple solution, if only the latter works, would be to alias python3 to python by adding this line to your .bashrc profile:
alias python=python3

You can simply run the above in your shell and try installing again, but the change will be for the duration of that session. If you want to persist it by adding it to your bash profile, you'll also need to run source ~/.bashrc after the addition, or just create a new session.
Let us know how it goes!

You might need python-is-python3

@cclauss  's recommendation is also a good one and essentially does the same thing I described, as a system-wide package
sudo apt-get install python-is-python3
Some light reading on what this package does and possible drawbacks/considerations.

I remember I have already tried this package, but still got the error.
Also, the alias command is the same as installing this package, isn't it?

Yes.

Yes.

I have set an alias, but still get the following error:
error /home/user/Documents/chessy/node_modules/gl: Command failed.
Exit code: 1
Command: prebuild-install || node-gyp rebuild
Arguments:
Directory: /home/user/Documents/chessy/node_modules/gl
Output:
prebuild-install warn install No prebuilt binaries found (target=20.5.0 runtime=node arch=x64 libc= platform=linux)
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp info find Python using Python version 3.11.4 found at<EMAIL_ADDRESS>gyp info spawn<EMAIL_ADDRESS>gyp info spawn args [
gyp info spawn args   '/home/user/Documents/chessy/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/user/Documents/chessy/node_modules/gl/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/user/Documents/chessy/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/user/.cache/node-gyp/20.5.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/user/.cache/node-gyp/20.5.0',
gyp info spawn args   '-Dnode_gyp_dir=/home/user/Documents/chessy/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/user/.cache/node-gyp/20.5.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/user/Documents/chessy/node_modules/gl',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
/bin/sh: 1: python: not found
gyp: Call to 'python commit_id.py check ..' returned exit status 127 while in angle/src/angle.gyp. while loading dependencies of binding.gyp while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/home/user/Documents/chessy/node_modules/node-gyp/lib/configure.js:325:16)
gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:294:12)
gyp ERR! System Linux 6.2.6-76060206-generic
gyp ERR! command "/home/linuxbrew/.linuxbrew/Cellar/node/20.5.0/bin/node" "/home/user/Documents/chessy/node_modules/gl/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /home/user/Documents/chessy/node_modules/gl
gyp ERR! node -v v20.5.0
gyp ERR! node-gyp -v v9.4.0
gyp ERR! not ok

@cclauss also, thanks for the pull request. I'll check it out.
https://github.com/BrainJS/brain.js/pull/905

My "Yes" was for Python venv.

Yes.

I have set an alias, but still get the following error when doing yarn add gpu.js:
error /home/user/Documents/chessy/node_modules/gl: Command failed.
Exit code: 1
Command: prebuild-install || node-gyp rebuild
Arguments:
Directory: /home/user/Documents/chessy/node_modules/gl
Output:
prebuild-install warn install No prebuilt binaries found (target=20.5.0 runtime=node arch=x64 libc= platform=linux)
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp info find Python using Python version 3.11.4 found at<EMAIL_ADDRESS>gyp info spawn<EMAIL_ADDRESS>gyp info spawn args [
gyp info spawn args   '/home/user/Documents/chessy/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/user/Documents/chessy/node_modules/gl/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/user/Documents/chessy/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/user/.cache/node-gyp/20.5.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/user/.cache/node-gyp/20.5.0',
gyp info spawn args   '-Dnode_gyp_dir=/home/user/Documents/chessy/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/user/.cache/node-gyp/20.5.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/user/Documents/chessy/node_modules/gl',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
/bin/sh: 1: python: not found
gyp: Call to 'python commit_id.py check ..' returned exit status 127 while in angle/src/angle.gyp. while loading dependencies of binding.gyp while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/home/user/Documents/chessy/node_modules/node-gyp/lib/configure.js:325:16)
gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:294:12)
gyp ERR! System Linux 6.2.6-76060206-generic
gyp ERR! command "/home/linuxbrew/.linuxbrew/Cellar/node/20.5.0/bin/node" "/home/user/Documents/chessy/node_modules/gl/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /home/user/Documents/chessy/node_modules/gl
gyp ERR! node -v v20.5.0
gyp ERR! node-gyp -v v9.4.0
gyp ERR! not ok

Both python3 --version and python --version log the same version, but I still have the error. I actually at the moment am a bit confused.

What are the contents of binding.gyp?

What are the results of python3 --version ? What are the contents of binding.gyp?
Oh... stackgl/headless-gl#221

The "Oh..." has made me oddly satisfied. So I need to install Python 2, don't I?

Sorry for sending several messages instead of sending one with everything, but I think I have found a temporary solution which is to install an older version of gpu.js, to wit, 1.10.4.

Also see: https://github.com/mikolalysenko/angle/pull/5

Also see: https://github.com/mikolalysenko/angle/pull/5

Hope what you have done will contribute to this problem getting finally fixed.

Had the same stack-trace during install on Mac OS Ventura, fixed with:
cd /opt/homebrew/bin
sudo ln -sf python3 python

@romaleev bad idea but hey, it is your machine.

https://snarky.ca/how-virtual-environments-work from a longtime Python code dev.

I had the same problem on Manjaro linux, somehow changing the node version from 20 to 16 fixed the problem. I tested it with multiple versions of node on both my ubuntu VM and my Manjaro machine and found out that brain.js couldnt install on anything newer than node 16.

npm ERR! path /home/user/Documents/chessy/node_modules/gl

Does npm install gl work?


fix: GL E-Ink DeparturesNoData

Asana task: DevOps Checkbox does not work for all screens
Correct the slot name used in props. After this, all screens are working when devops checkboxes are checked.
**Correction: Looks like gl_eink_single was not set up to handle these checkboxes. Since we still have single live single screen GL E-Ink screens, I added the logic so it doesn't show predictions when it shouldn't.

[ ] Tests added?

I'm really not sure why I didn't take that approach initially. I must have thought the slot names being the same would give the framework a harder time picking the right layout. Just tried it out and that doesn't seem to be the case.


Delete an agent breaks the UI if there exists a connection for the deleted agent

@wrathagom should we delete the connection to, or remove the agent from the connection?

I think it would be best if we remove the agent from the connection. Any chance we can turn the green checkmark/link on the connections list to a broken chain/red link?

Sure! Sounds good

Closed by https://github.com/samtecspg/articulate/commit/691360050818750216414630c4ceb58288869184


AVRO-3503 Fix usage of 'is' and 'as' in Equals

Jira

[ ] My PR addresses the following Avro Jira issues and references them in the PR title. For example, "AVRO-1234: My Avro PR"

https://issues.apache.org/jira/browse/AVRO-3503

Tests

[ ] My PR adds the following unit tests: Adding coverage for Equals changes

Commits

[ ] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain Javadoc that explain what it does

Currently working on tests.

I recommend to add the unit tests first into a different PR for each Equals code which will be changed. Once there is test coverage, the Equals code should be modified in a seperate PR.

I am not sure changing to SequenceEqual is the way to go. IMO those changes have a high risk for a breaking change.

I can break it out into separate PR's.  I'm going to use this as a bucket to check against the CI pipelines.
As for SequenceEqual, I find it better than the for loops and nested if statements as long as it is comparing simple types.  I'm reluctant to use it for complex types.

The complexity of reviewing  the SequenceEqual change is definetely higher than the actual problem the ticket scopes for. E.g. SequenceEqual is using the default comparer EquityComparer<string>.Default. Which is in your case is the Ordinal comparison code. IMO that knowledge is not trivial and can be easily missed.
The unit tests should provide the baseline for the changes you make, unless the changes are trivial.

The other issue is changing the code behaviour of the Equals functions. It is standard practice to either throwing a exception if the argument is null or returning false. Some of the changes would return false instead of throwing the exception (which is the current implementation in some of those codes). Which might be ok, if we mark this PR as a major release PR, but in that case, the scope is definetely as it is described in the ticket.

In general, I'd recommend having A.Equals(object obj) compare obj.GetType() == this.GetType() rather than obj.GetType() == typeof(A). This way, if another class B is derived from A, then B.Equals(object obj) can call base.Equals(obj) to compare the types and the members inherited from A.  If A is a struct or a sealed class, then the JIT compiler should be able to optimize this.GetType() to typeof(A).


Cached recipe tab bitmap caches are never invalidated.

The images that are used to show an item's location on the currency tab are generated the first time Procurement has to show an item in the top-left tab location of the selected item.  This image is then cached and reused whenever it needs to show the selected location.  However, there is no method to remove old cached bitmaps, such as when the contents of stash tabs change.  So, after moving around/adding/removing items, the images Procurement shows can get out of date.

I noticed something similar for the recipe tab. It showed me an old image of my stash tab with items in it which weren't even there anymore.


Make hamcrest hasProperty to match on nested properties

Use case below
http://stackoverflow.com/questions/36363372/is-there-a-way-to-do-deep-comparison-on-a-nested-property-with-hamcrest/36364718#36364718
I use hamcrest for most of my testing ,but have encountered a issue with it not being able to test a property one level down in the object graph .A snipped of my test case is below
final List<Foo> foos= fooRepository.findAll(spec);
      assertThat(results, is(notNullValue()));
      assertThat(results, hasItem(hasProperty("id.fooID1", equalTo("FOOID1"))));

so here I want to check if in the list of foos I have a property id.fooID1 equla to FOOID1 .Here I am going one level down to check my nested property .This doesnt currently work in hamcrest and I get the following error.

java.lang.AssertionError:
Expected: a collection containing hasProperty("id.fooID1", "FOOID1")
     but: No property "id.fooID1"
    at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
    at org.junit.Assert.assertThat(Assert.java:956)
    at org.junit.Assert.assertThat(Assert.java:923)

THink hamcrest should enhance for convenient nested property comparisons.

I use the following method to make assertions on graphs of properties.
private static <T> Matcher<T> hasGraph(String graphPath, Matcher<T> matcher) {

    List<String> properties = Arrays.asList(graphPath.split("\\."));
    ListIterator<String> iterator =
        properties.listIterator(properties.size());

    Matcher<T> ret = matcher;
    while (iterator.hasPrevious()) {
        ret = hasProperty(iterator.previous(), ret);
    }
    return ret;
}

It simply creates nested matchers but it is easy to read as it can be used with a syntax like this:
assertThat(bean, hasGraph("beanProperty.subProperty.subSubProperty", notNullValue()));

It would be nice to have this functionality on the org.hamcrest.Matchers class.

+1

Not sure what to do, to support this request. I use the workaround of cristcost in some projects but would love to see that in Matchers.

Hm, great issue. My usecase - matching arbitrary properties in Spring Integration message payloads.

Good point

One small correction, you don't need to do the null value check. The matcher should handle that.

I've pushed HasPropertyWithValue.hasPropertyAtPath() based on your solution. See what you think.

I've pushed HasPropertyWithValue.hasPropertyAtPath() based on your solution. See what you think.

Due to the signature of this method, it can currently only be used if every bean on the path is of the same type T. Similar to
public static <T> Matcher<T> hasProperty(String propertyName, Matcher<?> valueMatcher)

it should rather look like this (or use the iterator, if you insist):
@SuppressWarnings("unchecked")
public static <T> Matcher<T> hasPropertyPath(String path, Matcher<?> valueMatcher) {
    Matcher<?> ret = valueMatcher;

    String[] properties = path.split("\\.");
    for (int i = properties.length - 1; i >= 0; --i) {
        ret = new HasPropertyWithValue<>(properties[i], ret, "%s.");
    }

    return (Matcher<T>) ret;
}

This change would allow this:
A a = ...
Matcher<D> dMatcher = ...
assertThat(a, hasPropertyPath("b.c.d", dMatcher));

I agree with @anma, the matcher should have exactly the same signature as hasProperty.
What's the reason for hasPropertyAtPath to don't use Matcher<?>?
Any possibility to change the signature @sf105 ?


Pass test filename to arguments of algob test command

Proposed Changes

Move loadFilenames function(and test) from builtin-tasks/deploy.ts to lib/files.ts
Add addOptionalVariadicPositionalParam testFiles. Now we can run test file we want to run.
Ex:  algob test ./test/test.js.

Please, review it! Thanks for your support! ❤

FYI, @vuvth , I'm using yarn test path/to/file for running tests. You can also use a watch mode:
yarn test -w path/to/file