[Snyk] Security upgrade python from 3.8-alpine to 3.13.0a3-alpine

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

Dockerfile

We recommend upgrading to python:3.13.0a3-alpine, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

436
CVE-2023-6129 SNYK-ALPINE319-OPENSSL-6148881
No Known Exploit

436
CVE-2023-6129 SNYK-ALPINE319-OPENSSL-6148881
No Known Exploit

436
CVE-2023-6237 SNYK-ALPINE319-OPENSSL-6159994
No Known Exploit

436
CVE-2023-6237 SNYK-ALPINE319-OPENSSL-6159994
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Checkmarx One – Scan Summary & Details – fcf8eb2c-5201-4a87-a69d-8da4fa6c2f76
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2023-39325
Go-golang.org/x/net-v0.0.0-20211015210444-4f30a5c0130f
Vulnerable Package

CVE-2023-45133
<EMAIL_ADDRESS>Vulnerable Package

CVE-2023-45311
Npm-fsevents-1.2.9
Vulnerable Package

CVE-2023-49568
Go-github.com/go-git/go-git/v5-v5.4.2
Vulnerable Package

CVE-2023-49569
Go-github.com/go-git/go-git/v5-v5.4.2
Vulnerable Package

Cxb421a484-d05a
Go-github.com/cyphar/filepath-securejoin-v0.2.2
Vulnerable Package

Cxb6dee8d5-b814
Go-gopkg.in/square/go-jose.v2-v2.5.1
Vulnerable Package

CVE-2023-3978
Go-golang.org/x/net-v0.0.0-20211015210444-4f30a5c0130f
Vulnerable Package

CVE-2023-44487
Go-golang.org/x/net-v0.0.0-20211015210444-4f30a5c0130f
Vulnerable Package

CVE-2023-48795
Go-golang.org/x/crypto-v0.0.0-20210513164829-c07d793c2f9a
Vulnerable Package

Cx68162182-3f7b
Go-github.com/containerd/containerd-v1.5.2
Vulnerable Package

Path_Traversal
/scenarios/vulnerable_lambda/terraform/lambda_source_code/policy_applier_lambda1_src/click/core.py: 1046
Attack Vector

Path_Traversal
/scenarios/vulnerable_lambda/terraform/lambda_source_code/policy_applier_lambda2_src/click/core.py: 1046
Attack Vector

Path_Traversal
/scenarios/vulnerable_lambda/terraform/lambda_source_code/policy_applier_lambda2_src/click/utils.py: 510
Attack Vector

Path_Traversal
/scenarios/vulnerable_lambda/terraform/lambda_source_code/policy_applier_lambda1_src/click/utils.py: 510
Attack Vector

Path_Traversal
/scenarios/vulnerable_lambda/terraform/lambda_source_code/policy_applier_lambda1_src/click/utils.py: 510
Attack Vector

Path_Traversal
/scenarios/vulnerable_lambda/terraform/lambda_source_code/policy_applier_lambda2_src/click/utils.py: 510
Attack Vector

Fixed Issues

Severity
Issue
Source File / Package

Object_Access_Violation
/scenarios/vulnerable_lambda/terraform/lambda_source_code/policy_applier_lambda2_src/tabulate.py: 1807

Object_Access_Violation
/scenarios/vulnerable_lambda/terraform/lambda_source_code/policy_applier_lambda2_src/tabulate.py: 1870

Object_Access_Violation
/scenarios/vulnerable_lambda/terraform/lambda_source_code/policy_applier_lambda1_src/tabulate.py: 1870

Object_Access_Violation
/scenarios/vulnerable_lambda/terraform/lambda_source_code/policy_applier_lambda1_src/tabulate.py: 1807


Export: emission materials export too bright

A basic emission material like this

exports as
  "materials": [
    {
      "emissiveFactor": [1, 0, 0],
      "pbrMetallicRoughness": {},
      ...
    }

Since pbrMetallicRoughness is omitted, the defaults are baseColor=[1,1,1,1], metallic=1, roughness=1. This is much too bright.

Messing around in Blender to find an equivalent-looking Principled node, baseColor=[0,0,0,1], metallic=(anything), roughness=1 is much better.

Note: This material setup was discussed at https://github.com/KhronosGroup/glTF-Blender-IO/pull/1209#issuecomment-693649108.

Good catch, the exporter should produce baseColor: [0, 0, 0, 1] for materials like this.

Good catch, the exporter should produce baseColor: [0, 0, 0, 1] for materials like this.

@scurest @emackey Can you please have a look on #1569 ?


Measure tool: Add possibility to predefine question answers in dot env file

Hi! I'm away from PC right now, but does this PR allow to measure without any stdin from user, even without TTY?

Hi! I'm away from PC right now, but does this PR allow to measure without any stdin from user, even without TTY?

Yes when you define all the params in .env you can start the measure script without any stdin from the user, it will start straight away.


Schema-registry support

Hi,
Do you plan do add support for schema-registry to be able to read data serialized with protobuf or avro?

Hi, yeah support for SR will be added eventually.
It's not trivial addition to implement/test properly.
It's not currently priority within Infobip's and my team's plans. I'll try my best to find some time to implement it.


Add type key to properties (simple)

This addresses #269, but does not close it. That will be up to #270.
The type key will hold the value of the outermost type of the property it describes, i.e., for species, which is described as a "list of dictionaries", the type will be "list".
The value of type MUST be one of the OPTIMADE data types described here in the specification.

I'm happy with this as is, but do you think there should be a discussion of the type field in the section about provider-specific types? i.e. "Providers MUST/SHOULD provide the type of custom fields at the info/entry endpoint", or some such? Otherwise I don't see what value is gained from this PR alone for clients trying to display custom fields (as probably no-one will implement this field).

That would be great, but considering so many of the properties are already not a MUST, I think it's hard to justify this point.
However, we could always add a RECOMMENDED?

When we later upgrade this field to be a more complete type description; will we have to consider this a backwards-breaking change (i.e., new major version number) or a minor version?
How about we write in this text to that if the value isn't a simple OPTIMADE Datatype, the client should ignore the field?

In the latest commit I've added the following:

A database-provider-specific property MUST be listed in its respective entry listing /info endpoint.
Future-proofing the type field.
New :type: rst role to be used when writing OPTIMADE data types.


Release to npm and github using semantic-release

Before I set up semantic-release, I want to make sure I have the npm workflow set up correctly, for example, what scripts need to run before publishing, so that the dist and src folders are both on npm.
Should the examples be on npm, too?
Anything else I need to change before publishing to npm?
Feedback / help is much appreciated.
/cc @boennemann

You should remove tests and linting from prepublish, so it only builds the assets you want.
You then set up .gitignore and .npmignore as you need (lmk if you need more info on that).
From then on it's semantic-release-cli setup

@boennemann Thanks! I'd be very grateful for quick sanity check of the latest .gitignore and .npmignore. Then, I'll have the pleasure of using the cli for the first time :grinning:.

https://github.com/KeywordBrain/redbox-react/pull/5
When using the CLI let it overwrite your .travis.yml. Single node.js version should suffice. :+1:


deployCustom command works differently in 2.0

Not necessarily a bug but just so you are aware...
In 0.9, the following deployCustom command used to work for me (Windows)
pscp -C -r -v "$outputDir/*" apnmbx-wits@magicsplat.com:/var/www/magicsplat

In 2.0 beta it raises an error that key "$outputDir/*" (exact error below). I had to change the command to
pscp -C -r -v "$outputDir" apnmbx-wits@magicsplat.com:/var/www/magicsplat

which works but has different semantics requiring an additional step after the copy and is less convenient.
Just FYI in case it points to some other more significant issue.
The exact error stack was
---- 2019-11-10 11:14:37 IST [error]

*** error: key "outputDir/*" not known in dictionary ***
Traceback:
key "outputDir/*" not known in dictionary
    while executing
"dict get $substDict $key"
    ("uplevel" body line 4)
    invoked from within
"uplevel 1 $script"
    (procedure "::struct::list::Lmapfor" line 8)
    invoked from within
"::struct::list::Lmapfor x {pscp -C -r -v "$outputDir/*" apnmbx-wits@magicsplat.com:/var/www/magicsplat} {

I've reverted the deployCustom variable substitution to (a subset of) its old behavior.  Please check dev.

Updated.  I think I have found a nice compromise between the old and the new semantics.

Works for me. Thanks.
magicsplat is running the updated code.

Great! Thank you for your bug reports. If I get no new issues for a few days I'll release a new beta.


[MTDSA-6034] - delete other deductions raml

Harry had said before if whoever was doing the raml if they could fix the "Other Deduction API API" bit at the top of the page


add displayed_name attribute for the variables and additional check

related to the changes describe in #55 regarding the variable.
/cc @AntoineThebaud @ahurtaud

Codecov Report

Merging #58 (03b0e3b) into master (e60a5f1) will increase coverage by 0.15%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master      #58      +/-   ##
==========================================
+ Coverage   13.21%   13.36%   +0.15%
==========================================
  Files          54       54
  Lines        2006     2012       +6
==========================================
+ Hits          265      269       +4
- Misses       1692     1694       +2
  Partials       49       49

Impacted Files
Coverage Δ

pkg/model/api/v1/dashboard.go
0.00% <0.00%> (ø)

pkg/model/api/v1/dashboard_variable.go
68.15% <100.00%> (+0.83%)
:arrow_up:

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 e60a5f1...03b0e3b. Read the comment docs.


MISSING_VAR not triggering for tags in script

The following code should trigger a MISSING_VAR on httpResponse, but does not.
/**
 * Some function
 * @call The value of the call
 */
public void function foo(
	required string call
)
{
	cfhttp(url="#variables.host#", port="#variables.port#", method="GET", timeout="30", result="httpResponse") {
		cfhttpparam(type="url", name="call", value="#arguments.call#");
	}
}

It triggers fine on the standard tag equivalent.

I implemented this in a "pseudo" fashion.  Jericho HTML Parsing in not extensible, so it is not trivial to combine both cfml and these cfscript tags as a single abstraction.  For now, CFLint generates cfml code for the cfscript 'tag'.  Seems to work well for basic cases like this.


run on save not working

Have set "formatOnSave": true in both the default and user settings...
Using the latest version, 4.3.2

Is the file you are trying to save using either CSS or SCSS syntax? If not you might want to have a look at the "scssSyntax" option.

Yes, they are .scss files.

File extension and file syntax are two different things. This plugin checks the file syntax (indicated in the bottom right corner of ST) in order to determine if it should run on save: https://github.com/dmnsgn/sublime-stylefmt/blob/master/Stylefmt.py#L24
Unless there is an error in your ST console, format on save cannot be triggered if the file syntax setting is wrong.

Ahh... that was it. My syntax is set to Sass. Updating this in the config did the trick.
Thank you!


Add Support for API Gateway Lambda authorizer

Is your feature request related to a problem? Please describe.

The API Gateway Resolver does not (appear) to support the ability to dispatch to a function as a Lambda authorizer.
Describe the solution you'd like

Add support to be able to dispatch to a function that is a Lambda authorizer.
Describe alternatives you've considered

Additional context

@gwlester  - this is getting a little closer to being done. The next PR is focusing on the HTTP api lambda authorizer and then finally Rest api lambda authorizer will be done.

https://github.com/awslabs/aws-lambda-powertools-python/pull/620

Now avaiable in 1.20.0 both for v1 and v2: https://awslabs.github.io/aws-lambda-powertools-python/latest/utilities/data_classes/#api-gateway-authorizer


fix: message highlight issue & mini context-menu issue

@jasperhuangg Please review.
Details

https://github.com/Expensify/App/issues/5197#issuecomment-917113461
https://github.com/Expensify/App/issues/5250#issuecomment-919356200
Fixed Issues

$ https://github.com/Expensify/App/issues/5197
$ https://github.com/Expensify/App/issues/5250
Tests | QA Steps

Open any chat.
Right-click on any message. When Context Menu is open, no mini menu is shown.
Now move to the empty area on the same message, right-click on that empty area(which is not covered by the context menu).
Click anywhere on the app. Context Menu should close.
Now hover back on the same message. The mini menu should be shown again.

Long press/click over any chat item,
Chat options like Copy to Clipboard or Mark as Unread. will be shown.
Choose any one of the options mentioned above.
Hover the cursor on another message.
Previous message should not be highlighted anymore.

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web | Desktop

https://user-images.githubusercontent.com/24370807/133478084-a476e34e-4f9b-45ad-830d-c4ad74400b80.mp4
Mobile Web

https://user-images.githubusercontent.com/24370807/133487236-9d28efd3-a646-49ae-870f-b768848b6fe0.mp4
iOS

Android

https://user-images.githubusercontent.com/24370807/133480956-80b9da2d-7aa2-46cd-9174-1c1b5187d731.mp4

It seems that there is still some sort of race condition between the callbacks. When trying to right click through multiple messages in a short period of time, we can still get in some weird state. It's a bit of an edge case, but it would be nice to fix it.
https://user-images.githubusercontent.com/22219519/133495918-84c9adad-6b46-4e18-9242-7a7ab4a82c70.mov

Sure, let me check this.

Hi @parasharrajat, I've placed this issue on hold as per this update, as we are prioritising issues related to a feature release scheduled for 9/24. As an apology for the delay, we will add a $100 bonus as a thank you for waiting.

@luacmartins I have handled three types of possible race conditions now. It is performing better.

When onHide callback was getting overridden, if a new context menu was opening.
When onHide callback (called after user has done some action) was getting overridden, if a new context menu was opening.
When the Previous instance of the menu is supposed to close with a delay(If happens when user click either copy to clipboard or mark unread), but it was closing the new instance if user opened a new context menu.

This is a tricky one. I'm still seeing the race condition. I'm not too sure how to solve those though. Do you have any more ideas?
https://user-images.githubusercontent.com/22219519/133801029-c99aa454-38c6-4740-9ffe-70c801bb6faa.mov

Hmm. Interesting! I specifically checked all callbacks and applied for the fix. I am not facing any with the new changes. But it does not mean that there are none. I will check again.

@parasharrajat Let me know when you're done fixing that race condition, or if you need some help investigating!

@jasperhuangg Yeah, I need your help to confirm if race conditions are still happening on this PR. I don't see them anymore. Maybe my computer is processing too fast.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

Hmm I thought this PR was on n6-hold and we should not merge it. Is that not the case?

🚀 Deployed to staging by @jasperhuangg in version: 1.1.1-9 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @timszot in version: 1.1.2-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


#146 - Fixed UNSAFE_componentWillReceiveProps

Fixed UNSAFE_componentWillReceiveProps by replacing with getDerivedStateFromProps

Thanks @im28!
I have only checked the examples in index.html and I don't think it is working :confused:. Did you try that at least those examples are working as expected?
BTW, you don't need to commit the generated files under the lib directory. They are automatically generated when a new version is released.

Hello, just want to know is it already fixed?


Bugfixes after switching to Thoas

Type

Bug fixes

Related JIRA Issue(s)

[x] https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-787 (checkbox styling in instant protein download component)
[x] https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-786 (missing blue reference protein bar)
[x] https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-788 (missing external references)

Highlights

using product.length rather than cds.protein_length as source of data for protein length
updated the types of external references to match Thoas schema

Deployment URL
http://bugfixes.review.ensembl.org
Views affected
Entity Viewer — protein view and external references in the sidebar

@azangru There's a conflict in src/ensembl/src/content/app/entity-viewer/gene-view/GeneView.tsx

@azangru Is this PR still a work in progress?

@azangru Is this PR still a work in progress?

No, it can be considered to be ready for review.


Swiss Canal 9/Kanal 9

Guide
https://iptv-org.github.io/epg/guides/ch.xml
Description
https://github.com/iptv-org/epg/commit/dcc87f67032d147ad16b780e86f0397ea476fc07 added some Swiss channels but there is an error with Canal 9 / Kanal 9. These are separate channels - Kanal 9 is the German language version and Canal 9 is the French one. Both have separate programming and the guides for both are available at https://tv.blue.ch/tv-guide
Both were in the database previously but I think Kanal9.ch has been deleted.
Canal9.ch has been added to the guide but is showing the EPG for Kanal 9 (the German version). Can you correct this to the French version and re-add the tvg-id and EPG for the German channel.

Fixed in https://github.com/iptv-org/epg/commit/30e22ef67796361456481eea8f3ea4cf5667432e
The German version now has the ID Kanal9.ch and the French Canal9.ch.


Clarify use of the :delete adverb for method .trans

The problem
This page provides only one example for .trans with :delete:
"a123b123c".trans('23' => '', :delete);                       # RESULT: «a1b1c»

I think it's not sufficiently clear what the :delete adverb does, since
"a123b123c".trans('23' => '')

produces the same output.
Suggestions
Two examples instead of just one would clarify the use of :delete:
"a123b123c".trans('23' => '4');                                # RESULT: «a144b144c»
"a123b123c".trans('23' => '4', :delete);                       # RESULT: «a14b14c»

Thanks! We'll handle it as soon as possible.


Compliance prometheus

Hello
i was working on the installation of the exporter for SNMP services, all works fine !
But is that any way to me prometheus compliant ?
Url format /probe?target=xxx generate failure on the config need to create a proxy rewrite rules to make it works..
Can the route /metrics can expose all data of all the snmp monitored system ? OR JUST changing the URL path to remove the parameter system and replace by /probe/TARGET_NAME ?
tanks you

Hi!
Prometheus calls this schema the multi-target exporter pattern: https://prometheus.io/docs/guides/multi-target-exporter/
You have to use relabeling to set the target.
The blackbox_exporter includes a short example config: https://github.com/prometheus/blackbox_exporter?tab=readme-ov-file#prometheus-configuration

Okay works fine, thank you. :)


