permission error on proxy image

15#15: *26 open<EMAIL_ADDRESS>failed (13: Permission denied),

This is what the proxy images currently return, is it possible that they have been wrongly build? B/c those are static files in the container itself, but they have permission on the ds user and not the nginx user running the whole thing. Seems like this image wasn't tested.

Hello,
Could you specify if you are using your own rebuilt images or if you are starting pods under some other user than the one specified by default?

the official ones https://hub.docker.com/r/onlyoffice/docs-proxy (as far as i can see all three variants have that  problem)

Hello,
We have just tested it and couldn't reproduce the issue.
Could you give us a step by step scenario of how you installed the solution, any additional configurations made (if there were any), attach screenshots with the error you see and specify the browser and its version you are currently using?
This way we could be sure we don't miss anything during the testing from our side.


[ALLUXIO-1825]Pooling open ByteBufferKeyValuePartitionReader in KeyValueWorkerClientServiceHandler

https://alluxio.atlassian.net/browse/ALLUXIO-1825
my simple idea for a pool of ByteBufferKeyValuePartitionReader

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

Merged build finished. Test PASSed.

haven't think it thoroughly, Now I want to think it more!


Update enabling-editing-using-a-dialog-mass-edit-965ef5b.md

Mass edit is now also supported by CAP Node.js, but requires a feature flag configured in the service definition.
CAP Java doesn't require this feature flag, as it supported mass edit from the very beginning.

Hi @c-kobo  , thanks for your contribution . We appreciate it and will look into this.

The Enabling Editing Using a Dialog (Mass Edit) topic is updated with the suggested changes


[DEV, TEST] Sentry error appears in consle.log

As a DevOps Engineer,
I want to adjust the Content Security Policy settings in the Traefik configuration within our Docker compose file,
so that Sentry can properly report errors without being blocked by the CSP.
Summary:

Identify the incorrect CSP setting for the Sentry service in the dev, test, and staging environments.
Update the Traefik configuration in the Docker compose file to include the correct scripts locations for Sentry.
Ensure that the CSP settings allow Sentry to function correctly without compromising security.

This change enables Sentry to accurately report errors and issues, improving our ability to monitor and debug the application in development, testing, and staging phases.
Acceptance Criteria

[ ] The CSP setting in the Traefik configuration allows Sentry scripts to execute in the dev, test, and staging environments without being blocked.
[ ] The updated CSP settings do not allow any scripts from unauthorized sources to execute, maintaining the security of the web application.
[ ] Error reporting and logging through Sentry are verified to work correctly in all specified environments after the CSP adjustments.

@MSzalowski Is this still an issue?

Not blocked anymore


DatePicker requires date selection to be done twice to select

Describe the bug
When you select a date, the whole calendar container moves to the side a few pixels and you need to reselect the date. Only then the wanted date is actually selected.
Expected behavior
A single click to select the correct date.
Additional context
The behavior of moving a few pixels is happening in all 4 date pickers. These are distributed in a flex column container, being each picker input inside a flex row with its label.
The component is set as:
    <DatePicker
      selected={dueDate}
      onChange={setDueDate}
      dateFormat="MMM dd, yyyy"
      placeholderText="Select the End Date"
      minDate={new Date(startDate) || new Date()}
    />

https://user-images.githubusercontent.com/29472480/112237405-5f8fc880-8c21-11eb-9bfa-b9cc589695cb.mov
What could be causing the container to dance around and the date to not be registered? The click event is happening.
Update: it looks like I was able to solve it, I had a different input style affecting this one, in my case removing the padding on focus fixed it. The padding-left was causing the issue as the calendar container is positioned related to the text alignment in the input.
  input {
    width: 240px;
    text-align: center;
    text-transform: none;
    &:focus {
      padding-left: 0;
    }
  }

I had a similar issue when the datepicker appears above the input element. I was able to fix by passing fixedHeight as a prop to the datepicker.


[BUILD] Inconsitencies with ABI versions?

Environment
Operating System: Gentoo Linux 2.9
Version / Commit SHA: OpenVDB 10.0.1
CMake Version: 3.25.1
Compiler: gcc 11.3.1
Describe the problem
On Gentoo Linux, users can choose to build OpenVDB with a certain ABI compatibility, which is provided through the OPENVDB_USE_DEPRECATED_ABI_{7..9} cmake variables. While packaging for OpenVDB 10.0.1 I checked whether the use of ABI 7 is still supported and found some code, which looks like it's showing some inconsistency with this.
In https://github.com/AcademySoftwareFoundation/openvdb/blob/v10.0.1/cmake/config/OpenVDBVersions.cmake#L21 the minimum ABI is declared as ABI 8. However, in https://github.com/AcademySoftwareFoundation/openvdb/blob/v10.0.1/CMakeLists.txt#L138-L140 ABI 7 is still declared as being supported as a deprecated ABI and ABI 9 seems to be missing as a deprecated ABI (maybe it isn't deprecated yet).
When configuring for ABI 7, I get a cmake configuration error, which seems to honor the declaration of the minimum version from OpenVDBVersions.cmake:
cmake -C /var/tmp/portage-ondisk/portage/media-gfx/openvdb-10.0.1/work/openvdb-10.0.1_build/gentoo_common_config.cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_INSTALL_DOCDIR=share/doc/openvdb-10.0.1/ -DOPENVDB_ABI_VERSION_NUMBER=7 -DOPENVDB_BUILD_DOCS=no -DOPENVDB_BUILD_UNITTESTS=no -DOPENVDB_BUILD_VDB_LOD=no -DOPENVDB_BUILD_VDB_RENDER=no -DOPENVDB_BUILD_VDB_VIEW=no -DOPENVDB_CORE_SHARED=ON -DOPENVDB_CORE_STATIC=no -DOPENVDB_ENABLE_RPATH=OFF -DUSE_AX=no -DUSE_BLOSC=no -DUSE_CCACHE=OFF -DUSE_COLORED_OUTPUT=ON -DUSE_EXR=no -DUSE_IMATH_HALF=ON -DUSE_LOG4CPLUS=ON -DUSE_NANOVDB=no -DUSE_PKGCONFIG=ON -DUSE_PNG=no -DUSE_STATIC_DEPENDENCIES=no -DUSE_TBB=no -DUSE_ZLIB=no -DOPENVDB_USE_DEPRECATED_ABI_7=ON -DOPENVDB_SIMD=AVX -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_TOOLCHAIN_FILE=/var/tmp/portage-ondisk/portage/media-gfx/openvdb-10.0.1/work/openvdb-10.0.1_build/gentoo_toolchain.cmake /var/tmp/portage-ondisk/portage/media-gfx/openvdb-10.0.1/work/openvdb-10.0.1
loading initial cache file /var/tmp/portage-ondisk/portage/media-gfx/openvdb-10.0.1/work/openvdb-10.0.1_build/gentoo_common_config.cmake
-- The CXX compiler identification is GNU 11.3.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/sbin/x86_64-pc-linux-gnu-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Enabling colored compiler output
-- CMake Build Type: RelWithDebInfo
-- Found PkgConfig: /usr/sbin/x86_64-pc-linux-gnu-pkg-config (found version "1.8.0")
-- Configuring for OpenVDB Version 10.0.1
CMake Error at CMakeLists.txt:485 (message):
  OpenVDB ABI versions earlier than 8 are no longer supported.

-- Configuring incomplete, errors occurred!
See also "/var/tmp/portage-ondisk/portage/media-gfx/openvdb-10.0.1/work/openvdb-10.0.1_build/CMakeFiles/CMakeOutput.log".

From the output it became clear, that I can't support ABI 7 any longer in the package, yet the question stays, if the root CMakeLists.txt is correct with it's reference to ABI 7 and it's missing reference to ABI 9?

Hi @waebbl - We support the previous two ABI versions from the current major version e.g. VDB 10.X supports building with ABIs 8, 9 and 10. The OPENVDB_USE_DEPRECATED_ABI_7 CMake variable should have been removed in the bump to 10.X and won't do anything (as you've experienced, the v10.X builds will explicitly fail). The OPENVDB_USE_DEPRECATED_ABI_9 variable will work as expected but isn't documented in the root CMakeLists.txt. Sorry for the confusion, I'll update the variables accordingly

Hi @Idclip, thanks for clarifiying support of the last two ABI versions. I wasn't aware of this.
I'll keep the issue open as a reminder for a PR to close it.


Support for functions with any return type

Fixes #270
Thanks to @solnic and @flash-gordon for the indications to implement this one.
At the end, we decided to go with select { f(:count, :id).as(:count), concat(:first_name, :last_name).as(:full_name) } for brevety

I wonder if naming it function and aliasing it to f would be a better idea? While I love the brevity of f it's not immediately apparent what it does and I know my first thought when trying to use a function would be to call well function. So it hurts discover-ability a bit.

@abrthel @solnic I did change it to be call functionand aliased to f

@solnic @flash-gordon any update on this one?


Backend chart.js and orders

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

Project coverage is 97.50%. Comparing base (8436743) to head (97e8678).

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #84      +/-   ##
==========================================
+ Coverage   97.46%   97.50%   +0.04%
==========================================
  Files          65       65
  Lines        1617     1605      -12
  Branches      158      158
==========================================
- Hits         1576     1565      -11
+ Misses         40       39       -1
  Partials        1        1

Flag
Coverage Δ

frontend-customer
99.58% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines
Coverage Δ

backend/src/app.module.ts
94.11% <ø> (+5.22%)
:arrow_up:

backend/src/bookings/bookings.controller.ts
97.22% <ø> (-0.08%)
:arrow_down:

backend/src/bookings/bookings.module.ts
100.00% <ø> (ø)

backend/src/bookings/bookings.service.ts
100.00% <ø> (ø)

backend/src/orders/orders.module.ts
100.00% <ø> (ø)

backend/src/orders/orders.service.ts
100.00% <ø> (ø)

----
🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


Xamarin.iOS Build Task mix features from V1 and V2 on documentation

Required Information

Type: Bug
Task Name: XamariniOSV2

Environment

Server - Azure Pipelines - general issue, not specific to account/build
Agent - Hosted macOS

Issue Description
The documentation provided for Xamarin.iOS Build Task (V2) doesn't match the actual options of this build task. Worse yet is the fact that it lacks important features from the previous versions.
So I ask if the documentation is updated to provide accurate information or the task is updated to include the missing features that previously allowed signing an IPA from a file certificate/provisioning profile.

