File upload is broken

Hi guys,
I am using RestKit to work with my server. As you may know they are using AFN to send requests to server. Today I have found that my file upload is broken. I was playing around and reverting AFN commits one by one to find the place where file upload was broken.
I have found that commit f7d98aac9cd615eab4d70d6826f4ce907514dcf6 causes that issue.
I am not sure what is happening but I can see next log:
2013-04-26 12:28:27.888 Mileways[18944:c07] T restkit.network:RKHTTPRequestOperation.m:152 POST 'http://data.mileways.com/v097/test/':
request.headers={
    Accept = "application/json";
    "Accept-Language" = "en;q=1, ru;q=0.9, fr;q=0.8, de;q=0.7, ja;q=0.6, nl;q=0.5";
    "Content-Length" = 245745;
    "Content-Type" = "multipart/form-data; boundary=Boundary+0xAbCdEfGbOuNdArY";
    "User-Agent" = "Test (iPhone Simulator; iOS 6.1; Scale/2.00)";
}
request.body=<__NSCFInputStream: 0x220a9d00 hasBytesAvailable=NO, status='Not Open'>
2013-04-26 12:28:27.888 Mileways[18944:c07] Sent 4096 of 245745 bytes
2013-04-26 12:28:27.889 Mileways[18944:c07] Sent 8192 of 245745 bytes
2013-04-26 12:28:27.889 Mileways[18944:5703] Stream 0x220a9d00 is sending an event before being opened
2013-04-26 12:28:27.889 Mileways[18944:5703] Stream 0x220a9d00 is sending an event before being opened
2013-04-26 12:29:27.889 Mileways[18944:c07] E restkit.network:RKHTTPRequestOperation.m:173 POST 'http://data.mileways.com/v097/test/' (0) [60.0011 s]:
error=Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x1cdaa140 {NSErrorFailingURLStringKey=http://data.mileways.com/v097/test/, NSErrorFailingURLKey=http://data.mileways.com/v097/test/, NSLocalizedDescription=The request timed out., NSUnderlyingError=0x220aaf00 "The request timed out."}
    response.body=(null)
2013-04-26 12:29:27.889 Mileways[18944:a04f] E restkit.network:RKObjectRequestOperation.m:346 Object request failed: Underlying HTTP request operation failed with error: Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x1cdaa140 {NSErrorFailingURLStringKey=http://data.mileways.com/v097/test/, NSErrorFailingURLKey=http://data.mileways.com/v097/test/, NSLocalizedDescription=The request timed out., NSUnderlyingError=0x220aaf00 "The request timed out."}
2013-04-26 12:29:27.890 Mileways[18944:c07] E app:FlightDetailsViewController.m:1025 Failed to upload photo: Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x1cdaa140 {NSErrorFailingURLStringKey=http://data.mileways.com/v097/test/, NSErrorFailingURLKey=http://data.mileways.com/v097/test/, NSLocalizedDescription=The request timed out., NSUnderlyingError=0x220aaf00 "The request timed out."}

In the log you can find test url that you can use to reproduce the issue. I am sending small png image and with one parameter: hide=0.
And this is log when I am running the same code after reverting to 9b2a20c0a130104b2e792ab62b6c8cc8238323f1
2013-04-26 12:36:48.583 Mileways[19387:c07] T restkit.network:RKHTTPRequestOperation.m:152 POST 'http://data.mileways.com/v097/test/':
request.headers={
    Accept = "application/json";
    "Accept-Language" = "en;q=1, ru;q=0.9, fr;q=0.8, de;q=0.7, ja;q=0.6, nl;q=0.5";
    "Content-Length" = 245745;
    "Content-Type" = "multipart/form-data; boundary=Boundary+0xAbCdEfGbOuNdArY";
    "User-Agent" = "Test (iPhone Simulator; iOS 6.1; Scale/2.00)";
}
request.body=<__NSCFInputStream: 0x16a0f770 hasBytesAvailable=NO, status='Not Open'>
2013-04-26 12:36:48.702 Mileways[19387:c07] Sent 32768 of 245745 bytes
2013-04-26 12:36:48.703 Mileways[19387:c07] Sent 65536 of 245745 bytes
2013-04-26 12:36:48.703 Mileways[19387:c07] Sent 98304 of 245745 bytes
2013-04-26 12:36:48.703 Mileways[19387:c07] Sent 131072 of 245745 bytes
2013-04-26 12:36:48.942 Mileways[19387:c07] Sent 133216 of 245745 bytes
2013-04-26 12:36:49.061 Mileways[19387:c07] Sent 136112 of 245745 bytes
2013-04-26 12:36:49.121 Mileways[19387:c07] Sent 139008 of 245745 bytes
2013-04-26 12:36:49.158 Mileways[19387:c07] Sent 141904 of 245745 bytes
2013-04-26 12:36:49.270 Mileways[19387:c07] Sent 144800 of 245745 bytes
2013-04-26 12:36:49.312 Mileways[19387:c07] Sent 147696 of 245745 bytes
2013-04-26 12:36:49.370 Mileways[19387:c07] Sent 150592 of 245745 bytes
2013-04-26 12:36:49.404 Mileways[19387:c07] Sent 153488 of 245745 bytes
2013-04-26 12:36:49.431 Mileways[19387:c07] Sent 156384 of 245745 bytes
2013-04-26 12:36:49.548 Mileways[19387:c07] Sent 159280 of 245745 bytes
2013-04-26 12:36:49.575 Mileways[19387:c07] Sent 162176 of 245745 bytes
2013-04-26 12:36:49.641 Mileways[19387:c07] Sent 163840 of 245745 bytes
2013-04-26 12:36:49.688 Mileways[19387:c07] Sent 169416 of 245745 bytes
2013-04-26 12:36:49.722 Mileways[19387:c07] Sent 172312 of 245745 bytes
2013-04-26 12:36:49.776 Mileways[19387:c07] Sent 175208 of 245745 bytes
2013-04-26 12:36:49.811 Mileways[19387:c07] Sent 178104 of 245745 bytes
2013-04-26 12:36:49.842 Mileways[19387:c07] Sent 181000 of 245745 bytes
2013-04-26 12:36:49.918 Mileways[19387:c07] Sent 183896 of 245745 bytes
2013-04-26 12:36:49.923 Mileways[19387:c07] Sent 186792 of 245745 bytes
2013-04-26 12:36:49.975 Mileways[19387:c07] Sent 189688 of 245745 bytes
2013-04-26 12:36:50.011 Mileways[19387:c07] Sent 192584 of 245745 bytes
2013-04-26 12:36:50.048 Mileways[19387:c07] Sent 195480 of 245745 bytes
2013-04-26 12:36:50.123 Mileways[19387:c07] Sent 196608 of 245745 bytes
2013-04-26 12:36:50.150 Mileways[19387:c07] Sent 201272 of 245745 bytes
2013-04-26 12:36:50.191 Mileways[19387:c07] Sent 204168 of 245745 bytes
2013-04-26 12:36:50.271 Mileways[19387:c07] Sent 208512 of 245745 bytes
2013-04-26 12:36:50.318 Mileways[19387:c07] Sent 211408 of 245745 bytes
2013-04-26 12:36:50.375 Mileways[19387:c07] Sent 214304 of 245745 bytes
2013-04-26 12:36:50.390 Mileways[19387:c07] Sent 217200 of 245745 bytes
2013-04-26 12:36:50.451 Mileways[19387:c07] Sent 220096 of 245745 bytes
2013-04-26 12:36:50.474 Mileways[19387:c07] Sent 222992 of 245745 bytes
2013-04-26 12:36:50.485 Mileways[19387:c07] Sent 225888 of 245745 bytes
2013-04-26 12:36:50.548 Mileways[19387:c07] Sent 228784 of 245745 bytes
2013-04-26 12:36:50.588 Mileways[19387:c07] Sent 229376 of 245745 bytes
2013-04-26 12:36:50.589 Mileways[19387:c07] Sent 231680 of 245745 bytes
2013-04-26 12:36:50.605 Mileways[19387:c07] Sent 234576 of 245745 bytes
2013-04-26 12:36:50.668 Mileways[19387:c07] Sent 237472 of 245745 bytes
2013-04-26 12:36:50.690 Mileways[19387:c07] Sent 240368 of 245745 bytes
2013-04-26 12:36:50.725 Mileways[19387:c07] Sent 243264 of 245745 bytes
2013-04-26 12:36:50.808 Mileways[19387:c07] Sent 245745 of 245745 bytes
2013-04-26 12:36:52.461 Mileways[19387:c07] T restkit.network:RKHTTPRequestOperation.m:183 POST 'http://data.mileways.com/v097/test/' (200 OK) [3.8786 s]:
response.headers={
    "Access-Control-Allow-Origin" = "*";
    "Cache-Control" = "private, no-cache, no-store, must-revalidate";
    Connection = "Keep-Alive";
    "Content-Length" = 284;
    "Content-Type" = "application/json; charset=UTF-8";
    Date = "Fri, 26 Apr 2013 08:36:48 GMT";
    Expires = "Mon, 26 Jul 1997 05:00:00 GMT";
    "Keep-Alive" = "timeout=5, max=100";
    Pragma = "no-cache";
    Server = Apache;
}
response.body={
    "hide": "0",
    "session": "<><><>",
    "picture": {
        "name": "photo.png",
        "type": "image\/png",
        "tmp_name": "\/is\/htdocs\/user_tmp\/wp11076254_TYZRNXHENH\/phptQL2eD",
        "error": "0",
        "size": "245358"
    }
}

Thanks

@arsonik: Does "NSURLErrorTimedOut" error messages be localized from iOS SDK? Today, I saw though I havent localized this message, it is giving me localized error. How can it be possible?


Add documentation for usage with ssr

Hey there, I was just able to make the router work with ssr in a basic example.
From what I figured, its just about providing your own integration in the server part of the app/router rendering.
For me the integration looks like:
const ssrIntegration = createIntegration(
        () => req.normalisedPath(),
        () => undefined
      );

You will find the full example here: https://gitlab.com/BeneStem/es4x-flower/-/blob/master/src/server/ServerRouter.tsx#L22
Its probably a nice hint for other people to add this to the documentation.
I saw in you todos, that ssr is still not supported completely.
But if you'd go further it would probably be nice to set the current url directly as a prop like for example the vue ssr router is doing it. A full integration with history is probably not even needed on the initial ssr part.
What do you say about that? :)

For documentation sake this issue is related to a project which was discussed here: https://github.com/solidjs/solid/discussions/454

Yeah, that is fair. I need to add some more documentation on the subject and examples of well, everything.
The router component accepts a couple different forms for integration including a signal. I usually do something like this to support rendering on the server:
<Router integration={isServer ? createSignal({ value: req.originalUrl }) : pathIntegration()}>
  <MyApp />
</Router>

Ultimately you could even just pass in a signal-like tuple such as [() => ({ value: req.originalUrl }), () => {}]
This could definitely be improved, though I'm not sure what the best solution would be. I could:

Add an additional property like startLocation which could be useful on the client as well as the server.
Support passing a string into integration.
Support passing in a { value: String } type object into integration. This would give the router the ability to write to the object and the user the chance to read the value property after rendering in the event of a redirect in case they want to do something with that on the server.
Another option?

I'm also considering making pathIntegration() the default on the client just to cut down verbosity.

Thank you so much for all that information!
I didn't even think about using isServer in that context!
Currently I have two files, one for Client and one for Server root... I could merge them ;) Never thought about that :D
I am not sure if I can make the call on which option is best considered. My experience with providing such a framework are very limited.
Vue Router is doing the startLocation property thing... But the other options sound intriguing as well!

I added a little bit of documentation to the readme in https://github.com/rturnq/solid-router/commit/ffa31c845966d351e211673456d117a03846261c
I'll leave this issue open while I consider how to make this better.


fix issue with kaminari pagination

Fixes #2464
Looks like the refactor of strong params requires us to call the helper method rather than an instance variable when passing in the pagination options

ha ha. good catch @xsrust


Snowflake ingestion fix

Describe your changes :

I worked on the fixing ingestion fail issue and variant data type ingestion issue in snowflake

Type of change :

[x] Bug fix
[x] Improvement

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have performed a self-review of my own.
[x] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers
@ayush-shah

@codingwithabhi let's test and check other connectors as well, so that we are sure that it's not a breaking change

@codingwithabhi @ayush-shah what is pending on this PR?

I think it's ready to be merged in.
@codingwithabhi can you open this PR for review?


feat: add awsuserarn resource

Description of your changes

Fixes #
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

@akesser can you Check for CI jobs ?


Marvelousga Twitch & Twitter support

Can u add Marvelousga Twitch & Twitter support?

Added Twitch support in v2.0.12.
Twitter follows don't seem to be verified at this time, and so support isn't needed.

Thanks. Closed.


Fix autoclosure code generator

Description
Problem
When a protocol using an @autoclosure is used, the generated code is invalid as @autoclosure closures need a () when forwarding.

Changes
This PR extends the MethodParameter to detect an @autoclosure and handles it accordingly when generating.

Tests

Added an example method to the TestedProtocol to cover this
Added simple unit tests for mocking

Closing as no longer relevant for us. I opened a PR on Cuckoo directly though: https://github.com/Brightify/Cuckoo/pull/445


add admin user with edit access during installation

Currently we use the system:admin user and the developer user. However the system:admin user cannot log in via the UI.
It would be nice to be able to login as an admin to look at other namespaces such as the service catalog and ansible-service-broker
Currently I do this by login in as admin:admin through the UI. This creates a new user with no access. So then as the system:admin user I run
oc adm policy add-cluster-role-to-user edit admin
Doing this as part of the installation set up would be useful

@maleck13 Agreed this could be useful as I've ran that command myself many times.
I'd recommend including it for the 'local dev' setup only.
This may be a good one to discuss with the tooling guys where we want different ways of installing e.g. local dev, local not dev, remote...


bmech_reversepol

function should return error if user asks to reverse polarity of a channel that doesn't exist

added warning for missing channels in v1.5.19


[PL-52057] SMP Release Notes 0.18.0

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: SMP Release Notes 0.18.0
Jira/GitHub Issue numbers (if any):  PL-52057
Preview links/images (Internal contributors only): https://6682b5cda39c30009449966e--harness-developer.netlify.app/release-notes/self-managed-enterprise-edition#july-1-2024-version-0180

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://667d2210a4794195c941497b--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://667ea2243d9dce1c56cbb2c9--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://667ea82aca7a2b23979624be--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://667f45bf65c136963c1cd202--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6682b3f192523d149d2e7363--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6682b5cda39c30009449966e--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66840c3f2abdb27cb30b64a7--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6684dd91efca7e8befec78b9--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6685190101c956cdfd3cd390--harness-developer.netlify.app


Allow prepending access log handler for WASM filter

Commit Message: Allow prepending access log handler for WASM filter
Additional Description:
Risk Level: Low
Testing: Integration
Docs Changes:
Release Notes:
Platform Specific Features:
Fixes https://github.com/envoyproxy/envoy/issues/30859
This PR is in response to the approaches considered in ##35595 and #35742 in order to solve #30859. The recommended approach in these discussions was to override onStreamComplete callback, which may make sense for most filters. However, the WASM filter is a unique case in which doing this method would be more of a work-around hack as the filter itself does not inherit StreamFilter, and while the common WASM section does, it cannot utilize the onStreamComplete from its individual filters and thus is missing onStreamComplete, instead using onDone as a proxy for it. As a result, implementing onStreamComplete here would lead to onLog being called within the onStreamComplete method instead of the log() method, which doesn't seem to make the most sense for readability.
As such, we propose to continue the initial decided implementation of prepending the access loggers in order to maintain the execution order. This solution does seem to address this specific problem as described in the issue, so that AccessLogger doesn't see the dynamicMetadata until WASM finishes writing to it. This would be a case specific to WASM because of the details described above. Another WASM implementation is dependent on this issue being fixed, so @spacewander and any other, would welcome feedback or approval on this PR.

See my previous comment https://github.com/envoyproxy/envoy/pull/35595#issuecomment-2275413934

@sunaydagli
Maybe you could try my suggestion at https://github.com/envoyproxy/envoy/pull/35742#issuecomment-2303560466. Does it work for you?


USA 2018 Kia Stinger Openpilot doing unnecessary speed conversion

USA 2018 Kia Stinger Openpilot doing unnecessary speed conversion.
Love your work! Do you have a donate button?
https://drive.google.com/file/d/1K2nwrSuGHpfeeS2DXKJayFNHsWZOO1fV/view?usp=sharing

Probably fixed by 4584a9bdc5a04fdc86f3432538c38e62a1e21ae5, aaa46674c1977fa8583a413c76b41c610cb51f3c

Still having the incorrect speed issue. Thank you for all that you're doing for the community.
https://drive.google.com/file/d/1KIm7_HhOLVu3t--lGeBpEuE1AB34MPxT/view?usp=sharing

Probably fixed by 4584a9b, aaa4667
Still having the incorrect speed issue. Thank you for all that you're doing for the community.
https://drive.google.com/file/d/1KIm7_HhOLVu3t--lGeBpEuE1AB34MPxT/view?usp=sharing

Thanks for your help :)


