Nushell 0.97.1 error

Hey,
So, today I upgraded nushell to latest version and an error appeared from this plugin, then a simple protocol version increase was enough to fix it.
What I didnt understood was, why have that protocol version in the first place?
It's like asking, you have to upgrade the plugin everytime there is a new nushell version.

Yes, that's how the Nu plugin system works.  It's not something that can be mitigated by plugin authors.  We just have to keep tweaking and rebuilding our plugins.  I imagine it will be like this until Nu 1.0 release, and then we'll have stability.
The plugin protocol went through quite a bit of change during 0.90 - 0.94, but has since settled down, so it's generally now a matter of bumping the version number.
I'll do that shortly.

No, I mean.
PROTOCOL_VERSION=$(nu --version)

Ah, that's an interesting idea.
The benefit is that the plugin continues to work across Nu version updates.
The drawback is that it bypasses the Nu protocol version compatibility check, so unexpected breakage may occur.
But I'm up for this, so let's see how well it works.

Still, it would require the update if there were a breaking change.
And in both situations it would break, if new version and if breaking change.
Cool.

I'll close this when I've released 0.13 with your version idea.

Aargh!  This isn't going to work @dougg0k .  The plugin is actually broken because the protocol changed.
Nice idea, but for now I'm going to continue releasing a new version for each Nu release.

Line 337, 382 and 387 change to .Value[1].String
Line 157 change to echo -n "\"Value\":[{\"Record\":{\"val\":{"
Line 178 change to echo '},"span":{"start":0,"end":0}}},null]}}]}'
And fixed.
But now there is a signal msg that needs handling and I dont know how to. At least the plugin works.
nu ✗ ssh-agent | bash-env
Agent pid 3508019
╭───────────────┬─────────────────────────────────────╮
│ SSH_AUTH_SOCK │ /tmp/ssh-XXXXXX5U2pmh/agent.3508015 │
│ SSH_AGENT_PID │ 3508019                             │
╰───────────────┴─────────────────────────────────────╯
unexpected input: {"Signal":"Reset"}
``

I have concluded that implementing the Nu plugin protocol by hand has become unreasonable.  It grew in complexity, and the initial idea of using jq to process the protocol is no longer fit for purpose.
I am in the process of adding a Rust layer to interface with the Nu protocol engine, and hand off the actual environment processing to a separate bash process.
I'll leave this issue open until that is done, and I have something that works with this new approach.

My dev branch has a basically working implementation of the Rust protocol wrapper.
I'm pretty happy that this will make it easier to maintain in future.
I need to test it a bit more thoroughly and build the package in CI/CD for the tests.  Not today though.

I suppose now you can also automate to upload to crates.io, making it easier to update.

I might not automate the crate publishing for now. :smile:
Thanks for your input here.

Another thing, maybe you could make the code rust only and even better.
https://github.com/rust-shell-script/rust_cmd_lib

No, that's not going to work well.
Bash is complex, and trying to emulate it via a third party implementation is going to be an exercise in frustration.
Only by using actual Bash do you get complete compatibility.  Which is what this plugin is all about. :sunglasses:

It doesnt seem to be emulating anything, but rather running bash through rust.
But, if you say so.

Ah, so it's a convenience library over subprocess, or equivalent.  But that isn't all that inconvenient TBH.
I'm not sure I'm sufficiently interested to spend time looking into it.


feat(plugins): use @tauri-plugins/ namespace on NPM

Initially I wanted to use @tauri-apps but the conflict between the tauri CLI @tauri-apps/cli and the CLI plugin name sucks.

