Odata not working

Hi,
I cannot get my OData call working, here is my code(below).
I am calling an MVC action (which is what the URL points to) however the jsGrid just shows the loading symbol and nothing loads.
    $(function () {
        $("#jsGrid").jsGrid({
            height: "300px",
            width: "100%",

            inserting: true,
            filtering: true,
            editing: false,
            sorting: true,
            paging: true,
            autoload: true,
            pageloading:true,

            controller: {

                loadData: function()  {
                    var d = $.Deferred();
                    $.ajax({
                        url: "http://localhost:50795/Orders/OrderModels/Index",
                        dataType: "json"
                    }).done(function (response) {
                        setTimeout(function () {
                            d.resolve(response.value);
                        }, 2000);
                    });
                    return d.promise();
                }
            },

            fields: [
                { name: "Customer", type: "text", width: 10 },
                { type: "control" }
            ]
        });
    });

My MVC function that is handling the URL request above is as follows:
public IEnumerable GetCustomerOrders()
{
string[] Customer = { "d", "d", "F" };
return Customer;
}

Do you see any error in the browser console? Try to put debugger into your done function to see whether you get there and if yes, then what is the response.

Also I noticed that you have pageLoading: true. In this case you should supply data to the grid in other format. You can find details in the docs http://js-grid.com/docs/#loaddatafilter-promisedataresult

Hi,
I have now set pageLoading:false;
I am getting the following error from the Debugger:
Failed to invoke return value callback: SecurityError: The operation is insecure.
How can I resolve this?
Thanks.

The problem is Same-origin policy
You cannot access data from another domain, unless client has special header specified in response from server.
See this SO question:
http://stackoverflow.com/questions/20442628/cors-jquery-ajax-request
Checkout this article to enable CORS in WebAPI:
http://www.asp.net/web-api/overview/security/enabling-cross-origin-requests-in-web-api
Or you can use jsonp, but it allows only reading https://learn.jquery.com/ajax/working-with-jsonp/

Hi,
I did as specified in:
http://stackoverflow.com/questions/20442628/cors-jquery-ajax-request
I amended my code as described, however I get the same result. I used Fiddler to verify that JSON is being returned and it is.
Any advice?
Thanks.

Are you sure you specified it on the server side also? Which version of ODATA do you use? If it's ODATA v4 you should have something like WebAPI config
public static class WebApiConfig
    {
        public static void Register(HttpConfiguration config)
        {
            // New code
            config.EnableCors();

            config.Routes.MapHttpRoute(
                name: "DefaultApi",
                routeTemplate: "api/{controller}/{id}",
                defaults: new { id = RouteParameter.Optional }
            );
        }
    }

Also in testing purposes you can install the following plugin to be able to request another domain with ajax https://chrome.google.com/webstore/detail/allow-control-allow-origi/nlfbmbojpeacfghkpbjhddihlkkiljbi?hl=en

I am running it off my desktop as an MVC app, not Web API.
I also made changes to the ISS Express /config/applicationhost with:
    <httpProtocol>
        <customHeaders>
            <clear />
            <add name="X-Powered-By" value="ASP.NET" />
			   <add name="Access-Control-Allow-Origin" value="*" />
				<add name="Access-Control-Allow-Headers" value="Content-Type" />
        </customHeaders>
        <redirectHeaders>
            <clear />
        </redirectHeaders>
    </httpProtocol>

Have you tried the Chrome extension? Just to see if it works, when CORS issue is solved.

Hi,
I have tried it - no luck. Is this a bug and if so can it be fixed please.
Thanks.

Have you tried to put a debugger into your done handler to see the response? Try to see the request in DevTools in the Network section to know whether it succeeded or not and what is the response (feel free to attach the screenshot of DevTools request details to this issue)


Social icon missing on the footer section of the site .

@akshitagupta15june Please assign this issue to me I want to work on it.

@akshitagupta15june Please assign this issue to me under hacktoberfest label.

Please assign me this issue for GSSoC 2024

@akshitagupta15june please assign this issue to me because I have raise the issue first.


Don't re-verify the ACME account after initial creation

Splitting out this specific sub-issue from https://github.com/jetstack/cert-manager/issues/407#issuecomment-432328420 to make sure it doesn't get lost.
Right now, some cert-manager clients re-verify their accounts at an extremely high rate. In general there's no reason to re-verify an ACME account, so this logic should be removed. Thanks!

@munnerz How's this coming along? Do you think you'll be able to land this this week?
Thanks,
JAcob

PR #1032 implements this 😄
On Tue, 30 Oct 2018 at 23:06, Jacob Hoffman-Andrews <
<EMAIL_ADDRESS>wrote:

@munnerz https://github.com/munnerz How's this coming along? Do you
think you'll be able to land this this week?
Thanks,
JAcob
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jetstack/cert-manager/issues/1013#issuecomment-434502517,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMbP_CwmK9uIa8a-O66WxQdAdBlIJIcks5uqNuMgaJpZM4X7Juu
.


Change: use NodeId instead of RaftTypeConfig if a type only needs node-id as type param.

Changelog
Change: use NodeId instead of RaftTypeConfig if a type only needs node-id as type param.

Change: from DefensiveError<C: RaftTypeConfig> to DefensiveError<NID: NodeId>
Change: from ErrorSubject<C: RaftTypeConfig> to ErrorSubject<NID: NodeId>
Change: from Membership<C: RaftTypeConfig> to Membership<NID: NodeId>
Change: from MissingNodeInfo<C: RaftTypeConfig> to MissingNodeInfo<NID: NodeId>
Change: from SnapshotMeta<C: RaftTypeConfig> to SnapshotMeta<NID: NodeId>
Change: from StorageError<C: RaftTypeConfig> to StorageError<NID: NodeId>
Change: from StorageIOError<C: RaftTypeConfig> to StorageIOError<NID: NodeId>
Change: from Violation<C: RaftTypeConfig> to Violation<NID: NodeId>
Change: from Vote<C: RaftTypeConfig> to Vote<NID: NodeId>
CI: lint example-raft-kv

This change is

But the runtime itself will be in RaftTypeConfig.

Interesting!

But the runtime itself will be in RaftTypeConfig.

Interesting!

The other option would be to pass the Runtime as another type parameter, which we likely don't want to have. So, the association on RaftTypeConfig seems to me as the best idea.
The next thing is, of course, where we'll get the instance of the runtime, but that should be trivial to solve (make TokioRuntime have a Default which is used to construct an (empty) instance, create TestRuntime explicitly and pass it in a secondary new_with_runtime() constructor).


Reimplemented Paths framework in C++

This is the "SceneHierarchy rewrite" requested in #852. In reality, the SceneHierarchy code is barely touched, and it's the underlying Path and PathListingWidget classes which are rewritten in C++ for improved performance.
Paths can still be implemented in Python (and several are still in Gaffer), but the performance critical Path, FileSystemPath and ScenePath are now implemented directly in C++. I've also replaced the old Path.info() method which returned a dictionary with a new pair of Path::attributeNames() and Path::attribute() methods. This allows a single attribute to be queried at a time (a requirement Ivan had a long while back) and works around the fact that we don't have a direct equivalent for dict in pure C++. Attributes must be derived from RunTimeTyped, which is the most flexible we can be within the Cortex framework, but is still more restrictive than the pure Python implementation. The old info() method isn't visible in C++ at all, but I've emulated it in the bindings to keep old Python code working, and also provided default implementations for the new attribute API that use the old info() method if its available. I hope this will ease the transition between the two implementations.
The PathListingWidget rewrite means that we must now link to Qt from GafferUI, and there are some details to be aware of there and which are documented in the comments for 6f4e139. I'll write a separate internal mail about the necessary environment changes at Image Engine. PathListingWidget columns are now implemented in C++ too, which means they have lost a little flexibility compared to their old Python counterparts, but they have much better performance. 808b1c0 and cbb6a3d demonstrate how to update code to deal with that.
I don't think this is quite there yet, and I'm still waiting to see if the Travis tests are passing perfectly, but I wanted to get something up for discussion. In particular, I'd really like feedback on the following :

Is "attribute" a good name for "something you can query about a Path"? Are we worried about potential confusion with scene attributes? I didn't want to overload info() to avoid confusion with the old method, and also infoNames() sounds awful. I thought about "property", but that's got overlap with Qt. Any other ideas, or are you happy with attribute?
Many of the Path implementations which remain in Python are still implementing info() and relying on the emulation layer in the bindings to implement the attribute methods. That was useful to me in testing, but should I go through and replace them with the proper implementation. Or replace all but one, so we still have one testing the emulation?

I've fixed a bug and uploaded an updated set of dependencies with cortex 9.0.0-b3 and shiboken included, so the Travis tests now pass.

I haven't reviewed the code yet, but any reason you included the version bump here rather than waiting until it was merged?

Is "attribute"/"property" a good name for "something you can query about a Path"?

"trait", "feature"?

This branch requires Cortex 9.0.0-b3, and updated dependencies packages which include the Qt headers and the Shiboken Python module. I needed to update the SConstruct and IE config in order to be able to build that package and upload it so that the Travis tests could pass. As part of that I also needed to bump the version number to give the package it's proper version. In the past I've done this without committing the changes, and ended up committing them too late, and having no true record of how the dependencies were built. So this time I thought it was best to have a commit where I could say "that's how the dependencies were built".
Really, I think we need to move the dependencies build logic into the gafferDependencies project so that it's a standalone thing, but I haven't found them time. My current plan is to do it when I get GafferAppleseed integrated into the default builds, as that will require additions to the dependencies build anyway.

Traits and features both sound a bit on/off to me - like a path has them or it doesn't, rather than all paths have them, but with potentially varying values. Does that make sense?

Many of the Path implementations which remain in Python are still implementing info() and relying on the emulation layer in the bindings to implement the attribute methods. That was useful to me in testing, but should I go through and replace them with the proper implementation. Or replace all but one, so we still have one testing the emulation?

Lets go ahead and replace them. Better to have all the examples showing the thing we want people doing. Maybe we can have a manufactured example in the tests to verify the info() approach?

I get this in my terminal when using the Ops mode of iebrowser:
WARNING : PathListingWidget : TypeError: No registered converter was able to produce a C++ rvalue of type boost::intrusive_ptr<IECore::RunTimeTyped const> from this Python object of type list

I presume that's something in ieGafferExtensions that needs fixing up?