feat(authentication): add support to persist sessions and flows in database

[x] Add support to save user sessions and flows in the postgres database
[x] Documentation

Update API and CLI reference
Update server configurations

@Chief-Rishab can you rebase this with main, I'll review it after

@kushsharma ready for review


MWPW-143894 moving category authoring to separate row

resolution proposal to limit authoring errors in sidenav update vs categories
Resolves: MWPW-143894
Test URLs:
Before: https://main--cc--adobecom.hlx.live/drafts/npeltier/sidenav-test-old?martech=off
After: https://143894--cc--npeltier.hlx.live/drafts/npeltier/sidenav-test?martech=off

exact same code as what was initially presented in https://github.com/adobecom/cc/pull/245 before my local stage branch got crushed

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

Project coverage is 87.71%. Comparing base (52fab3a) to head (2d4992a).

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #254      +/-   ##
==========================================
+ Coverage   87.68%   87.71%   +0.02%
==========================================
  Files           9        9
  Lines         934      936       +2
==========================================
+ Hits          819      821       +2
  Misses        115      115

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

@npeltier reordering categories does not work with these changes. Could you please check?

@npeltier Could you check the PSI score? It is currently failing.
CC: @salonijain3

@npeltier Could you check the PSI score? It is currently failing. CC: @salonijain3

@npeltier Could you review the failure in PR checks?
CC: @salonijain3 @dstrong23 @Ruchika4

This PR is stale and was open > 2 weeks, closing this PR. Please feel free to open another PR if needed.


Select control doesn't render correctly when inside of ng-repeat in IE10