I think we should instead be using @tauri-apps/plugin-* so it feels familiar and more authentic and if we ever move to @tauri/* we can still have the CLI and the CLI plugin under the same org.


[Feature Request] implement a standard_normal keyword arg for RewardScaling transform

Motivation
ObservationNorm transform can be called with standard normal ((x-loc)/scale) or regular (x*scale+loc). For consistency, we should implement this option for both.
I would keep it False by default for now (or default it to true and rename the transform to RewardNorm).

Cc @adityagandhamal

I would keep it False by default for now (or default it to true and rename the transform to RewardNorm).

As far as the consistency is concerned, I believe it should be kept False by default; as is wrt the ObservationNorm.

Should I change this line to return reward * scale + loc so as to maintain the same idiom across the code?


ignore use of metacarpals when calculating finger lengths via OpenXR

Summary
Removes metacarpal lengths from the total finger length calculation. The finger length is expected to be the length of the finger beyond the palm.
Contributor Tasks
These tasks are for the merge request creator to tick off when creating a merge request.

[x] Pair review with a member of the QA team.
[x] Add any release testing considerations to the MR for the next release.
[x] Check any relevant CHANGELOG files have been updated.
[x] Ensure documentation requirements are met e.g., public API is commented.
[x] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.
[x] Add any relevant labels such as breaking to this MR.
[ ] If this MR closes a Jira issue, make sure the fix version on the JIRA issue is set to the correct one.

Reviewer Tasks
Add any instructions or tasks for the reviewer such as specific test considerations before this can be merged.
Use emojis in review threads to communicate intent and help contributors.

[x] Code reviewed.
[x] Non-code assets e.g. Unity assets/scenes reviewed.
[x] Documentation has been reviewed. Includes checking documentation requirements are met and not missing e.g., public API is commented.
[x] Checked and agree with release testing considerations added to MR for the next release.

Closes JIRA Issue
Closes UNITY-992

This looks good to me.


Write a JavaScript program to convert inches to feet

Description
Write a JavaScript program to convert inches to feet
1 foot = 12 inches
Input  : 60
Output : 5

How to contribute

Save the solution in ConvertInchesToFeet.js file
Add ConvertInchesToFeet.js file in program/convert-inches-to-feet folder

!assign

!assign

@Sumsum1000  this issue has been closed already


chore(Gamut): removed unused Banner and Cover cards

Removed unused Banner and Cover cards
They're not used anywhere.

📬Published Alpha Packages:@codecademy/brand-components@0.8.14-alpha.2ea412.0@codecademy/gamut-templates@2.6.6-alpha.2ea412.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5e8d0ab821d652653df28f94--codecademy-styleguide.netlify.comDeploy Logs


Write timezone-adjusted deadlines to the database

possible fix for #94 -- not sure about saving without checking for error though

TESTED=did some basic messing with the UI: changing dates multiple times, canceling, etc, seems to work


Why are your docs misleading?

I am trying to integrate web3Auth into my Flutter app. However the steps regarding setting up your package to work on iOS at https://pub.dev/packages/web3auth_flutter is different from the content on your site at https://web3auth.io/docs/sdk/pnp/flutter/install. I am literally and figuratively confused
Steps to reproduce

Go to https://pub.dev/packages/web3auth_flutter

Check the requirements for iOS under the Requirements section. It currently says this

For iOS, only iOS 12+

but then you go ahead to say

For iOS build: platform :ios needs to be 14.0

This is a contradictory statement

Scroll down to the iOS subsection under the Configuration section. It currently says this. I honestly have no idea what this is supposed to mean

Yeah. Just that. Nothing else

Now go to the docs on your website https://web3auth.io/docs/sdk/pnp/flutter/install

Scroll down to where it mentions configuring Web3Auth for iOS, specifically the Add dependencies section it currently says this

I am just really confused. Which should I follow? https://pub.dev/packages/web3auth_flutter? https://web3auth.io/docs/sdk/pnp/flutter/install? Or am I supposed to somehow combine both?

We fixed the readme now


Bug: Fixing index column validation in s3.read.parquet() validate schema

Bug

Fixing index column validation in s3.read.parquet() validate schema.
Add test case to validate the above.

Relates

#1717

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: cbc282e600fff7175d9e028dc8035531432fb730
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Topic/nested for

Extracted nested for loop from topic/if.
This also contains the parsing side refactoring for fileparser.py and blockparser.py.

I'm not a big fan of factory methods and believe using concrete classes as parsers would be better. Anyway, I'll merge this now and see can the methods be turned to classes later. This new functionality also needs documentation before we can consider #3079 ready.


xp for GO:1990755

I've just added GO:1990755 (Label: mitotic spindle microtubule depolymerization) in TGFreeForm. I think it could have this logical definition:
intersection_of: GO:0022411 ! cellular component disassembly
intersection_of: results_in_disassembly_of GO:1990498 ! mitotic spindle microtubule
cheers
m
Reported by: mah11
Original Ticket: geneontology/ontology-requests/11717

Might already be done?

Term's been available for a while, but still doesn't have the xp.

Fixed as requested.


add enhancements to the chat filter

add option to also use a default chat filter regex
add ability to exclude yourself, friends, or clan members from your filter

Link whatever issue this closes in your body closes #xxxx

Did you test this on a player with spaces in their name?

Did you test this on a player with spaces in their name?

confirmed that it works on a player with spaces in their name

Even though incomplete, #8305 may be worth taking some things from too for this (the tests mostly & centralizing the filter check).


Gracefully shut down tarpc

I'm writing a daemon with two threads: a tarpc that gets the client requests, and a "worker".
When i terminate (TERM signal, not KILL), i need that the tarpc shuts down gracefully, simply not accepting further connections but serving the active requests.
Is there a way?
i've read https://github.com/google/tarpc/issues/307 but i could not find a way.

Hi, thanks for the question! It should be possible. Can you share your code? Do you have a task that accepts new channels, and then you have a separate task executing each channel? If so, basically you'd just want the channel-accepting task to be abortable (might be able to just wrap it in an abortable future), and then there'd be a signal handler that aborts it. I haven't used signal handlers in rust. The CLI book has some instructions for setting up a thread that handles signals: https://rust-cli.github.io/book/in-depth/signals.html

Thank you for the comment!
sadly i can't share the code, because actually i'm writing the business logic library that will be used by this daemon, not the daemon itself, i will write it eventually.
Actually i used the term "worker" in a different way: the "worker thread" will do some math, file, net and db work, constantly and independently, and another thread (the one with tarpc) that listens for the client requests (simple CLI + tarpc applications on client PCs), and this thread will read the requests from tarpc and it will set some variables used by the "worker thread".
the "task" of the tarpc will be very fast, i will not need to spawn a thread for a request.


Lint warning Avoid using dynamic typ on extension type with version 1.1.4

Describe the error
With the version 1.1.4 the dart_code_linter package, the following code raises a lint warning on the line final Asset asset:
extension type Asset(String path) { }

class TestClass {
  const TestClass({required this.asset});

  // Lint warning: Avoid using dynamic typ
  final Asset asset;
}

This warning is should not be triggered, as the Asset is a valid extension type. The warning does not occur in version 1.1.3 of dart_code_linter
How to replicate the bug
Step by step to reproduce the error:

Use dart_code_linter version 1.1.4.
Define an extension type and use it as a class property as shown in the code above.

@quoc-huynh-cosee  You are right, It turns out that this functionality was released in a stable form in Dart version 3.3.0 and that scenario was not contemplated.
I hope to fix it tomorrow,Thanks for reporting it

@quoc-huynh-cosee This will be deployed in the next release


auto renewal doesn't support taxes

When toggling auto renewal on a domain paid with taxes (in this example California), the allowance is not big enough so we can't renew it. We could fix it by adding a way to retrieve the exact price after tax or by allowing the maximum. I suggest the former.

done


Finish Setting up Socials

[x] Slack
[x] GitHub
[x] YouTube
[x] LinkedIn
[x] Twitter

requires a k8gb.io email address
k8gb.io email address is a WIP

[ ] #1644

@elohmrow it's all done, correct?

@elohmrow it's all done, correct?

@ytsarev yes 👍


Overrides HTTP access log timestamp to use request arrival time.

Fixes #14.

Coverage remained the same at 100.0% when pulling 67a7e8896429f6a5ca5e9a38f0a09983a4b6082a on AndreLouisCaron:request-arrival-time into e962872e873b26fffa8e0b71a2a140565092b8cb on smartmob-project:master.


RN-306 Don't scroll to results when recent search is removed

Ticket Link
https://mattermost.atlassian.net/browse/RN-306

@hmhealey done


Easy view of Alchables in Bank

When clearing out my bank I like to look for any alchables I have lying about and find it annoying to have to look at each one individually to see which turn a profit and which don't.
I would like for there to be a tab, perhaps through the use of the Bank Tab addon by automatically attributing a specific tag, within the bank that only shows items that high alch for a profit. Possible features that can be added include setting a profit margin as a filter and selective item filtering.
An alternative solution would be to highlight the items which alch for profit but I can imagine this would be more difficult as it presents issues with scrolling.

You can search in the bank with ha > 350

Had no idea you could do that, thank you.
I still think it would be nicer to be able to have a bank tag do that, is this still a possibility?

It was a conscious decision at the time to not have it as a tag tab.
You can also search on a range or GE price
ge >= 2k
or
ha 400 - 5k

Thank you very much!

I noticed that there is no way of calculating the difference between the ge price and the high alch price which is what this request was all about, ha > 250 only gives items that alch for more than 250gp, there also doesn't seem to be a possibility of doing ha-ge > 250 in order to resolve this, would that be a viable solution?

Available in plugin hub as High Alc Highlight


Optimize mirror node get accounts call with limit

Description:
Mirror node calls for account has the unintended effect of getting the page limit of tranactions

Updated get account call to use order=desc and limit = 1
Updated spect ts
Add missing mocks in some spec tests

Related issue(s):
Fixes #1339
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.91 :tada:

Comparison is base (36a8346) 74.97% compared to head (da72e8f) 75.89%.

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

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1340      +/-   ##
==========================================
+ Coverage   74.97%   75.89%   +0.91%
==========================================
  Files          33       32       -1
  Lines        2482     2456      -26
  Branches      497      497
==========================================
+ Hits         1861     1864       +3
+ Misses        467      433      -34
- Partials      154      159       +5

Impacted Files
Coverage Δ

packages/relay/src/lib/clients/mirrorNodeClient.ts
88.85% <100.00%> (+0.23%)
:arrow_up:

... and 5 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Silent failure on invalid release version name

Issue Description
We have an app for years now, always worked fine with Fastlane and the Firebase App Distribution plugin.
For the first time, we have released with a version named 0.2.7+rc1, instead of the usual 0.2.7+2 (i.e. a number after the plus). It worked, but was ignored in the emails sent to tested, and actually overwrote (?) 0.2.7. It seemed it ignored the build label. Later, we released 0.2.7+rc2, which led to emails with 0.2.7 (2).
Later again, we released 0.2.7+gc, so no number anymore. And here was the silent error:

The lane execution works fine until the end. It warns of nothing unusual, and succeeds.
Nothing happens after that. No warning in the CLI or the Firebase console. The new build does not appear in the list on the console.
We then tried 0.2.7+3, and that just worked as usual.

So the problem is in the build label being something else than a number.
Is this a  bug or a feature? Honestly I remember reading the build number must be a number... So it is definitely "my fault". However the bug is the silent failure. Choosing a non-number for the build number should raise an error and avoid magic. I believe a warning is not enough here.
Side note: It is pretty common to have RCs and GMs and betas, basically text labels to tag builds. An alternative to error management is to allow text, if Firebase allows it.
Configuration
firebase_app_distribution(
  app: 'app_id',
  testers<EMAIL_ADDRESS>  release_notes: 'release_notes',
)

Complete verbose output
trace.txt
Environment

Library
Version

fastlane
2.185.0

fastlane-plugin-firebase_app_distribution
0.2.9

Hey Eric, thanks for the report. I wasn't able to reproduce locally. I set 0.2.7+rc1 as the CFBundleShortVersionString and CFBundleVersion to test both, and uploaded my test app via fastlane.
Here's what showed up in the dashboard:

Where/how is your app version specified in your project?

Thank you for looking into it. I came to realize an information is missing: I am using Flutter (2, not latest, but a few weeks old).
Would the problem be in Flutter or it’s integration with Fastlane?

Ah, gotcha. Probably the latter, perhaps it's having trouble parsing certain variations of non-conventional version strings. Unfortunately that's where my knowledge falls short 😅 .

Ah, gotcha. Probably the latter, perhaps it's having trouble parsing certain variations of non-conventional version strings. Unfortunately that's where my knowledge falls short 😅 .

Would you recommend where I could forward this? I will look at how the Flutter plug-ins are maintained in GitHut, but if someone knows the right place, appreciated!


Add orca gbw

[x] check .gbw reader @ 4.0.0 and 4.2.1
[x] ? manual correction for 3d @ def2svp etc -- is the order version dependent?

Maybe it's worth to specifying that we only deal with version 400 and 421 (in the doc or so)?

Orca  versions 4.0.0 and 4.2.1 are available on lc2 and 5.0.4 is on lc3. We may need to access some computations obtained with all of them (recently I had to read some old .scfp file by 4.0.0). As you see from the code, the .scfp/.scfr format has changed between 4.0 and 4.2, and in 5.0 they changed it to .densities. I haven't implemented readers for other versions because don't think we need it & don't want to install them but this can be done.
What would you say in the doc?
Actually I need to check if the .gbw format is the same for all the versions:

[ ] check .gbw reader @ 4.0.0 and 4.2.1

unless you wanted to do something more than throwing a warn()

I changed one of the warnings to error because it doesn't make sense to change AO order from orca to pyscf or whatever when the original order is wrong. Still, one can load the file without reordering, correct the 3d elements or anything manually and then reorder for pyscf.
Alternatively, I can just add a manual correction for 3d elements @ def2-svp and others.
Also I was thinking about trying to find a .gbw file in the same directory and using the basis set from it,
but it is weird because then you can read orbitals and then you don't need the density files.
What do you think?

@YAY-C do you think I can merge?

Sorry, I just saw the message!
But yes, I think it's ready for merging :+1:


Explain settings options

Most options in Settings are pretty hard to understand without more context. For example, what would "Read on Open" or "Badge Unread" mean to new users? (see screenshot)
We should look into how we can enable that. iOS does this by adding a footer to the cell, but seems to only do this once per section.

May be an idea to break it up a bit more than it is now as well?
You've got "Report a Bug", "View Source Code", "Star on Github" which are sort of GitHawk related but more so actions
Then "Badge Unread" which I feel could fall under it's own refresh title with an option to turn off background refresh entirely (without having to use app settings, ideally), badge unread and badge mentions (#292).
Also "Read on Open" and "GitHawk Signature" are generic settings which definitely need more explaining on their own

+1 for explanations for settings options.
iOS has the settings explanations on lots of places inside Settings app. For example, take a look at Settings -> General -> Accessibility
Note that if a settings option needs explanations, IOS has separate Section header title, cell and footer title for it.
AFAIK there is no option to enable it. However from popular form builder Projects like Eureka and XLForm having Separate section is the only easy way.
So we can group options under a section (w/ header title) and whichever settings need explanations we can have a separate section (w/ footer title)

Yep, think you'd have to do so manually, but that should be quite easy.
Sent with GitHawk

I think breaking it up by: Github/ GitHawk / Personal Settings would be a good thing now. We just added a push notifications switch and the 2nd section is a bit packed. I'd suggest breaking it up with:
GitHawk

Report a Bug
View Source Code
Write a Review

Personal

Double Tap Reaction
Badge Unread
Push Notifications
Read on Open
GitHawk Signature


When vm_stat fails when starting a daemon, the entire build fails

This causes a RuntimeException to be thrown:
https://github.com/gradle/gradle/blob/master/subprojects/launcher/src/main/java/org/gradle/launcher/daemon/server/health/memory/VmstatAvailableMemory.java#L63-L63
Which, I think was supposed to be guarded against here:
https://github.com/gradle/gradle/blob/master/subprojects/launcher/src/main/java/org/gradle/launcher/daemon/server/MasterExpirationStrategy.java#L76-L76
But since the RuntimeException is not handled, it bubbles up the call stack. addLowMemoryDaemonExpirationStrategyWhenSupported is called by MasterExpirationStrategy's constructor.  And MasterExpirationStrategy is created in DaemonServices.  Any exception occurring during service registry initialization just causes the entire daemon to shutdown.
Expected Behavior
The build should be able to continue working even if we cannot run vm_stat.
Current Behavior
The daemon randomly fails to start.  This occurs deep in the service registry/initialization code.
Context
As reported on the forums:
https://discuss.gradle.org/t/build-stops-with-message-gradle-build-daemon-has-been-stopped-service-stop/20517/4
Steps to Reproduce (for bugs)
This happens randomly due to /usr/bin/vm_stat failing.  I don't know of a reliable way to make it fail.
Your Environment
This affects macOS only.
Implementation comments
There are a few oddities for me with the current implementation of MemoryInfo and the various AvailableMemory types and how it interacts with the expiration strategies.  I would expect DefaultExecActionFactory to be injected from somewhere.  I would also expect AvailableMemory instances to be reused due to the comment in VmstatAvailableMemory, but maybe this is intentional to prevent state from bleeding between health checks.
To fix the service injection, I think you could pull MemoryInfo up to DaemonServices, inject the appropriate AvailableMemory and determine the type of AvailableMemory in the service registry (instead of in MemoryInfo).  That way you don't have to carry the dependencies for all the different types of AvailableMemorys around in MemoryInfo.
I think we should also change the way the LowMemoryDaemonExpirationStrategy is added to MasterExpirationStrategy so that we don't rely on exception handling from checkExpiration telling us if we should use LowMemoryDaemonExpirationStrategy.  I think it makes sense to just always add it and handle the failure elsewhere.  Maybe this can just be a AvailableMemory that returns -1 (or MAX_INT) if the underlying implementation fails once.

And as a separate thing, we should consider adding whatever functionality we need to do this natively into native-platform instead of forking a process and scraping its output.

I plan to add some way to query memory to native-platform at some point.

Thanks @big-guy for the detailed report and your insights.
Detangling memory health-checks and expirations strategies will be handled out of this issue which really is about a bug that can be fixed right away in isolation.

LGTM @eskatos


fix autoload deprecation warning

solutions_sidekiq    | 2022-04-23T03:39:25.183Z pid=1 tid=gmo8hx245 WARN: DEPRECATION WARNING: Initialization autoloaded the constants EmberCliRailsAssetsHelper, ApplicationHelper, ApiClientsHelper, ApiFormsHelper, ApiNamespacesHelper, ApiResourcesHelper, ContentHelper, DashboardHelper, MessagesHelper, SearchHelper, SigninWizardHelper, SignupWizardHelper, SimpleDiscussion::ForumPostsHelper, SimpleDiscussion::ForumThreadsHelper, SubdomainHelper, UsersHelper, EmberRailsHelper, LocalTimeHelper, Comfy, Comfy::Admin, Comfy::Admin::CmsHelper, Comfy::CmsHelper, DeviseHelper, and ApplicationController.
solutions_sidekiq    |
solutions_sidekiq    | Being able to do this is deprecated. Autoloading during initialization is going
solutions_sidekiq    | to be an error condition in future versions of Rails.
solutions_sidekiq    |
solutions_sidekiq    | Reloading does not reboot the application, and therefore code executed during
solutions_sidekiq    | initialization does not run again. So, if you reload EmberCliRailsAssetsHelper, for example,
solutions_sidekiq    | the expected changes won't be reflected in that stale Module object.
solutions_sidekiq    |
solutions_sidekiq    | These autoloaded constants have been unloaded.
solutions_sidekiq    |
solutions_sidekiq    | In order to autoload safely at boot time, please wrap your code in a reloader
solutions_sidekiq    | callback this way:
solutions_sidekiq    |
solutions_sidekiq    |     Rails.application.reloader.to_prepare do
solutions_sidekiq    |       # Autoload classes and modules needed at boot time here.
solutions_sidekiq    |     end
solutions_sidekiq    |
solutions_sidekiq    | That block runs when the application boots, and every time there is a reload.
solutions_sidekiq    | For historical reasons, it may run twice, so it has to be idempotent.
solutions_sidekiq    |
solutions_sidekiq    | Check the "Autoloading and Reloading Constants" guide to learn more about how
solutions_sidekiq    | Rails autoloads and reloads.
solutions_sidekiq    |  (called from <top (required)> at /var/app/config/environment.rb:5)

Research:

https://ryanfb.github.io/etc/2021/06/25/diagnosing_rails_6_deprecation_warning_-initialization_autoloaded_the_constants.html
https://bill.harding.blog/2021/07/22/rails-6-1-deprecation-warning-initialization-autoloaded-the-constants-what-to-do-about-it/

could be caused by mailgun, try upgrading the library
https://github.com/mailgun/mailgun-ruby/issues/215

POC: https://github.com/restarone/violet_rails/pull/808


[multsig-api][General] Update Prove Ownership message from wallet

Refer to docs:
https://aura-network.notion.site/Function-Connect-Wallet-e046d43db6cd4017aaeffdeb39be20c4

Verified. PASS


Using String values as keyPath fails when using getById

Great work, thank you for this repo, loving it.
Just came across an issue where using String values as the id does not work.
You can write to the database with a String value such as "abc" fine. However when you do a getById it fails
String values as a number as opposed to other characters appears to have different behaviour.
To explain better I made a small demo
https://codesandbox.io/s/competent-hill-5w9v5
Cheers

@pklitscher new release should fix this bug


1.7: MTU does not default to nic of default route

I'm running on GCE which has a MTU of 1460 by default.  I see all containers have 1500 MTU on their interfaces.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

assigned to @mavenugo


How to achieve Bluetooth low energy consumption?

How to achieve Bluetooth low energy consumption? Now that Bluetooth is 50ma when it is started, how can it be achieved below 10ma?

https://github.com/espressif/esp-idf/issues/947#issuecomment-500312453


items-array not shown

e.g. modeOfTransport in INTEL_REPORT_SUBMITTED

not recreated - probably solved by another fix


404 route fails on gh-pages

When visiting a none-existing url like /foo-bar the GitHub 404 page is shown in stead of our own custom page.

Apparently gh-pages (Jekyll) does not even support .htaccess files.
Closing for now, it's not a big deal for a singular page.


segmentInfos.replace() doesn't set userData

Description
Found that the replace method doesn't set userData with the new user data from other. Unsure if this is an oversight, but if it is, I have a PR up here.

Existing:
  void replace(SegmentInfos other) {
    rollbackSegmentInfos(other.asList());
    lastGeneration = other.lastGeneration;
  }

Fix:
  void replace(SegmentInfos other) {
    rollbackSegmentInfos(other.asList());
    lastGeneration = other.lastGeneration;
    userData = other.userData;
  }

Version and environment details
Lucene version 9.7

I was curious about this one, and whether it is a bug or intentional.
I noticed that the IndexWriter constructor that calls SegmentInfos.replace() has a comment saying:
          // Swap out all segments, but, keep metadata in
          // SegmentInfos, like version & generation, to
          // preserve write-once.  This is important if
          // readers are open against the future commit
          // points.
```

I suppose the `userData` isn't metadata, so you might expect it to be replaced too.

Also, `replace` is called when we have explicitly said that we want to load an earlier commit when initializing the `IndexWriter`. Part of that earlier commit is its `userData`, right?

tl;dr: Yeah -- this sounds like something that got missed.

Yeah exactly. I'd say userData isn't metadata so it should get replaced as well.

@msfroh this impacts the ability to snapshot since you can't read old userData. Check out the test in my PR: https://github.com/apache/lucene/pull/12626


Endpoint for repositories within an organization

I'm trying to give staticman access to my repository, I've added staticman as a collaborator.
Next step is to perform a handshake with the URL below:
https://api.staticman.net/v2/connect/{your GitHub username}/{your repository name}
In my case, my organization is called 'bcondevops' and the repository is called bcondevops.github.io.
When I try to call the endpoint I get back 'Invocation not found'
I've tried both the v1 and the v2 endpoint.

Hello @richardrobberse,
As referenced in issue #227, people using Staticman have now went to using v3 of the tool, which is a GitHub application. Follow the steps within this comment #243 . Note: He has updated the tool to production, so use api.staticman.net as the URL instead of dev....
Hope this helps.

This is a duplicate of #227.

Closed as duplicate of #277


AuthorizationFilterContext is no longer available in HandleRequirementAsync()

In ASP.NET Core 3.0 AuthorizationFilterContext is no longer available inside AuthorizationHandler.HandleRequirementAsync() method.
In 2.2 this method is used to work:
protected override Task HandleRequirementAsync(AuthorizationHandlerContext context, CookieOrTokenAuthorizationRequirement requirement)
{
	if (context.Resource is AuthorizationFilterContext mvcContext)
	{
		if (mvcContext.Filters.Any(filter => filter is MyFilter))
		{
			context.Succeed(requirement);
			return Task.CompletedTask;
		}
	}
}

However, in 3.0 context.Resource is no longer AuthorizationFilterContext, but instead Microsoft.AspNetCore.Routing.RouteEndpoint.
What's recommended way of accessing action filters in 3.0 inside AuthorizationHandler?

protected override Task HandleRequirementAsync(AuthorizationHandlerContext context, CookieOrTokenAuthorizationRequirement requirement)
{
	if (context.Resource is Endpoint endpoint)
	{
		if (endpoint.Metadata.OfType<IFilterMetadata>().Any(filter => filter is MyFilter))
		{
			context.Succeed(requirement);
			return Task.CompletedTask;
		}
	}
}

In ASP.NET Core 3.0:
When using endpoint routing,
Mvc will add all Filter as metadata to endpoint.Metadata and the AuthorizeAsync will called by AuthorizationMiddleware

Worked like a charm, thanks for the fast response!

As it is breaking change for Preview 8 - will we have workaround or suggested solution on how to redirect to custom URL when authorization failed?


AS not working

Describe the bug
The plugin just stopped working, just for changes I made the calendar a little longer for the change in weather and it worked fine. I just added an AxCalendar plugin | Customizable Advent Calendar and it stopped working
How to reproduce
The plugin just stopped working, just for changes I made the calendar a little longer for the change in weather and it worked fine. I just added an AxCalendar plugin | Customizable Advent Calendar and it stopped working
Screenshots / Videos

Server Log
No response

Hi, you must provide the server log which would let us diagnose your issues. It's located in logs folder, will be called latest.


new gt4py tag

new tag --> icon4py_20240903

launch jenkins py-gt4py

balfrin
:green_circle: unit testTest:green_circle:summary :green_circle: integration testTest:green_circle:py-gt4py-spack_info :green_circle:py-gt4py-spack_spec :red_circle: system<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
launch jenkins py-gt4py

launch jenkins py-gt4py

balfrin
:green_circle: unit testTest:green_circle:summary :green_circle: integration testTest:green_circle:py-gt4py-spack_info :green_circle:py-gt4py-spack_spec :red_circle: system<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
balfrin
:green_circle: unit testTest:green_circle:summary :green_circle: integration testTest:green_circle:py-gt4py-spack_info :green_circle:py-gt4py-spack_spec :red_circle: system<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
balfrin
:green_circle: unit testTest:green_circle:summary :green_circle: integration testTest:green_circle:py-gt4py-spack_info :green_circle:py-gt4py-spack_spec :red_circle: system<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
launch jenkins py-gt4py

balfrin
:green_circle: unit testTest:green_circle:summary :green_circle: integration testTest:green_circle:py-gt4py-spack_info :green_circle:py-gt4py-spack_spec :red_circle: system<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
launch jenkins py-gt4py

balfrin
:green_circle: unit testTest:green_circle:summary :green_circle: integration testTest:green_circle:py-gt4py-spack_info :green_circle:py-gt4py-spack_spec :green_circle: system<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
This PR changes the tests of py-icon4py and they fail:
https://jenkins-mch.cscs.ch/job/Spack/job/spack_PR/1720/artifact/log/balfrin/system_test/install_py_icon4py_version_0_0_12-py-icon4py_<EMAIL_ADDRESS>https://jenkins-mch.cscs.ch/job/Spack/job/spack_PR/1721/artifact/log/install_py-icon4py.log
This was missed because the tests were never executed. My advice, always run "launch jenkins all".
Until this is fixed I'm going to revert this PR because it is blocking several other PRs.
@nfarabullini can you please have an other look at it? Thank you.


Forrest can’t run (scripts)

Tested with:
node   5.5.0
npm    3.8.8

Could you provide more information on how you load node? I expect nvm loading inside of your zshrc?

Update. Forrest runs after changing my environment to:
node   v6.4.0
npm    3.10.6

Does it need Node 6.x?

No, that doesn't make much sense. But I'll dig into  it over the weekend. Could you still provide pieces of your zshrc? :)

I load nvm with the following two line in my zshrc:
export NVM_DIR=~/.nvm
source $(brew --prefix nvm)/nvm.sh

Did you change it temporarily or set a new nvm default?

Nope. Its now like that:
$ nvm ls
       v0.10.43
        v0.12.4
        v0.12.7
         v4.2.2
         v5.1.0
         v5.2.0
         v5.4.0
         v5.5.0
         v6.0.0
         v6.2.0
->       v6.4.0
default -> node (-> v6.4.0)
node -> stable (-> v6.4.0) (default)
stable -> 6.4 (-> v6.4.0) (default)
iojs -> N/A (default)

Before that v5.5.0 was the default.

Are you sure node and npm where there when you open a new terminal session?
This is all forrest does. Starting a new terminal session and then executing commands.
maybe you're running into this nvm bug
nvm is not compatible with the npm config "prefix" option: currently set to "/usr/local/Cellar/nvm/0.31.2/versions/node/v6.3.1"
Run `nvm use --delete-prefix v6.3.1 --silent` to unset it.

which forced me to execute this for every new sessino for a while?

Can’t reproduce.


[9.x] Vite

:zap: Vite is a modern frontend build tool that provides an extremely fast development environment and bundles your code for production.
This PR introduces a @vite Blade directive to the framework that will be used in combination with the official Laravel Vite Plugin. This PR does not remove or deprecate the existing mix() helper. There are also PRs to laravel/laravel as well as laravel/breeze and laravel/jetstream that will make this the default for new Laravel applications. There is also, of course, documentation.
The Laravel side of the implementation is similar to Mix and should feel quite familiar.
The main difference is that instead of using the mix() helper, you would now use the @vite Blade directive. The reason for the directive is that Laravel needs to output complete <script> and <link rel="stylesheet"> tags, rather than just a path as with Mix.
For the best experience with a Blade app, you will want to specify both CSS and JavaScript entry points, which would look something like this in your Blade layout template:
- <link rel="stylesheet" href="{{ mix('css/app.css') }}">
- <script src="{{ mix('js/app.js') }}" defer></script>
+ @vite(['resources/css/app.css', 'resources/js/app.js'])

In development mode, this will also load the Vite client, which will automatically reload your JavaScript and CSS when you make changes. In production mode, it will automatically load the versioned assets for you.
For the best experience with a SPA (e.g. Inertia), you will want to import your CSS via your JavaScript entry point(s) and then only specify the JavaScript entry point to the @vite directive, which would look something like this:
  import './bootstrap.js';
+ import '../css/app.css';

- <link rel="stylesheet" href="{{ mix('css/app.css') }}">
- <script src="{{ mix('js/app.js') }}" defer></script>
+ @vite('resources/js/app.js')

When importing your CSS via JavaScript, Vite will automatically inject a <style> tag in development mode that it will keep up to date. When building for production, a compiled app.{version}.css file will be generated that the @vite directive will automatically load via a <link rel="stylesheet"> tag.
When using React, you will also need to place a @viteReactRefresh directive above your @vite directive that will inject Vite's React Refresh Runtime.
Everything will be configured for you with Laravel's updated starter kits.
As with Mix, The @vite directive will automatically detect when the Vite development server is running, otherwise, it will use the compiled and versioned assets from the manifest.
The Laravel plugin also handles Vite SSR builds and works well with tools like Sail and Vapor.
The documentation will include full instructions, examples, and advanced configuration.
This implementation requires a specific Vite configuration that the official Laravel Vite Plugin handles for you. For existing applications, there are also some required changes documented in the upgrade guide.

Will the Vite manifest SRI plugin be supported by this? That would be nice.

Will the Vite manifest SRI plugin be supported by this? That would be nice.

It's on my list of things to look at post-launch and should be easy to implement :+1:

- <link rel="stylesheet" href="{{ mix('css/app.css') }}">
- <script src="{{ mix('js/app.js') }}" defer></script>
+ @vite(['resources/css/app.css', 'resources/js/app.js'])

How would you add nonces to this vite call?

Hi @jessarcher

The main difference is that instead of using the mix() helper, you would now use the @vite Blade directive. The reason for the directive is that Laravel needs to output complete

@tabuna there isn't a way to do this currently with Vite, however we are considering enabling the specification of arbitrary attributes on entry point tags.

@tabuna there isn't a way to do this currently with Vite, however we are considering enabling the specification of arbitrary attributes on entry point tags.

I was thinking about this also, about how I could add a CSP nonce to the script tag. What about a blade template that can be overridden? That way, instead of calling makeTag/makeScriptTag/makeStylesheetTag, the URLs are pushed to the collection instead and then passed to a blade template.

after installing a fresh app

@nlvedwin it looks like you are visiting the Vite dev server. You still need to utilise php artisan serve, Valet or similar.
For example if you are using Valet on your system, you should visit laravel-vite.test instead.

No, you load the normal artisan serve URL, @.***` will take of making it
able to hot reload from the development server.
On Wed, 29 Jun 2022 at 17:28, Aurelijus Ušeckas @.***>
wrote:

facing the same issue as @nlvedwin https://github.com/nlvedwin. I use
Sail with localhost already being exposed and accessible.
npm run dev loads dev server with localhost:3000 which in theory should
load the page with hmr? Unfortunately it throws 404 instead.
—
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/pull/42785#issuecomment-1170124217,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFQHI5AHHCQTHKLIJRJACDVRRTRBANCNFSM5YTKQLKA
.
 You still need to utilise php artisan serve, Valet or similar.
For example if you are using Valet on your system, you should visit laravel-vite.test instead.

@nlvedwin it looks like you are visiting the Vite dev server. You still need to utilise php artisan serve, Valet or similar.
For example if you are using Valet on your system, you should visit laravel-vite.test instead.

got it now, it feels like magic 🧙

For others who are having a 404 when trying to check the assets (http://localhost:3000/build/css/app.css), run vite build first to see if there are any errors compiling. I moved from SASS to PostCSS at the same time as upgrading to Vite and had a few errors that PostCSS couldn't deal with (commented out @apply, for one).

Hi all, referred here by @tabuna. For those of you who are looking for a direct replacement of the mix() helper, please see my Vite helper package on Packagist - https://packagist.org/packages/motomedialab/laravel-vite-helper

Hey folks,
A lot of questions in this thread about adding a CSP nonce, Subresource integrity, or arbitrary attributes (turoblinks, media query stuff, etc) to the Vite generated tags.
I've just opened a PR to support all of those use-cases.
You can check it out here: https://github.com/laravel/framework/pull/43442
Any feedback would be appreciated.

Awesome stuff @timacdonald, thank you so much!

Great work @jessarcher  :+1: ,
I think it will be nice if we can also use @vitejs/plugin-legacy to inject nomdule script tag. In some cases like using the iPhone with iOS 13 that not support modular bundles <script type="module">.
Thank you,

I think it will be nice if we can also use @vitejs/plugin-legacy to inject nomdule script tag. In some cases like using the iPhone with iOS 13 that not support modular bundles <script type="module">.

After https://github.com/laravel/framework/pull/43442 I get a workaround to inject legacy generated files
        Vite::useScriptTagAttributes(function (string $src, string $url, array|null $chunk, array|null $manifest) {
            if (in_array(
                $src,
                [
                    'vite/legacy-polyfills',
                    'app/resources/js/app/app-legacy.js',
                    'app/resources/sass/app/app-legacy.scss',
                ]
            )) {
                return [
                    'type' => 'text/javascript',
                    'nomodule',
                ];
            }

            return [];
        });

Late comment, but while the above works (thanks!) it is still loading the legacy script via preloads for modern browsers
eg.
<link rel="modulepreload" href="/build/assets/app-legacy-d2b2bf94.js" />
So far I've been unable to find a workaround for this

I was able to find an ondocumented callback for the preloads, in which returning false causes no preloads to be included.
By default, a normal or module preload will cause the legacy bundle(s) to be downloaded even in modern browsers.
The following worked for us in a ViteServiceProvider we added to the project.
<?php

namespace App\Providers;

use Illuminate\Support\Facades\Vite;
use Illuminate\Support\ServiceProvider;

class ViteServiceProvider extends ServiceProvider
{
    protected const NONMODULE_FILES = [
        'vite/legacy-polyfills-legacy',
        'resources/frontend/app/app-legacy.js',
    ];

    /**
     * Register services.
     *
     * @return void
     */
    public function register()
    {
        //
    }

    /**
     * Bootstrap services.
     *
     * @return void
     */
    public function boot()
    {
        Vite::usePreloadTagAttributes(function ($src, $url, $chunk, $manifest) {
            // Don't preload non-module files at all
            if (in_array($src, self::NONMODULE_FILES)) {
                return false;
            }
            // Use the default attributes for the rest
            return [];
        });
        Vite::useScriptTagAttributes(function (string $src, string $url, array|null $chunk, array|null $manifest) {
            if (in_array($src, self::NONMODULE_FILES)) {
                return [
                    'type' => 'text/javascript',
                    'nomodule',
                ];
            }
            return [];
        });
    }
}


