Undefind reference to sc_core::sc_api_version_2_3_3cxx201103L ...

Issues1.pdf
What is the solution
Thanks and regards
Mazhar

This issue is due to mismatched C++ Standard feature flags enabled for your module buld vs the SystemC compilation flags.
Please check the -std=c++xx flag when building your project, where xx is the value between 11,14,17, etc.

Building using 11 standard only still facing same issue
On Thu, 26 Oct, 2023, 1:42 pm Ameya Vikram Singh, @.***>
wrote:

This issue is due to mismatched C++ Standard feature flags enabled for
your module buld vs the SystemC compilation flags.
Please check the -std=c++xx flag when building your project, where xx is
the value between 11,14,17, etc.
—
Reply to this email directly, view it on GitHub
https://github.com/accellera-official/systemc/issues/60#issuecomment-1780625132,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAOG5MBAT5LUNIM4CF6O3TTYBILNPAVCNFSM6AAAAAA6QPW7WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBQGYZDKMJTGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

With which c++ standard flags was the SystemC library built with?
You can check the SystemC forum for similar discussion and possible solution.

Closed as answered.


Dockerfile is outdated

Hello,
Dockerfile.focal looks to be outdated and references script that is no more existing :
./scripts/download_driver.sh
As a consequence the image can't be build .
Regards.
Michael

@mboitet Hi, thanks for your feedback, there is indeed a minor issue.
Now the script file should be ./scripts/download_driver_for_all_platforms.sh, I have try to fix it.
Or you can also correct it temporarily in your local Dockerfile.focal file before the code is merged into branch master.

@mboitet Hi, thanks for your feedback, there is indeed a minor issue.
Now the script file should be ./scripts/download_driver_for_all_platforms.sh, I have try to fix it.
Or you can also correct it temporarily in your local Dockerfile.focal file before the code is merged into branch master.


Bank account - Almost done screen shown briefly when coming from choose an account page

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

Version Number: 9.0.56-0
Reproducible in staging?: Y
**Reproducible in production?:**Unable to check
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Issue found when executing PR https://github.com/Expensify/App/pull/49536
Action Performed:

Navigate to staging.new.expensify.com
Create a workspace and enable expensify card
Go to Expensify Card and click on issue card
Add a bank account via plaid
On choose account page choose saving and click next but watch closely before the next page appears

Expected Result:
Almost done screen does not get shown in between "Choose an account" page and "Personal Info" page
Actual Result:
Almost done screen get shown briefly in between "Choose an account" page and "Personal Info" page
Workaround:
Unknown
Platforms:

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

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/57373860-299c-41b5-97c3-3e2e75d217f0
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021852305752972180049
Upwork Job ID:<PHONE_NUMBER>972180049
Last Price Increase: 2024-11-01

We think that this bug might be related to #wave-collect - Release 2

Demoted. Reached out to @koko57 in the slack thread

Proposal
Please re-state the problem that we are trying to solve in this issue.
Bank account - Almost done screen shown briefly when coming from choose an account page
What is the root cause of that problem?
ConfirmationStep component inadvertently includes the "Almost done" screen in its path before reaching the intended "Personal Info" page.
What changes do you think we should make in order to solve the problem?
To resolve this, modify the navigation path within the ConfirmationStep component to skip the "Almost done" screen and navigate directly to the "Personal Info" page.
In the ConfirmationStep component, change (line 52):
    useEffect(() => {
        if (!isSuccessful) {
            return;
        }
        Navigation.navigate(backTo ?? ROUTES.WORKSPACE_EXPENSIFY_CARD.getRoute(policyID ?? '-1'));
        Card.clearIssueNewCardFlow();
    }, [backTo, policyID, isSuccessful]);

to :
Navigation.navigate(ROUTES.WORKSPACE_PERSONAL_INFO.getRoute(policyID ?? '-1'));

What alternative solutions did you explore? (Optional)

@grgia I can work on this one 🙂

I will be working on this issue and the one that has the same root cause https://github.com/Expensify/App/issues/50422, but first I need to finish some Workspace Feed issues

I'm finishing my Workspace Feed tasks - I will focus on this issue from Monday.

@grgia if you want, happy to take over, I have worked with @koko57 on these flows for last couple of weeks. but do not want to force-takeover 😄 so up to you

all yours @mountiny (now you owe me one fun issue in the future)

Mostly finished WFeed issues, now I'm able to fully focus on this one.

@mountiny today I will help with the new Workspace Feed bugs, they are higher priority? Maybe we can move this one to weekly?

Note for the PR phase, we need to recheck these issues again:

https://github.com/Expensify/App/issues/50422
https://github.com/Expensify/App/issues/51479

@eVoloshchak Could I take over this issue? Because this is a deploy blocker from the previous issue that I worked with @koko57

Still working on it. I've already removed some unnecessary code, for now it looks fine, looking for some edge cases.

EDIT: I need to rethink my solution. This component has too much complexity, I will try to simplify it a bit but I can't go with the solution I thought of first

Feel free to post a proposal first, then we can discuss it thoroughly together

I tested some other ideas, I really wanted to simplify this logic, but TBH it's really hard.
I tried to reproduce the issue once again on staging but I cannot get the exact behavior consistently.
https://github.com/user-attachments/assets/5f8d3ca7-9b16-4276-a2b0-ca5e05c2c2b6
So in my opinion, it doesn't make sense to burn more time on this - but let's retest it first. The only issue I've found - is that when we have the supported currency for the nonUSDBankAccountStep for the workflows we display the non-USD flow and for the Expensify Card we get the modal to change the currency - is it expected?
cc @mountiny

is that when we have the supported currency for the nonUSDBankAccountStep for the workflows we display the non-USD flow and for the Expensify Card we get the modal to change the currency - is it expected?

For Expensify Card, you need to have USD settlement bank account so I think yes

Issue not reproducible anymore
https://github.com/user-attachments/assets/fd280f3a-1708-4ede-9949-bf508979102b

Thanks! Lets close then and hopefully we dont have to handle this one again


Icon request: NotABug.org

URL of the site or app (required): https://notabug.org/
Logo resources for the icon (optional, but recommended): https://notabug.org/img/notabug-lg.png

Here you go!
https://github.com/aegis-icons/aegis-icons/blob/master/PNG/NotABug.org.png
https://github.com/aegis-icons/aegis-icons/blob/master/PNG/Variations/NotABug.org bg.var.png

Thank you so much for creating all of the requested icons. They are great.


Readme Improvement for facial biometric folder

https://github.com/akshitagupta15june/Face-X/tree/master/Facial_Biometric

Would love to work on this issue, can you please assign this to me under GSSOC'21.

Sure will assign you


Develop

Codecov Report

Merging #290 into develop will increase coverage by 0.26%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #290      +/-   ##
===========================================
+ Coverage    67.53%   67.80%   +0.26%
===========================================
  Files          210      210
  Lines        11454    11454
===========================================
+ Hits          7736     7766      +30
+ Misses        3718     3688      -30

Impacted Files
Coverage Δ

framework/demuxer/play_list/SegmentTracker.cpp
83.06% <0.00%> (-0.55%)
:arrow_down:

framework/demuxer/play_list/HLSStream.cpp
68.57% <0.00%> (ø)

framework/demuxer/avFormatDemuxer.cpp
79.45% <0.00%> (+0.30%)
:arrow_up:

mediaPlayer/SuperMediaPlayer.cpp
76.19% <0.00%> (+0.67%)
:arrow_up:

framework/filter/ffmpegAudioFilter.cpp
80.50% <0.00%> (+1.00%)
:arrow_up:

mediaPlayer/media_packet_queue.cpp
84.80% <0.00%> (+1.59%)
:arrow_up:

framework/data_source/curl/curl_data_source.cpp
86.61% <0.00%> (+1.67%)
:arrow_up:

mediaPlayer/player_msg_control.cpp
79.36% <0.00%> (+5.55%)
:arrow_up:

Continue to review full report at Codecov.

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


firebase ios15 cannot receive offline push

firebase ios15 cannot receive offline push,but android and ios15-  works well

Hi @Huangkaiping, any issues with firebase should be reported in it's dedicated repo over on https://github.com/firebase/flutterfire/issues.
Closing as this is not the right place to report firebase issues.
Thank you


Fix for latest k2 version

This PR is required so that the changes in https://github.com/k2-fsa/k2/pull/690 will not cause a crash.


Issue345 durack1 revise frequency entries

Fix #345
@taylor13 please take a look and review these changes

@taylor13 @martinjuckes those changes are in this PR, please review.
Once @martinjuckes has indicated he is ready to implement the change in the data request we'll merge these changes in and update the cmip6-cmor-tables

