lora workflow not loading

lora workflow does not load?

what do you mean?

Mine's not looking in the right place for Loras, it defaulted to the furry one, but when I try to change it I have no options, meaning it's not looking at the 'normal' lora folder

You shoul put Flux Loras to models\xlabs\loras


Gemfile lists active_support. Should be activesupport

I was able to install and use this plugin only after i replaced active_support with activesupport.
$ bundle install
Fetching gem metadata from https://www.rubygems.org/.........
Fetching gem metadata from https://www.rubygems.org/..
Resolving dependencies...
Could not find gem 'active_support (>= 0) ruby' in the gems available on this machine.

This was fixed and the repo is deprecated


Thread Thrashing in some processing steps

Heya,
Setting up an OpenSfM container on a 96 core aws container, and noticed a staggering 10k (≃ 96²)  threads and resultant threading issues during detect_features after setting "processes: 96" in config.yaml, whilst setting "processes: 1" in the same way yields full multi-core usage.
However, in the later reconstruction stage, "processes: 1" utilizes only one core, whilst "processes: 96" yields full multi-core usage.
Are some of the stages incorrectly multi-threading twice?

Hi,
We just figure out that opencv might spawn more threads in our back and we made a fix : https://github.com/mapillary/OpenSfM/commit/41f144035fdf61aa38538efdd906318b02ef6acb
Can you fetch latest master and let us know if that fixes your contention issue ?
Thanks,
Yann

Since OpenSfM switched to multithreading instead of multiprocessing, it should have fixed this issue.


feat: modernize front-end

Context
To stay up to date with modern front-end structure, this PR has added the "new" src directory for better file management. Additionally, some dependencies have been updated.
Changes

Added ./src/app directory.
Renamed postcss.config.js to postcss.config.mjs.
Added e2e to the ignore path of Jest.

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 commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have tested my code for breaking changes and added the corresponding footer in this PR if needed
[x] I have added tests that prove my fix is effective or that my feature works

:tada: This PR is included in version 3.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add reference benchmarks for bit vector implementations

This adds reference benchmarks for std::vector<bool> in the C++ STL and CFBitVector in Core Foundation.
Checklist

[X] I've read the Contribution Guidelines
[X] My contributions are licensed under the Swift license.
[X] I've followed the coding style of the rest of the project.
[ ] I've added tests covering all new code paths my change adds to the project (if appropriate).
[X] I've added benchmarks covering new functionality (if appropriate).
[X] I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
[ ] I've updated the documentation if necessary.

The included library produces the following charts:

@swift-ci test

@swift-ci test


Density Coordination

Hello, this is a really cool library. I'm using it in my WPF project, and now I have a question. One of my layers is filled with labels, and I want it to display only one label if there is any overlap.

This is not supported through configuration. It is possible to build something like this yourself if you use a custom IProvider and filter on the labels on zoomed-out resolutions. This may not be easy.

Thank you for your reply. Could you provide a simple demo to solve this problem?


Thank you!

Hi @philr, just wanted to thank you for this package, couldn't find you on twitter.
I'm trying to resolve the problem when a new version of tzdata is released, so I made a couple of things:

a ruby package that contains each version of the database in JSON files, and can return the diff (for ex: what do I have to check in my system if I'm in 2016c and install 2017a, for America/Santiago and America/Punta_Arenas). I extracted all the data from your tzinfo-data gem.
a npm package that uses the json data generated above, and do the same in javascript.
a demo to see the changes, for example: here you can see the changes above for America/Santiago → America/Punta_Arenas.

I will post a medium post later on the topic, but thanks again for your work.

Thanks for letting me know about your new project. It looks interesting. I've written scripts before to compare the offsets of used time zones between different tzinfo-data versions, but this is much more comprehensive.
I've had a quick look at your DataGenerator code. I note that it is currently accessing the protected #info method to obtain transition data. Is there a reason why you're not using the public TZInfo::Timezone#transitions_up_to method instead?

Oh no, you got me doing something inappropriate ;-)
Sorry, I use the protected methods because wanted the full list of transitions, and didn't want a hardcoded end date.
By the way, the moving 50 year limit is kind of an issue for me now, the utilities reports changes between versions when nothing changed from the tzdb perspective, like this one.
I'm still working on documentation, I think it looks good enough so far.


encodingcom: Parse status description

Parse job output status description from encoding.com API response.

looks good!


2 member kanban board

Link to the kanban board in projects
We are just 2 members in our group

**Hi @shegy28 and @r-ahmed2022
You did great. Your kanban board is complete!  There is nothing else to say other than... it's time to start coding :shipit:
Congratulations! 🎉

Highlights
✔ Descriptive PR
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
m05e5

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.**


Use custom fonts

Ability to change fonts would be very helpful and will give a much better reading experience

Added in 0.4


molokai: black color (16) to orange color (208)

In my opinion, black color doesn't look good in molokai theme
Normal mode before

Normal mode after

Insert mode before

Insert mode after

Replace mode before

Replace mode after

Visual mode before

Visual mode after

thanks.


python3Packages.rokuecp: init at 0.8.1

Motivation for this change
Needs a maintainer. cc @Church-
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

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

3 packages built:

home-assistant
python38Packages.rokuecp
python39Packages.rokuecp

The fun fact will be, that ultimately the home-assistant maintainers will keep this up to date with home-assistant requirements, given that we don't like test failures much.

I forgot to add a maintainer...

@Church- It would be great if you could step up and maintain this package, given that I am not a roku user and therefore cannot test it.


initial support for volumes

Adds support for nova-volume service that by default uses a 2gig file backed vg.

updated per comments