cascading transformer comment typo

Sorry if I am misunderstanding cascading head paper, in the paper (pdf link), they are adding the previous head's attn output to next head's input (X'ij = Xij + ~Xi(j-1)) eq -3.  This head's input will be then mapped into k,q,v through their respective linear layers.
But why do we add it only to query in this repo's implementation? Is it because it might break kv-cache, etc. Sorry, if this is too noob of a question, I am still learning. Thanks.

@p0p4k ah hey, yea that doesn't look right
i'm going to remove it anyways

Okay, got it! Very interesting repo, I am going through it line by line, really like your style of coding.

Not 100% readable xD , but it is quite "smart" and inspiring. I am taking notes on a Jupyter notebook on the side which can complement this repo for slow learners like me.


Miscellaneous bugfixes / Tiny Feature Changes

Other fixes in this PR

Fix bat being killed outside of dungeons triggering secret event (and therefore secret chime)

gabagool


Make table updating when array push or splice

What problem does this feature solve?
According to Angular documentation, developers should not use push or splice to change the data passed to nzData.
But it will be confused, when array's address can not be rewrited. So the default behavior can handle most situations,but not all.
What does the proposed API look like?
I do some work for nz-table's source code, and i write some similar codes for implement this purpose, check the following code:
export class TestTableComponent implements OnInit, OnChanges, DoCheck {

  @Input() nzData: any = [];    //

  data: any = [];

  constructor() { }

  ngOnInit() {
  }

  ngOnChanges(changes){
      if (changes.nzData) {
          this.update();
          console.log("changed");
      }
  }

  ngDoCheck() {
      if(this.data.length !== this.nzData.length) {
          this.update();
      }
  }

  update() {
      this.data = [...this.nzData];
  }
}

Now you can bind the array, and push item to array, the nz-table whill update, and every thing works fine!
Just a idea for situations when array' address can not be redefined, and also this code just for reference, you guys know what i mean and will make it better!

Check OnPush on this page: https://angular.io/api/core/ChangeDetectionStrategy.

i see. have nothing to say in reply!

this is nothing to do with OnPush mode. cause you split data(bind for table component) away from nzData(input) for pagination. check source code:
updateFrontPaginationDataIfNeeded(isPageSizeOrDataChange: boolean = false): void {
    let data = this.nzData || [];
    if (this.nzFrontPagination) {
      this.nzTotal = data.length;
      if (isPageSizeOrDataChange) {
        const maxPageIndex = Math.ceil(data.length / this.nzPageSize) || 1;
        const pageIndex = this.nzPageIndex > maxPageIndex ? maxPageIndex : this.nzPageIndex;
        if (pageIndex !== this.nzPageIndex) {
          this.nzPageIndex = pageIndex;
          Promise.resolve().then(() => this.nzPageIndexChange.emit(pageIndex));
        }
      }
      data = data.slice((this.nzPageIndex - 1) * this.nzPageSize, this.nzPageIndex * this.nzPageSize);
    }
    this.data = [...data];
    this.nzCurrentPageDataChange.emit(this.data);
  }

if you bind nzData directly, you remove onpush mode, it works fine!
but now even if  remove onpush mode, also no effect for push and splice, you can try!

this is nothing to do with OnPush mode. cause you split data(bind for table component) away from nzData(input) for pagination. check source code:
updateFrontPaginationDataIfNeeded(isPageSizeOrDataChange: boolean = false): void {
    let data = this.nzData || [];
    if (this.nzFrontPagination) {
      this.nzTotal = data.length;
      if (isPageSizeOrDataChange) {
        const maxPageIndex = Math.ceil(data.length / this.nzPageSize) || 1;
        const pageIndex = this.nzPageIndex > maxPageIndex ? maxPageIndex : this.nzPageIndex;
        if (pageIndex !== this.nzPageIndex) {
          this.nzPageIndex = pageIndex;
          Promise.resolve().then(() => this.nzPageIndexChange.emit(pageIndex));
        }
      }
      data = data.slice((this.nzPageIndex - 1) * this.nzPageSize, this.nzPageIndex * this.nzPageSize);
    }
    this.data = [...data];
    this.nzCurrentPageDataChange.emit(this.data);
  }

if you bind nzData directly, you remove onpush mode, it works fine!
but now even if remove onpush mode, also no effect for push and splice, you can try!

the component won't and shouldn't modify[mutate] user data, the computation inside the table component is not the reference to your input data.

ok. just for display. no offense! this will never change user data by inside the component! and just update display.

no one changes user data. it takes time.


Task 10 & Task 11

Compiling Task 10 & Task 11 together along with the updates for task6

{
"Task 10.xaml":  [
{
"Variable str_userinput does not respect the set pattern ^(dt_)?([A-Z]|[a-z])+([0-9])$|out[A-Za-z][A-Za-z0-9_]$":  "Make sure all the variables follow the naming convention. "
},
{
"Activity Log Message has a default name.":  "Check if it could be easier to understand what the activity does by adding a more descriptive title. "
}
],
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
},
{
"Process does not define a main entry point.":  "Fix the project.json file to point to the entry/main workflow. "
},
{
"Dependency package UiPath.Excel.Activities is not used.":  "Remove unused packages in order to improve process execution time. "
},
{
"Dependency package UiPath.Mail.Activities is not used.":  "Remove unused packages in order to improve process execution time. "
}
]
}

