Improve reporting (phase 2)

This will implement the second phase of the reporting update. Supersedes #126 which was from a branch in a fork; all can commit to this branch. See there for more comments & discussion.
See also:

iiasa/message_ix#206 for corresponding changes to message_ix.
iiasa/message_data#41 for corresponding changes to the MESSAGE global model.
iiasa/message_ix#149 master issue.

Progress
Address requirements from wiki:

[x] A1. Provide equal support for any type of model that can be built on the ixmp.
[x] A2. Support use of exogenous data.
[ ] A3. Support basic operations:

[x] A3i. Weighted sums using model or exogenous weights.
[x] A3ii. Disaggregation using model or exogenous shares.
[ ] A3iii. Interpolation: linear, exponential, etc.

[x] A4. Support operations using quantities at different levels of aggregation.
[x] A5. Support user-defined operations.
[x] A6. Duplicate or clone existing operations for multiple other sets of inputs or outputs.
[ ] A7. Support renaming of quantities using multiple name mappings:

[x] A7i. …given programmatically.
[ ] A7ii. …loaded from file.

[x] A8. Compute only a subset of quantities from a larger/complete report.

[x] A8i. …for testing/development use-cases.
[x] A8ii. …for high-performance use-cases.
[x] A8iii. …using command-line arguments or other straightforward inputs to specify the subset.

[x] A9. Handle units for quantities.

[x] Both quantities with provided units, and quantities without units.
[x] Derive units for operations such as division and multiplication.

[x] A10. Provide automated description of how quantities are computed, as text (console output) or image.
[ ] A11. Callable through retixmp (tests require #135)

PR checklist:

[x] Tests added (ongoing)
[x] Documentation added — preview here.
[x] Description in RELEASE_NOTES.md added

Miscellaneous:

[x] Choose target release: 0.3 or 1.0?
[ ] Decide: this adds dependencies on dask[array] (thus toolz), graphviz (for dask.visualize), pint, and xarray. Should these be non-optional requirements, or extras (ixmp[reporting])?
[ ] Per @gidden comment in superseded PR, provide user-friendly exception handling when bad units are encountered.

closing in favor of #150


Add test coverage for MHSM and local cryptography

Resolves #16713
Resolves #18864
Temporarily works around #18800 by trimming leading zeros coming back from the service after updating a key and before asserting equality.

@schaabs @christothes @pakrym the PR is not actually that big - only 10 files, and mostly small changes - if you look at the non-recordings: https://github.com/Azure/azure-sdk-for-net/pull/18902/files?file-filters[]=.cs&file-filters[]=.csproj


Bug - query, fetch and get not returning promise if rejected

Hi dude
take a look at lines: 1790, 2175, 2609, 2643
https://github.com/VasilioRuzanni/angular-modelizer/blob/master/dist/angular-modelizer.js#L1790
You fire $q.reject but you never return it so you can't catch the promise
discovered this when route got resolved even when server returned an error

@dani3l Thanks for the catch! Will take a look. Thanks!

@dani3l Fixed, feel free to reopen or create another one if there are any related issues.

cool. thanks :)


Fix or update Block APIs in JSON_RPC_API.md file

Change summary:

Fix or update Block APIs in JSON_RPC_API.md file
Spin off Consensus APIs from Block APIs

Related issues:

https://github.com/ainblockchain/ain-blockchain/issues/1235

Thanks for the review! @jiyoung-an  Now merging..


fetch submodules explicitly

I think I understand the motivations here, but just to be clear, this is trying to:

Prevent checking out code that isn't needed for the current build target
Prevent developers forgetting to initialize submodules before building

Point 1. hasn't been a major issue so far, but will be more annoying if we add all of our Windows dependencies as submodules. Point 2. seems to be only an occasional problem that's easily corrected, but it does consume some time to remind developers about this step.
These are real practical problems, however I have conceptual concerns with this approach. I think many developers (myself included) think of a build system as having a distinct role from a source control system. Conflating these two may cause more confusion than it's worth.
We can take other steps to reduce these problems without changing the nature of our build process, e.g. shallow clones of submodules can reduce the size of downloads by orders of magnitude.

For 2. we have a warning that hints to use git submodule update --init --recursive.
This could also say 'Please run ./get_dependencies.sh [linux|android|....]'. The problem with the global recursive is that one fetches also submodules that we don't need at all, like core/include/earcut.hpp/glfw. That's also a reason why I would prefer to explicitly checkout submodules.
The get_dependencies script could also take care of fetching shallow clones when one just wants to build the tangram. For development I find it comfortable to be able to work on the submodules directly.


Can I attach a link programmatically using pyrobolearn library ?

I need this capability for attaching different types of grippers or end-effectors to robot or change their position/orientation through code rather than changing the URDF.

Yes this is possible.


Update various field names to their v2 api equivalent