@ravero thanks for reporting this.  We made the documentation consistent for V2 (the changes should be live within a few days) and added a small sample for signing and provisioning a Xamarin.iOS app.  This small sample uses YAML.  Is that what you're using?  Can you please let us know if you hit any more obstacles?
Sign and provision a Xamarin.iOS app
To sign and provision a Xamarin.iOS app, set packageApp to true and specify a signing identity and provisioning profile ID:
- task: XamariniOS@2
    inputs:
      solutionFile: '**/*iOS.csproj'
      configuration: 'AppStore'
      packageApp: true
      signingIdentity: 'iPhone Developer: Chris Sidi (7RZ3N927YF)'
      signingProvisioningProfileID: 'iOS Team Provisioning Profile: com.hashtagchris.*'

See Sign your mobile app during CI for more information about signing and provisioning your app.

Thanks David, I could check that the documentation is updated. But it still lacks some concrete examples like the one you posted here, which may leave a beginner really confused.
I suggest adding examples to the documentation of all tasks, because YAML is support is pretty new, and it gets confusing for people like me who's migrating from the old visual editor. Is there a way we can contribute with this documentation to enrich it?

Hi @ravero.  I too have been anxious for us to provide better examples using YAML.  I'm sorry for the confusion in the meantime.  The Azure Pipelines documentation is here (see Xamarin.md) and any contributions are much appreciated!

Hi @davidstaheli,
Please let me know how can I contribute with the docs. I have plenty of examples that I've been building on our pipelines.
Best regards.


Issues with default template

Hi,
first of all, thanks for your work. I like it a lot.
However I have some questions and suggestions regarding the starter default to make it even better.
Travis CI config
The travis config is very specific and doesn't contribute any value to the starter template. If somebody needs to set up a CI specific config it's likely they can and will add their own.
package.json

gh-pages
The package file has a dependency on gh-pages which is not necessary to understand the example template. In my opinion it would be much better to add a section in the documentation to explain how one can deploy to gh-pages than to add something which is not part of the "core" example.

prettier
The dependency is missing and it refers to wrong and missing paths.

React dependencies are not declared
I guess they are installed as peer dependencies of Gatsby. This would force me to disable import/no-extraneous-dependencies so my lint does not fail. Imo that's not a good solution. Is there a reason for that?

gitignore
It looks like the .gitignore is based on you personal config. I suggest to remove everything which is not related to the example to keep it as clean as possible.
Missing Eslint config
All code should follow some guidelines. It would be great if a basic eslint config could be added (maybe pull in https://github.com/yannickcr/eslint-plugin-react).
typography.css
The name is misleading. The file actually contains reset and typography related styles. This could actually be moved into a base component with a base css.
Code style

The examples use mainly React.Components where in most cases stateless functional components would be the preferred choice. For instance html.js could be rewritten this way

const getCSS = () => {
  if (process.env.NODE_ENV === 'production') {
    return (
      <style
        dangerouslySetInnerHTML={{
          __html: require('!raw!../public/styles.css'),
        }}
      />
    );
  }
  return undefined;
};

const HTML = ({
  body,
  headComponents,
  postBodyComponents,
}) => (
  <html lang="en">
    <head>
      <meta charSet="utf-8" />
      <meta httpEquiv="X-UA-Compatible" content="IE=edge" />
      <meta
        name="viewport"
        content="width=device-width, initial-scale=1.0"
      />
      {headComponents}
      {getCSS()}
    </head>
    <body>
      <div
        id="___gatsby"
        dangerouslySetInnerHTML={{ __html: body }}
      />
      {postBodyComponents}
    </body>
  </html>
);

Mix of tagged template literals and  single / double quotes. There is no reason for tagged template literals so I'd remove them. Also it would be nice to unify the quotes. For instance in the index.js
Class properties are used throughout the project to set propTypes. However they still are experimental and therefore I suggest to use the default way to declare PropTypes instead.

I understand that this is a lot of nitpicking. However I would love to see a lot of people adopting high quality and consistent code.
Btw. if you agree we could create a list and I will make dedicated PRs for all the issues.

These are fantastic suggestions. 100% agree the default starter should be
as perfect as possible. Could you out together a PR with these changes?
On eslint, I'd really like to copy what create-react-app does here.
On Wed, Jul 12, 2017, 7:27 AM Savio van Hoi<EMAIL_ADDRESS>wrote:

Hi,
first of all, thanks for your work. I like it a lot.
However I have some questions and suggestions regarding the starter
default to make it even better.
Travis CI config
The travis config is very specific and doesn't contribute any value to the
starter template. If somebody needs to set up a CI specific config it's
likely they can and will add their own.
package.json
-gh-pages
The package file has a dependency on gh-pages which is not necessary to
understand the example template. In my opinion it would be much better to
add a section in the documentation to explain how one can deploy to
gh-pages than to add something which is not part of the "core" example.

prettier
The dependency is missing and it refers to wrong and missing paths.

gitignore
It looks like the .gitignore is based on you personal config. I suggest to
remove everything which is not related to the example to keep it as clean
as possible.
Missing Eslint config
All code should follow some guidelines. It would be great if a basic
eslint config could be added (maybe pull in
https://github.com/yannickcr/eslint-plugin-react).
typography.css
The name is misleading. The file actually contains reset and typography
related styles. This could actually be moved into a base component with a
base css.
Code style

The examples use mainly React.Components where in most cases
stateless functional components would be the preferred choice.
Mix of tagged template literals and single / double quotes. There is
no reason for tagged template literals so I'd remove them. Also it would be
nice to unify the quotes. For instance in the index.js

I understand that this is a lot of nitpicking. However I would love to see
a lot of people adopting high quality and consistent code.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gatsbyjs/gatsby-starter-default/issues/29, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEVhztxXcN_NNOGwm3pqNFNRZzFZ2_Qks5sNNfegaJpZM4OVth7
.

Thanks for your feedback @KyleAMathews!
I will work on it, but first I need some clarification on this one:
"React dependencies are not declared" < Should we set no-extraneous-dependencies to false? The default create-react-app eslint will complain about that. A better approach (in the future) might be to explicitly declare react dependencies in the package.json.

I'd rather not declare react as a dependency by default. You certainly can if you know what you're doing but part of the point of Gatsby is you can use it without really knowing what you're doing.

@KyleAMathews I created a PR. However there seems to be an issue with the build. Let's continue in the PR.


Account Id not consistent with change.

The account Id was recently set to uint64 in some parts of the code with the alias of Id while in the account class its int.

https://github.com/santegoeds/oanda/commit/8319e971dcd01843895f919f885d0d73c51ddc4d#diff-d0b7f86cea13f90d3cc0cc2338da8d5fR53
this was the change and you can see in the accoutn class its still int.

Thank you for reporting this.  I'll try to get this fixed by Monday.

Fixed by PR #10

thanks mate :)


fix return types of Literal logical operators

Currently operator &&, || and ! of Literal return another Literal containing the result of applying
the respective operator to the effective boolean value of the arguments.
This is inefficient as it requires calls to the node storage and registry to actually do anything useful with the returned
values. Operator chaining is especially expensive as each intermediate value requires a call to the node storage and registry.
Proposed fix:

implement #57

class Literal {
    ...
    - Literal logical_and(Literal const &other, NodeStorage &node_storage = NodeStorage::default_instance()) const;
    - Literal operator&&(Literal const &other) const;

    - Literal logical_or(Literal const &other, NodeStorage &node_storage = NodeStorage::default_instance()) const;
    - Literal operator||(Literal const &other) const;

    - Literal logical_not(NodeStorage &node_storage = NodeStorage::default_instance()) const;
    - Literal operator!() const;

    + TriBool logical_and(Literal const &other) const;
    + TriBool operator&&(Literal const &other) const;

    + TriBool logical_or(Literal const &other) const;
    + TriBool operator||(Literal const &other) const;

    + TriBool logical_not() const;
    + TriBool operator!() const;
   ...
};

Note: The proposed solution does not break operator chaining, see: https://godbolt.org/z/GY3x7s51K

closing because #85 allows the same thing with less implicit conversions and with more obvious behaviour


[SPARK-47657][SQL] Implement collation filter push down support per file source

What changes were proposed in this pull request?

Previously in #45262 we completely disabled filter pushdown for any expression referencing non utf8 binary collated columns. However, we should make this more fine-grained so that individual data sources can decide to support pushing down these filters if they can.
Why are the changes needed?

To enable collation filter push down for an individual data source.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

With previously added unit test.
Was this patch authored or co-authored using generative AI tooling?

No.

@cloud-fan can we merge this?

thanks, merging to master!


test: fix build against djangotip

Django recently enabled the cached template loader by default in development. This was added in https://github.com/django/django/pull/15586 (commit https://github.com/django/django/commit/bf7c51a5f4da5f00b46923545ea6657ba9556bf6).
As a result, some tests started failing when the whole test suite was run, but not when they were run individually.
We can fix this by setting the template loaders in our test settings.

Thanks! :)

I've released v2.0.3 with this.


SCM/Explorer: Cannot get contextmenu popup with keyboard (Shift-F10)

Keyboard command: contextmenu stopped working in both SCM and Explorer trees.
The menu pops up correctly with the mouse right click.
Version: 1.32.0-insider (user setup)
Commit: 003521e715f2dbcf4f98be99a923097505859954
Date: 2019-02-15T06:16:29.903Z
Electron: 3.1.3
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17134

I can repro. This is tree specific, leaving up to @joaomoreno

@joaomoreno
Just observed, probably obvious also, problem output tree exhibits the same behavior further indicating it's probably a base tree event issue.

Broken by https://github.com/Microsoft/vscode/commit/e50ef11ff189afa60ced0bfab7156d843f3881ba

This was an insanely hard bug to fix. Good catch.


Support inscription number lookup at the top level: ordinals.com/N

It's time to bend the knee 🧎♂

we've already done this with ordinals.com/inscription/N.
Or do you mean the search bar?

I mean without the /inscription/ prefix, so you can go to https://ordinals.com/N, like on ord.io

Done!


postgresql::server::config_entry - dependency cycles detected (after upgrade to 10.0.0)

Describe the Bug
After upgrade from 9.2.0 to 10.0.0 or 10.0.1 puppet fails with dependency cycle error:
Error: Found 1 dependency cycle: (Anchor[postgresql::server::service::begin::main] => Postgresql_psql[Set template1 encoding to UTF8] => Postgresql::Server::Instance::Late_initdb[main] => Postgresql::Server::Instance::Initdb[main] => Class[Postgresql::Server::Initdb] => Postgresql_conf[wal_level] => Class[Postgresql::Server::Service] => Postgresql::Server::Instance::Service[main] => Anchor[postgresql::server::service::begin::main])\nCycle graph written to /opt/puppetlabs/puppet/cache/state/graphs/cycles.dot. Error: Failed to apply catalog: One or more resource dependency cycles detected in graph
Expected Behavior
Update the config entry to postgresql.conf
Steps to Reproduce
Steps to reproduce the behavior:
For example change the wal_level
postgresql::server::config_entry { 'wal_level':
value   => 'archive',
}
Apply puppet and it fails.
Environment