This is a bug in IE10 (I didn't check other versions of IE), checked with Angular 1.2.1 and latest 1.5.1.
If a select control with options generated by ng-repeat is nested within another ng-repeat, on initial navigation to the page we can see angulars {{variable_name}} as a selected text of the select box. Only after clicking on the select box the {{variable_name}} is being correctly replaced by a value.
Investigating the DOM, the values are correctly populated, it seems like IE refuses to render them correctly.
The problem only exists if the select is inside ng-repeat, everything works fine if it is not.
Here is a jsfiddle replicating the problem.

Can't reproduce in IE11.

In IE10, how stable is it? Does it happen always or from time to time?

Can reproduce in IE10. What a strange problem. I guess we could try to trigger a re-render somehow, as it looks like a similar problem to https://github.com/angular/angular.js/issues/6211

This works in >= 1.6.0


ssl verification

#transport=AsyncProxyTransport.from_url(random.choice(self.main.proxies)),
for example does not respect verify=False and will except when ssl verif fails, anyway to fix this or give asyncproxytransport its own verify=False?

transport = AsyncProxyTransport.from_url('...', verify=False)


Add missing bc in Builder image

Required to compare floating point v numbers of glide
Related to #1906

@aslakknutsen snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1907-1

Codecov Report

Merging #1907 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1907   +/-   ##
=======================================
  Coverage   61.34%   61.34%
=======================================
  Files         132      132
  Lines       12968    12968
=======================================
  Hits         7955     7955
  Misses       4301     4301
  Partials      712      712

Continue to review full report at Codecov.

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

@aslakknutsen snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1907-2

@aslakknutsen snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1907-3

@aslakknutsen snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1907-4

@aslakknutsen snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1907-5

@aslakknutsen snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1907-6

Closing this as we've moved to dep, and download the appropriate dep version in the Makefile.


C program to find the number of keywords in a given Text file !!

Hey !! I want you to please add these files in your repository as it contains the concept of file handling in c language.
Thank you.

Hello bhai pull request bhi dekhna hota hai time time par
Jyada request accept nahi kar paate I toh atleast kuch review bhi dekh saktei ho.
Varna chode dei bhai tere bass ka nahi hai.


Feature request: module to Sign Requests

Use case
It would be nice to have a module in the AWS Powertools that would sign requests made to AWS Resources via the SigV4 method. Currently doing it yourself is a tedious process and needing to understand the underlying mechanism.
This is also discussed in the Powertools for Python repositor

https://github.com/aws-powertools/powertools-lambda-python/issues/2713
https://github.com/aws-powertools/powertools-lambda-python/issues/2493
https://github.com/aws-powertools/powertools-lambda-python/pull/2435

Solution/User Experience
Same as for the python version,  I am proposing adding a new class that will take in the parameters to create this signed request for the end user to simplify it since it is not a very straightforward method and should be made easier.
Currently it differs based on which request library you are using, for example with Axios there is an intercepter, for got there is a got4aws you could use or in cases where I'm at currently I've implemented our own hook in a request library.
Having an supported module by powertools that does this would be preferred.
Alternative solutions
No response
Acknowledgment

[X] This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
[X] Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers
Please react with 👍 and your use case to help us understand customer demand.

Hi @cino, thank you for taking the time to open the issue.
As discussed earlier today I think this is a valuable utility, so I would definitely want to look more into it and see if we can add it to the roadmap.
I'm gonna take some time and go though the existing issues that you've linked to understand where they stand, then I'll also discuss this internally.
I'll try to get back to you here in a reasonable amount of time, but no earlier than a couple of weeks likely since we're going to focus on releasing v2 (this week) and Parser in the coming weeks.

Hi - just wanted to follow up on this.
We have been discussing this internally and we still intend to work on this utility but at the moment we are prioritizing the new Event Handler utility due to higher demand.
We'll revisit this in 3 months to see if bandwidth allows us to move this forward.
--
For future readers: ine thing that would be extremely helpful to prioritize is to have company names, as GitHub doesn't always have that info -- feel free to email us<EMAIL_ADDRESS>if you don't feel comfortable sharing in public.


vc1parser: add boundary check for every read bits

bitreader: add new version of peek that returns a bool value

close this since we have #577


Add the rst module

Description
What?
This PR contains a new module that intends to introduce teachers and teacher assistants to the markup language reStructuredText (RST).
Why?
Some teacher or teacher assistants may not be familiar with RST. Therefore, this module presents only the necessary roles and directives that are required to create a course. In this way, the teacher will not need to read about or learn unnecessary directives that are presented in the RST or Sphinx documentation.
How?
The text is written based on my experience and knowledge.
Testing
Remember to add or update unit tests for new features and changes.

How to test your changes in A-plus
How to test accessibility

What type of test did you run?

[ ] Accessibility test using the WAVE extension.
[ ] Django unit tests.
[ ] Selenium tests.
[ ] Other test. (Add a description below)
[X] Manual testing.

I tested that the content was rendered properly.
Did you test the changes in

[X] Chrome
[X] Firefox
[ ] This pull request cannot be tested in the browser.

Think of what is affected by these changes and could become broken
It is necessary to proofread this PR.
Translation

[ ] Did you modify or add new strings in the user interface? (Read about how to create translation)

Programming style

[ ] Did you follow our style guides?

Have you updated the README or other relevant documentation?

[ ] documents inside the doc directory.
[ ] README.md.
[ ] Aplus Manual.
[ ] Other documentation (mention below which documentation).

Is it Done?

[ ] Reviewer has finished the code review
[ ] After the review, the developer has made changes accordingly
[ ] Customer/Teacher has accepted the implementation of the feature

Clean up your git commit history before submitting the pull request!

I merged this PR manually: https://github.com/apluslms/aplus-manual/commit/fe6155ea1bf38d87b81f7225d5bd3e27cce4b69f
I made many changes myself in order to fix errors and typos.


'Cannot find module' when using webpack loaders

Hi,
Apologies if I missed something stupid, but I've been working off of the react-redux-universal-hot-example, which uses these tools, and have been running into trouble. Note: I'm only having issues with the .server() functionality. The webpack-isomorphic-tools/plugin works fine.
Basically I want to use the responsive-loader like so:
import logo from 'responsive?sizes[]=100,sizes[]=200,sizes[]=300!./logo.png';
...
<img alt='logo' { ...pick(logo, 'src', 'srcSet') } />

Now the image assets are defined like so:
assets: {
	images       : {
		extensions: ['jpeg','jpg','png','gif'],
		parser    : WebpackIsomorphicToolsPlugin.url_loader_parser
	}
}

Which is also shown by the logs:
...
[1] [webpack-isomorphic-tools] [debug]  registering a require() hook for *.png
[1] [require-hacker] [debug] Hooking into *.png files loading
...

However, it seems like either this module, or require-hacker is having trouble loading my image through the loader:
Error: Cannot find module 'responsive?sizes[]=100,sizes[]=200,sizes[]=300!./logo.png'

It seems to me that the require-hacker is not matching the png extension to my import. I'm aware of your updated universal-webpack project, but it would be awesome if I wouldn't have to refactor our entire setup :)
Thanks!

First, post your webpack-assets.json

After doing a regular webpack build (without the isomorphic tools server):
{
	"javascript": {
		"main": "/dist/main-4741642bcf773c303347.js"
	},
	"styles": {
		"main": "/dist/main-4741642bcf773c303347.css"
	},
	"assets": {
		"./~/responsive-loader?sizes[]=200w,sizes[]=900w!./src/components/Footer/logo.png": {
			"srcSet": "/dist/b543654d2aa566278f4a55fa57f60710-200.png 200w,/dist/173c90859b68dae28f380594dab6600c-900.png 900w",
			"images": [
				{
					"path": "/dist/b543654d2aa566278f4a55fa57f60710-200.png",
					"width": 200
				},
				{
					"path": "/dist/173c90859b68dae28f380594dab6600c-900.png",
					"width": 900
				}
			],
			"src": "/dist/b543654d2aa566278f4a55fa57f60710-200.png"
		},
		"./src/components/FlightSearchForm/paper-plane.png": "/dist/e43977ae42c5fd34ddc5f704b5379647.png",
		"./src/components/Footer/logo.png": "/dist/40ad81f97f992aa2762104859a58f3b0.png",
		"./src/components/search/CalendarInput/pick-dates-arrows.png": "data:image/png;base64,(...)",
		"./src/components/search/DestinationInput/airplane-land.png": "data:image/png;base64,(...)",
		"./src/components/search/OriginInput/airplane-takeoff.png": "data:image/png;base64,(...)",
		"./src/components/AirSearch/AirSearch.scss": {
			"airSearch": "_2EWuPkdN7-e_9a4Lyck7bD",
			"input": "_26laaCQwJnVw2Dp2w-6PhK",
			"container": "_2izjQPwb252hdg1VOZ3KH9",
			"suggestion": "GLkZ2a4Q8GUlEBT9roaqk",
			"focused": "_2BeuLz_R9ZntuWUlrg1_WS"
		},
		"./src/components/Footer/Footer.scss": {
			"footer": "_2nhzBA1RlNKOVN_nNggXzW",
			"columnContainer": "_3dgNKmQSUHP_s-80dcoG1J",
			"column": "_2s5Kwhrv5lnUGjWHVoaWv5",
			"disclaimer": "_1uXyy1r8U9wrrnNh8NRCGo"
		},
		"./src/components/common/NewsletterSection.scss": {
			"newsletterSection": "_3lNtYGZLk_EXefXckLuHUU"
		},
		"./src/containers/App/App.scss": "// removed by extract-text-webpack-plugin",
		"./src/containers/Deals/Deals.scss": {
			"deals": "_2ZBPCFQ3eIrR7OdYz_fy8t"
		},
		"./src/containers/Home/Home.scss": "// removed by extract-text-webpack-plugin"
	}
}

I trucated the data urls for brevity.

So, yeah, it says Cannot find module 'responsive?sizes[]=100,sizes[]=200,sizes[]=300!./logo.png' because this module isn't present in your webpack-assets.json.
Instead you have ./~/responsive-loader?sizes[]=200w,sizes[]=900w!./src/components/Footer/logo.png.
What you could do is to modify path parser for responsive-loader assets.
Try adding a dedicated assets entry for that type of require() calls. The extensions will stay the same, but path function will be different. Make it match only ./~/responsive-loader?... paths and transform them to responsive?....
I don't know why the sizes are different in both cases.

Ah, thanks for the explanation. I think I've made some progress, but not quite there yet.
So I'm importing the following:
import logo from 'responsive?sizes[]=200w,sizes[]=900w!./logo.png';

And I've modified my extension like so:
		images       : {
			extensions: [
				'jpeg',
				'jpg',
				'png',
				'gif'
			],
			path: function(module) {
				if (/\.\/~\/responsive-loader/.test(module.name)) {
					return module.name.replace('./~/responsive-loader', 'responsive');
				}
				return module.name;
			},
			parser    : WebpackIsomorphicToolsPlugin.url_loader_parser
		}

Which results in the following key in the assets json:
"responsive?sizes[]=200w,sizes[]=900w!./src/components/Footer/logo.png"
It obviously still complains:
Error: Cannot find module 'responsive?sizes[]=200w,sizes[]=900w!./logo.png'

because the imported url is relative to the component (./logo.png), while the asset refers to the path relative to the root.
I'm seeing other assets that are also identified relative to the root: "./src/components/FlightSearchForm/paper-plane.png", and those don't seem to pose an issue. I'm guessing the loading syntax (responsive?...) is messing up with the matching logic?
Thanks so far!
Btw, sizes were different because I'm reproducing on a different machine, and didn't push on the other.

You can try running the whole thing in debug mode which will generate webpack-stats.json.
Then upload that webpack-stats.json and post the link to it here.
Maybe github will upload it automatically when you paste the contents of the file in the comment box.

Oh, no, I get it, the issue is in the other place.

Well, I guess, there's currently no way to make it work, because require('responsive?...') will look for responsive?... file existence (on disk) and since there's no such file then it will throw Error: Cannot find module 'responsive?...'.
I guess you may try moving to universal-webpack instead, because I don't see how this kind of require() calls could work with the current implementation of this library.

Okay, understood. Thanks for the swift replies!