{
"Task 10.xaml":  [
{
"Variable Str_userinput does not respect the set pattern ^(dt_)?([A-Z]|[a-z])+([0-9])$|out[A-Za-z][A-Za-z0-9_]$":  "Make sure all the variables follow the naming convention. "
}
],
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
},
{
"Process does not define a main entry point.":  "Fix the project.json file to point to the entry/main workflow. "
}
]
}

{
"Task 11.xaml":  [
{
"Flowchart Fruits/Vegetables flowchart is used in a secondary layer in Task 11.":  "Flowchart should only be used in top layer for maintainability and readability reasons. "
},
{
"MessageBox display name is defined many times. Current allowed threshold is 1. Code contains 7.":  "Names of activities should give a clear indication of how they are being used. Default names are usually too generic. Please avoid duplicate names. "
},
{
"Variable Str_userinput does not respect the set pattern ^(dt_)?([A-Z]|[a-z])+([0-9])$|out[A-Za-z][A-Za-z0-9_]$":  "Make sure all the variables follow the naming convention. "
}
],
"NoFile":  [
{
"Process does not define a main entry point.":  "Fix the project.json file to point to the entry/main workflow. "
},
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
}
]
}

{
"Task 10.xaml":  [
{
"Variable Str_userinput does not respect the set pattern ^(dt_)?([A-Z]|[a-z])+([0-9])$|out[A-Za-z][A-Za-z0-9_]$":  "Make sure all the variables follow the naming convention. "
}
],
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
},
{
"Process does not define a main entry point.":  "Fix the project.json file to point to the entry/main workflow. "
}
]
}