Description
Update various field names to their v2 api equivalent - a few field names were renamed during v2 api migration. This update should get them. Note that I looked for confignamev1: in libcalico-go/lib/apis/v2/* to locate renamed fields.

Todos

[X] Tests - see https://github.com/projectcalico/calicoctl/pull/1750

Release Note

None required

Good catch!


GPIO labels

Clarify the fact that these are logical GPIO numbers, as opposed to physical pin numbers - since actual pin numbers are device-dependent, and since there is a risk of someone ignorant (like me!) thinking these are actual pin numbers, it's probably safer to designate them as "GPIO" pins.

Hey there @mindplay-dk , we're going to stick with the "pin" language in our code base. Thank you for the PR suggestion, please stop by our discord at https://discord.gg/Nc2ByRMk if you'd like to chat with the dev group about changes and suggestions. We're very active in #firmware-development !

Perhaps your documentation should clarify this then?
The software itself adapts in other ways to the device it's installed on - some people might expect "pin" to be the actual pin numbers on the device. Well, why not. The printed pin numbers on the Pico are "1, 2, 3", exactly the way they're shown in the manual and in the software - while the printed GPIO pins are labeled "GP1, GP2", etc.
I'm obviously new at this. Just trying to help others find their way and avoid mistakes. 🙂


Community guidelines for contributing and seeking support are not clear

Following the JOSS review, one of the items is:

Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

However, I think the community guidelines are not clear. The closest is the following line at the top of the README:

Pull requests, suggestions, and issues are very welcome.

In particular, it's unclear to me how to contribute. The pose2sim repository on the github does not have the code, and people outside of INRIA cannot comment on the INRIA gitlab .
Furthermore, it would be useful to have a code standard or some kind of guideline for contributing.
The README points to this issues page, which is clear enough. It is confusing to have separate github and a gitlab repositories for issues and code still.
I'm not sure where I should seek support. Is there a documentation website for this software? Is this github issues page the standard reference? It would help to specify this precisely.

Copied issue to the new repository:
https://github.com/perfanalytics/pose2sim/issues/1


Rev 1.0 PCB: DNP components are stuffed

@sglow discovered 5V on the CC-3V3 rail. Looks like this is because JLCPCB stuffed many of the DNP components in the BOM. Fix: remove R2, R73, R75, R77. R67, R17, R18, R59, R60, R68, R69

Some of those resistors are for setting different voltage options for the sensors, and they come in pairs.  You're only supposed to have one of the two populated, as stipulated by the BOM.  If you have both populated, as they are on the board, it bridges the 3.3V and 5V domains.  This may cause problems with IO signaling levels and ADC scaling.  PCBs SN 01, 02, 03, and 05 were shipped with this error intact.

Single-iron resistor removal tips:
Step 1: Set the iron to 300C and let it heat up.

Step 2: Apply a ball of solder to each end of the part so that the tip can reach both ends simultaneously.  Avoid touching other parts.

Step 3: with a clean iron (a couple stabs into the brass cleaning iron will do it), contact both balls simultaneously.

Step 4: when the solder has melted, sweep the part off in a direction where it will not contact other parts.  The solder has some adhesion so you should be able to sweep either laterally or longitudinally and the part will stick to the iron.  It might take a couple tries.

Step 5: Clean off the tip in the brass sponge again, then use the hot iron to clean up any stay solder left behind or on other components.

Locations of the 11 resistors listed:


[Bug]: Recipe is not getting fetched in Recipe App

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Recipe is not getting fetched in Recipe App. When searched for any recipe it is giving error in console.
Expected behavior
We should add cards for few recipes on the frontend itself and there should be a feature to search for the recipes.
Add ScreenShots

On which device are you experiencing this bug?
Chrome
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a SSOC'24 contributor
[X] I have starred the repository

@Archiesachin u are assigned


Dev

Description
Hello,

I have added the darkTheme property featured in the MaterialApp widget to the CupertinoApp widget to take advantage of automatic detection of system-wide dark mode. This is especially useful for iOS developers who use the CupertinoApp widget if they want their app to automatically change themes depending on the system's theme. Note that I am not an experienced flutter developer nor am I especially familiar with the internal workings of the engine.

Related Issues

darkTheme property lacking from CupertinoApp widget

Tests
I added the following tests:

hello_world test succeeded

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.
I read the Contributor Guide and followed the process outlined there for submitting PRs.
I signed the CLA.
I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
I read the Tree Hygiene wiki page, which explains my responsibilities.
I updated/added relevant documentation (doc comments with ///).
All existing and new tests are passing.
The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
I am willing to follow-up on review comments in a timely manner.
Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.
No, no existing tests failed, so this is not a breaking change.
Yes, this is a breaking change. If not, delete the remainder of this section.
I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
I got input from the developer relations team, specifically from: Replace with the names of who gave advice
I wrote a migration guide: Replace with a link to your migration guide*

@owenkealey did you create your feature branch by branching off of dev? It looks like there are some regressions in the diff here.

@christopherfujino I might have forgot to update my fork before submitting the PR. Should I close and submit a new one with up to date branch?

@christopherfujino I might have forgot to update my fork before submitting the PR. Should I close and submit a new one with up to date branch?

Yes. The most important thing is that when creating a new branch, branch from master, and not a release branch.

Closing to reopen later.


Allow SVGs in getting started to be themeable

We'd need to export our color tokens as css variables, which we can access in SVGs. This would allow illustrations to be themed like:
https://user-images.githubusercontent.com/35271042/122453947-a0b52180-cf5f-11eb-967b-4dffd484b701.mp4

This shipped last iteration


HSEARCH-5086 Upgrade to Lucene 9.10.0

https://hibernate.atlassian.net/browse/HSEARCH-5086

@marko-bekhta CI doesn't agree :|

Yeah 😞 and what's sad about it is that it complains about
[WARNING] /mnt/workdir/jenkins/workspace/hibernate-search_PR-3971/backend/lucene/src/main/java/org/hibernate/search/backend/lucene/search/extraction/impl/ExtractionRequirements.java:[89,40] [deprecation] create(Sort,int,int) in TopFieldCollector has been deprecated
[WARNING] /mnt/workdir/jenkins/workspace/hibernate-search_PR-3971/backend/lucene/src/main/java/org/hibernate/search/backend/lucene/search/extraction/impl/LuceneCollectors.java:[96,17] [deprecation] search(Query,Collector) in IndexSearcher has been deprecated
[WARNING] /mnt/workdir/jenkins/workspace/hibernate-search_PR-3971/backend/lucene/src/main/java/org/hibernate/search/backend/lucene/search/extraction/impl/LuceneCollectors.java:[171,16] [deprecation] search(Query,Collector) in IndexSearcher has been deprecated

Which was supposed to happen in Lucene 10... but I guess 10.. 9.10 🤷🏻 😃

Well, that's fair from them since it's just a deprecation.
I think we can suppress the warnings for now. But we'll really need to work on the switch soon.
BTW, we may want to enable deprecation warnings in dependency update jobs... WDYT?


Feature: Translation

Is your feature request related to a problem? Please describe.
I wanna collaborate to Spanish translation.
Describe the solution you'd like
Allow to collaborate with translations to other languages.
Additional context
I really like this whishlist, easy docker compose, pc browser and cell phone browser looks really good! And reverse proxy usage without any complicated configuration!,  Thanks!

Thanks! This is definitely something I want to set up at some point

I'd love to help with the French translation!

Hey! I've finished adding support for translations. Translations will be managed through Weblate. You can create an account or log in with Github to start translating. So far I've added Spanish, French, and Swedish. If there is another language you can/wish to contribute to, then you can request it through Weblate here, and I'll get it added

I wanted to request german, but the link does not work. No public project found.

Thanks for the report. I'm looking into the Weblate access. In the meantime, I will add German, thanks!


the demo.py

There is  a command in Readme.md need demo.py, but I can't find the project. would you send me the code of that? I just learn it recencently ,not familiarly。。。

The code of demo is similar to "test" phase, you can write it by yourself. (I am sorry, i delete the demo code in my own computer.---I will update this code in the future)

Hi @kunfei1 @AceCoooool ! I did a demo.py, I can create a PR if you give me access rights.

@eram1205 OK，thanks for your help !

@eram1205 Thank you！

@kunfei1  I have add the demo. （the pre-trained model will provide tomorrow）


FastAdapter for classes who already extends from a base parent

Hi Mike,
Just wondering how I could use FastAdapter to apply to child classes that already extends a common base class.
Suppose I have a collection of sport players... BasketballPlayer, FootballPlayer, SoccerPlayer, BaseballPlayer, GolfPlayer.  They each could inherited from a common class SportPlayer, which could include many shared properties such as Name, Location, Height, Weight, Bio, etc.  However, each sport player type differs on how their stats are being tracked... "Par" stat of a GolfPlayer would not exist in other classes.
Let's suppose a list of ALL players (regardless of their sport) needs to be displayed... it should render the rows differently depending on which sport they play.  We're talking about multiple layout types in the same list.
I imagine that each specific sport player concrete class would provide its own type of ViewHolder, type, and layout, as well as how it should bind its views.  However, we're facing double inheritance: Extending from the base class and extending from AbstractItem.

@duyngn hi
If you can't extend from the AbstractItem you either could just implement the IItem interface, or you choose to split up Model and Item as shown in the MultiTypeGenericItemActivity
https://github.com/mikepenz/FastAdapter/blob/develop/app/src/main/java/com/mikepenz/fastadapter/app/MultiTypeGenericItemActivity.java
It just uses one model class, but you can easily change it to allow different model types too, and you can then simply define which item to choose for which model or any logic which is used.

Thanks Mike,
I think I got it working... more of an exercise to mess with your library :)
public abstract class SportPlayer<Item extends AbstractItem<Item, VH>, VH extends RecyclerView.ViewHolder> extends AbstractItem<Item, VH> {}
public class BasketballPlayer extends SportPlayer< BasketballPlayer, BasketballPlayer.ViewHolder> {}
public class GolfPlayer extends SportPlayer< GolfPlayer, GolfPlayer.ViewHolder> {}
This will enforce the concrete player classes to implement:
public int getType()
public int getLayoutRes()
But it won't enforce the concrete player classes to implement:
public void bindView(ViewHolder vh)
That's because AbstractItem already has an implementation of this function.
So a manual override for bindView() must be done in each concrete player class.

@mikepenz can you add an example of how it to allow different model types?, even a basic example here?
I have the following:
public abstract class BaseItemWrapper<Item extends BaseItemWrapper<?, ?>, VH extends RecyclerView.ViewHolder> extends AbstractItem<Item, VH> {

}

``java
public class NewsItemWrapper extends BaseItemWrapper<NewsItemWrapper, NewsItemWrapper.ViewHolder> {
}
```java
public class AdItemWrapper extends BaseItemWrapper<AdItemWrapper, AdItemWrapper.ViewHolder> {
}

now how create the GenericItemAdapter out of this?

i just came across the same problem and found this thread, but for some reason i couldnt really understand the solution offered and also failed implementing it by trying to copy it.
i have however found a different, less complicated (at least in my mind) solution.
@mikepenz please tell me if you think this is a "bad" way to solve the issue.
here is the declaration of my base (or "father") class:
public class MyItem<T extends MyItem, VH extends RecyclerView.ViewHolder> extends AbstractItem<T, VH>
and here is the definition of the inherited (or "son") class:
public class MyItemAlso extends MyItem<MyItemAlso, MyItemAlso.ViewHolder>
thats it!
the "father" class would have to override the methods "getType" and "getLayoutRes" which in my case don't have any meaning because "MyItem" is simply used to hold shared information and only classes extending it are to be displayed in the recyclerView. so in my case these methods can simply call the "super" methods.
however if you wish for the "Father" class to be displayed as an item in the recyclerView, simply implement these methods as you were with a normal AbstractItem, and the same goes for any inherited (or "son") classes

@or-dvir it's totally fine. In general the type definitions in Java will help you while coding the most, the code which is executed in the end does not care much about it anyways.


Build-deploy error

Hello,
I have been following the tutorial and it was working until I added an Rmd file. Github actions failed with the message:
Error in loadNamespace(x) : there is no package called ‘jsonlite’
I changed the .Rmd to .qmd and changed some syntax but that did not fix the issue.
I noticed you had a similar issue, but it is not clear how this can be resolved. What is going on and how can I fix it?

Hi @bdturley !
Thanks for posting and providing links!
This error is because your r-example.qmd has R code in it, and the GitHub Action from the tutorial book is not set up to expect R.
I created a pull request with the update you need: https://github.com/bdturley/quarto-test-drive/pull/1. It does the following:
To update your GitHub Action to include R code, you can add the following to your quarto-publish.yml (referenced from quarto-dev's github):
- name: Install R
  uses: r-lib/actions/setup-r@v2
  with:
    r-version: '4.2.0' # The R version to download (if necessary) and use.

Thanks for the patch @jules32. But it still didn't work. I did get it to work by also adding:
      - name: Install rmarkdown         run: |           install.packages("rmarkdown")         shell: Rscript {0}
The error message keep saying the rmarkdown was not there, so I searched around to see how to install packages. However, the build took almost 7 minutes. That seems like alot and I am wondering if there is a better way to do this especially if the code has a lot package of dependencies.
My takeaway is that maybe this quarto-github pages is best used for content and not complex R code. I am curious to see your thoughts on this.

I really appreciate the time you took to help me out @jules32!
As an update to my previous comment, Github caches so the build took less time the sequent builds. I enjoyed very much the OpenScapes sessions this summer. Thanks to everyone's hard work and dedication!
Cheers!

Hi @bdturley !
Glad you got past this particular issue but that is strange that it took so long. And cool to learn about the cache as well - I haven't played around with that. I (ironically?) don't have a lot of experience with github-actions with R! We've mostly used github-actions with "freezing" python code and for repos with no code at all (besides quarto).
If the slowness continues, I wonder if you want to try quartopub (https://quartopub.com/), which is native quarto publishing!


bug fix  - Time.parse test_find_tracking_info_should_handle_special_cases

Hello everyone ,
Sorry my english :)
I am living in Brazil, when I was executing the application tests returned error below

To resolve the problem the conversion the time, i  changed the code

Looks like this test is now failing on Travis CI.

@wvanbergen, ok i´II  look.


Support for ESP-IDF v5.1 CI

Build with activated ESP-IDF environment with 5.1 is failing:

  --- stderr
  Build configuration: BuildConfig {
      esp_idf_tools_install_dir: None,
      esp_idf_sdkconfig: None,
      esp_idf_sdkconfig_defaults: None,
      mcu: None,
      native: NativeConfig {
          esp_idf_version: Some(
              Tag(
                  "v5.1",
              ),
          ),
          esp_idf_repository: None,
          esp_idf_cmake_generator: None,
          idf_path: Some(
              "/Users/rust/projects/esp-idf-5",
          ),
          extra_components: [],
          esp_idf_components: None,
      },
      esp_idf_sys_root_crate: None,
  }
  Using activated esp-idf v5.1.0 environment at '/Users/rust/projects/esp-idf-5'
  ERROR: /Users/rust/projects/esp-idf-rs-test/.embuild/espressif/python_env/idf5.1_py3.9_env/bin/python doesn't exist! Please run the install script or "idf_tools.py install-python-env" in order to create it
  CMake Error at /Users/rust/projects/esp-idf-5/tools/cmake/build.cmake:342 (message):
    Some Python dependencies must be installed.  Check above message for
    details.
  Call Stack (most recent call first):
    /Users/rust/projects/esp-idf-5/tools/cmake/build.cmake:480 (__build_check_python)
    CMakeLists.txt:14 (idf_build_process)

  thread 'main' panicked at '
  command did not execute successfully, got: exit status: 1

  build script failed, must exit now', /Users/rust/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.48/src/lib.rs:975:5

Here are my test results on Linux:
Generate command:
cargo generate --git https://github.com/esp-rs/esp-idf-template cargo --name test50 --vcs none --silent -d mcu=esp32 -d std=true -d espidfver=mainline -d devcontainer=false

Using activated environment with esp-idf master branch:

  --- stderr
  Build configuration: BuildConfig {
      esp_idf_tools_install_dir: None,
      esp_idf_sdkconfig: None,
      esp_idf_sdkconfig_defaults: None,
      mcu: None,
      native: NativeConfig {
          esp_idf_version: Some(
              Tag(
                  "v5.1",
              ),
          ),
          esp_idf_repository: None,
          esp_idf_cmake_generator: None,
          idf_path: Some(
              "/home/sergio/.espressif/frameworks/master",
          ),
          extra_components: [],
          esp_idf_components: None,
      },
      esp_idf_sys_root_crate: None,
  }
  Using activated esp-idf v5.1.0 environment at '/home/sergio/.espressif/frameworks/master'
  ERROR: /home/sergio/Documents/Espressif/tests/test51/.embuild/espressif/python_env/idf5.1_py3.10_env/bin/python doesn't exist! Please run the install script or "idf_tools.py install-python-env" in order to create it
  CMake Error at /home/sergio/.espressif/frameworks/master/tools/cmake/build.cmake:360 (message):
    Some Python dependencies must be installed.  Check above message for
    details.
  Call Stack (most recent call first):
    /home/sergio/.espressif/frameworks/master/tools/cmake/build.cmake:498 (__build_check_python)
    CMakeLists.txt:14 (idf_build_process)

  thread 'main' panicked at '
  command did not execute successfully, got: exit status: 1

  build script failed, must exit now', /home/sergio/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.48/src/lib.rs:975:5
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Same result as @georgik had on MacM1.

Activated env
error[E0428]: the name `i2s_channel_t` is defined multiple times
     --> /Users/sergio/Documents/Espressif/tests/dev51/target/xtensa-esp32-espidf/debug/build/esp-idf-sys-cf0cb59a10fbadc3/out/bindings.rs:75590:1
      |
75546 | pub struct i2s_channel_t {
      | ------------------------ previous definition of the type `i2s_channel_t` here
...
75590 | pub type i2s_channel_t = c_types::c_uint;
      | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `i2s_channel_t` redefined here
      |
      = note: `i2s_channel_t` must be defined only once in the type namespace of this module

error[E0117]: only traits defined in the current crate can be implemented for primitive types
     --> /Users/sergio/Documents/Espressif/tests/dev51/target/xtensa-esp32-espidf/debug/build/esp-idf-sys-cf0cb59a10fbadc3/out/bindings.rs:75545:17
      |
75545 | #[derive(Debug, Copy, Clone)]
      |                 ^^^^
      |                 |
      |                 impl doesn't use only types from inside the current crate
      |                 `u32` is not defined in the current crate
      |
      = note: define and implement a trait or new type instead
      = note: this error originates in the derive macro `Copy` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0117]: only traits defined in the current crate can be implemented for primitive types
     --> /Users/sergio/Documents/Espressif/tests/dev51/target/xtensa-esp32-espidf/debug/build/esp-idf-sys-cf0cb59a10fbadc3/out/bindings.rs:75545:23
      |
75545 | #[derive(Debug, Copy, Clone)]
      |                       ^^^^^
      |                       |
      |                       impl doesn't use only types from inside the current crate
      |                       `u32` is not defined in the current crate
      |
      = note: define and implement a trait or new type instead
      = note: this error originates in the derive macro `Clone` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0117]: only traits defined in the current crate can be implemented for primitive types
     --> /Users/sergio/Documents/Espressif/tests/dev51/target/xtensa-esp32-espidf/debug/build/esp-idf-sys-cf0cb59a10fbadc3/out/bindings.rs:75545:10
      |
75545 | #[derive(Debug, Copy, Clone)]
      |          ^^^^^
      |          |
      |          impl doesn't use only types from inside the current crate
      |          `u32` is not defined in the current crate
      |
      = note: define and implement a trait or new type instead
      = note: this error originates in the derive macro `Debug` (in Nightly builds, run with -Z macro-backtrace for more info)

No activated env
 Using esp-idf v5.1.0 at '/Users/sergio/Documents/Espressif/tests/dev51/.embuild/espressif/esp-idf/v5.1-dev'
  ERROR: tool cmake does not have versions compatible with platform macos-arm64
  Error: Could not install esp-idf

  Caused by:
      command '"/Users/sergio/Documents/Espressif/tests/dev51/.embuild/espressif/python_env/idf5.1_py3.10_env/bin/python" "/Users/sergio/Documents/Espressif/tests/dev51/.embuild/espressif/esp-idf/v5.1-dev/tools/idf_tools.py" "--idf-path" "/Users/sergio/Documents/Espressif/tests/dev51/.embuild/espressif/esp-idf/v5.1-dev" "--tools-json" "/var/folders/_w/919x4xzs7zl5kyydzg5nr_v40000gn/T/.tmpcKOpbl" "install" "cmake"' exited with non-zero status code 1


VSCode Razor highlighting does not handle nullability well in @code blocks

As soon as a property is declared that is of a nullable type, i.e. ? suffix, the syntax highlighting of the rest of the file seems to get confused.
Reproduce

Generate standard template project: dotnet new blazorserver
Open in VS Code
Open FetchData.razor
Observe syntax highlighting correctly highlights WeatherForecast as a class/type

Add nullable field

Add string? test; before the WeatherForecast declaration
Observe that the highlighting of WeatherForecast is still correct

Add nullable property

Add string? test1 {get; set;} before the WeatherForecast declaration
Observe that the highlighting of WeatherForecastnow reverts to generic text

It does not seem to make any difference if the  setting on the project file is enabled or not.

I also have this issue :(

I am also having this issue as well.

A note since it seems to have been lost, the issue was filed against csharp-tmLanguage as https://github.com/dotnet/csharp-tmLanguage/issues/191.


CollectionView didSelectItemAt not being called

Hello,
I've created a pull request here which shows a problem where didSelectItemAt in UICollectionViewDelegate is not being called when I use Gemini.
Here is the link:
https://github.com/shoheiyokoyama/Gemini/pull/2
Does anyone else have this problem or knows how to work around this?
Thank you.

@agarbowitzOmadaHealth
I resolve this problem and released version 1.1.2.
Thank you for reporting 👍


Add support for NPM publish with --publish option

Looks good to me (and also something I've wanted for a while ;) ).

I was gonna PR this tonight if he hadn't :D


can't find a python file

when ran the 'visualization.py' file under the core.utils, the codes line 'from core.models.stagewise_search import vgg_stage_wise_connectivity_matrix_cross_task' occures a error as there is no 'stagewise_search' under the file of core.models.
I hope you can check whether forgetting put the python file in the project.
Thank you for your reply !

Hi, thanks for pointing it out. The __main__() in visualization.py  was only meant for testing purposes when the code was developed. As the codebase was finalized, some function names and filenames have been changed and the __main__() function became deprecated. Though this does not impact any usage of visualization.py in the main program. I have removed __main__() to avoid any future confusion.


Be clear about desired vs actual transmission

Currently, inside xray centring, we take the transmission specified in the ispyb section of the supplied parameters to mean the desired transmission and set it on the device. We then read this back to find the actual transmission and put that back in the ispyb params object to put in ispyb.
We should instead specify the desired transmission as part of the experiment parameters, then use that to set on the hardware and read the actual back from there to put in ispyb. Note that the removal of the putting the readback into ispyb_params will be done as the last part of https://github.com/DiamondLightSource/hyperion/issues/1218. So this issue mostly boils down to move desired_transmission into the experiment params (not in the base class as not used by PinTipCentring)
Acceptance Criteria

The desired transmission is set in the experiment params
Plans no longer make reference to ispyb_params for this

We think 1 day


Popper.js error

Bug description:
Getting this error when i want to serve my app with ng2-semantic-ui included:
<EMAIL_ADDRESS>(104,3): Cannot redeclare exported variable 'default'.
node_modules/popper.js/index.d.ts (106,24): Cannot redeclare exported variable 'default'
It seems to be related to the recent popper.js update 1.11.0, specifically the addition of types to their package with the pull #351. Manually downgrading popper.js to the older 1.10 branch temporarily helps to avoid the error.
Version of Angular, ng2-semantic-ui, and Semantic UI:

Angular: 4.3.1
ng2-semantic-ui: 0.9.3
Semantic UI: 2.2.11

Is this a problem with the type definitions shipped with Popper.js or with the way the lib is used in this repo?

I think it's the latter. @types/popper.js is set as dependency in this repo which should cause the error.

Ahh ok I see whats happened. I'll now that Popper.js is including their own types I no longer need to depend on @types/popper.js. FYI the reason it's a dependency is because I re-export a couple of definitions from the lib hence the error. Will get a fix out in the next release.

Workaround for now is manually installing<EMAIL_ADDRESS>

As this is affecting quite a few people, I'm going to release a hotfix for it ASAP.

@edcarroll what could have been done on Popper.js side to avoid this problem?

@FezVrasta so I've had a play with the code and what's happened is the type definitions included with popper.js are actually different to the ones in @types/popper.js. Normally when a module includes its own defs the old @types ones are ignored, however in this instance they conflicted, causing the errors to appear.
As far as I can tell the types now included in popper.js will have broken all builds requiring the old types, because the original ones allows you to write:
import Popper from "popper.js";

const myPopper = new Popper(...);

const modifiers:Popper.Modifiers = ...;

Whereas the guy that modified them in the Popper.JS PR has made it so you need to write:
import * as Popper from "popper.js";

const myPopper = new Popper.default(...);

const modifiers:Popper.Modifiers = ...;

Or (what I've done):
import Popper from "popper.js";
import * as PopperTypes from "popper.js";

const myPopper = new Popper(...);

const modifiers:PopperTypes.Modifiers = ...;

This is a step backwards, and I would recommend a new release that includes the old type definitions.

@FezVrasta it wouldn't let me tag you in my previous comment, not sure why. Here is the tag anyway

ping @giladgray, may you work on this?

@FezVrasta I'm happy to sort this out in a PR, as there are also a couple of other things missing in the type definitions that I'd like to fix 😄

@FezVrasta have just opened a PR that fixes the issues I've mentioned above.

0.9.4 is now live which locks down the Popper dependencies for now. @mvcoding this will sort out your build.

Great, thanks for the quick fix!

This seems to have popped back up.  popper v1.14.1 came out just a few days ago.  I've explicitly set it to use the older version to workaround for now: "popper.js": "1.12.9"
ERROR in ../node_modules/ng2-semantic-ui/dist/modules/sidebar/services/sidebar.service.d.ts(13,11): error TS2503: Cannot find namespace 'Popper'.
../node_modules/ng2-semantic-ui/dist/modules/sidebar/services/sidebar.service.d.ts(14,12): error TS2503: Cannot find namespace 'Popper'.
../node_modules/ng2-semantic-ui/dist/modules/sidebar/services/sidebar.service.d.ts(15,10): error TS2503: Cannot find namespace 'Popper'.
../node_modules/ng2-semantic-ui/dist/modules/sidebar/services/sidebar.service.d.ts(16,13): error TS2503: Cannot find namespace 'Popper'.

1.14.1 does export the namespace 🤔


ruff: 0.5.0 -> 0.5.1

Description of changes
Diff: https://github.com/astral-sh/ruff/compare/refs/tags/0.5.0...0.5.1
Changelog: https://github.com/astral-sh/ruff/releases/tag/0.5.1

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

The build fails with:
thread 'main' panicked at cargo-auditable/src/collect_audit_data.rs:77:9:
cargo metadata failure: warning: `/build/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
error: Package `ruff_python_ast v0.0.0 (/build/source/crates/ruff_python_ast)` does not have feature `schemars`. It has an optional dependency with that name, but that dependency us>

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: could not compile `ruff_python_formatter` (bin "ruff_python_formatter")

However, running the exact same build command:
CC_X86_64_UNKNOWN_LINUX_GNU=/nix/store/kp2j7yn0wzwq5piy494r54dafrh83s6s-gcc-wrapper-13.3.0/bin/cc \
CXX_X86_64_UNKNOWN_LINUX_GNU=/nix/store/kp2j7yn0wzwq5piy494r54dafrh83s6s-gcc-wrapper-13.3.0/bin/c++
CARGO_TARGET_X86_64_UNKNOWN_LINUX_GNU_LINKER=/nix/store/kp2j7yn0wzwq5piy494r54dafrh83s6s-gcc-wrapper-13.3.0/bin/cc CC_X86_64_UNKNOWN_LINUX_GNU=/nix/store/kp2j7yn0wzwq5piy494r54dafrh83s6s-gcc-wrapper-13.3.0/bin/cc CXX_X86_64_UNKNOWN_LINUX_GNU=/nix/store/kp2j7yn0wzwq5piy494r54dafrh83s6s-gcc-wrapper-13.3.0/bin/c++ \
CARGO_TARGET_X86_64_UNKNOWN_LINUX_GNU_LINKER=/nix/store/kp2j7yn0wzwq5piy494r54dafrh83s6s-gcc-wrapper-13.3.0/bin/cc \
CARGO_BUILD_TARGET=x86_64-unknown-linux-gnu \
HOST_CC=/nix/store/kp2j7yn0wzwq5piy494r54dafrh83s6s-gcc-wrapper-13.3.0/bin/cc \
HOST_CXX=/nix/store/kp2j7yn0wzwq5piy494r54dafrh83s6s-gcc-wrapper-13.3.0/bin/c++ \
cargo build -j 12 --target x86_64-unknown-linux-gnu --offline --profile release

from the nix-build -A ruff.src folder works perfectly fine.
Note:

I manually added --target-dir /tmp/ruff-target to the build command because we can't write in the nix store
This was executed from nix-shell -p rust-jemalloc-sys, the only dependency for this package

What could be wrong here ? Is it an upstream issue ? How should I report this to them ?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/rust-package-ruff-fails-to-build-only-in-sandbox/48792/1

@GaetanLepage
Adding schemars = ["dep:schemars"] to the features made it work for me:
  preBuild = ''
    sed -i crates/ruff_python_ast/Cargo.toml \
      -e '/\[features\]/aschemars = ["dep:schemars"]'
  '';

According to Features - The Cargo Book, if a package is marked as optional then this should be implicitly set. I don't know why explicitly specifying it fixes the issue or why it works when you manually build ruff from source.

As discussed in the upstream PR, It should be enough to patch the package with:
  # Fix compatibility with cargo-auditable
  # See: https://github.com/astral-sh/ruff/pull/12275#issuecomment-2221245280
  preBuild = ''
    sed -i 's/dep:schemars/schemars/' crates/ruff_python_ast/Cargo.toml
  '';

This is necessary at least for now until compatibility with cargo-auditable is fixed upstream.

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

6 packages marked as broken and skipped:

khoj
khoj.dist
open-webui
open-webui.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist

12 packages failed to build:

nbqa
nbqa.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.pyhanko
python311Packages.pyhanko.dist
python311Packages.xhtml2pdf
python311Packages.xhtml2pdf.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
vunnel
vunnel.dist

43 packages built:

dmarc-metrics-exporter
dmarc-metrics-exporter.dist
pentestgpt
pentestgpt.dist
python311Packages.instructor
python311Packages.instructor.dist
python311Packages.langchain
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langsmith
python311Packages.langsmith.dist
python311Packages.pytest-examples
python311Packages.pytest-examples.dist
python311Packages.python-lsp-ruff
python311Packages.python-lsp-ruff.dist
python311Packages.xsdata
python311Packages.xsdata.dist
python312Packages.instructor
python312Packages.instructor.dist
python312Packages.langchain
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langsmith
python312Packages.langsmith.dist
python312Packages.pytest-examples
python312Packages.pytest-examples.dist
python312Packages.python-lsp-ruff
python312Packages.python-lsp-ruff.dist
python312Packages.xsdata
python312Packages.xsdata.dist
ruff
ruff-lsp
ruff-lsp.dist
shell-gpt
shell-gpt.dist

Result of nixpkgs-review pr 324823 run on aarch64-linux 1

10 packages marked as broken and skipped:

khoj
khoj.dist
open-webui
open-webui.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist

8 packages failed to build:

nbqa
nbqa.dist
python311Packages.pyhanko
python311Packages.pyhanko.dist
python311Packages.xhtml2pdf
python311Packages.xhtml2pdf.dist
vunnel
vunnel.dist

43 packages built:

dmarc-metrics-exporter
dmarc-metrics-exporter.dist
pentestgpt
pentestgpt.dist
python311Packages.instructor
python311Packages.instructor.dist
python311Packages.langchain
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langsmith
python311Packages.langsmith.dist
python311Packages.pytest-examples
python311Packages.pytest-examples.dist
python311Packages.python-lsp-ruff
python311Packages.python-lsp-ruff.dist
python311Packages.xsdata
python311Packages.xsdata.dist
python312Packages.instructor
python312Packages.instructor.dist
python312Packages.langchain
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langsmith
python312Packages.langsmith.dist
python312Packages.pytest-examples
python312Packages.pytest-examples.dist
python312Packages.python-lsp-ruff
python312Packages.python-lsp-ruff.dist
python312Packages.xsdata
python312Packages.xsdata.dist
ruff
ruff-lsp
ruff-lsp.dist
shell-gpt
shell-gpt.dist

Result of nixpkgs-review pr 324823 run on aarch64-darwin 1

6 packages marked as broken and skipped:

khoj
khoj.dist
open-webui
open-webui.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist

46 packages failed to build:

dmarc-metrics-exporter
dmarc-metrics-exporter.dist
nbqa
nbqa.dist
pentestgpt
pentestgpt.dist
python311Packages.instructor
python311Packages.instructor.dist
python311Packages.langchain
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langsmith
python311Packages.langsmith.dist
python311Packages.pyhanko
python311Packages.pyhanko.dist
python311Packages.pytest-examples
python311Packages.pytest-examples.dist
python311Packages.xhtml2pdf
python311Packages.xhtml2pdf.dist
python312Packages.instructor
python312Packages.instructor.dist
python312Packages.langchain
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langsmith
python312Packages.langsmith.dist
python312Packages.pytest-examples
python312Packages.pytest-examples.dist
ruff-lsp
ruff-lsp.dist
shell-gpt
shell-gpt.dist
vunnel
vunnel.dist

9 packages built:

python311Packages.python-lsp-ruff
python311Packages.python-lsp-ruff.dist
python311Packages.xsdata
python311Packages.xsdata.dist
python312Packages.python-lsp-ruff
python312Packages.python-lsp-ruff.dist
python312Packages.xsdata
python312Packages.xsdata.dist
ruff

Result of nixpkgs-review pr 324823 run on x86_64-darwin 1

6 packages marked as broken and skipped:

khoj
khoj.dist
open-webui
open-webui.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist

46 packages failed to build:

dmarc-metrics-exporter
dmarc-metrics-exporter.dist
nbqa
nbqa.dist
pentestgpt
pentestgpt.dist
python311Packages.instructor
python311Packages.instructor.dist
python311Packages.langchain
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langsmith
python311Packages.langsmith.dist
python311Packages.pyhanko
python311Packages.pyhanko.dist
python311Packages.pytest-examples
python311Packages.pytest-examples.dist
python311Packages.python-lsp-ruff
python311Packages.python-lsp-ruff.dist
python311Packages.xhtml2pdf
python311Packages.xhtml2pdf.dist
python312Packages.instructor
python312Packages.instructor.dist
python312Packages.langchain
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langsmith
python312Packages.langsmith.dist
python312Packages.pytest-examples
python312Packages.pytest-examples.dist
shell-gpt
shell-gpt.dist
vunnel
vunnel.dist

9 packages built:

python311Packages.xsdata
python311Packages.xsdata.dist
python312Packages.python-lsp-ruff
python312Packages.python-lsp-ruff.dist
python312Packages.xsdata
python312Packages.xsdata.dist
ruff
ruff-lsp
ruff-lsp.dist

Result of nixpkgs-review pr 324823 run on aarch64-darwin 1

6 packages marked as broken and skipped:

khoj
khoj.dist
open-webui
open-webui.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist

29 packages failed to build:

dmarc-metrics-exporter
dmarc-metrics-exporter.dist
emacsPackages.lsp-bridge
nbqa
nbqa.dist
pentestgpt
pentestgpt.dist
python311Packages.langchain
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain.dist
python311Packages.pyhanko
python311Packages.pyhanko.dist
python311Packages.xhtml2pdf
python311Packages.xhtml2pdf.dist
python312Packages.langchain
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
tests.testers.lycheeLinkCheck.network
tests.testers.nixosTest-example
tests.testers.runNixOSTest-example
tests.trivial-builders.references
vunnel
vunnel.dist

31 packages built:

python311Packages.instructor
python311Packages.instructor.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langsmith
python311Packages.langsmith.dist
python311Packages.pytest-examples
python311Packages.pytest-examples.dist
python311Packages.python-lsp-ruff
python311Packages.python-lsp-ruff.dist
python311Packages.xsdata
python311Packages.xsdata.dist
python312Packages.instructor
python312Packages.instructor.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langsmith
python312Packages.langsmith.dist
python312Packages.pytest-examples
python312Packages.pytest-examples.dist
python312Packages.python-lsp-ruff
python312Packages.python-lsp-ruff.dist
python312Packages.xsdata
python312Packages.xsdata.dist
ruff
ruff-lsp
ruff-lsp.dist
shell-gpt
shell-gpt.dist

Result of nixpkgs-review pr 324823 run on x86_64-darwin 1

6 packages marked as broken and skipped:

khoj
khoj.dist
open-webui
open-webui.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist

51 packages failed to build:

dmarc-metrics-exporter
dmarc-metrics-exporter.dist
emacsPackages.lsp-bridge
nbqa
nbqa.dist
pentestgpt
pentestgpt.dist
python311Packages.instructor
python311Packages.instructor.dist
python311Packages.langchain
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langsmith
python311Packages.langsmith.dist
python311Packages.pyhanko
python311Packages.pyhanko.dist
python311Packages.pytest-examples
python311Packages.pytest-examples.dist
python311Packages.python-lsp-ruff
python311Packages.python-lsp-ruff.dist
python311Packages.xhtml2pdf
python311Packages.xhtml2pdf.dist
python312Packages.instructor
python312Packages.instructor.dist
python312Packages.langchain
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langsmith
python312Packages.langsmith.dist
python312Packages.pytest-examples
python312Packages.pytest-examples.dist
shell-gpt
shell-gpt.dist
tests.testers.lycheeLinkCheck.network
tests.testers.nixosTest-example
tests.testers.runNixOSTest-example
tests.trivial-builders.references
vunnel
vunnel.dist

9 packages built:

python311Packages.xsdata
python311Packages.xsdata.dist
python312Packages.python-lsp-ruff
python312Packages.python-lsp-ruff.dist
python312Packages.xsdata
python312Packages.xsdata.dist
ruff
ruff-lsp
ruff-lsp.dist


Pact Rebase

Every one from the 10+ items on the list has been implemented as requested or otherwise denied after thorough consideration.
Compromises Made:

TC removed from secret room :: replaced w. Pyjama bag
Deathsquad mask in secret room renamed and its armor value removed. Mask type altered.

Changes Denied:

Cool brown windows next to power :: kept them. They look cool and nobody else has complained about them yet.
Request add power monitors to substation rooms :: No changes because every substation room already has a power monitor.

Complete List

Pipes and doors around cryo fixed.
Meteor shielding improved, but only by a little bit. (as requested)
Spade and Sustenance vendor added to Perma.
Captains room given antique pistol (it's in the locker)
Telecoms room made slightly bigger. (Grog was right on this one. It was very uncomfortable to look at.)
Telecrystals removed from secret room and replaced with something less broken but still fun.
Special mask no longer has armor, but now has a unique name.
Grilles added to bar and salvage.
Added borg recharger to AI room
Added Intellicard to AI room
Added Intercom next to AI (Not 100% if needed, but the requester was kind and made a fair point)
Northeast solars made a little nicer. Will redo southwest solars at a later date should it be needed.

Checking about everywhere I can, I physically cannot create a branch. This is the best I can do for now.
Though in all logical seriousness, a branch isn't needed for very minor changes such as this with infrequent changes such as they are now.

superceded


Make sure anonymous users can download published ATBDs

Published ATBDs are public. So anonymous users should be able to download them.

@batpad or @thenav56 – would you have time to review this by the end of the week?

@thenav56 Looks like authorization headers are missing in that requests:  'auth_data': {'id_token': '', 'access_token': None, 'user_email'<EMAIL_ADDRESS>Can you check the headers for the request?
I will add an explicit check for missing headers.

Hi @sunu
Now the error is showing about Missing authorization headers.
Basically, as a<EMAIL_ADDRESS>account I followed this steps

Started from scratch. docker-compose down and docker-compose up db bootstrapper localstack api
Clicked Download for document http://localhost:9000/documents/test-atbd-1/v2.0

v2.0 Journal PDF is failing due to missing text key. Maybe issue with bootstrap data
v2.0 Document PDF is showing Missing authorization headers issue

This is the link it gets forwared to LINK which has the token as GET param.

Also, typo in app/api/v2/pdf.py
https://github.com/NASA-IMPACT/nasa-apt/blob/29d185d98dc3ef69648a1fc543b5c710a67ccdea/app/api/v2/pdf.py#L174
Logs
For text key
backend-api-1           | During handling of the above exception, another exception occurred:
backend-api-1           |
backend-api-1           | Traceback (most recent call last):
backend-api-1           |   File "/app/./app/api/v2/pdf.py", line 155, in get_pdf
backend-api-1           |     local_pdf_filepath = generate_pdf(
backend-api-1           |   File "/app/./app/pdf/generator.py", line 982, in generate_pdf
backend-api-1           |     raise e
backend-api-1           |   File "/app/./app/pdf/generator.py", line 979, in generate_pdf
backend-api-1           |     latex_document = generate_latex(atbd, filepath, journal=journal)
backend-api-1           |   File "/app/./app/pdf/generator.py", line 713, in generate_latex
backend-api-1           |     output = prepare_sections.prepare_sections(
backend-api-1           |   File "/app/./app/pdf/prepare_sections.py", line 29, in prepare_sections
backend-api-1           |     "contents": fill_contents.fill_contents(
backend-api-1           |   File "/app/./app/pdf_utils/fill_contents.py", line 67, in fill_contents
backend-api-1           |     contents.append(process_lists.ul_ol_lists(element))
backend-api-1           |   File "/app/./app/pdf_utils/process_lists.py", line 29, in ul_ol_lists
backend-api-1           |     for item in list_items(child):
backend-api-1           |   File "/app/./app/pdf_utils/process_lists.py", line 18, in list_items
backend-api-1           |     return [d["text"] for _indx, d in enumerate(items)]
backend-api-1           |   File "/app/./app/pdf_utils/process_lists.py", line 18, in <listcomp>
backend-api-1           |     return [d["text"] for _indx, d in enumerate(items)]
backend-api-1           | KeyError: 'text'

@thenav56 thanks for spotting the typo. Can you check which commit are you on for the frontend? The latest one should use auth headers instead of a token as query param.

Thanks, @sunu. The token issue is solved by using the latest client. Sorry about that.

@thenav56 @sunu once you guys think this is ready, one of you can merge it 😄


Add configuration to NerdDice

Allow users to configure NerdDice with properties such as the randomization methods to use, defaults used by the gem, etc.
NerdDice.configure do |config|
  # default to SecureRandom which has a decent trade-off between entropy and speed
  config.randomization_technique = :secure_random # [:rand, :secure_random, :random_new, :randomized]
  # only needed if :randomized is chosen from randomization_technique
  config.randomization_technique_randomizer = :secure_random # [:rand, :secure_random, :random_new, nil]
  config.ability_score_array_size = 7 # default 6
  # other future config, for properties of dice or customization of gem
end

Blocks #1


Suspicious local dependency

In relay-mobile-examples/package.json I see:
/Users/chandrasekharkode/Desktop/Kode/Programming/relay/react-native

yeah relay doesn't work out of the box in react-native https://github.com/facebook/relay/issues/26 :(

now react-native and relay work out of the box :)


[Improvement] RuleApplyRowFilterAndDataMasking supports column pruning

Code of Conduct

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

Search before asking

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

What would you like to be improved?
If table t has 100 columns and the query only fetch 2 columns, e.g.
SELECT c1, c2 FROM t

We can get column AccessRequest for c1 and c2 instead of all columns.
It can improve performance with wide table.
How should we improve?
No response
Are you willing to submit PR?

[ ] Yes. I can submit a PR independently to improve.
[ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

@yaooqinn is it safe for authorization ? cc @pan3793 @bowenliang123

how much perf can we gain?


uE Instance ID of UUri when set to 0 is ambiguous

Some languages like up-cpp has interpreted the spec that it must always set the instance id to be 1 however the intention was that a value of 0 (don't care) is also used to indicate when there is only a single instance. the purpose of not forcing the "1" for a single instance was to avoid sending additional bytes for the URI.
The specifications need to be clarified to indicate that setting instance_id (upper 16 bits of ue_id) to 0 (don't care) is used to also indicate a single instance. It is covered slightly in the someip specs but needs some more TLC.

@stevenhartley - I think this is a spec bug that needs to be fixed before we make code changes. We discussed elsewhere, but I've copied my recommendation into the bug filed against up-cpp: https://github.com/eclipse-uprotocol/up-cpp/issues/259#issuecomment-2276430356
In short, I recommend that we update the spec to define 0xFFFF as the wildcard filter value for instance ID. It solves several problems, allows for the wildcard value to be reserved, improves the SOME/IP instance ID mapping, and removes ambiguity around the usage of instance ID 0 in several situations.

FWIW, this would very seamlessly slot into how vsomeip defines ANY_INSTANCE and ANY_SERVICE. :+1:


Fix/docker compose

Add ws_server to docker-compose
Change entrypoint to CMD on Dockerfile to enable debug
Change localhost to <IP_ADDRESS> on ws_server to run server correctly

Is CI back?

CI/Pullapproval back

👍


Lootr 1.16.4-<IP_ADDRESS>, custom chests not working properly.

When making a custom lootr chest ("/lootr custom" while standing on a chest), whenever a player takes an item out of the chest, the item disappears for all players. If they put an item in the chest, it doesn't appear for any players.

Bugger, I swear I fixed this, let me look into it.

Okay, it took me a while, but I finally tracked down the issue. This should be fixed in the latest release on CurseForge (0.0.6+).


No Sound in silent mode

When the phone is in silent mode the video doesn't play the sound, how can I avoid that?

did you get any way to fix it?


[boinc] Add custom patch (copied from mainstream unreleased code) to support OpenSSL3

Signed-off-by: Vitalii Koshura<EMAIL_ADDRESS>

Any chance to get it reviewed and maybe even merged? ^^

I confirmed that this was merged upstream as https://github.com/BOINC/boinc/commit/689dc20ede9768377d4032ff8c70b58269c8dc9c
Thanks for the patch!

(In the future if you include a link to upstream where it is landed to make it easy to check it will make review easier and as a result probably faster, thanks!)


feat(server): add OpenTelemetry middleware and metrics

Add OpenTelemetry instrumentation to chi router
Adds OpenTelemetry middleware to the chi router to collect:

Request duration metrics
In-flight request counts
Response size metrics
Distributed tracing

The instrumentation uses the otelchi package to automatically capture routes and metrics using the configured OpenTelemetry meter provider.

[!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

#147  👈 (View in Graphite)
#146
main

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

Merge activity

Dec 24, 5:35 PM EST: A user started a stack merge that includes this pull request via Graphite.


Soft alignment visualisation

The goal is to be able to get images of alignment, which are seen everywhere in the NMT papers.

It should be possible (and quite cool) to add these alignments to tensorboard via tf.image_summary...

@jindrahelcl I tried doing that here. But I don't know what attentions_in_time are and why there are (in the case of tests/small.ini) 11 of them.
Also, am I correct in assuming that the image always corresponds to the last sentence in the batch? I'm not sure how to get more than one image per batch or how to prevent it from being overwritten by the next batch…

Hi, as for now, (almost) all of the sequences are represented as a Python list of length max_output_len (max_input_len for encoders). This dimension is in the code often called time. The contents of these lists are Tensorflow tensors, whose first dimension is the batch size. Note that this will change with  #116. Then, all of the sequences will be represented as single Tensors of shape [batch_size, time, (whatever_shape_of_the_tensor_of_one_token)]
It is not clear what images are you talking about. It should always be as many images as there are sentences in the batch, though.
As for the images that should be generated from the alignment, I would do it the same way sample sentences are outputted during the validation, i.e. for starters, first 15 sentences from validation. Then we can add an option to log the validation output on a random or some selected subset of the data.
And the final answer:
attentions_in_time is an array of the attention weights. These are the vectors that we want to visualize (I think). The array is in time which means it has length of whatever the maximum length of the decoder is. Note that this can be longer than the output sequence and something must be done about that.
The Tensors in attentions_in_time have shape [batch_size, max_input_length] and should contain numbers from zero to one and should sum to one over the last dimension.
For example, the value on the index [24,6] in the 3rd tensor in this array is a probability with which the third word on the output is aligned to the seventh word on the input during decoding the 25th sentence in the batch

@jindrahelcl @obo
I think I managed to visualize the alignments for the first batch of validation data every validation_period; see #121. It's probably not the neatest possible solution, though, and I cannot guarantee I didn't break something.
I'm not sure what to do about the fact that the matrices are of fixed dimensions, as @jindrahelcl wrote.
I tried testing it only on tests/small.ini and the output didn't make a lot of sense (but neither did the translations).

I can see that in master, the corresponding image summary is still in the graph, but it is no longer fetched during validation. Can you think of a clean way to do that in the new code?

Sure, it's simple, I just forgot about it. You just add the fetches in the next_to_execute method and then you assign the results to the image_summaries field of the ExecutionResults. If you want to get familiar with the new runners, try it yourself, otherwise I can do it.

Thank you, I will try to do it.
On Mon, 28 Nov 2016 10:34 Jindřich Libovický<EMAIL_ADDRESS>wrote:

Sure, it's simple, I just forgot about it. You just add the fetches in the
next_to_execute method and then you assign the results to the
image_summaries field of the ExecutionResults. If you want to get
familiar with the new runners, try it yourself, otherwise I can do it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ufal/neuralmonkey/issues/108#issuecomment-263224098,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHrH9BuE4BLrMt-nsHDpkgal__E6LRJNks5rCqApgaJpZM4KUg2I
.


Programatically disable swipe behavior?

Is there any way to disable the swipe behavior? I know that sounds like a ridiculous request, but I'd like to use this library, but not allow users access to the swipe functionality until I've had some more time to build it out.

@Slapbox I haven't tried it but would disableLeftSwipe={true} and disableRightSwipe={true} do the trick?
Might not be the most efficient way but they do already exist

@jemise111 that sounds like exactly what I'd need! Thanks for your quick response!
Oddly, swiping right is still something I can do after adding those to the <SwipeListView /> component. It seems to prevent it about 90% of the time, but sometimes I can still swipe it. Swiping left seems to be 100% disabled, but swiping right is not 100% disabled.

@Slapbox Hm, can you post your code? Will try to take a look when I can
Additionally the real "right" way to do this is to prevent the gesture handler from accepting gestures in the first place if a certain prop is passed. Will also try to do then when I can but if you want to give it a shot and submit a PR, it's always welcome :)

Closing, please reopen if this is still an issue, thanks!

@jemise111 - this is still not working for me.
I have 2 issues now:
this is my code:
<SwipeListView
            data={groupUsers}
            renderItem={(user, rowMap) => (
              <SwipeRow
                disableRightSwipe={true}
                disableLeftSwipe={true}
                // leftOpenValue={20 + parseInt(user.item.key) * 5}
                // rightOpenValue={-150}
              >
                {/* {console.log('user', user)} */}
                <View style={styles.rowFront}>
                  <View
                    style={[
                      styles.groupItem,
                      !isLastElement(groupUsers, user.index)
                        ? styles.borders
                        : null,
                    ]}>
                    <View style={styles.groupData}>
                      <View style={{width: 60}}>
                        <Avatar.Image
                          style={styles.groupActionIcon}
                          size={50}
                          source={
                            isSet(user.item) && user.item.profileImage
                              ? {
                                  uri: user.item.profileImage,
                                }
                              : require('./../../public/images/default-group-sm.png')
                          }
                        />
                      </View>
                      <View style={{justifyContent: 'center'}}>
                        <Text style={styles.groupTitle}>
                          {user.item.displayName}
                        </Text>
                      </View>
                    </View>
                  </View>
                </View>
              </SwipeRow>
            )}
            renderHiddenItem={(user, rowMap) => (
              <View
                style={[
                  styles.rowBack,
                  {
                    backgroundColor: theme.colors.primary,
                    flexDirection: 'row',
                    justifyContent: 'flex-end',
                    alignItems: 'center',
                  },
                ]}>
                <IconButton
                  size={30}
                  color="#fff"
                  icon="close"
                  style={{paddingTop: 10}}
                  onPress={() =>
                    dispatch(removeUserFromGroup(groupId, user.item))
                  }
                />
              </View>
            )}
            rightOpenValue={-60}
            keyExtractor={(item, index) => index.toString()}
          />

