XMPP backend / client side

#15
@LEDfan I get an error for /http-bind:
No memcache available

Is there a way to disable memcache while I am developing, or do I have to install memcache?
TODO
I would implement the following points:

[ ] make it possible to enable/disable in admin section (otherwise any other XMPP server can't be used)
[ ] use jsxc.start

@LEDfan I get an error for /http-bind:

Should be fixed now, was a hard code value for testing.

Does your implementation only work on the current oc master? Because I get an internal server error.
PHP Fatal error:  Class 'Sabre\\Xml\\Writer' not found in /var/www/apps/ojsxc/lib/http/xmppresponse.php on line 14

Maybe related 6e6efb7?

Yes that commit will break it. We use the Sabre XML library as wrapper for PHP. The inclusion of the autoloader is needed for this.

@sualko since oC 9.0 sabre/xml is included, so we can use the library inclued in core.

I removed the line, because there is no vendor folder.
Any chance for a fallback for oc versions < 9. What is the minimum required
version for your code?
Am 20. Januar 2016 2:54:04 nachm. schrieb LEDfan<EMAIL_ADDRESS>
@sualko since oC 9.0 sabre/xml is included, so we can use the library
inclued in core.

Reply to this email directly or view it on GitHub:
https://github.com/owncloud/jsxc.chat/pull/16#issuecomment-173210783

Ah okay. There isn't a vendor directory because it's in .gitignore. The dependencies can be installed via composer install. This works both for 9.0 and < 9.0. So for now I would leave this as is.
I'll have a look at which server version my codes supports.

Hey, I could it running (after increasing the version number). Can you send/receive messages?
Can you add the subscription attribute to the roster items? This would lead to colourful avatars.
<item<EMAIL_ADDRESS>          name='Benvolio'
          subscription='both'>

Okay will do, but for now there are no presences. The version number must be increased for the database probably.
What code do you use in oc-handle.js for starting the xmpp connection?

I'm using:
/* global OC */
$(document).ready(function () {
	jsxc.options.xmpp.url = OC.generateUrl('apps/ojsxc/http-bind');
	jsxc.start(OC.currentUser + '@' + OC.getHost(), Math.floor(Math.random() * (1000 - 1)) + 1, Math.floor(Math.random() * (1000 - 1)) + 1);
});

But when the localStorage is clear (i.e. first time the page is loaded). I also have to call $("#jsxc_roster").removeClass("jsxc_noConnection");

@sualko which git tag should I use for the JSXC submodule with this branch?


Safe UI not showing most recent transactions information (latest nonces and signature data)

Description
When posting transactions with our delegate, we cannot get the UI to show the latest data. We have found a workaround if we post an on-chain rejection manually, we can get the latest data to show right away. We suspect it might be a cache bug.
For example, for our safe at 0x16388463d60FFE0661Cf7F1f31a7D658aC790ff7 on Eth mainnet, the UI shows this:
.
Notice that we pushed an on-chain rejection, since it wasn't showing up earlier.
However, we at the point of this screenshot, we had pushed a TX with nonce 1320 and it just doesn't show up no matter how often we refresh.
The transaction API does show a TX with nonce 1320 though:
https://safe-transaction.mainnet.gnosis.io/api/v1/safes/0x16388463d60FFE0661Cf7F1f31a7D658aC790ff7/transactions/
Here is a snippet of TX info from the endpoint at the time of that screenshot
[{"safe":"0x16388463d60FFE0661Cf7F1f31a7D658aC790ff7","to":"0x40A2aCCbd92BCA938b02010E17A5b8929b49130D","value":"0","data":"0x8d80ff0a000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000f200a696a63cc78dffa1a63e9e50587c197387ff6c7e000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000447c6a4f240000000000000000000000008c818613a97900cc1eda5893f04701b62e7c113800000000000000000000000000000000000000000000000000000000000004ec008c818613a97900cc1eda5893f04701b62e7c1138000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044641257d0000000000000000000000000000","operation":1,"gasToken":"0x0000000000000000000000000000000000000000","safeTxGas":0,"baseGas":0,"gasPrice":"0","refundReceiver":"0x0000000000000000000000000000000000000000","nonce":1320,"executionDate":null,"submissionDate":"2022-01-01T17:46:12.849908Z","modified":"2022-01-01T17:46:12.849908Z","blockNumber":null,"transactionHash":null,"safeTxHash":"0xf135b4934c5df52f8d0dda9dc1cffdd67df030ab51a94d28d8e3b50069a71272","executor":null,"isExecuted":false,"isSuccessful":null,"ethGasPrice":null,"gasUsed":null,"fee":null,"origin":"github.com/banteg/ape-safe","dataDecoded":{"method":"multiSend","parameters":
After 25 minutes delay, finally the UI did show 1320:

There weren't any noteworthy issues in the browser console while the issue was happening.
Environment

Browser: Edge
Wallet: Can repro this without a wallet connected, but typically Metamask
Safe: Eth mainnet - 0x16388463d60FFE0661Cf7F1f31a7D658aC790ff7
Environment:

production

Steps to reproduce

Post a TX to a safe
Go to the /transactions/queue UI

Expected result
Latest transaction and signature data
Obtained result
UI is out of data, but the backend API https://safe-transaction.mainnet.gnosis.io/api/v1/safes/{safe}/transactions/ endpoint has the latest data. UI takes 25 minutes to show it.

Any ETA on the fix?
As a work around, we are pushing tx from the web UI (removing an owner for example) and that triggers the update asap.

@kx9x @poolpitako
We have deployed a fix on January 7 and it seems to have fixed the issues that you mentioned on this ticket – the UI should now show the transactions/confirmations as soon as they are recognised by our Safe Transaction Service.
We are still keeping an eye on this specific issue so if the same issue arises don't hesitate to let us know.
Thank you for reporting!


Draft: more fix for seminaive

This PR fixes some remaining issues of #93 (which was described in #142) that the right-hand side of the set is not a function but bound to a function in the previous let binding. eg:  (rule ((= f0 (f 0))) ((let a (f 3)) (set (f 0) a)))
The previous fix didn't add semi-naive rule to match the variable bonded function call, and this fix conservatively moves all let binding to the body to ensure all functions are matched.
This PR also removes Action::SetNoTrack, which should be unnecessary, and turn off the semi-naive transformation in final_desugar pass to avoid auto-generated let binding being moved again.
A possible optimization is to do liveness analysis instead of moving all let binding to the body, but might be complex.
However, this fix is blocked by #143, as a test cannot pass without #143 being fixed.

Subsumed by https://github.com/egraphs-good/egglog/pull/197


Breaker Panels

From what I've gathered; there seems to be some interesting emphasis and mutual agreement between suggester and developer about creating a conduit system. Here's some things I have to add onto it.
You should add a circuit breaker / fuse holder panel along with conduits and junction boxes.
This would allow for easier, compact, and convenient methods for protecting your circuits / isolating specific circuits.
The capacity of breakers / fuse holders that a panel could hold should be directly associated with the capacity of conduits. If you're going to make conduit tiers; the tiers should be applied to the panels.
Circuit breakers could be added into the circuit panel box simply by inserting it into a slot and configured in the UI somewhere.
Sidenote:
if you add this and there isnt a satisfying "CACLUNK" when you "click in" a breaker onto the panel i'm going to be disappointed 😛

other components for din rails would also be cool


Please update ProvidedTypes.fs for Mono 5.0 #82

Please update to use the latest version of ProvidedTypes.fs, as described in fsprojects/FSharp.TypeProviders.StarterPack#121

@JohnDoeKyrgyz Could you please re-release package on NuGet?
Sorry, I accidentally pushed the fix to the repo indead proper PR.

NuGet package is updated.

Thanks!


Set signup state to waiting after successful signup & friends

:eyeglasses: @keybase/react-hackers
We now set the signup reducer state to waiting when the user confirms the final signup step, because the UI will linger for a few seconds on this dialog while the login and bootstrapping process occurs. Once the bootstrap finishes, we reset the signup reducer state.
I've tested this on desktop, iOS, and Android. On iOS I discovered some flakiness in the final signup screen closing that seems to be unrelated to these changes.

:mag_right: The commits 1d599b7d2917...0741e448c13e introduced some visual changes on win32:

Changed: user_search-Normal (before) (after)

Changed: unlock_folders-Single (before) (after)

Changed: unlock_folders-No_paperkeys (before) (after)

Changed: unlock_folders-Normal (before) (after)

👍


POC: EE-2493: mtls for edge agent

requires https://github.com/portainer/agent/pull/234
To use this, I create the 3 certificates we need (they go into ~/.config/portainer/certs/) using the ./build/mtlscerts.sh script, and then build and start both portainer and the agent using those
I then start portainer with the following args:
        "--sslcert",
        "${env:HOME}/.config/portainer/certs/server-cert.pem",
        "--sslkey",
        "${env:HOME}/.config/portainer/certs/server-key.pem",
        "--sslcacert",
        "${env:HOME}/.config/portainer/certs/ca.pem",

And an agent with:
        "--EdgeMode",
        "--EdgeKey",     "aHR0cHM6Ly9wb3J0YWluZXIucDEuYWxoby5zdDo5NDQzfHBvcnRhaW5lci5wMS5hbGhvLnN0OjgwMDB8Yzk6NWM6NmM6ZGI6MjM6ODk6ZjQ6NWY6NDQ6YjE6ZmE6MjM6NGI6MTM6MTM6MGR8Mw",
        "--EdgeID",
        "7e2b0143-c511-43c3-844c-a7a91ab0bedc",
        "--LogLevel",
        "DEBUG",
        "--sslcert",
        "${env:HOME}/.config/portainer/certs/agent-cert.pem",
        "--sslkey",
        "${env:HOME}/.config/portainer/certs/agent-key.pem",
        "--sslcacert",
        "${env:HOME}/.config/portainer/certs/ca.pem",

Replaced by https://github.com/portainer/portainer/pull/6612


Stop autorebuild if disabled in config file

This is a multiproject effort, that will also require:

change to osbs-client documentation about build process
changes to pyrpkg to provide commands to get/set this value

Looks pretty good to me, just a few comments above.

Thanks for the comments Tim. I fixed everything in the second commit.

LGTM


[PY] Fix: Update readme for autogen and twenty questions samples

Linked issues
closes: # (issue number)
Details
Provide a list of your changes here. If you are fixing a bug, please provide steps to reproduce the bug.
Change details

Describe your changes, with screenshots and code snippets as appropriate

code snippets:
screenshots:
Attestation Checklist

[ ] My code follows the style guidelines of this project

I have checked for/fixed spelling, linting, and other errors

I have commented my code for clarity

I have made corresponding changes to the documentation (updating the doc strings in the code is sufficient)

My changes generate no new warnings

I have added tests that validates my changes, and provides sufficient test coverage. I have tested with:

Local testing
E2E testing in Teams

New and existing unit tests pass locally with my changes

Additional information

Feel free to add other relevant information below

FYI to team - I checked with Aamir 1:1 and he is aware of the PR status and will circle back to it when he has some time :)


WIP: support Ember Data 3.13

Closes #338

I've tried to debug the broken serialization. I think the issue is, that our record is not created through InternalModelFactory's build method. It seems like Ember Data is creating another instance of InternalModel for the same record, which is used on serialization. I don't see any option to use InternalModelFactory cause that one is private and not exported. It seems like even InternalModel is only exported for ember-data-model-fragment: https://github.com/emberjs/data/blob/e773f8bbf668a3436433060294a667ba94877bb8/packages/store/addon/-private/index.ts#L28-L30
I fear either help from Ember Data team or a bigger refactoring is needed.

It seems like Ember Data is creating another instance of InternalModel for the same record, which is used on serialization.

Let me elaborate on this one a little bit as it's critical for the situation. I think it's best to understand by a show case:

Put a debugger here: https://github.com/lytics/ember-data-model-fragments/blob/master/addon/ext.js#L279
Execute the serialization test.
Inspect the decorator function for createSnapshot when it's executed for a fragment. I've used name fragment.

// verify that you inspect the correct record
snapshot.modelName // "name"

// compare the identifier of the internal model via person record in store and via internal model of the snapshot
// you will see that both are the same
snapshot._store.peekRecord('person', '1').name._internalModel.identifier === snapshot._internalModel.identifier // true

// compare the internal model retrieved via person record in store and via internal model of the snapshot
// they should be the same but are not
snapshot._store.peekRecord('person', '1').name._internalModel === snapshot._internalModel // false
``

@jelhan thanks for looking into it! I was afraid this day would come eventually. I think the solution here is to rewrite everything to use the modelData api.

@jakesjews could this be a temp solution before the rewrite?

@GCheung55 I don't think this PR is working yet but if there was a way to get it going then it could work.

@GCheung55 This PR is not working and if I didn't missed something there isn't a quick path to make it working. Ember Data changed there internal state management and do not export the required pieces that would be needed to adopt this change. As this addon was relying heavily on a private API that's not their fault. As far as I can see there isn't any other solution than rewriting this one based on newly exported public APIs.
@jakesjews Will close this one to avoid confusion.


Refresh linked data on dialog after dropdown update

I looked for the answer to this but cannot seem to find the right info. Please excuse my newbie ignorance.
I need to re-populate linked data on a dialog when the user changes a joined record using a LookupEditor, including if InplaceAdd = true and the user has added a new record or changed it.
An example would be in Northwind when in the Product dialog. You can assign or add a new supplier. If we wanted to display the supplier phone number on the Product dialog- it would need to update if the supplier updates or we add a new supplier.
In another case- we may want to populate non-linked data with defaults from the linked record. In Northwind, on the Order dialog, you have (non linked) shipping information. When adding a customer from the LookupEditor, how could we populate the shipping fields with default customer shipping address information?
So, what handler must I override to detect a value change in the LookupEditor? And what must I do to get the data in the dialog to conform to the linked record? Should this be done in the xyzDialog.ts script?
Also, is there full documentation (other than just the code) of Serenity objects and their methods?
Thank you!

Something like
form.MyLookupField.changeSelect2(e => {
     MyLookupService.Retrieve({
         EntityId: Q.toId(form.MyLookupField.value)
     }, response => {
         form.SomeDependentField.value = response.Entity.SomeField.value;
     }
});

There is wiki, guide as documentation, and comments in code.

OK, I'll try this. But where to put it? Would it go in the xyzDialog.ts script? And what is the handler that I must override? Would it be onchange() ?

Just put it in constructor.

See populate linked data sample in latest template (<IP_ADDRESS>)

Just wanted to inform you that I did implement this and it worked great. I did have to test for blank data first though or else it failed the lookup. Thanks for your help!
E.g.
`
form.MyLookupField.changeSelect2(e => {
if (form.MyLookupField.value != "")
{
MyLookupService.Retrieve({
EntityId: Q.toId(form.MyLookupField.value)
}, response => {
form.SomeDependentField.value = response.Entity.SomeField.value;
}
else
{
form.SomeDependentField.value = null;
}
});
`

@kerrgibson
Thumbs-up for the advice on using change() instead of changeSelect2()!. Been pulling my hair out all day because the inPlaceAdd button does not reflect the changes back in the form.


Feat:adding a new page to display all contributors✨

@SurajPratap10
I want to add a page to showcase all the contributors of this website.
can you assign me this issue.

But, there is a contibutors page right. You wanna enhance that then right ? @T-Rahul-prabhu-38


Nick: Watch  <IP_ADDRESS>

Nick requests the watch of the watch_keyword  199\.192\.26\.181. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

 199\.192\.26\.181 has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Do nit

help~

no one else,but you

I'm not sure if this is spam or you are making a real request.
You can use the pyDes.PAD_PKCS5 support (which is effectively the same as PKCS7).


Additional Linux dependencies now required?

When building via GitHub CI using the ubuntu-18.04 image, I had to install 3 additional packages to make it work:

libpango1.0-dev
libatk1.0-dev
libgtk-3-dev

If this is a requirement from now on, it should be mentioned somewhere in the docs.

Ok, after having a look at the output of cargo tree I think, I'm wrong. These dependencies seems to be related to the rfd crate I use. It's only a little bit strange that the build failed on compiling egui-winit, that was a little bit misleading.

those are required to build the file_dialog example


PI-8539 changed order how product actions are dispatched

Coverage remained the same at 33.498% when pulling aab2f9f20f87ec763a4992087bd70286ac041aa3 on PI-8539-error-when-opening-from-cart into c3c798e1106902ff45570dc8042bfb609c0bd30b on master.


Handling ISUP Messages

Hi,
Does DrachtIO server is able to handle ISUP Messages over SIP (as defined in RFC https://www.rfc-editor.org/rfc/rfc3372.txt) to receive PSTN call informations from PSTN Gateways.
It seems (if the gateway supports this behaviour) the ISUP Message should be transported within a Multipart body?

I've not done any work to support that specific RFC, or ISUP interop in general.  However, drachtio does provide some support for multipart bodies.  In the incoming invite request, the req.payload property will be an array of the part contents, as discussed here: https://drachtio.org/api#message-prop-payload

I'd be interested to know more about the scenarios / networks in which you find ISUP over SIP still a thing, as the spec is quite old and I'd figured the air had gone out of that balloon as we slowly are becoming an all-VoIP world.

We are working in a telecom environment using  outbound calls but a significant amount of PSTN ( ISDN ) on the other side (especiAlly Hardware Gateways SIP -> ISDN).
For scenarios like „temporary not available“ gateway send ISUP messages long before the final Sip Response (Gateway Plays an Audio Stream saying „not available“ and the ends the call). Our system can cancel the call in this scenarios earlier.
Von meinem iPhone gesendet
Am 19.12.2018 um 16:16 schrieb Dave Horton <notifications<EMAIL_ADDRESS>I'd be interested to know more about the scenarios / networks in which you find ISUP over SIP still a thing, as the spec is quite old and I'd figured the air had gone out of that balloon as we slowly are becoming an all-VoIP world.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/davehorton/drachtio-server/issues/67#issuecomment-448630926, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYvpiPVtkqpx5imzjPsK7nVvEOj9g4BGks5u6lhdgaJpZM4ZaZSi.

Ah, interesting, thanks for the elucidation.  Let me know if you are able to do what you need through examining the multipart content, or if more support is needed somewhere.

Yup, we will try this
You may close this issue
Von meinem iPhone gesendet
Am 19.12.2018 um 17:03 schrieb Dave Horton <notifications<EMAIL_ADDRESS>Ah, interesting, thanks for the elucidation. Let me know if you are able to do what you need through examining the multipart content, or if more support is needed somewhere.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/davehorton/drachtio-server/issues/67#issuecomment-448648304, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYvpiIkISeNouhiAuduvsT21PuP6Oqhoks5u6mNdgaJpZM4ZaZSi.


Simplify Riak cluster creation HostAndPort was added

Looks mostly good, just need to fix the formatting of the brackets to match the project.  +0.75 otherwise.

@alexmoore I also realized that introduced approach should be propagated to the RiakClient level as a newClient() routine.. Will add it and adjust PR according your comments.


Add netiquette feature

Part of #5934

Test URLs

Old issue: https://github.com/refined-github/refined-github/issues/3076
Old PR: https://github.com/refined-github/refined-github/pull/159

Screenshot

it's always still best to report issues with a regular bug report.

I'm leaving 3 months for this. The only reason to comment on closed PRs especially is to avoid having to create a full bug report. After 3 months the code is already well set and done.
I'll create a separate rgh-netiquette feature to completely hide the comment field on old rgh issues/PRs (behind a button still)


Person Properties Periodic Report

I started hacking around and got pretty close to building in easy user functionality for a periodic person properties report like GCM had. In this PR, I'm trying to put on more of my developer hat, so any feedback on how to improve the Rust code and structure is welcome. One of the features that I always wanted in GCM was a periodic report that listed people by cross combination of two person properties (number of people who are sick and under five, sick and over 65, etc.), so I implemented this as a necessary first step to adding that functionality.
However, this process raised a bunch of key questions for me about our ixa design so far, mainly on lazy property initialization.
Design Sketch

When defining a person property, the user specifies whether they would like the property included in the report or not.

define_person_property!(IsRunner, bool, true); // true means to include in report
define_person_property_with_default!(RunningShoes, u8, false, 0); // third arg is whether in report

All person properties implement a trait PersonPropertiesPeriodicReport that provides a method that tabulates the number of occurrences of each of the observed property values.
The reports module has a method that allows people to add a person properties periodic report that reports out the properties tabulation every report_period amount of time. Properties that are included in the report are passed onto the reports module automatically, and the reports module iterates over them, calling their tabulation method and sending a report for each property value to the person_properties_report.csv.

Implementation challenges
Challenges I describe here are also listed in the comments in the code, if it's easier to read inline.

At the current time, we have no context.remove_person(person_id) functionality, and it does not seem like we will add this functionality. This means that people we have set to be dead are still reported out on in the report. We could create add a new person property value to every property specific to dead people, or make every property an Option of what it already is and set dead people to be None, but neither of these feel like (a) good solutions (the first case sounds dangerous for f64 types and in the second case what if the type is already an Option?) or (b) user-friendly solutions. Some sort of context.person_teardown(person_id) functionality would be really helpful.
Each row in the report is associated with a time, but the interpretation of that time is not consistent. The report plan is added to the plan queue like any other plan, and there could be plans added after it at the same time as it. It is logical to make the row mean "the state of the world at the end of the listed time", but to implement that we need to have plans with priority.
Lazy initialization for person properties means that the initialize method for a property isn't called until that property is first accessed. The initialize method also adds the property to the list of properties, so a person property isn't included in the report until it is first accessed. One way around this is by producing an "initialization" report as well, and then our accompanying Python analysis package for ixa can stitch together the two to make a true person properties periodic report.

Moreover, lazy initialization also includes automatic set expansion. So, if the property is only accessed for the first two of five people (i.e., people with Ids 0 and 1), only property values for the first two people will be listed, not even listing "None" for the remaining three. if the property is accessed for people 0 and 3, two values will be listed and two "None"s will be listed. I have a test that shows this counterintuitive behavior in people.rs.

I think I caught a bug on the data plugins macro. I believe the data plugins struct must be public so that data plugins are accessible beyond just the mod in which they are created. This is necessary for being able to share the person properties data plugin with the reports module and generally for user-defined data plugins. I can pull out those commits into a separate PR if this is a bug fix. However, to not give the user the entirety of the data container plugin in a way that they could mess with it, I've made the properties_map public only to the crate. I couldn't do the same for the include_in_periodic_report attribute, but I do not understand why.
Next steps

GCM printed out person properties tabulations by region. With the argument that we just want to support a broad "partition" plugin for users, of which regions is one subclass, it is not clear to me where listing out number of people with each person property by some group fits in here -- perhaps the user can pick one of their one-to-one groups as a stratifier?
The code for counting number of people with each person property may be refactored as new ixa functionality comes online.
I realized that the implementation for the cross combination properties report I described is probably very different, instead with the user just providing the two particular properties they want cross tabulated as function inputs and does not require the PersonPropertiesPeriodicReport trait.

Example of what the report looks like

I left a few comments in line and I think this is a good start but I think it might be worth taking a slightly different approach. Here's what I'd recommend:

Sounds good! I appreciate the comments here -- I was more just hacking around and pleasantly surprised at how far I got in recreating the person properties periodic report from GCM. Was pretty sure this was not the right approach, and happy to switch to an alternative approach.

I would define the computer function as part of a register_periodic_report API method (i.e., an extension to context) rather than tied tightly to each PersonProperty

I thought through this design a bit, and the problem I had with it is that you would need to specify all person properties explicitly, right? That doesn't seem ideal to me when it could be done automatically and more importantly at the site of property initialization. However, I may not be understanding your idea properly.

Internally, this would depend on some implementation of "phases" as in here: https://github.com/CDCgov/ixa/pull/39/files – I'd recommend doing that part first in a separate PR (the requirements being: a first/normal/last phase, plans get added to Normal by default but you can use add_plan_to_phase with a phase name instead)

Yes! Wholeheartedly agreed. I added a test to #39 that I think users may find useful (since some of our users will honestly just read the tests to figure out how things work) and that's awaiting your review. Happy to make further changes there too.
I also think that even after that, pulling out some changes from here like adding some of the helper methods to context that see if there are more plans should be landed as PRs before this one.

I think moving it to an API method would also simplify registration quite a bit (since you would just expect people to initialize it manually) and we wouldn't really need automatic registration, although I'm open to other arguments.

I thought through this design a bit, and the problem I had with it is that you would need to specify all person properties explicitly, right? That doesn't seem ideal to me when it could be done automatically and more importantly at the site of property initialization. However, I may not be understanding your idea properly.

I can see how doing it at the site of property initialization would be nice in some cases, but I think there's plenty of scenarios where it wouldn't be – for example, if you wanted to reuse a person property across models but have different reporting, or maybe even if you have different kinds of reports that have different computations. I guess it's a judgment call but I don't think the alternative (i.e., just specifying them all explicitly) is that bad.

Yes! Wholeheartedly agreed. I added a test to https://github.com/CDCgov/ixa/pull/39 that I think users may find useful (since some of our users will honestly just read the tests to figure out how things work) and that's awaiting your review. Happy to make further changes there too.

Oh sweet didn't realize. Will take a look :)

I can see how doing it at the site of property initialization would be nice in some cases, but I think there's plenty of scenarios where it wouldn't be – for example, if you wanted to reuse a person property across models but have different reporting, or maybe even if you have different kinds of reports that have different computations. I guess it's a judgment call but I don't think the alternative (i.e., just specifying them all explicitly) is that bad.

I agree with Kate here. I don't think that the authors of properties are in a position to know which reports people want and I don't want random property authors littering my reports directory with stuff I don't want.

Ok! I am convinced on this front! This version would make registration much easier. Looking forward to diving into it!


Automate code checks

We should be checking each PR for code health checks.
Possible checks are:

code coverage
cppcheck
warnings
valgrind/address sanitizer

Would asan and lsan be preferred over valgrind?

Related: https://github.com/LLNL/axom/issues/211

Discuss at a future meeting and decide what we want to do.


fixing examples/angular-1/sibbling-routes

I tried out the sibbling-routes demo and I had to make a few modifications to make it work.  Please review and pull in if it is acceptable. I tried using router-link but didn't find any documentation on creating the links.

This has since been fixed in v0.5.0.
The intent was for both component and components to both work.
Apologies for the confusion!

@btford No problem, it appears the other issue was still unsolved, create pull request for the links: #189.


EditorNode3DGizmo._redraw not called when more than 2 nodes are selected.

Tested versions
4.2.1
System information
Ubuntu 22.04, Vulkan forward+
Issue description
The EditorNode3DGizmo._redraw method is not called whenever there is three or more nodes selected.
Steps to reproduce

If I select one node in the editor, it print a list of one node
If I select two node, it prints a list of two node
If I select three or more node, it does not print anything (Method not called?)

Minimal reproduction project (MRP)
Frankly I have no time right now to build such a project, sorry, here is my script though
extends EditorNode3DGizmo

func _redraw():
    print(EditorInterface.get_selection().get_selected_nodes())

If I select one node in the editor, it print a list of one node
If I select two node, it prints a list of two node
If I select three or more node, it does not print anything (Method not called?)

The Gizmo's _redraw method is called whenever the editor needs it to be redrawn. It is not guaranteed to be called every time new nodes are selected. That may just be a side-effect of it

Closing as per the above, if you can find some specific behaviour that makes things unusable, rather than unexpected workflows, please open a new issue


Make startHook not blocking jenkins startup

This PR is two folded. The first commits holds a lot of whitespace fixes.
The second commit is the actually change. It moves the creating of the hook into a runnable, which makes it way faster on startup.
I have choosen a fixed thread pool with five executors. Not sure if this is a good value or not :)

Not sure what the cause for the errors are, looking into them.

This could fix #461

@bjoernhaeuser looks like there's a merge conflict now.
@benpatterson do you have any time to take a look at this and/or help?

Merge-Conflict solved!

@benpatterson I think that we should still let people configure it in a range 1..Runtime.getRuntime().availableProcessors()
I personally wouldn't want to make assumptions on what resources you do/don't have on a users' system

Ok. I may keep it simple. Or, if someone wants to tackle it, that's fine, too. Thx for pinging back.

Yeah, but has someone an idea how to make this configurable through the UI? :D

heh @bjoernhaeuser yes I think it's do-able...will take some cleaning & casting-to-int kinds of things (i.e., more work...not a ton of work, but it'll still need to get done).

Personally, I would like to see this auto-scale with Runtime.getRuntime().availableProcessors() but be configurable via system property for those who care.  I don't see any use in it being configurable via web UI.

@samrocketman the only reason why I mentioned having it in the UI, with 1 being the default & system CPUs as the max, is because I don't think it's a good idea to make assumptions as to what is a "smart" use of a users' system resources. Sure, we can make a best guess but if the configuration is "hard" to change it makes the plugin a bit more inaccessible.
Just trying to keep user-empathy in mind, although I might be over-thinking it.

Just trying to keep user-empathy in mind, although I might be over-thinking it.

It's not that I don't have empathy for users or and I'm not disregarding your feedback.  Contrary I'm sympathizing as a user myself, users want Jenkins to perform well out of the box without the need for them to heavily tune.  Detecting the number of processors at runtime is definitely reasonable and a known good practice for threaded programming.
Essentially, what I'm taking into account with my feedback is also user experience.  As a user of Jenkins, Jenkins has many checkbox items.  Adding more options for things like number of threads GhprbTrigger should use is typically a very advanced user desire.  It's better to detect resources and make a decision for the user (but fall back to allowing the user to override our decision via system property).
I would also like to point out that there's precedence for my feedback in Jenkins core as well.  Check out Jenkins.class where Jenkins automatically detects the number of cores for it's own runtime.
I warmly give this feedback as a Jenkins user myself.  I maintain a Jenkins instance with over 3000 jobs and 1000 users.  I feel the feedback I've given is relevant to both large and small Jenkins instances which is why I want to take the time to explain to you the thoughts behind my feedback.
I care about this PR because it delays my Jenkins startup time by more than 15 minutes.  I would like to see it account for practices seen elsewhere in the Jenkins code base which is why I've provided links to other code justifying my feedback.

@samrocketman completely fair & valid opinion, I was just giving my two cents is all. Like you I'm managing a master with similar numbers (thousands of jobs & users) and am coming from a perspective where I would like to tweak/tune the config multiple times depending on type of instance the master is running on via UI.

My concern is more along the lines of how many configuration bits are in this plugin, and trying to keep it simpler. Contradicting myself though, I am picking away at moving this to the UI. Although it's a good start, I don't want to hardcode it.
If someone wants to set it to the available processors, we can merge that and worry about the UI configuration later as an enhancement. Or, wait until the UI end of it gets done. No strong preference between the two right now.

Sorry; wanted to clarify.... To put it another way, I see both sides of the argument, and perhaps focusing in "when can this get done" instead, avoiding the GUI changes will speed up getting this merged.

@benpatterson totally ok with that, thanks for the thoughts!
And yes, I'm ok with just merging this as is 😄

Does the thread pool created continue to be used post-startup during normal operation?  It was my understanding that this only affects GhprbTrigger on Jenkins startup.

Thanks for the chatter folks. Merging as-is. I'm planning on following-on with minor enhancements, but in case I can't get to that soon, the main value of getting this merge will be realized now. :dancer:

Released v 1.39.0; it'll appear in Cloudbees infra in ~24 hrs.

I'll open a PR based on my feedback since it wasn't updated.  I'll link back to this PR for discussion purposes.

@benpatterson @samrocketman @bjoernhaeuser yaaay!!! Awesome stuff guys, thank you all 😄


Allow configuring the working directory of C-API external commands

Some external commands shell out to tools which may produce dependency files. Configuring them with a working directory allows relative paths which may appear in these files to be resolved correctly. The resolution logic added here is identical to ShellCommands'
rdar://99284779

@swift-ci please smoke test

@swift-ci please smoke test


Issue with installation

Describe the bug
Hi. I followed all the steps outlined here:
https://www.wangchucheng.com/en/docs/hugo-eureka/getting-started/
and installed using submodule.
When I type hugo
I get this
Start building sites …
hugo v0.99.1-d524067382e60ce2a2248c3133a1b3af206b6ef1 windows/amd64 BuildDate=2022-05-18T11:18:14Z VendorInfo=gohugoio
WARN 2022/10/11 09:53:24 Param 'hero' in params.toml is deprecated and will be removed in Eureka v1.0.0. See https://www.wangchucheng.com/en/docs/hugo-eureka/homepage-configuration/
Error: Error building site: POSTCSS: failed to transform "css/eureka.css" (text/css): resource "css/css/eureka.css_e15155940383ab15df770a6225032646" not found in file cache
Total in 793 ms

To Reproduce
Does this issue reproduce with the latest release?
I use version v.0.9.3
Steps to reproduce the behavior:

Go through installation process via submodule..

Expected behavior
A built website
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

Hugo Version: 0.99.1
Eureka Version: v0.9.3
Go Version: 1.19.2
Additional context

Add any other context about the problem here.

Hi @RenaudDev,
I think it is because of Hugo Version. Hugo introduces a new feature which makes the cache incompatible with previous version. So you can upgrade to Hugo v100.0+ and this issue should be solved.


Dockerfile adapted with the new GalaxyLD architecture

Dockerfile did not work. The file is now adapted with the new directories organization.

Thanks Olivier !

Le 5 oct. 2017 à 16:01, Olivier Filangi<EMAIL_ADDRESS>a écrit :
Dockerfile did not work. The file is now adapted with the new directories organization.
You can view, comment on, or merge this pull request online at:
https://github.com/albangaignard/galaxy-PROV/pull/4 https://github.com/albangaignard/galaxy-PROV/pull/4
Commit Summary
Dockerfile adapted with the new GalaxyLD architecture
File Changes
M Dockerfile https://github.com/albangaignard/galaxy-PROV/pull/4/files#diff-0 (6)
Patch Links:
https://github.com/albangaignard/galaxy-PROV/pull/4.patch https://github.com/albangaignard/galaxy-PROV/pull/4.patch
https://github.com/albangaignard/galaxy-PROV/pull/4.diff https://github.com/albangaignard/galaxy-PROV/pull/4.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/albangaignard/galaxy-PROV/pull/4, or mute the thread https://github.com/notifications/unsubscribe-auth/AKLGEIXTlEikuh4V7o_5r_JfY3ZQejQYks5spOFRgaJpZM4PvIUR.

--
Alban Gaignard, PhD, CNRS

+1


get recent update of a repo

Proposed Method: get_repo_update()
Description
Return the recently updated date.
To what class it belongs?: Repository
kindly, assign me this issue.

i would like to work on this issue under JWOC

Go ahead @codesleep-Beperfect , name it last_updated_at()


[Resources] Rest Api Defined in Swagger Returns 404 by Service

This issue originates from https://github.com/Azure/azure-sdk-for-js/issues/15460.
The swagger defines a rest api, however, the service returns 404 error when call this api:
{
    "error": {
        "code": "InvalidResourceType",
        "message": "The resource type 'operations' could not be found in the namespace 'Microsoft.Resources' for api version '2021-01-01'. The supported api-versions are '2015-01-01'."
    }
}

@shenglol pls help take a look at the issue

Will take a look.

@shenglol  Any updates on this issue? I can see from your manifest. Microsoft.Resources/operations still only support 2015-01-01 https://armmanifest.visualstudio.com/One/_git/Manifest?path=%2FMICROSOFT.RESOURCES%2FPROD%2FMANIFEST.JSON&version=GBmaster&line=2402&lineEnd=2402&lineStartColumn=2&lineEndColumn=28&lineStyle=plain&_a=contents and we have another customer complains about this issue again https://github.com/Azure/azure-sdk-for-js/issues/15460#issuecomment-891522699.


Error caused by guzzle psr-7 update

Environment details

OS: Ubuntu
PHP version: 5.6
Package name and version: Google api client 2.2.3

Error
Header value must be a string or an array of strings.

Code
$token = $client->fetchAccessTokenWithAuthCode($code);

The latest update to Guzzle psr7 https://github.com/guzzle/psr7/pull/250, causes an error with google api client when trying to fetch an access token.
To fix it I had to downgrade the Guzzle psr7 version to 1.5.2 in composer.json
"guzzlehttp/psr7": "1.5.2"

Thanks rajeshjayan60, I too am getting errors but I'm yet to identify which of the packages is using Guzzle in a way that's causing it.

Update: This breaks the aws/aws-sdk-php package version 3.99.2 S3 client

v1.5.2 is the latest release of guzzlehttp/psr7, so I'm not sure what you are downgrading from. Are you using dev-master or another unreleased version of the dependency? We don't recommend relying on unreleased package versions when it can be avoided.
It appears that they've merged a fix for this already: https://github.com/guzzle/psr7/pull/272

Thanks for the reply. It seems my guzzlehttp/psr7 dependency was pointing to dev-master. Changing the minimum-stability  to stable in composer.json seems to do the trick.


Manual upgrade to 7.4.4

PR Summary

PR Context

Thank you for helping us keep this updated @KexyBiscuit! Running checks and hopefully can merge once they pass


[3.1] Column Name Mapping Issue

If a column is defined as
[Column("foo")]
public int Bar { get; set; }

When auto-select is enabled, the generated SQL looks like SELECT foo AS Bar FROM ... and PropertyMapper.FindMember will find the column, because the corresponding PocoMember name is "Bar" and the data reader field's name is "Bar" too.
However, as soon as manual SQL is written, neither SELECT * FROM ... nor SELECT foo FROM ... work because the PocoMember name is still "Bar" but the data reader field's name is "foo"... and the PocoColumn.ColumnAlias is empty. So, FindMember does not find the member.
Practically, this means that SELECT * cannot work at all, and any custom SQL must remember to add the AS Bar bit. Which is not really convenient. In addition, the following will fail, even with auto-select.
[Column("foo")]
public int Bar { get; set; }
[Column("bar")]
public int Foo { get; set; }

Indeed, auto-select will do SELECT foo AS Bar, bar AS Foo FROM ..., the reader's first field will be named "Bar" which will be mapped to property Bar instead of Foo. Of course one answer is... don't do it ;-) But...
Couldn't the situation be improved with:

Queries (and that includes auto-select) do not alias a column unless an alias is specified explicitely for that column
FindMember is modified with:

return pocoMembers.FirstOrDefault(x =>
{
  var col = x.PocoColumn;

  if (col != null) // if we have a column, match against the alias if any, else the name
    return IsEqual(name, col.ColumnAlias ?? col.ColumnName);

  return IsEqual(name, x.Name); // else use member's name
});

Is this all making any sense to you?

And... that would not be enough, now BuildMapPlans would need to be modified to begin with:
// find pocomember by property name
var pocoMember = pocoMembers.FirstOrDefault(x => IsEqual(groupedName.Item, x.Name));

So FindMember is used only when mapping from old to new conventions, and it has to work as described above, and then it's not needed anymore and everything can happen on name only. But FindMember should not be used in both cases else it causes confusion.

hey, @zpqrtbnk @schotime i think the problem is the difference between property and column name in PropertyMapper.FindMember, i don't know if it is intended, therefore there is ColumnAlias to accomodate this, but here is my fix in PropertyMapper.FindMember
return pocoMembers.FirstOrDefault(x => IsEqual(name, x.Name) || (x.PocoColumn != null && (IsEqual(name, x.PocoColumn.ColumnName) || IsEqual(name, x.PocoColumn.ColumnAlias))));

@dwirawan I tried this too but as long as you leave the initial IsEqual(name, x.Name) you cannot handle the mixed foo/bar columns and aliases from my example. FindMember needs to be splitted into two, one method that deals with database names and aliases (when converting from "old conventions") and not names, and another method that deals with names.

@zpqrtbnk ahh yess, i forgot that.. well, i agree with you, it should look for ColumnName or ColumnAlias first, and fallback to default property name :+1:

hmmm.... @zpqrtbnk you're changes created 10 test failures, and if you use FindMember with your changes in both spots you get 50 test failures. double hmmmm

This seemed to make it work.
            return pocoMembers
                .Where(x => x.ReferenceType == ReferenceType.None)
                .FirstOrDefault(x =>
                {
                    var col = x.PocoColumn;

                    if (col != null && IsEqual(name, col.ColumnAlias ?? col.ColumnName))
                        return true;

                    return IsEqual(name, x.Name);
                });

Fixed in latest commit.


Radio with model=undefined and checked=undefined should be checked by default

I'm submitting a bug report

Library Version:
latest in gist

Please tell us about your environment:

Browser:
all

Language:
all

Current behavior:
If input type="radio" has model.bind="undefined" and checked.bind="value" where value=undefined, it is not checked.
https://gist.run/?id=5c2d55c58bb270bfab2f41026898cd23
Expected/desired behavior:
It should be checked by default, similar to when it is clicked.

Thanks for reporting this.
https://github.com/aurelia/binding/blob/b2d68c85d1e02775300a083746880de03990d034/src/checked-observer.js#L19


Bump RGD to get Mesh3D model rename

The PointCloud model was renamed to Mesh3D upstream in rgd_3d to account for the fact that it supports generic meshes, not just point clouds. Since we're using it for non-point cloud meshes, I've upgraded the dependency so we can use it.
I've also changed the before_binding method name to mutate_configuration, since the former has been deprecated by composed-configuration.

I approve of this, but I had another PR (#18) I was making, so I've rebased that off of this, so this PR is now included in that one. Closing in favor of #18.


Try sharing binary artifact for benchmarks job

Description of proposed changes:
Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

https://github.com/gluwa/creditcoin/runs/7658779784?check_suite_focus=true#step:6:36
Hmm looks like it was a cache miss

Closing in favor of #499.


bat: Specify where to run bat tests from

Bat test requires access to a ciao cluster and for storage
tests it requires qemu-img and access to the ceph cluster.
This change updates _relase/bat/README.md to

Instruct the user to run the tests from the controller
Fix typo in 'wildcard'
Fix hyperlink to singlevm

Signed-off-by: Alberto Murillo Silva<EMAIL_ADDRESS>

@kaccardi Can you review this one?

Coverage increased (+0.005%) to 64.745% when pulling df5019fe9d4ac43708b9156a1401be330e64d244 on albertomurillo:bat into d940dcc3edf3b6a4ea99b69ea2afd30d9bb3da6f on 01org:master.

Coverage decreased (-0.01%) to 64.742% when pulling f663ef46ad019554d08b74124635de5617f30bcc on albertomurillo:bat into 49b9b8242c3dd8bb25805fc21e681981a039e797 on 01org:master.


fix(hydration): should patch option's value when hydrate select

fix #4006

See 34d4991d - unfortunately this PR doesn't cover other cases in which v-model input elements can also have non-string bindings: :value, :true-avlue and :false-value.


Mutation methods polyfill overwrites native implementations

Element.prototype.mutation polyfill implements these DOM methods: append, prepend, before, after, replaceWith, remove. It does so without checking whether any individual methods already exists on Element. For example, Chrome, Firefox, Opera, and Safari implement the element.remove() method natively.
The detection code for mutation polyfill will let the polyfill happen if any of these methods are missing. Therefore, if the browser implements 5 of these methods but not the 6th, the polyfill would still kick in (as it should) but it will overwrite the 5 native implementations (as it shouldn't).
My proposed solution is to have per-method conditionals within the polyfill to only define the methods which are missing.
/cc @jonathantneal

@mislav good catch. The quick fix is to add a check before every method in both variations of the polyfill. However, if any browser implements another mutation method unlike our existing sets, we’ll have even more fragmented polyfills.
Each method (append, prepend, before, after, replaceWith, remove) should be its own dependency, and the mutation macro should be its own private dependency ala #280. This would make transitions like #254 all the easier.

I think that the complexity of splitting mutation methods each into its own polyfill isn't worth it. All of them share the same internal method that they're implemented in, after all, and their total size is negligible when served over the wire. I would suggest keeping everything as it is now, but avoiding overriding native methods at all costs.

@mislav, I didn’t mean to miscommunicate; this is not about total size.
This is about keeping the polyfills organized and easily maintainable. What if Firefox begins supporting the ParentNode methods prepend and append? What if Chrome finishes supporting the remaining ChildNode methods after, before, and replaceWith? What if after is implemented in one browser but then becomes appendAfter? We could have 3 to 5 versions of the same polyfill.
All of those scenarios have happened in one way or another already, because we’re dealing with prollyfills. It’s an exciting new game to play, and this project has always benefited from keeping its polyfills modular.

Resolved by #288


Will not scrobble Napster

I switched to Samsung Galaxy S8 plus and now Napster is not scrobbling.

Napster doesn't show up as an enabled app for me with the latest version of this and Napster


Protocol::ACME is NOT installed

I'm trying to install the plugin, but I get the following message which halts the installation process. I do what the plugin suggests (install using /scripts/perlinstaller - appears to be successful), but I still don't see anything under the plugins section in cPanel WHM. From what I can tell, I believe this error could be related to the fact that I am on an older version of Centos (CENTOS 5.11 i686 virtuozzo – host  WHM 56.0 (build 22)).
Protocol::ACME is NOT installed
Installing Protocol::ACME
.....
.....
 Testing  perl modules we just installedw
.....
Protocol::ACME is NOT installed
.....
There was an error verifying  required perl modules are installed.
The following perl modules could not be installed:
Protocol::ACME
You can try installing these modules by running
/scripts/perlinstaller <module_name>
for each module name listed above.

Glad to see I'm not alone.

Have you tried running
/scripts/perlinstaller Protocol::ACME

Yes.

Reply to this email directly, view it on GitHubhttps://github.com/Prajithp/letsencrypt-cpanel/issues/58#issuecomment-226505316, or mute the threadhttps://github.com/notifications/unsubscribe/AS5ATpkcMN56iOj65rXWOUYRDli89Sxjks5qMWAbgaJpZM4IwHDw.

@itseasy21 Thank you so much for helping out him.

@Prajithp why has the issue been closed when there have been no fixes posted..., @itseasy21 suggested running the perlinstaller but the original issue description shows he tried that (and so have I) and it doesn't work!

Couple of things that come to mind:

Ensure host name is set correctly
CentOS 5 doesn't support SNI, so you're going to run into issues if you don't have static IP addresses for everything
Ensure you are not using 2FA for root (it may work at this time, but I recall there being an issue at one point)

Hope this helps someone.

So the actual issue is that let's encrypt can't be supported properly on WHM/cPanel on CentOs 5? That should be specified somewhere, perhaps on the README.MD.
I know CentOS 5 is on EOL for WHM/cPanel support but a lot of servers are still running on it.

I didn't say "not supported". I did say you'd need static IP addresses on everything. One of the big reasons a lot of people abandoned CentOS 5 years ago in favor of 6, is that SNI was supported. This meant less static IPs needed.
It is stated in the previous issues (I'm the one that mentioned it a few months ago), but you're welcome to contribute to the README if you like.
Are you fully updated with yum and cPanel on your CentOS 5 server?
Also, depending on when you installed, it may be worth it to remove (not upgrade) and completely re-add this script...then reinstall it. Curious if that fixes the issue for you.

It's fine for me, i'll just update the server to newer OS, it was on our TODO list anyway before fall 2016 so this is a good reason to push forward. Although, to answer, yes I keep an updated server aside from still rolling on CentOS 5. I don't have enough static IPs for my needs also.
Perhaps it is supported but it requires a few workarounds and defeats the purpose of actually using let's encrypt which is auto renewal and maintenance. The fact that I am here discussing this issue shows that it's not clear enough on the get go that there are issues with Let's encrypt plugin and CentOS 5.
Thanks for the quick replies though


add new twitter: SREWorkbook

This change add the SREworkbook twitter account of the Site Reliability Workbook

Thanks 👍

@dastergon Thanks to you for the awesome collection 💯


API schema docs sometimes rendered on one line

For example, look at PatchCallEdit on the mgmt orchestrator docs. Compare it to ServiceInstance on the same page. The most obvious difference between the two in the source code is that PatchCallEdit has a newline after """ while ServiceInstance does not.

[ ] Investigate root cause: newline?
[ ] If feasible, fix the root cause, if not work around it by dropping the newlines everywhere.

Correction, ServiceInstance is shown on three lines, with each line showing more than one :param, so it suffers from this issue as well.


find -m not supported on OSX

https://github.com/creationix/nvm/blob/master/nvm.sh#L555
$ find -maxdepth 1 -type d -name 'default.*'
find: illegal option -- m
usage: find [-H | -L | -P] [-EXdsx] [-f path] path ... [expression]
       find [-H | -L | -P] [-EXdsx] -f path [path ...] [expression]

This turned out to be an issue on my side.  Sorry!

For more detail this error was popping up since I didn't have a .nvm directory upon installation, therefore the search path passed to the find command was null.

@patbaker82 Thanks for reporting - the $NVM_DIR should be created by the installation process, since that's where nvm.sh should live - can you elaborate on how you installed nvm and where the error was?

@ljharb this might not be an issue for this project.  I installed nvm with Homebrew.  I didn't debug too much after the fact.  Everything is working great now after the .nvm directory was created manually.

@patbaker82 ah, homebrew is unsupported and highly discouraged. Thanks for clarifying.

@ljharb I just experienced this same issue when installing via Homebrew - can you explain why it is unsupported and highly discouraged?

@dav- primarily that it's not an official distribution channel, and as such, I can't make any guarantees as to the formula quality. Also, I believe updating with homebrew will wipe out your node installations, which is just insanely bad.


Make Event class chainable

It would be cool to do:
const event2 = event.filter(data => !!data).map(data => data.field);

dude - don't over do it ;-)

It sucks cause now I have to write:
map(filter(event, data => !!data), data => data.field);

Or worse:
event = filter(event, data => !!data);
event = map(event, data => data.field);

Here are a few examples:

https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/extensions/electron-browser/extensionEditor.ts#L189
https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/extensions/electron-browser/extensionsViewlet.ts#L95

I could write all that logic in each event listener, but that wouldn't be cool. 😎

Sorry, but how is that more elegant (not event talking about wasted performance and function scopes) that a single listener and a switch/if-else statement?

Apart from personal taste, the reason I comment on this is that Event and Emitter must kept stable cos they are reflected one by one as API and wouldn't like to see a set of shadow features on top of the defined ones.

Good to know. I don't mind doing it in a subtype, doesn't need to go to the base type:
interface EventVNext extends Event {
  constructor(event: Event);
  map...
  filter...
}

Performance is relative. I doubt that it is a significant factor for the amount of these events we intend to observe. I take preference on code style over that sort of performance problems, any day.
The entire virtual rendering of the list, which we can agree is quite performant, is made with function closures, by the way.  Would it be faster with a bunch of for loops and if statements? Yes. Would it be perceivable? Probably not. Would it be more readable or better maintainable code? I don't agree that it would.

Would it be more readable or better maintainable code? I don't agree that it would.

That's where personal taste begins


Add import command and fixed bugs as well as tests

Fixes #90

Currently .csv files are being checked for style and automatically failing because well their .csv files and not code files

LFG FIXED THE RANDOM BUG


Interractable items without actors.

Is your feature request related to a problem? Please describe.
I like being able to make interactable things where I can check out an actor and make it say text. my problem is I want to use this feature of making something interractible but with something like a trigger when i can be a certain size for long areas you can check out or really small areas like an 8x8 square.
Describe the solution you'd like
Either make a new solution or make it so triggers can also be used as press [BUTTON HERE] for [ACTION HERE] instead of only being walked into.
Describe alternatives you've considered
Actors. lots of actors for one long item to be interractible.

I forgot to mention that it would be cool to have interractable areas with no collision. like closing a door in a top-down or sidescroller


Filenames with umlauts cause broken upload

On rocketchat+ on iOS when you upload a file (eg pdf) with an umlaut the file seems to upload correctly and is shown in the message stream. But clicking it does not open it but only shifts the text up and down a bit

@emign Sorry, is this mobile or on a Mac computer?

It is on iOS mobile (iPad and iPhone) with version 1.6.0. the same (umlaut-titled file) can be downloaded via a browser on the device just fine btw.

Issue moved to RocketChat/Rocket.Chat.iOS #851 via ZenHub


When powercalculator starts calculating impact, need to check sample fields

How to reproduce:
When configuring initial state:

set calculateProp to impact
If we set total sample and runtime
set lockedField to visitorsPerDay

visitorsPerDay will start with the wrong number as there only calculation we do in that case is impact.

Fixed with https://github.com/bookingcom/powercalculator/commit/9bc5c8d702a75bfab97c6644023acd3199308898


 This shuts them down by default. They can be turned back
on with config.SILENCE_FAB = True
Also:

shushing a flask-cache warning around setting up a null (default) cache.
showing the config file that gets loaded explicitely
After:

$ superset
Loaded your LOCAL configuration at [/Users/maxime_beauchemin/code/caravel/superset_config.pyc]
usage: superset [-?]

                {shell,version,worker,db,runserver,refresh_druid,init,load_examples,update_datasources_cache}
                ...

positional arguments:
  {shell,version,worker,db,runserver,refresh_druid,init,load_examples,update_datasources_cache}
    shell               Runs a Python shell inside Flask application context.
    load_examples       Loads a set of Slices and Dashboards and a supporting
                        dataset
    worker              Starts a Superset worker for async SQL query
                        execution.
    db                  Perform database migrations
    runserver           Starts a Superset web server
    refresh_druid       Refresh druid datasources
    init                Inits the Superset application
    version             Prints the current version number
    update_datasources_cache
                        Refresh sqllab datasources cache

optional arguments:
  -?, --help            show this help message and exit

LGTM

I'll skip the typo fix here to preserve the commit SHA since I have another PR on top of this one. Will fix on top of these 2.


Use react-markdown in DeleteEnvModal

blocked by https://github.com/facebook/jest/issues/9430
related to https://github.com/inmanta/web-console/issues/1798
Use ReactMarkdown for bold and italics: https://www.npmjs.com/package/react-markdown
The words module also needs to distinguish between regular text and markdown text.

Hey team! Please add your planning poker estimate with ZenHub @bartv @Stijnkool


For the traffic flow limit, we don't cover Azure Firewall

Hi, this page explains traffic flow limit, and it doesn't include Azure Firewall. Is that because it's consider as NVA? Would it be great if we add AzFW for better explanation?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c7c054b7-422c-c3b0-fc8e-91314231ee0c
Version Independent ID: 42825540-2137-92e3-08b0-0dbd84089eda
Content: Azure virtual machine network throughput
Content Source: articles/virtual-network/virtual-machine-network-throughput.md
Service: virtual-network
GitHub Login: @asudbring
Microsoft Alias: allensu

@hanchoi
Thanks for your feedback! We will investigate and update as appropriate.

@hanchoi Azure Firewall is considered as a PaaS service in itself, not a VM.
Please refer to https://learn.microsoft.com/en-us/azure/firewall/firewall-performance for information on Azure Firewall performance and throughput

@hanchoi As there are no active discussions going on, I am closing this thread. Please tag me should you have additional queries, we shall reopen the issue and work with you.


[14.0.x] ISPN-14390 When reading entries from read only store apply expiration

https://issues.redhat.com/browse/ISPN-14390

Merged, thanks


Pin dask ipywidgets version to 7.7.1

Changes introduced in this PR:

Pin ipywidgets to 7.7.1 for the Dask built-in environment.

The latest ipywidgets 8.x removed an essential method used by dask-gateway when using the client widgets. This is a short-term solution.
Types of changes
What types of changes does your PR introduce?
Put an x in the boxes that apply

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features to not work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing
Requires testing

[ ] Yes
[x] No

In case you checked yes, did you write tests?

[ ] Yes
[ ] No

Documentation
Does your contribution include breaking changes or deprecations?
If so have you updated the documentation?

[ ] Yes, docstrings
[ ] Yes, main documentation
[ ] Yes, deprecation notices

Further comments (optional)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered and more.

Thanks for the update @viniciusdc!
As I was testing the dask dashboards for the v0.4.4 release, my basic test seemed to work using both ipywidget 7.x and 8.x. Is this something that you think needs to be included in the v0.4.4 release?

Thanks for the update @viniciusdc! As I was testing the dask dashboards for the v0.4.4 release, my basic test seemed to work using both ipywidget 7.x and 8.x. Is this something that you think needs to be included in the v0.4.4 release?

Hi @iameskild that's good to know, did you try running the snippet bellow?
options = gateway.cluster_options()
options

Thanks for pointing this out @viniciusdc!
When running the following, I unfortunately I get an error for both ipywidget version.
from dask_gateway import Gateway
gateway = Gateway()
options = gateway.cluster_options()
options

Here's what I get with ipywidgets 7.x:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
File /home/conda/filesystem/50d20409d0f86927105b69a2dfd2298cd115a880b6bb965f6d3e0719186801d4-20220922-025319-219615-2-dask/lib/python3.9/site-packages/IPython/core/formatters.py:921, in IPythonDisplayFormatter.__call__(self, obj)
    919 method = get_real_method(obj, self.print_method)
    920 if method is not None:
--> 921     method()
    922     return True

File /home/conda/filesystem/50d20409d0f86927105b69a2dfd2298cd115a880b6bb965f6d3e0719186801d4-20220922-025319-219615-2-dask/lib/python3.9/site-packages/dask_gateway/options.py:77, in Options._ipython_display_(self, **kwargs)
     75 widget = self._widget()
     76 if widget is not None:
---> 77     return widget._ipython_display_(**kwargs)
     78 from IPython.lib.pretty import pprint
     80 pprint(self)

AttributeError: 'VBox' object has no attribute '_ipython_display_'

And here's what I get with ipywidgets 8.x:
[Open Browser Console for more detailed log - Double click to close this message]
Failed to load model class 'VBoxModel' from module '@jupyter-widgets/controls'
Error: Module @jupyter-widgets/controls, version ^1.5.0 is not registered, however,         2.0.0 is
    at f.loadClass (https://eaerel.qhub.dev/user/eskild/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/134.bcbea9feb6e7c4da7530.js?v=bcbea9feb6e7c4da7530:1:74977)
    at f.loadModelClass (https://eaerel.qhub.dev/user/eskild/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/150.3e1e5adfd821b9b96340.js?v=3e1e5adfd821b9b96340:1:10729)
    at f._make_model (https://eaerel.qhub.dev/user/eskild/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/150.3e1e5adfd821b9b96340.js?v=3e1e5adfd821b9b96340:1:7517)
    at f.new_model (https://eaerel.qhub.dev/user/eskild/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/150.3e1e5adfd821b9b96340.js?v=3e1e5adfd821b9b96340:1:5137)
    at f.handle_comm_open (https://eaerel.qhub.dev/user/eskild/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/150.3e1e5adfd821b9b96340.js?v=3e1e5adfd821b9b96340:1:3894)
    at _handleCommOpen (https://eaerel.qhub.dev/user/eskild/lab/extensions/@jupyter-widgets/jupyterlab-manager/static/134.bcbea9feb6e7c4da7530.js?v=bcbea9feb6e7c4da7530:1:73393)
    at b._handleCommOpen (https://eaerel.qhub.dev/user/eskild/static/lab/jlab_core.1d4a092221669bba35bb.js?v=1d4a092221669bba35bb:2:996482)
    at async b._handleMessage (https://eaerel.qhub.dev/user/eskild/static/lab/jlab_core.1d4a092221669bba35bb.js?v=1d4a092221669bba35bb:2:998472)

It looks like we might need to upgrade jupyterlab_widgets as well. I'm currently trying to test this now.

Thanks for checking that out @iameskild , are you sure the env you ran had ipywidgets==7.7.1 ? I did run using that pin in the Dashboards env it seemed to work, but i might have missed something

That's interesting... I can confirm that I'm using ipywidgets ==7.7.1:
import ipywidgets
ipywidgets.__version__

'7.7.1'

We're also installing ipywidget in the JupyterLab Docker image. Do you think it would make a difference if we made the update there as well?

I dont think that would help, I thought conda-store didnt update the build but of you can match the versions from the module then thats not the case. I will debug this later as well


Document test file format

Using the genetic algorithm to create configurations is very helpful, however it would be nice if the test file format was documented.
Looking at this example: https://github.com/larsga/Duke/blob/dda63901a144a624ed7d68e3a17cc9403d77a70e/doc/example-data/countries-test.txt
It seems the format is

MATCH (+)/ NON MATCH (-)
ID1
ID2
???

What is the last value?

I did some more diving into the documentation and found the format specified in the Tuning Guide.
However, when I look at the source I see that the testfile is deprecated in favor of a LinkDatabase, however that seems to be not documented.  Related to #51 perhaps?


Inline formatting using python

I wrote a xbar plugin using python and am having trouble getting inline styling to work. I have attempted some of the examples provided in other issue tickets, but those all seem to be shell and when I try them using python the whole thing is treated as a string (ansi is not turned into formatting).
For example:
print(u'\u001b[34m blue \u001b[31m red | ansi=true')
Results in:

Thanks for reporting this @pnewell - we're working on it.

Duplicate of #699


Linear problems

As mentioned in #16, it is possible to make the code faster in a specific setting by exploiting linearity to define a sparse linear system. Namely, when $\boldsymbol{q}(x, y, t, u) = A_q(x, y, t)\boldsymbol{\nabla} u + \boldsymbol{B}_q(x, y, t) + \boldsymbol{C}_q(x, y, t)u$, $R(x, y, t, u) = A_R(x, y, t) + B_R(x, y, t)u$, and the boundary conditions are also linear. In this setting, we can write the PDE in the form
$$
\dfrac{\mathrm d\boldsymbol{u}}{\mathrm dt} = \boldsymbol A\boldsymbol u + \boldsymbol b
$$
for some matrix $\boldsymbol A$ and vector $\boldsymbol b$, and $\boldsymbol A$ is sparse. This could be worth implementing.
One issue would be thinking about the interface for this that doesn't disrupt the existing interface. Maybe an interface like
struct LinearFlux{F1, F2, F3}
  Aq::F1
  Bq::F2
  Cq::F3
end
(f::LinearFlux)(x, y, t, a, b, c, p) = Aq(x, y, t, p) * [a, b] + Bq(x, y, t, p) + Cq(x, y, t, p) * (a*x + b*y + c)
# (with obvious extensions for in-place methods)

struct LinearReaction{F1, F2}
  AR::F1
  BR::F2
end
(f::LinearReaction)(x, y, t, u, p) = AR(x, y, t, p) + BR(x, y, t, p) * u

# general form needed for the boundary condition functions

The functions Aq, Bq, Cq, AR, and BR would be FunctionWrappersWrappers, although the user can just define anonymous functions that are then wrapped (as is done already for the boundary functions). The user would then provide these structs so that the solver constructs the matrices $\boldsymbol A$ and vector $\boldsymbol b$. The number of non-zeros of $\boldsymbol A$ is already known, so pre-allocating (as a dualcache) this matrix is easy, simply storing the coordinate vectors (I, J, V) that define a sparse matrix. May be some difficulty handling the boundary conditions in this case.
The same methods used for computing $\boldsymbol A\boldsymbol u + \boldsymbol b$ would be used for solving the steady state case, where $\boldsymbol A\boldsymbol u + \boldsymbol b = \boldsymbol 0$ so that $\boldsymbol u = -\boldsymbol A^{-1}\boldsymbol b$.

Another feature of interest would be the case where the ODE is autonomous, in which case A and b only have to be computed once.

I'm not so sure this is all worth the effort anymore. A PR for this would be great, but it will not be me who does it.


Fix butterfly index

fixes bug introduced in #10087

(it would be nice to have a unit test that would have caught this if you can add one without too much effort)

(it would be nice to have a unit test that would have caught this if you can add one without too much effort)

I played around a bit, but actually can't reproduce the error with the Epochs testing dataset (neither epochs nor epochs_full fixtures)

Okay, I took a quick look -- looks like using raw works

@drammock looks like the test_ica.py failure seen on the Notebook tests is real, I can replicate locally with pytest mne/viz/tests/test_ica.py:
mne/viz/tests/test_ica.py:222: in test_plot_ica_sources
    fig = ica.plot_sources(raw)
mne/preprocessing/ica.py:1964: in plot_sources
    return plot_ica_sources(self, inst=inst, picks=picks,
mne/viz/ica.py:90: in plot_ica_sources
    fig = _plot_sources(ica, inst, picks, exclude, start=start, stop=stop,
mne/viz/ica.py:1106: in _plot_sources
    fig._draw_traces()
mne/viz/_mpl_figure.py:1721: in _draw_traces
    if self.mne.ch_selections is None and self.mne.butterfly
E   AttributeError: 'BrowserParams' object has no attribute 'ch_selections'

Thanks @drammock !


Write ATS for TG requirement 49

A containing Category Layer itself includes a Name by which a map portraying all of the nested layers can be requested at once. If a metadata description of this category composition exists then the MetadataURL for the Category Layer shall be provided.

I agree not machine testable, but when a category layer exists, the test suite can suggest to do a manual test


shortlinkv not working

Link
https://shortlinkv.com/CG8m
Version
Manifest-v2
What browser(s) are you using?
Chrome browsers (includes brave, edge, opera, etc)
What platform are you using?
Computer (Windows, Linux, MacOS)
(Optional) Anything else?
No response

The link has nothing to resolve, it has moved to the target page on its own


add sorting on peers page

I'm new to wxWidgets. sorry this sorting thing is kind of ugly but it kind of works.

Hey, that's neat! :) Great work!


add template that works well with phi-2

I'm not having a ton of success with the current templates. I'm guessing there's a way we can fake the system prompt with the chat template but it needs some experimentation. It doesn't look like there's an obvious way to do system prompt but maybe it could be passed as a first message.
For example we could try this template...
Alice: [System prompt]
Bob: OK, I will follow these instructions.
Alice: [user's first message]
Bob:
...

[ ] phi-2 should auto select this template

#69 fixes!


Grand calculated summary inside a repeating section

What is the context of this PR?
This PR adds support for using a Grand Calculated Summary within a repeating section. Within a repeating section a grand calculated summary is allowed to reference other calculated summaries within the repeating section, or non-repeating calculated summaries from other sections.
The corresponding validator PR ensures that a GCS can only reference a repeating CS if both reside in the same repeating section
(Note that the schema is actually valid without the validator changes, as those have added restrictions rather than enabled something new, however this PR is pointing at the validator branch to demo that the validator changes are compatible with these ones)
For this iteration, a repeating GCS using non-repeating calculated summaries with repeating answers is not supported.
How to review
It was decided that the refactor of return_to parameters into a class would be done separately in a follow on ticket, so it is not a separate piece of work here but to simplify review, the three main commits are

Add return to list parameters
Changes required to support grand calculated summaries in repeats
Functional tests

the return_to parameters have been extended to include return_to_list_item_id and return_to_list_name so that when using the change links to route to a non-repeating calculated summary and its answers, the continue button has sufficient information to return to the repeating section at the correct list item. These needed to filter through to answer/block/question/calculated summary contexts and handlers
How to test functionally
Use the test_grand_calculated_summary_inside_repeating_section schema and follow the guidance in the first section. Namely, do not add items to the list, that functionality is in the follow on card. But do check that the change links from the repeating sections for vehicles work as expected, you can change answers in both the repeating and non-repeating calculated summaries and return to the correct location, and that progress updates as expected when updating answers in the first section.
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

 Grand Calculated Summary: Support within repeating sections (5 SP)

@katie-gardner ignore.


Module parse failed: Unexpected character '@' (11:0)

Bug Report
Steps
I follow the steps described on the docs:

Add the two modules with yarn yarn add semantic-ui-react semantic-ui-css
Add the css on the app entry file import 'semantic-ui-css/semantic.min.css'

Expected Result
I expect to see semantic ui css applied
Actual Result
Webpack give me this error:
ERROR in ./node_modules/semantic-ui-css/semantic.min.css 11:0
    Module parse failed: Unexpected character '@' (11:0)
    You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
    |  *
    |  */
    > @import url('https://fonts.googleapis.com/css?family=Lato:400,700,400italic,700italic&subset=latin');
    | /*!
    |  * # Semantic UI 2.4.0 - Reset
     @ ./src/gui/renderer.tsx 13:0-39

Version
"semantic-ui-css": "^2.4.1"
"semantic-ui-react": "^1.2.1"
"webpack": "^4.43.0"

@Zikoel this issue has nothing to do with Semantic UI React. It looks like you are trying to process a CSS file with Webpack and do not have the correct loader configured in your webpack.config.js. I'd recommend taking a look at your loader rules and see if you have something set up. I'd recommend asking your question on Stackoverflow with a webpack tag and including your config file.
Closing since this is not an issue with this library.

While it is true that this error is not to do with semantic-ui, it is exactly the error you will get if you already have a webpack build and then follow the instructions to add semantic-ui-react as described at https://react.semantic-ui.com/usage. So it might be worth adding a note to the docs.
FWIW I got it working by adding url-loader so that my webpack.config.js contained:
      {
        test: /\.css$/,
        use: [
          { loader: 'url-loader' },
        ],
      }


Designing A Logo For Scrape-ML

Hi Admin,
I'm interested in contributing to your project as part of GSSoC. I've been following your work and believe my skills align well. You can find my portfolio here: (https://sites.google.com/view/uibymehtab) and LinkedIn (https://www.linkedin.com/in/mehtabarkhan/)
Thanks,
Mehtab

Could you raise simillar issue on stackoverflow repo in same org

Could you raise simillar issue on stackoverflow repo in same org

give me the stackoverflow link please

Hello Sangati here,
I would like to help design logo for Scrape -ML kindly assign me

Please assign this issue to me. I'm a GSSOC'24 Contributor

pls, assign me the issue. I will make sure the task is done.

pls, assign me the issue. I will make sure the task is done.


JSON-RPC errors not working

The JSON-RPC responses that contain an error ("error" field within the response is not null) are simply returned as if they were correct responses:
transforms.push(function(data) {
    return data.id === id ? data.result || data.error : null;
});

I have forked your repo and I propose to change that line of code for something similar to the following block:
    if (data.error !== null) {
        throw data.error;
    }
    if (data.id !== id) {
        throw '[json-rpc] wrong response ID, expected = ' + id + ', received = ' + data.id;
    }
    return data.result;

In my opinion, it would be better to deal with this problem from a different perspective (maybe using interceptors instead of transformers?); but this might be a quick improvement over the existing solution.
Please let me know what you think.

I think that's a good way to handle errors (throwing them up the chain). There are a bunch of TODOs in the code that I never got to, one of which is about waiting for the interceptors stuff to be stable (which it now is). Feel free to submit a pull request and I'll merge it in, and I'll get back to those TODOs in a bit.
Thanks!

Ok, thanks for your opinion!
I am currently struggling with the tests. I am not a master with Jasmine, but I cannot make them work "out-of-the-box"; this is, I forked the repo, installed NPM and Bower dependencies executed grunt and the tests fail. Am I doing anything wrong?
By the way, I can help you with the TODOs. I am really interested on this library since I am using it as the main communications component in my project.


Destructuring for pure-component

Would anyone be interested in an option for the pure-component transform that would destructure the props where possible - i.e. when there's no {...this.props} or doStuff(this.props) and only keys of this.props are used?
I would be down to open a PR if so.
So
render() {
  const { prop1 } = this.props;
  return <div prop1={prop1} prop2={this.props.prop2} />;
}

Would become
({ prop1, prop2 }) => <div prop1={prop1} prop2={prop2} />;

Opened PR #94 - closing


Allow third parties to easily deploy custom playgrounds

Summary
This PR includes a number of improvements that make deploying your own playground significantly easier. It allows you to better customize which crates you allow. It further features a deployment executable that manages deploying a self-contained playground on EC2 serving content over HTTP. This eliminates all manual setup steps for instances.
Customizations

Can limit the number of top crates to include in your playground (set to zero to include include no top crates).
Can omit cookbook crates
Combining the previous 2 options and tweaking crate-modifications.toml, you can deploy a playground that serves only the crates in your organization.

Automated deployment
Our deployment architecture looks like the following:
Manual one-time setup

Route53 hosted zone with an "A" DNS record pointed to...
... an API Gateway. This API gateway has CORS enabled (as the playground does), uses a an ACM certificate for HTTPS
with our custom domain name. Our config simply proxies all HTTP requests to...
... an elastic IP.

Automatic deployment

Compile ui, frontend, deployment app, rust-playground-top-crates
Run rust-playground-top-crates, build docker images and publish them
Spin up and tag an EC2 instance and install prereqs on the machine with a user-data script.
Copy ui, frontend to the EC2 instance.
run fetch.sh on the new instance
systemctl start playground on the EC2 instance.
Assign the elastic IP to the new instance
terminate all tagged instances that aren't the new instance.

This approach has a number if differences with today's model:

No cron jobs to sync images. Images get downloaded one time on machine setup. To update the crates, run another deployment.
No manual setup for EC2 instances
AWS manages the HTTPS certificate in ACM, so you don't have to run a certbot cron job to renew it.

Binaries build under a workspace
ui, deployment, and top-crates now reside under a [workspace]. This improves build times as dependencies are shared and reused across components.
This is a dump of what we have working on our end, so there's probably a bit more work to migrating the official playground to using this model.

I have not read through this at all, just some high-level comments.

I'm sympathetic to the general goal presented here.
I'd much rather use the (relatively new) Ansible playbooks instead of having a completely disjoint deploy mechanism.

Closing this request until I've reworked the deployment situation...


Adds selinux flags to docker-compose config files

Volume definition in docker-compose file doesn't allow :z flag in long format.

Volume definition in docker-compose file doesn't allow :z flag in long format.

Also I did not try that on any other distro than Fedora, so I have no idea how that behaves on distros without Selinux.

Also I did not try that on any other distro than Fedora, so I have no idea how that behaves on distros without Selinux.

https://issues.redhat.com/browse/DRFT-111

https://issues.redhat.com/browse/DRFT-111

I think it was discussed last week that this was working fine. Merging now.


Chef run fails when node server up which does not have schedulable attribute set.

Hi @IshentRas
I ran into this one while provisioning my test VMs with version 1.10.22 of the cookbook.
The first chef-run works fine, but the second one fails with the following stack trace:
==> master: Chef Client failed. 5 resources updated in 14 seconds
==> master: [2016-12-19T10:29:15+00:00] FATAL: Stacktrace dumped to /tmp/vagrant-cache/chef/chef-stacktrace.out
==> master: [2016-12-19T10:29:15+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
==> master: [2016-12-19T10:29:15+00:00] ERROR: execute[Set schedulability for Master node : node-1] (cookbook-openshift3::master_config_post line 82) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
==> master: ---- Begin output of /usr/bin/oadm manage-node node-1 --schedulable=${schedulability} --config=admin.kubeconfig ----
==> master: STDOUT:
==> master: STDERR: Error: invalid argument "" for --schedulable=: strconv.ParseBool: parsing "": invalid syntax
==> master:
==> master: Usage:
==> master:   oadm manage-node [options]
==> master:
==> master: Examples:
==> master: 	# Block accepting any pods on given nodes
==> master: 	oadm manage-node <mynode> --schedulable=false
==> master:
==> master: 	# Mark selected nodes as schedulable
==> master: 	oadm manage-node --selector="<env=dev>" --schedulable=true
==> master:
==> master: 	# Migrate selected pods
==> master: 	oadm manage-node <mynode> --evacuate --pod-selector="<service=myapp>"
==> master:
==> master: 	# Migrate selected pods, use a grace period of 60 seconds
==> master: 	oadm manage-node <mynode> --evacuate --grace-period=60 --pod-selector="<service=myapp>"
==> master:
==> master: 	# Migrate selected pods not backed by replication controller
==> master: 	oadm manage-node <mynode> --evacuate --force --pod-selector="<service=myapp>"
==> master:
==> master: 	# Show pods that will be migrated
==> master: 	oadm manage-node <mynode> --evacuate --dry-run --pod-selector="<service=myapp>"
==> master:
==> master: 	# List all pods on given nodes
==> master: 	oadm manage-node <mynode1> <mynode2> --list-pods
==> master:
==> master: Options:
==> master:       --dry-run=false: Show pods that will be migrated. Optional param for --evacuate
==> master:       --evacuate=false: Migrate all/selected pods on the node.
==> master:       --force=false: Delete pods not backed by replication controller. Optional param for --evacuate
==> master:       --grace-period=30: Grace period (seconds) for pods being deleted. Ignored if negative. Optional param for --evacuate
==> master:       --list-pods=false: List all/selected pods on the node. Printer flags --output, etc. are only valid for this option.
==> master:       --no-headers=false: When using the default output, don't print headers.
==> master:   -o, --output='': Output format. One of: json|yaml|wide|name|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... See golang template [http://golang.org/pkg/text/template/#pkg-overview] and jsonpath template [http://releases.k8s.io/release-1.3/docs/user-guide/jsonpath.md].
==> master:       --output-version='': Output the formatted object with the given group version (for ex: 'extensions/v1beta1').
==> master:       --pod-selector='': Label selector to filter pods on the node. Optional param for --evacuate or --list-pods
==> master:       --schedulable=false: Control pod schedulability on the node.
==> master:       --selector='': Label selector to filter nodes. Either pass one/more nodes as arguments or use this node selector
==> master:   -a, --show-all=false: When printing, show all resources (default hide terminated pods.)
==> master:       --show-labels=false: When printing, show all labels as the last column (default hide labels column)
==> master:       --sort-by='': If non-empty, sort list types using this field specification.  The field specification is expressed as a JSONPath expression (e.g. '{.metadata.name}'). The field in the API resource specified by this JSONPath expression must be an integer or a string.
==> master:       --template='': Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
==> master:
==> master: Use "oadm options" for a list of global command-line options (applies to all commands).
==> master: ---- End output of /usr/bin/oadm manage-node node-1 --schedulable=${schedulability} --config=admin.kubeconfig ----
==> master: Ran /usr/bin/oadm manage-node node-1 --schedulable=${schedulability} --config=admin.kubeconfig returned 1
==> master: [2016-12-19T10:29:15+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

I believe that the failing code is this snippet from recipe[master_config_post]:
  execute "Set schedulability for node : #{nodes['fqdn']}" do
    command "#{node['cookbook-openshift3']['openshift_common_admin_binary']} manage-node #{nodes['fqdn']} --schedulable=${schedulability} --config=admin.kubeconfig"
    environment(
      'schedulability' => !nodes.key?(:schedulable) && node_servers.find { |server_node| server_node['fqdn'] == nodes['fqdn'] } ? 'True' : nodes['schedulable'].to_s
    )
    cwd Chef::Config[:file_cache_path]
    not_if do
      master_servers.find { |server_node| server_node['fqdn'] == nodes['fqdn'] } ||
        Mixlib::ShellOut.new("oc get node | grep #{nodes['fqdn']}").run_command.error?
    end
  end

When:

the 'schedulable' attribute is not set for the node
and the node is not master
then the environment schedulability will evaluate to empty string
which makes the oc adm manage-node fail

We should either make the schedulable attribute mandatory or find a default value that does not evaluate to an empty string.
As a workaround, I set the schedulable attribute for all openshift nodes in my VM.

fixed by https://github.com/IshentRas/cookbook-openshift3/pull/33


Move runtime_tables, runtime_table_offset out of LookupConfiguration

runtime_tables and runtime_table_offset do not belong in LookupConfiguration, which is used to set up the general structure of the constraints without specifying the layout of the actual circuit. It would be best to move them to LookupConstraintSystem, and store only a max_runtime_table_width in LookupConfiguration.

it's actually not really clear to me why there's a separate LookupConfiguration type :o is it just a semantic distinction or is it important that there are values that must live in it instead of LookupConstraintSystem?

It's important that they are distinct: one is the 'shape' of the constraint system from e.g. pickles' perspective, and the other contains the actual values, tables, etc. that are to be used.


htmlPy with PySide2

Hi,
is there a way to use htmlPy with PySide2. I'm asking because I use python 3.6 and the latest PySide release has at least 3.5 support or did i miss something?

I' facing the same problem as well.

You can get PySide for Python 3.6 at Here and use pip to install.

Also, on ubuntu you can use apt install python3-pyside to install Python3-compatible PySide.

I'm interested in an upgrade since the QtWebKit in PySide 1.2.4 doesn't support flexgrid (as far as i can tell) that is used by bootstrap...

Last commit 3 years ago. Sadly I dont think we're ever going to see this solved. :(


12.1 Mac Wallet WATCHDOG_EXPIRED but Really ENABLED

I spun up three masternodes Dec 19 around 4pm. The following morning, all masternodes were running as expected but the status in my wallet was WATCHDOG_EXPIRED for all three masternodes. All three nodes were paid several times throughout the 15 hours or so they have been running. They are in fact ENABLED on the network according to each other. I believe the actual problem may be the desktop wallet.
yQ3PAPRw8gAZNU5CtUaxziyFxb3kqukj2P
yiHKzBUKCf2inMHz4t4e5UipbZQQ2naTwi
yXbSxmuv4ji4HkiGgQqs2CdXbegEEYvSpe

I have the three debug.log files from the masternodes as well as the wallet itself if needed. I am not sure what other information I should provide but I'll be available to provide everything I can.

4pm in what timezone ?
The network is currently undergoing a protocol upgrade that could have caused issues like that but I don't know if it spans the time when this was observed.

If you have "new" wallet (70204) but "old" MNs (70203) then such a wallet will not be able to see watchdogs from your MNs

Apologies: ET zone / NYC.
More info. My wallet are masternodes were all on 70203. Though I just ran a script a minute ago to upgrade them all to the latest build from a few hours ago. That may impact the protocol, if it's new.
I was able to make my wallet see them all as ENABLED after a simple wallet restart. I did not remove mncache.dat.

If it happened this morning I suspect it's somehow related to the protocol update even if your wallet wasn't upgraded at the time.  It's possible all your peers upgraded to 70204 (especially if you were peered with Holger's nodes) and there was no 70203 path in the network between your wallet and your masternodes.

@tgflynn I bet you are right. I'm in the process of moving to the new protocol now anyway. Perhaps this issue can be closed?

Ok some more info. All three masternodes and my wallet are on 70204. After it was sync'd, my wallet showed all nodes as ENABLED. Now, maybe 30 minutes later, they all show as WATCHDOG_EXPIRED. Further, the wallet shows all the masternodes as on 70203.

You may need to restart the masternodes (ie. with start-alias) after the protocol upgrade.

Hmm, interesting... have you issued "masternode start-many" for them?

Ugh, I never issued a remote start. I forgot a remote start is needed after a protocol change. That said, the wallet was entirely misleading.

I only realized this after running sentinel manually and it yelled at me :)

Closing this issue because it probably had to do with the protocol change originally, and then my need for a remote start.
Thank you all for the help.


Remove commas ?

@dippydodge

Parse error: syntax error, unexpected ')' in
/home/onerxusi/public_html/wp-content/plugins/kredeum-nfts/admin/media-list/actions.php on line 68
i have this error any help?

related to "," commas at the end of array list, before  ")" parenthesis
different PHP version treat these differently ? error or ok ?

Trailing comas are supported by php since PHP 7.3 version
Wordpress supports PHP 7.3 since Wordpress 5.0 version
Wordpress dropped support for PHP 5.2, 5.3, 5.4, 5.5 since Wordpress 5.2 version
Current version of Wordpress : 6.0.1 ( supports PHP 5.6 to PHP 8 )

=> determine wich checks are adding trailing comas, and see if desactivating this precise auto formater causes bugs
=> determine if the support of previous version of PHP 7.3 is consistent

https://laravel-news.com/php-trailing-commas-functions
https://fr.wordpress.org/about/requirements/

Proposition :

remove commas
add "--config-set php_version 50639" command in wordpress checks script to set checks to php 5.6.39 version

=> wordpress/package.json l.13-14
"fix": "vendor/bin/phpcbf plugins/kredeum-nfts --ignore=vendor --ignore=loco-translate --extensions=php --standard=WordPress --config-set php_version 50639",
"format": "vendor/bin/phpcs plugins/kredeum-nfts -n --ignore=vendor --ignore=loco-translate --extensions=php --standard=WordPress --config-set php_version 50639"