x/image/font: make it easier to measure a string's bounds and draw it in a bounding box

This issue applies to github.com/golang/freetype, if that is still under development.
I want to accomplish the following (superficially) easy tasks:

Given a string and a fully specified font/context, determine the rendered string's bounds, taking into account ascenders, descenders, etc.; something along the lines of NSString's -sizeWithAttributes: method.
Given an appropriately sized rect, render a string in that rect, compensating for ascenders, descenders, etc; something like NSString's -drawInRect:withAttributes: method.

I will use this to render a simple, short string into a texture of just the right size, and then upload that texture onto a window for use as a label at a particular origin.
MeasureString looks close, but it only provides the width, not the height. (And I don't see a way to get the line height / leading from a font.) And DrawString is close, but the dot's y offset is the baseline of the text, which I don't see a handy way to calculate.
The fact that these are top-level APIs in Cocoa suggests that these are common needs and that they cover a large portion of use cases. Maybe this should be handled with examples, or maybe with new fundamental APIs, or maybe with convenience APIs. I don't know enough to say.
/cc @nigeltao

Yes, this is part of the "TODO: per-font Metrics" in font.go.
BTW, github.com/golang/freetype is still under development. See also https://github.com/golang/freetype/issues/15

Of the two tasks, the first one seems supported. https://godoc.org/golang.org/x/image/font#Metrics has Ascent and Descent now, and Drawer.BoundBytes seems to work great.
Second isn't. I would love for someone to provide me a "with this font, at whatever face point size is appropriate (but still let me pick DPI & Hinting?), render this text into a box that shall not exceed H pixels tall and/or W pixels wide". For my current need, I specifically am looking to constrain height only.
For now, I wrote a sort.Search gimmick that looks for a point size between 0 and 72 (one inch tall text) at small increments.


Icon request: VirMach

URL of the site or app
https://virmach.com/
Logo resources for the icon
No response
Anything else?
No response

No high quality logos available for this service. I'm dropping this.
Use Server generic icon instead.


How to peek and poke an internal signal or memory?

I searched and didn't find an example.
peek("instA.instB.data", 42)
poke("instA.instB.data")
// or
peek("instA_instB_data", 42)
poke("instA_instB_data")

I saw an example here https://github.com/freechipsproject/treadle/blob/bb72c8c34a1ff707720956c21715d3c202c7bec4/src/test/scala/treadle/MemoryUsageSpec.scala#L420-L429, using LoadMemoryAnnotation, which uses ComponentName.
While I didn't find an example for ComponentName to reference a deep component.

try ReferenceTarget, I think ComponentName has been deprecated?

peek("instA.instB.data", 42)
poke("instA.instB.data")

should work. I verified with a small example.
ComponentName will be transformed to ReferenceTarget.

I think this can be closed


Existing solution doesn't show up in the solutions pages

I've started the threebot server and click on the solution tab.
I was expecting to find all the solutions that are live on the grid also presented in here, but I found nothing.
The all reservations tab is also empty.
Is there anything special to be done to load all solutions from the explorer ?

should fix after merge PR: https://github.com/threefoldtech/js-sdk/pull/210

Verified


processed data files in COSMIC

Could you offer the sample of how to use the processed data files in COSMIC? Thanks.

Could you offer the sample of how to use the processed data files in COSMIC? Thanks.

Thanks for your interest in our work.
The examples for using DialogueCRN with RoBERTa features (i.e., IEMOCAP and MELD) are available now. You can see README.md in this repo for details.
If you have any other questions, please feel free to ask me.

I'm sorry to bother you, but can you provide a fine-tuned roberta model? My GPU doesn't support fine-tuning robert, but I want to extract the features of the text myself.


copyright year updated (sir i have just updated copyright year)

What type of PR is this? (check all applicable)

[ ] ♻ Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 👷 Optimization
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
Related Tickets & Documents
Added to documentation?

[ ] 📜 readme
[ ] 🙅 no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

Maybe you've pushed the wrong branch then? Go to Files changed and you will be able to see that this is not the case.

also the blanks .. Bobby ... all a submit at the private account who be shown.. .. well it's only a comment ;) @bobbyiliev


Design suggestion: keep component alone in render area, move info to right panel

Just an idea.

Yeah totally agree with you on that. If we do that, it'll be possible to use this addon with React Native Storybook. Also check these similar addons:

https://github.com/kadirahq/storybook-addon-notes
https://github.com/mthuret/storybook-addon-usage

It'll be great if someone writes an addon to display component prop information

Do you have a guide for configuring/contributing to this addon? I know it uses the RCK.

I think it'll be a new addon. Check our addon docs: https://getstorybook.io/docs/addons/writing-addons
If we are doing this, I think it's a pretty good idea to provide a way to pass react-docgen to parse the source code and get the propType information.

This will be a good improvement when using this addon with the storyshots feature.
For now, snapshots created from your stories by storyshots includes all the info markup in addition to your component markup.

Here is an attempt to display components info (props & story) into panels
https://github.com/marc-rutkowski/storybook-addon-props
Any feedback is very welcome!


Eigen fails assert after map is fused

Hello,
I am trying to run simple_demo.launch on ROS Kinetic. I believe all of my configs, topics, and transforms have been set up correctly.
When I start up the software, I can see laser scans being incorporated in RVIZ. However, when the map is fused and published, I get the following error:

elevation_mapping: /usr/include/eigen3/Eigen/src/Eigenvalues/EigenSolver.h:347: Eigen::EigenSolver<_MatrixType>::EigenvectorsType Eigen::EigenSolver<_MatrixType>::eigenvectors() const [with _MatrixType = Eigen::Matrix<double, 2, 2>; Eigen::EigenSolver<_MatrixType>::EigenvectorsType = Eigen::Matrix<std::complex, 2, 2>; typename Eigen::NumTraits::Real = double]: Assertion `m_eigenvectorsOk && "The eigenvectors have not been computed together with the eigenvalues."' failed.

A GDB trace shows that this is coming from the following line:
const double ellipseRotation(atan2(solver.eigenvectors().col(maxEigenvalueIndex).real()(1), solver.eigenvectors().col(maxEigenvalueIndex).real()(0)));
Any idea what could be causing this? It always happens after ROS_INFO prints for the first time that the map has been fused.
Thanks,
d-rohr

This seems to be the same as pull request #65 related to covariances of the pose being too high. I can suppress this issue by artificially lowering the covariances, but I imagine that will degrade performance.


Fixing add profile repeater not enabled for fetched speaker profile

isPlaceholder is returned as true for some saved profiles. ideally it should not be stored and returned from backend. Adding checks to prevent handling of this.
Resolves: MWPW-154773
Test URLs:

Before: https://main--ecc-milo--adobecom.hlx.page/
After: https://gbajaj-bugfix--ecc-milo--adobecom.hlx.page/

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

Please upload report for BASE (dev@f9df14b). Learn more about missing BASE report.

Additional details and impacted files
@@          Coverage Diff           @@
##             dev     #102   +/-   ##
======================================
  Coverage       ?   67.22%
======================================
  Files          ?        2
  Lines          ?      238
  Branches       ?        0
======================================
  Hits           ?      160
  Misses         ?       78
  Partials       ?        0

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

Just have one quick question on a lana line removal. Other than that LGTM.

And we can probably remove the comment lines


[Cluster Object Model] Generate necessary service config based on cluster type

#3437 uses config/service.yaml and config/service.k8s.yaml to differ different cluster types.
If you add a new field in config/service.yaml, you need to revert changes in #3437 first.
The name openpai_parser_type in config/service.yaml is also confusing, could you use another name like service_type?

I wil change it in anther PR

#3437 uses config/service.yaml and config/service.k8s.yaml to differ different cluster types.
If you add a new field in config/service.yaml, you need to revert changes in #3437 first.
The name openpai_parser_type in config/service.yaml is also confusing, could you use another name like service_type?

#4038 Please review this PR first.

openpai_parser_type is confusing, maybe change to another name, e.g. service-type?

Done


Not able to remove events without ts errors. Hover in this example.

Describe the bug
A clear and concise description of what the bug is.
I'm sure you're getting sick of me already, but I'm having trouble removing events like hover within your library without type errors.
It all works, but the index file does not have that defined.

This works inside a normal, non-typescript version, but typing either  hover: { mode: null }, or the chartjsV3 way just throws errors.
events:[
        hover: {
          mode: null,
        },
       ],

Is there something I am missing?
To Reproduce
Put a reproduction link here based on this templates
https://codesandbox.io/s/responsive-chart-font-gk28n?file=/src/components/Chart2.vue

Template for Vue 3
Template for Vue 2
Template for Nuxt 2

Version of vue-chart-3
ex: v3.0.2
Version of Vue

[ x] Vue 3
[ ] Vue 2
[ ] Nuxt 2
[ ] Nuxt 3

This types of errors is not from vue-chart-3 but from Chart.js itself. This lib is just an adapter to use easily Chart.js in a Vue app with pre-made components. The events types from Chart.js source doesn't include hover, you need to check more what shape does the ChartOptions type have!

You put hover in the wrong place. It should look like this:
const options = computed<ChartOptions<'bar'>>(() => ({
      hover: {
        mode: null,
      },
    }));

Ahhh sorry, I figured it was some issue with the computed<ChartOptions<'bar'>> syntax from the composition API.
But still, when I try what you've written, I still get an error.

The 'fix' I've found is actually removing the hover event in the events array, but this doesn't seem like the safest/smartest option. It does remove the error however and there is no longer a hover event of any kind.

My code pen does give errors, but my project does. Very bizzare.
Thanks again for the quick comments though!


Implement custom UserAgent http header for Certes (#189)

Description
Implement custom UserAgent http header for Certes (#189)
UserAgent header has format: Certes{libversion} (ACME 2.0)
Checklist

[x] All tests are passing
[x] New tests were created to address changes in pr (and tests are passing)
[x] Updated README and/or documentation, if necessary

Cool! As Certes is a library it would also be useful (essential in some places) to also extend the user agent to include the name/version of the tool/UI etc that's using Certes. Users can override the default http client (skipping this implementation) but it would great if we could just set a string to extend the user agent.


fix(sqlparser): keyword after char shall not be consumed on error

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
When parsing CHARACTER VARYING the current sqlparser consumes the 2nd keyword unconditionally, leading to CHARACTER AS accepted as char unexpectedly.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

🥵 Did any user meet this bug and how did they use it?

Not heard any. The code path is seldom hit because we have been promoting varchar. Writing char would trigger an error either early (due to this sqlparser bug) or later (as an unsupported type).
I ran into this bug because I was testing character include for https://github.com/risingwavelabs/risingwave/pull/18821#discussion_r1794837382.


How to run UNIT TEST for a particular component (IDFGH-8681)

Answers checklist.

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

General issue report
Hello. I have been reading and learning about unit tests lately and wanted to setup a very simple project with my very first unit test.
I have followed these simple steps:

In my project, I have created a component called "test_component".

In this component directory, I have created a directory called "test" as explained in the esp.idf instructions.

In this "test" directory, I have test.c and CMakeLists.txt

I have enabled "Include Unity test fixture" in menuconfig

My test_component.c is as following:

#include <stdio.h>
#include "test_component.h"

int sum(int a, int b){
    return a+b;
}

As you can see from above, the component contains 1 function that I want to run unit test for.
My test.c is as following:
#include "test_component.h"
#include "unity.h"

// test sum function
TEST_CASE("sum function test", "[sum]")
{
      TEST_ASSERT_EQUAL_INT(sum(1,2),3);
}

My test CMakeLists.txt:
idf_component_register(SRC_DIRS "."
                       INCLUDE_DIRS "."
                       REQUIRES unity test_component)

My project structure is as following:

My problem:
It is not fully clear to me how can I run this test. Could someone help me understand how can I execute this test?

Hi @krupis, please refer to this example: https://github.com/espressif/esp-idf/tree/master/examples/system/unit_test

I'll close this as I think the question has been answered. Please leave a comment if something is unclear!


README: add installation for FreeBD etc

While here, switch some links to https.

as for "skip ci", I think we may exclude "md" from CI triggers


Boxes overlapping when using numeric columns and boxplots

When trying to plot a boxplot from a pandas.DataFrame where some of the column names are numbers like 7 or strings like "7", strange things happen like boxes overlapping each other.
For example, pd.DataFrame(np.random.randint(0, 100, (100, 3)), columns=['1', '2', 'a']).iplot('box') produces this

And pd.DataFrame(np.random.randint(0, 100, (100, 5)), columns=['1', '2d', 'a', 4, 'asfd']).iplot('box') produces this

Similar things happens in plotly express, not matplotlib. It seems plotly bug with mixture of number and letters columns.

plotly express

import pandas as pd
import numpy as np
import plotly.express as px
df = pd.DataFrame(np.random.randint(0, 100, (100, 3)), columns=['1', '2', 'a'])
px.box(pd.melt(df), x='variable', y='value')

matplotlib

%matplotlib inline
import matplotlib.pyplot as plt
pd.DataFrame(np.random.randint(0, 100, (100, 3)), columns=['1', '2', 'a']).plot(kind='box')

@xoelop The following issue might be related.
https://github.com/plotly/plotly.py/issues/1918#issuecomment-557379980
# quickfix
fig.update_layout(xaxis_type='category')


vscode-icons causes restart loop with NxWorkspace projects

[X] I'm sure this issue is not a duplicate.

vscode-icons causes NxWorkspace projects to keep reloading.

Create a new Nx Workspace (create-nx-workspace app-name)
Choose "fullstack application"
Open it
VS Code will keep refreshing itself

Remove package.json (or just change it's extension) and issue will disappear.

Only happens if you have vsicons.projectDetection.autoReload enabled.

Duplicate of #1925


Android build error

Summary

Version
2.1.3

Affected OS
Android

OS Version
?

Current behavior
Got error when run ./gradlew assembleRelease

Expected behavior

That’s the nature of a breaking change - please check release notes for major version bumps:
https://github.com/react-native-community/react-native-device-info/releases/tag/v2.0.0
(note sdk moved to 28)

@mikehardy
I have already set compileSdkVersion = 28 in android/build.gradle. I still got the same error.

Something isn’t the way you expect then, I can’t say what’s wrong with your local state but I know that symbol, it exists in 28 https://developer.android.com/reference/android/os/Build.VERSION_CODES.html#P
Maybe try npm i —save-dev react-native-clean-project && react-native clean-project-auto, but this is a project problem, not the module, sorry

I too am experience this issue with compiledSDKVersion 28
Android/build.gradle
`// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
ext {
buildToolsVersion = "28.0.3"
minSdkVersion = 19
compileSdkVersion = 28
targetSdkVersion = 28
supportLibVersion = "28.0.0"
googlePlayServicesVersion = "16.0.0"
firebaseVersion = "17.0.0"
}
repositories {
google()
mavenLocal()
mavenCentral()
jcenter()
}
dependencies {
classpath('com.android.tools.build:gradle:3.4.1')
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

}
allprojects {
repositories {
mavenCentral()
mavenLocal()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url("$rootDir/../node_modules/react-native/android")
}
maven {
// Android JSC is installed from npm
url("$rootDir/../node_modules/jsc-android/dist")
}
maven { url 'https://jitpack.io' }
google()
jcenter()
}
}
// Specified to graddle to ignore the other flavors of RNN provided.
// *** Needs to be updated as more variants become available. ***
subprojects { subproject ->
afterEvaluate {
if ((subproject.plugins.hasPlugin('android') || subproject.plugins.hasPlugin('android-library'))) {
android {
variantFilter { variant ->
def names = variant.flavors*.name
if (names.contains("reactNative51") || names.contains("reactNative56")) {
setIgnore(true)
}
}
}
}
}
}
subprojects {
project.configurations.all {
resolutionStrategy.eachDependency { details ->
if (details.requested.group == 'com.android.support' && !details.requested.name.contains('multidex') ) {
details.useVersion "27.1.1"
}
}
}
afterEvaluate {
android {
compileSdkVersion 27
buildToolsVersion "27.0.3"
defaultConfig {
targetSdkVersion 27
}
}
}
}`

Pattern off the example perhaps https://github.com/react-native-community/react-native-device-info/blob/master/example/android/build.gradle

for forammint what you want is likely a triple-tick and groovy, the code, then another tripletick like:
allprojects {
  repositories {
     etc
  }
}

Since the second time it's happened though people have tried to set to 28, there may be something in the tools that is leaving old/broken state behind? Or something else to it? If I could pin down what is causing it to be hard (it's supposed to be easy! but isn't everything...) we could add some docs.
In the meantime when I am having strange build problems I usually do a full purge before attempting deep inspection:
npm i --save-dev react-native-clean-project && npx react-native clean-project-auto
it'll cause a pod refetch and npm module re-fetch so might be network transfer expensive, but you will know you have clean state afterwards

Thanks for your help. I really appreciate it. I have been banging my head against the wall upgrading everything to RN 60 and AndroidX.
I am in the process of cleaning everything, re-installing, and then I will invalidate my caches for AndroidStudio and report back.

No problem - I’m also the jetifier person (https://github.com/mikehardy/jetifier) - written because yes, it can be super frustrating. It is possible though! Unless your libraries have not moved to AndroidX and have one of the problems in the troubleshooting section of jetifier. Good luck

Receiving the same error: cannot find symbol variable P
react-native 0.60.0-rc
react-native-device-info 2.2.0
I've tried
rm -r node_module
npm i --save-dev react-native-clean-project && npx react-native clean-project-auto
npm install
react-native start -- --reset-cache
Android Studio > File > Invalidate Caches / Restart
buildscript {
    ext {
        buildToolsVersion = "28.0.3"
        minSdkVersion = 19
        compileSdkVersion = 28
        targetSdkVersion = 28
        supportLibVersion = "28.0.0"
        googlePlayServicesVersion = "16.0.0"
        firebaseVersion = "17.0.0"
    }
    repositories {
        google()
        mavenLocal()
        mavenCentral()
        jcenter()
    }
    dependencies {
        classpath('com.android.tools.build:gradle:3.4.1')

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        google()
        mavenCentral()
        mavenLocal()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        maven { url 'https://jitpack.io' }
        // google()
        jcenter()
    }
}

// Specified to graddle to ignore the other flavors of RNN provided.
// *** Needs to be updated as more variants become available. ***
subprojects { subproject ->
    afterEvaluate {
        if ((subproject.plugins.hasPlugin('android') || subproject.plugins.hasPlugin('android-library'))) {
            android {
                variantFilter { variant ->
                    def names = variant.flavors*.name
                    if (names.contains("reactNative51") || names.contains("reactNative56")) {
                        setIgnore(true)
                    }
                }
            }
        }
    }
}

subprojects {
    project.configurations.all {
        resolutionStrategy.eachDependency { details ->
            if (details.requested.group == 'com.android.support' && !details.requested.name.contains('multidex') ) {
                details.useVersion "27.1.1"
            }
        }
    }
    afterEvaluate {
        android {
            compileSdkVersion 27
            buildToolsVersion "27.0.3"
            defaultConfig {
                targetSdkVersion 27
            }
        }
    }
}

Any more advice on this?

If it’s set correctly, and you’re current, it’s going to work: https://github.com/react-native-community/react-native-device-info/blob/master/android/build.gradle#L19

Ah and the example app is using RN v60 with AndroidX?

Not yet - I haven’t updated it. RN0.60 came out just this morning and I merged 2 PRs instead

But you can run ‘refresh-example.sh’ in the repo and try it - the entire example is actually constructed dynamically - https://github.com/react-native-community/react-native-device-info/blob/master/refresh-example.sh

@mikehardy, After running the scripts you recommended and then building our project in Android Studio, all of our Sync's have been stuck at Evaluate Settings for roughly an hour.  Is this what you meant when you said it was 'Network Intensive'?

Hmm deoends on speed I think? And how many npm packages and how big I think? I have a small 4mbit connection in Ecuador and it's usually just 10 to 20 minutes to get a new machine set up even with pod download if they already have xcode and android studio downloaded. So that seems odd

It's been a long day...

It has been a long day...

 Hopefully it all eventually worked out for you and I guess if anything this will server as a good indicator of which libraries to use or avoid from a maintenance perspective and we can all limp along jetifying until then. Cheers


Hello when i try to compile i get this error is it possible to disable OpenCL?

home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_opencl.cpp:33:21: fatal error: CL/cl.hpp: Datei oder Verzeichnis nicht gefunden
compilation terminated.
iai_kinect2/kinect2_registration/CMakeFiles/kinect2_registration.dir/build.make:100: recipe for target 'iai_kinect2/kinect2_registration/CMakeFiles/kinect2_registration.dir/src/depth_registration_opencl.cpp.o' failed
make[2]: *** [iai_kinect2/kinect2_registration/CMakeFiles/kinect2_registration.dir/src/depth_registration_opencl.cpp.o] Error 1
In file included from /usr/include/eigen3/Eigen/Core:276:0,
from /usr/include/eigen3/Eigen/Geometry:4,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_cpu.h:22,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_cpu.cpp:18:
/usr/include/eigen3/Eigen/src/Core/Functors.h:973:28: warning: ‘template class std::binder2nd’ is deprecated [-Wdeprecated-declarations]
struct functor_traits<std::binder2nd >
^
In file included from /usr/include/c++/5/bits/stl_function.h:1128:0,
from /usr/include/c++/5/string:48,
from /usr/include/c++/5/bits/locale_classes.h:40,
from /usr/include/c++/5/bits/ios_base.h:41,
from /usr/include/c++/5/ios:42,
from /usr/include/c++/5/istream:38,
from /usr/include/c++/5/sstream:38,
from /usr/include/c++/5/complex:45,
from /usr/include/eigen3/Eigen/Core:28,
from /usr/include/eigen3/Eigen/Geometry:4,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_cpu.h:22,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_cpu.cpp:18:
/usr/include/c++/5/backward/binders.h:143:11: note: declared here
class binder2nd
^
In file included from /usr/include/eigen3/Eigen/Core:276:0,
from /usr/include/eigen3/Eigen/Geometry:4,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_cpu.h:22,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_cpu.cpp:18:
/usr/include/eigen3/Eigen/src/Core/Functors.h:977:28: warning: ‘template class std::binder1st’ is deprecated [-Wdeprecated-declarations]
struct functor_traits<std::binder1st >
^
In file included from /usr/include/c++/5/bits/stl_function.h:1128:0,
from /usr/include/c++/5/string:48,
from /usr/include/c++/5/bits/locale_classes.h:40,
from /usr/include/c++/5/bits/ios_base.h:41,
from /usr/include/c++/5/ios:42,
from /usr/include/c++/5/istream:38,
from /usr/include/c++/5/sstream:38,
from /usr/include/c++/5/complex:45,
from /usr/include/eigen3/Eigen/Core:28,
from /usr/include/eigen3/Eigen/Geometry:4,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_cpu.h:22,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_cpu.cpp:18:
/usr/include/c++/5/backward/binders.h:108:11: note: declared here
class binder1st
^
In file included from /usr/include/eigen3/Eigen/Core:276:0,
from /usr/include/eigen3/Eigen/Geometry:4,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_cpu.h:22,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/kinect2_registration.cpp:22:
/usr/include/eigen3/Eigen/src/Core/Functors.h:973:28: warning: ‘template class std::binder2nd’ is deprecated [-Wdeprecated-declarations]
struct functor_traits<std::binder2nd >
^
In file included from /usr/include/c++/5/bits/stl_function.h:1128:0,
from /usr/include/c++/5/string:48,
from /usr/include/c++/5/random:40,
from /usr/include/c++/5/bits/stl_algo.h:66,
from /usr/include/c++/5/algorithm:62,
from /usr/local/include/opencv2/core/core.hpp:56,
from /usr/local/include/opencv2/opencv.hpp:47,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/include/kinect2_registration/kinect2_registration.h:24,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/kinect2_registration.cpp:18:
/usr/include/c++/5/backward/binders.h:143:11: note: declared here
class binder2nd
^
In file included from /usr/include/eigen3/Eigen/Core:276:0,
from /usr/include/eigen3/Eigen/Geometry:4,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/depth_registration_cpu.h:22,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/kinect2_registration.cpp:22:
/usr/include/eigen3/Eigen/src/Core/Functors.h:977:28: warning: ‘template class std::binder1st’ is deprecated [-Wdeprecated-declarations]
struct functor_traits<std::binder1st >
^
In file included from /usr/include/c++/5/bits/stl_function.h:1128:0,
from /usr/include/c++/5/string:48,
from /usr/include/c++/5/random:40,
from /usr/include/c++/5/bits/stl_algo.h:66,
from /usr/include/c++/5/algorithm:62,
from /usr/local/include/opencv2/core/core.hpp:56,
from /usr/local/include/opencv2/opencv.hpp:47,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/include/kinect2_registration/kinect2_registration.h:24,
from /home/linaro/cat/src/iai_kinect2/kinect2_registration/src/kinect2_registration.cpp:18:
/usr/include/c++/5/backward/binders.h:108:11: note: declared here
class binder1st
^
CMakeFiles/Makefile2:398: recipe for target 'iai_kinect2/kinect2_registration/CMakeFiles/kinect2_registration.dir/all' failed
make[1]: *** [iai_kinect2/kinect2_registration/CMakeFiles/kinect2_registration.dir/all] Error 2
Makefile:126: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j4 -l4" failed

It is disabled if OpenCL is not installed, but you can disable it manually. But I would recommend trying to solve your OpenCL problems instead.


Setting UI can get into broken state for Icon Theme change

Initial state

After running Preferences: Icon Theme, select a new theme, and reload:

Plain text editor:

Additionally:

Try to uninstall Nord theme while it's active
Continue to change the Color Theme and Icon Theme using the Setting UI for a few times
Run a "Reload"

VS Code can get into a broken state showing a "null box" on upper left area.

There are at least two bugs here

Open settings editor, reload window. The theme and icon select boxes are empty and throw when you click them. Not sure why this is a regression, but we are not adjusting correctly when the themes are loaded.
Edit a setting then immediately open a select box. We rerender the list and sometimes render a different setting with the template containing the open select box. This is a problem because now the open select box has an invalid state and throws when you hover an item. This is a regression apparently because the new tree is more likely to use a different template when rerendering.

Open settings editor, reload window. The theme and icon select boxes are empty and throw when you click them. Not sure why this is a regression, but we are not adjusting correctly when the themes are loaded.

Fixed with this issue

Edit a setting then immediately open a select box. We rerender the list and sometimes render a different setting with the template containing the open select box. This is a problem because now the open select box has an invalid state and throws when you hover an item. This is a regression apparently because the new tree is more likely to use a different template when rerendering.

Fixed in #69297


Server will accept any websocket connection on the correct port

The server should refuse connections that do not connect with a name specified in the url parameters.

Server will now refuse connections without name parameter.


AttributeError: 'NuScenes3DOPC' object has no attribute 'loader'

When I ran the tpvformer_lidarseg_dim128_r50_800_3DOPC.py, the following bug happened.
File "/media/re/2384a6b4-4dae-400d-ad72-9b7044491b55/openmmlab/occ/OpenOcc/train.py", line 111, in main
label_str = train_dataset_loader.dataset.loader.nuScenes_label_name
AttributeError: 'NuScenes3DOPC' object has no attribute 'loader'
It seems that train_datasetloader.dataset doesn't have the attribute 'loader'.
What's wrong with that?


Throw exception when timestamp is invalid

If the timestamp is invalid, now the error is not detected because it succeeds silently.
In this pull request, I throw an exception when the timestamp response is invalid.

Thanks


SkyMed

Rescue flights centred around GapExtras airstrips

missions are time sensitive with expiry
type 1 simple aid to single patient - trivial
type 2 provide aid as in type 1 but the patient needs to be evacuated to close medical facilities
Type 3 major event 10 - 20 need to be rescued and evacuated from several locations, Could require the use of multiple air and ground vessels to accomplish

SkyMed flight 1 mission written and tested.  Will expand to flight 2 and 3 and introduction mission


spelling of pre-nasalized consonants in bipa

@cormacanderson asks (and this question is justified), why we spell prenasalization exclusively with the superscript "n", such as in [ⁿp], where we could also write [ᵐp]. My reason for this is simplicity: Superscript n indicates a pre-nasalization which will usually have the same place of articulation as the following stop. Spelling this out would require us to pay closest attention to the superscripts available, AND we will anyway run into trouble if it comes to things that require a diacritic element for the "n"-part (prenasalized voiced dental plosive).
But we should make sure that different spellings are captured by aliases. And here, I'd radically suggest to
1 define all nasal superscript elements in preceding position as an alias of superscript "n" in our diacritics.tsv
2 add a couple of normal combinations (like mp, mb, etc.) to be also rendered as alias of the super-script n case, as people OFTEN spell the sounds in this way

I will handle this by now as follows: as long as we are only talking about the feature "prenasalized", which we can regularly handle in our system, I don't want multiple values to be used, as it is inconsistent, if I have superscript "ŋ", superscript "n", and superscript "n", but then I may be too lazy to use superscript "palatal-n", etc. If people think a prenasalization can have a different manner than the base sound (what we find in the data at times), they could user "mt" or whatever construct. But in fact, in most cases it is already an error in the data or due to typing of the data, as we saw in case of fricatives, where we have sounds like k+superscript-x which would be identical with the affricate "kx", but probably stem from the NAPA tradition of spelling and are mixed as "IPA" in Pbase or Phoible. This means in short, I'll define all superscript n-sound preceding the base sound as an alias.


Add AVS3, VVC and EVC related descriptors

Related issue (if any):

Affected components:

Brief description of the proposed changes:

Hi @paulhiggs
Thanks a lot for the update with the new standards 👍
In the new source files, please put your name in the copyright lines instead of mine. You are the author, I am not. You own the copyright for these files.
You may also add your name at the end of the CONTRIBUTORS.txt file.

You also need to update the tables XML model file in src/libtsduck/config.
The model file is used to validate input XML files. This is the way an invalid table or descriptor is detected ahead of the XML deserialization methods of the various classes. The principles of XML model files is explained in section 2.6.3 of the user's guide.
I agree that the XML model file is huge and not immediately detectable for implementors of new tables and descriptors. I plan to make it modular in the source tree so that each table or descriptor will have its .xml file along with its .h and .cpp.

finding a way to develop the model from the source would be useful and less prone to oversight.

Definitely. Ideally, I used to have a dream about a tool which could describe the binary using some formal representation (XML or other) and then automatically generate the XML model and the manipulation code (or allow dynamically handling of general structures from the formal description at run-time).
However, such a tool would be a project in itself. If I had anticipated the amount of work for tables and descriptors 15 years ago, I would have started with such a tool. And when you realize that the tool would have been useful, it is too late, the amount of remaining work for the new descriptors or tables is much lower than developing the tool.
Would you have a real-world stream with all these new descriptors? I mean a stream which was generated by another tool, not TSDuck. I would add the stream (or at least the TS packets containing the tables) in the non-regression test suite?
Please let me know when you're done with the commits so that I can start the merge.

I'm done with all the commits I need for now as part of the DVB Next Generation Video Codecs activity. Sorry there was so many, but the Ubuntu and macos builds throw errors that are not present on my local Win64 system.

Hi @paulhiggs
I am reviewing the code, fixing a few XML glitches and adding tests in the test suite.
I do not have recent versions for the standard, they are not freely available. Could provide the syntax table for EVC_video_descriptor? There is some inconsistency I need to fix.

@paulhiggs

Could provide the syntax table for EVC_video_descriptor?

And also VVC_video_descriptor please.

EVC_video_descriptor is table 2-140 in H.222.0 which is freely available (ISO/IEC 13818-1 8th edition which has the same information is not free).
VVC_video_descriptor is table 2-133 in same document.
from ISO/IEC 13818-1 8th edition...

Thanks @paulhiggs

EVC_video_descriptor is table 2-140 in H.222.0 which is freely available (ISO/IEC 13818-1 8th edition which has the same information is not free).

It must be in the 2021 edition, which is not free, even in the H.222.0 version. The H.222.0 (06/21) page says "This text was produced through a joint activity with ISO and IEC. According to the agreement with our partners, this document is only available through payment. Please get in touch with<EMAIL_ADDRESS>for more information."
This is quite logical and, to my experience, it has always been like that: the latest edition of H.222.0 is not freely available. I hate this ISO policy, it prevents open source developers from having access to the most up-to-date standards.

Hi @paulhiggs
I have some questions about the AVS3_video_descriptor.

What is the document "T/AI 109-6" you mention in the source code? Is this a Chinese AVS document or a DVB document?
The descriptor tag is 0xD1. In DVB signalisation, this is in the private descriptor range but no private data specifier is defined. Is this descriptor valid in a DVB stream? Or is this an extension for AVS countries (ie. China)?
How is AVS3 integrated in DVB streams?

Since you added AVS in the list of standards in tsStandards.h, I will assume that this is not DVB compliant and I will add an option --avs (just like --atsc or --isdb) in relevant tools and plugins to force the interpretation of AVS-specific signalisation. Do you agree?

@lelegard

What is the document "T/AI 109-6" you mention in the source code? Is this a Chinese AVS document or a DVB document?
There are two principal documents associated with AVS3, both are developed by the AVS Working Group of China (note that AVS3 has now been included in the DVB Bluebook A001 a.k.a. "the codec toolbox")
The AVS3 video coding specification (T/AI 109.2) and the AVS3 systems specification (T/AI 109.6 where the AVS3_video_descriptor is defined) are both freely available from here.

The descriptor tag is 0xD1. In DVB signalisation, this is in the private descriptor range but no private data specifier is defined. Is this descriptor valid in a DVB stream? Or is this an extension for AVS countries (ie. China)?
Indeed, there is no formal way of registering  for values in the user private descriptor range and we do not find a registrar or registry for the private descriptor range of ITU-T H.222.0 / ISO/IEC 13818-1 we just had to take a value which we determined was not available. We did ask ATSC to record our use in the ATSC Code Point Registry, but they declined.

In regard to the using the extended stream id, we consulted with SMPTE, the authors of Direc and other codecs but all indicated a 'free for all' in grabbing tag vales. In the end we followed the previous approach used by VC-1 (another non-MPEG codec) in an MPEG-2 transport stream and 'obtained' a value that was not identified in the MediaInfo code for the extended stream id.

How is AVS3 integrated in DVB streams?
According to clause 4 of DVB Bluebook A001.

Since you added AVS in the list of standards in tsStandards.h, I will assume that this is not DVB compliant and I will add an option --avs (just like --atsc or --isdb) in relevant tools and plugins to force the interpretation of AVS-specific signalisation. Do you agree?
I'm not sure what 'DVB compliant' means in tsduck. The new DVB codec toolbox includes AVS3 alongside VVC (H.266) and HEVC. Going forward, a perfectly valid DVB transport stream (or DVB-DASH streaming service) will include AVS3 coded media and related signalling.

I'm not sure what 'DVB compliant' means in tsduck.

This is not specifically TSDuck, this is DVB. In DVB, descriptor tags 0x80 to 0xFF are "private", they cannot be used by DVB. They are typically used by countries or operators. Private descriptors must be preceded by a private_data_specifier_descriptor containing the private_data_specifier of the country or operator defining this private descriptor.
This means that it is forbidden to use 0xD1 as descriptor tag in a DVB transport stream, unless you are a private entity with a DVB-registered private_data_specifier  and you precede your 0xD1 descriptor with a private_data_specifier_descriptor containing your private_data_specifier.
This is DVB. SMPTE is a different standard body, they are not DVB. If they let you use 0xD1 (and even register it in SMPTE), your TS will be SMPTE-compliant, but not DVB-compliant.
We had a similar issue with AC-3. ATSC (which is not DVB either) decided to use 0x81 for an AC3 descriptor. For the same reasons, this value is invalid in DVB. Consequently, DVB defined another form of AC3 descriptor with tag 0x6A, officially registered in EN 300 468 (and a different structure).
So, if you describe your AVS3 elementary stream with a 0xD1 descriptor in SMPTE transport streams, you cannot do that in DVB transport stream. You need to apply for a specific descriptor at ETSI. Since the range 0x40-0x7F is already saturated, you will get an "extended descriptor", meaning that you will have to define a slightly different structure.
And you will necessary end up with the same situation as AC3: two different AVS3 descriptors for SMPTE and DVB, with different tags and slightly different structures.

OK, thanks. I will raise the use of private_data_specifier with DVB and AVS. It should not be a problem to get the necessary identifiers.

From: Thierry Lelegard @.>
Sent: Thursday, October 6, 2022 5:51:25 PM
To: tsduck/tsduck @.>
Cc: Paul Higgs @.>; Mention @.>
Subject: Re: [tsduck/tsduck] Add AVS3, VVC and EVC related descriptors (PR #1063)
I'm not sure what 'DVB compliant' means in tsduck.
This is not specifically TSDuck, this is DVB. In DVB, descriptor tags 0x80 to 0xFF are "private", they cannot be used by DVB. They are typically used by countries or operators. Private descriptors must be preceded by a private_data_specifier_descriptor containing the private_data_specifier of the country or operator defining this private descriptor.
This means that it is forbidden to use 0xD1 as descriptor tag in a DVB transport stream, unless you are a private entity with a DVB-registered private_data_specifier and you precede your 0xD1 descriptor with a private_data_specifier_descriptor containing your private_data_specifier.
This is DVB. SMPTE is a different standard body, they are not DVB. If they let you use 0xD1 (and even register it in SMPTE), your TS will be SMPTE-compliant, but not DVB-compliant.
We had a similar issue with AC-3. ATSC (which is not DVB either) decided to use 0x81 for an AC3 descriptor. For the same reasons, this value is invalid in DVB. Consequently, DVB defined another form of AC3 descriptor with tag 0x6A, officially registered in EN 300 468 (and a different structure).
So, if you describe your AVS3 elementary stream with a 0xD1 descriptor in SMPTE transport streams, you cannot do that in DVB transport stream. You need to apply for a specific descriptor at ETSI. Since the range 0x40-0x7F is already saturated, you will get an "extended descriptor", meaning that you will have to define a slightly different structure.
And you will necessary end up with the same situation as AC3: two different AVS3 descriptors for SMPTE and DVB, with different tags and slightly different structures.
—
Reply to this email directly, view it on GitHubhttps://github.com/tsduck/tsduck/pull/1063#issuecomment-1270403226, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAYDGF6ZLRGHQIP2MN25QETWB37Q3ANCNFSM6AAAAAAQ33I7OM.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @paulhiggs
I have integrated your code. The PR is not automatically marked as merged by GitHub because I skipped the last 3 commits which were integrations and reverts of the bug fix in c46290484cdf45fa4ae0d4509b3c732c137276b1. They were not needed since merging with the master branch brings that commit back. So, you may close the PR if you like and reopen one or an issue when a DVB AVS3 descriptor is defined.
I have added test-115 in the test-suite for your 8 new descriptors. This kind of test is predefined: just create an XML file with several examples of the new tables or descriptors. No matter the semantics, this is just a way to test the syntax, all possible conversions follow between XML, JSON, binary section, TS packets in both directions. The first time, it helps to find bugs (I fixed a few in these descriptors). Then, all intermediate results are kept in the test suite to track potential direct or induced regression in the future.
I also removed a few extra fields in the XML. For instance, when a binary structure contains a field to indicate the number of following subprofile IDC, this is useful in binary (how many bytes to decode) but useless in XML (just count the XML substructures). As a general method, when looking at a new binary descriptor, we need to classify semantic fields and syntactic fields apart. Only the semantic fields need to be transposed in XML. The XML format carries its own syntax.
Thanks again for this very useful contribution. Since you seem deeply involved with the integration of new codecs, we are lucky to have your direct contribution. If TSDuck can help in the prototyping and testing of these new codecs, I will consider this as an achievement.

It is likely we still need 07146c0 since the VVC Timing and HRD descriptor uses the same logic (negative flag for 90kHz) as HEVC and I 'copied' the HEVC code to get things started.

Ooops !!! My bad.
Because of the similarities between the two descriptors, I did not pay enough attention and incorrectly assumed it was the HEVC descriptor patch being integrated twice, back and forth. I merge this one right away.


Need to update package to fix transformers dependency conflict

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
transformers 4.40.1 requires tokenizers<0.20,>=0.19, but you have tokenizers 0.15.2 which is incompatible.
Successfully installed coloredlogs-15.0.1 fastembed-0.2.6 flatbuffers-24.3.25 huggingface-hub-0.20.3 humanfriendly-10.0 loguru-0.7.2 mpmath-1.3.0 onnx-1.16.0 onnxruntime-1.17.3 protobuf-5.26.1 pyreadline3-3.4.1 sympy-1.12 tokenizers-0.15.2 win32-setctime-1.1.0

available as of fastembed==0.2.7


Pass withQueries parameter when using yii\db\Query::create for query building

Fix for #18066
Added passing of withQueries parameter from source query to target query, when copying query using Query::create.
Added tests for Query::create method.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues
#18066

Thanks!


Laplacian via HyperDuals

Moving the discussion from Zulip to an issue ... I wonder whether our explicit forward-mode implementation would be complete overkill and simply ensuring that all our codes are compatible with Dual and HyperDual numbers (ForwardDiff.jl, DualNumbers.jl, HyperDualNumbers.jl) will be easier and possibly even more efficient.

First example:
using ForwardDiff, LinearAlgebra, HyperDualNumbers

F(xx) = sum( (xx[i] - xx[j])^2 / (1 + xx[k]^2)
            for i in 1:length(xx)
               for j in i+1:length(xx)
                  for k = 1:length(xx)
            )

function laplacian(F, xx::AbstractVector{T}) where {T}
   # assume output type of F is also T
   Δ = zero(T)
   for i = 1:length(xx)
      hxx = [ Hyper(xx[j], j==i, j==i, 0) for j = 1:length(xx) ]
      Δ += F(hxx).epsilon12
   end
   return Δ
end

N = 5
xx = randn(N)

L1 = laplacian(F, xx)
L2 = tr(ForwardDiff.hessian(F, xx))

@show L1 - L2

Here is an example of a second derivative of a chain
using Polynomials4ML, HyperDualNumbers, Lux, LuxCore, Random
P4ML = Polynomials4ML
rng = Random.default_rng()

##

Pn = legendre_basis(10)
l_Pn = P4ML.lux(Pn)

l_embed = BranchLayer(;Pn = l_Pn,)

bA = P4ML.PooledSparseProduct([ (n,) for n = 1:length(Pn) ])
l_bA = P4ML.lux(bA)

ch1 = Chain(embed = l_embed, A = l_bA)

##

xx = 2*rand(5) .- 1

ps, st = Lux.setup(rng, ch1)
o, _ = ch1(xx, ps, st)

P = Pn(xx)
A = bA( (P,) )

##

hxx = [ Hyper(xx[i], i==1, i==1, 0) for i = 1:length(xx) ]
hA1 = bA( (Pn(hxx),) )

hA2, _ = ch1(hxx, ps, st)
hA1 == hA2

##

using BenchmarkTools

@btime $bA( ($Pn( $xx ),) )     # 160.236 ns
@btime $ch1( $xx, $ps, $st )    # 171.607 ns
@btime $bA( ($Pn( $hxx ),) )     #  262.451 ns
@btime $ch1( $hxx, $ps, $st )     #  270.026 ns

Another thought is that if we really had a bottleneck for some layer then we could overload an entire kernel for Hyper inputs.

A very simple example showing that one can take hyperduals as arguments into a Zygote gradient:
using Zygote

function f(xx, p)
   aa = Zygote.Buffer(xx, length(xx)^2)
   idx = 0
   for i = 1:length(xx)
      for j = 1:length(xx)
         idx += 1
         aa[idx] = (xx[i] - xx[j])^2
      end
   end

   return dot(copy(aa), p)
end

xx = 2*rand(5) .- 1
hxx = [ Hyper(xx[i], i==1, i==1, 0) for i = 1:length(xx) ]

W = randn(length(xx)^2)
f(xx, W)

gp = xx -> Zygote.gradient(p -> f(xx, p), W)[1]

gp(xx)
gp(hxx)

I believe this is now more or less settled and will come with #39


Optimize the /list fetching code to not round-trip to UUID.

Changes proposed in this PR

Don't round-trip jobs to UUID's then back to job entities in the /list path. Get the entities and populate them.

Why are we making these changes?

We think it'll be a modest performance increase; should avoid an extra random IO per job in the result set.

This PR partially addresses issue #617.

This PR addresses #617. the additional refactors to not have /jobs endpoint use the list-jobs function addresses part of #617.

@dposada  Is there a unit test /jobs/#UUID that exeercises this codepath for https://github.com/twosigma/Cook/pull/848/files#diff-6611b39b65ff49438a4d940b51c85cc0R2549 ?
I didn't find one in a search, nor on your commit d236ec3b36c7538b79b11a6bf2fdbeefb38e17ee  #756
I'd like to validate that this works correctly.

@scrosby Do we want to keep this PR open?

@scrosby Can we close this PR?


Account memo display is truncated

Description
The account memo displayed is truncated and not showing the full 100 characters.

Steps to reproduce
See screenshot
Additional context
No response
Hedera network
other
Version
v0.13.2 - alpha.1
Operating system
None

we should also fix this in the history view

The account memos are no longer truncated.


set default zoom of AudioPlus

Is your feature request related to a problem? Please describe.
When using AudioPlus, long audio files start at minimum zoom level, which is impractical for annotation. Currently, every time a task is visited, the annotator has to manually hit the zoom button to get back to a more reasonable level
Is there any way to set the default zoom level of AudioPlus? Or to go back to the previous zoom level when reopening an AudioPlus task?
Describe the solution you'd like
It would be nice to be able to set the default zoom level of the AudioPlus, e.g., through a new defaultValue attribute.
Additional context
It would similarly be nice to be able to set the default speed of the AudioPlus.

@bethard Thank you for your request, it looks very helpful to have default value for AudioPlus, I've added a ticket for our frontend team about this.


Highlighting for HTTP/2 syntax

HTTP/2 uses a completely different syntax to describe requests/responses. It is not as simple as replacing HTTP/1.1 with HTTP/2 and adding support for pseudo-headers (which is what I see as having been done from the issues). See section 8.8 of RFC9113 which is the HTTP/2 specification.
Please consider adding proper highlighting support for HTTP/2!

Please let us know what you mean by "proper support". HTTP/2 is a binary protocol, which is out of scope for Pygments.
We added some support for pseudo headers, for example, because tools like curl like to print out requests/responses in this format.

Is that format documented, or used anywhere else? I wouldn't be too keen on highlighting an ad hoc format used just in a single RFC...

This format is quite common in spec work: See, for example, RFC 8164, RFC 8030, Web Transport Spec RFC8441 etc. I am sure there are other references but these are relevant to my immediate work of writing notification protocols.  RFC 9113 does document the format in a rather terse notation (Much like modified ABNF is a rather terse form used to document HTTP/1.1 syntax in RFC9110 and RFC9112). Also, RFC 911x are kind of foundational to the web. Just Saying :)
I understand what I request is a very niche requirement and that you would certainly have many other priorities. But syntax highlighting for HTTP/2 is nonetheless a valuable addition (especially so when juxtaposed against HTTP/1.1).


Add tests for Add Capacity and Storage System List Page

/test odf-console-e2e-aws

/lgtm
/test odf-console-e2e-aws
Based on the CI screenshots, I'm wondering if we need to revisit the cy.logout method, due to its potentially flaky behavior?


OutOfMemory: Java Heap Size error during tests

From some time flank's CI has been hit with OOM error example run

 Stack trace
ftl.run.TestRunnerTest > mockedIosTestRun local FAILED
    java.lang.OutOfMemoryError: Java heap space
        at (Coroutine boundary.()
        at ftl.run.NewTestRunKt.runTests(NewTestRun.kt:47)
        at ftl.run.NewTestRunKt$newTestRun$2$1.invokeSuspend(NewTestRun.kt:27)
        at ftl.run.NewTestRunKt.cancelTestsOnTimeout(NewTestRun.kt:56)
        at ftl.run.NewTestRunKt$newTestRun$2.invokeSuspend(NewTestRun.kt:27)
        at kotlinx.coroutines.TimeoutKt.withTimeoutOrNull(Timeout.kt:101)
        at ftl.run.TestRunnerTest$mockedIosTestRun local$1.invokeSuspend(TestRunnerTest.kt:135)

        Caused by:
        java.lang.OutOfMemoryError: Java heap space
            at com.google.common.io.ByteStreams.combineBuffers(ByteStreams.java:200)
            at com.google.common.io.ByteStreams.toByteArrayInternal(ByteStreams.java:183)
            at com.google.common.io.ByteStreams.toByteArray(ByteStreams.java:221)
            at com.google.cloud.storage.contrib.nio.testing.FakeStorageRpc.create(FakeStorageRpc.java:100)
            at com.google.cloud.storage.StorageImpl$3.call(StorageImpl.java:221)
            at com.google.cloud.storage.StorageImpl$3.call(StorageImpl.java:218)
            at com.google.api.gax.retrying.DirectRetryingExecutor.submit(DirectRetryingExecutor.java:105)
            at com.google.cloud.RetryHelper.run(RetryHelper.java:76)
            at com.google.cloud.RetryHelper.runWithRetries(RetryHelper.java:50)
            at com.google.cloud.storage.StorageImpl.internalCreate(StorageImpl.java:217)
            at com.google.cloud.storage.StorageImpl.create(StorageImpl.java:171)
            at ftl.gc.GcStorage$uploadWithProgress$1.invoke(GcStorage.kt:174)
            at ftl.gc.GcStorage$uploadWithProgress$1.invoke(GcStorage.kt:34)
            at ftl.util.ProgressBarKt.runWithProgress(ProgressBar.kt:39)
            at ftl.util.ProgressBarKt.runWithProgress$default(ProgressBar.kt:34)
            at ftl.gc.GcStorage.uploadWithProgress(GcStorage.kt:172)
            at ftl.gc.GcStorage.access$uploadWithProgress(GcStorage.kt:34)
            at ftl.gc.GcStorage$upload$1.apply(GcStorage.kt:158)
            at ftl.gc.GcStorage$upload$1.apply(GcStorage.kt:34)
            at java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1737)
            at ftl.gc.GcStorage.upload$test_runner(GcStorage.kt:148)
            at ftl.gc.GcStorage.upload(GcStorage.kt:63)
            at ftl.util.FileReferenceKt.uploadIfNeeded(FileReference.kt:42)
            at ftl.util.FileReferenceKt.uploadIfNeeded(FileReference.kt:32)
            at ftl.run.platform.ios.CreateXcTestContextKt.createXcTestContexts(CreateXcTestContext.kt:17)
            at ftl.run.platform.ios.CreateIosTestContextKt.createIosTestContexts(CreateIosTestContext.kt:9)
            at ftl.run.platform.RunIosTestsKt$runIosTests$2.invokeSuspend(RunIosTests.kt:49)
            at ftl.run.platform.RunIosTestsKt$runIosTests$2.invoke(RunIosTests.kt)
            at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:91)
            at kotlinx.coroutines.CoroutineScopeKt.coroutineScope(CoroutineScope.kt:194)
            at ftl.run.platform.RunIosTestsKt.runIosTests(RunIosTests.kt:34)
            at ftl.run.NewTestRunKt.runTests(NewTestRun.kt:47)

After some digging it turned out it's due to `GcStorage` client and `FlankTestRunner`. Here are some of my thoughts and conclusions:

When FlankTestRun is initiated it uploads some artifacts needed during tests. GcStorage uses FakeStorageRpc (during test run) under the hood and one preserves all artifatcs/files/and other files as String byte[] map. https://github.com/Flank/flank/pull/1350 added two new artifacts that are uploaded and one of them is EarlGreyExample.zip which is quite heavy ~47MB.
There are a couple of tests which uploads those zip file but with different key (which expected). Yet, it leads to the point when we have few big byte[] in memory and referenced by GcStorage (so gc can not free the memory)
I checked and the default xmx for gradle test task on GH action runner is 512 MB.
In general, it is not so small number but...if we run mockedIosTestRun gcsAndHistoryName and mockedIosTestRun local we already have ~141MB of memory occupied only by those zip files, one for the FlankTestRunner and each of tests 'uploads' zip on it's own. And we need to remember there are other lots of other tests that 'uploads' files...
All above can cause OOM error being thrown (at least I think so)

Why I do not see such a problem on my local machine?
TBH -- I'm not sure, maybe GH runner has some additional restrictions for jvm? I ran some tests with increased heap memory for tests and so far I did not encounter OOM error example run
Solution?

easy win is just to increase heap size for the test task (numbers can of course change)tasks.test {
    maxHeapSize = "3072m"
    minHeapSize = "512m"
}

reimplement our test logic to clean storage after each test, we can leave files 'uploaded' by FlankTestRunner or make them uploaded on demand
???

Let me know what do you think and which option should I proceed

I will implement 1) as a temporary solution and create a follow-up issue for solution 2)


Remove duplicated sentence in docs

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes
Fixed a small docs error.
Verification
Looked at the rendered docs in my branch.

Thanks!


9.73.04 changed  HistoricalData signature

@erdewit ,
as you know new version of ibapi has an updated signature for hsitoricaldata call. I figured i'd submit a patch for it. Please let me know.

Thanks again for the patch!


Fix #20247: Support for variadic console controller action methods

Adds support for variadic console controller action methods.
public function actionMerge(string ...$names)
{
    // ...
}

php yii foo/bar/merge name1 name2 name3

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

@samdark Done

Thank you!


Add the GooseFS integration document

What is the purpose of the pull request
Resolve integration issues with GooseFS and HUDI
Brief change log
Goosefs does not support appending and needs to be marked in StorageSchemes
Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.
Committer checklist
Has a corresponding JIRA in PR title & commit
Commit message is descriptive of the change
CI is green
Necessary doc changes done or have another open PR
For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

你不应该把 goosefs_hoodie.md 放在旧版本的目录中。你可以把它放在/website/docs/，只是 Eupdatecloud.md并添加 goosefs_hoodie.md 文件。

Thank you, I have modified

@lubo212 any updates here?

@lubo212 : can you address the feedback please.


FOPTS-5124 Added batch processing for some Policies with high memory consumption

Added batch processing in AWS Object Storage Optimization, Azure Databricks Rightsize Compute Instances and Azure Reserved Instance Recommendations Policies
Description
Following the release of batch processing for all organizations, it was decided to modify the templates with the highest memory consumption to make use of batch processing. These policies are:

AWS Object Storage Optimization
Azure Databricks Rightsize Compute Instances
Azure Reserved Instance Recommendations

NOTE: For AWS Object Storage Optimization, I think there was a mistake in the parameters to run script
$js_aws_s3_objects_with_storage_class. It was using $ds_aws_list_s3_objects but I think it should use, $ds_aws_s3_objects because it is the data source that has the objects filtered by tags if we use that param, and $ds_aws_s3_objects  was not being used by any other datasource. I changed the data source used as input, but let me know if it was correct
Issues Resolved
FOPTS-5124
Link to Example Applied Policy

Contribution Check List

[x] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[x] New functionality has been documented in CHANGELOG.MD

@JesusParada One last thing - regarding this error:

cost/azure/databricks/rightsize_compute/azure_databricks_rightsize_compute.pt
Policy Template file has not yet been enabled for automated permission generation. Please help us improve coverage by [following the steps documented in tools/policy_master_permission_generation/](https://github.com/flexera-public/policy_templates/tree/master/tools/policy_master_permission_generation) to resolve this.
--

Is it possible to add the Azure Databricks Rightsize Compute policy template to the validated policy list here? - https://github.com/flexera-public/policy_templates/blob/3983e1dd7269a7e2f1811dfa997012392e940f04/tools/policy_master_permission_generation/validated_policy_templates.yaml (under the Azure section following alphabetical order)

Just one outstanding change requested, then happy to approve


docs: updating logos

What does this PR do?

Fixes #<issue_number>

Before submitting

Was this discussed/agreed via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
Did you make sure to update the documentation with your changes? (if necessary)
Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
Did you list all the breaking changes introduced by this pull request?
Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

Reviewer checklist

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

cc @borda @carmocca @justusschock @awaelchli

The texts are much smaller than before, and the subtitle "Created by Ligihtning AI" appears tiny. Is this intentional?

BTW it seems the new images have a different logos

The texts are much smaller than before, and the subtitle "Created by Lightning AI" appears tiny on the generated website. Is this intentional?

@alexlouiserose @likethecognac ^^

this is how the docs will look like: https://pytorch-lightning--18375.org.readthedocs.build/en/18375/

yes, had called out the small copy size myself ,when we first added the byline, but it was intentionally on the smaller side. fwiw it's called micro in our design system and to be used sparingly. are you inserting that updated image into the same sized div? The added byline may be making it not fit into the original space as easily. here's a mock to share what is expected

@lantiga yes, the original icon (logo) and wordmark (brand text) was actually one typeface and a different custom wordmark for "lighting", so those two aren't even the same font. Keeping the sub brands in a more easily changeable format for now to more easily update for things like lit-LLaMA > Llama , or addign spaces or changing lit-parrot > GPT, etc.

We would need to slightly adjust the size to fit what is expected as pointed out by @likethecognac. If this is not controllable here in lightning, it might need adjustment in the docs template.

I believe we need to update this CSS to set some higher max size but preserve max-width:
https://github.com/Lightning-Universe/lightning_sphinx_theme/blob/2c040181e16bcfcf98a1c3d7fcc92ecfa984c7e1/scss/shared/_navigation.scss#L34
cc: @adamjkuhn


Improve subscription and clean up of live graph

Seems to improve the ability to record on x6 slowdown after visiting test model page.

Closing in favour of different approach.


Backstage app not able to fetch a page with base URL on refresh

The backstage app with a basePath such as /backstage is able to load the page /backstage/catalog for the first time, but once refreshed it is not able to fetch/ get the page with route /backstage/catalog
Expected Behavior
It should be able to render the page with the /backstage/catalog route
Current Behavior
Currently, it crashes with a message Cannot GET /backstage/catalog
Steps to Reproduce
Follow this link to reproduce the issue
Your Environment
Using these versions
"@backstage/core-app-api": "^0.1.23",
"@backstage/core-components": "^0.6.0",
"@backstage/core-plugin-api": "^0.1.9",

Hi
Are you seeing this problem in production or just during local development?
It's currently a known problem in development where the dev server tries to load the index.html from /.
This is of course something we should fix but I just want to double check if there's an issue in production as well.

Yes, this issue is there in production as well. This is our app config ```
app:
title: ${TITLE}
baseUrl: ${HOST_URL}/${BASE_PATH}
gqlUrl: ${GRAPHQL_URL}
organization:
name: ${COMPANY_NAME}
backend:
baseUrl: ${URL}/${BACKEND_BASE_PATH}
listen:
port: 7000
csp:
connect-src: ["'self'", 'http:', 'https:']
cors:
origin: ${HOST_URL}
methods: [GET, POST, PUT, DELETE]
credentials: true
database:
client: pg
connection:
host: ${POSTGRES_HOST}
port: ${POSTGRES_PORT}
user: ${POSTGRES_USER}
password: ${POSTGRES_PASSWORD}
cache:
store: memory
integrations:
github:
- host: github.com
token:
$env: GITHUB_TOKEN
techdocs:
builder: 'local'
generators:
techdocs: 'docker'
publisher:
type: 'local'
auth:
environment: development
providers:
github:
development:
clientId: ${AUTH_GITHUB_CLIENT_ID}
clientSecret: ${AUTH_GITHUB_CLIENT_SECRET}
auth0:
development:
clientId: ${AUTH0_CLIENT_ID}
clientSecret: ${AUTH0_CLIENT_SECRET}
domain: ${AUTH0_DOMAIN}
okta:
development:
clientId: ${OKTA_CLIENT_ID}
clientSecret: ${OKTA_CLIENT_SECRET}
audience: ${OKTA_DOMAIN}
scaffolder:
github:
token:
$env: GITHUB_TOKEN
visibility: public
We are facing this issue on page refresh but for now we have handled using nginx config.
 But the UI component served by internal plugins doesn't include the base path. For ex: /search and other internal buttons

