Unable to locate libpkgconf

Hello guys,
I am trying to build muon library (https://github.com/annacrombie/muon), but failing with script unable to find libpkgconf. Is it a bug or am I doing something wrong?
recipe.yaml
# yaml-language-server: $schema=https://raw.githubusercontent.com/prefix-dev/recipe-format/main/schema.json
context:
  version: "0.2.0"

package:
  name: muon
  version: ${{ version }}

source:
  git: https://github.com/annacrombie/muon
  rev: ${{ version }}

build:
  number: 0

requirements:
  build:
    - ${{ compiler('c') }}
    - ${{ compiler('cxx') }}
  host:
    - ninja
    - meson
    - cmake
    - libcurl
    - libarchive
    - pkg-config

about:
  homepage: https://github.com/annacrombie/muon
  license: GPL-3.0
  license_file: LICENSE
  summary: muon is an implementation of the meson build system in c99 with minimal dependencies.

build.sh
meson setup build
cd build
ninja build
meson test
meson install

rattler-build build --recipe conda/pkg/muon --package-format conda --output-dir ./build/output
+ meson setup build
The Meson build system
Version: 1.3.1
Source dir: /app/cpp_training_flakes/build/output/bld/rattler-build_muon_1707341827/work
Build dir: /app/cpp_training_flakes/build/output/bld/rattler-build_muon_1707341827/work/build
Build type: native build
Project name: muon
Project version: 0.2.0
C compiler for the host machine: $BUILD_PREFIX/bin/x86_64-conda-linux-gnu-cc (gcc 13.2.0 "x86_64-conda-linux-gnu-cc (conda-forge gcc 13.2.0-5) 13.2.0")
C linker for the host machine: $BUILD_PREFIX/bin/x86_64-conda-linux-gnu-cc ld.bfd 2.40
Host machine cpu family: x86_64
Host machine cpu: x86_64
Program git found: YES (/usr/bin/git)
Compiler for C supports arguments -Wno-missing-braces: YES
Compiler for C supports arguments -Wendif-labels: YES
Compiler for C supports arguments -Wimplicit-fallthrough=2: YES
Compiler for C supports arguments -Winit-self: YES
Compiler for C supports arguments -Wlogical-op: YES
Compiler for C supports arguments -Wmissing-include-dirs: YES
Compiler for C supports arguments -Wno-missing-field-initializers: YES
Compiler for C supports arguments -Wno-unused-parameter: YES
Compiler for C supports arguments -Wold-style-definition: YES
Compiler for C supports arguments -Woverflow: YES
Compiler for C supports arguments -Wstrict-aliasing=2: YES
Compiler for C supports arguments -Wstrict-prototypes: YES
Compiler for C supports arguments -Wundef: YES
Compiler for C supports arguments -fstrict-aliasing: YES
Configuring version.c using configuration
Found pkg-config: YES ($PREFIX/bin/pkg-config) 0.29.2
Run-time dependency libcurl found: YES 8.5.0
Run-time dependency libarchive found: YES 3.7.2
Found CMake: $PREFIX/bin/cmake (3.28.3)
Run-time dependency libpkgconf found: NO (tried pkgconfig and cmake)
Looking for a fallback subproject for the dependency libpkgconf
Neither a subproject directory nor a pkgconf.wrap file was found.
Subproject  pkgconf is buildable: NO (disabling)
Dependency libpkgconf from subproject pkgconf found: NO (subproject failed to configure)
Dependency samurai skipped: feature samurai disabled
Run-time dependency bestline found: NO (tried pkgconfig and cmake)
Looking for a fallback subproject for the dependency bestline

Executing subproject bestline

bestline| Project name: bestline
bestline| Project version: undefined
bestline| C compiler for the host machine: $BUILD_PREFIX/bin/x86_64-conda-linux-gnu-cc (gcc 13.2.0 "x86_64-conda-linux-gnu-cc (conda-forge gcc 13.2.0-5) 13.2.0")
bestline| C linker for the host machine: $BUILD_PREFIX/bin/x86_64-conda-linux-gnu-cc ld.bfd 2.40
bestline| Build targets in project: 3
bestline| Subproject bestline finished.

Dependency bestline found: YES undefined (overridden)
Run-time dependency tracy found: NO (tried pkgconfig and cmake)
Program python3 found: YES ($PREFIX/bin/python3)
Program test.sh found: YES (/app/cpp_training_flakes/build/output/bld/rattler-build_muon_1707341827/work/tests/fmt/test.sh)
Program afl-fuzz found: NO
Program ninja found: YES ($PREFIX/bin/ninja)
Program runner.sh found: YES (/app/cpp_training_flakes/build/output/bld/rattler-build_muon_1707341827/work/tests/project/runner.sh)
Program scdoc found: NO
Build targets in project: 4

muon 0.2.0

    libcurl   : true
    libarchive: true
    libpkgconf: false
    samurai   : false
    bestline  : true

  Subprojects
    bestline  : YES
    pkgconf   : NO
                Neither a subproject directory nor a pkgconf.wrap file was found.

Found ninja-1.11.1 at $PREFIX/bin/ninja
+ cd build
+ ninja build
ninja: error: unknown target 'build'
Error:   × Build failed

build.sh
meson setup build
cd build
ninja build
meson test
meson install

The ninja program doesn't take a "build" argument.
It is just ninja.
It's the same as make. If you download a project that uses configure scripts, you just run ./configure && make, you don't run make build.

Hi @brano543 – exciting that you are trying out rattler-build!
Here is a working version of your recipe.yaml (tested on osx-arm64):
# yaml-language-server: $schema=https://raw.githubusercontent.com/prefix-dev/recipe-format/main/schema.json
context:
  version: "0.2.0"

package:
  name: muon
  version: ${{ version }}

source:
  git: https://github.com/annacrombie/muon
  rev: ${{ version }}

build:
  number: 0
  script:
    # ${MESON_ARGS} expands to `--buildtype release --prefix=$PREFIX -Dlibdir=lib`
    # We need to install the files into the `prefix` directory
    - meson ${MESON_ARGS} builddir
    - meson install -C builddir

requirements:
  build:
    - ${{ compiler('c') }}
    - ninja
    - meson
    - pkg-config
  host:
    - libcurl
    - libarchive

tests:
  - script:
      - muon -h

about:
  homepage: https://github.com/annacrombie/muon
  license: GPL-3.0
  license_file: LICENSE
  summary: muon is an implementation of the meson build system in c99 with minimal dependencies.

During the build process it doesn't find all the (optional) dependencies. E.g.:
Configuring version.c using configuration
Found pkg-config: YES ($BUILD_PREFIX/bin/pkg-config) 0.29.2
Run-time dependency libcurl found: YES 8.5.0
Found CMake: /opt/homebrew/bin/cmake (3.28.1)
Run-time dependency libarchive found: NO (tried pkgconfig, framework and cmake)
Run-time dependency libpkgconf found: NO (tried pkgconfig, framework and cmake)
Looking for a fallback subproject for the dependency libpkgconf
Neither a subproject directory nor a pkgconf.wrap file was found.
Subproject  pkgconf is buildable: NO (disabling)
Dependency libpkgconf from subproject pkgconf found: NO (subproject failed to configure)
Dependency samurai skipped: feature samurai disabled
Run-time dependency bestline found: NO (tried pkgconfig, framework and cmake)
Looking for a fallback subproject for the dependency bestline

Executing subproject bestline

bestline| Project name: bestline
bestline| Project version: undefined
bestline| C compiler for the host machine: arm64-apple-darwin20.0.0-clang (clang 17.0.6 "clang version 17.0.6")
bestline| C linker for the host machine: arm64-apple-darwin20.0.0-clang ld64 609
bestline| Build targets in project: 3
bestline| Subproject bestline finished.

Dependency bestline found: YES undefined (overridden)
Run-time dependency tracy found: NO (tried pkgconfig, framework and cmake)
Program python3 found: YES ($BUILD_PREFIX/bin/python3)
Program test.sh found: YES (/Users/wolfv/Programs/rattler-build/output/bld/rattler-build_muon_1707379919/work/tests/fmt/test.sh)
Program afl-fuzz found: NO
Program ninja found: YES ($BUILD_PREFIX/bin/ninja)
Program runner.sh found: YES (/Users/wolfv/Programs/rattler-build/output/bld/rattler-build_muon_1707379919/work/tests/project/runner.sh)
Program scdoc found: NO
Build targets in project: 4

muon 0.2.0

    libcurl   : true
    libarchive: false
    libpkgconf: false
    samurai   : false
    bestline  : true

  Subprojects
    bestline  : YES
    pkgconf   : NO
                Neither a subproject directory nor a pkgconf.wrap file was found.

  User defined options
    buildtype : release
    libdir    : lib
    prefix    : $PREFIX

Found ninja-1.11.1 at $BUILD_PREFIX/bin/ninja
WARNING: Running the setup command as `meson [options]` instead of `meson setup [options]` is ambiguous and deprecated.
+ meson install -C builddir

Hi @brano543 – exciting that you are trying out rattler-build!

Thank you for making this possible. The conda-build command takes forever to build anything. I don't know why does it take so much time to process. I hope we can all standardize the recipes and keep up the ecosystem of both mamba and rattler-build.
The above recipe was failing for me unfortunately, but I was able to figure it out in the end.
# yaml-language-server: $schema=https://raw.githubusercontent.com/prefix-dev/recipe-format/main/schema.json
context:
  version: "0.2.0"

package:
  name: muon
  version: ${{ version }}

source:
  git: https://github.com/annacrombie/muon
  rev: ${{ version }}

build:
  number: 0

requirements:
  build:
    - ${{ compiler('c') }}
    - ${{ compiler('cxx') }}
  host:
    - ninja
    - meson

about:
  homepage: https://github.com/annacrombie/muon
  license: GPL-3.0
  license_file: LICENSE
  summary: muon is an implementation of the meson build system in c99 with minimal dependencies.

build.sh
./bootstrap.sh build
build/muon setup -D prefix=$PREFIX build
build/muon -C build install

Great! Congrats :) Yes, I hope so, too.
Should we close this issue?

Thank you very much for kind support ! Yes, we can close the issue :)


Kubebuilder 2.3.1 installation no longer working

It seems that the files required to install <3.0.0 versions are no longer there, therefore the action fails when trying to install them.

Hi @fspaniol , do you have any logs or example for me?
I want to make sure the patch can be correctly fixed your issue

Caused by https://github.com/kubernetes-sigs/kubebuilder/issues/2311

@zwtop and @fspaniol, thank for reporting and working on this.
I have released v1.2.1 so please use it for your workflow.
Please open up an issue if you see there is an issue again.
Thank you!


ui: skip texture frame copy

There still seems to be an issue were EGL claims some ownership of the passed in fd, closing it on calling eglDestroyImage. Not destroying is also not an option, since there is some limited amount of images that can be created, besides possible memory leaks.
Might need to destroy the images after the fd is closed, or possibly pass in a duplicated fd to eglCreateImageKHR.