Version [Puppet 7]
Platform [Ubuntu 20.04]
Postgresql-14
puppetlab-postgresql (since 10.0.0)

Hi,
thanks for the Ticket, we're able to reproduce it in https://github.com/puppetlabs/puppetlabs-postgresql/pull/1547

Any updates on this? We're experiencing the same issue after upgrading the module and had to revert to 9.2.0

@ShadNex this should be fixed in https://github.com/puppetlabs/puppetlabs-postgresql/pull/1564 . Can you try that branch and comment in the PR please?


Lint setup fix

Test fix.
Description
Changes to GitHub actions to fix linting bug. Is this good @adamltyson ? should we handle this differently now that we have the .github repo?

Yeah I think it makes more sense to use the actions scripts in brainglobe/actions. I think all that's needed is for tox.ini, .pre-commit-config.yaml and .github/workflows/test_and_deploy.yml to be copied from e.g. imio to this repo.
@brainglobe/ucl-rsdg is there a good way to automate this? We've centalised a lot of the setup, but there are still lots of files in each repo that could get out of date.

But is it centralised? ie for imio, does it happens that if something is changing in brainglobe/.github it is automatically changed also in imio/.github?

I don't think there's an easy way to share the test/pre-commit configuration files above across repositories unfortunately.

I don't think there's an easy way to share the test/pre-commit configuration files above across repositories unfortunately.

isn't there a way to have a part of a repo that is itself a repo?

Yeah I think it makes more sense to use the actions scripts in brainglobe/actions. I think all that's needed is for tox.ini, .pre-commit-config.yaml and .github/workflows/test_and_deploy.yml to be copied from e.g. imio to this repo.
@brainglobe/ucl-rsdg is there a good way to automate this? We've centalised a lot of the setup, but there are still lots of files in each repo that could get out of date.

There I don't understand the redundancy between the test matrix defined in the workflows .yml and the tox.ini. What of the tox.ini is used where?

There I don't understand the redundancy between the test matrix defined in the workflows .yml and the tox.ini. What of the tox.ini is used where?

That I don’t know, @dstansby?

Do you mean this section: https://github.com/brainglobe/imio/blob/3dac57ee27c8b7f9d0eef2e546319c36597c1e7e/tox.ini#L4-L8 ? It's a hangover from the template tox.ini that napari provide for plugins, and isn't neccessary because tox will automatically select an environment depending on which python version is available, which is set in the github actions config.

Regarding pre-commit I don't think you can share across repos partly because you might have a different configuration across repos. For example, in this one we're using prettier whereas usually we're just using python related ones like this. However, seeing as python stuff would be unrelated to prettier type ones, it wouldn't matter if we used the same pre-commit everywhere. The limitation being that pre-commit doesn't work that way

Ok, this is now fixed, @adamltyson what do you think?
I removed the mypy check, we are not used type hinting at all in this repo, not familiar with it yet and I feel that it makes mypy not so useful here.
@paddyroddy ok, I see! But then this does not standardise much things across repos right? I think that at least for linting we should probably have common tests, and maybe just keep out the (few) repos that won't nee python-related tests?
I feel that it is somehow counterintuitive to have common actions to run tests but then to determine their behavior locally in every repo...(also related to the tox.ini file @dstansby was mentioning)

Looks fine to me @vigji!

I feel that it is somehow counterintuitive to have common actions to run tests but then to determine their behavior locally in every repo...(also related to the tox.ini file @dstansby was mentioning)

I agree. If we can't standardise everything with brainglobe/actions, I think we should maybe still have some standard-ish yml files we can keep up to date and copy/paste from. At the moment we're just copying from whatever we think the "best" repo is currently.

Ok, this is now fixed, @adamltyson what do you think? I removed the mypy check, we are not used type hinting at all in this repo, not familiar with it yet and I feel that it makes mypy not so useful here.

I disagree on your mypy comment. Just because this repo doesn't have much typing now does not mean it won't in the future. Easier to introduce early rather than a very well established repo. Can catch mistakes which will save you time later down the line.

Ok, this is now fixed, @adamltyson what do you think? I removed the mypy check, we are not used type hinting at all in this repo, not familiar with it yet and I feel that it makes mypy not so useful here.

I disagree on your mypy comment. Just because this repo doesn't have much typing now does not mean it won't in the future. Easier to introduce early rather than a very well established repo. Can catch mistakes which will save you time later down the line.

Ok, happy to learn here! Can I ask your help to fix the mypy error that I am getting there? On a python 3.9 (where I am testing this and where tests are running) I get complaints about missing setups in request. The recommendation seems to be to pip install types-requests but it does not fix it in my case, do you know what is happening?

Fixed in #123


non-flash version with link on the right

Split view expanded

Edit view collapsed

Content:
"Copy and send this draft link to anyone. *'Ctrl + c' (Win), 'Cmd + c' (OSX)."

Functionality to include:

URL is automatically highlighted on click of the 'share draft' button.
In the event that the user no longer has the URL highlighted:
Clicking the input highlights entire URL

@flashbackzoo If you can make it so the copying shortcuts only appear for their relative operating systems, that would be great if not too much effort?


DEV |Space feed page - Frontend

Description
html page has been created for the space feed page.

You need to resolve conflicts before merging it to the dev. If you don't know how to do it I can help you with that.

You need to resolve conflicts before merging it to the dev. If you don't know how to do it I can help you with that.

hi Ceyda, it would be great, generally the system gives this error.

Hey, could you first watch this: https://www.youtube.com/watch?v=mOJazBNrG-c
The most important part is to decide which version should be the current one.
For the next branch you are creating make sure that I is created from devand once in a while do git merge origin/dev to make sure your branch is up to date. If you have questions after the video we can go over it tomorrow at the class time.


Refactored out huge method from facade to visitor

Hello again,
I'm submitting a PR to refactor the gigantic getTypeConcrete method in the JavaParserFacade by using the visitors from JavaParser so that each expression now is split nicely into it's own method.
As a side benefit of the refactoring my IDE now also highlighted some lines which were invalid. In fact lines 493-507 in the original JavaParserFacade are illegal since the original condition is that node instanceof MethodReferenceExpr. I've removed them and the tests still pass, but @ftomassetti if you can have a look and add them back if needed in a proper way would be helpful.

Definitely a good idea to split this giant method! Thanks a lot for the contributions.
I hope to close a big refactoring on JavaParser and be soon back to JavaSymbolSolver to do a release including your contributions. Thanks!


fix: Object examples not properly displayed as placeholders

Description
Stringifying object examples
Task Item
closes #3951
Screenshots

Coverage increased (+0.004%) to 55.504% when pulling 516e06f628ab0ef40f3034f8d763dd50736f6883 on leugene/issue3951 into 673f961ac3c6765b6598624215c909699188e2f8 on main.

There are some build errors now @LouisEugeneMSFT


Minor fixes

fixed overflow issue on challenge 2

whats going on here?

Yea that's what I was wondering

Why does it say your trying to merge into DavidMatthewFraser:minor-fixes instead of DavidMatthewFraser:master

think its because i named the branch minor-fixes can we delete this branch il just make a new one


Pebblo Docs - Add different reports examples in Config tab

Add different reports in config to show difference between xhtml2pdf and weasyprint report:

These changes look good to me. @rutujaac Do we want to add anything in the reports section as well?

These changes look good to me. @rutujaac Do we want to add anything in the reports section as well?

I think we're good with the changes made. Let's keep the reports section as is for now.


Content Component returns this error :TypeError: undefined is not an object (evaluating 'route.routeName')  in beta 22 but works in beat21

this is the github repo link: https://github.com/kakulgupta/CustomDrawer
it works weel in beat 21 but at beta22 it throws error TypeError: undefined is not an object (evaluating 'route.routeName')
maybe package broken
advance thankyou for your valuable reply

Duplicate #2718


get no alerts when setting multi values to query_key

I use the frequency rule to do the monitoring.  This is my configuration.
type: frequency
num_events: 1
timeframe:
  minutes: 5
filter:
  - query:
      range:
        query_time:
             gte: 0.5
use_terms_query: true
query_key:
    - beat.hostname
    - port

When elastalert was up, No alert was send. I tried to debug, I found the aggs part of query to ES was:
    "aggs": {
        "counts": {
            "terms": {
                "field": "beat.hostname,port",
                "size": 50
            }
        }
    }

As far as I know, "field": "beat.hostname,port" is not supported by ES, So the buckets returned are null.
Do I make any mistake?

my mistake, use_terms_query: true should not be used

The issue is when using >1 query_key + use_terms_query together. I should put a check in the code to prevent this!


AppImage error

The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_electrBtLtxs/chrome-sandbox is owned by root and has mode 4755.
追踪与中断点陷阱

this looks like a solution
https://github.com/electron/electron/issues/17972#issuecomment-486927073

别人的AppImage怎么没问题？
https://github.com/xtuJSer/CoCoMusic/releases


[WIP] Cypress tests for FormContextWithValidation

Hi @iusehooks,
I am still working but here is my first PR for https://github.com/iusehooks/usetheform/issues/24. Please let me know if anything has to be changed

Hi, It looks good so far.
We should add into .gitignore  a new path for excluding cypress/videos
Well done.
Thanks

Hi @iusehooks,
I have added all the tests. Please let me know if any changes have to be made


NMS not working!

Thanks for publishing your code.
I have a question about the post-processing part here.
It seems that nms is not working. choosing circle or rotate nms would give around 498 3D boxes.
Is it a bug or am I missing something?
I also noticed that the model scores are quite high ~0.5.
Thanks,
Youshaa

Hi!
Have you set the right hyper parameter like https://github.com/Megvii-BaseDetection/BEVStereo/blob/master/exps/bev_stereo_lss_r50_256x704_128x128_24e_2key.py#L183 ?
And if you get the detection score right, it should be right.

I using the same thresholds. But, still getting ~500 boxes.

Hi @yinchimaoliang, I am using these parameters:
test_cfg = dict(
    post_center_limit_range=[-61.2, -61.2, -10.0, 61.2, 61.2, 10.0],
    max_pool_nms=False,
    thresh_scale=[0.7, 0.9, 0.8, 0.8, 0.8, 0.9],
    score_threshold=0.7,
    out_size_factor=4,
    voxel_size=[0.2, 0.2, 8],
    nms_type='circle',
    pre_max_size=1000,
    post_max_size=30,
)

post_max_size was set to 83 which leads to get (83 * num_tasks) boxes = 498.
even after reducing the number, I am getting 30 * 6 random boxes during inference.
I am using this config
Could you please guide me to get normal results ?