{
"Task 11.xaml":  [
{
"Flowchart Fruits/Vegetables flowchart is used in a secondary layer in Task 11.":  "Flowchart should only be used in top layer for maintainability and readability reasons. "
},
{
"MessageBox display name is defined many times. Current allowed threshold is 1. Code contains 7.":  "Names of activities should give a clear indication of how they are being used. Default names are usually too generic. Please avoid duplicate names. "
},
{
"Variable Str_userinput does not respect the set pattern ^(dt_)?([A-Z]|[a-z])+([0-9])$|out[A-Za-z][A-Za-z0-9_]$":  "Make sure all the variables follow the naming convention. "
}
],
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
},
{
"Process does not define a main entry point.":  "Fix the project.json file to point to the entry/main workflow. "
}
]
}

{
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
}
]
}

{
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
}
]
}

{
"NoFile":  [
{
"Your organization requires your project to have an Automation Hub URL defined.":  "Use "Project Settings" to add the missing information. "
}
]
}

@shakeelabdull
Task -6
Changes verified.(update the tracker with the pull request (PR) number in the respective tasks in Excel)
Task -10
Code verified.
Task -11
Code verified.


⚙Tech Debt: Allow all props to be overridable

The Problem
Right now, some props are overridable, and also allow bringing your own store (BYOS), while some are not. This brings:

Inconsistency
e..g. while you have an open prop, you may have extra props for pressed, such as defaultPressed and onPressedChange

Prop bloat
For each overridable prop, you need two extra props

Hard to maintain
Each time you have to add an overridable prop, you need to add a lot of logic to it. An example taken from checkbox/types.ts:

	defaultChecked?: boolean | 'indeterminate';
	checked?: Writable<boolean | 'indeterminate'>;
	onCheckedChange?: ChangeFn<boolean | 'indeterminate'>;

And then checkbox/create.ts:
const checkedWritable = withDefaults.checked ?? writable(withDefaults.defaultChecked);
const checked = overridable(checkedWritable, withDefaults?.onCheckedChange);

Proposed solution
We flatten the props to a single one. It will accept a store, or a static value. If it's a static value, it'll behave like defaultValue does now. Otherwise, it'll function as BYOS. To bring in the onValueChange functionality, you need only import our overridable function:
	import { createToggle, melt, overridable } from '$lib/index.js';

	const {
		elements: { root },
	} = createToggle({
		pressed: overridable(false, ({ curr, next }) => {
			console.log('pressed', curr, next);
			return next;
		}),
		// or pressed: writable(false),
		// or pressed: false,
	});

The typings are much simpler:
	pressed?: WritableProp<boolean>;

And consuming said prop, is also easier:
	const pressed = parseProp(withDefaults.pressed);

With this, it'll be much easier to add overridable support and BYOS to all props.
Pros

Consistency
Cleaner internals
More flexibility for the user

Cons

Less intuitive
Whereas currently, defaultValue and onValueChange are quite clear, and value has TS errors if you try and pass in a non-store value to it, this would require some previous knowledge to use efficiently.

Also, some people may think you can do this:
<script>
  let open = false
  const { } = createDialog({ open })
</script>

<button on:click={() => open = true}>open</button>

Which won't alter dialog state. This could be a problem.
Other ideas
One potential con of this, is the doubt as to when it's wise to use overridable, as sometimes it does not make sense, since we don't modify the option internally. We can create a ReadableProp type which disallows overridables for this scenario.
Thoughts?

