Datapoint not created correclty, true/false datapoint is missing

Hi.
I've got a "mmwave" sensor. It works perfectly within home assistant. But I like to use it within iobroker.
The sensor shows up in the browser and works.
But there is a problem with the data point in the "objects" section of iobroker.
There is only a folder but not a real "true/false" datapoint.
I tried to delete everything, so that the adapter creates it again, but... same problem.
So I can't use the sensor right now. Not sure how to fix it.
Versions:

Adapter version: v0.2.4
JS-Controller version: v16.17.0
Node version: 8.15.0
Operating system: linux

Can you please Share your yaml?
(Please ensire that secrets, like wifi password etc, are Not in your comment 😊)

`esphome:
name: mmwave-occupancy
esp8266:
board: d1_mini
Enable logging
logger:
Enable Home Assistant API
api:
ota:
password: "totoally_secret_you_know..."
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Mmwave Fallback Hotspot"
password: "totoally_secret_you_know..."
substitutions:
device_name: mmwave-sensor
captive_portal:
web_server:
port: 80
version: 2
include_internal: true
http_request:
useragent: esphome/$device_name
timeout: 2s
switch:

platform: safe_mode
internal: true
name: use_safe_mode

binary_sensor:

platform: gpio
name: mmwave_in_bedroom
pin:
number: GPIO16
mode: INPUT_PULLDOWN

uart:
id: uart_bus
tx_pin: GPIO4
rx_pin: GPIO5
baud_rate: 115200
debug:
direction: BOTH
dummy_receiver: true
after:
delimiter: "\n"
sequence:
- lambda: UARTDebug::log_string(direction, bytes);
number:

platform: template
name: distance
id: distance
min_value: 0
max_value: 1350
initial_value: 315
optimistic: true
step: 15
restore_value: true
unit_of_measurement: cm
set_action:

uart.write: "sensorStop"
delay: 1s
uart.write: !lambda
int cm = (int)ceil(x / 15.0);
std::string cms = "detRangeCfg -1 0 " + to_string(cm);
return std::vector(cms.begin(), cms.end());
delay: 1s
uart.write: "saveCfg 0x45670123 0xCDEF89AB 0x956128C6 0xDF54AC89"
delay: 1s
uart.write: "sensorStart"

platform: template
name: latency
id: latency
min_value: 0
max_value: 65000
initial_value: 12500
optimistic: true
step: 25
restore_value: true
unit_of_measurement: ms
set_action:

uart.write: "sensorStop"
delay: 1s
uart.write: !lambda
int ms = (int)ceil(x / 25.0);
std::string mss = "outputLatency -1 0 " + to_string(ms);
return std::vector(mss.begin(), mss.end());
delay: 1s
uart.write: "saveCfg 0x45670123 0xCDEF89AB 0x956128C6 0xDF54AC89"
delay: 1s
uart.write: "sensorStart"

button:

platform: restart
name: Restart $device_name

platform: template
name: "factory_reset_sensor"
id: "factory_reset_sensor"
on_press:

uart.write: "sensorStop"
delay: 1s
uart.write: "factoryReset 0x45670123 0xCDEF89AB 0x956128C6 0xDF54AC89"
delay: 3s
uart.write: "sensorStart"
`

I can also send you my wemos D1 mini with the mmwave sensor if you want to test/fix things.

I think this can be closed as it is already implemented https://github.com/DrozmotiX/ioBroker.esphome/blob/main/main.js#L378C1-L380C16 and I also just validated that it works using the given yaml.

I think this can be closed as it is already implemented https://github.com/DrozmotiX/ioBroker.esphome/blob/main/main.js#L378C1-L380C16 and I also just validated that it works using the given yaml.

thank you validating :)


Setup instructions?

Would you please elaborate? If you are trying to deploy your own instance of Riju, there is extensive documentation at https://github.com/raxod502/riju/blob/master/doc/selfhosting.md.

This thread is being closed automatically by Tidier because it is labeled with "waiting on response" and has not seen any activity for 90 days. But don't worry—if you have any information that might advance the discussion, leave a comment and I will be happy to reopen the thread :)


Throw error when parsing specific TR words

Here is part of my intl_tr.arb file
{ "back_new_chest_unlock_day": "Gün ${arg1}'da açılır", "@@locale": "tr" }
And the output was
Building package executable...
Built intl_utils:generate.
ERROR: Failed to generate localization files.
type 'Null' is not a subtype of type 'int' of 'index'

Hi @RaymondGsc,
Could you check if the "back_new_chest_unlock_day" localization message in your main localization file contains the same placeholder ({arg1}) that you use in the intl_tr.arb file?

Hi @RaymondGsc,
Could you check if the "back_new_chest_unlock_day" localization message in your main localization file contains the same placeholder ({arg1}) that you use in the intl_tr.arb file?

Sorry I made a foolish mistake. Please close this issue.


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/VSC-Service-Account/docs-archive-test-source.git

Docs Build status updates of commit fe7dc3d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

archiveTargetFolder/content/someContent.md
:warning:Warning
View
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

archiveTargetFolder/TOC.yml
:white_check_mark:Succeeded
View

archiveTargetFolder/breadcrumb/E2EArchiveTarget_1895716f-1210-47be-82bf-69ffadb47b7d/toc.yml
:white_check_mark:Succeeded

archiveTargetFolder/content/sql-database-engine.png
:white_check_mark:Succeeded
View

archiveTargetFolder/docfx.json
:white_check_mark:Succeeded

archiveTargetFolder/content/someContent.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


web support broken