Is "attribute" a good name for "something you can query about a Path"? Are we worried about potential confusion with scene attributes? I didn't want to overload info() to avoid confusion with the old method, and also infoNames() sounds awful. I thought about "property", but that's got overlap with Qt. Any other ideas, or are you happy with attribute?

I am a little worried about the confusion with scene attributes... it'll be pretty hard to explain to a user... "There's an issue with the attributes on the scene path. No, not the attributes on the path in the scene, the attributes on the thing that lets you look at the path in the scene".
@paulondc didn't mind properites, he didn't think people would be confused with Qt properties.
@ivanimanishi said that Jabuka uses infoKeys currently, and he doesn't mind that. Or if you really don't like having info in there, maybe just keys()?

I've added a bunch of commits to address your comments. Things still outstanding :

Prefix the exception for out of range exceptions? I guess I don't mind either way very much, but what's there matches what was in Python, and I never had need for more. I guess in C++ it can be handy to have a prefix, but in Python you get that from the stacktrace anyway.
"Looks funny". Not a very compelling argument, but I can change it if you really want.
Remove info() from python implementations and replace with attributes() and attributeNames(). Agreed - I'd like to get agreement on the right names for attributes before I do this though, so I don't have to do it twice.
'Path' object has no attribute '_setCaches'. You mailed offline about this and I've replied offline too, I'm just putting it here so we have a complete list of all outstanding questions.

That just leaves the question of the naming. I decided to move away from info() for a few reasons :

It started to sound funny. I guess it sounds like a plural thing to me, so getting one at a time of it sounded off. This is the least compelling reason.
Jabuka has overloaded it to optionally take an infoKey, and I really didn't want to try to translate that into two C++ virtual functions with the same name, different return types (one dict-like one and one RunTimeTyped one), and then try to manage compatibility in the bindings as well.
We don't even have a dictionary-like type in C++ that can hold generic RunTimeTyped objects - the closest we have is CompoundData or CompoundObject. I felt it was important to support RunTimeTyped to keep it as flexible as possible, and it seemed that the one-at-a-time query was what we really wanted anyway (Ivan made a very good case for it in the past). So a new API plus a backwards compatibility layer for the short term seemed the best way.

That leaves us with properties vs attributes I think. I find it hard to imagine the scenario where we're trying to explain Path attributes vs ScenePlug attributes to a user - only the latter are really user facing in any way. So I think it's more down to what us programmers think. I agree that the clash with Qt properties isn't really a concern - I guess it felt like one to me because I was working on Qt/Paths code at the time, but we explicitly exclude Qt from the public API, so it's not really relevant from an outside perspective.
I don't feel crazily strongly either way, and I'm a bit biased by being the poor typist in this case. Maybe properties would be better? Better enough to warrant changing it? Wanna have a quick chat with the guys to get a consensus and then I'll go with the majority?

Prefix the exception for out of range exceptions

Yeah, I was thinking about the lack of full stacktrace making it more relevant.

properties vs attributes

Consensus is to go with properties.

OK, I've replaced attributes with properties (and I think I prefer it), and updated all subclasses to implement the property API rather than the old info one. Good to go?

Code looks good, but I'm marking this as pr-externalDependency until we do some testing with users. I'm hoping to get @chelmer and Norrie on it today.

How about we merge anyway, so I can work on top of it and get a bit more testing done? If we need to push out anything else in a hurry we can always use a 0.9_maintenance branch to do so...

I've pushed a fix for a crash which could occur if a plug was removed from its node, while being observed by a ScenePath which is then destroyed before the node is. I'm speculating that this will fix the crash that Ben observed in Caribou during testing, although I haven't reproduced his original problem.


Migration of nfv-example-cnf-deploy roles to redhatci.ocp.collection

SUMMARY
Migrating the roles from https://github.com/rh-nfv-int/nfv-example-cnf-deploy
ISSUE TYPE

New or Enhanced Feature

Tests

[x] example-cnf deployment in direct mode - https://www.distributed-ci.io/jobs/1b0bc57c-2acc-413e-9a67-40818fd83617/jobStates?sort=date
[x] example-cnf deployment in LB mode - https://www.distributed-ci.io/jobs/40aa9647-57d5-4d5c-8adf-a85d2483cfd3/jobStates/?sort=date
[x] example-cnf deployment in LB mode with preflight and certsuite execution - https://www.distributed-ci.io/jobs/56d33661-20cd-47e3-8d1c-a6876f02f4b9/jobStates?sort=date
[x] example-cnf extra trex job + draining scenario - https://www.distributed-ci.io/jobs?limit=20&offset=0&sort=-created_at&where=pipeline_id:af8c00f4-7683-41c3-aa32-8bc661931e35,state:active
[x] example-cnf upgrade validation scenario - https://www.distributed-ci.io/jobs?limit=20&offset=0&sort=-created_at&where=pipeline_id:d2757257-08c8-4167-982d-77a4f36ea5e2,state:active

Test-Hints: no-check

The change is ready for review, in terms of testing, all possible scenarios are passing. I just have pending to make the sanity check to pass and to refactor the README. The rest of the code is ready for review, cc @capolrik

Commits have been squashed and the README is now updated, this change is ready.

LGTM, only a couple of things in the README to update if possible Also, I wonder if it's worth it to bump up the version in ansible-collection-redhatci-ocp.spec because of the new role addition.

I didn't do it on a first instance because it didn't imply a change in our agents, but I'll do it anyway, thanks!


How to implement interceptor(or middleware)-like functionality before or after each rpc call?

Is your feature request related to a problem? (你需要的功能是否与某个问题有关?)
I'm implementing a service which contains 8 rpc calls, and i want to do something (auth, logging, tracing, etc) before / after each of these rpc calls, how should i do that ? A similar issue already existed in grpc https://github.com/grpc/grpc/issues/9035
Describe the solution you'd like (描述你期望的解决方法)
How to do it in a clean and safe way?
Describe alternatives you've considered (描述你想到的折衷方案)
Currently I'm considering sub-classing brpc::ClosureGuard and add logging/tracing logic there, but is that even possible ?, if so, is it safe?
Additional context/screenshots (更多上下文/截图)

client-side auth, server-side auth, tracing (no english doc yet). As for logging, it's more likely to be temporarily added for debugging, with the source code in hand, I think you can add logging anywhere you like.

Thanks, i'll look into it.


[#544] ADD Rails/HttpStatus cop

This cop enforces consistent use of symbol or numeric
value to describe HTTP status.
Example EnforcedStyle: symbol (default)
  # bad
  it { is_expected.to have_http_status 200 }
  it { is_expected.to have_http_status 404 }

  # good
  it { is_expected.to have_http_status :ok }
  it { is_expected.to have_http_status :not_found }
  it { is_expected.to have_http_status :success }
  it { is_expected.to have_http_status :error }

Example EnforcedStyle: numeric
  # bad
  it { is_expected.to have_http_status :ok }
  it { is_expected.to have_http_status :not_found }

  # good
  it { is_expected.to have_http_status 200 }
  it { is_expected.to have_http_status 404 }
  it { is_expected.to have_http_status :success }
  it { is_expected.to have_http_status :error }

Closes #544

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes.
[x] The build (bundle exec rake) is passing.

If you have created a new cop:

[x] Added the new cop to config/default.yml.
[x] The cop includes examples of good and bad code.
[x] You have tests for both code that should be reported and code that is good.

Thank you for your first PR on rubocop-rails, @anthony-robin.
Don’t be intimidated by the four failing builds – they’re all failing for the same reason: a too long line in the YAML config. You can see the error locally by running rake confirm_config.

Thanks for your review !
I want to apologies for my naive approach on this cop. As I didn’t want to add rack as dependency of the gem, I recreated the hash without thinking I could require it from the rails dependency :(
I will update my code according to your recommendation this week !
Thanks 👍

I want to apologies for my naive approach on this cop.

No need to apologise.

As I didn’t want to add rack as dependency of the gem, I recreated the status hash without thinking I could require it from the rails dependency

Just to be clear, this gem doesn’t have a dependency on either of rack or rails. So I think enabling/disabling autocorrect by trying require 'rack' ; rescue LoadError would be a reasonable approach.

I made some changes according to your comments :)
However, I have some hard time figuring out how works the pattern in the def_node_matcher method:

How can I set the selector to be the status code instead of the method name ? (I had a look at several other cops but the syntax doesn’t make sense to me)
How can I handle the parenthesis in the pattern ?

I added more tests (that are still failing for now) until I understand how works the AST pattern.
Also, is it fine to add rack as a development dependency only ? I don’t know how I can make specs to pass without specifying it in the gemspec …
Thanks !

The confirm_config is failing. I'm not sure why the blank line is being removed at the top of my configuration cop here

Feel free to refactor this cop as your wish after merging it :)


Implement generic OTP action.

support for TOTP and HOTP urls.
use 'totp' as an alias for new otp action.
add ability to parse "otpauth://" urls (supported by pass-otp,
passforios, browserpass).
maintain compat with YAML style "totp" entries.
add ability to produce QR codes (-qr filename.png).

Closes #422

Updated!

I'm facing this issue now, do I need to call the old command differently now or is it broken for all my old entries and I need to edit them?
$ gopass  gitlab.blablabla.com/authenticator
otpauth://totp/john.doe@blablabla.com?secret=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&issuer=gitlab.blablabla.com+%7C+john.doe%40blablabla.com
$ gopass totp -c gitlab.blablabla.com/authenticator