Hi! @YoushaaMurhij If you use the ckpt I provided and inference it without changing the exp, can you get the right result?

Thanks for your reply!
I figured out what the problem was.
Pytorch lighting was not loading the exp weights and instead the pretrained ones are loaded.
I loaded the weight using Pytorch and got reasonable results.
Can you please tell me in which coordinates system the results are predicted?
Thanks

Hi! In our model, only ego coordinate system is used, when applying evaluation, the results are transformed to global coordinate system.

I got it. Thanks for your response. Closing this issue!


Snippet to detect device type

Description

Added new snippet

Lodash[ACTION] #100 -> https://lodash.com/docs/4.17.4#(method)
What does your PR belong to?

[ ] Website
[x] Snippets
[ ] General / Things regarding the repository (like CI Integration)

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (non-breaking improvement of a snippet)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have checked that the changes are working properly
[x] I have checked that there isn't any PR doing the same
[x] I have read the CONTRIBUTING document.

@Chalarangelo @fejes713 Thank you so much! it's my privilege to contribute to this project :smile:


Fix typo, frmo -> from

Overview
Fix typo found via codespell -S deps,_build.
What problem is being solved by this branch?
Changes
Fix typo.
Tests
Collaborators

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


[BUG] Unable to redeploy a model once undeployed on Windows

What is the bug?
ML Commons: We have been seeing a bug on deploy/undeploy model due to Windows holding folder access while OpenSearch process is running.

This is only a Windows isolated issue.
It will prevent cleanup during undeploy and re-deployment on the same id.
The folder will be released only when you stop the opensearch cluster.

How can one reproduce the bug?
Steps to reproduce the behavior:
1) Register a model version
POST /_plugins/_ml/models/_register
{
  "name": "huggingface/sentence-transformers/all-MiniLM-L12-v2",
  "version": "1.0.1",
  "model_format": "TORCH_SCRIPT"
}

## Response
{
  "task_id": "FFe1cIkBT5fLQDwZTj7J",
  "status": "CREATED"
}

2) Get model_id using the task_id above:
GET /_plugins/_ml/tasks/<task_id>
3) Deploy using the model_id
POST /_plugins/_ml/models/<model_id>/_deploy
4) Undeploy it successfully
POST /_plugins/_ml/models/<model_id>/_undeploy
5) Redeploy the same model using the same model ID. The model fails to get deployed
POST /_plugins/_ml/models/<model_id>/_deploy
What is the expected behavior?
When a user undeploy a model and tries to re-deploy the same model, it should get deployed successfully.
What is your host/environment?

OS: Windows

Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.

Windows system has some issue deleting a file if any process holds the file handle. From this stackoverflow,

Give it a try with Windows 10, May 2019 Update (19H1) or later: Microsoft changed the DeleteFile() API default semantics to POSIX style and your problem should be solved by that

Our integ test runs on a version before this patch Windows 10, May 2019 Update (19H1)
When user undeploy a model, we can see model files deleted from local cache folder. But the cache folder still there.
The impact scope is just the current model, user can't redeploy a model. The work around is user can create a new model and deploy, or stop the OS process and delete the model cache folder manually. The model file itself will be deleted from cache folder, just can't delete the empty cache folder.


sumneko_lua is deprecated, use lua_ls instead. See :h deprecated

Started getting this error in Neovim 0.8.3, changing to lua_ls gives another error saying lua_ls is not known:
sumneko_lua is deprecated, use lua_ls instead. See :h deprecated
This function will be removed in lspconfig version 0.2.0
stack traceback:
        .../.local/share/nvim/lazy/nvim-lspconfig/lua/lspconfig.lua:41: in function '__index'
        ...al/share/nvim/lazy/lsp-setup.nvim/lua/lsp-setup/init.lua:67: in function <...al/share/nvim/lazy/lsp-setup.nvim/lua/lsp-setup/init.lua:61>
        [C]: in function 'pcall'
        ...m/lazy/mason-lspconfig.nvim/lua/mason-lspconfig/init.lua:59: in function 'fn'
        ...l/share/nvim/lazy/mason.nvim/lua/mason-core/optional.lua:91: in function 'if_present'
        ...m/lazy/mason-lspconfig.nvim/lua/mason-lspconfig/init.lua:57: in function 'fn'
        .../nvim/lazy/mason.nvim/lua/mason-core/functional/list.lua:98: in function 'each'
        ...m/lazy/mason-lspconfig.nvim/lua/mason-lspconfig/init.lua:67: in function 'setup_handlers'
        ...al/share/nvim/lazy/lsp-setup.nvim/lua/lsp-setup/init.lua:60: in function 'setup'
        /Users/pedro/.config/nvim/lua/plugins/lsp-setup.lua:168: in function 'config'
        ...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:318: in function <...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:316>
        [C]: in function 'xpcall'
        .../.local/share/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:110: in function 'try'
        ...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:333: in function 'config'
        ...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:301: in function '_load'
        ...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:179: in function 'load'
        ...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:33: in function <...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:26>

This seems to have been solved by an update to the plugins, closing.


a few improvements for the cli commands.

I'll start looking through these, thanks so much!

Merged, looks good!


[BUG] Global forecaster unable to make predictions

Describe the bug
Global forecaster not able to make predictions due to (missing) frequency information?
To Reproduce
Modified from pydata Berlin notebooks. Complete code & data here.
y_train_global, y_test_global, X_train_global, X_test_global = temporal_train_test_split(y_global, X_global)

regressor = make_pipeline(
    RandomForestRegressor(random_state=1),
)

def count_gt130(x):
    """Count how many observations lie above threshold."""
    return np.sum((x > 700)[::-1])

kwargs = {
    "lag_feature": {
        "lag": [1],
        "mean": [[1, 3], [3, 6]],
        "std": [[1, 4]],
        count_gt130: [[2, 3]],
    }
}

steps=[
        ("daily_season", DateTimeFeatures(ts_freq="D")),
        ("daily_season2", DateTimeFeatures(manual_selection=["week_of_month", "day_of_quarter"])),
]

forecaster_global = make_reduction(
    regressor,
    scitype="tabular-regressor",
    transformers=[WindowSummarizer(**kwargs, n_jobs=1, truncate="bfill")],
    window_length=None,
    strategy="recursive",
)

# Version 2: Global Forecasting
pipe_global = ForecastingPipeline(steps= steps + [("forecaster", forecaster_global)])

_ = pipe_global.fit(y_train_global, X_train_global, fh=FH)

# TODO (check): Does not recognize freq in X (so how did train work?)
y_pred_global = pipe_global.predict(X=X_test_global)

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Input In [10], in <cell line: 2>()
      1 # TODO (check): Does not recognize freq in X (so how did train work?)
----> 2 y_pred_global = pipe_global.predict(X=X_test_global)

File ~\.conda\envs\sktime-pydata\lib\site-packages\sktime\forecasting\base\_base.py:320, in BaseForecaster.predict(self, fh, X)
    318 # we call the ordinary _predict if no looping/vectorization needed
    319 if not self._is_vectorized:
--> 320     y_pred = self._predict(fh=fh, X=X_inner)
    321 else:
    322     # otherwise we call the vectorized version of predict
    323     y_pred = self._vectorize("predict", X=X_inner, fh=fh)

File ~\.conda\envs\sktime-pydata\lib\site-packages\sktime\forecasting\compose\_pipeline.py:358, in ForecastingPipeline._predict(self, fh, X)
    343 """Forecast time series at future horizon.
    344
    345 Parameters
   (...)
    355     Point predictions
    356 """
    357 X = self._transform(X=X)
--> 358 return self.forecaster_.predict(fh, X)

File ~\.conda\envs\sktime-pydata\lib\site-packages\sktime\forecasting\base\_base.py:320, in BaseForecaster.predict(self, fh, X)
    318 # we call the ordinary _predict if no looping/vectorization needed
    319 if not self._is_vectorized:
--> 320     y_pred = self._predict(fh=fh, X=X_inner)
    321 else:
    322     # otherwise we call the vectorized version of predict
    323     y_pred = self._vectorize("predict", X=X_inner, fh=fh)

File ~\.conda\envs\sktime-pydata\lib\site-packages\sktime\forecasting\base\_sktime.py:62, in _BaseWindowForecaster._predict(self, fh, X)
     60 # all values are out-of-sample
     61 if fh.is_all_out_of_sample(self.cutoff):
---> 62     return self._predict_fixed_cutoff(
     63         fh.to_out_of_sample(self.cutoff), **kwargs
     64     )
     66 # all values are in-sample
     67 elif fh.is_all_in_sample(self.cutoff):

File ~\.conda\envs\sktime-pydata\lib\site-packages\sktime\forecasting\base\_sktime.py:96, in _BaseWindowForecaster._predict_fixed_cutoff(self, fh, X, return_pred_int, alpha)
     81 """Make single-step or multi-step fixed cutoff predictions.
     82
     83 Parameters
   (...)
     93 y_pred = pd.Series or pd.DataFrame
     94 """
     95 # assert all(fh > 0)
---> 96 y_pred = self._predict_last_window(
     97     fh, X, return_pred_int=return_pred_int, alpha=alpha
     98 )
     99 if isinstance(y_pred, pd.Series) or isinstance(y_pred, pd.DataFrame):
    100     return y_pred

File ~\.conda\envs\sktime-pydata\lib\site-packages\sktime\forecasting\compose\_reduce.py:525, in _RecursiveReducer._predict_last_window(self, fh, X, return_pred_int, alpha)
    523 # Get last window of available data.
    524 if self.transformers_ is not None:
--> 525     y_last, X_last = self._get_shifted_window()
    526 else:
    527     y_last, X_last = self._get_last_window()

File ~\.conda\envs\sktime-pydata\lib\site-packages\sktime\forecasting\compose\_reduce.py:478, in _RecursiveReducer._get_shifted_window(self, shift, y_update, X_update)
    476 """Select shifted window."""
    477 # Get the start and end points of the last window.
--> 478 cutoff = _shift(self.cutoff, by=shift)
    479 start = _shift(cutoff, by=-self.window_length_ + 1)
    481 if self.transformers_ is not None:
    482     # Get the last window of the endogenous variable.
    483     # If X is given, also get the last window of the exogenous variables.

File ~\.conda\envs\sktime-pydata\lib\site-packages\sktime\utils\datetime.py:106, in _shift(x, by)
    104 if isinstance(x, pd.Timestamp):
    105     if not hasattr(x, "freq") or x.freq is None:
--> 106         raise ValueError("No `freq` information available")
    107     by *= x.freq
    108 return x + by

ValueError: No `freq` information available