Rename media to atomic

refs: https://github.com/facebook/draft-js/commit/0096d9873e5f7e98145c0a835a52a42f54003306

I'm good with the first commit, 1f0aee6, but why are we adding the compiled code to the repo?

Sorry miss... need dependecy from my production. is fixed

Now it's good :+1:

Thanks for the contribution. This looks good to me.


[DP0003] Missing docs in link

Problem/Concern

There are two links in this deliverable that lead to '404 mistake'. One link is 'dependent identity', second one 'independent identity'. Links are pointing into non-existent folder 'DP0003-laws-of-identity'. Most likely the mistake is in the relative path assigning.

Proposed Solution
Change the link to files in the original MarkDown file.

Links corrected


DOCSP-43159: QB returns objects

adds documentation to note that QB returns results as objects instead of arrays in v5
https://jira.mongodb.org/browse/DOCSP-43159
Staging
Checklist

[ ] Add tests and ensure they pass
[ ] Add an entry to the CHANGELOG.md file

This needs to be documented in the upgrade guide. This is a major breaking change.


update probes and add securityContext settings to address warnings

Addresses OSD-12964

updates the readiness and liveness probes to check that the AWS auth secrets exist otherwise it cannot create a VPC Endpoint, this should fail the pod before it tries to reconcile a CR.
since the type of creds required varies on STS or not, the check looks for both and passes as long as one of them is successful.
Adds security context configuration that explicity sets what appears to be defaults. This is to address warnings I saw on deploying to a 4.11 cluster.