Error: No OTP entry found for gitlab.blablabla.com/authenticator
$```


GH-615: Docs - Migrating Legacy Error Handlers

See https://github.com/spring-projects/spring-kafka/issues/615
cherry-pick to 2.8.x

... and cherry-picked to 2.8.x


[Migration] Data type change in api.identity.oauth.dcr.endpoint.yaml swagger Application property

Describe the issue:
With this improvements here, client_secret_exp attribute will no longer be a string value. It has been converted from string to a long value. Any client created using this swagger must change according to this new change since this is not backward compatible.

Added to docs with https://github.com/wso2/docs-is/pull/2991, https://github.com/wso2/docs-is/pull/2997


Reorganize

This pr does:

organize test files
separate test files from example input files
pep8 issues for all python files (didn't solve E501 -line too long)

This PR addresses https://github.com/ergs/d3ploy/issues/123


IPROTO-65 WrappedMessage.writeMessage does not handle instances of Sh…

https://issues.jboss.org/browse/IPROTO-65

Thanks @anistor :+1:

Integrated in both 4.2.x and master (4.3.x)


tests: Extend wait time after interrupt

Description
This PR increases the timeout after interrupting a thread in the ConstantTimeBackoffTest.waitBeforeRetryWithInterrupt test, preventing intermittent failures especially in build envs with limited resources
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale

[ ] Major
[x] Minor

How Has This Been Tested?
Builds fail for some other reason

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_check_mark: centos7 :heavy_multiplication_x: centos8 :heavy_check_mark: debian. SL-JID 110

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 112

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_check_mark: centos7 :heavy_multiplication_x: centos8 :heavy_check_mark: debian. SL-JID 113

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_multiplication_x: centos7 :heavy_multiplication_x: centos8 :heavy_multiplication_x: debian. SL-JID 115

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_multiplication_x: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 119

Packaging result: :heavy_multiplication_x: centos7 :heavy_multiplication_x: centos8 :heavy_check_mark: debian. SL-JID 126

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 127

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 128

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 142

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_check_mark: centos7 :heavy_multiplication_x: centos8 :heavy_multiplication_x: debian. SL-JID 143

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_multiplication_x: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 145

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 146

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_check_mark: centos7 :heavy_multiplication_x: centos8 :heavy_check_mark: debian. SL-JID 147

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 162

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_multiplication_x: centos7 :heavy_multiplication_x: centos8 :heavy_check_mark: debian. SL-JID 163

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_multiplication_x: centos7 :heavy_multiplication_x: centos8 :heavy_multiplication_x: debian. SL-JID 173

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_multiplication_x: centos7 :heavy_multiplication_x: centos8 :heavy_multiplication_x: debian. SL-JID 174

@blueorangutan package

Packaging result: :heavy_multiplication_x: centos7 :heavy_multiplication_x: centos8 :heavy_multiplication_x: debian. SL-JID 175

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 176

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S]

Packaging result: :heavy_check_mark: centos7 :heavy_multiplication_x: centos8 :heavy_check_mark: debian. SL-JID 177

unit test only, merging


Bugs in current master

first issue
I downloaded the current master and tried to compile it for
Kernel version: Linux version 5.10.7-gentoo (xxx@linuxServer) (gcc (Gentoo 9.3.0-r2 p4) 9.3.0, GNU ld (Gentoo 2.34 p6) 2.34.0)
it failed with
arch/arch_info.c:52:10: fatal error: sys/sysctl.h: No such file or directory
52 | #include <sys/sysctl.h>
|          ^~~~~~~~~~~~~~
compilation terminated.
to make it work I changed
52 | #include <sys/sysctl.h> to 52 | #include <linux/sysctl.h>
this seems to be necessary for new Linux builds because sys/sysctl.h has been moved to linux/sysctl.h

second issue
when starting ltfs the first time it fails with
ltfs: error while loading shared libraries: libltfs.so.0: cannot open shared object file: No such file or directory
this can be fixed as described in
http://www.tandbergdata.com/default/assets/File/PDFs/LTFS_For_Linux_and_Mac_User_Guide_March_2014.pdf

On some systems trying to execute the ltfs command may result in an error message of the form“libltfs.so.0: cannot open shared object file: No such file or directory”. To resolve this it is necessary to tell the linker/loader how to locate the required dynamic library files. There are several ways of doing this:
•Add/usr/local/lib/ to the environment variable LD_LIBRARY_PATH  OR
•(Asroot) Add /usr/local/lib/  to the file /etc/ld.so.conf  and then execute /sbin/ldconfig.

Maybe you could add this to the readme :)

This issue was fixed by #262.

I just cloned the repo and ran the command ltfs and I'm getting:
ltfs: error while loading shared libraries: libltfs.so.0: cannot open shared object file: No such file or directory
This is not in fact fixed.

@DrBrad ,

I just cloned the repo and ran the command ltfs and I'm getting:
ltfs: error while loading shared libraries: libltfs.so.0: cannot open shared object file: No such file or directory
This is not in fact fixed.

The problem fixed in this issue, actually #262, is the first problem, build break in the new linux systems.
Second problem is not a target of this issue because, the solution is already provided in to the original description in this issue. Please refer the last 3 parts of the original message.
Actually, configuration of the path of dynamic loading system is different in each distro. At this time, LTFS targets RHEL7/8 mainly and they already have user/local/lib in it. And gentoo is not a list of our target list at this time. So, I don't know how to handle this kind of information in the README at all... It is really helpful if you can describe it in the README as a PR.


Event Schedule

VTN code question.
Can created events be accessed from a callback via an aiohttp GET endpoint?
For example if I have some code to create an event to be pushed down to a VEN like below:
"""
Handle a trigger event request with openleadr.
"""
server = request.app["server"]
server.add_event(ven_id=ven_id,
    signal_name='LOAD_CONTROL',
    signal_type='x-loadControlCapacity',
    intervals=[{'dtstart': event_start_utc,
                'duration': timedelta(minutes=minutes),
                'signal_payload': 1.0}],
    callback=event_response_callback,
    event_id=event_start_formatted_local_tz,
)

Is it possible to lookup all events configured with for server that would show event_IDs and associated VEN for the event ID? Any tips on how to implement this greatly appreciated.

I think you could set up a separate database to keep track of your created events, so that every time you call the event trigger the server writes the relevant information (like ven ID and event ID) to an "events" table in the database and then call the server.add_event(). This way you can code another GET endpoint that queries the DB which I think is a common use case, or connect directly to the DB from another terminal.

@porkytin thanks for the response, that makes perfect sense. What I envision starting out on this journey is something very small, like a just a handful of VENs all (part of the same utility demand response program) receiving the same demand response signal at one time.
Do you think pydantic models are a neat feature for that could be incorporated into a restful openLeadr VTN?
I have been playing around with aiohttp-pydantic example code, morphing it into VEN storage where thru the rest interface VENs can be updated, added, deleted, viewed, etc. See screenshot below...
Curious if anyone would be interested in collaborating at all on something like with, maybe with jwt incorporated for authentication?
The aiohttp pydantic seems sort of cool, it has swagger features built into it.

I'm not familiar at all with pydantic, but if it provides a simple way to add a graphical interface for making requests to your VTN´s API I think is useful. In my case, I coded a simple client in python to make those requests (add_ven, add_event, cancel_event, etc.) and for "security purposes" I'm sending the whole private key in the request, and the server checks if it matches its own, which I don't think is a recommended way of doing these things, even if the request is encrypted. So, adding a more standard auth method with jwt to interact with the internal API would be cool.
If you go on with your project I think it could serve as an example/tutorial of how to implement OpenADR server and clients with openLEADR.

@porkytin Thanks!


Indicator Refactor & Tests

Simplification of the Indicator class and creating an interface for each of the individual indicators. I've also included the start of a unit testing script named tests.py. Aside from finding more intuitive names for anything named d# (d1, d2, d3), the only thing you can do is to set up a test case for run_logc.

@Jwmazzi i think i merged your changes them successfully.


Custom class

I added a new property “Class” to the GoogleMap class, in order to be able to override the default one.
inside the GoogleMap class:
public string Class { get; set; }
then inside the GoogleMapBuilder class:
public GoogleMapBuilder Class(string className)
{
if (className == null) throw new ArgumentNullException("class");
Component.Class = className;
return this;
}
and inside the Build function:
var content = new HtmlElement("div")
.AddClass(String.IsNullOrEmpty(Component.Class) ? "googlemap" : Component.Class)
.Attribute("id", Component.Id);

With the current version it is really easy to customize the googlemap container by including styles in your css targeting the googlemap class the control provide.
I don't really see the need to add the "Class" helper method you are suggesting.
Could you please point me out with some scenarios where the current implementation is not enough
Thank for your feedback.


Is there way to add typing to .meta()?

Hello, nice approach, few weeks ago I implemented someting similiar but there is no reason to duplicate similiar packages. And I really confused why zod author won't support this feature natively, however I understand his arguments.
Now I think about the way to make this lib support typing of data containing in meta. I tried to override default type Record<string, unknown> it in standalone d.ts but this unfortunately does not work (this only works when I edit embedded node_modules/zod-metadata/dist/index.d.ts):
type TMeta = {
    example?: any;
    description?: string;
}

declare module 'zod' {
    interface ZodTypeDef {
        meta?: TMeta;
    }
    interface ZodType {
        getMeta(): TMeta;
        meta(meta: TMeta): this;
    }
}

What do you thing about making at least optionally generic getMeta and meta methods, like this?
declare module 'zod' {
    interface ZodTypeDef {
        meta?: Record<string, unknown>;
    }
    interface ZodType {
        getMeta<T = Record<string, unknown>>(): T;
        meta<T = Record<string, unknown>>(meta: T): this;
    }
}

This is ugly, of course, but I really don't see other options to override meta typing. Maybe you have some ideas?
UPD: I solved overriding issue: first line import z from 'zod'; is neccessary to make it work, so we have a typed meta now! )
<root>/typings/zod-metadata.d.ts:
import z from 'zod';

declare module 'zod' {
    interface TMeta {
        one?: string;
        two?: number;
    }
}

And to make it work we need to slightly change node_modules/zod-metadata/dist/index.d.ts:
declare module 'zod' {
    interface TMeta {
        [k: string]: unknown;
    }
    interface ZodTypeDef {
        meta?: TMeta;
    }
    interface ZodType {
        getMeta(): TMeta;
        meta(meta: TMeta): this;
    }
}

This works because interfaces in TS can be extended, so we exactly extending TMeta.

@kozubsky hey, thanks for the issue. I'll give it a shot. Can you check if https://github.com/IvanovES/zod-metadata/pull/2 does it?

@kozubsky hey, thanks for the issue. I'll give it a shot. Can you check if #2 does it?

Hello, thank you for your attention to this issue! I tried both approaches and the original one works better for my purposes. Let me explain.
(A) Defining global type for all meta() and getMeta() calls. It supports autocomplete (at least in JetBrains' IDE).
node_modules/zod-metadata/dist/index.d.ts
import z from 'zod';

declare module 'zod' {
    interface TMeta {
        [k: string]: unknown;
    }
    interface ZodTypeDef {
        meta?: TMeta;
    }
    interface ZodType {
        getMeta(): TMeta;
        meta(meta: TMeta): this;
    }
}

export declare function register(zod: typeof z): void;

And overriding TMeta interface in project, for example in <root>/typings/zod-metadata.d.ts:
import z from 'zod';

declare module 'zod' {
    interface TMeta {
        name: string;
        age?: number;
    }
}

Finally, we have this:

(B) Approach from #2 automagically infers type from meta() argument and it works... Within single file. In another IDE has no idea about getMeta() return type anymore, unfortunately.


Ingress only external

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets
-

License
Apache 2.0

What's in this PR?

Why?

Additional context

Checklist

[ ] Implementation tested
[ ] Error handling code meets the guideline
[ ] Logging code meets the guideline
[ ] User guide and development docs updated (if needed)

To Do

[ ] If the PR is not complete but you want to discuss the approach, list what remains to be done here

A fix in the upstream project will make this change obsolete


[labs/react] Omit 'children' from element type in props

Fixes #1826

@justinfagnani is there already a plan for a prerelease of @lit-labs/react that will include this change?


Fix infinite recursion for ElementName property

Fix infinite recursion for ElementName property

Do you know why CI was failed?

This is a transient failure.  Passed on re-run.


Option for case-insensitive filter

Hello,
is it possible to add a flag for case sensitivity file filter? In minimatch there is an optionflag for that:
https://github.com/isaacs/minimatch#nocase
Currently the filterFilter only matches case sensensitiv.
Kind regards,
Dennis

You can set filter to be a function, then do your own call to minimatch with whatever options you like.
This lib does not currently provide a way to pass arbitrary options to minimatch.


ASU-760 Add MAILER_LOCK_PATH to settings

The lock file's path needs to be changeable as otherwise, it tries to
add lock file to the root of the application and it is not permitted in
the OpenShift platform.

Codecov Report

Merging #44 (d42bcd6) into develop (32d1bb4) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop      #44      +/-   ##
===========================================
+ Coverage    88.71%   88.73%   +0.01%
===========================================
  Files           30       30
  Lines          984      985       +1
  Branches        98       98
===========================================
+ Hits           873      874       +1
  Misses          88       88
  Partials        23       23

Impacted Files
Coverage Δ

apartment_application_service/settings.py
82.95% <100.00%> (+0.19%)
:arrow_up:

Continue to review full report at Codecov.

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


Distinguish between countries as spatial regions and countries as organisation

Description of the issue
In the context of issue #1449 we discussed at the last OEO dev meeting brevely that we have to distinguish between

countries as spatial regions, defined by their borders, and
countries as organisation, which are actors and doing things.

Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

Sounds good. This ties into the #1336 discussion.
One could further specify "countries as spatial regions, defined by their political borders, .."

In the GEO ontology I found an article on the distinction of the sovereign nation state versus the geographical region claimed and governed by the nation state: https://github.com/ufbmi/geographical-entity-ontology/wiki


"Execute SQL Statement" and "Execute script" don't see delimiter

Description
"Execute SQL Statement" and "Execute script" options don't see a delimiter.
When I am trying to execute SQL commands on Snowflake (6 commands) by using "Execute script" I see the error:
SQL Error [8] [0A000]: Actual statement count 6 did not match the desired statement count 1.
Actual statement count 6 did not match the desired statement count 1.,
Also when I am trying to execute 1 SQL command by using "Execute SQL Statement" from the place of cursor then I see the same error.
Looks like DBeaver does not see my delimiters.
Before updating to the newest version (<IP_ADDRESS>301060755) everything was working fine.
DBeaver Version
<IP_ADDRESS>301060755
Operating System
Windows 10
Database and driver
Snowflake + snowflake_jdbc
Steps to reproduce
No response
Additional context
No response

Hello @TomaszSroka,
Can you please provide a sample of the script you're trying to execute?

Sure,
Script:
DROP TABLE IF EXISTS MART_FLSEDW_CI.DEPLOYMENT_SCRIPTS;
CREATE TABLE IF NOT EXISTS MART_FLSEDW_CI.DEPLOYMENT_SCRIPTS
(
DEPLOYMENT_SCRIPTS_ID INTEGER IDENTITY(1,1) NOT NULL
, MODEL VARCHAR NOT NULL
, TYPE VARCHAR NOT NULL
, EXECUTION_DATE TIMESTAMP_LTZ NOT NULL DEFAULT CURRENT_TIMESTAMP
, SCRIPT VARCHAR NOT NULL
, HASHDIFF BINARY(16)
);
INSERT INTO MART_FLSEDW_CI.DEPLOYMENT_SCRIPTS (DEPLOYMENT_SCRIPTS_ID,
MODEL, "TYPE", EXECUTION_DATE, SCRIPT, HASHDIFF)
SELECT
DEPLOYMENT_SCRIPTS_ID
, DEPLOYMENT_MODEL AS MODEL
, 'OneTime' AS "TYPE"
, EXECUTION_DATE AS EXECUTION_DATE
, DEPLOYMENT_SCRIPT AS SCRIPT
, NULL AS HASHDIFF
FROM MART_FLSEDW_CI.DEPLOYMENT_SCRIPTS_BKP;
And the way how I am executing it:
[image: obraz.png]
I didn't have a problem with it in the past.
czw., 12 sty 2023 o 14:36 ShadelessFox @.***>
napisał(a):

Hello @TomaszSroka https://github.com/TomaszSroka,
Can you please provide a sample of the script you're trying to execute?
—
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/18750#issuecomment-1380367919,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMOSRCOXMKJRLGTDHRQIYY3WSACHLANCNFSM6AAAAAATZE4AIY
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Z poważaniem,
Tomasz Sroka

What statement delimiter is set in the preferences?

I think that it is default:

Wow, when I clicked "Restore Defaults" nothing were changed, but it is working now :).

Well, glad it helped! Since the issue was solved, I will close the ticket.

hmm, but it is working only in one case. And in another not.

It is working for DML and not working for DDL operations.

Are you using the same script shown before?

Yes
czw., 12 sty 2023, 15:50 użytkownik ShadelessFox @.***>
napisał:

Are you using the same script shown before?
—
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/18750#issuecomment-1380480981,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMOSRCJHKMDFEBBKXHS4NB3WSAK3HANCNFSM6AAAAAATZE4AIY
.
You are receiving this because you were mentioned.Message ID:
@.***>

This is happening to me too- something about the newer verison. Was working before...

Thank you for bug report. I reproduced it.

Could you please estimate when the fix will be ready?

I hope it will be fixed in the next release. The fix has been done in scope of #18787.

You could try early access version https://dbeaver.io/files/ea/ or wait for DBeaver 22.3.3 release.
Please let me know if your issue has been solved.

This error is not occurring anymore in the newest version.


Avoid shell out tar for genesis archive creation

Problem
Spawning a subprocess to utilize tar incurs some overhead. Moreso, it introduces some variability based on what version of tar the caller happens to have available in PATH
Summary of Changes
Use the tar crate instead of invoking tar in a subprocess.
Fixes #

I believe this change is the right thing to do regardless. However, the motivation for looking at this was that many people had reported issues running solana-test-validator, seemingly related to variation on what version of tar is available (per https://github.com/solana-labs/solana/issues/34625).
I was unable to reproduce the issue running solana-test-validator locally, with both v1.18 and v2.0 versions. My local setup:
$ sysctl -a | grep machdep.cpu.brand_string
machdep.cpu.brand_string: Apple M3 Max

$ sw_vers
ProductName:		macOS
ProductVersion:		14.6.1
BuildVersion:		23G93

$ tar --help | head -n 1
tar(bsdtar): manipulate archive files

It seems that I'm not the only one who was unable to reproduce, such as https://github.com/anza-xyz/agave/issues/2838#issuecomment-2331086031. I'm probably going to try to track someone down who was able to reproduce so I can validate that the test validator issue is resolved with this change

I can reproduce:
➜  rocket sysctl -a | grep machdep.cpu.brand_string

machdep.cpu.brand_string: Apple M1 Pro
➜  rocket sw_vers
ProductName:		macOS
ProductVersion:		15.0
BuildVersion:		24A335
➜  rocket tar --help | head -n 1
tar(bsdtar): manipulate archive files
➜  rocket
➜  rocket solana-test-validator

Notice! No wallet available. `solana airdrop` localnet SOL after creating one

Ledger location: test-ledger
Log: test-ledger/validator.log
Error: failed to start validator: Failed to create ledger at test-ledger: io error: Error checking to unpack genesis archive: Archive error: extra entry found: "._genesis.bin" Regular
➜  rocket rm -rf test-ledger
➜  rocket solana-test-validator

Notice! No wallet available. `solana airdrop` localnet SOL after creating one

Ledger location: test-ledger
Log: test-ledger/validator.log
Error: failed to start validator: Failed to create ledger at test-ledger: io error: Error checking to unpack genesis archive: Archive error: extra entry found: "._genesis.bin" Regular

Thanks for trying this out @ferric-sol ! I am a bit confused as well as to what we would have changed between v1.18.25 and the tip of master. Per our DM's, it sounds like you are willing to git bisect this one. If so, thank you very much and lemme know when you're able to get to it / how it goes

After digging around, https://github.com/solana-labs/solana/pull/35213 looked like a probable culprit for change in behavior; @ferric-sol did the git bisect and confirmed this to be the case. This change was pushed to master after v1.18 was cut; the reports I have seen of the issue have been with <= v1.18.
It is still a mystery to me as to why the issue would show on an M1, but not my M3. In any case, the issue goes away when we do NOT shell out, so this change is still good to go

Oops, never hit enter to send my response

Code looks good. Are there tests for genesis archive creation? Or iow, how was this change tested?

The function create_new_ledger() unpacks the archive; however, it doesn't check the actual contents of what was unpacked. The multinode demos exercise this by way of having additional validators download and unpack genesis.tar.bz2; if the additional nodes were unable to reconstruct proper genesis, those tests would fail.
That being said, I extended an existing unit test to simply read both genesis.bin and genesis.tar.bz2 and compare to the genesis config we used to create ledger. That is done with https://github.com/anza-xyz/agave/pull/3079/commits/0f22dacdde112de78213f4cedab19952682a511e


Import Error

From the screenshot below
Setting 'allowSyntheticDefaultImports' flag to be true in tsconfig.json resolevd the problem and the module can be loaded successfully

Seems to be related to a library called flatbush or might it be other problems?
Also, I must specify import SnapFeatures from<EMAIL_ADDRESS>in order to import the module which is different from all "normal" modules.

Thanks a lot

Part of the issue here is that I didn't understand JS bundling or TS super well two years ago.

Also, I must specify import SnapFeatures from<EMAIL_ADDRESS>in order to import the module which is different from all "normal" modules.

One issue is that the NPM package inadvertently wasn't including the dist/ or lib/ folders. So you should I think now be able to import the package normally with 0.2.1 that I just published. Or I'd assume you could import the index.ts as you do above without any issues if you're working in a TS project.
I haven't seen the error about allowSyntheticDefaultImports before. If it still happens with 0.2.1 you can make a PR to update this project's tsconfig

The error is solved, I can import the library normally.
Thank you very much.


Delay when opening the first page for the first time

Vite Plugin Version
v1.0.1
Laravel Version
v10.24.0
Node Version
v21.5.0
NPM Version
10.2.4
Operating System
Windows (WSL)
OS Version
11
Web browser and version
Google Chrome Version 120.0.6099.227 (Official build) 64 bits
Running in Sail?
No
Description
I develop using Laravel which runs on Docker, but runs Vite outside of Docker, what is happening is that, when opening the website for the first time (any page), there is a huge delay (up to 10 minutes) for me to receive the assets from the "yarn dev" server. This is getting worse every day, because I've always done it this way but now I practically have to run "yarn dev" and go out and do something. Remembering that the Vite server runs quickly. The project is not big, it has around 50 assets (JS, CSS and images)
Some images to demonstrate what I'm talking about
Time to start Vite

Time for Vite to respond to requests in the browser

It's not just SASS that is slow, all images and javascripts are slow
Steps To Reproduce
I don't know what is causing the slowdown, so I don't yet know how to replicate the problem

Hi there. While I understand that this is annoying for you I do consider this an edge case at best. I recommend to not run Vite outside of Docker and to run it alongside the same image as your Laravel app. Something like Sail can help you with that.
If you still want to go ahead and figure out why this is running slow for you I recommend a support channel:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Vite runs outside of Docker, both vendor and node_modules are outside too


We need a license

So our code can be officially open source. Also so nobody hooks up the kiwidrive code to their nuclear reactor and then sues us when things go to pot..
pyfrc is MIT (this seems popular for javascript and python libraries)
robotpy-wpilib is 3-clause BSD (because wpilib is BSD)
or we could do GPL.

I vote MIT.

I vote MIT

MIT is fine with me.

Do you want to do that for all of our stuff Ellery?
Pass the job to Caleb if you're too busy.

I vote AGPLv3 (list of some projects that use it). If we're going to be putting this on all our stuff, it'll be nice to have work on the future WPILib on JS come back into the community. It would help with growth (meaning more people to find bugs and suggest features :)). My issue with MIT or 3-clause BSD is that people can take our code or libraries and modify them without ever giving back to the community. While that may seem good short term, in the long term having a license like the GPL would encourage continued development by the nature of how changes used in competition (over a network, the FMS) would have to be accessible in some way. This keeps the code up to date and avoids stagnation, even if the original devs (us) drift away from it—as long as someone's using it, it's good. Commercial use shouldn't be a problem, as all of this is being used with robots in a community-focused program, anyway. If any of our future projects under Retrobotics have a good chance of being used commercially and we're worried about that, we can decide then and there. (We might even be able to dual license for commercial use and get that revenue feeding to the club, but that's pretty far down the road right now.) (Also, WPILib's 3-clause BSD license is compatible with the v3 GPLs, so that's not an issue.)

I personally think github's infrastructure has done more to keep software projects alive than the GPL has.
Our robot code doesn't have a >1 year lifespan, and it is unlikely to be useful in a commercial context.
The only relevant case I can think of is another team using our code and not disclosing their changes, but even that is unlikely since that code is fairly dependent on our custom hardware.

Although, if you want to build that battery charger idea and sell it to other teams, I'm in.

Ellery, will you help with porting wpilib to nodejs?
I think there is potential for great glory there....

@ariovistus commented on Apr 9, 2015, 2:38 PM PDT:

I personally think github's infrastructure has done more to keep software projects alive than the GPL has.

That's debatable, as GNU & GPL have been around a fair bit longer than GitHub and social coding sites in general, but that is its own debate and not too relevant right now.
@ariovistus commented on Apr 9, 2015, 2:38 PM PDT:

Our robot code doesn't have a >1 year lifespan, and it is unlikely to be useful in a commercial context.
The only relevant case I can think of is another team using our code and not disclosing their changes, but even that is unlikely since that code is fairly dependent on our custom hardware.

I was thinking more for all our Retrobotics projects—you're right, this robot code probably wouldn't be that widely used. However, a port of WPILib to JS or GObject or anything else would probably end up being used a lot by other teams. That's where I really want to make sure the proper care is being put, and I think a GPL would do better long-term.
@aebooth commented on Apr 9, 2015, 2:43 PM PDT:

Ellery, will you help with porting wpilib to nodejs?
I think there is potential for great glory there....

I've been thinking about how to do that, and what about a port to GObject? It binds to other languages pretty easily and porting to Vala probably would be less of a pain.

I think anything after node is gravy--I just think that js is important because it is becoming so universal.
Plus node add-ons lend themselves nicely to this kind of project.

I agree with the importance of a JS port, but I think porting to Vala and binding out from there to JS instead of through addons would be a lot easier to implement. Plus, we get other languages for free along with JS. The less we have to think about, the easier this will be.

I don't like the idea of a port. It puts the burden of upstream patches on you to translate and merge in. It puts the burden of QA on you - duplicated effort if the original already does it (I don't know what the wpilib folks do though). That said, it's what the robotpy people did, but then they seem more motivated than I am..
Vala is interesting but risky.  Maybe that's why robotpy went to a pure python implementation.. Do you know of any vala projects that are distributed over npm?
Having never used either, is GObject a better option than a SWIG wrapper around c++ wpilib?

Anyways, the answer is no unless and until someone buys me a roborio and makes a power cord that plugs it into a regular wall outlet. That would be wizard.

@ariovistus commented on Apr 9, 2015, 5:52 PM PDT:

Vala is interesting but risky.  Maybe that's why robotpy went to a pure python implementation.. Do you know of any vala projects that are distributed over npm?
Having never used either, is GObject a better option than a SWIG wrapper around c++ wpilib?

I'd tend toward Vala because if we use SWIG we're going to have to be making manual adjustments anyhow with SWIG and there are a couple of semi-minor changes I want to make along the way, like what RobotPy did with the lambdas for PIDController. We also get ValaDoc for nice documentation, something SWIG doesn't have an equivalent to. It's pretty simple to get JS running with a GObject lib (see here, the first bits with building wouldn't even be needed unless someone was modifying WPILib, rather like RobotPy when they were on SIP. Even then, changes with WPILib would just be a matter of recompiling to C and using the cross-compiler on those, along with generating the bindings. That could all be automated in a makefile/script/something).

Not to say I don't have the time, but I am lazy.
Let's use MIT for this project, and have it be our default choice unless there is a compelling reason to use something else.

@bb010g building vala code is the easy part. I'd be more worried about whether we can get node build for the roborio. Also, what about multithreading? At least PIDController uses it, and nodejs doesn't have it.
Or it does, but doesn't expose it to javascript code. point to vala, I guess.

I would look into what gjs has for multithreading too. It's like node.js, but on Spidermonkey instead of V8 (their performance is pretty dang close, so that isn't an issue) and natively supports GObject Introspection. I'm pretty sure they both have ARM binaries; I'll check when I get off mobile.

Do we really need multithreading?

Seeing as how real-time programs are all centered around a giant event loop anyway, I thought nodejs would be a natural choice since it follows the same idiom.

I think going outside of c++ to accommodate something like GObject might be extra work where we're wandering around in a number of languages and codebases.  Node add-ons are supposedly dead easy to write, and straightforward.  If that is the case, then after deciding how we are going to organize everything, we just have to write a c++ addon for each c++ class (same language, all well documented).  I imagine if we put our heads together, we could even write an addon generator in python, haskell, etc. that takes header files and makes v8 JS object classes and headers which need only minor tweaking.

The other thing is that node add-ons are just c++ code that makes v8 objects, so in the node model, we get everything c++ wpilib can do for free--multithreading included.

I would assume wpilib has its own event loop; I wonder if node's event loop is even suitable. Seems like you'd need a way to terminate a js script if it blocks for too long for physical safety concerns.

Part of my point is we could use the wpilib event loop because v8 (where you build node add-ons) is just a c++ library.

all right, so a viable game plan would be to embed v8 in a c++ project that loads and runs javascript code in the event loop. Its worth a try.

That's what I'm saying.
Then, if we follow some organizational conventions, we can take advantage of the nodejs infrastructure/package management system as well.

You guys will want to check out tutorials on nodejs add-ons and the events module.

FYI we now have an Open Source license for Confluence, Confluence Questions, and Confluence Calendar at https://retro3223.atlassian.net


Add support for BPF_PROG_TYPE_SOCK_OPS

References:

https://lwn.net/Articles/727189/
https://blogs.oracle.com/linux/post/bpf-a-tour-of-program-types

Closing this as this prog_type and corresponding attach type and helper is discussed in more detail in #786 .


Error while closing the tab

Problems summary
I am getting this error while closing a tab.
E784: Cannot close last tab page
Environment Information

OS: Mac os 10.13

neovim :version output:
NVIM v0.4.0-1021-gdd21cd2a4
Build type: Release
LuaJIT 2.0.5

:checkhealth or :CheckHealth result(neovim only):
OK

How to reproduce the problem from neovim startup (Required!)

Open the a tab or more tab then select one of them.
Try to close with  + tc
See the error out put.

Screenshot (if possible)

Please try C-x

That works but we should update the document then.

@emeentag  because set hidden  will  cause the tabclose didnt work. should remove the tabclose


OpenCL registration method not available

I tried to run kinect2 in ubuntu 14.04 and got the following error.
jihoonl@whoola:~/research/ros/freenect2/devel$ rosrun kinect2_bridge kinect2_bridge
^[[A[DepthRegistration::New] OpenCL registration method not available!
[DepthRegistration::New] OpenCL registration method not available!
[OpenGLContext] failed to initialize glew for the current context!
Segmentation fault (core dumped)

That is because libfreenect2 does not initialize glfw. I added a fix for this in the devel branch.

I see thanks.

Hi @wiedemeyer,
Could you please point out which commit fixed this issue? I tried but couldn't find it.


Some typo fixes

Found some typos while I was reading the paper and took the liberty of fixing them. These are all small spelling or grammar corrections.

Thanks @arcalinea for catching and fixing these typos 👍 . And thanks @domi41 for highlighting them some of them too!


Pulled and merged.


Add missing stops

Following stops after Hemp tree and before Italian cypress:

Chinese tallow tree
California white oak
Monterey cypress
Crape myrtle
California live oak
Foothill pine

See spreadsheet: https://docs.google.com/spreadsheets/d/1s8GtXKEdwAt4b4bxgf3uJJ4E3mC7PW5CnBU88yKW6F4/edit#gid=0


[WIP]Add pip support for licensed

This is an initial take on adding pip package support for licensed.
The idea as a start is to shell out to pip and gather all the information on installed packages.  We also expect a requirements.txt that contains all the packages that the current project depends on and could use that to generate the package list and look for the respective license files in the location provided.
Alternatively pypi does have an API that we could use to gather license and other metadata for a package in requirements.txt but does not have the location of where the files are installed locally (which we'll need to gather the license files itself).

Testing this on a simple python flask app:
root@9e7587f53f1b:/licensed/workspace# licensed list
Displaying dependencies for my_app
  pip dependencies:
    Found Flask (0.12.1)
    Found Flask-Migrate (2.0.3)
    Found Flask-SQLAlchemy (2.2)
    Found Flask-Script (2.0.5)
    Found Jinja2 (2.9.6)
    Found Mako (1.0.6)
    Found MarkupSafe (1.0)
    Found SQLAlchemy (1.1.9)
    Found Werkzeug (0.12.1)
    Found alembic (0.9.1)
    Found click (6.7)
    Found google-api-python-client (1.6.2)
    Found gunicorn (19.7.1)
    Found httplib2 (0.10.3)
    Found itsdangerous (0.24)
    Found oauth2client (4.0.0)
    Found psycopg2 (2.7.1)
    Found pyasn1 (0.2.3)
    Found pyasn1-modules (0.0.8)
    Found python-dateutil (2.6.0)
    Found python-editor (1.0.3)
    Found rsa (3.4.2)
    Found six (1.10.0)
    Found uritemplate (3.0.0)
  * pip dependencies: 24

licensed status
Checking licenses for my_app: 24 dependencies
FFFFFFFFFFFFFFF.FF.FFFFF

@jonabc yeah there's where I'm planning on going next .


Tues cli test

Revised pr after code review with Scott

Hate PR/Merge some broke code, but trying to get everything on same master.


telemetry: fix labels not being included

Backfill integration test for labels being sent to Cloud
Store collected labels on Client and include them in every ClientMetadata

LGTM! left a small nit comment.


Call to function "list" in ../../modules/gke-cluster/main.tf failed

I was trying out the example in .../networking/hub-and-spoke-peering using Terraform (v0.15.3) from within Cloud Shell.
The plan command returned the following error:
Error: Error in function call
│
│   on ../../modules/gke-cluster/main.tf line 105, in resource "google_container_cluster" "cluster":
│  105:     for_each = length(var.master_authorized_ranges) == 0 ? [] : list(var.master_authorized_ranges)
│     ├────────────────
│     │ var.master_authorized_ranges is map of string with 3 elements
│
│ Call to function "list" failed: the "list" function was deprecated in Terraform v0.12 and is no longer available; use tolist([ ... ]) syntax to write a literal list.

Going by the last line in the error message, it appears that the error occurred because I'm using a version that's higher than 0.12.  But, interestingly, the same example worked fine when I tested from an off-cloud host that has Terraform v0.14.11.

We haven't yet verified and aligned code for terraform 0.15...
On Fri, May 21, 2021, 19:05 Kumar Dhanagopal @.***>
wrote:

I was trying out the example in .../networking/hub-and-spoke-peering
using Terraform (v0.15.3) from within Cloud Shell.
The plan command returned the following error:
Error: Error in function call
│
│   on ../../modules/gke-cluster/main.tf line 105, in resource "google_container_cluster" "cluster":
│  105:     for_each = length(var.master_authorized_ranges) == 0 ? [] : list(var.master_authorized_ranges)
│     ├────────────────
│     │ var.master_authorized_ranges is map of string with 3 elements
│
│ Call to function "list" failed: the "list" function was deprecated in Terraform v0.12 and is no longer available; use tolist([ ... ]) syntax to write a literal list.
Going by the last line in the error message, it appears that the error
occurred because I'm using a version that's higher than 0.12. But,
interestingly, the same example worked fine when I tested from an
off-cloud host that has Terraform v0.14.11.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/terraform-google-modules/cloud-foundation-fabric/issues/247,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAQDV7DS4HA56WZACA4RNLTO2HFBANCNFSM45JQWGNA
.

@kumar-dhanagopal can you try replacing the list with tolist()?

Yes, @rosmo . I was able to create an execution plan and apply it after changing list() to tolist([...]).

Thanks Taneli for the quick fix!


com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource linking failed

What went wrong:

Execution failed for task ':path_provider:verifyReleaseResources'.

1 exception was raised by workers:

com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource linking failed
C:\Users\Tejaswini\Desktop\fph_user\build\path_provider\intermediates\res\merged\release\values\values.xml:171: error: resource android:attr/fontVariationSettings not found.
C:\Users\Tejaswini\Desktop\fph_user\build\path_provider\intermediates\res\merged\release\values\values.xml:172: error: resource android:attr/ttcIndex not found.
error: failed linking references.
this is the error am facing after i updated to newest version of flutter
there were two more errors which go solved after degrading the gradle version

Hi @tejz1607
Which version are you using?
Please default  classpath 'com.android.tools.build:gradle:3.5.0'
if the problem persist, can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you


Add design documentation

Signed-off-by: Frank A. Zdarsky<EMAIL_ADDRESS>

@fzdarsky - thanks for this, my initial observation is I think it would be beneficial to have a use case/user story section as well.

@fzdarsky - thanks for this, my initial observation is I think it would be beneficial to have a use case/user story section as well.

That's a good idea @screeley44. I'll add those in a follow-up PR.

@mangelajo please review %)

/lgtm


Unable to install (Error 0x80070643: Failed to install MSI package.)

Microsoft PowerToys version
0.62.1 & 0.63.0 & 0.64.0
Running as admin

[X] Yes

Area(s) with issue?
Installer
Steps to reproduce

The old version got uninstalled, since I was not able to upgrade (same error).
Trying to freshly install PowerToys via PowerToysSetup-0.62.1-x64.exe (downloaded from https://github.com/microsoft/PowerToys/releases/tag/v0.62.1).
At the following screen, the setup fails:

This is the “error message” that pops up:

If I click OK, the following popup appears:

So I need to click cancel, which finally results in this popup:

And this is the final error:

Logfile: powertoys-bootstrapper-msi-0.62.1_20220926181116.log

✔ Expected Behavior

Installation should be successful.

❌ Actual Behavior

Installation not possible.

Other Software
No response

I still get the same issue with PowerToysSetup-0.63.0-x64.exe.

And still the same issue with PowerToysSetup-0.64.0-x64.exe.
→ Even in 0.64.0, the file it is looking for is called PowerToysSetup-0.61.1-x64.msi, just in case someone will ever read this.

Alright, I found a solution: I basically went ahead and deleted everything containing “PowerToys” from the registry. Yeah, might have been dangerous, however, after doing so, the installation works like a charm.

Hi Fabian, I just encountered the same issue, what files did you exactly delete?

Hi Fabian, I just encountered the same issue, what files did you exactly delete?

I uninstalled PowerToys completely, but used a third-party tool for it (in my case, IObit Uninstaller). That cleans leftovers of uninstalls from the registry. That did the trick, if I remember right.
(However, please don't do it if you don't know what you're doing. I had backups and all that.)

oh perfect! Thank you very much, it seems like it helped


Consistency issue in lime image explanation

Every time I run explanation.get_image_and_mask, I get different regions of the image highlighted as green and red. I keep all the parameters even after providing same seed value in explainer.explain_instance  .
Some of the results are as under.
Run_1:

Run_2:

Run_3:

I used the following parameters for the above explanation.
%%time
# Hide color is the color for a superpixel turned OFF. Alternatively, if it is NONE, the superpixel will be replaced by the average of its pixels
explanation = explainer.explain_instance(X_train_0, new_predict_fn, top_labels=2, hide_color=0, num_samples=10, random_seed=10)

temp, mask = explanation.get_image_and_mask(explanation.top_labels[0], positive_only=False, num_features=10, hide_rest=False)
plt.imshow(mark_boundaries(temp / 2 + 0.5, mask))

The random_seed only impacts the segmentation (this is a bug in documentation I guess). If you want to get the same explanation again and again, you need to restart the explainer and set random_state, or do it by hand.


Feature Add support of ProjectNode in PlanTranslator

Proposed changes
Issue Number: no issue
Problem Summary:
Since we will do the column prune with project node, so we need compact the project outputs to the PlanNode in PhysicalPlanTranslator::visitPhysicalProject
Checklist(Required)

Does it affect the original behavior: (No)
Has unit tests been added: (No)
Has document been added or modified: (No)
Does it need to update dependencies: (No)
Are there any changes that cannot be rolled back: (No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

i suggest collect all plan translator's file into a new sub package under nereids for reading easily

done


feature: Python 3.11 support

Feature scope
Other
Description
Python 3.11.0 is planned to be officially released as of 2022-10-24. We should add it to our test matrix, and build Docker images for it for each release.

Is there an ETA for when 3.11 support will be added? I'm also interested in meltano/meltano Docker images with Python 3.11.


Is there a way to deliver additional props with the render/component props?

Our org is looking at Formik to replace redux-form.  Some of our forms are fairly complex, and rely on some redux store states to enable/disable or display/hide certain elements within a form.  Is there a way (or what is the "official" pattern) to accomplish this in Formik - that is to pass these additional objects down into the Formik component?
Thanks.

Where did this logic live before? Within the redux-form hoc?

<Formik/>
I know that lots of ppl from Redux-land love the HoC approach. However, the  component is actually more powerful because you have full access to React state, props, and lifecycle methods directly. It's just plain React!
<Formik
    initialValues={...}
    validate={...}
    onSubmit={ ... }
    render={formikProps =>
       <Component  {...formikProps} {...whatever you need} />
    }
/>

HoC
if you are using redux:

export default connect({...})(withFormik({ .. })(Comp))

// or with recompose

export default compose (
   connect({ ... })
   withFormik({ ... })
)(Component)

Also FYI, withFormik() is calls<Formik render /> under the hood anyways. 😎

Nice! The first code block i what I was looking for. Thanks so much :D

Thanks for responding so quickly, @jaredpalmer!

Can't you guys write a good easy code for demonstrating something as an example because there are many users who are beginners..

Hi!
Sorry, but I don't get how to connect Formik with the following Container, and what should I do with the handleSubmit method inside mapDispatchToProps?
The Container:
import { connect } from 'react-redux';
import { loginRequest } from '../redux/actions';
import SignInForm from './SignInForm.component';

const mapDispatchToProps = dispatch => {
  const handleClickShowPassword = () => {
    this.setState({ showPassword: !this.state.showPassword });
  }

  const handleSubmit = e => {
    e.preventDefault();

    const payload = {
      username<EMAIL_ADDRESS>// this.state.username,
      password: 'EasyToGuess$135', // this.state.password,
    }

    try {
      dispatch(loginRequest(payload));
    } catch (err) {
      // TODO - Replace with a react logger or with a direct message to the user.
      console.error('===> Singin - handleSubmit - err', err);
    }
  };

  return {
    handleClickShowPassword,
    handleSubmit,
  }
};

const mapStateToProps = state => {
  const { isLoading } = state.user;
  const showPassword = false;

  return {
    isLoading,
    showPassword,
  }
};

export default connect(mapStateToProps, mapDispatchToProps)(SignInForm);

the presentational component:
import React from 'react';
import PropTypes from 'prop-types';
import classNames from 'classnames';
import { withStyles } from '@material-ui/core/styles';
import Button from '@material-ui/core/Button';
import IconButton from '@material-ui/core/IconButton';
import Input from '@material-ui/core/Input';
import InputLabel from '@material-ui/core/InputLabel';
import InputAdornment from '@material-ui/core/InputAdornment';
import FormControl from '@material-ui/core/FormControl';
import TextField from '@material-ui/core/TextField';
import Visibility from '@material-ui/icons/Visibility';
import VisibilityOff from '@material-ui/icons/VisibilityOff';

const styles = theme => ({
  root: {
    display: 'flex',
    flexWrap: 'wrap',
  },
  margin: {
    margin: theme.spacing.unit,
  },
  withoutLabel: {
    marginTop: theme.spacing.unit * 3,
  },
  textField: {
    flexBasis: 200,
  },
});

const SignInForm = ({
  classes,
  handleClickShowPassword,
  handleSubmit,
  isLoading,
  showPassword,
}) => {
  if (isLoading) return null;

  return(
    <form
      noValidate
      autoComplete="off"
      onSubmit={(e) => { handleSubmit(e) } }
    >
      <TextField
        id="username"
        label="Username"
        margin="normal"
      />
      <FormControl className={classNames(classes.margin, classes.textField)}>
        <InputLabel htmlFor="password">Password</InputLabel>
        <Input
          id="password"
          type={showPassword ? 'text' : 'password'}
          endAdornment={
            <InputAdornment position="end">
              <IconButton
                onClick={handleClickShowPassword}
              >
                {showPassword ? <VisibilityOff /> : <Visibility />}
              </IconButton>
            </InputAdornment>
          }
        />
      </FormControl>
      <Button
        variant="contained"
        color="primary"
        type="submit"
        label="Submit"
        className={classes.button}
      >
        Login
      </Button>
    </form>
  );
};

SignInForm.propTypes = {
  classes: PropTypes.object.isRequired,
  handleClickShowPassword: PropTypes.func.isRequired,
  handleSubmit: PropTypes.func.isRequired,
  isLoading: PropTypes.bool.isRequired,
  showPassword: PropTypes.bool.isRequired,
};

export default withStyles(styles)(SignInForm);

Thank you!

As a beginner to Formik, I took to HoC approach purely because it was the number one approach listed on home docs. Perhaps we can swap that around and make using render number one? :)

where do i import compose from?

@marth00165 if you're looking for recompose documentation, I'd check out https://github.com/acdlite/recompose

@marth00165, we were using https://ramdajs.com/docs/#compose.

I am passing prop from one component to its child component and in my child component I want to use withFormik() hook. How can I get the values sent by my parent component in child component?

I am passing prop from one component to its child component and in my child component I want to use withFormik() hook. How can I get the values sent by my parent component in child component?

const MyComponent = props => {
function handleSubmit(values, { setSubmitting }) {
// handle
}
return (
    <CreateForm handleSubmit={ handleSubmit }/>
)

}
const CreateForm = props => {
const { handleSubmit } = props;
const MyFormWithFormik = withFormik({
    // ...,
    handleSubmit: handleSubmit,
})(MyForm);

return <MyFormWithFormik/>

}

Formik render prop has been deprecated and will be removed in future versions of Formik.
Deprecated:
<Formik
  initialValues={{ foo: 'bar' }}
  onSubmit={() => console.log('submit')}
  render={(formikProps) => <NewComponent {...props} {...formikProps} />}
/>

New way:
Now, to pass props to the child component, use a child callback function instead like this:
<Formik
  initialValues={{ foo: 'bar' }}
  onSubmit={() => console.log('submit')}
>
    {(formikProps) => <NewComponent {...props} {...formikProps} />}
</Formik>

Formik render prop has been deprecated and will be removed in future versions of Formik.
Deprecated:
<Formik
  initialValues={{ foo: 'bar' }}
  onSubmit={() => console.log('submit')}
  render={(formikProps) => <NewComponent {...props} {...formikProps} />}
/>

New way:
Now, to pass props to the child component, use a child callback function instead like this:
<Formik
  initialValues={{ foo: 'bar' }}
  onSubmit={() => console.log('submit')}
>
    {(formikProps) => <NewComponent {...props} {...formikProps} />}
</Formik>


[Feature Request] Dragging two perpendicular splitters at the same time

Describe the solution you'd like
VSCode does a thing with its splitters, where it allows dragging both focused splitters at the same time, if they're perpendicular to each other

There's actually a PR for this: #155
We just haven't worked on it much in a while.


SortableTable: Only use a single timer for live updates and pause on scroll

This PR changes the way that the LiveDate column works (and provides a mechanism we can use for all Live columns).
Currently, when there are 100 rows in a page on a sortable table with the Age column, we create a timer for every age field.
On some older browsers (Edge 91, for example), this makes it impossible to use the scroll bar to scroll through the list.
This PR makes 4 changes:

Provides a mechanism where the SortableTable will use a single timer to update all live columns in the table
Updates the LiveDate component to use this mechanism
Updates SortableTable so that we pause live updating when the user is scrolling the page
Slightly improves the performance of the LiveDate component

These updates may help with general page performance with large lists.

This will be replaced by: https://github.com/rancher/dashboard/pull/5435


Refactoring docs to support docsify

Issues resolved
Docisfy deployed version:
English: https://sshniro.github.io/apisix-docsify/#/
CN: https://sshniro.github.io/apisix-docsify/#/zh-cn/
The PR does not modify the content of the docs. This will be done in the subsequent PRs.

nice PR

This is a list of plugins we can support:
https://docsify.js.org/#/plugins

Full-text search
Google analytics
Copy-code

@sshniro you can update your repo first ^_^. https://github.com/sshniro/apisix-docsify

@sshniro you can update your repo first ^_^. https://github.com/sshniro/apisix-docsify

Aw, forgot to update.
https://sshniro.github.io/apisix-docsify/#/README
https://sshniro.github.io/apisix-docsify/#/zh-cn/
Now it's similar to the current PR.

it is 404 now:

Hi @membphis The reference to the language change should be removed for the main content. The language is switchable via this tab:

I did not remove the Chinese doc and wanted to remove it in the subsequent PR to easily track changes. And also the Introduction page will be fully rewritten as the current one simply lists the docs, which is already visible in the nav bar,

@sshniro

@membphis using absolute path will result in an error.

@membphis absolute path results in an error:

this is great work @sshniro

absolute path results in an error

many thanks your reply

Shall we merge this, so I can move forward with the content refactoring?
Also, where are we going to host this? In Github pages? If so we need to change the folder name from doc to docs

merged already. you can continue your job now @sshniro


Would be nice if probe unloading was faster

Thank you so much for writing this awesome tool, it has made learning, using, and debugging the Linux network stack not just so much easier, but feasible at all for me. I used to have so much trouble figuring out why something wasn't working. (Significant kudos to kernel devs as well for enabling this with probing functionality.)
Is there any way to make attaching and detaching probes faster? Detaching probes seems to go a few times slower than attaching for me.
I guess maybe https://github.com/cilium/pwru/pull/99 isn't implemented for unloading?

Thanks for the issue (and feedback)!
Could you provide the following?

Which kernel (uname -a)
Params for pwru
The first log lines before Listening for events

Why not attaching/detaching kprobes concurrently?
It seems better to attach/detach kprobes concurrently.
./pwru --backend kprobe --output-meta --output-tuple icmp
2023/10/23 13:01:12 Attaching kprobes (via kprobe)...
1462 / 1462 [----------------------------------------------------------------------------------------------------] 100.00% 347 p/s
2023/10/23 13:01:17 Attached (ignored 0)
2023/10/23 13:01:17 Listening for events..
               SKB    CPU          PROCESS                     FUNC
^C2023/10/23 13:01:19 Received signal, exiting program..
2023/10/23 13:01:19 Detaching kprobes...
215 / 1462 [--------------->_______________________________________________________________________________________] 14.71% 35 p/s

P.S. it seems something wrong with the progressbar.

Cool!
I haven't tested, but it looks like detach is still an order of magnitude (p/s) slower? (This is not significant for my usecase.)

I think we could detach in batches too.

It does detach in batches: DetachKprobes()

Oops, my bad.


passwords for users created via graph is stored unhashed in idm

Describe the bug
Currently the user passwords for users created via graph are stored in cleartext in libregraph/idm (for other LDAP implementation this depends a bit on the specific configuration). We could either:

add (LDAP) client side hashing, this would mean we need know about the hashes supported on the client side
rely on server side hashing (teach IDM to hash passwords), and e.g. use the LDAP Modifiy Password extension when talking to servers that support it.

Note: the userpassword for the user admin and all service users are already hashed.

@micbar, IMO this should have a higher priority.

rely on server side hashing (teach IDM to hash passwords)
I think this would be the clean solution. Where would we add the hashing? To the ldapserver or to the handlers (boltdb, etc...)?
@rhafer

rely on server side hashing (teach IDM to hash passwords)

I think this would be the clean solution. Where would we add the hashing? To the ldapserver or to the handlers (boltdb, etc...)? @rhafer

If it just where about idm I would lean towards adding it to the ldapserver at the top-level (i.e. https://github.com/libregraph/idm/blob/master/pkg/ldapserver/add.go#L12 and https://github.com/libregraph/idm/blob/master/pkg/ldapserver/modify.go#L13)
It's more difficult however as we also want to support external LDAP servers. OpenLDAP e.g. does not hash the password when add or modified via the standard LDAP operations (mainly to stay compatible with the LDAP RFC). For OpenLDAP it would makes sense set the password via the LDAP Password Modify Extended Operation sigh. Other LDAP servers (e.g. 389DS) do hash the password received via ADD/MODIFY requests though.
The most compatible approach might be to add LDAP Password Modify Extended Operation to idm and always use that operation to set passwords. I haven't checked how hard this is yet. But I think it shouldn't be too much work (famous last words ...)

Yes, this makes sense. I can take a look into that next week.

Oh. I already started some ground work on that. (Sorry, I saw this a bit too late. Didn't want to step on your toes). See https://github.com/rhafer/idm/tree/pwexop
If you want we can pair on this on monday.


ci: refactor example-basic

Change
The workflow .github/workflows/example-basic.yml is refactored as follows:

The workflow is converted to use a matrix of operating systems for clarity
latest operating systems are pinned to concrete versions for stability:

windows-latest changed to windows-2022 (Windows Server 2022)
macos-latest changed to macos-14 (macOS 14 Arm64)

This is in preparation for adding ubuntu-24.04 which is expected to exit beta status soon.

@jennifer-shehane
PR from last week requesting review and merge!
I'd like to be ready for ubuntu-24.04.

@jennifer-shehane

Sorry I missed this one!

Thank you for merging! Now this repo is using ubuntu-24.04 as default (this is now also labeled ubuntu-latest).
At some stage I would expect ubuntu-20.04 to be deprecated and withdrawn, as GitHub's policy is to support only 2 versions of each OS (see GA). That would be the trigger to remove the use of Ubuntu 20.04 in this GitHub Actions repo.


Optional field Delay to pass when using @OnCLick or OnLongCLick

It would be best if we can pass the delay after which we want that action to happen.
So I don't have to set delay at all the places in the app.

This library is solely for the binding of listeners. For application-level features like delay, you're on your own to implement them.


Config file not present

not sure why I am getting this error from your code
when i run the data_preperation.py, second workbook step

@awsshaun it seems to happen for all new instances or or studio server kernels since April this year, but it won't affect the execution of the script.

thankyou
Shaun Keating
Snr Manager, Solution Architects, Financial Services
Amazon Web Services
+61 434 410 783 - mobile
Please note I work outside of traditional business hours as that works for me. If you have received this email after hours, I do not expect a response before the next business day.
[signature_1083371959][signature_2939025925][signature_227648429][signature_1956530583][signature_4083939803]
From: "Gordon Wang (Guanghui Wang)" @.>
Reply to: aws-samples/amazon-sagemaker-llm-on-video-audio @.>
Date: Saturday, 23 September 2023 at 1:19 pm
To: aws-samples/amazon-sagemaker-llm-on-video-audio @.>
Cc: "Keating, Shaun" @.>, Mention @.***>
Subject: Re: [aws-samples/amazon-sagemaker-llm-on-video-audio] Config file not present (Issue #8)
@awsshaunhttps://github.com/awsshaun it seems to happen for all new instances or or studio server kernels since April this year, but it won't affect the execution of the script.
—
Reply to this email directly, view it on GitHubhttps://github.com/aws-samples/amazon-sagemaker-llm-on-video-audio/issues/8#issuecomment-1732195081, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2GKXE72TWSPWRMP2SOY3RTX3ZIKBANCNFSM6AAAAAA42RLCEA.
You are receiving this because you were mentioned.Message ID: @.***>


Long Build Time for Docs

Description
I'm at the airport and cloned the repo so I could read the docs offline on the plane.  Installing, downloading, and compiling Ruby and the required Jekyll deps took a long time (> 5mins).  What do you think of converting the docs from Jekyll (Ruby) to 11ty (JavaScript) to keep the docs within the JS stack?  Happy to take this on if everyone would find it beneficial to remove the Ruby dependency and migrate to JavaScript/npm.
Steps to Reproduce
$ time gem install bundler jekyll

Another option would be to add a service worker

Great idea.  A one-file solution is always nice.

What do you think of converting the docs from Jekyll (Ruby) to 11ty (JavaScript)

I would love to do this. I've been using 11ty a lot recently and really like it. Not sure where this falls on our team priority list though. Contributions would be very welcome!
cc @arthurevans

I'm totally onboard with using 11ty for docs. 👍

Fixed by #1076

Thanks so much for taking the time to look into this and resolving.  Apologies for the late reply and my unavailability to contribute.


hardeningEnable and hardeningDisable not documented

There is the Hardening in Nixpgs section in the manual and both variables are listed, but it is not explained what types they are or what the semantics are (I first I thought hardeningDisable = true; would have an effect).
It gets worse because mkDerivation just forwards anything it gets and no error is thrown on wrong usage.
cc @globin @fpletz

https://nixos.org/releases/nixpkgs/nixpkgs-16.09pre90369.202d9e2/manual/#sec-hardening-in-nixpkgs describes the flags
Do you mean it should be mentioned that both take a list ?

Yes. And what they do exactly (why there’s two). It seemed to me like hardeningEnable = [] doesn’t actually disable all flags (what I expected).

hardeningEnable just enables optional hardening flags. To disable all hardening, there's a special "all" flag. That's indeed undocumented and should be fixed.
This would disable all hardening: hardeningDisable = [ "all" ].


Appstudio update test-component-pac-futj

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-futj-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
15 seconds
init

✅ Succeeded
21 seconds
clone-repository

✅ Succeeded
29 seconds
build-container

✅ Succeeded
44 seconds
deprecated-base-image-check

✅ Succeeded
12 seconds
inspect-image

✅ Succeeded
31 seconds
clamav-scan

✅ Succeeded
9 seconds
clair-scan

✅ Succeeded
8 seconds
sbom-json-check

✅ Succeeded
44 seconds
label-check

✅ Succeeded
10 seconds
show-summary

✅ Succeeded
10 seconds
show-sbom


Mangled properties are not resolved by ResourceDecoder

Codegen mangles property names that are in the set of reserved keywords for both JVM, Scala and Pulumi (wait, notify, given, urn, id, etc). These properties are generated with a following underscore so: notify_, urn_. We need to implement identical logic (probably via a separate module?) for mangling and demangling between codegen and core and use it in ResourceDecoder field lookup.

Needs some tests.


Put page nav in middle of action bar

Permalink/sidebar trigger will go on right.

Added in 97a981d5d9d8d32b5deaeeb370f1589bab763aac


Assigning Using Stack Allocated Chars

When trying to define a char using the syntax:
char nodeKey[4];

This allocated memory is placed in a specific location on the CPU memory, which becomes inaccessible as a different function (insert__hashmap() in this scenario) is called. So passing nodeKey into insert_hashmap will result in undefined behavior when trying to print a node's key.
The necessary changes to allow the use of char nodeKey[4] will require utilizing a struct to result in a pass by value to the function, which will then guarantee that nodeKey is accessible within the function. A struct like the following would result in a pass by value if it was used as an input into a function
struct SomeKey {
    char nodeKey[4];
};

This will need a refactor on insert__hashmap to handle a struct class.

With further research and investigation, the hashmap will utilize a vtable to support having dynamic type functions. The vtable (which is represented as a struct) can have specific compare and print methods that work for whatever type of key is inside of the struct. Because of the way that structs work (specifically looking at struct pass by value) we will no longer need to you the above suggestion for allocated char *'s (or char nodeKey[4]'s) and can instead use a vtable to store any type of information.

With the recent merge #4, overloading insert__hashmap() now works. See the pull request message for more information.


Compatibility with Raspberry Pi

Hi,
I am planning on using this haptic motor driver with the Raspberry Pi. Would it be compatible with something other than an Arduino? Also, I intend to use Python to code the driver.

Transferring this issue from the SparkFun DRV2605L Arduino Library over here as a request.


Suggestion for fixing the unintentional situation that since v0.6 the…

… dataconverter required a config file if it was called the classical way and in case no parameter yaml file was provided. For programmatically use of the converter the creation of an additional params file with only a few entries is unnecessary overhead especially when all cli arguments are available in the callers scope and thus the CLI call can be issues directly using the classical way dataconverter convert [INPUTFILES] options

I also removed the outdated documentation of the command line options as it is a second place where changes have to be applied constantly and the instructions for empowering people to find these are already given in the readme plus follow the typical style how to get help for command line calls

Tested 30ad68c of this branch solves the problems @sherjeelshabih


Emit declarations using alternative containing modules for types exported using separate export statements

fixes https://github.com/microsoft/TypeScript/issues/56856

Just a note to say that this change seems to have regressed our (Bloomberg's) workaround for #38111.
I'll put a playground together and raise a concrete issue tomorrow 🙂


WIP Guide for using Weave on Amazon ECS

Is this ready to be merged?

I don't think so. Anita was going to work on it.
On Monday, August 3, 2015, Ilya Dmitrichenko<EMAIL_ADDRESS>wrote:

Is this ready to be merged?
—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/guides/pull/13#issuecomment-127417802.

@2opremio yes working on it. Should have something up tomorrow.

A made my changes in another branch, aws-ecs-edits Please have a look when you guys get a chance. I also have a question with regards to weaveDNS terminology. Maybe @rade would like to comment on that? See my pull request, not sure if you all get this message or not, so bare with me ;)

Close in favor of https://github.com/weaveworks/guides/pull/23


Add 'Begin Latex in minutes'

Added 'Begin Latex in minutes' to the 'LaTeX' section and fixed typos in 'Arbitrary Latex Reference' (Arbirtrary -> Arbitrary)

Thanks!


Update downstream dependencies.

This bumps:

base
ledger
plutus

In addition, the index-state and pinned nix dependencies are synced with
those in base and ledger (and node).
A spurious upper bound on the semialign dependecy is dropped, since
this prevented building with aeson > 2.0.0. which is needed for other
components.

Github CI is failing:
 Resolving dependencies...
cabal.exe: Could not resolve dependencies:
[__0] next goal: cardano-crypto-class (user goal)
[__0] rejecting: cardano-crypto-class-2.0.0 (conflict: pkg-config package
libsecp256k1-any, not found in the pkg-config database)
[__0] fail (backjumping, conflict set: cardano-crypto-class)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: cardano-crypto-class


Add screenshots, keywords and icon

https://code.visualstudio.com/api/references/extension-manifest

Closed via https://github.com/Quatters/select-and-run-without-debug/commit/791ab03a3d2b17fbb1a295fa8d8deefe5be9ab9b