I feel like the overridable mechanism is pretty elegant. Right now, I understand that it would be a big lift to just add overridable to everything in the short-term and you run the risk of people forgetting to add them in the long-term if you keep it the way it is, but it's also already got a pretty friendly API in my opinion.
One thought I have is that maybe melt can expose a modified version (or maybe even the existing version) of the overridable function that accepts a writable as a first param and a ChangeFn as a second param. Basically the same API that exists now, but remove the onus from melt and add it to the consumer.

My biggest concern with this proposal atm is that we'd be intentionally removing the distinction between the reactive bits and the non-reactive bits. I can't recall ever seeing an API design where a prop prefixed with default is reactive once an instance has been created with it. The users that expect modifying the defaultValue after instantiation will result in some form of reactivity are users whom the flattening of this will confuse 100% more.
I can appreciate the idea of being able to pass in options as stores. If we were to do so I think moving options into a separate object to add separation between the values would make this more intuitive:
type DialogProps = {
	defaultOpen: boolean;
	open: Writable<boolean>;
	onOpenChange: ChangeFn<boolean>
	options: {
		preventScroll: boolean | Writable<boolean>
		// ...
	}
}

With the flattening of all of these, it isn't obvious what Melt may possibly change, whereas right now I can easily know by looking at what props have a change function associated with them.
My current thoughts (subject to change with more time thinking about this) are exposing the overridable is more difficult to explain and more complex than the equivalent open onOpenChange which is self-describing via name/types.

My biggest concern with this proposal atm is that we'd be intentionally removing the distinction between the reactive bits and the non-reactive bits.

Options will have a Readable type while state will be Writable. You can tell if it’s reactive by looking at the type.

My biggest concern with this proposal atm is that we'd be intentionally removing the distinction between the reactive bits and the non-reactive bits.

Options will have a Readable type while state will be Writable. You can tell if it’s reactive by looking at the type.

Readable is still reactive, e.g. if you pass down a store, but modify that store from the outside, that works.
I think the concern comes from removing defaultValue


/System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python: No module named spyder_kernels

Issue Report Checklist

[x] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
What steps reproduce the problem?

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

If you want to use your system Python to run code (really not advisable because you shouldn't touch your system Python at all), you need to install spyder-kernels on it.
Also, please read our guide
https://github.com/spyder-ide/spyder/wiki/Working-with-packages-and-environments-in-Spyder
to understand how to do that.


Update index.md

@j-martens : Thanks for your contribution! The author, @xiaoharper, has been notified to review your proposed change.


Feat/update dot com domain

This is a sanitised version of the feat/update-dot-com-domain branch.

LGTM, but the last commit message is very confusing. Because below 2.7.9 doesn't fall back to getstream.io, it als uses the .com domain but it connects using the OpenSSL libs.

All tests passing indicates that stuff is still working with the new domain BTW.

Yeah that is lame @JelteF - I'll reword the commit message.


Enhance primitive object display in the frontend

For now we use basic JSON serialization and code highlight.
Log lists / dict should be trimmed to avoid painful scrolling.
          > Could we store a plotted representation of the series ? The markdow layout will be bad especially for large series. [Pandas offers this](https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.Series.plot.html#pandas-series-plot) with a default matplotlib backend (which is supported by the frontend).

I think its hard to find a generic plot which can represent all sort of series, while remaining easy to understand.
Maybe we can just display a sample of the series when its too long ? As done by pandas in python (0, 1, 2, [...], 3, 4).
@rouk1 is there the same problem on list-primitive type?
@MarieS-WiMLDS @sylvaincom what do you think?
Keep in mind that, as for python list, the user can put whatever he wants in his series (str, number, str & number etc).
Originally posted by @thomass-dev in https://github.com/probabl-ai/skore/issues/378#issuecomment-2371250928

Solution suggestion @anasstarfaoui @rouk1
Primitive list:

Show as a table with a limited height. The user can use more height by dragging the component vertically.

Series:

Use the default plotting function of pandas.
The user can also switch to a table view like primitive lists.

Primitive dictionary:

use disclosure buttons to show/hide dictionary values. Use Option or Alt to recursively show/hide values.

This problem lacks proper framing, though the pain point remains valid.
Pausing until we have more feedback about it.


Ts proto integration does not support wrapper types

Hi,
Firstly great work on these libraries. I'm working on a wrapper of sorts myself. Basically I find the protobuf format fustratingly lacking - seriously, no ability to define required types?? - so have wrapped it with io-ts decoders and encoders and send all messages using the Struct and ListValue protobuf types - ie. JSON. This means I lose some of the GRPC tooling nice-ness using utils like BloomRPC in that all messages are Structs or ListValues, but within VS Code at least my clients and server imps are dealing with types based on the io-ts defined types - that is, with all the allowed and powerful constraints of io-ts, not handicapped by Google's half-way house binary protocol!
My one real quirk with nice-grpc is the encoding/decoding step, which doesn't seem to support wrapper types like the other integrations. Because I'm exclusively using Struct and ListValue, this means I need to do the wrap/unwrap explicitly, whereas before the grpc-js integration for example just handled it.
Here's an example of how I wrap methods where I have JSON in, JSON out .....:
export type Transport = (request: any, options?: CallOptions) => Promise<any>;

export type Server = (request: any, context: CallContext) => Promise<any>;

export type StructTransport = (
  request: DeepPartial<Struct>,
  options?: CallOptions
) => Promise<Struct>;

export type StructServer = (
  request: Struct,
  context: CallContext
) => Promise<Struct>;

export const wrapStructTransport: (transport: StructTransport) => Transport =
  (transport) => (request, options) =>
    transport(Struct.wrap(request), options).then((res) => Struct.unwrap(res));

export const makeStructServer: (server: Server) => StructServer =
  (server) => (request, context) =>
    server(Struct.unwrap(request), context).then((res) => Struct.wrap(res));

Ideally I'd like not to do this at all and just feed in JSON and/or a list, or handle JSON and/or a list out, but that would require nice-grpc to do this step for me, which I believe the grpc-js integration does for example via these encode/decode methods:
https://github.com/stephenh/ts-proto/blob/main/src/encode.ts
I'm guessing there was probably a good reason it wasn't done this way and can workaround the current solution, but this tweak would definitely make nice-grpc even nicer, IMO! :)

Hey,
Yep, this would be nice to have. Should not be hard to implement it in ts-proto, reusing these generateEncoder  and generateDecoder helpers.


Switching code that can use FunctionOpInterface instead of func::FuncOp to use it.

There's lots of tech debt around func.func, it turns out. As many uses of func (besides creation) have been switched to the FunctionOpInterface as a first step toward support non-func dialects. These changes will also allow more passes to correctly operate on initializers and future dispatch export ops that carry more information than func.func allows. Codegen is welcome to keep using func where it wants as it's more aligned with upstream than the rest of the compiler but there was a lot of unnecessary coupling to func that predated the existence of the FunctionOpInterface/CallOpInterface this cleans up.
There's a few places that still rely on func that don't really need it but they aren't trivial to switch and the hope is that the bulk of the cleanup here (passes, basic walks/iteration, etc) will make them easier to burn down now that they are the exception rather than the rule.
Progress on #16187.

Nice to see I'm not alone in disliking --pass-pipeline="builtin.module(func.func(... in tests :P

oh I didn't notice you commented about it too, yeah I think it's also a problem when trying to run one-off passes outside of tests (scripting/debugging). I bet if we go fix a bunch of passes upstream to use the interface support gets added pretty soon after :)

contributions to make upstream better very welcome :)


Spring Gremlin - Resolve day-1 experience related bugs - gremlin

Bug 6319667: CosmosDB + Gremlin / Spring Data quickstart: java.lang.NoClassDefFoundError:
https://msazure.visualstudio.com/Unified Platform KPIs/_workitems/edit/6319667
Bug 6319549: CosmosDB + Gremlin / Spring Data quickstart: unit tests are failing
https://msazure.visualstudio.com/Unified Platform KPIs/_workitems/edit/6319549
Bug 6319536: CosmosDB + Gremlin / Spring Data quickstart: step order
https://msazure.visualstudio.com/Unified Platform KPIs/_workitems/edit/6319536

Gremlin is abandoned, we don't support Gremlin anymore. #21522


Error when launching docker run --gpus all

System Info

Information

[X] Docker
[ ] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction
I launch:
model=meta-llama/Llama-2-7b-chat-hf
volume=$PWD/data
docker run --gpus all --shm-size 1g -p 8080:80 -v $volume:/data ghcr.io/huggingface/text-generation-inference:1.0.1 --model-id $model
and I have this error
docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]].
ERRO[0000] error waiting for container:

Nvidia Container Toolkit installed
nvidia-ctk --version
NVIDIA Container Toolkit CLI version 1.13.5
nvidia-smi

Expected behavior
No error

You need nvidia-docker : https://github.com/NVIDIA/nvidia-docker.


fix(multi-truncation): use pipe for multiline truncation

Add multiline truncation pipe

@SMahil snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1772-fabric8-planner.int.rdu2c.fabric8.io

@SMahil snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1772-fabric8-planner.int.rdu2c.fabric8.io

@SMahil snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1772-fabric8-planner.int.rdu2c.fabric8.io

UI of the current iteration progress bar is distorted.

@SMahil We also need the tooltip for parent iteration path.

@SMahil there are also some odd things going on with a Card on the Board View regarding truncation - not sure if you were looking at that as part of this fix:
Unselected Card:

Selected Card:

@vikram-raj tooltip on parent iteration path wasn't there earlier. Do you want me to add it?

@SMahil Yes, we need tooltip.
https://redhat.invisionapp.com/share/YPB0J2NGB#/screens/219918404

@SMahil snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1772-fabric8-planner.int.rdu2c.fabric8.io

@SMahil Add iteration start and end date to the iteration. and then check UI of progress bar will break.

@mindreeper2420 with iteration start and date progress bar is breaking as we don't have enough space to accomodate the dates and completion count.
Do you have any idea on it?

@SMahil snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1772-fabric8-planner.int.rdu2c.fabric8.io

@SMahil snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1772-fabric8-planner.int.rdu2c.fabric8.io

@SMahil left-truncate not applied as expected.

@vikram-raj I can't reproduce left truncation issue

