[5.9] Allow function calls on non-objects in higher order messaging

This PR adds the ability to call built-in PHP functions on scalar/null/array (non-object) types in a collection through Higher Order Messages.
Example
$collection = collect(['abc ', ' def  ', 'g h i  ', null]);

$collection->reject->is_null()->map->trim();

// Current:

PHP Error:  Call to a member function is_null() on string

// Output with this PR:

=> Illuminate\Support\Collection {
     all: [
       "abc",
       "def",
       "g h i",
     ],
   }

I know you can pass methods to map simply like $collection->map('trim'); however the problem is the key is forwarded to the function as opposed to the value Issue #25549. The idea here would be for the methods to only be called on the value.
Useful functions

is_array
is_bool
is_int
is_null
is_numeric
filter_var

$collection = collect(['abc', 'def<EMAIL_ADDRESS>null]);

$collection->filter->filter_var(FILTER_VALIDATE_EMAIL);

/**
=> Illuminate\Support\Collection {
     all: [
       2 =><EMAIL_ADDRESS>     ],
   }
**/

dump (Can dump values to the dump server in the middle of a collection pipeline)
trim
array_values

collect([['a' => 'b', 'c' => 'd'], ['e' => 'f']])->map->array_values();

// Would output: [['b', 'd'], ['f']]

Drawbacks

Functions that are haystack, needle (value) as opposed to taking the value as the first parameter. (e.g. explode() or strpos()). However, I think there are enough valuable functions to promote adding this functionality to core.

Change
We just need check if an item is not an object to cover scalar, null, and arrays in Illuminate\Support\HigherOrderCollectionProxy’s __call method. The only difference I see in behavior is passing null would fall in trying to call the function on null as opposed to a method being called from null (both would result in an error). I'm not sure if this would qualify as a BC, but this would be for 5.9) h/t @staudenmeir for the idea of using ! is_object()

Please add a test.

@staudenmeir done, thanks!

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


updating file path

Closes #790
Changes proposed in this PR:

Fixing incorrect file path

so random, not even sure this had any implications at all but better be sure


⚠ Jenkins Plugins Artifactory has degraded performance

In 070b88c, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1236 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 31a3eaf after 48 minutes.


[CL Message Audit]: MsgUnlockAndMigrateSharesToFullRangeConcentratedPosition [2/2]

Clickup Checklist:
https://app.clickup.com/37420681/v/dc/13nzm9-19570/13nzm9-36390
What is the purpose of the change
This PR includes changes made from the internal audit of MsgUnlockAndMigrateSharesToFullRangeConcentratedPosition.
This is the refactor portion of the audit.
Brief Changelog

Refactors the routing function:

We used to do validation and then route to the respective migration function
We now route first and then do validation within the migration function itself

This is to prevent issues in the future in case these migration functions are use directly and not through the router

Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (yes / no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (yes / no)
How is the feature or change documented? (not applicable   /   specification (x/<module>/spec/)  /  Osmosis docs repo   /   not documented)

Would it be possible to separate the refactor from the rest of the nit / comment changes please?
I'm having a hard time telling what I should focus on reviewing in mode detail vs what can be a quick skim

@p0mvn split it up so that this PR is the refactor and the following PR https://github.com/osmosis-labs/osmosis/pull/5178 is just the nits / test additions / etc


citation widget on PomBase publication page

if this is possible...

It's more or less working on my desktop.  I've had to reformat a bit to get it looking OK.
How's this?
https://desktop.kmr.nz/about/pombase-and-collaborative-publications
(Sorry, slow to load)

Mouse-over:

For comparison, it looks like this at the moment:

I've also updated the Citing PomBase page:
https://desktop.kmr.nz/about/citing-pombase

It's more or less working on my desktop.

Sometimes the new badges don't display unless you reload the page.  I'm working on that now.

I've also updated the Citing PomBase page:
https://desktop.kmr.nz/about/citing-pombase

on this page we should update the recommended GO citation to the 2023 publication

You could also add to the preprints.

You could also add to the preprints.

Which preprints?

Sometimes the new badges don't display unless you reload the page. I'm working on that now.

I think I've fixed that now so I'm going to commit the changes and update the main site.
I'll make your changes first.

At the top of the publicatins page. The mondo preprint has been cited >40 times I think....

At the top of the publicatins page.

Ah, sorry!  I misread your comment as "You could also add the preprints" and was confused.
It didn't occur to me that the pre-print would have DOIs.  Good plan!  This will be on the main site in a little while:

I noticed a typo on the "citing PomBase" page here

the 'i' is missing in "curation tool"

I noticed a typo on the "citing PomBase" page here

Thanks!  I'll fix that now.

I think this is all done now.

Thanks, it's a bit silly but funders love metrics. It looks pretty anyway ;)


TSC Meeting (01 Mar 2022): AWS follow-up, v3.7.0 preparation

March 2022 @StackStorm/tsc 1 hour planned meeting: Tuesday, 01 Mar 2022, 09:30 AM US Pacific.
See #33 for more info about how to join.
(TLDR; Zoom link: https://us02web.zoom.us/j/81082101702?pwd=N1V4TWdYRVQ4SXBsaFh1TFYvVDA0UT09)
Meeting host: @nzlosh
Meeting Agenda
StackStorm AWS account follow-up ~(20min)

See previous meeting for the issue description and more context: https://github.com/StackStorm/community/issues/97
Update: Per Slack and @punkrokk the AWS FOSS credits expiration date is 31-July-22, not 31-March-22 as thought before
Discuss the AWS account/ownership migration
Discuss the ST2 infra future in the AWS

StackStorm v3.7.0 release preparation ~(40min)

Release Manager: @cognifloyd
Release Assistant: still missing a volunteer. Who from @StackStorm/maintainers?
Target month: March 2022
Project & Roadmap: https://github.com/orgs/StackStorm/projects/23

Some follow-up and stats from the AWS discussion today.
AWS Reducing costs project: https://github.com/orgs/StackStorm/projects/27
AWS monthly running costs for the latest 3mo: Dec '21, Jan '22, Feb '22:

AWS daily costs for the Februrary '22 (avg ~$21/day):

cc @bishopbm1

Meeting minutes for TSC Meeting (01 Mar 2022): AWS follow-up, v3.7.0 preparation
Attendees:

Bradley Bishop
Ankur Signh
Eugen Cusmaunsa
Jacob Floyd
Amanda (amanda11)
Carlos (nzlosh)
AJ (guzzijones)
Saurav Kumar

AWS account ownership
Bradley Bishop of Encore Technology has talked internal about taking ownership of the StackStorm AWS Account (child) under the Encore Technology (parent) account.
A condition to Encore Technology taking on the StackStorm AWS account, they want to see a project plan outlining the actions the StackStorm project will take to reduce AWS operational costs.
AWS Actions
The TSC has agreed to create a Gtihub project board and fill in tasks that lead to the reduction of these costs.
Bradley is in contact with JP and will determine what day to day effort is required to manage an AWS child account.
AJ (guzzijones) has been approved to work on StackStorm related work by his company and has offered to work on migrating  API and documentation websites from AWS S3 to github pages.
Bradley offered his help with LDAP hosting in AWS if needed.  Eugen suggested LDAP could be replaced with another authentication solution to help reduce AWS costs.
Bradley needs to determine how child/parent ownership works and long with other AWS details.  He'd like to target mid to late June to carry out the AWS migration.
v3.7 Release Actions
Carlos (nzlosh) will be release assistant for v3.7
Carlos (nzlosh) will follow-up on issues #5152 #5143 and #4924 which are blocked in in progress.


Update Posts “20220928-dynamic-programming-vs-memoization”

Automatically generated by Netlify CMS

👷 Deploy Preview for monetaboot processing.

Name
Link

🔨 Latest commit
27d5a7185a6c05f3a184b15bc3bea63546400f75

🔍 Latest deploy log
https://app.netlify.com/sites/monetaboot/deploys/633ba0891cc9480009d51097


Certificate issued to work.azdo.io is expired

Describe the Bug
Certificate issued to work.azdo.io is expired on 3/11/2021
Steps to Reproduce
Open an URL referring to Azure Boards and you get the error.

Fixed! Thanks for reporting!


bulk event create

still need to add a test

this was doing 5 queries per event, now it does 3 total.


Release v1.31.0

Release v1.31.0 is a smaller release containing minor and improvements and bug fixes to the Packer module's usage of service accounts.

Discussion with @tpdownes, He is working on docs update as hotfix but does not want to hold release.

Good to go from my side. Only todo for this PR would be,
Update the Release title and description.


Added config sliders.

Adds sliders as a config option for int types.
Simply add a range parameter to the ConfigItem annotation.
@ConfigItem(
	keyName = "sampleslider",
	name = "Sample Slider",
	description = "Just a Sample",
	range = { 17, 35 }
)
default int sampleSlider()
{
	return 35;
}

As we do not need them atm for anything there was no reason for this PR to be merged. Maybe you can make use of it for your PR?


chore: Typedoc

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Periodic tasks add only if

I use django-q for some background tasks. The tasks looks like this in pseudocode
def task(param)
  if param:
    do_something() #runs instantly
  if not param:
    do_something_else() #takes a while to run
    time.sleep(3600)

If I run the task every 5 minutes and param == False for a few times in a row I will create a lot of tasks and my queue will overflow. Is there a way that only a new task is created if there is no task running, taking into consideration the timeout?

Would it be possible to have this task schedule a second task which exectes the long-running code?
That way, the task that is scheduled to run every 5 minutes can check the current queue, and decide whether to schedule another long-running task. Either way, it will finish relatively quickly.

I cannot get this to work. I need to pass an object into the function, which is causing me problems, since it can not be pickled


First try w/El Cap... kernel panic after using CAT 2.2.2

I get a kernel panic upon booting after using CAT 2.2.2, (does not boot after install).
MacBookPro7,1 (mid 2010 MBP 13" 2.4)
IO Gear dongle (used to work great with CAT & 10.10)
I did a clean install of 10.11 about a month ago, I went without continuity. I've since updated to 10.11.1.
Been reading and decided to try it since others said 2.2.? was working with dongles.
Sometimes I have had to take out dongle and put back it for it to be fully recognized by my mac (since I got it). I am not entirely sure if there is sometimes an intermittent issue w/my USB ports, I do have a hardware issue with the trackpad, mostly the button is not working properly, may replace it soon.
Sometimes my mac recognizes the dongle (YES on low power), but, I may get this error w/CAT 2.2.2 "Verifying Bluetooth version...          NOT OK. Your hardware doesn't support Bluetooth 4.0, necessary for Continuity. Current LMP Version=4, expected 6."
Upon going through all the steps as outlined, and getting an OK on 4.0, I run CAT and I get these errors: "Backing up original drivers...          cp: /System/Library/Extensions/IOBluetoothFamily.kext/: unable to copy extended attributes to /Users/mbenjamindavid/KextsBackupBeforePatch/IOBluetoothFamily.kext: Operation not permitted
cp: /System/Library/Extensions/IO80211Family.kext/: unable to copy extended attributes to /Users/mbenjamindavid/KextsBackupBeforePatch/IO80211Family.kext: Operation not permitted
OK. Wi-Fi and Bluetooth kexts were backed up in '/Users/mbenjamindavid/KextsBackupBeforePatch'
Backing up patched drivers...           cp: /System/Library/Extensions/IOBluetoothFamily.kext/: unable to copy extended attributes to /Users/mbenjamindavid/KextsBackupAfterPatch/IOBluetoothFamily.kext: Operation not permitted
cp: /System/Library/Extensions/IO80211Family.kext/: unable to copy extended attributes to /Users/mbenjamindavid/KextsBackupAfterPatch/IO80211Family.kext: Operation not permitted"
It states the files were backed up even though it was not permitted.
In any case, it all seems to be installing, but, when I restart at the end it will not boot, I get this kernel panic:

It restarts and gets this error every time.
I, fortunately, have the 10.11.1 full installer on a thumb drive, so, I was able to recover by installing 10.11.1, however, I have tried 3 times to use CAT 2.2.2 and get the same results every time. On the 3rd try I even tried deleting my VPN settings and VPN Unlimited app (& restart), as it was a startup app, made no difference.
(I'm not a dev.)

I have the same exact issue with the same Macbook Model and Bluetooth Dongle. I'm looking at the kexts over the weekend.

good to know! ...at least it's not some mysterious issue with some app, but, I've tried to minimize utilities or anything that starts up with the mac.

you two are not the only one, see issue #240 ( https://github.com/dokterdok/Continuity-Activation-Tool/issues/240 )

Oh, I missed that when I was looking for similar issues...I could have just posted there instead.

I am having the same problem. Is there a way to reverse the install without reinstalling OSX from a backup or doing a clean install?

Want to close your issue so people can just post there?


custom formatters don't work with 1.0.0-rc2

The fmt argument here: https://github.com/SlexAxton/messageformat.js/blob/v1.0.0-rc.2/lib/index.js#L253
is shadowed by the fmt variable here: https://github.com/SlexAxton/messageformat.js/blob/v1.0.0-rc.2/lib/index.js#L274
but the reduce callback wants to use the first one: https://github.com/SlexAxton/messageformat.js/blob/v1.0.0-rc.2/lib/index.js#L275
This fixes it:
var fmtKey = Object.keys(compiler.formatters);
if (fmtKey.length) obj.fmt = fmtKey.reduce(function(o, key) { o[key] = fmt[key]; return o; }, {});

There's no branch for this tag, so I can't send in a pull request.

Thank you for spotting this! The branch for this ended up here due to its origin as #138. Would you be ok submitting a PR against that branch, or would you prefer I add a commit to that effect myself?

I think it'd be quicker if you commited it.

Fixed in RC3.


Upgrade Binance Perpetuals to v2.1

The rationale behind this enhancement was discussed in this forum thread: https://forum.hummingbot.org/t/hip-cex-connectors-revamp/212

Hey can this be assigned to me?
I'm an engineer who has been working in the industry for 5 years and strong in python coding.
Can talk more about it on discord if you want.

I would like to be assigned this ticket

@HODLER-CODING, you have been assigned to this issue. Thank you for your contribution.

https://github.com/hummingbot/hummingbot/pull/5814
PR submitted thanks

I would like to be assigned this bounty and solve the remaining problems.

Removing the bounty of this issue.

https://github.com/hummingbot/hummingbot/pull/5976 Merged

Enhancement has been deployed to development branch and will be available on the next release version 1.12


Fix data races, convert to Go modules, various minor fixes

Closes #20.

Coverage decreased (-0.2%) to 36.989% when pulling d72e71e48c52b903caf6d9ff241064b0c0e09bf7 on knweiss:knweiss into c7bd0f5263ed02b4f16ef63a463183dd4c01ed74 on mjtrangoni:master.

@knweiss Thanks for fixing and refactoring!


Case sensitive secrets

General information

App version: 0.2.7
App source: F-Droid
Android Version: 7.1.2 (LineageOS 14.1)

I was migrating from Google Autenticator, so I've copied its sqlite database from /data/data/** and created otp_accounts.json file in the format andOTP expects. However, only those secrets that were in uppercase generated the same codes as Google Authenticator, those that were lowercase generated wrong codes. As soon as I've converted all lowercase secrets to uppercase, they've all started to generate correct codes.
Following generates wrong codes:
{"secret":"xyz","label":"user@gmail.com","period":30,"digits":6,"type":"TOTP","algorithm":"SHA1"}

Following generates correct codes:
{"secret":"XYZ","label":"user@gmail.com","period":30,"digits":6,"type":"TOTP","algorithm":"SHA1"}

I haven't read the spec whether these codes should always be uppercase, but looks like they should.
I think this is something that can/should be fixed (converted to uppercase on backup restoration), but feel free to close this if it is not relevant.

To be honest I never encountered lower-case secrets. Usually they should be encoded as Base32-String which should always be upper case.
I will add a conversion to upper-case when importing accounts.

Import from JSON was literally the only case where I forgot the conversion to upper-case.
When manually adding an entry or scanning a QR code the secret is always converted to upper-case.
@nazar-pc Thanks for finding this bug ;)

Thanks for fixing this issue and for the app!


Unpin System.Runtime.CompilerServices.Unsafe

see dotnet/aspnetcore#24937

(Ignored irrelevant test failure)


Persistent tasks

Add persistence for tasks

Coverage decreased (-1.2%) to 45.73% when pulling 3583fd0b9e569aaf90b25427c50174e14ee26e41 on stgleb:persistent_tasks into ede4e68f77af3b5ffa5ff047442d9b8e48aef273 on supergiant:master.

Please, review all the error messages and imports formatting.


Dataset view is slow

I've identified the following problems:

[ ] timeseries are loaded in their entirety (linked issue: #150)
[ ] most operations involving timeseries (changing timeseries offset, fuse, onSetName, onSetUnit) work in the frontend, move them to backend

currently we load the whole dataset, modify it in frontend, and send it back to the backend. This won't work with streaming

[ ]  (un)locking datasets needs multiple requests, reduce them to one

Removed the locking feature.


Start syslog-ng before runit, and stop after runit.

Use Case: I had a problem with my app dropping logs to the central log server which syslog-ng was forwarding to, when containers were restarting.
Problem: When syslog-ng is managed as an runit service, application logs may be
lost during shutdown, when the syslog-ng service stops before the app
exits.
Solution: This change uses the my_init.d directory to manage syslog-ng at a lower
runlevel than runit.

Request for comments?

@hyperknot or @kingdonb ?

Sorry, this doesn't make sense for me. The key line is:
/etc/init.d/syslog-ng start

In there, telling System V init to start the service, but we are not even using sysvinit. Our init system is runit.
If you'd like to prioritise services maybe we can do some kind of kind of support for 10_syslog_ng, 20_cron, 30_sshd like naming convention and start them manually or something similar, but it's not possible to start something before the init process.

@hyperknot This is just piggybacking on the default init script, which takes care of the pid file and a status check to wait for a successful syslog startup, and allows us to signal the process to gracefully stop. It is less code to maintain, the original (removed) script in the .runit file was essentially copied from this script to begin with. It does not cause any interference, or fork a whole sysvinit.

@sundbry but the default init script should be a sequence of blocking scripts, that is not background processes.
The question with background processes is that what is their parent process and who is supervising them.

I believe this functionality is already available via runit without removing syslog-ng as a runit service.

@jwilson8767 the suggested runit style solution of coding the syslog dependency into the application's init script does not solve the shutdown order dependency. The primary purpose of this PR is to prevent application logs from being truncated at container shutdown when syslog-ng stops before the 'userspace' services have exited.

What is the consensus around this PR?

I haven't had a chance to look at it again, but I'm inclined to say go ahead and merge it because it looks like the submitter has done his homework, and truncating the logs is kind of a nasty problem.

There should be a way to ensure that starting syslog-ng via init.d still results in the creation of the appropriate pid file, or whatever runit is looking for, to result in sv status being able to report back on the status of the daemon.  How soon are we trying to push 0.9.23?

0.9.23 will be released this week, but this can always be pushed to the next release.

I really don't agree with this PR, as it introduces two separate service supervisors into one container. Making everything double, complicated and bloated.

It's not really two separate supervisors though is it?
Well... but it is though, right?  The processes that runit didn't spawn, it also can't reap forked children from.  So it's actually important that the processes spawn from runit to the whole "supervisor cleans up after its children" proposition.  That's part of the reason why runit services are supposed to be foreground processes, because it's waiting for them to exit, "supervising" them, and restarting them as needed when they exit without being stopped.
Is there any way to prevent the log truncation without going outside of runit?

That's a pure mental point about the two separate supervisors, the root
supervisor is my_init, which cleans up after its children in its shutdown
routine. Runit has it's utility in making user applications very convenient
to program to start and stop. Beyond that, it has it's limitations, as in
this situation where shutdown sequencing is important.
On Tue, Oct 31, 2017 at 11:43 AM, Kingdon Barrett<EMAIL_ADDRESS>wrote:

It's not really two separate supervisors though is it?
Well... but it is though, right? The processes that runit didn't spawn, it
also can't reap forked children from. So it's actually important that the
processes spawn from runit to the whole "supervisor cleans up after its
children" proposition. That's part of the reason why runit services are
supposed to be foreground processes, because it's waiting for them to exit,
"supervising" them, and restarting them as needed when they exit without
being stopped.
Is there any way to prevent the log truncation without going outside of
runit?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phusion/baseimage-docker/pull/425#issuecomment-340865869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAhhmRcX0ihN3g5R3g9UeBN1TdfZPJA2ks5sx2pIgaJpZM4OLboU
.

I agree with @hyperknot that the change makes me uncomfortable, but truncated logs makes me unhappy too.  I would be more comfortable if it added documentation of the problem with runit.
As it is now, if we merge this change then users who want to restart syslog-ng need to know at least that the syslog can't be restarted interactively with an sv restart and will need to be restarted a different way.  That isn't documented anywhere.
@sundbry Would you be willing to add a commit to the README that describes the shutdown sequencing issue (since you appear to know intricately how it fails) and explains why the decision to launch syslog a different way was made?
I'm OK with the idea of doing a different thing where it's appropriate, but it can't be undocumented.  We go back and look at code all the time and say "why was this unusual thing done this way?" and if we can't figure it out from the comments in the code or the README, we'll end up put it back the way it was (read: subtly broken.)

@kingdonb No problem, pushed.
I also set the syslog script to start with 10_ so the order is fixed and it matches the /etc/my_init.d/00_regen_ssh_host_keys.sh script.
This should also fix issue #436 (Lost log messages in docker logs) for reference.

There will still be a problem with the syslog-forwarder, however, since that service is still not synchronized. I have experimented with syslog-ng.conf to output directly to the docker console, without any luck yet, but may address that in a separate PR.

So this breaks logging to the docker console with https://github.com/phusion/baseimage-docker/pull/438, since the syslog-ng stdout pipe is not getting to the console.
Please do not merge, I will have to revise.

This latest commit will preserve the STDOUT file descriptor, so the logs forward completely to the docker output.
I have also removed the call to init.d, and it no longer uses start-stop-daemon to supervise because of it.
$ docker run phusion/baseimage:0.9.22
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/my_init.d/10_syslog-ng.init...
Oct 31 22:42:35 a25d8e4afa0b syslog-ng[11]: syslog-ng starting up; version='3.5.6'
Oct 31 22:42:36 a25d8e4afa0b syslog-ng[11]: EOF on control channel, closing connection;
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 17
Oct 31 22:42:36 a25d8e4afa0b cron[20]: (CRON) INFO (pidfile fd = 3)
Oct 31 22:42:36 a25d8e4afa0b cron[20]: (CRON) INFO (Running @reboot jobs)

^C*** Shutting down runit daemon (PID 17)...
*** Running /etc/my_init.post_shutdown.d/10_syslog-ng.shutdown...
Oct 31 22:42:45 a25d8e4afa0b syslog-ng[11]: syslog-ng shutting down; version='3.5.6'
Oct 31 22:42:45 a25d8e4afa0b syslog-ng[11]: EOF on control channel, closing connection;
*** Killing all processes...
`

Can someone check the memory usage before vs. after this PR?
On 2017. Nov 1., Wed at 18:18, Travis Rowland<EMAIL_ADDRESS>wrote:

@Theaxiom approved this pull request.
LGTM! Thanks everyone! 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phusion/baseimage-docker/pull/425#pullrequestreview-73548901,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeKj4AWILZcRL2VoxM2uqN3EljawIlPks5syKfWgaJpZM4OLboU
.

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.5  32312 10676 ?        Ss   18:09   0:00 /usr/bin/python
root        11  0.0  0.3  72376  7824 ?        S    18:09   0:00 /usr/sbin/syslo
root        17  0.0  0.0   4400  1188 ?        S    18:09   0:00 /usr/bin/runsvd
root        18  0.0  0.0   4248   672 ?        Ss   18:09   0:00 runsv cron
root        19  0.0  0.0   4248   656 ?        Ss   18:09   0:00 runsv sshd
root        20  0.0  0.1  29276  2868 ?        S    18:09   0:00 /usr/sbin/cron

There's no change here, a few kb less maybe since there's no runsv for syslog-ng.

Thanks @sundbry for your diligence and hard work, it is greatly appreciated! I have merged this into master now. Thank you @hyperknot and @kingdonb for your contributions as well and ensuring that only the highest quality contributions make it into release. 👍

Also, please raise the minor version to 0.10.0 as this is breaking compatibility with child images. We should also document somewhere that lines like:
touch /etc/service/syslog-ng/down
rm -rf /etc/service/syslog-ng

Will have no effect, and need to be changed.
Also
touch /etc/service/syslog-forwarder/down

Will break the build since that folder no longer exists.


Automates terraform documentation generation

Hey @npalm
I wrote some bash that wraps terraform-docs and pandoc to auto-generate the terraform documentation. As part of this, I've moved the 'base' READMEs to a _docs folder for each module. The resulting README.md should look like same with the one exception being that the terraform-docs table is now appended to the end of each module's README.md.
Assuming I'm not too far from the mark I guess the next step is integrating this into the existing CI?
I held off on adding a blurb to the main README.md on how to generate these docs b/c I wasn't sure if those types of instructions would work better in a contribution guidelines doc or as a separate contributing heading in the README. There are a few boilerplate templates out there for the standalone contributing docs but I didn't want to make any assumptions about your project. Either or I can provide a simple howto for doc generation if you'd like.

@userhas404d thanks, will check your proposal in the next days.

Yet I think it is time to start writing a contribution guide :) Feel free to make any proposal.

I am quite happy with our contribution. But not sure if it should be part of the CI. Since it results each time in a commit. Having it for the moment in a contribution guide would be great. Other option could be a post commit.

I understand. I have a similar workflow set up where on commit the README is generated and forces the CI to fail if there's a diff between the generated README and the existing README. Was thinking more along the lines of 'keep the codebase in check' as opposed to 'generate the README on commit/push/etc'
Turns out there's a decent pre-commit hook that's doing this already.. Looks like they're using perl to insert the terraform-docs output between comments in the README itself. Would probably be easier to incorporate this instead and it has the added bonus of not impacting your existing README layout.

@userhas404d just would like to know I am horrible busy these days. Will merge your PR as soon I have some time. Hopefully the weekend.


In browser python linter

in browser python Linter would be best for VSCode Web.
maybe using this:
https://skulpt.org/

Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue.


Fix get instr normalization

Attempting to patch an PIE ARM thumb binary (attached) produces the following error.
Traceback (most recent call last):
  File "/workdir/tests/test_arm.py", line 75, in test_insert_instruction_pie_patch
    self.run_one(
  File "/workdir/tests/test_arm.py", line 192, in run_one
    p.apply_patches()
  File "/workdir/src/patcherex2/patcherex.py", line 57, in apply_patches
    patch.apply(self)
  File "/workdir/src/patcherex2/patches/instruction_patches.py", line 51, in apply
    p.utils.insert_trampoline_code(
  File "/workdir/src/patcherex2/components/utils/utils.py", line 18, in insert_trampoline_code
    assert force_insert or self.is_valid_insert_point(
  File "/workdir/src/patcherex2/components/utils/utils.py", line 103, in is_valid_insert_point
    return self.get_instrs_to_be_moved(addr) is not None
  File "/workdir/src/patcherex2/components/utils/utils.py", line 95, in get_instrs_to_be_moved
    if not self.is_movable_instruction(insn_addr):
  File "/workdir/src/patcherex2/components/utils/utils.py", line 108, in is_movable_instruction
    asm = self.p.disassembler.disassemble(insn, addr, is_thumb=is_thumb)[0]
IndexError: list index out of range

printf_pie.zip
This PR fixes this issue by making sure to check for the thumbness first before denormalizing the address and adds a small unit test that tests for this issue.

@Ninja3047  Thank you for the PR! It looks good to me. Please ignore the private-test; that's actually a CI issue. Could you provide the source code and compiler flags so that we may reuse it for other architectures in the future? Just pasting them here as a reply would be great.

@Ninja3047 Thank you for the fix! It looks good to me. Please ignore the private-test that's actually a CI issue. Could you provide the source code and compiler flags so that we may reuse it for other architectures in the future? Just pasting them here as a reply would be great.

FROM ubuntu:22.04

RUN apt-get update && apt-get install -y gcc-12-arm-linux-gnueabihf

#include <stdio.h>

int main(int argc, char* argv[]) {
    printf("%s", "Hi");
    return 0;
}

compile flags are the default ubuntu compiler flags
arm-linux-gnueabihf-gcc-12 -o printf_pie printf_pie.c


Add ability to autotile more finely based on bitmask grid

Currently, auto tiling is based entirely on what tile is adjacent to another. This is fine in some instances, but if for example, you want to create the top left image, it is impossible. It will instead look like the top right image. I believe a "bitmask autotiling mode" would fix this.
The first conception I came up with was to add a "bit layer" to tilemaps that you could draw on.
Essentially you draw pattern the size of the bitmap editing grid for where you want a certain material to be, and the autotiler lays down the corresponding tiles.
I think my current conception of this solves the problem more elegantly, and without adding a new data layer. In this version in "bitmask autotiling mode", the place inside each tile you click determines what tile is placed. For instance, if you have grass selected, and you click and drag along the edge between two dirt tiles, it would place a transitional grass tile on either side of that edge. Clicking on a corner, you would see each become a corner transition etc.
The bottom two images illustrate where you would click in blue and where the actual tile grid is in red. The bottom right corresponds to a 3x3 bitmask. The bottom left image corresponds to an edge-based bitmask (2x2 turned 45 deg); which is the ideal sub grid the tiles used in the example. (this is the same as in issue #17063)

While this feature would go along nicely with adding ignored bitmask bits (#18134), I think it may take some brainstorming to make code that determines what you mean when drawing in these ignored spaces in the tilemap editor.

Check the proposals here and try the new TileMap/TileSet editor in 4.0 nightly builds before opening a proposal.

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


luci-app-olsr: OLSR 0.9.5 now with prettyfied jsonplugin

Older OLSRd-version outputs JSON humanreadable over multiple lines. now its also readable for browsers. but the http headers had to be removed.
the ETX mathematics also has changed: multiplication with 1024 now gone.
see also
https://github.com/openwrt-routing/packages/pull/242
https://github.com/openwrt/luci/pull/879/commits/8ca5d6da9640f78b67081f2d1edeb0a6d0ca2120
https://github.com/openwrt/luci/pull/874
@bittorf please have a look

the multiplication-stuff does not seem backward compatible for older olsrd-versions. for the jsonplugin ACK from me - thank you!

@bittorf ok, thank you

@jow- can you please merge this? i think making it "backward compatible" is not needed here.

The commits should be signed off properly...

@FreifunkUFO - please sign the commits.

sorry, i am still not able to do that. @bittorf please can you sign it?

@FreifunkUFO will do it this evening lazy bastard 8-)

please drop the old pullrequest and use this, which is basically the same but 'signed'
https://github.com/openwrt/luci/pull/929


Update Go to version 1.4.2

This pull requests updates the following things:

Update Go from version 1.4.1 to the latest stable version 1.4.2.
Make box description explicit about the goal of this box.

As a reference, this is what is fixed in Go 1.4.2:

go1.4.2 (released 2015/02/17) includes bug fixes to the go command, the compiler and linker, and the runtime, syscall, reflect, and math/big packages. See the Go 1.4.2 milestone on our issue tracker for details.

Looks good, thanks


Allow ScrollBar to watch ScrollContainer in tree

The ScrollBar is allowed to watch the ScrollContainer if both are in the tree.
That is, according to the orientation of this ScrollBar, the corresponding ScrollBar in the ScrollContainer is shared with this ScrollBar.
This patch will make it easy to replace the internal ScrollBar of the target ScrollContainer in the editor:

Set the corresponding *_scroll_mode in ScrollContainer to SCROLL_MODE_SHOW_NEVER; (Scrolling is not available and will be fixed by #63562.)
Add an extra ScrollBar and set its watch_target_path to the path of the target ScrollContainer.

https://user-images.githubusercontent.com/30386067/181773134-cd8b1a6a-e48b-4d4b-8431-f54b992f24cb.mp4
Close godotengine/godot-proposals#5012

Something like this needs a proposal first to see if this is indeed an issue that many need fixing, and if this is indeed the solution that would be the best for the issue.

Implementation looks ok, but I wonder if this really should be inside ScrollBar. It looks like something that should be in ScrollContainer. But then it would become more complex, idk 🤔


fixed variable names in script

IMPORTANT: only merge after https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/690


'new goog.Uri' throws exceptions on certain types of URIs

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=566

TL;DR any URIs encoded via escape() have the potential to throw. escape() encodes them in a format not compatible with the standard decodeURIComponent.
One potential fix here is to find/replace any escape() encodings that deviate from the standard UTF-8 encodings. From ref-urlencode, it seems to be approximately %80 through %FF.
From the original issue:
Most types of malformed URIs are handled incorrectly, but this one throws an exception:
var uri = new goog.Uri(
    'http://www.cpdee.ufmg.br/~elt/docs/DSP/Microsoft%20PowerPoint' +
    '%20%20Aula_01_Aritm%E9tica.pdf')

decodeURIComponent blows up trying to decode it.
More concretely decodeURIComponent('%E9') throws.
escape('é') -> "%E9"
encodeURIComponent('é') -> "%C3%A9"


Don't require the huge BC7m6 tables if this format is disabled

A rather trivial change -- the 1.3 MB file might be considered excessive when bundling the transcoder sources in another project, don't require it to be present when not needed.

Good catch - thanks a lot!


There are no unrendered fields in it that could cause the issue you mention.

The validate function return errors = { hidden: true }.
I'm just simulate the situation where the input is not rendered but validation is failing. So no submission is desirable.

(on the sandbox the field is omitted completely)

OK, so your sandbox was incomplete.
In this case I don't know what the outcome should be as I don't have enough context on the form's validity logic. cc @erikras

@phuongnd08 Why would you even want to validate hidden fields?


Finished bare bones game input, and added an attribute called NamedMultiform.

The attribute NamedMultiform is an attribute which can be applied to a multiform class to give it a specific name, if you want to do that for whatever reason. So for example, if you type
[NamedMultiform("Level")]
public class LevelMultiform : Multiform { }

Then in the Engine.MultiformManager, LevelMultifom's name will be "Level". So for example, you can type MultiformManager.Construct("Level").

FaNcY


128x32 RGB Matrix

Hey, i tried to set up a 128x32 matrix but after i uploaded the code it doesnt display the aurora demo or anything else correctly. When im using matrix width at 64 and height at 32 i works correctly and displays on both the same. But width matrix width at 128 and height at 32 it just display`s random pixels
Here is a video:
https://drive.google.com/file/d/16BezRXYpocoWVlfiUOlObM921X3q0c3o/view?usp=sharing

Not sure how I can diagnose.... could be anything Check the wiring, power, try another sketch. Can you run the sketch with SERIAL_DEBUG enabled (refer to the .h file to enable) and print the output here?


Tigger for cron jobs doesn't actually start one

What steps did you take and what happened:
I click the trigger menu item on a cron job, the alert that the cron job was started show at the top of the browser, however no job was actually started
What did you expect to happen:
I expected the job to be started
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Octant version 0.15.0
Kubernetes version 1.18.2
OS(macOS 10.15

Are you able to create a job via kubectl create job --from=cronjob/<cron-name> <job-name>? Do events say anything on a manual trigger?

Yes I can create it via kubectl, and there is nothing in the Events for the manga; trigger.
Terry Humphries
STRATUS Operations Lead
GTP Services, LLC
816-377-1113
<EMAIL_ADDRESS>This email is the property of GTP Services, LLC and may contain confidential and/or privileged information.
If you are not the intended recipient or have received this e-mail in error please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
On Sep 4, 2020, at 2:18 PM, Sam Foo <notifications<EMAIL_ADDRESS>wrote:
Are you able to create a job via kubectl create job --from=cronjob/ ? Do events say anything on a manual trigger?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/vmware-tanzu/octant/issues/1323#issuecomment-687333638, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK7G2ZNYW6X7HG2MXQ37ZN3SEE4PHANCNFSM4QYQVMDQ.

I'm unable to replicate this with examples from https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/
@trhumphries are you able to provide the YAML for the cronjob with any sensitive details scrubbed.
Maybe it is something with how Octant is interacting with the specific way our cronjob is declared. It's a long shot, but worth checking to be sure.

I have the same issue. The banner on top tells me the that the job with name xxx has started but in fact nothing starts. I'm able to trigger the job through kubectl (and the kubernetes-dashboard). Nothing in Events.
Environment:
Octant version 0.19.0
Kubernetes version: 1.17.12 on EKS
OS(Windows 10 pro): 10..0.19042


Feature Request: Slider to adjust stroke step freuency/detail

As mentioned in the other Feature Request, I love how easy it is to do quick sketches and create placeholder graphics with this plugin, but they always look a bit choppy, due to the amounts of points used to draw the line.
I looked through the script, trying to find where this frequency is set, but count not find it. Maybe you could expose this as a slider in the Inspector so people can draw smoother curves or even more angular designs if they want to?
Thank you again!

Hi @golddotasksquestions, thanks for the feature request.
The point frequency is actually controlled by the MIN_POINT_DISTANCE constant, so it should be relatively simple to implement a way to adjust this value in a UI.
Does the choppiness you are referring to happen on sharp angles? If so, lowering this value will actually make this worse, as the draw_multiline function does not allow to control the joint drawing mode, and will instead default to sharp.
The a way of fixing this is by manually drawing the joints with draw_circle, but this is really slow due to the number of individual draw calls required.
An alternative method is by using a Line2D to draw the stroke, instead of utilizing the _draw function.
I will open a separate issue for fixing the line choppiness and keep this one open for the point freq slider feature request.

Adjustable minimum point distance was implemented in #6 and will be available in the next release.

Does the choppiness you are referring to happen on sharp angles?

with "choppiness" I was actually referring to the number of points, not the corners. Faster movements made it obvious the line from point to point is actually straight, so drawing a circle looked more like drawing a polygon (a circle with chopped off sides).
I did not mind the sharp angles on corners when drawing zig-zag lines. But without the sharp corners it's fine too. Line2D offers the ability to chose, which is nice of course.

The round joints will probably still diminish the obviousness of the number of points in a stroke, however it seems what you are observing is more related to the processing speed of the godot editor?
Point frequency is determined by distance to the previous point, and not an amount of time passing so faster movements should in theory not change the point density.
The only other thing that would control how often points are drawn is the fps of the editor, so if your editor is lagging a bit, the strokes will not be as smooth either.


fix: add support for passing null in prefix

Description
Added  support for passing null in prefix
###issue : https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vpc/issues/598
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[x] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

When merging, use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

/run pipeline

@Khuzaima05 see comments. Can you also please paste a terraform plan output when prefix is set to null ?

/run pipeline

So @Khuzaima05 from the screenshot (which looks like its a plan from an existing terraform state), the current code is giving an error. Are you looking in to that?

/run pipeline

/run pipeline

So @Khuzaima05 from the screenshot (which looks like its a plan from an existing terraform state), the current code is giving an error. Are you looking in to that?

This error got resolved.

@Khuzaima05 see comments. Can you also please paste a terraform plan output when prefix is set to null ?

Recieving the same error in plan if we pass NULL in example.

@Khuzaima05 Passing null for prefix does not work. I cloned your branch and updated the main.tf default example like this:
module "slz_vpc" {
  source                                 = "../../"
  resource_group_id                      = var.resource_group != null ? data.ibm_resource_group.existing_resource_group[0].id : ibm_resource_group.resource_group[0].id
  region                                 = var.region
  name                                   = var.name
  prefix                                 = null
  tags                                   = var.resource_tags
  access_tags                            = var.access_tags
  enable_vpc_flow_logs                   = var.enable_vpc_flow_logs
  create_authorization_policy_vpc_to_cos = var.create_authorization_policy_vpc_to_cos
  existing_cos_instance_guid             = ibm_resource_instance.cos_instance[0].guid
  existing_storage_bucket_name           = ibm_cos_bucket.cos_bucket[0].bucket_name
  address_prefixes                       = var.address_prefixes
  network_cidrs                          = var.network_cidrs
}

The error I get is:
│ Error: Invalid template interpolation value
│
│   on ../../dynamic_values.tf line 7, in module "dynamic_values":
│    7:   prefix               = "${var.prefix}-${var.name}"
│     ├────────────────
│     │ var.prefix is null
│
│ The expression result is null. Cannot include a null value in a string template.

Looks like there are 3 more places you need to make the change to support passing null for prefix:

https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vpc/blob/25cfdcaeedd851224c3a04c1492e722859307c30/dynamic_values.tf#L7
https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vpc/blob/25cfdcaeedd851224c3a04c1492e722859307c30/dynamic_values/main.tf#L20
https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vpc/blob/25cfdcaeedd851224c3a04c1492e722859307c30/network_acls.tf#L164

Please update these and show me the output of your test when passing null for prefix

@Khuzaima05 This is NOT how to test it. You do not want the pass null for the prefix variable in the example. you want you pass null into the VPC module directly. Just like I showed you in https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone-vpc/pull/605#issuecomment-1689534168

@Khuzaima05 This is NOT how to test it. You do not want the pass null for the prefix variable in the example. you want you pass null into the VPC module directly. Just like I showed you in #605 (comment)

@ocofaigh , I tested accordingly, here is the terraform output (default example) :

Yes thanks, please push the code updates @Khuzaima05

/run pipeline

/run pipeline

/run pipeline

/run pipeline

@ocofaigh Upgrade test is failing, Can I skip that.

@Khuzaima05 no - upgrade test should not fail with the changes being made in this PR - we need to figure out why its failing

@ocofaigh  Pipeline passed, Could you please review and merge.

:tada: This PR is included in version 7.4.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Move non-processor drivers out of targets

Things like the flash driver on G120, that's not LPC17 specific. It should be in its own Drivers folder which gets included by the G120 device definition.

Done!


Figure 1 Discussion

Let's use this issue to discuss modifications to Figure 1. Code added in #19.

Figure 1. Cell Painting and L1000 data provide complimentary measurements of compound perturbations across doses. (a) Percent replicating scores calculated via median pairwise correlations between replicates of compound perturbations across dose. We generated the non-replicate distribution from matched randomly sampled non-replicate groups. See methods for full details about sampling and data processing. The dotted blue line indicates the 95th percentile of the non-replicate distribution. (b) The L1000 and Cell Painting assays reproducibly measure a complementary set of compound perturbations. The three numbers represent (from top to bottom) the number of reproducible compounds unique to L1000, the number of overlapping reproducible compounds between the two assays, and the number of reproducible compounds unique to Cell Painting. (c) Percent matching scores calculated via median pairwise correlation of level 5 consensus signatures of compounds mapping to the same mechanism of action (MOA) across dose. The dotted blue line indicates compounds significantly matched to their MOA based on a non-parametric p value (see methods). (d) The L1000 and Cell Painting assays each capture a complementary set of compound MOAs. The three numbers represent counts reflecting the ordering as described in panel b. (e) Consensus signatures of select MOAs demonstrate high heterogeneity across assays and doses.

[ ] Some heatmaps are missing dividing lines between compounds for some reason. I just need to slightly tinker with plot size

from @shntnu

[ ] Add the "overlapping" category to the legend to reflect this and drop the legend title ("Assay")

[ ] Confirm that the percent replicating numbers and null distribution are being derived from the overlapping compound set

[ ] Add supplementary figure comparing Cell Painting compound median replicate correlations with the same replicate counts as L1000


Integration of v8n library instead of typescript

Is your feature request related to a problem? Please describe.
I know we are integrating typescript to control how our API is called but maybe is a bit over-engineered for the first iteration. I found this library on the Internet which looks pretty nice and useful at a first look: https://github.com/imbrn/v8n
Describe the solution you'd like
To check this library and evaluate if it's worth it against TypeScript
Describe alternatives you've considered
No alternatives considered yet
Additional context
Source: https://github.com/imbrn/v8n

Well to me... I was thinking about the checks of types (.string(), .Integer(), etc...). The moment we use types with TypeScript, this would lose its purpose right?

I don't think that the purpose of that lib is to "simulate" a type system, but more on creating complex rules and validate them in with a centralized and clear API. Can be useful as an utility in other part of the code, but not atm IMHO.

Close due to inactivity


first try on CI with caching

Description
CI.yml file update to have caching and faster tests
Todos

[ ] Working new file

Status

[ ] Ready to go

Codecov Report

Merging #17 (da0b8ea) into main (f3fb00a) will not change coverage.
The diff coverage is n/a.


Better documentation

Really need some better documentation. I would like to see some wiki pages please with examples.

I was hopeful that the links to documentation from the readme would help, but this url 404's: http://flatiron.github.com/api-easy

I totally agree.  I'm using this for work, and we're behind schedule, but due to our finicky api (not written by us), other systems wouldn't correctly send POST calls.  This one does, but I've got 9 tabs open from googling how to use the damned thing.

Hey guys I've made my own API test tool with a nice README if anyone's interested...
https://www.npmjs.com/package/teqlabs-testify
Sent from my iPhone

On Oct 22, 2015, at 4:53 PM, kassimir<EMAIL_ADDRESS>wrote:
I totally agree. I'm using this for work, and we're behind schedule, but due to our finicky api (not written by us), other systems wouldn't correctly send POST calls. This one does, but I've got 9 tabs open from googling how to use the damned thing.
—
Reply to this email directly or view it on GitHub.


3008 slowpath execute exponential backoff

Description

Type of change

[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[ ] Refactoring
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires changes in customer code

High-level change(s) description - from the user's perspective

Related Issue(s)
Fixes
Related pull request(s)

Looks like updates to schema.sql is missing, will add and resolve, the merge conflicts as well.


Timed transition start time update

Hi
I am using arduino-fsm for a two-button system, where I have to detect multiple events (single click, double click, muliple clicks...). In one of the states I had 2 possible transitions, one timed (the user keeps the button pressed and the transition "times out") and one "standard" (the user releases the button before the timeout). If the "standard" transition is triggered the timed transition start time is not updated and remains at the previous value during the next iteration, resulting in a lower (if not even 0) interval.
I've corrected this bug moving the update after every state change; this also has the advantage of a more precise start time, as the user doesn't have to call check_timer in order to update start to millis().
In this pull request I've also added the fix for bug #4

I force-pushed a small fix: now millis() is called only once at the beginning of update_timed_transitions_starts() and its result is saved in millis_value

Thanks for this commit.
It solves an issue where, if I return from one timed transition to another timed transition before the timer interval has expired, the next timed transition would happen immediately.


Fix code coverage for importing modules

I don't expect this to be merged in, but this was the only way I could get import modules to 100 coverage. I have instructed the babel transformer to add the istanbul ignore comment and have done a search for function _interopRequireDefault(obj) and replaced it with /*istanbul ignore next */\nfunction _interopRequireDefault(obj).
For some reason babel does not add the auxiliaryCommentBefore before the _interopRequireDefault. I'm going to add an issue on babel about it.

Actually I will completely understand if you don't want to add this in especially since I found this: https://phabricator.babeljs.io/T6787 I'm going to try and fix it and send a PR to babel.

Hi, sorry, I did a lot more research and I just pushed a new version of the code. I found that utilizing babel-plugin-transform-runtime prevents the issues from arising because the functions that are normally embedded in the output JS are replaced with require('babel-runtime/*').

Hey! The contents of this repo moved into jest itself: https://github.com/facebook/jest/tree/master/packages/babel-jest
Feel free to open a pull request there :)


Upgrade Start & Min limits do not work

When I try to set the value of the start and min it does not have any effects and still spends coins.
"auto_upgrade_start":<PHONE_NUMBER>,  # Start buying upgrades when the balance is greater than this amount
"auto_upgrade_min":<PHONE_NUMBER>,  # Stop buying upgrades when the balance is less than this amount
I have set it to 1 Billion and 1 Hundred million to start spending coins and stop when less that 1 billion.
But it spent almost 800 millions and did not stop.

READ COMMENTS:
            "auto_upgrade_start": 2_000_000,  # Start buying upgrades when the balance is greater than this amount
            "auto_upgrade_min": 100_000,  # Stop buying upgrades when the balance is less than this amount
            # This feature will ignore the auto_upgrade_start and auto_upgrade_min.
            # By changing it to True, the bot will find the overall best card and then wait for the best card to be available (based on cooldown or price).
            # When the best card is available, the bot will buy it and then wait for the next best card to be available.
            # This feature will stop buying upgrades when the balance is less than the price of the best card.
            "wait_for_best_card": True,  # Recommended to keep it True for high-level accounts
            "enable_parallel_upgrades": True,  # Enable parallel card upgrades. This will buy cards in parallel if the best card is on cooldown. It should speed up the profit.
            "parallel_upgrades_max_price_per_hour": 1000,  # Cards with less than X coins per 1k will be bought


More constraints

Adds UI support for constraints introduced in https://github.com/apache/brooklyn-server/pull/999

@tbouron i think the logic now (after last push) does the best thing for corner cases such as blank string (counts are being set but not acceptable when "required") and false (also counts as being set).  also it's a bit simpler.
can you eyeball and merge?  i've tested it with the blueprint at https://github.com/apache/brooklyn-server/pull/999#issuecomment-423919250 and it seems to work as expected.

NP, will review tomorrow morning @ahgittin


apps sc: fixes mismatched s3 config in elastic backup

What this PR does / why we need it: Part of qa testing for v0.7.0. Fixes elasticsearch backups failing due to mismatching config in backup job and elasticsearch
Which issue this PR fixes (use the format fixes #<issue number>(, fixes #<issue_number>, ...) to automatically close the issue when PR gets merged): #15
Public facing documentation PR (if applicable)

Special notes for reviewer:
Checklist:

[ ] Added relevant notes to WIP-CHANGELOG.md
[ ] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[ ] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Also see this PR for changes to the opendistro helmchart https://github.com/elastisys/opendistro-build/pull/30


Vickel: Watch greyspacecomputing.com

Vickel requests the watch of the watch_keyword greyspacecomputing\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

greyspacecomputing\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Ryan M in Charcoal HQ


[Exam] Complaing is possible even though there are no scores shown

Describe the bug
When the release date of the results is not set but the review period is, the student is allowed to complain, however, no scores are shown, which makes it misleading. We should make setting the release date mandatory and not allow the start student review date to be before the release date.
To Reproduce

Create an exam, with no result release date. Set the student review period
Participate in the exam, evaluate your submissions.
As a student again, go to the exam summary page.

Expected behavior
You should not see the complaint component or the scores should also be shown
Screenshots
Environment

 - OS: Windows
 - Browser chromium

I consider this as a mistake of the instructor (setting the dates incorrectly), so this is low priority, but of course, it would be nice if it gets fixed


RpcInvocation adds returnType assignment in initParameterDesc

What is the purpose of the change
RpcInvocation adds returnType assignment in initParameterDesc
see more detail from #7745
Brief changelog
Verifying this change

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Can this line be deleted?

Can this line be deleted?

greet! i think this line can be deleted.

Codecov Report

Merging #7746 (793eca5) into master (e845e16) will decrease coverage by 0.30%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #7746      +/-   ##
============================================
- Coverage     59.28%   58.97%   -0.31%
+ Complexity      529      527       -2
============================================
  Files          1077     1080       +3
  Lines         43565    43604      +39
  Branches       6368     6339      -29
============================================
- Hits          25826    25715     -111
- Misses        14879    15037     +158
+ Partials       2860     2852       -8

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/org/apache/dubbo/rpc/RpcInvocation.java
64.73% <100.00%> (+0.20%)
0.00 <0.00> (ø)

...ntext/event/AwaitingNonWebApplicationListener.java
48.48% <0.00%> (-24.25%)
0.00% <0.00%> (ø%)

...ng/transport/dispatcher/all/AllChannelHandler.java
68.96% <0.00%> (-20.69%)
0.00% <0.00%> (ø%)

...rg/apache/dubbo/remoting/utils/PayloadDropper.java
76.92% <0.00%> (-15.39%)
0.00% <0.00%> (ø%)

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
0.00% <0.00%> (ø%)

...bo/config/event/listener/LoggingEventListener.java
50.00% <0.00%> (-12.50%)
0.00% <0.00%> (ø%)

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
0.00% <0.00%> (ø%)

...in/java/org/apache/dubbo/common/utils/JVMUtil.java
81.13% <0.00%> (-11.33%)
0.00% <0.00%> (ø%)

...dubbo/remoting/exchange/support/DefaultFuture.java
77.87% <0.00%> (-9.31%)
0.00% <0.00%> (ø%)

.../dubbo/remoting/transport/netty4/NettyChannel.java
53.46% <0.00%> (-7.93%)
0.00% <0.00%> (ø%)

... and 54 more

Continue to review full report at Codecov.

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


[fix][doc] remove irrelevant components metrics links under broker section

Fixes #xyz

Master Issue: #xyz
Motivation
On the https://pulsar.apache.org/docs/2.10.x/reference-metrics#broker listed all components metrics ToC links but it should only display for the broker section.

Modifications

Removed irrelevant components metrics links under the broker section.
Preview for this PR:

Verifying this change

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

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] Anything that affects deployment

Documentation

[x] doc
[ ] doc-required
[ ] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Thanks for your contribution! May I ask why the contents in the green boxes are not exactly the same?

Thanks for your contribution! May I ask why the contents in the green boxes are not exactly the same (while they should be)?

I think they should keep same, and I guess I find some issues here

Duplicate for Replication metrics

The markdown title level should be 3 not 4 on Replication metrics which make the right side ToC miss to scrape it.

@Anonymitaet I recheck the broker metrics list with each metrics content. After the fix, the list will keep consistent and I will apply the fix to previous version doc.
The preview looks like

Hi @ericsyh

They are still not the same, right?

Why would we add a ToC after the broker section even though users can see the structure from the right navigation panel? Is it duplicated effort?

@ericsyh thanks for your work! I suggest keeping the ToC on the navigation panel only because:

Readers: have a single source of truth (content) and a better reading experience (because the useful content length is shorter)
Maintainers: eliminate maintenance efforts. The ToC under the "broker" section might be generated from some editor tools (e.g. VS Code) automatically, which is error-prone.

cc @momo-jun @DaveDuggins @D-2-Ed

@Anonymitaet Applied the suggestions. It will look like


Cannot trigger Winter Festival

Cannot trigger Winter Festival when challenge phase ends to get 2 power. Have to do manually
See attached.

Thanks for reporting. This is fixed now.


Catch UTF symbols

Some UTF symbols can be converted by Java to normal ASCII (source).
Example:
${jnd${upper:ı}:ldap:URL}

Maybe we can block all requests that contain UTF symbols altogether as I can't imagine a situation when they are used in URIs or headers. But it seems too blunt, maybe there's a better way.

Aren't they url-encoded by Nginx when they arrive at Nginx?

In the nginx access logs they do become escaped:
"${${jnd${upper:\xC4\xB1}:ldap:localhost/log4shell_test}"

But does it mean they're neutralized?

There are more known attack vectors, like date or environment variables. As of now there is 13 different bypass techniques: https://github.com/Puliczek/CVE-2021-44228-PoC-log4j-bypass-words


Add Travis CI support

Parallelize Travis-ci tox tests
Add Travis-ci badge

Nope, it's just that if in the future we add support for 3.5, it looks nicer to have it at the end after 2.7 :)

Nope, it's just that if in the future we add support for 3.5, it looks nicer to have it at the end after 2.7 :)

Makes sense to me!
:+1:


Issue run package

Please do not submit this issue.

[X] I understand

Hello, Just traied tu run yarn run package:linuxb and I have this issue
> Error! Unexpected token, expected "{" (14:7)   /mnt/c/metaplex/js/packages/cli/node_modules/react-native/index.js error Command failed with exit code 2.
Any idea, please

Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.


can't compile with ghc-7.10

Compile success if higher-leveldb.cabal like:
build-depends:       base == 4.*
, cereal
, lifted-base
, leveldb-haskell
, bytestring
, resourcet
, transformers-base
, mtl
, monad-control
, data-default
, transformers

The issue was GHC 7.10 required mtl >= 2.2, and I had an upper bound on 2.2. I've uploaded a new version that supports mtl <= 2.3.


events with same ID should not be replaced

In some cases an event would have the same ID of an existing one (as we pull snapshots, this can happen, as IDs are not generated upstream).
The issue is that some (previously ignored) fields can be updated, and screw the import process, generating duplicates.
This PR fixes that issue by not overwriting already existing documents

/cc @gamli75

/retest


gluon documentation bug

Dear all,
in the gluon documentation of the neural network layers (Versions(master)), the mxnet.gluon.nn..HybridLambda(function, prefix=None) appears only in the analytic description of the page, but is not listed in any of the tables in the beginning. I think this is missing.
Thank you for all your great work.

Indeed. Sorry that I missed it. Would you mind adding it to the list at the top?

Hi @szha, not at all but I don't know how to do so.

@feevos thanks! You can add the missing entries in this file https://github.com/apache/incubator-mxnet/blob/master/docs/api/python/gluon/nn.md

Thanks @szha I am closing this and I hope I haven't created more trouble than help with my ignorance in contributing (getting there ... :) ).


 These should not be classed as psychiatric disorders."

Also, sexual disorder (MONDO_0000595) has the exact synonym of "sexual and gender identity disorders", suggesting that gender identity disorder (MONDO_0001500) should be related to sexual disorder?

note to self - need to revise the superclass for 'sexual disorder' - not sure what the best parent should be, need to look into thiis

Looking at this more closely - the mappings for the term MONDO_0000595 'sexual disorder' suggest this is actually a psychiatric disorder.
NCIT:C92202 is Sexual and Gender Identity Disorders and MONDO 'sexual disorder' is using the text def from NCIT:C92202  Sexual and Gender Identity Disorders.
DOID:0060043 'sexual disorder' is an equivalent class and the text def is:
A disease of mental health that involves the impairment in normal sexual functioning.
SCTID:231532002 'sexual disorder' has the Semantic Types: | Mental or Behavioral Dysfunction | Mental or Behavioral Dysfunction | Mental or Behavioral Dysfunction
UMLS:C0236989 has the same label and text def as NCIT.

Move MONDO_0002134 'physiological sexual disorder' to a child of MONDO_0005039 'reproductive system disease'.

this seems reasonable
On Mon, Dec 16, 2019 at 4:20 PM Nicole Vasilevsky<EMAIL_ADDRESS>wrote:

Looking at this more closely - the mappings for the term MONDO_0000595
'sexual disorder' suggest this is actually a psychiatric disorder.
NCIT:C92202 is Sexual and Gender Identity Disorders and MONDO 'sexual
disorder' is using the text def from NCIT:C92202 Sexual and Gender Identity
Disorders.
DOID:0060043 'sexual disorder' is an equivalent class and the text def is:
A disease of mental health that involves the impairment in normal sexual
functioning.
SCTID:231532002 'sexual disorder' has the Semantic Types: | Mental or
Behavioral Dysfunction | Mental or Behavioral Dysfunction | Mental or
Behavioral Dysfunction
UMLS:C0236989 has the same label and text def as NCIT.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/monarch-initiative/mondo/issues/723?email_source=notifications&email_token=AAAMMONW6ZYML6BHIMQAAQTQZALLZA5CNFSM4HTTLPX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHAT6FY#issuecomment-566312727,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOOPKXG4JVX4JTZ6OYDQZALLZANCNFSM4HTTLPXQ
.


Cannot read property 'maxMessageSize' of null

[x] I have provided steps to reproduce (e.g. a link to a jsfiddle)
[x] I have provided browser name, version and adapter.js version
[ ] This issue only happens when adapter.js is used

Versions affected
Version 65.0.3325.181 (Official Build) Built on Ubuntu , running on Ubuntu 17.10 (64-bit)
adapter.js 6.1.5
Description
While trying to send a data over RTCDataChannel the following Exception is thrown: TypeError: Cannot read property 'maxMessageSize' of null
The bug is pointing to the following code inside webrtc-adapter:
var length = data.length || data.size || data.byteLength;
if (length > pc.sctp.maxMessageSize) {
  throw new DOMException('Message too large (can send a maximum of ' +
           pc.sctp.maxMessageSize + ' bytes)', 'TypeError');
}

And actually pc.sctp is null. This value is possible in the sctp documentation.
I tried to reproduce this bug with an equivalent code: https://jsfiddle.net/kalitine/1b68eLdr/14951/.
But it works there (sctp is not null) and I cannot explain why in my lib sctp value is null (without webrtc-adapter it works).
Steps to reproduce
https://jsfiddle.net/kalitine/1b68eLdr/14951/
Expected results
No exception thrown.
Actual results
TypeError: Cannot read property 'maxMessageSize' of null

The fiddle works perfectly well for me with Chromium version 65.0.3325.181.

what is pc.signalingState and pc.iceConnectionState when that happens?
Also pc.localDescription and pc.remoteDescription

We could change that (but there's not much to gain other than ultimate spec conformance - sending is still not possible at that point, regardless of the error).

I'm getting this error when the RTCDataChannel is open. This monday I'll do more tests and I'll provide more information. In my use case the error is thrown during Karma test running. The code is not the same as in the provided jsfiddle, but very similar logic.
Anyway it worse nothing to add an sctp null check isn't it?

Anyway it worse nothing to add an sctp null check isn't it?

I don't understand. Can you rephrase?

Sorry misspell :). It costs nothing to add an sctp null check isn't it?

will be done in #812 but i'd still like to understand how this happens

I've done a more detailed test. I apologize, it was my mistake (without webrtc-adapter it does not work neither. Test without webrtc-adapter was running with different code version which worked). I provide here all details which I hope might help you somehow or anybody else to not come to the same issue as I did.
I've have updated the jsfiddle which reproduces this case completely (where the problem is actually the code and not webrtc-adapter).
In all cases we have:
Signaling State:  have-local-offer
Ice Connection State:  new
Local Descritpion: {sdp:"v=0 o=-<PHONE_NUMBER>316458427 2 IN IP4 <IP_ADDRESS>...
SCTP :  undefined

The differences are:
Version 65.0.3325.181 (Official Build) Built on Ubuntu , running on Ubuntu 17.10 (64-bit)
Remote Descritpion:  {sdp:"", type:""}
DOMException: Failed to execute 'send' on 'RTCDataChannel': Could not send data

Version 65.0.3325.181 (Official Build) Built on Ubuntu , running on Ubuntu 17.10 (64-bit) + webrtc-adapter
Remote Descritpion:  {sdp:"", type:""}
DOMException: TypeError: Cannot read property 'maxMessageSize' of null

Firefox 59.0.2 (64-bit), running on Ubuntu 17.10 (64-bit)
Remote Descritpion: null
DOMException: An attempt was made to use an object that is not, or is no longer, usable

Firefox 59.0.2 (64-bit), running on Ubuntu 17.10 (64-bit) + webrtc-adapter
Remote Descritpion: null
DOMException: pc.sctp is null

ah... as I suspected, thanks for digging deeper into this.
This will be fixed in #812 which will pass the native error when send is called on a datachannel which is not open yet.

@flippo,
question about your statement:

when send is called on a datachannel which is not open yet.

Based on the sequence diagram in WebRTC Spec
createDataChannel() [7] is way before setLocalDescription(offer) [12].
What would be the possible causes why data channel is not yet opened at this [12] time?

Before the connection has been established, calling createDataChannel is more of an intent to establish such a channel.

original issue should be fixed, please reopen (or holler) if there is still an issue. Thanks!


There are several empty csv's with API redirect message

Hi there, this repo in general should not be used as the source of data truth - instead, please use our API at https://covidtracking.com/api.


Erlang error: {:EXIT, {:noproc, {GenServer, :call, [Sentry.TaskSupervisor,

Environment
erlang 23.1.1
elixir 1.11.0-otp-23
phoenix "~> 1.5"
How do you use Sentry?
Sentry SaaS (sentry.io)
Which SDK and version?
e.g: Elixir "~> 8.0"
Steps to Reproduce

Set up sentry in an umbrella phoenix app following the docs here
Deploy it to Heroku
Get the following error during each deploy

Expected Result
Shouldn't throw any errors
Actual Result
Erlang error: {:EXIT, {:noproc, {GenServer, :call, [Sentry.TaskSupervisor, {:start_task, [{:"server@e26c12c3-fa2d-4590-b295-311e2960a816", Logger, #PID<0.421.0>}, [#PID<0.421.0>], {:erlang, :apply, [#Function<2.95599806/0 in Sentry.Client.do_send_event/3>, []]}], nil, nil}, :infinity]}}}

Maybe related to https://github.com/getsentry/sentry-elixir/issues/339 ?

@subsetpark Thanks for the detail! Could you elaborate on when the LoggerBackend tries to crash a process.?
The issue seems to be that the handler can be re-attached and receive messages before the Sentry application and its children (including the TaskSupervisor) are back up?

Closing this issue for now, but happy to look closer with more details.


Ledger code is not merged!

When hardware wallet?

The devs are not completely motivated to support a closed source hardware wallet.

Perhaps we'll add support for Sekura Hardware Wallet it's out.

such safu!


colcon list error

~/workspace$ colcon list
usage: colcon [-h] [--log-base LOG_BASE] [--log-level LOG_LEVEL] {build,mixin,test,test-result} ...
colcon: error: argument verb_name: invalid choice: 'list' (choose from 'build', 'mixin', 'test', 'test-result')

This is not related to ros2-rust, you probably didn't install all the colcon extensions. The list verb is in the python3-colcon-package-information package.


a test with quickcheck

Continuing https://github.com/aleeusgr/gimbalabs-dandelion-pbl/issues/3
Case
Here is a property check;

for all (a, b, c) strings
the concatenation of a, b and c always contains b

Docs
https://www.cse.chalmers.se/~rjmh/QuickCheck/manual.html

https://www.schoolofhaskell.com/user/pbv/an-introduction-to-quickcheck-testing

3 Test suite qcheck-test: RUNNING...                                                                           [0/52]
2 *** Failed! Falsified (after 3 tests and 4 shrinks):
1 [0]
4   [1]
1 Test suite qcheck-test: PASS

https://www.schoolofhaskell.com/user/pbv/an-introduction-to-quickcheck-testing
More thorough testing


Silent failure with option/command starting with "/"

When an incorrect sub-command or argument which begins with "/" is used, no error is raised. Instead the help message is shown and the command ends with exit code 0.
For example:
(sstcam) ~/Software/sstcam-eventbuilder  develop*    $ sstcam-eventbuilder test                                                                                5.4G 1.76 10:28
Usage: sstcam-eventbuilder [OPTIONS] COMMAND [ARGS]...
Try 'sstcam-eventbuilder --help' for help.

Error: No such command 'test'.

(sstcam) ~/Software/sstcam-eventbuilder  develop*    $ sstcam-eventbuilder -test                                                                                5.4G 1.77 10:28
Usage: sstcam-eventbuilder [OPTIONS] COMMAND [ARGS]...
Try 'sstcam-eventbuilder --help' for help.

Error: No such option: -t

(sstcam) ~/Software/sstcam-eventbuilder  develop*    $ sstcam-eventbuilder --test                                                                                5.4G 1.75 10:28
Usage: sstcam-eventbuilder [OPTIONS] COMMAND [ARGS]...
Try 'sstcam-eventbuilder --help' for help.

Error: No such option: --test

(sstcam) ~/Software/sstcam-eventbuilder  develop*    $ sstcam-eventbuilder /test                                                                                5.37G 1.72 10:28
Usage: sstcam-eventbuilder [OPTIONS] COMMAND [ARGS]...

  Event builder for the SST camera.

Options:
  --port INTEGER  Port on which the gRPC server is hosted.  [default: 50051]
  --ip TEXT       IP address of the gRPC server.  [default: localhost]
  --help          Show this message and exit.

Commands:
  calibration  Commands relating to the online calibration.
  display      Commands relating to the real-time event display.
  gate         Commands relating to the queued events at the gate.
  listener     Commands relating to the UDP packet listener.
  mock         Commands relating to the mock camera UDP server.
  pipeline     Commands relating to the event builder pipeline.
  server       Commands relating to the gRPC server.

I would expect the last command to also error.
I believe the issue #1929 and PR #1930 are related to this bug.
Environment:

Python version: 3.8.0
Click version: 8.1.3

Duplicate of https://github.com/pallets/click/issues/1322


[WIP] Support for exporting environment variables (e.g. HTTP_PROXY support)

On our corporate network, we're required to specify the HTTP_PROXY and HTTPS_PROXY environment variables in order to fetch the images we are attempting to deploy as containers on the provisioned machines.

Thanks!  I think this is a good start for a discussion around configuring the Docker daemon and supporting things like the environment.
These questions are not necessarily aimed at you, I'm just asking to start a discussion :)
In this case, this is specific to Virtualbox / Boot2Docker.  How would we add these to the other providers (without /var/lib/boot2docker/profile)?
I'm also cautious of what this might open up.  For example, in the case of setting system environment variables, this sort of crosses over into a config management area.  I do think we need to be able to configure the Docker daemon but I'm not sure about other system aspects.
One other possible solution is to use cloudinit.  We want to move in that direction anyway and that would allow almost any customization like this from the user.

@ehazlett
Cool, thanks.
From what I could see in host.go, "virtualbox", "vmwarefusion", "vmwarevsphere" drivers use the /var/lib/boot2docker/profile location in the generateDockerConfig method, for anything else it writes the config out to /etc/default/docker.

actually it's a little different for the non-b2d hosts.  For non-b2d, we use /etc/default/docker to provide the options for the Docker daemon -- therefore the HTTP_PROXY etc would not work there.
Also, thinking ahead, another reason to support cloudinit is in the case of different distros.  For example, if you use a distro with systemd or non-ubuntu machine won't work because it most likely doesn't support /etc/default/docker.

Cool -- well, sounds like cloudinit is the way to go :smile:.  Let me know if I should close the PR.


Crash when exiting character profiles

Sometimes, usually the first time booting up the game after a new update, if you go to the Character Profiles in CI and then exit by pressing E twice it'll crash without any error message.

Can't get that to happen. Does it still happen after the latest update?

It happened with that last one yes, and another from last night. It seems to happen only the first time you launch the game after a fresh Windows boot.

Windows 10 user here; I can't reproduce the issue from a fresh boot either. Do you have anything that hooks to the process, such as Steam Overlay, Rivatuner, or the like?

I do not, no, but I am on Windows 11. I'll try to get a video tomorrow if I can get it to happen again. It did happen at least 4 times since last night.

I ought to add a crash handler to the game.

I can't seem to replicate it again, after a fresh boot and installation of the latest update... Strange, haven't changed anything on my end and it seemed fairly consistent on my end.

There is now a crash handler. If you get a crash, make sure to post the screenshot of the error message.

If you're building from source and were updating an existing build, I have an anecdote that may be related.
There was at least one occasion where I pulled the latest commit, called make and ran pd but it would exit consistently (I forget what triggered it).
I deleted the build artifacts and rebuilt from a clean source tree. Afterwards I restored the ini and eeprom files and had no issues even though it was the same commit, settings, save, etc.
My assumption is that maybe some of the necessary objects were not rebuilt when trying to update and that may have been causing a crash somewhere. But I'm not certain about it.
Extra:
It's also possible I mixed optimization flags between those builds, using O3 for build one and O0 (the default at the time) for build two.
Since the default compiler flags in the makefile changed to Og, I wonder if this is also somehow related.

When headers are modified that won't trigger the rebuild of source files that use them, so you need to do a clean build in those cases.

Going to assume this was fixed at some point.


Combine index lookups on different columns of multi-column indexes with different operators

Right now expressions on the columns of a key with different operators, such as:
select * from sales_estimate where act_symbol = 'AAPL' and retrieval_date < '2017-11-01';
Assuming that act_symbol and retrieval_date are two columns in the key, we can't form an index lookup on these terms because the two comparisons use different operators (= and <). Fixing this will take a little thought -- none of the current index interfaces address this possibility for multi-key indexes.

This is the next major expansion in usefulness for indexes

This is now supported!