I'm not sure which files I'm supposed to check, but the frequency tweaks haven't been implemented in the files I checked.
Also, in the CMIP input table for CMOR the conventions attribute needs to be updated.  It reads:
"Conventions":[
"^CF-1.7 CMIP-6.0\\( UGRID-1.0\\)\\{0,\\}$"

It should now be "CMIP-6.2".  I wonder when we change the frequency options whether that should represent a release where the 2 is incremented to 3 (6.3.?).  If so, then the conventions specification should be "CMIP-6.3".

@taylor13 those changes can be found directly at WCRP-CMIP/CMIP6_CVs/pull/398/files the changes in the cmip6-cmor-tables you likely reviewed (if you clicked the link in my comment above) will need to be made once the CMIP6_CVs have been updated.. They are downstream


[Feature request] Function to reset view to init X and Y position

https://github.com/tradingview/lightweight-charts/issues/282#issuecomment-566140337
Need to set X and Y to initial range.
Example chart.resetScale()

Just to clarify. Time scale could be reset by calling https://github.com/tradingview/lightweight-charts/blob/master/docs/time-scale.md#resettimescale. But looks like we don't have an API to reset price scale.

Hm, looks like for price scale you can get price scale with https://github.com/tradingview/lightweight-charts/blob/v2.0.0/src/api/ichart-api.ts#L130 and then set autoScale option enabled. Does it work for now?

I'm going to close the issue since it seems that it already might be achieved (see my comments above). If you'll have any question or updates - feel free to re-open it.


RAG Enhancement

register DataReader with rule which specifies file name or file type
add file manager to manage document sources, e.g. nfs, ceph, minio, etc.
use scan instead of notify for file changes
add milvus store, add db index for db-store.
Support multi-index for one store
reranker function support float result (score)
Q-A pair search support
multi-media (picture first) support

can use https://github.com/fsspec/filesystem_spec to support 2


add wt 4.0.4

I've followed this guide
step by step carefully. Yes

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/caseymcc/hunter/builds/20847881
https://travis-ci.org/caseymcc/hunter/builds/464986453

I have submitted CI configs to https://github.com/ingenue/hunter targeting pkg.template branch,
see this merged pull request https://github.com/ingenue/hunter/pull/303

My change will resolve this "New package" request: https://github.com/ruslo/hunter/issues/757

This should be ready to go.

Testing:

https://ci.appveyor.com/project/ingenue/hunter/builds/20958561
https://travis-ci.org/ingenue/hunter/builds/467038058?utm_source=github_status&utm_medium=notification

Uploading

Upload failed because one of the dependency is not cacheable, see MySQL-client:

https://github.com/ruslo/hunter/blob/v0.23.72/cmake/projects/MySQL-client/hunter.cmake#L56-L57

I will remove cacheable attribute for now. Next the MySQL-client should be fixed or MySQL-client dependency removed by option like WITH_MYSQL_CLIENT=OFF.

I will remove cacheable attribute for now.

See https://github.com/ruslo/hunter/commit/231e56ca2191c4793fec81a6441902e3100e5fbc


fix typo in lidar_fake_perception.launch

Signed-off-by: mitsudome-r<EMAIL_ADDRESS>Bug fix
Fixed bug
Fixed typo in fake_lidar_perception.launch file under fake_lidar_perception package.
Fix applied
Fixed typo as following:
"publish_object" -> "publish_objects"
Steps To Reproduce
Before applying this fix:

cd ~/Autoware/ros/
./colcon_release
source ~/Autoware/ros/install/setup.bash
roslaunch lidar_fake_perception lidar_fake_perception.launch
roslaunch fails with

[/home/mitsudome-r/Autoware_test/ros/install/lidar_fake_perception/share/lidar_fake_perception/launch/lidar_fake_perception.launch] requires the 'publish_object' arg to be set
The traceback for the exception was written to the log file

After applying this fix

cd ~/Autoware/ros/
./colcon_release
source ~/Autoware/ros/install/setup.bash
roslaunch lidar_fake_perception lidar_fake_perception.launch
roslaunch launches successfully with following:

process[lidar_fake_perception-2]: started with pid [2439]
process[detection/fake_perception/fake_perception_visualization_01-3]: started with pid [2444]
[ INFO] [1558677408.372130024]: [visualize_detected_objects] objects_src_topic: /detection/fake_perception/objects
[ INFO] [1558677408.372773275]: [visualize_detected_objects] object_speed_threshold: 0.10
[ INFO] [1558677408.373339785]: [visualize_detected_objects] arrow_speed_threshold: 0.25
[ INFO] [1558677408.373946416]: [visualize_detected_objects] marker_display_duration: 0.20
[ INFO] [1558677408.374526975]: [visualize_detected_objects] label_color: {R:255.0, G:255.0, B:255.0, A:1.0}
[ INFO] [1558677408.375152576]: [visualize_detected_objects] arrow_color: {R:0.0, G:255.0, B:0.0, A:0.8}
[ INFO] [1558677408.375728170]: [visualize_detected_objects] hull_color: {R:51.0, G:204.0, B:51.0, A:0.8}
[ INFO] [1558677408.376283666]: [visualize_detected_objects] box_color: {R:51.0, G:128.0, B:204.0, A:0.8}
[ INFO] [1558677408.376866537]: [visualize_detected_objects] model_color: {R:190.0, G:190.0, B:190.0, A:0.5}
[ INFO] [1558677408.377438812]: [visualize_detected_objects] centroid_color: {R:77.0, G:121.0, B:255.0, A:0.8}
[ INFO] [1558677408.381215209]: [visualize_detected_objects] object_src_topic: /detection/fake_perception/objects
[ INFO] [1558677408.381827061]: [visualize_detected_objects] markers_out_topic: /detection/fake_perception/objects_markers

See also #2276

Didn't notice there was a duplicate


Recording the time for user

Creating a new database field for storing the time of user. We'll get an prediction on how much time is spent by the user for a particular search. In future we can release for premium version of LatteArt also and can provide a free trial version for the users to understand the workflow of the application.

I think, this is a good enhancement point. If possible, please record not only the time but also what kind of operation which users done.


feat: add allow missing field

Closes #59
This PR adds a new field to ColumnInfo called allow_missing. During validation, if we find that a column is missing, we check if allow_missing is set inside schema.column_infos[missing_column]. If True, we don't append an error.
Note that we need to check whether schema.column_infos.get(missing_column) is not None because the user may have requested a superfluous column (e.g., test_validators.test_validation_column_subset().

This would be super helpful to have.

Fix applied so allow_missing works with nested models.

I want to expand the the tests to include lists of structs - but I cannot add these tests until #100 has been merged.

A while back, @JakobGM and I spoke about using the following = None syntax to represent columns that are allowed to be missing:
class Foo(pt.Model):
    id: str
    optional_column: Optional[str] = None

I think I prefer your suggestion, since it is way more explicit, and I really had to think to remember the above suggestion.
I'm happy to merge this, great if you can add a test to cover the (now merged) #100 optional list of structs.

I believe the allow_missing syntax was your idea: https://github.com/JakobGM/patito/issues/59 - but yes, I prefer it too.
Sounds good - I'll get those tests added.

Bloody hell, clearly the lack of sleep has gotten to me a bit 😂 thank you for implementing this!

Tests updated and ready for review @thomasaarholt


Docs Page on Mobile Not Responsive

Description
Went to the docs page from my device and the docs sidebar covered up the contents, not a common thing with docusaurus docs.

Link to Reproduction
https://panda-css.com/docs
Steps to reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

JS Framework
No response
Panda CSS Version
0.3.2
Browser
Brave
Operating System

[ ] macOS
[ ] Windows
[ ] Linux

Additional Information
No response

Can't reproduce this at the moment. We'll keep an eye out for this issue.


Switch to tracing + flamegraphs 🔥 🔥

I was using log but the cool kids seem to be using tracing 😎
The big selling point for me is tracing-flame which means I can generate flamegraphs and start identifying bottlenecks 🧐
$ rm -rf .ditto   # with a clean build
$ DITTO_TRACE_DIR=.ditto/traces ditto make
$ cat .ditto/traces/* | inferno-flamegraph --flamechart > flamegraph.svg
PROFIT

Here's an example flamegraph for a cold build of https://github.com/ditto-lang/std/tree/9ecfe9785ff3c67ab78517b136b4cdc33d909ca1


Move selected state to model and select file names

Fixes #132.

Notes to self:

Expose isSelected, select, and deselect and fire a signal on those
Fix cut class handling
Make sure we aren't reading DOM classes outside of an event path

:shipit: after fixing comments


{AKS} Refactor 8th part of the update sub-command in acs module

Description

Refactor the update of windows profile

Unit Test Coverage

"covered_lines": 1642,
"num_statements": 1654,
"percent_covered": 99.27448609431681,
"missing_lines": 12,
"excluded_lines": 0

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

AKS


Broaden configuration options for Flask

Enables a relative instance directory, which prevents config and other artifacts from being dropped in he app/ folder with source code.
Add supports for loading config from instance/app.cfg or from arbitrary file pointed to by CONFIG_FILE environment variable.

Does this have an advantage over setting SERVER_NAME (for example) in your environment?

Not specifically for SERVER_NAME or the other settings that are configured to read from environment variables, but customizing one of the flags that aren't read from environment (e.g. POSTGRES_DB) or introducing new config parameters is currently not possible without altering the codebase (at minimum, in serve.py or in a WSGI wrapper).
The support for pyfile or envvar make it trivial to override or introduce new config options at runtime with no changes to the app code. This could be particularly useful in a container setup with distributed config management, where the container would pull down the desired config from centralized source at runtime.

I'm completely open to allowing all configuration options to be read from the environment.
With that said -- I think I would like to keep the entire application configuration there.
I usually maintain an .env file in my projects that I source before a deploy. You can even hook this into docker-compose if you're into that sort of thing.

That's fair -- to dynamically load any config key from the environment we'll need to pick some prefix, tomorrow I can work on changes to swap out the file-based configs from 209f3ec for a base class that reads any environment variable prefixed with FLASK_ and sets the corresponding instance variable in the config class, then we can inherit from that and provide the defaults as done in config.py today.

Heh, no need to reinvent the wheel here: brettlangdon/flask-env. I'll setup APP_ as the prefix instead of FLASK_ as the prefix to avoid confusion about what's for flask or used by the flask app.
Do you intend to maintain compatibility with Python2? If so I will also add a dependency on the future module: http://python-future.org/compatible_idioms.html#metaclasses

Do you intend to maintain compatibility with Python2?

Nope!


build docs doesn't seem to be working

Trying to build the docs from what I saw was being incorporated the other night and it's erroring out
First it errors out saying it wants node 23.1 but the project is using 22.xx.  I update to 23.1 using nvm and it still errors out.
Putting this here as a place holder - this needs more work.
eliza>$ pnpm build-docs

eliza@ build-docs /Users/davidjaramillo/Documents/Projects/eliza
pnpm --dir docs build

WARN  Unsupported engine: wanted: {"node":"23.1.0"} (current: {"node":"v22.11.0","pnpm":"9.12.3"})

<EMAIL_ADDRESS>build /Users/davidjaramillo/Documents/Projects/eliza/docs
docusaurus build

[INFO] [en] Creating an optimized production build...
[info] Loaded plugin typedoc-plugin-markdown
[error] The tsconfig file /Users/davidjaramillo/Documents/Projects/eliza/tsconfig.json does not exist
[ERROR] Error: Unable to build website for locale en.
at tryToBuildLocale (/Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/@docusaurus+core@3.5.2_@docusaurus+types@3.5.2_acorn@8.14.0_react-dom@18.2.0_react@18.2.0__re_e6f3ssmiin2uov5e54dllhgixm/node_modules/@docusaurus/core/lib/commands/build.js:54:19)
at async /Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/@docusaurus+core@3.5.2_@docusaurus+types@3.5.2_acorn@8.14.0_react-dom@18.2.0_react@18.2.0__re_e6f3ssmiin2uov5e54dllhgixm/node_modules/@docusaurus/core/lib/commands/build.js:65:9
at async mapAsyncSequential (/Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/@docusaurus+utils@3.5.2_@docusaurus+types@3.5.2_acorn@8.14.0_react-dom@18.2.0_react@18.2.0__r_ommau7el7tbopkaz2g33fzjgfi/node_modules/@docusaurus/utils/lib/jsUtils.js:21:24)
at async Command.build (/Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/@docusaurus+core@3.5.2_@docusaurus+types@3.5.2_acorn@8.14.0_react-dom@18.2.0_react@18.2.0__re_e6f3ssmiin2uov5e54dllhgixm/node_modules/@docusaurus/core/lib/commands/build.js:63:5) {
[cause]: Error: ENOENT: no such file or directory, scandir '/Users/davidjaramillo/Documents/Projects/eliza/src'
at Object.readdirSync (node:fs:1502:26)
at glob (/Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/typedoc@0.26.11_typescript@5.6.3/node_modules/typedoc/dist/lib/utils/fs.js:259:32)
at /Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/typedoc@0.26.11_typescript@5.6.3/node_modules/typedoc/dist/lib/utils/entry-point.js:207:38
at Array.flatMap ()
at expandGlobs (/Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/typedoc@0.26.11_typescript@5.6.3/node_modules/typedoc/dist/lib/utils/entry-point.js:206:31)
at getEntryPoints (/Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/typedoc@0.26.11_typescript@5.6.3/node_modules/typedoc/dist/lib/utils/entry-point.js:83:53)
at classThis.getEntryPoints (/Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/typedoc@0.26.11_typescript@5.6.3/node_modules/typedoc/dist/lib/application.js:299:53)
at classThis.convert (/Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/typedoc@0.26.11_typescript@5.6.3/node_modules/typedoc/dist/lib/application.js:321:38)
at generateTypedoc (/Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/docusaurus-plugin-typedoc@1.0.5_typedoc-plugin-markdown@4.2.9_typedoc@0.26.11_typescript@5.6.3/node_modules/docusaurus-plugin-typedoc/dist/plugin.js:99:31)
at async Object.pluginDocusaurus [as plugin] (/Users/davidjaramillo/Documents/Projects/eliza/node_modules/.pnpm/docusaurus-plugin-typedoc@1.0.5_typedoc-plugin-markdown@4.2.9_typedoc@0.26.11_typescript@5.6.3__/node_modules/docusaurus-plugin-typedoc/dist/plugin.js:40:9) {
errno: -2,
code: 'ENOENT',
syscall: 'scandir',
path: '/Users/davidjaramillo/Documents/Projects/eliza/src'
}
}
[INFO] Docusaurus version: 3.5.2
Node version: v22.11.0
 ELIFECYCLE  Command failed with exit code 1.
 ELIFECYCLE  Command failed with exit code 1.
eliza>$

Fixed, other issues but this one is gud


Whiteboarding - Pima org chart

Map out partner org chart to better understand team setup.

Org chart provided by Pima


Semi-supervised learning?

Thanks for writing this awesome library, only recently discovered it.
Do you have plans to support semi-supervised umap?
From my first try outs of your library, this is the fastest (h)umap implementation which has nndescent. I would like to use it for semi-supervised learning, too.

Hi!
I definitely plan plans for a semi-supervision p! There's a bunch of other stuff in the backlog that I have to organize.
I won't have time to work on it in the next few weeks...
Maybe at the end of October. Let me know if you want to help me with this.

I don't think I have the programming skills. I'm a useR reticulating around :) I think there is a bug in RStudio, I had to wrap the terminal, otherwise it crashed :P

That's totally fine! Keep coming with the good suggestions though :)

Sure, thanks for creating this great software. I'm on Manjaro. I had an install issue as well. I had the dependencies but could only install it after this command I found somewhere I can't remember. I'm not sure why. Somehow my OS did not know abut the Eigen lib, I guess.
sudo ln -s /usr/include/eigen3/Eigen /usr/include/Eigen

In particular, I was trying semi-supervised learning with umap-learn with 200k records and a few hundred classes (clusters), but it did not finish the job in reasonable time. I'm hoping a c++ library could do that.


2024.03.1 and 2024.06.0 releases are broken

access-om2-bgc 2024.03.1 and access-om2-bgc 2024.06.0 are built with hdf5 1.14.3 which contains a bug that prevents ACCESS-OM2-BGC from running.
The issue is fixed in hdf5 1.14.4, but this version is not yet available in the spack package.
What's the right way forward here? Revert to hdf5 1.14.2 for now?
Note, this issue also affects one ACCESS-OM2 release - see https://github.com/ACCESS-NRI/ACCESS-OM2/issues/74
Tasks

[x] Remove access-om2-bgc 2024.03.1 as a Release (but keep the tag for transparency)
[x] Remove access-om2-bgc 2024.06.0 as a Release (but keep the tag for transparency)
[x] Create the (first!) backport/2024.03 branch, which is where the 2024.03.* (namely, 2024.03.2) tags will live, since there is a 2024.06.0 in front in the history.
[x] Link PR for 2024.03.2 that addresses the above
[x] Link PR for 2024.06.1 that addresses the above (can be main branch)

Note: We have released a ACCESS-OM2-BGC 2024.07.0 that contains just the MOM5 WOMBAT bug fix. The above can still be done.


Search all controller mappings before trying to assign a default interaction

Search all controller mappings before trying to assign a default interaction mapping.

I'm not sure this makes sense, controller mappings are not transferable between controllers.   The only transference allowed is where it's the same controller can be used on different platforms.
Just allowing ANY mapping to be used on any controller, just because it's the same hand does not make sense to me.
Please correct me if I'm misunderstood the purpose of this PR

This is just addressing a bug in SetupConfiguration() where we only check the first entry of controllerMappings when looking for a mapping for the controller.


Evaluate the permission change for jackson-databind

In order to jackson-databind to be used in the server folder, the SHAs, licenses, and notices had to be removed from all plugins and modules.  They still have access to jackson through server, but the discovery-ec2 plugin also had the accessDeclaredMembers and suppressAccessChecks permissions in the build.gradle.  For the plugin to function properly with the jackson relocation, these permissions were added to the server build.gradle.  We need to evaluate whether there are any unintended consequences of adding these permissions.
Link to jackson relocation PR: https://github.com/opensearch-project/OpenSearch/pull/5366

Looks like GH hit a snafu, dup https://github.com/opensearch-project/OpenSearch/issues/5504


Upgrade plug to support latest phoenix

Hi, i was exploring pow and came across this issue, to fix this either i have to downgrade plug_cowboy from 2.0 to 1.0 or update the plug version condition. Tried both and both worked.
Thus the PR to fix deps.get issue with latest phoenix, (the  Plug version updated).

Thanks! I've relaxed the requirement to any version below 2.0.0 since that's what Phoenix does too.


[Kestrel] Re-enable trace-level test logging

Any idea how to find these logs in the new build? Do you have to download the entire build artifacts zip? I canceled it after 100mb.

Unless there's a failed test, you have to download the entire artifacts zip. In the build you linked to, it's 170mb.


Use local JQuery and fonts rather than Google hosted versions

Re: #396
Preview: http://dg0.dtrt.org/
@btcdrak Some quick testing shows that the main page for the site (one of its smallest pages) is about 270 KB with all resources and loading JQuery adds 90 KB, which seems reasonable to me but you know more about the server's bandwidth limitations.

We're fine on bandwidth. Moving the binaries there is gonna be orders of magnitude more than any site (though I'm actually surprised that jQuery is that large... Isn't there a "cut down" version with just what we need?).
Loading fonts locally would be nice too (as long as they're loaded last).
On July 5, 2017 1:22:12 PM EDT, "David A. Harding"<EMAIL_ADDRESS>wrote:

Re: #396
Preview: http://dg0.dtrt.org/
@btcdrak Some quick testing shows that the main page for the site (one
of its smallest pages) is about 270 KB with all resources and loading
JQuery adds 90 KB, which seems reasonable to me but you know more about
the server's bandwidth limitations.
You can view, comment on, or merge this pull request online at:
https://github.com/bitcoin-core/bitcoincore.org/pull/401
-- Commit Summary --

Use local JQuery rather than Google hosted version

-- File Changes --
M _includes/_scripts.html (3)
-- Patch Links --
https://github.com/bitcoin-core/bitcoincore.org/pull/401.patch
https://github.com/bitcoin-core/bitcoincore.org/pull/401.diff

Added locally-hosted copies of the same fonts we used before, now loaded from the end of the page footer.  Per Google, the font license is SIL 1.1 (license text contained within this commit).  Here's what the FSF says about it (source):

Since .ttf files have occasionally been used in to attack browsers, here are the wgets I ran in case anyone wants to verify this commit is providing faithful copies of the fonts:
wget https://fonts.gstatic.com/s/ptserif/v8/03aPdn7fFF3H6ngCgAlQzC3USBnSvpkopQaUR-2r7iU.ttf
wget https://fonts.gstatic.com/s/ptserif/v8/QABk9IxT-LFTJ_dQzv7xpJ0EAVxt0G0biEntp43Qt6E.ttf
wget https://fonts.gstatic.com/s/ptserif/v8/EgBlzoNBIHxNPCMwXaAhYPesZW2xOQ-xsNqO47m55DA.ttf
wget https://fonts.gstatic.com/s/ptsansnarrow/v7/Q_pTky3Sc3ubRibGToTAYjnFfol0SnfBMmbnmUK0fZM.ttf
wget https://fonts.gstatic.com/s/ptsansnarrow/v7/UyYrYy3ltEffJV9QueSi4UpeNX8RPf6i6WQfJWyCWEs.ttf

The preview is updated: http://dg0.dtrt.org

@TheBlueMatt regarding JQuery size, it looks like the minimal webserver bundled with Jekyll doesn't support gzip, so I was seeing the full file sizes.  My preview server dg0.dtrt.org does support gzip, and it shows JQuery as 32KB, which is the same size reported on the JQuery website.

I believe gzip is turned off on bitcoincore.org, though it's likely not useful to do so. We can turn it back on if it's worth a lot.
On July 5, 2017 3:41:08 PM EDT, "David A. Harding"<EMAIL_ADDRESS>wrote:

@TheBlueMatt regarding JQuery size, it looks like the minimal webserver
bundled with Jekyll doesn't support gzip, so I was seeing the full file
sizes.  My preview server dg0.dtrt.org does support gzip, and it shows
JQuery as 32KB, which is the same size reported on the JQuery website.

@TheBlueMatt please do re-enable gzip compression. That's a basic staple. It's not about your bandwidth costs, it's about page speed load time and gzip makes a big difference.

Indeed, I disabled it without thinking cause it would be bad if we had any dynamic content, but we don't on the main server.... Will do it when I get a chance.
On July 5, 2017 9:57:25 PM EDT, "฿tcDrak"<EMAIL_ADDRESS>wrote:

@TheBlueMatt please do re-enable gzip compression. That's a basic
staple. It's not about your bandwidth costs, it's about page speed load
time and gzip makes a big difference.

utACK

@harding I'll merge this tomorrow after server maintenance.


More logging

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 28.587%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

background/refreshdates.go
0
3
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
797

Relevant Lines:
2788

💛  - Coveralls


SLM finds an update of the  current version upon manual check

Describe the bug
SLM finds an update of the current version upon manual check
To Reproduce
Steps to reproduce the behavior:

Go to 'settings'
Click on 'check for updates'
See error

Expected behavior
It should not offer to download a newer version when there isn't one
Screenshots

Thank you for your report, it should be fixed on the next release.


Bootloader sdk v3.2 cannot load app -> Fatal exception (28): LoadProhibited (IDFGH-1002)

Environment

Development Kit:      none
Module or chip used:  ESP32-PICO-D4
IDF version v3.2
Build System:         Make
Compiler version crosstool-ng-1.22.0-80-g6c4433a
Operating System:     Linux
Power Supply:         USB

Problem Description
I migrated sdk from a255622 to v3.2 (286202c) and our bootloader build is not able to load application anymore. All build succeeds
The only thing I change in out bootloader source code is esp_image_load(ESP_IMAGE_LOAD,  to esp_image_verify(ESP_IMAGE_VERIFY,
I disable all secure boot
Expected Behavior
As seen below app:  text which is part of the app is shown. That is part of our application.
D (281) boot: Firmware update CRC @ 0x13fffc: 39a8d98a
I (287) boot: Calculating CRC32 for partition at 0x10000
D (293) bootloader_flash: mmu set block paddr=0x00010000 (was 0x00130000)
D (327) bootloader_flash: mmu set block paddr=0x00020000 (was 0x00010000)
D (354) bootloader_flash: mmu set block paddr=0x00030000 (was 0x00020000)
D (382) bootloader_flash: mmu set block paddr=0x00040000 (was 0x00030000)
D (409) bootloader_flash: mmu set block paddr=0x00050000 (was 0x00040000)
D (437) bootloader_flash: mmu set block paddr=0x00060000 (was 0x00050000)
D (464) bootloader_flash: mmu set block paddr=0x00070000 (was 0x00060000)
D (492) bootloader_flash: mmu set block paddr=0x00080000 (was 0x00070000)
D (520) bootloader_flash: mmu set block paddr=0x00090000 (was 0x00080000)
D (547) bootloader_flash: mmu set block paddr=0x000a0000 (was 0x00090000)
D (575) bootloader_flash: mmu set block paddr=0x000b0000 (was 0x000a0000)
D (602) bootloader_flash: mmu set block paddr=0x000c0000 (was 0x000b0000)
D (630) bootloader_flash: mmu set block paddr=0x000d0000 (was 0x000c0000)
D (657) bootloader_flash: mmu set block paddr=0x000e0000 (was 0x000d0000)
D (685) bootloader_flash: mmu set block paddr=0x000f0000 (was 0x000e0000)
D (712) bootloader_flash: mmu set block paddr=0x00100000 (was 0x000f0000)
D (740) bootloader_flash: mmu set block paddr=0x00110000 (was 0x00100000)
D (767) bootloader_flash: mmu set block paddr=0x00120000 (was 0x00110000)
D (795) bootloader_flash: mmu set block paddr=0x00130000 (was 0x00120000)
D (822) boot: Calculated CRC @ offset 0x10000: 0x39a8d98a
I (822) boot: Firmware CRC32 check OK (0x39a8d98a)
D (823) boot: Firmware verified succesfully
I (826) boot: Booting firmware at 0x00010000
I (831) boot: Disabling RNG early entropy source...
D (837) esp_image: reading image header @ 0x10000
D (842) bootloader_flash: mmu set block paddr=0x00010000 (was 0x00130000)
D (848) esp_image: image header: 0xe9 0x06 0x02 0x02 40080ef8
I (854) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x38e1c (232988) map
D (863) bootloader_flash: mmu set paddr=00010000 count=4
D (950) bootloader_flash: mmu set block paddr=0x00040000 (was 0xffffffff)
I (950) esp_image: segment 1: paddr=0x00048e44 vaddr=0x3ffb0000 size=0x035c8 ( 13768) load
D (955) bootloader_flash: mmu set paddr=00040000 count=1
D (965) bootloader_flash: mmu set block paddr=0x00040000 (was 0xffffffff)
I (967) esp_image: segment 2: paddr=0x0004c414 vaddr=0x40080000 size=0x00400 (  1024) load
D (976) bootloader_flash: mmu set paddr=00040000 count=1
D (982) bootloader_flash: mmu set block paddr=0x00040000 (was 0xffffffff)
I (988) esp_image: segment 3: paddr=0x0004c81c vaddr=0x40080400 size=0x037f4 ( 14324) load
D (997) bootloader_flash: mmu set paddr=00040000 count=2
D (1008) bootloader_flash: mmu set block paddr=0x00050000 (was 0xffffffff)
I (1009) esp_image: segment 4: paddr=0x00050018 vaddr=0x400d0018 size=0xa7e84 (687748) map
D (1018) bootloader_flash: mmu set paddr=00050000 count=11
D (1265) bootloader_flash: mmu set block paddr=0x000f0000 (was 0xffffffff)
I (1265) esp_image: segment 5: paddr=0x000f7ea4 vaddr=0x40083bf4 size=0x0cb20 ( 52000) load
D (1269) bootloader_flash: mmu set paddr=000f0000 count=2
D (1296) bootloader_flash: mmu set block paddr=0x00100000 (was 0xffffffff)
D (1296) esp_image: Calculated hash: 1a8e86c1
D (1296) bootloader_flash: mmu set paddr=00100000 count=1
D (1311) boot: Mapping segment 0 as IROM
D (1311) boot: Mapping segment 4 as DROM
D (1311) boot: calling set_cache_and_start_app
D (1314) boot: configure drom and irom and start
D (1319) boot: start: 0x40080ef8
I (1322) cpu_start: Pro cpu up.
I (1326) cpu_start: Single core mode
I (1330) heap_init: Initializing. RAM available for dynamic allocation:
I (1337) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (1343) heap_init: At 3FFC03C0 len 0001FC40 (127 KiB): DRAM
I (1350) heap_init: At 3FFE0440 len 0001FBC0 (126 KiB): D/IRAM
I (1356) heap_init: At 40078000 len 00008000 (32 KiB): IRAM
I (1362) heap_init: At 40090714 len 0000F8EC (62 KiB): IRAM
I (1369) cpu_start: Pro cpu start user code
I (45) cpu_start: Starting scheduler on PRO CPU.
I (78) p1_app: nvsstorage_init()[704][247864]: Checking partition "confprim"

Actual Behavior
D (480) boot: Firmware update CRC @ 0x13fffc: 39a8d98a
I (489) boot: Calculating CRC32 for partition at 0x10000
D (498) bootloader_flash: mmu set block paddr=0x00010000 (was 0x00130000)
D (2701) bootloader_flash: mmu set block paddr=0x00020000 (was 0x00010000)
D (4904) bootloader_flash: mmu set block paddr=0x00030000 (was 0x00020000)
D (7106) bootloader_flash: mmu set block paddr=0x00040000 (was 0x00030000)
D (9309) bootloader_flash: mmu set block paddr=0x00050000 (was 0x00040000)
D (11512) bootloader_flash: mmu set block paddr=0x00060000 (was 0x00050000)
D (13715) bootloader_flash: mmu set block paddr=0x00070000 (was 0x00060000)
D (15918) bootloader_flash: mmu set block paddr=0x00080000 (was 0x00070000)
D (18120) bootloader_flash: mmu set block paddr=0x00090000 (was 0x00080000)
D (20323) bootloader_flash: mmu set block paddr=0x000a0000 (was 0x00090000)
D (22526) bootloader_flash: mmu set block paddr=0x000b0000 (was 0x000a0000)
D (24729) bootloader_flash: mmu set block paddr=0x000c0000 (was 0x000b0000)
D (26932) bootloader_flash: mmu set block paddr=0x000d0000 (was 0x000c0000)
D (29135) bootloader_flash: mmu set block paddr=0x000e0000 (was 0x000d0000)
D (31338) bootloader_flash: mmu set block paddr=0x000f0000 (was 0x000e0000)
D (33541) bootloader_flash: mmu set block paddr=0x00100000 (was 0x000f0000)
D (35744) bootloader_flash: mmu set block paddr=0x00110000 (was 0x00100000)
D (37948) bootloader_flash: mmu set block paddr=0x00120000 (was 0x00110000)
D (40151) bootloader_flash: mmu set block paddr=0x00130000 (was 0x00120000)
D (42353) boot: Calculated CRC @ offset 0x10000: 0x39a8d98a
I (42364) boot: Firmware CRC32 check OK (0x39a8d98a)
D (42373) boot: Firmware verified succesfully
I (42379) boot: Booting firmware at 0x00010000
I (42387) boot: Disabling RNG early entropy source...
D (42401) esp_image: reading image header @ 0x10000
D (42409) bootloader_flash: mmu set block paddr=0x00010000 (was 0x00130000)
D (42422) esp_image: image header: 0xe9 0x06 0x02 0x02 40080ef8
I (42433) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x38e1c (232988) map
D (42450) bootloader_flash: mmu set paddr=00010000 count=4 size=38e1c src_addr=10020 src_addr_aligned=10000
D (49001) bootloader_flash: mmu set block paddr=0x00040000 (was 0xffffffff)
I (49014) esp_image: segment 1: paddr=0x00048e44 vaddr=0x3ffb0000 size=0x035c8 ( 13768)
D (49031) bootloader_flash: mmu set paddr=00040000 count=1 size=35c8 src_addr=48e44 src_addr_aligned=40000
D (49438) bootloader_flash: mmu set block paddr=0x00040000 (was 0xffffffff)
I (49451) esp_image: segment 2: paddr=0x0004c414 vaddr=0x40080000 size=0x00400 (  1024)
D (49467) bootloader_flash: mmu set paddr=00040000 count=1 size=400 src_addr=4c414 src_addr_aligned=40000
D (49518) bootloader_flash: mmu set block paddr=0x00040000 (was 0xffffffff)
I (49531) esp_image: segment 3: paddr=0x0004c81c vaddr=0x40080400 size=0x037f4 ( 14324)
D (49547) bootloader_flash: mmu set paddr=00040000 count=2 size=37f4 src_addr=4c81c src_addr_aligned=40000
D (49971) bootloader_flash: mmu set block paddr=0x00050000 (was 0xffffffff)
I (49983) esp_image: segment 4: paddr=0x00050018 vaddr=0x400d0018 size=0xa7e84 (687748) map
D (50001) bootloader_flash: mmu set paddr=00050000 count=11 size=a7e84 src_addr=50018 src_addr_aligned=50000
D (69263) bootloader_flash: mmu set block paddr=0x000f0000 (was 0xffffffff)
I (69276) esp_image: segment 5: paddr=0x000f7ea4 vaddr=0x40083bf4 size=0x0cb20 ( 52000)
D (69293) bootloader_flash: mmu set paddr=000f0000 count=2 size=cb20 src_addr=f7ea4 src_addr_aligned=f0000
D (70770) bootloader_flash: mmu set block paddr=0x00100000 (was 0xffffffff)
D (70785) esp_image: Calculated hash: 1a8e86c1816c2302a741b4aff11d7923ea9193e4b8b36bebdcb05017a5be8140
D (70798) bootloader_flash: mmu set paddr=00100000 count=1 size=20 src_addr=1049d0 src_addr_aligned=100000
D (70821) bootloader_flash: mmu set paddr=00100000 count=1 size=20 src_addr=1049d0 src_addr_aligned=100000
D (70851) boot: Mapping segment 0 as IROM
D (70857) boot: Mapping segment 4 as DROM
D (70863) boot: calling set_cache_and_start_app
D (70870) boot: configure drom and irom and start
D (70879) boot: start: 0x40080ef8
I (70886) Fatal exception (28): LoadProhibited
epc1=0x40008044, epc2=0x00000000, epc3=0x00000000, excvaddr=0x000008e6, depc=0x00000000

Behavior changes I notice are below.

printout between bootloader_flash: mmu set block paddr texts is much slower
printout between esp_image: segment  is also much slower
esp_image: Calculated hash:  prints the entire hash (early sdk prints only the first 8)
Bootloader.bin size grows from 22KiB to 24 KiB

Partition table
#Name,          Type,   SubType,    Offset,     Size
# not used,     ,       ,           0x0,        0x1000
#stage2_bl,     app,    bl,         0x1000,     0x7000
#partitions,    data,   pt,         0x8000,     0x1000
nvs,            data,   nvs,        0x9000,     0x4000
otadata,        data,   ota,        0xD000,     0x3000
firmware_0,     app,    ota_0,      0x10000,    0x130000
firmware_1,     app,    ota_1,      0x140000,   0x130000
confprim,       data,   nvs,        0x3A0000,   0xC000
confback,       data,   nvs,        0x3AC000,   0xC000

Hi @farizadp, could you please attach the .map and .elf files of the bootloader?

Sure, here you go
bootloader.zip

@igrr : What kind of things I can expect to find in the map file related to the issue?

Did it really take 70 seconds or is the clock messed up?

@farizadp My plan was to:

check that there are no functions called from the image loading stage which are placed into .text segment, they should be in .iram_loader.text segment. See https://github.com/espressif/esp-idf/blob/a20d02b7f196c407bc9f39b781e31a0a4f665968/components/bootloader/subproject/main/esp32.bootloader.ld#L35-L69

convert the bootloader to a .bin file, flash it onto a board, and then debug it over JTAG

With regards to step 1, i have noticed three functions which normally seem to be not present in IDF bootloader: verify_firmware, get_signed_crc32, calculate_crc32. Are you using a customized bootloader? If yes, please note that the bootloader component has been reorganized between IDF v3.1 and v3.2. I have also noticed that the functions in the ELF file resemble ESP-IDF v3.1 bootloader, not v3.2 bootloader.
For correct operation, you may need to redo your modifications on top of a stock v3.2 bootloader. The positive thing about this is that it should now be much easier to modify the bootloader, as only the top level logic is now located in the bootloader component. The support functions are in bootloader_support, so it should now be easier to update IDF to new version without losing any changes.
With regards to step 2, unfortunately I couldn't reproduce the issue, as the firmware is not getting loaded seemingly due to the added check.
I (31) boot: Starting PT ESP32 2nd stage bootloader
...
E (270) boot: 'entry_point' equals nullptr, error initializing boot partition
E (280) boot: No valid firmware found, aborting boot and exiting.
user code done

@igrr : Thanks, and yes those functions are created by us specifically for our application. And yes, we thought that updating only the SDK and replacing deprecated functions used by our implementation would be sufficient.
In that case, we'll try to re-implement our bootloader functionality on top of v3.2. Will this always be the case for future SDK releases?

Hi @farizadp,
Sorry for the delay between responses. Did you get the bootloader working correctly in v3.2?

In that case, we'll try to re-implement our bootloader functionality on top of v3.2. Will this always be the case for future SDK releases?

This is our mistake that we didn't highlight the potential for breaking changes due to the bootloader refactoring in v3.2. Sorry about that.
The idea behind the bootloader refactoring is to present a clearer public API via the bootloader_support component for all major functions of the bootloader, so the ESP-IDF default "bootloader" subproject itself becomes a minimal implementation that mostly calls bootloader_support functions.
This means that a custom bootloader can be created without needing to directly modify much ESP-IDF internal code. A custom bootloader that only uses the bootloader_support API, plus custom code that calls bootloader_support API functions, should not break during future minor IDF updates. If the bootloader_support API behaviour has breaking changes as part of a major IDF update then we'll flag it as a breaking change in the release notes. (IDF version policy is here).
If a custom bootloader involves changing or replacing the implementation of the bootloader_support component, rather than only calling the APIs in bootloader_support, then it'll need to be checked carefully during each update as the implementation may have changed between releases.
If you have particular requirements regarding bootloader customization that are awkward even after the refactoring in v3.2, then please open a new issue with as many requirements details as you can provide, and we'll try to find ways to support it in the future.

@farizadp Thanks for reporting, would you please help share if you get the bootloader working correctly in v3.2? Thanks.

We put this issue on hold for now. I close this thread for now (may be reopened later on)


Incorrect void type check in registry's assure function

The changes made in commit https://github.com/skypjack/entt/commit/d5613e8c6576b98c4fa2998434a1e8b535a3bdb1 seem to be a typo. Referencing the other "use is_void_v as needed" commits, the correct substitution should be std::is_void_v<Type>.

 Good catch! Thanks. 👍


So cool!!

thank you and any suggestions or contributions are welcome :)

This is an auto-response. Thanks for your E-mail.

This is an auto-response. Thanks for your E-mail.


Investigate state transition performance

Describe the bug
In the profiler result below, Root comparison and state.setStateCachesAsPersistent seems to be too high compared to others:

We need to analyse why and if we can improve it

Benchmark for Root equals check:
Currently block.stateRoot is tree backed
test ssz equal                                                         17778.09 ops/s      56.24900 us/op 264549 runs    15.01 s

If I use block.stateRoot.valueOf() as Uint8Array it's 3.5 times faster:
test ssz equal using valueOf()                                         63673.99 ops/s      15.70500 us/op 933370 runs    15.03 s

seems like this is related to https://github.com/ChainSafe/ssz/issues/83
also, we use ssz.Root.equals() in a lot of places, we need to either apply the pattern to all places or fix the above ssz issue.


[TACHYON-990] Executor dependencies provided from under file system

https://tachyon.atlassian.net/browse/TACHYON-990
In current version, assuming  tachyon binaries and java is installed and are already in mesos slaves but may not be in practice. Executor dependencies provided from distributed file system or some server.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5116/
Test PASSed.

Aslan, thank you for the PR. It looks good to me. Before we merge it, let me set up buckets with the necessary artifacts so that we can test it with defaults that work.

Perfect. Really glad to hear that. Please test it, and let me know for any question, then I will create other PRs. Thanks @jsimsa .

I have uploaded all the artifacts to the following bucket: s3.amazonaws.com/tachyon-mesos

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5311/
Test PASSed.

@jsimsa , did you have a chance to test this PR?

You should be able to test it yourself using virtualbox locally to emulate a small cluster. The instructions for how to do that with Tachyon can be found here: http://tachyon-project.org/documentation/master/Deploy-Module.html.
In any case, I will try to find some time today to test it myself.

I was able to run some tests and it seems that your PR does not work. Here what you can do to reproduce my results:
First, you will have to change your PR in two places:

Replace

tachyon.integration.mesos.executor.dependency.path=https://s3.amazonaws.com/bucketname/foldername/
tachyon.integration.mesos.jre.url=https://bucketname/java/jre-7u76-linux-x64.tar.gz
tachyon.integration.mesos.jre.version=jre1.7.0_76

with
tachyon.integration.mesos.executor.dependency.path=https://s3.amazonaws.com/tachyon-mesos/
tachyon.integration.mesos.jre.url=https://s3.amazonaws.com/tachyon-mesos/jre-7u79-linux-x64.tar.gz
tachyon.integration.mesos.jre.version=jre1.7.0_79

Replace tachyon.tgz with tachyon.tar.gz.

Next, download and install Mesos to your machine and start both the Mesos master and slave. Use the master UI to make sure the slave have successfully connected to the master.
Next, run the Tachyon framework with your modifications (and the above changes), pointing it to the Mesos master running on your machine. You should see that the framework successfully connects and schedules the tasks. However, after the tasks fetch the URIs, they fail.
I believe the issue lies in the way you set up the command to be executed. In particular, I don't think that the command behaves like shell in the sense that it understands environment variables. Instead, you will have to specify environment variables through a separate proto field. In addition, I am not sure you can assume that the task will execute in the same directory in which the URIs are downloaded to and so you should use an absolute and not a relative path to the tachyon.
Hope this gives you enough information to make progress.

Thanks for your comments @jsimsa.
My prediction is that, this is because of step 2. (Replace tachyon.tgz with tachyon.tar.gz). Because it is it tries to find "dependency_path/tachyon.tgz" and it could not, that is why it fails. Can you retry with tachyon.tgz instead of tar.gz?

I checked that tachyon.tar.gz is found and extracted correctly.

Hey @jsimsa , I tried it on my side, and seems ok. Can you please share exception trace in stderr, stdout in the sandbox of task?

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5619/
Test FAILed.

Per offline discussion with @aslanbekirov, will create a new PR for this.


Remove unused resources to avoid conflicts

The main goal of this PR is to remove the unused app_name string from the library module.
The problem happens when the library is added into a project, and app_name is not defined is the root module. In that case, gradle doesn't know which definition of app_name is more important, so it might device to use Tour Guide as app_name :(
app_name is unused anyway, so I thought I could remove it to avoid confusion.
As for ic_launcher1, I just saw it was unused so I thought it's be ok to remove it to avoid conflicts and save some space.
note: tests run ok in my machine

thanks mikel !! @akaita


Instead of building cint, could you please depend on the pre-built cint package?

See the BUILD_LIBCINT option that clones cint: https://github.com/pyscf/pyscf/blob/master/pyscf/lib/CMakeLists.txt#L125
Despite  BUILD_LIBCINT being an option, build fails with BUILD_LIBCINT=OFF.

You can use the pre-build binaries the CI pipeline uses.
https://github.com/pyscf/pyscf/blob/master/.github/workflows/ci_linux/build_pyscf.sh
The prebuild binaries are linked to libblas3 the system default blas library. It performs really slow. If you compile pyscf with this version, pyscf functions might be linked to the libblas3.

I assume it should be possible to use a more efficient version in Debian/Ubuntu. In Fedora we use flexiblas to be able to switch between implementations; I think debuntu relies on alternatives but one might be able to pick the right version just by explicitly specifying OpenBLAS to be installed..?

You can use the pre-build binaries the CI pipeline uses.

I can't use pre-built binaries because I build packages on FreeBSD and (1) they have to always build from source, (2) no binaries are available for FreeBSD anyway.
I'm just interested in using external ```cint`` package instead of bundled one.

You can use the pre-build binaries the CI pipeline uses.

I can't use pre-built binaries because I build packages on FreeBSD and (1) they have to always build from source, (2) no binaries are available for FreeBSD anyway.
I'm just interested in using external cint package instead of bundled one.

This is already supported by the build system; e.g. in Fedora PySCF is built separately from libcint/qcint. Just turn off the build of libcint
cmake -DBUILD_LIBCINT=OFF

and it will use the system library.

Hi @yurivict , has this been resolved?

Do you have error messages or outputs related to the problem you faced? If you manually compiled and install libcint to certain system library path, then compiling pyscf with -DBUILD_LIBCINT=OFF should automatically link to the external libcint library.


Ignore import assertions (e.g., CSS and JSON modules)

Adds the acorn-import-assertions plugin to allow JSON and CSS (etc.) modules to be parsed correctly. Currently ignores these files, but happy to take a different tack if you'd rather the system just skip recursion on them instead.
Fixes #2

This was fixed upstream in acorn v8.14.0, shipping with v1.0.1 of this package: https://github.com/acornjs/acorn/blob/master/acorn/CHANGELOG.md#8140-2024-10-27


Dropdown design

https://www.figma.com/file/5JBhCbve90PJPO8c0kd0G3/Swap-App?type=design&node-id=346%3A16301&t=8ieYLdJXWfcj5da9-1

@smitch88 Can you soften the drop shadow and add more blur
box-shadow: 0px 4px 4px 0px #00000040;
And move to the left so the right side lines up with the right side of the button,
Reduce font size to 12px
Fleek:

@smitch88 can you speed up the arrow animation on the APY dropdown to make it more snappy or just make the transition instant


add local windows dev support using make windows

Overview
This PR includes the following proposed change(s):

Create new docker-compose for windows
Update makefile with windows scripts
Update default port of api when running locally to match that in .env
Update api package.json to include a nodemon windows build/run rule

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Version change

How Has This Been Tested?
Manual testing in Windows
Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have made corresponding changes to the documentation
[X] New and existing unit tests pass locally with my changes

Closing, couldn't get it working reliably in time. Need to move onto other things.


chore(main): release 0.5.0

:robot: I have created a release beep boop
0.5.0 (2024-08-21)
Miscellaneous Chores

release 0.5.0 (1170eee)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.5.0
:sunflower:


platformer_stock_B game window variables and text

Replaced constants 1080 and 576 with assigned variables to allow different game resolutions, which resolves #11
Pause text has positioning relative to these assigned variables to follow the set resolution, which resolves #10

Also removed music text displaying the current soundtrack name since it's not needed in most games, but can be easily added in if required.


[Bug] zk3.4.6+dolphinscheduler3.1.1 deployment error

Search before asking

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

What happened
官网文档说是zk3.4.6+即可 但是zk3.4.6+dolphinscheduler3.1.1部署报错
原因是dolphinscheduler 3.0.2 和 3.1.0 以上的zk 驱动都是 3.8.0 的，所有安装时候需要zk 新版本 才能解决此问题
What you expected to happen

How to reproduce
zk3.4.6+dolphinscheduler3.1.1部署 启动时会直接报错
Anything else
No response
Version
3.1.x
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Need to upgrade zk to 3.8.x.


Coins Mcdonald has shared a file with you

https://acrobat.adobe.com/id/urn:aaid:sc:VA6C2:27f8ba0b-53e3-4d4c-a844-fa9a3499af36

22nd century stuff!

@CodeAWS1
Please Note, GitHub forum is dedicated for Microsoft documentation related issues.
It would be great if you could elaborate your query and add a link to the Microsoft documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!


Calendar fails to load

Mostly the team drop down is empty for some users. In the console, there is clearly an exception related to a team id:
First a 404 on this url:
https://telindus.visualstudio.com/_apis/projects/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/teams/fb1b89e9-2900-4f42-b748-d4a89eb1fdeb

Then this error
Uncaught (in promise) TFS.WebApi.Exception: The team with id 'fb1b89e9-2900-4f42-b748-d4a89eb1fdeb' does not exist, or you do not have permission to access it.
    at Object.<anonymous> (https://ms-devlabs.gallerycdn.vsassets.io/extensions/ms-devlabs/team-calendar/2.0.16/1579110530797/dist/Calendar.js:94:24025)
    at https://ms-devlabs.gallerycdn.vsassets.io/extensions/ms-devlabs/team-calendar/2.0.16/1579110530797/dist/Calendar.js:94:22573
    at Object.next (https://ms-devlabs.gallerycdn.vsassets.io/extensions/ms-devlabs/team-calendar/2.0.16/1579110530797/dist/Calendar.js:94:22678)
    at a (https://ms-devlabs.gallerycdn.vsassets.io/extensions/ms-devlabs/team-calendar/2.0.16/1579110530797/dist/Calendar.js:94:21424)

As a consequence, the drop down is empty:

Im project admin, and org admin so permission is not the issue. I believe it relates to a team Id I was part of, then the team was deleted but the id is still in my profile
Any help would be appreciated

I have exactly the same problem. The calendar was working fine, then I removed a team (non-default) that we weren't using anymore and now the calendar view is empty and I can't select the default team :(

After digging into the code of the calendar, I have found a workaround that worked for all team members:

go to https://.visualstudio.com/_apis/projects//teams

where
INSTANCENAME = your instance
PROJECTID= your project id (should be a guid)
PROJECTNAME = you project Name

From this, you will get a json of all teams and their ids

Take the guid id of a valid team then go to https://.visualstudio.com//_apps/hub/ms-devlabs.team-calendar.team-calendar?team=

When you use this link once, the menu entry works permanently
It appears the id of the team you used last time is somehow stored somewhere.
This of course is just a workaround to get the calendar working again.

Works! Thanks a lot!

Appears to be the same as #374


test_replay.cc: reduce the time of code execution

Probably cut the time in half, at least.

I don't think we want to stop testing the cameras entirely. But with how catch2 works, we are currently downloading everything twice. The part above "SECTION" is run for every test. If we can make it only download once, we could halve our runtime and still test everything


Always getting this error!!

Install : node-red-contrib-tensorflow 0.3.1
2022-10-12T06:12:43.465Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict<EMAIL_ADDRESS>2022-10-12T06:12:43.937Z [err] npm
2022-10-12T06:12:43.937Z [err]  WARN config production Use --omit=dev instead.
2022-10-12T06:12:54.950Z [err] npm
2022-10-12T06:12:54.950Z [err] WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
2022-10-12T06:12:55.017Z [err] npm
2022-10-12T06:12:55.017Z [err] WARN deprecated<EMAIL_ADDRESS>request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
2022-10-12T06:12:55.363Z [err] npm WARN
2022-10-12T06:12:55.363Z [err] deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
2022-10-12T06:12:55.499Z [err] npm
2022-10-12T06:12:55.499Z [err] WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
2022-10-12T06:13:07.561Z [err] npm ERR!
2022-10-12T06:13:07.561Z [err] code 1
2022-10-12T06:13:07.561Z [err] npm ERR! path /home/vcap/app/.node-red/node_modules/@tensorflow/tfjs-node
2022-10-12T06:13:07.571Z [err] npm ERR! command failed
2022-10-12T06:13:07.571Z [err] npm ERR! command sh -c node scripts/install.js
2022-10-12T06:13:07.571Z [err] npm ERR! CPU-linux-3.20.0.tar.gz
2022-10-12T06:13:07.571Z [err] npm ERR! https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-linux-x86_64-2.7.3.tar.gz
2022-10-12T06:13:07.571Z [err] npm ERR! * Downloading libtensorflow
2022-10-12T06:13:07.571Z [err] npm ERR! node:events:505
2022-10-12T06:13:07.571Z [err] npm ERR!       throw er; // Unhandled 'error' event
2022-10-12T06:13:07.571Z [err] npm ERR!       ^
2022-10-12T06:13:07.571Z [err] npm ERR!
2022-10-12T06:13:07.571Z [err] npm ERR! Error: ENOSPC: no space left on device, write
2022-10-12T06:13:07.571Z [err] npm ERR! Emitted 'error' event on Unpack instance at:
2022-10-12T06:13:07.571Z [err] npm ERR!     at Unpack.onerror (node:internal/streams/readable:773:14)
2022-10-12T06:13:07.571Z [err] npm ERR!     at Unpack.emit (node:events:527:28)
2022-10-12T06:13:07.571Z [err] npm ERR!     at Unpack.warn (/home/vcap/app/.node-red/node_modules/tar/lib/warn-mixin.js:7:12)
2022-10-12T06:13:07.571Z [err] npm ERR!     at Unpack.[onError] (/home/vcap/app/.node-red/node_modules/tar/lib/unpack.js:325:12)
2022-10-12T06:13:07.571Z [err] npm ERR!     at WriteStream. (/home/vcap/app/.node-red/node_modules/tar/lib/unpack.js:381:20)
2022-10-12T06:13:07.571Z [err] npm ERR!     at WriteStream.emit (node:events:527:28)
2022-10-12T06:13:07.571Z [err] npm ERR!     at WriteStream.[_onerror] (/home/vcap/app/.node-red/node_modules/fs-minipass/index.js:234:10)
2022-10-12T06:13:07.571Z [err] npm ERR!     at WriteStream.[_onwrite] (/home/vcap/app/.node-red/node_modules/fs-minipass/index.js:296:21)
2022-10-12T06:13:07.571Z [err] npm ERR!     at /home/vcap/app/.node-red/node_modules/fs-minipass/index.js:291:21
2022-10-12T06:13:07.571Z [err] npm ERR!     at FSReqCallback.wrapper [as oncomplete] (node:fs:805:5) {
2022-10-12T06:13:07.571Z [err] npm ERR!   errno: -28,
2022-10-12T06:13:07.571Z [err] npm ERR!   code: 'ENOSPC',
2022-10-12T06:13:07.571Z [err] npm ERR!   syscall: 'write'
2022-10-12T06:13:07.571Z [err] npm ERR! }
2022-10-12T06:13:07.571Z [err]
2022-10-12T06:13:07.571Z [err] npm ERR! A complete log of this run can be found in:
2022-10-12T06:13:07.571Z [err] npm ERR!     /home/vcap/app/.npm/_logs/2022-10-12T06_12_43_893Z-debug-0.log
2022-10-12T06:13:07.630Z rc=1

@ujjwalkuikel Thank you for using the TensorFlow.js node! I thought that you are using Cloud Foundry like IBM Cloud. Could you use the normal Node-RED environment on your local PC?


Please support variables from less/sass.

Man, first of all, this is really a life saver. Big thx, I really like it. My only problem, atm is, that if I have this inside a file called _variables:
$grey-normal: #eee;
$grey-hover: #fff;
$grey-click: #aaa;

everything is fine and it works, when I import this file into an other and I use this:
background-color: $grey-normal.

it doesn't resolve the variable value. This would be a nice enhancement too.
Regards
Chris

Hi Chris,
Now, this plugin doesn't check color values per mime-type. Search just color value literals.
So, at first this plugin has to check a mime-type, then has to check all variables whether they have a color literal using a lexer/parser for less/sass, finally has to check whether the current line has the variables if implement your request.
I'm not sure whether I can do it soon. But I understood your request.
Thanks,
Junichi

Anything new here?

Fixed. https://github.com/junichi11/netbeans-color-codes-preview/releases/tag/v0.8.0
Note: Resolve the simplest cases only: e.g. $green: #0f0; Then, in this case the popup does not work. I won't fix it.


Integrate standard.js

https://standardjs.com
Should we ditch the eslint configs?
What about eslint-compat which provides nice info if using features not compatible with supported browsers?
What about eslint polyfills?

Closing this since the repo moved to https://github.com/orbitdb/orbit-web


Add character: Chapolin

Hero Description
Chapolin Colorado is a clumsy, fearful and clumsy hero, who always appears when someone needs it. With his bionic sledgehammer and shrinking pill, it often causes more confusion than it necessarily helps.
Concept Art

Inspiration
I will use Chapolin's own skills. Like a paralyzing horn, Naniconin pills and sledgehammer.
Moves
Idle

[STICK] Walk

[LEFT] Hammered
Hammered. Every third attack, does a lot of damage and pushes back.

Reference:

[MIDDLE] Standstill horn
Paralyzes opponent. It will be a very strong paralysis, with a considerable time

Reference:

[RIGTH] Nanicoline Pill
Chapolin swallows a nanicoline pill, getting small and going through obstacles.
Chapolin will stay in this size for 3 seconds and will increase in speed. During that time you will not be able to use other skills
(Chapolin ficará nesse tamanho por 3 segundos e terá aumento de velocidade. Durante esse tempo não poderá usar outras habilidades)

Reference:

[Q] vinyl antennas
Chapolin uses its vinyl antennas, detecting attacks and staying unusable for 5 seconds
(Chapolin utiliza suas antenas de vinil, detectanto ataques e ficando invuneravel por 5 segundos)

The walk, idle, left, midle animations
OPTIONAL
[E] TAUNT

Reference:

[SPACE]/Shift extra skill, usually dash
Tasks

[x] Idle
[x] Walk
[ ] Hurt
[x] [LEFT] add skill name
[x] [MIDDLE] add skill name
[x] [RIGHT] add skill name
[ ] [Q] add skill name

Approved for work!

11/05/2020 a 14/05/2020
ISSUE. Modeling and animation: idle, walk, LEFT

15h

18/05/2020 a 21/05/2020
middle, rigth, taunt, ultimate

17:30h


[#76] Generating backup keys Step 1 and 2

I made a PR to your PR and made comments on https://github.com/Kyrrui/UniversalLoginSDK/pull/1

@alexvandesande Perhaps you can make some UI touch ups to the brain wallet generation, as they take a while to load and currently the only info given to the user is "loading...". Also when it is loading we should gray out the set as backup button if possible.

Is this PR superseded by https://github.com/EthWorks/UniversalLoginSDK/pull/85 ? In that case, can I close this?


[Feature][UI] add future cron tab run times button

Purpose of this pull request

add future cron tab run times button

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] Change does not need document change

update style


nano 2.4

The patch for devel-2.3.6 has been fixed in 2.4 - so removed.
A minor patch is required to compile v2.4 on Mac OS X.
see https://savannah.gnu.org/bugs/?44609 .
(replaces #444)

Sorry for the delay in pulling this! When building locally I couldn't repro the glib requirement, so I'm testing another PR.

Not sure why this one worked fine! Merged, sorry again!


Fixed error on _id search with comma separated values

Fixes https://app.asana.com/0/1201910659736001/1202276096220382/f

Coverage increased (+0.0004%) to 94.466% when pulling dbce1d8f92ecd5dcbf36b3f9f0ac5b38fb7ab9c8 on cody-id-comma-separated into 6ef488b1aba04a9aaf7cb8c6edb9e0ca0829aa46 on main.


First pass at incemental visual improvement.

Put suite title in header
Add footer
Have 'run_as_group' auto-collapsed in tree menu
Favor 'short_title' in tree menu if available
Move 'about' test group description higher, put more emphasis on run button
Add title of test you are running in the input modal
Add input instructions in input modal, if available

WIP screenshot:

Codecov Report

Merging #85 (016526f) into main (039e030) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #85   +/-   ##
=======================================
  Coverage   94.08%   94.08%
=======================================
  Files         100      100
  Lines        2467     2467
=======================================
  Hits         2321     2321
  Misses        146      146

Continue to review full report at Codecov.

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


Change model (#9)

Codecov Report

Merging #10 (877a01e) into main (65c7462) will decrease coverage by 6.58%.
The diff coverage is 40.00%.

: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
@@              Coverage Diff              @@
##                main      #10      +/-   ##
=============================================
- Coverage     100.00%   93.42%   -6.58%
- Complexity        92      101       +9
=============================================
  Files             25       27       +2
  Lines            333      365      +32
=============================================
+ Hits             333      341       +8
- Misses             0       24      +24

Impacted Files
Coverage Δ

...tion/Shopping/Query/GetShoppingListByUuidQuery.php
0.00% <0.00%> (ø)

...opping/Query/GetShoppingListByUuidQueryHandler.php
0.00% <0.00%> (ø)

src/Domain/Shopping/ShoppingList.php
87.50% <0.00%> (-12.50%)
:arrow_down:

...ine/Repository/Shopping/ShoppingListRepository.php
54.16% <8.33%> (-45.84%)
:arrow_down:

...Controller/Shopping/SaveShoppingListController.php
84.37% <54.54%> (-15.63%)
:arrow_down:

...ation/Shopping/Command/SaveShoppingListCommand.php
100.00% <100.00%> (ø)

...hopping/Command/SaveShoppingListCommandHandler.php
100.00% <100.00%> (ø)

...cation/User/Command/RegisterUserCommandHandler.php
100.00% <100.00%> (ø)

...stence/Doctrine/Repository/User/UserRepository.php
100.00% <100.00%> (ø)

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


charts: broken chart v0.23.1 - no container images available

A Helm chart version 0.23.1 was released a while back to update some chart information.
Without realizing this needed to be accompanied by images in the container registry for v0.23.1, it turns out this completely broke the helm chart.
Since we're not likely to actually release a v0.23.1 for everything, the approach might just be to tag the existing v0.23.0 images with v0.23.1. This would be highly hackish, but it will have to suffice for now, and learn this lesson moving forward.

helm can now pull images for v0.23.1, even if these are essentially the same as v0.23.0 :shrug:


Initial release of cosmos-sdk-proto

This pull request contains the first release of cosmos-sdk-proto, an upstream crate containing proto definitions for Cosmos sdk blockchains.
Currently cosmos-sdk-proto is more of a renamed ibc-proto crate with only a few changes to the build process. Most of the task of this pull request is to get the repo setup and really kickstart contributions to this repo.
TODO:

[x] Add representative from Iqlusion as a crate owner
[x] Add representative from Informal as a crate owner
[ ] Approval for merge

🍾


more arrow separators?

from Catalyst.jl, they use the following arrows for their DSL: (stored as a Set{Symbol} in catalyst, converted to Vector{Char} here)
fwd_arrows = ['>', '→', '↣', '↦', '⇾', '⟶', '⟼', '⥟', '⥟', '⇀', '⇁', '⇒', '⟾']
bwd_arrows = ['<', '←', '↢', '↤', '⇽', '⟵', '⟻', '⥚', '⥞', '↼', '↽', '⇐', '⟽']
double_arrows = ['↔', '⟷', '⇄', '⇆', '⇔', '⟺']
pure_rate_arrows = ['⇐', '⟽', '⇒', '⟾', '⇔', '⟺']
equal_sign = ['='] #not used in catalyst, but used here

defining:
const EQUALCHARS = vcat(fwd_arrows,bwd_arrows,double_arrows,pure_rate_arrows,equal_sign)

would extend automatically the amount of separators used.

the julia parser, as of 1.6,  supports the following arrows :
(← → ↔ ↚ ↛ ↞ ↠ ↢ ↣ ↦ ↤ ↮ ⇎ ⇍ ⇏ ⇐ ⇒ ⇔ ⇴ ⇶ ⇷ ⇸ ⇹ ⇺ ⇻ ⇼ ⇽ ⇾ ⇿ ⟵ ⟶ ⟷ ⟹ ⟺ ⟻ ⟼ ⟽ ⟾ ⟿ ⤀ ⤁ ⤂ ⤃ ⤄ ⤅ ⤆ ⤇ ⤌ ⤍ ⤎ ⤏ ⤐ ⤑ ⤔ ⤕ ⤖ ⤗ ⤘ ⤝ ⤞ ⤟ ⤠ ⥄ ⥅ ⥆ ⥇ ⥈ ⥊ ⥋ ⥎ ⥐ ⥒ ⥓ ⥖ ⥗ ⥚ ⥛ ⥞ ⥟ ⥢ ⥤ ⥦ ⥧ ⥨ ⥩ ⥪ ⥫ ⥬ ⥭ ⥰ ⧴ ⬱ ⬰ ⬲ ⬳ ⬴ ⬵ ⬶ ⬷ ⬸ ⬹ ⬺ ⬻ ⬼ ⬽ ⬾ ⬿ ⭀ ⭁ ⭂ ⭃ ⭄ ⭇ ⭈ ⭉ ⭊ ⭋ ⭌ ￩ ￫ ⇜ ⇝ ↜ ↝ ↩ ↪ ↫ ↬ ↼ ↽ ⇀ ⇁ ⇄ ⇆ ⇇ ⇉ ⇋ ⇌ ⇚ ⇛ ⇠ ⇢ ↷ ↶ ↺ ↻ <-- <-->)

in julia 1.6, the strings <-- and <--> are supported as symbols, (other arrows are invalid julia parser notation). here, as there are only string manipulation, is ok to have also <-,->, -->, and <-> as valid separators, but they are strings, so they can't be stored in EQUALCHARS , maybe adding a second vector  EQUALSTRINGS and adding those there?

@longemen3000


feat: add user agent to requests

Hi @dupdob,
Please find attached the start of a feat. to add the user agent to requests.
Issue => the creator of AoC posted a message here asking to add user-agents to automated tools.
reddit post
see  a good User Agent would be something like github.com/topaz/name-of-tool by<EMAIL_ADDRESS>I don't think AoCAutomaton is an issue here because of the caching you implemented. Just thought I'd point to this request.

Maybe making an email address or Github user name mandatory as a parameter to concat in the user-agent would be good

Thanks for the PR. Could please open an issue to describe the change ? I will merge it aftwerwards.


Feature request: turn on all features when generating docs

Motivation
https://docs.rs/windows/latest/windows/ is very empty, lacking e.g. SetFileTypes. I believe this is simply because all feature are opt-in (which is great), but the docs are built with the default (empty) feature set.
This should be easily fixable by adding this to every Cargo.toml:
[package.metadata.docs.rs]
all-features = true

Drawbacks
None
Rationale and alternatives
No response
Additional context
No response

Note that docs.rs cannot handle large crates, so the docs for the windows crate are hosted here instead:
https://microsoft.github.io/windows-docs-rs/

Oh, I did not know that! I always visit docs.rs/$CRATE_NAME and assume that's where the docs are 🤦
I would suggest to add a link from https://docs.rs/windows/ to https://docs.rs/windows/latest/windows/ but then I guess that would result in https://docs.rs/windows/latest/windows/ linking to itself, which would be silly.
Thanks for the explanation!


Need help in streaming the graph's agent response from backend to frontend

Hi, I'm learning langgraph right now. I'm trying to build a full-stack app with Nextjs. I'm not able to stream the response from the backend to the frontend. I can invoke the graph and send the completed response, but I don't know how to send the stream response. Right now, I'm not using Langgraph Studio or Cloud. Can you please share code snippets for NextJs or ExpressJs that invoke a graph and stream the final response?
In the frontend, I'm trying to use Vercel's AI package to stream the chat response. It would be great if you could share a code that works with this package.
Thanks in advance.

I'm trying something similar with expressjs and having trouble getting it to work. I can stream the response, but there is no benefit to streaming because I can't seem to pass the streamed chunks coming from the model to the client. The only way I've gotten it to work is invokng the model and getting a message string as a response. Here is a working example that I'm hoping someone can change to actually use the streamed output of the llm:

For anyone looking for a Nextjs + Langgraphjs + Vercel AI SDK, here is my example app, and you can find the code here. Currently it has a simple chat completion and a chat with history features. I'm currently working on tool calling and generative UI.

Here is an example graph and tests to show how local works, but remote does not:
import { StateGraph, END } from "@langchain/langgraph";
import { ToolNode } from "@langchain/langgraph/prebuilt";
import { StateAnnotation } from "./simple-messages-state.js";
import { ChatOpenAI } from "@langchain/openai";

import { tool } from "@langchain/core/tools";
import { z } from "zod";

import { AIMessage } from "@langchain/core/messages";

const model = new ChatOpenAI({
  model: "gpt-4o-mini",
  temperature: 0,
  streaming: true
});

const searchTool = tool((_) => {
  // This is a placeholder for the actual implementation
  return "Cold, with a low of 3℃";
}, {
  name: "search",
  description:
    "Use to surf the web, fetch current information, check the weather, and retrieve other information.",
  schema: z.object({
    query: z.string().describe("The query to use in your search."),
  }),
});

const tools = [searchTool];

const toolNode = new ToolNode(tools);

const boundModel = model.bindTools(tools);

const routeMessage = (state: typeof StateAnnotation.State) => {
  const { messages } = state;
  const lastMessage = messages[messages.length - 1] as AIMessage;
  // If no tools are called, we can finish (respond to the user)
  if (!lastMessage?.tool_calls?.length) {
    return END;
  }
  // Otherwise if there is, we continue and call the tools
  return "tools";
};

const callModel = async (
  state: typeof StateAnnotation.State,
) => {
  // For versions of @langchain/core < 0.2.3, you must call `.stream()`
  // and aggregate the message from chunks instead of calling `.invoke()`.
  const { messages } = state;
  const responseMessage = await boundModel.invoke(messages);
  return { messages: [responseMessage] };
};

// Define the graph
const workflow = new StateGraph(StateAnnotation)
  .addNode("agent", callModel)
  .addNode("tools", toolNode)
  .addEdge("__start__", "agent")
  .addConditionalEdges("agent", routeMessage)
  .addEdge("tools", "agent");

export const exampleSimpleGraph = workflow.compile();

exampleSimpleGraph.name = "Example Simple Graph";

and here are passing (local) and failing (remote) tests:
  Example Simple Streamed Graph
    ✓ should process input through the graph - local (2543 ms)
    ✕ should process input through the graph - remote (2431 ms)

import { isAIMessageChunk, isToolMessageChunk } from "@langchain/core/messages";
import { exampleSimpleGraph } from "../src/agent/example-simple-graph.js";

describe("Example Simple Streamed Graph", () => {
  async function testGraphStream(graph, options) {
    const stream = await graph.stream(
      { messages: [{ role: "user", content: "What's the current weather in Nepal?" }] },
      options
    );

    let streamedAIMessage = "";
    let streamedToolMessage = "";

    for await (const [message] of stream) {
      if (isToolMessageChunk(message)) {
        streamedToolMessage += message.content;
      } else if (isAIMessageChunk(message)) {
        streamedAIMessage += message.content;
      }
    }

    expect(streamedToolMessage).toBeDefined();
    expect(typeof streamedToolMessage).toBe("string");
    expect(streamedToolMessage).toBe("Cold, with a low of 3℃");

    expect(streamedAIMessage).toBeDefined();
    expect(typeof streamedAIMessage).toBe("string");
    expect(streamedAIMessage).toContain("cold");
  }

  it("should process input through the graph - local", async () => {
    await testGraphStream(exampleSimpleGraph, { streamMode: "messages" });
  }, 30000); // Increased timeout to 30 seconds

  it("should process input through the graph - remote", async () => {
    const url = `http://<IP_ADDRESS>:8123`;
    const graphName = "example-simple-graph";
    const remoteGraph = new RemoteGraph({ graphId: graphName, url });

    await testGraphStream(remoteGraph, {
      streamMode: "messages",
      configurable: {
        "__pregel_stream": ["messages/complete"]
      },
    });
  }, 30000); // Increased timeout to 30 seconds
});


Place a temporary message for ML service errors

ML service is being migrated internally and is currently down. We should return a better message to users.

Resolved - ML model back up


Sessions still active on Datasource

Hello,
I am contacting you concerning a problem found when using superset.
We have several session still running on our datasource (Postgres Database) even when superset dashboard is closed or cached on redis.
How can we make sure that superset session are well closed after querying the datasource.
Thank you for you help.

SQLAlchemy uses connection pools by default and the whole purpose of those is to keep connections open for faster access to the database.
That's desired for the metadata database.
We used to also use pools for analytics query against external database but that's been switched off in more recent versions.
Also FAB (Flask App Builder) is known to have session leakage issues. That's a FAB issue we should get to the bottom of at some point

Hello,
We also do analytics query using external database on which we have active session which is problematic for us.
And our version is 0.18.5
Do you think if do an update of superset we will resolve the issue ?
Regards.
Regards

This is the PR you want https://github.com/apache/incubator-superset/pull/4251

Thank you for your reply and your help.
We will try to update our superset version.

It should be in 0.24.0

I'm having a similar (possibly the same) issue with Postgres with superset 0.24.0.
In superset 0.22.2 I had no problems with database connections. When I upgraded to superset 0.24.0 and started the server I had >100 connections by the end of the day to the database it runs queries on. Every time I restart the server, the superset server goes back to about 5 database connections, but by the end of the day it's back > 100. The simple hack to handle that problem is to just restart the superset server every night, but I'd rather not rely on restarting the service in order to kill connections to the database. Superset was not making a ridiculous number of queries to the metadata database (it has been getting to 10 connections, then goes back to 5 connections when I restart the superset server).
Is this enough information to suggest that I messed something up in a config?
Is this an issue with Superset or some package that it relies on?
What other information can I provide that would help figure out the cause of this issue?

@austenhead you're talking about the metadata server right?
How many gunicorn workers are you running? You should expect to see 5 connection per worker. You can tune the configuration variables exposed by flask-sqlalachemy  here http://flask-sqlalchemy.pocoo.org/2.3/config/ . Any of these you can set in your superset_config.py

I'm not clear on what's a reasonable number of connections to a MySQL of Postgres database, but 100 connections doesn't seem crazy to me. Say in an environment where you'd have say a few servers with a bunch of CPUs and some connection pools for each worker.

The number of database connections to the metadata server is small and not an issue.
The number of database connections to the database with company metrics (the data that gets shown in superset) got very big.
I have 5 gunicorn processes running.
From https://serverfault.com/a/862418 it looks like database on AWS's RDS by default can handle ~85 connections per 1GB of RAM. So you're right that 100 connections shouldn't bother me as much as it is. If someone is running this against a small database, then it could be an issue.
From looking at the flask-sqlalchemy I think you're right that that is the most likely culprit.
Thanks for the quick response! I'll write back in the next couple of weeks if this did not resolve my issue (or if it ends up being tricky and someone else might benefit from notes on it).

Hi,
We're using superset 0.24.0 and the issue is still there. Every time I run a query on the SQL lab, a new connection is made to the DB server (we're using postgres), and at the end of the day, we end up with hundreds of db connections, all are idle of course. Previous Superset versions did not have this issue. I wonder if there's a permanent fix coming up or perhaps we should rely on workarounds for now?

This issue, at least I think that it is the same issue, seems to still be open in 0.25.6.  To reproduce, query: select count(*)  from stv_sessions; in Redshift and watch the count increment as you run the query.

Can you check 0.26.rc1?

To get 0.26.rc1 I select that tag from the repo, correct?  If so, that's what I did.  If not please let me know.
Same result, seems to create and leave a connection open each query.  I built from source, installed only the RS driver, and ran in development mode on my local machine.  Then, just query as above and watch the connection count increase.
Please let me know if I'm not testing correctly.

Is you database set to async mode or not? If in async mode, did you restart the worker after upgrading?

Actually, i didn't upgrade.  This was a clean build and install from source.  All settings were default when the app was started.  I created the single Redshift DB connection.  It was set to only sync, not async.

Hi. I confronted same issue while using superset 0.26.3 with postgresql in sync mode. Superset constantly creates new idle connection when I run query in sql lab.
https://github.com/apache/incubator-superset/blob/master/superset/sql_lab.py#L166
Every time i send query using sql lab, new engine instance is created(checked id of engine instance. it is not memoized) with nullpool=False(since I ran query with sync option). So every time a new query is called, engine is created with default pool. Raw dbapi connection created from engine may not be closed after query execution, instead it just releases back to engine's pool. (http://docs.sqlalchemy.org/en/latest/core/connections.html#working-with-raw-dbapi-connections)
I searched some histories to find out implementation background.
https://github.com/apache/incubator-superset/blame/d3f55a0905e4aa7a2da22113ea8e25c174903c9f/superset/sql_lab.py#L48
Looks like former implementations did not create engine in sync case. Is there any particular reason for creating new engine instance and not using NullPool in sync case?
Sorry for my bad grammar.
Thank you for great application.

We are temporarily using gunicorn's max-requests option so that workers automatically recycles themselved with their idle connections.

Having the same issue. Superset 0.26.3 create a new idle connection every time  run a query in sql lab in sync mode @mistercrunch


No completions after "yield" or "yield*"

Starting from the following file state:
import 'dart:async';
class C {
  Stream foo() => null;
  Stream bar() async* {
    yield f;
    yield* f;
  }
}

Place the cursor after each of the identifiers "f" and request code completions.
Expected result: "foo()" should be suggested as a completion.
Observed result: no completions are available.

In IntelliJ, this is not working with
IntelliJ IDEA 2019.2.3 (Ultimate Edition)
Build #IU-192.6817.14, built on September 24, 2019
and
Dart plugin 192.6603.23
Especially "yield [Constructor initials]" only offers to complete the desired constructor when the "new" keyword is included.


Add TokenRequestOptions

Add TokenRequestOptions type and use in every GetToken call for TokenCredentials.
This option type will include a scopes field

Added in linked PR #6432


No option to configure boolean editor representation

Description
Booleans are (by default) displayed as "[ ]" and "[ v ]" in data editor/grid.
I wanted to change this behavior, but couldn't find any settings affecting this.
I found out that there should be a configuration section in "Settings > Editors" (from a colleague using an older version). See screenshot 1 + 2.
It's even mentioned in "Settings > Editors > Data Editor > Appearance Grid" (on right side section "Behavior"). See screenshot 3.

DBeaver Version
Community Edition Version <IP_ADDRESS>410201725
Operating System
macOS 15.1 (24B83)
Database and driver
Current PostgreSQL JDBC Driver - version is not disclosed in connection details/settings.
Steps to reproduce

Open settings
Go to Editors
Note: no boolean configuration section

Additional context
No response

@E1izabeth  By the way, search by the keyword "bool" doesn't find the related settings in Preferences.
I suggest adding it as well.

It was moved to User Interface -> Miscellaneous:

Thanks for the report.


How to localize water effect

Hello, I'm trying to make a map where there's a small body of water (taken from the seaport map) in the center. Problem is that other points of the map go below that water level, and are suddnly submerged as well. Is there any way to contrain the water just to the center?

Pictured here, when going down this ramp, players are considered underwater

Hello, i don't think it's possible with the current water

Noted. And there wouldnt be any way to bring in other waters would there? I've tried to no avail

Noted. And there wouldnt be any way to bring in other waters would there? I've tried to no avail

You maybe can use the damage player script
It have a post event
Disable the damages and see if the post events can be used to make an underwater effect


Bump v0.6.0

Promoting v0.6.0+dev+4 to 0.6.0 stable

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

Coverage data is based on head (d0b99e8) compared to base (2689247).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #10   +/-   ##
=======================================
  Coverage   76.32%   76.32%
=======================================
  Files          11       11
  Lines         566      566
=======================================
  Hits          432      432
  Misses        134      134

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.


Can we have free hand drawing feature in Version 3 (Draw and insert in editor). Lexical Editor by Facebook is having this feature.

Can we have free hand drawing feature in Version 3. Lexical Editor by Facebook is having this feature. Lexical is using Excalidraw for this feature.
Lexical
Excalidraw
it would be even better if this feature could be done using only js/html only.

I postponed it to 3.1.0, but I will reschedule it to 3.0.0.
I think it can be added relatively easily with the current structure.

I postponed it to 3.1.0, but I will reschedule it to 3.0.0. I think it can be added relatively easily with the current structure.

Any tentative date for 3.0.0 version


Fix prerequisites Makefile target to align with docs and help

Change Makefile target from cft-prerequisites to prerequisites.

It was not consistent in the docs and Makefile, but I've changed it the other way around, if that works better.


the word shows Application is Global attribute has to set checked, but the pic keeps unchecked.

the word shows Application is Global attribute has to set checked, but the pic keeps unchecked, please revise the pic.

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

ID: b100266e-1709-282a-df8c-be30485bb6e9
Version Independent ID: 3d314a70-37d8-c0fb-06af-bbb4adaa4637
Content: Walkthrough 3: Display Microsoft Dynamics 365 for Customer Engagement apps records of Unified Interface app in your agent application
Content Source: ce/unified-service-desk/walkthrough3-unified-interface-display-microsoft-dynamics-365-records-in-your-agent-application.md
Service: usd
GitHub Login: @kabala123
Microsoft Alias: kabala

@luoyong0201 : Thanks for sharing the feedback. I will update the topic and release it in couple of days.
So as of now I am resolving this comment. please continue to share more feedback so we can enhance the quality of the documentation.