In dart 2.0, dart:isolate is no longer supported (see https://github.com/dart-lang/sdk/issues/30538) on web. The resolve package uses Isolate.resolvePackageUri and therefore support for web is broken.  Although dart2js and dartdevc do not seem to complain (yet?), the pana package does not categorize this package as fit for web. Consequently, on https://pub.dartlang.org/packages/resource , web is also not listed as supported platform.
This also means that other packages depending on resource and importing dart:html, have conflicting components and cannot be categorized by pana at all.

The latest build_web_compilers should disallow dart:isolate imports on the web.
We need to either go forward with a faked solution like #36 or drop support for the web from this package.
See also https://github.com/dart-lang/sdk/issues/37153

@lrhn - could you take a look?

If Isolate is not available, then this package won't work. There is no other defined way of accessing the information necessary to perform the operations of this package.
So, yes, it doesn't work on the web any more.

@lrhn if you wish to preserve the old behavior on the web, one option here would be to duplicate the logic that we used to have in the web implementations of Isolate.resolvePackageUri (possibly dart2js's which had support to override the prefix used to fetch resources from the server). The code is pretty small (5 LOC), so it is a small change overall.
If web support is not a goal, it would be nice to update the package to delete the unsupported code and indicate more clearly that it is only meant to be used on the VM.


[AKS]Add PPG support

Description

Add PPG support as part of GA work item
Testing Guide

az aks create --name test-cluster --resource-group test-rg --load-balancer-sku standard --ppg "/subscriptions/{subid}/resourceGroups/test-rg/providers/Microsoft.Compute/proximityPlacementGroups/test-ppg" --location centralus
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

AKS

/azp run

Hi @tilnl , could you please fix the Automation Test failure ?

Sure. I will do it.
From: Xiaojian Xu<EMAIL_ADDRESS>Sent: Tuesday, October 13, 2020 6:31 PM
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: Tingting Liu<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] [AKS]Add PPG support (#15445)
Hi @tilnlhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftilnl&data=04|01|tilnl%40microsoft.com|7973dcde30c1459816f308d86fe0d306|72f988bf86f141af91ab2d7cd011db47|1|0|637382358689094730|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=zFIw7zAvmrB8LA51QuLaUZ6Uyk6lQJO9UXcS1hi5GHA%3D&reserved=0 , could you please fix the Automation Test failure ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fpull%2F15445%23issuecomment-708099139&data=04|01|tilnl%40microsoft.com|7973dcde30c1459816f308d86fe0d306|72f988bf86f141af91ab2d7cd011db47|1|0|637382358689104723|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=yv%2B%2BGxjvIFhdUfv0YPWClaOK7nwlPLcEGZUEaBHN%2Fpw%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKUWPKPG3UK4WLSG5MIGPKDSKT5NXANCNFSM4SI2DNAA&data=04|01|tilnl%40microsoft.com|7973dcde30c1459816f308d86fe0d306|72f988bf86f141af91ab2d7cd011db47|1|0|637382358689104723|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dZ7q3AZWl3idSPTQEW%2BkPMZtG3OQM5VimLxDtHKLQaI%3D&reserved=0.

@arrownj , test is fixed. Thanks!


Problem access database postgresql  with ruby in dokku

Hi I have an application on rails and want to access from external ruby script in the application using the same database.
Try follows but results
/var/lib/gems/1.9.1/gems/sequel-4.27.0/lib/sequel/adapters/postgres.rb:241:in `initialize': PG::ConnectionBad: FATAL:  password authentication failed for user "postgres" (Sequel::DatabaseConnectionError)
FATAL:  password authentication failed for user "postgres"
My code in ruby is:
#Connection to database
conn = Sequel.postgres('tilo_cms', :user=>'postgres',
:password=>'ff76e153f06737d69e7036cc96a944fe', :host=>'localhost', :port=>5432,
:max_connections=>10)

This isn't an issue with dokku - dokku does not come out of the box with postgres - but rather an issue with your application code. If you have an issue with a specific plugin, please re-file at that plugin's issue tracker.
Note: It seems like your host is invalid, since postgres wouldn't be running inside of your container, but rather potentially inside of another one.


Automate guarantee that mk8sv is satisified

Followup from:

I think this breaks the Kubernetes version guarantee - requires openapi to upgraded to
1.31 to compile kube-rs as a dependency. @clux

Originally posted by @aviramha in https://github.com/kube-rs/kube/issues/1605#issuecomment-2421919001
An innocent change broke that guarantee and could've slipped to a release.
Opening this issue to discuss how we can guarantee that this doesn't happen in the future.
My suggestion is to change the dev dependency of openapi to use mk8sv (perhaps run tests both on latest and mk8sv?)
Happy to hear other suggestions

It's funny because we do run the tests on both versions, but there's clearly a gap here since this got through.
Thanks for raising.

Yeah it's runtime vs compilation - the new version will run on older clusters, just won't compile with "old" openapi

Yeah. Tbh, this is a reason why parts of me wants to drop k8s-openapi's version choice and turn it into fixed latest because the runtime is way more important than the schemas. If we pin latest we can:

drop all the feature madness, e2e tests actualling un-defaulting the feature, and adding in earlier
re-export k8s-openapi exports under a namespace (as in here)
avoid people having to update k8s-openapi and kube together (we pin, you get updates)

It's also the versioning strategy most other kubernetes tools on the go side uses (update client-go? cool, dont' stray too far, here's a compatibility matrix, but you get updated structs anyway).
The alternative here is doing more like what we do in the e2e style tests (which do actually run both feature versions).

Okay, sounds like a good plan to me. It's less backward compatible but good trade offs in terms of usability/maintenance and if it's the standard then no reason to stray from that.


chore(website-backend): bumped wordpress and plugin versions

I tested locally (not thoroughly!):

wordpress backend
gatsby dev
gatsby build

I'd think we should ship this to stage and ask our peeps to have a closer look as well.
Be aware that the database needs updates, which may cause problems on a downgrade. We should make sure to be able to roll back while going forward (at least by saving a point in time backup of the DB).
I ain't worried at all!

@phollome

prod db imported
shipped to stage
migrated to most recent wp core + plugins
local build of gatsby was successful

I like ... you like?

@phollome fixed the remote peer version error issue by bumping the gatsby-source-wordpress dependency.
Sorry, obviously did build against prod which did not show the issue, because of an older remote wp plugin.
Action did go thru.

@phollome
deployed to PROD Wordpress and successfully build locally against updated PROD.
In case of problems. The prior version DB is in reach on server in "~/deployments/_BACKUP"


🚚 Expose PoP 🗝 as JWT claim

Allow PoP key to be stored in the JWT claims directly as pop_key, without the need of a tdf_claims object
This allows the token to be used with endpoints that require user signed content but are indifferent to entitlements

Checklist

[x] A clear description of the change has been included in this PR.
[ ] A clear description of whether this change is a Major, Minor, Patch or cosmetic change as per the Versioning Guidelines has been included in this PR.
[ ] All schema validation tests have been updated appropriately and are passing.
[ ] MAJOR/MINOR VERSION CHANGES ONLY: This PR should be made in branches prefixed with draft-<change>
[ ] MAJOR/MINOR VERSION CHANGES ONLY: A link to a reference implementation (PR or set of PRs) of the change has been included in this PR.
[ ] MAJOR/MINOR VERSION CHANGES ONLY: A writeup has been included discussing the motivation and impact of this change.
[ ] MAJOR/MINOR VERSION CHANGES ONLY: The minimum wait time has elapsed.
[ ] DRAFT MERGE ONLY: Draft Semver has been updated in the VERSION file (optional)
[ ] DRAFT MERGE ONLY: Tagged this branch with new semver version and an annotation describing the change (ex: git tag -s 4.1.0 -m "Spec version 4.1.0 - did a thing")
[ ] DRAFT MERGE ONLY: Version numbers have been updated as per the Versioning Guidelines.
[ ] This change otherwise adheres to the project Contribution Guidelines.

@pbacon-blaber What do you think? This should harmonize the work you've done with our open source work

Minor suggestion - to avoid any future collisions with other claims, might be best to name the claim tdf_pop_key or similar.

This proposal was withdrawn in favor of the hopefully soon-ot-be-standard, DPoP, in https://github.com/opentdf/spec/pull/10


repLoad error for 10X

I encountered the error when trying to repLoad a 10X VDJ library. Do you know why?
> repLoad(
+   "Fresh1_Tcell_vdj/outs/",
+   .format = "10x")
Parsing Fresh1_Tcell_vdj/outs/ ...
Parsing Fresh1_Tcell_vdj/outs//all_contig_annotations.bed -- 10x
Error in `[[<-.data.frame`(`*tmp*`, .nuc.seq, value = character(0)) :
  replacement has 0 rows, data has 7715
In addition: Warning messages:
1: The following named parsers don't match the column names: AGTAGTCTCGTTTAGG-1_contig_1, 22, 356, TRBV13-1_L-REGION+V-REGION
2: In .which_recomb_type(df[[.vgenes]]) :
  Can't determine the type of V(D)J recombination. No insertions will be presented in the resulting data table.

I used cellranger v3.0.2 to produce the input repertoire files.
Thanks in advance!

Looks like I loaded the wrong file. If I specify the exact file name (filtered_contig_annotations.csv) instead of the folder name, it works. I'm closing this issue for now. Thanks!


Hovering a Pin when adding a Link is causing the canvas to clip

I have found that the node editor canvas is clipping when attempting to create a link.
I believe it is related to this issue in the underlying imgui-node-editor, which has a workaround.
https://github.com/thedmd/imgui-node-editor/issues/237
https://github.com/pthom/imgui_bundle/assets/5153498/d25ac2cd-ccbc-4b2d-9cf1-be454dcce694

Hi,
It is strange that the issue was closed in the imgui-node-editor repository. Having an issue or a related PR would be the best way to get this to be solved in the main repository.
Did you try the workaround on your side with your project, and does it fix the issue?

I have not reproduced the workaround, I've been using the precompiled wheel from pip.
I did also find this possibly related issue that remains open on the imgui-node-editor repository.
https://github.com/thedmd/imgui-node-editor/issues/205

Could you post a minimal reproducible example?

To reproduce, it requires the graph to be in a docking window, and the clipping is screen position depended.
from imgui_bundle import imgui, imgui_node_editor as ed, immapp
from imgui_bundle.immapp import static, run_anon_block as anon
from imgui_bundle import hello_imgui

@immapp.static(id=0)
def next_id():
    next_id.id += 1
    return next_id.id

@immapp.static(id=0)
def next_link_id():
    next_link_id.id += 1
    return next_link_id.id

def gui():
    next_id.id = 0

    ed.begin("My Editor", imgui.ImVec2(0.0, 0.0))

    ed.begin_node(ed.NodeId(next_id()))
    imgui.text("Node 1")
    ed.begin_pin(ed.PinId(next_id()), ed.PinKind.output)
    imgui.text("Out ->")
    ed.end_pin()
    ed.end_node()

    ed.begin_node(ed.NodeId(next_id()))
    imgui.text("Node 2")
    ed.begin_pin(ed.PinId(next_id()), ed.PinKind.input)
    imgui.text("-> In")
    ed.end_pin()
    ed.end_node()

    if ed.begin_create():
        input_pin_id = ed.PinId()
        output_pin_id = ed.PinId()
        if ed.query_new_link(input_pin_id, output_pin_id):
            if ed.accept_new_item():
                ed.link(ed.LinkId(next_link_id()), input_pin_id, output_pin_id)
    ed.end_create()

    ed.end()

runner_params = immapp.RunnerParams()
runner_params.imgui_window_params.menu_app_title = "Pipeline"
runner_params.imgui_window_params.enable_viewports = True
win = hello_imgui.DockableWindow()
win.gui_function = gui
win.label = "graph"
runner_params.docking_params.dockable_windows = [win]

add_on_params = immapp.AddOnsParams()
add_on_params.with_node_editor = True

immapp.run(runner_params, add_on_params)

Yes, the workaround seems to solve the issue.
I will consider adding this to my node fork, will keep you posted

Thank you for reproducing!

Thank you for reproducing!

Hi, I just pushed a commit that correct this:

[https://github.com/pthom/imgui-node-editor/commit/471bdda7adaa230928f87b6a20de192d5af69580](correction in the node editor fork)
[https://github.com/pthom/imgui_bundle/commit/79bde7de7bc1cb8c808123d9850c39428332d1f0](update submodule in this repository)

As of now, I did not release a new version of the pip package (this might take a few weeks, as I want to group updates).
If you want the modification on your side, you will need to build the pip package from source.
git clone https://github.com/pthom/imgui_bundle.git
cd imgui_bundle
git submodule update --init --recursive  # Since there are lots of submodules, this might take a few minutes
pip install -v . # The build process might take up to 15 minutes
pip install opencv-contrib-python

I'll need to find an appropriate way to transmit the fix to @thedmd, together with an easily reproducible example.
I'll work on this a little later.

@pthom Issue is now resolved in node editor. Thanks for your help!

This issue is now fixed, and also fixed in @thedmd  repo. Thanks a lot!


Simplify & test format_rust_expression

This doesn't solve the issue I was looking at, but it hopefully cleans up a function and adds some tests.
There's still a unicode issue somewhere else in the code which means replacing inline code where one of the characters is unicode doesn't work well
Let me know any feedback / preferences around tests. Also possible I'm missing the reason behind the original code

I'm not sure I can justify the original code any more.


Add AIX support

The build and the simple tests in example_test.go seems to work as expect.

Thanks!


Should the addon declare a node dependency?

Currently the v2 addon here in the blueprint, but also other v2 addons in the wild (e.g. ember-page-title), have an engines.node declaration in their package.json. While they have some dependencies (at least @embroider/addon-shim) that run in node (which express their node dependency on their own), the addon itself is supposed to be static browser-based/idiomatic JavaScript.
So it seems to me we should remove the declaration?

@ef4 do you agree? 👆


Remove the line in the development README about having a GHE account

Puppet (this repo) is now public on normal GitHub, so people won't
need a GHE account to get started with the dev VM.

:+1: merge when green

:+1:

:sunny:


refactor: valid_date does not work in PHP 8.2

Description
See #6170
See https://github.com/codeigniter4/CodeIgniter4/pull/6172#issuecomment-1275496541
bash-3.2$ ./phpunit tests/system/Validation/FormatRulesTest.php
PHPUnit 9.5.25 #StandWithUkraine

Runtime:       PHP 8.2.0-dev
Configuration: /Users/kenji/work/codeigniter/official/CodeIgniter4/phpunit.xml

...............................................................  63 / 193 ( 32%)
............................................................... 126 / 193 ( 65%)
............................................................... 189 / 193 ( 97%)
....                                                            193 / 193 (100%)

Time: 00:00.325, Memory: 14.00 MB

OK (193 tests, 193 assertions)

Checklist:

[x] Securely signed commits
[] Component(s) with PHPDoc blocks, only if necessary or adds value
[] Unit testing, with >80% coverage
[] User guide updated
[x] Conforms to style guide

Is there a case where $date is a DateTime instance yet $errors contains actual errors? If no, then can we remove the getLastErrors check?

Is there a case where $date is a DateTime instance yet $errors contains actual errors?

Yes.
            [
                '1991-02-29',
                'Y-m-d',
                false,
            ],
            [
                'Thu, 31 Jun 2013 13:31:00',
                'D, d M Y H:i:s',
                false,
            ],
            [
                '2, 17, 2001',
                'j, n, Y',
                false,
            ],
            [
                '09-42-25, 12-00-17',
                'h-i-s, j-m-y',
                false,
            ],

Thank you @kenjis


ShrinkWrap Resolver 2.2.0-beta-2 release blog

Thank you! Pushed upstream; https://github.com/arquillian/arquillian.github.com/commit/9ab4047df9c18a2f1569e83e80b75f20543d0b9c and pushed live: http://arquillian.org/blog/2015/04/11/resolver-2-2-0-beta-2/


Running from within a firewall

This is really a maven issue; however, others may be in the same position I find myself and addressing this issue could prove helpful.
I was able to successfully run the cleo-primer from behind a less-restrictive firewall; the remote fetching worked and the server started.  Now I am trying to run the sample from behind a restrictive firewall and the startup fails because remote files cannot be downloaded.
I checked Maven's site http://maven.apache.org/guides/mini/guide-proxies.html and duly created a file ~jlpoole/.m2/repository/settings.xml  as follows:
jlpoole@themis /usr/local/src/cleo-primer $ cat ~/.m2/repository/settings.xml
--settings--
--proxies--
--proxy--
--active--true--/active--
--protocol>http--/protocol--
--host--[the proxy server]--/host--
--port--[the proxy port]--/port--
--/proxy--
--/proxies--
--/settings--
Note: I had to substitute "--" for opening and closing markup since my pasting them in caused them to disappear.
jlpoole@themis /usr/local/src/cleo-primer $
Yet, when I try to run the launching command, it's showing the proxy is not working:
    jlpoole@themis /usr/local/src/cleo-primer $ MAVEN_OPTS="-Xms1g -Xmx1g" mvn jetty:run -Dcleo.instance.name=Company -Dcleo.instance.type=cleo.primer.GenericTypeaheadInstance -Dcleo.instance.conf=src/main/resources/config/generic-typeahead
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building cleo-primer 1.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-jetty-plugin:6.1.25:run (default-cli) @ cleo-primer >>>
[WARNING] The POM for org.codehaus.jackson:jackson-lgpl:jar:0.9.4 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
[WARNING] Could not transfer metadata org.springframework:spring-core/maven-metadata.xml from/to m1.dev.java.net (http://download.java.net/maven/1): No connector available to access repository m1.dev.java.net (http://download.java.net/maven/1) of type legacy using the available factories WagonRepositoryConnectorFactory
[WARNING] Could not transfer metadata org.springframework:spring/maven-metadata.xml from/to m1.dev.java.net (http://download.java.net/maven/1): No connector available to access repository m1.dev.java.net (http://download.java.net/maven/1) of type legacy using the available factories WagonRepositoryConnectorFactory
[WARNING] Could not transfer metadata org.springframework:spring-beans/maven-metadata.xml from/to m1.dev.java.net (http://download.java.net/maven/1): No connector available to access repository m1.dev.java.net (http://download.java.net/maven/1) of type legacy using the available factories WagonRepositoryConnectorFactory
[WARNING] Could not transfer metadata org.springframework:spring-context/maven-metadata.xml from/to m1.dev.java.net (http://download.java.net/maven/1): No connector available to access repository m1.dev.java.net (http://download.java.net/maven/1) of type legacy using the available factories WagonRepositoryConnectorFactory
[WARNING] Could not transfer metadata org.springframework:spring-web/maven-metadata.xml from/to m1.dev.java.net (http://download.java.net/maven/1): No connector available to access repository m1.dev.java.net (http://download.java.net/maven/1) of type legacy using the available factories WagonRepositoryConnectorFactory
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ cleo-primer ---
[debug] execute contextualize
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 4 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ cleo-primer ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ cleo-primer ---
[debug] execute contextualize
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory /usr/local/src/cleo-primer/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ cleo-primer ---
[INFO] No sources to compile
[INFO]
[INFO] <<< maven-jetty-plugin:6.1.25:run (default-cli) @ cleo-primer <<<
[WARNING] Failure to transfer org.springframework:spring-core/maven-metadata.xml from http://download.java.net/maven/1 was cached in the local repository, resolution will not be reattempted until the update interval of m1.dev.java.net has elapsed or updates are forced. Original error: Could not transfer metadata org.springframework:spring-core/maven-metadata.xml from/to m1.dev.java.net (http://download.java.net/maven/1): No connector available to access repository m1.dev.java.net (http://download.java.net/maven/1) of type legacy using the available factories WagonRepositoryConnectorFactory
[WARNING] Failure to transfer org.springframework:spring/maven-metadata.xml from http://download.java.net/maven/1 was cached in the local repository, resolution will not be reattempted until the update interval of m1.dev.java.net has elapsed or updates are forced. Original error: Could not transfer metadata org.springframework:spring/maven-metadata.xml from/to m1.dev.java.net (http://download.java.net/maven/1): No connector available to access repository m1.dev.java.net (http://download.java.net/maven/1) of type legacy using the available factories WagonRepositoryConnectorFactory
[WARNING] Failure to transfer org.springframework:spring-beans/maven-metadata.xml from http://download.java.net/maven/1 was cached in the local repository, resolution will not be reattempted until the update interval of m1.dev.java.net has elapsed or updates are forced. Original error: Could not transfer metadata org.springframework:spring-beans/maven-metadata.xml from/to m1.dev.java.net (http://download.java.net/maven/1): No connector available to access repository m1.dev.java.net (http://download.java.net/maven/1) of type legacy using the available factories WagonRepositoryConnectorFactory
[WARNING] Failure to transfer org.springframework:spring-context/maven-metadata.xml from http://download.java.net/maven/1 was cached in the local repository, resolution will not be reattempted until the update interval of m1.dev.java.net has elapsed or updates are forced. Original error: Could not transfer metadata org.springframework:spring-context/maven-metadata.xml from/to m1.dev.java.net (http://download.java.net/maven/1): No connector available to access repository m1.dev.java.net (http://download.java.net/maven/1) of type legacy using the available factories WagonRepositoryConnectorFactory
[WARNING] Failure to transfer org.springframework:spring-web/maven-metadata.xml from http://download.java.net/maven/1 was cached in the local repository, resolution will not be reattempted until the update interval of m1.dev.java.net has elapsed or updates are forced. Original error: Could not transfer metadata org.springframework:spring-web/maven-metadata.xml from/to m1.dev.java.net (http://download.java.net/maven/1): No connector available to access repository m1.dev.java.net (http://download.java.net/maven/1) of type legacy using the available factories WagonRepositoryConnectorFactory
[INFO]
[INFO] --- maven-jetty-plugin:6.1.25:run (default-cli) @ cleo-primer ---
[INFO] Configuring Jetty for project: cleo-primer
[INFO] Webapp source directory = /usr/local/src/cleo-primer/src/main/webapp
[INFO] Reload Mechanic: manual
[INFO] Classes = /usr/local/src/cleo-primer/target/classes
2012-03-06 14:48:47.802:INFO::Logging to STDERR via org.mortbay.log.StdErrLog
[INFO] Jetty server exiting.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.554s
[INFO] Finished at: Tue Mar 06 14:48:47 PST 2012
[INFO] Final Memory: 10M/981M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.25:run (default-cli) on project cleo-primer: Failure: Bad temp directory: /usr/local/src/cleo-primer/target/work -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
2012-03-06 14:48:48.074:INFO::Shutdown hook executing
2012-03-06 14:48:48.074:INFO::Shutdown hook complete
jlpoole@themis /usr/local/src/cleo-primer $

Is there something that can be tweaked to bypass refreshing from remote sources so when the example is run from within a restrictive firewall it is ready to run and/or aborts trying to get the latest files?  Or have I missed some basic Maven configuration making my attempt to create a proxy entry useless?

When I first installed the cleo-primer, I did so as root and with a not-as-restrictive firewall.  The appropriate files were downloaded by maven and stored under root's .m2/repository.  When I was under a restrictive firewall, I attempted to run as user jlpoole and since it was the first time, the failed attempt to download through the proxy proved fatal to the launching of the server.  When I changed to root and ran the cleo-primer, attempts were made to download, again, but since the previous run in the less restrictive environment had successfully downloaded the requisite files, the files were available for this session where the Maven proxy configuration does not seem to be working.
Conclusion, once you're able to download the required files, they can be used later when download is not possible.  The project uses cached files.

It is not necessary to install cleo-primer as root. It can be any user like jlpoolen under a restrictive firewall. For the maven repository/cache, once you have needed jars downloaded, they are cached and reused.


[Merged by Bors] - feat: Results about convergence of measures of sets assuming convergence of indicator functions.

Adding results about convergence of measures of sets assuming convergence of indicator functions.

I could find surprisingly few results about the use of indicators in measure theory, and they were scattered in different places.
The immediate use case for me is the portmanteau theorem (specifically showing that if for all Borel sets with null boundary we have convergence of measures of the set to its measure in the candidate limit, then for all closed sets we have limsup of the measures of the set at most its measure in the candidate limit). For this purpose only the lemma tendsto_measure_of_tendsto_indicator_of_isFiniteMeasure' is needed, but the other formulations come with almost no additional effort.

[x] depends on: #6445 [a.e. measurability for indicators]

Are all the conversations above resolved? If they are, could you mark them accordingly?
@ADedecker, does the PR look good to you now?

Oh sorry this went out of my head. I just had a quick look and everything looks good to me (and I believe all the conversations are indeed resolved). The only thing I'm not sure about is whether the measure arguments should be implicit/use volume_tac, but you probably know the convention better than me so I'll let you comment on it.

It looks like some of the measure arguments should be implicit, but otherwise it all looks good to me. bors d+

Thanks!
I will make these implicit. Probably the reason I write more explicit measure arguments than the other parts of the library is that I use these for weak convergence of measures where there are always multiple measures and so it is often necessary to specify the measure. But with Lean4's named arguments, this should be smooth with implicit measures as well.

✌ kkytola can now approve this pull request. To approve and merge a pull request, simply reply with bors r+. More detailed instructions are available here.

bors r+

bors r+

@kkytola This PR has added a huge import to Integral/Lebesgue: a file that imports a significant part of the analysis library.
Could you please undo that part of the PR (maybe move the new lemmas to a new file) and add a line assert_not_exists NormedSpace to make sure we don't add such a big import to this file again? Thanks!

@kkytola This PR has added a huge import to Integral/Lebesgue: a file that imports a significant part of the analysis library.
Could you please undo that part of the PR (maybe move the new lemmas to a new file) and add a line assert_not_exists NormedSpace to make sure we don't add such a big import to this file again? Thanks!

PR #6850 creates a new file for two lemmas and undoes the adding of the import.
In the original PR and review, the creation of a new file vs. adding an import was discussed from the start. To me, these are still complicated trade-offs. I definitely understand the goal to minimize imports for efficiency and even mathematical elegance, but how to weigh that against creation of new files and scattering thematically related lemmas to different places is not easy for me. Sorry about having created an unsatisfactory situation, I hope the fix PR makes it better!

Ah yes sorry this is my fault, I suggested this move. I didn't realize importing borel was a heavy import for measure theory (maybe Bourbaki bias here...). @fpvandoorn do you think it would make sense to split off the NormedAddCommGroup lemmas from Mathlib.MeasureTheory.Constructions.BorelSpace.Basic? Would that be enough to make this import viable again?

Thanks for the new PR, and no worries, these things can happen!
Yes, I was also wondering if the problem was somewhere else.
If easy it might be nice if MeasureTheory.Constructions.BorelSpace.Basic doesn't import Mathlib.Analysis.Normed.Group.Basic. But in this case the relevant thing is that MeasureTheory.Constructions.BorelSpace.Metrizable has the much heavier import Mathlib.Topology.MetricSpace.Metrizable since that imports Mathlib.Analysis.SpecificLimits.Basic. Somewhere this chain should probably be broken.
I also added a comment to #6850 that probably allows us to make the lemmas added in this PR more elementary.


[Neuvector] Check for PSP compatibility in target cluster

Parent ticket: https://github.com/rancher/rancher/issues/39366
Kubernetes 1.25 drops support for PSP, so additional checks need to be added.
Rancher team 3 is following the proposal outlined in "Kubernetes v1.25 PSP to PSA migration proposal document"
Every chart that ships with a PSP must be changed to add a new condition checking for the PSP capability in the target cluster:
Capabilities check for Helm
{{- if .Capabilities.APIVersions.Has "policy/v1beta1/PodSecurityPolicy" }}
This change allows the charts to still work with PSPs in Kubernetes versions prior to v1.25, and work in Kubernetes v1.25 or higher by skipping installation of PSPs.
Charts that need updating:

Neuvector (has PSPs in the upstream )

If a cluster role in a chart contains PSP's along with other permissions extra work may be needed to achieve the intended behavior of that role.

https://github.com/rancher/charts/pull/2300

will be validated by @selvamt94

Verified with 2.7 dev brach Rancher Manager v2.7-9bb8d5674d4f2fe85cca799b07a6d18eee257b9e-head. The new Neuvector feature chart 102.0.0+up2.4.2 show error if psp is enabled on k8s version 1.26. And chart with older version k8s if psp is enabled.

@selvamt94 Can you confirm if checks for this issue are complete and if we can close the issue ?

@sowmyav27 I verified both older and newer version of Kubernetes for this check. Please close it. Thanks.


Fix scrolling to new tab when tabs overflow

Task/Issue URL: https://app.asana.com/0/1201048563534612/1208326825362864/f
Description:
Perform all updates of the collection view in a batch and only scroll to the new tab from the completion handler.
Steps to test this PR:

Open so many new tabs that the tab bar overflow mode is enabled and arrow buttons are present
From the Open new tab via context menu or cmd+click
Verify that the tab bar is scrolled to show the newly opened (inactive) tab.

Definition of Done:

[ ] Does this PR satisfy our Definition of Done?

Internal references:
Pull Request Review Checklist
Software Engineering Expectations
Technical Design Template
Pull Request Documentation

Turns out this breaks opening Zoom links, so let me work on it a bit more.


HTTP Collector and Hadoop

Will HTTP Collector work with Hadoop in a near future?

Not on the radar... yet.  I thought this question would come earlier, but you are the first one to ask! :-)
Our focus has been maximum flexibility/extensibility over maximum quantity.  In other words, "how many things can you do with one instance" over "how many docs can you process with multiple instances".  It matches what we felt was needed the most (and matches the requests we get).
You can still have many different instances of the collector running in parallel with different start URLs or filters, to crawl many millions of pages.

Maybe it is time we start thinking about this.  Do you want to make this a feature request?
It should not be that hard to modify the collector code to have instances runnable in an Hadoop cluster and share processing of tons of URLs.  Is that what you would envision or do you have something else in mind?  Would you like the collector to take care of setting up the cluster itself and spawn itself according to whatever configuration?

Maybe it is time we start thinking about this.

Please, do. Although not everybody needs it, I think there is a nich on Windows.

Would you like the collector to take care of setting up the cluster itself and spawn itself according to whatever configuration

You are the expert. All what you propose sounds good to me. Just keep applying "flexibility/extensibility" now to "maximum quantity".

I am marking the integration with Hadoop as a feature request with no set release in mind.  I'll pay attention to the demand.  Anybody else reading this can chime in if they have a need for it as well.

Thank you


Update fetching-incidents.md

Status
Ready
Related Issues
N/A
Description
Add more explanation of why value of demisto.getLastRun() shows up as empty dict. (This has come up and caused confusion several times. Please feel free to rephrase to make this clearer or more accurate.)
Screenshots
N/A

Thanks @bakatzir! So I am good to squash and merge this?


add async124 yield-in-asynccm-not-in-try

last part of #262, though I'm not 100% on whether this should be a rule in flake8-async.
have not bumped version or added to changelog, and will extend the tests if we decide to go ahead.
(and if not make sure the fix to Visitor102.Visit_Try gets merged elsewhere)

I'd lean towards "don't bother doing this", since we're already covering the try/finally case I think there aren't any awaits that wouldn't already be warned-about.

I'd lean towards "don't bother doing this", since we're already covering the try/finally case I think there aren't any awaits that wouldn't already be warned-about.

right, I guess if the yield raises then any awaits can't cause any problems so this is about a completely different problem that's fairly well known and usually quite noticeable when it's not followed.


Parallel VMDB specs

Summary
Leverage the parallel_tests gem to run the vmdb test suite in parallel. This saves ~15 minutes on CI, and with 8 cores locally the VMDB suite runs in about 8-9 minutes!
Details

You can now run the VMDB suite in parallel over the number of available cores on your machine. Just run PARALLEL=true bin/rake test:vmdb
If your databases aren't set up for parallel tests, it will exit gracefully and tell you what to do (run PARALLEL=true bin/rake test:vmdb:setup)
REQUIRED: parallel_tests require you to have an updated database.yml. Running the previous setup command will also exit gracefully and tell you what you need to do (add the proper TEST_ENV_NUMBER to your database.yml)
Even though coveralls was already flaky, this will completely bust it because two processes will send coverage details from their selection of tests.

TODO

[x] Automagically update developer's database.yml to specify database: vmdb_test<%= ENV['TEST_ENV_NUMBER'] %> 👉 https://github.com/ManageIQ/manageiq/pull/8942
[x] Create a talk discussion based on above details Not necessary with new Clippy™ style help in test tasks
[x] Confirm changes are ok for

[x] appliance builds and simple updates (bin/update and bin/setup can be used there, which calls test:vmdb:setup No longer utilizing these scripts so shouldn't be a problem.
[x] MIQ dockerfile build Same
[x] local vm + shared code folder setup used by smart state analysis developers

Cool stuff...looking forward to this!

Minor, but would be nice if I didn't have to set two separate env vars (PARALLEL and PARALLEL_TEST_PROCESSORS)...perhaps blend it into just something like PARALLEL=2 (means run in parallel on 2 processors), PARALLEL=0 (means run in parallel using ALL processors)

Minor, but would be nice if I didn't have to set two separate env vars (PARALLEL and PARALLEL_TEST_PROCESSORS)...perhaps blend it into just something like PARALLEL=2 (means run in parallel on 2 processors), PARALLEL=0 (means run in parallel using ALL processors)
or perhaps PARALLEL=0 means no parallelization; PARALLEL=N means use all cores
you get the idea

Yeah, parallel_tests owns PARALLEL_TEST_PROCESSORS and I don't really want developers to have to even know about that unless they care to configure it.
I think the only thing devs care about is if they want to run the suite in parallel or not.

I think the only thing devs care about is if they want to run the suite in parallel or not.

Ah I understand...I thought a dev was going to have to set both.  Then yeah, PARALLEL=true or 1 or whatever is fine.

Considering the speedup and that it doesn't touch application code, perhaps this should be darga/yes? ¯\_(ツ)_/¯ @chessbyte

With 2e9fb88c00183e25e9de8da16315ef49a6167593, the following scenario will play out for someone who has no idea how to set up parallel_tests beyond just executing with the environment variable:

@roliveri and/or @bdunne, can you confirm the last few steps of TODO in the description? I don't think it should be an issue but double checking would be 👌

@miq-bot remove_label wip

@chrisarcand It doesn't look like there's anything that could impact "local vm + shared code folder setup used by smart state analysis developers" - so I'm OK with it. If it does break something in that area, I'll just fix it if and when we encounter it.

😱 🎉

Great work @chrisarcand and @jrafanie !! 🎉 🎉

Even though coveralls was already flaky, this will completely bust it because two processes will send coverage details from their selection of tests.

I'm ok with this being merged for now given the amount of time savings we will get.  Let's try to figure out how to get coveralls working perhaps with that gem you found.

:tada:


Soft engagement with head of content profession

What
Have a meeting with Eva Lake to bring her attention to the stakeholder map/relationship between the content profession and the service manual
Why
Part of the value of a stakeholder map is being a living document to co-design along with stakeholders. This ensures the relationship is well defined and each stakeholder has a sense of ownership for their input in the final outputs
Relates to
#707 & #780

Have an agreement for a meeting next week Wednesday

Is there a statement of what the service manual is?
Besides content design, there are other kinds of content that are developed in a user-centred way, e.g. social media/comms/engagement
There are 4 parts to the content community:

Content design
Social media
Multimedia
Content managers, e.g. ratings and reviews

Perhaps add an overlapping circle with content design for multimedia/social media
To add to the service manual: images guidance and social media guidance, esp accessibility of social media - we have info from working with social media platforms that other organisations could benefit from.
What is NHS.UK only and what is useful guidance for the wider NHS?
NHS.UK has the ability to influence social media giants, e.g. Google =, YouTube
NHS Digital corporate style guide has a different aim. Recent rebrand of NHSD - they’re doing some new style guide stuff. There is an opportunity for us to try to align. NHS Digital could be more aligned with NHS.UK/service manual. Roger Donald leading on branding NHSD. Eva trying to align with Matt Bacon. Marc Silverside is doing a session on strategy. Maybe Eva will invite Sara.
Vision for NHSD corporate website - CRM based. Same people may interact with NHS website. Again we need to find ways to align.
Comms teams - NHSD comms team does a different job to other NHS comms teams. NHSD comms team = emails, press releases, campaigns, including promoting service manual. NHS trust comms teams - responsible for websites, intranets etc - may be using service manual. Look at comms teams as users of service manual too.
@sarawilcox  to see if social media is on mailing list  for Style Council
Health charities - how they can use and input to the service manual, e.g. Asthma UK. They know their users and many are working in a user-centred way


TS: Extract contextual type for object/array literals

When an object/array literal has a contextual type, we now extract that instead of its inferred expression type. This was motivated by a performance gains in cherow shown below, but I believe it's also an improvement on its own.

before
after

cherow
217s
109s

vscode
288s
270s

For example:
interface TNode {
  x?: number;
  child?: TNode;
}
let obj: TNode = { x: 123 }

The object literal above now has type TNode instead of the anonymous type { x: 123 }. This means it would be found if searching for all expressions of type TNode, which seems useful. Being able to search for expressions with a literal type doesn't seem as important, since the DataFlow IR can handle that anyway.
The main reason for this switch is to speed up extraction of large nested literals like in this file. The type of a large object/array literal is essentially a copy of that object, which led to an N^2 cost in the depth of the object. The contextual type tends to be much smaller, usually just a named type, possibly with some type arguments.
For example, when processing this line
let deep: TNode = { child: { child: { child: { x: 123 }}}}

Each object literal now has the type TNode, previously we would independently process these four types:
{ x: 123 }
{ child: { x: 123 }}
{ child: { child: { x: 123 }}}
{ child: { child: { child: { x: 123 }}}}

I tried a few ideas to reuse intermediate results when processing these types, but it didn't make much of a difference, and switching to contextual types was way simpler.
Running a sanity check evaluation on typescript-full.slugs.

LGTM.
Would it make sense to investigate changing the inference for functions as well? I.e. could we gain anything by using the declared type of () => 42 instead of the inferred expression type?

Sanity check evaluation came out fine.

Would it make sense to investigate changing the inference for functions as well?

Worth trying at least. I'll try it out this week and see what happens.

Hmm. This technically requires an extractor bump.

Hmm. This technically requires an extractor bump.

If I understand correctly, it's only used for trap caching, which is disabled for TypeScript.

Right. This is not the first time I have forgotten about that disabled caching. Everything is fine then.

Didn't seem to make a difference for function types.


Fix toolchain path when invoking build_script_helper.py

build_script_helper.py hardcodes a usr component in the toolchain path it builds, which broke a build with a non-/usr install destination.
Fix the script invoking build_script_helper.py to path a complete toolchain path, and remove the hardcoded usr path component. The logic to determine the toolchain path was lifted from another script, as this logic is repeated in several location, with slight variations. I picked the variant that seemed the most complete.
The first commit is tested in a Linux; the second commit fixes similar code in the vicinity and has not been exercised. It is possible that these changes break on macOS and require some slight tweaking (e.g. the toolchain path given to build_script_helper.py might need to include usr as its last path component).

@swift-ci build toolchain

@swift-ci test

Note to self, need to change the toolchain installation location.


[Internal] Redemon infinite loop when running make watch

It looks like redemon somehow is ignoring the --extensions flag

We are going to switch over to watchexec

We are going to switch over to watchexec


Can't skip rules with underscore

terrascan version: v1.6.0
superlinter version: v4.0.2
Operating System: Ubuntu 20.04.2 LTS

Description
I'm using terrascan within the superlinter github action and figured out that it is not possible to skip rules with an userscore (e.g. AC_AWS_049).
What I Did
Use the superlinter github action

Hey @alexgoedeke ,
Can you please let us know how are you trying to skip rules? Are you using --skip-rules with the CLI or inline comments in your IaC code?

@kanchwala-yusuf I use the inline comments

Hey @alexgoedeke ,
I believe #843 should fix this problem. Thanks :)


NameError: name 'Image' is not defined

./swagger_server/messaging/message_queue_producer.py has a __main__, but it can't be run:
python3 ./swagger_server/messaging/message_queue_producer.py
Traceback (most recent call last):
  File "[..]./swagger_server/messaging/message_queue_producer.py", line 59, in <module>
    image = Image(filename="local-ctlr-1.manifest")
NameError: name 'Image' is not defined

Where does Image come from, and why does it attempt to load a JSON file?
https://github.com/atlanticwave-sdx/sdx-lc/blob/6cb6e2d7c46a2e0f7e66814912e8f85faeb8abdf/swagger_server/messaging/message_queue_producer.py#L59-L60

We can remove the usage of Image with this:
    f = open(file="./mq-test/local-ctlr-1/local-ctlr-1.manifest")
    data = json.load(f)

But then another problem arises:
python3 ./swagger_server/messaging/message_queue_producer.py
Traceback (most recent call last):
  File "[..]./swagger_server/messaging/message_queue_producer.py", line 64, in <module>
    with RabbitMq(server) as rabbitmq:
AttributeError: __enter__

Seems that these lines:
https://github.com/atlanticwave-sdx/sdx-lc/blob/6cb6e2d7c46a2e0f7e66814912e8f85faeb8abdf/swagger_server/messaging/message_queue_producer.py#L62-L63
.. could just be:
    RabbitMq(server).publish(body=data)

And with that we should be able to run python3 ./swagger_server/messaging/message_queue_producer.py, if RabbitMQ is running:
python3 ./swagger_server/messaging/message_queue_producer.py
Published Message: {'endpoints': [...]}

PR will follow.

This is also related to #14.

Fixed with PR #32.


stm32/uart: rework ringbuf

bors try

bors try

This PR is quite big. Could you split it into "fix RX" and "add TX support"?
I think the DmaRingBuffer struct should be split into two separate structs for TX and RX. They share almost no code, and having a const M: bool generic param where false is TX and true is RX is very awkward.

About the RX changes:

Is this supposed to fix #1427? If so, can you expand the tests to check that the repros don't fail anymore?

About the design for TX:

I would prefer to use embassy_hal_common::atomic_ring_buffer instead of writing the ringbuffer implementation from scratch. The TX code is a standard ringbuffer, no hacks needed unlike for RX. Using the atomic ringbuffer wll make it easier to start the DMA transfers from the IRQ in the future (when we make it possible to run custom code in the DMA IRQs)
Since you do control when DMA is started and stopped, and which part of the buffer is being TX'd, volatile copies are not needed. The CPU should only write to memory that's not being touched by DMA now.

The tx changes have been taken out and the struct refactor has been reverted. The tests were commented out because they rely on the broken behavior of storing ndtr, and I did not want to rewrite them and then have to throw that work away. I may bring them back in a future PR, once this has been merged.

Alright, tests are back. Not as much work as I thought.

@rmja Would you be okay if I merged these changes? I will cleanup the commits first.

Yes, lets do that. Should we add the fix to get_complete_count, such that it always returns the sum of the complete_count atomic + the tcif interrupt flag?


Working with my front end developers who would like to move off of full visual studio, they would really appreciate a way to ship code from VSC

By Design I need to be able to target and deploy to windows based azure web apps, and modifying this out seemed to work fine.

This is super helpful to be able to deploy from VSCode to my windows app

https://github.com/Microsoft/vscode-azureappservice/issues/67

@beaudryj Thanks for the contribution! As a workaround until this gets released, your windows web apps should still be listed in the App Service Explorer. You should be able to right click on a web app and deploy from there:

sadly that grabs the whole workspace, rather than say my "Dist" directory generated by my NG Build


Heroku pipelines

What about deploying this to heroku as well, just so that we can use the review apps functionality?
Benefits:

No more need for printscreens on PRs
Ability for anyone on the company to more easily provide feedback before merging
Easier for anyone to test on different browsers before merging

@subvisual/developers Anyone?

I don't fully know how that works, but it looks interesting. Can it do the following?

Have a staging app, automatically deployed from master
Have additional apps, for each PR

If so, it would be useful, because right now I'm deploying randomly to our own staging server whenever I want to test a new branch

In my opinion makes sense to try this feature. If it works as well as advertised it allows designers to be included in the review process. No downsides. :+1:

@naps62 It does exactly that.

Looks nice, we should try this.

Closing


Travis: only npm run package-all before a deploy

Since we don't usually need to have the extension packages, we can save
build time by packaging them only before a deployment, rather than on
every commit. Here's more info on when the various Travis scripts run:
https://docs.travis-ci.com/user/customizing-the-build/#The-Build-Lifecycle

Good catch.
The "Update branch" button is again not visible 😕

Looks like the following repo setting is the reason for it ... still confused why there is no "update branch" button.

Require branches to be up to date before merging
This ensures the branch has been tested with the latest code on master.


RTSP streaming does not work when RTSP security is enabled

... and unfortunately, it can not disabled any more when it was enabled with a recent app / firmware version.
This happened to me because I added another camera, which then enabled HTTP digest auth for all cameras without the possibility to turn it off again :-(.
See https://github.com/fuatakgun/eufy_security/issues/588#issuecomment-1397751520

There seems to be no possibility to configure credentials for the rtsp URL.
When I use the generic camera integration instead (and supply the http digest auth info) it works fine:

Reinstalling the integration with v6.2.0 fixed this, the RTSP stream URL now includes "user:passwort" in the string :-)


docs: Correct link address for simple example

Description
Maybe the folder name or link address isn't right, I really don't know. Either way this is the right link address.
Motivation and Context
It helps people find the files needed to run the example.
How Has This Been Tested?

[x]  It's a simple typo fix.

This PR is included in version 5.0.0 :tada:


Clarify Timestamp documentation

Some parts of the Timestamp documentation could be reworded for clarity, to reduce the amount of cross-referencing needed to fully understand the specified behavior.
A pair of topics for consideration:
Timestamp component requirements
From the binary documentation:

If a timestamp representation has a component of a certain precision, each of the less precise components must also be present or else the representation is illegal. For example, a timestamp representation that has a fraction_exponent and fraction_coefficient component but not the month component, is illegal.

This seems like it should be moved out of the binary documentation and into the the spec documentation, or removed as redundant with the linked W3C note.
A binary decoding of a Timestamp will interpret the bytes of the Timestamp in sequence as a VarInt offset, then a VarUInt year, then as a VarUInt month, etc. A Timestamp that has an offset, year, fraction_exponent, and fraction_coefficient but no month is unrepresentable. The supposed fraction_exponent and fraction_coefficient will be treated as though they are the VarUInt month, leading to a decoding error if the supposed VarInt fraction_exponent and Int fraction_coefficient don't happen to form a valid VarUInt.
Local Offsets
The text documentation leads off with:

Timestamps represent a specific moment in time, always include a local offset, and are capable of arbitrary precision.

This agrees with the binary documentation:

The 2 non-optional components are offset and year.

But conflicts with the user guide:

Ion timestamps may optionally encode a time zone offset.

And conflicts with itself a few lines down:

In the text format... Local-time offsets... are required on timestamps with time and are not allowed on date values.

But is then further detailed with:

Ion follows the “Unknown Local Offset Convention” of RFC3339

Values that are precise only to the year, month, or date are assumed to be UTC values with unknown local offset.

Synthesizing these points and taking into consideration the semantic isomorphism between the text and binary formats, I reach the following readings:

The spec counts having an unknown offset as "including a local offset" when it specifies that Timestamps "always include a local offset".

When the user guide says that Timestamps "optionally encode a time zone offset" it means that Timestamps optionally encode a known offset, and otherwise encode the default of "unknown".

Points already noted in https://github.com/amzn/ion-docs/issues/91. These can be inferred, but would benefit from being made explicit.

Text Timestamps with "date values" are prohibited from having a known offset, so they must always encode the default of unknown local offset. By isomorphism, this restriction also applies to binary Timestamps.
Binary Timestamps encode "unknown local offset" with an offset VarInt encoding negative zero (likely 0b11000000, but a less compact form of negative zero would also be valid).

These elements of the spec could be made more explicit, perhaps with text like:

https://amzn.github.io/ion-docs/docs/spec.html#timestamp

Timestamps represent a specific moment in time, are capable of arbitrary precision, and always include either a known or an unknown local offset.

Known local offsets are required on timestamps with time and are not allowed on date values.

Values that do not have a known local offset are by default UTC values with unknown local offset.

https://amzn.github.io/ion-docs/docs/binary.html#6-timestamp

The offset denotes the local-offset portion of the timestamp, in minutes difference from UTC. An unknown local offset is represented as negative zero.

(Note: my usage of the term unambiguous local offset below is not defined in the spec; I'm introducing it for the purposes of this comment to mean that we know whether a local offset is known or unknown. If we need to clarify the spec I'd be open to suggestions for a better term.)

Timestamps represent a specific moment in time, always include a local offset, and are capable of arbitrary precision.

I agree this is potentially confusing since text timestamps without a time component do not explicitly include a local offset in the encoding. However, even in this case, the local offset of such text timestamps is unambiguous : it's unknown local offset (which would be encoded explicitly as -00:00 for text timestamps with a time component). Perhaps this sentence should instead state that the local offset of any timestamp is always unambiguous even for date-only timestamps where it is not explicitly included in the encoding. I believe this is consistent with your first conclusion: "The spec counts having an unknown offset as "including a local offset" when it specifies that Timestamps "always include a local offset"."
I also agree that the "Why Ion?" page's sentence "Ion timestamps may optionally encode a time zone offset" isn't very crisp. "Optional" doesn't seem to be the right word, as both the text and binary encodings either require or prohibit encoding an explicit local offset depending on whether the timestamp has precision beyond date (modulo the issue described in #91). Maybe something more general like "Ion timestamps are capable of conveying time zone offsets" would cover us here.

Here are few more things about timestamps that probably ought to be clarified in the docs. I have worded this in a Q&A format, but it does not necessarily need to be so.

Timestamps represent a specific moment in time, always include a local offset, and are capable of arbitrary precision.

What is a "moment in time" in this context? The definition of moment found on Google (which is provided by Oxford Languages) has both "a very brief period of time" and "an exact point in time".
"Moment in time" should be interpreted in the latter sense of "an exact point in time".
What exactly is meant by precision? Does precision imply the existence of error or uncertainty?
Precision refers to the length of the timestamp representation (or the number of significant figures), rather than the units used to measure time (eg. hours, minutes, seconds). Though precision is like significant figures, it does not imply the existence of error or uncertainty. The Ion value itself has no error or uncertainty because it always faithfully represents user data.
How does precision affect the equality of timestamps?
Ion equality is different from (e.g.) mathematical equality. For example, -0 and 0 are mathematically equivalent, but are not Ion equivalent.
With respect to timestamps, two Ion timestamps with the same time but different precisions (eg. 2021-01-01T00:00Z and 2021-01-01T00:00:00.000000Z) are equal points in time, even though they are not equal Ion values.

Unlike a number, which counts from some “epoch”, arbitrary precision timestamps also allow applications to represent deliberate ambiguity.

Ion timestamps do not have any inherent ambiguity. We should remove the mention of "deliberate ambiguity" or else elaborate on it to avoid any confusion.


Tabs: fix a close button style overwriting bug

Please makes sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's Contributing Guide.
[ ] Rebase before creating a PR to keep commit history clear.
[ ] Add some descriptions and refer relative issues for you PR.

#847


Fixed integration tags for docker images

Closing. Already updated remote integration versions and tags to 3.0.1PE


AMBARI-22759 [Hive Views 2.0] Deleting a Saved query is Buggy

What changes were proposed in this pull request?
AMBARI-22759
[Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
How was this patch tested?
Tested in UI when a duplicate name saved query is deleted , exactly the same sved query is deleted than randon
NO UT Failures
[INFO] Results:
[INFO]
[INFO] Tests run: 99, Failures: 0, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:20 min
[INFO] Finished at: 2018-02-21T19:07:31+05:30
[INFO] Final Memory: 69M/908M
[INFO] ------------------------------------------------------------------------

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/729/
Test FAILed.
Test FAILured.

LGTM

LGTM.


Consider marking images that have been exported

And then based on this, could offer an Export All or Export New option

Added in #36.


The medium Level is not working atall

the issue is in FCMG

I have fixed this in: 1df44608d8471a04f78cad2d5133cd69ff81d2f7


Ability to validate inline inputs

Nothing on this?

Yes, it would be create if you could add this as a validation function to the column and then allow to highlight or somehow alert the user with a provided CSS class.

Looking forward to it.


Register pre-installed extensions for demo

Pick a set of extensions to pre-install
Ingest demo objects
Create simple mechanism (script? Bake into images?) for registering pre-installed Amherst extensions

Extensions that need to self-register do so via the loader service


login user back end

In GitLab by @lakhoune on Apr 6, 2020, 14:46

In GitLab by @lakhoune on Apr 11, 2020, 15:46
closed


Update .travis.yml

Test PR to reproduce default build script not running with only one version in the matrix

I think we should just delete the .travis.yml file instead. The JuliaLang organization has run out of Travis credit and I don't think anyone is applying for OSS Travis credits since they seem to have a lot of hoops you have to jump through to get them.

https://twitter.com/james_hilliard/status/1336081776691843072
yep, travis is gone.

Deleted .travis file in https://github.com/JuliaLang/Example.jl/commit/1c8e6057b587fe5cb291bd6917d830233ebf2f79


Enable object_name_linter for R code

At the moment the  object_name_linter is disabled in tests/unit/check_r_code.R. This linter should be enabled and invalid variable names fixed (mostly names with a dot in them, the dot should be replaced by an underscore).

Done in 1570.


Add more Complex methods (part 2)

Based on #699 since that was accepted before I added more :)
Continues #608.

Nice!


adding fix for ensuring fterm filetype is set

this fixes this issue here: https://github.com/beauwilliams/focus.nvim/issues/49
I found sometimes the filetype changes from fterm to term.

We can see now after we toggle fterm closed the filetype is still set to fterm

Thanks for the fix. Although I am not sure about setting filetype twice. First being inside the :create_win.

I just removed the first call and it seems perfectly okay so now we have only one.
One other thing I noticed is that either way, the filetype initially (first run only) was never set to "fterm" in either case.
So I also went and pushed a fix for that. 2ea07ce
It should now have 'fterm' filetype set both on first run, and on close. It seems there are two events we need to handle so we might need to set ft for the both of them.

Thanks for the fix. Although I am not sure about setting filetype twice. First being inside the :create_win method. Thoughts?
Edit: For more context see #13 #14

My last commit should help if not hopefully solve #13. They can use the filetype event to set options.
I think it was not working correctly earlier because 'fterm; filetype was not set on first run

Thanks for making the changes. I don't use filetype event myself but It seems fine to me.
Also, I am thinking of exposing win hl and blend  option anyway.

Okay sounds good then. I think exposing those options sounds like a good idea. Probably less room for error

@beauwilliams I left a comment can you address it? After that it should be fine to merge.

@beauwilliams I left a comment can you address it? After that it should be fine to merge.

sorry I couldn't find what comment we are referring to

I mean the review comment.

Do you mean add the option for hl and blend to the pr?

Nope, this one

Weird. I really can't see that suggestion..  I'll remove that line now

All done

@beauwilliams Thanks for your contribution :)

No worries 👍


Beta badges for webauthn

replaces #5977, couldn't unwind the rebase/merge situation.

thank you @ewdurbin


[BUG] uvicorn can not start FastAPI with example settings

import uvicorn
from fastapi import FastAPI
app = FastAPI(title='MADS API')
uvicorn.run(app, host='<IP_ADDRESS>', port=8127, workers=2)
WARNING:  You must pass the application as an import string to enable 'reload' or 'workers'.

than it quits with SystemError 1
Corresponding ticket in uvicorn
Versions:
$ pip3 list |grep "uvicorn\|fastapi"
fastapi                          0.55.1
uvicorn                          0.11.5

Why do you say it is a bug?
It is your first try at FastAPI?

No, i upgraded from Ubuntu 18.04 to Ubuntu 20.04. It was running fine on Ubuntu 18.04. productive a long time like this.

You must pass the application as an import string to enable 'reload' or 'workers'.

Is the program stopping here? Looks like it's only a warning but it's very straightforward about what's going on.

@phy25 Yes it stops here. I was searching through a bit, but only found this issue report on uvicorn under Windows.. But I think they are not really related.

When I try it as supposed in the related issues, it gives me errors as well:
uvicorn.run("app", host='<IP_ADDRESS>', port=8127, workers=2)
ERROR:    Error loading ASGI app. Import string "app" must be in format "<module>:<attribute>".

and
uvicorn.run("main:app", host='<IP_ADDRESS>', port=8127, workers=2)
ERROR:    Error loading ASGI app. Could not import module "main".

So uvicorn does not found the FastAPI application.

This is intended and not related to fastapi:
https://github.com/encode/uvicorn/blob/9b92925a352b9743c5cfcef4a65e74a81a1bad4f/uvicorn/main.py#L343
You need to run it with command line uvicorn if you want to run with multiple workers. Please read uvicorn documentation.

Thanks for the help here @phy25 ! :clap: :bow:
If that solves the original problem, then you can close this issue @cgi1  :heavy_check_mark:

The answer I was searching for is here: You can actually start it the way I wanted it, but make sure to name it correctly:
uvicorn.run("main:app", host='<IP_ADDRESS>', port=8127, workers=2)
ERROR:    Error loading ASGI app. Could not import module "main".

comes because the file is not named main.py! If you have it as my_fastapi_server.py, you run it as follows:
uvicorn.run("my_fastapi_server:app", host='<IP_ADDRESS>', port=8127, workers=2)

Adding another snippet as the ones posted here were pretty cryptic for me.
With the following files:
app\main.py    # Containing an app object
debug_server.py

I needed my debug_server.py to be:
import uvicorn

# Importing app here makes the syntax easier
from app.main import app

if __name__ == "__main__":
    uvicorn.run("debug_server:app", host="<IP_ADDRESS>", port=80, reload=True)

That way the debug auto-reload server did work properly and there’s nothing related to it in the /app folder.

I got following error
$ uvicorn main:app --reload
←[32mINFO←[0m:     Uvicorn running on ←[1mhttp://<IP_ADDRESS>:8000←[0m (Press CTRL+C to quit)
←[32mINFO←[0m:     Started reloader process [←[36m←[1m22984←[0m] using ←[36m←[1mwatchgod←[0m
←[31mERROR←[0m:    Error loading ASGI app. Could not import module "main".
←[32mINFO←[0m:     Stopping reloader process [←[36m←[1m22984←[0m]
I am using uvicorn [0.13.4] on Windows 10
Kindly suggest steps to resolve it.

The answer I was searching for is here: You can actually start it the way I wanted it, but make sure to name it correctly:
uvicorn.run("main:app", host='<IP_ADDRESS>', port=8127, workers=2)
ERROR:    Error loading ASGI app. Could not import module "main".

raises Error because the file is not named main.py! If you have it as my_fastapi_server.py, you run it as follows:
uvicorn.run("my_fastapi_server:app", host='<IP_ADDRESS>', port=8127, workers=2)

You can use pathlib to avoid this problem:
from pathlib imprt Path

uvicorn.run(f"{Path(__file__).stem}:app", host='<IP_ADDRESS>', port=8127, workers=2)

Try this.
if __name__ == "__main__":
    uvicorn.run("__main__:app", host="<IP_ADDRESS>", port=8000, reload=True)

What also worked for me was this:
inside the api.py file
if __name__ == "__main__":
    run(app="api:app", reload=True, port=8080, host="<IP_ADDRESS>")

What also worked for me was this:
inside the api.py file
if __name__ == "__main__":
    run(app="api:app", reload=True, port=8080, host="<IP_ADDRESS>")

This depends on your file being named api.py. Using __main__.app means you can rename your app.py file to anything and it will still work.
Further reading https://docs.python.org/3/library/main.html

Thanks for reporting back and closing the issue @cgi1 ! 🍰
And thanks everyone else for the discussions here. ☕


Fix timestamp parsing error

Timestamp parser updated to parse format 2020-11-11T19:29:18.096679+00:00

@ericwholt That timestamp was probably originally chosen for a reason -- any idea why it looked different when the plugin was created?

@ericwholt That timestamp was probably originally chosen for a reason -- any idea why it looked different when the plugin was created?

It may have changed in a version, but I am not finding documentation to support that. We know the version we are using is 6.7. I recommend we use that as a base line and if needed add other timestamp format options in the future.

Okay, sounds good to me 👍


Work around MemoryError when using an SSL endpoint

Thanks for your patch @jbq, in order for us to accept a pull request we need to have a jira ticket associated with it. Please see our contributing guide at http://thrift.apache.org/docs/HowToContribute


Get DIGBot running on staging

Rellies on #2
Once the staging server is up we can work on getting the bot hosted and running on it. At this stage we should ensure that the bot is at least as stable as the current version being run on live.
Hosting relies on Llama, once he works out how the bot is going to be hosted by the community we should be able to implement this soon as the initial master branch code will server for this purpose.

DIGBot is running, but does not automatically update yet. This will be addressed soon.


Supported More Text file for Peek

Description of the new feature / enhancement
Many files are in text format, and PowerToys Peek should try to guess that it is a text file and display it when it encounters a file it does not recognize.
Scenario when this would be used?
Such as .dockerignore and other files that do not have an open method set in Windows.
Supporting information
No response

/dup #26760


Delete secret mutation webhook

Description
Changes proposed in this pull request:

as in the title

Related issue(s)

https://github.com/kyma-project/serverless/issues/335

/test pre-serverless-operator-build


[docs] Have more details about FormControl, FormGroup etc.

So i've been trying to understand what are the different From* components are used for and what are the differences between them and what i should use with what.
I was forced to go to the source to actually understand what they do.
Should we have a more detailed information about those components? The documentation on the API doc is pretty minimal
Currently they are used in several examples yet i didnt fully understand their purpose.
For example, in the checkbox example all the checkboxes are placed in a FormGroup. They can be placed in a FormControl as well with a FormLabel (am i correct?), yet if i put a disabled prop on FormControl, the checkboxes are not disabled. Not sure if that's intended or not
<FormControl disabled>
  <FormLabel component="legend">Header</FormLabel>
  <FormControlLabel control={<Checkbox value="A"} label="A" />} />
</FormControl>

I have added more information to the API pages. It's better but not perfect.

I believe the example mentioned above would be useful to have on the FormControl documentation page.

@oliviertassinari at the moment I don’t feel confident in my full
understanding of the design and what the example should be. I’ll take a
deeper dive into the subject and may be could do something about it.
On Thu, 16 May 2019 at 15:31, Olivier Tassinari<EMAIL_ADDRESS>wrote:

@Gems https://github.com/Gems Do you want to add such an example for
the composition of the form input elements?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mui-org/material-ui/issues/8159?email_source=notifications&email_token=AACHTC7FPIRMKL2SF43K5D3PVVO2HA5CNFSM4D2RHSMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVRZ7PQ#issuecomment-493068222,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACHTCY7JADF7NPDDYMYKRTPVVO2HANCNFSM4D2RHSMA
.


CI: Add filter for virtualization testing.

Replace current virtualization test skipping mechanism with a ginkgo test filter. This allows creation of a new prow job to run virtualization tests separately from the other E2E tests. Setting TEST_VIRT to true now adds a "virt" filter to the test-e2e ginkgo command line, and all current virtualization tests are updated to have this label.

/retest

This might be a little hasty. I should probably make sure all the tests have good labels, and see if the virtualization tests actually need to be combined with the cluster type.
The filter mechanism itself is good though. Maybe it would be better to give prow more control over the filter, instead of just setting a virtualization-only test flag?

infra issue
/retest

/retest

/override ci/prow/4.12-e2e-test-azure
/override ci/prow/4.13-e2e-test-azure

ordered by the commander

well.. if the change doesn't in fact get tested by the tests.. who cares

due to the new tests being behind a label, the existing tests do not apply.
/override ci/prow/4.12-ci-index
/override ci/prow/4.12-images
/override ci/prow/4.13-ci-index
/override ci/prow/4.13-images
/override ci/prow/4.14-ci-index
/override ci/prow/4.14-e2e-test-aws
/override ci/prow/4.14-e2e-test-azure
/override ci/prow/4.14-images
/override ci/prow/images
/override ci/prow/unit-test

why have we disabled virt tests?

why have we disabled virt tests?

There is a new prow job for virtualization tests: https://github.com/openshift/release/pull/48623
The new job sets TEST_VIRT, which now sets up ginkgo labels to only run the virtualization tests and nothing else. The labels may need to be adjusted when there are actual VM tests to run. I took out the code that figured out when to skip the tests, so now it defers to prow.


Correcting version

This addition to T-SQL was added in SQL Server 2019, not 2012.

@way0utwest : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add rust implementation of ConfigPaths

This is a quite literal re-implementation of the ConfigPaths class from c++ to rust. The error handling is still c-style to make it easier to call from c++, but should be replaced with Result<_, _> eventually. You probably also want to drop the m_ prefix eventually.
This is still missing a wrapper to replace the c++ class as well as an implementation for process_args and i18n which I'm not sure I can provide.
Related to #286

I'm finally moving on this front! Just submitted #505, which is an implementation of a formatting function we need to make internationalization work. It's all in Rust, no C++, and I'd appreciate a code review if you can spare a moment, @kpcyrd.
In the meantime, I'll whip this PR back in shape, add gettext calls, and see to those FFI bindings.

A list of things I need to get done before merging this:

[ ] implement process_args
[ ] port tests
[ ] add FFI bindings
[ ] use gettext-rs and strprintf to internationalize messages

Our C++ tests for ConfigPaths make very good usage out of Catch2's SECTION macro. No such thing exists in Rust's default test framework; to add insult to injury, Rust tests are run in parallel, forcing us to use separate crates for each test. With that, our 1300 lines of C++ tests will probably expand into many thousands of Rust. That's both very tedious to write (I should know, I nearly died of boredom writing the C++ version), and hardly maintainable (C++ has very little repetition at little cost for readability; Rust will either duplicate a lot of stuff, or move parts of tests into submodules and hurt readability).
To get around this, I'm going to look into alternative test frameworks for Rust, and if none provide anything like SECTION, I'll see if it can be re-implemented and integrated with Rust's default framework somehow.

I'm not sure I fully get the problem, usually tests don't interfere with each other, but you could either use:
cargo test -- --test-threads=1

or add a global mutex that is locked by each test to force them to run sequentially.

There are two particularities in ConfigPaths tests as they are in C++, which turn into problems as tests are ported to Rust:

there is a lot of repetition in setup and checks. E.g. we need to set up a mock home directory, with ~/.newsboat directory, and ensure that ConfigPaths behave the same no matter if XDG dirs exist or not, and what values do XDG_CONFIG_HOME and XDG_DATA_HOME have. Catch2 lets us hide all this repetition with its SECTION macro. The following code is ran four times, with different combinations of two environment variables: https://github.com/newsboat/newsboat/blob/de404f3058491ed1b5568908208d299493030363/test/configpaths.cpp#L37-L100
Rust's test framework doesn't have anything like that. The closest we can get is move setup and checks into a free functions, and write four tests that run generic setup, then change environment variables, and run generic checks. But that leads to the second problem, which is:

environment variables are global to the process. As a result, no two ConfigPaths tests can run simultaneously within the same process. This isn't a problem in Catch2, because it runs everything serially, but turns into a problem in Rust.
This can indeed be solved with a global lock; thank you for the idea! --test-threads=1 is less useful in this case because not all of our tests are interdependent like that.

(I'm still going to look at alternative framework, just in case there is a cleaner solution somewhere.)

I had to lay this aside to work on i686 builds, but I'm back now. There are two crates that implement Catch-like syntax, ratcc and section_testing, but both seem to be in an alpha state, aren't maintained, and aren't used by anyone else.
Furthermore, I no longer think the lock is a good idea. I'll just bite the bullet and port each existing test as a separate Rust integration test. It's more honest this way.

I got bored and tried both crates. ratcc doesn't compile, but even if it did, it won't help us as it creates separate tests that would be executed in parallel—we would've had to employ the mutex hack or --test-threads=1 to combat that.
section_testing, on the other hand, compiles with Rust 1.26.0 and newer, and works just fine! I think I'm going to write all ConfigPaths tests with it, and bump the Rust version requirement. This will also let me revert this decision; one less hack in the codebase, yay.

Okay, cool, so tests fail with the same errors as C++ tests had. Time to resolve #561. I think this is caused by tests running under superuser on FreeBSD. Need to reproduce in a local VM to make sure.
i686 tests fail with out-of-memory errors, which is interesting. I don't see docks mentioning the exact memory limit, but the default for Linux VMs is 2G, and I can compile Newsboat just fine with docker run --memory=2G …. 1 gigabyte is not enough though, not for three simultaneous jobs anyway. Don't know what to do about that one yet.

Docker build fails even with 4GB of RAM, but works fine with 8GB. It just occurred to me that the cause might be a beefy CPU: Rust detects many cores and spawns many concurrent threads, eating up all the RAM. I want to see the current build go green, and then I'll try limiting Rust thread count to see if it works with default memory setting.

Nope, didn't help. I rolled back the changes, and now work on adding gettext and strprintf calls—the final things this PR needs to get merged.

Done! Tested it by commenting out the if, installing Newsboat into a local directory (with make prefix=localdir install), and adjusting LANGUAGE env var to see how message changes. It works.
@pickfire, @kpcyrd, feel free to review (note that the first two commits are from another PR, #561, cherry-picked here to make tests pass on FreeBSD). Otherwise I'll merge this in three days.

i686 build got rescheduled, which is considered normal according to the docs. Cirrus doesn't hide this from GitHub to be transparent about what it's doing. In short: the CI is green, this PR is good to go.

I can't say much about the C++ part, but the rust part looks fine for me.

somebody from irc pointed out that all functions in rust/libnewsboat-ffi/src/configpaths.rs (except create_rs_configpaths()) should be marked as unsafe

Why should they be unsafe? Just as an extra precaution against calling them from safe Rust? Their types should be a sufficient deterrent in that regard, and I'm careful about libnewsboat-ffi being at the root of the dependency tree—no Rust code will call these functions.
FWIW, Nomicon does not mention unsafe fn either.

Yes, the functions take arbitrary pointers (possibly invalid) pointers which would technically make them unsafe.
The difference in the docs is that it's in a extern "C" { block, which implies unsafe, while extern "C" fn foo() does not.
I agree that this is confusing, I just had this explained to me since I didn't know that either.

I pushed fixes for the last two comments. I'll create a PR fixing the same issues in other FFI bindings later, when we're done with this one.
But I still don't get why bindings should be marked unsafe:

Yes, the functions take arbitrary pointers (possibly invalid) pointers which would technically make them unsafe.

What's unsafe about taking an argument? Comparing it to null can't be unsafe either. Dereferencing it is definitely unsafe, though, which is why I put that line into an unsafe block. Marking the whole function unsafe seems overkill; aren't I supposed to keep the unsafe blocks as small as possible?

unsafe means slightly different things depending on context. An unsafe block means "I understand that the compiler can't check the safety of these operations, I promise to do this correctly". On a function signature, it means "this function has additional requirements for safety that cannot be checked by the compiler"
One test for whether a function should be marked unsafe is this: can safe code alone cause UB by calling this function? In this example the answer is yes: destroy_rs_configpaths(std::ptr::NonNull::dangling().as_ptr()). Because destroy_rs_configpaths does not (and cannot) verify that object: *mut c_void is actually a pointer to a ConfigPaths, it should be marked as unsafe.

Thanks for the explanation! I marked everything but the constructor.


Add Portuguese as a supported language

We've built our documentation using Nextra. Right now, only Spanish and English are supported, but we would like to support more languages.
This issue is for adding support for Portuguese.
How to add support for a new language
The project is structured following Nextra documentation. There are a lot of files that have several versions of the same file (e.g. introduction.en.mdx and introduction.es.mdx). To add a new language, create a new version of every file (e.g. introduction.pt.mdx) and translate the content of the file using the English version as the base.
Requirements

The language name for Portuguese should be pt
Include the new language in locales inside next.config.js
All files must be translated (including FAQ)
Spelling errors will not be accepted
We prefer effective communication over a literal translation. Some concepts may be better to leave in English if the Portuguese translation doesn't make much sense in Opire's context

/reward 20

/try

/try


Certain functions are undefined on iOS

After following the setup docs I still cannot use several functions.
Appcues.track() doesn't work as it will crash the app because it's undefined. Appcues.setup() and Appcues.identify() seem to work as they don't crash the app.
React Native - 0.74.6
Appcues - 4.0.1
Setup in App.js
useEffect(() => {
    async function setupAppcues() {
      await Appcues.setup('appID', 'code');
      await Appcues.identify('Jonathan');
      Appcues.track('asdfasdfasdf');
    }
    setupAppcues().then();
  }, []);

Usage in the app
<Button
  type={'mini'}
  color={'primary'}
  icon={'add'}
  onPress={() => {
    Appcues.track('Add button');
    setAddOpen(!addOpen);
  }}
  margin={'none'}
/>

Hi @Lump01, this is unexpected, and we can certainly try to help you pinpoint what may be going on here.
First, would  like to confirm the install instructions here, including the iOS pod install step.

In your app's root directory, install the Appcues React Native Modulenpm install --save @appcues/react-native
# OR
yarn add @appcues/react-native

Under your application's ios folder, runpod install

Is there any error message given in this case, or can you provide any more details about the app crash you're seeing? Double checking, this is not an Expo app, correct? I'm wondering if perhaps the setupAppcues() function isn't getting called before the usage in the <Button ... /> example. Even so, that should not crash the application.
We have a reference application in the example folder in this repo, if that helps at all to compare implementation code. In that app, the Appcues SDK is initialized here, and an example usage of tracking events can be found on the Events tab here.
For the actual track implementation itself, that function is defined in the iOS native module here, and implemented here.
The versions of React Native and the Appcues module you are using look good, thank you for providing that.

@iujames Thanks for getting back to me.
It's weird because in the code sample labeled "Setup in App.js" the Appcues.identify() method works because I see the user ID of "Jonathan" in Audiences > Users.
The code sample labeled "Usage in the app" is a later page that is under that same navigation tree as the "Setup in App.js". I have even tried calling Appcues.setup() again in the exact same page as the "Usage in the app" code sample to no avail.
My project is not expo, it's base React Native.
Here's the error I get on press of that button:

My apologies for the bother... I wrote this code at the end of the day.
I just realized that I wrote this:
import Appcues from '@appcues/react-native';
instead of this as my import statement:
import * as Appcues from '@appcues/react-native';
It now works!

Excellent! was just about to ask about that import 😀 - thanks for trying it out! Let us know if you have any further questions we can help with.


Suggestion

Can you add bot duels with easy hard medium and hacker difficulty 😁

Planning on doing this further down the line, alongside support for PocketMine-MP 4.0. Thanks for the suggestion.


Add a redirect from the docs site hosted in this repository to the new docs site

This PR adds files related to Jekyll (static site generator) to add the following functionality:

Automatically redirect visitors from the previous ScalarDL docs site (hosted in this repository) to the new ScalarDL docs site.
Track visits to the previous ScalarDL docs site (hosted in this repository) so that we can decommission it in the future (after confirming minimal or no impact on visitors).

I have tested the redirect (with different URLs) in my personal repository. In my test, I confirmed the redirect works as expected. Regardless of the page the visitor lands on on the previous docs site, they will be redirected to the new ScalarDL docs home page.

I guess these files are used by Jekyll. Sorry I am not familiar with it. If they work in your test, then I believe they are OK!
Thank you 🙇

@supl Thank you! You are correct. I've updated my initial comment to mention that this PR includes Jekyll files for easier reference in the future.


refactor(connector): remove default case handling

Type of Change

[ ] Bugfix
[ ] New feature
[ ] Enhancement
[X] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Fix issue https://github.com/juspay/hyperswitch/issues/2272
Changes to be made : Remove default case handling
Added all the ConnectorAuthType (which are not auth_type ) against the default case
File changed: transformers.rs (crates/router/src/connector/iatapay/transformers.rs)

Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Checklist

[ ] I formatted the code cargo +nightly fmt --all
[ ] I addressed lints thrown by cargo clippy
[ ] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

@HeetVekariya Can you please address the failing CI checks?
You need to run cargo +nightly fmt for formatting code, and cargo clippy --all-features --all-targets to catch compilation errors and common mistakes. Refer to the Cargo commands section on the contributing guidelines for more info.

@SanchithHegde I have done cargo +nightly fmt, but while running this command cargo clippy --all-features --all-targets i got this:

This changes are not done by me, as you can see in the images, So what should i do ?

Hey @HeetVekariya, as far as I understand, the ConnectorAuthType enum is not included under the scope of handling default cases. The enums that must be handled are primarily the payment methods related enums such as PaymentMethodData and PaymentMethod. You can also handle default cases for the IatapayPaymentStatus enum in your case.
And to clarify your question:

This changes are not done by me, as you can see in the images, So what should i do ?

Here, cargo is informing you that you haven't handled one variant (NoKey) of the ConnectorAuthType enum in the crates/router/src/connector/iatapay/transformers.rs file (check the first half of the compilation logs in your screenshot). In the later part of the compilation logs, it just shows where the enum variant has been defined, for your reference. Need not necessarily mean that there's an error in that file.

@SanchithHegde My bad, sorry for that. I found that i forget to include the NoKey against the default case, which causes the error.

@prasunna09 can you provide me more details, because i am not able to understand the suggested changes.

@prasunna09 I have added PaymentMethod cases against default case.

@SanchithHegde Thank you for merging
@prasunna09 Thank you for being with me for the queries.

Hey @HeetVekariya ,
Thanks a bunch for all your contributions! We've got a little something for you to show our appreciation.
Just take a moment to fill out this form, and get ready for some awesome swag coming your way.
Thanks!