Steps to produce this error:

Serve frontend with basepath
build and deploy frontend with nginx or http-server.
route to different page forex: /basepath/catalog or any other path
Refresh the page. On refresh it will so can not get /basepath/catalog and site will crash.

Hi,
This issue seems to be resolved in the production environment. When we created a new test app and served using Nginx it seemed to work. Currently, we are migrating away from backstage/core and will update here if the issue still exists.


nixos/redis: set vm.overcommit_memory using mkDefault

Description of changes
This setting is unconditionally set to 1 in the installation device profile which prevents you from enable redis when creating a vm image with nixos-generators for example.
When evaluating a qemu vm image package generated by nixos-generators of a system that has redis enabled, I am faced with:
       error: The option `boot.kernel.sysctl."vm.overcommit_memory"' is defined multiple times while it's expected to be unique.

       Definition values:
       - In `/nix/store/1h99qq6970gkx3j0m9w4yrrl9y99y1nk-source/nixos/modules/services/databases/redis.nix': "1"
       - In `/nix/store/1h99qq6970gkx3j0m9w4yrrl9y99y1nk-source/nixos/modules/profiles/installation-device.nix': "1"
       Use `lib.mkForce value` or `lib.mkDefault value` to change the priority on any of these definitions.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

We don't want to use mkDefault here as that could silently disable the option again.
We probably want to convince https://github.com/NixOS/nixpkgs/blob/1355a0cbfeac61d785b7183c0caaec1f97361b43/nixos/modules/config/sysctl.nix#L4-L12 to treat the same values as the same.
@roberth can you help to achieve that? I am very lost how to do that.

Does this need to be a custom type instead of oneOf [ bool str int (enum [ null ]) ]?
Ideally just use that type, but otherwise try with mergeEqualOption.

Also, it looks like the conversion to string should be done in the type so that equivalent definitions are accepted despite the convenient "syntax", e.g. lib.mkMerge [ 1 "1" ] should probably be valid as either one results in "${n}=1" in the generated file.

Note that as a workaround you can set it once with mkForce "1" in your own configuration.


fix: Use the right short types for IntervalDay and IntervalYear #240

According to the documentation the short types for IntervalDay and IntervalYear are iday and iyear
https://substrait.io/extensions/#function-signature-compound-names
https://github.com/substrait-io/substrait-java/issues/240

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Arnaud Jegou seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Only log metadata retry refreshes when using a list of topics

Right now, our logs are full of "starting metadata refresh" lines due to the 10 minute background refresh interval we have in place. This makes the logs noisy.
I think we only request the metadata for all topics:

during startup
during background refresh.

I think we can live without the logs in these cases.
Not sure if this is a good idea. @Shopify/kafka, what do you think?

I don't consider one log every ten minutes to be "noisy".

Closing this.


Robot.run in for loop - issue

We ran robot.run in for loop in python code.
We provided all kind of arguments to run function e.g. output dir which changed in every loop.
When second execution happened the first defined output dir was still there.
We found out that when we fetched outpudir with following command it returned value defined in previous run.
If I remember correctly when we had three runs in loop then last one still had first one output dir value.
output_dir = BuiltIn().get_variable_value('$OUTPUT_DIR')

More details:

During execution we import python libraries for plotting like in this example.
Some of python libraries have class variables like this outputdir explained below.

This class variable is not cleared after first execution
In this class some functions are static

When we use this class/module, we do not instantiate this instantiation is not needed when all methods are static and variables are in class (outside of init). We just import this python module and access this variable.
However if we move this variable to init method and we instantiate this class when use it, then this output_dir works OK, even tho as you see the code outside of init is same like it is in init.

The class which uses this static one:

It's certainly possible some global state is left over. It would help debugging this if you could create a bit more complete example. Would also be good to know are there problems with other options other than the output dir.

Description updated. :)

This seems to work as expected. Class variables are set only once when the class is created and within the same Python execution classes aren't recreated.

To understand you comment.. no bug?
But when calling robot.run twice for example, should all classes which are created in first run still remain when exeuting robot.run second time? I would say no, those are two different executions. Now in this case the first exeution creates these classes and uses them and second execution have same classes even though execution is totally different from testing point of view.
I assumed that robot.run executions are happenning in different processes and are not related to each other. :)

One confirmation from our end:
If we execute robot in our loop using os.system then this works ok and older classes are not there after first run.

No, we cannot realistically force recreating all classes. That would be fighting against how Python works. I'm not sure would it even be possible but if it was, it would slow down the overall execution speed.
In general with Python (and all other languages I know) you should use instance attributes with values you want to be different when instances are created and class attributes only if you want them to be same all the time. If you want total independency, running each execution round as a separate process is a good idea.
Based on this discussion there's no bug in Robot or in Python. I initially thought the value of ${OUTPUT_DIR} would be same on different rounds even if it shouldn't, but the problem clearly is that it's only fetched once.

Hmm.. I still disagree or we are talking about different thing here.
Explanation in other words:
Now when we run robot.run in loop and at first it e.g. executes test1.robot.
This test1.robot file says Library pythonlibraryA where this pythonlibraryA uses other python library let's call that like libraryB which contains class variables and staticmethods.  Also this libraryB reads output_dir and saves it class variable.
Now when we run robot.run second time which e.g. executes test2.robot.
This test2.robot file says same Library pythonlibraryA where this same pythonlibraryA uses this same libraryB, but output_dir which are read in this class is having same output_dir value what's been set in first run.
I still assume these own python libraries used in tests to be re-instantiated and re-set again in next runs when using robot.run. I would not concider to let these instances be there after first execution because we are talking about two different test runs.
That's why os.system works for us because all instances are wiped out after one process ends. :)
If you still think this how it's behaves is OK then that's fine.
Maybe like you said, everything else is OK but output_dir is not set correctly even tho we set that as an arg for robot.run. :)

" Class variables are set only once when the class is created and within the same Python execution classes aren't recreated."
So you mean that when we run this from python then all classes creared by robot.run remains as long as we are in this python library? Then it would make sense.. on other hand then setting output_dir is the issue.. we reset that in all robor.run executions..

This is how classes work in Python. You have two easy ways to avoid the problem.

Yes, somehow I missed this one and I was only concentrating into those test executions and keeping those as a separate. Thanks for help! :)


Updated devise engine routes and initializer to embed devise_for

Related to #976. Small change to update how the embedded devise engine handles the devise_for route. Rationale for this change is explained here:
https://github.com/plataformatec/devise/wiki/How-to:-use-devise-inside-a-mountable-engine
Devise 2.0 was warning on app startup regarding the currently way devise_for is declared from outside the engine within the application's route configs. I attempted to run the spec quite before submitting this, but got so many failures I wasn't able to suss out if my changes really broke anything. Let me know if there's anything more you'd like me to do in that regard.
A nice side-effect of this change is that I was able to take the devise_for declaration entirely out of my app's routes config, which should mean that all of the fuffing about that rails_admin does in its generators to update the devise_for routes in the app can be removed. I'm not intimately familiar with everything rails_admin does in that regard, otherwise I'd just clean that code up myself as part of this pull request. If anyone wants to spell out for me which files (generators, dummy-app, specs, etc) need to be updated, I'd be happy to amend the pull request. Otherwise, I will leave that as an exercise to someone better acquainted with rails_admin.
Cheers!

Hi @dparis,
Thanks for the time you took to sort that out.
I am not sure this is a good idea to bind RailsAdmin to Devise further on.
Today, RailsAdmin can work with any Authentication library, Devise is installed as a safe and convenient default.
Devise installation should be an option, actually. Or even removed, to remove the burden of the integration. Now that it is mature enough, I think RA should go toward lighter and modular integration.
What is your opinion?

The warning has disappeared. I guess it was related to some engine tested in the specs.

Ah, good deal that it went away, I'll give a quick test to confirm on my app and kill my fork if I can confirm with my setup.
I tend prefer a modular approach for features that are fairly well covered by external gems. So long as the integration is simple (a config file entry, or a separate gem that can just be included in the gemfile, etc) and can be changed for an existing installation without too much trouble, I'd be fine with decoupling the Devise integration.


Added fizzbuzz for Lua

Looks great! Thanks for contributing, I am going ahead with the merge. If possible, (I don't know lua),  could you add a way for the user to input how far to go on for FizzBuzz instead of setting it static at 100? Also, I would greatly appreciate it if you could star this repo as it helps us get more contributors. Thanks in advance!


Revert "Revert "IWCD update geom""

Reverts WCSim/WCSim#364
The CI is finally working, so lets revert the revert, to restore the #355 PR

Ok so despite everything being red, I'm happy to accept it

You've fixed the stuck track warnings "Optical photon is killed because of missing refractive index". I'm very grateful for this!

There is a small increase in "GeomNav1002" warnings in the SK geometry. For example here but up to 10% more (~30) of those warnings for a reduction of 10,000s of the others is a small price to pay

There are geometry overlap warnings in the old nuPRISM geometry. Which is fine, because that is superceeded.
Whilst there are differences in number of tracks/hits/digits

The blacksheet skin being added fixes the optical photon warnings, so must also effect the number of photons(->hits->digits)
These are mostly at the ~1% level, traditionally what we use to say things are consistent
Things are more different with the "ODbarrelIn" particle guns for the 20" & mPMTs seen here. But we know that these weren't perfect before (difference in hit rate when starting at +x or +y) and despite the means changing, the assymettries are actually slightly reduced. So another win.

Thank you very much @kmtsui. Sorry again for the delay
I'll tag to produce a new set of references today, using the new IWCD geometries


[typo] Update hit-the-rollup.md

typo
Proposed changes
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

LGTM.
Thanks your contributions ❤😃.

I find there already is a PR about docs/typo.  I prefer to close this PR and put it into another PR #8538

I find there already is a PR about docs/typo. I prefer to close this PR and put it into another PR #8538

ok

I find there already is a PR about docs/typo. I prefer to close this PR and put it into another PR #8538
close it


Build native extensions on M1

We already support disabling this compilation flag anyway, so might as well just do it automatically for architectures that don't support it.

Hello, just a friendly poke.
Based on https://github.com/sass/sassc-ruby/graphs/contributors perhaps @bolandrm or @eregon could help?

Friendly ping here. 👋

Maybe @glebm or @Edward could help?

Upon further investigation, this issue only exists in versions prior to v2.3.0. It's not clear which commit fixes it, but this does address this error:
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    current directory: /Users/brian.buchalter/.gem/ruby/2.7.4/gems/sassc-2.2.1/ext
/Users/brian.buchalter/.rubies/ruby-2.7.4/bin/ruby -I /Users/brian.buchalter/.rubies/ruby-2.7.4/lib/ruby/2.7.0 -r ./siteconf20210720-81997-w05u9w.rb extconf.rb
creating Makefile

current directory: /Users/brian.buchalter/.gem/ruby/2.7.4/gems/sassc-2.2.1/ext
make "DESTDIR=" clean

current directory: /Users/brian.buchalter/.gem/ruby/2.7.4/gems/sassc-2.2.1/ext
make "DESTDIR="
compiling ./libsass/src/units.cpp
clang: error: the clang compiler does not support '-march=native'
make: *** [units.o] Error 1

make failed, exit code 2

Gem files will remain installed in /Users/brian.buchalter/.gem/ruby/2.7.4/gems/sassc-2.2.1 for inspection.
Results logged to /Users/brian.buchalter/.gem/ruby/2.7.4/extensions/arm64-darwin-20/2.7.0-static/sassc-2.2.1/gem_make.out

An error occurred while installing sassc (2.2.1), and Bundler cannot continue.
Make sure that `gem install sassc -v '2.2.1'` succeeds before bundling.

Per your comment, it was probably https://github.com/sass/sassc-ruby/pull/158


Invisible timepicker on some themes

Afer a recent commit, timepicker is invisible on themes with noCalendarBorder option set to false.
Environment

Version used: commit d5bdbc57a178835bbcb4ee68b7ba3dbf941adcb0
Browser Name and version: Google Chrome 55.0.2883.87 m
Operating System and version (desktop or mobile): desktop

Yes, this is due to a dev version getting pushed to docs.
I've reverted docs to v2.2.4 until all variations of flatpickr work correctly and in all browsers.
Will keep this open and updated as I iterate on the dev version


[sdkv2] add indexer query getAccountOwnedTokensByTokenId

Description

Add getOwnedTokensByTokenData over to sdk v2
Note:

Test is not included yet, will wait until we have Token client/class to wrap up the test.
Another account token query getTokenOwnedFromCollectionNameAndCreatorAddress is not included, because it relies on getCollectionAddress query, which Oliver is working on.

Test Plan

pnpm fmt
pnpm test
pnpm lint
Related Links

Current dependencies on/for this PR:

main

PR #29   👈

This comment was auto-generated by Graphite.

we also need to add the api/internal functions...?

oops, good catch.

Didn't realize this query already been ported over with a different name? I will close this PR - https://github.com/aptos-labs/aptos-ts-sdk/blob/main/src/internal/queries/getAccountOwnedTokensByTokenData.graphql#L2-L11


[HUDI-6760] Add SelfDescribingInputFormatInterface for hive FileInput…

…Format
Change Logs
Currently, After doing schema evalution using spark-sql, query using hive will fail
-- spark-sql
set hoodie.schema.on.read.enable=true;

create table hudi_mor_test_tbl (
  id bigint,
  name string,
  ts int,
  dt string,
  hh string
) using hudi
tblproperties (
  type = 'mor',
  primaryKey = 'id',
  preCombineField = 'ts'
)
partitioned by (dt, hh);

insert into hudi_mor_test_tbl values (1, 'a1', 1001, '2021-12-09', '10');

ALTER TABLE hudi_mor_test_tbl ALTER COLUMN ts TYPE bigint;

-- hive
select * from hudi_mor_test_tbl_rt;

Failed with exception java.io.IOException:java.lang.ClassCastException: org.apache.hadoop.io.LongWritable cannot be cast to org.apache.hadoop.io.IntWritable

The root cause is that FileInputFormat does not implement SelfDescribingInputFormatInterface, see
/**
 * Marker interface to indicate a given input format is self-describing and
 * can perform schema evolution itself.
 */
public interface SelfDescribingInputFormatInterface {

}

Impact
After doing schema evalution using spark-sql, query using hive will success
Risk level (write none, low medium or high below)
none
Documentation Update
none
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@Zouxxyy Can you elaborate a little more what the purpose of this change? Does it has risk of breaking the compatibility for low version Hive?

@danny0405

Can you elaborate a little more what the purpose of this change?

See updated Change Logs.

Does it has risk of breaking the compatibility for low version Hive?

This interface (SelfDescribingInputFormatInterface ) has existed since hive 2.0, and there is no compatibility problem

Can someone help to understand why hudi-spark-common cannot automatically depend on hive-exec in hudi-hadoop-mr ?
 mvn dependency:tree -pl hudi-spark-datasource/hudi-spark-common -Dspark2

[INFO] --- maven-dependency-plugin:3.1.1:tree (default-cli) @ hudi-spark-common_2.12 ---
[INFO] org.apache.hudi:hudi-spark-common_2.12:jar:0.15.0-SNAPSHOT
[INFO] +- org.apache.hudi:hudi-hive-sync:jar:0.15.0-SNAPSHOT:compile
[INFO] |  +- org.apache.hudi:hudi-hadoop-mr:jar:0.15.0-SNAPSHOT:compile
[INFO] |  +- org.apache.hudi:hudi-sync-common:jar:0.15.0-SNAPSHOT:compile

here is the error in integration-tests,  don't know much about the env of integration testing, can anyone help~
2023-09-08T05:11:59.7764700Z Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.hive.ql.io.SelfDescribingInputFormatInterface
2023-09-08T05:11:59.7764906Z 	at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
2023-09-08T05:11:59.7765092Z 	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
2023-09-08T05:11:59.7765284Z 	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
2023-09-08T05:11:59.7765373Z 	... 58 more
2023-09-08T05:11:59.7765560Z 23/09/08 05:11:59 INFO util.ShutdownHookManager: Shutdown hook called
2023-09-08T05:11:59.7766126Z 23/09/08 05:11:59 INFO util.ShutdownHookManager: Deleting directory /tmp/spark-b81218a3-32e6-4851-9b25-b15373acd05b
2023-09-08T05:11:59.7766507Z 23/09/08 05:11:59 INFO util.ShutdownHookManager: Deleting directory /tmp/spark-9b58a267-201d-4404-baeb-49e617b23ad1
2023-09-08T05:11:59.7766647Z
2023-09-08T05:11:59.7766919Z Sep 08, 2023 5:11:59 AM org.glassfish.jersey.internal.Errors logErrors
2023-09-08T05:11:59.7767534Z WARNING: The following warnings have been detected: WARNING: Cannot create new registration for component type class com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider: Existing previous registration found for the type.
2023-09-08T05:11:59.7767548Z
2023-09-08T05:11:59.7768090Z [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 96.75 s <<< FAILURE! - in org.apache.hudi.integ.command.ITTestHoodieSyncCommand

You can take a look at the readme: https://github.com/apache/hudi/tree/master/hudi-integ-test

@Zouxxyy you need to run the exact same commands as shown in the logs in the docker environment to debug the failed integration.  It looks like the HiveSyncTool spark job fails due to class not found.  Likely the new class, SelfDescribingInputFormatInterface, is not included in the bundle.
Also wondering, how does SelfDescribingInputFormatInterface automatically fix the schema evolution (I don't see any API implemented)?

@xushiyan @bvaradar Can someone help to understand why hudi-spark-common cannot automatically depend on hive-exec in hudi-hadoop-mr ?
 mvn dependency:tree -pl hudi-spark-datasource/hudi-spark-common -Dspark2

[INFO] --- maven-dependency-plugin:3.1.1:tree (default-cli) @ hudi-spark-common_2.12 ---
[INFO] org.apache.hudi:hudi-spark-common_2.12:jar:0.15.0-SNAPSHOT
[INFO] +- org.apache.hudi:hudi-hive-sync:jar:0.15.0-SNAPSHOT:compile
[INFO] |  +- org.apache.hudi:hudi-hadoop-mr:jar:0.15.0-SNAPSHOT:compile
[INFO] |  +- org.apache.hudi:hudi-sync-common:jar:0.15.0-SNAPSHOT:compile

I think this dependency is already the case?

@yihua see https://github.com/apache/hudi/pull/7129 , it turns out that this question has already been raised
I think he had the same problem as me

The hive dependency is not passed

@Zouxxyy have you figured out why integration tests failed in the GH actions?

@Zouxxyy : Can you rebase and resolve the merge conflict ? We can take a look at the test failure after that

Fixed conflicts and rebased. Made minor changes to align with latest code.

@bvaradar Sorry for delay, thanks for your help, It seems that the CI is not stable.

Rerunning failed jobs


Fix pslite

rely on https://github.com/dmlc/ps-lite/pull/90

guess you need to update the submodule as well?


Undefined errno on Mac OS X

Compiling the training tools on OS X produces errors like:
combine_tessdata.cpp:120:9: error: use of undeclared identifier 'errno'
        errno = 0;
        ^
lstmtraining.cpp:93:69: error: use of undeclared identifier 'errno'

due to a missing include

This bug was reported by @escapist21 in a comment on #1453


Android / Xamarin Platform Support

is there any way to use with xamarin? (run on android)

Definitely not qualified for this but this  might be useful.
I personally don't think Xamarin is the right way to go with this, you might have better luck porting your code over to C++ if the challenge is not too great :)

i already made raylib-cs run on android on this repo
but i think we need a custom build of this line on raylib source

@anggape Hi, can you write a guide on how to set up raylib-cs to run on Android?

also you need to instal android workload documented here

sorry for slow response, i think i accidentally deleted the previous implementation while ago, but i reimplement it again here https://github.com/anggape/Raylib-cs/tree/android

Hi, i am trying to use raylib-cs.Android by project files and by assembly still unable to run it because of this unhandled exception

is there any step i am missing or dll that need to be include?
my current project setup is android app using net core 6 and 7 via visual studio project template.

@sdb7 if you use Raylib-cs.Native from master branch it does not include android native libraries until #186 finished, you need to manualy download Raylib-cs.Native.[SOME_VERSION].nupkg from github artifacts, use https://github.com/anggape/raylib-cs-samples if you want to try, and please give feedback since its an experimental

Decided to change Raylib-cs.Android to Examples.Android. Easier to maintain as an example rather than a package. @anggape Could use help getting it to work the same as your samples project.

Closing in favour of using #144 to track platform support instead.


Time to release this as non-beta?

This works great, let's release the current master as 3.0.

You're right, I will make a release shortly.

Just published v3.0.0.


Wrong roughness in BRDF LUT

I think the BRDF LUT in the pbribl example is calculated with the roughness value flipped. If data/shaders/glsl/pbribl/pbribl.frag is modified to set color like so:
color = vec3(brdf.r, brdf.g, 0);`