I'm getting this error:

oddly enough, when I uncomment the console.log('user'), this error goes away ...

When this does render (byI add the console.log), no effect is taking place, and the swipe is is not disabled.

Is here any way to do it only for some items? I want to make it disabled conditionally - depended on item but I can't pass there callback - only boolean value.

Hi @kpietrzak-web please see this doc https://github.com/jemise111/react-native-swipe-list-view/blob/master/docs/per-row-behavior.md


Colossal Blow in EB is not avoidable

Hey there, wanted to let you know you have this spell loaded in incorrectly for the last boss. Logs as avoidable for party, it isn't.

Unfortunately, the two parts of Colossal Blow (frontal with stun / party dmg) share the same spellID and cannot be separated. I opted initially to include it as avoidable, but as classes can mitigate the AoE more or less effective, this skews the overall results of the dungeon heavily.
I have moved Colossal Blow from Avoidable Damage to Avoidable Auras for #53 => This should hopefully only track the stun portion (and thus the avoidable frontal).


Ctrl+x not working properly

code-server version: 1.868-vsc1.33.1
OS Version: Ubuntu 16.04.4 LTS

Description
Ctrl+x seems not to work like in vs code. When nothing is selected the whole line gets cut in vs code. In code server, it seems like nothing happens unless some code is marked.
Steps to Reproduce

