Creating LoadBalancers does not work with OpenContrail

Affected binary: openstack-cloud-controller-manager (occm)
/kind bug
What happened: I am trying to use the openstack-cloud-controller-manager in a Kubernetes that is installed on OpenStack Ocata.
When I create a Service of Type LoadBalancer I get the following error-event:
 Warning  SyncLoadBalancerFailed  34s (x4 over 74s)  service-controller  Error syncing load balancer: failed to ensure load balancer: error creating LB floatingip {Description:Floating IP for Kubernetes external service default/my-service from cluster kubernetes FloatingNetworkID:fe4fa7de-7649-444b-96d8-c64248d3f8f4 FloatingIP: PortID:46858c5d-71c3-4996-910f-0784285c08fe FixedIP: SubnetID: TenantID: ProjectID:}: Bad request with: [POST https://redacted:9696/v2.0/floatingips], error message: {"NeutronError": {"message": "Unrecognized attribute(s) 'description'", "type": "HTTPBadRequest", "detail": ""}}

and the cloud-controller fails to provision the LoadBalancer.
What you expected to happen: Provisioning of the LoadBalancer should succeed without errors.
How to reproduce it: Try to create a Service of type LoadBalancer on an Openstack installation that is using OpenContrail
Anything else we need to know?:  The error is caused by the following line: https://github.com/kubernetes/cloud-provider-openstack/blob/a4ac35b8e879f597c666b05006e061814db0d2c6/pkg/cloudprovider/providers/openstack/openstack_loadbalancer.go#L1293 (but other lines the add descriptions to networking-resources will also cause similar problems).
I talked to our internal OpenStack-team and got the following response:
"we are using OpenContrail as an SDN and it doesn't support 'Description' no matter the OpenStack version"
This means, that at the moment this cloud-provider does not work for anyone using OpenContrail.
I see two possible solutions here:

Remove all "Description" fields from all create-requests for networking resources
Add a flag to the configfile (contrail_compatibility_mode=true??) and if that flag is set, set all "Description"-attributes to "" when creating networking-resources (and as the struct fields are tagged with omitempty, the fields will not be sent at all).

Environment:

openstack-cloud-controller-manager(or other related binary) version: 1.16.8
OpenStack version: Ocata
Others: OpenContrail as SDN

Also, here is the list of the OpenContrail components we are using and their versions:
OpenContrail 3.2 version

ii  contrail-config                      3.2~20180723125558-0              amd64        OpenContrail configuration management
ii  contrail-config-openstack            3.2~20180723125558-0              amd64        OpenContrail configuration OpenStack module
ii  contrail-control                     3.2~20180723125558-0              amd64        OpenContrail control-node
ii  contrail-database                    3.2~20180723125558-0              amd64        OpenContrail database integration
ii  contrail-dns                         3.2~20180723125558-0              amd64        OpenContrail control-dns
ii  contrail-lib                         3.2~20180723125558-0              amd64        OpenContrail libraries
ii  contrail-nodemgr                     3.2~20180723125558-0              amd64        OpenContrail nodemgr implementation
ii  contrail-utils                       3.2~20180723125558-0              amd64        OpenContrail tools and utilities
ii  contrail-web-controller              3.2~20180723125558-0              all          OpenContrail WebUI Controller
ii  contrail-web-core                    3.2~20180723125558-0              amd64        OpenContrail WebUI Core

just in case anyone is intersted.

According to https://releases.openstack.org/, Ocata is already Unmaintained (This doesn't affect this issue though, just a reminder).
According to https://docs.openstack.org/api-ref/network/v2/index.html?expanded=create-floating-ip-detail#floating-ips-floatingips, description is part of Neutron floating IP creation API, and the openstack-cloud-controller-manager supports OpenStack.
we are using OpenContrail as an SDN and it doesn't support 'Description' no matter the OpenStack version, this is not right, using OpenContrail as Neutron plugin shouldn't affect Neutron API, the floating IP description is stored in Neutron DB not OpenContrail.

So I don't think there is something we can do to solve your issue. Please let us know if you have any other questions.

While I agree with you, that "in theory" using OpenContrail should not affect the Neutron-API, I do get an "Unrecognized attribute"-Error from a Neutron-API that should definetly know this attribute.
The OpenContrail documentation does not mention "Description" as a supported field ( https://www.juniper.net/documentation/en_US/release-independent/contrail/information-products/pathway-pages/api-server/vnc_cfg_api_server.gen.html#vnc_cfg_api_server.gen.resource_common.FloatingIp ).
And at the moment I just do not have a better explanation for the error I am seeing.
I will create a fork of the provider, comment-out the offenting lines and check if this solves the problem.
If it is OpenContrail's fault or not. Something makes using the cloud-provider impossible on some OpenStack-clouds and that should be resolved.

Something makes using the cloud-provider impossible on some OpenStack-clouds and that should be resolved.

We only support official OpenStack API and I'm pretty sure Ocata Neutron should support description attribute of floating IP, https://github.com/openstack/neutron/blob/stable%2Focata/neutron/db/l3_db.py#L1322

@lingxiankong opencontrail doesn't have an ml2 plugin, it has a monolithic plugin and it doesn't use neutron db at all.
@dbaumgarten the description field is available in id-perms object in floating ip
I am using opencontrail r5.1 release with openstack neutron rocky. Moreover I am using the
NeutronPluginContrailCoreV2, i think you are using NeutronPluginContrailCoreV3 which is not supported.
I am able to create a floating IP with description field using openstack cli:
$ openstack floating ip create public --description "some description"
$ openstack floating ip show e3916775-8f3f-4eaa-a686-52a3559889e6
+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field               | Value                                                                                |
+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| created_at          | None                                                                                |
| description         | some description                                                                                |
| dns_domain          | None                                                                                |
| dns_name            | None                                                                                |
| fixed_ip_address    | None                                                                                |
| floating_ip_address | *.*.*.*                                                                                |
| floating_network_id | ************************                                                                                |
| id                  | e3916775-8f3f-4eaa-a686-52a3559889e6                                                                                |
| location            | cloud='', project.domain_id='default', project.domain_name=, project.id='*', project.name='services', region_name='*', zone=                                       |
| name                | *                                                                                |
| port_details        | None                                                                                |
| port_id             | None                                                                                |
| project_id          | *                                                                                |
| qos_policy_id       | None                                                                                |
| revision_number     | None                                                                                |
| router_id           | None                                                                                |
| status              | DOWN                                                                                |
| subnet_id           | None                                                                                |
| tags                | []                                                                                |
| updated_at          | None                                                                                |
+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+

This means that cloud provider should also have no issues with setting description field in floating IPs, please check your contrail version/configurations. Hope this helps!

The CLI command you used to test this does not work for me:
openstack floating ip create public --description "some description"
Error while executing command: BadRequestException: Unknown error, {"NeutronError": {"message": "Unrecognized attribute(s) 'description'", "type": "HTTPBadRequest", "detail": ""}}

I do not have access to the details of the OpenContrail installation (or configuration), and even if I did, I would not be able to change it.
So far it seems like I only have two options here:

Wait for an update of the Openstack/Opencontrail installation that hopefully fixes this.
Maintain a fork of this repo with changes that enable it to work with the current OpenContrail installation.

Neither of these sounds great...

One solution code be to attach the floating ip to neutron port by yourself:

create a neutron port
create a floating ip (without description field) and attach it to your neutron port
pass the port id in loadbalancer.openstack.org/port-id annotation
cloud provider will automatically pick up the floating ip attached to your port
when you delete your service type loadbalancer, cloud provider will simply detach the floating IP, it won't delete it.

let me know if this works for you!


add rule for vm in SecurityGroup to touch each other for issue2786

there are two places I modify:
1.when add vm to SecurityGroup
triggerApplyRules will always be true. fix it
2. add rule for vm in SecurityGroup to touch each other
for https://github.com/zstackio/issues/issues/2786

请教@MatheMatrix 后决定将这个fix 改为一个feature来做 https://github.com/zstackio/issues/issues/997


Font Scaling issue

For QuarmTool there's a font size scaling issue. It looks like the labels in the Mob window have a limited space to fill in and if you adjust font size it begins to be cut off.  The column for labels should change with window size.
Attached is a picture at font sizes 12 and 20.
Pictures

This will be fixed in the next release (v<IP_ADDRESS>).


Revert String() change to escaped string

Revert change from https://github.com/GoogleCloudPlatform/k8s-cloud-provider/pull/6
Fixes https://github.com/GoogleCloudPlatform/k8s-cloud-provider/issues/11

cc: @rramkumar1

/lgtm


How to set language?

I am unable to set the language for Selenium. According to my understanding, these two options are not supported:
@config = {
headers: { "Accept-Language" => "de-DE" }
}
or
options.add_argument("--lang=de-DE")

Hi there,
Did you manage to find a solution ?


docs: Add missing document link

Add link in the README to the existing cpuset doc which previously was not very visible.
Fixes #557.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

I think we can avoid a CI run for this one :smile:

I think we can avoid a CI run for this one 😄

We don't have the super power to force merge now :)

/test

hmm, metrics hit a build time fail - let me re-nudge:
10:49:40 Install CRI-O dependencies available for Ubuntu 16.04
10:49:42 FATAL: command execution failed

Ugh - 5 line doc change requiring full CI run...
/test

Nobody looking? Good...

@jodh-intel :smile:
form https://github.com/kata-containers/tests/pull/1583#issuecomment-493076736

@devimc - did you just merge your own PR? :-)
Not something we normally do on the kata repos...
I think that's the second (not just you...) I've seen in the last 24h - let's keep an eye on that practice folks....

cc @grahamwhaley

yeah, I know @devimc , but I am just one voice.... if others in the project feel they need to merge their own PRs to aid project velocity, then, well, we should probably agree at a project level and document that that is acceptable. Historically for the last 3+ years on this and some of its forerunner codebases though, it was not the norm. I'll likely still refrain from merging my own though :-)

@grahamwhaley - I don't believe we've actually documented either way? If all checks are passed, I don't personally see the problem (why do we need to wait for someone else to notice it's ready to merge when it's "ready to merge" and the author is happy to "do that work"? :)
However, if it offends sensibilities, do feel free to raise at the Arch Committee meeting so we can thrash it out.


WIP: Migrate cargo readme

After the suggestion in https://github.com/usbalbin/iter_fixed/pull/23#issuecomment-2171733720 I test to migrate Readme management to cargo-readme.

move some information in crate documentations
add the template README.tpl for generation
add crate badge to experimental
do some documentation improvement

RFC: This is wip, I'm interested about comment, spelling correction, etc

#25 is this PR + CI checking if the readme is up to date. Do you think something like that would make sense?

Yes it's a good idea, I made some small comments.
But with the change I'm validate.
I you have no remark to my change, you can merge it, and then the #25 (with adjustment).
And after, release a new version :+1:

Thanks a lot :)