Clear selected item after form submission

Hi! How i can clear the selected item after form submission?, te value of the ng-model turn empty but the widget still show the previous selected item.
Sorry for my english
Thanks

+1
The ng-model value can be changed to null, but the dropdown stays the same. We need a way to deselect.

Hi, I have a PR to solve that. I make the component get unselected when the component is undefined.
https://github.com/lordfriend/nya-bootstrap-select/pull/42 you only have to get an option with the value set to "" or not defined to get the unselected status or if you want to get the unselected value from the controller, you can set the model to undefined.
Please make +1 in the PR.


Improve docs for OAuth2 with Autoconfiguration

This is with the latest version (3.0.0)
Request to improve documentation to describe how OAuth2 works in the new version and how to hook it into the new autoconfiguration.
There's a great example of how to do OAuth2 with the old API, but the classes are different, so I had to use trial-and-error to figure that out, and there's no information apply the SecurityConfiguration to the autoconfigured Docket.
The only thing I found that worked was to build a SecurityScheme and SecurityContext and pass those a manually configured Docket.
Here's what I ended up with.
  @Bean
  public Docket docs() {
    return new Docket(DocumentationType.OAS_30)
        .select()
        .paths(PathSelectors.ant("/**"))
        .paths(PathSelectors.ant("/actuator/**").negate())
        .paths(PathSelectors.ant("/probe/**").negate())
        .paths(PathSelectors.ant("/error/**").negate())
        .build()
        .securitySchemes(List.of(ccScheme()))
        .securityContexts(List.of(securityContext()))
        ;
  }
  public SecurityScheme ccScheme() {
    return OAuth2Scheme.OAUTH2_CLIENT_CREDENTIALS_FLOW_BUILDER
        .name("my OAuth2")
        .tokenUrl("https://agtauth-dev.usps.gov/agtauth/oauth/token")
        .scopes(List.of(new AuthorizationScope("my_admin", "my Admin")))
        .build();
  }
  public SecurityContext securityContext() {
    return new SecurityContextBuilder()
        .securityReferences(List.of(new SecurityReference("my OAuth2", new AuthorizationScope[] {new AuthorizationScope("my_admin", "my Admin")})))
        .build();
  }

  @Bean
  public SecurityConfiguration swaggerSecurity() {
    return SecurityConfigurationBuilder.builder()
        .clientId("xxx")
        .clientSecret("xxx")
        .realm("xxx")
        .build();
  }

Guys, this took me soooo long to figure out. The new API isn't well documented.


GPT parser for oven

That thing is actually uhh
Present on paper

is it usable for popcorn?

I'm going to isolate the code for libpop as well

ok, don't forget to add/move stuff in the project digarm

I'm tired af
Maybe tomorrow, okay?

100%. when  you are comfortable.

I still haven't imported the sketch, right?


Find a way to accommodate inexact match for attribute definition

http://vocab.nerc.ac.uk/collection/P01/current/INPPIIP4/ is close but not exact match for integrated_npp definition (difference in filter size). Is there a way to accommodate?

still no perfect match in http://vocab.nerc.ac.uk/collection/P01/current/
consider adjusting attribute definition to "Vertically-integrated net primary productivity measured as uptake rate of carbon per unit area of the water body [particulate >0.7um phase]"

This change was not made for knb-lter-nes.16.3. Consider for next version.

added phase designation in knb-lter-nes.16.4


SMNcopynumbercaller tsv sample names

Description of the bug
Sample names in out/justhusky.tsv are currently on the form slowlycivilbuck_sorted_md instead of slowlycivilbuck.
Command used and terminal output
No response
Relevant files
No response
System information
No response

Done in https://github.com/nf-core/raredisease/pull/522


Improve some ingestors

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (0730690) to head (06b6273).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #316   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           49        49
  Lines         1216      1222    +6
  Branches        45        45
=========================================
+ Hits          1216      1222    +6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Extracting 2D keypoint data (x,y) coordinates from MediaPipe Pose Python

I am working to a project to extract and analyze motion data using MediaPipe Pose Python version. Is there a way to extract the x and y coordinates from each keypoint as an output from videos?

Yes, you can do
image_hight, image_width, _ = image.shape
x_coodinate = results.pose_landmarks.landmark[mp_pose.PoseLandmark.NOSE].x * image_width)
y_coodinate = results.pose_landmarks.landmark[mp_pose.PoseLandmark.NOSE].y * image_hight)

Hi adding a follow up question , is there a way to output the keypoints in a json format ?

@timtensor I would also like to have keypoints in json format

Hi @timtensor and @Adeel-Intizar,
Just saw your question. I am not sure if this is what you need
The snippet of the code
import json
import cv2
import mediapipe as mp

mp_drawing = mp.solutions.drawing_utils
mp_drawing_styles = mp.solutions.drawing_styles
mp_pose = mp.solutions.pose

# For static images:
IMAGE_FILES = ["pose.jpg"]
BG_COLOR = (192, 192, 192) # gray
with mp_pose.Pose(
    static_image_mode=True,
    model_complexity=2,
    enable_segmentation=True,
    min_detection_confidence=0.5) as pose:
  for idx, file in enumerate(IMAGE_FILES):
    image = cv2.imread(file)
    image_height, image_width, _ = image.shape
    # Convert the BGR image to RGB before processing.
    results = pose.process(cv2.cvtColor(image, cv2.COLOR_BGR2RGB))

# Get pose landmarks and all detected points
dic = {}
for mark, data_point in zip(mp_pose.PoseLandmark, results.pose_landmarks.landmark):
    dic[mark.value] = dict(landmark = mark.name,
        x = data_point.x,
        y = data_point.y,
        z = data_point.z,
        visibility = data_point.visibility)

# Transform the dictionary into a json object
json_object = json.dumps(dic, indent=2)

