fix: restoring cache for pyproject.toml

Let's wait for #94 with merging, then we can release two fixes at once.

Closes #93

LGTM as a quick fix. In general, we should make sure, though, that setup-pixi works out of the box if only a pyproject.toml is present without specifying manifest-path.
@nichmor can you bump the patch version in package.json? Then the release pipeline will be triggered automatically once merged.

Hey!
Yeah, totally. I just wanted to make the scope of this PR very small and later maybe work on automatic discovery of pyproject manifest.
Let me bump the patch version

bumped.
@pavelzw can I merge it?

let's wait for CI and then we can merge it 👍🏻


chore: percy visual regression tests

Checklist

[x] Include a description of your pull request and instructions for the reviewer to verify your work.
[x] Link to the issue if this PR is issue-specific.
[ ] Create/update the corresponding story if this includes a UI component.
[ ] Create/update documentation. If not included, tell us why.
[ ] List the environments / browsers in which you tested your changes.
[ ] Tests, linting, or other required checks are passing.
[x] PR has an informative and human-readable title

PR titles are used to generate the change log in releases; good ones make that easier to scan.
PRs will be broadly categorized in the change log, but for even easier scanning, consider prefixing with a component name or other useful categorization, e.g., "BaseButton: fix layout bug", or "Storybook: Update dependencies".

[x] PR has been tagged with a SemVer label and a general category label, or skip-changelog.

These tags are used to do the aforementioned broad categorization in the change log and determine what the next release's version number should be.
Release Drafter will attempt to do the category labeling for you! Please double-check its work.

Description
Completes https://github.com/nasa-jpl/www/issues/188

Adds percy visual regression tests to our CI.
Check /apps/vue-storybook/.percy.yml to see a list of included/excluded stories. We may continue to refine this depending on how our quota usage goes.

Instructions to test

pnpm install
make vue-storybook-build
pnpm --filter @explorer-1/vue-storybook percy:dry-run

Link to percy tests: https://percy.io/e5a03e0a/explorer-1/builds/35608683
Note: this generated 1434 snapshots and used ~8% of our quota. Seems a bit high, so I might remove firefox snapshots since Scott and I regularly use the site in Firefox. I think we need to keep Safari snapshots, though. This should reduce snapshots by a third.

Note, I canceled the last test action to not needlessly use up our quota.


chore(main): release 0.2.0

:robot: I have created a release beep boop
0.2.0 (2022-12-26)
Features

analysis: AnalysisView (7f02172)
device: better DeviceView (2a8ff3b)

Bug Fixes

deps: update kotlin monorepo to v1.8.0 (a173796)

Reverts

Revert "ci: release-as: 0.1.0" (e8b5473)

Continuous Integration

build: build web for every push (9765b6b)
build: no web (dcbfeb5)

Miscellaneous Chores