@SMahil snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1772-fabric8-planner.int.rdu2c.fabric8.io

@SMahil snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1772-fabric8-planner.int.rdu2c.fabric8.io

@SMahil snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1772-fabric8-planner.int.rdu2c.fabric8.io

@SMahil I'm seeing a weird instance on prod-preview/production where when I click and drag a card to a new column, the truncation is lost. This does not occur on your branch here. Did you fix that with this branch?

@mindreeper2420 I fixed this issue but on selection of card we have a little jump as border width changes from 1 to 2

@SMahil ok - that jump is fine for now. I can take care of those little things as part of the big UX CSS walkthrough

@SMahil snapshot fabric8-ui is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-1772-fabric8-planner.int.rdu2c.fabric8.io


Layout and visual refinement

This branch is a companion to #2413 typography uplift design work.
Full canvas layout, fixed content width
This sets the navigation and grid layout to be full-width, while setting the max-width of page content to the prose width of 712px, occupying the free space in the center of the viewport between the navigation and table of contents:

Default docs page layout

For layouts using the landing page layout, I measured the maximum width the content could previously occupy prior to the typography and this layout branch change (with the previous outer container max-width on the Page grid), and came up with a value of 896px:

Test Analytics landing page example

Details and refinements
Hyperlink interaction design refinement
Replace svg asset for external link with built-in unicode glyph in font set. Set a fainter text-decoration colour, which becomes fully opaque on hover:
https://github.com/buildkite/docs/assets/677025/be6f99d1-c039-4848-bb14-d032101dacc5
Heading anchor interaction design
New interaction design for anchors:
https://github.com/buildkite/docs/assets/677025/d87bc97d-b891-4e7d-b0ec-9baef3499dbf
Refined table design

Refined Callout design
The previous troubleshooting callout was not accessible on white.

Specify a background and foreground colour with each callout type, this allows for the note to be more scannable as a callout, with a more accessible text colour.
We no longer render the corresponding emoji for the callout in the body; instead we use a mono icon from the Hero Icons library that corresponds to the type of callout.
Typesetting refinements so that the text is always indented to the left from the icon.
One line callouts no longer appear as if they are missing a title

Redesigned responsive-image styling
Rather than padding and a grey border, images are now full-bleed, have a rounded radius applied, and a subtle shadow/outline:

I see this is in draft so I might be jumping the gun, but I think this is looking great! Yay the new callouts and tables! The only thing that I'm not sure about is the inline code background color. It might be a me thing, but I find it a lot harder to read than the existing style.

@mbelton-buildkite Cheers! Feedback always welcome as I gear up to get this ready for review (Wanted to write a more thorough PR description).
We can certainly tweak the code background colour, would you say the background colour is a little too dark and needs to be fainter against the code text, or the background itself needs to be darker against the white background?
I’ve had a quick go darkening and saturating the element to get it close to #eeeeee but saturated with our navy colour temperature (#e9e9fa), does this look better/worse in regards to legibility for you? (e.g. does code text need to be darker)

would you say the background colour is a little too dark and needs to be fainter against the code text, or the background itself needs to be darker against the white background?
I’ve had a quick go darkening and saturating the element to get it close to #eeeeee but saturated with our navy colour temperature (#e9e9fa), does this look better/worse in regards to legibility for you?

I should have been more specific, sorry! I think it was mainly the background against the white. I find the new version much easy to read 😊

I am loving these changes @BrettJay.

Did something change with the emojicom rendering? I'm seeing it double up when I navigate back to a page on the preview:
https://github.com/buildkite/docs/assets/119824349/0bb614a8-7f60-4265-9259-6ef90da616cd
(Or maybe this is to do with the static preview, @dannymidnight?)

Did something change with the emojicom rendering? I'm seeing it double up when I navigate back to a page on the preview:

Nope, I've seen this before. It's related to the Turbo.

Nope, I've seen this before. It's related to the Turbo.
I should pop something in our backlog to address it.

I couldn't reproduce the issue on the live site 🤷🏻♂


counts-metapaths-to endpoint: support metanodes filter

closes https://github.com/greenelab/hetmech-backend/issues/58
Should enable queries like:
https://search-api.het.io/v1/count-metapaths-to/2/?metanodes=G,MF

Frontend now uses the metanodes filter option as of https://github.com/greenelab/hetmech-frontend/pull/152


Bug in apostrophe encoding

First of all, thank for your great work. I'm using it all the time!
Found a bug in the export of apostrophes to xml, they get encoded as &apos; rather than '
Attaching an image as an example.
Thanks!

Also "&" gets encoded as &amp; instead of &
Thank you so much for the plugin!

Just pushed v52 which should fix this issue. The problem was that the new backend for exporting XML always encodes characters, causing them to be double encoded.
Unfortunately, this means the "Don't format illegal characters" option is no longer functional and has been removed. Apostrophes are no longer encoded either because this. Fortunately, apostrophe encoding is only needed when values are wrapped with single quotes, which is impossible here.


Add support for dot

What do these changes do?
Adds support for both df.dot and series.dot
Related issue number

[x] passes flake8 modin
[x] passes black --check modin
[x] tests added and passing

Great PR @williamma12! We should update the docs to show that this has been added.


feat: add ability to support additional gateway/domain

Description
Adds ability to override and add an additional gateway to the nginx config.
Related Issue
Relates to #98
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Other (security config, docs update, etc)

Checklist before merging

[x] Test, docs, adr added or updated as needed
[x] Contributor Guide Steps followed

👍 is this something we have or should have tests to verify the behavior of?

I'm not sure if we want to explicitly test this based on this comment: #98 (comment)
but will defer to @mjnagel if anything extra is required here. Happy to clarify in the docs that this isn't tested as well if that helps at all.

@catsby / @joelmccoy definitely feel weird advocating for not testing this, but I think that is what I said in the comment 😆. I may have poorly stated it there - I think if there were an easy way to test this in CI I'd be good with adding testing, but made an assumption that the complexity around a new domain/cert might be non-trivial. I mostly don't want us to invest too much time in a feature that is not required by uds-core and uds packages in general - I see that as the primary place to focus uds-k3d development efforts and testing.
Also worth calling out, as-is I don't think we even have tests of the primary domain nginx pattern (uds.dev). We probably should track the need for a test on the nginx config in general as a future issue. If developing that test naturally made it easy to add a test of the custom domain pattern no issue also handling that.

assumption that the complexity around a new domain/cert might be non-trivial

@mjnagel I was hoping that helm had some kind of easy way to check that "given a template and a config, does helm execute to create the result we expect" kind of thing, so testing the generated helm result and not so much the final product e.g. (😉) "does it respond to multiple domains". If we don't have that, or it's not practical, so be it 👍

@catsby ah - makes sense, yeah more of unit test type thing rather than an e2e validation. Definitely could add some helm testing with helm template or other tooling to validate.


loadtxt compat: empty comments

Just a minor compatibility note:
npreadtxt seems to treat empty comment strings (comments="") like comments=None, whereas np.loadtxt raises an exception:
>>> from npreadtxt import _loadtxt
>>> import io
>>> import numpy as np
>>> s = StringIO("1 2 3")
>>> _loadtxt(s, comments="")
array([1., 2., 3.])
>>> s.seek(0)
>>> np.loadtxt(s, comments="")
Traceback (most recent call last)
   ...
ValueError: empty separator

IMO npreadtxt's behavior is more sensible, but it is an incompatibility so adding it to the issue tracker just so it's not lost.

This one is nice:
In [24]: np.loadtxt(StringIO("1\n2"), dtype="S100", comments=[""])
<ipython-input-24-5a394dc7cbe0>:1: UserWarning: loadtxt: Empty input file: "<_io.StringIO object at 0x7fa425ed33a0>"
  np.loadtxt(StringIO("1\n2"), dtype="S100", comments=[""])
Out[24]: array([], dtype='|S100')

but it doesn't really matter :).  And it actually changed to error in current NumPy main...

Lets add a deprecation for this: To disable comments, the user should use comments=None and not comments="".

In [3]: np.loadtxt(['1 "\n1"', "2 2"], comments="")
<ipython-input-3-9841b64304b5>:1: UserWarning: loadtxt: Empty input file: "['1 "\n1"', '2 2']"
  np.loadtxt(['1 "\n1"', "2 2"], comments="")
Out[3]: array([], dtype=float64)

?!

Hahaha, looks like NumPy 1.21.x broke comments="" to just comment out literally everything..

OK. since comments="" seems to have been broken until NumPy 1.22 (and now gives an error), it seems good to just disable it.
Further passing an empty string for delimiter or quote should be an error now.  The only weird thing is that delimiter=None means "any whitespace" while quote=None, and comments=None means that there is no quote/comment character.

an empty comment now raises a nice ValueError as per Ross' addition.


Implement Godot Oculus Mobile plugin

Provides an initial implementation for the Godot Oculus Mobile VR plugin!
The code still needs some cleanups, but is in a state where it can be pushed for additional testing and contributions!
The README has been subsequently updated to provide instructions to setup, build and deploy the Godot Oculus Mobile VR plugin.

Amazing stuff! Thanks man :)


Add more precompiled types

This allows for fast compilation of xtensor-zarr when used with a GDAL or local file system IO handler, with zlib, GZip or Blosc compression (or no compression). It produces a 17M shared library.

We need https://github.com/xtensor-stack/xtensor-io/pull/156 released, that's why tests are failing.

How big is the shared object actually?

20M


issue with installing on RPi3

Hello,
I'm currently trying to install Huginn to a RPi3 that has Ubuntu Mate 17.04.  I am having difficulties at this part:
sudo bundle exec rake production:export --trace
** Invoke production:export (first_time)
** Invoke production:check (first_time)
** Execute production:check
** Execute production:export
** Execute production:stop
Stopping huginn ...
Exporting new services ...
It seems to remain at "Exporting new services" and never seems to complete.  Was wondering if this is a known problem or if I have configured something wrong?  Not really sure how to troubleshoot this.
Many Thanks for any help and advice you can offer.

Did you managed to get this working?
I am building an docker arm image for the RP4, and face the same Problem.
root@7008eecce5c4:/home/huginn/huginn# sudo bundle exec rake production:export
Stopping huginn ...
Exporting new services ...
and this "Exporting new services ..." never ends


Big update

Coverage remained the same at 100.0% when pulling 6b4b080a982edd06a2844723a3aac98e281ea622 on ktutnik:master into 8f88c07169bc096276c3695d5b71ef2abb5283ac on kambojajs:master.