Expected behavior
Would have expected this to work since training uses the same X data frame indices.
Versions

System:
python: 3.9.12 | packaged by conda-forge | (main, Mar 24 2022, 23:17:03) [MSC v.1929 64 bit (AMD64)]
executable: C:\Users\Nikhil.conda\envs\sktime-pydata\python.exe
machine: Windows-10-10.0.19044-SP0
Python dependencies:
pip: 22.1.1
setuptools: 62.3.2
sklearn: 1.1.1
sktime: 0.11.4
statsmodels: 0.13.2
numpy: 1.22.4
scipy: 1.7.3
pandas: 1.4.2
matplotlib: 3.5.2
joblib: 1.1.0
numba: 0.53.0
pmdarima: 1.8.5
tsfresh: 0.19.0

@danbartl , this looks like it might potentially come from WindowSummarizer?

Hello, I am experiencing the same issue, but I don't have any WindowSummarizer.

Hi I checked the example by @ngupta23 and the issue seems to be that the way you try to set indices ignoring the instancing of the multiindex:
y_global.set_index(["time_series", "date"], inplace=True)
X_global.set_index(["time_series", "date"], inplace=True)

This will lose the freq argument, as can be seen by
from sktime.datatypes._utilities import get_time_index
get_time_index(X_global)

You need to specify
X_global = X_global.groupby(["time_series"], as_index=True).apply(
    lambda df: df.drop(["time_series"], axis=1).set_index(["date"]).asfreq('D')
)
y_global = y_global.groupby(["time_series"], as_index=True).apply(
    lambda df: df.drop(["time_series"], axis=1).set_index(["date"]).asfreq('D')
)
get_time_index(X_global)
get_time_index(y_global)

for pandas to recognize the freq argument.
Then the example of @ngupta23 works without error (only tested based on my refactoring PR, but should work with main also).
@samuelefiorini Can you check whether that this fixes your issue as well
@fkiraly  cc

@danbartl, thanks for investigating this! I think I get it now!
It seems very unintuitive though that this additional code might be needed.
Should the temporal_train_test_split not preserve freq automatically?
I vaguely remember a PR where we wanted to address that, do you still remember where that was?

@fkiraly temporal_train_test_split  does not lose the freq, it actually was never there because the way it is assigned (see the full notebook, not the just the script) by ngupta meant it was never there.

Are you saying the problem is with the initial data?
I.e., the same code, with other data, runs?

@danbartl @fkiraly
Also, the fact that the error does not show up in fit and only in predict seems confusing (unexpected to a user not familiar with the internals). Can we add an exception during fit to somehow indicate the need to have the frequency set in the data? This would also save training time, especially for larger datasets.

You are absolutely right @ngupta23 , thanks for the suggestion. Will include that

@ngupta23 @fkiraly
Set up the following pull request to raise a warning and also provide a convience function to set freq for multiindex. The solution I presented with convert datetimeindex no longer works in latest pandas, but setting multiindex with
ttps://github.com/sktime/sktime/issues/2710](https://github.com/sktime/sktime/pull/3729


the accuracy is just about 50%

I used the prertrained model, the command is
python -m torch.distributed.launch --nproc_per_node=8 imagenet.py /media/userdisk3/ImageNet_ILSVRC2012 --distributed --batch_size 640 --epochs 45
,but after 30 epochs, the accuracy is still about 50%, just like the train stage at first epoch.

I just confirmed the accuracy with the default setting.


chore: expose absl::nullopt in our namespace

This change is

As I said elsewhere, maybe we should consider google::cloud::optional<> as essentially there for backwards compatibility, and absl::optional<> (and its friends) should be the "One True" type we expose and document. If this is true, then adding more backwards compatibility declarations probably does not make sense.
Thoughts?

Closing per our discussion, we will migrate towards absl names and not introduce any new aliases in our namespace


add bar2 to missing diagrams (missing bar count)

add missing bar count to missing diagrams

@studyproject-mlds I'm missing what adding a new diagram with the counts adds. Could you please elaborate?

@studyproject-mlds I'm missing what adding a new diagram with the counts adds. Could you please elaborate?


NIFI-1767 AWS IoT processors

20160413_apache-nifi-aws-iot-pull-request_lerchkay.pdf
Four new processors to communicate with Amazon’s managed device gateway service AWS IoT.
Use cases

Consume reported states from a fleet of things managed and secured on Amazon’s gateway service
Propagate desired states to a fleet of things managed and secured on Amazon’s gateway service
Intercept M2M communication
Hybrid IoT solutions: brings together a managed device gateway in the cloud and onpremise data-consumers and -providers.

GetAWSIoT:
Opens up a connection to an AWS-account-specific websocket endpoint in order to subscribe to any of the MQTT topics belonging to a registered thing in AWS IoT.
PutAWSIoT
Opens up a connection to an AWS-account-specific websocket endpoint in order to publish messages to any of the MQTT topics belonging to a registered thing in AWS IoT.
GetAWSIoTShadow
In AWS IoT a physical thing is represented with its last reported state by the so-called thing shadow. This processor reads out the current state of a shadow (persisted as JSON) by requesting the managed API of AWS IoT.
PutAWSIoTShadow
In AWS IoT a physical thing is represented with its last reported state by the so-called thing shadow. This processor updates the current state of a shadow (persisted as JSON) by requesting the managed API of AWS IoT. An update to a shadow lets AWS IoT propagate changes to the MQTT topics of the thing.
Known issues:

It was hard for me to write appropriate integration tests since the MQTT processors work with durable websocket-connections which are kind of tough to test. With your help I would love to do a better job on testing and hand it in later on. All of the processors were tested in a live-scenario which ran over a longer period of time. Didn’t observe any issue.
I got rid of all the properties for the deprecated AWSCredentialProviderService and only make use of AWSCredentialsProviderService. If both are still necessary for backward-compatibilit sake I would add the deprecated feature.

Hello @KayLerch .  Really cool contribution and awesome start.  We'll want to make sure there is an open Apache NiFi JIRA for this and you are more than welcome to create that.  We'll need the commits to reference that JIRA.  Take a look here for some details to help the review and follow-on processes go smoothly.  https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide
Look forward to helping you get this through the review process and included.  Your PDF writeup of the requirement and your approach is very nicely done.

Hi Joe,
thanks for helping me out. I just opened an issue in JIRA => NIFI-1767
Looking forward to getting this through :)

Live demo for PutIOTMqtt-processor ;)
https://twitter.com/KayLerch/status/721455415456882689

@KayLerch not sure why the Travis build did not trigger for your PR.  I was scoping some of this out locally and see that some contrib issues came up (this can be evaluated locally with a mvn clean install -Pcontrib-check)

@KayLerch this bundle looks awesome!
One thing, I would prefer to rename the processors to have AWS in their name. We will more than likely also have general MQTT processors unrelated to AWS and the names may be confusing.

@JPercivall Agree on that but made the naming decision based on an established convention to all the other AWS processors in this project. None of them indicates "AWS" in their names. This wasn't a problem until now as SQS, SNS, S3 and so on are really unique names. Which isn't true for IoT and MQTT. Wouldn't make the decision to break a naming convention on my own but would rather encourage the NiFi-team to think it over.
@apiri As soon as I have the time I'll take a look.

@KayLerch I definitely appreciate the decision to follow the established naming convention but I'm for breaking the convention for these processors, where the name is not unique.
If anyone else has a dissenting opinion feel free to comment.

I agree with the point @KayLerch made.  This processor is not just mqtt but is mqtt & aws so i think his naming decision makes sense.  Good to talk about the consistency approach though

Errr..i messed that response up.  I meant I agree with the point @JPercivall was making and understand what @KayLerch was thinking.  I think the names should be
GetAWSIoTMqtt
PutAWSIoTMqtt
GetAWSIoTShadow
PutAWSIoTShadow
The names have a lot going on but these are pretty purpose built for the AWS IoT platform.
Thanks

I am on board with those names

@joewitt @JPercivall : So I renamed the processors to
GetAWSIoT
PutAWSIoT
GetAWSIoTShadow
PutAWSIoTShadow
@apiri : I resolved several check-style warnings and successfully made a clean install with contrib-check. Should work now.

Is there anything I can help with getting this through?

@JPercivall you by chance have bandwidth to keep progressing this with @KayLerch ?

Yup I will start an in-depth review

I actually already committed general MQTT processors [1] and they have some good "best practices" with regards to publishing/consuming messages and MQTT I think would be good to follow here. The first few I have are below:
First in regards to the internal queue of messages, there needs to be some kind of limit on it. If a user doesn't set a fast enough trigger duration the queue could become enormous and, since all the messages are held in memory, potentially bringing NiFi to a halt. Here is the property I add to ConsumeMQTT[2].
This leads to the second, what to do with the internal queue when the processor is stopped. There will potentially be some data left in the internal queue when the processor is stopped and if that data is not handled it will more than likely be lost. In the OnStopped I actually transfer all messages in the queue (just like is done int he OnTrigger)[3].
In the PutAWSIoT processor, you read the attributes from the FlowFile to essentially overwrite Processor defined properties. Being able to have different QoS/Topics/Retained different messages is very important and the most user friendly way to do this is through Expression Language. Check out how I do it here[4]. This gives the user to potentially dynamically select the QoS/Topic/Retained and doesn't do things automatically for the user.
[1] https://github.com/apache/nifi/tree/f47af1ce8336c9305916f00738976f3505b01b0b/nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt
[2] https://github.com/apache/nifi/blob/f47af1ce8336c9305916f00738976f3505b01b0b/nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java#L111
[3] https://github.com/apache/nifi/blob/f47af1ce8336c9305916f00738976f3505b01b0b/nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java#L233
[4] https://github.com/apache/nifi/blob/f47af1ce8336c9305916f00738976f3505b01b0b/nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java#L63

The more I type out and try to easily distinguish GetAWSIoT and PutAWSIoT the more I think MQTT should be integrated into the name and all four of the processors should be Publish/Consume.
The GetAWSIoT and PutAWSIoT don't support all the AWS IoT protocols (don't support "HTTP") and only support MQTT and MQTT over websockets. The name should convey that they are specifically MQTT processors.
In NiFi, we have a couple different naming conventions. Get/Put are for processors that do individual requests to some endpoint. For example GetFile and PutFile, they don't have any lasting connections and each time get or put a file. Publish and Consume, in general, are for processors which are listening/putting to a topic. For example the PublishKafka and ConsumeKafka processors publish and subscribe to a Kafka topic (it's "consume" instead "subscribe" because we're actually doing something with the messages and not just "subscribing" to a topic, there was a whole big thread about it).

Does AWS IoT support communicating over SSL with MQTT or shadows? If so, that option should be added.