The following image is generated:

Roughness increases from left to right. Green edges should be seen on the left, not the right. Y/V in the BRDF LUT texture is roughness. data/shaders/glsl/pbribl/genbrdflut.frag does the following:
outColor = vec4(BRDF(inUV.s, 1.0-inUV.t), 0.0, 1.0);

Which is what results in the flip. Just passing inUV.t instead of 1.0-inUV.t as roughness to BRDF() makes it correct.
The following two screenshots are from running https://github.com/JoeyDeVries/LearnOpenGL/tree/master/src/6.pbr/2.2.1.ibl_specular first as is and then just rendering rg from the BRDF LUT. Roughness increases from left to right.

Thanks for spotting this and adding in screenshots for comparison. This looks wrong indeed and I wonder why I didn't notice earlier. I'll fix this with one of the next udpates.

@SaschaWillems Needs to be fixed in pbrtexture example as well. (Sorry, should have mentioned both when I filed issue.)


Bytecode Reader and Writer

A reader and writer mechanism will be needed for storing and transmitting byte code. I'm currently working on this, so I'm assigning myself to the issue.

Closing this as this has now been merged into main


Add Docker 20.10.17

https://github.com/moby/moby/releases/tag/v20.10.17
This also includes adding support for previous versions that are not yet there in https://github.com/rancher/install-docker as well as changing 20.10.sh install script to point to the latest supported version. We do want to ensure this latest version is available on the OSes listed on Rancher's Support Matrix (e.g. here is one for 2.6.5 release which is the latest available at this time: https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-5/)