Set the cursor somewhere in the editor
Press Ctrl+x

Let's pick up the conversion in https://github.com/codercom/code-server/issues/487


D18, Additional Mag and Disabled Auto-Eject

About the PR

Gave D18 an Additional Mag and Disabled Auto-Eject
Why / Balance

Parity
Technical details

Media

Requirements

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

Breaking changes

Changelog

:cl:

tweak: Gave D18 an Additional Mag and Disabled Auto-Eject

Test Fails Unrelated to PR.


Getting started with C++ function pointers

We ask that you please be patient as our team works through approving and publishing all articles/tutorials in a timely manner. Allow 1-3 days for a topic to be reviewed and/or approved - allow 3-7 days for an articles to be reviewed and/or published.
Be sure to visit our Resources Page for tools, resources, and example articles to go over.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
NOTE: We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
We're looking for the first 2-3 paragraphs of the article that appropriately summarize what your article will be about.
Proposed title of article
Getting started with C++ function pointers
Introduction paragraph (2-3 paragraphs):
Pointers are used to point to data. Like normal data pointers, we have function pointers which point to functions. Function pointers store the address of a function. In greater detail, they store the starting address or entry point of the block of memory containing all the instructions in a function. We use function pointers for several tasks. One example is to prevent code redundancy, which is what most programmers seek to achieve. For example, if you're writing a sort() function, you may want to give the function's caller the option of sorting data in ascending or descending order. Some programmers may need to sort in ascending or descending order, while others may prefer something in between. Function pointers allow the programmer to choose how to sort the data. Callbacks, event-driven programs, and so on are all applications of function pointers. This article will introduce the reader to the working and examples of the function pointer along with code examples.
Key takeaways:

Function pointers and callbacks
How to create function pointers
Interesting facts about function pointers
Passing function pointers as arguments
Code examples to demonstrate the use of function pointers.

References:
N/A
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

@Dawe-7
to help avoid a backlog queue we are only accepting one article topic/pr approved at a time 👍
I just noticed you submitted like 3-4 topics - please only one at a time.


Pablo

Renesas Rx65N porting for MQTT finished,request to merge.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: PabloShi:x: Pablo ShiPablo Shi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: PabloShi:x: Pablo ShiPablo Shi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Bridge request for Picarto.tv

Bridge request

General information

Host URI for the bridge (i.e. https://github.com):
Main site here: https://www.picarto.tv
Relevant API here: https://api.picarto.tv/

Which information would you like to see?
A Picarto channel going live.

How should the information be displayed/formatted?
What I had in mind was just an entry coming up when the channel the feed is for goes live. The channel name should probably be stated somewhere, and the date should probably match the date the channel went live. For a (more or less) working example, see:
http://picartotorss.rf.gd/rss.php?channel=playloudlive (source code)
I must clarify, that example was a pet project of mine meant for personal use, as it is limited to 50k daily requests by the free host I'm using - good enough for myself and a couple friends, not so much for actual public use.
Adding a stream thumbnail is very much optional.

Which of the following parameters do you expect?

[X] Title
[X] URI (link to the channel)
[ ] Author
[X] Timestamp
[ ] Content (the content of the article)
[ ] Enclosures (pictures, videos, etc...)
[ ] Categories (categories, tags, etc...)

Options

[ ] Limit number of returned items

Default limit: 5

[ ] Load full articles

Cache articles (articles are stored in a local cache on first request): yes
Cache timeout (max = 24 hours): 24 hours

[X] Balance requests (RSS-Bridge uses cached versions to reduce bandwith usage)

Timeout (default = 5 minutes, max = 24 hours): 5 minutes

https://rss-bridge.org/bridge01/#bridge-PicartoBridge


BLE ANCS Pairing Issue with ESP32 (Error Code: 0x66/102) (IDFGH-14177)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
Issue Description:
The ESP32 running the ESP-IDF BLE ANCS example frequently fails to pair with an iOS device after repeated connect/disconnect cycles. The pairing fails with the error code 0x66 (102).

Steps to Reproduce:

Run the built-in ESP-IDF BLE ANCS example on the ESP32.
Connect the ESP32 to an iOS device.
Disconnect and reconnect multiple times or move the iOS device in and out of range.
Observe pairing failure with error 0x66.

Observation:

The issue occurs more frequently when the connection/disconnection cycle is fast.
It appears the device cannot proceed with pairing or retrieve ANCS services/characteristics due to timing issues.
Even if disconnections are delayed, the problem reoccurs after multiple cycles.

Logs:
I (31) boot: ESP-IDF v5.3.1 2nd stage bootloader
I (31) boot: compile time Dec  4 2024 12:49:33
I (31) boot: Multicore bootloader
I (35) boot: chip revision: v3.1
I (39) boot.esp32: SPI Speed      : 40MHz
I (44) boot.esp32: SPI Mode       : DIO
I (48) boot.esp32: SPI Flash Size : 2MB
I (53) boot: Enabling RNG early entropy source...
I (58) boot: Partition Table:
I (62) boot: ## Label            Usage          Type ST Offset   Length
I (69) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (77) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (84) boot:  2 factory          factory app      00 00 00010000 00100000
I (92) boot: End of partition table
I (96) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=20a7ch (133756) map
I (150) esp_image: segment 1: paddr=00030aa4 vaddr=3ffbdb60 size=04bech ( 19436) load
I (158) esp_image: segment 2: paddr=00035698 vaddr=40080000 size=0a980h ( 43392) load
I (175) esp_image: segment 3: paddr=00040020 vaddr=400d0020 size=7bb34h (506676) map
I (349) esp_image: segment 4: paddr=000bbb5c vaddr=4008a980 size=0caf0h ( 51952) load
I (381) boot: Loaded app from partition at offset 0x10000
I (381) boot: Disabling RNG early entropy source...
I (393) cpu_start: Multicore app
I (402) cpu_start: Pro cpu start user code
I (402) cpu_start: cpu freq: 160000000 Hz
I (402) app_init: Application information:
I (405) app_init: Project name:     ble_ancs
I (410) app_init: App version:      1
I (414) app_init: Compile time:     Dec  4 2024 12:48:21
I (420) app_init: ELF file SHA256:  516f9382e...
I (425) app_init: ESP-IDF:          v5.3.1
I (430) efuse_init: Min chip rev:     v0.0
I (435) efuse_init: Max chip rev:     v3.99
I (440) efuse_init: Chip rev:         v3.1
I (445) heap_init: Initializing. RAM available for dynamic allocation:
I (452) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (458) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (464) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (470) heap_init: At 3FFC75F0 len 00018A10 (98 KiB): DRAM
I (476) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (482) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (489) heap_init: At 40097470 len 00008B90 (34 KiB): IRAM
I (497) spi_flash: detected chip: generic
I (500) spi_flash: flash io: dio
W (504) spi_flash: Detected size(16384k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I (518) coexist: coex firmware version: 4482466
I (523) main_task: Started on CPU0
I (533) main_task: Calling app_main()
I (553) BTDM_INIT: BT controller compile version [b022216]
I (553) BTDM_INIT: Bluetooth MAC: ec:64:c9:09:fa:96
I (553) phy_init: phy_version 4830,54550f7,Jun 20 2024,14:22:08
I (863) BLE_ANCS: app_main init bluetooth
I (973) BLE_ANCS: REG_EVT
I (983) main_task: Returned from app_main()
I (1013) BLE_ANCS: advertising start success
I (20513) BLE_ANCS: ESP_GATTC_OPEN_EVT
W (22963) BT_SMP: FOR LE SC LTK IS USED INSTEAD OF STK
I (23783) addr: 6f 0d 8b 27 11 26
I (23783) BLE_ANCS: pair status = success
I (26873) BLE_ANCS: ESP_GATTC_DIS_SRVC_CMPL_EVT
I (26933) BLE_ANCS: ESP_GATTC_CFG_MTU_EVT, Status 0, MTU 500, conn_id 0
I (26933) BLE_ANCS: ESP_GATTC_SEARCH_CMPL_EVT
I (26933) BLE_ANCS: Find Apple control point char
I (26943) BLE_ANCS: Find Apple noticification source char
I (26943) BLE_ANCS: Find Apple data source char
I (50123) BLE_ANCS: EventID:New message EventFlags:0x10 CategoryID:Social CategoryCount:1 NotificationUID:8
I (50123) BLE_ANCS: Get detailed information
I (50183) BLE_ANCS: recevice Notification Attributes response Command_id 0 NotificationUID 8
I (50183) Identifier: net.whatsapp.Wha
I (50183) Identifier: tsApp
I (50193) Title: Nitin
I (50193) Message: Hello
I (50193) MessageSize: 5
I (50203) Date: 20241204T131537
I (50203) NActionLabel: 43 6c 65 61 72
I (61553) BLE_ANCS: EventID:New message EventFlags:0x10 CategoryID:Social CategoryCount:2 NotificationUID:9
I (61553) BLE_ANCS: Get detailed information
I (61673) BLE_ANCS: recevice Notification Attributes response Command_id 0 NotificationUID 9
I (61673) Identifier: net.whatsapp.Wha
I (61673) Identifier: tsApp
I (61673) Title: Nitin
I (61683) Message: Hmm
I (61683) MessageSize: 3
I (61683) Date: 20241204T131549
I (61693) NActionLabel: 43 6c 65 61 72
I (76373) BLE_ANCS: EventID:New message EventFlags:0x10 CategoryID:Social CategoryCount:3 NotificationUID:10
I (76373) BLE_ANCS: Get detailed information
I (76433) BLE_ANCS: recevice Notification Attributes response Command_id 0 NotificationUID 10
I (76433) Identifier: net.whatsapp.Wha
I (76433) Identifier: tsApp
I (76443) Title: Nitin
I (76443) Message: 123456
I (76443) MessageSize: 6
I (76453) Date: 20241204T131604
I (76453) NActionLabel: 43 6c 65 61 72
I (84593) BLE_ANCS: EventID:New message EventFlags:0x10 CategoryID:Social CategoryCount:4 NotificationUID:11
I (84593) BLE_ANCS: Get detailed information
I (84713) BLE_ANCS: recevice Notification Attributes response Command_id 0 NotificationUID 11
I (84713) Identifier: net.whatsapp.Wha
I (84713) Identifier: tsApp
I (84723) Title: Nitin
I (84723) Message: Nitin
I (84723) MessageSize: 5
I (84733) Date: 20241204T131612
I (84733) NActionLabel: 43 6c 65 61 72
W (95743) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x13
W (95743) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x13
I (95753) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x13
I (95773) BLE_ANCS: advertising start success
I (98463) BLE_ANCS: ESP_GATTC_OPEN_EVT
I (98903) addr: 6f 0d 8b 27 11 26
I (98903) BLE_ANCS: pair status = success
W (102493) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x13
W (102493) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x13
I (102503) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x13
I (102523) BLE_ANCS: advertising start success
I (113693) BLE_ANCS: ESP_GATTC_OPEN_EVT
W (114573) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x8
E (114583) BT_BTM: Device not found

W (114583) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x8
W (114583) BT_APPL: bta_gattc_mark_bg_conn unable to find the bg connection mask for: 6f:0d:8b:27:11:26
I (114613) addr: 6f 0d 8b 27 11 26
I (114613) BLE_ANCS: pair status = fail
I (114613) BLE_ANCS: fail reason = 0x66
I (114613) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x8
I (114633) BLE_ANCS: advertising start success
I (125223) BLE_ANCS: ESP_GATTC_OPEN_EVT
W (125593) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x13
E (125603) BT_BTM: Device not found

W (125603) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x13
W (125603) BT_APPL: bta_gattc_mark_bg_conn unable to find the bg connection mask for: 6f:0d:8b:27:11:26
I (125613) addr: 6f 0d 8b 27 11 26
I (125623) BLE_ANCS: pair status = fail
I (125623) BLE_ANCS: fail reason = 0x66
I (125623) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x13
I (125653) BLE_ANCS: advertising start success
E (133283) BT_APPL: bta_gattc_process_indicate indication/notif for unknown device, ignore
I (133283) BLE_ANCS: ESP_GATTC_OPEN_EVT
W (133633) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x13
E (133643) BT_BTM: Device not found

W (133643) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x13
W (133643) BT_APPL: bta_gattc_mark_bg_conn unable to find the bg connection mask for: 73:6e:05:0f:9e:24
I (133653) addr: 73 6e 05 0f 9e 24
I (133663) BLE_ANCS: pair status = fail
I (133663) BLE_ANCS: fail reason = 0x66
I (133663) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x13
I (133693) BLE_ANCS: advertising start success
I (139713) BLE_ANCS: ESP_GATTC_OPEN_EVT
W (140023) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x13
E (140033) BT_BTM: Device not found

W (140033) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x13
W (140033) BT_APPL: bta_gattc_mark_bg_conn unable to find the bg connection mask for: 73:6e:05:0f:9e:24
I (140043) addr: 73 6e 05 0f 9e 24
I (140053) BLE_ANCS: pair status = fail
I (140053) BLE_ANCS: fail reason = 0x66
I (140053) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x13
I (140083) BLE_ANCS: advertising start success
I (144123) BLE_ANCS: ESP_GATTC_OPEN_EVT
W (144403) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x13
E (144413) BT_BTM: Device not found

W (144413) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x13
W (144413) BT_APPL: bta_gattc_mark_bg_conn unable to find the bg connection mask for: 73:6e:05:0f:9e:24
I (144423) addr: 73 6e 05 0f 9e 24
I (144433) BLE_ANCS: pair status = fail
I (144433) BLE_ANCS: fail reason = 0x66
I (144433) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x13
I (144463) BLE_ANCS: advertising start success

Key observations from logs:

Initial pairing succeeds (pair status = success).
On reconnection attempts, pairing fails (pair status = fail, fail reason = 0x66).

Potential Cause:
The BLE stack might not handle rapid reconnections or repeated disconnection scenarios effectively, leading to pairing and service discovery failure.

Based on your log, the reason for the SMP failure is 0x66, which indicates an SMP timeout. This means that during the SMP process, no packets were received from the peer device.
ESP_AUTH_SMP_CONN_TOUT, /*!< Pairing process failed due to connection timeout */

Additionally, I noticed the following in your log:
I (144433) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x13.
The peer device appears to be repeatedly disconnecting.
I suspect that during the peer device’s disconnection process, the SMP procedure has not been completed, which ultimately results in the SMP failure.
I recommend ensuring the connection is maintained until the SMP process is successfully completed before disconnecting. This should help resolve your issue.

Thank you for the insights, @esp-zhp
It seems the issue arises because the user is frequently moving in and out of the device's Bluetooth range. This causes the Bluetooth connection to toggle repeatedly, which may be leading to the SMP timeout and disconnection issues.
Given this behavior, could you suggest steps to prevent or mitigate this problem? Should we consider making adjustments in the firmware to handle frequent reconnections more effectively, or are there other solutions you would recommend?

@nitin-jethava
It doesn’t seem like the disconnection was caused by exceeding the connection range. If it were, an error code of 0x08 would have been reported instead of 0x13. The 0x13 code indicates that the peer device actively terminated the connection, meaning the iPhone device disconnected intentionally.
There are two possibilities: one is that the Apple Bluetooth stack actively disconnected, and the other is that the user disconnected at the application layer.
I suspect the frequent disconnections might be caused by user actions. Do you have any other perspectives? do you know the scenario in which this issue occurred?

Based on your recent description, the issue appears to have changed and seems to be related to SMP (Security Manager Protocol). It looks like the ESP device may have lost the bond information.
To verify this assumption, you can try printing the bond list using the following APIs:

int esp_ble_get_bond_device_num(void)
esp_err_t esp_ble_get_bond_device_list(int *dev_num, esp_ble_bond_dev_t *dev_list)

If it is confirmed to be an SMP-related issue, you can test the behavior without bonding to see if the problem still occurs.
Please let us know if further assistance is needed!

You are correct, @esp-zhp. I had tested this, and the bond information indeed appears to be missing when the issue occurs.
Under normal circumstances, the int esp_ble_get_bond_device_num(void) API returns 1, indicating the presence of bond information. However, when the error (0x66) occurs, the same API returns 0, suggesting that the bond information is lost or in an idle state.
Since bonding is closely tied to the ANCS functionality in our application, this loss of bond information directly impacts the ability to receive notifications seamlessly.
Given this scenario, could you please advise on the best approach to handle such cases? Specifically:

What is the ideal way to manage situations where bond information is lost?
Are there recommended steps or fallback mechanisms we can implement in the firmware to gracefully handle this situation and re-establish the bond without requiring user intervention?

Your guidance on this matter would be greatly appreciated as it will help us optimize our handling of these disconnections.

In fact, we have never encountered a situation where the ESP32 loses bond information.
Could you add more debug logs to trace when exactly the bond information gets lost?

Thank you for your input, @esp-zhp.
After reviewing your suggestions, I’ve added debug logs at key events to monitor the bond list and collected the following observations:

Before Connection:
The bond list size is logged after advertising starts, showing an initial value:
I (48502) BLE_ANCS: advertising start success
I (48502) BONDING_LIST: Bond list size after restart adverties: 3

After Connection (ESP_GATTC_CONNECT_EVT):
The bond list size remains consistent, confirming successful pairing:
I (50842) BLE_ANCS: ESP_GATTC_CONNECT_EVT
I (50842) BONDING_LIST: Bond list size after connection: 3
I (50852) BLE_ANCS: ESP_GATTC_OPEN_EVT
I (47092) BLE_ANCS: pair status = success

After Disconnection (ESP_GATTC_DISCONNECT_EVT):
The bond list size decreases when an error occurs. Specifically, after the 0x66 error:
I (51832) BLE_ANCS: pair status = fail
I (51832) BLE_ANCS: fail reason = 0x66
I (51832) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x8
I (51842) BONDING_LIST: Bond list size after disconnection: 2

Reconnection Attempts:
Subsequent attempts fail with bond list inconsistencies persisting:
I (52902) BLE_ANCS: fail reason = 0x66
I (52902) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x13
I (52912) BONDING_LIST: Bond list size after disconnection: 2

From these logs, it’s clear that bond information is lost after certain disconnection scenarios, particularly when errors 0x66 and 0x13 are encountered. This affects the ANCS functionality, as bonding is critical for receiving notifications seamlessly.
I’ve attached the full log file (ble_ancs_logs_11_dec.txt) for your review.
Could you please advise on the following:

The most effective approach to recover from bond information loss.
Any additional configurations or changes in the pairing process that could help prevent this issue.

If you require additional logs, specific test scenarios, or further debugging, please feel free to let me know. I’ll be glad to provide any necessary details or support to help resolve this issue.
ble_ancs_logs_11_dec.txt

Based on the additional logs you provided, we further confirmed the bond loss scenario. Could you check whether the example actively clears bond information?
If there’s no active clearing, we suspect this might be a bug in the protocol stack. I’ve added some HCI logs for further debugging.
0003-fix-bt-Display-hci-data-including-up-and-down.zip
Please apply the patch and share the complete logs with me.
Additionally, have you tried using the latest branch?

Thank you for the clarification, @esp-zhp.

No Active Clearing of Bond Information:
After reviewing the example code, I can confirm that the bond information is not actively cleared in the example.

Patch Application and Log Analysis:
I applied the provided HCI log patch and rebuilt the project. Below are the observations from the debug logs:

Before Connection:I (322733) BLE_ANCS: advertising start success
I (322733) BONDING_LIST: Bond list size after restart adverties: 3

After Connection:I (324143) BLE_ANCS: ESP_GATTC_CONNECT_EVT
I (324153) BONDING_LIST: Bond list size after connection: 3

After Disconnection (Error 0x66):I (324543) BLE_ANCS: ESP_GATTC_DISCONNECT_EVT, reason = 0x13
I (324543) BONDING_LIST: Bond list size after disconnection: 2

These logs indicate that the bond list size decreases after the disconnection, suggesting a bond loss scenario.

Attached Full Logs:
I have attached the full log file for your reference, which includes the HCI logs and additional debug outputs.

ble_ancs_logs_12_dec.txt

ESP-IDF Version:
I am currently using the stable release v5.3.2.

Could you please advise further based on these findings? Do you suspect this could be a protocol stack issue, and are there additional steps or tests you would recommend?
If you require additional logs, specific test scenarios, or further debugging, please feel free to let me know. I’ll be glad to provide any necessary details or support to help resolve this issue.

Thank you so much for your solution, @esp-zhp!
The issue is now resolved, and everything is working as expected. I appreciate your detailed explanation and the suggested changes regarding bond information retention. The fix has worked for me, and I can confirm the solution is effective.
I'll also be starting a new thread for a similar issue in the Arduino environment, as I was using the BLEDevice library for the development. I'll need to make similar changes in that library to address this issue, and I'll make sure to update the discussion accordingly.
Thanks again for your valuable support and for guiding me through this!

@nitin-jethava
thanks for your updating.
Actually, I don’t know much about Arduino, and this seems to be a new issue. If your BLE problem has already been resolved, you can create a separate issue specifically about Arduino. More knowledgeable experts will be able to help you with that.

Thank you so much for your guidance, @esp-zhp!
I truly appreciate your help in addressing this issue, and for your suggestion regarding the Arduino environment. I’ve created a new issue specifically for the BLEDevice library on the Arduino platform, and you can find it here: [Issue #1201](https://github.com/nkolban/esp32-snippets/issues/1201).
Since I’ve now raised the issue in the appropriate place, please feel free to close this one.
Thanks again for all your support! I’ll keep you updated on any progress and let you know if I need further assistance.
Best regards,
Nitin

@nitin-jethava yeah,please close this issue.


npm link src with angular 5

I have symlinks enabled:
"build": {
      "preserveSymlinks": true
    }

but when I try to run against npm link with src, I get this error:
ERROR in ./node_modules/mylibrary/index.ts
Module build failed: Error: /Users/sgentile/Workspaces/myproject/node_modules/mylibrary/index.ts is not part of the compilation output. Please check theother error messages for details.
Any ideas?

Why are you trying to link the src anyway, you're suppose to link the dist directory. Angular 5 has known issues with compilation so it often doesn't accept raw TS files from third party libraries. I've ran into this problem with my own library which is why I'm checking this one out and it works great, simply run npm run build and then switch to dist directory and run npm link there.

For development so you don't have to recompile after every change.  What
you described is very time consuming and not very productive
Certainly before preparing for release we link to dist.
On Dec 30, 2017 3:41 AM, "Ante Adamovic"<EMAIL_ADDRESS>wrote:
Why are you trying to link the src anyway, you're suppose to link the dist
directory. Angular 5 has known issues with compilation so it often doesn't
accept raw TS files from third party libraries. I've ran into this problem
with my own library which is why I'm checking this one out and it works
great, simply run npm run build and then switch to dist directory and run npm
link there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jvandemo/generator-angular2-library/issues/252#issuecomment-354534636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIFND97U1Aabeep5RpJNmiq20AJLxASks5tFfcugaJpZM4REtK5
.


Fixed view of new results block

Fixed issue #10  add stream-container class to build more complex selector.
As I can see stream-container wraper presents on all pages in twitter

@alxlark Perfect :+1: Works fine. Just a small thing - can you please move the new styles under the comment common styles - across all pages? I'm just keeping all common styles there for easier reference. (this file needs quite a lot of cleanup though :grin: )

@tsriram please review, I put styles in common section

Thank you so much, @alxlark :smile:

Closes #10

You are welcome!)
Do you mean twitter account, then @AlxLark


Add static check

@jcchavezs
Please support php8
https://github.com/hyperf/hyperf/issues/3963

@diankemao last PR https://github.com/jcchavezs/zipkin-php-opentracing/pull/59

Done @diankemao


Firefox extension manual install

Firefox extension/add-on is ready to go but just got this from Mozilla... they won't approve my highlighter extension until Roam is public or Open Beta! Lame!

Since Firefox won't let us upload a public add-on until Roam is open Beta, I created a private add-on you have to download directly. Here is the link.
https://github.com/GitMurf/roam-highlighter/blob/master/Firefox temp Add-on/roam_highlighter-1.8-fx.xpi
Go to that GitHub page, click "Download" and then choose to "Open" and choose "Firefox" as the program to open with (this is at least from a Windows perspective). It should install the Add-on for you. Let me know if you have any issues.

Pardon my ignorance, but isn't Roam in open beta right now?
I can go to the website and click on "sign up". I don't see any mention of the wait list.