A bit nit picky and I may be alone here, but I find putting "if" statements and their content on the same line a bit hard to read when trying to read someone else's code. For example line 107 of GetAWSIoT[1]. When reviewing it's nice to distinctly see "if" statements condition and content.
I would prefer the bit more verbose but easier consume longer format:
`if (awsQos == 0) {
mqttClient.unsubscribe(awsTopic);
}'
[1] https://github.com/apache/nifi/blob/d46b01c7edf9089a944c3fc1c71b046cd19a04c2/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/iot/GetAWSIoT.java#L107-L107

For the new dependencies, NOTICE/LICENSE information needs to be added if applicable. Paho is EPL 1.0 licensed and requires being added to the nar NOTICE like so[1]. Do the other two new deps have license or notice information to add?
[1] https://github.com/apache/nifi/blob/f47af1ce8336c9305916f00738976f3505b01b0b/nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-nar/src/main/resources/META-INF/NOTICE#L29

The Get/PutAWSIoT processors read and overwrite mqttClient many times without a read/write lock, this can lead to problems in multi-threaded scenarios. For example, the both processors call "AbstractAWSIoTProcessor.connect()" when the connection is about to expire. When a processor is running with more than one thread, multiple will potentially enter that method and attempt to reconnect the client.

A couple places have weird comments like "// @TRACE 252=connect to host {0} port {1} timeout {2}". Is this a convention I'm not aware of or left over from copy/paste?

Currently the only tests are integration tests that rely on an AWS instance. I would like to see more true unit tests. For inspiration, check out the Publish/Consume MQTT unit tests[1].
[1] https://github.com/apache/nifi/tree/f47af1ce8336c9305916f00738976f3505b01b0b/nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/test/java/org/apache/nifi/processors/mqtt

Hey @KayLerch we're starting to wrap up the 0.7.0 release, did you get a chance to address these concerns?

@JPercivall : I started to work on the issues but did not finish. Have a lot of going on at the moment and no time in the next three weeks to finish my work :-(

@KayLerch unfortunate you won't be able to finish it for 0.7.0 but I'm looking forward to having it in 1.0.0! I'm going to change the status of the ticket from "Patch Available" to "In Progress".

@KayLerch do you think you'll have time to come back to this?  I'm inclined to close this as part of a stale PR sweep but wanted to check with you.  Totally understand if so.  And if you can't do it soon then perhaps you can close it and try again later?

@joewitt - I am happy to adopt the stalled PR and address @JPercivall 's comments.

@joewitt Hope you're fine. Sorry for not having my work completed. It's been a busy time.
@trixpan thanks a lot for taking this over. You're right: AWS released a Java Client SDK for IoT shortly after I submitted the PR. I agree on rather building on top of this than going forward with the custom implementation. However, AWSIoT processors for NiFi would be a big win. I am looking forward to using it.

Thabk Kay, would it be possible to  close this PR?


Fixed empty string cast

fixes https://github.com/frictionlessdata/goodtables-py/issues/109

@brew
could you please review

@brew
It's blocking please review after merge if needed.

LGTM

Thanks!


feat(ci): move from travis to gitlab ci

free travis-ci.org is end of life and travis-ci.com is only a paid service

cool!
...how does the integration into the github checks work?

I think that doesn't, its only connected via webhooks 🤷

but a failing lint is blocking, right?

but a failing lint is blocking, right?

Yep that works fine 😘


@azure/app-configuration combined with @azure/identity - Suggest best practice

If I want as many configs/secrets/feature flags as possible in App Config, and the fewest environment variables to run an app hosted on Azure (Functions or App Service is what I'm thinking), and since App Config is connected by a connection string, how bad would it be to NOT set the DefaultAzureCredential variables in the environment but instead read them out of the App Config?
If you have only 1 or 2 settings beyond DefaultAzureCredential, setting them in the App service isn't a big deal, but if you have 20 or 30 and growing, across multiple deployments then only having 1 setting in App service then getting everything else from App Config makes sense to me.

As I’m trying to figure out how to approach this issue, I can divide it into three questions:

What is the recommended approach to use @azure/app-configuration to configure an app that uses @azure/identity?
What is the recommended approach to use @azure/app-configuration to configure an app that uses @azure/identity … for the deployment of a large amount of resources?
Could there be a credential that reads and authenticates with the values stored App Config?

For the first question, Harsha and I can think on a sample scenario. I would estimate this would be fairly easy and not too different from our current samples.
For the question of a large deployment, Harsha and I can work on a sample scenario using ARM templates.
For the feature request of making Identity work with App Config, we would need to bring this suggestion to the Identity feature crew.
Alternatively, @azure/app-configuration could have a method to export environment variables — thus making the EnvironmentCredential work. — meaning, there could be an alternative solution coming from @azure/app-configuration instead of @azure/identity.
While we work on those answers, I believe this issue is, at heart, really a feature request. Let me know if that is correct, and I will update the label.

After discussing with @sadasant and others from the app-config (SDK) feature crew, got hold of a couple of resources and gained some knowledge.
The summary is to use app-config and keyvault together while developing the applications.
App Config for all the general settings such as endpoints, client id, tenant id, etc. Keyvault for all the secrets such as connection strings, client secrets, shared access keys, etc.
Based on the kind of architecture, environment, and the AAD credential used, what we store in app-config and keyvault might vary.
For example, if InteractiveBrowserCredential is used with say, popup login mechanism, we get the credential from identity, we can use the credential with app-config and keyvault SDKs to get the non-secrets and secrets which can later be used for the other Azure services.
Resources

azure/architecture/solution-ideas/articles/appconfig-key-vault
azure/azure-sdk-for-net/app-secrets-configuration - uses a .NET sample, but the content is applicable for all the languages.

This article shares examples of the non-secrets to be stored in App Config and the secrets to be stored in keyvault.

Here's a TypeScript sample secretReference.ts that shows how to use the special config setting called SecretReference to get secrets from keyvault by leveraging app-config and keyvault SDKs

User authenticates to app-config with AAD, gets the SecretReference for the key name. Leverages keyvault secrets SDK, uses the key name from before to load the secret corresponding to the key name.
JS/TS App Config Samples

Thank you - this is guidance I can take forward.


Error: spawn python ENOENT

Describe the bug
A clear and concise description of what the bug is.
docker error log:
2024-08-07 20:05:17 Error: spawn python ENOENT
2024-08-07 20:05:17     at ChildProcess._handle.onexit (node:internal/child_process:286:19)
2024-08-07 20:05:17     at onErrorNT (node:internal/child_process:484:16)
2024-08-07 20:05:17     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
2024-08-07 20:05:17   errno: -2,
2024-08-07 20:05:17   code: 'ENOENT',
2024-08-07 20:05:17   syscall: 'spawn python',
2024-08-07 20:05:17   path: 'python',
2024-08-07 20:05:17   spawnargs: [
2024-08-07 20:05:17     '/app/src/web/nextui/.next/server/app/api/eval/job/wrapper.py',
2024-08-07 20:05:17     '/app/src/web/nextui/resp-gen-ip.py',
2024-08-07 20:05:17     'get_var',
2024-08-07 20:05:17     '/tmp/promptfoo-python-input-json-1723041317203-ff97d966e2159.json'
2024-08-07 20:05:17   ]
2024-08-07 20:05:17 }

To Reproduce
Steps to reproduce the behavior, including example Promptfoo configurations if applicable:

check out the latest code
build docker image
docker build --build-arg NEXT_PUBLIC_PROMPTFOO_BASE_URL=http://localhost:3000 -t promptfoo-ui .
run the container
docker run -d --add-host host.docker.internal:host-gateway --name promptfoo_container -p 3000:3000  -p 11434:11434 -v /Users/deepakkumar.sahoo/add_bins/promptfoo_workspace:/root/.promptfoo -e OPENAI_API_KEY=sk-xxxx -e PROMPTFOO_CONFIG_DIR=~/.promptfoo promptfoo-ui
can see the hosted instance in localhost:3000
Now create promptfooconfig.yaml file like below

description: 'Dynamic var example'

prompts:
  - "{{context}} \n\n {{userip}}"

providers:
  - id: ollama:llama3

tests:
  - vars:
      userip: file://resp-gen-ip.py
      context: file://resp-gen.py

copy resp-gen-ip.py and resp-gen-ip.py files to /app/src/web/nextui/ since for some reason if the py files are not present here getting error.

No files found for variable userip at path /app/src/web/nextui/resp-gen-ip.py
2024-08-07 20:04:34     at generateVarCombinations (/app/src/web/nextui/.next/server/app/api/eval/job/route.js:10351:23)
2024-08-07 20:04:34     at Evaluator.evaluate (/app/src/web/nextui/.next/server/app/api/eval/job/route.js:10727:17)
2024-08-07 20:04:34     at evaluate (/app/src/web/nextui/.next/server/app/api/eval/job/route.js:11056:15)
2024-08-07 20:04:34     at Object.index_evaluate [as evaluate] (/app/src/web/nextui/.next/server/app/api/eval/job/route.js:11629:23)
2024-08-07 20:04:34     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Run eval from the hosted instance

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information (please complete the following information):

Promptfoo version:

Additional context
Add any other context about the problem here.

Just now tried with the example
https://github.com/promptfoo/promptfoo/blob/main/examples/python-assert-inline/promptfooconfig.yaml
Getting similar error
Error: spawn python ENOENT
2024-08-07 22:26:04     at ChildProcess._handle.onexit (node:internal/child_process:286:19)
2024-08-07 22:26:04     at onErrorNT (node:internal/child_process:484:16)
2024-08-07 22:26:04     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
2024-08-07 22:26:04   errno: -2,
2024-08-07 22:26:04   code: 'ENOENT',
2024-08-07 22:26:04   syscall: 'spawn python',
2024-08-07 22:26:04   path: 'python',
2024-08-07 22:26:04   spawnargs: [
2024-08-07 22:26:04     '/app/src/web/nextui/.next/server/app/api/eval/job/wrapper.py',
2024-08-07 22:26:04     '/tmp/temp-python-code-1723049764221-7895919c037ee.py',
2024-08-07 22:26:04     'main',
2024-08-07 22:26:04     '/tmp/promptfoo-python-input-json-1723049764222-9e2bbf7afd8ff.json'
2024-08-07 22:26:04   ]
2024-08-07 22:26:04 }

Has anyone tried python  tests or asserts directly in the UI by using hosted instance (using the docker image) ?

This happens because there is no python runtime in the Docker image.  The hosted instance doesn't support Python asserts at this time, because it is a less common use case to want to run the eval directly in the image, but you can probably get it working by installing Python in the Docker build - I'd happily accept a PR for this

Hi @dmockingbird551, thanks so much for bringing this up and for your patience! We fixed the issue by adding a Python runtime to the Docker image as part of this PR. Apologies for not notifying you sooner! Please feel free to pull the latest image, and if you run into any further issues, don’t hesitate to re-open this or create a new issue.

I'm still seeing this problem after install via npm:
npm install -g promptfoo
promptfoo init

$ promptfoo --version
0.87.1

Any ideas?

You might need to set your PROMPTFOO_PYTHON environment variable:
https://www.promptfoo.dev/docs/providers/python/#setting-the-python-binary-path
On Sun, Sep 15, 2024 at 8:19 AM Chris DiGiano @.***>
wrote:

I'm still seeing this problem after install via npm:
npm install -g promptfoo
promptfoo init
$ promptfoo --version
0.87.1
Any ideas?
—
Reply to this email directly, view it on GitHub
https://github.com/promptfoo/promptfoo/issues/1389#issuecomment-2351635068,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACLYJRDDND5ORS3BSW7QVLZWWQO7AVCNFSM6AAAAABMESME7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJRGYZTKMBWHA
.
You are receiving this because you commented.Message ID:
@.***>

Hi @justdigi, apologies for the confusion! I added Python support in #1519 but we removed it in #1599. I’ll re-add it and test it now. Thanks for your patience, and I’ll keep you posted once it's ready!

The fix is in https://github.com/promptfoo/promptfoo/pull/1677. I’ve also added checks in the CI to make sure Python stays in the image going forward. Thanks so much for your patience and for flagging this—please don’t hesitate to reach out if you run into any other issues.


[Validating] Updating build definitions

Updating build definitions to isolate worker and extensions
Issue describing the changes in this PR
Pull request checklist

[ ] My changes do not require documentation changes

[ ] Otherwise: Documentation issue linked to PR

[ ] My changes should not be added to the release notes for the next release

[ ] Otherwise: I've added my notes to release_notes.md

[ ] My changes do not need to be backported to a previous version

[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr

[ ] I have added all required tests (Unit tests, E2E tests)

/check-enforcer reset

/check-enforcer reset

/check-enforcer evaluate

/check-enforcer evaluate


Fix workflow effort being wasted if a single export fails (fixes #1319)

Previously, if your workflow completed successfully but a single toil.exportFile call failed, the entire effort would be wasted, because there was no way of running the export steps again (the workflow would crash if restarted).
This PR allows a "restart" if the workflow is nominally completed and the jobStore hasn't been deleted. No Job work will be done on this type of "restart", just export steps and other main-method work.

@joelarmstrong, is this ready to merge?

Hey Edwin,
Yeah, this should be OK to merge. Thanks.

Thank you @joelarmstrong


FIX Don't pass labelfield as value for SearchableDropdownField

Issue

https://github.com/silverstripe/silverstripe-framework/issues/11294

Prefer-lowest CI failure is unrelated.


Sync eng/common directory with azure-sdk-tools for PR 1148

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/1148  See eng/common workflow

/check-enforcer override


more usefull player FOV, prepare weapon models for drop ability, player camera refactor

Fov applying now by multiplier and animation speed tomake it more advansed

forward velocity fov like example
https://github.com/user-attachments/assets/d41cde1a-adfc-4b17-8cce-c2d82d659153
ViewModelCamera deleted and camera movement now inside player component to use camera variables and methods directly
Setup world model physics hulls to make weapons drop/pickup soon
Make weapons souds more quiet

Let's start off with these 4 comments before discussing the rest, I do really like the fov change when running :D


Bulk Data Group/$export using Group.characteristic

follow-on from #108

review the cohorts we want to support
express the cohorts using the FHIR Group resource (using inclusion and exclusion criteria)
write generic utility for resolving the inclusion/exclusion criteria into a list of patient resources
hook it into the bulk export operation

Suggestions for making this tractable:

start with export on just a single criteria (e.g. look at the Group examples)
alternative:  start with just the the 4 characteristics defined at https://www.hl7.org/fhir/population.html
manually construct the search string that corresponds to a single criteria

Then:  identify the delta between that and a more complicated cohort definition like one for Diabetes.

Related to FHIR Resource: Group.characteristic

Source: https://ibm.ent.box.com/file/922194231982
The HL7 FHIR Bulk Data Export Implementation Guide has support for the Group/$export extended operation. The Group/$export exports all user data pertaining to a group (in the IBM FHIR Server it’s limited to the Patient Compartment data).
There are two main types of groups Descriptive or Actual; specified in the Group.actual field. An actual group specifies a set of members Group.member where each member includes a Reference (Patient/1-2-3-4).  A descriptive group uses Include/Exclude traits that are described as a combination of FHIR Data Types:

valueCodeableConcept			CodeableConcept
valueBoolean            		boolean
valueQuantity               	Quantity
valueRange                  	Range
valueReference              	Reference

Today, the IBM FHIR Server supports Actual (Group.member). The team has implemented the processing of the Dynamic Groups for specific use cases, such as Age Range-Blood Pressure. The package com.ibm.fhir.operation.bulkdata.tool.helpers.dynamic contains sample groups and Patient Bundles in Java code and actual JSONs in fhir-examples/src/main/resources/json/ibm/bulk-data/group.
An example characteristic is:
"characteristic": [
        {
            "code": {
                "coding": [
                    {
                        "system": "http://loinc.org",
                        "code": "29553-5"
                    }
                ],
                "text": "Age calculated"
            },
            "valueQuantity": {
                "value": 13,
                "comparator": ">=",
                "unit": "years",
                "system": "http://unitsofmeasure.org",
                "code": "a"
            },
            "exclude": false
        }]

The team built a GroupSearchCompiler (implementation: GroupSearchCompilerImpl) in fhir-search which takes the Group and uses characteristic specific processing to compile down to search parameters:
private static final List<CharacteristicProcessor> CODEABLE_CONCEPT_PROCESSORS = Arrays.asList(new PregnancyStatusCharacteristicProcessor(), new AdministrativeGenderCharacteristicProcessor());
private static final List<CharacteristicProcessor> BOOLEAN_PROCESSORS = Arrays.asList(new NoOpCharacteristicProcessor());
private static final List<CharacteristicProcessor> RANGE_PROCESSORS = Arrays.asList(new NoOpCharacteristicProcessor());
private static final List<CharacteristicProcessor> REFERENCE_PROCESSORS = Arrays.asList(new NoOpCharacteristicProcessor());
private static final List<CharacteristicProcessor> QUANTITY_PROCESSORS = Arrays.asList(new PatientAgeCharacteristicProcessor());

The generated Search is targeted on Patient in order to generate a list of patients. For example an Age search would generate a birthdate=le2000&birthdate=ge1990 for a target age range.
The next steps to complete the Dynamic Group is to hook into the com.ibm.fhir.bulkdata.export.group.resource.GroupHandler.process(groupId), and check to see if the group retrieved is actual or characteristic. If Group.actual = false and there are characteristics, then process GroupSearchCompiler to get a Search Parameter, and then Page through the Search each time it is called.
public void process(String groupId) throws Exception {
        if (patientMembers == null) {
            Group group = findGroupByID(groupId);
            uniquenessGuard = new HashSet<>();
            patientMembers = new ArrayList<>();
            // List for the group and sub groups in the expansion paths, this is used to avoid dead loop caused by circle reference of the groups.
            Set<String> groupsInPath = new HashSet<>();
            expandGroupToPatients(group, groupsInPath);
        }
    }


Model scan missing properties that are visible during serialization only

When a model class has a property that is only visible to jackson during serialization (due to a @JsonIgnore on the setter and @JsonInclude on the getter, for instance), the ApiModelReader returns a model that does not include the property.
Example model class:
class ModelWithSerializeOnlyProperty {
  String alwaysVisible;
  @JsonIgnore
  private Long visibleForSerialize;

  @JsonProperty
  public Long getVisibleForSerialize() {
    return visibleForSerialize;
  }

  @JsonIgnore
  public void setVisibleForSerialize(Long visibleForSerialize) {
    this.visibleForSerialize = visibleForSerialize;
  }
}

Current scan result:
models: {
    ...
    ModelWithSerializeOnlyProperty: {
        properties {
            alwaysVisible: { ... }
        }
    }
...
}

Correct scan result:
models: {
    ...
    ModelWithSerializeOnlyProperty: {
        properties {
            alwaysVisible: { ... },
            visibleForSerialize: { ... }
        }
    }
   ...
}

Hi
I have 0.9.4 and I still have the described issue in my project. I have looked ApiModelReader and it has the method mergeModelMap, so I assume that it supposed to be fixed. However I see the same model for get and set methods.
My code is
...
@JsonIgnore
private Boolean built_in;
..
@JsonProperty
public Boolean isBuilt_in() {
return built_in;
}
@JsonIgnore
public void setBuilt_in(Boolean built_in) {
    this.built_in = built_in;
}

..
This field isn't present in the swagger model at all. Jackson is working as expected, the field is returned on get and ignored on set.
Is there anything I am missing?

@mkarasik Just so I understand..
You have Model with this particular set of annotations. What are you doing with the model?

Is this a model returned from a method?
is this a model that also a method parameter?

The merge kicks in only if the model is used in the context of serialization (input param) as well as deserialization (return value).

It is used as the returned value of GET method and as input value @RequestBody in POST method.


dyld[11411]: Library not loaded: /opt/homebrew/opt/xz/lib/liblzma.5.dylib on MacOS

Description
We have a composer installation step in our workflow: composer i --no-dev, this fails as of today with:
dyld[11411]: Library not loaded: /opt/homebrew/opt/xz/lib/liblzma.5.dylib
  Referenced from: <F2996FBC-0EDB-359C-9603-1721ACB56297> /opt/homebrew/Cellar/libtiff/4.6.0/lib/libtiff.6.dylib
  Reason: tried: '/opt/homebrew/opt/xz/lib/liblzma.5.dylib' (), '/System/Volumes/Preboot/Cryptexes/OS/opt/homebrew/opt/xz/lib/liblzma.5.dylib' (no such file), '/opt/homebrew/opt/xz/lib/liblzma.5.dylib' (), '/opt/homebrew/Cellar/xz/5.4.5/lib/liblzma.5.dylib' (), '/System/Volumes/Preboot/Cryptexes/OS/opt/homebrew/Cellar/xz/5.4.5/lib/liblzma.5.dylib' (no such file), '/opt/homebrew/Cellar/xz/5.4.5/lib/liblzma.5.dylib' ()Library not loaded: /opt/homebrew/opt/xz/lib/liblzma.5.dylib
  Referenced from: <1C0C8B9A-537B-3097-935A-73CFDF859EAE> /opt/homebrew/Cellar/libzip/1.10.1/lib/libzip.5.5.dylib
  Reason: tried: '/opt/homebrew/opt/xz/lib/liblzma.5.dylib' (), '/System/Volumes/Preboot/Cryptexes/OS/opt/homebrew/opt/xz/lib/liblzma.5.dylib' (no such file), '/opt/homebrew/opt/xz/lib/liblzma.5.dylib' (), '/opt/homebrew/Cellar/xz/5.4.5/lib/liblzma.5.dylib' (), '/System/Volumes/Preboot/Cryptexes/OS/opt/homebrew/Cellar/xz/5.4.5/lib/liblzma.5.dylib' (no such file), '/opt/homebrew/Cellar/xz/5.4.5/lib/liblzma.5.dylib' ()
/Users/runner/work/_temp/f04796ca-c2f2-42ff-9b5b-91c0b94ef81d.sh: line 1: 11411 Abort trap: 6           composer i --no-dev
Error: Process completed with exit code [13](https://github.com/nextcloud/talk-ios/actions/runs/8062655789/job/22022843943#step:7:14)4.

Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[X] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Failed run:
  Image: macos-14-arm64
  Version: 20240116.1
  Included Software: https://github.com/actions/runner-images/blob/macOS-14/20240116.1/images/macos/macos-14-arm64-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/macOS-14%2F20240116.1

https://github.com/nextcloud/talk-ios/actions/runs/8062655789/job/22022843943
Successful run:
  Image: macos-14-arm64
  Version: 20240116.1
  Included Software: https://github.com/actions/runner-images/blob/macOS-14/20240116.1/images/macos/macos-14-arm64-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/macOS-14%2F20240116.1

https://github.com/nextcloud/talk-ios/actions/runs/8046896893/job/21976274539
Is it regression?
Yes, see successful link above
Expected behavior
Composer installation should run without issue
Actual behavior
Composer installation fails with the message above
Repro steps
    - name: Checkout Talk
      uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
      with:
        repository: nextcloud/spreed
        path: server/apps/spreed
        ref: main

    - name: Set up production dependencies
      working-directory: server/apps/spreed
      run: composer i --no-dev

Hey @SystemKeeper,
Image versions do not change between successful and unsuccessful runs. I would suggest reporting to shivammathur/setup-php or to brew, since error is in setup-php extensions step.

since error is in setup-php extensions step.

Very sorry about that, I did miss it since the step was marked as successful. Will investigate further. Thanks for your help.


RFC1: Add SourceLocation Specification

https://github.com/opencomputeproject/ocp-diag-core/discussions/634
Signed-off-by: ChunKai Chen<EMAIL_ADDRESS>

@arunkoshy waiting for an approval from you; i think we need to add you to the gh team here
@dframe-google are we blocked on the DCO or can we use a blank signature for this one (and we provide the DCO text later)?

@mimir-d LGTM based on our discussion.

@ckchen-google thanks for this PR and the fixes. seems the DCO bot isnt liking your signature. we can manually bypass this, but ideally the commits would be fixed.
here's the list of errors:
Commit sha: [6c1e522], Author: Chun-Kai Chen, Committer: Chun-Kai Chen; Expected "Chun-Kai Chen [chunkaichen@google.com](mailto:chunkaichen@google.com)", but got "ChunKai Chen [chunkaichen@google.com](mailto:chunkaichen@google.com)".
Commit sha: [6d065cc], Author: ckchen-google, Committer: ckchen-google; Expected "ckchen-google [chunkaichen@google.com](mailto:chunkaichen@google.com)", but got "ChunKai Chen [chunkaichen@google.com](mailto:chunkaichen@google.com)".
Commit sha: [120df12], Author: ckchen-google, Committer: ckchen-google; The sign-off is missing

@ckchen-google @mimir-d  yep, DCO is " literal " - my recommendation is to setup something automatic in your git workflow to ensure the signature is fixed to what passes going forward. I'd to do this for OCP-OSFCI.

Fixed DCO issues.


Date of Birth and Age

Description
Added an autogenerated age field and add validation in the date of birth field.
Fixes #317
closes #317 Birth Date Validation and age Field Addition
Screenshots
https://github.com/Counselllor/Counsellor-Web/assets/86224794/2ac1303c-da16-472f-95b9-cc926c101811
Checklist

[ ] Tests have been added or updated to cover the changes
[x] Documentation has been updated to reflect the changes
[ ] Code follows the established coding style guidelines
[ ] All tests are passing

Thanks for your compliment @thestarsahil

@thestarsahil how about adding a navbar on top of the page in login and signup, if you think it will be good than I can raise an issue regarding it. The design will be similar to the rest of the site
We can add the links in the navbar about,  countact us, about, privacy policy, contributors
And later when these pages are developed we can add the link to redirect to those pages.
What's your opinion??


[MTA-002] Analysis weather API and design app architecture

api : https://openweathermap.org/api/hourly-forecast
UX Icon : https://openweathermap.org/weather-conditions

Analysis weather API Documents

https://github.com/ababqq/motov-test-android/blob/develop/docs/HowToCallAPI.md
https://github.com/ababqq/motov-test-android/blob/develop/docs/HowToGetIconURL.md

Design app architecture Document

https://github.com/ababqq/motov-test-android/blob/develop/images/architecture.png


gcr.io transition...

There may be issues using gcr.io after March 18, 2025, but it looks like it might continue to work for simple image pulls...

https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr
https://book.kubebuilder.io/reference/metrics#important-if-you-are-using-kube-rbac-proxy

Currently SusQL Operator uses gcr.io as follows:

Dockerfile:FROM gcr.io/distroless/static-debian12:nonroot
config/default/manager_auth_proxy_patch.yaml:        image: gcr.io/kubebuilder/kube-rbac-proxy:v0.14.1

Received the following announcement. Looks like it is just about time to take action on this:
https://github.com/redhat-openshift-ecosystem/community-operators-prod/discussions/5625

Looks like updating operator-sdk from 1.36.1 to 1.38 and applying the migration steps below seems to be a good approach:
https://v1-38-x.sdk.operatorframework.io/docs/upgrading-sdk-version/v1.38.0/


Request to join the community

Hello, I want to contribute to open-source projects. I want to build a good portfolio on Git Hub, I need PR, issues, contributions, and all other stuff. Please consider my request and send me the invitation.

I ahve already sent an invite to an earlier open issue, please feel free to reopen this in case the invite expires : ) Thanks


Optimizing encoded H264 size

I'm using the SequenceEncoder to encode a MP4/H264 video, but the file size is pretty enormous when compared to the equivalent ffmpeg output. I'm completely green with video encoding, so I'm not sure if it is an issue with how SequenceEncoder is configured, or with the Baseline codec itself. Can the muxer in SequenceEncoder be configured to optimize for size?

Well, this is expected as JCodec's H.264 is rudimentary. It will produce
enormous output compared the state-of-the-art x264 encoder used in ffmpeg.
Stan
On Mon, Mar 30, 2015 at 4:24 PM, Chris Parker<EMAIL_ADDRESS>wrote:

I'm using the SequenceEncoder to encode a MP4/H264 video, but the file
size is pretty enormous when compared to the equivalent ffmpeg output. I'm
completely green with video encoding, so I'm not sure if it is an issue
with how SequenceEncoder is configured, or with the Baseline codec
itself. Can the muxer in SequenceEncoder be configured to optimize for
size?
—
Reply to this email directly or view it on GitHub
https://github.com/jcodec/jcodec/issues/72.

OK, thanks for the quick response.


Azure container instances don't work with azure data blobs.

I can't seem to mount azure data blobs on ACI using docker, always runs into
fuse mount failed,
I can circumvent this, by passing arguments when using docker run, --cap-add SYS_ADMIN, --device /dev/fuse --security-opt apparmor:unconfined on my local, is there a way to pass these arguments to docker when launching container instance?

@vasusingla619 Azure file shares can be mounted in Azure Container Instances.  Please see here: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-volume-azure-files


⚠ Bofrost.be has degraded performance

In eef2f82, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1368 ms

Resolved: Bofrost.be performance has improved in 95d0ea6 after 16 minutes.


FishFeed Merd buttons are grabbable

You can pick up the merd buttons on the control panel and move them around in the Fish feeding game.

The merd buttons had the VRIF grabbable script attached, removing this script fixed the issue.


Edit UG and README

Codecov Report

Merging #297 (51abcc9) into master (46aa7d4) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #297   +/-   ##
=========================================
  Coverage     46.46%   46.46%
  Complexity      487      487
=========================================
  Files           117      117
  Lines          2615     2615
  Branches        183      183
=========================================
  Hits           1215     1215
  Misses         1322     1322
  Partials         78       78

Continue to review full report at Codecov.

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


Stand up integration tests for S3 and GCS

This ticket is two parts:

Standing up an S3 and GCS bucket in Pipekit infrastructure for testing
Adding integration tests to the Argo Workflows codebase that validate that reads/writes to S3 and GCS work as intended

We'll need @tico24 to stand up the infrastructure, provision any secrets needed, and add them to the appropriate secrets store (most likely the Github secrets on this repo)
From there, we're free to implement the tests that do the connection however we see fit. I know @Joibel and @tico24 have both mentioned that they would like to test workflows using Argo Workflows itself. I'll leave that decision on whether to do that in this PR to y'all

Oddly, I have a PR to add s3 buckets to our internal workflows instance already, so this is almost 'done'.
For GCS, I'll need... GCS please @JPZ13

s3 is now set up internally.
@Joibel will need various bits of internal access in order to use it though. Probably not sensible to document on this public repo.

@JPZ13 @caelan-io  can you either give me access to the argo-workflows project or put this issue in the backlog of https://github.com/orgs/pipekit/projects/3/views/1


Preparatory fixes for NumericalBRadialGridGenerator

Before we implement general numerical magnetic fields, we need to fix the following issues:
RadialGridGenerator

[ ] Generalize the FindMagneticFieldExtremum method so that it can find Bmin, Bmax and the corresponding angles for general magnetic fields (currently only symmetric ones supported)
[x] Remove the "optimized" functions that take cos(theta) and sin(theta) as arguments. They are probably useless to NumericalB, and are no longer really used, as they were superceded by EvaluateGeometricQuantities which turned out to be much more efficient.

FluxSurfaceAverager

[ ] It would be a pleasant surprise if FluxSurfaceAverager.avalancheDelta.cpp works correctly with NumericalB. This should be tested by extending the RunawayFluid test to a numerical grid.

I have reviewed the code of RadialGridGenerator, FluxSurfaceAverager and BounceAverager, and surprisingly this is all I could find that looked off. Otherwise it looks like everything has been prepared!

Numerical magnetic fields are now implemented.