And the result would be like the following, just show some of them
{
  "0": {
    "landmark": "NOSE",
    "x": 0.2963533401489258,
    "y": 0.21098068356513977,
    "z": 0.027127068489789963,
    "visibility": 0.9998650550842285
  },
  "1": {
    "landmark": "LEFT_EYE_INNER",
    "x": 0.2739577293395996,
    "y": 0.19375263154506683,
    "z": -0.027974184602499008,
    "visibility": 0.999710738658905
  },
  "2": {
    "landmark": "LEFT_EYE",
    "x": 0.2753041386604309,
    "y": 0.18623779714107513,
    "z": -0.028469190001487732,
    "visibility": 0.999727189540863
  },
  "3": {
    "landmark": "LEFT_EYE_OUTER",
    "x": 0.2763845920562744,
    "y": 0.1787756383419037,
    "z": -0.028236480429768562,
    "visibility": 0.9997602105140686
  },
  "4": {
    "landmark": "RIGHT_EYE_INNER",
    "x": 0.27062976360321045,
    "y": 0.20308701694011688,
    "z": 0.042521875351667404,
    "visibility": 0.9998564720153809

I'm working on pose detection , and I extracted the coordination from the poseLandmarks list attribute fromResult object.
this documentation shows you every index's representation. For example ,  0 refers to nose, 1 refers to left eye , ...

Here is the example of my JS file's code :
const video5 = document.getElementsByClassName("input_video5")[0];  capturing the video from HTML file

function onResultsPose(results) {
  console.log(results.poseLandmarks); this will shows you the list of all landmarks , in my case : from 0 to 32.
}

const pose = new Pose({
  locateFile: (file) => {
    return `https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>  },
});

pose.onResults(onResultsPose);

const camera = new Camera(video5, {
  onFrame: async () => {
    await pose.send({ image: video5 });
  },
  width: 480,
  height: 480,
});
camera.start();

My code is inspired from this repository : https://github.com/LintangWisesa/MediaPipe-in-JavaScript.git ❤
PS : I'm using<EMAIL_ADDRESS>


OpenDSS version

Hi,
not really an issue, more of a documentation question. Where can we find which OpenDSS version is dss_sharp built against?
Regards,
Maciej

The usual version string in DSS.Version contains most of the info:

DSS C-API Library version 0.12.1 revision 7230c9ec1f69ee2f13ac11202ced49ab0b239ebb based on OpenDSS SVN 3460 [FPC 3.2.2] (64-bit build) MVMULT INCREMENTAL_Y CONTEXT_API PM<PHONE_NUMBER>5448; License Status: Open

From the C-API version, you can see more in the changelog at https://github.com/dss-extensions/dss_capi/blob/master/docs/changelog.md#version-0121 and most of the omissions from our fork at listed at https://github.com/dss-extensions/dss_capi/blob/master/docs/known_differences.md
Revision 7230c9ec1f69ee2f13ac11202ced49ab0b239ebb is the Git commit hash from the DSS C-API repo.
SVN 3460 can be seem through the official repo at https://sourceforge.net/p/electricdss/code/HEAD/tree/trunk/
So, a few commits before the latest OpenDSS release.
[FPC 3.2.2] is the compiler, and the following are flags for some of our extensions:

MVMULT: a compile flag to use our matrix multiplication using Eigen in C++ instead of the original Pascal version
INCREMENTAL_Y: the support for incremental Y updates was compiled (still disabled by default)
CONTEXT_API: the support for multiple DSS contexts is enabled
PM: the support for the official parallel-machine mechanism based on actors is built-in.

And<PHONE_NUMBER>5448 is the timestamp when the binary was built.
License Status: Open is kept from the official OpenDSS version string, which is something like:

Version <IP_ADDRESS> (64-bit build); License Status: Open

Thanks. In my case, I wanted to cross-verify my dss_sharp program with an OpenDSS script, so I wanted to install standalone OpenDSS in a version that'd match dss_sharp build. With the above infomation, I could check in the OpenDSS history for the SVN 3460 changeset, and the 0.12.1 version of DSS C-API is somewhere between OpenDSS Version <IP_ADDRESS> and Version <IP_ADDRESS>.
Any thoughts on including the OpenDSS Version somewhere in there more explicitly?

I don't think it's that simple. Listing a version can lead to wrong conclusions since most users don't follow closely the development of either the official version nor DSS C-API.
The codebase is quite different and we port things selectively after testing and cross-validating ourselves. Technically we would tag our latest release to match OpenDSS v<IP_ADDRESS> for example, but the official version had a bug that affected a lot of systems. We noticed something was off and reverted the change for our release. If we mentioned it was based on v<IP_ADDRESS>, the results would be off.
Besides occasional bugs, not every commit there needs to be ported for various reasons, be it code for features not exposed in the official OpenDSS (e.g. a lot of commits go to OpenDSSCmd for FPC, which is not exactly official), GUI, documentation, or just due to the different code architecture of DSS C-API v0.12.x.
Maybe you found this: nowadays there is a .txt in the official repo for the version at https://sourceforge.net/p/electricdss/code/HEAD/tree/trunk/Version8/Source/Current_ver.txt -- replace HEAD with the SVN revision and we usually should be between that and the previous version. I'd recommend keeping a known valid set of results to validate the new OpenDSS versions so you don't assume there are issues here. Most of the OpenDSS components are very stable and should not change from one release to another -- if something does and it's not explained in the changelog, it's usually a bug.

I'll see if I can automate grabbing the version from that txt. If that works fine, as long as part of my previous comments are left in the DSS.Version comments/docstring, that seems good enough for the current situation.

That's definitely not very important, just a cosmetic thing - as you explained, there's ways to get at that version. But thanks!
If I may, however, I think I'd recommend trying to build DSS C-API and DSS Sharp against official versions of OpenDSS (as much as possible with the selective porting of features). If nothing else, that'd just be clearer - this version is built off XXX OpenDSS version. Like you said, the components should be stable at this point, so not taking the absolutely latest OpenDSS changes shouldn't be a big deal. If latest OpenDSS version has a known issue - just take a previous, but official stable version. Again, the components should be stable at this point, so downgrading one minor version shouldn't matter. And in an off chance that there is another bug (not known yet) which found its way into either OpenDSS or DSS Sharp, it's much easier to compare the results (and be confident in them) if you know for sure that they are using the same version of the key solver.

Text wall warning! TLDR: There are a few ways things can progress, only time will tell, but right now DSS C-API cannot use the original/official OpenDSS code anymore.

If I may, however, I think I'd recommend trying to build DSS C-API and DSS Sharp against official versions of OpenDSS (as much as possible with the selective porting of features).

That can't be done anymore. The only feature we could add without much hassle would be mapping OpenDSS errors to exceptions, everything else including the API performance cannot be achieved.
We've gone through a few phases already:

In 2016-2017, we tried to use the official OpenDSSDirect.DLL. Besides the bugs and some limitations, in the end we had the same issues as the official COM OpenDSSengine.DLL. That's when we started developing and testing DSS C-API and DSS Python.

In 2018, we felt it was mature enough. The first public releases of DSS C-API were basically what you proposed -- use the official version with minimal changes. It was maintained as a set of patches in hopes that EPRI would integrate it someday. That's why https://github.com/dss-extensions/electricdss-src existed. You can follow some of the conversations on https://sourceforge.net/p/electricdss/discussion/861976/thread/525c13df/ and https://sourceforge.net/p/electricdss/discussion/861977/thread/89f78cd6/?limit=25#2d06

In 2019, a year or so after the first public release, that become impractical as we added more and more fixes. Since it was clear a direct contribution wouldn't work, we started addressing other issues in the API code and DSS C-API became more of a friendly fork than a set of patches.

By 2020, we already had some internal branches at Unicamp testing some of the bonus features we released in 2022. There are still some extra features we didn't publish.

The DSS C-API library nowadays:

Probably cannot be built with Delphi without some changes, so Free Pascal is a requirement. This is in direct conflict with the official implementation, which only supports Delphi. OpenDSSCmd is built with Free Pascal and, since it lacks the changes from DSS C-API, has a lot of bugs and limitations. I already expressed my concerns in https://sourceforge.net/p/electricdss/discussion/861976/thread/7172875585/
Uses a fork of KLUSolve with extra features that allow better performance and incremental Y updates.
Has a rewritten IO system replacing the limited and deprecated Pascal IO system. This is what enabled using ZIP files as input.
Supports UTF8 and is ready for i18n. Even if ASCII is fine for a lot of users, I'm in Brazil, so this is important in the long term.
Supports multiple DSS engines. This required changing a lot of code to replace global variables, so cannot be done with the current OpenDSS version.
Complex numbers use operator overloads, resulting in cleaner code.
The whole property system was rewritten. This removed a whole class of bugs from the implementation -- some recent OpenDSS bugs fall on this and they don't affect us. This also changed a lot of files in the codebase. This allows exposing every single data class from OpenDSS -- currently we do it in dss.hpp and DSS Python, see for example https://dss-extensions.org/dss_python/obj.html
The library and bindings are built and tested on most the most platforms and processor architectures. The official version is restricted to Windows x86 and x64.

I'm working on finishing https://github.com/dss-extensions/dss_capi/issues/88 next week. After that and reintegrating A-Diakoptics, DSS C-API v1.0 is almost ready. DSS Sharp itself needs some good examples and maybe a COM layer (so it can be used as a COM module) to reach v1.0.
If you look in the DSS C-API repo, you will see that nearly all of the changes in the last couple of years are made by myself, with some ports from the SVN. Even the official repository is very restricted in terms of contributors. This is terrible.  I'm only comfortable with Pascal because I used in the 1998-2003. People are happier to test and contribute documentation, or work on the language bindings -- besides the projects here on DSS Extensions, I know people use it in Swift, Go, and a couple of people looking into Rust.
For example, using other programming languages, a lot of people develop features OpenDSS lacks and sometimes reimplement features they consider limited in the official engine; a lot of that goes to waste or is restricted to a small subset of users. There are other reasons for that, but I firmly believe that OpenDSS being written in Pascal is one of the main issues.
To workaround this Pascal issue, at the same time we've been working on finishing the C++ port to abandon Pascal completely (so, not a chance to even consider using the current official version of OpenDSS).  Some of the changes in the engine incorporated here in DSS C-API will greatly facilitate that, and https://github.com/dss-extensions/dss_capi/issues/88 is one of the final pieces -- like the rest of the big features, it will result in a major rewrite of the related code (and it's quite boring to work on), so I'm taking the opportunity to leave the code in a place that it's easier to port to C++. We already have a plan to address some concerns other people may have regarding this C++ port vs. the official version, so hopefully by next year we may have a more robust development community, and maybe (hopefully) more direct collaboration with EPRI.

Thank you for the extensive explanation!


md_color_button_text not respected in theme

Library Version:
2.2.0
Affected Device(s):
Google Pixel 3, 9.0
Describe the Bug:
'md_color_button_text' is not respected and instead overridden by colorPrimary when set in a theme
To Reproduce:

Download material dialog sample.
Update to md_color_button_text in AppTheme.Custom to some color
Inside the sample app, change to custom theme and open any of the sample dialogs.

Expected Behavior:
The color of the action buttons should be set per the md_color_button_text, but is instead colorPrimary.
Note
Looks like DialogActionButton.update reverts the color?

Cheers!


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.11 to before v5.15.5",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d055126180564a57fe533728a4e93d0cb53d49b3",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=439b99314b635b40f2e0622eabe62d7055bb409b"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d055126180564a57fe533728a4e93d0cb53d49b3",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "439b99314b635b40f2e0622eabe62d7055bb409b",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "bpf: Forbid bpf_ktime_get_coarse_ns and bpf_timer_* in tracing progs\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.5 by commit 439b99314b635b40f2e0622eabe62d7055bb409b, it was introduced in version v5.11 by commit d055126180564a57fe533728a4e93d0cb53d49b3. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1002304


Parse dates in RFC 2822 format as seen in HTTP headers

Hi. Have you ever seen a HTTP response header? The last-modified field looks like this
'last-modified': 'Tue, 27 Dec 2011 02:12:35 GMT',

It's a string representing a date and time according to a format defined in RFC 2822. Alas, JavaScript's date object and methods are too weak to parse it. It would be extremely helpful to offer a capable helper method to parse this string to Javascript Date object.

I was wrong. The javascript Date('Tue, 27 Dec 2011 02:12:35 GMT') works. To get a Unix timestamp, which is what I wanted, do Date.parse('Tue, 27 Dec 2011 02:12:35 GMT')/1000


Align release process with scapegoat

To simplify the release processes across repos, I propose to align sbt-scapegoat with scapegoat. With this change both are published based on tags through CI.
This should also help to get release process clearer and get releases for sbt-scapegoat going again.

Just to give some context - and not to leave your question unanswered:

as mentioned in some other tickets, I don't have permissions/credentials to release the sbt-scapegoat project
if I had, I wouldn't mind that much
but I am not a user of sbt-scapegoat as I hardly use sbt

I think the most promising way would be to encourage people like you or someone else and let them take over the maintenance of the project.

Sure thing.
And to give you some context.
Yes. I think it makes sense to align the release processes.
Or at the very least to have an easy possibility to release a version of sbt-scapegoat based on some new release of scapegoat (i.e. an optional alignment).

Or at the very least to have an easy possibility to release a version of sbt-scapegoat based on some new release of scapegoat (i.e. an optional alignment).

I'm not necessarily thinking to release both in tandem, but mostly aligning both to use sbt-ci-release and tag based releases for simplicity and clarity (so the way to release is the same, but cycles might differ).
I am planning to do some experimentation with the scapegoatVersion variable to default based on the Scala major version, to simplify the out of the box experience. With this, tandem releases might make more sense to keep the default recent.

is this PR enough to release sbt-scapegoat or do we need @sksamuel to put his credentials as secrets in this repo?

Unless you have admin on scapegoat itself as well, I think we need Sam to put the Sonatype credentials and GPG pair as variables in GitHub Actions: https://github.com/scapegoat-scala/scapegoat/blob/master/.github/workflows/master-release.yml#L40
If you do have admin, then you could copy the variables into GitHub actions settings. I would like @sksamuel 's upvote on the MR before doing so though (unless you feel otherwise?).
One thing that I'm not fully certain about in the MR, is the overrides scapegoat ci does regarding the GPG key variables: https://github.com/scapegoat-scala/scapegoat/blob/master/.github/workflows/master-release.yml#L17
The current sbt-ci-release template doesn't include that part. I'm not sure whether this is a newer set up or whether there was a fight with GPG key setup in the past (I always have a few hours of ci variable "fun" when I need to rotate my keys).

I do have admin (which I didn't remember :D), but I don't see the current values of the secrets. It seems like Github makes them write-only for humans.

One thing that I'm not fully certain about in the MR,

About that I have no meaning input. I only faintly recall that the PGP keys have always been a bit of a struggle with various build tools (Maven, etc.) and the behavior varied over time/versions of these.

It seems like Github makes them write-only for humans.

Ha, seems GitHub built the mythical Write Only Memory. I'm mostly using GitLab CI so wasn't aware of this feature in Github Actions. Looks we'll need support from Sam to set up the variables then.

@sksamuel Any chance we could get your help here?

In case you missed/forgot the last pings: @sksamuel Could you help you configure the same credentials in the Action Secrets as scapegoat so we can start publishing the plugin again?

Yep sorry, what are we needing here. Just GPP keys to publish to com.sksamuel.scapegoat ?

Yep sorry, what are we needing here. Just GPP keys to publish to com.sksamuel.scapegoat ?

Thanks! According to sbt-ci-release, it should be the PGP key (PGP_SECRET (base64 of private key) / PGP_PASSPHRASE) and the Sonatype credentials to ship it to Maven central (SONATYPE_USERNAME / SONATYPE_PASSWORD)
https://github.com/sbt/sbt-ci-release#secrets

Ok, added:
PGP_SECRET - base64 armored key for<EMAIL_ADDRESS>PGP_PASSPHRASE
SONATYPE_USERNAME
SONATYPE_PASSWORD

Just did a dry run with a tag based on this MR: https://github.com/scapegoat-scala/sbt-scapegoat/actions/runs/4932935859/jobs/8816423773#step:4:31
Will diagnose a bit later whether the ci template is doing something wrong here or if the encoding is really malformed 🤔

@sksamuel I've added a small snippet to validate the input and I think you may have forgotten to apply the base64 encoding. When looking at the first 4 and last 4 characters they're all ---- which I think suggests that it's "just" the armor format. Could you apply base64 and configure the PGP_SECRET again?
ref: https://github.com/scapegoat-scala/sbt-scapegoat/actions/runs/4976011215/jobs/8903698254#step:4:18

I armored it, but I don't know how to export as base64. Do you know the command @Johnnei

I armored it, but I don't know how to export as base64. Do you know the command @Johnnei

@sksamuel https://github.com/sbt/sbt-ci-release#secrets has a few samples:

macOS
gpg --armor --export-secret-keys $LONG_ID | base64 | pbcopy
Ubuntu (assuming GNU base64)
gpg --armor --export-secret-keys $LONG_ID | base64 -w0 | xclip
Arch
gpg --armor --export-secret-keys $LONG_ID | base64 | sed -z 's;\n;;g' | xclip -selection clipboard -i
FreeBSD (assuming BSD base64)
gpg --armor --export-secret-keys $LONG_ID | base64 | xclip
Windows
gpg --armor --export-secret-keys %LONG_ID% | openssl base64

Usually just piping it through | base 64 works. The final new-line tends mess up automation which is probably why they suggest to use a command to send it to the clipboard.

Ok try now @Johnnei

Ok try now @Johnnei

Thanks! The last attempt looks to have published succesfully https://github.com/scapegoat-scala/sbt-scapegoat/actions/runs/5020848340/jobs/9002684401
I'll check in a few hours on central to confirm it all went fine.

sweet
On Thu, 18 May 2023 at 23:34, Johan @.***> wrote:

Ok try now @Johnnei https://github.com/Johnnei
Thanks! The last attempt looks to have published succesfully
https://github.com/scapegoat-scala/sbt-scapegoat/actions/runs/5020848340/jobs/9002684401
I'll check in a few hours on central to confirm it all went fine.
—
Reply to this email directly, view it on GitHub
https://github.com/scapegoat-scala/sbt-scapegoat/pull/153#issuecomment-1553982938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGWVZ2UYTITRFB2N4OTXG3Z4DANCNFSM6AAAAAAW3DCWCE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Can no longer customise colour of label text

With the update to 4.x I can no longer change the Next / Skip / Back / Done label text to black, as we have white slides in our app intro.
Previously we were able to use the buttonTextStyle prop and now this is gone.
Please provide some kind of upgrade guide and information as to how to restore 3.x functionality.

Hi @cameronmurphy,
Upgrade guide is under releases.
What you can do now is define render functions like so:
_renderDoneButton = () => <Text style={styles.buttonText}>Done</Text>
_renderNextButton = () => <Text style={styles.buttonText}>Next</Text>

return <AppIntroSlider renderDoneButton={this._renderDoneButton} renderNextButton={this._renderNextButton} />

Ah thank you! The upgrade guide should mention that slides prop is now called data :)

Ah thank you! The upgrade guide should mention that slides prop is now called data :)

Yes of course! Fixed

I'm going to close this since it seems resolved. Let me know if other issues arise!


Instructions & Garnish sections not updating

[X] I have read the FAQ.

Describe the bug
Instructions & Garnish sections of cocktail page do not update when navigating from another cocktail.
To Reproduce
Navigate to a cocktail.
Open search (Ctrl-K or clicking the menu both produced same results)
Search for and navigate to another cocktail
Image/Description/Tags/etc all update - Instructions & Garnish sections still display information from prior cocktail.
Versions:

Docker: 20.10.21
Browser: Chrome, Firefox
Salt Rim: v1.10.0
Bar Assistant: v1.10.2
Meilisearch: 1.1.1

Additional context, log outputs...
No errors in logs noticed.

And I just realized this might belong to the salt-rim repo.  Let me know if I should close and reproduce it there.

This is the same as this I believe (Stupifier here)
https://github.com/karlomikus/vue-salt-rim/issues/73

Yeah - I closed this one after finding it.


⚠ ClamAV has degraded performance

In f0b3771, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 101 ms

Resolved: ClamAV performance has improved in 569e7cc.


a good design

hi,
I have added your qc-hash into my benchmark (https://github.com/ktprime/emhash/blob/master/bench/ebench.cpp),
some cases qc-hash is very fast but others quite slow. and it can not run(hanged) and martin bench(martin_bench.cpp).
can you fix the issuse?
I add my owern emhash7/emhash5 into your bench file benchmark.cpp(https://github.com/ktprime/emhash/blob/master/bench/qbench.cpp), it's a very good benchmrak.

Interesting, thanks for taking the time to add this to your benchmark. I have not encountered any hanging in my own tests, but if you can provide the operation and kind of data that makes it hang, I would love to fix any bugs I may have missed.
As a side note, I noticed you're using std::hash with the map in your benchmark. I recommend using qc::hash::IdentityHash (the default) for keys with reasonable low-order entropy (which I think your random gamma distributed keys are) or qc::hash::FastHash otherwise. I would expect either to yield a notable step-up in speed.

qc-hash is slow in insert-erase case. (ex https://martin.ankerl.com/2019/04/01/hashmap-benchmarks-03-03-result-RandomInsertErase/), mybe the main reason is simple linear probing(I use 2-3 complex probling).
you can test and reproduce https://github.com/ktprime/emhash/blob/master/bench/martin_bench.cpp (case 6 bench_insert)
how to build my bench on bench dir
hyb@PC210500096:/mnt/f/emhash/bench$ clang++ -O3 -march=native -mtune=native -I.. -I../thirdparty  -DQC_HASH=2 -std=c++20 martin_bench.cpp -o mbenc
or
clang++ -O3 -march=native  -I.. -I../thirdparty  -DFIB_HASH=2  -DQC_HASH=2 -std=c++20 ebench.cpp -o ebench
my bench can choose 6 hash functions by set FIB_HASH=(1-6)  in build cmd.
template<typename T>
struct Int64Hasher
{
    static constexpr uint64_t KC = UINT64_C(11400714819323198485);
    inline std::size_t operator()(T key) const
    {
#if FIB_HASH == 1
        return key;
#elif FIB_HASH == 2
        return hashfib(key);
#elif FIB_HASH == 3
        return hash_mur3(key);
#elif FIB_HASH == 4
        return hashmix(key);
#elif FIB_HASH == 5
        return rrxmrrxmsx_0(key);
#elif FIB_HASH > 10000
        return key % FIB_HASH; //bad hash
#elif FIB_HASH > 100
        return key / FIB_HASH; //bad hash
#elif FIB_HASH == 6
        return wyhash64(key, KC);
#else
        auto x = key;
        x = (x ^ (x >> 30)) * UINT64_C(0xbf58476d1ce4e5b9);
        x = (x ^ (x >> 27)) * UINT64_C(0x94d049bb133111eb);
        x = x ^ (x >> 31);
        return x;
#endif
    }
};

Thanks for the feedback! That's not a performance case I had considered. When I get some time I'll expand my benchmarking and decide whether that case is worth the increased complexity of a more sophisticated probing strategy, like the one you've come up with

https://www.reddit.com/r/cpp/comments/ve3qbx/updating_map_benchmarks_send_your_hashmaps/


runtime/pprof: graphviz node names are funny with generics

Go 1.18.3.
Not sure what I expect when I use `go tool pprof's web mode to see the graphviz SVG output on a node using generics, but not this:

Either without the newlines, or with the concrete types (if/when available)?
FWIW, that's from:
// Set populates an entry in a map, making the map if necessary.
//
// That is, it assigns (*m)[k] = v, making *m if it was nil.
func Set[K comparable, V any, T ~map[K]V](m *T, k K, v V) {
	if *m == nil {
		*m = make(map[K]V)
	}
	(*m)[k] = v
}

I wonder if https://github.com/google/pprof/pull/689 will address this. I’m skeptical though, as bad escaping should most likely cause parse errors.

There is an even worse case with pkg.(*T[...]).f turning into pkg..f, even in the text view. Both of these are covered by https://github.com/google/pprof/issues/705.

Fix in https://github.com/google/pprof/pull/717

Thank you for filing this bug @bradfitz and for the quick response and fix @prattmic! I think fixing this for Go1.19 is useful as it is just updating the dependency. I have sent a CL vendoring the fix in https://go-review.googlesource.com/c/go/+/420234. @ianlancetaylor @rsc can I kindly implore you to let this fly in the Go1.19 release :-) or perhaps should we wait until the next point release and also backport too?

cc @golang/release
This would be nice to have in 1.19 or 1.19.1 (arguably backported to 1.18 too), but I am not sure we want to pull this in so close to the release. FWIW, this does have a clear workaround: use upstream pprof.

This isn't going to make it into 1.19, but we can consider it for 1.19.1 (I'm personally still a bit unsure since there is a workaround).

I'll move this issue to Go 1.20 milestone since the fix will need to land on master branch first. To address this issue for minor releases, we'd need to use the https://go.dev/wiki/MinorReleases process to create children backport issues.

@gopherbot Please backport to 1.19. This fix just barely missed 1.19. While it does have a workaround (use upstream pprof instead of go tool pprof), that is unlikely to be clear to users, and the fix is simple.

@prattmic The backporting approach described in https://github.com/golang/go/issues/34536#issuecomment-572188389 suggests we'll need to also backport the fix to 1.18, since the problem also exists in that version.

Sure, I can do so. Do we have a standard process for backporting one-off fixes to vendored packages, rather than wholesale updates? I can easily manually apply the appropriate changes to the vendored pprof files, but what should go.mod say? The vendored code will no longer any valid upstream version of github.com/google/pprof.

I don't see any such similar cases on https://go-review.git.corp.google.com/q/project:go+is:merged+file:vendor+-branch:master+-branch:dev.link+-branch:dev.boringcrypto+-branch:dev.typeparams+-branch:dev.fuzz. :(
A full update of pprof on release-branch.go1.18 will pull in 20 commits:
$ git log --oneline f987b9c94b31..154dc81eb7b0
154dc81 all: update dependencies (#702)
59ca7ad Generalize the unit support in pprof a bit further. (#699)
83db2b7 Split monolithic webhtml.go into multiple files. (#695)
fdd30d9 Update minimum Go version to 1.17 in go.mod. (#693)
d8f96c0 Fix doc comments format to become compatible with tip gofmt. (#694)
b5a4dc8 allow rendering big flame graphs by avoiding stack overflow in JS parser (#684)
85950bb Fix tagroot to properly format unitless numeric tags. (#691)
c2158d7 Add Go 1.18 to testing, remove Go 1.16. (#692)
b2ab032 third_party: fix typo (#685)
5bba342 internal/graph: Support comments with double quotes (#688)
0368bd9 Handle either _text or _stext as the kernel relocation symbol. (#674)
43b8053 Parse and propagate the name of the kernel relocation symbol (#675)
513e8ac doc: clarify graph view docs to note negative values appear in profile comparison (#667)
8c355e5 internal/elfexec: Fix typos in elfexec.go (#681)
d25a53d Log build ID in local symbolization error messages. (#679)
6f57359 Update d3-flame-graph from 2.0.0-alpha to 4.1.3 (#677)
2007db6 Add badge link to Go API docs in pkg.go.dev (#676)
1daafda Update instructions to use "git clone" instead of "go get". (#673)
44fc4e8 proto/profile.proto: fix typo (#672)
e9b0287 Update mapassign regex to match both call variants (#668)

Do we have a standard process for backporting one-off fixes to vendored packages, rather than wholesale updates?

We have a standard process that applies to golang.org/x dependencies. It uses "internal-branch.go1.x-vendor" branches and is documented at https://go.dev/wiki/MinorReleases#cherry-pick-cls-for-vendored-golangorgx-packages.
This is the first backport request for a problem in the github.com/google/pprof dependency that I'm seeing, so not sure. Depending on how much the vendored github.com/google/pprof interacts with cmd/pprof and other parts of the standard library, it might be safest to update it to the same v0.0.0-20220729232143-a41b82acbcb1 version. If that isn't safe, we'll need to figure out what to do instead.

I can take a closer look tomorrow, but I don't think there are any technical blockers (or any changes to non-vendored code required) to updating pprof to v0.0.0-20220729232143-a41b82acbcb1 in 1.18, it's just that pulling in a bunch of unrelated commits has higher risk of introducing other issues. Sounds like taking that risk is the best bet right now.

@gopherbot Please backport to 1.18. While it does have a workaround (use upstream pprof instead of go tool pprof), that is unlikely to be clear to users.


Sema: Move SimpleDidSetRequest::evaluate() to TypeCheckStorage.cpp

I think TypeCheckStorage.cpp is a better place for this than
TypeCheckDecl.cpp, since all the other requests for storage
and accessor declarations appear in the former.

@swift-ci Please smoke test


Regarding README point 8

Do not add the tests/modified build.gradle to your artemis git repository (it should already be in your .gitignore)

build.gradle is a tracked file and cannot be ignored from git, I think it's important to state 'when possible' or 'not to push', alternatively, mention 'how to stage commits'
Tracked files can only be removed from git history. Not sure how it would affect the Artemis repository.

It's not even in the .gitignore...
I just copied that point from @MaximilianAnzinger 😅


Add a Time and TimeConverter that can be used to convert nanoTime to Timestamp.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@7c59ee6). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #160   +/-   ##
=========================================
  Coverage          ?   94.32%
  Complexity        ?      366
=========================================
  Files             ?       50
  Lines             ?     1057
  Branches          ?       66
=========================================
  Hits              ?      997
  Misses            ?       42
  Partials          ?       18

Impacted Files
Coverage Δ
Complexity Δ

...oogle/instrumentation/common/TimestampFactory.java
83.33% <ø> (ø)
3 <0> (?)

...om/google/instrumentation/trace/TimeConverter.java
100% <100%> (ø)
4 <4> (?)

...in/java/com/google/instrumentation/trace/Time.java
100% <100%> (ø)
8 <8> (?)

...a/com/google/instrumentation/common/Timestamp.java
100% <100%> (ø)
19 <2> (?)

Continue to review full report at Codecov.

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


feat: Updated adxl345 sensor driver to configuration via devicetree file.

Followup PR of: #66046
Updated/rewritten adxl345 sensor code to support devicetree parameters. I have tested the code with an nrf52840-dk and a adxl345 connected via I2C.

Updated code and normally fixed compliance checks. Please apologize, but I am not sure why the last three checks are not running.

@MaureenHelm please provide an update

@MaureenHelm please apologize to bother you again, but I have now reverted all whitespace issues as good as possible and one change is mandatory to ensure functionality if FIFO is disabled (possible now via DT setup).
Maybe you can catch some time to review one more time :)

Rebased on current main

Hi @MaureenHelm
thank you very much for your feedback and please apologize the circumstances.
As requested, I have squashed all the commits and force pushed to includes everything within a single commit without "reverting" commits.

Fixed compliance issues, please review again @MaureenHelm


Non-ASCII characters like ampersand (&) have their encoding changed, even when they should be considered valid HTML

I noticed this issue while using PreMailer.Net and was able to isolate the cause down to AngleSharp. I describe the issue in some detail in an issue on PreMailer.Net's repository.
When the HTML I parse contains a non-ASCII value, like an ampersand, AngleSharp will encode the character. For example:
static async Task FirstExample()
{
    var config = Configuration.Default;
    var context = BrowsingContext.New(config);
    var document = await context.OpenAsync(req => req.Content("
&
"));
    Console.WriteLine(document.DocumentElement.OuterHtml);
}

The following code will take the input:

&

And will output:

&

In my research on this issue, which has been reported and caused issues for many users, I found the following statement from @FlorianRappl in this closed issue.

This is by specification, see the string escaping that needs to be applied on attribute values..

However, as demonstrated in my above example, this is not just encoding attribute values, it is actually encoding innerHTML content which unless I am mistaken, is certainly valid HTML. I am not aware of any standards that say that HTML content must only include encoded strings.

However, as demonstrated in my above example, this is not just encoding attribute values, it is actually encoding innerHTML content which unless I am mistaken, is certainly valid HTML. I am not aware of any standards that say that HTML content must only include encoded strings.

It has nothing to do with attributes. This is the spec.
Please try running your example in the browser. A & character is &. The HTML parser does convert it.
Run the following in your browser:

&

The output will be:

We cannot (and will not) deviate from the specification.

I also want to mention that we have an alternative non-spec compliant handling of invalid char. references implemented via parser options:
https://github.com/AngleSharp/AngleSharp/blob/master/src/AngleSharp/Html/Parser/HtmlParserOptions.cs#L77


net: net.Listen cannot handle IPv6 addresses not wrapped in square brackets

What version of Go are you using (go version)?

$ go version
go version devel go1.19-dd97871282 Thu Apr 14 18:00:13 2022 +0000 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN="/home/user/go-linux-amd64-bootstrap/bin"
GOCACHE="/home/user/.cache/go-build"
GOENV="/home/user/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/user/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/user/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/user/go-linux-amd64-bootstrap"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/user/go-linux-amd64-bootstrap/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="devel go1.19-dd97871282 Thu Apr 14 18:00:13 2022 +0000"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1164764538=/tmp/go-build -gno-record-gcc-switches"

What did you do?
Listen to the address ::1
https://go.dev/play/p/RA_UpIcsvtp?v=gotip
What did you expect to see?
net.Listen being able to handle IPv6 addresses not wrapped in square brackets
What did you see instead?
error: too many colons in address
I think either net.Listen has to handle IPv6 addresses the way net.ParseIP does, or otherwise net.ParseIP has to return an error on IPv6 addresses not wrapped in square brackets.

Please see https://pkg.go.dev/net#JoinHostPort which handles this case correctly. String concatenation does not work. Closing.


CIP-0030: provide unique wallet identification

When trying to integrate light wallets with the Plutus Application Backend, I came across the issue where I need a wallet id before activating a contract. Currently, the PAB requires a wallet id encoded in blake2b_160, which is what Daedalus (cardano-wallet) uses.
Therefore, does it make sense to enhance the API with a getWalletId function?
Maybe something like:
api.getWalletId(): Promise<WalletId>

type WalletId = Blake2b_160;

@rooooooooob

I need something like this as well.
@rooooooooob

Need a good definition of what is the "wallet id" in that case, and how Daedalus/PAB define it. It's gotta be a Blake2b_160 of something specific, there's no such thing as a wallet identity inherently in the scheme, can be some part of the derivation.
Yoroi has an experimental feature available in the connector now where you can request identification from a user, when connecting, and then receive an auth object with some parameters like a wallet ID and a dapp-specific pubkey, etc. We could add some PAB-specific identity there as well quite easily, before proposing the final version of this to the spec, but need to know what exactly the cardano-wallet is using in that case.
@koslambrou , can you provide some links to the PAB or cardano-wallet documentation where this specific wallet id is described?

One idea we had in the past was to instead define a new derivation paths for wallets that are a "utility key" path. You can still find the draft idea for this here: https://github.com/Emurgo/EmIPs/pull/4

Also, depending on what you want this for, it may be related to https://github.com/cardano-foundation/CIPs/issues/204


Acmorris/readGeopackage

@ldanzinger @michael-tims please review

@michael-tims p/r

@michael-tims p/r

@michael-tims mostly done but how do I push up the filename changes? I changed them and pushed them up but when I checked out again they were back to their original (un-camelcased) state

@acmorris You may have to use command line git and do git mv Geopackage GeoPackage.  then git should detect the case change.

@michael-tims files should be good now

@michael-tims should be alright now

@michael-tims folders are renamed


[QA] Minigames | After losing a spot and re-enter, the camera is no longer fixated

Explorer Alpha build versions:
Not version specific
Issue Description:

Color Pop:
To reproduce this issue, we need to have more people in queue. One needs to kick out the previous person, and the one that has been kicked out needs to re-enter. When entering again, the fixed camera stops working and the movement of the game goes with the movement of the avatar and you can exit the first person view, seeing your avatar walking around and your nametag.
STR:

Start playing
Have 2 more players entering the queue, the third one will kick you out
Try enter the game again and play

Expected behaviour:
The queue should not be breaking and we should wait again for our turn
Current behaviour:
The queue breaks and entering the game again breaks the fixation of the camera
Evidence:
https://github.com/user-attachments/assets/6f6296c1-ab76-49a5-9197-3febc1f10488
Additional Notes:

Issue related to https://github.com/decentraland/unity-explorer/issues/2500

Couldn't reproduce the issue with the new queue version on v0.37

Couldn't reproduce the issue with the new queue version on v0.37

I was able to reproduce it on v0.38 (currently testing for release), we were testing the queue, it didn't kicked me out of the game but the camera got dettached:
https://github.com/user-attachments/assets/f1062555-5590-414b-93c0-d3291d354d02


About Hybrid-Layer Implement

Thank you for your great work and well-organized repo.
However, I do not find any code for the variant scheme Hybrid epoch or Hybrid layer. How did you implement Hybrid layer? Are there two decoders, and calculate losses separately?

Thanks for your interest in our work.
We will release the code for the hybrid epoch and the hybrid layer scheme. Considering the trade-off between the overall training cost and the detection performance, we encourage you to try our hybrid branch scheme.


Fix "method_lines" issue in client/src/pages/SignupPage.js

Function SignupPage has 84 lines of code (exceeds 25 allowed). Consider refactoring.
https://codeclimate.com/github/chrisminnick/soliloquy/client/src/pages/SignupPage.js#issue_65836b83e25656000100003c

Refactored to extract functions into custom hooks.


Modify SelectJupyterURI to allow URI parameter

For #8902
Made the change to allow a bool and URI to be passed to command jupyter.selectjupyteruri. If source is a Uri it sets the serverSelector to the remote uri provided by the user.
I added the bool mostly because it seemed like that was what it was originally setup to do. But the arg was unused because this.serverSelector.selectJupyterURI(true, source), had true hardcoded. It might not be necessary but it does allow someone to call jupyter.selectjupyteruri and have their selector not include local options.
I also added a test for this case in the commands unit test for the serverSelector.

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[x] Appropriate comments and documentation strings in the code.
[x] Has sufficient logging.
[ ] Has telemetry for enhancements.
[x] Unit tests & system/integration tests are added/updated.
[x] Test plan is updated as appropriate. : N/A
[x] package-lock.json has been regenerated by running npm install (if dependencies have changed). N/A

Codecov Report

Merging #8918 (af09aa1) into main (e9eb7e1) will decrease coverage by 0%.
The diff coverage is 100%.

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

@@          Coverage Diff           @@
##            main   #8918    +/-   ##
======================================
- Coverage     71%     71%    -1%
======================================
  Files        382     382
  Lines      24750   24828    +78
  Branches    3826    3860    +34
======================================
- Hits       17718   17645    -73
- Misses      5503    5659   +156
+ Partials    1529    1524     -5

Impacted Files
Coverage Δ

src/client/datascience/commands/serverSelector.ts
90% <100%> (+3%)
:arrow_up:

src/client/debugger/jupyter/debugControllers.ts
20% <0%> (-43%)
:arrow_down:

...ience/variablesView/variableViewMessageListener.ts
77% <0%> (-23%)
:arrow_down:

src/client/debugger/jupyter/kernelDebugAdapter.ts
57% <0%> (-20%)
:arrow_down:

src/client/debugger/jupyter/helper.ts
41% <0%> (-20%)
:arrow_down:

...ent/common/application/webviewViews/webviewView.ts
67% <0%> (-11%)
:arrow_down:

...rc/client/datascience/jupyter/debuggerVariables.ts
58% <0%> (-8%)
:arrow_down:

...tascience/jupyter/kernels/kernelCommandListener.ts
69% <0%> (-5%)
:arrow_down:

...ient/datascience/jupyter/kernels/kernelProvider.ts
85% <0%> (-5%)
:arrow_down:

.../client/datascience/debugLocationTrackerFactory.ts
92% <0%> (-4%)
:arrow_down:

... and 26 more

You should fix the linter problems. The other tests failing are a known issue and not caused by your change. You can ignore those.


upgrade to django 4.0

@jtrain - I fixed up all of the tests and ran black. I will merge this in - this is good to go I think.
I intend to do those things for all of the projects we started using in our repo directly.
The tests were run on django==5.1.11.


This feature is implemented using reflection. If you see this exception, something in your setup is not standard.

device: Xiaomi Redmi Note 5 Pro, API 28

method: carbon.widget.EditText.setCursorColor(...)
cause: java.lang.NoSuchFieldException: No field mCursorDrawable in class Landroid/widget/Editor; (declaration of 'android.widget.Editor' appears in /system/framework/framework.jar!classes2.dex) at getDeclaredField(Class.java:-2)

Duplicate of https://github.com/ZieIony/Carbon/issues/425


bundle outdated prints incorrect output

Overview
bundle outdated fails to list gems that are outdated.
Expected output
bundle outdated
Fetching gem metadata from https://rubygems.org/............
Fetching version metadata from https://rubygems.org/.
Resolving dependencies...

Outdated gems included in the bundle:
  * aws-sdk (newest 2.6.27, installed 2.6.23) in group "default"
  * aws-sdk-core (newest 2.6.27, installed 2.6.23)
  * aws-sdk-resources (newest 2.6.27, installed 2.6.23)

Actual output
bundle outdated
Fetching gem metadata from https://rubygems.org/............
Fetching version metadata from https://rubygems.org/.
Resolving dependencies...

Bundle up to date!

Diff
diff expected actual
6,9c6
< Outdated gems included in the bundle:
<   * aws-sdk (newest 2.6.27, installed 2.6.23) in group "default"
<   * aws-sdk-core (newest 2.6.27, installed 2.6.23)
<   * aws-sdk-resources (newest 2.6.27, installed 2.6.23)
---
> Bundle up to date!

Full steps to reliably reproduce the problem:

Install gems until you get exactly the following output from gem list aws.

gem list aws

*** LOCAL GEMS ***

aws-sdk (2.6.23)
aws-sdk-core (2.6.23)
aws-sdk-resources (2.6.23)

Note that aws-sdk 2.6.27 is not installed.

In an empty directory, create the following files:

cat Gemfile Gemfile.lock
# Gemfile
source 'https://rubygems.org'
ruby '2.2.5'
gem 'aws-sdk'

# Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:
    aws-sdk (2.6.23)
      aws-sdk-resources (= 2.6.23)
    aws-sdk-core (2.6.23)
      aws-sigv4 (~> 1.0)
      jmespath (~> 1.0)
    aws-sdk-resources (2.6.23)
      aws-sdk-core (= 2.6.23)
    aws-sigv4 (1.0.0)
    jmespath (1.3.1)

PLATFORMS
  ruby

DEPENDENCIES
  aws-sdk

RUBY VERSION
   ruby 2.2.5p319

BUNDLED WITH
   1.13.6

Notice that the Gemfile places no constraints on aws-sdk.

Run bundle outdated and see the message "Bundle up to date!", which is incorrect, because aws-sdk 2.6.27 has been released.

Versions Tested
ruby -v # ruby 2.2.5p319 (2016-04-26 revision 54774) [x86_64-darwin15]
gem -v # <IP_ADDRESS>
bundler -v # Bundler version 1.13.6
rbenv -v # rbenv 1.0.0-21-g9fdce5d

Notes

bundle outdated --no-strict also erroneously prints "Bundle up to date!"
bundle update works as expected, updating the gems to 2.6.27 and writing a new lock file
If you gem install aws-sdk -v '2.6.27' and then run bundle outdated, it produces the correct output.
The aws gems are just the example I have chosen. This issue is not specific to them

This looks like #4979. If you agree, we can close this.

This looks like #4979. If you agree, we can close this.

I'm not certain it's the same. I'm not using source .. do as you are in your test case but I don't know if that's a significant difference.
So this is fixed in master, but has not been released yet? If you're convinced it's fixed, feel free to close.

Correct, fixed in master, should go out with 1.14.

As a workaround, instead of bundle outdated, I have been using:
bundle update && git checkout . && bundle outdated

Hope it helps someone.


Incorrectly reads config with comments

Hello! Thanks for the simple and great plugin!
The old library for config parsing is incorrectly parsing configs with comments.  I checked the library and there was no change there for 4 years. Maybe we can replace it with something more popular like - https://www.npmjs.com/package/ssh-config ? I didn't test yet if the library correctly parses comments in the config file.

Hey, thanks, man! I'm pleased to hear it's helped you :)
And holy crap, yeah, that lib is soooo much better! If I find some spare time, I'll switch to using it. If you get impatient, though, I'd happily accept a PR and immediately publish to npm.
Thanks for discovering the bug and researching that package; future users will appreciate the smoother experience :)

Do you have an example config that causes the incorrectness? I'm having some issues reproducing. This works fine for me:
# This is a test comment
Host test.localhost
    # This is also a test comment
    User they4kman
    Port 31337
    IdentityFile ~/.ssh/id_rsa

Closing due to inactivity.
Lemme know if it's still giving ya trouble


Feature Request - File syncing of project code with sbt client/server

This is not a bug report, it is a feature request.
At my last job, the setup we had involved two separate tools - one to sync the code files in a project between our local laptops and our build/test servers and a separate tools to actually compile/run/build the code on our build/test servers. It would be nice if one tool could do both of those things.
Basically, instead of using something like Unison (http://www.cis.upenn.edu/~bcpierce/unison/ ) to sync the code on our laptop with the code on our build/test server and using sbt client/server to send the compile/test/run commands over the wire, could you combine those two things and maybe integrate it with IntelliJ so that it is one tool that just works and does what I want it to do? Forcing every single person to set up and configured Unison to sync sbt project files between their laptop and their workstation is a pain.

It's an interesting idea, but I think this is something that can first be implemented as an experimental sbt plugin in the ecosystem. Would you like to work on it, and see how it pans out?

I've actually been thinking about this recently and had toyed with the idea of writing a plugin that implements some variant of this idea myself. I agree with @eed3si9n that this is something that should probably be done as a plugin first. It isn't exactly clear to me what the exact semantics of the syncing should be. For example, should it use rsync or git? How is the server run? How are firewalls navigated? If I built the plugin myself it may not exactly fit your needs.  If it started as a plugin, it would be easy to iterate on and you or someone else could get something out that provided value very quickly. The time scale to get the feature merged into sbt would likely be significantly longer.
I do think it's a great idea and hope that someone can contribute something.


🐞[Bug]:  Social media icons are not functional

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Social media icons are not functional, not redirected to any site when clicked.
Expected behavior
Should open respective social media pages
Add ScreenShots

What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@sk66641 please assign this issue to me, i will add functionality to icons.
Please label it under Gssoc and assign a level.


Calling functions inside functions in service/factory

How do recommend calling a service function inside another function?
function dataservice() {
    var b = 42;

    var service = {
        getSomething: getSomething,
        getSomethingElse: getSomethingElse
    };

    return service;

    ////////////

    function getSomething() {
        // this might cause problems right?
        return calcSomething(value);
    }

    function getSomethingElse() {
        // this might cause problems right?
        return calcSomething(value);
    }

    function calcSomething(a) {
        return a + b;
    }
}

// this might cause problems right?

@tobbbe, what kind of problems do you have in mind ?

@tobbbe This looks perfect. I don't see any issues on this. In fact, in my current project I have something similar to this where i need to do some string manipulation before hitting the API. We kind of put the logic inside a private function and that stuff seems to work like a charm.

You're doing it correctly.  You're basically using calcSomething() as a private function since it's not part of your service object that you're returning.

 But I might have get that wrong then :)
I thought I'd might need a var that = this; to be safe. But I dont then?

As long as you don't use this within calcSomething you're good to go. Since you most likely won't this shouldn't be a problem.

nope. no issues there.

Thanks for posting this question and for the people who answered it! It helped me in my project :)


Find is not working

What system are you running Yazi on?
Linux Wayland
What terminal are you running Yazi in?
Alacritty
Yazi version
yazi 0.1.5
Did you try the latest main branch to see if the problem has already been fixed?
Tried, but the problem is still present
Describe the bug
When using main branch latest release, find is not working anymore.
I thought it's my duty to notify it.
Expected Behavior
I expected it to work.
To Reproduce
Simply run find command and it won't work.
Configuration
No response
Anything else?
In the past, when the find command was working fine, I also noticed that when you search for a folder like Vídeos (with an accent in letter "i"), it didn't match the query when searching without accent.
It would be great to have a way to search without having to write accents.
Thank you in advance.

Thanks for your report. I've recently refactored a significant amount of code in preparation for the new plugin system.
While I carefully reviewed each command, I seem to have misplaced a find_do - it's an internal command and is not documented externally. Maybe we need more reviewers!
Anyway, I've implemented a quick fix for it, https://github.com/sxyazi/yazi/commit/5336f005ce76b58199cbf84f5c74dec98b5b8784. Let me know if it works for you!

Working fine, thank you @sxyazi
By the way, do you thing that a find command without having to type accents would be possible?

I haven't used these symbols, seems that it requires some specific Unicode conversion.
Yazi uses the regex crate for impl find, which appears to have provided some Unicode support. I'm not sure if it covers the symbols you mentioned, if it's possible and doesn't cause a performance impact, I would be willing to accept a PR.


Add client_secret_basic auth exchangeCode Method. IdentityModel/oidc-client-js#892

See related IdentityModel/oidc-client-js#892
This Pull request add a new parameter named client_authentication who hold the needed authentication type (client_secret_post or client_secret_basic).
To avoid breaking change, the default value is client_secret_post.
This PR allow to exchange a code for user information in the method exchangeCode.

This pullrequest is already open 3 months. Is it possible to merge this? This is the solution for me i am waiting for and is the solution for me to be able to use it

var client_authentication = args._client_authentication || this._settings._client_authentication
shouldn't the variables be var client_authentication = args.client_authentication || this._settings.client_authentication without lodash notation? only local variables on the class have underscore prefixes not the settings variables.

@waldo2188 Any comments on @frontendplace's feedback?

Selam JavaScript kimlik doğrulaması için sanırım erişim veriliyor

Wow, incredible that client_secret_basic still doesn't work.

Hi,
Any news on this pull request ?

Selam @Blamoh
Did you check here?  https://github.com/IdentityModel/oidc-client-js/issues/892#issue-465838030

Salam @kadirselcuk, thanks for the comment ... i added a comment there also :)

@brockallen is there an update on this?
I've got make this pr work on my side. I can offer to create a new pr since the original creator isn't responding.

@brockallen is there an update on this?
I've got make this pr work on my side. I can offer to create a new pr since the original creator isn't responding.

Thank you for taking care of it. Unfortunately I don't have much time at the moment.

Thank you for taking care of it. Unfortunately I don't have much time at the moment.

There were some small issues with the PR, but I fixed them. This will be included in the next release (which I finally have a day open tomorrow to work on!)

There were some small issues with the PR, but I fixed them. This will be included in the next release (which I finally have a day open tomorrow to work on!)

I looked at the code from the merge. It’s look like a part of the code is missing in the file src/TokenClient.js in the method exchangeCode under the line basicAuth = args.client_id + ':' + args.client_secret;
This was the part that build the url query.
urlQuery = "?grant_type=" + encodeURIComponent(args.grant_type) +
               "&redirect_uri="+ encodeURIComponent(args.redirect_uri) +
               "&code="+ encodeURIComponent(args.code);

What is the reason for the deletion of this code?
Did I need to do a new PR to update this part ?

What is the reason for the deletion of this code?

Because the params still needs to go into the request body, even if you're passing the client credentials as HTTP basic auth. Not sure why that was added in the original PR, as it's incorrect.

My bad.
I’ve misunderstood the implementation of OpenId Connect for our use (the sever was taking both source URL Query and body). So now I understand why you clean the code.
thank you very much for these clarifications.


title hover effect

Fixed issue  🛠  #142

improved title hover effect
removed shadows background form title
white hover effect on title

do some other style changes as this one is not as appealing as it should be

do some other style changes as this one is not as appealing as it should be


Added extra checks to review method

Review text is now optional in both method checks and schema.
Review rating is checked to make sure it's an integer between 0 and 3.
Review object structure is checked so that no other fields are permissible.

Fixes #30

:+1:


Increase test coverage across all modules

Issue used to track a single pass of test additions to across the repository.

#364 #360 #359 #358 #357 #356 #355


Register page on Angular SPA Template

From @kwakuduahc1 on Thursday, September 26, 2019 3:02:48 PM
Register page on Angular SPA Template
I cannot find the register page/view in the new Angular SPA template. I have looked into the pages and ClientApp folder but I can neither find the controller for authentication nor the view/page for it.
Clicking on register loads the page alright.
Thank you.
Copied from original issue: dotnet/core#3484

Thank you @scalablecory, it is easily forgettable that netcore is not the same as aspnet netcore

Thanks for contacting us, @kwakuduahc1 .
Identity related pages are loaded from the DefaultIdentityUI package. If you want to modify those in any way, you can scaffold the necessary pages and modify as needed.

You can read more about this https://devblogs.microsoft.com/aspnet/aspnetcore-2-1-identity-ui/


makefile: update hyprpm headers on make installheaders

Describe your PR, what does it fix/add?
Do a work arround to use plugins fixing #5896
It just updates the headers of hyprpm when doing make installheaders
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
no
Is it ready for merging, or does it need work?
yes

no, this is bad. It's better to actually fix the issue


WorkQueueExecutor.set_bad_state_and_fail_all fails when some tasks have already completed

Describe the bug
BlockProviderExecutor.set_bad_state_and_fail_all contains code to fail all tasks:
        for task in self._tasks:
            self._tasks[task].set_exception(BadStateException(self, self._executor_exception))

However, with the Work Queue Executor, if some tasks have already completed (see issue #2207 for when this might happen), then set_exception will raise an exception when called on the tasks that are already completed.
1668693198.706212 2022-11-17 13:53:18 MainProcess-54349 FlowControl-Thread-139792904353536 parsl.dataflow.flow_control:100 make_callback ERROR: Flow control callback threw an exception - logging and proceeding anyway
Traceback (most recent call last):
  File "/home/benc/parsl/src/parsl/parsl/dataflow/flow_control.py", line 98, in make_callback
    self.callback(tasks=self._event_buffer)
  File "/home/benc/parsl/src/parsl/parsl/dataflow/task_status_poller.py", line 111, in poll
    self._error_handler.run(self._poll_items)
  File "/home/benc/parsl/src/parsl/parsl/dataflow/job_error_handler.py", line 14, in run
    self._check_irrecoverable_executor(es)
  File "/home/benc/parsl/src/parsl/parsl/dataflow/job_error_handler.py", line 19, in _check_irrecoverable_executor
    es.executor.handle_errors(self, es.status)
  File "/home/benc/parsl/src/parsl/parsl/executors/status_handling.py", line 147, in handle_errors
    error_handler.simple_error_handler(self, status, init_blocks)
  File "/home/benc/parsl/src/parsl/parsl/dataflow/job_error_handler.py", line 25, in simple_error_handler
    executor.set_bad_state_and_fail_all(self.get_error(status))
  File "/home/benc/parsl/src/parsl/parsl/executors/status_handling.py", line 124, in set_bad_state_and_fail_all
    self._tasks[task].set_exception(BadStateException(self, self._executor_exception))
  File "/usr/lib/python3.9/concurrent/futures/_base.py", line 540, in set_exception
    raise InvalidStateError('{}: {!r}'.format(self._state, self))

This leads to subsequent tasks not having an exception set.
To Reproduce
parsl master branch 34fe75fd27f7f0989e944c12930500bf90351733
Run this code, then when the code is "waiting for that worker lost", killall -KILL work_queue_worker.
Observe that
from parsl.tests.configs.workqueue_blocks import config

import parsl

parsl.load(config)

@parsl.python_app
def fast():
  pass

@parsl.python_app
def long():
  import time
  while True:
    time.sleep(3600)

print("running one task to completion")
fast().result()

print("one task run to completion")

while True:
    print("now submit one that I expect to fail with worker lost")
    future = long()

    print("waiting for that worker lost")
    assert future.exception() is not None

print("done")

The following log message will appear (as should happen)
set_bad_state_and_fail_all ERROR: Setting bad state due to exception
but then the above concurrent.futures._base.InvalidStateError will be logged, and the workflow will not terminate.
This does not happen with the HighThroughputExecutor, because HTEX removes completed tasks from self.tasks.
A fix for this bug might be for the Work Queue Executor to also remove completed tasks from self.tasks.
Expected behavior
The test workflow should not hang.
The test workflow should probably return an exception from every invocation of future = long().exception() - so it should be seen to noisily loop infinitely, rather than hang.
In practice in a real workflow (with a non-infinite number of tasks) that should result in clean workflow ending via exceptions.
Environment
my laptop

HTEX also seems to call _set_bad_state_and_fail multiple times, but this results in a different weird behaviour: that the stack track for the failing exception gets long and longer (as if it's being nested repeatedly due to how it is generated?)


Azure IoT Sample Does not work for MQTT_PROTOCOL_V5

Got the reason. MS Azure does not support V5 yet.


How to infer inscription id from transfer event?

I have a use case where I have known inscriptions (with id, or number) that I would like to track ownership transfers of. It seems that the transfer event only has "ordinal_number". Would it be possible to have inscription id too?
I understand I could do full indexing and try and maintain the link between inscription id and ordinal_number base on inscription_revealed event, but this seems like an overkill.
 "inscription_transferred": {
                  "destination": {
                    "type": "transferred",
                    "value": "bc1q8h67dytup75uurg9jpj32mtudrauraf2fd7lnp"
                  },
                  "ordinal_number":<PHONE_NUMBER>93125,
                  "post_transfer_output_value":<PHONE_NUMBER>5,
                  "satpoint_post_transfer": "461b0d8cfea306734a36394edce052194a78b1dc55ab98ab41de17c763bd154b:0:2291455881",
                  "satpoint_pre_transfer": "399f1bd0adb1ba6a3f40c41a8bc9b7b12722d3913741ccb7b2ecad4aae6227d2:0:2291455881",
                  "tx_index": 25
                }

Hi @wagmiwiz! If your observer is running on the same machine than ordhook, you could query the inscriptions table present in the hord.sqlite database.
SELECT inscription_id FROM inscriptions WHERE ordinal_number = ?

Good tip, will move observer to same machine.


Vertex AI [feature]: Support JSON Mode for Gemini

See documentation for responseMimeType at https://cloud.google.com/vertex-ai/generative-ai/docs/model-reference/gemini#request_body
See https://github.com/langchain-ai/langchainjs/issues/5071

Is it possible to pass in our defined schema and specify the use of json_mode, like in this example?
https://python.langchain.com/v0.1/docs/modules/model_io/chat/structured_output/
structured_llm = model.with_structured_output(Joke, method="json_mode")


luci-mod-system: remove bogus btn class in flash.js

fixes #4970

Signed-off-by: Dirk Brenken<EMAIL_ADDRESS>

after the change the modal window looks like that ...

Thanks, I've rebased this PR and synced translations

This change breaks alignment, the text next to the checkbox is not vertically centered. Also the checkbox cannot be selected anymore by clicking anywhere into the red area.

The latter point was really meant as a "feature"? I thought it was a bug, for me it's at least unexpected.


Add code coverage for method _process_compiler_config

The codecov report for https://app.codecov.io/gh/buildtesters/buildtest/blob/devel/buildtest/builders/base.py indicates we have no coverage over this method. See below. Let's add coverage for this

@Mariamajib i will be assigning this task to you

take a look at these

Documentation example https://buildtest.readthedocs.io/en/devel/buildspecs/compiler.html#running-stream-benchmark-with-multiple-compilers
Use this example https://github.com/buildtesters/buildtest/blob/devel/examples/compilers/stream_example.yml for testing


Regex capture group support

As far as I can tell, the current regex module doesn't support capture groups. The search method simply returns the starting and ending indexes of the entire match - there's no way to get the matched groups. I had to hack around this limitation in one of my recent apps: https://github.com/mackorone/tidbyt-word-of-the-day/blob/main/word_of_the_day.star#L60
Any chance capture groups can be supported?

Does findall do what you need?

As far as I can tell, no:
regex = "foo(.*)baz"
content = "foobarbaz"
print(re.findall(regex, content))

Output:

@mackorone Try re.match, it's not documented but it works. It looks like the return value is a tuple, the first item is the full match, and then matching groups follow in order.

Hi @mackorone - Just tested @joeyhoer's solution and it should do what you're looking for:
load("re.star", "re")

def main():
    regex = "foo(.*)baz"
    content = "foobarbaz"
    print(re.match(regex, content))
    return []

$ pixlet render examples/re.star
[examples/re.star] [("foobarbaz", "bar")]

It looks like there are a few methods undocumented and this one of them 😢
Going to close this for now, thank @joeyhoer for the solution! Please feel free to add a comment or open a new issue if this doesn't solve your use case.

Hi @mackorone - Just tested @joeyhoer's solution and it should do what you're looking for:
load("re.star", "re")

def main():
    regex = "foo(.*)baz"
    content = "foobarbaz"
    print(re.match(regex, content))
    return []

$ pixlet render examples/re.star
[examples/re.star] [("foobarbaz", "bar")]

It looks like there are a few methods undocumented and this one of them 😢
Going to close this for now, thank @joeyhoer for the solution! Please feel free to add a comment or open a new issue if this doesn't solve your use case.


Quaternion compression 150 angle diff after decompression

Describe the bug
On some Quaternions decompressed vector can be as much as 150 degrees different from the original.
How to reproduce the issue, step by step

Open your Mirror test project.
Add this script to the Assets folder.
Enter play mode. (Script will spawn 2 cubes: Origin and Another)
Rotate Origin cube and see decompressed result on Another cube.
Apply problematic Quaternion to Origin cube's transform.

Confirmed rotations that give large angle difference:
Vector3(338.850037,170.609955,182.979996)
Vector3(338.850006,230.809998,182.979996)
A pair of close rotations:
This rotation has big difference: Vector3(338.850006,230.809998,241.619995)
But this is good: Vector3(338.850006,230.809998,261.599976)
Expected behaviour
A Quaternion within acceptable margin from the original.
Screenshots

Desktop:

OS: Windows 10
Build target: Standalone x64 for Windows & Linux
Unity version: 2020.3.0f1
Mirror branch: 32.1.4

Additional context:
All issues & pull requests I could find regarding this feature: #2570, #2584, #2368.

True story @vis2k


Narrowed types from user defined type guards are lost in subsequent method calls

TypeScript Version:  2.6.1.
Code
{
    // no error
    const arr1: Array<number> = ['foo', 1].filter(
        (x): x is number => typeof x === 'number',
    );

    /* unexpected error:
[ts]
Type '(string | number)[]' is not assignable to type 'number[]'.
Type 'string | number' is not assignable to type 'number'.
Type 'string' is not assignable to type 'number'.
*/
    const arr2: Array<number> = ['foo', 1]
        .filter((x): x is number => typeof x === 'number')
        .map(x => x);

    // workaround. no error
    const arr3: Array<number> = ['foo', 1]
        .filter((x: any): x is number => typeof x === 'number')
        .map(x => x);
}

Related https://github.com/ReactiveX/IxJS/issues/162

possibly related to #19334. defining the type-guard before the filter call works fine:
function isNumber(x: string | number): x is number {
  return typeof x === 'number';
}
// no error
const arr: Array<number> = ['foo', 1].filter(isNumber).map((x) => x);

@OliverJAsh based on https://github.com/Microsoft/TypeScript/issues/19640#issuecomment-341122227 it looks like this may be fixed by #17600, as this form also works in 2.6.1:
// no error
const arr: Array<number> = ['foo', 1]
  .filter<number>((x): x is number => typeof x === 'number')
  .map((x) => x);

This is indeed fixed by #17600.


Disable RDS backups by default (workaround)

Some facts:

We wish to have the ability to disable RDS backups.
Disabling RDS backups is achieved by setting the backup retention period to 0.
The golang zero value for an Int is 0.
The RDS broker default value for backup retention is 1.
The RDS broker allows you to override the backup retention period as
long as the value is > 0.

Hence, we cannot turn off backups either from a plan or with user-specified parameters.
We decided that having backups default to being off (0) is reasonable as the plans themselves can override this - we may even wish to expose a postgres plan that explicitly does not have backups for testing.
This change simply takes whatever value is defined in the plan rather than requiring it to be > 0, and the plan default is 0 (off).

This could do with unit test coverage (see https://github.com/alphagov/paas-rds-broker/blob/master/rdsbroker/broker_test.go#L297)

@alext Test added. Can we please take out all the aurora tests. Please.


GBM prediction code

This code loops through the species and uses GBM to make predictions about the (Poisson-distributed) abundances.  It would take a while with 8 cores, so we should probably use Hipergator.

Looks great overall.
The one main thing is my confusion as to how the execution of the unnamed function happens. Assuming this is basically a lambda function of some kind, then for something this length I think it's probably easier to understand as it's own separate (non-nested) named function, but since I don't really follow how it's being executed this may be something you have to do to get things to work.
The only other thing that I noticed is that I think a lot of the data management code could be made easier to read using dplyr, but that may just be a personal preference. E.g.,
train_climate = select(train_bbs, matches("ppt|tmin|tmean|tmax"))
train_rescaler = make_rescaler(train_climate)

or even
train_rescaler = make_rescaler(select(train_bbs, matches("ppt|tmin|tmean|tmax"))

instead of
climate_colnames = grep("ppt|tmin|tmean|tmax", colnames(train_bbs), value = TRUE)
train_rescaler = make_rescaler(train_bbs[ , climate_colnames])

hey @davharris - just wanted to see if you might have the chance to finish the recommended changes so that we can get this merged in. I'm also happy to go ahead and merge this one as is if you don't want to make any changes.

Ack.  When did this merge happen? I think someone needs to take the command line away from me whenever I get sick.
Sorry!

Oh no.  I set weecology/bbs-forecasting as my upstream remote and as my origin remote. So when I tried to push to my own master branch, I ended up pushing here.  Fixing now...
Really sorry!

No worries. Just go ahead and submit a new PR with any changes you want to make and reference this one so that it's easy to go back and look at the conversation.


Screen blank when browser size is reduced in full screen

Describe the bug
When the browser size is reduced while the editor window is enlarged, a blank space appears on the right side
To Reproduce
Steps to reproduce the behavior:

Go to workbench
full size button click
browser size reduce
See error

Expected behavior
Area is drawn normally
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@sting009
LNB 클릭 이슈는 여기에 포함되나요?

@ufoscw
LNB 클릭이슈는 기획확인이 필요하여 포함되어있지 않고, 해당 이슈만 선작업하였습니다.


Strip links from featured item description

So I was totally clicking about the app market, and absolutely baffled how I ended up on some weird "OpenAPI" page. Turns out, when I clicked on the Swagger box, it took me there, because this link actually becomes a link on the New & Updated page, since Swagger is the newest updated app.
I love that app descriptions can contain links, and I hope it never goes away. But I'd really like to not suddenly end up on weird pages from the featured box. Clicking on the box should take you to the app page, always.

FWIW you and @kentonv disagree on this point. :)

@paulproteus We do? I don't remember this coming up. What did I say?
I think my current opinion is that the summary card (as screenshotted) ought to de-linkify the text. Actually we've also had problems with headings and such looking wrong there, so this is just one of several formatting changes that should happen specifically for these cards...

See #27 for past discussion. In that one, @zarvox and @kentonv seemed to express a preference for retaining A HREF tags within this summary card, and @neynah seemed to express a preference for removing external links from summary cards.

I am inclined to close this as a dupe of #27, which I did not see when I opened this.


[MonorepoBuilder] SplitCommand default branch option to current branch

Thanks

Seems like last 2 PRs of your have broken the Symplify split :(
https://travis-ci.org/symplify/symplify/jobs/648337614#L420

Could you look at it as soon as possible?


cava module fails: Unable to receive desktop appearance: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop

[2024-07-08 17:08:43.019] [info] Using configuration file /home/snick/.config/waybar/config
[2024-07-08 17:08:43.022] [info] Unable to receive desktop appearance: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop
[2024-07-08 17:08:43.022] [info] Using CSS file /home/snick/.config/waybar/style.css
[2024-07-08 17:08:43.054] [info] Hyprland IPC starting
[2024-07-08 17:08:43.056] [info] Loading persistent workspaces from Hyprland workspace rules
error: interrupted by the user
fish: Job 1, 'waybar' terminated by signal SIGSEGV (Address boundary error)

the configuration used to work until i updated to latest version v0.10.3
configuration:
	"cava": {
		"cava_config": "$XDG_CONFIG_HOME/cava/config",
		 // "format": "  |{}|",
		"framerate": 120,
		"autosens": 1,
		"sensitivity": 1.5,
		"bars": 14,
		"lower_cutoff_freq": 50,
		"higher_cutoff_freq": 15000,
		"hide_on_silence": true,
		"method": "pulse",
		"source": "auto",
		"stereo": false,
		// "reverse": true,
		"bar_delimiter": 0, //124,
		"monstercat": false,
		"waves": false,
		"noise_reduction": 0.77,
		// "input_delay": 2,
		"ascii_max_range": 8,
		// "format-icons": ["▁","▂","▃","▄","▅","▆","▇","█"],
		"format-icons": ["█", "▇", "▆", "▅", "▄", "▃", "▂", "▁"],

		"actions": {
			"on-click-right": "mode"
		}

have you been able to find a fix yet? I am having the same issue :(

no, still crashing when cava plugin is enabled

Hi @i-am-logger , @ItsAllPeachy . libcava was synced with cava upstream. At least there was some major issue with pulse input which is solved. Can you update waybar. Make sure libcava-0.10.3 is used. Let me know about results.
Thanks

Thanks for the pointer to libcava-0.10.3 seems  nix's waybar  package installs  libcava-0.10.1
https://github.com/NixOS/nixpkgs/blob/nixos-24.05/pkgs/by-name/wa/waybar/package.nix#L76

after update libcava to 0.10.3 i get this error:

my cava configuration is in ~/.config/cava/config

"cava_config": "$XDG_CONFIG_HOME/cava/config",

missed this in the config...all good!