is this ready for default enabled?  Or should we add it with default disabled and after some time enable it?

fair nuff - default disabled for now then...


Added keynavigation to the table

You can now navigate with the arrow keys
Left/Right

This leaves the key event hanging in the rest of the application. - do not pull :)


My feature

torvalds.dev is analyzing the pull request

torvalds.dev is analyzing the pull request

The task involves reviewing the provided GitHub PR diff to check if it adheres to the provided coding standards document. The coding standards document outlines best practices for naming conventions, code formatting, and comments/documentation.
The PR diff shows changes in the following files:

src/core/MusicPlayerCore/index.ts
src/core/VueMiniPlayerCore/index.ts
src/core/VueMiniPlayerCore/index_2.ts (new file)
src/core/VueMiniPlayerCore/new-index.ts (new file)

The plan is as follows:

Review the changes in each file against the coding standards document.
Identify any deviations from the standards.
Provide recommendations for improvement.

Let's start with the first file, src/core/MusicPlayerCore/index.ts.

Upon reviewing the provided GitHub PR Diff, the following issues were identified with respect to the coding standards document:

File: src/core/MusicPlayerCore/index.ts

The extra empty lines added seem unnecessary and decrease code readability. It's recommended to remove the empty lines 118 to 119.
On line 136, it seems the formatting syntax {} has been mistakenly added, which results as a syntax error. Remove {}.
On line 163, this.SongIdList === list should be this.SongIdList = list, as per the context, it seems like an assignment operation is intended here, not a comparison.
A variable name P has been used on line 182 (from p to P) which is not in compliance with the best practices which advise against the use of single-letter variable names.
The function named Prev-Song does not adhere to the recommended camelCase or snake_case naming conventions. This name should be changed to prevSong.

File: src/core/VueMiniPlayerCore/index.ts

The Single-letter variable a and b on line 18 and 44 respectively are non-descriptive and do not align with coding standards. Make sure the variable names are descriptive like 'wrapperIdentity' or 'appCreation' respectively.
songInfoList becomes SONGinfoLIST and should stay as songInfoList, adhering to the camelCase naming convention mentioned in your Coding Standards Document.
It is also seen that s is being changed to s = document.getElementById(Wrapper-ID) which will literally look for an ID 'Wrapper-ID'. If you're trying to concatenate variables, it should be done properly.
It also seems that the - character is being used in the middle of the variable names and function names. The - operator is generally used in JavaScript for subtraction and using it in names might lead to code errors.

File: src/core/VueMiniPlayerCore/index_2.ts

Duplicate of index.ts named index_2.ts seems to have been added. If it was added for backup or testing purposes, it's recommended to keep different versions or testing files in separate dedicated directories or branches.
The same issues mentioned for src/core/VueMiniPlayerCore/index.ts are seen here as well. The solutions are the same.

File: src/core/VueMiniPlayerCore/new-index.ts

The naming for the file does not adhere to the recommended naming conventions. File names should be descriptive and follow either camelCase or snake_case naming conventions. A better name might be NewIndex if following CamelCase, or new_index if following snake_case, depending on your standards.
The same issues mentioned for src/core/VueMiniPlayerCore/index.ts are seen here as well. The solutions are the same.

In conclusion, it is imperative to ensure that the code adheres to the prescribed coding standards to maintain consistency, readability, and to ease collaboration among the team. It seems a few issues have been introduced in this PR which goes against the prescribed standards, the corrections for which are mentioned above.


annotation: Support co.elastic.apm/attach

Description
Adds support for co.elastic.apm/attach as the primary annotation for kubernetes pods while still supporting the old co.elastic.traces/agent for a more seamless experience for upgrading users. We can drop the old annotation in a future version.
Related issues
Part of #28

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-09-14T11:16:34.844+0000

Duration: 5 min 53 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
16

Skipped
0

Total
16

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