deps: upgrade (612398c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/CCXXXI/ecg_monitor/releases/tag/v0.2.0 :sunflower:


Improve reliability when switching between models

Sometimes when I switch between models, the bot becomes unresponsive for a message or two. I think this is from messaging it before the new model has loaded in. We check for the server to be ready by listening to its stdout. I bet there is a more reliable way like pinging the /health endpoint (didn't exist when we started this project).

too annoying, fixing. I think this regression emerged with the llama.cpp version on the TestFlight.


RFC: upstreaming this implementation to scipy

SciPy is trying to remove all Fortran code: see https://github.com/scipy/scipy/issues/18566
This repo looks like a young, but very nicely maintained and thoroughly tested implementation of the L-BFGS-B algorithm and is far more understandable than the F77 goto mess we currently have, so my question is: would you be open to contribute your code to SciPy?
If yes, we would need to know if you have detailed benchmarks against Scipy's implementation.
CC @ilayn

Hi @dschmitz89,
First issue and what an issue! Contributing to scipy would be a real honor! Thank you for your interest.
Indeed, the repo is young and as you can see in the history, I'm still correcting a lot of things at the moment. The original code is pretty damn good, and it's not easy to reproduce the behavior in fine detail. To be perfectly honest, I've relied heavily on the work of Jacob Williams (lbfgsb in F90), who had the wisdom to get rid of those famous F77 gotos. F90 is much easier to digest.
By the way, he did the same for slsqp, which must also be on your list (https://github.com/scipy/scipy/blob/main/scipy/optimize/slsqp/slsqp_optmz.f)? Maybe I'll port it to Python in a few months, as I'll be using this solver in my work.
Coming back to this LBFGSB implementation, I think you know it well, but it's more memory- and computation-intensive than Fortran code. But in my opinion, this will always be negligible compared with the calculation of the objective function and its gradient (at least in most problems).
 In fact, a lot of unit tests are missing -> I've got a small (long) list of things to test...
Refine the documentation, and in particular review the equations and replace all the description that hang around here and there.
Clean up comments and check references
Implement various linesearch algo's and test them -> most of them are already in scipy, great!
Explain and document the logging usage
Document stop criteria and how to use them
... some other cool stuff

It should not take too long.
As far as benchmarking with the current scipy code is concerned, that's a work in progress. I've already implemented a number of functions for this and done a lot of 2D testing on problems with several thousand parameters as part of my work (see pyrtid which is also under construction).
Cheers
Antoine

This is wonderful work. Congratulations. If it is any better, I already ported this to C and indeed I have been going through a lot of versions in C. However many are in GPL license hence I did not have a chance to get any insights.
But, since I am slightly going mental from all these F77 code, this testing scheme that you have is golden ticket for us. Because the correctness is the only way to debug fortran code and if you are willing to collaborate, I can do the extremely boring part of the translation (which I already did almost completely) and we can use your testing suite to beat the shit out of the code.
In fact, if you think your translation is better and uses modern things like matrix multiplications (I myself can't believe I am calling matmul modern, I know) and NumPy stuff I can easily convert it to C and we can directly benefit from the low-level stuff.

One of the major problems with C code you see online is that they are the cleanedup f2c translations which is not portable enough to be used and carries over all the memory bugs and segfault behavior. That's why I went through hell to translate all our F77 code. Typically to unroll gotos is quite alright if the authors are not nasty coders. But some code is just insanity hence I leave a bit of those if it becomes a mess of code repetition.


ROX-12976: fix for 3.71.x: cherry-pick finish-release to avoid auto-trigger on release publish

Description
Cherry-picking the finish-release workflows from the master branch.
This is to remove the trigger on a new release, which previously triggered the finish-release workflow from the release branch after the release engineer had created a new release. Though having no side effects, the Slack message it did send lead to some confusion.
The variables workflow may not be strictly necessary to be updated, but I did it as it is a direct dependency of the finish-release workflow. The common.sh and other scripts are taken from master, so we don't need to update them to the release branch.
Checklist

[ ] Investigated and inspected CI test results
~[ ] Unit test and regression tests added~
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

If any of these don't apply, please comment below.
Testing Performed
No testing required.

Shouldn't we just delete the file?

Would also work, I think updating the workflow is more future facing 😄

I thought the idea was to never execute this workflow from release branch :thinking:

I thought the idea was to never execute this workflow from release branch 🤔

The idea is only to remove the auto trigger.


add ghetto surgery real

About the PR
taken from the tg wiki mostly:

welder lighter matches screwdriver wirecutter esword armblade etc can be used
welder lighter esword need to be turned on
lasers can be used, it uses a shot
advanced/laser versions are faster

some changes:

no SharpComponent automatically being a shitty scalpel/bone saw, cbf
cleaver is a good bone saw instead of shit, its meant to cut off limbs
esword can very slowly cauterize, you have to be careful not to cut so its slow
spoons can remove eyes slower than fork :trollface:

tool speeds can be examined by clicking scalpel button in examine
Why / Balance
tider vox conversion society in maints
Technical details
added Tweezers and Tending tool components to have different speeds for ghetto tools
pen can tend wounds but not remove organs, opposite for fork
this prs patch can be used on any fork, licensed CC0-1.0 so do whatever you want
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes
:trollface:
matchstick commit will be prd upstream as well so no conflicts
Changelog
:cl:

add: Ghetto surgery is now possible, read the TG wiki!

Summary by CodeRabbit
Summary by CodeRabbit

New Features

Introduced the MatchstickSystem for enhanced matchstick interactions.
Added MatchstickComponent to manage matchstick states and behaviors.
Implemented new surgical tools and components, including Cautery, Scalpel, and BoneSaw, across various entities.
Added a SurgeryToolConditionsSystem to enforce usage conditions for surgical tools.
Expanded surgical steps with new entities for enhanced gameplay mechanics.
Introduced new components for existing entities, enhancing their functionalities related to surgery and tools.
Added new entities like TweezersComponent and TendingComponent for surgical operations.

Bug Fixes

Improved interaction logic for igniting matchsticks only when unlit.

Documentation

Updated localization strings for new surgical tools and usage instructions.

instamerge in 3

One thing of note with this PR, with so many things being able to trigger the surgery menu, I'll probably have to look at adding drapes (or bedsheets as ghetto alternatives) and removing the ability for the tools themselves to bring up the surgery menu.


org.testng.internal.Version should be up-to-date

org.testng.internal.Version.VERSION is 6.8.9beta since TestNG 6.8.8 release and was 6.8.2beta... before.
The version value should be updated with TestNG release like it's written in CHECKLIST.
I propose to make it with maven and its resources filtering feature.
Eclipse will generate the file with the appropriate m2e plugin.

Rebased and working on Travis! \o/


Allow for non standard cosmologies, and improve cosmological time integration

We want to include non-standard cosmological models that have time-dependent dark energy equation of state. This pull request implements w0,wa parameterization of the DE EOS. It also incorporates a Runge-Kutta integrator to improve the integration of the physical timestep with scale factor, pre-computes the offset in physical time for z<\infty ICs, and writes the expansion history to a file. We also allow for non-zero radiation energy density.  I have checked the expansion history agrees to within ~0.1% with independent calculations.

The cpp-format test fails on the following code block in global/global.cpp
// NOLINTNEXTLINE(cert-err58-cpp)
// NOLINTNEXTLINE(*)
const std::set<std::string> optionalParams = { "flag_delta","ddelta_dt","n_delta","Lz","Lx","phi","theta","delta","nzr","nxr","H0","Omega_M","Omega_L","Omega_R","Omega_K","w0","wa","Init_redshift","End_redshift", "tile_length", "n_proc_x", "n_proc_y", "n_proc_z" }; // NOLINT

This line already had a NOLINTNEXTLINE(), but I could not get that to work no matter how I formatted the line. I have tried various iterations of NOLINTBEGIN/NOLINTEND, NOLINT, NOLINTNEXTLINE, etc.  So if you can recommend how to get around the clang formatting issue, that would be much appreciated.

After a lot of effort and help from Bruno, the version 1f05b8d reproduces well the original cosmological hydro sims using the same flags. The salient issue that may need discussion is the last commit that undoes changes to PPMP_cuda.cu, where ifdef CTU had been changed to ifndef VL. The last commit undoes this change, since it was affecting the cosmological hydro integration, and these portions of the PPMP scheme now only apply to CTU again (not VL or SIMPLE). @evaneschneider do you know why this change was made?  Is it OK to keep this off whenever SIMPLE is used, or should I add an ifndef COSMOLOGY and revert the changes back to ifndef VL?

@brantr I do think this needs some discussion. Perhaps part of the problem is that I don't really understand what SIMPLE should do. As I've mentioned a couple times, I think SIMPLE is numerically unstable in more than 1D, since I thought it was just the first half of CTU, and removing the characteristic projections and time evolution of the interface states makes it numerically unstable in 1D as well, so I probably thought I was helping when I noticed that step had been eliminated. (I do remember showing some KH tests in the CAAR slack that demonstrated instabilities that went away when the characteristic projection step was turned back on.) That said, if you all have worked out that simple works without those steps, we can (and perhaps should) get rid of all of that code (and I think we should be consistent here, either we have it in all the reconstructions, or we have it in none). I think resolving this question is best done through a conversation, since it seems like maybe you all did some development work in creating simple that I'm unaware of / do not understand.

Let's discuss offline, but then when we resolve we can post back here for prosperity.

When you get a chance @brantr can you re-run clang-format? I was going to try to investigate the linting error but right now there are a bunch of violations in a bunch of files.

@brantr Are you sure you're running the right version of clang-format? There are still a bunch of errors in a number of files, but a lot of them seem to be simple things (like not removing end spaces or not getting equalities in line) that should just be taken care of when you run the formatting, so I don't really understand why it's not working.

BTW, other than the formatting errors, everything seems okay on this branch except the new cosmology system test, which makes sense. Given that I assume this version has been verified for some forms of correctness, I'm happy to merge this and then rerun the system test and swap out the test data.

pre-commit.ci autofix

Oh wow! it looks like it precomit worked! That's extremely encouraging!

Regarding formatting, thanks to @mabruzzo's PR #404 we now have the ability to fix formatting errors on PRs, so I went ahead and applied those changes.


Brackets complete

I finished a gopls-based lapce plugin for go, but in the process of using it, I found that bracket completion (typing pairs of brackets at once and moving the input cursor into the middle of the brackets) is a big problem, how should I solve it?

Hello,
I can't seem to reproduce the issue. What exactly is the problem for you? Also, what is your OS, and Lapce version?
For your information, there is already another gopls-based lapce plugin for go :)

Hello.
Here's what I mean by the description,the image above is from lapce,the image below is from vscode,obviously, having the bracket-completion feature gives us developers a better experience,so I hope you can answer my questions about this.

Okay, I see what you mean, you'd like Lapce to move in between the brackets automatically. This is not something on the LSP side but on Lapce's side, and should not be too difficult to implement.
@MinusGix I believe this could be labeled as "Good first issue", as it's quite literally moving the cursor by one on the right.

Following your link, I looked at your plugin code and it was very enlightening, but I still strongly recommend that you use Golang's own env command, as there are no relevant definitions for GOPATH and GOBIN in my computer's environment variables（PATH）.
Yes, there is definitely work to do on that part, but I have not looked into it yet. I've been experimenting with the Plugin API design (which should be coming soon as it's the main priority right now). Once the plugin API is out, the current functions will be obsolete and most likely will break.

Do note that executing commands straight from your plugin will not work as the runtime of each plugin is confined to its own folder.

Do note that executing commands straight from your plugin will not work as the runtime of each plugin is confined to its own folder.

I was already aware of this problem during the quiz phase, so I strongly suggest that such features (LSP missing etc...) can be Add Command Palette, similar to VScode.

Hopefully it is built in as a plug-in feature with event listening and presentation by the editor.I think this is a better solution.

I was already aware of this problem during the quiz phase, so I strongly suggest that such features (LSP missing etc...) can be Add Command Palette, similar to VScode.

This depends on plugin API which is still non-existent

I was already aware of this problem during the quiz phase, so I strongly suggest that such features (LSP missing etc...) can be Add Command Palette, similar to VScode.

This is one of the features mentioned during the initial brainstorm of the API yes

If you are interested in my ideas, I can implement them as my immediate work

If I want to contribute to this project, which branch should I start from?

If I want to contribute to this project, which branch should I start from?

If you're referring to Lapce, then the master branch.

If you are interested in my ideas, I can implement them as my immediate work

You have to wait for plugin API

If I want to contribute to this project, which branch should I start from?

master

Do you have a good idea for the plugin-api or have you implemented it so far?

Do you have a good idea for the plugin-api or have you implemented it so far?

It's being actively worked on as part of this PR https://github.com/lapce/lapce/pull/893

Is the bracket-completion ("Good First Issue" part ) still non-existent?
I would love to implement .
Which file should I start with ?
@nheuillet

@ki9gpin It's already been implemented actually! The cursors automatically skips to the middle of the brackets and other symbols - [], (), etc.
@panekj This issue can be closed I believe


copr: Switch to use nanosecs for Duration

Signed-off-by: Dian Luo<EMAIL_ADDRESS>
What have you changed?

Removed the fsp in current Duration implementation.
Changed to use the same memory format for the Duration.

What is the type of the changes?

Engineering (engineering change which doesn't change any feature or fix any issue)

How is the PR tested?

Unit test

/run-all-tests

/run-all-tests

Still ICE...

/release

/run-test

/run-all-tests

/run-all-tests

/test

/run-tests

/test

/run-tests

/run-all-tests

/run-tests

/run-all-test

/merge

/run-all-tests

/run-all-tests

/merge

/merge

/merge

/mergr

/merge


util/addon: find both by owner and impl

This allows to have multiple addons of different types with the same
owner.

Ref discussion in https://github.com/swaywm/wlroots/pull/3101#issuecomment-896632559


fix: new llmq-qvvec-sync syntax in <IP_ADDRESS>-rc4

Issue being fixed or feature implemented
Dash containers were failing with the following error after updating from <IP_ADDRESS>-rc3 to -rc4:
Error: Invalid format in -llmq-qvvec-sync: llmq_100_67

What was done?
Use new syntax for this setting
How Has This Been Tested?
Tested on Palinka
Breaking Changes
None
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[ ] I have assigned this pull request to a milestone

Changed the base to master, not sure where you want to change the core docker image version? This is usually done in dash-network-configs


⚠ PrivateHD has degraded performance

In 1253359, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1936 ms

Resolved: PrivateHD performance has improved in 330b29d.


feat(api): Add the ability to include commit authors and PR references to default-changelog-notes

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Context:
Fixes #1716  🦕
This PR is a follow-up to #1717
We can probably close it as my PR is based off it.
Changes:

Utilise the commitPartial attribute from BaseStrategyOptions
Add commitPartialPath to the manifest config and friends
Commit authors and PR reference links can be added to the commit entries for a release by providing a custom .release-please-commit-partial.hbs file.

You can find the template file here (we default to this template when no commitPartialPath is provided)

TESTING
I have done testing on this dummy repo.
https://github.com/jamszh/test-release-please
Here is an example auto-release PR

This would be very nice to have!

Sorry for the late review, but this is looking great!
One question -- is this opt-in? IMO, all the new features should not change existing behavior.

Yep.
See: https://github.com/googleapis/release-please/pull/1938/files#r1322981745

This would be very nice to have! Another related thought, maybe a list of excluded authors? For example, I wouldn't want myself listed by every single commit I do.

Yeah I can see that being annoying.
I guess we could also remove the @ from the author's user ID when building the notes.

What is the current state of this PR?
Would love to see this, especially in combination with the beforementioned exclude-list!
Thanks for your work!

What is the current state of this PR? Would love to see this, especially in combination with the beforementioned exclude-list!
Thanks for your work!

I have updated the PR again. It should be ready for another review from @chingor13.
I'm thinking instead of an exclusion list, it might more sensible to add further capabilities to this .hbs file.
Perhaps there is a way to list the authors at the PR level, rather than the commit level.

This looks so close. I think we will want to pass the template string in the config, rather than making an extra GitHub API request to fetch the template from a file on the repository. The template contents should be small enough (generally a one-liner)

The example template I used is quite big.
https://github.com/jamszh/test-release-please/blob/main/.release-please-commit-partial.hbs
Though i'm not too sure how others will use it
Are you saying we should have the contents of the 'commit-partial.hbs' file as part of the config?
It doesn't feel like a one-liner to me, especially if users want something more customized (hence more complicated).


only order subject ids if they exist

on selection avoid trying to respect the ordering of an empty list.
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

So we're still going to ask the database to return to all the subjects matching one of an empty array of IDs, just not sort it? :)

Yeah - the serializer needs a scope to resolve, it'll be an empty scope SELECT"subjects.* FROM subjects WHERE subjects.activated_state = 0 AND 1=0.

Sorry, snide remark getting in the way of being actually helpful. What i meant to suggest was using .none, which AR knows how to short-circuit.
    if selected_subject_ids.empty?
      selected_subject_scope = Subject.none
    else
      selected_subject_scope = Subject.active.where(id: selected_subject_ids)
        .order("idx(array[#{selected_subject_ids.join(',')}], id)")
    end

Nice - Scope.none is a better option.


merged LAB conversion and color approximation, removing an allocation.

I also added a pre-processing step to the palettes being used right before they're converted to LAB: It now runs a deduplication step, which has a large performance improvement whenever multiple styles of the same theme are used at the same time.

Added the new themes to the CLI help message

Also fixed the unstable feature. Tested and compiles on Rust 1.69.0 stable

Thank you, I was working on the duplication issue as some themes like edge have a lot of duplicate values.
I'm also rewriting some sections of code so I will push shortly which will hopefully not interfere that much with your PR.
Also, I think it might be a good idea to create feature issues so that they're tracked and can be marked into milestones as I'm almost ready to release v1.0.0-rc.

Before merging, please go over your PR as the changes that I made in PR #5 may conflict with yours + I refactored large parts of the code. Thanks.

I already went over #5 as well as fixing the conflicts. The changes are great

Ok, I will take a second look at your PR before merging. Great job with these improvements.

Approved!


remove timestamp cast to collector_tstamp in page_views

Removed timestamp(colllector_tstamp) casting because BQ doesn't allow casting fields to the same datatype

Nice @ericalouie! What do you make of the failing test in the CI build?


Update storage-blob-performance-tiers.md

@aishwmano : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@aishwmano : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@aishwmano: I'm sorry - only the author of this article, @mhopkins-msft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off

@aishwmano: I'm sorry - only the author of this article, @mhopkins-msft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Merging based on approval by content owner @mhopkins-msft

#sign-off


New marker line overlaps on the context menu items when marking a message as "unread"

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app
Open any report
Send any message
Mark it as unread
Observe that new marker is over hover menu and hover menu items are not selectable

Expected Result:
New marker should not overlap hover menu items and should not block menu items from click
Actual Result:
App overlaps new marker on hover menu items and makes the hover menu items non clickable
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/236004946-2ef5d8b7-5379-49d3-86d1-f64cff728096.mp4
https://user-images.githubusercontent.com/43996225/236004962-ba454911-71fb-4f4e-aebe-d2f7b2c0f87c.mp4
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683084751140789
View all open jobs on GitHub

Triggered auto assignment to @sonialiap (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Triggered auto assignment to @tgolen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

I'm out for the night, if you need a BZ to do anything ASAP then please reassign

Added MacOS / Desktop to the reproducible platforms.

Going to take the opportunity to update this regression TC:

Message Action menu - Unread Messages

We're not verifying that the New messages line should display when using the mark as unread button. Will update this message when updated.

Seems most likely caused by this https://github.com/Expensify/App/pull/17704

Gonna revert it.

Hi @sonialiap, @marcaaron, @dangrous sorry its my first deploy blocker issue so not aware whether eligible for reporting bonus or not but if this report had triggered the changes to fix the issue, will I be eligible for reporting bonus?

Checking with the team

The team agrees that reporting an issue that led to a fix (including a revert) should be compensated
@dhanashree-sawant I've sent an offer to you 😄
Upwork post https://www.upwork.com/jobs/~015b100cf73ac86202

Paid ✅


Amplify gen2 - Use same sandbox on multiple dev environments

Environment information
System:
    OS: Windows 11 10.0.22000
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 2.68 GB / 15.73 GB
  Binaries:
    Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 9.8.1 - C:\Program Files\nodejs\npm.CMD
    pnpm: Not Found
    bun: Not Found
    Watchman: Not Found
  npmPackages:
    @aws-amplify/backend: ^0.10.3 => 0.10.3
    @aws-amplify/backend-cli: ^0.9.6 => 0.9.7
    aws-amplify: ^6.0.12 => 6.0.13
    aws-cdk: Not Found
    aws-cdk-lib: Not Found
    typescript: ^5.3.3 => 5.3.3

Description
I would like to use the same sandbox on two different computers but 'npx amplify sandbox' creates a new sandbox for the second dev environnement.
The project name is the same. Howover, the $(whoami) part of the name of the sandbox is not the same (amplify--<$(whoami)>-sandbox)

Hi @jbp35, you can use npx amplify sandbox --name <some name> to substitute a value for $whoami. If you use the same --name arg across multiple machines, sandbox will deploy to the same stack.

Hi @jbp35, you can use npx amplify sandbox --name <some name> to substitute a value for $whoami. If you use the same --name arg across multiple machines, sandbox will deploy to the same stack.

Thanks, confirming it's working.


Query Builder Page, total run column shows 0, which are not 0 on live

Query Builder Page, Total run column shows 0, which are not 0 on live

it is working
just starting with 0 again


zh: update full export and import for more columns in downstream

What is changed, added or deleted? (Required)
support more columns in downstream for full export and import, because we have supported it in https://github.com/pingcap/dm/pull/906.
Which DM version(s) do your changes apply to? (Required)

[x] master (the latest development version, including v2.0 changes for now)
[ ] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s):

Do your changes match any of the following descriptions?

[ ] Delete files
[ ] Change aliases
[x] Have version specific changes
[ ] Might cause conflicts

@GMHDBJD @ireneontheway PTAL

/merge


Feature to grab logo/background files from local

Build in feature to use your local path e.g.:
const data {
logo: './img/logo.png'
}

Will add this to feature list.


Consider alternatives to redirects for passing authentication response to apps

By sending the authentication response with a GET - we're causing the following problems:

leaking the token in Referrer headers in the app
running into limits of URI length (414 error) or header size (520 error)

This recently bit me on a Blockstack app.  Looking at the authResponse, a large chunk of the data is my profile.  Can we consider not passing the profile object in the authResponse, and simply having the app look the profile up itself as part of processing the sign-in?

Can we consider not passing the profile object in the authResponse, and simply having the app look the profile up itself as part of processing the sign-in?

I think this is a good decision in the long term. The only gotcha is that we would break apps with an older version of blockstack.js. Do we pass the version of blockstack.js with our authRequest? If so, we could have conditional logic here.

I think this is a good decision in the long term. The only gotcha is that we would break apps with an older version of blockstack.js. Do we pass the version of blockstack.js with our authRequest? If so, we could have conditional logic here.

I was afraid of that.  However, I think we can address this in a backwards-compatible way by having handlePendingSignin() automatically fetch the profile and store it into the userData structure before storing userData to local storage.
The authResponse tokens are versioned, so we can definitely add some conditional logic there to only carry out the app-driven lookup for newer versions.

I think we already don't pass the profile in auth responses >=1.1

Ah, nm.  The above is already implemented.  I should have read the code closer.

Yes. We don't pass profiles in apps using blockstack.js released any time in 2018.

The calling structure for this is really confusing though -- it's not immediately obvious that profiles aren't sent over -- basically, for backwards compatibility, we kept the profile key in the auth response object, and so it's left as an argument in the makeAuthResponse function. However, if the browser sees the do_not_include_profile key in the auth request, it will pass null to that function. This is definitely technical debt, as it embeds the logic for this across two different projects.


Can you do the same for facebook www.messenger.com

Can you do the same for facebook www.messenger.com ?

I can help with coding

Yes

I was thinking about that.  There are several messenger.com wrappers in the Store, however.  What would the advantage be for ours?  (serious question...)

De advantage would be that it's open source, all the other wrappers seem like keyloggers to me. But will anybody notice...?


Fix??

What are you exactly trying to "fix"?

I'm just testing, if it fixes you can merge

who are you!


Don't run the build steps on PRs when only documentation is updated

Small update to make it so that design doc PRs or just README changes don't need to run all the rust related actions. Lot faster to get design doc only PRs in.

You can also add .yml to ignore paths


[WIP] Add support for the QLP & SPOC FFI light curve products

Fixes #912.
Both the MIT Quicklook Pipeline (QLP) and the Ames pipeline (SPOC) recently started delivering FFI-based light curve products and target pixel files as High Level Science Products (HLSP) to the data archive at MAST.  It is important for Lightkurve to support searching and reading these valuable products!
The following changes are required:

Going forward, the search_lightcurve function will now return MAST portal products with filename suffix "lc.fits".  Previously it was looking for the string "Light Curve" appearing in the product description field, but this is not the case for these HLSPs.
The search_targetpixelfile function will now return products with filename suffix "tp.fits" or "targ.fits.gz".  In the past it was looking for the string "Target Pixel" in the description field.

Note: to search for SPOC FFI light curves, users will have to pass author="TESS-SPOC", whereas short cadence light curves will be known under author="SPOC". Demo:

This is a Work In Progress (WIP) because I have yet to test downloading and opening these products.

Update: it is now possible to search and download both SPOC and QLP light curves based on FFI data!
Screenshot:


chore(master): release 0.4.0

:robot: I have created a release beep boop
0.4.0 (2024-02-04)
Features

apk: apk repository builder (#237) (007d18d)
apk: implement apk pipe (#281) (d8e5b38)
appinstaller: group on-launch config under single parent (#242) (dc08d28)
better error messages on failed integration (#250) (e08fde5)
better version constraints (#249) (2755b2c)
cli: manage RSA keys (#244) (cb5de41)
generate jsonschema from config (#287) (fe5e907)
source/gitlab: allow setting custom URL (for self-hosted) (#240) (3ed31b4)
use raw base64 ed25519 keys (#262) (b18608a)
validate config (#290) (fd12557)

Bug Fixes

apk: incorrect version constraint, handle target errors (#305) (8c5b11e)
appinstaller: wrong extension for appxbundle (#282) (591f90d)
dirname validation (#297) (416b2df)
pgp: invalid signature on fedora 39 (#227) (9c2049f)
sparkle: invalid ed signature (#248) (04e0ae6)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/abemedia/appcast/releases/tag/v0.4.0 :sunflower:


build fail with 0.3.1, was working with 0.3.0

Hi @ksugar ,
With docker I created  (16 days ago) a conda env (using a yml file) to create a samapi environment (see below )
DockerFile
FROM nvcr.io/nvidia/pytorch:23.07-py3

...
...
...

# install samapi
COPY conda_envs/env_samapi.yml /tmp/env_samapi.yml
RUN conda env update -n samapi -f /tmp/env_samapi.yml \
    && conda clean --all -f -y \
    && conda env export -n "biop"

env_samapi.yml
name: "samapi"
channels:
  - conda-forge
  - defaults
dependencies:
  - python=3.11
  - pip
  - pip:
      - git+https://github.com/ksugar/samapi.git
prefix: "/opt/conda/envs/samapi"

But now I get an error
...
 => ERROR [16/18] RUN conda env update -n samapi -f /tmp/env_samapi.yml     && conda clean --all -f -y     && conda env export -n "biop"                                       183.2s
------
 > [16/18] RUN conda env update -n samapi -f /tmp/env_samapi.yml     && conda clean --all -f -y     && conda env export -n "biop":
1.667 Channels:
1.667  - conda-forge
1.667  - defaults
1.667 Platform: linux-64
1.667 Collecting package metadata (repodata.json): ...working... done
46.59 Solving environment: ...working... done
47.75
47.75 Downloading and Extracting Packages

53.45 Preparing transaction: ...working... done
53.66 Verifying transaction: ...working... done
54.83 Executing transaction: ...working... done
57.20 Installing pip dependencies: ...working... Pip subprocess error:
182.9   Running command git clone --filter=blob:none --quiet https://github.com/ksugar/samapi.git /tmp/pip-req-build-c_iehv3a
182.9   Running command git clone --filter=blob:none --quiet https://github.com/ksugar/MobileSAM.git /tmp/pip-install-52glofzl/mobile-sam_7aa91f777a704ab2840ce452a2a8d188
182.9   WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7f676c388850>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /packages/f4/74/1c0c87dcf7ee0d69d383448182ca8b675d230f7329411f88067cba874ecd/fastapi-0.96.1-py3-none-any.whl.metadata
182.9 ERROR: Ignored the following versions that require a different python version: 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11; 3.0.0 Requires-Python >=3.7, <=3.11
182.9 ERROR: Could not find a version that satisfies the requirement torchvision<0.15.0,>=0.14.1 (from samapi) (from versions: 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.2.0, 0.2.1, 0.2.2, 0.2.2.post2, 0.2.2.post3, 0.15.0, 0.15.1, 0.15.2)
182.9 ERROR: No matching distribution found for torchvision<0.15.0,>=0.14.1
182.9
182.9 Ran pip subprocess with arguments:
182.9 ['/opt/conda/envs/samapi/bin/python', '-m', 'pip', 'install', '-U', '-r', '/tmp/condaenv.gbpw91fb.requirements.txt', '--exists-action=b']
182.9 Pip subprocess output:
182.9 Looking in indexes: https://pypi.org/simple, https://pypi.ngc.nvidia.com
182.9 Collecting git+https://github.com/ksugar/samapi.git (from -r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Cloning https://github.com/ksugar/samapi.git to ./pip-req-build-c_iehv3a
182.9   Resolved https://github.com/ksugar/samapi.git to commit 6be6c93d40fc30bdd6d5279c7945e1e8996324a6
182.9   Installing build dependencies: started
182.9   Installing build dependencies: finished with status 'done'
182.9   Getting requirements to build wheel: started
182.9   Getting requirements to build wheel: finished with status 'done'
182.9   Preparing metadata (pyproject.toml): started
182.9   Preparing metadata (pyproject.toml): finished with status 'done'
182.9 Collecting mobile_sam@ git+https://github.com/ksugar/MobileSAM.git (from samapi==0.3.1->-r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Cloning https://github.com/ksugar/MobileSAM.git to ./pip-install-52glofzl/mobile-sam_7aa91f777a704ab2840ce452a2a8d188
182.9   Resolved https://github.com/ksugar/MobileSAM.git to commit 41ac534a20a4779fab4f8c84e158ca7c7b40ff26
182.9   Preparing metadata (setup.py): started
182.9   Preparing metadata (setup.py): finished with status 'done'
182.9 Collecting fastapi[all]<0.97.0,>=0.96.0 (from samapi==0.3.1->-r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Obtaining dependency information for fastapi[all]<0.97.0,>=0.96.0 from https://files.pythonhosted.org/packages/f4/74/1c0c87dcf7ee0d69d383448182ca8b675d230f7329411f88067cba874ecd/fastapi-0.96.1-py3-none-any.whl.metadata
182.9   Downloading fastapi-0.96.1-py3-none-any.whl.metadata (24 kB)
182.9 Collecting geojson<4.0.0,>=3.0.1 (from samapi==0.3.1->-r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Downloading geojson-3.0.1-py3-none-any.whl (15 kB)
182.9 Collecting numpy<2.0.0,>=1.23.5 (from samapi==0.3.1->-r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Obtaining dependency information for numpy<2.0.0,>=1.23.5 from https://files.pythonhosted.org/packages/32/6a/65dbc57a89078af9ff8bfcd4c0761a50172d90192eaeb1b6f56e5fbf1c3d/numpy-1.25.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
182.9   Downloading numpy-1.25.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (5.6 kB)
182.9 Collecting opencv-python<<IP_ADDRESS>,>=<IP_ADDRESS> (from samapi==0.3.1->-r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Obtaining dependency information for opencv-python<<IP_ADDRESS>,>=<IP_ADDRESS> from https://files.pythonhosted.org/packages/f5/d0/2e455d894ec0d6527e662ad55e70c04f421ad83a6fd0a54c3dd73c411282/opencv_python-<IP_ADDRESS>-cp37-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
182.9   Downloading opencv_python-<IP_ADDRESS>-cp37-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (19 kB)
182.9 Collecting pillow<10.0.0,>=9.5.0 (from samapi==0.3.1->-r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Downloading Pillow-9.5.0-cp311-cp311-manylinux_2_28_x86_64.whl (3.4 MB)
182.9      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.4/3.4 MB 28.2 MB/s eta 0:00:00
182.9 Collecting scikit-image<0.22.0,>=0.21.0 (from samapi==0.3.1->-r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Obtaining dependency information for scikit-image<0.22.0,>=0.21.0 from https://files.pythonhosted.org/packages/22/c3/c5f3c351d6337a18d07c3fb04475626c106cd3dc3d59b85ec50d07656db0/scikit_image-0.21.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
182.9   Downloading scikit_image-0.21.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (14 kB)
182.9 Collecting shapely<3.0.0,>=2.0.1 (from samapi==0.3.1->-r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Downloading shapely-2.0.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (2.3 MB)
182.9      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.3/2.3 MB 26.9 MB/s eta 0:00:00
182.9 Collecting timm<0.10.0,>=0.9.2 (from samapi==0.3.1->-r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Obtaining dependency information for timm<0.10.0,>=0.9.2 from https://files.pythonhosted.org/packages/7a/bd/2c56be7a3b5bc71cf85a405246b89d5359f942c9f7fb6db6306d9d056092/timm-0.9.7-py3-none-any.whl.metadata
182.9   Downloading timm-0.9.7-py3-none-any.whl.metadata (58 kB)
182.9      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 58.8/58.8 kB 33.6 MB/s eta 0:00:00
182.9 Collecting torch<2.0.0,>=1.13.1 (from samapi==0.3.1->-r /tmp/condaenv.gbpw91fb.requirements.txt (line 1))
182.9   Downloading torch-1.13.1-cp311-cp311-manylinux1_x86_64.whl (887.4 MB)
182.9      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 887.4/887.4 MB 14.0 MB/s eta 0:00:00
182.9 INFO: pip is looking at multiple versions of samapi to determine which version is compatible with other requirements. This could take a while.
182.9
182.9 failed
182.9
182.9 CondaEnvException: Pip failed

I tried to modify to the version below  (from the updated README)
name: "samapi"
channels:
  - conda-forge
  - defaults
dependencies:
  - python=3.10
  - cudatoolkit=11.7
  - pip
  - pip:
      - git+https://github.com/ksugar/samapi.git
prefix: "/opt/conda/envs/samapi"

but still get an ERROR  :
 => ERROR [16/18] RUN conda env update -n samapi -f /tmp/env_samapi.yml     && conda clean --all -f -y     && conda env export -n "biop"                                       118.5s
------
 > [16/18] RUN conda env update -n samapi -f /tmp/env_samapi.yml     && conda clean --all -f -y     && conda env export -n "biop":
1.982 Channels:
1.982  - conda-forge
1.982  - defaults
1.982 Platform: linux-64
1.982 Collecting package metadata (repodata.json): ...working... done
51.91 Solving environment: ...working... done
53.11
53.11 Downloading and Extracting Packages
libsqlite-3.43.0     | 821 KB    |            |   0%
53.14 cxx-ng-13.1.0  | 3.7 MB    |            |   0%
53.14 s-6.4          | 860 KB    |            |   0%
53.14 ools-68.1.2    | 451 KB    |            |   0%
53.14 -3.10.12       | 24.4 MB   |            |   0%
53.14 1.0.8          | 484 KB    |            |   0%
libsqlite-3.43.0     | 821 KB    | ########## | 100%
53.98 cxx-ng-13.1.0  | 3.7 MB    | #########2 |  92%
54.04 s-6.4          | 860 KB    | 1          |   2%
54.04 ools-68.1.2    | 451 KB    | 3          |   4%
54.04 -3.10.12       | 24.4 MB   | ##9        |  30%
54.05 1.0.8          | 484 KB    | 3          |   3%
54.05 0.41.2         | 56 KB     | ########## | 100%
57.39 cxx-ng-13.1.0  | 3.7 MB    | ########## | 100%
57.39 p_mutex-4.5    | 23 KB     | ######9    |  69%
57.45 ools-68.1.2    | 451 KB    | ########## | 100%
57.45 -3.10.12       | 24.4 MB   | #########3 |  94%
57.45 1.0.8          | 484 KB    | ########## | 100%
57.45 l_linux-64-2.4 | 688 KB    | 2          |   2%
57.45 -ng-13.1.0     | 758 KB    | 2          |   2%
57.45 p_mutex-4.5    | 23 KB     | ########## | 100%
57.52 .6             | 409 KB    | ########## | 100%
57.52 l-3.1.2        | 2.5 MB    | ########## | 100%
57.52 tificates-2023 | 146 KB    | ########## | 100%
57.52 l_linux-64-2.4 | 688 KB    | ########## | 100%
75.70 -ng-13.1.0     | 758 KB    | ########## | 100%
75.70 s-6.4          | 860 KB    | ########## | 100%

75.71
75.71
75.71
75.71 Preparing transaction: ...working... done
75.92 Verifying transaction: ...working... done
77.24 Executing transaction: ...working... By downloading and using the CUDA Toolkit conda packages, you accept the terms and conditions of the CUDA End User License Agreement (EULA): https://docs.nvidia.com/cuda/eula/index.html
79.84
79.84 done
79.91 Installing pip dependencies: ...working... Pip subprocess error:
96.66   Running command git clone --filter=blob:none --quiet https://github.com/ksugar/samapi.git /tmp/pip-req-build-zqqgui68
96.66   fatal: unable to access 'https://github.com/ksugar/samapi.git/': Could not resolve host: github.com
96.66   error: subprocess-exited-with-error
96.66
96.66   × git clone --filter=blob:none --quiet https://github.com/ksugar/samapi.git /tmp/pip-req-build-zqqgui68 did not run successfully.
96.66   │ exit code: 128
96.66   ╰─> See above for output.
96.66
96.66   note: This error originates from a subprocess, and is likely not a problem with pip.
96.66 error: subprocess-exited-with-error
96.66
96.66 × git clone --filter=blob:none --quiet https://github.com/ksugar/samapi.git /tmp/pip-req-build-zqqgui68 did not run successfully.
96.66 │ exit code: 128
96.66 ╰─> See above for output.
96.66
96.66 note: This error originates from a subprocess, and is likely not a problem with pip.
96.66
96.66 Ran pip subprocess with arguments:
96.66 ['/opt/conda/envs/samapi/bin/python', '-m', 'pip', 'install', '-U', '-r', '/tmp/condaenv.zcouky75.requirements.txt', '--exists-action=b']
96.66 Pip subprocess output:
96.66 Looking in indexes: https://pypi.org/simple, https://pypi.ngc.nvidia.com
96.66 Collecting git+https://github.com/ksugar/samapi.git (from -r /tmp/condaenv.zcouky75.requirements.txt (line 1))
96.66   Cloning https://github.com/ksugar/samapi.git to ./pip-req-build-zqqgui68
96.66
96.66 failed
96.66
96.66 CondaEnvException: Pip failed
96.66
------
Dockerfile:95
--------------------
  94 |     COPY conda_envs/env_samapi.yml /tmp/env_samapi.yml
  95 | >>> RUN conda env update -n samapi -f /tmp/env_samapi.yml \
  96 | >>>     && conda clean --all -f -y \
  97 | >>>     && conda env export -n "biop"
  98 |
--------------------
ERROR: failed to solve: process "/bin/sh -c conda env update -n samapi -f /tmp/env_samapi.yml     && conda clean --all -f -y     && conda env export -n \"biop\"" did not complete successfully: exit code: 1

Could it be because of https://github.com/ksugar/samapi/commit/ab8845eb131e96d41ed4a52ee9704aeba76135ad  ?
Thank you for your inputs,
Cheers,
R

Hi @romainGuiet, thank you for sharing the issue.
I think the direct cause was shown in the following line.

96.66   fatal: unable to access 'https://github.com/ksugar/samapi.git/': Could not resolve host: github.com

It seems that it can happen when you connect to the internet using a proxy server.
If you have HTTP_PROXY environment variable, you can pass it to docker build as follows.
docker build -t samapi --build-arg HTTP_PROXY=${HTTP_PROXY} .

with the following Dockerfile:
FROM nvcr.io/nvidia/pytorch:23.07-py3

ARG HTTP_PROXY
ENV PATH="~/miniconda3/bin:$PATH"

RUN mkdir -p ~/miniconda3 &&\
 wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O ~/miniconda3/miniconda.sh &&\
 bash ~/miniconda3/miniconda.sh -b -u -p ~/miniconda3 &&\
 rm -rf ~/miniconda3/miniconda.sh &&\
 conda update -n base -c defaults conda

# install samapi
COPY conda_envs/env_samapi.yml /tmp/env_samapi.yml
RUN conda env update -n samapi -f /tmp/env_samapi.yml \
    && conda clean --all -f -y \
    && conda env export -n "biop"

and the following condo_envs/env_samapi.yml file:
name: "samapi"
channels:
  - conda-forge
  - defaults
dependencies:
  - python=3.10
  - cudatoolkit=11.7
  - pip
  - pip:
      - git+https://github.com/ksugar/samapi.git
prefix: "/opt/conda/envs/samapi"

Please try it and let me know if it works.

Could it be because of https://github.com/ksugar/samapi/commit/ab8845eb131e96d41ed4a52ee9704aeba76135ad ?

I don't think this causes the issue because this is just a setting file for the VSCode.
Anyway, it was pushed by mistake and I will remove this line in the next release.

Thanks @ksugar for your swift answer !
As far as I know , no proxy set ...
What I find weird is that with my previous yml :
name: "samapi"
channels:
  - conda-forge
  - defaults
dependencies:
  - python=3.11
  - pip
  - pip:
      - git+https://github.com/ksugar/samapi.git
prefix: "/opt/conda/envs/samapi"

it seems that the git clone works (see error above) but pip complains because now they are versions problems .
I thought it could be due to the modification of the versions of torch in the commit https://github.com/ksugar/samapi/commit/ab8845eb131e96d41ed4a52ee9704aeba76135ad , file pyproject.toml , because the container I start from is torch >2 ( see doc )
so I modified my yml file to target the 0.3.0  :
name: "samapi"
channels:
  - conda-forge
  - defaults
dependencies:
  - python=3.11
  - pip
  - pip:
      - https://github.com/ksugar/samapi/archive/refs/tags/v0.3.0.tar.gz
prefix: "/opt/conda/envs/samapi"

and now it builds again... so I would guess the issue is not a proxy but some changes in the 0.3.1 ?
Best,
R

HI @romainGuiet , thank you for the update. Could you try again it with the following yml file?
name: "samapi"
channels:
  - conda-forge
  - defaults
dependencies:
  - python=3.10
  - pip
  - pip:
      - https://github.com/ksugar/samapi/archive/refs/tags/v0.3.1.tar.gz
prefix: "/opt/conda/envs/samapi"

It is possible that a temporal network problem caused the previous error.
Form my understanding, the following error is related to the network problem
96.66 fatal: unable to access 'https://github.com/ksugar/samapi.git/': Could not resolve host: github.com

In my environment, the following Dockerfile and condo_envs/env_samapi.yml build a Docker image without errors.
FROM nvcr.io/nvidia/pytorch:23.07-py3

ENV PATH="~/miniconda3/bin:$PATH"

RUN mkdir -p ~/miniconda3 &&\
 wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O ~/miniconda3/miniconda.sh &&\
 bash ~/miniconda3/miniconda.sh -b -u -p ~/miniconda3 &&\
 rm -rf ~/miniconda3/miniconda.sh &&\
 conda update -n base -c defaults conda

# install samapi
COPY conda_envs/env_samapi.yml /tmp/env_samapi.yml
RUN conda env update -n samapi -f /tmp/env_samapi.yml \
    && conda clean --all -f -y \
    && conda env export -n "biop"

name: "samapi"
channels:
  - conda-forge
  - defaults
dependencies:
  - python=3.10
  - cudatoolkit=11.7
  - pip
  - pip:
      - git+https://github.com/ksugar/samapi.git
prefix: "/opt/conda/envs/samapi"

I just tested consequently and everything works now 🤯
name: "samapi"
channels:
  - conda-forge
  - defaults
dependencies:
  - python=3.10
  - cudatoolkit=11.7
  - pip
  - pip:
      - git+https://github.com/ksugar/samapi.git
prefix: "/opt/conda/envs/samapi"

and
ˋˋˋ
name: "samapi"
channels:

conda-forge
defaults
dependencies:
python=3.10
cudatoolkit=11.7
pip
pip:

https://github.com/ksugar/samapi/archive/refs/tags/v0.3.1.tar.gz
prefix: "/opt/conda/envs/samapi"

ˋˋˋ
So I really don't know what was going wong...
Thank you again 🙏
Cheers,
R


Bug of ag or bug of vim?

My plugin LeaderF encountered an issue, ag can not list files on Windows.
Steps to reproduce:

enter vim
run the below commands::py import subprocess
:py print subprocess.Popen('ag -g "" .', shell=True, stdout=subprocess.PIPE).stdout.read()

no output.(suppose there are some files in current directory)
Expected result:
all the files can be listed just like running ag -g "" . in git-bash.
If purely run the python code, everything works fine.
For example, execute the command  py -2 test.py, test.py is as below:
import subprocess
print ( subprocess.Popen('ag -g "" .', shell=True, stdout=subprocess.PIPE).stdout.read() )

rg does not have this issue.

verified that this is a bug of vim.


Fix pfstates access issues and readme update on permissions

/api/diagnostics/firewall/pfstates requires full admin access
/api/diagnostics/firewall/pf_states which shows the same data can be accessed with Dashboard (all) permission

@alexdelprete I had left this in Draft as I was still testing everything before marking it as ready. I don't see any issues so I came back to mark it as Ready for review but see you already merged it. Everything is fine with this PR, but next time, please hold off until I set it as ready to review.

My bad, I wanted to release a quick beta to test pf_states privileges. Sorry for the rush.


fix: all_pks() for complex keys

Description
HashModel.all_pks() and JsonModel.all_pks() return only the last part of the Redis key after the last colon (:) instead of full key without the global/modal prefixes.
This only makes difference when we use colons in the primary keys. E.g.:

Global prefix: location
Model prefix: city
Primary key: ca:qc:montreal
Full Redis key: location:city:ca:qc:montreal
Expected result of all_pks: ca:qc:montreal
Actual result of all_pks: montreal

See related Issue fro details.
Related issues

#470

Codecov Report
Base: 78.85% // Head: 78.85% // No change to project coverage :thumbsup:

Coverage data is based on head (40da58e) compared to base (721f734).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #471   +/-   ##
=======================================
  Coverage   78.85%   78.85%
=======================================
  Files          14       14
  Lines        1173     1173
=======================================
  Hits          925      925
  Misses        248      248

Flag
Coverage Δ

unit
78.85% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

aredis_om/model/model.py
87.02% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

Fixes #470


aztec-nargo new --contract should add contract dependencies and template a contract

Problem
aztec-nargo new --contract doesn't add all of the setup that it could to help devs get set up with writing contracts.
Happy Case
running aztec-nargo new --contract should include the following in main.nr
use dep::aztec::macros::aztec;

#[aztec]

and add the latest aztec dependency to Nargo.toml
aztec = { git = "https://github.com/AztecProtocol/aztec-packages/", tag = "aztec-packages-v0.65.2", directory = "noir-projects/aztec-nr/aztec" }

Workaround
Yes
Workaround Description
Do it manually.
Additional Context
No response
Project Impact
Nice-to-have
Blocker Context
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

I don't think that nargo should be injecting Aztec dependencies in the default templates, this is going to add a whole new level of dependency hell between noir and Aztec.
This could be put in aztec-nargo but that's not developed in this repository or maintained by the noir team.


Provide good standalone docs for the GUI version

There needs to be a user manual, ideally with an itch.io tutorial. This could be extracted from the README.

Fixed in d745af1ea9b8b02636b1625ab296a2939d262e51


(Firebird) Navigator > Tables structure shows first table after modifying the structure

System information:

Operating system (distribution) and version
Windows 10

DBeaver version
7.0.5

Additional extensions
None

Connection specification:

Database name and version
Firebird 2.5

Driver name
org.firebirdsql.jdbc.FBDriver

Do you use tunnels or proxies (SSH, SOCKS, etc)?
No. localhost

Describe the problem you're observing:
When changing the structure of a table (eg adding an field) and persist/save the changes, the tables list in the DBeaver Navigator is wrong. The edited table is replace with the first table.
Steps to reproduce, if exist:
Create a Firebird database with 2 or more tables.
Add a field to second table.
Save/persist changes
DBeaver > Navigation automatically refreshes and the current selected table is replaced with the first table. It can be fixed by disconnecting and reconnecting to the database.
Include any warning/errors/backtraces from the logs
Error log is empty

thanks for the bug report

not reproducible anymore (21.1.3)


[Author] putting the edited readme

Not sure where it's getting this as the author: https://unrealarchive.org/authors/putting-the-edited-readme.html
Real author list:
DM-Dualistic by Scott 'Pudd' Fowler  https://unrealarchive.org/maps/unreal-tournament/deathmatch/D/dm-dualistic_049f8836.html
DM-lucifixpitt by Terry 'lucifix' Miller https://unrealarchive.org/maps/unreal-tournament/deathmatch/L/dm-lucifixpitt_bf2d363f.html
DM-lucifixsatlantisfinal by Terry 'lucifix' Miller https://unrealarchive.org/maps/unreal-tournament/deathmatch/L/dm-lucifixsatlantisfinal_48beeeca.html
DM-outworld by Terry 'lucifix' Miller https://unrealarchive.org/maps/unreal-tournament/deathmatch/O/dm-outworld_958af9d1.html
DM-shotinthedark by Terry 'lucifix' Miller https://unrealarchive.org/maps/unreal-tournament/deathmatch/S/dm-shotinthedark_4ead6beb.html
DM-skyzone by Mike 'chaosz23' really don't want to give my last name https://unrealarchive.org/maps/unreal-tournament/deathmatch/S/dm-skyzone_04753e11.html (also can change release date, according to readme, to September 27, 2001)
DM-toberus by John 'Rukee' https://unrealarchive.org/maps/unreal-tournament/deathmatch/T/dm-toberus_09a69588.html
Source: readme's.

Great thanks. All updated.


Timestamp for this request was 1000ms ahead of the server's time.

I am running your code via docker on my mac. When bot decides to buy there is an error that says Unable to perform ticker and an exception like the issue title. How can I fix this?
Thanks

Hi is this fixed? I'm still running into this issue. And @VasTShadowZz suggested solution did not work.

The problem describe here is not an issue with the script, but rather an issue with the end host not being synchronized with ntp.

Windows has a program called Dimension 4, it synchronizes your clock at regular intervals. it was the only thing I tried that fixed the timestamp error permanently when working with Binance for another project.


Makefile and parallel execution build issue.

Describe the bug
The Makefile is not compatible with parallel execution.
To Reproduce
run the build with :
make -j8 build
Expected behavior
The build should run and finish without any error.
Environment (please complete the following information):
Add a MAKEFLAGS with "-j8"
Run a manual build of the app with make build
Logs:
[...]
yarn install v1.22.5
$ concurrently yarn:download:*
/bin/sh: concurrently: command not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
make: *** [Makefile:13: download-bins] Error 127
make: *** Waiting for unfinished jobs....
[...]

Workaround:
I need to either unset my MAKEFLAGS variable or force it to make -j1 build

To fix it, you could probably make good use of .NOTPARALLEL

I think the issue here is that concurrently package is missing.

Hi @nevalla
concurrently is actually installed from the Makefile here:
install-deps:
	yarn install --frozen-lockfile

Because of the parallelization and the -j8 not being supported, it starts multiple steps and failed.
We have
$ concurrently yarn:download:*
/bin/sh: concurrently: command not found

because concurrently is needed in the next Makefile steps.

This should work now as expected.

This should work now as expected.


Development notifications page

Finished notifications page

@mhmdhelmy28
make sure to pass all checks.

@Mahmoud-Emad
Done, all is good.


omc events ?

Could it be possible to have: omc events
Like oc events, it brings options that oc get event doesn't have
Like event type filtering:
oc events --types=Warning
LAST SEEN                  TYPE      REASON                            OBJECT                                            MESSAGE
3m27s (x3279 over 2d20h)   Warning   FailedToRetrieveImagePullSecret   Pod/common-service-db-1                           Unable to retrieve some image pull secrets (ibm-entitlement-key); attempting to pull the image may not succeed.
2m26s (x3234 over 2d19h)   Warning   FailedToRetrieveImagePullSecret   Pod/elasticsea-0ac3-ib-6fb9-es-server-esnodes-2   Unable to retrieve some image pull secrets (ibm-entitlement-key); attempting to pull the image may not succeed.
2m10s (x3237 over 2d19h)   Warning   FailedToRetrieveImagePullSecret   Pod/elasticsea-0ac3-ib-6fb9-es-server-esnodes-0   Unable to retrieve some image pull secrets (ibm-entitlement-key); attempting to pull the image may not succeed.
99s (x3248 over 2d19h)     Warning   FailedToRetrieveImagePullSecret   Pod/elasticsea-0ac3-ib-6fb9-es-server-esnodes-1   Unable to retrieve some image pull secrets (ibm-entitlement-key); attempting to pull the image may not succeed.
90s (x3268 over 2d20h)     Warning   FailedToRetrieveImagePullSecret   Pod/common-service-db-2                           Unable to retrieve some image pull secrets (ibm-entitlement-key); attempting to pull the image may not succeed.

And object filtering:
oc events --types=Warning --for=Pod/common-service-db-2
LAST SEEN                  TYPE      REASON                            OBJECT                    MESSAGE
2m28s (x3268 over 2d20h)   Warning   FailedToRetrieveImagePullSecret   Pod/common-service-db-2   Unable to retrieve some image pull secrets (ibm-entitlement-key); attempting to pull the image may not succeed.

giving omc the same possibility could be nice. What do you think ?

oc events adds several features, including output automatically sorted by "LAST SEEN". It was introduced in oc binary 4.13.
More info about the events sub-command in [1].
[1] https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/1440-kubectl-events#limitations-of-the-existing-design


Set up hosting for flowbite-vue.com

Hey @Chank1e, @ralphschuler,
We could host this on Flowbite Vue with any hosting platform that you think that plays nicely with Vue.
Let me know, we'll cover the costs.
Cheers,
Zoltan
PS: you can join our Discord Server and there's quite a bit of Vue.js community there that can get involved with the development of this library.
You can just DM me (zoltanszogyenyi) and get things started.

It appears this is done? Or is the current site hosted somewhere else?

Closing it as https://flowbite-vue.com/ exists.


fix: Typo...

🚀 Styleguide deploy preview ready!https://606b63c2245ddd009b746014--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/styleguide@33.6.3-alpha.7432c9.0


Adding PIC SPI master files from /randywu763 to /firmware

Purpose

Adding copy of the PIC-IoT_SPI-Master.X folder to /firmware
moving from original location (github.com/randywu763)
eliminate confusion on where to find instructions on how to program PIC board for SPI / cloud agent functionality

Does this introduce a breaking change?

[ ] Yes
[X ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[X] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

What to Check
Verify that the following are valid

.hex file from folder is transferable to plugged-in CURIOSITY

Looking to add changes to README documentation before merging this PR

Need to finalize changes to grammar, titles in Cloud_Agent README


Data Ingest Board Pre-Generalization > UX/I Fixes

https://github.com/sennetconsortium/portal-ui/issues/771

[x] Fix brief showing of login form after globus redirect
[x] Fix brief showing of login form on click of Logout button
[ ]  React key prop complaints
[ ] Resolve button ui border etc
[ ] Resolve chip/badge ui color contrasts etc

React key prop complaints will be resolve during generalization. rowKey="hubmap_id" .. needs to be configured.


Question about bpy and the 3d_copy_and_paste.py

Dear authors, thank you for the wonderful works.
When I try to reproduce the experiment, I met two problem:
(1) the version about the bpy, I found that bpy can only be installed by 2.91.0, other version will get build error.
(2) running the 3d_copy_and_paste.py, I met the error at line 51:
" bpy.ops.mesh.boundbox_add()"
:
site-packages/2.91/scripts/modules/bpy/ops.py", line 132, in call
ret = _op_call(self.idname_py(), None, kw)
AttributeError: Calling operator "bpy.ops.mesh.boundbox_add" error, could not be found
Exception ignored in: <function CyclesRender.del at 0x7f0fea965290>

OK, thank you for your quick answer, and I have installed the createBoundingbox plugin in the blender.
I have two another questions:
(1) where does the python script 3d_copy_and_paste.py to be ran, is it ran on the python environment installed on my computer, or on the python interpreter of Blender?
(2) I install the plugin in Blender, if it is ran based on Blender's python interpreter, then I need to install all the imported package for Blender's python interpreter, then copy the 3d_copy_and_paste to Blender's Scriping Layout and run, right?
Thank you very much!
Best wishes!

Hi @RongkunYang, were you able to replicate the results?


Drop pod limits

The higher limit can sometimes overwhelm the cache

/test jvm-build-service-in-repo-apicurio-e2e


don't panic when there is a very long word in usage

each_split_within will panic if a single word is longer than the limit
it is given.  This seems unnecessary to me; the worst that will happen
with a very long word is that the help output will be a bit uglier
than it should be.
Fixes #36.

Thanks!


bring back Session

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

#64  👈
#63
master

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

Join @pepyakin and the rest of your teammates on  Graphite


WFCORE-1604 Fail-fast start up init.d scripts on error / WFCORE-1615 Make wildfly-init-redhat.sh consistent with wildfly-init-debian.sh

Now that WildFly creates an startup-marker we can detect an error before timeout of the init.d startup scripts.
I also change tabs for spaces, but the real change is in the start() section on:
grep -i 'error:' "$JBOSS_MARKERFILE"

Thank you, but please remove the whitespace changes so we can readily evaluate the functional change.

Core - Full Integration Build 2975 outcome was FAILURE using a merge of e9c93f671904175909d9ca02b7bfc95bff81c9e4
Summary: Tests failed: 1 (1 new), passed: 3398, ignored: 193 Build time: 00:59:11
Failed tests
org.jboss.as.test.clustering.cluster.web.passivation.FineSessionPassivationTestCase(SYNC-tcp).test: java.lang.AssertionError: response doesn't contain header 'result', all response headers = {name=Connection, value=keep-alive}, {name=X-Powered-By, value=Undertow/1}, {name=Set-Cookie, value=JSESSIONID=rf52VmJXirTlWEMQX_TRg9xvYPdzrwyeg9ffbSqF.node-0; path=/passivation}, {name=Server, value=WildFly/10}, {name=hUJcjAL7_HUJLT_5weO2lIhODrmYm6t3GzHbfxn2, value=PASSIVATION}, {name=Content-Length, value=0}, {name=jsessionid, value=rf52VmJXirTlWEMQX_TRg9xvYPdzrwyeg9ffbSqF}, {name=Date, value=Tue, 21 Jun 2016 01:29:21 GMT},
	at org.jboss.as.test.clustering.cluster.web.passivation.SessionPassivationTestCase.getRequiredHeaderValue(SessionPassivationTestCase.java:207)
	at org.jboss.as.test.clustering.cluster.web.passivation.SessionPassivationTestCase.test(SessionPassivationTestCase.java:121)
------- Stdout: -------
18:29:21,103 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:29:21,103 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:29:21,103 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-0
 [0m18:29:21,116 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /opt/buildAgent/work/38e1ea00f932992d/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-0/standalone/data/content/e2/b41151d3040c0f33b57e0fa8b75555f85a73d9/content
 [0m [0m18:29:21,123 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "passivation.war" (runtime-name: "passivation.war")
 [0m [0m18:29:21,206 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m18:29:21,207 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m18:29:21,207 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 35) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m18:29:21,207 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m18:29:21,266 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 36) WFLYCLINF0002: Started passivation.war cache from web container
 [0m [0m18:29:21,266 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) WFLYCLINF0002: Started routing cache from web container
 [0m [0m18:29:21,275 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 33) WFLYUT0021: Registered web context: /passivation
 [0m [0m18:29:21,282 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "passivation.war" (runtime-name : "passivation.war")
 [0m18:29:21,288 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Deploying deployment=deployment-1
 [0m18:29:21,295 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /opt/buildAgent/work/38e1ea00f932992d/full/testsuite/integration/clustering/target/wildfly-SYNC-tcp-1/standalone/data/content/e2/b41151d3040c0f33b57e0fa8b75555f85a73d9/content
 [0m [0m18:29:21,297 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "passivation.war" (runtime-name: "passivation.war")
 [0m [0m18:29:21,358 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m18:29:21,359 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 18) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m18:29:21,365 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m18:29:21,366 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 24) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
 [0m [0m18:29:21,376 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 18) ISPN000310: Starting cluster-wide rebalance for cache routing, topology CacheTopology{id=1, rebalanceId=1, currentCH=DefaultConsistentHash{ns=80, owners = (1)[node-0: 80+0]}, pendingCH=DefaultConsistentHash{ns=80, owners = (2)[node-0: 40+40, node-1: 40+40]}, unionCH=null, actualMembers=[node-0, node-1]}
 [0m [0m18:29:21,377 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 18) [Context=routing][Scope=node-1]ISPN100002: Started local rebalance
 [0m [0m18:29:21,377 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 24) ISPN000310: Starting cluster-wide rebalance for cache passivation.war, topology CacheTopology{id=1, rebalanceId=1, currentCH=DefaultConsistentHash{ns=80, owners = (1)[node-0: 80+0]}, pendingCH=DefaultConsistentHash{ns=80, owners = (2)[node-0: 40+40, node-1: 40+40]}, unionCH=null, actualMembers=[node-0, node-1]}
 [0m [0m18:29:21,377 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 24) [Context=passivation.war][Scope=node-1]ISPN100002: Started local rebalance
 [0m [0m18:29:21,403 INFO  [org.infinispan.CLUSTER] (remote-thread--p7-t2) [Context=routing][Scope=node-0]ISPN100003: Finished local rebalance
 [0m [0m18:29:21,405 INFO  [org.infinispan.CLUSTER] (remote-thread--p7-t2) [Context=passivation.war][Scope=node-0]ISPN100003: Finished local rebalance
 [0m [0m18:29:21,414 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t14) [Context=routing][Scope=node-1]ISPN100003: Finished local rebalance
 [0m [0m18:29:21,416 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t14) ISPN000336: Finished cluster-wide rebalance for cache routing, topology id = 1
 [0m [0m18:29:21,418 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t20) [Context=passivation.war][Scope=node-1]ISPN100003: Finished local rebalance
 [0m [0m18:29:21,425 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 18) WFLYCLINF0002: Started routing cache from web container
 [0m [0m18:29:21,430 INFO  [org.infinispan.CLUSTER] (transport-thread--p16-t20) ISPN000336: Finished cluster-wide rebalance for cache passivation.war, topology id = 1
 [0m [0m18:29:21,435 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 24) WFLYCLINF0002: Started passivation.war cache from web container
 [0m [0m18:29:21,450 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 24) WFLYUT0021: Registered web context: /passivation
 [0m [0m18:29:21,463 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "passivation.war" (runtime-name : "passivation.war")
 [0m [0m18:29:21,489 INFO  [stdout] (default task-17) http://[::1]:8080/passivation/listener?operation=set&name=a&value=1;jsessionid=kAnt_64Xxe6uWxtziB3pKwuZCulyIjLYbjr7CHkg
 [0m [0m18:29:21,500 INFO  [stdout] (default task-6) http://[::1]:8080/passivation/listener?operation=set&name=a&value=2;jsessionid=hUJcjAL7_HUJLT_5weO2lIhODrmYm6t3GzHbfxn2
 [0m [0m18:29:21,518 INFO  [stdout] (default task-62) http://[::1]:8080/passivation/listener?operation=get&name=a;jsessionid=rf52VmJXirTlWEMQX_TRg9xvYPdzrwyeg9ffbSqF
 [0m18:29:21,521 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-0
18:29:21,521 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Starting deployment=NONE, container=container-1
18:29:21,521 INFO  [org.jboss.as.test.clustering.NodeUtil] (main) Undeploying deployment=deployment-0
 [0m18:29:21,529 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 36) WFLYUT0022: Unregistered web context: /passivation
 [0m [0m18:29:21,556 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 23) ISPN000029: Passivating all entries to disk
 [0m [0m18:29:21,557 INFO  [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 23) ISPN000030: Passivated 2 entries in 0 milliseconds
 [0m [0m18:29:21,566 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 23) WFLYCLINF0003: Stopped passivation.war cache from web container
 [0m [0m18:29:21,578 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment passivation.war (runtime-name: passivation.war) in 51ms
 [0m [0m18:29:21,591 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 23) WFLYCLINF0003: Stopped routing cache from web container
 [0m [33m18:29:21,633 WARN  [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address []

Windows Build 3344 outcome was FAILURE using a merge of e9c93f671904175909d9ca02b7bfc95bff81c9e4
Summary: Tests failed: 1 (1 new), passed: 3624, ignored: 56 Build time: 00:47:40
Failed tests
org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.testRightVaultPassword: java.lang.AssertionError: Password should be right and authentication successful
Expected: a string containing "\"outcome\" => \"success\""
     but: was "-2147483648: "
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
	at org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.testRightVaultPassword(VaultPasswordsInCLITestCase.java:144)
------- Stdout: -------
07:23:36,411 INFO  [org.jboss.as.test.integration.management.util.CustomCLIExecutor] (main) A timeout has occurred while invoking CLI command.

Done Brian, removed the withespace change, the failed test are not related to this commit.
Retest this please.

Note: The wildfly-init-debian.sh was tested on Ubuntu 14.04 (pre-systemd) and 16.04 (systemd). The wildfly-init-redhat.sh was superficially tested on Fedora 24 (systemd), it works, but the correct tests needs to be made in pre-systemd versions.
If someone can fully test on RHEL or any other pre-systemd would appreciate.

@jorsol Thanks for this! I need to do a bit of housekeeping before merging:
We require that all contributions be made under the terms of the MIT License, http://www.opensource.org/licenses/mit-license.php. Do you agree to the these terms?

@bstansberry, hold this merge, I'm making improvements to the redhat script.
I'm testing it in CentOS (RHEL) 6.8, CentOS (RHEL) 7.2 and Fedora 24 Server. The redhat script will have some features found in debian script, and a little housekeeping too.
I'm also making them more compatible with systemd.

Ok, Jorge; sounds good.

Done Brian, it can be reviewed now and merged if approved.
I agree with the MIT License.


EBD-492: Apollo3 low power support

Added basic support for runtime-idle and suspend-to-idle states on the Ambiq Apollo3. When in suspend I measured the current draw to be 338uA which according to JB should be good enough. We can add further power optimizations by turning off sensors and peripherals once as we add more functionality.

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

hal_ambiq
899ea4c72d33330c3a5d5b27bb54aad7377810f7
b0f7395673908d4cbd2a796bba5d9198f8ee8d8d
N/A

Note: This message is automatically posted and updated by the Manifest GitHub Action.


swww: 0.7.3 -> 0.8.1

Diff: https://github.com/Horus645/swww/compare/refs/tags/v0.7.3...v0.8.1
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

1 package built:

swww


[Improve][Doc] Intro the multi-line text feature in document

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
We need to provide a detailed introduction in the Config https://github.com/apache/seatunnel/blob/dev/docs/en/concept/config.md document about our support for multi-line symbols """, making it easier for users to write complex configuration files. Please refer https://seatunnel.apache.org/docs/2.3.4/faq#how-do-i-write-a-configuration-item-in-multi-line-text-in-the-configuration-file
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Can I take this issue? It's my first time contributing.

closed by #6713


Peerd: Use message receipts to confirm receival

Peer messages sent to a remote peer are now cached until the remote peer has replied with a corresponding receipt.
If the connection fails in a listener spawned peerd, the cache is emptied before peerd shuts down and the messages are sent back to their respective origin (swapd). Swapd then processes them into its own cache.
If the connection fails in a connecting peerd, the cache is only emptied once the reconnect has been a success. Messages are not sent back to their origin.

@h4sh3d force pushed the required changes.

I pushed a commit to remove the swapd request whitelisting.


CODE_OF_CONDUCT, ISSUE_TEMPLATE, PULL_REQUEST_TEMPLATE guidelines added

Code of conduct , issue template and pull request template guidelines are among 6 key features for community profile for our project. Ref:- https://github.com/UdacityMobileWebScholarship/guess-quote/community
This PR will help our project stand out in terms of recommended community standards.
Templates provided in the PR will also help our contributors while creating PR and issues with standard guidelines  by showing them the template as the last time checklist template in the description text area provided.

@optimistanoop Thank You for you contribution.


[cgal] update to 5.6

This pull-request updates the cgal port to CGAL version 5.6.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

You can refer to this comment for logs.

You can refer to this comment for logs.

Thanks to the discussion. I found out the logs, available in the artifacts of Azure job. It turns out the issue is CGAL-5.6 that is no longer tested on Windows x86 (32 bits). And the error is:
D:\installed\x86-windows\include\CGAL/cpp_float.h(30): error C3861: '_BitScanForward64': identifier not found
D:\installed\x86-windows\include\CGAL/cpp_float.h(42): error C3861: '_BitScanReverse64': identifier not found

I will try to find out a solution with my fellow CGAL developers...

Done: now the CI checks are fine. I will contribute the patch upstream, now that I have verified that it is correct.

Note: I will be converting your PR to draft status. The above suggested changes are only recommendations. If you are willing to adopt them, please click "ready for review" after making the modifications. If you do not wish to make any changes, please click "ready for review" directly. That way, I can be aware that you've responded since you can't modify the tags.


/key endpoint ignores the body field wrappingKey

No matter the wrapping key specified, /key endpoint never wraps the key returned.

Looks like this is intentional because we don't actually wrap keys in the privacy sandbox use case, however in that case should this field be removed?


Update SipTesterClient.ps1 in siptesterclient.zip

Update RetryCount mapping in Sip Tester client

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@raivoe Could you please point out the best person to review and approve this PR? Thanks

@LanaChin could you please review and merge? Thank you.


CORS issue, how to get around it?

I'm getting the following error when using the libraries.   I don't have this issue with OpenAI, Google or Microsoft AI services.  I'm wondering what I could be missing here?
taskpane.html:1  Access to fetch at 'https://api.anthropic.com/v1/messages' from origin 'https://ghostwriter-ai.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Same issue as well when using localhost:3000 on my React App for testing

@phusting I got around this in development by initiating the fetch module to have "https://cors-anywhere.herokuapp.com" before it:
const client = new Anthropic({
fetch: async (url, init)  => {
console.log('About to make a request', url, init);
const response = await fetch(https://cors-anywhere.herokuapp.com/${url}, init);
console.log('Got response', response);
return response;
},
apiKey: "apiKey", // defaults to process.env["ANTHROPIC_API_KEY"]
});
but this is not really a solution that would work in production

Anthropic's recommendation here is to build a server-side proxy: https://github.com/anthropics/anthropic-sdk-typescript/issues/219#issuecomment-1830324926

@phusting @Vagif12 our latest SDK release now offers CORS support [changelog].


v1.2 - beta issue

I am using a windows laptop without much available storage, so I am trying to use the added functionality of changing the output folder to a removable drive. I ran the program twice using two different sets of GoPro files. Both times the program completed and output a file that looked good in the folder I asked it to. But when running through ReelsteadyGo it said "no metadata found." Not sure the cause of this. Happy to troubleshoot other ideas.

Hi! Let's dig into it.
I assume that the device you're trying to store the joined file on, is formatted in NTFS or another file system that allows files larger than 4GB.
I've created a provisional version with the next fixes and future features for the final v1.2.0 with a console to be able to see and execute freely what you want in the application and a system of logs to try to detect the problem.
I would appreciate it if you could try again to process the same files that have given you a problem (it does not require installation) and upload the log file that is in the following path: %USERPROFILE%\AppData\Roaming\reelsteady-joiner\logs\renderer.log
All the information you can provide is always welcome.
v1.2.0-beta-fix-0.0.1: Download


Use GitHub Packages directly in action.yml files

Docker images published to http://docker.pkg.github.com/ can't directly be used in action.yml files via docker://, for a couple of reasons:

the docker package registry currently requires HTTP auth, including for public repositories
the actions docker daemon doesn't authenticate with docker.pkg.github.com by default

Workaround
To work around this, course templates need to currently specify their own action locally, that builds a Dockerfile locally that references the course image, and the workflow files need to add an additional step to authenticate with docker before running the course action.
Once Fixed
Once this is no longer the case, and actions.yml files can directly reference docker images on docker.pkg.github.com, the following changes need to be made in this repository:

The action .github.to.move/workflows/action/ directory should be deleted
from templates/learninglab/course-template
The workflow file templates/learninglab/course-template/.github.to.move/workflows/check-queries.yml should be updated to address the TODO comments
Instructions should be updated in templates/learninglab/README.md to instruct course creators to modify the uses property in .github.to.move/workflows/check-queries.yml instead of updating the Dockerfile.

cc @adityasharad


Stream is now playing

I dont know how they pulled that one out.
But right now the stream is playing in the farm because I can hear it!
Wasnt like that 10 min ago lol.

Hi,
Have you tried refreshing the page a couple times ? Does the farm still open its black & green interface ?
If an update is needed, I'm still waiting for the HUGE 2.0 UPDATE as they claim. If they change some things regarding ticket farming it might be worth it to wait & not work for nothing.
Thanks for the support.

Reopening browser seemed to be the fix. Refresh did not work. Btw, I consider it a possible 'wifi loss', reconnecting issue. This is when it happened. It's working just fine now!

Ok nice!
You can reopen this issue if you encounter this bug one more time.


error on installation

python setup.py install
... snip...
Installed /home/esheldon/miniconda3/envs/mystack/lib/python3.7/site-packages/descwl_shear_testing-0.1.0-py3.7.egg
Processing dependencies for descwl-shear-testing==0.1.0
Searching for galsim
Reading https://pypi.org/simple/galsim/
Downloading https://files.pythonhosted.org/packages/77/24/dcaa9e935186c86f148c8f8a02dafe80de3cc8fa8d3c940d7991de2d5aa1/GalSim-2.2.3.tar.gz#sha256=ec1ceffc08f8c8d10c65bed698375685bc263923bac7c7dd4ee584b33e5c3cc7
Best match: GalSim 2.2.3
Processing GalSim-2.2.3.tar.gz
Writing /home/esheldon/data/tmp/easy_install-x2ndkbag/GalSim-2.2.3/setup.cfg
Running GalSim-2.2.3/setup.py -q bdist_egg --dist-dir /home/esheldon/data/tmp/easy_install-x2ndkbag/GalSim-2.2.3/egg-dist-tmp-inubnq7w
Using setuptools version 42.0.2.post20191201
Python version =  3.7.3 | packaged by conda-forge | (default, Dec  6 2019, 08:54:18)
[GCC 7.3.0]
GalSim version is 2.2.3
Looking for  libfftw3.so
   /home/esheldon/miniconda3/envs/mystack/lsst_home/stackvana_fftw/lib  (yes)
Include directory for fftw3 is  /home/esheldon/miniconda3/envs/mystack/lsst_home/stackvana_fftw/include
Looking for Eigen:
   /home/esheldon/miniconda3/envs/mystack/lsst_home/stack/miniconda/Linux64/eigen/3.3.7  (no)
   /home/esheldon/miniconda3/envs/mystack/lsst_home/stack/miniconda/Linux64/eigen/3.3.7/include  (yes)
PyBind11 is version  2.2.4
Looking for pybind11 header files:
error: Setup script exited with error: SandboxViolation: mkdir('/home/esheldon/.local/lib', 511) {}

The package setup script has attempted to modify files on your system
that are not within the EasyInstall build area, and has been aborted.

This package cannot be safely installed by EasyInstall, and may not
support alternate installation locations even if you run its setup
script by hand.  Please inform the package's author and the EasyInstall
maintainers to find out if a fix or workaround is available.

This is a weird setiptools thing, not the local package. I added install instructions to the readme. Closing.


[Misc] Update hardcoded image asset URLs

For posterity, I did run this locally to ensure the image assets were loading as expected:


tests are not always able to download ruby

First, there doesn't always exist dir for some particular distribution release, like debian-7,8 (which I need now). And there doesn't always exist ruby for that particular release, like 2.0.0-p353 for squeeze. So, why don't we turn system_version into array? Turning test_ruby_patchlevel into array must be a hassle, but you might consider switching to 247... er, which is not available for jessie, so doesn't sound right. But then again, we can download whatever patchlevel available, and set test_ruby_patchlevel=$(ls test/opt/rubies | sed -E 's/.*p([0-9]+)/\1/'), can't we?

So we used some code from RVM to detect the arch, OS, distro, and then download the precompiled ruby for said platform. Unfortunately, rvm-binary doesn't always have the most complete coverage.

So, why do we decide which version to use before knowing it's there? Why don't we download whatever ruby version available?

The tests depend on knowing a specific version. Usually, rvm-binary has decent coverage for recent ruby versions. If you're platform isn't supported, open an issue with them and they'll look into it.

I just run into the same problem. Using mint and there's no binaries from it. In that case, defaulting to ubuntu works fine I think.


IDEasy labeler not working correctly

Expected behavior
As a IDEasy developer, I want the github-action bot to correctly label Issues and PR.
Actual behavior
Currently every PR is labeled as bash, despite not being Bash.
Steps to reproduce (bug) / Use Case of feature request (enhancement)

create PR and it will automatically be labeled as bash

Comments/Hints:
https://github.com/devonfw/IDEasy/blob/main/.github/labeler.yml
Affected version:

Github

Following KISS would be to delete the workflow (label-pr.yml) and its config (labeler.yml).