Fixes documentation links in Readme

Update the links to the Transpiler, Middleware, Renderer, and Webpack Plugin Readme's to link to the packages directory.

Hey @BlakeSimpson, thanks for these fixes! 🎈
We'll give the docs a major overhaul soon to reflect the changes we're working on in the betas, but for the time being, this is really helpful.
Would you mind adding yourself to the contributors section in the main readme file? After that, I'm happy to merge.

Hey, glad to help out :)
There is no contributors list in the main readme but I guess you meant the root package.json contributors list? I've added my name there now, if you meant somewhere else let me know :)

Thanks - and of course you got it completely right! Sorry for the mixup.


[ARQ-653] Reworked configuration sharing between client and container side.

It's using yaml serialization/deserialization to pass only relevant bits of the persistence extension configuration.
I was having troubles trying to use the same approach on the container side as it's used in ConfigurationRegistrar (Shrinkwrap). Details here: https://gist.github.com/1396309
Pros: compact representation with only relevant stuff for persistence extension.
Cons: different approach, additional dependency for the extension (if you don't want to use YAML for datasets).

Thanks for the review Aslak. I will clean it up and push upstream soon.

Changed as suggested and pushed upstream.


Indicator does not stick to the currently selected tab when scrolling

When using a TabBarTop with scrollEnabled the indicator for the selected tab demonstrates strange behaviour. When scrolling inside the tab bar, the indicator does not remain fixed to the currently selected tab. Instead, it moves a bit along the scrolling direction before settling into the correct position.
It can be reproduced using one of the examples provided (https://github.com/react-native-community/react-native-tab-view/blob/master/example/src/TopBarTextExample.js). It can also be noticed in the GIF below.

Due to the way it's implemented, it's impossible to make it follow the scroll, at least not until we can implement native animation events. It's more important to have good frame rates for the indicator rather than making it follow the scroll. Perhaps one day we'll be able to change the implementation to make it follow the scroll properly without having to sacrifice on frame rate. But it's still a long way to go. I think the current behaviour is good enough since we avoid anything abrupt and animate the indicator nicely.


nconf uses github reference

github reference to nconf is causing npm install issues. Any chance this can be switched back to a registry reference? Thanks!

this has been resolved in >= v1.6


Update handling-client-impersonation-in-umdf-1-x-drivers.md

"In UMFD versions 1.9" should be "In UMDF versions 1.9"
"UMFD" is an abbreviation for "User Mode Font Driver"

Docs Build status updates of commit e29b2e9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-driver-docs-pr/wdf/handling-client-impersonation-in-umdf-1-x-drivers.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Thanks Terry, appreciate the sharp eye!  The fix should appear on the live site within 5-10 minutes

Docs Build status updates of commit e29b2e9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-driver-docs-pr/wdf/handling-client-impersonation-in-umdf-1-x-drivers.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Private field is promotable in spite of noSuchMethod forwarder

The following test fails in both analyzer and CFE
class A {
  final int? _x = 42;

  void testA() {
    if (_x != null) {
      _x.isOdd;  // No expected error
//       ^^^^^
// [analyzer] unspecified
// [cfe] unspecified
    }
  }
}

class C {
  void _x();

  dynamic noSuchMethod(Invocation inv) {}
}

main() {
  A a = A();
  if (a._x is int) {
    a._x.isEven;  // No expected error
//       ^^^^^^
// [analyzer] unspecified
// [cfe] unspecified
  }
  a.testA();
}

According to the https://github.com/dart-lang/language/issues/2020#issuecomment-1663069707 if there is an implicit noSuchMethod forwarder in the same library field should not be promotable
cc @stereotype441
Tested on Dart SDK version: 3.2.0-edge.655687db777cf07cb4d75398f9eaf2d30ab6af44 (be) (Wed Sep 13 02:35:01 2023 +0000) on "macos_x64"

Sorry, that comment doesn't reflect what I actually implemented. What I actually implemented was exactly what @eernstg suggested, namely that a forwarder for a method does not interfere with the getter of a final instance variable. Promotion is only cancelled if there is a noSuchMethod forwarder with the same name which is a getter. I've updated that comment accordingly.
So in @sgrekhov's example, no error should be reported. Which matches the behaviour as of b555e71ecdcca112f449da1656b273663aa65d83.
I'm assigning this issue to myself as a reminder to update the text in the CHANGELOG to reflect this subtlety.


Detect MIPS R9000 ELFs

Needs to adjust rabbitizer config for proper disassembly

Done in https://github.com/encounter/objdiff/commit/9e57a66a05d9b3410db09f539fa3e3fd797df397


Felix debug logs turned on in calico.yaml

http://docs.projectcalico.org/master/getting-started/kubernetes/installation/hosted/k8s-backend/calico.yaml
has
            - name: FELIX_LOGSEVERITYSCREEN
              value: "debug"

in the calico-node section.  Should this be set in a production system?

This appears to be fixed in the latest release, but the CNI plugin is still set to debug level.

We will soon be introducing k8s 1.7 manifests, so let's at least fix this up in those manifests.


Return value of assigned array

Adds the name of the lhs array to the end of the returned expression. I think that's all which is needed to "fix" #22?

Can you figure out why Travis CI is failing?

I don't think it has anything to do with my changes. Could you try manually triggering a build for master, for comparison?
The error for the 0.5 test seems to be an instance of this -- the solution for which would be updating to 0.6 (because the OpenSSL version used in 0. 5 is too old for Github).
For nightly, I have no idea. Maybe the semantics of @simd have changed in 0.7.

Thanks it seems to be working on 0.6 which is good enough for me.


Ensure user is logged in to access /multicloud/ansibletower

Signed-off-by: Kevin Cormier<EMAIL_ADDRESS>

/cc @RobDolares

/cherry-pick release-2.6

/cherry-pick release-2.5


Configure logging to log to Stackdriver (when flag is set)

Logger has a console handler (logging.StreamHandler) and a syslog handler (logging.handlers.SysLogHandler). On GCE instance we install the fluentd logging agent which will transparently pass the syslog entries to stackdriver.

I haven't cleaned up all the imports yet, mostly the ones that were nearby the log_util import.
Changed logger to use the SysLogHandler and removed the cloud logging related stuff. PTAL.

Coverage increased (+0.2%) to 65.867% when pulling 06d2cb5251b463d481b548493f1efb62c9ae8d8e on configure-logging into 8e614bad7a24cc91e067c0ae790b72e12cb9f8b4 on master.

Coverage increased (+0.2%) to 66.167% when pulling f2876d7fafb4cf27a82f4cbe7de2b049867e038e on configure-logging into 7d4757ddc6c4e9a8e04ad2646d93fee03bec6b0f on master.

Adding cla: yes label, as the PR author is a googler at the time of this PR was created.


HBASE-28954 Apply workaround for HADOOP-19164 for Hadoop 3.4.1

The fix didn't make it into Hadoop 3.4.1

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for branch

+1 :green_heart:
spotless
0m 58s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m  6s

Maven dependency ordering for patch

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
spotless
1m  0s

patch has no errors when running spotless:check.

Signed-off-by: Duo Zhang<EMAIL_ADDRESS>Signed-off-by: Wei-Chiu Chuang<EMAIL_ADDRESS>


[WIP][DRAFT] HADOOP-18842: Support Overwrite Directory On Commit For S3A Committers

Description of PR
Support Overwrite Directory On Commit For S3A Committers. Refer HADOOP-18842 for more details
How was this patch tested?
TODO: Add Unit Tests
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
48m 21s

trunk passed

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
0m 39s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 36s

trunk passed

+1 :green_heart:
mvnsite
0m 45s

trunk passed

+1 :green_heart:
javadoc
0m 29s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 39s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 13s

trunk passed

+1 :green_heart:
shadedclient
34m  0s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 32s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
compile
0m 27s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 27s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 22s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 4 new + 1 unchanged - 0 fixed = 5 total (was 1)

+1 :green_heart:
mvnsite
0m 32s

the patch passed

+1 :green_heart:
javadoc
0m 18s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 27s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m  5s

the patch passed

+1 :green_heart:
shadedclient
37m 21s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 38s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

137m  0s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5931/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5931

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux ad70282e531c 4.15.0-212-generic #223-Ubuntu SMP Tue May 23 13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0deb83f01fad90dc8594d1712f604fe1c43d9bed

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5931/1/testReport/

Max. process+thread count
555 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5931/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


PWACompat update post

What's changed, or what was fixed?

Adds PWACompat update post

Target Live Date: 2018-07-17

[ ] This has been reviewed and approved by (NAME)
[ ] I have run npm test locally and all tests pass.
[ x ] I have added the appropriate type-something label.
[ ] I've staged the site and manually verified that my content displays correctly.

CC: @petele

Whoops!
There were 1 critical errors that broke the build and prevented it from being automatically deployed.
There were 2 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
ERRORS
src/content/en/updates/2018/07/pwacompat.md - Page is missing page title eg: '# TITLE {: .page-title }'
WARNINGS
src/content/en/updates/2018/07/pwacompat.md#L59 - '

Whoops!
There were 2 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2018/07/pwacompat.md#L67 - '


Jenkins plugin does'nt visualize old simulations after upgrading to Jenkins 1.597

After upgrading to the latest Jenkins (1.597) I have som issues with the Jenkins gatling plugin, and that is that it does'nt seem to find old simulations. If I go in to a specific gatling simulation build, there is no gatling-button there (in the left menu), and it seems like the plugin is not able to find and visualize the simulation. If I run a new build everything works as expected.
My first thought is that this has something to do with the new JENKINS_HOME layout that Jenkins has implemented in the latest version (see https://wiki.jenkins-ci.org/display/JENKINS/JENKINS-24380+Migration and https://issues.jenkins-ci.org/browse/JENKINS-24380 for more information).
On the server, all the simulations seems to lie there, and the new folder structure has been implemented by Jenkins.

Closed by https://github.com/jenkinsci/gatling-plugin/pull/9


Via 3 fails if "url" parameter is missing on route_by_content view

We currently fail with an un-handled exception if we omit the URL param when routing by content.
We should catch this and raise a sensible error.

Done!


Improve ncdump handling of time units

This PR changes the strcmp and strncmp calls to strcasecmp and strncasecmp calls in nctime.c, nctime0.c to account for the case-insensitive nature of UDUNITS unit names, and adds a test by piggybacking on the calendar focused test in ncdump/.

Great catch, Sean.  Thanks!


move deprecated kwargs from trainer to trainingargs

Description
This PR should help resolve some of the upstream changes in main that will break tests when we upgrade.

Motivation and Context

How has this been tested?

Screenshots (if appropriate)
Types of changes

Social Handles (Optional)

additional tests against upstream main here https://github.com/axolotl-ai-cloud/axolotl/actions/runs/11761420503


Difficulty opening Neurodesk packages in Neurodesktop

Hello. I recently installed neurodesk but am having some trouble getting the individual packages to work. In the neurodesktop environment, I can open most things (like office software and internet), but when I select anything in the neurodesk menu, I get a terminal window that produces an error message before closing itself. The error comes after it attempts to launch the container (in this case fmriprep):
FATAL         exec /usr/bin/cat failed: invalid argument
FATAL           exec /bin/bash failed: invalid argument
Is this a bug or am I doing something wrong? I've tried this on several different computers now with different versions of MacOS and have gotten the same result. The machine I have mostly tested on has an M1 processor with MacOS 13.6.1.
Thank you in advance for your help!
Anthony

Dear @salilabwfu,
This is, unfortunately, a recent bug of Docker on Apple Silicone. The workaround is to use Podman instead of Docker.
So install podman (https://podman.io/) and then select podman in the neurodesk app:

Let us know if this works
and we very much hope this bug can be fixed soon.


Example - 3D Renderer

Description
To coincide with the game jam, we should render a Tiled map in 3D [#16] for use in a dungeon crawler game. This includes debug wireframes/rendering, a GUI, audio, etc. This will prepare us for infrastructure that we won't have to deal with during the week.

This will be done through pulde via glTF


Unit tests for reading from stdin

Streaming to stdin is currently broken and untested but is a very important feature. Support the following syntax:
cat sample-data/polygons.geojson | gj2ascii -

Check to see if multi-layer support is needed via -,LAYERNAME.

This appears to be untestable.


Solution for map operator testcase

I merged the same code from master to solved to keep branches consistent and took two solutions from this branch. Thanks for your contribution @ritesh-singh


Hide pages in docs and algolia

Changelog

hide docs pages (tours,guides ,api-reference, parsley index)
hide algolia api
remove packages
'@uiw/react-codemirror';
'@codemirror/view';
'@codemirror/lang-javascript';
'@uiw/codemirror-theme-github';

This PR comments out the problem areas. The problem areas commented out needs to be investigated.
I upgraded the CPUs to 4 with always on CPU and 2GB more of ram. This should buy us time to solve the problem @darwin808 . If it does solve the problem it will be a temporary increase in resource until the problem is resolved.
Please return the uncommented code and review the parsley functions for iteration leaks or timeout issues. Thank you

@ardeay can we merge this to prod for testing/monitoring and revert the cpu/memory to original then we can monitor it if the issue exist
also most error 504 is this pages

also saw our virtual size jump +8mb

please see #1710


Market Creation Pending Bug

i think this is related to https://github.com/AugurProject/augur.js/issues/27


cannot import name '_imaging' from 'PIL'

ImportError: cannot import name '_imaging' from 'PIL' (/usr/lib/python3/dist-packages/PIL/__init__.py)
Get this error after install and run demo

python3.9 -m pip install -U Pillow
This row is help me


DNS config example not working

Is this a BUG REPORT or FEATURE REQUEST?: BUG
What happened: dnsConfig in https://github.com/argoproj/argo/blob/master/examples/dns-config.yaml not working
What you expected to happen: container dns config should be changed
How to reproduce it (as minimally and precisely as possible): kubectl -n default create -f dns-config.yaml
kubectl get pod <pod_name> -o yaml
check the dnsConfig
Anything else we need to know?:
Environment:

Argo version: v2.2.0

$ argo version

Kubernetes version : 1.12

$ kubectl version -o yaml

Other debugging information (if applicable):

workflow result:

$ argo get <workflowname>

executor logs:

$ kubectl logs <failedpodname> -c init
$ kubectl logs <failedpodname> -c wait

workflow-controller logs:

$ kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name)

Not reproducible.


Avoid using deprecated commands in task

The kubectl run way of creating Deployment is deprecated. This PR
replaces it with the new equivalent command.
closes: #18978

/lgtm
/cc @soltysh

Thanks!
/approve


Added a responsive spotify webpage

Responsive Spotify webpage using Html and Css Mediaqueries.

Hey @thecyberbuzz I have added a responnsive Spotify_Webpage using Html and Css Media queries...Can you please merge it under hactoberfest2023 label!!


calc tests - plus,mul

added tests for three calc operations: +, *.

Just a few small comments.

@vext01 review comments addressed

LGTM. Please squash.

squashed

bors r+


Broken download link for rhino

The do_fetch job for rhino is failing. Going to the link in the recipe https://github.com/downloads/mozilla/rhino/rhino1_7R4.zip returns 502 status code with message "Error downloading file".
On the Github page for Rhino, there is a release titled Rhino1_7R4_RELEASE. It has a download link for the source zip file which works: https://github.com/mozilla/rhino/archive/refs/tags/Rhino1_7R4_RELEASE.zip
While it's tagged as the same version, the sha256 of the zip file is different than the one listed in the recipe. Unfortunately I don't have the zip file from the original link to be able to run a diff on the contents

I am also blocked on this. I do have a version (with the correct MD5 hash) which I could use, but need a clean build for a release without manual intervention. Is there any progress?

resolved by #7


[QUERY] client side encryption with BlockBlobClient

Query/Question
How to use BlockBlobClient to download and upload with ClientSideEncryption?
I know the BlobClient can handle Client Side Encryption thing, But our code currently is using BlockBlobClient, and it seems that this class is not supported the client side encryption download and upload.
Environment:

Azure.Storage.Blobs 12.5.0

Found the clue from SDK source code


Ok, maybe now the unix and git notes files are in the right place??

Many thanks in advance for your "patients", I hope i got it right.

This PR is better. But it still contains unnecessary files.
https://github.com/codefellows/sea-w25-uge/pull/29/files

oops, i am answering emails out of order, sorry, these new tabs in gmail
.... So, the question is, did I pass?  I have added a new GitHub account
for my own android project and was eventually able to get it pushed up to
the new account "brightquasar" is my other username on GitHub email:
<EMAIL_ADDRESS>so I have more to practice with, and it
complicates authentications etc. having two accounts on one PC.
On Mon, Mar 9, 2015 at 8:24 AM, Ryan Sobol<EMAIL_ADDRESS>wrote:

This PR is better. But it still contains unnecessary files.
https://github.com/codefellows/sea-w25-uge/pull/29/files
—
Reply to this email directly or view it on GitHub
https://github.com/codefellows/sea-w25-uge/pull/29#issuecomment-77874435
.

I am sorry, but closed #29 is greek to me. Probably only because I am not
even a student there yet?
On Mon, Mar 9, 2015 at 8:24 AM, Ryan Sobol<EMAIL_ADDRESS>wrote:

Closed #29 https://github.com/codefellows/sea-w25-uge/pull/29.
—
Reply to this email directly or view it on GitHub
https://github.com/codefellows/sea-w25-uge/pull/29#event-248602258.

Unfortunately, this pull request is not adequate. I closed it so you could try again.

I see, thanks for the clarification.  I have paid to attend the next
workshop, perhaps I'll see you there.  I have switched from windows to a
MacBookPro so, I am having to learning to use OSX etc. before I will start
again on gitHub.
On Thu, Mar 12, 2015 at 1:30 PM, Ryan Sobol<EMAIL_ADDRESS>wrote:

Unfortunately, this pull request is not adequate. I closed it so you could
try again.
—
Reply to this email directly or view it on GitHub
https://github.com/codefellows/sea-w25-uge/pull/29#issuecomment-78603014
.

Good idea. OS X is really big and I think it's a really smart of you to learn it will before starting a course with us. Here are a few links that you may find useful. Good luck!
https://www.youtube.com/watch?v=wSPisJXyjso
http://www.atomiclearning.com/mac-os-x-10.10-yosemite-training
http://www.lynda.com/Mac-OS-X-tutorials/Mac-OS-X-Yosemite-Essential-Training/179057-2.html
http://www.lynda.com/Mac-OS-X-tutorials/Mac-OS-X-Yosemite-New-Features/181883-2.html


Bootstrap 4?

Bootlint is incredibly useful, but I am not sure it's currently compatible with BS4.
Any info would be appreciated.

Correct, Bootlint is not currently compatible with Bootstrap 4, but I'm hoping that support is added at some point. There's an open PR with a lot of good work on adding BS4 support here:
https://github.com/twbs/bootlint/pulls


Add support for Oracle/PostgreSQL JSON validations

Test case
Oracle:
CREATE TABLE dvt_test.tab_json
(
  id VARCHAR2(10) NOT NULL PRIMARY KEY
, col_json1 CLOB
, col_json2 CLOB
);
ALTER TABLE dvt_test.tab_json ADD CONSTRAINT tab_json_chk1 CHECK (col_json1 IS JSON) ENABLE;
ALTER TABLE dvt_test.tab_json ADD CONSTRAINT tab_json_chk2 CHECK (col_json2 IS JSON) ENABLE;
INSERT INTO dvt_test.tab_json VALUES (1,'{"a": 1}','{"a": 1}');
COMMIT;

PostgreSQL:
CREATE TABLE dvt_test.tab_json
(
  id varchar(10) NOT NULL PRIMARY KEY
, col_json1 json
, col_json2 jsonb
);
INSERT INTO dvt_test.tab_json VALUES (1,'{"a": 1}','{"a": 1}');

Oracle uses CLOB/NCLOB columns for JSON data, we should be able to compare these with PostgreSQL JSON columns. At a minimum, for column validation, we should be able to compare by string length like we do for some other string columns.
We need to check all validation types. Search for "issue-1338" in the repo.
We might need to revert some of the changes from https://github.com/GoogleCloudPlatform/professional-services-data-validator/issues/1335.

We should add json/jsonb columns to the pso_data_validator.dvt_pg_types test table.


feat: add propagation tests for SNS raw message delivery enabled / disabled

Motivation
Ensure propagation works for both message format types
Changes
Adds another test. Adds required query parameters
Workflow

⚠ Create your PR as draft ⚠
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
Framework is modified, or non obvious usage of it -> get a review from R&P team

:rocket: Once your PR is reviewed, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist

[ ] If PR title starts with [<language>], double-check that only <language> is impacted by the change
[ ] No system-tests internal is modified. Otherwise, I have the approval from R&P team
[ ] CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
[ ] A docker base image is modified?

[ ] the relevant build-XXX-image label is present

[ ] A scenario is added (or removed)?

[ ] Get a review from R&P team

I'm converting to draft, to decrease the stress level on my notification queue 😄
You can convert it to normal once the CI is green !


possibility to define a default png to be rendered outside the coverage of a source

Using
  bgSource:
    type: tile
    url: 'file:///mapproxy/multimapproxy_conf/bg.png'
    grid: GLOBAL_WEBMERCATOR_4_V3

works in some cases, but not with metatiling

I solved same issue with additional wms-like server which returns background image
https://gist.github.com/ramunasd/90229d7db167374ec5b6b34be20f98a4


Privileges needed to create properly

Need to add proper privileges to dittybopper namespace with 4.12 cluster version and future verisons
11-30 08:47:36.192  + ./deploy.sh
11-30 08:47:36.192
11-30 08:47:36.192
11-30 08:47:36.192      ____  _ __  __        __
11-30 08:47:36.192     / __ \(_) /_/ /___  __/ /_  ____  ____  ____  ___  _____
11-30 08:47:36.192    / / / / / __/ __/ / / / __ \/ __ \/ __ \/ __ \/ _ \/ ___/
11-30 08:47:36.192   / /_/ / / /_/ /_/ /_/ / /_/ / /_/ / /_/ / /_/ /  __/ /
11-30 08:47:36.192  /_____/_/\__/\__/\__, /_.___/\____/ .___/ .___/\___/_/
11-30 08:47:36.192                  /____/           /_/   /_/
11-30 08:47:36.192
11-30 08:47:36.192
11-30 08:47:36.192  Using k8s command: oc
11-30 08:47:36.192  Using namespace: dittybopper
11-30 08:47:36.192  Using default grafana password: admin
11-30 08:47:36.192
11-30 08:47:36.192  Getting environment vars...
11-30 08:47:36.756  Command "get-token" is deprecated, and will be removed in the future version. Use oc create token instead.
11-30 08:47:36.756  error: could not find a service account token for service account "prometheus-k8s"
11-30 08:47:37.013  Command "new-token" is deprecated, and will be removed in the future version. Use oc create token instead.
11-30 08:47:37.270  Prometheus URL is: https://prometheus-k8s-openshift-monitoring.apps.scaleci12-301040.qe.azure.devcluster.openshift.com/
11-30 08:47:37.270  Prometheus bearer token collected.
11-30 08:47:37.270
11-30 08:47:37.270  Creating namespace...
11-30 08:47:38.199  namespace/dittybopper created
11-30 08:47:38.199
11-30 08:47:38.199  Deploying Grafana...
11-30 08:47:40.805  service/dittybopper created
11-30 08:47:40.805  route.route.openshift.io/dittybopper created
11-30 08:47:40.805  Warning: would violate PodSecurity "restricted:v1.24": allowPrivilegeEscalation != false (containers "dittybopper", "dittybopper-syncer" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (containers "dittybopper", "dittybopper-syncer" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or containers "dittybopper", "dittybopper-syncer" must set securityContext.runAsNonRoot=true), seccompProfile (pod or containers "dittybopper", "dittybopper-syncer" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
11-30 08:47:40.805  deployment.apps/dittybopper created
11-30 08:47:40.805  configmap/sc-ocp-prom created
11-30 08:47:40.805  configmap/sc-grafana-config created
11-30 08:47:40.805
11-30 08:47:40.805  Waiting for dittybopper deployment to be available...
11-30 08:47:53.001  deployment.apps/dittybopper condition met
11-30 08:47:53.001
11-30 08:47:53.260  You can access the Grafana instance at http://dittybopper-dittybopper.apps.***.qe.azure.devcluster.openshift.com/
11-30 08:47:53.260  + popd
11-30 08:47:53.260  ~/ws/workspace/nch-pipeline_cluster-post-config

Fixed in https://github.com/cloud-bulldozer/performance-dashboards/pull/60


Demo page bug

If you make a selection on the demo page, hit enter, then click on the highlight you get an uncaught exception self.wrapperNodes is undefined.

Thank you, I will look into it :)


VnV Review: Clarification of 'tol' in Test Case Formulas

In most test case formulas, I see 'tol', but it's not specified what this means. I searched the document and found its meaning, 'tolerance', along with its corresponding value, in the appendix section. Perhaps specifying it at the beginning of the test cases and providing a reference to the appendix would be a good idea.

Fixed with #22


Improve sticker's load

sticker's load taking lot of time even with hi-speed internet on first launch.. user's were not sure what's happening and leading to a bad first time experience

Hi @deepakbharanikana can you pinpoint where the slowness comes from? Is is the image downloads, server calls, etc? Are you loading webp versions of the images? They substantially smaller than PNG's to download. There are many imaging libraries around with webp support. We offer bifrost but you can also use Fresco or other libraries for that.

Closing… Please recreate the issue if you are still experiencing problems

We are using the messaging sample code from your repo in our app. When the app is launched for first time and tapped on a button that shows stickers,  here nothing will load..  If I close the app from background and start again then everything works normal
Thanks Deepak
Sent from Yahoo Mail on Android
On Tue, May 3, 2016 at 3:02 PM, Nima<EMAIL_ADDRESS>wrote:
Closing… Please recreate the issue if you are still experiencing problems
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Have you tried overriding onError in your WrappedAsyncTask to see if anything is showing up there?
Ex: https://github.com/imojiengineering/imoji-android-sdk/blob/master/imoji-android-sdk/src/androidTest/java/io/imoji/sdk/ErrorTests.java#L74

Will let you know
Sent from Yahoo Mail on Android
On Tue, May 3, 2016 at 5:20 PM, Nima<EMAIL_ADDRESS>wrote:
Have you tried overriding onError in your WrappedAsyncTask to see if anything is showing up there?
Ex: https://github.com/imojiengineering/imoji-android-sdk/blob/master/imoji-android-sdk/src/androidTest/java/io/imoji/sdk/ErrorTests.java#L74
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub


pypi search results delayed

reported by @JacksonMaxfield
described & discussed on the napari zulip
Description
napari-aicsimageio was updated to 0.3.4 on July 11, however as of today (July 12) it is not showing up on the napari hub.
Steps/Code to Reproduce

see the package on pypi at https://pypi.org/project/napari-aicsimageio/
see the plugin on the napari hub at https://napari-hub.org/plugins/napari-aicsimageio

Expected Results

the hub should show 0.3.4

Actual Results
the hub shows 0.3.3
Additional information
presumably, the napari hub has not recognized that the plugin is updated because the pypi search page still lists the version as 0.3.3: https://pypi.org/search/?q=&o=&c=Framework+%3A%3A+napari
however, BiqQuery does seem to have the correct data (h/t @tlambert03 )
SELECT DISTINCT  name, version, home_page, summary
    FROM `bigquery-public-data.pypi.distribution_metadata`
    LEFT JOIN UNNEST(classifiers) cl
    WHERE cl='Framework :: napari'

when we were spec'ing the napari hub, we wanted to make sure that plugins showed up within 5 minutes of being pushed to PyPI and determined that querying BigQuery every 5 minutes didn't meet our requirements. from @ziyangczi 's notes...

Pros/Cons:

Pro: Does not require traffic to pypi
Con: Requires google project setup. Also we are bound by the update frequency of this dataset and cannot improve scan rate beyond that. It is not documented how frequently it is updated and it can change at any time.

Findings:

Still require a backend, can’t solely rely on integrating bigquery API to website due to volume constraint, the bigquery sandbox(basicly free usage) give 1TB of query capacity, however each query would require 1.2 G to run simply to get the names of the plugins. So we cannot run more than hourly update from this method

I can think of at least two possible solutions here that would be fairly straightforward without querying BigQuery more than once per hour....

when we poll pypi, we no longer consider the version listed at the search page to be the latest... instead, we use that list then check the individual package endpoint to get the latest version
we could also do the BigQuery search daily or hourly to sync our cache

note: this package finally showed up, but this should still be fixed for future plugins

I am hoping to see another case that this happened so we understand better the frequency, and possibly the reason why this is happening, before taking action to add changes on our end.

reviewing bugs. curious if you are still seeing this @haesleinhuepf?

No, I haven't seen that issue for quite a while! Feel free to close this. And big thanks to whoever fixed it ☺


Update README for new (0.2) screenshots;

Add new screenshots, showing "Crusader Network Tester 0.1";
Update README and CHANGELOG to pass markdownlint with minimal warnings

I'd avoid formatting and changes in the same commit. You could probably drop the screenshots as they're already out of date.

re: Formatting and screen shots... The screen shots match the released (0.1.0) version. This allows newcomers to get the right idea about the program.
But Crusader is moving fast (that's GREAT! And you're addressing my comments. That also makes me feel terrific!) I am content to "play catchup" for the next couple development cycles. I wouldn't mind a general "roadmap" of additional changes you you plan to make. Thanks.

@Zoxc I think this README has caught up to the 0.2 version. Let me know if it needs tweaks. Thanks

Good catch. I removed both Crusader-Results.png and Crusader-Latency.png - both were renamed.

Thanks!


Viruses

I have started coding the viruses into the game so with the server side I went into config and saw no way during the heart beat to tell if the target is a virus or a food or player, am I missing something or do I need to add that?

You could add it to the users list and then do users[e].isVirus == true then the current hit testing code will work.

I had set it up as its own list and was going to have it check in the heart beat if the collision has occurred and if it had to steal half the players mass but to do that it was necessary to know if the player had encountered a food or virus and there is nothing in food to tell if it is a food or not so should  i add an isFood=Ture and an isVirus=False to food and the opposite to Virus

or maybe a type

In the actual agar they use isVirus, http://agar.io/main_out.js?531

is that a function that checks or is it a property

Hey, in order to avoid duplicates, could we please move this discussion to #25 so people can find details about Viruses in a single place?
Thanks! :)

Sorry I don't realize there was already an issue on the viruses
On Jun 9, 2015 5:05 PM, "Igor Antun"<EMAIL_ADDRESS>wrote:

Hey, in order to avoid duplicates, could we please move this discussion to
#25 https://github.com/huytd/agar.io-clone/issues/25 so people can find
details about Viruses in a single place?
Thanks! :)
—
Reply to this email directly or view it on GitHub
https://github.com/huytd/agar.io-clone/issues/194#issuecomment-110504043
.


Reset initiated if we disable

when we disable, previous initiated state is still store. After we enable scrolling, some event get trigger because we have a initiated state.

poke @bjornstar


Permit running on remote servers

Tests can now be run on remote servers (Selenium server or Sauce Labs) or locally.  Further work required to enable remote tests to connect to an existing Dossier stack instance and reset state to a pre-determined point.

Sweet! Thanks!


Adding direct_message views

Adding direct_message_list view and direct_message_create view
Adding main_messages, message_form and direct_message html files
Adding direct button on base.html
Adding direct_message_view tests
fix #137

For now it looks like this:
![image](https://user-images.githubusercontent.com/90772515/168459947-23e93fef-74ce-442d-abf2-caa45b2726f4.png)
![image](https://user-images.githubusercontent.com/90772515/168459967-7ce254fd-aa0b-4a33-b7d0-7ef2ab96198b.png)
![image](https://user-images.githubusercontent.com/90772515/168459985-5791cad0-c938-41f3-a25e-3d0ef13586f5.png)

Maybe we can add some more tests here? For example, what should happen after a new message is created, a redirect or something else?

Maybe we can add some more tests here? For example, what should happen after a new message is created, a redirect or something else?

Done

@TomerNewmanPrograms Please squash all the commit :)


(CFA1, LMFC, FTC_001, FingerTip) These electronic circuit boards have not found corresponding folders and PCBs in the project. Please help me, thank you very much.

(CFA1, LMFC, FTC_001, FingerTip) These electronic circuit boards have not found corresponding folders and PCBs in the project. Please help me, thank you very much.

cc @icub-tech-iit/silo-electr

hi @xilihutu888 the board are:
CFA1: https://github.com/icub-tech-iit/electronics-boards-public/tree/master/other-boards/can-filter
MAIS-FC: is in the same folder of the MAIS: https://github.com/icub-tech-iit/electronics-boards-public/tree/master/sensor-boards/mais
FTC and FTC-con: https://github.com/icub-tech-iit/electronics-boards-public/tree/master/other-boards/ftc
the fingertips are not released open-source yet

hi @maggia80
I have received the latest documentation information. Thank you very much for your reply. Is there any alternative to the iCub header (CCG012, COMe-cKL6)? Can I download the electronic circuit board (PCB, BOM)?

CCG012 is the only one that fits and it's from https://connecttech.com/ . The COM-express Compact Type 6 COMe-cKL6, could be replaced with any other COMe Type 6 Compact but we tested only this one. You need to pay attention to the heat sink, it must fit into the head.

The problem has been solved, thank you for your reply.


Cost optimization v0.4 workbook - Reservation section fails to load

🐛 Problem
Cost Optimization v.03 and v.04 bug with resource type not found.
👣 Repro steps
Open v.03 or v.04 cost opt workbook.
Rate optimization
Azure reservations
First load "no reservations recommendations found" < typo there too.
Change term or anything else, auto refresh.
This query could not run because some parameters are not set.
Please set: Resource type

Resource type never has anything other than "All"
📷 Screenshots

Everything else seems to function ok.
Savings plan rec is 'no recommendations found'. We do have a high utilisation savings plan, but I thought i'd get a rec at 3y. Not sure.
This is an EA account.

@psilantropy The first issue is already fixed on the version that we will release later this month.
About the savings plan issue, do you see any recommendations on Advisor?
This workbook tab copies the data from Advisor, so if you don't have any recommendations there, you won't see anything on the workbook either.
The break even point is the only calculation we are doing in the workbook. Everything else comes straight from Advisor via Azure Resource Graph queries.

@psilantropy The first issue is already fixed on the version that we will release later this month. About the savings plan issue, do you see any recommendations on Advisor? This workbook tab copies the data from Advisor, so if you don't have any recommendations there, you won't see anything on the workbook either. The break even point is the only calculation we are doing in the workbook. Everything else comes straight from Advisor via Azure Resource Graph queries.

Great, thank you.
Savings plan: Yes it looks like you are right, thanks for the information.


Inefficient use of Vec::push in prepare_uniform_components function

I created a stress test scenario with the Bevy engine (link) where I created 100K entities. I noticed that the prepare_uniform_components function was using 4.23% of the CPU time, and upon investigating the code, I found that the Vec3::push method was being called for each of the entities, which is not efficient.
To improve performance, I suggest copying all the objects in batches instead of pushing them one by one. Apart from that, DynamicUniformBuffer::write can be optimized as well. I am attaching my Flamegraph to this issue.
https://github.com/bevyengine/bevy/blob/aefe1f0739bb395d2454e05a1a812acab767892c/crates/bevy_render/src/extract_component.rs#L126-L153

@CrazyRoka turns out the values Vec is basically unused. #8299 removes it. As for the performance issues with encase, I strongly suggest making a PR upstream to address it. The flamegraph you provided definitely shows there's some non-trivial overhead when using it.

@james7132 Thank you for your PR to improve Bevy performance. I have 2 more questions:

How did you measure performance improvements in your PR?
Can we replace component_uniforms.uniforms.push(component.clone()) with batch write? I was diving deeper into the implementation and it looks like each push call creates Writer Cursor, writes and closes this complex object. I think it will make a difference to open WriteCursor once and write all the components together.

How did you measure performance improvements in your PR?

I used Tracy and the trace_tracy feature. You can find the docs on how to use it under docs/profiling.md in the repo.

Can we replace component_uniforms.uniforms.push(component.clone()) with batch write? I was diving deeper into the implementation and it looks like each push call creates Writer Cursor, writes and closes this complex object. I think it will make a difference to open WriteCursor once and write all the components together.

Batch insertion probably is for the best here. We need to construct both the buffer and the Vec for Commands, and preallocating then skipping the capacity checks likely will have a significant speedup. Though with that said, with dynamic uniform offsets being pessimistically aligned to 256 bytes, we might not see much gain there.


XBox S/X Controller Won't Pair With a Different Aquarius+

XBox s/x controller paired with a rev2 prototype Aquarius+, but would not pair with a second, different Aquarius+ signature edition. It would pair with a Windows PC, and when the original rev2 prototype was turned on, it paired back with it as well, but would never pair with the second Aquarius+.

All systems tested were running V0.17a

Please retest if running all systems on V0.17 (without 'a') makes a difference.

Downgraded both systems to V0.17. At first, it would not pair with the "new" system. I unplugged and installed the "old" system, forced a re-pairing while old Aq+ was on, then immediately turned it off. Re-plugged-in the "new" system and was able to pair it.
Not sure if it was a V0.17a issue, or oddities with paired device memory.

Issue came back on the "new" unit. Controller, blinks, appears to pair, and then loses conneciton and goes back to blinking again. Went back to V0.17 to confirm, and it still happens.
Seems to only want to pair with the original Aq+.

Now on V0.22a. Even after an esp:settings > sysreset, I can't get an XBox s/x controller previously paired with another aqplus to pair with another, different aqplus. Controller pairs with a Windows 11 PC and an actual Xbox Series S game console.
I've tried on two different Aq+ Minis and on two different Aq+ standard units to no avail. I've tried fresh batteries, I've tried "resetting" the controller (power on, go into pairing mode, force power off, try to re-pair).

Performed Xbox controller firmware update and problem is resolved.


Need clarification on /authorize endpoint

The sample is using the following in the script for Start.cshtml:
let authorizeEndpoint = "https://login.microsoftonline.com/common/oauth2/authorize?" +                         toQueryString(queryParams);
However the documentation here says:

To get the correct token for Microsoft Teams Free and guest users, it is important that the apps use tenant specific endpoint https://login.microsoftonline.com/{tenantId}. You can get tenantId from the bot message or tab context. If the apps use https://login.microsoftonline.com/common, the users will get incorrect tokens and will log on to the "home" tenant instead of the tenant that they are currently signed into.

Can you clarify the scenarios for /common and /tenantID?  Also, for multi-tenant apps the endpoints listed in the Application Registration page point to the /organization endpoint.  When should that endpoint be used?

We are closing this issue for now, Please feel free to reopen it, if required.


[FEATURE REQUEST] Add a current status filter to the search.

What feature are you suggesting?
The ability to filter by current record status.
Is your feature request related to a problem?
"I was hoping to be able to filter out by-laws from the past two years with statuses of amending and repealing." - m.j
Are there any workarounds?  Are there any alternative solutions that would work?
Not easily.

Added to "Records by Record Type" report.
d0469c1111b45a6dca1f146b5f583d84c77b61c6

Filter implemented.
e85d0b9e313f2a66fe3ea956302afea6e320b868


Update build.gradle

Multidex migration

Pls merge this, it need to avoid android jetifier

Is there any way to force this library to use androidx.multidex instead of com.android.support?
The situation is just stupid, this is the only library that's stopping me from disabling jetifier

Thanks man!🧡🫡


Use Markdown parser for comment text

It doesn't look like this plugin takes advantage of the built-in markdown parser.

Text is parsed as Markdown. message().

Oh, my mistake. I noticed my smartypants settings (curly quotes, etc.) weren't being applied to the comment text. I thought markdown handled that. It turns out kirbytext() is the function that parses through smartypants.
Would you consider using kirbytext() instead of markdown() in the message() function?

kirbytext() is dangerous, as you are able to access custom kirbytext extensions when writing a comment.

It would expand the commenter's ability to insert inline YouTube videos, or properly obfuscated email addresses. I don't think this is inherently dangerous.
On second thought, this does add a degree of complexity and site owners might not realize that their commenters can use kirbytags.
How about just running the smartypants filter after markdown(): https://github.com/getkirby/kirby/blob/fe9d8c5e70a3d73a41e3f3e10cb0fb62fc3a2611/core/kirbytext.php#L55

Some thoughts:

Inline YouTube-videos may violate the privacy of your users by exposing their visit to YouTube
Kirby developers are able to write their own kirbytext extensions, which might offer greater attack vectors than the default kirbytext “tags”. (a “read file” kirbytext extension might be a good idea for inserting text-snippets, but it is able to expose secrete config files)

Applying smartypants is a good for English websites, but it may be an issue when writing comments in different languages. I think it’s best to offer smartypants as an option.

Smartypants settings can be applied per-language:
https://forum.getkirby.com/t/is-it-possible-to-change-options-for-smartypants-dependent-on-the-language/1940

I will an option for smartypants (default: enabled), so that it can be disabled for certain languages.


Pure ascii

Some clients doesn't support unicode well, or at least only partly.
Initially I tought that conversion to ISO-8859-1 (Latin 1) or  ISO-8859-15 etc. might work, but then I noticed that a lot of post now contains ’ (for things like I’m) instead of '. And then there are emojis.
So maybe --ascii should use something like https://github.com/anyascii/anyascii#rust (and have the option --unicode keeping the original unicode)?

Does the current --ascii not work well with your client? I just made a change to it, so a regression may have occured

It's not directly related to nkizz/mop3#4
It's more that som clients doesn't support Unicode, or only support Unicode as definded some time ago (i.e. no emojis). I suspect debugging might also be easier when it's possible to convert to pure ascii.

That is exactly what the --ascii flag should do, are you using that? because if you are, it shouldn't be sending any non-ascii characters

Ah, I see now that deunicode should do the same.
But it doesn't seem to be any difference between using --ascii and not.
For example https://ganesha.social/@sophia/110616728918181522
become:
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Ganesha 0.3 is ready for a test run. Careful though, there are still lot's o=
f
sharp corners and features flat out missing. Oh, and moving forward, Ganesha=

requires iOS 17.

=E2=86=92 [https://testflight.apple.com/join/6fjaxCwS][1]

[#Ganesha][2] [#AppStore][3] [#TestFlight][4]

[1]: https://testflight.apple.com/join/6fjaxCwS
[2]: https://ganesha.social/tags/Ganesha
[3]: https://ganesha.social/tags/AppStore
[4]: https://ganesha.social/tags/TestFlight

https://ganesha.social/@sophia/110616728918181522

mop3 --account<EMAIL_ADDRESS>--token "…" --pop3port 1100 --url --ascii  --nosmtp

This is a bit of a necropost, but I thought I'd put an explanation here for future reference.
This is a regression from switching from assembling the emails manually to using a library. The library was outsmarting me and escaping utf-8 to make it 7-bit clean. This means there wasn't actually any unicode in the email to deunicode, since it had already been escaped. It now adapts the text before passing it to the library, which transforms it correctly.
The messages still report the charset as utf-8, but my guess is that a client will either ignore that header, or respect it and handle the ascii correctly. The fix will be committed soon
Thanks for the report!


Use devnet-wallets in test-harness

In order to maintain only a single source of wallets for testing test harness should use wallet data files stored in dusk-blockchain/devnet-wallets instead of dusk-blockchain/harness/data/. In addition, this will allow us to run test-harness with more than 10 nodes (up to 119)

They are already being used, and were swapped in the commit https://github.com/dusk-network/dusk-blockchain/commit/28b9b3de31210254b8ab1294776dc551ca3ab399.

They are already being used, and were swapped in the commit https://github.com/dusk-network/dusk-blockchain/commit/28b9b3de31210254b8ab1294776dc551ca3ab399.


DGL Refactor (rapidsai/cugraph#4486)

Applies rapidsai/cugraph#4486 to this repository.

@tingyu66 we still need it because of how the containers are built.  They have to be able to build without PyTorch or DGL/PyG


🐛 Bug Report: Error when we add repo environment variables and secrets in github

📜 Description
Hi,
I have a template where I create a repository with step code called publish:
- id: publish
  name: Publish
  action: publish:github
  input:
    repoUrl: ${{ parameters.githubHost }}?owner=${{ parameters.githubOrganization }}&repo=${{ parameters.repositoryName }}
    repoVisibility: private
    defaultBranch: develop
    repoVariables:
      REGISTRY_FOLDER: ${{ parameters.repositoryName }}
      SONAR_SCAN: "true"
      PRISMA_SCAN: "false"
      PRISMA_CODE_SCAN: "false"

This step works properly and I have the repository with repoVariables and secrets inside.
After that, I have another step where I create and environment for the repo with the following code:
- id: envPreEnv
name: Create Pre Environment
action: github:environment:create
input:
repoUrl: ${{ parameters.githubHost }}?owner=${{ parameters.githubOrganization }}&repo=${{ parameters.repositoryName }}
name: pre
environmentVariables:
CLUSTER: ${{ parameters.repositoryName }}
DB_CONECTOR: ${{ parameters.repositoryName }}
DB_SCHEMA: ${{ parameters.repositoryName }}
REPLICAS: ${{ parameters.repositoryName }}
secrets:
DB_SECRET_NAME: ${{ parameters.repositoryName }}
ROLE_TO_ASSUME: ${{ parameters.repositoryName }}
And when it´s executed, I have and error in the log
66 2024-05-30T15:12:57.988Z Beginning step Create Pre Environment
67 2024-05-30T15:12:59.933Z HttpError: Not Found - https://docs.github.com/rest
68    at /app/node_modules/@octokit/core/node_modules/@octokit/request/dist-node/index.js:125:21
69    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
70    at async requestWithGraphqlErrorHandling (/app/node_modules/@octokit/plugin-retry/dist-node/index.js:71:20)
71    at async Job.doExecute (/app/node_modules/bottleneck/light.js:405:18)
I´ve removed the code to create environmentVariables and secrets (just the env name) and it works like a charm.
Pat permissions are ok, but I don´t understand why is not working
👍 Expected behavior
Create environment with variables and secrets provided
👎 Actual Behavior with Screenshots
It gives an error
👟 Reproduction steps

📃 Provide the context for the Bug.

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Hey @jaalvarezuria,
can you please provide more information about this issue?
As it depends what kind of values did you use in parameters.
I'm a bit puzzled to see "https://docs.github.com/rest" during the github publish

Hi @acierto,
Thanks for you response. It´s very strange because I tried several options and all of them give me the same error. In fact, I tried to create variables and secrets in the same way as you can find in the documentation (http://yourserver/create/actions)

and the result is the same.
If I remove everything related with variables and secrets (just create an environment), github:environment:create works properly.
Let me know if you need more information, but it´s all I can find in the logs.
Thanks

Hello, I can also confirm this issue. But i didnt know you can add Repo Vars as below, thanks for sharing and reporting.
repoVariables:
  REGISTRY_FOLDER: ${{ parameters.repositoryName }}
  SONAR_SCAN: "true"
  PRISMA_SCAN: "false"
  PRISMA_CODE_SCAN: "false"

Hi @ext-mohamed-el-taier ,
Repo vars are added using   action: publish:github and environment vars uses action: github:environment:create that it´s different, that is why it´s working for repo var but not for environment vars.
I hope somebody can help us to know what´s happening with action: github:environment:create
Thanks

Is this related to #25042?

@benjdlambert yes, it´s the same problem. What I have done it´s create a github action with github api calls to create variables and secrets and call from bakcstage with a github:actions:dispatch

@benjdlambert yes, it´s the same problem. What I have done it´s create a github action with github api calls to create variables and secrets and call from bakcstage with a github:actions:dispatch

nice, bit scrappy though. Are you feeding the secret your action encrypted?
I am also getting intermittent 404 errors when I try to create Github Environment after Publishing a Repo(but it works 70% of the time), which leads me to think there is a consistency issue with Github API.

No, I´m feeding the secret with random data and I´m populating it directly in github. What I want to do it´s set all vars and secrets needed to perform actions, as a base template.
Regards.

I also get a failure when creating secrets for a GitHub environment.
I am using GitHub App for authentication.
And am trying to create a repo environment (yaml definition is below), with a secret.
But I keep getting the error "Bad request - validation failed due to an improperly encrypted secret".
    - id: create-dev-github-environment
      name: create dev github environment
      action: github:environment:create
      input:
        repoUrl: ${{ parameters.repoUrl }}
        name: dev
        deploymentBranchPolicy:
          protected_branches: false
          custom_branch_policies: true
        customBranchPolicyNames:
          - dev
        environmentVariables:
          USER_NAME: dev_cicd_user
        secrets:
          PASSWORD: "this is not the dev password"
        token: ${{ secrets.USER_OAUTH_TOKEN }}

Hi guys, it seems this issue is related to this https://github.com/backstage/backstage/issues/25042.
The Github Actions plugin is using an Octokit that uses different types of identifiers for Github Repo, which would explain the 404's.

I think that this should be fixed now in later releases as we've closed #25042, closing this issue, if it still persists for someone feel free to comment and we can re-open.


Weaken wording regarding idle timeout notifications?

Section 9.1.6 Idle Timeout
Consider replacing "must" with "should" in the phrase "the
P4Runtime must generate a stream notification".  "must" seems to imply
that an implementation can guarantee it will send such a message, but
this seems impossible to guarantee for most reasonable-cost
implementations, e.g. a table with 1 million entries has an idle
timeout of 1 millisecond for all entries, and no packets match any
entries for a long time.
Same comment for this phrase where it occurs in Section 16.4 "Table Idle Timeout Notification"

Is this the same as #116 ?

Yes, closing this one.  Must have fat-fingered the creation of the earlier issue and accidentally created two of them.


New PowerFx formula bar does not highlight open/close parentheses or curly brackets when on same line and ctrl + F does not open find window

I keep trying to use the new Power Fx experimental feature for the formula bar but I keep turning it off.
Often I write code on one line with complicated if statements or AddColumns statements.  Keep in mind that you cannot format the code if there are any errors. Often errors occur because you are missing a closing ")" or "}". In the current formula bar editor, the editor will highlight the matching bracket or parentheses to the best of its ability which is important for troubleshooting to remove errors so you can format the code and clean it up.
In the new formula bar the only indication of an open or close statement is the very faint line connecting the lines together. This is only accessible with properly formatted, error-free code. This just isn't enough if you have errors and can't format the code. Can you provide an extension that will highlight matching brackets and parentheses? I really can't use the new feature.
Also, pressing ctrl F in the current formula bar would open a small find window in the top right (very useful). The new formula bar does not have ctrl F find, rather it goes to the search menu item on the far left vertical menu panel (not so useful).
See screenshots below:
No closing brackets highlighted (new formula bar):

closing brackets highlighted (current formula bar):

Hi @kayetter, thank you for reporting this issue and your feedback on find + replace feature. As we announced earlier this year, we are actively considering new functionalities for the new formula bar and that includes find and replace as well. We've fixed the bracket highlighting issue that you encountered, and it is rolling out as i write this reply. It should be fully available in production by the end of this month. Thank you once again for bringing this to our attention. We would love to hear any other feedback you may have and would encourage you to fill any other issue related to new formula bar in forum here https://powerusers.microsoft.com/t5/Power-Apps-Community/ct-p/PowerApps1.


Sporadic C# compilation issue

Over the past few days, a few function apps have run into a compilation failure that seems to be caused by an attempt to queue additional Roslyn compilation events after the compilation is marked as completed, leading to an InvalidOperationException with the message: Cannot enqueue data after PromiseNotToEnqueue.
Opening this for investigation and tracking.

Looks like a Roslyn issue, we are following up with them.

@fabiocav any updates on this? If we don't have a date for when this is likely to be unblocked I think I should move it out of the January milestone.

Still an ongoing discussion with the team. It's not likely to be unblocked in this milestone, but it sounds like there has been some work done to address this issue in 2.0.0 (Roslyn)

This is still happening, three different function apps, and different functions within each app are now presenting the same problem as covered here

@DamianFlynn thank you for reporting. Unfortunately, a restart is indeed the way to address this at the moment, but we understand this is not ideal. We'll be working on updating the compiler references soon, now that 2.0 has been released, both, to address issues like this and bring C# 7.0 support.

This issue occurred in a Queue bound function yesterday, nearly ruining a demo we were giving to a customer. The function in question was deployed weeks ago and just suddenly stopped working. As we're using the consumption model, I didn't find an obvious way to restart them as suggested by @DamianFlynn. I just disabled and reenabled the function, which seems to have solved the issue.  Do you have an ETA on when this will be resolved?

Ran into this here as well: http://stackoverflow.com/questions/43085082/azure-function-with-servicebustrigger-stops-receiving-messages?noredirect=1#comment73298766_43085082

I am currently converting my solution to a class library. Will this approach circumvent the problem until such time as 2.0 is live?
Thanks
Get Outlook for iOShttps://aka.ms/o0ukef

From: Fabio Cavalcante<EMAIL_ADDRESS>Sent: Thursday, March 23, 2017 5:27:53 PM
To: Azure/azure-webjobs-sdk-script
Cc: Damian Flynn; Mention
Subject: Re: [Azure/azure-webjobs-sdk-script] Sporadic C# compilation issue (#999)
@DamianFlynnhttps://github.com/DamianFlynn thank you for reporting. Unfortunately, a restart is indeed the way to address this at the moment, but we understand this is not ideal. We'll be working on updating the compiler references soon, now that 2.0 has been released, both, to address issues like this and bring C# 7.0 support.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-webjobs-sdk-script/issues/999#issuecomment-288797527, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AF_zD6I7Ftxj8btjo0yl6yYGTlRI20EOks5roquZgaJpZM4K-Tqm.

Assigning this back to triage so we can get traction on this - customers are hitting this, and we're also seeing this in our runner from time to time, generating sev 2 incidents.

Just ran in to this issue today as well on an HTTP triggered function. Restarting the app service brought everything back up. Also on consumption plan.
@tomasmcguinness: you can restart the service by going to the function app like normal, then function app settings, and under the "Manage" section click on "Go to App Service Settings" and from there you can stop and start it like a normal app service.

Reopening for triage as this did not get resolved as expected

We need a workaround so the app doesn't end up in a permanently stuck state when this occurs.

@fabiocav added retries and additional logging in attempt to address this, see https://github.com/Azure/azure-webjobs-sdk-script/commit/f24f85cd1c2f0ad4a5f2c1bc12f86faeb8b13d1a
This change should be deployed globally by 7/21. If it reproduces beyond that we should reactivate.

Was the change deployed on 7/21? I've got the similar error with my function today

I seem to have run in this problem today, while editing a functions app via the Azure portal. It's the first time I've experienced this problem. Like others also mentioned, a restart of the Web application resolved the problem.

I just ran into this for the first time. It appears to have started sometime between Friday afternoon and this morning. Like all the others, the restart worked fine for me, though is obviously not ideal.
Mine was an HttpTrigger and consumption plan. I hope it is obvious how this is problematic - things just stop working without changes by us and without warning.
Any updates on this?

We've reached out to the compiler team as we were still seeing instances of this happening. We've put some mitigation steps that help some scenarios, but as you found, we're not as aggressive with those steps.
We did get an update from the team and there's a fix in the latest compiler version. We'll be deploying that with our next release.

I ran into this issue today with an .csx Script Function. Does a precompiled deployment fix this?

@rs38 yes, it does, as there's no runtime compilation in those scenarios. This is being addressed in this sprint.

I can confirm that we are seeing this issue on our eventhub triggered functions.
We saw it last week on our consumption plan function, and again today on another consumption plan function.

@MeshTucker, fixes to address this are being rolled out and should be fully deployed by Wednesday. You can subscribe to this issue to receive updates: https://github.com/Azure/app-service-announcements/issues/39

@fabiocav : I hit this today, when visiting the portal. Function just stopped working without making any changes to it. Restart worked. Waiting on this fix to be deployed fully.

FYI I just got this today when editing a function in the portal.

I just got this today. Refer to screenshot below. I really need this fixed as we are relying on functions in production. This issue caused a reporting system to go down - I've not changed the function in a month or two.

same here, restart was needed

Ran into this issue over the weekend, our function app stopped working on 7/28/18 at 11:51 PM Pacific Time. When I logged into Azure Portal and looked at the app's code, I saw the erorr notification with the message "Cannot enqueue data after PromiseNotToEnqueue." Restarting the app fixed it.

Ran into this issue over the weekend, our function app stopped working on 7/28/18 at 11:51 PM Pacific Time. When I logged into Azure Portal and looked at the app's code, I saw the erorr notification with the message "Cannot enqueue data after PromiseNotToEnqueue." Restarting the app fixed it.

Guys - we're looking at this now and will get a fix out for this in the next release.

Until the fix is deployed globally, the best workaround is to switch to writing your function as a class library in VS or VS code (e.g. https://docs.microsoft.com/en-us/azure/azure-functions/functions-develop-vs) so that no compilation is required on the server side. I understand that moving from csx to cs is not 100% trivial and it might not be viable, but I would say that we are still at least a week away from having this fix be deployed globally so you might want to consider it. Sorry I dont have a better workaround to share right now.

This issue still exist!

Hi @paulbatum ,
Is there an update / fix to this issue?

It seems that despite multiple attempts to address this issue through roslyn updates and other mitigations, this error can still occur. I don't have any updates to share at this time. The same recommendation that I made before still applies - you can completely avoid impact by deploying compiled binaries. Our dev tools in VS and VS Code make this straightforward.

We are planning on taking another Roslyn update (see the issue referenced above).

Another customer is raising the same issue 183252697.


PipelineBase should not contain multi key operations

PipelineBase should not look like it contains multi key operations.
This is modification of #2007 and #2025

@DvirDukhan PING! as you were the author of related PRs.

@sazzad16 I think we should also add these methods to the interfaces MultiKeyBinaryRedisPipeline and MultiKeyCommandsPipeline

@gkorland MultiKeyBinaryRedisPipeline and MultiKeyCommandsPipeline contains actual Redis commands. Because of this conflict, we already have an open issue #2029 related to this.


[Question] about the ec tool project and the right version to use

Hi there,
As stated in this project README, fw-fanctrl

uses fw-ectool to change parameters in FrameWork's embedded controller (EC).

the link refers to the DHowett/fw-ectool project, which is a fork of the Framework team's FrameworkComputer/EmbeddedController project.
The main concern here is that the DHowett/fw-ectool project is a whopping 10098 commits behind the official project.
I imagine that there are reasons for using DHowett/fw-ectool instead of FrameworkComputer/EmbeddedController, but I cannot seem to find any information or documentation about it either in DHowett/fw-ectool or in this project and would appreciate a bit of context about this choice.
Thank you and have a great day.

Yes, the project actually moved to Gitlab: https://gitlab.howett.net/DHowett/ectool
I forgot to update the link in the readme, I'm on it

Thank you @TamtamHero , btw you forgot the first link of the readme in your last commit :)

Under the hood, it uses fw-ectool to change parameters in FrameWork's embedded controller (EC).


Optics

[ ] Test / validate Headers.normalForm
[ ] use non snapshot dependency of Monocle
[ ] upgrade argonaut with compatible version of Monocle (may not be needed if next version of argonaut has core dependency free)
[ ] test optics using scalacheck (problem require to define Arbitrary instances for all core model)

Sorry for letting this PR open for so long :(
I don't think I will have time to work on it anytime soon and I don't want to rush something half done and let other people maintain it, so I would suggest to drop it for now. It can always be reopened later. WDYT?

I'll put a freezer tag on it and leave it open.  Hopefully someone can pick it up and run with it.  Thanks for the head start!


cli.py should check_schema before using it.

The documentation suggests "first verify that the provided schema is itself valid, since not doing so can lead to less obvious error messages and fail in less obvious or consistent ways" but the command line utility does not follow this advice.
If it is desirable to not recheck the schema on every run for performance reasons related to scripting it would be possible to instead check the schema just when the cli tool is called with no instances (which currently appears to be effectively a no-op), but I would prefer it on every run (since multiple instances can be provided in a single execution).

Yup, agreed. Any chance you'd be interested in a PR?

Not really.  There are several different ways the issue could be resolved and I don't think it's my place to determine which of those methods is correct, especially since I have no particular understanding of this project, or more than a passing familiarity with Python.
For my purpose because I am calling the validator from other code as well I have changed the Validator.__init__ function, adding the line schema is not self.META_SCHEMA and self.check_schema(schema).  I chose this because it is more convenient for me to know that any validator object has a legal schema attached, but I don't know how this fits into the scope of your project.
Going forward I think I am likely to abandon JSON schema in general anyway since I need more expressive power, meaning either XSD1.1 or a Lua DSL.

Fixed in #297


Provide an accurate error message when set autoTopicCreation

Motivation
We mention in the documentation that setting --num-partitions  is not allowed when the user wants to use the non-partitioned AutoTopicCreation configuration.

But some users ignore this and get errors like:

Reason: Invalid configuration for autoTopicCreationOverride

IMO, it's a bit confusing, not telling the user where they are invalid.
Modifications

Provide an accurate error message

Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[x] no-need-doc

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks


fix editor alignment

closes https://github.com/grafana/opensearch-datasource/issues/150
utilize InlineSegmentGroup to fix alignment issues
Before:

After:

Nice! Though I found one more misaligned button (sneaky)

Good catch! Just updated


Mobile landscape mode fixes

Need to center project images and decrease padding in top of Contact section

Removed padding from project item containers to eliminate shift to the right. Instead of margin 0 auto, set margin to 0 and allow flex container to justify content to center.
Contact section padding altered for landscape mode only, portrait mode padding remains intact.


Move keymap handling off viewer

Description
This PR simplifies our ViewerModel (preparing the way for it to become an evented dataclass) by moving the KeyMapHandler off the Viewer and onto the QtViewer as an attribute instead of using inheritance. This change should have no direct user implications, but will simplify things on our end. I'm wondering if one day we'd even move the KeyMapHandler onto the window itself, as that is really where the keymapping and mouse function handling should probably live.
Note that the ViewerModel like our Layers is still a KeyMapProvider, so all the bind_key syntax is unchanged. This just moved the handling elsewhere. (so viewer.key_press('A')) would no longer work, but I don't think that is syntax that people should have been using anyway.
This will also make it much easier to deal with different keymap providers like our plugins and or an Animation  class in #780, though we might want to think this through in a little more detail before we merge. After this change the ViewerModel would no longer have the complete list of keymap_providers, which we might actually want to keep.
It's worth thinking about these changes in the context of #1952 too, and any similarlites or differences between how our mouse bindings are handled.
We might want to wait a little before deciding on this PR, but it was quick to make so am putting it out there for consideration.
Type of change

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

@sofroniewn This is interesting, and I think it makes sense. Keymap handling should be done by the front-ends, in this case Qt but in the future maybe some web framework? I guess until now we made sure that the front end asked the ViewerModel to handle keystrokes? Which in a way is nice, though, as you can now have multiple front ends and as long as they pass keystrokes on to the viewer they all behave the same way.
Aaaaand I've talked myself around in a circle. 😂 So I guess that's the two ways of looking at things — as you say, @sofroniewn, I'd be happy to hear other thoughts on this!

Aaaaand I've talked myself around in a circle. 😂 So I guess that's the two ways of looking at things — as you say, @sofroniewn, I'd be happy to hear other thoughts on this!

Lol yes - I'm running around the same circle too.
There's one additional aspect to this PR, which is that with keymap handling on the viewer, the viewer then knows about all the active key provides - i.e. the active layer, maybe one day an animation class, maybe one day a plugin.
After this PR the viewer only ever knows about the viewer keymap and it is on the front end side that all the keymap providers get combined.
I can see pros/ cons of both approaches too, but probably the biggest thing that is strange right now is that mouse function handling is done the opposite way then key map handling.
So currently the viewer only knows about viewer mouse functions, and only in the front end do different mouse functions get combined.
This change would make the viewer know about both only viewer mouse functions and keymaps and the other sources get combined in the front end

I've fixed a couple merge conflicts and am marking this as ready for review @jni. Having had a couple weeks to think about it more I'm pretty confident this is a step in the right direction and that keymap handling should be off the viewer.
Note that this doesn't change how keybindings can be added to the viewer. I think we'll also want to provide from hookspecs for adding keybindings too, but they won't be changed by this either.
You can see in #2018 how this could work with some changes to the active layer too, but I think it makes sense to merge this first and then figure out the active layer stuff.


I don't know error...

I don't know what to do.. It happens sometime.. Help..
It's too long error, can't fit in a screenshot

I don't know what to do.. It happens sometime.. Help..

I added that feature..
I thought this error occured automatically
It didn't occur because of  command i guess maybe..

i don't think i create for that feature
have a screenshot on HandleMsg for that feature?

I added that feature..
I thought this error occured automatically
It didn't occur because of command i guess maybe..

maybe it's error from rest api, but console log show error from axios

maybe it's error from rest api, but console log show error from axios
Well it isn't occurning anymore.. So it's fine for now


design-folder-creation

contains prototypes, assets, user stories, etc.

Coverage remained the same at 26.226% when pulling 14b97c4fd867313937aae82b5ad82b406a3045b3 on design-folder into 69cb41b484324885d9fd9535c26253fa90af6668 on master.

I made a few comments on the Slack channel


Sound improvements

Added ability to stop sounds in audio library and sound_player config player.  Added new test to stop sound.

latest commit fixes #27


Support cross-building arm32 rpm for jdk11 and jdk 17

Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

@gdams will update jenkins after arm32 jdk8 is done.


KAFKA-9830: Implement AutoCloseable in ErrorReporter and subclasses

The DeadLetterQueueReporter has a KafkaProducer that it must close to clean up resources
Currently, the producer and it's threads are leaked every time a task is stopped
Responsibility for cleaning up ErrorReporters is transitively assigned to the
ProcessingContext, RetryWithToleranceOperator, and WorkerSinkTask/WorkerSinkTask classes
One new unit test in ErrorReporterTest asserts that the producer is closed by the dlq reporter

Signed-off-by: Greg Harris<EMAIL_ADDRESS>More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc @wicknicks @C0urante @ncliang for review

Thanks for your comments @wicknicks @C0urante, this is ready for a second pass.

ok to test

@kkonstantine It appears that the tests failed because of some unrelated checkstyle issue on trunk that has been fixed, can you re-run the tests?

ok to test

retest this please

@kkonstantine I've implemented your feedback and this is ready for another pass.

retest this please


Navigation page - null Application.Current

The current sample app works completely fine, but when testing my production app I noticed the AutoPageTracking not working.
After debugging for some reason the Application.Current is null so it fails to setup the page tracking -

Ive created a repo project here -
https://github.com/IeuanWalker/TinyInsights.Maui/tree/NullRepo
The only difference between that and the sample is the sample is Shell and the repo is NavigationPage.

I know what the problem is. MainPage is injected into the App class. That means that the provider is created before the App class is created.
If you do like this it should work:
        public App(IServiceProvider serviceProvider)
        {
            InitializeComponent();

            MainPage = new NavigationPage(serviceProvider.GetRequiredService<MainPage>());
        }

mmm thats fixed it for the repo, but not my production app :/
Will keep debugging

@dhindrik Interesting, so there was 2 reasons why it was null,

The one you mentioned above, about DI and the app.cs
At the bottom of the MainProgram.cs was trying to set the user language before any stats went to application insights -

MauiApp result = builder.Build();

insights = result.Services.GetService<IInsights>();
insights?.UpsertGlobalProperty("Language", AppSettings.IsWelsh ? "cy-GB" : "en-GB");

return result;

Not a big deal I can move that too the app.cs