Successfully completed testing docker install scripts 20.10.13-20.10.17 on following OSes.

Ubuntu 20.04
CentOS 7.9
RockyLinux 8.6

Following OSes comes with docker pre-installed.

SLES - 15 SP4
OpenSUSE Leap 15.4

On RHEL 8.6 docker version greater than 20.10.7 is not supported.

On Oracle Linux 8.6 the cluster creation is blocked by this issue.

Hence, closing this issue.


Update to 4.1.0 release of ffpyplayer

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)

Bumps the version to the last ffpyplayer release.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


JsRender for Node.jS - Server side nesting templates

I'm trying to create two jsrender template files: layout.html and contactus.html. So when user request contactus.html (which is partial view) I would like to wrap it inside layout.html...
Is this possible to accomplish with {{include tmpl=.../}} or I need to use some hacks...
This is like the first thing everybody needs to use when using JsRender on server side, and there is no any documentation about it...

Did you find the documentation?

http://www.jsviews.com/#node/filetmpls - see nested calls to file-based templates.

Also

https://github.com/BorisMoore/jsrender-node-starter/blob/master/templates/layout-movies.html#L33
https://github.com/BorisMoore/jsrender-node-starter/blob/master/templates/layout-movies.html#L38

and many others on the https://github.com/BorisMoore/jsrender-node-starter site.