Update market actor

Task summary

Update the market actor to include CronTick and remove HandleExpiredDeals
Specification reference

Market actor

Other information and links

I believe my PR for the Market Actor Tests should take care of this once the PR for Miner Actor gets merged


Use FSharp.Core 6.0.1 instead of 6.0.2, lowest denominator approach for versions

Fixes: #121.
~Just running full CI to see what happens.~ All tests pass just fine. Let's downgrade the lowest supported FSharp.Core.dll version.
Note that we cannot go all the way to 6.0.0, unless we write the taskSeq overload code such that we don't use NoEagerConstraintApplication. This means either marker interfaces, or explicits (i.e., require users to do Task.ofAsync and the like). I'm fine with using this approach though, as it behaves closer to how task behaves.

Will be part of 0.3.1 or 0.4.0. We probably go for 0.4.x though, as technically this is a breaking change.


Support for ipadOS and VoiceOver

Hello
I have tried using this component with multiple different screenreaders, and am very happy with its behavior on FireFox+NVDA, Chrome+JAWS and Android+TalkBack. But on my iPad Gen7 (iPadOS 15.0) I can't get the dropdown to work properly.
When writing on the keyboard, the dropdown opens as expected with the results list, but when I try to navigate the dropdown, it keeps closing.
I have tried navigating both using swipe and explore by touch, but both causes the dropdown to close.
I am using version 2.0.3 in my own project, but am able to replicate on your examples page:
https://alphagov.github.io/accessible-autocomplete/examples/

Maybe because the iPad user agent no longer contains the "iPad" keyword. It's now the same as a mac. In the autocomplete code, there are multiple fix to avoid closing the listbox on iPhone/iPad while using VoiceOver.


Fetching Error on updating

System: macOS Sonoma 14.1
% brew update && brew upgrade && brew cleanup
fatal: couldn't find remote ref refs/heads/master
Error: Fetching /usr/local/Homebrew/Library/Taps/heroku/homebrew-brew failed!
Error: Some taps failed to update!
The following taps can not read their remote branches:
  heroku/brew
This is happening because the remote branch was renamed or deleted.
Reset taps to point to the correct remote branches by running `brew tap --repair`

% brew tap --repair
fatal: couldn't find remote ref refs/heads/master
Error: Failure while executing; `git -C /usr/local/Homebrew/Library/Taps/heroku/homebrew-brew fetch origin` exited with 128.

% heroku --version
heroku/8.7.0 darwin-x64 node-v16.19.0

I also tried brew update-reset but nothing changed.

I also encountered this but got it working after a brew untap heroku/brew && brew tab heroku/brew. Wish I'd backed up the old clone because I can't replicate the error after retapping.

% brew untap heroku/brew
Error: Refusing to untap heroku/brew because it contains the following installed formulae or casks:
heroku
heroku-node

Anyway, brew untap heroku/brew --force && brew tab heroku/brew worked. Thank you.

brew untap heroku/brew --force && brew tab heroku/brew solved the issue.

JFYI, the reason is that they changed their main branch name from master to main

brew untap heroku/brew --force && brew tab heroku/brew solved the issue.

Typo on the second command (/tab/tap/s), should be:
brew untap heroku/brew --force && brew tap heroku/brew

Typo fixed.


Installation - confused

I am confused with the installation instructions. When I run npm install the process will look for package.son in home/pi but further on you suggest that the software should be installed in /opt/ but when I do that, npm install gives an error message

If you clone the repository into /opt then run npm install inside the upnp-playlist-service. You'll need to make she your permissions are correct. Npm ininstallhould download the necessary dependencies into the node-modules folder. You can then start the service. You don't have to install in /opt that is just convention. No reason not to install in your own home folder. I plan to create a deb file for easier installation soon.


Unspecific installation error (windows-10, conda 4.9.2)

Preliminaries

[x] I have followed the latest version of the
installation instructions.
[x] I have checked the troubleshooting page and my problem is either not mentioned there, or the solution given there does not help.
check, does not resolve the issue

Description of error
choco install manimce
Installation aborts with unspecific error:
Execution of C:\ProgramData\chocolatey\lib\manimce\tools\chocolateyinstall.ps1
is not verbose, then aborts with ERROR
Script and folder C:\ProgramData\chocolatey\lib\manimce\tools\
are removed after abortion. Thus checking not possible of script in such folder….
Installation logs

..
    Preparing wheel metadata: finished with status 'error'
ERROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop:     ERROR: Command errored out with exit status 1:
Environment Vars (like PATH) have changed. Close/reopen your shell to
 see the changes (or in powershell/cmd.exe just type `refreshenv`).
The install of manimce was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\manimce\tools\chocolateyinstall.ps1'.
 See log for details.
Chocolatey installed 1/2 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures

manimce (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\manimce\tools\chocolateyinstall.ps1'.
See log for details.

t
Chocolatey v0.10.15
Installing the following packages:
manimce
By installing you accept licenses for the packages.
Progress: Downloading ffmpeg <IP_ADDRESS>01122... 100%
Progress: Downloading manimce 0.2.0... 100%
ffmpeg v<IP_ADDRESS>01122 [Approved]
ffmpeg package files install completed. Performing other installation steps.
The package ffmpeg wants to run 'chocolateyInstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): y
Extracting 64-bit C:\ProgramData\chocolatey\lib\ffmpeg\tools\ffmpeg-release-essentials.7z to C:\ProgramData\chocolatey\lib\ffmpeg\tools...
C:\ProgramData\chocolatey\lib\ffmpeg\tools
Environment Vars (like PATH) have changed. Close/reopen your shell to
see the changes (or in powershell/cmd.exe just type refreshenv).
ShimGen has successfully created a shim for ffmpeg.exe
ShimGen has successfully created a shim for ffplay.exe
ShimGen has successfully created a shim for ffprobe.exe
The install of ffmpeg was successful.
Software installed to 'C:\ProgramData\chocolatey\lib\ffmpeg\tools'
manimce v0.2.0 [Approved]
manimce package files install completed. Performing other installation steps.
The package manimce wants to run 'chocolateyinstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): y
Found python at 'C:\msys64\mingw64\bin\python.exe' using it.
Using python version Python 3.8.3 (default, May 14 2020, 12:19:09)  [GCC 10.1.0 64 bit (AMD64)]
E:\olippuner.local\lib\python3.8\site-packages
C:\tools\Manim
C:\tools\Manim\installInfo.json
Upgrading pip and install Wheel
Looking in links: e:\olippuner\AppData\Local\Temp\tmpvoa6fa4f
Collecting setuptools
Collecting pip
Installing collected packages: setuptools, pip
Successfully installed pip-19.2.3 setuptools-41.2.0
Collecting pip
Downloading https://files.pythonhosted.org/packages/de/47/58b9f3e6f611dfd17fb8bd9ed3e6f93b7ee662fb85bdfee3565e8979ddf7/pip-21.0-py3-none-any.whl (1.5MB)
Collecting wheel
Downloading https://files.pythonhosted.org/packages/65/63/39d04c74222770ed1589c0eaba06c05891801219272420b40311cd60c880/wheel-0.36.2-py2.py3-none-any.whl
Installing collected packages: pip, wheel
Found existing installation: pip 19.2.3
Uninstalling pip-19.2.3:
Successfully uninstalled pip-19.2.3
Successfully installed pip-21.0 wheel-0.36.2
Install Numpy v1.19.3 to avoid problems
Collecting numpy==1.19.3
Downloading numpy-1.19.3.zip (7.3 MB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'error'
ERROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop:     ERROR: Command errored out with exit status 1:
Environment Vars (like PATH) have changed. Close/reopen your shell to
see the changes (or in powershell/cmd.exe just type refreshenv).
The install of manimce was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\manimce\tools\chocolateyinstall.ps1'.
See log for details.
Chocolatey installed 1/2 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures

manimce (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\manimce\tools\chocolateyinstall.ps1'.
See log for details.

Don't know howto further check

FFMPEG
Output of `ffmpeg -version`:
(base) C:\WINDOWS\system32>ffmpeg -version
ffmpeg version 4.2.3 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 9.3.1 (GCC) 20200523

Additional comments
as mentioned above, I try to use easy install with
choco install manimce
Installation aborts with unspecific error
Execution of C:\ProgramData\chocolatey\lib\manimce\tools\chocolateyinstall.ps1
is not verbose, then aborts with ERROR
Script and folder C:\ProgramData\chocolatey\lib\manimce\tools\
are removed after abortion. Thus checking not possible of script in such folder….

Hey why does msys2 python comes up here? That's the problem...
Msys2-mingw64 python is compiled with gcc and normally compiled things won't work there. Did you do it on purpose?
Or did you mess up your path variable?

Hey why does msys2 python comes up here? That's the problem...
Msys2-mingw64 python is compiled with gcc and normally compiled things won't work there. Did you do it on purpose?
Or did you mess up your path variable?

I think this issue is fixed closing.


Merge resources/projects and resources/projectPortTesting

Which area this feature is related to?

/area test-automation
Which functionality do you think we should add?

Upon testing we use two different resource dirs projects and projectPortTesting. Among several projects we have inside these projects, there are a few duplicates. To prevent that, we have to merge the two dirs and use only one dir to import projects needed for unit testing.
A good workaround would be to move all contents from projectPortTesting to projects. As the port detection unit tests are using right now the projectPortTesting dir for testing, we need to update the path in component_recognizer_test.go.

closing in favor of https://github.com/devfile/api/issues/1166


”Săuca”, ”Becheni”, ”Cean”, ”Chisău”, ”Silvaș” are listed in the drop-down menu

Description:
When user writes ”Săuca”, ”Becheni”, ”Cean”, ”Chisău”, ”Silvaș” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Săuca"

Expected results
The location appears in the drop-down menu as "Sat Săuca, SATU MARE (Săuca)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Becheni"

Expected results
The location appears in the drop-down menu as "Sat Becheni, SATU MARE (Săuca)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Cean"

Expected results
The location appears in the drop-down menu as "Sat Cean, SATU MARE (Săuca)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Chisău"

Expected results
The location appears in the drop-down menu as "Sat Chisău, SATU MARE (Săuca)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Write in the search bar "Silvaș"

Expected results
The location appears in the drop-down menu as "Sat Silvaș, SATU MARE (Săuca)".