File existence requirement is not mine and is Node.js'es.
https://github.com/halt-hammerzeit/webpack-isomorphic-tools#cannot-find-module

Out of curiousity. Does that mean that it is entirely impossible to use webpack loaders this way in a universal app? I mean to define the loader in the import string.

It is possible to bypass Node.js file existence requirement by using .global_hook instead of .hook
https://github.com/halt-hammerzeit/require-hacker#global_hookmeaningful_id-resolve-options
It can be implemented in this library (either instead of the regular file extension hook or additionally for loaders only).
I'll see.

Okay, seems that I made it.
Install the latest version of the package, revert to the initial assets configuration (no custom path parsing) and post back on results.

Awesome! Works for my use-case. Thanks a lot.


How to use a MySQL database in Java

Introduction paragraph (2-3 paragraphs):
We will learn how to connect to a MySQL database using Java code and run simple queries to get and update data in this tutorial. We'll utilize the JDBC (Java Database Connectivity) API, which is included in the standard Java library, to connect to the database.
JDBC allows you to connect to any database, including Postgres, MySQL, SQL Server, Oracle, and others, as long as you have the right driver. The Type 4 JDBC driver from the mysql-connector-java-5.1.23-bin.jar package will be used to connect to the MySQL database.
Key takeaways:
-The JDBC connection string (for example: jdbc:mysql://localhost:3306/test).
-Username (root).
-Password (root).
-Database with some number of tables for example (e.g. book database).

Good afternoon and thank you for submitting your topic suggestion. @Amoh-writer
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Unfortunately, this article appears to be covered here https://www.section.io/engineering-education/java-jdbc/.

Hello @WanjaMIKE Have changed the topic title from How to use a MySQL database in java  to How to use a MySQL database in C#

Unfortunately, this topic appeared to have been suggested here https://github.com/section-engineering-education/engineering-education/issues/3603. Feel free to suggest another topic thanks.


Fix formatting in pid.cpp.

Commits in this PR

Fix formatting in pid.cpp.
Somehow escaped clang-format.

PR chain

👉 #494 Fix formatting in pid.cpp. 👈 YOU ARE HERE
#495 Remove trailing whitespace in sample-data/README.md
#483 Move flow zeroing into TVIntegrator.
#485 Units: Allow x / y to return a raw ratio.
#486 Move blower_fsm implementations into cpp file.
#488 Rise from PIP to PEEP in 100ms.
#496 Bump gcc version to 9.2.1.
#497 Eagerly home pinch valves
#498 Rename SensorReadings proto -> SensorsProto.
#499 SensorReadings from SensorsProto.

@a-vinod sorry, there's a bug in my git-pr-chain tool that's causing the occasional PR to get marked as merged even though I'm not actually done with it.
Would you mind re-approving this one?

You got it!


DIALServer: make autostart as configurable

https://jenkins.code.rdkcentral.com/job/github-triggered/1231/ started


Word and word groups view need to only give result for specified language

It needs to be decided as soon as possible. Because current logic for backend supposed to give only one descriptions for the specified language. But currently backend sends the word groups with all the descriptions in all of the languages and then it's decided to use which on a frontend side


Gardena not available

Hi,
Since a few day my Gardena Integration is not working anymore and entities show up as not available.
This is the logfile:
Deze fout is ontstaan door een aangepaste integratie.
Logger: homeassistant.config_entries
Source: custom_components/gardena_smart_system/init.py:44
Integration: Gardena Smart System integration (documentation, issues)
First occurred: 08:32:17 (1 occurrences)
Last logged: 08:32:17
Error setting up entry for gardena_smart_system
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 339, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/gardena_smart_system/init.py", line 44, in async_setup_entry
client_secret=entry.data[CONF_CLIENT_SECRET],
KeyError: 'client_secret'
I think it's a problem with the "client sercret" but i didn't change anything. Problem started after update of the Gardena integration in HACS.
Can anyone help please?
Kind regards

Found the solution for this in the closed items!

Good to know.
Sorry for the delay in the answer :)


Bluemediafile

Domain
https://bluemediafile.sbs/
Link
https://bluemediafile.sbs/url-generator-1.php?url=SDUS9bRvhba8BF9dQAj5cgIzeg4+4r9hpGtYJn0s4Kwtvb6uOzeLgbYwfW9y0s5afDD5E0lCVLwSMo4Ub9c9/6OkLKOdprACYqHFSdDReqQ
Version
0.2268 412fdd8
What browsers are you seeing the problem on?
Chrome
What OS are you seeing the problem on?
Windows
Anything else?
Bluemediafile.com was renamed to Bluemediafile.sbs and probably works a bit differently.

I've been trying to work on this, but Mv3 security is blocking the bypass that worked fine on Mv2, so I'll need to come up with a workaround.


CLP pointer permissions

Previously before Parse Server, I could specify pointers in a class to be able to have certain permissions on an object through the data browser's CLP settings. Now with Parse Server, that no longer works and I have to allow the public to read/write if I want to access the data. The schema in my mongodb updated with the correct CLP, but it is returning [Error]: Permission denied for this action..
Here is my schema:
        "class_permissions": {             "get": {},             "find": {},             "update": {},             "create": {                 "*": true             },             "delete": {},             "addField": {},             "readUserFields": [                 "toUser",                 "fromUser"             ],             "writeUserFields": [                 "toUser",                 "fromUser"             ]         }
Thanks for the help.

Pointer permissions aren't supported in Parse Server yet. We're continuing to work towards complete feature parity with Parse.com, but we aren't there yet.

Hi!
Any news about CLP pointer permissions release date? Thanks!

Pointer Permissions are done and will be part of the next release.


Error logging into tf wallet

When you log into a tf wallet account you get an error saying no stacktrace available.

Fixed in da7420251efe2d4ee0be895a3164784fd3f501b4


Update translations.yml

Footer content – translate Hugo name and add translators here

Actually if that's okay with you I'd like my name to remain in Latin, unless this is something really inappropriate in Russian.

Ping @grawl.

Regarding to our cyrillic-letters write system we always translate human names when possible. So, Albert Einstein in Russian will be “Альберт Эйнштейн”.

Okay, I'm fine with that. Could you please rebase your branch perhaps?

Oh I don't know how to rebase.

Okay, I'll tackle this myself then. ;)


Quick Start Demo Issue with source hudi and target iceberg

Hi all, im trying to run the quick start demo but noticing the following issue. I created the hudi table
 rahilchertara@rahils-mbp  /tmp/hudi-dataset/people  ls -a
.          .hoodie    city=DFW   city=ORD   city=SFO
..         _delta_log city=NYC   city=SEA
 rahilchertara@rahils-mbp  /tmp/hudi-dataset/people 

And also am using this yaml file
sourceFormat: HUDI
targetFormats:
  - DELTA
  - ICEBERG
datasets:
  -
    tableBasePath: file:///tmp/hudi-dataset/people
    tableName: people
    partitionSpec: city:VALUE

I am see the delta log created but i do not a iceberg metadata folder created. The onetable job also seems to hang for me.
 java -jar utilities/target/utilities-0.1.0-SNAPSHOT-bundled.jar --datasetConfig my_config.yaml
SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
SLF4J: Ignoring binding found at [jar:file:/Users/rahilchertara/workplace/onetable/utilities/target/utilities-0.1.0-SNAPSHOT-bundled.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
2023-11-22 09:13:48 INFO  io.onetable.utilities.RunSync:141 - Running sync for basePath file:///tmp/hudi-dataset/people for following table formats [DELTA, ICEBERG]
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.spark.unsafe.Platform (file:/Users/rahilchertara/workplace/onetable/utilities/target/utilities-0.1.0-SNAPSHOT-bundled.jar) to constructor java.nio.DirectByteBuffer(long,int)
WARNING: Please consider reporting this to the maintainers of org.apache.spark.unsafe.Platform
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
2023-11-22 09:13:49 INFO  io.onetable.client.OneTableClient:220 - No previous OneTable sync for target. Falling back to snapshot sync.
2023-11-22 09:13:49 INFO  io.onetable.client.OneTableClient:220 - No previous OneTable sync for target. Falling back to snapshot sync.
# WARNING: Unable to get Instrumentation. Dynamic Attach failed. You may add this JAR as -javaagent manually, or supply -Djdk.attach.allowAttachSelf

Hi @rahil-c - thanks for opening the issue.
I ran the same example you're referring to, but was unable to replicate the issue you're facing. So a few follow up questions.

Are you using JDK11?
While building the jar from source (assuming you built it from main branch), did you see any errors?
Just for good measure, can you pull the latest changes and build the jar once again?

From my tests:
sagarl@dev onetable_256 % cat my_config.yaml
sourceFormat: HUDI
targetFormats:
  - DELTA
  - ICEBERG
datasets:
  -
    tableBasePath: file:///tmp/hudi-dataset/people
    tableName: people
    partitionSpec: city:VALUE

sagarl@dev onetable_256 % java -jar utilities/target/utilities-0.1.0-SNAPSHOT-bundled.jar --datasetConfig my_config.yaml
SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details.
SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier.
SLF4J: Ignoring binding found at [jar:file:/Users/sagarl/oss/onetable_256/utilities/target/utilities-0.1.0-SNAPSHOT-bundled.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.
2023-11-22 10:28:14 INFO  io.onetable.utilities.RunSync:150 - Running sync for basePath file:///tmp/hudi-dataset/people for following table formats [DELTA, ICEBERG]
2023-11-22 10:28:17 INFO  io.onetable.client.OneTableClient:220 - No previous OneTable sync for target. Falling back to snapshot sync.
2023-11-22 10:28:17 INFO  io.onetable.client.OneTableClient:220 - No previous OneTable sync for target. Falling back to snapshot sync.
# WARNING: Unable to attach Serviceability Agent. You can try again with escalated privileges. Two options: a) use -Djol.tryWithSudo=true to try with sudo; b) echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
2023-11-22 10:28:35 INFO  io.onetable.client.OneTableClient:123 - OneTable Sync is successful for the following formats [DELTA, ICEBERG]

sagarl@dev onetable_256 % ls -la /tmp/hudi-dataset/people
total 16
drwxr-xr-x@ 11 sagarl  wheel   352 Nov 22 10:28 .
drwxr-xr-x@  4 sagarl  wheel   128 Nov 22 10:23 ..
-rw-r--r--@  1 sagarl  wheel  6148 Nov 22 10:23 .DS_Store
drwxr-xr-x@ 15 sagarl  wheel   480 Nov 22 10:21 .hoodie
drwxr-xr-x   4 sagarl  wheel   128 Nov 22 10:28 _delta_log
drwxr-xr-x@  6 sagarl  wheel   192 Nov 22 10:21 city=DFW
drwxr-xr-x@  8 sagarl  wheel   256 Nov 22 10:21 city=NYC
drwxr-xr-x@  6 sagarl  wheel   192 Nov 22 10:21 city=ORD
drwxr-xr-x@  6 sagarl  wheel   192 Nov 22 10:21 city=SEA
drwxr-xr-x@  6 sagarl  wheel   192 Nov 22 10:21 city=SFO
drwxr-xr-x  12 sagarl  wheel   384 Nov 22 10:28 metadata
sagarl@dev onetable_256 %

Alternatively, if you're just running the quickstart example, you can try running the sync with the utilities-0.1.0-beta1-bundled.jar at https://github.com/onetable-io/onetable/packages/1986830
i.e. java -jar ~/Downloads/utilities-0.1.0-beta1-bundled.jar --datasetConfig my_config.yaml

Thanks @sagarlakshmipathy for getting back to me.

I am using the jdk 11
I built the jar without issues
pulled latest changes on main and tried again with same issue.

Will try using the beta jar. One thing i saw between your log output and mine is that mine contains this log
# WARNING: Unable to get Instrumentation. Dynamic Attach failed. You may add this JAR as -javaagent manually, or supply -Djdk.attach.allowAttachSelf

which it hangs on indefinitely so not sure is this is an issue.

Hi @rahil-c,
I have faced this error long back and that was because I was in an old terminal session that was using JDK8, but in your case you have confirmed that you're using JDK11. So I'm not sure how I can replicate this issue.
However, I've raised this PR to add a docker playground where folks can try OneTable.
This will atleast ensure there are no environment related issues. I've tested all combination syncs and it seems to work well. You can wait until it gets merged to main or you can give it a try even now. The doc to use the docker playground is here: https://github.com/onetable-io/onetable/pull/258/files#diff-d713b45afd9e8b5ffc2728e6ba8882871143038694ff6e0141a56606c0738f5e
Let me know how it goes.

Very cool thank you @sagarlakshmipathy for the constant effort on this issue, will give it a try!

I do want to add one thing on this thread i noticed. On my intel based mac i had no issues running this quick start demo, the issue above is still happening on my m2 pro mac so not sure if its something regarding that.
Using java 11 on both, but i think the intel mac has mvn 3.6.3 version, the m2 running on 3.9.

thanks for reporting your findings.
I have an m2 mac as well and I don't see any issues while running the quickstart example on my machine (mvn 3.9.4).
sagarl@dev ~ % uname -m
arm64

sagarl@dev ~ % mvn --version
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Maven home: /Users/sagarl/Downloads/apache-maven-3.9.4
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "11.0", arch: "x86_64", family: "mac"

A quick side note: can you double check if you're seeing something similar to the issue mentioned here

Ok so i think i finally fixed the issue on my m2 mac, the thing that worked for me was for some reason installing amazon corretto jdk 11 for some reason.
ilchertara@rahils-mbp  ~/workplace/onetable   main ±  java -version
openjdk version "11.0.21" 2023-10-17 LTS
OpenJDK Runtime Environment Corretto-<IP_ADDRESS>.1 (build 11.0.21+9-LTS)
OpenJDK 64-Bit Server VM Corretto-<IP_ADDRESS>.1 (build 11.0.21+9-LTS, mixed mode)
 rahilchertara@rahils-mbp  ~/workplace/onetable   main ± 

Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: /opt/homebrew/Cellar/maven/3.9.5/libexec
Java version: 11.0.21, vendor: Amazon.com Inc., runtime: /Library/Java/JavaVirtualMachines/amazon-corretto-11.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.1.1", arch: "aarch64", family: "mac"

Now when running quick start it does not hang and passes. Thanks @sagarlakshmipathy for the help!


Unused basis argument in external.pp.scanorama_integrate()

[x] Additional function parameters / changed functionality / changed defaults?
[ ] New analysis tool: A simple analysis tool you have been using and are missing in sc.tools?
[ ] New plotting function: A kind of plot you would like to seein sc.pl?
[ ] External tools: Do you know an existing package that should go into sc.external.*?
[ ] Other?

The current external.pp.scanorarma_integrate() function has a basis argument which isn't actually used in the code (as far as I can tell). This is probably confusing to users (definitely was to me) so I would suggest removing it or at least mentioning in the docs that it isn't used.
I can probably submit a PR if maintainers let me know what the preferred option is.

Nevermind, this is actually used, I just failed at searching 🤦🏻 .


❓ Dark/Light Mode

I like to use Pixel Banner with the Border theme and Style Settings plugin which has an automatic light/dark mode setting. When my them changes to the dark settings, the title in my banner becomes unreadable, so I have to set it to a lighter text. But when then when my them switches to the light mode, I have to manually change the title color again.
I would love to see an inline title color for both light modes and dark mode.

@maliikm
would you mind putting together a quick sample vault (zip it and attach it here) that I can use to reproduce the problem and work out a solution for you?
Thanks so much for the issue report.
🍻 Cheers

@maliikm are you having an issue because the dark vs light mode changes the "color" of the title in obsidian?
I would suggest just starting your note content further down the page and/or adjusting the height of the banner.
The readability of the Title on the Pixel Banner solely depends on the banner image you are using and isn't anything I can really accommodate for.  If however you start your page content further down on the note (using the default content-start frontmatter field), you can mitigate this issue all together, no matter your dark/light theme.

For example, this note has the frontmatter filed set like this:
content-start: 350

This was I can read the note Title well no matter the dark/light theme.
The only other solution I can think of is having some option to specify a different banner image dependent on the dark/light theme, but unfortunately this is a complicated and heavy lift as it would involve extra complexity around random-shuffle, folder images, and frontmatter settings.... not something I would consider anytime soon as I think the cons far outweigh the pros here.
If I am not understanding the issue, please let me know.
Thanks again for your support.

@maliikm ping

Hi Justin, yes I guess the problem is mostly with where the heading starts, as it does start over the image itself, so I'll try out the suggestion to move the title below the banner image. I attached the vault in case you're interested in seeing my setup.
Text Vault.zip

Thanks for the info @maliikm
Please let me know with another issue or our Discord if you have any other feature requests/bugs 😀
eQuill Labs Discord Link


[Question] the proof that PyBullet's environment is more difficult than Mujoco's environment

Hi, I saw this description in the README.md
Note: those environments are derived from Roboschool and are harder than the Mujoco version (see Pybullet issue)

But when I clicked on the link about Pybullet issue, I found that the issue is no longer valid.
Therefore, I would like to ask if there are other links that can prove that the PyBullet environment is more complicated than MuJoCo?

But when I clicked on the link about Pybullet issue, I found that the issue is no longer valid.

Oh I see, all issues were removed/moved.
You can find an archived version here.
Basically, the robots used are heavier which prevent some weird behavior observed on Mujoco ones:

the half cheetah cannot flip around
the walker must walk (and cannot run as it is the case in the Mujoco version)

I think that the reward function are also different but apart from looking at the code, I don't have much reference to give you.

Ok, I got it. Thanks!


Can't uplaud image or save a draft or publish an article : "Failed to persist entry: API_ERROR: Not Found"

Hi everyone !
I'm stuck for a while with this problem, everything works otherwise I was able to add the different collaborators on the CMS but they have the same error.
Can not save a draft, publish an article or upload an image. On the first two I get an error "Failed to persist entry: API_ERROR: Not Found" and on the third an blank error but the console says "API_ERROR: Not Found" so I guess it's related...
When I try to save a draft
The famous error :

and the console :

When I try to upload an image
The blank error :

and the console :

Config.yml
backend:
  name: git-gateway
  accept_roles:
    - Editeurs
  branch: master
publish_mode: editorial_workflow
media_folder: "static/images/couvertures/"
public_folder: "/images/couvertures/"
collections:
  - name: "Articles"
    label: "Articles"
    folder: "content/articles/"
    create: true
    slug: "{{year}}-{{month}}-{{slug}}"
    fields:
      - {label: "Titre", name: "title", widget: "string"}
      - {label: "Date de publication", name: "date", widget: "datetime"}
      - {label: "Brouillon", name: "draft", widget: "boolean", default: false}
      - {label: "Couverture", name: "image", widget: "image"}
      - {label: "Miniature", name: "bgImage", widget: "image"}
      - {label: "description", name: "description", widget: "string"}
      - {label: "Auteur·e·s", name: "author", widget: "string"}
      - {label: "type", name: "type", widget: "hidden", default: "post"}
      - {label: "Article", name: "Body", widget: "markdown"}
  - name: "AilleursSurLeWeb"
    label: "AilleursSurLeWeb"
    folder: "content/ailleurssurleweb/"
    create: true
    slug: "{{year}}-{{month}}-{{slug}}"
    fields:
      - {label: "Titre", name: "Title", widget: "string"}
      - {label: "Date de publication", name: "date", widget: "datetime"}
      - {label: "Brouillon", name: "draft", widget: "boolean", default: false}
      - {label: "Couverture", name: "image", widget: "image"}
      - {label: "Miniature", name: "bgImage", widget: "image"}
      - {label: "description", name: "description", widget: "string"}
      - {label: "Auteur·e·s", name: "author", widget: "string"}
      - {label: "type", name: "type", widget: "hidden", default: "post"}

And here you have the Github Repo
Thank you all for reading, I hope not to have missed the solution in Github Issues and the doc :/

Your organization account probably needs to grant access to your Netlify CMS instance:
https://github.com/netlify/netlify-cms/issues/1816#issuecomment-445599821
You can find more detailed instructions here: https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps

Wow, thank you very much @tomrutgers  for responding so quickly!
It worked :) I close the issue !


update file name

Addressing issue https://github.com/OfficeDev/office-js-docs-pr/issues/267

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/includes/file-get-started-excel-jquery.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Quick time display

It would be really helpful to get some "at a glance " times into the application, particularly for duration (finished - started).

Add a duration method to baleen.models.Job that computes the number of seconds between started and finished (unless not finished, then between now and started).

Add the duration to the page colored green if it's less than an hour, yellow if it's less than 5 hours, and red otherwise.

Iconography from font awesome would also help make things stand out!

Ok, I've added the duration to the model and to the status page - but haven't done the front end work for colorization or iconography.

I can take a look at this.

@bahadasx awesome thanks -- have you seen the new front end? I had some debugging issues I had to deal with, and figured I mind as well just put the helpers I was looking at onto the status page.
Note also that you have direct access to the repo now; so please be sure to branch from develop and to merge into develop!

I did see the new front end.  It looks great and I think it was a good idea to split the logs out into its own page.

@bbengfort What are your thoughts on iconography?  Are you thinking along the lines of having an icon next to the label for each cell?

@bbengfort FYI, I made a PR to address this issue but somehow it ended up as a new issue #42.

@bahadasx my thoughts are basically that the icons give a quick visual indication of what's happening in the system, and allow you to symbolically look up the information you want faster (right now you just have to read through everything). If it looks good I think it will work, so an icon next to the label or in its own cell would work fine!

So this is closed by PR #42? (Pull requests are just issues)

I did not address the iconography, so you can leave it open until I address that if you like.

Ok - sorted; thanks!


fix user and room send_file

I removed a charset param that is not required by hipchat api and, moreover, the api is returning 400 when that charset param is passed.
Unsupported encoding: 'UTF-8'. Please, consider using UTF-8.

This PR fix the send_file call by removing that param

We noticed our bot started failing to send files yesterday. This changed fixed it for us.

Thanks for the PR. This looks like a bug on the hipchat API, I already raised the issue internally, and we're looking into a fix for it.

This was a regression on the HipChat API, that is now fixed. Could you let know if your bot is still having issues?

@rberrelleza k. thanks for looking into this.
The bot is no longer having issues uploading files. Thanks for fixing your API!


Bump z-index on navuser app menu

Addresses #99

I didn't bump the version here assuming we would not release a new version for this small change.


Sonarr V4 support

Seems I'm getting a 404 error on one of the Sonarr v4 endpoints
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://<IP_ADDRESS>:8989/sonarr/api/profile?apikey=REDACTED

Assuming there'd be other changes to the API as well, thats the only error I'm getting so far though.

Looks like v2 of the API is deprecated in V4. Looks like it may need to be upgraded to the v3 API.

I will include support for api v3 and backward compatibility in v3 by the end of next week


Question about access_api_server test

Is [0] a vulnerability? If you have anonymous enabled in the api you can see [2] as well as version and healthz. Only when you try to access namespaced objects as anonymous and you have access it makes sense to mark as vulnerable.
What others think?
This design document tries to have stricter defaults [1].
[0] https://github.com/aquasecurity/kube-hunter/blob/master/src/modules/hunting/apiserver.py#L228
[1] https://github.com/kubernetes/enhancements/pull/720
[2]
{
  "kind": "APIVersions",
  "versions": [
    "v1"
  ],
  "serverAddressByClientCIDRs": [
    {
      "clientCIDR": "<IP_ADDRESS>/0",
      "serverAddress": "IP:6443"
    }
  ]
}

@oriagmon thoughts? You seem to be the author of this test.

I think the way we should approach this is that kube-hunter explores what information is available from various endpoints, and shows that to the user. It is really up to the user to decide whether this is a risk or not. As an example, the CIS benchmark has long recommended turning off anonymous-auth access altogether on the API server, although many considered this overkill as it prevented anonymous access to health endpoints. One person's vulnerability is another person's useful functionality.

Thanks for the reply @lizrice . That makes total sense.
The way the information is presented to the user though, is a little scary [0].
It is not clear that this is only discovery information that can help create
an attack, an attack though might not be possible.
[0]
Vulnerabilities
+----------------------+----------------------+----------------------+----------------------+----------------------+
| LOCATION             | CATEGORY             | VULNERABILITY        | DESCRIPTION          | EVIDENCE             |
+----------------------+----------------------+----------------------+----------------------+----------------------+
| xxxxxxxx-xxxxxxxxxxx | Remote Code          | Access to server API |  Accessing the       | {"kind":"APIVersions |
| xxxxxxxxxx:6443      | Execution            |                      | server API within a  | ","versions":["v1"], |
|                      |                      |                      | compromised pod      | ...                  |
|                      |                      |                      | would help an        |                      |
|                      |                      |                      | attacker gain full   |                      |
|                      |                      |                      | control over the     |                      |
|                      |                      |                      | cluster              |                      |
+----------------------+----------------------+----------------------+----------------------+----------------------+

[1]
$ kubectl describe clusterrole system:basic-user
Name:         system:basic-user
Labels:       kubernetes.io/bootstrapping=rbac-defaults
Annotations:  rbac.authorization.kubernetes.io/autoupdate=true
PolicyRule:
  Resources                                      Non-Resource URLs  Resource Names  Verbs
  ---------                                      -----------------  --------------  -----
  selfsubjectaccessreviews.authorization.k8s.io  []                 []              [create]
  selfsubjectrulesreviews.authorization.k8s.io   []                 []              [create]
$ kubectl describe clusterrole system:discovery
Name:         system:discovery
Labels:       kubernetes.io/bootstrapping=rbac-defaults
Annotations:  rbac.authorization.kubernetes.io/autoupdate=true
PolicyRule:
  Resources  Non-Resource URLs       Resource Names  Verbs
  ---------  -----------------       --------------  -----
             [/api]                  []              [get]
             [/api/*]                []              [get]
             [/apis]                 []              [get]
             [/apis/*]               []              [get]
             [/healthz]              []              [get]
             [/openapi]              []              [get]
             [/openapi/*]            []              [get]
             [/swagger-2.0.0.pb-v1]  []              [get]
             [/swagger.json]         []              [get]
             [/swaggerapi]           []              [get]
             [/swaggerapi/*]         []              [get]
             [/version]              []              [get]
             [/version/]             []              [get]


faostat parquet file contains a huge metadata payload

The parquet files on catalog are much bigger than feather converted to parquet locally
Looking at the faostat_food_explorer dataset:

On the catalog, feather is 47.3 MB: https://catalog.ourworldindata.org/garden/faostat/2022-05-17/faostat_food_explorer/all_products.feather
On the catalog, parquet is 196.1 MB: https://catalog.ourworldindata.org/garden/faostat/2022-05-17/faostat_food_explorer/all_products.parquet

If I convert the feather file → parquet locally, it's 63.5 MB:
cat = catalog.RemoteCatalog()
food_explorer_df = cat.find(dataset="faostat_food_explorer").iloc[0].load()
food_explorer_df.to_feather("faostat_food_explorer.feather") # 47.3 MB (same as catalog)
food_explorer_df.to_parquet("faostat_food_explorer.parquet") # 63.5 MB (vs 187 MB on catalog)

Most of the file size in catalog is metadata payload (the data is identical, except for one column type being different (due to repacking)
When inspecting the metadata contained in the two parquet files (local vs catalog) with parquet-tools:
parquet-tools meta faostat_food_explorer.parquet > parquet.meta

The metadata of the locally generated parquet file is 38 KB
The metadata of the catalog parquet file is 132.6 MB

Most of the increased metadata payload is due to ARROW:schema being much bigger and owid_table being included
The rough diff of the first few lines, local vs catalog:
file:                                                                file:/Users/danielg/Desktop/parquet_file_sizes/local.parquet
creator:                                                             parquet-cpp-arrow version 7.0.0
extra:                                                               pandas = {"index_columns": ["product", "country", "year"], "$
- extra:                                                               ARROW:schema = //////grAAAQAAAAAAAKAA4ABgAFAAgACgAAAAABBAAQA$
+ extra:                                                               ARROW:schema = /////9A7YwMQAAAAAAAKAA4ABgAFAAgACgAAAAABBAAQA$
+ extra:                                                               owid_table = {"short_name": "all_products", "dataset": {"nam$
+ extra:                                                               owid_fields = {"product": {}, "country": {}, "year": {}, "ar$
+ extra:                                                               primary_key = ["product", "country", "year"]

file schema:                                                         schema

...from here there are some insignificant differences...

In the catalog metadata, the largest line lengths occur on line 4 and 5, and account for probably >99% of file size:
line 4: extra:                                                               ARROW:schema = /////9A7YwMQAAAAAAAKAA4ABgAFAAgACgAAAAABBAAQA
line 5: extra:                                                               owid_table = {"short_name": "all_products", "dataset": {"na

ARROW:schema line: locally 15105 characters long, catalog 75780129 characters long (~72 MB)
owid_table line: locally 0 (omitted), catalog 56821934 characters long (~54 MB)

Hopefully this helps with debugging. 😰

In line 5, the primary_key is huge:
"primary_key": [["Almonds", "Afghanistan", 1975], ["Almonds", "Afghanistan", 1976], ["Almonds", "Afghanistan", 1977], ["Almonds", "Afghanistan", 1978], ["Almonds", "Afghanistan", 1979], ["Almonds", "Afghanistan", 1980], ["Almonds", "Afghanistan", 1981], ["Almonds", "Afghanistan", 1982], ["Almonds", "Afghanistan", 1983], ["Almonds", "Afghanistan", 1984], ["Almonds", "Afghanistan", 1985], ["Almonds", "Afghanistan", 1986], ["Almonds", "Afghanistan", 1987], ["Almonds", "Afghanistan", 1988], ["Almonds", "Afghanistan", 1989], ["Almonds", "Afghanistan", 1990], ["Almonds", "Afghanistan", 1991], ["Almonds", "Afghanistan", 1992], ["Almonds", "Afghanistan", 1993], ["Almonds", "Afghanistan", 1994], ["Almonds", "Afghanistan", 1995], ["Almonds", "Afghanistan", 1996], ["Almonds", "Afghanistan", 1997], ["Almonds", "Afghanistan", 1998], ["Almonds", "Afghanistan", 1999], ["Almonds", "Afghanistan", 2000], ["Almonds", "Afghanistan", 2001], ["Almonds", "Afghanistan", 2002], ["Almonds", "Afghanistan", 2003], ["Almonds", "Afghanistan", 2004], ["Almonds", "Afghanistan", 2005], ["Almonds", "Afghanistan", 2006], ["Almonds", "Afghanistan", 2007], ["Almonds", "Afghanistan", 2008], ["Almonds", "Afghanistan", 2009], ["Almonds", "Afghanistan", 2010], ["Almonds", "Afghanistan", 2011], ["Almonds", "Afghanistan", 2012], ["Almonds", "Afghanistan", 2013], ["Almonds", "Afghanistan", 2014], ["Almonds", "Afghanistan", 2015], ["Almonds", "Afghanistan", 2016], ["Almonds", "Afghanistan", 2017], ["Almonds", "Afghanistan", 2018], ["Almonds", "Afghanistan", 2019], ["Almonds", "Afghanistan", 2020], ["Almonds", "Africa (FAO)", 1961], ["Almonds", "Africa (FAO)", 1962], ["Almonds", "Africa (FAO)", 1963], ["Almonds", "Africa (FAO)", 1964], ["Almonds", "Africa (FAO)", 1965], ["Almonds", "Africa (FAO)", 1966], ["Almonds", "Africa (FAO)", 1967], ["Almonds", "Africa (FAO)", 1968], ["Almonds", "Africa (FAO)", 1969], ["Almonds", "Africa (FAO)", 1970], ["Almonds", "Africa (FAO)", 1971], ["Almonds", "Afri .................aaaaaaaaaaaaaaaaaaaaand there is waay more

Got a fix, it's only this one dataset, a typo made it serialise much of the table into the metadata, but only for the parquet format.

Ah, awesome! I went into depth-first debugging, not checking the other files.

For sanity I did a scan of all other parquet files generated, this was the only case.
Here's the scan_for_bad_parquet.py script I used:
#!/usr/bin/env python

from pathlib import Path
from etl.files import walk
import pyarrow.parquet as pq
import json

for filename in walk(Path("data")):
    if filename.suffix != ".parquet":
        continue
    schema = pq.read_schema(filename)
    if b'owid_table' not in schema.metadata:
        continue

    meta = json.loads(schema.metadata[b'owid_table'])
    if 'primary_key' not in meta:
        continue

    primary_key = meta['primary_key']
    if (not isinstance(primary_key, list)
        or not all(isinstance(x, str) for x in primary_key)):
        print(f"{filename} has bad primary key")


[mtv/comedycentral] Add alternate way to retrieve mgid

Uses the embed URL to retrieve the mgid for a given episode, if all other methods fail.
Fixes rg3/youtube-dl#5369.

Turns out it was fixed meanwhile.

Please reopen, the mgid extractor has failed again, and I have confirmed that my patch fixes the problem.


[SDLe][native-sql-engine] Issues from Static Code Analysis with Klocwork need to be fixed

Issues from Static Code Analysis with Klocwork need to be fixed before OAP 1.0.0 release.

@HongW2019 FYI. just merged #2002

Got it, close it now. @zhouyuan


[Improve][Sort] Doris full database migration missing audit data

Description
Doris full database migration missing audit data

InLong Component
InLong Sort
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Audit module has been refactored, close this issue.


Minor Changes:

Implemented service for ldap auth
A tiny bit of refractoring
Added adaptation to current frontend for ldap auth

.

Breaking vercel deployment...

nigga what's the folder rename & change >?


feat: add oz prefix name

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 2 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 38.51%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/cmd/ozctl/cmd/create_exec_access_request.go
0
1
0.0%

internal/cmd/ozctl/cmd/create_pod_access_request.go
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1091

Relevant Lines:
2833

💛  - Coveralls


[SQL] Remove cross-file references from SQL specs

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1046

Includes https://github.com/Azure/azure-sdk-for-python/pull/1039
Will merge this one since it's the last one. ChangeLog in https://github.com/Azure/azure-sdk-for-python/pull/1039

included in https://github.com/Azure/azure-sdk-for-python/pull/1043


Single-header version

Hi, thanks for this great project! I've been looking for something like this 🙂 std::variant IMO violates C++'s "don't pay for what you don't use" principle (e.g. lots of valueless_by_exception checks) and doesn't fit my projects.
Would it be possible to create a single-header version? I can concatenate the files myself, but it would be nice to have it automatically generated when there's a new release.
[EDIT] Just wanted to add that I get about 35% better overall performance in my benchmarks, compared to mpark::variant. This is great 👍

Hey, thanks for your interest :)
The only reason I can think not to do that is that there are some headers that add "optional" stuff that you might not want.
For instance variant/stream_ops.hpp makes variant streamable into std::ostream's. Not everyone wants that though, I've seen a lot of libraries where that kind of thing is in a separate header to make it opt in.
The other big one that comes to mind is variant/spirit.hpp. The library has no dependency on boost spirit, but if you want to make boost spirit grammars that parse directly into your data structures and use strict_variant in your data structures, you need to specialize this trait that tells spirit that this thing is a variant and how to use it. I already did that work but I doubt you want to include that in all your translation units because then you will be compiling a bunch of boost spirit stuff you don't need -- boost spirit can take a long time esp. on older compilers. Usually what I do is only include variant/spirit.hpp in the .cpp file where I am actually using spirit. If you jam this in single file it might hurt the build time of your project.
But yeah I guess for many projects with nice build times it doesn't matter.
Do you already have a script to concatenate the files? If not I guess I can throw one together.


[MDEPLOY-265] Maintain backwards compatibility for alt*DeploymentRepository in id::default::url format

[MDEPLOY-265] Maintain backwards compatibility for alt*DeploymentRepository in id::default::url format
The legacy format (<=2.x) of alt*DeploymentRepository is id::layout::url.
The new format (>= 3.x) of alt*DeploymentRepository is id::url, which is equivalent to id::default::url from the legacy format.
This change introduces backwards compatibility with 2.x by supporting alt*DeploymentRepository values in the id::layout::url format if and only if the layout is equal to default.  The default layout is the most commonly used layout, so this should maintain backwards compatibility with the large majority of projects using the alt*DeploymentRepository properties.
Usage of the legacy format with the default layout will result in a warning message being logged.
Usage of the legacy format with layouts other than default will result in an exception being thrown.
One use case this change will help is when alt*DeploymentRepository properties are set in common maven settings.xml files used for a large number of projects.  For example, a CI server.  Keeping backwards compatibility with id::default::url allows those settings.xml files to be used regardless of the version of maven-deploy-plugin used by the projects built on that CI server.  Projects can individually upgrade their maven-deploy-plugin without breaking.
Following this checklist to help us incorporate your
contribution quickly and easily:

[x] Make sure there is a JIRA issue filed
for the change (usually before you start working on it).  Trivial changes like typos do not
require a JIRA issue.  Your pull request should address just this issue, without
pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [MPH-XXX] - Fixes bug in ApproximateQuantiles,
where you replace MPH-XXX with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the
commit message.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
[x] You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[ ] In any other case, please file an Apache Individual Contributor License Agreement.

@cstamas WDYT?

My original change was doing exactly this, so I am +1 on this (so "legacy syntax w/ default layout should work + warn), but there was a discussion where we agreed that ANY unexpected syntax should fail the build.
https://github.com/apache/maven-deploy-plugin/pull/12#discussion_r541552391
So, again, I am +1, but @mickroll?

So, again, I am +1, but @mickroll?

Build Warning is fine aswell. :+1:

Hmm, this should have happened pre 3.0.0 🤣. My proposal is to allow this during milestone phase, but ultimately drop with GA.

FWIW, I would like to keep these changes in 3.0 GA.   For me, it's not useful unless it makes it into GA.  It seems like such a small amount of code for huge wins in compatibility.

Let me think about that and come back to you later.

Can you please describe why this is so important to you since this is a non-standard case?

Sure thing.
We have an artifactory instance in our corporate environment to which we deploy thousands of our own artifacts.  This is a large corporate environment that supports many, many dev teams.
We do not specify a distributionManagement section in our thousands of git repositories. Instead, we specify the alt*DeploymentRepository properties in a maven settings.xml file (example) on our CI servers. When the thousands of git repositories are built using these CI servers, they automatically pick up the alt*DeploymentRepository values from the maven settings.xml files.  This gives us a central place to manage where artifacts are deployed.  This approach has proven invaluable at times, since we've gone through a few artifactory migrations, and have had to redirect things several times over the last few years.
We want to allow projects to upgrade the version of maven-deploy-plugin used in their projects at their own pace.  And we want the builds to continue to work and deploy correctly when they do upgrade maven-deploy-plugin without any other changes to the build pipeline.  This transparency requires backwards compatibility of the alt*DeploymentRepository value format, since they all use the same settings.xml file.
There are several alternatives, but none are very desirable

Stop using alt*DeploymentRepository, and use distributionManagement in each repo, or in parent poms.  This requires each repo to be updated any time we need to change the distribution settings.  This is not scalable.
Create separate settings.xml files for each alt*DeploymentRepository value format.  This does not allow repos to transparently upgrade maven-deploy-plugin.  The builds will break when maven-deploy-plugin is upgraded.  The build pipeline for each individual repo would then need to be modified to use different settings.xml file.  This is not something I want to expose to the vast majority of other developers, since they do not need to be aware of the distribution management settings to get their job done.

In short, not maintaining backwards compatibility of this format will cause us a tremendous amount of toil.  That toil can be easily avoided if the format remains backwards compatible.   The code to keep backwards compatibility is straightforward and simple, and totally worth it.

I agree with Phil. 3.0.0-M1 made it wrong: old param should be deprecated but usable (like this PR makes it), not unsupported. 4.x may drop legacy (deprecated) syntax completely, IMO

@philsttr Thanks for your elaboration. There are few nits with your settings which you should correct:

When defining central in a profile point to a non-existent URL so your mirror will do the right thing
Do not use central for deployment repos. You never logically deploy to it, use your own id please

Now back to your approach: As far as I understand the target repo does not depend on the group/artifact id, but no the CI server performing actions?

the target repo does not depend on the group/artifact id, but no the CI server performing actions?

(I do not quite understand the question, but I'll attempt to answer what I think you are asking.  If this does not answer your question, please clarify the question.)
Each of our many repos define their dependencies and plugins, and version of each.  They are free to use whatever they need.  They are currently using various versions of the maven-deploy-plugin  (but not 3.0.0-M1, since that broke compatibility).
The CI server does not define dependencies, plugins, or versions.

Sorry for the confusion. There was a nasty typo in my question. I wll rephrase: How do you know/decide on the CI server to which hosted repo a deployment will go and why is not possible to have that kind of information staticially in the POMs?

We have one shared artifactory instance to which all artifacts are published.  All CI servers use the same settings.xml file, which causes artifacts to publish to the same repositories on the shared artifactory instance.  The example settings.xml file shows that artifacts are published to one of three repositories on the shared artifactory instance (either maven-releases, maven-snapshots, or maven-combined)
We prefer to centrally manage the distribution settings on our CI servers via settings.xml files rather than poms.  We do this mainly because we have few CI servers (less than 5), and many poms (thousands).   If/when we need to change these settings, it's a trivial task to update the CI servers.  By comparison, to update all the poms would be a monumental task of distributed effort across many dev teams and release cycles.  It's just not a scalable solution.   Note that this isn't just a theoretical exercise.  We have had to update these settings several times over the past few years due to changes to our artifactory infrastructure.

OK, let me summarize: You update at most 5 CI servers for new URLs instead to manipulate the corporate POM and then need to update all dependend projects (thousands)?

Correct

But you still have to maintain developer settings to resolve artifactsduring coding, right?

Yes, the same settings.xml file is used by developers as part of an automated dev environment setup.

Thank you very much making your setup clear. I will re-review this PR today and go ahead with the merge.

@philsttr It'd be awesome if you could share/write down your approach as a single page for our Maven Site Guides as "Large Scale Centralized Deployments with Maven".

@michael-o  I'd be happy to.  Where are the Maven Site Guides located?  Can you point me to where I should submit a PR?

https://github.com/apache/maven-site/tree/master/content/apt/guides


Create guide on how to create Orion tweaks without Theos

Hey, sorry for the late response and thanks for the PR! For the guide on Orion without Theos, it's intended to be geared towards people who want to integrate Orion with other build systems like Xcode, SPM, and Bazel. The preprocessing stage is something we should definitely document in that article, but building Swift/Objective-C files themselves is out of scope for Orion's docs.
If integration with Xcode build scripts, SPM plugins, and the like is something you're familiar with then feel free to update your PR with that in mind; otherwise I definitely plan to get to that myself too. I will say that general information on cross-compiling Objective-C and Swift code for iOS is quite sparse atm (short of reading through the source code of an existing build system) – so if you do want to help document that I'd recommend somewhere like the iPhoneDevWiki which is better suited to deep dives than Orion's user-facing docs.


Fix typos in /lib

This pull request fixes some typos in the error messages for the methods in /lib

Hi, Thanks for patch, I see a lot of this kind of issues, I will add new way to handle this error report.so I'm not merge this patch.feel free open new issues and pull requests. thanks.


Upgrade to NodeJS service

#28
Dart service is impossible, so Node is the better solution.

https://github.com/103cuong/store-pattern-server


CPU centric pod eviction similar to memory centric eviction

The main feature request here is to provide the mechanism in the safe scheduler that will dynamically monitor and balance the cluster through eviction of pods from busy nodes.

Currently, Kubernetes monitors resource utilization of each nodes.  In case of out of memory, Kubernetes evicts offending pod from the node to release memory to bring back the proper performance of each nodes, however, when the CPU is fully utilized, CPU is compressed & throttled which is causing performance degradation of the application.  We also need eviction mechanism for CPU similar to "out of memory" case.  Since Kubernetes does not provide this option, we need this mechanism to avoid CPU performance degradation issue.


Various improvements required to connect to a managed remote host

Use case
Ansible host is a regular application server running RHEL 8, and needs to establish an IPSec connection to a NetApp storage. The storage is managed by various other means (either Ansible or other proprietary tools), but requires very specific parameters in order to establish a connection.
This pull request implements the necessary methods to pass all the required parameters to the tunnel configuration.
Features that have been added

When establishing a connection between the current running host on a playbook, and only one remote host, you don't need to specify the host in the connection variable.
The flag no_log has been added to the beginning of the opportunistic configuration to prevent leak of the PSK.
A few tweaks on the README file.

Options that have been added

shared_key_content -- the PSK in plain text (added a note to README about secrecy of the value).
leftid and rightid -- the IPSec ID of each host (when different from the FQDN).
ike and esp -- Allow detailed specification of the encryption algorithms.
type -- Tunnel or transport.

[citest commit:7966f6e9f5925d73bcf634fa4e478698865a321b]

ok - https://github.com/linux-system-roles/vpn/pull/66 was merged - please rebase

Can you do a rebase without a merge commit?

I created another PR

removes the merge request
fixes an error with if tunnel.hosts[host2]['shared_key_content']
adds a test for shared_key_content

https://github.com/linux-system-roles/vpn/pull/68

Sorry, when I saw your rebase note I had already merged. What should I do now?

Sorry, when I saw your rebase note I had already merged. What should I do now?

one of these

take the code from https://github.com/linux-system-roles/vpn/pull/68, replace your local branch with this, force push
do a git rebase -i master with your branch to squash into a single commit, then incorporate the additional commits from https://github.com/linux-system-roles/vpn/pull/68
drop https://github.com/linux-system-roles/vpn/pull/65 and we'll just use https://github.com/linux-system-roles/vpn/pull/68

[citest]

If we accept this PR, we're going to need a follow up PR to add a lot of testing for the new parameters, otherwise, QE is going to be very unhappy, and/or we won't be able to put this functionality into the downstream product.  @ueno can you help write some tests for leftid/rightid, ike_enc_alg, esp_enc_alg, and type?

[citest]
At least tests_host_to_host_psk_custom.yml should pass

passed! https://dl.fedoraproject.org/pub/alt/linuxsystemroles/logs/lsr-citool_vpn-65-4432c1e_RHEL-7.9-20200917.0_20220818-134510/artifacts/tests_host_to_host_psk_custom-PASSED.log

[citest]


config: remove SITE_HOSTNAME

The usage of SITE_HOSTNAME should be fully removed. It has been superseded by SITE_API_URL and SITE_UI_URL.
This includes (but not limited to):

Docs

Documentation should remove refeferences, and add the new variableas.

Invenio-CLI

Invenio-CLI uses a trick to correctly set SITE_HOSTNAME - this should be used for new varaibles.

Invenio-RDM-Records

Secret links have not been refactored to new code (still using )

SITE_API_URL and SITE_UI_URL should

end with :5000 for the local install (it does +1 )
end without :5000 for the containerized install (it doesn't -1 )

I've observed those as well when trying out the containerized setup :+1:


Data dir rfc

Issue: https://github.com/rancher/rancher/issues/45038

Problem

Solution

CheckList

[ ] Test

[ ] Docs

@ericpromislow Updated. CI won't pass until https://github.com/rancher/rancher/pull/45326 is merged anyways.

@jakefhyde please squash the commits when merging.


chore(litmus-portal): Added unique attributes in frontend for E2E testing and minor CSS changes

Proposed changes
This PR adds:

Unique attributes required for E2E tests
Refactored the LinearProgressBar Component
Minor CSS fixes

Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[x] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the commit for DCO to be passed.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

Dependency

Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

@amityt Can you add the key property to the two divisions! deepscan is complaining about the same

@S-ayanide DeepScan issues fixed :heavy_check_mark:

/run-unit


[Wallet] Add migration to set redeemComplete to true if account exists

Description
Added a migration for the Redux store that sets redeemComplete to true if there is an account saved on the store.
Tested
1- Manually set redeemComplete to false in the store and opened the app.
2- I saw the invite screen even though I had an account.
3- Add the migrations in the PR and opened the app again.
4- Saw on the logs that migrations run and I appeared on the Home screen.
Related issues

Fixes #4997

Backwards compatibility
That's the point of the PR :D

Hi @jeanregisser i have verified task using Test flight build v1.1.0 (21) & & Valora internal build V1.1.0(1004294309)
Test scenarios:

Verify user should able to install valora V1.0.1 build from play store
Verify user is able to upgrade valore v1.0.1 to internal build v1.1.0
Verify Invite code page should not show when user upgrade

Devices: iPhone 6+ (12.4.5), Google pixel Xl 8.1
Fixed issues:
#4997
Please let me know if any thing else i need to verify for this task.
Thanks !


cob_simulation: 0.7.5-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository cob_simulation to 0.7.5-1:

upstream repository: https://github.com/ipa320/cob_simulation.git
release repository: https://github.com/ipa320/cob_simulation-release.git
distro file: noetic/distribution.yaml
bloom version: 0.10.0
previous version for package: null

cob_gazebo_objects
* Merge pull request #178 <https://github.com/ipa320/cob_simulation/issues/178> from fmessmer/test_noetic
  test noetic
* Bump CMake version to avoid CMP0048 warning
* Contributors: Felix Messmer, fmessmer

cob_gazebo_tools
* Merge pull request #178 <https://github.com/ipa320/cob_simulation/issues/178> from fmessmer/test_noetic
  test noetic
* ROS_PYTHON_VERSION conditional dependency
* Bump CMake version to avoid CMP0048 warning
* Contributors: Felix Messmer, fmessmer

cob_gazebo_worlds
* Merge pull request #178 <https://github.com/ipa320/cob_simulation/issues/178> from fmessmer/test_noetic
  test noetic
* Bump CMake version to avoid CMP0048 warning
* Contributors: Felix Messmer, fmessmer

@fmessmer Looks like this conflicts now that I merged one of the other packages.  Mind rebasing?

@clalancette rebase done...was an expected conflict...thanks!


gather_all_tensors_if_available  share the same underlying storage for all GPUs

🐛 Bug

Hi, one of new features in   #2528  gather_all_tensors_if_available has a  list copy bug,  and this would lead that tensors in all GPUs  are the wrongly same as one GPU,  since they share the same storage:
https://github.com/PyTorchLightning/pytorch-lightning/blob/master/pytorch_lightning/metrics/converters.py#L304
gathered_result = world_size * [torch.zeros_like(result)]

change into:
gathered_result = [torch.zeros_like(result) for _ in range(world_size)]

@justusschock @SkafteNicki

@ShomyLiu good catch, would you be up for sending a PR? Please, note that the function is not used anywhere yet, but are there for future changes to the metric package.

@SkafteNicki  it's my pleasure for a PR. I will finish this as soon as possible.
Yeah, it's a new function to wrap the torch.distributed.all_gather.  But I think it is a very common use case;  especially, when using DDP mode, we always need to gather all the outputs cross all the GPUs.

@ShomyLiu Yes, I agree that it is a common use case.
Please ping me when PR is ready.

@SkafteNicki  Hi, I have sent a PR jus now for your review   #3319


#38 links about recently added blogs pointed to rss instead blog homepage - fixed.

Thank you for PR! :)

Closes #38