Add Stable mgmt for Confidential Ledger

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[✔ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[✔ ] Other, please clarify - Stable swagger for GA. Same as last approved preview version.

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[✔ ] SDK of .NET (need service team to ensure code readiness)
[✔ ] SDK of Python
[✔ ] SDK of Java
[✔ ] SDK of Js
[ ✔] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[✔ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[✔ ] I have reviewed the documentation for the workflow.
[✔ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[✔ ] Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[✔ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

approved for python breaking change

@fengzhou-msft could you please help about the details on azure-sdk-for-net-track2 pipelines? Some details are not looking correct

@fengzhou-msft could you please help about the details on azure-sdk-for-net-track2 pipelines? Some details are not looking correct

Confidential Ledger only has a data plane track 2 package, therefore this PR has no impact on azure-sdk-for-net-track2.

@akning-ms Could you help merge this PR?

Hi @musabbir, can you confirm what you did for this PR just move preview version 2021-5-13-preview? if any other change in swagger in new version, we may need ARM to sign off, and BTW, is there new version deployed to production? if no, when it will be deployed?

There are no changes other than copying over the last approved swagger (2021-5-13) to a stable folder.
This version is fully supported in production.

Hi @musabbir, can you confirm what you did for this PR just move preview version 2021-5-13-preview? if any other change in swagger in new version, we may need ARM to sign off, and BTW, is there new version deployed to production? if no, when it will be deployed?

There are no changes other than copying over the last approved swagger (2021-5-13) to a stable folder.
This version is fully supported in production.

We will update the ARM Manifest after this PR is merged.


xacro: 1.13.19-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository xacro to 1.13.19-1:

upstream repository: https://github.com/ros/xacro.git
release repository: https://github.com/ros-gbp/xacro-release.git
distro file: melodic/distribution.yaml
bloom version: 0.11.2
previous version for package: 1.13.18-1

xacro
* Evaluate ``arg`` value as str/unicode (#322 <https://github.com/ros/xacro/issues/322>)
* Contributors: Robert Haschke

Holding for Melodic sync


MMB: update menu design to be Android compatible

Will this work for groups with one child?

I think this bug is not fixed yet - this just updates the design to the Android-friendly:

Ok, will you please make a task for it, so I can keep track of it?


Explain the module specific themes separation capability of Silverstripe

A problem I had recently highlighted the need for some missing docs on how the theme_module setup is possible.
#3944

:mind_blown: is this true?! Are there even any tests for this behaviour?

Ya - its been around since 2.3 / 2.4
I think this line is the best proof:
https://github.com/silverstripe/silverstripe-framework/blob/3.1/core/manifest/TemplateManifest.php#L189
Not sure if there are tests.


Back from SQL Managed Instance

On the Overview page you are saying
Backups from a managed instance can only be restored to another managed instance. They cannot be restored to an on-premises SQL Server or to a single database/elastic pool.
But on FAQ
How can I move database from managed instance back to SQL Server or Azure SQL Database?
ou can export database to BACPAC and then import the BACPAC file. This is a recommended approach if your database is smaller than 100 GB.
Transactional replication can be used if all tables in the database have primary keys.
Native COPY_ONLY backups taken from managed instance cannot be restored to SQL Server because managed instance has a higher database version compared to SQL Server.
which one is correct?

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

ID: aa11b569-0d56-63b7-aac5-4b2dd9a859e2
Version Independent ID: 87d7d50e-7fae-c36e-43af-ec18dbef9b48
Content: Managed instance FAQ - Azure SQL Database
Content Source: articles/sql-database/sql-database-managed-instance-faq.md
Service: sql-database
Sub-service: managed-instance
GitHub Login: @jovanpop-msft
Microsoft Alias: jovanpop

@mailtogurvindersingh Thanks for the question. We will update you shortly.

@mailtogurvindersingh Backups(.bak) and bacpac are 2 different types of files. The overview page is referring to native backups (.bak) and you will not be able to take the back up and restore it on premises or azure sql single Db as explained in these threads - https://github.com/MicrosoftDocs/azure-docs/issues/32768
https://feedback.azure.com/forums/915676-sql-managed-instance/suggestions/35414512-make-backups-portable-to-on-premise-sql
But the bacpac export from MI and Transactional replication with MI as publisher works as explained here:
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-transactional-replication
Hope this helps.

@mailtogurvindersingh Please let us know if you need any further help or we will close this thread by EOD.


No air friction?

Hi:
All my spherical RigidBodies slide through the ground plane infinitely no matter what friction I put in the ground plane or the bodies. Is there a way to ensure they will stop? or to set up some kind of air friction.
Thanks

I'm having the same prob. Has this been addressed?

I have the same problem. Can it be fixed? @lo-th


Makefile doesn't work for spacy

Running the Makefile still requires me to run pip install -e server/spacyface after the makefile completes the run. Otherwise I get an error about spacy not being present.
This happens even though the output of the makefile does show that the spacy installation was successful.

Hmmm, I can think of a couple possible issues. What is the path to your conda activate binary? The Makefile assumes it is at
at ${HOME}/anaconda3/bin/activate.


[fix] PFE-badge variants fail a11y contrast & no darker options among the variants

Description of the issue

PFE-badge variants are barely visible against the background of the RHEC Search pages
Impacted component(s)

Filter Select

Steps to reproduce

Go to any Catalog search page
Click on any filter checkbox
Badge will appear next to the facet heading
Confirm that color contrast isn't high enough/badge outline is difficult to see

Expected behavior

The PFE Badge icon color should be distinguishable from the background color.
Screenshots

Related issues

#100

Closing based on https://github.com/patternfly/patternfly-elements/pull/1783#issuecomment-1049840313. If still relevant, please re-open.


Simplify default export

Looks great @fredj.  Please merge.

@fredj - in case you don't get around to fixing the conflicts, I opened a new PR with a rebased version: https://github.com/openlayers/openlayers/pull/7593

Merged in #7593.


Array/sequence interface

get items, iterators, len, etc...
https://github.com/pybind/pybind11/blob/416f7a4410d3638273dd071a7cd4e63cd481ca92/tests/test_sequences_and_iterators.cpp#L272-L322

Also see https://github.com/pybind/pybind11/blob/416f7a4410d3638273dd071a7cd4e63cd481ca92/tests/test_sequences_and_iterators.cpp#L505-L524

len and iterators was added to APyFixedArray in #62

__getitem__, len, and iterator was added last week for APyFloatArray in #80


[FLINK-5012] Expose Timestamp in Timely FlatMap Functions

This also adds a Context parameter that holds the timestamp, time domain
and TimerService to declutter the parameter list of the functions.
R: @StefanRRichter and @kl0u for review, please
CC: @jgrier

LGTM

Thanks for reviewing @jgrier!


jpalmer108/updateDemoDoc/#160

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes: #160
Summary:
Adds a section that explicitly states you can conditionally return an attribute to auro-input's error message to manage error states.
Type of change:

[X] Other (docs)

Checklist:

[X] My update follows the CONTRIBUTING guidelines of this project
[X] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

Please see our Contributing guidelines for how to craft a commit message.
Specifically, all commit messages should use an imperative mood.


Add author profiles

In the authors.yml file in the data folder we have to create authors.
For each author we write a small bio, add a profile picture and our social links.
We could optionally add a pseudo author for the tutorials or just also put a regular author (you or me) next to a tutorial.

https://mmistakes.github.io/minimal-mistakes/docs/authors/
see this part of the documentation for explanation


RuntimeError: "slow_conv2d_cpu" not implemented for 'Half'

RuntimeError: "slow_conv2d_cpu" not implemented for 'Half'

AttributeError: 'NoneType' object has no attribute 'dtype'

What pytorch version did you install?

2.0.0下面，使用的是MacPro M2

https://github.com/liujing04/Retrieval-based-Voice-Conversion-WebUI/issues/67#issuecomment-1510027220


File added: CODE_OF_CONDUCT.md

This Code of Conduct is adapted from the Contributor Covenant, version 1.4.

@juanluischaurant Looks good! Can you also add yourself to the Contributor List?

@scrabill Of course, I'll do it in a while, I'm working on some other changes for the app.

No rush!


Enchantment Giveaway System that has a requirement to upload an image

Giveaway created by Giveawayboat -> Thread created by admin -> Command bot sends by  Admin -> Members will upload the image via this command -> Bot sends the image to the thread
If giveaway ends:
Giveawayboat sends a specific message in giveaway channel -> Warnetbot triggered -> Warnetbot parses the ID of the winner -> If found, Warnetbot sends the image in the giveaway channel -> End

I think its too complex, maybe forward the image (like nqn) but instead member send the image in message it will be upload to a form modal. After that, the bot would store the message ID and save it in the database.


Add FinanceKit

@daveverwer I can't see why this would fail. It says dumpTimeout. Have you seen that before?
It passed locally! :)

@daveverwer I can't see why this would fail. It says dumpTimeout. Have you seen that before?
It passed locally! :)

I noticed that Xcode could not resolve the package either. I think it was due to the tag being '0.1'.
Xcode required '0.1.0', and after changing it it worked.
I would rerun the checks here, as I think that should solve it. Can't see how though.

Sorry about that, it looks like the GH Action just timed it out for some reason. I checked it locally and re-ran the action and it passed with flying colours! Thanks so much for submitting it. 👍
Dave


[PERF]: pipeline segment committing/flushing

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

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

#3360  👈 (View in Graphite)
#3359
#3357
main

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


Changing configuration of the integration gives an error

The problem
If I do try to configger the installed integration it is not showing the configuration module but gives an error
Version of afvalwijzer integration having the issue?
mijnafvalwijzer
Version of Home Assistant Core having the issue?
core-2024.12.4
Anything in the logs that might be useful for us?
^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 342, in async_init
    result = await self._async_handle_step(flow, flow.init_step, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 517, in _async_handle_step
    result: _FlowResultT = await getattr(flow, method)(user_input)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/afvalwijzer/config_flow.py", line 86, in async_step_init
    current_options = self.options or {}
                      ^^^^^^^^^^^^
AttributeError: 'AfvalwijzerOptionsFlow' object has no attribute 'options'

Additional information

Same here

+1

This happens when you install it? Or when does this happen?

@DaanSelen Installed the update, restarted home Assistant, tried to open the configure menu and got the error.

@DaanSelen Installed the update, restarted home Assistant, tried to open the configure menu and got the error.

Yup! Same here.

Huh weird, I was able to reproduce this issue. Now its fixed suddenly. Please try to use the latest code from: https://github.com/xirixiz/homeassistant-afvalwijzer/blob/main/custom_components/afvalwijzer/config_flow.py and paste it into the config_flow.py for a starter.

Yeah, that is correct. I fixed it for the latest release so it at least is working. Modifying the config after installation is also working, but keeps giving an error. I`ve created an issue for that, so let's wait for a full fix. I anyone still has initial config problems with the component, please let me know. https://community.home-assistant.io/t/config-flow-issue-updating-configuration/812969

Ah, my bad, 2024.01.02 was indeed broken. I at least uploaded release 2024.01.03 now, which solves the initial config.
All code and bugfixes have been fixed in the latest release. Saver has been added, and Rova has been updated to be a separated provider. The only thing left for now is the final config_flow fix. I`ll first test things properly before delivering a new release, so you don't have any issues with it. Thanks for sharing your solution @DaanSelen

Indeed, changing the configuration gives an update failed

Indeed, changing the configuration after installing 2024.12.03 gives an update failed But it looks like the changes are still stored

Same here

Please read my comments properly. I mentioned there is still an issue with it :). I removed the optionsflow for now.


stream.async.splat: avoid infinite pattern recursion

We would previously return success() even when we moved the op to its current location, leading to infinite pattern recursion. Detect this case and return failure() instead.

Nice catch!


pre-trained models from publication

Hello,
I am interested in running TAGPPI prediction on a list of possible PPIs to compare to a results I obtained using a different machine learning tool. Are there trained-model files available that can be used to run such a "quick check" analysis without training a new model myself? The multi-species dataset model presented in the publication would be the most interesting for me, but could make due with the yeast model. (I've downloaded these datasets, but having an already trained and cross-validated model would be really great).
From there, as I understand, I would to use SeqVec separately to generate embeddings for my test data (or is this integrated in the TAGPPI pipeline?). Then, could you please outline which .py scripts I would need to run and which variables need to be set in them to make predictions on my test PPI pairs using the multi-species trained model? (I think all I will need in the end is the 1. trained model file, 2. protein embeddings, 3. a pairwise tsv of each PPI I wish to test, with names matching the input fasta to SeqVec?) I see some comments in the py files, but how exactly to use the tool isn't entirely clear to me.
Thank you for the help!

I have this running to attempt to recreate the published yeast model. However am receiving an error that might relate to the protein embeddings:
Running EPOCH 1
Traceback (most recent call last):
  File "my_main.py", line 25, in <module>
    main()
  File "my_main.py", line 22, in main
    train(trainArgs)
  File "/lustre/fs0/home/iwill/TAGPPI/TAGPPI-main/my_train_and_validation.py", line 54, in train
    for batch_idx,(G1,dmap1,G2,dmap2,y) in enumerate(train_loader):
  File "/home/iwill/my-envs/tagppi_3/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 628, in __next__
    data = self._next_data()
  File "/home/iwill/my-envs/tagppi_3/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 671, in _next_data
    data = self._dataset_fetcher.fetch(index)  # may raise StopIteration
  File "/home/iwill/my-envs/tagppi_3/lib/python3.7/site-packages/torch/utils/data/_utils/fetch.py", line 58, in fetch
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "/home/iwill/my-envs/tagppi_3/lib/python3.7/site-packages/torch/utils/data/_utils/fetch.py", line 58, in <listcomp>
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "/lustre/fs0/home/iwill/TAGPPI/TAGPPI-main/graph_cmap_loader.py", line 74, in __getitem__
    G2,embed2 = self.loader(cmaproot+p2+'.npz',p2)
  File "/lustre/fs0/home/iwill/TAGPPI/TAGPPI-main/graph_cmap_loader.py", line 42, in default_loader
    G.ndata['feat'] = g_embed
  File "/home/iwill/my-envs/tagppi_3/lib/python3.7/site-packages/dgl/view.py", line 99, in __setitem__
    self._graph._set_n_repr(self._ntid, self._nodes, {key: val})
  File "/home/iwill/my-envs/tagppi_3/lib/python3.7/site-packages/dgl/heterograph.py", line 4033, in _set_n_repr
    ' Got %d and %d instead.' % (nfeats, num_nodes))
dgl._ffi.base.DGLError: Expect number of features to match number of nodes (len(u)). Got 205 and 255 instead.

I added some code to print out some more info as the function runs to see the node/feature mismatch:
nodenum is 59
g_embed length is 59
g_embed is tensor([[-0.3556, -0.1379, -0.0917,  ..., -0.2526, -0.0242,  0.3453],
        [-0.2281,  0.2757, -0.1602,  ..., -0.2342, -0.0326,  0.1073],
        [-0.0355, -0.1601,  0.0321,  ..., -0.2930,  0.1983, -0.1177],
        ...,
        [-0.0265,  0.0224, -0.3109,  ..., -0.2147, -0.0951, -0.0090],
        [ 0.2207,  0.0904,  0.0844,  ...,  0.0323, -0.0259, -0.1708],
        [-0.1693,  0.3720, -0.1931,  ...,  0.0684, -0.2738, -0.1622]])
pid is P81450
G isGraph(num_nodes=59, num_edges=891,
      ndata_schemes={}
      edata_schemes={})
nodenum is 295
g_embed length is 295
g_embed is tensor([[-0.3399, -0.0940, -0.0824,  ..., -0.0480,  0.1147,  0.1128],
        [ 0.2022,  0.2139,  0.1005,  ...,  0.2424,  0.0260, -0.1995],
        [ 0.1819, -0.0007, -0.1988,  ..., -0.0266,  0.0773, -0.1405],
        ...,
        [-0.3939, -0.2824, -0.1768,  ...,  0.0194, -0.0387, -0.0707],
        [-0.4689, -0.4695, -0.0849,  ..., -0.2983,  0.2909, -0.1734],
        [-0.5129, -0.2805, -0.4166,  ...,  0.1559, -0.1940, -0.1230]])
pid is P32573
G isGraph(num_nodes=292, num_edges=9518,
      ndata_schemes={}
      edata_schemes={})
Traceback (most recent call last):...........#error as shown above#

Removing that specific protein (P32573) and all its PPIs from the training pairs eventually shows another protein giving a similar error. I used the provided yeast alphafold cmap and dictionary.tsv (converted to fasta and then I ran Seqvec). Where do you think the problem lies - dependency environment (I've tried many), tagppi code, or embedding files?
When I try using the provided multi-spp data instead, I do not get this error, but get a different one. This might indicate a problem with embedding files? Seqvec doesn't offer too many parameters to change, but any details there? Or could the hosted alphafold data be somehow incorrect?
Thank you

Did you solve this problem? and how did you solve it? Thank you!

I never went back to the yeast data, I just continued with the multi-spp data. There were other issues unrelated to this protein embedding thing that we worked around by editing the python script and how training works. Which all is a little suspicious (either a code bug or we don't have the expertise to use the tool correctly), so we've stopped working with TagPPI.


CkExit() crashes called from main chare constructor with -tracemode projections

Original issue: https://charm.cs.illinois.edu/redmine/issues/948

This exhibits as follows in tests/charm++/{queue,topology}:
#0  0x00007ffff7012cc9 in __GI_raise (sig=sig`entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007ffff70160d8 in __GI_abort () at abort.c:89
#2  0x00000000005ece61 in charmrun_abort (s=0x639668 "Error! This group proxy has not been initialized!") at machine.c:997
#3  0x00000000005ec7d5 in LrtsAbort (message=0x639668 "Error! This group proxy has not been initialized!") at machine.c:539
#4  0x00000000005ec2a1 in CmiAbortHelper (source=0x64ee49 "Called CmiAbort", message=0x639668 "Error! This group proxy has not been initialized!", suggestion=0x0, tellDebugger=1, framesToSkip=0) at machine-common-core.c:1416
#5  0x00000000005ec2d0 in CmiAbort (message=0x639668 "Error! This group proxy has not been initialized!") at machine-common-core.c:1420
#6  0x000000000052950b in CProxy_Group::ckCheck (this=0x7fffffffe240) at charm++.h:780
#7  0x00000000006339c8 in CProxy_TraceProjectionsBOC::ckCheck (this=0x7fffffffe240) at TraceProjections.decl.h:1455
#8  0x000000000062e037 in CProxy_TraceProjectionsBOC::traceProjectionsParallelShutdown (this=0x7fffffffe240, impl_noname_7=0, impl_e_opts=0x0) at TraceProjections.def.h:1948
#9  0x0000000000623438 in TraceProjectionsExitHandler () at trace-projections.C:1867
#10 0x000000000050e8c1 in _exitHandler (env=0xa805a0) at init.C:521
#11 0x00000000005f2dc5 in CmiHandleMessage (msg=0xa805a0) at convcore.c:1633
#12 0x00000000005f3046 in CsdScheduleForever () at convcore.c:1861
#13 0x00000000005f2f77 in CsdScheduler (maxmsgs=-1) at convcore.c:1797
#14 0x000000000050f592 in CkExit () at init.C:923
#15 0x00000000005b74f4 in controlPointManager::doExitNow (this=0xa4e1e0) at controlPoints.C:929
#16 0x00000000005b7447 in controlPointManager::exitIfReady (this=0xa4e1e0) at controlPoints.C:916
#17 0x00000000005b78c9 in controlPointShutdown () at controlPoints.C:1235
#18 0x000000000050e8c1 in _exitHandler (env=0xaae7a0) at init.C:521
#19 0x00000000005f2dc5 in CmiHandleMessage (msg=0xaae7a0) at convcore.c:1633
#20 0x00000000005f3046 in CsdScheduleForever () at convcore.c:1861
#21 0x00000000005f2f77 in CsdScheduler (maxmsgs=-1) at convcore.c:1797
#22 0x000000000050f592 in CkExit () at init.C:923
#23 0x000000000050bf25 in main::main (this=0xa4e180, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at pgm.C:295
#24 0x000000000050b51a in CkIndex_main::_call_main_CkArgMsg (impl_msg=0xa4eb20, impl_obj_void=0xa4e180) at main.def.h:49
#25 0x00000000005103b0 in _initCharm (unused_argc=1, argv=0x7fffffffea48) at init.C:1452
#26 0x00000000005ec097 in ConverseRunPE (everReturn=0) at machine-common-core.c:1262
#27 0x00000000005ebfc8 in ConverseInit (argc=1, argv=0x7fffffffea48, fn=0x50f7c5 <_initCharm(int, char**)>, usched=0, initret=0) at machine-common-core.c:1180
#28 0x000000000050db7e in main (argc=1, argv=0x7fffffffea48) at main.C:18

Because of the wonky initialization order semantics, calling CkExit from the mainchare's constructor means that you get into code that expects initialization that hasn't happened yet to be done.

Original date: 2016-03-03 19:40:41

https://charm.cs.illinois.edu/gerrit/#/c/1095/

Original date: 2016-05-05 16:45:38

Posted patch needs substantial further work.

Original date: 2017-04-12 20:35:29

I've got most of a fix for this done. It will just short-circuit the exit-time code if initialization hasn't happened.

Original date: 2017-04-12 20:54:58

~~https://charm.cs.illinois.edu/gerrit/2389~~ https://github.com/UIUC-PPL/charm/commit/9fb4709c61477c422c1a76d93cbc4994e72331c6


The "custom" property not documented well enough:

Describe the bug

I would like to mock the API for development by leveraging the graphql-mesh.
This doesn't seem to be working by following the API provided in the documentation - https://www.graphql-mesh.com/docs/transforms/mock/.
The API documentation isn't quite clear on how the mock could be provided by using the custom property.

Solution: I have managed to provide a custom file by doing the following:
The moduleName is actually a path + file name and the exportNane is the property being exported.
e.g.
// mocks.ts
export default {
  id: 'sample-id',
  fullName: 'John Snow',
};

There are a couple of other ways to define the data in the custom mocks file, but I haven't tried it out yet.
So, in the end, the value of the custom property, when mocking, should look like this:
transforms:
  - mock:
      mocks:
        - apply: User.id
          custom: './packages/transforms/mock/test/mocks.ts#id', // also, this path is weird. The root should be `mock` folder, not its parent, or more precisely the root of the monorepo.
        - apply: User.fullName,
          custom: './packages/transforms/mock/test/mocks.ts#fullName',

What would be nice is having an option to define a whole set of the mocked data.
For example, when mocking a list of data, to define a whole list of, e.g. 20 items.
Also, when mutating, at the moment a mocked data is returned. It would be nice to be able to persist the data, and when receiving a response from the mutation to get the exact data that was submitted.
To Reproduce
Steps to reproduce the behavior:
Option 1:

codesandbox: https://codesandbox.io/s/inspiring-benz-tr73v?file=/gateway/.meshrc.yaml

Option 2:

clone the repo https://github.com/nemanjamilosavljevic-newtron/graphql_ensemble
install all dependencies of the /gateway and the two backend services
run yarn start
observe that nothing is mocked

Expected behavior

I expect to be able to customize the mocking so that it can be used in an expected manner for both development and for testing.
Environment:

OS: Windows 10
"@graphql-mesh/cli": "0.26.2",
"@graphql-mesh/graphql": "0.15.2",
"@graphql-mesh/openapi": "0.13.3",
"@graphql-mesh/runtime": "0.12.0",
"@graphql-mesh/transform-mock": "0.8.5",
"graphql": "15.5.0"
NodeJS: 14.16.0

Additional context

Could you update the packages and try again?

I have updated the repo and tested it. No noticeable change in the behavior.
The repo, above, is now up to date with the latest versions of the libraries.

Also, I have to ask, how does one mock mutation? What's the API for mocking mutations?

@ardatan I'd appreciate it if you could point me to existing documentation regarding the mutation mocking.

I'm adding a lot here but I'm just labeling it according to our new Contribution Guide and issue flow.
It looks like already got it into stage 1! thank you for that!
Now in order to advance to stage 2 we'll need a failing test.
Would be great if someone could help progress the issues through the stages.
Here is where the mocking tests exist: https://github.com/Urigo/graphql-mesh/blob/master/packages/transforms/mock/test/mocking.spec.ts
Do you think you can create the same configurations as in your reproduction there and see if you can get a failing test.
Also maybe it would be easier later on to break this issue into multiple issues and so we could go through the same stages for each of your findings, but it could wait once we identify at least one failing test.
Thank you and sorry that this comment is not a complete solution (yet)

Hi Urigo,
Thanks for stepping in, in an effort to progress this issue.
Yes, I will try to set up and add the failing test(s).

As suggested, and after lerning more about the API, I have adjusted the issue's title and its scope. I hope this simplifies resolvement.
Also, I've created this pull request for extending the test cases: https://github.com/Urigo/graphql-mesh/pull/1998

@nemonemi Could you try it with the following version?
<EMAIL_ADDRESS>

@ardatan I have reduced the scope of this issue.
What should I be testing with this version?
Are you referring to the mutation mocking and persistence?

@nemonemi I created this PR based on the failing tests you created before in #1998 . It seems the field mocks weren't working properly according to your failing tests. So you can test mutations etc. But not sure what you mean by persistence, are you referring to stateful mocking?

Yes, I've meant stateful mocking.
p.s. thanks for working on this! 👍

@ardatan, how could I assist you with progressing on the https://github.com/Urigo/graphql-mesh/pull/2001?


feat: unnesting arbitrary subqueries (likely broken)

Somewhere between a proof of concept and a draft—work still heavily in progress. Will already successfully parse and fully unnest a subset of correlated and uncorrelated subqueries (although I am uncertain about correctness).
TODO:

[ ] Formal testing
[ ] EXISTS clauses
[ ] IN clauses
[ ] ANY/ALL clauses
[ ] Correctness issue with COUNT(*) (requires adding left outer join to plan)
[x] Move some/all of this to rewriting stage to support multiple subqueries/ordering operations
[x] “Sideways information passing” (subplans are duplicated now instead of making a DAG)

It seems that a DAG representation is only supported by looking for groups that appear the same. It looks to me that the cloned branches generated by this PR are indeed marked with the same group ID. I marked this bullet point as completed with this in mind.

[ ] Support more pushdowns (e.g. limit, joins)
[ ] Optimizations from the paper are all missing (Out of scope?)

TODO on the tooling side:

with_logical is super confusing, this means "with data fusion logical optimizer", we should either doc it or have a human-readable name
I think now we need explain_after_heuristic so that we can print out a so-called optimized logical plan.

also we should consider bump compiler version and upgrade to Rust 2024 edition


Should be message oriented

Right now the Actor framework is method oriented, the ActorRef is generalizing over the ActorImpl ActorRef<ActorImpl>, this is causing design-problems if one wants to store different ActorRefs over different ActorImpls in a single container. The intention of the container is to sent the same message to each one.
Instead of ActorRef<ActorImpl> the framework should use references being message oriented, such as Slot<MessageType>
Lets call this proxy (channel::tx) Slot for now.
The function create_actor() might return a single slot or multiple slots, for example
let (slot_msg_type1, slot_msg_type2) : (Slot<MsgType1>, Slot<MsgType2>) = create_actor(MyActorImpl::new(x,y,z))?;

Thanks for this issue @frehberg! Its a problem that has vexed me for some time. I was thinking perhaps this could be solved though enums generated by a macro, similar to inventory but I havent had the chance to look into this in more detail...


6.4.0 fails to start on Phytium arm platform

Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Start tiflash 6.4.0 on specific arm platforms
2. What did you expect to see? (Required)
Started successfully like 6.3.0

3. What did you see instead (Required)
Compared with 6.3.0, there are some more link libraries：libgmssl.so    libgmssl.so.3.0 libgmssl.so.3

4. What is your TiFlash version? (Required)
v6.4.0-pre

Cause by https://github.com/pingcap/tiflash/pull/6200. This so called Phytium platform has not support armv8.2. QA need tiflash v6.4 can work on it.


Add Codecov to Travis

Signed-off-by: Gábor Lipták<EMAIL_ADDRESS>Example report https://codecov.io/gh/gliptak/pyro/branch/codecov1

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@6e843c0). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev   #1288   +/-   ##
=====================================
  Coverage       ?   90.9%
=====================================
  Files          ?     116
  Lines          ?    6236
  Branches       ?       0
=====================================
  Hits           ?    5669
  Misses         ?     567
  Partials       ?       0

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 6e843c0...c034c50. Read the comment docs.

Thanks for adding a code coverage report to Pyro. Just to confirm - it looks like this is using all the test stages from travis? Would it be simple to remove one or more stages from the coverage report, say the examples stage for instance?

Would it be simple to remove one or more stages from the coverage report, say the examples stage for instance?

I think we can just remove the --cov invocation from pytest for those stages. We can do that later (it won't really affect the marginal code coverage so we could leave it in as well) and add a badge to our README too.
LGTM. @jpchen, @fritzo - Let me know if you have any thoughts / comments on inc. a code coverage report for PRs.

I think we can just remove the --cov invocation from pytest for those stages

sounds fine to me. i dont really know how accurate this is, afaik it does static analysis of coverage and cant do anything fancy like testing going down different branches in models with dynamic control flow

@jpchen Thank you for the pointer
@neerajprad The easiest way to exclude would be to not generate coverage for example
https://github.com/uber/pyro/blob/dev/.travis.yml#L75
I will update the PR

@neerajprad The easiest way to exclude would be to not generate coverage for example
https://github.com/uber/pyro/blob/dev/.travis.yml#L75

That's right. we can just remove it from the examples stage.

Updated as per above, please review

Looks good! Thanks for contributing.


Django 3.0 support currently broken (django.utils.six)

dpaste is waiting for django-csp to release a new version Pypi: https://github.com/mozilla/django-csp/issues/129
The current workaround to uninstall django-csp and reinstall their Git master branch: https://github.com/bartTC/dpaste/blob/f86f298a03d14944fd083dc496faf6494a44af04/Dockerfile#L46-L48

Fixed in dpaste v3.5


Null safe migration for fuchsia remote debug protocol

Mostly just from dart migrate, plus deleting some now unreachable code and a few tweaks/hints that seemed right to me.
@chaselatta  - any chance you can verify this doesn't break fx attach?
Required for https://github.com/flutter/flutter/issues/71379

Going to see if I can run this through some internal testing that might exercise that.

Going to see if I can run this through some internal testing that might exercise that.

Per @chaselatta this is working internally, with one exception being that an // ignore: await_only_futures might not actually be doing what we want it to.
If that's the case, we might need to roll vm_service internally as part of the flutter roll :(

Per @chaselatta this is working internally, with one exception being that an // ignore: await_only_futures might not actually be doing what we want it to.
If that's the case, we might need to roll vm_service internally as part of the flutter roll :(

Also, this needs an internal buildrule update, which I'll file a g3 fix for - but I think it needs to be approved before I can do that.

Also, this needs an internal buildrule update, which I'll file a g3 fix for - but I think it needs to be approved before I can do that.

We will also need to update the build rule in the fuchsia repo but I can add that for you.

We will also need to update the build rule in the fuchsia repo but I can add that for you.

Regarding the vm_service, when we roll this into fuchsia we will roll the version of vm_service that you are using locally. I didn't realize you had updated the version so I was still using version 5.5.0 locally so this will resolve itself when we roll.

Regarding the vm_service, when we roll this into fuchsia we will roll the version of vm_service that you are using locally. I didn't realize you had updated the version so I was still using version 5.5.0 locally so this will resolve itself when we roll.

I'll open a g3 fix for this.

I'll open a g3 fix for this.


Refactoring

Instead of building Dockerfile-postgres used PostgreSQL + postgis.
Refactored web module.

@gen1us2k could you review this PR?


Fix redshift_data hook to considered access and secret key from the connections object not from extra

Considered access and secret key if it is passed in connection login and password field
Considered AWS session token if it is passed in extra_config

closes: #741

@pankajastro @rajaths010494 Addressed your review comments, can you please take a look at it


Add Kotlin support.

Add default argument to createTempFileWithCode which accepts file
extension. Kotlin requires the correct file extension in order to
compile, and the temporary file for selection based execution does not
have a file extension.
Delete built jar after running. Other grammars don't seem to do any
clean up (Rust, Obj-c), but I'm not sure if this is intentional.

I have a feeling that Atom's API has a way to provide an extension (maybe multiples though?), which could be a more general purpose way of doing this.

Thanks for the addition! While you're at it, feel free to put Kotlin on the README.

Oops, I thought I had. I'll add it.

how could I run a kotlin script (a file with extension .kts)?. From the command line it would be kotlinc -script file.kts


Links in Twython docs to Twitter API docs all now broken

Every link in the Twython docs to the Twitter API documentation is now broken, subsequent to a rejig by Twitter of their own documentation.
Gah!

https://github.com/ryanmcgrath/twython/pull/463

thanks very much for your efforts.
Hadn't searched issues properly b4 posting :(

It's the opposite -- I hadn't searched the issues before I made a PR. This issue predates the PR :)


Made the randomization cryptographically safe

The Math.random() function in JavaScript uses pseudo-random therefore it can be predicted very easily. Thus making the password generator unsafe. With the 'crypto' package npm has, it is now nearly impossible to predict the outcome.

thx


CI: use docker base bcc

use docker based bcc instead of build bcc by us.
Signed-off-by: Sam Yuan<EMAIL_ADDRESS>

@rootfs , there is no deb in ghcr.io/iovisor/bcc:ubuntu-20.04 ... strange....

@SamYuan1990 let's build the bcc deb in this repo https://github.com/sustainable-computing-io/kepler-ci-artifacts/

447363047

what's this magic number?

that is the artifact ID.
It looks the artificat are only valid for 90 days. Can you help to make the bcc pkg as a release pkg instead of build artifact?


Historical data, and how can we help

I see there is currently no way to fetch historical data. Would this be possible to implement?
I would also like to help out with development. If you have a to-do list, it would be great to share it. Thanks!

Hello there,
Historical data
I am not sure to understand what you mean by « historical data » is it possible to send me an example ?
Development
I would love to get some help.
I have prepared a new structure : so people can add/modify a feature without having to look at other features code.
Also have a todo list.
Will try to share both the refactoring and the todo list this weekend.
Thanks

Closing this issue.
Feel free to join me on discord if you want to contribute.
My contact details are on my github profile.


Drawer doesn't close  if it's open and back is pressed

When the drawer is open and you press back instead of closing it does what's in the onbackpressed method. Any solution

U can add this line of code to your menu list's (listview) click listener:
YourDrawerLayout.closeDrawers();
and then it will work !!!

thanks