W0906 15:50:34.753365   64831 warnings.go:70] would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "aws-vpce-operator" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "aws-vpce-operator" must set securityContext.capabilities.drop=["ALL"]), seccompProfile (pod or container "aws-vpce-operator" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
deployment.apps/aws-vpce-operator created

Looks good! We should also remove this code as a result of this change https://github.com/openshift/aws-vpce-operator/blob/main/main.go#L104-L111

Looks good! We should also remove this code as a result of this change https://github.com/openshift/aws-vpce-operator/blob/main/main.go#L104-L111

Yep, that makes sense to me. Changes pushed, thanks!

Codecov Report

Merging #56 (b9b798d) into main (123d4cf) will increase coverage by 0.36%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #56      +/-   ##
==========================================
+ Coverage   65.01%   65.38%   +0.36%
==========================================
  Files          23       23
  Lines        1069     1063       -6
==========================================
  Hits          695      695
+ Misses        293      287       -6
  Partials       81       81

Impacted Files
Coverage Δ

main.go
10.00% <ø> (+1.30%)
:arrow_up:

/lgtm
/approve


SimpleMigration

#10365
SimpleMigration, Multiple Fixes:

Correct eslint rules
Fix dummy test assertions
Correct linting
Upgraded sinon

jenkins test it

@varunsharma27  resolve conflict in .gitignore please

Are changes made, can this issue be closed @szydan

@varunsharma27 see Mikes question above

@szydan actually Varun said it's okay...just waiting for your approval after PR review changes made by him.


ViewPager child height is doubled in ScrollView

Bug
First of all, thank you for this great package.
ViewPager child's height is doubled (or so) when ViewPager is embedded inside a ScrollView. This affects the dynamic content's UI I am fetching from my API (e.g. I receive content of 300px height and the ViewPager scales to ~600px).
I don't know if this is a bug or normal behaviour, but I do want to know how to work around this issue without any marginBottom: -100% non-reliable code.
Here is a sample video from my app. Although, another interesting thing is that it doesn't double on first render, because I present an  while the content is downloaded, but it overextends just as I scroll to another page:

Environment info

react-native info output:
System:
    OS: macOS 10.15.4
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 13.8.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.4 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      Android NDK: 21.0.6113669
  IDEs:
    Android Studio: 3.6 AI-192.7<IP_ADDRESS>08749
    Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild
  Languages:
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.0 => 16.13.0
    react-native: ^0.62.0 => 0.62.0
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 3.3.0
Steps To Reproduce

Embed ViewPager (flex: 1) in ScrollView.
Add View (check its height with e.g. 'backgroundColor: 'red'`) with content that is bigger in size than the ViewPager (e.g. bigger than the screen).
Scroll to next page and see that the ViewPager increased in height way beyond its initial height is extended.

Describe what you expected to happen:

The children to not be stretched or to be stretched only as big as the ViewPager (not to overflow its height).

Reproducible sample code

import ViewPager from '@react-native-community/viewpager'
import React from 'react'
import { ScrollView, View } from 'react-native'

const CHILD_HEIGHT = 300

const ViewPagerHeightBug = (): JSX.Element => (
  <ScrollView>
    <ViewPager style={{ flex: 1, marginLeft: 16, marginRight: 16 }}>
      {Array.from(Array(2)).map((item, index) => (
        <View key={index.toString()} style={{ backgroundColor: 'red' }}>
          <View
            style={{
              backgroundColor: 'green',
              width: '100%',
              height: CHILD_HEIGHT,
            }}
          />
        </View>
      ))}
    </ViewPager>
  </ScrollView>
)

export default ViewPagerHeightBug

As you can see in this example, whatever the CHILD_HEIGHT we set, the ViewPager somehow doubles.

hey @teo029
I created a separate branch for your issue: https://github.com/react-native-community/react-native-viewpager/commit/44bbe9572ced59099ec9e568a80b6ed8923e95a4
And I could not reproduce it. Probably your issue is related to:
https://github.com/react-native-community/react-native-viewpager/issues/143#issuecomment-622272328
Could you remove this line https://github.com/react-native-community/react-native-viewpager/commit/44bbe9572ced59099ec9e568a80b6ed8923e95a4#diff-b081bed2305f7821e911f8a940431586L182 locally in your code and provide me a result of these change ?

Will be back with a response in around one week, but, for sure, I forked the project (some time ago) just to remove that line and saw the same problem. Will confirm later on, thank you.

I am not sure if this is related but may be, because something similar is happening to me.
Every time when my keyboard is going down, my screen getting "extra" space for short time and then jumping to original size, which looks like screen is jumping.
Downgraded to 3.3.0 for now.

Our component composition/styling is similar to this. I've tried disabling the forced absolute layout for ViewPager in the js api and set its style to flex: 1. After that, the container's height is getting set to the aggregate height of all the children pages. This makes sense to me, as they're all just children to the layout engine. Disabling visibility from js technically works, but breaks gesture/transition behaviors. Managing rendering for children natively probably can help alleviate this, but might be a bit challenging. 🤷

Disabling visibility from js technically works, but breaks gesture/transition behaviors.

Could you record this kind of behavior ? Because I did not notice this kind of behavior once I removed childrenWithOverriddenStyle

Managing rendering for container/children natively probably can help alleviate this, but might be a bit challenging. 🤷

I am wondering, how to create some kind of portal for those child views, because VP works differently from scrollview. ScrollView adds scrollable ability for all content inside Scrollview.
VP uses adapter to display each child view, hence all children should be painted in React Native. They must be measured and "transported" to adapter. It would be ideal scenario.

Ok, I retested the problem with v4.
I can reproduce this problem with both childrenWithOverriddenStyle:
Code:
/* eslint-disable */

import ViewPager from '@react-native-community/viewpager'
import React from 'react'
import { ScrollView, View } from 'react-native'

const CHILD_HEIGHT = 300

const ViewPagerHeightBug = (): JSX.Element => (
  <ScrollView contentContainerStyle={{ flexGrow: 1 }}>
    <ViewPager
      style={{
        flexGrow: 1,
        marginLeft: 16,
        marginRight: 16,
        backgroundColor: 'blue',
      }}
    >
      {Array.from(Array(1)).map((item, index) => (
        <View key={index.toString()} style={{ backgroundColor: 'red' }}>
          <View
            style={{
              backgroundColor: 'green',
              width: '100%',
              height: CHILD_HEIGHT,
            }}
          />
        </View>
      ))}
    </ViewPager>
  </ScrollView>
)

export default ViewPagerHeightBug

And without (with it removed):
/* eslint-disable */

import ViewPager from '@react-native-community/viewpager'
import React from 'react'
import { ScrollView, View } from 'react-native'

const CHILD_HEIGHT = 300

const ViewPagerHeightBug = (): JSX.Element => (
  <ScrollView>
    <ViewPager
      style={{
        marginLeft: 16,
        marginRight: 16,
        backgroundColor: 'blue',
      }}
    >
      {Array.from(Array(1)).map((item, index) => (
        <View key={index.toString()} style={{ backgroundColor: 'red' }}>
          <View
            style={{
              backgroundColor: 'green',
              width: '100%',
              height: CHILD_HEIGHT,
            }}
          />
        </View>
      ))}
    </ViewPager>
  </ScrollView>
)

export default ViewPagerHeightBug

With childrenWithOverriddenStyle removed I clearly see that the viewpager doubles in height with respect to my view. My problem is when having bigger CHILD_HEIGHT (800), it will go way beyond the screen's size. I need to find a way to make the ViewPager stop exactly at its container's height.
Without childrenWithOverriddenStyle:

With childrenWithOverriddenStyle:

Disabling visibility from js technically works, but breaks gesture/transition behaviors.

Could you record this kind of behavior ? Because I did not notice this kind of behavior once I removed childrenWithOverriddenStyle

Managing rendering for container/children natively probably can help alleviate this, but might be a bit challenging. 🤷

I am wondering, how to create some kind of portal for those child views, because VP works differently from scrollview. ScrollView adds scrollable ability for all content inside Scrollview.
VP uses adapter to display each child view, hence all children should be painted in React Native. They must be measured and "transported" to adapter. It would be ideal scenario.

re:portals: I wonder if the page views (children) need to be hoisted like they describe in the blog entry about InputAccessoryView. Also, I'm wondering if the PageView container itself needs to be a RCTRootView.
(See: https://stackoverflow.com/a/43195387 and FlexibleSizeExampleView.m)
(Note: if a RCTRootView is actually necessary, might make sense to have a separate pod solely responsible for sharing the bridge w/a singleton, if there isn't already one.) (Perhaps the lib could set the UIPageViewController or RCTRootView container height to the current page height or the max height of all containers. I tinkered a bit with using RCTRootView, but it's getting a bit late; not sure I'm using it correctly.

Regarding your reference to that issue, I didn't manage to make it work back then, because whichever height I told it to be, it still doubled or got out of bounds.
I don't understand what is causing this problem, but the only solution I've got right now is to fork a version where I removed the children= line.

I don't understand what is causing this problem, but the only solution I've got right now is to fork a version where I removed the children= line.

are you familiar with patch-package ? You can use it, to remove this line locally.

Wanted to give an update from comments the other day:
After looking at how views are being managed better, it appears hoisting is already being done here, just differently than RN core's approach. In the interim, I've worked around the container height issue by adjusting component composition/styling, initializing ViewPager with a static height, then using onLayout within each page view hierarchy. (Unfortunately this meant also identifying which children views would provide the correct height values and accumulating them.) Finally, once all height values are available, the container height is set to the max page height value.

I think this issue might be related to the issue I raised here at https://github.com/react-native-community/react-native-viewpager/issues/180, although I did patch the module locally to remove the children=.. line and my issue has been solved 🤔
What are the side effects of removing this line?

What are the side effects of removing this line?

TBH I don't know. It has been added before I started contributing to ViewPager. I can see, it causes some unexpected behaviour. Probably this prop should be called, once some kind of prop like "useLegacyOverriding" passed to View Pager component like below:
   <ViewPager
      style={{ flex: 1, marginLeft: 16, marginRight: 16 }}
      useLegacyProp={true}>
          ...
    </ViewPager>

By default, useLegacyProp will be false. Someone can change VP behaviour toggling  useLegacyProp

Ah, sadly I am still hitting this issue on even with the patch of removing children=.. from above. I am using it inside a Modal component, although I am not sure if this is messing it up.

My component looks something like this:
import Modal from "react-native-modal";

<Modal isVisible={display}>
  <ViewPager initialPage={0}>
    {slides.map((_, index) => (
        <View key={index}>
          <Text>Title goes here</Text>
          {buttons.map((_, index) => (
              <Button key={index} title="button text" />
            ))}
        </View>
      ))}
  </ViewPager>
</Modal>

So I have a ViewPager, with x amount of children which all have a View. Inside this View is a Text component, and y amount of buttons.

You can wrap a component with React.Fragment instead of removing childrenWithOverriddenStyle
import React, { Fragment } from 'react';

<ViewPager>
  <Fragment>
    <PageComponent />
  </Fragment>
</ViewPager>


Update RBD docker managed plugin to Luminous

This patch updates the Ceph packages in the RBD Docker managed plugin to
the Ceph Luminous release.
Fixes #1050

Codecov Report

Merging #1051 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1051      +/-   ##
==========================================
- Coverage    34.5%   34.47%   -0.04%
==========================================
  Files          36       36
  Lines        2901     2901
==========================================
- Hits         1001     1000       -1
- Misses       1796     1797       +1
  Partials      104      104

Impacted Files
Coverage Δ

libstorage/api/types/types_localdevices.go
84.93% <0%> (-1.37%)
:arrow_down:

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 3dce0e4...f13e5c6. Read the comment docs.


Latest generator

Summary

Use latest template and generator to auto-generate this.
Relevant Issue(s)

Checklist

[x] Summarized PR's changes in CHANGELOG.md
[x] Add example on converting JSON in README
[x] Do an integration test
[ ] Fix missing models in docs?

Not too sure how to handle missing models in docstring. The root problem is that the models don't have docstrings, so mkdocs hides them.
For example, the first model:
class AutoScale(BaseModel):
    class Config:
        extra = Extra.allow
        allow_mutation = False

    max_workers: Optional[int] = Field(
        None,
        description=(
            "The maximum number of workers to which the cluster can scale up when"
            " overloaded. max_workers must be strictly greater than min_workers."
        ),
    )
    min_workers: Optional[int] = Field(
        None,
        description=(
            "The minimum number of workers to which the cluster can scale down when"
            " underutilized. It is also the initial number of workers the cluster has"
            " after creation."
        ),
    )

This doesn't show in the docs because it's missing a docstring:

However, if I manually input a dummy docstring:
class AutoScale(BaseModel):
    """a"""

It shows up, but it doesn't include args.

I couldn't find a way to monkeypatch datamodel code generator, so I did a simple string replacement instead. Seems to work well:


Merge #412 into a separate branch called "atmos"

Could've just posted this as a comment in the PR.


REDIS_URL vs DJANGO_CACHE_URL

Here's a glitch:

In config.settings.production.py, we specify REDIS_URL.
In compose/django/entrypoint.sh, we specify DJANGO_CACHE_URL.

This is a conflict. REDIS_URL is a Heroku-ism, but on the other hand DJANGO_CACHE_URL might be too specific. I'm tossing this into @jayfk's court for the first pass at an answer to what value we should set and where.

That's a hard one. I prefer DJANGO_CACHE_URL because it describes the service (cache), not the product that is used (redis). Cookiecutter used this before 613b91d71e14639ca2cc514aa2473a9f5db09871. I believe that's the reason why the naming is not consistent here.
But I really have no strong opinion here, both are fine. If REDIS_URL works on heroku out of the box, then let's stick to it.


CMake: Add proper installation steps

This commit adds a few new CMake commands to get a proper installation
target.  The proper include path is not simply include/ but may be
system dependent.  As far as I know, using GNUInstallDirs is
recommended.
By using write_basic_package_version_file and
configure_package_config_file we get CMake files that can be installed
and can then be used in other projects.
With this change, you can do:
cd /path/to/tuplet
cmake -S . -B build
cmake --build build
cmake --build build --target install

The last step may require sudo if you haven't set
-DCMAKE_INSTALL_PREFIX="/path/to/install".
The system (or install directory) will now have a few more files:
├── include
│   └── tuplet
│       └── tuple.hpp
└── share
    └── tuplet
        └── cmake
            ├── tupletConfig.cmake
            ├── tupletConfigVersion.cmake
            └── tupletTargets.cmake

If you have another project, you can now require tuplet:
cmake_minimum_required(VERSION 3.14)

project(my_project LANGUAGES CXX)

find_package(tuplet REQUIRED)

add_library(my_project)
target_sources(my_project PRIVATE test.cpp)
target_link_libraries(my_project PRIVATE tuplet::tuplet)

And in your test.cpp you can easily include it:
#include <tuplet/tuple.hpp>

Furthermore, this commit moves helper.cmake into a new directory
cmake.  I've done this to group cmake files.
Also, a version is added, so that the find_package calls can also
require a specific version.
All of this is exactly what I'm using for my own header-only library. :)

Please let me know what you think. Other libraries such as Catch2 also allow users to simply include their git repository.
I haven't looked into that, though.
Regards,
Andre

Dear Andre,
Thank you so much for this pull request! I'd been meaning to improve the installation process for some time now, and it will be great to have tuplet configurable as a CMake package! I have two questions:

Could you update the project version to 0.9.0? This is a bit arbitrary, however the project is very near completion (it's just missing comparison operators and a few other small things), and once those are added it'll be changed to version 1.0.0!
Would there be any way to include cxx_standard_20 as part of the interface of the library, when it's used as a package? It would be really convenient if projects using the library were automatically targeted to C++20, since due to the use of concepts, the library itself requires C++20 to compile.

It's late here and I'm about to sleep, but I'll merge this in the morning!
Best,
Alecto

Could you update the project version to 0.9.0? This is a bit arbitrary, however the project is very near completion (it's just missing comparison operators and a few other small things), and once those are added it'll be changed to version 1.0.0!

Done. :)

Would there be any way to include cxx_standard_20 as part of the interface of the library, when it's used as a package? It would be really convenient if projects using the library were automatically targeted to C++20, since due to the use of concepts, the library itself requires C++20 to compile.

That is already the case because you have added it as an interface compile feature:
target_compile_features(
    tuplet
    INTERFACE
    cxx_std_20
)

Just tested it in a test project. :)

It's late here and I'm about to sleep, but I'll merge this in the morning!

Good night. :)
It's around 1pm here in Germany. :smile:


refactor(Algebra/Group): make IsUnit a typeclass

Also change some lemmas to assume [IsUnit _] instead of [Invertible _].
Motivated by potential non-defeq diamonds in #14986, see also Zulip

!bench

What's the situation where having this as a typeclass is useful? I agree that there are a handful of Invertibles in mathlib that might be better spelt IsUnit, but I don't see why we can't use (h : IsUnit x) in those places. What makes IsUnit typeclass-worthy when Prime is not?

For me, the main case is the instance [Field K] [CharZero K] : IsUnit (2 : K) (available via NeZero).

I don't understand what you mean; if you're writing theorems that take [IsUnit 2], can't you just write them to take (h : IsUnit 2)?

Why not let TC search find it for me?

Here is my personal opinion: any attempt to convert existing Prop/Type to class will break the old code using dot notation. Sometimes this will make existing code significantly longer.


minor fixes to workshop

Issue #, if available:
Description of changes:
Missing the following block in 3 notebooks.
---- ⚠ Un-comment and edit the below lines as needed for your AWS setup ⚠ ----
os.environ["AWS_DEFAULT_REGION"] = "<REGION_NAME>"  # E.g. "us-east-1"
os.environ["AWS_PROFILE"] = "<YOUR_PROFILE>"
os.environ["BEDROCK_ASSUME_ROLE"] = "<YOUR_ROLE_ARN>"  # E.g. "arn:aws:..."
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing this based on new updates and testing on the latest workshop - https://github.com/aws-samples/amazon-bedrock-workshop. Please do resubmit if it still exists in the new workshop.


The Original File Names are not fully visible if the File Names  are long.

Microsoft PowerToys version
0.49.0
Running as admin

[ ] Yes

Area(s) with issue?
PowerRename
Steps to reproduce
Perform a power rename on very long file names.  The Files in Scope are showed on the right hand side of the screen in a "Grid" like view. However the Column "Original" is too small and therefore on long file names the file names are cut.
✔ Expected Behavior
Column Original should be resizable.
❌ Actual Behavior
Column Original is not resizable.
Other Software
No response

I have experienced this issue also

PR #14365 would address some of this, would love to better see what your naming stuff.  Details / screenshots are critical so we can see real world scenarios

@niels9001 did your PR correct this?  I haven't done a full sweep yet with the new UX tweaks

@niels9001 did your PR correct this?  I haven't done a full sweep yet with the new UX tweaks

It made it better (as in, more space noe to show the filenames). However, columns are still not draggable so for very long names (or when resizing the window) the issue will persist.

@niels9001 thanks for the new implementation. It's much better now!


Migrate the bot to a dedicated account

[x] new username
[x] new credentials
[x] add bot as contributor to network subs
[x] figure out how to get past the new-user rate limit. maybe ask admins for an api exception.
[x] share the inbox to a private Discord channel via RSS
[x] change OC announcer to account for new username
[x] add reddit search RSS feed for posts mentioning the bot's username. Announce to Discord
[x] update AutoModerator configs to account for new username
- [ ] trackreddit.com for the new username

Done


Public fonts can't be resolved in CRA@4

Error: Can't resolve '/excalidraw-assets/FG_Virgil.woff2'

When importing<EMAIL_ADDRESS>in a CRA@4 app. See https://github.com/facebook/create-react-app/issues/9870
Haven't dug deep. Quick skim of CRA docs it seems they no longer allow referencing root/public paths from CSS files, though as per custom, it's not stated clearly anywhere so you have to read between the lines. Also, no mention in release notes.
For now, I hacked around this by adding the fonts into src/ and importing them from there, not using the fonts.min.css file from the package.
/cc @ad1992

Too many upvotes on the issue so might get fixed in CRA 🤞 . Lets wait for some time and can add a comment stating the font files will need to be added manually to the src folder if using CRA@4. WDYT?

Too many upvotes on the issue so might get fixed in CRA 🤞 . Lets wait for some time and can add a comment stating the font files will need to be added manually to the src folder if using CRA@4. WDYT?

I wouldn't hold my breath on that one. But we can amend the readme to include a workflow for CRA@4, yea.

I wouldn't hold my breath on that one. But we can amend the readme to include a workflow for CRA@4, yea.

closing this as this is fixed now in 0.2.1

closing this as this is fixed now in 0.2.1


OPCPublisher - no data published

Dear team
I am testing the OPC UA simulation, following this guide, however, even if the connectiivy seems in place, once the simulation starts, I do not see any message exchanged between the OPC simulator and the OPCPublisher.
My setup is:

Prosys UA simulator running locally on MacOS (M1 silicon)
Iot Edge Device in a Ubuntu 22 (ARM64) VM, still running on my laptop, setup made following this guide
OPCPublisher v2.8, as v2.9 could not start once deployed

No errors in the logs.
I then tried different combinations, like:

changed the VM to a Debian 11 ARM64 -> same result
changed the simulator to the OPC-PLC server -> same result

From this last test, here the logs (changed the ip to a placeholder):
[2024-01-06 20:56:45.349 INF OpcUa] TransportChannel RECONNECT: Reconnecting to opc.tcp://$server:50000/.
[2024-01-06 20:56:45.349 INF OpcUa] ChannelId 0: in Connecting state.
[2024-01-06 20:56:45.372 INF OpcUa] ChannelId 0: in Opening state.
[2024-01-06 20:56:45.373 INF OpcUa] ChannelId 0: Token #0 created. CreatedAt=20:56:45.373.  CreatedAt=20:56:45.430. Lifetime=3600000.
[2024-01-06 20:56:45.442 INF OpcUa] Security Policy: http://opcfoundation.org/UA/SecurityPolicy#None
[2024-01-06 20:56:45.442 INF OpcUa] Sender Certificate: (none)
[2024-01-06 20:56:45.442 INF OpcUa] ChannelId 3: Token #1 activated. CreatedAt=20:56:45.430. Lifetime=3600000.
[2024-01-06 20:56:45.442 INF OpcUa] ChannelId 3: in Open state.
[2024-01-06 20:56:45.442 INF OpcUa] ChannelId 3: Token Expiry 01/06/2024 21:56:45, renewal scheduled in 2699990 ms.
[2024-01-06 20:56:45.460 INF OpcUa] ChannelId 3: in Closing state.
[2024-01-06 20:56:45.462 WRN OpcUa] ChannelId 3: Force reconnect reason=BadConnectionClosed 'Remote side closed connection'
[2024-01-06 20:56:45.462 INF OpcUa] ChannelId 3: in Closed state.
[2024-01-06 20:56:45.462 INF OpcUa] ChannelId 3: CLIENTCHANNEL SOCKET CLOSED: 0369120D
[2024-01-06 20:56:45.463 INF Microsoft.Azure.IIoT.OpcUa.Protocol.Services.DefaultSessionManager] Creating session 'opc.tcp://$server:50000_83CF7F93' for endpoint 'opc.tcp://$server:50000'...
[2024-01-06 20:56:45.464 INF OpcUa] ChannelId 0: in Connecting state.
[2024-01-06 20:56:45.466 INF OpcUa] ChannelId 0: in Opening state.
[2024-01-06 20:56:45.466 INF OpcUa] ChannelId 0: Token #0 created. CreatedAt=20:56:45.466. Lifetime=3600000.
[2024-01-06 20:56:45.467 INF OpcUa] Security Policy: http://opcfoundation.org/UA/SecurityPolicy#None
[2024-01-06 20:56:45.468 INF OpcUa] Sender Certificate: (none)
[2024-01-06 20:56:45.468 INF OpcUa] ChannelId 4: Token #1 activated. CreatedAt=20:56:45.466. Lifetime=3600000.
[2024-01-06 20:56:45.468 INF OpcUa] ChannelId 4: in Open state.
[2024-01-06 20:56:45.468 INF OpcUa] ChannelId 4: Token Expiry 01/06/2024 21:56:45, renewal scheduled in 2699998 ms.
[2024-01-06 20:56:45.470 INF OpcUa] ChannelId 4: in Closing state.
[2024-01-06 20:56:45.473 WRN OpcUa] ChannelId 4: Force reconnect reason=BadConnectionClosed 'Remote side closed connection'
[2024-01-06 20:56:45.473 INF OpcUa] ChannelId 4: in Closed state.
[2024-01-06 20:56:45.473 INF OpcUa] ChannelId 4: CLIENTCHANNEL SOCKET CLOSED: 0396417E
[2024-01-06 20:56:45.483 WRN OpcUa] Certificate Validation failed. Reason=BadCertificateUntrusted. [CN=OpcPlc] [B8E6E8DD552504EA7DEE5BF28F2011A06C1450BE]
[2024-01-06 20:56:45.483 WRN Microsoft.Azure.IIoT.OpcUa.Protocol.Services.DefaultSessionManager] Accepting untrusted peer certificate B8E6E8DD552504EA7DEE5BF28F2011A06C1450BE, 'CN=OpcPlc' due to AutoAccept(UntrustedCertificates) set!
[2024-01-06 20:56:45.483 WRN OpcUa] Validation errors suppressed:  [CN=OpcPlc] [B8E6E8DD552504EA7DEE5BF28F2011A06C1450BE]
[2024-01-06 20:56:45.483 INF OpcUa] ChannelId 0: in Connecting state.
[2024-01-06 20:56:45.485 INF OpcUa] ChannelId 0: in Opening state.
[2024-01-06 20:56:45.486 INF OpcUa] ChannelId 0: Token #0 created. CreatedAt=20:56:45.486. Lifetime=3600000.
[2024-01-06 20:56:45.658 WRN OpcUa] Certificate Validation failed. Reason=BadCertificateUntrusted. [CN=OpcPlc] [B8E6E8DD552504EA7DEE5BF28F2011A06C1450BE]
[2024-01-06 20:56:45.658 WRN Microsoft.Azure.IIoT.OpcUa.Protocol.Services.DefaultSessionManager] Accepting untrusted peer certificate B8E6E8DD552504EA7DEE5BF28F2011A06C1450BE, 'CN=OpcPlc' due to AutoAccept(UntrustedCertificates) set!
[2024-01-06 20:56:45.658 WRN OpcUa] Validation errors suppressed:  [CN=OpcPlc] [B8E6E8DD552504EA7DEE5BF28F2011A06C1450BE]
[2024-01-06 20:56:45.669 INF OpcUa] Security Policy: http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256
[2024-01-06 20:56:45.669 INF OpcUa] Sender Certificate: [CN=OpcPlc] [B8E6E8DD552504EA7DEE5BF28F2011A06C1450BE]
[2024-01-06 20:56:45.669 INF OpcUa] ChannelId 5: Token #1 activated. CreatedAt=20:56:45.486. Lifetime=3600000.
[2024-01-06 20:56:45.669 INF OpcUa] ChannelId 5: in Open state.
[2024-01-06 20:56:45.669 INF OpcUa] ChannelId 5: Token Expiry 01/06/2024 21:56:45, renewal scheduled in 2699862 ms.
[2024-01-06 20:56:45.697 INF OpcUa] Revised session timeout value: 60000.
[2024-01-06 20:56:45.697 INF OpcUa] Max response message size value: 4194304. Max request message size: 4194304
[2024-01-06 20:56:45.710 INF OpcUa] Empty results were received for the ActivateSession call.
[2024-01-06 20:56:45.722 INF Microsoft.Azure.IIoT.OpcUa.Protocol.Services.DefaultSessionManager] Session 'opc.tcp://$server:50000_83CF7F93' created, loading complex type system ...
[2024-01-06 20:56:45.820 INF Microsoft.Azure.IIoT.OpcUa.Protocol.Services.DefaultSessionManager] Session 'opc.tcp://$server:50000_83CF7F93' complex type system loaded
[2024-01-06 20:56:45.820 INF Microsoft.Azure.IIoT.OpcUa.Protocol.Services.DefaultSessionManager] Azure IIoT opc.tcp://$server:50000_83CF7F93 took 00:00:00.3564188.
[2024-01-06 20:56:45.820 INF Microsoft.Azure.IIoT.OpcUa.Protocol.Services.DefaultSessionManager] Connected to 'opc.tcp://$server:50000'
[2024-01-06 20:56:45.820 WRN OpcUa] A smaller minLifetimeInterval 10000ms than session timeout 60000ms configured for subscription 0.
[2024-01-06 20:56:45.830 INF OpcUa] For subscription<PHONE_NUMBER>, Lifetime count was revised from 10000 to 3600
[2024-01-06 20:56:45.830 INF OpcUa] Subscription CREATED, Id=3176424674, LastNotificationTime=20:56:45, GoodPublishRequestCount=1, PublishingInterval=1000, KeepAliveCount=10, PublishingEnabled=False, MonitoredItemCount=0
[2024-01-06 20:56:45.831 INF Microsoft.Azure.IIoT.OpcUa.Protocol.Services.SubscriptionServices+SubscriptionWrapper] Added 3 monitored items to subscription '1000'/'opc.tcp://$server:50000_83CF7F93'
[2024-01-06 20:56:45.881 INF Microsoft.Azure.IIoT.OpcUa.Protocol.Services.SubscriptionServices+SubscriptionWrapper] Now monitoring 3 nodes in subscription '1000'/'opc.tcp://$server:50000_83CF7F93'
[2024-01-06 20:56:45.885 INF OpcUa] Subscription PUBLISHING ENABLED, Id=3176424674, LastNotificationTime=20:56:45, GoodPublishRequestCount=1, PublishingInterval=1000, KeepAliveCount=10, PublishingEnabled=True, MonitoredItemCount=3
[2024-01-06 20:56:45.885 INF Microsoft.Azure.IIoT.OpcUa.Protocol.Services.SubscriptionServices+SubscriptionWrapper] Subscription '1000'/'opc.tcp://$server:50000_83CF7F93' state actual(revised)/desired: PublishingEnabled True/True, PublishingInterval 1000/1000, KeepAliveCount 10/10, LifetimeCount 3600/10000
[2024-01-06 20:56:45.885 INF Microsoft.Azure.IIoT.OpcUa.Protocol.Services.SubscriptionServices+SubscriptionWrapper] Set monitoring to Reporting for 3 items in subscription '1000'/'opc.tcp://$server:50000_83CF7F93'.
[2024-01-06 20:56:46.900 WRN Microsoft.Azure.IIoT.OpcUa.Protocol.Services.SubscriptionServices+SubscriptionWrapper] DataChange for subscription '1000'/'opc.tcp://$server:50000_83CF7F93' has unexpected sequenceNumber 1 vs expected 118, publishTime 01/06/2024 20:56:46
[2024-01-06 20:56:56.748 INF Microsoft.Azure.IIoT.OpcUa.Edge.Publisher.Engine.DataFlowProcessingEngine]
  DIAGNOSTICS INFORMATION for          : opc.tcp://$server:50000_83CF7F93
  # Ingestion duration                 :    00:00:12:00 (dd:hh:mm:ss)
  # Ingress DataChanges (from OPC)     :            498 (All time ~0.69/s; 14 in last 60s ~0.23/s)
  # Ingress ValueChanges (from OPC)    :          1,494 (All time ~2.07/s; 42 in last 60s ~0.7/s)
  # Ingress BatchBlock buffer size     :              0
  # Encoding Block input/output size   :              0 | 0
  # Encoder Notifications processed    :          1,494
  # Encoder Notifications dropped      :              0
  # Encoder IoT Messages processed     :            497
  # Encoder avg Notifications/Message  :              3
  # Encoder avg IoT Message body size  :            629 (0%)
  # Encoder avg IoT Chunk (4 KB) usage :            0.2
  # Estimated IoT Chunks (4 KB) per day:         59,639
  # Outgress Batch Block buffer size   :              0
  # Outgress input buffer count        :              0
  # Outgress input buffer dropped      :              0
  # Outgress IoT message count         :            497 (0.69/s)
  # Connection retries                 :              2
  # Opc endpoint connected?            :           True
  # Monitored Opc nodes succeeded count:              3
  # Monitored Opc nodes failed count   :              0

The container create option configuation set in the portal is:
{
    "Hostname": "publisher",
    "Cmd": [
        "publisher",
        "--PkiRootPath=/mount/pki",
        "--pf=/appdata/pn.json",
        "--mm=PubSub",
        "--me=Json",
        "--fd=false",
        "--bs=100",
        "--bi=1000",
        "--aa",
        "--ll verbose"
    ],
    "HostConfig": {
        "Binds": [
            "/var/iiotedge:/appdata"
        ],
        "CapDrop": [
            "CHOWN",
            "SETUID"
        ]
    }
}

And the content of the pn.json file (as simplified version of what proposed by the opc-plc simulator):
[
  {
    "EndpointUrl": "opc.tcp://$server:50000",
    "UseSecurity": false,
    "OpcNodes": [
      { "Id": "nsu=http://microsoft.com/Opc/OpcPlc/Boiler;i=6211" },
      { "Id": "nsu=http://microsoft.com/Opc/OpcPlc/Boiler;i=15013" },
      { "Id": "nsu=http://microsoft.com/Opc/OpcPlc/;s=StepUp" }
    ]
  }
]

And the route is set as:
"routes": {
    "publisher": {
        "route": "FROM /messages/modules/publisher/* INTO $upstream"
    }
}

Any help would be greatly appreciated. Thank you.

The logs show that data is flowing between plc and publisher:  # Ingress ValueChanges (from OPC)    :          1,494 (All time ~2.07/s; 42 in last 60s ~0.7/s).  Is the issue that you do not see data in IoT Hub?  Here also # Outgress IoT message count         :            497 (0.69/s) shows data flowing to edgehub.  Routes and configuration look ok.

Hi Marc
exactly, I do not see any data in IoTHub: I have plugged an eventhub + ADX to the IoTHub and it is basically writing empty rows:

Can you use the az cli to monutor the the iot Hub messages?.  I would like to exclude the hub to add part here first given that data is published...

Here the output, no results:
az iot hub monitor-events --hub-name $iothub Starting event monitor, use ctrl-c to stop...

Have you looked at the logs of EdgeHub and EdgeAgent inside the IoT Edge installation?  Do you seen any errors?

I have follow the troubleshooting page but everything seemed ok. I then removed the event-hub, added a route to storage and then I was able to see the data saved as json. I then rebuilt the route to event-hub + ADX, new ingestion and now it is working there too. Frankly I am not sure what was wrong, anyhow good it works.
Thanks Marc for the support.
One thing that still I cannot do is to see the messages via az cli (or Iot explorer): is this related to the $default consumer group being already busy (I am using the free iothub)?


[BUG] Service does not process function block info notifications from a MIDI 2.0 UMP USB device

Describe the bug
When a device sends a Function Block Notification request, after the initial enumeration process after insertion of the device, the Windows MIDI service does not seems to process it. This case is when non-static function blocks are used.
To Reproduce

Send a response upon enumeration after insertion of the device:

F0118633 08020101 00000000 00000000 Stream (0F) Function Block Info Notification Complete, Block 6 , Active Yes, UI Hint 03h, m1.0 00h, Direction 03h, First Group 8, Number of Groups 2, MIDI-CI Version 0001h, Sysex8_Streams 1

After some time send an info notification from the device to the host:

F0118633 08050001 00000000 00000000 Stream (0F) Function Block Info Notification Complete, Block 6 , Active Yes, UI Hint 03h, m1.0 00h, Direction 03h, First Group 8, Number of Groups 5, MIDI-CI Version 0000h, Sysex8_Streams 1

check midi.exe  ep props. The groups did not change

Expected behavior
According to page 37 of UMP 1.1.1. a device can send a info notification. Groups should be increased after receiving the info notification
Installer Name or Version
DP7 , Driver: <IP_ADDRESS>
Desktop

OS:  Windows 11  Pro Canary, Insider preview:   27754.1000

Device information, if this is with an external MIDI device:
Yes, custom
Application Information
N/A
Additional context
B.T.W the UMP 1.1.1 specification does not define an "ACK" or "NACK". As such the device actually does not know if the service really has processed the requests. An option could be for a device to send a info request to the host to get the function block data, but it appears this UMP message is only defined as host to  device....

Strangely after a reboot of Windows 11 this now worked.

As requested.


add note icon to all pages

Per Kirill, the challenge is that only the Bootstrap pages have the note icon to let users add feedback. So I added the note icon for feedback on other pages by adding:
  in .component.html files, and
import {FeedbackModule} from "../../feedback/feedback.module";  in .module.ts file, also add
@NgModule({
imports: [..., FeedbackModule],
in .module.ts file

Good stuff!


In which version dvr of fip port forwarding is implemented

hello, I used kolla-ansible to deploy openstack yoga and victoria with ovn banckend. And I create floating ip port forwarding. But I found that, in yoga, the  port forwarding traffic flows directly from compute nodes.  In victoria, the  port forwarding traffic still goes through network nodes
I would like to ask, is this related to the neutron version, or is it caused by a different ovn version?
the ovn version in yoga is 22.06.1, and the ovn version in Victoria is 20.03.2

I think this is related to how OVN is deployed so it's probably best to discuss with the kolla-ansible folks


CI Checks for Mimir Alerts

Motivation
The new mimir setup for our observability platform leads to new requirements for our alerts, like adding the cluster identification, since now it's centrally managed from the MC and no longer directly from the WC. In order to make sure alerts are still working as expected and improve not just the migration process but the user experience creating alerts we should add an CI check making sure all newly created alerts fit to this new requirements.
Todo

[ ] Create a CI check for alerts with mimir which checks if all the requirements for mimir alerts are met. Relevant requirements:

The cluster id
...

Outcome

We have early feedback loops giving us initial feedback in the PR if an Alert might work or break on Mimir.

We need 4 labels:

cluster_id
installation
pipeline
provider

Can we check that we have those without spending a month building a script? Can we use promtool (validation) for this?
Can we use a simple awk command ? (if there is a by, the labels should be there) but we do not validate aggregations without by in there?

Looking what we can do with pint

@hervenicol what's the progress here? Would be really good if we can get this issue closed fast, since it's blocking any alert review of giant swarm teams and thus our mimir rollout :)

@hervenicol what's the progress here? Would be really good if we can get this issue closed fast, since it's blocking any alert review of giant swarm teams and thus our mimir rollout :)

Should be good now @Rotfuks .
All PRs are merged, and documentation is here: https://github.com/giantswarm/prometheus-rules#prometheus-linter


feat(docker): add mongo_db_plugin support to docker

Make Docker image support mongo_db_plugin.
Reference the options from the script https://github.com/EOSIO/eos/blob/master/scripts/eosio_build_ubuntu.sh

HI, I got a problem when i build docker image. those error message are below:
CMake Error at plugins/mongo_db_plugin/CMakeLists.txt:22 (find_package):
  By not providing "Findlibbsoncxx-static.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "libbsoncxx-static", but CMake did not find one.

  Could not find a package configuration file provided by "libbsoncxx-static"
  with any of the following names:

    libbsoncxx-staticConfig.cmake
    libbsoncxx-static-config.cmake

  Add the installation prefix of "libbsoncxx-static" to CMAKE_PREFIX_PATH or
  set "libbsoncxx-static_DIR" to a directory containing one of the above
  files.  If "libbsoncxx-static" provides a separate development package or
  SDK, be sure it has been installed.

I found the problem was the option -> "-DBUILD_MONGO_DB_PLUGIN=true". when I removed this, then image can built succeeded. I'm not sure do this only happen on my machine or it's a problem that need fix it.

@masato25 hello, You should update/rebuild your eosio/builder, then build the docker.

@Akagi201 thanks for your response.
yes, if i run docker-compose build builder first, then do docker build . -t eosio/eos. the problem is solved.

@masato25Your ideas also works for me, but whether there is any bad effect ...?!


Update UG for list command

Updated the user guide for the list command, labelled group related commands as [NOT READY]

Codecov Report

Merging #49 (9e7080c) into master (7b06cf7) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #49   +/-   ##
=========================================
  Coverage     52.09%   52.09%
  Complexity      463      463
=========================================
  Files            89       89
  Lines          2102     2102
  Branches        265      265
=========================================
  Hits           1095     1095
  Misses          927      927
  Partials         80       80

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 7b06cf7...9e7080c. Read the comment docs.


Correct CurlLogger's URL to actual destination

Description
The CurlLogger hardcodes http://localhost:9200. This change instead uses the given configuration values.
Issues Resolved
n/a
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dekimsey Thank you for this change! Can you please rebase and get in the latest changes from main?

Sorry for not seeing your request @dblock, it has been a busy year and I missed your request. I'm updating it now. I also fixed the tests to validate the change.

@VachaShah I believe this is complete now. Let me know what you think, thank you for pinging me on this!

Apologies for having missed this. I resolved the CHANGELOG conflict, let's merge this once CI passes.


The initial height for .half doesn't fit many screens. How to dynamically implement it?

Description : For the FloatingPanelLayout class, I am trying to override and implement an initial height. Although .full and .tip work gracefully. The .half doesn't fit many screens halfway. Is there a way to implement this dynamically?
Expected behavior
Actual behavior
Steps to reproduce
Code example that reproduces the issue
How do you display panel(s)?

Add as child view controllers
Present modally

How many panels do you displays?

1
2+

Environment
Library version
Installation method

CocoaPods
Carthage
Swift Package Manager

iOS version(s)
Xcode version

There are instructions for how to do this in the README.

Thank you, @warpling!


[NGINX]: Rewrite annotation adding trailing slash

Hi,
I'm seeing an odd behavior where using the rewrite annotation, a trailing slash is appended to the end of the path.  Here's my YAML:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    ingress.kubernetes.io/rewrite-target: /app/webapi
  name: rewrite
  namespace: dev
spec:
  rules:
  - host: foo.bar.com
    http:
      paths:
      - backend:
          serviceName: app
          servicePort: 8080
        path: /webapi

Here's what I'm seeing in nginx.conf
server {
        server_name foo.bar.com;
        listen 80;
        listen [::]:80;
        set $proxy_upstream_name "-";
        location ~* ^/webapi\/?(?<baseuri>.*) {
            set $proxy_upstream_name "upstream-default-backend";

            set $namespace      "dev";
            set $ingress_name   "rewrite";
            set $service_name   "";

            port_in_redirect off;

            client_max_body_size                    "1m";

            proxy_set_header Host                   $best_http_host;

            # Pass the extracted client certificate to the backend

            # Allow websocket connections
            proxy_set_header                        Upgrade           $http_upgrade;
            proxy_set_header                        Connection        $connection_upgrade;

            proxy_set_header X-Real-IP              $the_real_ip;
            proxy_set_header X-Forwarded-For        $the_real_ip;
            proxy_set_header X-Forwarded-Host       $best_http_host;
            proxy_set_header X-Forwarded-Port       $pass_port;
            proxy_set_header X-Forwarded-Proto      $pass_access_scheme;
            proxy_set_header X-Original-URI         $request_uri;
            proxy_set_header X-Scheme               $pass_access_scheme;

             # mitigate HTTPoxy Vulnerability
            # https://www.nginx.com/blog/mitigating-the-httpoxy-vulnerability-with-nginx/
            proxy_set_header Proxy                  "";

            # Custom headers to proxied server

            proxy_connect_timeout                   5s;
            proxy_send_timeout                      60s;
            proxy_read_timeout                      60s;

            proxy_redirect                          off;
            proxy_buffering                         off;
            proxy_buffer_size                       "4k";
            proxy_buffers                           4 "4k";

            proxy_http_version                      1.1;

            proxy_cookie_domain                     off;
            proxy_cookie_path                       off;

            # In case of errors try the next upstream server before returning an error
            proxy_next_upstream                     error timeout invalid_header http_502 http_503 http_504;
            rewrite /webapi/(.*) /app/webapi/$1 break;
            proxy_pass http://upstream-default-backend;

        }

Is this the expected behavior?  I'm expecting location ~* /webapi ?  I've tried several of the latest nginx controller versions and they all behave the same way.
Thanks.

Seems related to https://github.com/kubernetes/ingress/issues/1260

/reopen

This issue is still around


Planning: Define functional and non functional requirements for MVP 2

What:

I need to define the functional requirements for my project
I need to define the non-functional requirements for my project
I need to define the MVP 2 for my project

How:

By writing them in the comments of this ticket

Why:

To enable me to deliver the second MVP of my project
To ensure I keep track of my progress and keep on target
To aid in ticket writing

MVP-2

Adding Map rendering to page
Use long/lat in api response to plot on map
Keep table from MVP 1
Fully styled frontend including:

Reactive Nav bar
styled input component
Map and table styled appropriately (TBC)

Consider migration from SPA model - Note this only has to be considered, not implemented


Car following model

which car following model did you use?
and what about the lane change strategy?
If users want to revise Car following model or lane change model, how to do it?

you can use sumo or others software to do this. Please see  Co-simulation in tutorials


3/29 Code for Boston agenda

Last week: #208 (comment).
Review priorities (umbrella issues):

current: finish Student profile improvements

???

next: Productionize visualizations of STAR academic progress
after: SPED referral form

Help finish what's in progress:

Finish any work-in-progress you own
Help anyone else with work-in-progress if you can (keeping in mind that sometimes piling on more people doesn't help)
Check out work that's left over from last week.
Check open pull requests
Umbrella issues - see if there's a clear piece you can get done on one of the open issues

Start some new work:

Fix an Open bug
Start on a help wanted issue
Start a brand new feature
Talk it out with Kevin if you have questions or if you're stuck

Help new folks pitch in:

Coordinating tonight: @erose
Talk about any questions from the project overview
Help them set up development environment
Show them the agenda issue and our workflow

Questions for Kevin:

@erose Thanks for adding this!  I added #249 to capture an answer to your question about keyboard navigation too.

Also, I think if there's no new input then it's reasonable to use the same product prioritization from the last week. :)


multi-storage ?

you tried to use LevelDB (from google, that already include snappy) in place of LMDB ?
https://github.com/google/leveldb

I thought about it, but no I didn't. LMDB's benchmarks (http://symas.com/mdb/microbench/) are interresting. It seems that LevelDB is faster on writings but LMDB is a lot faster on reading operations.
My guess is that data are read more often then written.

https://influxdb.com/blog/2014/06/20/leveldb_vs_rocksdb_vs_hyperleveldb_vs_lmdb_performance.html
sure that lmdb more faster on read ? on this benchmark is not so clear....
and http://symas.com/mdb/ondisk/
leveldb use natively snappy, that you've added on your server !
and not all need more read that write depend on application need...
this while be interesting to make plugable the storage engine...

Maybe. I'll take a look at the complexity, because each engine has different functionnalities and a different API...


reCaptcha or simply Captcha

Just wondering if there is any way to reduce spams by putting some challenge questions? What about reCaptcha?
Thank you.

This is not under the scope of this gem. We might consider in future if there are more requests.


scheduler(ticdc): evenly distribute tables for drain capture

What problem does this PR solve?

Issue Number: ref #4757
What is changed and how it works?
Evenly distribute tables for drain capture, it smoothes loads of each capture.
Check List
Tests

Unit test
Manual test (add detailed scripts or steps below)

This PR
master

Questions
Will it cause performance regression or break compatibility?
No
Do you need to update user documentation, design documentation or monitoring documentation?
No
Release note
None

/merge

/run-all-tests


Project blacklist.

Add to the settings a blacklist for block what project don't want to show in the rich presence.

I think they meant when they are editing things inside a "blacklisted" project the rich presence does not show on your profile

Closing this since theres no activity.

Closing this since theres no activity.


Jolt enabled project fails to export in CICD

Problem Description
I started setting up a gitlab CICD pipeline today for a small project I've got that uses Jolt and ran into some issues preventing my pipeline from successfully completing. This seems to be due to running from command line when the .godot folder is not present.
Context
Due to some of the current godot engine oddities godot must be launched once which triggers an import of all assets and libraries (as the .godot folder shouldn't exist) from there another godot run should be launched  that actually does the compiling.
I setup my pipeline but it kept hanging during the initial empty run. The command that needed to run was godot -v -e --quit --headless (again on a machine with no .godot folder). I was also able to reproduce this locally and did confirm that this indeed only happened when running projects with godot-jolt.
Steps to reproduce

Setup a new godot 4.2 project
Add the godot-jolt package and enable it
Delete the .godot folder
from a linux terminal run godot -v -e --quit --headless

I haven't been able to figure out any workarounds here, but if I find some time I might dig a bit more into what's going on (no promises though :) )

and did confirm that this indeed only happened when running projects with godot-jolt

I don't believe this is specific to this extension, and likely happens with any GDExtension.
This is almost certainly because you don't have an extension_list.cfg when you start up a project fresh for the first time, i.e. without a .godot folder.
If (before running Godot) you create a .godot/extension_list.cfg file containing a single line, like this:
res://addons/godot-jolt/godot-jolt.gdextension

It should be able to load the extension right away without needing a restart first.
Some people even commit this file into their source control, which should be fine I guess, since it's not really transient/temporary/local in the same way that much of the other stuff is in that folder.
Anyway, please confirm whether this fixes the problem for you.

omg this should be documented somewhere! just hit this problem and thanks god there was an issue with this info

For what it's worth this limitation of needing the extension_list.cfg has been removed from Godot as of godotengine/godot#93972 (i.e. Godot 4.4).


Rename missed files

@potatoqualitee Sent you vai DM in Slack the updated manifest files with what I found missing.
Changes proposed in this pull request, renamed a few more files

Just renamed the file CsvSqlImport.ps1 to match function name -> Import-DbaCsvToSql (also added Dba prefix to function name).
Rename of internal function vai manifest update Chrissy had done: Invoke-Dbacmd2 -> Invoke-DbaCmd (no reason to put the "2" since it is our version of the command now).
Renamed Get-DbaServerAuditSpecification -> Get-DbaSqlAuditSpecification
Renamed Get-DbaAudit -> Get-DbaSqlAudit

The last two are to simply match up to what we named the copy functions of the same objects.
How to test this code:

[ ] No code changes just renames.

Thanks so much @wsmelton !
In addition to renaming Invoke-DbaSqlcmd, can you also update the pester names? They are causing failures.


Missing detection

The algorithm does not detect following coplanar triangle triangle intersection:
https://lokiresearch.github.io/fast-triangle-triangle-intersection/build/demo/

Thank you very much for reporting this issue.
I think I've solved the problem, I added more tests to be sure.
If you find another case with an issue, please let me know!


expose to Terraform function_name

Feature proposal
expose to terraform (via "apex infra") the lambda function name
Description
Apex compute the AWS lambda function names using the nameTemplate with default {{.Project.Name}}_{{.Function.Name}}.
For example in a project “api” with ./functions/users becomes api_users.
The new exposed variable could be apex_function_name_NAME.
In the example above we could then reference the function name in terraform as ${var.apex_function_name_users}
If this feature is accepted I will open a pull request.

Hmm we do apex_function_%s for the ARN, so I guess maybe apex_function_%s_name? Reads a little weird haha, feels redundant but it's not

Ok, it seems better!
I will open a pull request.

Sounds good! I wonder if we should have apex_function_%_arn to slowly phase out the old one as well, not a build deal for this PR though

Yes, that could be a better naming convention now that we have more than one variable.
If you want I can open also one pull request to add apex_function_%_arn leaving there the old one (commenting it is deprecated)

oops thought it was open


trivial fix to documentation

add "cd prompts-ai" before "yarn install".
I knew better, but did it anyway...

I can't get this to work at all


Updated notebook openai_functions_agent.ipynb

Here's the updated code with grammatical improvements, added comments, and placeholders for users to add their API keys and customize the notebook for their specific use cases.
Linked to issue #6178

@sumanthdonthula thanks for the contribution! Looking good!
I'm wondering if we could paraphrase the "train" word in this sentence:
"The agent will be trained to perform 3 search functionalities with the respective tools"
There is no training in the machine learning sense. Maybe something alone the lines that  "the agent is given access to 3 tools or something of that nature"

Hi @eyurtsev,
Sorry, made changes. Thanks for the suggestion. Now the sentence looks like,
The agent is given ability to perform 3 search functionalities with the respective tools.

@eyurtsev can you please validate the code now and approve the PR.


New version: CmdStan v5.2.1

Registering package: CmdStan
Repository: https://github.com/StanJulia/CmdStan.jl
Created by: @goedman
Version: v5.2.1
Commit: ea94459fdcefebcd62db5b3008912c61e94d8a2b
Reviewed by: @goedman
Reference: https://github.com/StanJulia/CmdStan.jl/issues/60

Your new version pull request met all of the guidelines for automatic merging.
I will automatically merge this pull request during the next cron job.
If you want to prevent this pull request from being auto-merged, simply leave a comment.
(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

[noblock]


Project #1 Create a hello world web application with bottle.py

https://bottlepy.org/docs/dev/tutorial.html

done


Feature: Add a variable type that will point to an Ansible inventory

Related to
Web-Frontend (what users interact with)
Impact
major improvement to user experience
Missing Feature

Having the option for a variable type that offers a dropdown list based on an Ansible inventory would be extremely beneficial. This feature would reduce the number of locations that need to be updated when updating an Ansible inventory. Specifically, when Ansible scripts are designed to allow users to execute scripts on specific computers.
Implementation
The inventory should be pulled regularly in the background, ensuring that users always have access to the latest inventory when executing playbooks from Semaphore. Initially, it would be useful to display all hosts in the inventory. For future enhancements, the ability to filter and display only PCs from specific groups would be ideal.
Design
No response

I like this idea.  I am trying to come up with a way for my DevOps users to easily select a single machine to run a playbook against without asking them to add CLI Args of ["-l", "host-name-of-server"]


Question: any solid CMS using Nuxt?

Is there a solid CMS out there thats built using Nuxt?  Needs to be SEO friendly, still fun to develop with, and have good page editing tools in the admin/backoffice.
P.S. If there isn't a good option out there, is anyone interested in starting a project to create one?

I've decided to take the headless CMS approach like https://getdirectus.com/

Hi @derekshull,
Actually, the closest project to answer your question from the community is Nuxtent.

I believe @medfreeman, one of the maintainers of nuxtent, is working on something similar to this: https://github.com/medfreeman/nuxt-netlify-cms-module

If you need headless CMS, there is also CosmicJS with an example with Nuxt.js: https://github.com/cosmicjs/nuxt.js-website

In my team, we use another (french) headless CMS : https://prismic.io/

@derekshull I am currently developing a CMS based on Nuxt, Vuetify and graphql + graph.cool. If you are interested send me a PM

I really which I can find this near perfect API-Based CMS which works hand in hand with NUXT.
Because for me NUXT is truly amazing and nearly perfect to work with!
But I have been really stuck on this same backend dilemma for some time now.. trying to find something modern and open-source , at the same time self-hosted and cheap to host!
I guess there are many great CMSes out there like Cosmicjs, Prismic, Contentful, Contentstack, ButterCMS, GraphCMS, Storyblock, Sanity, etc.. these are the usual recommended CMSes most of the time for NUXT but for someone like me who focuses mainly on small businesses who are not willing to pay lots of money for a host then none of these are an option for me!
So is there any self-hosted headless CMS, api-driven and open-source that would work great with Nuxt ?
I have played around with Directus and Cockpit's latest version..
And I was impressed with Cockpit and liked it much more than Directus..
Both are open source and self hosted and API driven.
The problem with both for me that you can only use their control panels to add the content models and fields, I just prefer having the option to do this in code like in Json or yaml.
Also not much of documentation for Cockpit but it is under heavy development so keep your eyes on it!
I usually use OctoberCMS for my typical none Nuxt projects.. I love this CMS and its easy workflow.
October which is a Laravel 5.5 based can be used as a headless CMS and with some tweaks, it can become a great CMS to use with Nuxt.. the only thing it is not made to be used as a headless CMS.
So anyway for PHP based CMS I would vote for Cockpit or even OctoberCMS.
if we only could take from the two and makes them ONE! :(
Now if money is not a issue for you to host NodeJS and want a Nodejs based CMS which is also open source as well then my vote would easily go for STRAPI.
Their version 2 is still in beta as well but its workflow is a beauty and more than simple!
I believe many would enjoy working with Strapi..
I would really love to see how other people think about all this!
We really need a backend/CMS which is free or at least not expensive and self-hosted!

Anybody heard of Craft 3? They're vamping up their content API w/ the release of 3. Their content editing and structuring experience for both users and devs has always been 👌🏻. I'd be really curious to see an integration with Nuxt…

@justin-schroeder @derekshull
What about having something like ng-admin and Admin on rest but built with NuxtJS.
This approach makes perfect sense for quicker development and for decoupling frontend from the backend. As for the backend, one can choose whichever backend framework they like. Let it be AdonisJS, Express, Laravel, Slim or whatever to build the RESTful API.

anyone already played around with strapi.io? their roadmap seems promising…

@justin-schroeder like wagtail (Django-based CMS framework, which can be used headless) but for nuxt.

it'd be best if this nuxt-cms is serverless!

I came across a very promising open source headless CMS which is relatively new called Daptin
The CMS seems easy to work with and addresses many of the points I made earlier like using YAML or JSON to define the schema.
What do you guys think? anyone of you used it?
Key Features

JSON APIs

create, read, update, delete

GraphQL APIs

work in progress

Client libraries for all platforms
Rich data types
Websocket support
Sub sites hosting
Oauth token and connections
Cloud storage sync
Action APIs and Relational data APIs
Validation and conformation support
Daptil will expose all APIs for easy use
Fully featured dashboard

Responsive to desktop, mobile and table

Cross platform

Windows, Mac and Linux ready.

Daptin is an open-source backend development framework to develop and deploy production-ready JSON API based applications. With Daptin you can design your data model and have a production ready JSON API online in minutes.

Relational database backed persistent data
CRUD JSON API
User registration and login system
Social login with oauth2: tested with google, github, linkedin
Extensive state tracking APIs
Enable Data Auditing from a single switch
Market place enabling a variety of features
Cloud storage sync like gdrive, dropbox, b2, s3 and more
Manage multiple websites under separate sub-domain/sub-paths
Connect with external APIs by using internal extension points
Database to easily evolves your data schema & migrates your database [Postgres/MySQL/SQLite]
Flexible auth using the JWT-based authentication & permission system
Works with all frontend frameworks like React, Vue.js, Angular, Android, iOS
Very low memory requirement and horizontally scalable
Can be deployed on a wide range of hardware arm5,arm6,arm7,arm64,mips,mips64,mips64le,mipsle (or build for your target using go)

Tech stack

Backend
Frontend
Standards
Frameworks

Golang
BootStrap
RAML
CoPilot Theme

Api2go

JsonAPI
VueJS

rclone
grapesJs

Element UI

Because this issue seems to be inactive for quite some time, I'll close it now. If you feel like it deserves some attention because it's not fixed, feel free to ping me and I'll reopen it.


The moving event fires forever

When initiating a touch, the moving event fires continuously as I move around. It continues to fire after I end the touch. Should the moving event listener be removed at end?

Is there any troubles if the moving event still bound?

It wouldn't make unnecessary calls to the moving callback, making the code more efficient. The main reason though, is that it feels more obvious that the moving callback should only be concerned with movement when "swiping".
An example would be if we wanted an element to follow the "cursor", we could set the element's x and y within the moving callback and we're done. But if moving is always called, we have to bind it in start and then unbind it on end or else the element will continue tracking the cursor.

I can't understand your problem clearly. I'm not good at English in fact. Reffer to https://github.com/jerrybendy/vue-touch-events/blob/master/index.js#L112 , only when touchMoved is true, the moving event will be triggered. And the touchMoveEvent function is called when native touchmove or mousemove event triggered. So I think your problem doesn't exist. Moving event wouldn't be triggered when you release your finger from a touch screen.

You may be right. The README.md does say that moving is a "Continuously triggering Event". I got confused because it doesn't track movement from the beginning.
Example: https://jsfiddle.net/kvfm8xsr/

Moving often works with start and end. In your example, you should set clicked to true when start triggered and set to false when end triggered.
<div
  v-touch:start="() => this.clicked = true"
  v-touch:end="() => this.clicked = false"
  v-touch:moving="movingHandler"
></div>

movingHandler: function (e) {
        if (this.clicked) {
	    [this.x, this.y] = [e.x - 25, e.y - 75];
        }
}


Display bug on collection's watch tab

On collection's watch tab, when the main page display starts to have a scroll bar, it is not possible to interact with both filter builder and published messages / documents; the arrows won't unfold, and when unfolded, will fold as soon as we try to scroll.

It might come from the scroll on new messages that is enabled by default

Yes this is because scroll on new messages is enabled. I am going to put the whole message list inside a container which will have a scroll bar


Xml

Added the ability to toggle between  XML and Json formats.

Conor, I just ran your instructions above and I did not get any errors. The request worked fine.

Same here, no errors for me.


How to load custom model in object-detector-python

Hello,
I'm not able to load a custom model in a modified example of object-detector-python. From the Dockerfile.model I see that the current model is compiled to run on google coral so I transformed my model acordingly (based on yolov4-tiny).
My custom model is fully quantized to tf-lite int8 and then postprocessed to be compatible with google coral by using edgetpu_compiler with success. also I tried with no success to load the quantized int8 model without compiling for google-coral.
But after loading the docker image to the camera (P3265) it shows the following error:
ERROR in Inference: Failed to load model model.tflite (Could not load model: Could not build an interpreter of the model)
<_InactiveRpcError of RPC that terminated with:
object-detector-python-object-detector-python-1  | 	status = StatusCode.CANCELLED
object-detector-python-object-detector-python-1  | 	details = ""
object-detector-python-object-detector-python-1  | 	debug_error_string = "{"created":"@1657181878.926597840","description":"Error received from peer ipv4:<IP_ADDRESS>:8501","file":"src/core/lib/surface/call.cc","file_line":1063,"grpc_message":"","grpc_status":1}"
I don't know if I'm missing some step or the model needs to be converted in a different way.
Environment

Axis device model: P3265-LVE
Axis device firmware version: 10.10.73
SDK VERSION: 1.2
docker daemon: 1.2.3

EDIT: I upgraded the camera firmware to 10.11.76 (also I reinstalled docker daemon 1.2.3). Now the error is different:
/usr/bin/acap_runtime: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /host/lib/liblarod.so.1)
Thank you very much

Hello
I've got the same error  when I run AxisCommunications/acap-computer-vision-sdk-examples/object-detector-python/ example without any changes.
"/usr/bin/acap_runtime: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /host/lib/liblarod.so.1)"

I suspect version 10.11.76 is incompatible with sdk computer vision 1.2. In mi case the example object-detector-python without changes was working with firmware 10.10.73

Hello! yes there was an already reported bug with 10.11 or greater firmware, that has been fixed today.
There are some minor changes on the examples, mainly in the docker-compose file. Make sure to have them up to date with the master branch.
I'll close this issue, feel free to open another one if you encounter more problems.

Hi, I have the same issue when I loaded my own tflite model.
I have already replaced the path to my model in the [Dockerfile.model]
(https://github.com/AxisCommunications/acap-computer-vision-sdk-examples/blob/main/object-detector-python/Dockerfile.model)
There is the error I encountered:

error message:
ERROR in Inference: Failed to load model train-608_best.tflite (Could not load model: Asynchronous connection has been closed)
<_InactiveRpcError of RPC that terminated with:
object-detector-python_1  |     status = StatusCode.UNAVAILABLE
object-detector-python_1  |     details = "failed to connect to all addresses"
object-detector-python_1  |     debug_error_string = "{"created":"@1659425957.027178280","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":3217,"referenced_errors":[{"created":"@1659425957.027173640","description":"failed to connect to all addresses","file":"src/core/lib/transport/error_utils.cc","file_line":165,"grpc_status":14}]}"
Environment

Axis device model: P3265-LVE
Axis device firmware version: 10.11.76 (also tried 10.10.73 but didn't work)
SDK VERSION: 1.2.1
docker daemon: 1.2.3

Please help me, thanks in advance.


logrotate: 3.19.0 -> 3.20.1

Description of changes
Fixes CVE-2022-1348.

https://github.com/logrotate/logrotate/releases/tag/3.20.0
https://github.com/logrotate/logrotate/releases/tag/3.20.1

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Can backport to 22.05, can we look into applying a patch for 21.11?

I just tried to apply the two commits on top of logrotate version 3.18.1, as present in the release-21.11 branch. However, not even the logrotate.c file can be patched, as there were to many changes in between. As I don't want to introduce further issues, I don't want to create a patch by myself. Thus, could we just backport this PR?

@mweinelt: I just backported this manually for 21.11 in #174584. Would you mind to take a look? Thanks!


App crashes in Android 5.1 devices when user tries to zoom-in beyond a certain extent in the map.

We have come across a crash report with the below mentioned stack trace in our Application which is currently live:
Caused by java.lang.NullPointerException: Attempt to read from null array
       at java.util.ArrayList.get(ArrayList.java:310)
       at com.google.maps.api.android.lib6.gmm6.vector.gl.drawable.g.a(g.java:56)
       at com.google.maps.api.android.lib6.gmm6.vector.gl.drawable.ao.a(ao.java:91)
       at com.google.maps.api.android.lib6.gmm6.store.fetch.i.a(i.java:99)
       at com.google.maps.api.android.lib6.gmm6.store.fetch.f.a(f.java:3)
       at com.google.maps.api.android.lib6.gmm6.store.j.a(j.java:19)
       at com.google.maps.api.android.lib6.gmm6.store.k.a(k.java:96)
       at com.google.maps.api.android.lib6.gmm6.store.k.d(k.java:164)
       at com.google.maps.api.android.lib6.gmm6.store.k.a(k.java:31)
       at com.google.maps.api.android.lib6.gmm6.store.f.handleMessage(f.java:100)
       at android.os.Handler.dispatchMessage(Handler.java:111)
       at android.os.Looper.loop(Looper.java:218)
       at com.google.maps.api.android.lib6.gmm6.store.k.run(k.java:126)
       at com.google.maps.api.android.lib6.gmm6.store.ab.run(ab.java:12)

The crash has occurred in Android 5.1 (OPPO device). I have gone through other similar crashes reported by others and seems like all of them have reported in Android 5.1 devices. We have tested in other Android versions (8, 9 and 10) but were not able to reproduce it with the steps mentioned in those similar crash reports. We don't have any Android 5.1 devices with us. As per the discussions on other similar crashes, I have come to know that the crash has something to do with the zoom level exceeding 16 in those devices. In our application, we are using react-native-maps to show markers on the map. I have cross verified the logic of markers and it looks fine.
While browsing through the similar crashes I have come across one open issue with google on this. Here is the issue tracker link: https://issuetracker.google.com/issues/145941832
Environment info:
react: 16.8.3
react-native: 0.59.10
react-native-maps: 0.22.1
Steps To Reproduce:

Open maps in an Android 5.1 version device (Oppo / Lenovo / LG / Huawei devices preferable).
Try to zoom in beyond the maxZoomLevel of 16.

Expected Behaviour:
The app shouldn't crash and user should be able to zoom in.
Actual Behaviour:
The app crashes.

+1, I have faced this issue too in current RN project.

+1, me also. Android 5.1 on Lenovo phone.

+1, also. Android 5.1 on Huawei Y6 Pro